devel-announce July 2013

devel-announce@lists.fedoraproject.org

6 participants
56 discussions

Fedora 17 End of Life
by Dennis Gilmore 31 Jul '13

31 Jul '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As of 30th July 2013, Fedora 17 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 17. A previous reminder was sent on July 3rd [0]. Fedora 18 will continue to receive updates until approximately one month after the release of Fedora 20. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [1]. The Fedora Project wiki also contains instructions [2] on how to upgrade from a previous release of Fedora to a version receiving updates. Cheers, Dennis [0] https://lists.fedoraproject.org/pipermail/announce/2013-July/003169.html [1] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedu… [2] http://fedoraproject.org/wiki/DistributionUpgrades -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlH5RDcACgkQkSxm47BaWfeGyQCfRaTPrFR2cZfg24tDmyEFL+j8 VIEAnRBsiNAYq+Pc6voWfC3DarHXH+qn =gA5+ -----END PGP SIGNATURE-----

1 0

botan update to 1.10
by Thomas Moschny 26 Jul '13

26 Jul '13

Hi, this is a heads-up that I updated the botan package to the latest stable version 1.10.5 in rawhide, as requested in bug 822421. This changes the API and thus the soname of the library. Also, since 1.9.18, the library and header paths have been changed to allow parallel installation of different versions of the library, so headers are in /usr/include/botan-1.10/botan now, the library is named libbotan-1.10, botan-config and the botan pkg-config file are namespaced. The dependent packages that need to be rebuilt by their owners are: * bind10: configure finds botan-1.10, but a local rebuild failed later due to an unrelated problem as far as I can see * softhsm: seems to support botan-1.10 in principle, but needs a patch for configure (resp. m4/acx_botan.m4) from SVN * ne7ssh: rebuild failed, seems to need a patch * monotone: needs a patch from mainline, will take care of that myself Regards, Thomas

1 0

Summary of accepted Fedora 20 Changes - week 30
by Jaroslav Reznik 25 Jul '13

25 Jul '13

Greeting! This is a summary of accepted Fedora 20 Changes by FESCo for week 30 (2013-07-24 meeting). = System Wide Changes = * Unversioned Docdirs - https://fedoraproject.org/wiki/Changes/UnversionedDocdirs discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185633.html * Allow kdump on secureboot machines - https://fedoraproject.org/wiki/Changes/Kdump_with_secureboot discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185133.html Partially accepted Changes * No Default Sendmail - https://fedoraproject.org/wiki/Changes/NoDefaultSendmail - https://lists.fedoraproject.org/pipermail/devel/2013-July/185328.html Sendmail will be removed from @core. Removal of sendmail from @standard didn't pass. Note: About @standard group might be decided in next release of Fedora. * No Default Syslog - https://fedoraproject.org/wiki/Changes/NoDefaultSyslog discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185329.html Remove rsyslog from @core, move to @standard pending revaluation in future. * Change Packaging Guidelines to discourage requires into /bin and /sbin - https://fedoraproject.org/wiki/Changes/NoBinDeps discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185632.html FESCo agreed to defer to FPC to figure out the right thing to do here, reevaluate if this needs to be handled as a Change later = Self Contained Changes = * Vagrant - https://fedoraproject.org/wiki/Changes/Vagrant discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185864.html * GNOME 3.10 - https://fedoraproject.org/wiki/Changes/Gnome3.10 discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185381.html * DNSSEC support for FreeIPA - http://fedoraproject.org/wiki/Changes/IPAv3DNSSEC discussed on http://lists.fedoraproject.org/pipermail/devel/2013-July/185626.html * Snapshot and Rollback Tool - http://fedoraproject.org/wiki/Changes/Rollback discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185804.html * Transitive Trusts with Active Directory support for FreeIPA - http://fedoraproject.org/wiki/Changes/IPAv3TransitiveTrusts discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185634.html * OS Installer Support for LVM Thin Provisioning - http://fedoraproject.org/wiki/Changes/InstallerLVMThinProvisioningSupport discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185803.html FESCo accepts LVM thinp as a Change and asks to treat usability issues as bugs to be worked out, change documentation from N/A to 'please document in install guide' and speak to maintainers of tools like coreutils. * Enlightenment - http://fedoraproject.org/wiki/Changes/Enlightenment discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/186080.html (announced on 2013-07-18 but without complaints) * Apache OpenOffice - http://fedoraproject.org/wiki/Changes/ApacheOpenOffice discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/ Apache OpenOffice Change is accepted under the condition that the conflicts with libreoffice must be worked out. openoffice and libreoffice packagers get to work them out. There is no Fesco mandate that libreoffice must change to accomodate openoffice at this time. alternatives is not the way to resolve the conflicts but environment-modules may be looked at as a similar means to achieve that. mattdm wants this to be perfectly clear: FESCo does not grant automatic exceptions to our processes on any basis. * X2Go - http://fedoraproject.org//wiki/Changes/X2Go discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185644.html * Sugar 0.100 (1.0) - http://fedoraproject.org/wiki/Changes/Sugar-0.100 discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185808.html * SSSD Smart Card Support - http://fedoraproject.org/wiki/Changes/SSSD_Smart_Card_Support discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185977.html * ACPICA Tools Update - http://fedoraproject.org/wiki/Changes/AcpicaTools discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185802.html * Developer Assistant GUI - http://fedoraproject.org/wiki/Changes/DeveloperAssistantGUI discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185374.html * Role based access control with libvirt - http://fedoraproject.org/wiki/Changes/Virt_ACLs discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185419.html * SSSD CIFS plugin - http://fedoraproject.org/wiki/Changes/SSSD_CIFS_plugin discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185376.html * FreeIPA OTP UI - http://fedoraproject.org/wiki/Changes/IPAv3OTPUI discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185657.html * Ryu Network Operating System - http://fedoraproject.org/wiki/Changes/Ryu discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/184930.html * Plasma-nm - http://fedoraproject.org/wiki/Changes/Plasma-nm discussed on https://lists.fedoraproject.org/pipermail/devel/2013-July/185649.html

1 0

F20 System Wide Change: Enable SELinux Labeled NFS Support
by Jaroslav Reznik 25 Jul '13

25 Jul '13

= Proposed System Wide Change: Enable SELinux Labeled NFS Support = https://fedoraproject.org/wiki/Changes/LabeledNFS Change owner(s): Daniel Walsh <dwalsh(a)redhat.com>, Steve Dickson <steved(a)redhat.com> The Linux Kernel has grown support for passing SELinux labels between a client and server using NFS. == Detailed description == We have always needed to treat NFS mounts with a single label usually something like nfs_t. Or at best allow an administrator to override the default with a label using the mount --context option. With this change we have lots of different Labels supported on an NFS share. == Scope == Proposal owners: * Steve Dickson needs to make sure nfs-utils works properly. * Dan Walsh needs to make sure selinux-policy works properly in all use cases. Other developers: Kernel * Turn on Labeled NFS in the Fedora Kernel, Fix any policy issues that arise because of this. I believe this is mainly a testing issue, and that the functionality is complete. Release engineering: N/A (No changes for Release Engineering) Policies and guidelines: N/A (not affected)

1 0

Planned Outage: Datacenter work outage - 2013-07-30 21:00 UTC
by Kevin Fenzi 23 Jul '13

23 Jul '13

Planned Outage: Datacenter work outage - 2013-07-30 21:00 UTC There will be an outage starting at 2013-07-30 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2013-07-30 21:00 UTC' Reason for outage: We are going to be adding memory and disks to various virtual server hosts and updating all instances to the latest security updates. During the outage window particular services may go down and come back up. We will try and keep disruptions down as much as we are able. Affected Services: Ask Fedora - http://ask.fedoraproject.org/ BFO - http://boot.fedoraproject.org/ Blockerbugs - https://qa.fedoraproject.org/blockerbugs/ Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control - pkgs.fedoraproject.org Docs - http://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Calendar - https://apps.fedoraproject.org/calendar/ Fedora Hosted - https://fedorahosted.org/ (trac logins may be unavailable when/if openid is down) Fedora OpenID - https://id.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ Wiki - http://fedoraproject.org/wiki/ Unaffected Services: DNS - ns-sb01.fedoraproject.org, ns02.fedoraproject.org, ns04.fedoraproject.org, ns05.fedoraproject.org Fedora People - http://fedorapeople.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Secondary Architectures QA Services Contact Information: Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/3904 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above.

1 0

F20 System Wide Change: NetworkManager Bonding Support
by Jaroslav Reznik 23 Jul '13

23 Jul '13

= Proposed System Wide Change: NetworkManager Bonding Support = https://fedoraproject.org/wiki/Changes/NetworkManagerBonding Change owner(s): Dan Williams <dcbw at redhat dot com>, Pavel Šimerda <psimerda at redhat dot com> NetworkManager should be able to configure bond master interfaces with commonly used options and recognize their existing configuration on startup without disrupting their operation. == Detailed description == NetworkManager's existing support for bond interfaces covers a limited number of use-cases and can conflict with existing bonding configurations created by tools like libvirt. The purpose of this Fedora feature is to implement more flexible bonding infrastructure in NetworkManager to support an expanded number of use-cases and to be more cooperative with other users of bonding. Support will be added to NetworkManager to detect the existing configuration of a bond interface and its slaves and to seamless "take over" that connection without disrupting it. Even if the existing configuration is not backed by ifcfg files on-disk, NetworkManager will leave that configuration on the interface unless told to change it by the user via GUI or CLI tools. Additional bond interface configuration will be added to expand the use-cases and hardware that NetworkManager can configure (eg primary, use_carrier, xmit_hash_policy, etc). == Scope == Proposal owners: development, dcbw Other developers: This feature requires changes to nm-applet (done), nm- connection-editor (done), gnome-shell, gnome-control-center (in-progress) and KDE counterparts to expose bond interfaces and their connection information in the user interface. NetworkManager also needs updates to implement the proposed changes (mostly done). This Change Proposal has been communicated with Wrangler before the Submission deadline.

1 0

F20 System Wide Change: NetworkManager Bridging Support
by Jaroslav Reznik 23 Jul '13

23 Jul '13

= Proposed System Wide Change: NetworkManager Bridging Support = https://fedoraproject.org/wiki/Changes/NetworkManagerBridging Change owner(s): Dan Williams <dcbw at redhat dot com>, Pavel Šimerda <psimerda at redhat dot com> NetworkManager should be able to configure bridge interfaces with commonly used options and recognize their existing configuration on startup without disrupting their operation. == Detailed description == A bridge connects two or more physical or virtual network interfaces to allow network traffic to flow between the two interfaces at a low level. Bridging is commonly used to connect Virtual Machines to the outside world; a bridge interface is created, to which a physical interface (typically ethernet) is assigned as a slave, and a virtual interface (typically TAP) is created and also assigned to the bridge as a slave, and then given to the Virtual Machine. Thus traffic from one or more VMs can be combined and sent out of the machine via the physical interface. This setup is currently done either manually using ifcfg files and ifup/ifdown, or by a tool like libvirt/netcf. NetworkManager should be able to configure bridge interfaces and their slaves with the same functionality as provided by libvirt, and should recognize and not disrupt existing bridge connections when it starts up. == Scope == Proposal owners: development dcbw Other developers: This feature requires changes to nm-applet (done), nm- connection-editor (done), gnome-shell, gnome-control-center (in-progress) and KDE counterparts to expose bridge interfaces and their connection information in the user interface. NetworkManager also needs updates to implement the proposed changes (mostly done). This Change Proposal has been communicated with Wrangler before the Submission deadline.

1 0

F20 Self Contained Change: Adding NetworkManager Connections via CLI
by Jaroslav Reznik 23 Jul '13

23 Jul '13

= Proposed Self Contained Change: Adding NetworkManager Connections via CLI = https://fedoraproject.org/wiki/Changes/NetworkManagerCLIAddConnection Change owner(s): Jiří Klimeš<jklimes at redhat.com>, Pavel Šimerda <psimerda at redhat.com> Support for adding new NetworkManager connections using the nmcli commandline tool. == Detailed description == Administrators will be able to configure new connections via a simple command- line interface. It will be possible to create and activate new connections, as well as delete them. == Scope == Proposal owners: development Jirka Klimes and Pavel Šimerda Other developers: N/A Release engineering: N/A Policies and guidelines: N/A This Change Proposal has been communicated with Wrangler before the Submission deadline.

1 0

Summary of accepted Fedora 20 Changes - week 29
by Jaroslav Reznik 18 Jul '13

18 Jul '13

Greeting! This is a summary of accepted Fedora 20 Changes by FESCo for week 29 (2013-07-17 meeting). = System Wide Changes = * Fedora 20 Boost 1.54 Uplift - https://fedoraproject.org/wiki/Changes/F20Boost154 announced on 2013-07-08 https://lists.fedoraproject.org/pipermail/devel/2013-July/184929.html * ARM as primary Architecture - https://fedoraproject.org/wiki/Changes/ARM_as_Primary announced on 2013-07-09 https://lists.fedoraproject.org/pipermail/devel/2013-July/184962.html FESCo resolution: Build ARM on primary infrastructure. Whether it is released as a primary Fedora 20 or as 'Fedora 20 for ARM' depends on how well it fulfills release criteria and functionality criteria closer to release time. = Self Contained Changes = * Hadoop - https://fedoraproject.org/wiki/Changes/Hadoop announced on 2013-07-10 https://lists.fedoraproject.org/pipermail/devel/2013-July/185026.html * Shared Certificate Tools - https://fedoraproject.org/wiki/Changes/SharedCertificateTools announced on 2013-07-10 https://lists.fedoraproject.org/pipermail/devel/2013-July/185027.html * SDDM as the default KDE DM - https://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM announced on 2013-07-10 https://lists.fedoraproject.org/pipermail/devel/2013-July/185118.html * KDE Plasma Workspaces 4.11 - https://fedoraproject.org/wiki/Changes/KDE411 announced on 2013-07-11 (one day less but no complaints raised on devel list) https://lists.fedoraproject.org/pipermail/devel/2013-July/185132.html * Yesod Web Framework - https://fedoraproject.org/wiki/Changes/YesodWebFramework announced on 2013-07-11 (one day less but no complaints raised on devel list) https://lists.fedoraproject.org/pipermail/devel/2013-July/185141.html * ARM on x86 with libvirt/virt-manager - https://fedoraproject.org/wiki/Changes/Virt_ARM_on_x86 announced on 2013-07-11 (one day less but no complaints raised on devel list) https://lists.fedoraproject.org/pipermail/devel/2013-July/185151.html * VM Snapshot UI with virt-manager - https://fedoraproject.org/wiki/Changes/Virt_Manager_Snapshots announced on 2013-07-11 (one day less but no complaints raised on devel list) https://lists.fedoraproject.org/pipermail/devel/2013-July/185152.html

1 0

F20 Self Contained Change: Enlightenment
by Jaroslav Reznik 18 Jul '13

18 Jul '13

= Proposed Self Contained Change: Enlightenment = https://fedoraproject.org/wiki/Changes/Enlightenment Change owner(s): Rahul Sundaram <sundaram AT fedoraproject org>, Christopher Meng <i AT cicku me>, Dan Mashal <dan.mashal AT fedoraproject org> Enlightenment 0.17 a new stable release has been released after 12 years or so of development. As many desktops are being landed on Fedora, Integrating Enlightenment in Fedora can not only enlarge the number of available desktops in Fedora, but also improve user experiences and give users another choice of Desktop Environment. == Detailed description == Enlightenment 0.17 (a.k.a E17) is the next generation of graphical desktop shell from the Enlightenment project. When you first run it and get past the initial setup wizard, you should end up with a desktop not unlike the above. It is a very traditional UNIX/X11 style desktop, because that is what E primarily is and attempts to be, BUT with a bunch of bells, whistles and modernities that were never there, as well as a different core design philosophy. There seems to be some obsession with Window Manager vs. Desktop Environment debates. It doesn't much matter what you call it. It manages windows. It does compositing. It manages files. It launches applications. It handles UI and system settings. Before we go any further, it is time to clean up some common misconceptions. * First, Enlightenment is not new. It is OLD. * It predates larger desktop environments like GNOME or XFCE. It is just barely younger than KDE. * It never started life as an attempt to "be a full desktop environment". * It started life as simply a window manager. This was back towards the latter part of 1996, and its first 0.1 release came in the first part of 1997. It was a window manager with some extras to scratch the itch that "everything was gray bevels and UIs had to be plain to be functional or useful, and that computers/X11 were not capable of more". * It handily proved that to be wrong. It could manage function AND form more flexibly than anything else, and to this date is still in an enviable position of flexibility in both behavior features and in terms of visuals. In fact, its Achilles heel simply may be that it has too many options and too much flexibility. Some of the extras filled in the gaps, like setting wallpaper, that was always done by 3rd party tools and not the window manager at the time. If you are after a constrained and simple UI, then Enlightenment (E) is not for you. It can be configured to be plain and simple if you try, or to be buzzing with activity and complexity, but this is up to you. Its default is somewhere in between these to give you a taste of what it can do on both ends of the spectrum. The default look is not what you are stuck with. Enlightenment was the first Window Manager (WM) to introduce themes in X11 (pre-packaged sets of data that you just grab and select, providing you with a vast new look and feel). Today in Enlightenment, these themes come as "Edje" files (.edj), and are pre- packaged data files containing all images, layout, animation etc. that you may need. They never get "unpacked". They are used "live as-is", and only the data needed from the file is sourced and decoded, so even if the theme is massive, only the pieces needed at any one time are decoded into memory, which is normally a fraction of the actual file size. They are also live data and need to be there while E17 runs as it is forever digging bits of data out of these files as it needs it. It is an accepted fact that the default look will not be for everyone. It tries to strike a balance of being unique (not mimicking some other desktop look), yet still being stylish. It is meant to echo some of the past from where Enlightenment comes from, and yet roll in modern effects and feels. It sacrifices some "usability" for look, yet tries to keep a balance and still be functional. It will not be for everyone, but it is hoped that it keeps you mostly happy until you find other themes that exactly meet your visual needs. You will find this as an on-going philosophy in Enlightenment. One size does NOT fit all. That's what options are for. Thats why we have themes. Do not have the misconception that what you see is what you are stuck with. You are expected to experiment and discover what is good for you. Maybe the default is fine. Maybe it is not. That's why we pioneered themes and spent immense amounts of time making them nicely packaged, efficient and powerful enough to fine-tune almost any aspect of the UI. == Scope == Just package every dependency and promise that they can be reviewed 'PASS'. * Proposal owners: Package all dependencies and push them to review queue. * Other developers: Keep existed dependency packages updated, make sure the default backgrounds and theme is available. * Release engineering: Nothing here currently. If there are sufficient interests and participation, a Fedora Enlightenment spin could be released. * Policies and guidelines: N/A (not a System Wide Change)

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce July 2013