Re: An error while using livecd-creator
On Tue, Aug 11, 2009 at 8:24 PM, Paul W. Frieldssticks...@gmail.com wrote: My bet is that either your package set is too big for the created file system image, or you ran out of space on whatever partition holds /var/tmp on your system. Both seems to be ok in this case, having around 27GB of free space and image size should be around 1100MB :) Kushal -- http://fedoraproject.org http://kushaldas.in -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
KDE-SIG weekly report (33/2009)
This is a report of the weekly KDE-SIG-Meeting with a summary of the topics that were discussed. If you want to add a comment please reply to this email or add it to the related meeting page. -- = Weekly KDE Summary = Week: 33/2009 Time: 2009-08-011 14:00 UTC Meeting page: https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2009-08-11 Meeting minutes: http://meetbot.fedoraproject.org/fedora-meeting/2009-08-11/fedora- meeting.2009-08-11-14.07.html Full log: http://meetbot.fedoraproject.org/fedora-meeting/2009-08-11/fedora- meeting.2009-08-11-14.07.log.html -- = Participants = * Jaroslav Reznik * Kevin Kofler * Rex Dieter * Sebastian Vahl * Steven Parrish * Lukas Tinkl * Thomas Janssen -- = Agenda = topics to discuss: * KDE 4.3.0 blockers (for F11/F10) * Extragear for KDE 4.3.0 (status) * KDE live images - status = Summary = o KDE 4.3.0 blockers (for F11/F10) * fish:/// problem [1] ** regression, suspicious commits #946444, #933202 ** ltinkl to try reverting suspect upstream commit(s), and test things out * ctrl+f12 problem [2] ** probably plasma to plasma-desktop rename problem ** reported upstream o Extragear for KDE 4.3.0 (status) * assigned to svahl while than is away * there are no group acls... o KDE live images - status * i686 and x86_64 images ready by svahl [3] * prelink issues ** kio slaves are segfaulting ** prelink bug should be reopened as we thought it's fixed already * image contains newer PyKDE4 and kde-settings from koji to get printer configuration and wallpaper back * firstboot is not working [4] * x86_64 image is much more bigger than i686 -- = Next Meeting = http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2009-08-18 -- = Links = [1] https://bugzilla.redhat.com/show_bug.cgi?id=516416 [2] https://bugzilla.redhat.com/show_bug.cgi?id=516445 [3] http://lists.fedoraproject.org/pipermail/fedora-kde/2009- August/003555.html [4] https://bugzilla.redhat.com/show_bug.cgi?id=515419 -- Jaroslav Řezník jrez...@redhat.com Associate Software Engineer - Base Operating Systems Brno Office: +420 532 294 275 Mobile: +420 731 455 332 Red Hat, Inc. http://cz.redhat.com/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Soname bump for openssl
Hi all, I'd like to upgrade OpenSSL to 1.0.0-beta3 version just after the F12 Alpha release. I asked rel-eng to create a custom build target for the rebuild so we can avoid shipping the symlink hacks in rawhide. The API did not change in a way it would break any sensible user's of the API, so no patches to the dependent packages are expected to be necessary. Unfortunately as this is major version upgrade the ABI changed. I know that the upgrade would be better before the F12 Alpha however it required major patch porting for the FIPS validation related code which is not included in the upstream 1.0.0 branch. I was unfortunately not able to complete this porting before Alpha Freeze. As always I will rebuild all the dependent packages if you do not ask me otherwise for your package. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
rawhide report: 20090812 changes
Compose started at Wed Aug 12 06:15:05 UTC 2009 New package usbmuxd Daemon for communicating with Apple's iPod Touch and iPhone Removed package cryptix Removed package cryptix-asn1 Updated Packages: firstboot-1.108-1.fc12 -- * Tue Aug 11 2009 Chris Lumens clum...@redhat.com 1.108-1 - Move python-meh initialization to after we have gtk imported (#515419). - Do @VERSION@ substitution on progs/firstboot. - Switch to using system-config-keyboard for the keyboard bits (katzj). - Stop using rhpl.ethtool (katzj). gdb-6.8.50.20090811-2.fc12 -- * Tue Aug 11 2009 Jan Kratochvil jan.kratoch...@redhat.com - 6.8.50.20090811-1 - Support constant DW_AT_data_member_location by GCC PR debug/40659 (BZ 515377). - Fix .spec URL. - archer-jankratochvil-fedora12 commit: 81de3c6abae4f7e3738aa9bcc0ab2f8725cce252 * Tue Aug 11 2009 Jan Kratochvil jan.kratoch...@redhat.com - 6.8.50.20090811-2 - archer-jankratochvil-fedora12 commit: 93f5e942bdcdcc376ece452c309bedabae71def9 - Fix can't compute CFA for this frame (by Tom Tromey, BZ 516627). * Mon Aug 10 2009 Jan Kratochvil jan.kratoch...@redhat.com - 6.8.50.20090810-2 - Upgrade to the FSF GDB gdb-6.8.50 snapshot: 6.8.50.20090810 - archer-jankratochvil-fedora12 commit: 93ec16e6f5000dd64d433d86674e820ed0f35b72 gnu-efi-3.0e-9.fc12 --- * Tue Aug 11 2009 Peter Jones pjo...@redhat.com - 3.0e-9 - Change ExclusiveArch to reflect arch changes in repos. gtk2-2.17.6-6.fc12 -- * Tue Aug 11 2009 Matthias Clasen mcla...@redhat.com - 2.17.6-6 - Fix setting root cursors ifuse-0.9.3-1.fc12 -- * Mon Aug 10 2009 Peter Robinson pbrobin...@gmail.com 0.9.3-1 - Update to 0.9.3 release kernel-2.6.31-0.125.4.2.rc5.git2.fc12 - * Wed Aug 12 2009 Matthew Garrett m...@redhat.com - linux-2.6-pat-fix.patch - fix potential memory corruption in KMS * Tue Aug 11 2009 Kyle McMartin k...@redhat.com - private-f12-2_6_31_rc5-imeanit: LZMA. OFF. I MEAN IT. libiphone-0.9.3-1.fc12 -- * Mon Aug 10 2009 Peter Robinson pbrobin...@gmail.com 0.9.3-1 - Update to 0.9.3 release libvirt-0.7.0-3.fc12 * Mon Aug 10 2009 Mark McLoughlin mar...@redhat.com - 0.7.0-3 - Don't fail to start network if ipv6 modules is not loaded * Thu Aug 06 2009 Mark McLoughlin mar...@redhat.com - 0.7.0-2 - Make sure qemu can access kernel/initrd (bug #516034) - Set perms on /var/lib/libvirt/boot to 0711 (bug #516034) * Wed Aug 05 2009 Daniel Veillard veill...@redhat.com - 0.7.0-1 - Upstream release of 0.7.0 - ESX, VBox3, Power Hypervisor drivers - new net filesystem glusterfs - Storage cloning for LVM and Disk backends - interface implementation based on netcf - Support cgroups in QEMU driver - QEmu hotplug NIC support - a lot of fixes mutter-2.27.2-1.fc12 * Tue Aug 11 2009 Peter Robinson pbrobin...@gmail.com 2.27.2-1 - New upstream 2.27.2 release. Drop upstreamed patches. pango-1.25.2-1.fc12 --- * Tue Aug 11 2009 Behdad Esfahbod besfa...@redhat.com - 1.25.2-1 - 1.25.2 pyxf86config-0.3.37-7.fc12 -- * Fri Aug 07 2009 Dave Airlie airl...@redhat.com 0.3.37-6 - fix ErrorF/VErrorF symbol visibility - hacky but should do for now * Fri Aug 07 2009 Dave Airlie airl...@redhat.com 0.3.37-7 - fix X server and put this back Summary: Added Packages: 1 Removed Packages: 2 Modified Packages: 11 Broken deps for i386 -- 389-ds-1.1.3-4.fc12.noarch requires 389-ds-admin R-RScaLAPACK-0.5.1-19.fc11.i586 requires openmpi-libs asterisk-fax-1.6.1-0.24.rc1.fc12.i686 requires libspandsp.so.1 bigboard-0.6.4-12.fc12.i686 requires mugshot = 0:1.1.90-1 clutter-cairomm-0.7.4-2.fc11.i586 requires libclutter-cairo-0.8.so.0 clutter-cairomm-0.7.4-2.fc11.i586 requires libcluttermm-0.8.so.2 clutter-cairomm-0.7.4-2.fc11.i586 requires libclutter-glx-0.8.so.0 clutter-cairomm-devel-0.7.4-2.fc11.i586 requires pkgconfig(cluttermm-0.8) clutter-cairomm-devel-0.7.4-2.fc11.i586 requires pkgconfig(clutter-0.8) clutter-gtkmm-0.9.4-1.fc12.i586 requires libclutter-gtk-0.9.so.0 clutter-gtkmm-0.9.4-1.fc12.i586 requires libclutter-glx-0.9.so.0 clutter-gtkmm-devel-0.9.4-1.fc12.i586 requires pkgconfig(clutter-gtk-0.9) cluttermm-0.9.4-1.fc12.i586 requires libclutter-glx-0.9.so.0 cluttermm-devel-0.9.4-1.fc12.i586 requires pkgconfig(clutter-0.9) dap-hdf4_handler-3.7.9-2.fc11.i586 requires libdap.so.9 dap-hdf4_handler-3.7.9-2.fc11.i586 requires libdapserver.so.6 entertainer-0.4.2-5.fc12.noarch requires pyclutter-cairo octave-forge-20080831-10.fc12.i686 requires octave(api) = 0:api-v32 perl-DBIx-Class-Schema-Loader-0.04006-4.fc12.noarch requires perl(DBIX::Class) php-layers-menu-3.2.0-0.2.rc.fc12.noarch requires
Re: Soname bump for openssl
On Wed, Aug 12, 2009 at 11:45:50AM +0200, Tomas Mraz wrote: Hi all, I'd like to upgrade OpenSSL to 1.0.0-beta3 version just after the F12 Alpha release. I asked rel-eng to create a custom build target for the rebuild so we can avoid shipping the symlink hacks in rawhide. A few questions: Why a beta version? Is there a good chance the final upstream release will be done before F12 GAs? Will the beta nature of the release cause lots of potential rebuilds as you update it with newer betas? josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: help needed for bug #512115 (Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display...)
On Tue, 11 Aug 2009, Matthias Clasen wrote: Could you help with the following bug? https://bugzilla.redhat.com/show_bug.cgi?id=512115 It is a Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed error. This seems to be appeared with gtk 2.16.x. Pybliographer on F10 with gtk 2.14.7 has no problem. Try updating to the latest gtk2 update in f11 (2.16.5). That should fix it. I've done a yum update and gtk2 is 2.16.5 now. It doesn't fix the problem. Any idea what else could I check? Just for information: The machine I tested on now was a rawhide installation during f11 devel phase, and now it's still at the f11 stage. Before I started the update I checked the program on this machine, and it seemed with gtk 2.16.1 it was OK. Thanks for your help! Zoltan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Soname bump for openssl
On Wed, 2009-08-12 at 07:36 -0400, Josh Boyer wrote: On Wed, Aug 12, 2009 at 11:45:50AM +0200, Tomas Mraz wrote: Hi all, I'd like to upgrade OpenSSL to 1.0.0-beta3 version just after the F12 Alpha release. I asked rel-eng to create a custom build target for the rebuild so we can avoid shipping the symlink hacks in rawhide. A few questions: Why a beta version? Because the changes on the 1.0.0 branch will not break ABI as they will be bugfix-only and it will allow us to upgrade to 1.0.0 later. Is there a good chance the final upstream release will be done before F12 GAs? Yes, there is, but of course I cannot guarantee that. But it shouldn't be a problem too big as the beta3 is already in pretty good shape. Will the beta nature of the release cause lots of potential rebuilds as you update it with newer betas? If you mean rebuilds of dependencies then definitely not. And even rebuilds of openssl there should not be many as I suppose there will be a final release soon. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Soname bump for openssl
On Wed, Aug 12, 2009 at 03:38:27PM +0200, Tomas Mraz wrote: On Wed, 2009-08-12 at 07:36 -0400, Josh Boyer wrote: On Wed, Aug 12, 2009 at 11:45:50AM +0200, Tomas Mraz wrote: Hi all, I'd like to upgrade OpenSSL to 1.0.0-beta3 version just after the F12 Alpha release. I asked rel-eng to create a custom build target for the rebuild so we can avoid shipping the symlink hacks in rawhide. A few questions: Why a beta version? Because the changes on the 1.0.0 branch will not break ABI as they will be bugfix-only and it will allow us to upgrade to 1.0.0 later. Thanks for the quick response! One more question: Are we planning for a compat- package for the current OpenSSL version? josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Soname bump for openssl
On Wed, 2009-08-12 at 09:47 -0400, Josh Boyer wrote: On Wed, Aug 12, 2009 at 03:38:27PM +0200, Tomas Mraz wrote: On Wed, 2009-08-12 at 07:36 -0400, Josh Boyer wrote: On Wed, Aug 12, 2009 at 11:45:50AM +0200, Tomas Mraz wrote: Hi all, I'd like to upgrade OpenSSL to 1.0.0-beta3 version just after the F12 Alpha release. I asked rel-eng to create a custom build target for the rebuild so we can avoid shipping the symlink hacks in rawhide. A few questions: Why a beta version? Because the changes on the 1.0.0 branch will not break ABI as they will be bugfix-only and it will allow us to upgrade to 1.0.0 later. Thanks for the quick response! One more question: Are we planning for a compat- package for the current OpenSSL version? I currently do not plan it - we did not do it for recent OpenSSL soname bumps either, however I would not object if anyone wants to make the compat package. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Cannot rely on /dev being present in %post scripts?
According to bug #517013, %post scripts should not assume that /dev is available -- so we can't do anything that requires the existence of /dev/null, /dev/urandom, etc. Is this a known and expected packaging rule, or is it a bug in the way that the user is attempting to install the packages? -- David WoodhouseOpen Source Technology Centre david.woodho...@intel.com Intel Corporation -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: rawhide report: 20090812 changes
Rawhide Report wrote, at 08/12/2009 07:14 PM +9:00: Compose started at Wed Aug 12 06:15:05 UTC 2009 Broken deps for i386 -- sugar-pippy-34-2.fc12.i686 requires libstdc++.so.6(CXXABI_1.3)(64bit) sugar-pippy-34-2.fc12.i686 requires libc.so.6()(64bit) sugar-pippy-34-2.fc12.i686 requires libgcc_s.so.1(GCC_3.0)(64bit) sugar-pippy-34-2.fc12.i686 requires libm.so.6()(64bit) sugar-pippy-34-2.fc12.i686 requires libm.so.6(GLIBC_2.2.5)(64bit) sugar-pippy-34-2.fc12.i686 requires libc.so.6(GLIBC_2.2.5)(64bit) sugar-pippy-34-2.fc12.i686 requires libstdc++.so.6()(64bit) sugar-pippy-34-2.fc12.i686 requires libstdc++.so.6(GLIBCXX_3.4)(64bit) sugar-pippy-34-2.fc12.i686 requires libgcc_s.so.1()(64bit) This is very strange and should not happen. Actually this i686 binary package contains the following binary files: /usr/share/sugar/activities/Pippy.activity/library/pippy/physics/box2d/box2d_linux64/_Box2D2.so /usr/share/sugar/activities/Pippy.activity/library/pippy/physics/box2d/box2d_linux32/_Box2D2.so These files - are installed under %_datadir, although these are arch-dependent - and it seems these files are pre-compiled files in the tarball. Regards, Mamoru -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: 2009-08-13: Fedora 12 Test Day - NetworkManager
On Tue, 2009-08-11 at 16:19 -0700, Adam Williamson wrote: Yes, folks, it's that time of year again - Test Day time! The first main cycle Test Day[1] of the Fedora 12 cycle is happening on Thursday, and it's all about...NetworkManager. [1]: https://fedoraproject.org/wiki/Test_Day:2009-08-13_NetworkManager [2]: http://fedoraproject.org/wiki/How_to_use_IRC The Live Images referenced at [1] above seem to have disappeared. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Cannot rely on /dev being present in %post scripts?
On Wed, Aug 12, 2009 at 4:18 PM, David Woodhouse dw...@infradead.orgwrote: According to bug #517013, %post scripts should not assume that /dev is available -- so we can't do anything that requires the existence of /dev/null, /dev/urandom, etc. Is this a known and expected packaging rule, or is it a bug in the way that the user is attempting to install the packages? IMHO, if i want to install something in a chroot i have to create /dev, and /proc entry at least or put a bind mount to these. So, i think that it is the user have do some error in installaling the package. Regards -- David WoodhouseOpen Source Technology Centre david.woodho...@intel.com Intel Corporation -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: 2009-08-13: Fedora 12 Test Day - NetworkManager
Hi. On Wed, 12 Aug 2009 12:32:48 -0400, Matthias Clasen wrote Sorry, I had no idea somebody else was referring to them. Next time, kindly tell me if you want to reuse something that I put up with the explicit warning that it will be removed shortly after the test day that it was intended for... Errr. wouldn't that be tomorrow, technically? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Cannot rely on /dev being present in %post scripts?
On Wed, Aug 12, 2009 at 03:18:16PM +0100, David Woodhouse wrote: According to bug #517013, %post scripts should not assume that /dev is available -- so we can't do anything that requires the existence of /dev/null, /dev/urandom, etc. Is this a known and expected packaging rule, or is it a bug in the way that the user is attempting to install the packages? I mentioned it already in the bug report: There are some scriptlet recommendations that use /dev/null: https://fedoraproject.org/wiki/Packaging:ScriptletSnippets Regards Till pgpVetQ7miiwI.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: 2009-08-13: Fedora 12 Test Day - NetworkManager
On Wed, 2009-08-12 at 18:40 +0200, Ralf Ertzinger wrote: Hi. On Wed, 12 Aug 2009 12:32:48 -0400, Matthias Clasen wrote Sorry, I had no idea somebody else was referring to them. Next time, kindly tell me if you want to reuse something that I put up with the explicit warning that it will be removed shortly after the test day that it was intended for... Errr. wouldn't that be tomorrow, technically? No, my isos were for the Fit and Finish test day that happened yesterday. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: 2009-08-13: Fedora 12 Test Day - NetworkManager
Hi. On Wed, 12 Aug 2009 12:51:26 -0400, Matthias Clasen wrote Errr. wouldn't that be tomorrow, technically? No, my isos were for the Fit and Finish test day that happened yesterday. Well, they're referenced on the wiki page regarding the NM test tomorrow. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: 2009-08-13: Fedora 12 Test Day - NetworkManager
On Wed, 2009-08-12 at 18:56 +0200, Ralf Ertzinger wrote: Hi. On Wed, 12 Aug 2009 12:51:26 -0400, Matthias Clasen wrote Errr. wouldn't that be tomorrow, technically? No, my isos were for the Fit and Finish test day that happened yesterday. Well, they're referenced on the wiki page regarding the NM test tomorrow. Yes. But I did not put that reference there, and I did not know about it. That is why I removed the isos after they served their purpose yesterday... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: 2009-08-13: Fedora 12 Test Day - NetworkManager
On Tue, 2009-08-11 at 16:19 -0700, Adam Williamson wrote: Yes, folks, it's that time of year again - Test Day time! The first main cycle Test Day[1] of the Fedora 12 cycle is happening on Thursday, and it's all about...NetworkManager. We've got some fairly specific test cases lined up (on the page already) to test the new features of NetworkManager for Fedora 12, but please do also come along, grab the live CD, and just test that NetworkManager is doing the right thing with whatever connections you have; we want to make sure it's all right for Fedora 12. There's a live CD available so you won't need a Rawhide installation, and myself and Dan Williams (our venerable NetworkManager wrangler) will be around to help with testing. The Test Day takes place in #fedora-qa on Freenode IRC: see this page[2] if you don’t know how to use IRC. See you there! I actually realized we'll need another koji build for the iscsi/assume stuff. Can that get rolled into the livecd before tomorrow? Dan [1]: https://fedoraproject.org/wiki/Test_Day:2009-08-13_NetworkManager [2]: http://fedoraproject.org/wiki/How_to_use_IRC -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Epiphany effectively orphaned
In the course of doing a bug report on Epiphany, it's come up that Epiphany is effectively orphaned: https://admin.fedoraproject.org/pkgdb/packages/name/epiphany it is owned by gecko-maint, but since it's now based on Webkit, that makes no sense, and I see no reason to expect the Gecko maintainers group to care about Epiphany. It seems like whoever controls the 'gecko-maint' group should formally orphan Epiphany, and someone else should pick it up. For reference, the bug I was reporting was https://bugzilla.redhat.com/show_bug.cgi?id=516938 . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: 2009-08-13: Fedora 12 Test Day - NetworkManager
On Wed, 2009-08-12 at 12:35 -0500, Dan Williams wrote: On Tue, 2009-08-11 at 16:19 -0700, Adam Williamson wrote: Yes, folks, it's that time of year again - Test Day time! The first main cycle Test Day[1] of the Fedora 12 cycle is happening on Thursday, and it's all about...NetworkManager. We've got some fairly specific test cases lined up (on the page already) to test the new features of NetworkManager for Fedora 12, but please do also come along, grab the live CD, and just test that NetworkManager is doing the right thing with whatever connections you have; we want to make sure it's all right for Fedora 12. There's a live CD available so you won't need a Rawhide installation, and myself and Dan Williams (our venerable NetworkManager wrangler) will be around to help with testing. The Test Day takes place in #fedora-qa on Freenode IRC: see this page[2] if you don’t know how to use IRC. See you there! I actually realized we'll need another koji build for the iscsi/assume stuff. Can that get rolled into the livecd before tomorrow? If you do the koji build then let me know by email or IRC, I'll try and get a new live image rolled. thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Epiphany effectively orphaned
On Wed, 2009-08-12 at 11:29 -0700, Adam Williamson wrote: In the course of doing a bug report on Epiphany, it's come up that Epiphany is effectively orphaned: https://admin.fedoraproject.org/pkgdb/packages/name/epiphany it is owned by gecko-maint, but since it's now based on Webkit, that makes no sense, and I see no reason to expect the Gecko maintainers group to care about Epiphany. It seems like whoever controls the 'gecko-maint' group should formally orphan Epiphany, and someone else should pick it up. For reference, the bug I was reporting was https://bugzilla.redhat.com/show_bug.cgi?id=516938 . I'd say you are making stuff up based on a throwaway comment of mine... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Updates lacking descriptions
I've noticed 4 updates for Fedora 10 recently that lacked any description, bug-links or any information besides the package version to explain what they were or what they would do. This is a problem. The update #s are: 6250, 6409, 7653 and 7838. I posted comments on their pages at admin.fedoraproject.org requesting a description, and have not had any response so far. I commented on one about a month ago, and the other 3 just now. I would have directly contacted the submitters, but I was unable to find a way to do that from the admin.fedoraproject.org update pages. What would be a good next step for me to take to help get descriptions added to these updates (and make sure this happens less often in the future) ? (I'm not receiving mail from the list, although I'll check the archives; so please CC me if you want me to see your reply promptly) Jesse Weinstein -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Epiphany effectively orphaned
On Wed, 2009-08-12 at 15:05 -0400, Matthias Clasen wrote: On Wed, 2009-08-12 at 11:29 -0700, Adam Williamson wrote: In the course of doing a bug report on Epiphany, it's come up that Epiphany is effectively orphaned: https://admin.fedoraproject.org/pkgdb/packages/name/epiphany it is owned by gecko-maint, but since it's now based on Webkit, that makes no sense, and I see no reason to expect the Gecko maintainers group to care about Epiphany. It seems like whoever controls the 'gecko-maint' group should formally orphan Epiphany, and someone else should pick it up. For reference, the bug I was reporting was https://bugzilla.redhat.com/show_bug.cgi?id=516938 . I'd say you are making stuff up based on a throwaway comment of mine... Making what up? How does it make sense for a project that's no longer based on Gecko to be maintained by the Gecko maintainers group? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Epiphany effectively orphaned
On Wed, 2009-08-12 at 12:20 -0700, Adam Williamson wrote: On Wed, 2009-08-12 at 15:05 -0400, Matthias Clasen wrote: On Wed, 2009-08-12 at 11:29 -0700, Adam Williamson wrote: In the course of doing a bug report on Epiphany, it's come up that Epiphany is effectively orphaned: https://admin.fedoraproject.org/pkgdb/packages/name/epiphany it is owned by gecko-maint, but since it's now based on Webkit, that makes no sense, and I see no reason to expect the Gecko maintainers group to care about Epiphany. It seems like whoever controls the 'gecko-maint' group should formally orphan Epiphany, and someone else should pick it up. For reference, the bug I was reporting was https://bugzilla.redhat.com/show_bug.cgi?id=516938 . I'd say you are making stuff up based on a throwaway comment of mine... Making what up? How does it make sense for a project that's no longer based on Gecko to be maintained by the Gecko maintainers group? Well, what you said was different, namely that it is not maintained at all. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Epiphany effectively orphaned
On Wed, 2009-08-12 at 15:27 -0400, Matthias Clasen wrote: On Wed, 2009-08-12 at 12:20 -0700, Adam Williamson wrote: On Wed, 2009-08-12 at 15:05 -0400, Matthias Clasen wrote: On Wed, 2009-08-12 at 11:29 -0700, Adam Williamson wrote: In the course of doing a bug report on Epiphany, it's come up that Epiphany is effectively orphaned: https://admin.fedoraproject.org/pkgdb/packages/name/epiphany it is owned by gecko-maint, but since it's now based on Webkit, that makes no sense, and I see no reason to expect the Gecko maintainers group to care about Epiphany. It seems like whoever controls the 'gecko-maint' group should formally orphan Epiphany, and someone else should pick it up. For reference, the bug I was reporting was https://bugzilla.redhat.com/show_bug.cgi?id=516938 . I'd say you are making stuff up based on a throwaway comment of mine... Making what up? How does it make sense for a project that's no longer based on Gecko to be maintained by the Gecko maintainers group? Well, what you said was different, namely that it is not maintained at all. sorry, I meant 'orphaned' in the sense that its listed maintainer is no longer appropriate - it needs to have the listed maintainer changed to an appropriate person / group. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Epiphany effectively orphaned
sorry, I meant 'orphaned' in the sense that its listed maintainer is no longer appropriate - it needs to have the listed maintainer changed to an appropriate person / group. Wouldn't that be to the current maintainer to say so? -- Mathieu Bridon (bochecha) -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Anaconda install askmethod
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 11 Aug 2009, Mike Chambers wrote: On Tue, 2009-08-11 at 14:35 -1000, David Cantrell wrote: What version of anaconda did you try? I just recently fixed a problem with askmethod not doing anything. If you booted from a CD or DVD but wanted to do a network install, the askmethod parameter was not working. That fix is in anaconda-12.12-1. I'll give it a shot again here in the next day or so, maybe this weekend if I get time and some personal things don't get in the way. I believe 12.7 was the last version I tried with. My mistake and I see a bug has already been filed. I was confusing 'askmethod' with 'asknetwork'. I had fixed a problem around the asknetwork parameter. - -- David Cantrell dcantr...@redhat.com Red Hat / Honolulu, HI -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqDG88ACgkQ5hsjjIy1Vkn5FwCgx7vfH0u4VPN5GHuc7uwzQPhN tfEAoNYKBOoDcJUDeJCG275GJ9g3VECx =IcfP -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Epiphany effectively orphaned
On Wed, 2009-08-12 at 21:37 +0200, Mathieu Bridon (bochecha) wrote: sorry, I meant 'orphaned' in the sense that its listed maintainer is no longer appropriate - it needs to have the listed maintainer changed to an appropriate person / group. Wouldn't that be to the current maintainer to say so? sure, if the 'gecko-maint' group is happy to maintain a non-gecko component, that's fine (though may look a bit confusing). I just wanted to flag the issue up, as Epiphany is a quite important package (it's GNOME's official browser, even if we ship Firefox on our 'desktop' spin). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Updates lacking descriptions
2009/8/12 Jesse W je...@wefu.org: What would be a good next step for me to take to help get descriptions added to these updates (and make sure this happens less often in the future) ? I've even coded a test patch to bohdi (attached) to warn maintainers when they are prepping the update without a description, but so far it's been ignored. See https://fedorahosted.org/bodhi/ticket/294 if you're interested. Richard. bodhi-description-fixes-ideas.patch Description: application/force-download -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Switch from OpenAL to OpenAL-Soft
I think it?s better when openal-soft will come with f12. The Packager have enough time to rebuild there packages. But when the packager want to rebuild there packages i will make an package for f11. Am 11.08.2009 23:39, schrieb Bastien Nocera: On Tue, 2009-08-11 at 23:18 +0200, LinuxDonald wrote: OpenAL-Soft use the openal.so.1 lib openal use the openal.so.0 lib. And that is the problem. Then ask for rebuilds, not for everyone to change all their packages... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Switch from OpenAL to OpenAL-Soft
I think it?s better when openal-soft will come with f12. The Packager have enough time to rebuild there packages. But when the packager want to rebuild there packages i will make an package for f11. Am 11.08.2009 23:39, schrieb Bastien Nocera: On Tue, 2009-08-11 at 23:18 +0200, LinuxDonald wrote: OpenAL-Soft use the openal.so.1 lib openal use the openal.so.0 lib. And that is the problem. Then ask for rebuilds, not for everyone to change all their packages... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Updates lacking descriptions
On Wed, Aug 12, 2009 at 12:06:56PM -0700, Jesse W wrote: What would be a good next step for me to take to help get descriptions added to these updates (and make sure this happens less often in the future) ? It should fall back to taking the description from the changelog (in fact, I think it already does that right now). Don't make package maintainers write 'New upstream release X.Y.Z' any more often than they have to ... Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Epiphany effectively orphaned
On 08/12/2009 11:29 AM, Adam Williamson wrote: In the course of doing a bug report on Epiphany, it's come up that Epiphany is effectively orphaned: https://admin.fedoraproject.org/pkgdb/packages/name/epiphany it is owned by gecko-maint, but since it's now based on Webkit, that makes no sense, and I see no reason to expect the Gecko maintainers group to care about Epiphany. I wouldn't say it's orphaned, but perhaps we probably should change the owner on it. For what its worth, the gecko group has done some WebKit related work in the not-so-distant past. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: source file audit - 2009-08-10
On Wed, 12 Aug 2009 07:32:29 +0300 Ville Skyttä ville.sky...@iki.fi wrote: On Tuesday 11 August 2009, Kevin Fenzi wrote: http://www.scrye.com/~kevin/fedora/sourcecheck/sourcecheck It doesn't seem to process https sources, only http and ftp. Is that an oversight? Yes. ;( Fixed for the next run. ;( kevin signature.asc Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: source file audit - 2009-08-10
On Tue, 11 Aug 2009 21:37:40 +0200 Mathieu Bridon (bochecha) boche...@fedoraproject.org wrote: Hi, This was run against Rawhide right? Yes. bochecha:BADURL:adonthell-0.3.5.tar.gz:adonthell Fixed in Rawhide (at least after the freeze is lifted). erikos:BADSOURCE:sugar-base-0.85.2.tar.bz2:sugar-base This is a development release. As per the roadmap, 0.85.3 should be out pretty soon [1]. I'll just let this one like this, it will be fixed by the end of August when one of us updates the package. ok. Up to you... Thanks for the reminder, that's a great help in keeping the Fedora repositories a bit saner! :) No problem. kevin signature.asc Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Fedora 12 Alpha Blocker Meeting 2009-08-14 @ 15:00 UTC (11 AM EDT)
When: Friday, 2009-08-14 @ 15:00 UTC (11 AM EDT) Where: #fedora-bugzappers on irc.freenode.net Join us Friday for what we hope to be the last blocker bug review meeting for the Fedora 12 Alpha. On Friday we will review the unresolved bugs on https://bugzilla.redhat.com/showdependencytree.cgi?id=507676hide_resolved=1 Here are the bugs presently blocking the Fedora 12 Alpha: * 515472 [ASSIGNED - medium - pjo...@redhat.com - --- -] f12 alpha system can not reboot [See dependency tree for bug 515472] * 516941 [MODIFIED - medium - kernel-ma...@redhat.com - --- -] kms broken and can cause oops without git3 upstream PAT patches [See dependency tree for bug 516941] * 517171 [NEW - medium - anaconda-maint-l...@redhat.com - --- -] Installation fails to find repodata when booting from boot.iso [See dependency tree for bug 517171] If you are aware of any bugs you think should block the Alpha, please set them to block 'F12Alpha' and come to the meeting to help guide the discussion. Thanks for your help and time, John -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Updates lacking descriptions
Ben Boeckel wrote: Updates need to be more descriptive than this. Changelog entries and CVS commits can range from split package to oops, forgot the patch to attempted before newRepo finished, bump release. These are useless as update texts. Maintainers should list things that have changed (features added, upstream bugs fixed, etc.). Linking the upstream changelog or release announcement is also good. If this is enforced (and it may be good to add it to the critical-path suggestion), updates will be reduced since when there's little to write about, there's less justification for an update in the first place. I agree wholeheartedly. Without following the upstream release announcements closely, a simple Update to new upstream release X.Y.Z means _nothing_ to users. We should want people to know what changed, at least briefly, with the updated version. What does the new release bring? Does it fix any security or other major bugs? Is it still compatible? I always ask myself these four main questions when creating an update notice through Bodhi: 1. Does this package fix any security issues? These should *always* be mentioned, with some unique and reputable identifier for it (e.g., a CVE number, Fedora/upstream bugzilla report, etc.). From my experiences, this is the only true requirement of Bodhi of these four, since it's necessary for the security team's approval of the update push request. 2. Does this package fix any show stopper bugs? Users should be told when the update fixes issues like crashers or data corruption, which significantly reduce (or worse, eliminate) the package's usefulness. 3. Does this update bring any cool new features to users? I feel it important to note any major feature additions that would entice users to the update. Among a possible myriad of such changes, perhaps it supports a new and better file format (e.g.,an office program having ODF support added), or updated translations, etc.? 4. Lastly, Will this cause any expected or known incompatibilities (backward OR forward) for the user? Would they need to recreate/adapt their existing configuration? Okay, so this last one is actually two questions, but the point remains: it is sometimes necessary to cause an incompatibility that can not (or perhaps should not¹) be prevented. Hopefully, such a change can be mitigated automagically (perhaps with some sed/awk-fu in the %post scriptlet or similar); but this is not always the case (especially if it's within the users' $HOME directories). Also, regardless of whether or not such an automatic change is done, the user SHOULD be informed about it. At best, they would then know *why* their configuration file(s) changed; and at worst, they would know to effect the change(s) themselves. In short: I think it's very reasonable for users to expect that new updates will work with their existing setups without modifications, and it's similarly reasonable to expect a big fat warning of some sort when this is not the case. [1] For example, if there is a major security bug caused by how the configuration is stored, and fixing it would change the format, then the decision is between breaking compatibility or keeping the program insecure: one that must be made for the former, much to users' potential frustration. With my updates, I try to always give a brief summary of what I think are the most important and/or most visible changes - answering these four questions - along with a mention on how to view the upstream changelog for it, so they can know everything that changed, and not just what the update mentions. -- Peter Gordon (codergeek42) pe...@thecodergeek.com signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: source file audit - 2009-08-10
On 08/10/2009 09:45 PM, Kevin Fenzi wrote: sundaram:BADURL:gnote-0.6.1.tar.bz2:gnote Built 0.6.2 with the correct url sundaram:BADURL:pyroom-0.4.1.tar.gz:pyroom Fixed in cvs. Won't do a rebuild. Thanks. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Plan for Friday's (20090814) FESCo meeting
The following topics will be discussed at Friday's FESCo meeting at 17:00UTC in #fedora-meeting on irc.freenode.net: 235 Apcupsd - static linking 241 Fedora Packaging Committee items for ratification 238 Can libvdpau go in Fedora? 236 Proposal to allow translated versions of Publican-created documents to bypass review. 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. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Updates lacking descriptions
Richard W.M. Jones rjones at redhat.com writes: It should fall back to taking the description from the changelog (in fact, I think it already does that right now). Where would I find the changelog? It's not visibly connected either to the description that shows up along with the update, or on the admin.fedoraproject.org page that is linked from there. And, what can I do to help get descriptions added for the 4 updates I mentioned? How can I find contact info for the submitters of those updates, or is there someone else who can add descriptions? Thanks to everyone who responded -- I'm glad that this is a live issue, and that some maintainers are careful to provide useful and complete update descriptions. Thanks again, Jesse -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 11 slapd too many open files: /lib64/libnspr4.so
Ping? This bug is pretty nasty: we have to restart slapd 2 or 3 times a day :-/ El Mon, 10-08-2009 a las 02:08 +0200, Bernie Innocenti escribió: Hello, I'm running into a problem with Fedora 11 and OpenLDAP's slapd instance (the same configuration that I've used for F8, F9, F10 and now F11). After a day or two, of continuous usage, the slapd instance hangs with the too many open files issue. I googled around a bit and found that some have fixed the problem by adding the following line to slapd.conf: # Disconnect idle connections idletimeout 60 This doesn't really seem to make a difference. When I do lsof -u ldap, I get the normal output of files in mem, followed by a ton of these: ... ... slapd 19221 ldap 37r REG 8,51235360 418680 /lib64/libnspr4.so slapd 19221 ldap 38r REG 8,51235360 418680 /lib64/libnspr4.so slapd 19221 ldap 39r REG 8,51235360 418680 /lib64/libnspr4.so slapd 19221 ldap 40r REG 8,51235360 418680 /lib64/libnspr4.so ... ... that never seem to go away, and lead to the too many open files issue. Can anyone offer some assistance as to how to fix this issue? Thank you in advance. -Anthony Did you eventually solve this issue? If not, is there a bug already filed in Bugzilla? I'm still seeing exactly the same on F11 with all updates installed as of today. I'd be tempted to point fingers at nss-softokn-freebl, as this is where the code to ope libnspr4.so actually lives. Upgrading openldap-servers and to rawhide has no effect. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Updates lacking descriptions
On 08/12/2009 11:54 PM, Ben Boeckel wrote: If this is enforced (and it may be good to add it to the critical-path suggestion), updates will be reduced since when there's little to write about, there's less justification for an update in the first place. Correct, such a step will add a significant bureaucratic burdons to maintainers. As maintainers hate bureaucrazy and prefer investing time on dealing with technical issues (such as bug fixes), this will likely introduce a further reduction of the quality of Fedora. Further more, do you realise that any changelog is likely similarly unreadable to most users? Ralf PS.: Stop cross-posting to newsgroups. I consider everybody who does this to behave rude. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 11 slapd too many open files: /lib64/libnspr4.so
El Thu, 13-08-2009 a las 07:12 +0200, Bernie Innocenti escribió:
Ping?
This bug is pretty nasty: we have to restart slapd
2 or 3 times a day :-/
Ok, I think I'm starting to see the light here, but perhaps
it's just because it's already dawn.
nss-3.12.3.99.3/mozilla/security/nss/lib/freebl/stubs.c
dlopen()s nspr4.so like so:
-8--8--8--8--8-
#define freebl_getLibrary(libName) \
dlopen (libName, RTLD_LAZY|RTLD_NOLOAD)
#define freebl_releaseLibrary(lib) \
if (lib) dlclose(lib)
#endif
extern SECStatus
FREEBL_InitStubs()
{
SECStatus rv = SECSuccess;
#ifdef FREEBL_NO_WEAK
void *nspr = NULL;
void *nssutil = NULL;
/* NSPR should be first */
if (!ptr_PR_DestroyLock) {
nspr = freebl_getLibrary(nsprLibName);
if (!nspr) {
return SECFailure;
}
rv = freebl_InitNSPR(nspr);
if (rv != SECSuccess) {
freebl_releaseLibrary(nspr);
return rv;
}
}
/* now load NSSUTIL */
if (!ptr_SECITEM_ZfreeItem_Util) {
nssutil= freebl_getLibrary(nssutilLibName);
if (!nssutil) {
return SECFailure;
}
rv = freebl_InitNSSUtil(nssutil);
if (rv != SECSuccess) {
freebl_releaseLibrary(nssutil);
return rv;
}
}
#endif
return rv;
}
-8--8--8--8--8-
There's no corresponding place in the code to call dlclose().
If slapd enters this multiple times (perhaps from multiple threads),
it might indeed leak file descriptors.
It remains to be determined what codepath in openldap does this.
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Broken dependencies: perl-DBIx-Class-Schema-Loader
perl-DBIx-Class-Schema-Loader has broken dependencies in the development tree: On ppc: perl-DBIx-Class-Schema-Loader-0.04006-4.fc12.noarch requires perl(DBIX::Class) On x86_64: perl-DBIx-Class-Schema-Loader-0.04006-4.fc12.noarch requires perl(DBIX::Class) On i386: perl-DBIx-Class-Schema-Loader-0.04006-4.fc12.noarch requires perl(DBIX::Class) On ppc64: perl-DBIx-Class-Schema-Loader-0.04006-4.fc12.noarch requires perl(DBIX::Class) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
