[Bug 814989] FTBFS, license outdated
https://bugzilla.redhat.com/show_bug.cgi?id=814989 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-Module-Starter-Plugin-CGIApp-0.41-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Finding out about a pkg?
I'm trying to follow up on struts, http://koji.fedoraproject.org/koji/buildinfo?buildID=239819 is the last mention I can see of it. yum with *testing shows nothing. How can I find if it's orphaned? -- Regards, Frank Jack of all, fubars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Finding out about a pkg?
On 05/26/2012 10:23 AM, Frank Murphy wrote: I'm trying to follow up on struts, http://koji.fedoraproject.org/koji/buildinfo?buildID=239819 is the last mention I can see of it. yum with *testing shows nothing. How can I find if it's orphaned? Hi, you could checkout the pkgdb: https://admin.fedoraproject.org/pkgdb/acls/name/struts It seems to be deprecated. Hope this helps, Johannes -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: How to proceed with MiniDebugInfo
On Thu, May 24, 2012 at 04:43:12PM +0200, Jan Kratochvil wrote: On Thu, 24 May 2012 16:35:57 +0200, Frank Ch. Eigler wrote: jan.kratochvil wrote: If your feature does not solve any problem it is just a bloat. This overstates the case. Alex's proposal clearly solves some problems. This is just about wording. My reaction was to: I don't think there has to be a specific problem. ... but then he goes on to list 4 or 5 different features, which are all nice to haves at a very small cost. I'll add one more case, which seems to happen to me all the time: - You're in IRC or email, and all the bug reporter has given you is a random copy and paste from their terminal. They don't care to open a bug; they don't much care about anything except getting a fix. Minidebuginfo would help here. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20120526 changes
Compose started at Sat May 26 08:15:05 UTC 2012 Broken deps for x86_64 -- [389-admin] 389-admin-1.1.28-1.fc18.i686 requires libicuuc.so.48 389-admin-1.1.28-1.fc18.i686 requires libicui18n.so.48 389-admin-1.1.28-1.fc18.i686 requires libicudata.so.48 389-admin-1.1.28-1.fc18.x86_64 requires libicuuc.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicui18n.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicudata.so.48()(64bit) [389-dsgw] 389-dsgw-1.1.9-2.fc17.x86_64 requires libicuuc.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicui18n.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicudata.so.48()(64bit) [aeolus-all] aeolus-all-0.4.0-2.fc17.noarch requires aeolus-conductor-doc = 0:0.4.0-2.fc17 aeolus-all-0.4.0-2.fc17.noarch requires aeolus-conductor-daemons = 0:0.4.0-2.fc17 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc18.noarch requires ruby-nokogiri [axis2c] axis2c-1.6.0-4.fc17.i686 requires httpd-mmn = 0:20051115-x86-32 axis2c-1.6.0-4.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [boost141] boost141-graph-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-graph-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-graph-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-graph-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) boost141-regex-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-regex-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-regex-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-regex-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [evolution-couchdb] evolution-couchdb-0.5.91-10.fc18.x86_64 requires libedata-cal-1.2.so.15()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libedata-book-1.2.so.13()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libecal-1.2.so.11()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libcamel-1.2.so.33()(64bit) [evolution-rss] 1:evolution-rss-0.3.91-1.fc18.x86_64 requires libedataserverui-3.0.so.1()(64bit) 1:evolution-rss-0.3.91-1.fc18.x86_64 requires libcamel-1.2.so.33()(64bit) [gambas3] gambas3-gb-pdf-3.1.1-2.fc18.x86_64 requires libpoppler.so.19()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python2-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python3-debug-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python3-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 [gdb-heap] gdb-heap-0.5-8.fc17.x86_64 requires glibc(x86-64) = 0:2.15 [ghc-warp] ghc-warp-0.4.6.3-3.fc18.i686 requires libHSwai-0.4.3-ghc7.4.1.so ghc-warp-0.4.6.3-3.fc18.i686 requires ghc(wai-0.4.3-876d0504e17291cc228eed88f0ba35c9) ghc-warp-0.4.6.3-3.fc18.x86_64 requires libHSwai-0.4.3-ghc7.4.1.so()(64bit) ghc-warp-0.4.6.3-3.fc18.x86_64 requires ghc(wai-0.4.3-80e159ce6c5c5bb23a495fb1953addc6) ghc-warp-devel-0.4.6.3-3.fc18.i686 requires ghc-devel(wai-0.4.3-876d0504e17291cc228eed88f0ba35c9) ghc-warp-devel-0.4.6.3-3.fc18.x86_64 requires ghc-devel(wai-0.4.3-80e159ce6c5c5bb23a495fb1953addc6) [gnome-pilot] gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libedataserverui-3.0.so.1()(64bit) gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libecal-1.2.so.11()(64bit) [gnome-python2-desktop] gnome-python2-evolution-2.32.0-9.fc17.x86_64 requires libecal-1.2.so.11()(64bit) [inkscape] inkscape-0.48.2-5.fc17.x86_64 requires libpoppler.so.19()(64bit) inkscape-view-0.48.2-5.fc17.x86_64 requires libpoppler.so.19()(64bit) [koji] koji-hub-1.6.0-3.fc17.noarch requires mod_python koji-web-1.6.0-3.fc17.noarch requires mod_python [mapnik] mapnik-2.0.0-4.fc17.i686 requires libicuuc.so.48 mapnik-2.0.0-4.fc17.x86_64 requires libicuuc.so.48()(64bit) mapnik-utils-2.0.0-4.fc17.x86_64 requires libicuuc.so.48()(64bit) [matreshka] matreshka-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnarl-4.6.so matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnarl-4.6.so()(64bit) matreshka-sql-core-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-core-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-postgresql-0.1.1-9.fc17.i686 requires libgnat-4.6.so
Re: SSD drives
2012/5/24 Michal Schmidt mschm...@redhat.com: On 05/24/2012 03:20 PM, Gerry Reno wrote: So is F17 going to support TRIM w/LUKS automatically? Or do we need to perform some special configuration to get TRIM w/LUKS? (Yes, I understand some attacker might be able to guess my filesystem type due to erased blocks - seems very low risk though). To use this feature, you can specify the option allow-discards in /etc/crypttab. You need systemd = 44-11, currently in updates-testing. Michal I have updated to systemd-44-12 to test this functionality, but I don't know if I'm doing it right. I have read that LVM has added support for passing discards to the layer below. Currently I have: Partition - Luks - LVM - ext4 ext4 is mounted with discard. I haven't done anything to LVM, and in /etc/crypttab I have added allow-discards as the fourth column. I suspect it isn't working because cryptsetup status /dev/mapper/luks-uuid does not say anything about discards. I think it must say flags: discards Any suggestion? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: How to proceed with MiniDebugInfo
On Sat, 26 May 2012 12:50:31 +0200, Richard W.M. Jones wrote: - You're in IRC or email, and all the bug reporter has given you is a random copy and paste from their terminal. They don't care to open a bug; they don't much care about anything except getting a fix. Minidebuginfo would help here. This is a bug of ABRT again. The crash should have been already reported without asking anything. (Not going to discuss some security claims.) You could just look up BZ(*) with the person's bugreport at that moment. (*) Maybe such mass bugreports should not end up in BZ as the first place. Regards, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
The package erlang-erlzmq2 can't be built for F-17 and F-18 (blocked)
Hello. This package was retired for some time and now it was re-enabled (see review request in https://bugzilla.redhat.com/810205 ). Unfortunately it still can't be built for F-17 anf F-18. Koji fails and returns quite cryptic messages like this one - FAILED: BuildError: package erlang-erlzmq2 is blocked for tag f18 (from this build attempt - http://koji.fedoraproject.org/koji/taskinfo?taskID=4104295 ). Surprisingly it builds just fine for F-16. I wonder what did we miss so far? And what should we do to re-add it back to the F-17 and Rawhide? -- With best regards, Peter Lemenkov. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The package erlang-erlzmq2 can't be built for F-17 and F-18 (blocked)
On Sat, May 26, 2012 at 4:36 PM, Peter Lemenkov lemen...@gmail.com wrote: Hello. This package was retired for some time and now it was re-enabled (see review request in https://bugzilla.redhat.com/810205 ). Unfortunately it still can't be built for F-17 anf F-18. Koji fails and returns quite cryptic messages like this one - FAILED: BuildError: package erlang-erlzmq2 is blocked for tag f18 (from this build attempt - http://koji.fedoraproject.org/koji/taskinfo?taskID=4104295 ). Surprisingly it builds just fine for F-16. I wonder what did we miss so far? And what should we do to re-add it back to the F-17 and Rawhide? Did you open a ticket with rel-eng to get it unblocked? https://fedorahosted.org/rel-eng/newticket Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Strategy for packaging an ARM Cortex-M toolchain
On 05/25/2012 08:27 PM, Ralf Corsepius wrote: Why have more than one gcc or binutils for arm-eabi at all? Just add multilibs for the extra variants of interest. You can even split the multilibs out into subpackages if it matters. This is simply not true. A gcc targeting glibc/linux is entirely different from a GCC targetting newlib and entirely different from a GCC targetting another OS. Exactly. There only needs to be one for newlib arm-eabi- it doesn't need to be Cortex-M specific. There only needs to be one for arm-linux-gneabi. Having arm-gp2x-linux is more specific than necessary. -- Brendan Conoboy / Red Hat, Inc. / b...@redhat.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: How to proceed with MiniDebugInfo
On Sat, May 26, 2012 at 12:50 PM, Richard W.M. Jones rjo...@redhat.com wrote: I'll add one more case, which seems to happen to me all the time: - You're in IRC or email, and all the bug reporter has given you is a random copy and paste from their terminal. They don't care to open a bug; they don't much care about anything except getting a fix. Minidebuginfo would help here. It seems you (and others in the thread) are hoping for an automatic backtrace on any crash - I don't think that's in the currently discussed scope. Even with this feature you'll have to walk them through 1) enabling core file creation, or finding the abrt-maintained core, and 2) running gdb or abrt on the core. I'm not sure whether minidebuginfo would make the situation actually simpler... Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 821632] perldoc man page is broken, shows Bperldoc [B-h] [B-D] etc
https://bugzilla.redhat.com/show_bug.cgi?id=821632 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA Last Closed||2012-05-26 03:22:32 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- perl-Pod-Perldoc-3.17-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 817256] perl-Glib-Object-Introspection-0.008 is available
https://bugzilla.redhat.com/show_bug.cgi?id=817256 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA Last Closed||2012-05-26 03:24:28 --- Comment #3 from Fedora Update System upda...@fedoraproject.org --- perl-Glib-Object-Introspection-0.008-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 818430] CVE-2012-2451 perl-Config-IniFiles: insecure temporary file usage [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=818430 --- Comment #9 from Fedora Update System upda...@fedoraproject.org --- perl-Config-IniFiles-2.72-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Net-OpenSSH
perl-Net-OpenSSH has broken dependencies in the rawhide tree:
On x86_64:
perl-Net-OpenSSH-0.57-3.fc18.noarch requires
openssh-clients(%{__isa_name}-%{__isa_bits})
On i386:
perl-Net-OpenSSH-0.57-3.fc18.noarch requires
openssh-clients(%{__isa_name}-%{__isa_bits})
Please resolve this as soon as possible.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
