Device Audio codec hwC0D0: Realtek and Device Audio codec hwC0D3: Intel on HDA Intel sound
Dear All. Recently I checked powertop and the first lines are: 100.0% Device Audio codec hwC0D0: Realtek 100.0% Device Audio codec hwC0D3: Intel I remember that it was only Intel codec. Do I really need - Audio codec hwC0D0: Realtek ? lspci: 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) ... Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel uname: Linux 3.1.0-0.rc10.git0.1.fc16.x86_64 #1 SMP Wed Oct 19 05:02:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Thanks in advance. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: BEWARE: a problematic glibc made it to stable (F16)
Am 23.10.2011 04:14, schrieb Kevin Kofler: Jim Meyering wrote: glibc-2.14.90-12.999, which has just made it to stable provokes a hard-to-diagnose (for me at least) problem. While most things work, and it fixed two problems that affected me, it caused me some frustration: https//bugzilla.redhat.com/747377 glibc-2.14.90-12.999 also breaks the build of ANY C++ code using fenv.h, which affects at least Qt (but likely also several other C++ packages, particularly mathematical ones, but not only, as can be seen from Qt). Thankfully, that showstopper is fixed in -13 which is already in stable by now (because it was aggressively up-karma'd by the KDE SIG). The fact that a glibc with showstoppers of this kind got pushed to stable shows that the karma system does not work at all. It just hinders getting legitimate fixes out and does nothing to stop regressions. glibc is even critpath, yet broken crap still goes out. Since a few days I've got the problem that lazarus and applications written with lazarus are running into an exception on closing them. Originaly I thought that this is a problem of that latest gtk2 update but could it be that glibc also affects lazarus, even if is pascal? Regards Heiko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Device Audio codec hwC0D0: Realtek and Device Audio codec hwC0D3: Intel on HDA Intel sound
Ok, as long as my sound onboard I disabled it, rebooted and enabled it again. So now I got in /sys/devices/pci:00/:00:1b.0/label only: Realtek High Definition Audio Device Where is my Intel HDA ? lspci: 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [ACTION REQUIRED v2] Retiring packages in F-16
Hello, I am replying to let you know that I succeeded in building gwaei. It took a fair bit of effort to get it going, because apparently the configure script that comes with gWaei doesn't properly pick up on 64-bit libraries (or Fedora's or the maintainer's gtk+-3 pkgconfig wasn't sane, or *something*). But in the end, it is now working nicely with a Gnome 3-like interface on my computer. Not only that, but the version of gWaei that was included in Fedora 15 was apparently *really* old (which might explain why it was broken). Some details on how to get it to compile are here: https://sourceforge.net/tracker/index.php?func=detailaid=3427591group_id=244762atid=1126810# If there is no package maintainer, I'm willing to try and be one, since I'm a bit of a fan of the software. (Though I'll have to study up on package maintaining.) Yours, - Vincent Beers -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Testers needed on short notice for 389DS, FreeIPA and SSSD update in F16
Please review the critical path update=20 https://admin.fedoraproject.org/updates/FEDORA-2011-14614 We're right up against the last minute to get these fixes in to ensure that all of these features work properly from the install DVD. We very desperately need testers (including one proventester, due to the selinux-policy update) to review these packages before the end of the day tomorrow (Monday Oct. 24) so that they can be pushed to stable in time for the release candidate build. signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Unresponsive Package Maintainer - Gary T. Giesen
I'm following the procedure at: http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers Does anyone know how to contact Gary T. Giesen? I've sent him an email (also CCed on this one) a few months ago requesting co-maintainer status for daemonize without a response. Gary has two open bugs without a response: https://bugzilla.redhat.com/show_bug.cgi?id=701383 https://bugzilla.redhat.com/show_bug.cgi?id=746783 His last koji build was in July 2009 - 27 months ago. -- sven === jabber/xmpp: s...@lankes.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: BEWARE: a problematic glibc made it to stable (F16)
Kevin Kofler wrote: Jim Meyering wrote: glibc-2.14.90-12.999, which has just made it to stable provokes a hard-to-diagnose (for me at least) problem. While most things work, and it fixed two problems that affected me, it caused me some frustration: https//bugzilla.redhat.com/747377 glibc-2.14.90-12.999 also breaks the build of ANY C++ code using fenv.h, which affects at least Qt (but likely also several other C++ packages, particularly mathematical ones, but not only, as can be seen from Qt). Thankfully, that showstopper is fixed in -13 which is already in stable by now (because it was aggressively up-karma'd by the KDE SIG). The fact that a glibc with showstoppers of this kind got pushed to stable shows that the karma system does not work at all. It worked in a way, but was an interesting case. As I see it, the general series of events went something like this: -10 was *generally* ok -11 fixed a few bugs, but introduced the nasty breaks grokking of /etc/groups, down karma'd -12 fixed some other bug, down-karma'd for not fixing -11 -12.999 got massive up-karma for fixing -11 problem, *but* introduced a new problem/regression. Got pushed stable. -13 was, of course, damage control from the fall-out from 12.999... Now, I'd argue the process worked up to -12.999, regressions were kept out of stable updates. The fail(*), imo, was with 12.999 going stable containing known-regressions. So, any suggestions, if any, to prevent any similar series of events? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: BEWARE: a problematic glibc made it to stable (F16)
sön 2011-10-23 klockan 17:04 -0500 skrev Rex Dieter: The fail(*), imo, was with 12.999 going stable containing known-regressions. So, any suggestions, if any, to prevent any similar series of events? My suggestions: Disable automatic push to stable when there is any negative karma, requiring the package maintainer to initiate the push even if karma kriteria have been met. Don't automatically push to stable until at least X days (3?) have passed, enabling sufficient time for regressions to be detected. Package maintainer can initiate push earlier by Push to stable if needed and confident there is no regressions. Make push to stable require extra confirmation when there is negative karma, making sure that whoever is initiating the push have actually looked at why there is negative karma. Regards Henrik -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fwd: Zif and SOS projects on Fedora Upstream
Hi. There is a project named SOS in Fedora collection on Transifex. I'd like to know if there is anyone maintaining it, because it seems like it needs to be translated, but there is no maintainer assigned in Tx and no translation team creation request has been fulfilled in 7 months. The latest change to code in Github is 6 months old. We tried to contact Adam Stokes mentioned in the source readme on Github, but no reply yet. Any help with getting response is much appreciated. -- Best regards, Misha Shnurapet, Fedora Project Contributor Email: shnurapet AT fedoraproject.org, IRC: misha on freenode https://fedoraproject.org/wiki/shnurapet, GPG: 00217306 Пересылаемое сообщение 21.10.2011, 20:42, Daniel Cabrera lo...@fedoraproject.org: On Wed, 2011-10-19 at 00:13 +0900, Misha Shnurapet wrote: Zif: I would send a message to Jorge González (aloriel at gmail.com), also nudge him in Transifex. Sos: I would contact the maintainer Adam Stokes (ajs AT redhat.com) or file a report in Github [1] where the code has moved. Also [2]. [1] https://github.com/sosreport/sosreport [2] https://github.com/sosreport/sosreport/blob/master/README -- Best regards, Misha Shnurapet, Fedora Project Contributor Email: shnurapet AT fedoraproject.org, IRC: misha on freenode https://fedoraproject.org/wiki/shnurapet, GPG: 00217306 -- Misha, Unfortunately until today I did not get any response to the emails I sent to Adam Stokes. Best regards, Daniel Cabrera (es) -- trans mailing list tr...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/trans Завершение пересылаемого сообщения -- trans mailing list tr...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/trans-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Systemd conversion versus updates in back Fedora branches
The current packaging guidelines require packages that update from sysv init scripts to systemd scripts to provide conversion triggers that are fired on the basis of an NVR comparison: https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Packages_migrating_to_a_systemd_unit_file_from_a_SysV_initscript That is, we assume that we know that all releases with NVR some-cutoff use initscripts and all releases with NVR = same-cutoff use systemd. The comments in the above-linked page acknowledge that this means it's impossible to upgrade the package to a newer upstream release in pre-systemd Fedora branches. (You can't just move the cutoff value forward, because then an upgrade in F16 or later will mistakenly re-fire the update trigger.) I'm really getting to the point where that's a completely unacceptable restriction. I've already blown off one mysql bug-fix release in F15 because of this restriction, and I see they just released another one that I'll be unable to ship in F15 because the systemd guys failed to do their homework, and there are likely to be several more before F15 dies. The idea I have at the moment is to ignore the advice to check package version, and instead have the triggerun script check to see whether the mysql sysv initscript file is present. I wonder whether anyone else has dealt with this and has working scriptlets? regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Rwhide: Last Kernel not booting in vmware
Linux rawhide.vmware.local 3.1.0-0.rc9.git0.0.fc17.x86_64 #1 SMP Wed Oct 5 14:37:47 this is the last kernel booting in vmware for me all following see screenshot -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm attachment: screen.png signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 16 beta vice Knoppix
Camilo Mesias camilo at mesias.co.uk writes: Hi, I tried some of these changes and they seemed to work reasonably well apart from the grub2 infrastructure is still a bit immature at running without initrd... specifically ... I'm not sure where to report this? Bugs against grub2 or something else? Is there a specific forum for initrdless working? -Cam ... With regard to initrdless boots: https://bugzilla.redhat.com/show_bug.cgi?id=734274 JB -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Systemd conversion versus updates in back Fedora branches
Tom Lane wrote: The current packaging guidelines require packages that update from sysv init scripts to systemd scripts to provide conversion triggers that are fired on the basis of an NVR comparison: https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Packages_migrating_to_a_systemd_unit_file_from_a_SysV_initscript That is, we assume that we know that all releases with NVR some-cutoff use initscripts and all releases with NVR = same-cutoff use systemd. The comments in the above-linked page acknowledge that this means it's impossible to upgrade the package to a newer upstream release in pre-systemd Fedora branches. (You can't just move the cutoff value forward, because then an upgrade in F16 or later will mistakenly re-fire the update trigger.) I'm really getting to the point where that's a completely unacceptable restriction. I've already blown off one mysql bug-fix release in F15 because of this restriction, and I see they just released another one that I'll be unable to ship in F15 because the systemd guys failed to do their homework, and there are likely to be several more before F15 dies. The idea I have at the moment is to ignore the advice to check package version, and instead have the triggerun script check to see whether the mysql sysv initscript file is present. I wonder whether anyone else has dealt with this and has working scriptlets? FWIW, what the tomcat6 maintainers did is that they just ignored the guideline which says that you cannot migrate to systemd in an update and pushed this update: https://admin.fedoraproject.org/updates/FEDORA-2011-13456 (which is already in the stable updates). I'm starting to wonder whether that wouldn't be the best solution here. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-Hash-FieldHash] update to 0.12
commit a8f8e9daf641d752f11fb4cbddd6c5a4e3416daa
Author: Iain Arnell iarn...@gmail.com
Date: Sun Oct 23 08:00:41 2011 +0200
update to 0.12
.gitignore |1 +
perl-Hash-FieldHash.spec | 12 +++-
sources |2 +-
3 files changed, 9 insertions(+), 6 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 0873817..77075ca 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
/Hash-FieldHash-0.10.tar.gz
+/Hash-FieldHash-0.12.tar.gz
diff --git a/perl-Hash-FieldHash.spec b/perl-Hash-FieldHash.spec
index 7209f42..4865fee 100644
--- a/perl-Hash-FieldHash.spec
+++ b/perl-Hash-FieldHash.spec
@@ -1,19 +1,18 @@
Name: perl-Hash-FieldHash
-Version:0.10
-Release:2%{?dist}
+Version:0.12
+Release:1%{?dist}
Summary:Lightweight field hash implementation
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Hash-FieldHash/
Source0:
http://www.cpan.org/modules/by-module/Hash/Hash-FieldHash-%{version}.tar.gz
+BuildRequires: perl(Devel::PPPort) = 3.19
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(ExtUtils::ParseXS) = 2.21
BuildRequires: perl(parent) = 0.221
BuildRequires: perl(Test::LeakTrace)
BuildRequires: perl(Test::More) = 0.62
-BuildRequires: perl(XSLoader) = 0.1
-Requires: perl(parent) = 0.221
-Requires: perl(XSLoader) = 0.1
+BuildRequires: perl(XSLoader) = 0.02
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
%{?perl_default_filter}
@@ -48,6 +47,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Sun Oct 23 2011 Iain Arnell iarn...@gmail.com 0.12-1
+- update to latest upstream version
+
* Tue Aug 23 2011 Iain Arnell iarn...@gmail.com 0.10-2
- drop unnecessary explicit buildrequires
diff --git a/sources b/sources
index 75409e1..d320912 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-bb8cb7ac175b7021f8ea1afe4f502ef5 Hash-FieldHash-0.10.tar.gz
+9d1308462bca7f4757f0c9136a08610e Hash-FieldHash-0.12.tar.gz
--
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
File XML-Atom-0.41.tar.gz uploaded to lookaside cache by iarnell
A file has been added to the lookaside cache for perl-XML-Atom: 99eeebbf90c95cc1a24426a0b9f2d6a5 XML-Atom-0.41.tar.gz -- 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
[perl-XML-Atom] update to 0.41
commit 041fefb5c1c5fb2c57d5f03f0acf23e16f0902b5
Author: Iain Arnell iarn...@gmail.com
Date: Sun Oct 23 08:09:20 2011 +0200
update to 0.41
.gitignore |1 +
perl-XML-Atom.spec |9 +++--
sources|2 +-
3 files changed, 9 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 673c39b..4f09f87 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
XML-Atom-0.37.tar.gz
/XML-Atom-0.38.tar.gz
/XML-Atom-0.39.tar.gz
+/XML-Atom-0.41.tar.gz
diff --git a/perl-XML-Atom.spec b/perl-XML-Atom.spec
index 7991c7f..582ea29 100644
--- a/perl-XML-Atom.spec
+++ b/perl-XML-Atom.spec
@@ -1,6 +1,6 @@
Name: perl-XML-Atom
-Version:0.39
-Release:3%{?dist}
+Version:0.41
+Release:1%{?dist}
Summary:Atom feed and API implementation
License:GPL+ or Artistic
Group: Development/Libraries
@@ -12,6 +12,7 @@ BuildArch: noarch
BuildRequires: perl(Class::ISA)
BuildRequires: perl(Class::Data::Inheritable)
BuildRequires: perl(DateTime)
+BuildRequires: perl(DateTime::TimeZone)
BuildRequires: perl(Digest::SHA1)
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(LWP::UserAgent)
@@ -21,6 +22,7 @@ BuildRequires: perl(XML::LibXML) = 1.69
BuildRequires: perl(XML::XPath)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# not automatically detected
+Requires: perl(DateTime::TimeZone)
Requires: perl(URI)
Requires: perl(XML::LibXML) = 1.69
Requires: perl(XML::XPath)
@@ -56,6 +58,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Sun Oct 23 2011 Iain Arnell iarn...@gmail.com 0.41-1
+- update to latest upstream version
+
* Wed Jul 20 2011 Petr Sabata con...@redhat.com - 0.39-3
- Perl mass rebuild
diff --git a/sources b/sources
index ca60286..53b77ee 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5537d57f4d8a64022ecf82265e2a0594 XML-Atom-0.39.tar.gz
+99eeebbf90c95cc1a24426a0b9f2d6a5 XML-Atom-0.41.tar.gz
--
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 748130] perl-NetAddr-IP-4.050 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=748130 Paul Howarth p...@city-fan.org changed: What|Removed |Added CC||p...@city-fan.org --- Comment #1 from Paul Howarth p...@city-fan.org 2011-10-23 06:28:55 EDT --- Test suite for 4.050 is failing on x86_64: https://rt.cpan.org/Public/Bug/Display.html?id=71869 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- 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 746941] perl-Mojolicious-2.09 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=746941 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|perl-Mojolicious-2.04 is|perl-Mojolicious-2.09 is |available |available --- Comment #4 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org 2011-10-23 06:43:17 EDT --- Latest upstream release: 2.09 Current version in Fedora Rawhide: 1.99 URL: http://search.cpan.org/dist/Mojolicious/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- 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-Catalyst-Plugin-Session-Store-DBIC
perl-Catalyst-Plugin-Session-Store-DBIC has broken dependencies in the F-16 tree: On x86_64: perl-Catalyst-Plugin-Session-Store-DBIC-0.12-1.fc15.noarch requires perl(:MODULE_COMPAT_5.12.4) On i386: perl-Catalyst-Plugin-Session-Store-DBIC-0.12-1.fc15.noarch requires perl(:MODULE_COMPAT_5.12.4) 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
Broken dependencies: perl-CatalystX-Profile
perl-CatalystX-Profile has broken dependencies in the F-16 tree: On x86_64: perl-CatalystX-Profile-0.02-1.fc15.noarch requires perl(:MODULE_COMPAT_5.12.4) On i386: perl-CatalystX-Profile-0.02-1.fc15.noarch requires perl(:MODULE_COMPAT_5.12.4) 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
Broken dependencies: perl-CatalystX-SimpleLogin
perl-CatalystX-SimpleLogin has broken dependencies in the F-16 tree: On x86_64: perl-CatalystX-SimpleLogin-0.15-2.fc15.noarch requires perl(:MODULE_COMPAT_5.12.4) On i386: perl-CatalystX-SimpleLogin-0.15-2.fc15.noarch requires perl(:MODULE_COMPAT_5.12.4) 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
Broken dependencies: perl-Carp-REPL
perl-Carp-REPL has broken dependencies in the F-16 tree: On x86_64: perl-Carp-REPL-0.15-2.fc15.noarch requires perl(:MODULE_COMPAT_5.12.4) On i386: perl-Carp-REPL-0.15-2.fc15.noarch requires perl(:MODULE_COMPAT_5.12.4) 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
Broken dependencies: perl-Pugs-Compiler-Rule
perl-Pugs-Compiler-Rule has broken dependencies in the F-16 tree: On x86_64: perl-Pugs-Compiler-Rule-0.37-9.fc16.noarch requires perl(:MODULE_COMPAT_5.12.3) On i386: perl-Pugs-Compiler-Rule-0.37-9.fc16.noarch requires perl(:MODULE_COMPAT_5.12.3) 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
Broken dependencies: perl-Text-Aspell
perl-Text-Aspell has broken dependencies in the F-16 tree: On x86_64: perl-Text-Aspell-0.09-9.fc15.x86_64 requires perl(:MODULE_COMPAT_5.12.3) On i386: perl-Text-Aspell-0.09-9.fc15.i686 requires perl(:MODULE_COMPAT_5.12.3) 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
