Re: Review Swap with 3 packages
Hi all, Now upstream has released the latest version which should all problems. Please, consider a review help. Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: anaconda / initial-setup / gnome-initial-setup: can we do this better?
On Fri, May 17, 2013 at 02:44:25PM -0700, Adam Williamson wrote: Thinking about it more, this really seems to be the way to go. Forcing user creation in anaconda is a problem for someone who wants to do a minimal install with no user account. Doing the above would reduce the paths to something manageable without compromising any existing use cases. Who'd want to do a minimal install and not create an account? (And wouldn't be doing that using a kickstart or another specialized install method?) Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: when startup delays become bugs (dmraid)
Le Sam 18 mai 2013 05:39, T.C. Hollingsworth a écrit : On Fri, May 17, 2013 at 7:34 PM, Adam Williamson awill...@redhat.com wrote: You could transfer the install to a system which contains a dmraid array, or add a dmraid array to an existing install (I think this thread has been considering only the case of the installed system itself being on the RAID array). Of course, the case where the installed system is not on the RAID array is much less 'urgent' - your system doesn't stop working, you just have to figure out you need to enable the service / install the tool in order to see the array. Yeah, but you'd need to do some manual configuration there anyway. Adding `yum install dmraid` to that isn't really a massive burden. That's really a terrible argument. It's why you get so many one thousand paper cut moments in IT nowadays. -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Does -devel package name only indicate C development packages?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 https://bugzilla.redhat.com/show_bug.cgi?id=962081 I have a request to change the name of selinux-policy-devel to selinux-policy-devel-support, since everywhere else in the distro -devel means just header files in c and not any other development tools and we have several scripts that assume that's the case. selinux-policy-devel contains interface files and tools required to build selinux-policy. It also currently contains the man pages, which I can move to the base package. selinux-policy-devel has existed I believe since at least Fedora 5, and is fairly well known as a package (Google Knowledge) I hesitate to change the name of this package, but if Fedora Packaging guidelines or consensus requires it, I will. * Tue Jun 20 2006 Dan Walsh dwa...@redhat.com 2.2.47-5 - - Break out selinux-devel package -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGXVYEACgkQrlYvE4MpobPI8gCfYXKHCKIZVaz0U2E4BiIn1EUg G7EAn262mtJpxJVfL1VLucOx/1q9LDSF =xf9a -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
On Sat, May 18, 2013 at 06:18:41AM -0400, Daniel J Walsh wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 https://bugzilla.redhat.com/show_bug.cgi?id=962081 I have a request to change the name of selinux-policy-devel to selinux-policy-devel-support, since everywhere else in the distro -devel means just header files in c and not any other development tools and we have several scripts that assume that's the case. That's some strange interpretation. I completly don't agree with that. selinux-policy-devel contains interface files and tools required to build selinux-policy. It also currently contains the man pages, which I can move to the base package. That seems like a perfect description for what -devel is. For normal usage selinux-policy is required. For building and modification – -devel package. Seems completely intuitive for me. About assumptions: does ‘rpmlint selinux-policy.spec‘ complains? -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
I agree with Tomasz. -devel has always means files and data necessary to support use as a build dependency to me. That's a superset of C header files. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
Hi, 2013/5/18 Tomasz Torcz to...@pipebreaker.pl On Sat, May 18, 2013 at 06:18:41AM -0400, Daniel J Walsh wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 https://bugzilla.redhat.com/show_bug.cgi?id=962081 I have a request to change the name of selinux-policy-devel to selinux-policy-devel-support, since everywhere else in the distro -devel means just header files in c and not any other development tools and we have several scripts that assume that's the case. That's some strange interpretation. I completly don't agree with that. selinux-policy-devel contains interface files and tools required to build selinux-policy. It also currently contains the man pages, which I can move to the base package. That seems like a perfect description for what -devel is. For normal usage selinux-policy is required. For building and modification – -devel package. Seems completely intuitive for me. Agree. I wonder if -devel means just header files in c applies to c++ headers as well? About assumptions: does ‘rpmlint selinux-policy.spec‘ complains? -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best regards, Michal http://eventhorizon.pl/ https://getactive.pl/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
On Sat, May 18, 2013 at 06:18:41AM -0400, Daniel J Walsh wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 https://bugzilla.redhat.com/show_bug.cgi?id=962081 I have a request to change the name of selinux-policy-devel to selinux-policy-devel-support, since everywhere else in the distro -devel means just header files in c and not any other development tools and we have several scripts that assume that's the case. OCaml development packages are called ocaml-*-devel. Example: http://koji.fedoraproject.org/koji/rpminfo?rpmID=3740331 Note that *.mli files are kind of equivalent to C header files. But I'd agree with you that anything needed for development (that term interpreted broadly) and not for use could go in a -devel package. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
Le Sam 18 mai 2013 12:35, Tomasz Torcz a écrit : That seems like a perfect description for what -devel is. For normal usage selinux-policy is required. For building and modification – -devel package. Actually, if modification and building can be dissociated, it'd be nice to keep -devel for building and split the rest in -tools -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/18/2013 06:37 AM, David Strauss wrote: I agree with Tomasz. -devel has always means files and data necessary to support use as a build dependency to me. That's a superset of C header files. Well if you were building policy in out spec file, you would need the Makefile and interface files for your policy to compile. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGXa1wACgkQrlYvE4MpobN3LACggRN4+TWRhdjre86FGrEBGEdV pQsAnRizYFQegR6VewHPQuzsrLhaOt3b =F3/d -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20130518 changes
Compose started at Sat May 18 08:15:03 UTC 2013 Broken deps for x86_64 -- [claws-mail-plugins] claws-mail-plugins-geolocation-3.9.0-7.fc20.x86_64 requires claws-mail(plugin-api)(x86-64) = 0:3.9.0.122 [dragonegg] dragonegg-3.1-19.fc19.x86_64 requires gcc = 0:4.7.2-9.fc19 [ekiga] ekiga-4.0.1-1.fc19.x86_64 requires libedata-book-1.2.so.17()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.12-3.fc20.x86_64 requires gcc = 0:4.8.0-5.fc20 gcc-python2-plugin-0.12-3.fc20.x86_64 requires gcc = 0:4.8.0-5.fc20 gcc-python3-debug-plugin-0.12-3.fc20.x86_64 requires gcc = 0:4.8.0-5.fc20 gcc-python3-plugin-0.12-3.fc20.x86_64 requires gcc = 0:4.8.0-5.fc20 [gdl] gdl-0.9.3-6.cvs20130321.fc20.x86_64 requires libhdf5.so.7()(64bit) gdl-0.9.3-6.cvs20130321.fc20.x86_64 requires hdf5 = 0:1.8.10 gdl-python-0.9.3-6.cvs20130321.fc20.x86_64 requires libhdf5.so.7()(64bit) [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.x86_64 requires servlet25 [lancet] lancet-1.0.1-6.fc19.noarch requires ant-nodeps = 0:1.7.1 [lua-logging] lua-logging-1.3.0-1.fc20.noarch requires lua = 0:5.2 [lua-rex] lua-rex-2.7.2-1.fc20.x86_64 requires lua = 0:5.2 [luadoc] luadoc-3.0.1-8.fc20.noarch requires lua = 0:5.2 [lutok] lutok-devel-0.2-4.fc19.i686 requires lua-devel 0:5.2 lutok-devel-0.2-4.fc19.x86_64 requires lua-devel 0:5.2 [mapserver] php-mapserver-6.0.3-9.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-mapserver-6.0.3-9.fc19.x86_64 requires php(api) = 0:20100412-x86-64 [ooo2gd] ooo2gd-3.0.0-6.fc19.x86_64 requires gdata-java [openbox] gdm-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel gnome-panel-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [perl-Bio-ASN1-EntrezGene] perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) [perl-Bio-SamTools] perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) [python-TraitsBackendQt] python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI [python-docs] python-docs-2.7.4-1.fc20.noarch requires python = 0:2.7.4 [python-flask-admin] python-flask-admin-1.0.5-3.fc20.noarch requires python-wtf-peewee [qpid-cpp] qpid-cpp-server-xml-0.20-6.fc20.x86_64 requires libxqilla.so.5()(64bit) [rrdtool] rrdtool-lua-1.4.7-16.fc20.x86_64 requires lua = 0:5.2 [scala] scala-2.9.2-2.fc19.noarch requires osgi(org.scala-ide.scala.library) [spacewalk-web] spacewalk-dobby-1.9.22-2.fc19.noarch requires perl(Spacewalk::Setup) [syncevolution] 1:syncevolution-libs-1.3.99.3-1.fc20.i686 requires libedata-book-1.2.so.17 1:syncevolution-libs-1.3.99.3-1.fc20.x86_64 requires libedata-book-1.2.so.17()(64bit) [zarafa] php-mapi-7.0.13-1.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-mapi-7.0.13-1.fc19.x86_64 requires php(api) = 0:20100412-x86-64 Broken deps for i386 -- [claws-mail-plugins] claws-mail-plugins-geolocation-3.9.0-7.fc20.i686 requires claws-mail(plugin-api)(x86-32) = 0:3.9.0.122 [dragonegg] dragonegg-3.1-19.fc19.i686 requires gcc = 0:4.7.2-9.fc19 [ekiga] ekiga-4.0.1-1.fc19.i686 requires libedata-book-1.2.so.17 [gcc-python-plugin] gcc-python2-debug-plugin-0.12-3.fc20.i686 requires gcc = 0:4.8.0-5.fc20 gcc-python2-plugin-0.12-3.fc20.i686 requires gcc = 0:4.8.0-5.fc20 gcc-python3-debug-plugin-0.12-3.fc20.i686 requires gcc = 0:4.8.0-5.fc20 gcc-python3-plugin-0.12-3.fc20.i686 requires gcc = 0:4.8.0-5.fc20 [gdl] gdl-0.9.3-6.cvs20130321.fc20.i686 requires libhdf5.so.7 gdl-0.9.3-6.cvs20130321.fc20.i686 requires hdf5 = 0:1.8.10 gdl-python-0.9.3-6.cvs20130321.fc20.i686 requires libhdf5.so.7 [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.i686 requires servlet25 [lancet] lancet-1.0.1-6.fc19.noarch requires ant-nodeps = 0:1.7.1 [lua-logging] lua-logging-1.3.0-1.fc20.noarch requires lua = 0:5.2 [lua-rex] lua-rex-2.7.2-1.fc20.i686 requires lua = 0:5.2 [luadoc] luadoc-3.0.1-8.fc20.noarch requires lua = 0:5.2 [lutok] lutok-devel-0.2-4.fc19.i686 requires lua-devel 0:5.2 [mapserver] php-mapserver-6.0.3-9.fc19.i686 requires php(zend-abi) = 0:20100525-x86-32 php-mapserver-6.0.3-9.fc19.i686 requires php(api) = 0:20100412-x86-32 [ooo2gd] ooo2gd-3.0.0-6.fc19.i686 requires gdata-java [openbox]
F-19 Branched report: 20130518 changes
Compose started at Sat May 18 09:15:02 UTC 2013 Broken deps for x86_64 -- [byzanz] byzanz-0.3-0.5.fc17.x86_64 requires libpanel-applet-4.so.0()(64bit) [deltacloud-core] deltacloud-core-rhevm-1.1.3-1.fc19.noarch requires rubygem(rbovirt) = 0:0.0.18 [dragonegg] dragonegg-3.1-19.fc19.x86_64 requires gcc = 0:4.7.2-9.fc19 [fence-virt] fence-virtd-libvirt-qmf-0.3.0-11.fc19.x86_64 requires libvirt-qmf [freeipa] freeipa-server-strict-3.2.0-0.3.beta1.fc19.x86_64 requires pki-ca = 0:10.0.1 freeipa-server-strict-3.2.0-0.3.beta1.fc19.x86_64 requires krb5-server = 0:1.11.2-1 freeipa-server-strict-3.2.0-0.3.beta1.fc19.x86_64 requires 389-ds-base = 0:1.3.0.5 [glusterfs] glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift-proxy = 0:1.8.0 glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift-object = 0:1.8.0 glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift-container = 0:1.8.0 glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift-account = 0:1.8.0 glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift = 0:1.8.0 [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.x86_64 requires servlet25 [libkolab] php-kolab-0.4.1-3.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-kolab-0.4.1-3.fc19.x86_64 requires php(api) = 0:20100412-x86-64 [ooo2gd] ooo2gd-3.0.0-6.fc19.x86_64 requires gdata-java [openbox] gdm-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel gnome-panel-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [perl-Bio-ASN1-EntrezGene] perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) [perl-Bio-SamTools] perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) [python-AppTools] python-AppTools-3.4.0-5.fc19.noarch requires python-TraitsGUI [python-TraitsBackendQt] python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI [python-flask-admin] python-flask-admin-1.0.5-2.fc19.noarch requires python-flask-mongonegine [scala] scala-2.9.2-2.fc19.noarch requires osgi(org.scala-ide.scala.library) [spacewalk-web] spacewalk-dobby-1.9.22-2.fc19.noarch requires perl(Spacewalk::Setup) [tntnet] tntnet-2.1-15.fc19.i686 requires libcxxtools.so.8 tntnet-2.1-15.fc19.x86_64 requires libcxxtools.so.8()(64bit) [zarafa] php-mapi-7.0.13-1.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-mapi-7.0.13-1.fc19.x86_64 requires php(api) = 0:20100412-x86-64 Broken deps for i386 -- [byzanz] byzanz-0.3-0.5.fc17.i686 requires libpanel-applet-4.so.0 [deltacloud-core] deltacloud-core-rhevm-1.1.3-1.fc19.noarch requires rubygem(rbovirt) = 0:0.0.18 [dragonegg] dragonegg-3.1-19.fc19.i686 requires gcc = 0:4.7.2-9.fc19 [fence-virt] fence-virtd-libvirt-qmf-0.3.0-11.fc19.i686 requires libvirt-qmf [freeipa] freeipa-server-strict-3.2.0-0.3.beta1.fc19.i686 requires pki-ca = 0:10.0.1 freeipa-server-strict-3.2.0-0.3.beta1.fc19.i686 requires krb5-server = 0:1.11.2-1 freeipa-server-strict-3.2.0-0.3.beta1.fc19.i686 requires 389-ds-base = 0:1.3.0.5 [glusterfs] glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift-proxy = 0:1.8.0 glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift-object = 0:1.8.0 glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift-container = 0:1.8.0 glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift-account = 0:1.8.0 glusterfs-ufo-3.4.0-0.4.beta1.fc19.noarch requires openstack-swift = 0:1.8.0 [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.i686 requires servlet25 [libkolab] php-kolab-0.4.1-3.fc19.i686 requires php(zend-abi) = 0:20100525-x86-32 php-kolab-0.4.1-3.fc19.i686 requires php(api) = 0:20100412-x86-32 [ooo2gd] ooo2gd-3.0.0-6.fc19.i686 requires gdata-java [openbox] gdm-control-3.5.0-11.20121001git782b28.fc19.i686 requires gnome-panel gnome-panel-control-3.5.0-11.20121001git782b28.fc19.i686 requires gnome-panel [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [perl-Bio-ASN1-EntrezGene] perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) [perl-Bio-SamTools] perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::SeqFeature::Lite)
Review request: mingw-portmidi (and a lot more to come)
Hello all! I'm trying to learn how to submit packages to Fedora...there's a lot to read! But I build packages locally all the time, and it seems like a shame that they don't go any further than that. So I'm trying to take it to the next level. (I'm already loving http://koji.fedoraproject.org/koji/ -- how awesome is it that I can test builds on versions of Fedora Core I don't have installed?) My first task is to submit all the dependencies that it takes to build Mixxx (an open-source DJing program, see http://www.mixxx.org/ for more info) under MinGW. (I'm also currently trying to get the latest Linux version of mixxx into RPMFusion.) All but one of the dependencies are of packages whose non-MinGW versions are already in the Fedora repos, so I necessarily have to submit packages to you. The first one is mingw-portmidi; see https://bugzilla.redhat.com/show_bug.cgi?id=964437 for more info. I understand that I have to review other people's packages in order to gain cred, so I'm off to do that :-) Steven Boswell -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: when startup delays become bugs (dmraid)
Am 18.05.2013 11:17, schrieb Nicolas Mailhot: Le Sam 18 mai 2013 05:39, T.C. Hollingsworth a écrit : On Fri, May 17, 2013 at 7:34 PM, Adam Williamson awill...@redhat.com wrote: You could transfer the install to a system which contains a dmraid array, or add a dmraid array to an existing install (I think this thread has been considering only the case of the installed system itself being on the RAID array). Of course, the case where the installed system is not on the RAID array is much less 'urgent' - your system doesn't stop working, you just have to figure out you need to enable the service / install the tool in order to see the array. Yeah, but you'd need to do some manual configuration there anyway. Adding `yum install dmraid` to that isn't really a massive burden. That's really a terrible argument. It's why you get so many one thousand paper cut moments in IT nowadays to it is a *very good argument* nobody needs *everything and all* in a *core setup* and i get my paper cut moments where people trying to make defaults and core setups idiot proof which will *never* success signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
On Sat, 2013-05-18 at 06:18 -0400, Daniel J Walsh wrote: https://bugzilla.redhat.com/show_bug.cgi?id=962081 I have a request to change the name of selinux-policy-devel to selinux-policy-devel-support, since everywhere else in the distro -devel means just header files in c and not any other development tools and we have several scripts that assume that's the case. selinux-policy-devel contains interface files and tools required to build selinux-policy. It also currently contains the man pages, which I can move to the base package. Well, there may have been some signals crossed somewhere. I've been part of the discussion about reducing the size of the desktop spin. selinux-policy-devel doesn't look bad to me, the one that looks like a problem is policycoreutils-devel : The policycoreutils-devel package contains the management tools use to develop policy in an SELinux environment. Now *that* is a non-standard interpretation of the -devel suffix. And policycoreutils-devel requires selinux-policy-devel - a package of 'runtime' stuff depending on a package of 'build time' stuff - and various 'runtime' packages depend on policycoreutils-devel, notably the SELinux troubleshooting thing, because policycoreutils-devel contains audit2allow. That's the thicket we are trying to unpick, I believe. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: anaconda / initial-setup / gnome-initial-setup: can we do this better?
On Sat, 2013-05-18 at 09:30 +0100, Richard W.M. Jones wrote: On Fri, May 17, 2013 at 02:44:25PM -0700, Adam Williamson wrote: Thinking about it more, this really seems to be the way to go. Forcing user creation in anaconda is a problem for someone who wants to do a minimal install with no user account. Doing the above would reduce the paths to something manageable without compromising any existing use cases. Who'd want to do a minimal install and not create an account? (And wouldn't be doing that using a kickstart or another specialized install method?) Prior to F19 it was what happened by default: there was no user creation in anaconda, and no CLI firstboot in Fedora (for a while there was one but it didn't offer user creation); so on a minimal install you only had to set a root password and you wound up with a system with just the root user. As I mentioned in my initial post, the Law of Xkcd informs us that if we change this so that user creation is mandatory, it will *inevitably* piss someone off. Having said that, I personally wouldn't mind doing it and facing down the inevitable flamewar, but hey. Cutting i-s down to size seems a more conservative and almost equally beneficial option. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
On Sat, May 18, 2013 at 10:12:52AM -0700, Adam Williamson wrote: On Sat, 2013-05-18 at 06:18 -0400, Daniel J Walsh wrote: https://bugzilla.redhat.com/show_bug.cgi?id=962081 I have a request to change the name of selinux-policy-devel to selinux-policy-devel-support, since everywhere else in the distro -devel means just header files in c and not any other development tools and we have several scripts that assume that's the case. selinux-policy-devel contains interface files and tools required to build selinux-policy. It also currently contains the man pages, which I can move to the base package. Well, there may have been some signals crossed somewhere. I've been part of the discussion about reducing the size of the desktop spin. selinux-policy-devel doesn't look bad to me, the one that looks like a problem is policycoreutils-devel : The policycoreutils-devel package contains the management tools use to develop policy in an SELinux environment. Now *that* is a non-standard interpretation of the -devel suffix. And policycoreutils-devel requires selinux-policy-devel - a package of 'runtime' stuff depending on a package of 'build time' stuff - and various 'runtime' packages depend on policycoreutils-devel, notably the SELinux troubleshooting thing, because policycoreutils-devel contains audit2allow. SELinux *management* often means *building* parts of policy. That's the problem, right? -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
On Sat, 2013-05-18 at 19:22 +0200, Tomasz Torcz wrote: On Sat, May 18, 2013 at 10:12:52AM -0700, Adam Williamson wrote: On Sat, 2013-05-18 at 06:18 -0400, Daniel J Walsh wrote: https://bugzilla.redhat.com/show_bug.cgi?id=962081 I have a request to change the name of selinux-policy-devel to selinux-policy-devel-support, since everywhere else in the distro -devel means just header files in c and not any other development tools and we have several scripts that assume that's the case. selinux-policy-devel contains interface files and tools required to build selinux-policy. It also currently contains the man pages, which I can move to the base package. Well, there may have been some signals crossed somewhere. I've been part of the discussion about reducing the size of the desktop spin. selinux-policy-devel doesn't look bad to me, the one that looks like a problem is policycoreutils-devel : The policycoreutils-devel package contains the management tools use to develop policy in an SELinux environment. Now *that* is a non-standard interpretation of the -devel suffix. And policycoreutils-devel requires selinux-policy-devel - a package of 'runtime' stuff depending on a package of 'build time' stuff - and various 'runtime' packages depend on policycoreutils-devel, notably the SELinux troubleshooting thing, because policycoreutils-devel contains audit2allow. SELinux *management* often means *building* parts of policy. That's the problem, right? Right, exactly. 'developing' SELinux policy is not an act of 'development' like writing code, and it's something we quite actively offer to people at run time - one of the actions the SELinux troubleshooting GUI offers in many AVC cases is 'run audit2allow to generate a policy that will allow this action', for instance, hence its dependency on policycoreutils-devel. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
On 05/18/2013 01:12 PM, Adam Williamson wrote: On Sat, 2013-05-18 at 06:18 -0400, Daniel J Walsh wrote: Well, there may have been some signals crossed somewhere. I've been part of the discussion about reducing the size of the desktop spin. selinux-policy-devel doesn't look bad to me, the one that looks like a problem is policycoreutils-devel Yep. I was thinking of policycoreutils-devel and wrote selinux-policy-devel in the report instead. Sorry for the confusion Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does -devel package name only indicate C development packages?
On Sat, 2013-05-18 at 13:41 -0400, Rahul Sundaram wrote: On 05/18/2013 01:12 PM, Adam Williamson wrote: On Sat, 2013-05-18 at 06:18 -0400, Daniel J Walsh wrote: Well, there may have been some signals crossed somewhere. I've been part of the discussion about reducing the size of the desktop spin. selinux-policy-devel doesn't look bad to me, the one that looks like a problem is policycoreutils-devel Yep. I was thinking of policycoreutils-devel and wrote selinux-policy-devel in the report instead. Sorry for the confusion And to make things clear there - the fact that policycoreutils and policycoreutils-devel are split is not exactly a problem, in fact it's making things better, it's just the nomenclature is off and it seems like the dependency of pcu-devel on selinux-policy-devel is sub-optimal and might be improveable. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Branched wiki page
I just replaced the mess that was the Branched page on the wiki with a new one based on the one I did for Rawhide a while back. https://fedoraproject.org/wiki/Releases/Branched Please edit/improve/etc. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Gnome-shell-extension-weather woes
Hi, So I thought let's get a weather extension to see current weather in my city. Should have been easy like slicing butter, right? It turned out to be crazy disaster!!. 0. I'm using GNOME Shell 3.4.1 on F17 (Beefy Miracle). 1. I do $ yum install gnome-shell-extension-weather. 2. It does not show up in the top panel. So I look around for some option to enable it. I try system settings, no luck. Nowhere do I see option for extensions. 3. On CLI $ gnome-shell- tab, lists gnome-shell-extension-tool I do - $ gnome-shell-extension-tool -e gnome-shell-extension-weather still it does not show up in the top panel. 4. $ gnome-shell-extension-prefs It lists the weather extension, I set preferences for temperature, wind speed units etc. and try to add city: Pune, India. Even after 5 minutes the `Ok' button does not come to life. I have absolutely no idea why. After typing few other random cities, I realise it must have been doing web search for the city I typed, for it shows me list of cities as auto-complete list. 5. I type `Pune, India' again and wait 5 minutes. This time it shows the drop down list with Pune at the top. I select it, but still the `Ok' button does not come to life. No Idea why. So I cancel. 6. Try again, type `Pune, India', wait 5 minutes, select Pune from the list, this time `Ok' wakes up, I click it. The `gnome-shell-extension-prefs' dialogue window has no `ok or apply' button, so I click `X (close)' at the top right corner. But the weather extension does not show up in the top panel. 7. I try: Alt+F2 r Enter, still no luck. 8. I log-out of the gnome-shell, and log-in again: and I'm greeted with the infamous - Oops! Something went wrong!! - message. I try to log-in couple more time, but same message. 9. I un-install `gnome-shell-extension-weather' from text console, and try to log-in, still same message. 10. I plug-out the USB datacard (internet) and try to log-in. It works! 11. I install `gnome-shell-extension-weather', set preferences, and log out. USB internet is on, try to log-in - Oops! Something went wrong!! 12. disconnect internet, try to log-in and it works. 13. Yet, weather extension is nowhere to be seen on the top panel or task bar. :( This is just bad state of affairs and *terrible* user experience @gnome-shell-weather-extension! :( Has anybody tried this extension before? Does it work?? --- Regards -Prasad http://feedmug.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Gnome-shell-extension-weather woes
I don't have a gnome-shell-extension-weather package installed, but I see the weather anyway. My only complaint is that it's showing the sunrise/sunset time according to the hardware-clock time (UTC) instead of my local time. I haven't gotten around to filing a bug about that yet. From: P J P pj.pan...@yahoo.co.in To: devel@lists.fedoraproject.org devel@lists.fedoraproject.org Sent: Saturday, May 18, 2013 2:09 PM Subject: Gnome-shell-extension-weather woes Has anybody tried this extension before? Does it work??-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Gnome-shell-extension-weather woes
On 05/18/2013 05:09 PM, P J P wrote: Hi, So I thought let's get a weather extension to see current weather in my city. Should have been easy like slicing butter, right? It turned out to be crazy disaster!!. Quick notes: * This is a RPM Fusion package https://bugzilla.rpmfusion.org/show_bug.cgi?id=2017 There is a bug report open on a similar problem https://bugzilla.rpmfusion.org/show_bug.cgi?id=2516 Perhaps you can provide the info there. However one quick route is to try https://extensions.gnome.org/extension/613/weather/ Works for me Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Gnome-shell-extension-weather woes
Hello Steven, From: Steven Boswell II ulat...@yahoo.com Subject: Re: Gnome-shell-extension-weather woes I don't have a gnome-shell-extension-weather package installed, but I see the weather anyway. How do you see weather anyway? gnome-shell shows it?? --- Regards -Prasad http://feedmug.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Gnome-shell-extension-weather woes
Hey hi, - Original Message - From: Rahul Sundaram methe...@gmail.com Subject: Re: Gnome-shell-extension-weather woes https://bugzilla.rpmfusion.org/show_bug.cgi?id=2017 https://bugzilla.rpmfusion.org/show_bug.cgi?id=2516 Perhaps you can provide the info there. However one quick route is to try Thanks for the links. I'll post information there. https://extensions.gnome.org/extension/613/weather/ I tried this. On FF it prompts me to install `weather' extension, though I already have it installed. On chromium it says: === You do not appear to have an up to date version of GNOME3. You won't be able to install extensions from here. See the about page for more information. === If I do install from the web-page, where would it install? Is there a way to do uninstall?? Thank you. --- Regards -Prasad http://feedmug.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Gnome-shell-extension-weather woes
Maybe it's because I'm running GNOME3 in fallback mode. I can't stand the new GNOME GUI. For instance, when I upgraded to FC18, nautilus lost its tree view. I grabbed the nautilus source from FC17, rebuilt it, and installed it. Much better. From: P J P pj.pan...@yahoo.co.in To: Steven Boswell II ulat...@yahoo.com; Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Saturday, May 18, 2013 7:21 PM Subject: Re: Gnome-shell-extension-weather woes Hello Steven, From: Steven Boswell II ulat...@yahoo.com Subject: Re: Gnome-shell-extension-weather woes I don't have a gnome-shell-extension-weather package installed, but I see the weather anyway. How do you see weather anyway? gnome-shell shows it?? --- Regards -Prasad http://feedmug.com-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Gnome-shell-extension-weather woes
On 05/18/2013 10:34 PM, P J P wrote: If I do install from the web-page, where would it install? Is there a way to do uninstall?? Thank you. --- Regards-Prasad Follows http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html. By default, in ~.local/share/gnome-shell/extensions Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-Event-Lib] Add patch to fix Segfault
commit 05af753bf783cf20082478d1bf8cb61f7cf5be98
Author: Nicolas Chauvet kwiz...@gmail.com
Date: Sat May 18 10:10:28 2013 +0200
Add patch to fix Segfault
lib-event.patch | 20
perl-Event-Lib.spec |8 +++-
2 files changed, 27 insertions(+), 1 deletions(-)
---
diff --git a/lib-event.patch b/lib-event.patch
new file mode 100644
index 000..4127e43
--- /dev/null
+++ b/lib-event.patch
@@ -0,0 +1,20 @@
+---
+ Lib.xs |2 +-
+ 1 files changed, 1 insertions(+), 1 deletions(-)
+
+diff --git a/Lib.xs b/Lib.xs
+index ac3ae5c..d014744 100644
+--- a/Lib.xs
b/Lib.xs
+@@ -255,7 +255,7 @@ int EVENT_INIT_DONE = -1; /* we use the pid here */
+
+ #define event_do_init() \
+ {\
+-int _pid_ = SvIV(get_sv($, FALSE)); \
++int _pid_ = getpid(); \
+ if (!EVENT_INIT_DONE || EVENT_INIT_DONE != _pid_) {\
+ event_init(); \
+ DEBUG_init_pending(aTHX); \
+--
+1.7.0.4
+
diff --git a/perl-Event-Lib.spec b/perl-Event-Lib.spec
index 81e530e..d557eec 100644
--- a/perl-Event-Lib.spec
+++ b/perl-Event-Lib.spec
@@ -1,12 +1,14 @@
Name: perl-Event-Lib
Version:1.03
-Release:19%{?dist}
+Release:20%{?dist}
Summary:Perl wrapper around libevent
Group: Development/Libraries
License:GPL+ or Artistic
URL:http://search.cpan.org/dist/Event-Lib/
Source0:
http://search.cpan.org/CPAN/authors/id/V/VP/VPARSEVAL/Event-Lib-%{version}.tar.gz
+#https://rt.cpan.org/Public/Bug/Display.html?id=80644
+Patch0:
https://rt.cpan.org/Ticket/Attachment/1136922/598341/lib-event.patch
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildRequires: perl(ExtUtils::MakeMaker)
@@ -26,6 +28,7 @@ received.
%prep
%setup -q -n Event-Lib-%{version}
+%patch0 -p1 -b .orig
%build
@@ -64,6 +67,9 @@ rm -rf $RPM_BUILD_ROOT
%changelog
+* Sat May 18 2013 Nicolas Chauvet kwiz...@gmail.com - 1.03-20
+- Fix segfault with perl 5.16 - rhbz#958361
+
* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.03-19
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
--
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-Event-Lib/f19] Add patch to fix Segfault
Summary of changes: 05af753... Add patch to fix Segfault (*) (*) This commit already existed in another branch; no separate mail sent -- 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-Event-Lib/f18] (2 commits) ...Add patch to fix Segfault
Summary of changes: b07f4c8... - Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass (*) 05af753... Add patch to fix Segfault (*) (*) This commit already existed in another branch; no separate mail sent -- 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 958361] perl -MEvent::Lib gives Segmentation fault
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=958361 --- Comment #2 from Fedora Update System upda...@fedoraproject.org --- perl-Event-Lib-1.03-20.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/perl-Event-Lib-1.03-20.fc19 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Ww7BnS7j0Fa=cc_unsubscribe -- 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 958361] perl -MEvent::Lib gives Segmentation fault
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=958361 --- Comment #3 from Fedora Update System upda...@fedoraproject.org --- perl-Event-Lib-1.03-20.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/perl-Event-Lib-1.03-20.fc18 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aWzzGuY2KTa=cc_unsubscribe -- 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-Bio-ASN1-EntrezGene
perl-Bio-ASN1-EntrezGene has broken dependencies in the rawhide tree: On x86_64: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) On i386: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) 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-Bio-SamTools
perl-Bio-SamTools has broken dependencies in the rawhide tree: On x86_64: perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) On i386: perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::PrimarySeq) 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-Bio-ASN1-EntrezGene
perl-Bio-ASN1-EntrezGene has broken dependencies in the F-19 tree: On x86_64: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) On i386: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) 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-Bio-SamTools
perl-Bio-SamTools has broken dependencies in the F-19 tree: On x86_64: perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) On i386: perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::PrimarySeq) 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
[Bug 960184] Calling dancer with invalid name does not signal failure by exit code
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=960184 --- Comment #6 from Fedora Update System upda...@fedoraproject.org --- perl-Dancer-1.3100-2.fc18 has been pushed to the Fedora 18 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. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Enf1jfUvLNa=cc_unsubscribe -- 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 960445] perl-POE-Component-Client-HTTP-0.948 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=960445 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-POE-Component-Client-HTTP-0.948-1.fc18 has been pushed to the Fedora 18 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. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=IWbI1DwU1Ta=cc_unsubscribe -- 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-Authen-Simple
perl-Authen-Simple has broken dependencies in the epel-6 tree: On ppc64: perl-Authen-Simple-0.4-5.el6.noarch requires perl(Crypt::PasswdMD5) 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-WWW-GoodData
perl-WWW-GoodData has broken dependencies in the epel-5 tree: On ppc: perl-WWW-GoodData-1.6-1.el5.noarch requires perl(Getopt::Long) = 0:2.36 On i386: perl-WWW-GoodData-1.6-1.el5.noarch requires perl(Getopt::Long) = 0:2.36 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-WWW-GoodData
perl-WWW-GoodData has broken dependencies in the epel-5 tree: On ppc: perl-WWW-GoodData-1.6-1.el5.noarch requires perl(Getopt::Long) = 0:2.36 On i386: perl-WWW-GoodData-1.6-1.el5.noarch requires perl(Getopt::Long) = 0:2.36 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
