announce October 2012

announce@lists.fedoraproject.org

6 participants
7 discussions

[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway 31 Oct '12

31 Oct '12

Some changes to the Fedora Packaging Guidelines have been made: --- In the specific case where multiple software components generate identically named (but incompatible) binaries, Fedora Packagers should make every effort to convince the upstreams to rename the binaries to resolve the conflict (see: Packaging:Conflicts#Binary_Name_Conflicts). However, if neither upstream is willing to rename the binaries to resolve the conflict, AND the binaries are not viable candidates for alternatives or environment modules (incompatible runtimes), as long as there are no clear cases for both packages to be installed simultaneously, explicit Conflicts are permitted at the packager's discretion. Both packages must carry Conflicts in this case. Be aware, adding explicit Conflicts means that if any other packages depend on your package, you may be creating a chain-of-conflicts that could cause user pain. Please consider this as a last resort. https://fedoraproject.org/wiki/Packaging:Conflicts#Incompatible_Binary_File… --- The PEAR section of the PHP Guidelines has been updated to reflect the existence of a new macro, %{pear_metadir}, along with an example of how it is to be used, and a new EPEL specific section relating to the fact that %{pear_metadir} does not exist in RHEL php builds. https://fedoraproject.org/wiki/Packaging:PHP#PEAR_Modules --- The MPI Guidelines have been updated to install the module files under a "mpi" sub-directory and adds "conflict mpi" to the module files to avoid being able to load multiple mpi modules at one time. https://fedoraproject.org/wiki/Packaging:MPI --- These guideline changes were approved by the Fedora Packaging Committee (FPC). Many thanks to Remi Collet, Orion Poplawski, Michal Sekletar, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines. As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here: https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure Thanks, ~tom

1 0

FAS update is live
by Ricky Elrod 19 Oct '12

19 Oct '12

Greetings all, This afternoon we deployed an update to the Fedora Accounts System (FAS), which can be seen live at https://admin.fedoraproject.org/accounts/ Some of the changes you will be able to see are as follows: * You can now store a secret question and answer. This will be used in the event of a forgotten password. The answer to the questions are GPG encrypted, and will be manually decrypted by a FAS administrator, in the event of a user needing to regain access to their own FAS account. (Implemented by Patrick Uiterwijk) To use this feature, you can log in to FAS using the link above, click "My Account" from the sidebar, then click "Change" next to the "Security question" label. * FAS groups now show all users in the group, right on the group information page, if there are less than 10 users in the group. This prevents having to click past the information page to see the user listing, if it is small enough to show right up front. (Implemented by Pierre-Yves Chibon) * Passwords are now checked against libpwquality, when they are changed. (Implemented by Christos T) * This release also marks the start of FAS integration with fedmsg - the Fedora Messaging Bus. (http://www.fedmsg.com/en/latest/) (Implemented by Ralph Bean) If you experience any issues using these features, or you notice that something isn't working right due to the upgrade, please either file a bug report on the FAS trac (https://fedorahosted.org/fas/) or contact us on irc.freenode.net in #fedora-apps. Thank you to all contributors who have made this release possible. A full changelog can be found in the NEWS file, within the FAS repo, or here: http://git.fedorahosted.org/cgit/fas.git/tree/NEWS We hope you enjoy using the new features. -Ricky, on behalf of Fedora Infrastructure

1 0

FUDCon Lawrence hotel block open
by Ruth Suehle 19 Oct '12

19 Oct '12

Good news, everyone! You can now officially reserve your room for FUDCon Lawrence. We have a block at the Springhill Suites for $119/night. All rooms include free wifi and breakfast buffet. The block will be held until December 14. Here's all the info: https://fedoraproject.org/wiki/FUDCon:Lawrence_2013#Lodging Note that Marriott has had some website problems today, so if at first you don't succeed, try, try again. In addition, if you haven't done so already, *please register for FUDCon now.* This helps us plan things like how much food we're going to need and how large of a space for FUDpub. Thanks! Registration: http://fudconlawrence-ianweller.rhcloud.com/ See you in Kansas! Ruth

1 0

Last call for F19 naming proposals (deadline today 23:59 UTC!)
by Christoph Wickert 16 Oct '12

16 Oct '12

Hi everybody, this is the final reminder that the Fedora 19 naming collection ends today at 23:59 UTC. That means you have 5 hours left to propose a name at http://fedoraproject.org/wiki/Name_suggestions_for_Fedora_19 Before proposing a name, please read the guidelines at http://fedoraproject.org/wiki/Guidelines_for_release_names Kind regards, Christoph

1 0

Smolt Retirement
by Kevin Fenzi 10 Oct '12

10 Oct '12

Greetings. The Fedora Infrastructure team will be retiring our smolts.org service on 2012-11-07. After this time, all new data sent to the smolts.org service will be discarded and users of the web interface will be directed to a page noting this retirement. Historical statistics will no longer be available from the smolts.org site, although raw data may be available for download. Around 2013-11-01 this redirect will be evaluated and dropped or maintained longer depending on the volume of traffic it still receives. Please see: https://fedoraproject.org/wiki/Smolt_retirement for more information on this retirement. A replacement for much of the functionality of smolt is under development, see the census project mailing list for more information: http://lists.fedorahosted.org/mailman/listinfo/census You can contact the Fedora Infrastructure Team on our mailing list: http://lists.fedoraproject.org/mailman/listinfo/infrastructure kevin

1 0

Don't have a cow, man: Fedora 19 naming suggestions are now open. Submit your idea!
by Robyn Bergeron 09 Oct '12

09 Oct '12

Greetings and salutations! It is time once again to choose the name for the next release of Fedora. Suggestions for names will be accepted beginning RIGHT THIS SECOND (October 9, 2012), and ending promptly at the end of the day on October 16, 2012 (23:59:59 UTC). So mooooooove on over, and help to pick out an udderly fabulous name for the next release. https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_19 The awesome fine print: You *must* follow the instructions and guidelines at the page listed above if you want your name to be considered. For instance, there must be an "is-a" link between the name "Spherical Cow" (from Fedora 18) and the name you suggest. That link must be different than previous links for Fedora release names. Names of living people and well-known trademarks will likely be rejected as well. (Apologies to those wishing to make links between spherical cows having spots, and Tom Callaway.) You can also find full schedule details for the release naming process on the above page. For those of you interested in reviewing the history of Fedora release names, there is an appropriately named wiki page for doing so: http://fedoraproject.org/wiki/History_of_Fedora_release_names I fully expect that, as always, we will have a delightful (and occasionally wacky) assortment of names to choose from - I look forward to seeing your suggestions! -Robyn

1 0

[Guidelines Change] Change to the Packaging Guidelines
by Tom Callaway 08 Oct '12

08 Oct '12

A few minor changes to the Fedora Packaging Guidelines have been made: --- The Ruby Packaging guidelines were updated to reflect the fact that rubygem packages must have a Requires: rubygems, because that package (rubygems) owns the RubyGems? directory structure. https://fedoraproject.org/wiki/Packaging:Ruby#RubyGems --- The systemd Scriptlets for Fedora 18+ have had their corresponding scriptlet Requires adjusted from "systemd-units" to "systemd", since "systemd-units" is provided by the "systemd" package in Fedora 18+. There is still a separation in previous releases of Fedora (16/17), so packagers can choose to continue using the old Requires (systemd-units) if they are targeting multiple versions of Fedora with a single spec file. https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Macroized_script… --- This guideline change was approved by the Fedora Packaging Committee (FPC). Many thanks to Vit Ondruch, Lennart Poettering, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines. As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here: https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure Thanks, ~tom

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

announce October 2012