devel-announce August 2012

devel-announce@lists.fedoraproject.org

8 participants
17 discussions

New bodhi release in production
by Luke Macken 09 Aug '12

09 Aug '12

A new release of Bodhi has just been deployed to production. https://admin.fedoraproject.org/updates Bugs and enhancement requests can be filed here: http://bodhi.fedorahosted.org Major changes in bodhi 0.9.2 ---------------------------- - fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean) - Re-organized the links on the front page, and link to the new Update Feedback Guidelines - The submitter of an update can no longer effect the karma (Till Maas) - Fix duplicate status change email notifications. (Till Maas) - Mention age of updates in testing digest mails (Till Maas) - Support e-mail threading in notification e-mails (Till Maas) - Add X-Bodhi mail headers (Till Maas) - Gracefully handle private bugs (Cole Robinson) - Set the default request for new updates to 'testing' in the web form - Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable. - Fixed the input box alignment in the login box (Kalpa Welivitigoda) Full list of changes since 0.8.7 -------------------------------- Kalpa Welivitigoda (1): fixed input box alignment issue in login box #579 Luke Macken (25): Convert our tags_url to a byte string before passing it to urlgrabber. Add a script to detect when older builds become the 'latest' in stable Update our test suite to reproduce ticket [ticket:683] Fix a bug in our critpath policy ([ticket:683]). Set the default request for new updates to 'testing' Clean up EOL buildroot overrides in our rmrelease tool (bz#818617) Fix a busted unit test (test_push_EPEL_critpath_before_tested) Add pkg_resources __requires__ hacks to bodhi tools to mitigate version conflicts Handle the case where a release doesn't have any overrides Change our X-Bodhi-Update-Release header to use the short name Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605) Update our unit tests to assume submitters cannot alter karma Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg Merge branch 'feature/bodhi1-fedmsg' into develop Fix a typo in the metrics tool Fix a typo in the new mail headers Re-organize our links, and add one to the new update feedback guidelines Clean up stray buildroot overrides Version bump for 0.9.2 Our build script uses bz2 Merge branch 'release/0.9.2' Mathieu Bridon (6): Have bodhi-init create all the tables masher: Fix the comparison masher: Reuse variable setup: Fix the Turbogears version requirement Don't version control auto-generated files setup: Add missing dependencies Ralph Bean (19): Sending messages with fedmsg. No longer using fedmsg schema/validation. fedmsg.ini -> fedmsg-config.py More detail in the update.complete message. More concise send_message calls. Ignore dev db. Merge branch 'master' into bodhi1-fedmsg Updates for the latest fedmsg. Getting tests passing. Merge branch 'master' into bodhi1-fedmsg Ignore mashing fedora file. Fixed what I think is a regression in login template. Merge branch 'master' into bodhi1-fedmsg Update to test fedmsg config. Work with both tests and under WSGI. Version bump for fedmsg in staging. Only send the comment with a comment is added, not the whole update. Using a "bodhi" user/group for mod_wsgi. fedmsg+ssl changes to bodhi.spec. Use modern fedmsg config format. Disable message signing for bodhi tests. Till Maas (8): Add X-Bodhi mail headers Support e-mail threading in notification e-mails Mention age of updates in testing digest mails Use format string instead of string concatenation Import exceptions from sqlite3 Remove files used by mercurial model.py: Change karma from Submitter to 0 Fix notification on automatic status change

1 0

f18 mass branching
by Dennis Gilmore 08 Aug '12

08 Aug '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mass branching for f18 is complete. please be sure to do a git pull. to get the f18 branch. also please be sure to use the latest fedpkg dist-rawhide has been removed if your tools are too old you wont be able to build for rawhide. Dennis - -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlAiZPUACgkQkSxm47BaWffGLwCbBX1mWZe+8jVFQTPdWl8rWwxY K+QAnRwlqCGhl0OowWIi/wlKB0/fcKpX =7Q/I - -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlAibzsACgkQkSxm47BaWfdQ7QCfUE0Jwugg3L27dC4FtORCbg+J 1H8An2ZFN/w+17u44aHHP08a9r3XmQm8 =omqP -----END PGP SIGNATURE-----

1 0

[Guidelines Change] Change to the Packaging Guidelines
by Tom Callaway 07 Aug '12

07 Aug '12

Here is one late change to the Fedora Packaging Guidelines: --- The systemd scriptlet guidelines have been updated for Fedora 18. In Fedora 18, the systemd package now provides helper macros to simplify %post, %preun, and %postun invocations in packages with systemd unit files. Additionally, these macros enable support for systemd "profiles", a Fedora 18 Feature. https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd --- This guideline change was approved by the Fedora Packaging Committee (FPC), but was delayed until recently, pending Feature approval of the systemd "profiles" feature. Many thanks to 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

Fedora 18 Feature/Branch Freeze is today, Aug 07
by Jaroslav Reznik 07 Aug '12

07 Aug '12

A friendly reminder: * Feature freeze is today, August 7, 2012 [1]. At this point, all accepted features should be substantially complete, and testable. Additionally, if a feature is to be enabled by default, it must be so enabled at Feature Freeze. See [2]. * Branch freeze is today too [3]. * Please update your Feature status - completion, last update date (should be at least 80% now!). * The FESCo review of incomplete Features is on next meeting Aug 13! Features in a high risk to miss the release could be removed from Fedora 18 Feature List and even postponed to the next Fedora release! If you think your Feature is in risk, let me know, comment it in Feature Current Status section to make life of FESCo easier. In case of any questions, comments - please, contact me. Thanks Jaroslav Btw. I'm on vacations this week but I'm checking emails. [1] http://fedoraproject.org/wiki/Releases/18/Schedule [2] https://fedoraproject.org/wiki/Feature_Freeze_Policy [3] http://fedoraproject.org/wiki/Branch_Freeze_Policy -- Jaroslav Řezník <jreznik(a)redhat.com> Your Feature Wrangler Office: +420 532 294 275 Mobile: +420 602 797 774 Red Hat, Inc. http://www.redhat.com/

1 0

FUDCon Paris Updates: Subsidy requests opening, hotel reminders
by Robyn Bergeron 03 Aug '12

03 Aug '12

Greetings! (...or perhaps I should say.... bonjour!) I'd like to share a few reminders and announcements regarding the upcoming FUDCon in Paris, France, on October 13-15, 2012. If you are planning to attend FUDCon and need a travel subsidy to do so, the ticketing system is now open for those requests. Requests will be accepted through August 15, 2012. Please note that funding requests without a ticket will not be considered. Preference will be given to attendees from the EMEA region who are actively contributing to Fedora, and have detailed their participation plans for FUDCon in their request. To place a subsidy request, please follow these steps: 1: Pre-register at http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration - and put an X in the $$$ column 2: Read about the funding request process and place a funding request ticket in the FUDCon-planning ticket tracker here: https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Additionally, a few notes regarding the hotel in Paris: There are other events in Paris during this time period; most notably, our first day of FUDCon will be taking place at the Open World Forum conference, on the day in which the public is encouraged to participate in and learn about open source projects. OWF had nearly 2000 attendees last year. Accordingly, rooms might be in short supply as we approach FUDCon; please, book your hotel as soon as possible, not only for affordability purposes, but also so that you have a bed to sleep in. :) We currently have a rate of EUR81 per night at the ibis Paris La Vilette Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. However, this rate will expire at the end of August, and any remaining rooms in our block will expire. For instructions on booking your hotel, please read the Lodging/Hotel section of the FUDCon: Paris wiki: http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel Cheers, -Robyn

1 0

Mass rebuild cleanup
by Dennis Gilmore 03 Aug '12

03 Aug '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, With branching for f18 happening on Tuesday next week we still have quite a large number of failures and packages needing rebuilt. the list of 415 current failures can be found at http://ausil.fedorapeople.org/f18-failures.html while the total rebuild list of 545 can be found at http://ausil.fedorapeople.org/f18-needsbuilt.html please fix them before branching. anything not built will start on the process of being removed from fedora. Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlAbaKEACgkQkSxm47BaWfe/DACfUg4i7NNMjVLYkq4u25pZAnBF SzkAn3B6hMuQNV7KQa49XSTnzS0HyCb3 =yreK -----END PGP SIGNATURE-----

1 0

[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway 01 Aug '12

01 Aug '12

Here are the latest set of changes to the Fedora Packaging Guidelines: --- A new section has been added to the SysV Initscripts section, discussing the proper use of subsys locking. Even though Fedora packages should no longer be using SysV Initscripts as a primary service mechanism, Red Hat Enterprise Linux and EPEL do. Additionally, Red Hat points partners to the Fedora Guidelines when they build for RHEL. https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of… --- The review guidelines now reflect the use of sha256sum (instead of md5sum) to confirm upstream source integrity. https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_O… --- The PHP Packaging guidelines have been updated to include guidance about when it is appropriate to have an explicit Requires on httpd & mod_php, how to handle explicit Requires on PHP extensions, and how to handle a Requires for a minimum PHP version. https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version --- A new section on Macros has been added to the Packaging Guidelines, covering Packaging of Additional RPM Macros. https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional… --- A new section on the Documentation= field in systemd unit files (F17+) has been added. https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field --- A short section on the Group tag in Fedora packages has been added. All current versions of Fedora (and their respective RPM versions) treat the Group tag as optional. Packages may include a Group: field for compatibility with EPEL, but are not required to do so. https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag --- The RHEL conditionalization has been removed from the Python3 example spec file, as it is no longer valid. https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file --- These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC). Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, 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

devel-announce August 2012