libsigsegv-2.9 update, abi bump
by Rex Dieter
I'm planning a libsigsegv-2.9 (rawhide) update relatively soon which
includes an abi change. According to repquery, only the following
packages should be affected:
clisp
gnu-smalltalk
(I'll help take care of these requisite rebuilds)
-- Rex
13 years
[HEADS-UP] Moving /var/run and /var/lock to tmpfs in Rawhide
by Lennart Poettering
Heya!
I hereby want to let everybody know that in the next days I will turn on
/var/run and /var/lock on tmpfs on Rawhide/F15. This is in accordance
with the following accepted F15 feature:
https://fedoraproject.org/wiki/Features/var-run-tmpfs
My current tests indicate that we will not run into too much trouble
with this and most things should continue to work just fine. However, of
course I run only a small subset of packages of the fedora archive on my
machine. So here's what might happen and which might need fixing over
the next weeks in various packages:
- Not all packages might be able to create their directory in /var/run
on start-up. Since SUSE and Ubuntu have already been shipping systems
with tmpfs on /var/run and /var/lock for quite a while I expect the
number of packages that are incapable of doing this to be very
small. If your software nonetheless fails witht this issue, then
there are two options to fix this: a) patch the program in
question, so that it is able to recreate the directories in
/var/run, or b) ship a simple drop-in file for /etc/tmpfiles.d/ which
recreates these directories on boot. (see below)
- There might be permission problems, since the rpms might have set
different perms on the subdirs of /var/run than the software itself
might apply when starting up. In this case, a drop-in file in
/etc/tmpfiles.d/ might help. (see below)
- The SELinux policy might trigger AVCs and disallow creation of the
dirs in question. In this case Dan will be of help of course, so make
sure to file a bug. And I guess I don't need to mention this but
temporarily falling back to permissive mode is a short-term workaround
for this.
- In some cases daemons might want to create more than one file/dir
below /var/run which are supposed to be labelled differently. In this
case the daemon can either be modified to fix its labels up itself, or
a drop-in file in /etc/tmpfiles.d/ might help (see below).
- Many .spec files currently own subdirs of /var/run. These need to be
updated to %ghost those dirs only, so that the automatic removal of
these files/dirs on boot doesnt cause rpm to complain. The list of packages
which own such files/subdir you find on the aforementioned feature
page. I will mass-file bugs against these packages later tonight,
requesting the %ghosting of these entries. For more information on the
%ghost directive in .spec files see this page:
http://www.rpm.org/max-rpm-snapshot/s1-rpm-inside-files-list-directives.h...
Action items:
a) Lennart will mass-file bugs regarding %ghost usage tonight
b) Lennart will switch on /var/run and /var/lock on tmpfs either
tomorrow or the day after tomorrow
c) YOU need to edit your .spec file and place a %ghost where
appropriate.
c) YOU need to test if you package still works, and if necessary file
AVC bugs, add an /etc/tmpfiles.d drop-in file to your program, or patch
it so that it is able to recreate these directories beneath /var/run on
its own.
On /etc/tmpfiles.d:
This is a new feature of systemd, but which is apparently very much
liked by people outside of systemd, so this might actually find adoption
even on systems which will not adopt systemd any time soon, since it
actually is not specific at all to systemd. By dropping a simple
configuration file in /etc/tmpfiles.d you can ensure that volatile files
and directories are: a) created, deleted or emptied at boot b) their
permissions/ownership fixed c) its directory contents cleaned up in
regular intervals (a la tmpwatch) and d) it is properly relabeled at
boot.
As an example, here's how such a file might look like for the screen package
(name it /etc/tmpfiles.d/screen.conf):
<snip>
d /var/run/screens 1777 root root 10d
d /var/run/uscreens 0755 root root 10d12h
</snip>
This encodes that two directories are created under the listed names, with
automatic clean up after 10 days resp. 10 days and 12h.
For more details consult the man page:
http://0pointer.de/public/systemd-man/tmpfiles.d.html
Thank you for your attention!
Lennart
--
Lennart Poettering - Red Hat, Inc.
13 years
Fedora Board, FESCo & FAmSCo Elections - Voting Information
by Robyn Bergeron
Greetings,
The elections for the Fedora Board, Fedora Engineering Steering
Committee (FESCo), and the Fedora Ambassadors Steering Committee
(FAmSCo) began at 0000 UTC on 20th November 2010, and are scheduled to
run until 23:59 UTC on 28th November 2010. (Please refer to a UTC
time zone converter, such as
http://www.timeanddate.com/worldclock/converter.html if you are unsure
of your time zone's relation to UTC.)
All groups have chosen to use the Range Voting method
(http://en.wikipedia.org/wiki/Range_voting).
Ballots may be cast on the Fedora Elections System at
https://admin.fedoraproject.org/voting. If this is the first time
you've used the voting system, please refer to the Fedora Elections
Guide, currently located at
http://pfrields.fedorapeople.org/documents/elections-guide.
To read more about the candidates, please refer to each group's
nomination pages:
* FAmSCo: http://fedoraproject.org/wiki/FAmSCo_election_2010_nominations
* Fedora Project Board:
http://fedoraproject.org/wiki/Board/Elections/Nominations
* FESCo: http://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
For more general information about the election, as well as finding
links for reading candidate answers to questionnaires and IRC town
hall transcripts, please refer to
http://fedoraproject.org/wiki/Elections.
Please remember to cast your vote!
Thanks,
Robyn
13 years
FESCo Election IRC Town Hall (2010-11-18 1500UTC)
by Kyle McMartin
Hi folks,
Just announcing that there'll be an IRC town hall with the FESCo
election candidates on Thursday, October 18th, at 1500UTC (1000
US/Eastern.)
You can join #fedora-townhall-public to ask questions of the moderators,
which will be posed and answered by the candidates in #fedora-townhall.
More information is available here:
https://fedoraproject.org/wiki/Elections#How_to_Join
A summary and the irc log will be posted and linked from the wiki after
the discussion, if you're unable to watch it live.
Thanks in advance for your interest,
Kyle
PS: I'd like a volunteer to help me moderate the questions, or at least,
help pick out the really good ones for our limited time (1 hr.) If you'd
like to help out, please let me know.
13 years
[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway
Here are the list of this week's changes to the Fedora Packaging Guidelines:
The FPC has taken over evaluating exceptions to the Bundled Library
Guidelines. A list of standard questions to be answered to give the FPC
information on whether to grant exceptions has been added to the
Guidelines:
https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Standard_qu...
---
An exception was added to the Guidelines concerning use of
%{_sourcedir}, specifically, when there is an available list of
supplementary source files, it is permissible to use this list in
conjunction with %{sourcedir} to simplify operations on those
supplementary source files.
https://fedoraproject.org/wiki/Packaging:RPM_Source_Dir
---
rpm %post and %postun scripts have been added for the following
important pieces of GNOME3 technology: GSettings, gdk-pixbuf loaders,
GTK3 modules, and GIO modules:
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GSettings_Schema
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#gdk-
pixbuf_loaders
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GTK.2B_modules
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GIO_modules
---
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
Many thanks to Kevin Kofler, Matthias Clasen, FESCo 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
13 years
[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway
Here are the list of recent changes to the Fedora Packaging Guidelines:
D Packaging Guidelines have been added:
https://fedoraproject.org/wiki/Packaging:D
---
The Java Packaging Guidelines have been revised:
https://fedoraproject.org/wiki/Packaging:Java
Diff:
https://fedoraproject.org/w/index.php?title=Packaging%3AJava&diff=206526&...
---
The Guideline that explains how and when to require base packages has
been substantially revised. The old language focused on -devel packages
and left other subpackages to the imagination of the reader. The update
has more generic advice and uses -devel and -libs packages as examples.
http://fedoraproject.org/wiki/Packaging/Guidelines#RequiringBasePackage
---
The perl guidelines have been updated with additional examples and
clarifications. Specifically, the Directory ownership, requires and
provides, and testing sections have seen wording changes:
https://fedoraproject.org/wiki/Packaging:Perl
---
A guideline was added explaining the %pretrans scriptlet and requiring
that if used it must be written in Lua.
https://fedoraproject.org/wiki/Packaging/Guidelines#The_.25pretrans_scrip...
---
A note was added about additional checks obtained by running rpmlint on
installed packages.
https://fedoraproject.org/wiki/Packaging/Guidelines#Use_rpmlint
---
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
Many thanks to Alexander Kurtakov, Jonathan Mercier, Stanislav
Ochotnicky 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
13 years
Welcoming New Fedora Program Manager Robyn Bergeron
by John Poelstra
Jared Smith made an announcement in his blog [1] about some upcoming
personnel changes in Fedora. I wanted to make a specific announcement
to the Fedora lists as well.
Through the end of 2010 and a little bit beyond, I will be working along
side Robyn Bergeron to transition my official Fedora responsibilities to
her. This will include getting the Fedora 15 team schedules into shape,
feature wrangling, bugzilla maintenance, and any number of other things.
Robyn and I are committed to making this transition as smooth,
complete and timely as we can, and expect the transition to be completed
before the Fedora 15 feature submission deadline. Said a different way,
if you've already been working with me on something, I'll continue to
help you with it. For all new topics, please contact Robyn directly and
we will work together as necessary to get them done.
One of the luxuries of my position was keeping tabs on most of the teams
in Fedora via their mailing lists. I won't have as much time for this
going forward so I'll be scaling back the number of mailing lists I
watch and contribute to. If I posted to a list in the past, please
don't assume I'll automatically see your message there in the future.
Also please don't hesitate to contact me directly if you feel the need
to do so.
Fedora, it's been a great ride. We've made great progress in the past
three years and I'm thankful you let me be a part of it. Here's to
wishing only the best to Robyn in her new role serving the Fedora community!
John
p.s. I'm still looking forward to and rooting for an on time Fedora 15
release. :)
[1] http://www.jaredsmith.net/2010/11/10/changing-of-the-seasons/
13 years
Reminder: Fedora 12 end of life on 2010-12-02
by Kevin Fenzi
Greetings.
This is a reminder email about the end of life process for Fedora 12.
Fedora 12 will reach end of life on 2010-12-02, and no further updates
will be pushed out after that time. Additionally, with the recent
release of Fedora 14, no new packages will be added to the Fedora 12
collection.
Please see http://fedoraproject.org/wiki/DistributionUpgrades for more
information on upgrading from Fedora 12 to a newer release.
kevin
13 years, 1 month
