devel-announce August 2010

devel-announce@lists.fedoraproject.org

12 participants
21 discussions

Outage: PHX2 network outage - 2010-08-15 01:00 UTC
by Mike McGrath 12 Aug '10

12 Aug '10

There will be an outage starting at 2010-08-15 01: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 '2010-08-15 01:00 UTC' Reason for outage: Network work is being done in our primary hosting facility. Some services may be offline during this time. It is possible nothing will go offline. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ CVS / Source Control Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora People - http://fedorapeople.org/ Fedora Talk - http://talk.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ Smolt - http://smolts.org/ Translation Services - http://translate.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/ Unaffected Services: BFO - http://boot.fedoraproject.org/ DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - http://docs.fedoraproject.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/ Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2335 Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage.

1 0

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

12 Aug '10

A new version of bodhi has just hit production. This release contains a number of bugfixes and improvements, along with some important process changes. https://admin.fedoraproject.org/updates ChangeLog ========= - Package update acceptance criteria compliance https://fedoraproject.org/wiki/Package_update_acceptance_criteria - Disable direct-to-stable pushes (https://fedorahosted.org/bodhi/ticket/434) - Minimum time-in-testing requirements - Every day bodhi will look for updates that have been in testing for N days (fedora: N=7, epel: N=14), and will add a comment notifying the maintainer that the update is now able to be pushed to stable. - When someone tries to push an update to stable, bodhi will look to see if it has the appropriate karma, or if it has been in testing for more than N days. - Critical path update changes - Hide obsolete updates in our critpath view (https://fedorahosted.org/bodhi/ticket/447) - Disabled strict critical path procedures for EPEL - EPEL is back to the same process that it has always had - Add a new nagmail message for unapproved critical path updates - RSS feed & grid of unapproved critical path updates https://admin.fedoraproject.org/updates/rss/rss2.0?critpath=True&release=F13 https://admin.fedoraproject.org/updates/critpath?unapproved=True&release=F13 - RSS feed & grid of user-specific comments (https://fedorahosted.org/bodhi/ticket/445) https://admin.fedoraproject.org/updates/comments?user=lmacken https://admin.fedoraproject.org/updates/rss/rss2.0?comments=True&user=lmack… - Package-specific RSS feeds of updates (https://fedorahosted.org/bodhi/ticket/339) https://admin.fedoraproject.org/updates/rss/rss2.0?package=kernel - Add more links to the package-specific page https://admin.fedoraproject.org/updates/TurboGears2 - Show 7 days worth of entries in our RSS feeds, as opposed to 20 entries (https://fedorahosted.org/bodhi/ticket/339) - Bodhi command-line client fixes - Output now goes to stdout, instead of stderr (https://fedorahosted.org/bodhi/ticket/449) (Thanks to Till Maas) - Duplicate logging issue resolved (https://bugzilla.redhat.com/show_bug.cgi?id=613533) - Support using --critpath and --type with --testable - Link to the submitter and release on the home page & testing list (Thanks to Till Maas) - Made the suggest_reboot flag actually configurable (https://fedorahosted.org/bodhi/ticket/352) - Notify the security team when an update is edited and turned into a security update (https://fedorahosted.org/bodhi/ticket/403) - Only verify the autokarma thresholds if it is enabled (Thanks to Till Maas) - Only touch bugs under the Fedora/EPEL Bugzilla products (https://fedorahosted.org/bodhi/ticket/448) - Prevent the masher from pushing obsolete updates - Prevent obsolete updates from getting auto-promoted to stable - Obsolete updates upon deletion, as opposed to destroying them. - Added more unit tests (up to 122) - Link up bug numbers and other URLs in the text of comments - Document the `newpackage` update type in the bodhi-client commands (https://bugzilla.redhat.com/show_bug.cgi?id=621828) - Set bugs to MODIFIED upon submission (https://fedorahosted.org/bodhi/ticket/343) - Added a `bodhi --push-request={stable,testing}` command to improve our releng updates push workflow - A new /updates/releases JSON API and python-fedora BodhiClient.get_releases() method for AutoQA - Have the build auto-completion widget query candidate builds from koji, as opposed to looking in /mnt/koji/packages (https://fedorahosted.org/bodhi/ticket/173) Bugs & RFEs =========== Please file and bug reports or enhancement requests here: https://fedorahosted.org/bodhi/newticket

1 0

Fedora 14 Alpha Go/No-Go Meeting: 2010-08-12 @ 12:00 UTC Recap
by Adam Williamson 11 Aug '10

11 Aug '10

The first Fedora 14 Alpha Go/No-Go Meeting was held 2010-08-12 at 12:00 UTC (so evening of 2010-08-11 in North America). The outcome of the meeting was a decision to slip the Alpha release by one week due to one bug agreed to be a definite blocker: https://bugzilla.redhat.com/show_bug.cgi?id=623129 "xdriver=vesa is not honored" and one bug that is potentially a blocker, pending more data: https://bugzilla.redhat.com/show_bug.cgi?id=596985 "hang at start of X11 on fresh install from DVD" All other bugs considered were agreed not to be release blockers and removed from the list. A slip announcement will be sent with more details on the slip specifically. We aim to build an RC4 tomorrow afternoon American time (2010-08-12) with the fix for 623129 (and possibly fixes for a couple of other bugs we decided were not blockers but would be nice to fix), and continue to research 596985 to decide if it is a blocker. If we decide it is, an RC5 build will be required. The automated summary of the meeting can be found here: http://meetbot.fedoraproject.org/fedora-meeting/2010-08-12/gonogo.2010-08-1… The full log of the meeting can be found here: http://meetbot.fedoraproject.org/fedora-meeting/2010-08-12/gonogo.2010-08-1… Thanks to all for attending and providing input. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

1 0

One week slip of Fedora 14 schedule
by Jared K. Smith 11 Aug '10

11 Aug '10

Today we held our readiness meeting for the Alpha release of Fedora 14. As you may know, this is a meeting with representatives from the Development, Release Engineering, and Quality Assurance teams. In these meetings, we evaluate the list of blocker bugs and give a "go" or "no go" signal on the state of the Fedora release. You can read the minutes of the meeting here[1], but in short the decision was made that the release has not passed its release criteria[2]. When this happens, the entire release schedule is slipped by a week, and we work to get things in better shape for the next meeting. We'll get the schedule[3] updated in the next day or so, but in general this means that our general availability date for Fedora 14 has now gone from October 26th to November 2nd. During composition of any further release candidates, the Fedora Release Engineering and Quality Assurance teams plan to be quite conservative in the updates they pull into the release candidates, so that we don't inadvertently create more blocker bugs. I'd also like to thank those who have really pushed hard to try to get the Alpha into shape. In particular, the Release Engineering team put in a lot of extra hours to compose our release candidates, and the QA team did a fantastic job of testing the release candidates and knocking out as many blocker bugs as possible. While I regret the fact that the schedule has slipped, I'm confident it was the right decision to ensure that Fedora 14 is a rock-solid release. [1] http://meetbot.fedoraproject.org/fedora-meeting/2010-08-12/gonogo.2010-08-1… [2] http://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria [3] http://fedoraproject.org/wiki/Releases/14/Schedule -- Jared Smith Fedora Project Leader

1 0

Want to help pick the F14 Release Slogan?
by Robyn Bergeron 11 Aug '10

11 Aug '10

We need a slogan for the F14 release. A release slogan is a short call-to-action that fits the artwork theme from Design, found at https://fedoraproject.org/wiki/F14_release_slogan#Themes. (F13's slogan was "Rock it.") If you are interested in suggesting ideas for the release slogan, please take a look at the Release Slogan SOP, and the criteria for selection, at https://fedoraproject.org/wiki/Release_slogan_SOP. The slogan must be: * short (1-3 words) * a call to action * positive It should reinforce that Fedora helps the user achieve something great. It should also reflect some of ideas and themes found in the release artwork, and, if possible, also touch upon the Four Foundations (https://fedoraproject.org/wiki/Foundations) Please put your slogan ideas here: https://fedoraproject.org/wiki/F14_release_slogan#New_slogan_ideas The deadline for submissions is Tuesday, August 17, at 21:00 UTC, which is our next Marketing meeting (https://fedoraproject.org/wiki/Marketing_meetings) We'll be discussing submissions there, and then the FPL, Mo Duffy, and the Marketing team lead (that's me!) will take that input and select the final slogan on Wednesday, August 18. Let me know if you have any questions, comments, or concerns -- and let the wiki table know if you have any ideas! Cheers, -Robyn

1 0

155 more python packages need to be rebuilt for Python 2.7
by Nils Philippsen 11 Aug '10

11 Aug '10

Hi everybody, a lot of packages were rebuilt for Python 2.7 recently, but unfortunately they've turned out to be not all that needed rebuilding. Essentially, all packages that contain .py files that aren't below /usr/lib(64)/python need to be rebuilt so that their respective pre-built .pyc/.pyo files are built with the new Python version. If the packages aren't rebuilt, python will either attempt to rebuild the .pyc/.pyo files (and fail due to SELinux policy) during runtime (if run as root[1]) or the program will take longer to startup because the python interpreter needs to parse the .py files everytime (and can't just use the respective .pyc/.pyo files since they're invalid). The reason why this hasn't been noticed/why those packages haven't been covered in the mass rebuild is because they don't require "python(abi)" (which was used to find out which packages to rebuild) even though the contained .pyc/.pyo files clearly do. This is because the pythondeps.sh used by rpmbuild only adds that dependency to packages which have modules in the standard paths[2]. Thanks to Kalev Lember who wrote a script identifying the affected packages. Using its output, Dave Malcolm has just mass-filed bugs against the packages which we could identify and he's looking to get these rebuilt en-masse as well. Owners or comaintainers still would need to file update requests so the packages actually end up where the users can get them ;-). For this purpose, I've attached two lists to this mail: one listing the affected packages and their owners and comaintainers, the other listing the affected packages each person owns or comaintains. Please file updates when your packages have been rebuilt and nag us if they don't get rebuilt in time, whatever that means. Thanks for your help, Nils [1]: https://bugzilla.redhat.com/show_bug.cgi?id=621726 - 'SELinux is preventing /usr/bin/python "write" access on /usr/share/system-config-firewall.' [2]: https://bugzilla.redhat.com/show_bug.cgi?id=623233 - 'python(abi) autodetection needed for all .py[co] files, not just those beneath /usr/lib*/python*' -- Nils Philippsen "Those who would give up Essential Liberty to purchase Red Hat a little Temporary Safety, deserve neither Liberty nils(a)redhat.com nor Safety." -- Benjamin Franklin, 1759 PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011

1 0

Reminder: Bugzilla UPGRADE to 3.6 on August 13th 9:00 p.m.EDT [01:00 UTC]
by John Poelstra 11 Aug '10

11 Aug '10

Sending on behalf of Dave Lawrence. This will affect Fedora too. REMINDER: Red Hat Bugzilla (bugzilla.redhat.com) will be unavailable on August 13th starting at 9:00 p.m. EDT [01:00 UTC] to perform an upgrade from Bugzilla 3.4 to Bugzilla 3.6. We are hoping to be complete in no more than 5 hours barring any problems. Any services relying on bugzilla.redhat.com may not work properly during this time. Please be aware in case you need use of those services during the outage. Also *PLEASE* make sure any scripts or other external applications that rely on bugzilla.redhat.com are tested against our test server before the upgrade if you have not done so already (see original email below). Let the Bugzilla Team know immediately of any issues found by reporting the bug in bugzilla.redhat.com against the Bugzilla product, version 3.6. ------------------------------------------- Greetings, The Red Hat Bugzilla team is happy to announce another public beta release of the next version of Red Hat Bugzilla based on the upstream 3.6 code base. Please test drive at: https://partner-bugzilla.redhat.com Over the years Red Hat has made substantial customizations to Bugzilla to fit into the Engineering tool chain. Over time the upstream has incorporated some of these customizations or solved them in different ways. Upgrading reduces our customization footprint (and thus maintenance) while bringing many bug fixes & enhancements. The main area of focus for our public betas is stability. Functionality that currently works in our 3.4 code base should continue to work as expected in the new 3.6 release. These include various ajax optimizations, needinfo actor support, frontpage.cgi, product browser, several various UI enhancements, and of course the XMLRPC API. Please feel free to point your various scripts and third party applications that use the XMLRPC API at the test server to make sure they continue to function properly. There are numerous other changes behind the scenes that we haven't listed. The goal is to make sure that functionality that people have come to expect in 3.4 is possible in the new system. There are also numerous new features/fixes that are part of the upstream 3.6 release. For more detailed information on what has changed since the last release, check out the release notes page at https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html . The database is a recent snapshot of the live database so should be useful for testing to make sure the information is displayed properly and changeable. Also with a full snapshot it is possible to test for any performance related issues. Email has been disabled so that unnecessary spam is not sent out. So feel free to make changes to bugs to verify proper working order. We are asking for everyone to get involved as much as possible with testing and feedback on the beta releases to help us make this the most robust and stable release possible. Please file any enhancement requests or bug reports in our current Bugzilla system at https://bugzilla.redhat.com . File them under the Bugzilla product and relevant component with the version 3.6. With everyone's help we can make this a great release. Thanks The Red Hat Bugzilla Team

1 0

Fedora 14 Alpha Go/No-Go Meeting August 12, 2010 @ 12:00 AM UTC
by John Poelstra 10 Aug '10

10 Aug '10

Join us on irc.freenode.net #fedora-meeting for this important meeting. Thursday, August 12, 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT, Wednesday, August 11, 2010* ) "Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: Go/No-Go Meeting." "Verifying that the Release criteria are met is the responsibility of the QA Team." For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime keep an eye on the Fedora 14 Alpha Blocker list and help us test! https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1 http://fedoraproject.org/wiki/Category:Fedora_14_Alpha_RC_Test_Results John

1 0

Fedora 14 Alpha Can Still Ship on Time IF these bugs get attention TODAY
by John Poelstra 05 Aug '10

05 Aug '10

It's been an exciting ride so far and we're embracing the peaks and valleys of the Fedora release process in real time. Even with all the recent changes and bugs we still have a shot at creating the Fedora 14 Release Candidate on schedule TOMORROW. Failure to successfully build the RC tomorrow could put the Fedora 14 Alpha at risk and push out the rest the schedule. In order for Release Engineering to create the Fedora 14 Alpha RC, all of the bugs below must be in a state of CLOSED or ON_QA by tomorrow--Bodhi updates have been submitted and the packages are in updates-testing. And, no new blocker bugs are identified before then. If there are other bugs that are of concern that you believe meet the release criteria, add 'f14alpha' as a blocker or ask for help on #fedora-qa. Thank you package maintainers and testers for all that you do! John 597858 :: NEW :: xdg-utils :: Rex Dieter :: "SELinux is preventing firefox from making its memory writable and executable." crashes rawhide firefox start :: https://bugzilla.redhat.com/show_bug.cgi?id=597858 --waiting to confirm availability of new selinux-policy 620623 :: ASSIGNED :: distribution :: Bill Nottingham :: Packages with unresolved dependencies :: https://bugzilla.redhat.com/show_bug.cgi?id=620623 --need rebuilt dependencies: https://bugzilla.redhat.com/show_bug.cgi?id=620944 --need rebuilt dependencies: https://bugzilla.redhat.com/show_bug.cgi?id=621286 620949 :: ASSIGNED :: gnome-panel :: Ray Strode [halfline] :: [abrt] gnome-panel-2.31.4-3.fc14: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV) :: https://bugzilla.redhat.com/show_bug.cgi?id=620949 --waiting for new build and submission to Bodhi 619889 :: ASSIGNED :: xorg-x11 :: X/OpenGL Maintenance List :: X.org pegged at 100% CPU usage after booting with systemd :: https://bugzilla.redhat.com/show_bug.cgi?id=619889 --waiting for new build and submission to Bodhi 615443 :: MODIFIED :: livecd-tools :: Bruno Wolff III :: booting live images from nightly fails (can't mount root filesystem) :: https://bugzilla.redhat.com/show_bug.cgi?id=615443 --appears to be fixed? Has packaged moved to updates-testing? 620900 :: MODIFIED :: anaconda :: Anaconda Maintenance Team :: traceback on install of F14 Alpha Test Compose #2 :: https://bugzilla.redhat.com/show_bug.cgi?id=620900 --should be fixed, need a new compose 617115 :: ON_QA :: livecd-tools :: Bruno Wolff III :: rawhide live spins showing black screen instead of syslinux boot menu :: https://bugzilla.redhat.com/show_bug.cgi?id=617115 --Needs Bodhi feedback

1 1

Software translation
by Noriko Mizumoto 02 Aug '10

02 Aug '10

Dear package maintainers This is kind reminder that it is F14 Software String Freeze today 03-Aug. Please update your POT with latest strings. All translators will be working hard to update your package translation. To ensure high quality translations in the final release, please be aware Software String Freeze Policy [1]. If you think that you need to break the string freeze, then please ask for approval from the Fedora Localization Team prior to breaking the freeze [1]. [1]:https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy Regards, noriko

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce August 2010