Fedora 15 Alpha to slip by one week
by Robyn Bergeron
Today at the Go/No-Go meeting[1] we decided to slip the Alpha by one week.
The slip is due to a blocker bug affecting a number of non-US keyboard
layouts, including German and French[2], which does not currently have a
fix or a reasonable workaround. All other blocker bugs are currently in
VERIFIED, or alternately, have workarounds documented in F15_Common_bugs.
At this time, we are not adjusting later milestone dates.
We will continue with the F15 Alpha readiness meeting tomorrow, as
previously announced on the logistics mailing list, and will have
another F15 Alpha Blocker Bug meeting Friday.
Thanks for your understanding. We will meet again next week for another
GO/NO-GO meeting.
-Robyn
[1]
http://meetbot.fedoraproject.org/fedora-meeting/2011-02-23/fedora-meeting...
[2] https://bugzilla.redhat.com/show_bug.cgi?id=676827
12 years, 9 months
PolicyKit authentication agent changes
by Matthias Clasen
As of version 0.100 (which will land in F15 as a post-alpha update), the
polkit-gnome package will no longer install an autostart file for
polkit-gnome-authentication-agent-1. Instead, each desktop environment
is reponsible for making sure that an authentication agent is running.
For GNOME, this is done by gnome-session installing an autostart file
with OnlyShowIn=GNOME;. Other desktop environments that rely on
polkit-gnome need to do something similar.
12 years, 9 months
New path available for joining the Fedora package maintainers group
by Kevin Fenzi
Greetings.
FESCo has added an additional path to becoming a co-maintainer of an
existing package in the Fedora package collection for folks who are not
currently in the packager group.
Traditionally, you would gain sponsorship by submitting a new package
you create and demonstrating your understanding of the guidelines and
processes from the review process.
This new path requires you to convince an existing maintainer
to mentor you in the processes and guidelines of package maintenance,
and would allow you to be sponsored by FESCo or an existing sponsor to
co-maintain those package(s) with your mentor guiding you.
Please see:
http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group
For the full description and process for this path to becoming a package
maintainer.
kevin
12 years, 9 months
notification-daemon autostart changes
by Matthias Clasen
I'm going to build notification-daemon 0.7.1 as an F15 update; this
release changes the way the daemon is started.
In the past, it was bus activated on the session bus and exited after
some idle time. This was causing a race condition with gnome-shell
taking the same bus name at session start to support notifications.
Starting with 0.7.1, the notification daemon is no longer bus activated,
and does not exit on its own. Desktop environments that use it to
provide notifications have to ensure it gets started in some way;
gnome-session will start it as a required component of the fallback
session.
Matthias
12 years, 9 months
Mass rebuild starting monday Feb 7
by Dennis Gilmore
Hi all,
for gcc-4.6, xz compression changes, and to a lesser extent we will be doing a
mass rebuild starting monday. it will be done in a side tag with a lower than
normal priority so that you can still submit builds and not have to wait for
the mass rebuild to finish. we will then tag into rawhide the builds after
unless you do a build in the meantime
Please note that mass branching will be occuring soon after the mass rebuild
as the Alpha freeze is 2011-02-15
Thanks
Dennis and the rest of rel eng
12 years, 10 months
[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway
Here are the latest set of changes to the Fedora Packaging Guidelines:
---
The rules for substituting dots with dashes in package names have been
clarified to make explicit that they apply to python modules and that
they do not apply to version numbers in compat libraries.
https://fedoraproject.org/wiki/Packaging:NamingGuidelines
---
Many implementations of md5 originate in a program and then end up
copied to other programs with compatible license terms. These
implementations have been granted a bundling exception. The usual
requirement to set a Virtual Provides: if bundling are in effect and
have some special notes due to the many implementations out there. Note
that copying the implementation from a library is not covered under this
exception.
https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Packages_gr...
---
rpm and yum treat a dependency on a package of the form Requires: foo as
being fulfilled by any available package foo, regardless of arch. On
multilib architectures, this means that there are often two packages
with the same name: one for each of the multilib arches. When yum is
asked to satisfy a dependency for that package name it could pull in the
package for the wrong arch. This happens when the correct architecture
is not available to yum. That might be the case if, due to some
malfunction, the Fedora repositories are out of synch. It can also
happen if a user has installed a package that is treated as "newer" than
the corresponding package in the currently enabled set of repositories;
in attempting to resolve otherwise-unresolvable dependency chains, yum
may decide to pull in the dependency chain for a different arch.
In some situations, this is not a problem, but there are some situations
where it does matter:
* A library that is explicitly Required (example a dlopen'd library)
* The dependency from one -devel packages that is not noarch to
another -devel package.
* A non-noarch subpackage's dependency on its main package or another
subpackage (e.g., libfoo-devel depends on libfoo, or fooapp-plugins
depends on foo-app).
The Packaging Guidelines (and Naming Guidelines) have been amended to
reflect that %{?_isa} must be used for Explicit Requires and Provides
that match those situations.
http://fedoraproject.org/wiki/Packaging:Guidelines#Requires
http://fedoraproject.org/wiki/Packaging:Guidelines#Explicit_Requires
http://fedoraproject.org/wiki/Packaging:Guidelines#Requiring_Base_Package
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Renaming.2Frepl...
---
Previously, there was a change made to the Documentation guidelines
which stated that:
If a package includes something as %doc, it must not affect the
runtime of the application. To summarize: If it is in %doc, the
program must run properly if it is not present.
In addition, %doc files must not have executable permissions.
This has been revised to:
Files marked as documentation must not cause the package to pull in
more dependencies than it would without the documentation. One simple
way to ensure this is to remove all executable permissions from %doc
files (chmod -x).
Also, if a package includes something as %doc, it must not affect the
runtime of the packaged application(s). To summarize: If it is in
%doc, the included programs must run properly if it is not present.
https://fedoraproject.org/wiki/Packaging:Guidelines#Documentation
---
A new section has been added to the Packaging Guidelines concerning test
suites included with source code:
If the source code of the package provides a test suite, it should be
executed in the %check section, whenever it is practical to do so.
https://fedoraproject.org/wiki/Packaging:Guidelines#Test_Suites
---
A new section has been added to the Packaging Guidelines concerning the
proper packaging of tmpfiles.d configurations and directories:
https://fedoraproject.org/wiki/Packaging:Tmpfiles.d
---
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
Many thanks to Jochen Schmitt 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:
http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
Thanks,
~spot
12 years, 10 months
Fedora GNOME 3 Test Day #1 coming up tomorrow
by Adam Williamson
QA and Desktop teams are running three Test Days to test out GNOME 3
ahead of F15 (and GNOME 3.0) releases, and the first is tomorrow!
https://fedoraproject.org/wiki/Test_Day:2011-02-03_GNOME3_Alpha
Please come along and help test - there will be live images so you won't
need a Rawhide installation, the testing will be easy, and you don't
have to do every single test - you can help out even with ten or fifteen
minutes (plus the time to download and burn an image). Please note that
right now the wiki page is in considerable flux - I have to write a
whole bunch of test cases which aren't up there yet - and desktop team
are in the middle of trying to land GNOME 2.91.6 in Rawhide, so please
hold off on testing for now, we should have everything in order by
tomorrow morning. If you're busy tomorrow, you can certainly come by and
do the tests later - all you'll miss is the IRC communication, but you
can do all the testing based on the Wiki page. IRC channel is
#fedora-test-day on Freenode. Please grab me if you have any questions
or suggestions! Thanks everyone.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
12 years, 10 months
