I'm going to be building Xaw3d 1.6.1 in rawhide shortly. This includes
a soname bump. The following packages are affected:
I will be rebuilding them as well. If all goes well, we may push to
F17 in a couple days.
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
Any reasons on why libgbm isn't being built and packaged in the
current mesa SPEC file? libgbm is a dependency for wayland-demos.
The --enable-gbm configure option depends on --enable-shared-glapi. Is
there any constraint?
I've been working on packaging collectd 5.x for work purposes and I
notice there's been no movement on
https://bugzilla.redhat.com/show_bug.cgi?id=743894 since its request.
There were 2 things preventing me from building directly using the
existing spec file - one was autoconf related (since debugged and
patch submitted upstream -
https://github.com/collectd/collectd/pull/35 and the second was that
this patch then didn't work on rawhide - due to broken iptables-devel
since usr move.
I notice that harald already has patches for this, (AFTER doing pretty
much the same thing. Grr)
1) is there a master bugzilla ticket to link all usrmove bugs to?
2) [mutterings about maintainer non-responsiveness for collectd
removed as I've just seen him update BZ #797773 ]
3) Given that this is a major version bump (even if there's a
backwards compat step possible) - how likely can I get it into EPEL6
which is my target for work (I can use our internal repo if necessary)
4) given the broken dependency in rawhide, how do I submit an update?
I have question about Fedora Review Process. 
First time submitter should block FE-NEEDSPONSOR. But since they are new
to the process they very often forgot to do that.
So I always try to check whether given bugzilla email already has FAS
account and if it is in packager group.
But I find incredibly hard to find relation between bugzilla email and
How do you do this check?
I recently asked few developers and they confirm that it is hard and
Therefore I suggest to enhance template of  to include line:
FAS account: <your FAS login>
Red Hat Satellite Engineering
> Message: 16
> Date: Mon, 27 Feb 2012 11:31:24 +0100
> From: Matej Cepl <mcepl(a)redhat.com>
> To: devel(a)lists.fedoraproject.org
> Cc: epel-devel-list(a)redhat.com
> Subject: Intent to orphan gpodder in EL-6 branch
> Message-ID: <jiflre$lpj$1(a)dough.gmane.org>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Looking at https://bugzilla.redhat.com/794971 (and its now depending
> bugs) I have decided that I don't want to maintain gpodder (and
> increasing number of packages, it seems) in EPEL-6 anymore since I don't
> use it at all.
> Does anybody want to take it or should I just orphaned and let it die in
> this branch?
gpodder sounds like an interesting package.
If someone's willing to 'play' sponsor for me (whom i may ask some question
in case i get stuck),
I'd be willing to try maintain it.
Havent worked with anything related to EPEL, nor with anykind of feeds, nor
with phyton nor gtk.
But i was able to create a lua menu für the awesome DE, without having any
knowledge about lue either.
Simon A. Erat (sea)
Looking at https://bugzilla.redhat.com/794971 (and its now depending
bugs) I have decided that I don't want to maintain gpodder (and
increasing number of packages, it seems) in EPEL-6 anymore since I don't
use it at all.
Does anybody want to take it or should I just orphaned and let it die in
This old stuff allow to create header for EL-4 repository.
As RHEL-4 will go EOL at the end of the month, I plan to orphan this
package (in rawhide, will keep it in fedora 17)
Any objection ?
(As far as it's still work, and have no open bug, it's not a big problem
to keep it in the repo if needed by someone)
# Fedora Quality Assurance Meeting
# Date: 2012-02-27
# Time: 16:00 UTC
# Location: #fedora-meeting on irc.freenode.net
It's Monday, and you know what that means. It's meeting time, and since
we miraculously managed to approve Alpha on-time, we don't have to do
any last-minute bug reviewing (yay). We'll mostly be wrapping up Alpha
and looking ahead to Beta this time, it should be a quick meeting.
This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
The current proposed agenda is include below.
== Proposed Agenda Topics ==
1. Fedora 17 Alpha wrap-up and Beta prep
2. Upcoming QA events
3. AutoQA update
4. Open floor
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
test-announce mailing list