Raleigh, we have a problem...
python-gammu, which is required by wammu, prevents users from updating
to the latest gammu release for several days now. It has already been
reported in Bugzilla, see
https://bugzilla.redhat.com/show_bug.cgi?id=426848 and - even more
This leads me to some questions:
1. Why is # 425831 still in status "New"? It has been reported on
Dec 16th and the maintainer already responded to it.
2. What's so difficult to coordinate 2 (3 with wammu) dependent
packages? All are owned by the same packager. IMO this should be
done in one single update in bodhi.
3. Do we need better training for our maintainers or more
documentation in the wiki? The broken deps already appeared in
EPEL before they were in F8, so the maintainer should have known
that he's breaking something when he did the gammu update in
4. When was the testing done? gammu-1.17.0-1.fc8 was built on Dec.
22 11:22:28 MST  and hit the updates repo on Dec. 23 22:50:08
. This is less than 36 hours for testing.
5. Why has gammu been pushed directly to updates and not to
updates-testing? According to the changelog it was not a
Note that I don't want to blame a single person here. I think this is
just an example that we really NEED to think about how to avoid such
situations in the future? I know there are people on vacation these
days, but there are enough people that offered help. Unfortunately they
are not allowed to by the ACLs.
It has been brought to my attention
(http://dot.kde.org/1197759365/1198030918/1198084280/1198100165/) that K3b is
no longer available on the DVD images (since the Core-Extras merge). As far as
I can tell, this is because it is marked only as "optional" and not "default"
in the sound-and-video group? As K3b is probably the best Free CD/DVD burning
program around, the burning tool of choice of most KDE users and even several
GNOME users, I think it would be great if this could be put back onto the DVD
images in F9. Can this be added to the pungi kickstart config?
when I tried to build a custom SELinux module, this strange behavior
when I used:
I got "read" denied source: tomcat5_t target: lib_t
class file read;
allow tomcat5_t lib_t:file read;
worked fine. Although this should essentially be the same in my
Any explanations for that?
-----BEGIN PGP SIGNED MESSAGE-----
I just saw the WishList on the fedora wiki site. I was interested in
the sshmenu app. I could not find anyone maintaining it for fedora.
I am interested in maintaining it, if any one does not have any objections.
Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas)
Help Desk APAC Team Lead,
Research and Development Lead,
Global Help Desk, Pune
Phone: +617 3514 8125 (UTC +5.5)
3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5
Visit the Help Desk portal at : http://helpdesk.corp.redhat.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----