Re: [ACTION REQUIRED] Retiring packages in F-16 (final warning)
by Marc Grimme
----- "Toshio Kuratomi" <a.badger(a)gmail.com> wrote:
> On Tue, Jul 26, 2011 at 01:56:36PM +0200, Marc Grimme wrote:
> > ----- "Bill Nottingham" <notting(a)redhat.com> wrote:
> >
> > > Orphan comoonics-base-py
> > > comaintained by: elcody02
> > I'm co maintaining this package and it is required for the packages
> comoonics-cdsl-py and comoonics-cluster-py.
> > Sorry but it didn't came to my attention that this package is
> orphaned.
> > Can I do something to move it to a proper state? (pickup, ..)
> >
> Visit:
> https://admin.fedoraproject.org/pkgdb/acls/name/comoonics-base-py
> Login.
> Click the buttons to take over ownership of the package on Fedora
> releases
> that you care about.
I've done this but could not take over the ownership for Fedora-devel. It's still orphaned there.
I also got reminders from rawhide that the dependent packages could not be built because of the dependency comoonics-base-py being not available.
Can I do something about it?
Thanks for your help
Marc.
______________________________________________________________________________
Marc Grimme
E-Mail: grimme(a)atix.de
12 years, 9 months
Fedora 15 for IBM System z 64bit official release
by Dan Horák
It's been a longer time since the Fedora 15 release for the primary
architectures than we expected, but here we are.
As today, the Fedora IBM System z (s390x) Secondary Arch team proudly
presents the Fedora 15 for IBM System z 64bit official release!
And without further ado, here the links to the actual release:
http://secondary.fedoraproject.org/pub/fedora-secondary/releases/15/Fedor...
http://secondary.fedoraproject.org/pub/fedora-secondary/releases/15/Every...
and obviously on all mirrors that mirror the secondary arch content.
The first directory contains the normal installation trees as well as
one DVD ISO with the complete release.
Everything as usual contains, well, everything. :)
For Fedora 14 we have collected a couple of example config files,
kickstart examples and a nice README here:
http://secondary.fedoraproject.org/pub/alt/spins/S390/
beware that currently the content there is outdated, but most of the
information should be still valid. We're working on fixing that over the
next weeks.
Additional information about know issues, the current progress and state
for future release, where and how the team can be reached and just
anything else IBM System z on Fedora related can be found here:
http://fedoraproject.org/wiki/Architectures/s390x/15
for architecture specific release notes
and
http://fedoraproject.org/wiki/Architectures/s390x
Thanks go out to everyone involved in making this happen!
Your Fedora/s390x Maintainers
--
Dan Horák, RHCE
Senior Software Engineer, BaseOS
Red Hat Czech s.r.o., Purkyňova 99, 612 45 Brno
12 years, 9 months
Re: [ACTION REQUIRED] Retiring packages in F-16 (final warning)
by Fabian Deutsch
> ----- Ursprüngliche Nachricht -----
> Von: Peter Robinson
> Gesendet: 27.07.11 10:09 Uhr
> An: Development discussions related to Fedora
> Betreff: Re: [ACTION REQUIRED] Retiring packages in F-16 (final warning)
>
> On Tue, Jul 26, 2011 at 8:13 PM, Fabian Deutsch <fabian.deutsch(a)gmx.de>wrote:
>
> > Am Dienstag, den 26.07.2011, 11:28 -0400 schrieb Bill Nottingham:
> > > Fabian Deutsch (fabian.deutsch(a)gmx.de) said:
> > > > It seems as if my first mail (from 12 days ago) got lost:
> > > > I can take
> > > >
> > > > > Orphan link-grammar
> > >
> > > It's not a matter of can you; you need to go to pkgdb to claim it. (Sorry
> > > if the original mail didn't make this clear.)
> >
> > I actually requested all rights, but there is still the notice: awaiting
> > review.
> >
> >
> Yes, because it happened after the deadline and has hence been blocked in
> yesterday's rawhide.
I actually requested all rights nearly two weeks ago, the problem was apparently, that I missed the "claim" button. or that it wasn't there yet.
thanks
- fabian
12 years, 9 months
Naming
by Nathan O.
I am probably going to try and package Peerguardian, and the question is
what should I name it, because the tarball is named pgl_noGUI. should I
name it pgl, pgl_nogui, pgl-console or possibly just peerguardian?
12 years, 9 months
Agenda for July 25 FESCo meeting
by Bill Nottingham
Following is the list of topics that will be discussed in the FESCo
meeting on 2011-07-25 at 17:00UTC (1:00pm EDT) in #fedora-meeting on
irc.freenode.net.
Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9
= Followups =
#topic #563 suggested policy: all daemons must set RELRO and PIE flags
.fesco 563
#topic #615 Strategy for services that do not have systemd native unit files
.fesco 615
= New business =
#topic #650 May DBUS autostart?
.fesco 650
#topic #651 Updated installation/live image needed
.fesco 651
= Fedora Engineering Services tickets =
https://fedorahosted.org/fedora-engineering-services/report/6
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
12 years, 9 months
Systemd transition prevents updating older release branches??
by Tom Lane
In
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
I read that conversion of a package using a SysV initscript to systemd
units requires a trigger with a "< NEVR" condition, and that
# Note: the NEVR in trigger scripts should all be the version in
# which the package switched to systemd unit files and the comparision
# should be less than. Using <= the last version with the sysV script won't
# work for several reasons:
# 1) disttag is different between Fedora releases
# 2) An update in an old Fedora release may create a newer NEVR
# Note that this means an update in an older Fedora release must be NEVR
# lower than this. Freezing the version and release of the old package and
# using a number after the disttag is one way to do this. Example:
# httpd-1.0-1%{?dist} => httpd-1.0-1%{?dist}.1
IOW, once I push a mysql update with native systemd support into
rawhide, I'll be forbidden from ever rebasing mysql in F15 up to
a newer upstream patch release. Considering that upstream issues
bug-fix releases about once a month, this is hardly acceptable.
I'll have the same problem with postgresql, too.
What's seeming like a better option is to bump the package's Epoch
for the systemd-native release.
Discuss.
regards, tom lane
12 years, 9 months
TBB (Threading Building Blocks) rebase
by Petr Machata
Hi there,
I rebased TBB to 3.0. This should even be ABI-stable release--upstream
didn't bump the SONAME, and I verified that no ABI-looking symbols
disappeared.
Thanks,
PM
12 years, 9 months