RE: New pkg SCM approval
Christopher Meng wrote on 2013-06-03: > SCM will be ready in a few hours, don't hurry. > > BTW a note, I hope you can change some items in the SCM comment. > > Description of yours: "package for OpenAttestation project" > > However I think it should be "Attestation Service & Host Agent based > on OpenAttestation SDK", yours seems not good. > > And no need for InitialCC: gwei3, you are the owner... Thanks for correcting me on the SCM request, I will update it soon. Jimmy smime.p7s Description: S/MIME cryptographic signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New pkg SCM approval
SCM will be ready in a few hours, don't hurry. BTW a note, I hope you can change some items in the SCM comment. Description of yours: "package for OpenAttestation project" However I think it should be "Attestation Service & Host Agent based on OpenAttestation SDK", yours seems not good. And no need for InitialCC: gwei3, you are the owner... Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] 2013-06-03 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2013-06-03 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! It's meeting time again today/tomorrow! Not a lot of new business, so I thought about cancelling, but we have a lot of action items to check in on so we'd best go through that list and take a quick look at F19 Final status and test days. This is a reminder of the upcoming QA meeting. Please add any topic suggestions to the meeting wiki page: https://fedoraproject.org/wiki/QA/Meetings/20130603 The current proposed agenda is included below. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 19 Final planning 3. Test Days 4. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
New pkg SCM approval
How long will it usually take to get the approval for a New Package SCM Request? And is it true that the package SCM requests will only be touched in working days? I just got a new package[1] pass review in last Friday afternoon US time but the SCM request has not been handled by far. Just curious, and want to see anyone have an answer or be able to share some experience. [1] https://bugzilla.redhat.com/show_bug.cgi?id=915864 Thanks Jimmy smime.p7s Description: S/MIME cryptographic signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging alien, debhelper and po-debconf
On 06/02/2013 03:56 PM, Sérgio Basto wrote: > it is possible use Chained_builds ? > https://fedoraproject.org/wiki/Using_the_Koji_build_system#Chained_builds > https://fedoraproject.org/wiki/Bodhi/BuildRootOverrides Chained builds only work in rawhide, but you can manually do the override tags for successful builds in the other branches, wait for the builder repodata to regenerate, then, kick off the next build in sequence. ~tom == Fedora Project -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora Hosted Usability and Developer Experience
Stephen John Smoogen wrote: > Actually I was going to ask the opposite question: Do we still need > FedoraHosted? I have found it a valuable service to provide an upstream home for fedora- specific projects. -- Rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora Hosted Usability and Developer Experience
HI On Sun, Jun 2, 2013 at 5:52 PM, seth vidal wrote: > > > I actually disagree with that. > > I think freedom of the service does matter. The debacles with google > reader and google talk recently should be pointing that up to all of > us. While DVCS do remove the possibility of our code getting locked up > somewhere it doesn't help us much if our entire workflow is locked up > there. > Personally, I value that advantage and have advocated for free infrastructure and emphasized that while setting up Ask Fedora etc but the question really is, is that enough of an advantage on its own to continue investing in maintaining fedorahosted? I don't think so. It is very clear that majority of open source developers are just fine with using github for hosting their code and if you really want to provide a compelling alternative, you need to compete in ease of use, features etc. If fedorahosted was the only reliable service that is using free software, I see a point in continuing with it but otherwise, what is the value of it over sf.net (which now develops and uses https://incubator.apache.org/projects/allura.html), gnu savannah, javaforge etc? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora Hosted Usability and Developer Experience
On Sun, 2 Jun 2013 16:39:20 -0400 Rahul Sundaram wrote: > Hi > > > On Fri, May 31, 2013 at 6:45 PM, Stephen John Smoogen wrote: > > > > > Actually I was going to ask the opposite question: Do we still need > > FedoraHosted? It was created before there was GitHub or Gitorious > > but frankly we are not funded or staffed to make it bigger and > > better than it is now. The systems are 2 virtual machines with one > > as primary and one as fallback. It is not a large set of systems > > and is made on the backbone of compromises of "We won't use > > FedoraHosted unless you support X VCS system"... none of the things > > that Github or Gitorious or even Savannah has had to deal with :). > > > > Yeah. Unless Fedora is going to invest in FedoraHosted and make it a > excellent platform for projects, there isn't really much need to keep > it at this point. There is no particular advantage to it over Google > Code or sf.net or github. The underlying platform being free > software isn't enough of an distinction when using distributed vcs. I actually disagree with that. I think freedom of the service does matter. The debacles with google reader and google talk recently should be pointing that up to all of us. While DVCS do remove the possibility of our code getting locked up somewhere it doesn't help us much if our entire workflow is locked up there. For example github's pull-request workflow is very nice for projects with a wide contributor base but it is hard to move away from once you are used to it. When I looked at other options to github I was looking for a similar or comparable workflow and I struggled to find any: - gitorious merge-request is a extremely cumbersome currently - gitlab has(had?) no such concept of public repositories so the idea of someone forking and contributing a patch was not even in the system I think the folks running/writing github are good folks with the right motivations but I've found that a lot of people with the right motivations end up getting weird when money gets tight. It is best not to be in a position where you have to find out about that. So - freedom of infrastructure matters - if for no other reason than making sure that anyone who wants to copy and walk away with their code/issues/tickets/wiki can do so w/o needing to buy any software (or worse yet software they CANNOT buy) I agree with smooge that we're understaffed to make the service everything it could be - but there are places we can be in between and we've made changes recently to make it easier for us to try out solutions w/o impacting every project. -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora Hosted Usability and Developer Experience
Hi On Fri, May 31, 2013 at 6:45 PM, Stephen John Smoogen wrote: > > Actually I was going to ask the opposite question: Do we still need > FedoraHosted? It was created before there was GitHub or Gitorious but > frankly we are not funded or staffed to make it bigger and better than it > is now. The systems are 2 virtual machines with one as primary and one as > fallback. It is not a large set of systems and is made on the backbone of > compromises of "We won't use FedoraHosted unless you support X VCS > system"... none of the things that Github or Gitorious or even Savannah has > had to deal with :). > > Yeah. Unless Fedora is going to invest in FedoraHosted and make it a excellent platform for projects, there isn't really much need to keep it at this point. There is no particular advantage to it over Google Code or sf.net or github. The underlying platform being free software isn't enough of an distinction when using distributed vcs. Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging alien, debhelper and po-debconf
On Ter, 2013-05-07 at 14:07 +0300, Oron Peled wrote: > On Wednesday 01 May 2013 22:21:20 Richard W.M. Jones wrote: > > On Wed, May 01, 2013 at 03:00:34AM +0100, Sérgio Basto wrote: > > > https://bugzilla.redhat.com/show_bug.cgi?id=591190 > > I'm prepared to take debhelper. But: > > (1) It looks like the latest package is over 1 year old. I think a > > newer package should be presented (in this bug or in a newly opened > > one). > > (2) Can debhelper be used to make .deb's on a Fedora host? If it > > works, that would currently be very interesting to me. > > I'll start with (2): > * I can build .deb's on Fedora using pbuilder/pdebuild. > > * Here is the tree of RR for making it work: >https://bugzilla.redhat.com/showdependencytree.cgi?id=591388 > > * Credit goes to Jeroen van Meeuwen. I just joined to help move it forward > [ with very little success so far, mind you :-( ] > > * And yes, I think it makes Fedora a better development platform if you can > use it to build both rpm's and deb's (on Debian, you can do both). > > Now to (1)... Ouch: > * The stalling of po-debconf is my fault, but see today's update to > rhbz#591389 >(I'm fixing my ways...) > > * If we resolve it quickly, the next is debhelper (rhbz#591190). IMO the main >blocker there is finding someone committed to review (I'm willing to > maintain it). >There's another problem in the chain (dpkg too old), but hopefully it will >be OK soon (maintainer updated today the BR and said he would fix it RSN) > > * I uploaded a temporary pbuilder SRPM: > http://oron.fedorapeople.org/deb-package/pbuilder-0.213-1.fc18.src.rpm >- It's up-to-date (Debian/wheezy) >- But I didn't have time to clean it up for review. Hope to do this in the > next > few days and update the RR. > > So maybe we finally have a chance to move this along before the > dedicated bug zappers would zap it (no criticism -- they work > hard to clean the mess we leave behind us). > > Unrelated note: > * I've been using schroot(1) a lot in the last years on both Debian/Fedora to > maintain multiple clean build environments of different OS. > * However, one of the most useful features -- snapshots via LVM -- is not > usable in Fedora due to rhbz#600636 > * That bug-report is stalled since 2010, and exactly a year passed since > I sent a tested patch... > > OK, back to work now. Hi, I'm going , if no problem, begin F18 cycle build this 7 packages: dpkg debconf po-debconf debhelper alien dh-make pbuilder 1st build dpkg and debconf after build po-debconf (depends on debconf) after build debhelper ( depends on dpkg and po-debconf ) after build alien (depends on debhelper) and dh-make (depends on debhelper ) after review and build pbuilder (depends on dh-make, debhelper and po-debconf ) it is possible use Chained_builds ? https://fedoraproject.org/wiki/Using_the_Koji_build_system#Chained_builds https://fedoraproject.org/wiki/Bodhi/BuildRootOverrides Thanks, -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Co-maintainer request
Hello packagers! Is there anyone with enough interest in Audacious (packages audacious*) as to help out as a co-maintainer? Then please sign up via pkgdb. I'm facing a serious lack of time due to house'n'roof renovation and accompanying things to do, and I cannot keep up with Fedora "duties" for a few weeks at least. Kind regards, -- mschwendt Fedora release 19 (Schrödinger’s Cat) - Linux 3.9.4-300.fc19.x86_64 loadavg: 0.09 0.09 0.06 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-19 Branched report: 20130602 changes
Compose started at Sun Jun 2 09:15:02 UTC 2013 Broken deps for x86_64 -- [bochs] bochs-2.6.1-1.fc19.x86_64 requires vgabios [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 [gcc-python-plugin] gcc-python2-debug-plugin-0.12-1.fc19.x86_64 requires gcc = 0:4.8.0-2.fc19 gcc-python2-plugin-0.12-1.fc19.x86_64 requires gcc = 0:4.8.0-2.fc19 gcc-python3-debug-plugin-0.12-1.fc19.x86_64 requires gcc = 0:4.8.0-2.fc19 gcc-python3-plugin-0.12-1.fc19.x86_64 requires gcc = 0:4.8.0-2.fc19 [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.x86_64 requires servlet25 [koji] koji-vm-1.8.0-1.fc19.noarch requires python-virtinst [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 [libreatlas] libreatlas-1.0.0a-3.fc19.x86_64 requires librasterlite.so.0()(64bit) [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 [ovirt-guest-agent] ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.x86_64 requires libgdmsimplegreeter.so.1()(64bit) [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.fc19.noarch requires python = 0:2.7.4 [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) [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 -- [bochs] bochs-2.6.1-1.fc19.i686 requires vgabios [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 [gcc-python-plugin] gcc-python2-debug-plugin-0.12-1.fc19.i686 requires gcc = 0:4.8.0-2.fc19 gcc-python2-plugin-0.12-1.fc19.i686 requires gcc = 0:4.8.0-2.fc19 gcc-python3-debug-plugin-0.12-1.fc19.i686 requires gcc = 0:4.8.0-2.fc19 gcc-python3-plugin-0.12-1.fc19.i686 requires gcc = 0:4.8.0-2.fc19 [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.i686 requires servlet25 [koji] koji-vm-1.8.0-1.fc19.noarch requires python-virtinst [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 [libreatlas] libreatlas-1.0.0a-3.fc19.i686 requires librasterlite.so.0 [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 [ovirt-guest-agent] ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.i686 requires libgdmsimplegreeter.so.1 [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) perl-Bio-SamTools-1.35-2.fc19.i686 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.fc19.noarch requires python = 0:2.7.4 [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) [zarafa] php-mapi-7.0.13-1.fc19.i686 requires php(zend-abi) = 0:20100525-x86-32 php-mapi-7.0.13-1.fc19.i686 requires php(api) = 0:20100412-x86-32 New package: NetworkManager-ssh-0.0.3-0.8.20130419git3d5321b.fc19 NetworkManager VPN plugin for SSH New package: funguloids-1.06-1.fc19 Sp
Re: Software Management call for RFEs
I'd like a tool similar to portaudit in FreeBSD or debscan in Debian. This tool should list all packages which have a security issue. Currently there is yum-security-plugin but it lists packages only if an update is available. The new tool would list vulnerable packages even if no update is available yet, so that the user can take precaution. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20130602 changes
Compose started at Sun Jun 2 08:15:03 UTC 2013 Broken deps for x86_64 -- [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) [entangle] entangle-0.5.1-2.fc20.x86_64 requires libraw.so.5()(64bit) [evas-generic-loaders] evas-generic-loaders-1.7.6-1.fc20.x86_64 requires libraw.so.5()(64bit) [gambas3] gambas3-gb-jit-3.4.1-3.fc20.x86_64 requires libLLVM-3.3svn.so()(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 [kdeedu] kdeedu-4.10.4-1.fc20.noarch requires kanagram >= 0:4.10.4 [kdegraphics] 7:kdegraphics-4.10.4-1.fc20.noarch requires gwenview >= 0:4.10.4 [kdeutils] 6:kdeutils-minimal-4.10.4-1.fc20.noarch requires ark >= 0:4.10.4 [koji] koji-vm-1.8.0-1.fc20.noarch requires python-virtinst [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 [luminance-hdr] luminance-hdr-2.3.0-6.fc19.x86_64 requires libraw_r.so.5()(64bit) [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 [nomacs] nomacs-1.0.2-3.fc20.x86_64 requires libraw.so.5()(64bit) [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 [ovirt-guest-agent] ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.x86_64 requires libgdmsimplegreeter.so.1()(64bit) [oyranos] oyranos-libs-0.4.0-7.fc19.i686 requires libraw.so.5 oyranos-libs-0.4.0-7.fc19.x86_64 requires libraw.so.5()(64bit) [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) [postgresql-plparrot] postgresql-plparrot-0.05-4.fc19.x86_64 requires libparrot.so.5.0.0()(64bit) [python-TraitsBackendQt] python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI [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) [scala] scala-2.9.2-2.fc19.noarch requires osgi(org.scala-ide.scala.library) [shotwell] shotwell-0.14.1-2.fc20.x86_64 requires libraw.so.5()(64bit) [spacewalk-web] spacewalk-dobby-1.9.22-2.fc19.noarch requires perl(Spacewalk::Setup) [spring] spring-94.1-1.fc20.x86_64 requires libassimp.so.2()(64bit) [tex-simplecv] tex-simplecv-doc-1.6-12.fc19.noarch requires texlive-texmf-doc [texlive] 2:texlive-convbkmk-bin-svn30408.0-23.20130523_r30652.fc20.noarch requires tex-convbkmk 2:texlive-texdiff-bin-svn15506.0-23.20130523_r30652.fc20.noarch requires tex-texdiff [zarafa] libmapi-7.0.13-1.fc19.i686 requires libicalss.so.0 libmapi-7.0.13-1.fc19.i686 requires libical.so.0 libmapi-7.0.13-1.fc19.x86_64 requires libicalss.so.0()(64bit) libmapi-7.0.13-1.fc19.x86_64 requires libical.so.0()(64bit) 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 zarafa-ical-7.0.13-1.fc19.x86_64 requires libicalss.so.0()(64bit) zarafa-ical-7.0.13-1.fc19.x86_64 requires libical.so.0()(64bit) Broken deps for i386 -- [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 [entangle] entangle-0.5.1-2.fc20.i686 requires libraw.so.5 [evas-generic-loaders] evas-generic-loaders-1.7.6-1.fc20.i686 requires libraw.so.5 [gambas3] gambas3-gb-jit-3.4.1-3.fc20.i686 requires libLLVM-3.3svn.so [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.i686 requires servlet25 [kdeedu] kdeedu-4.10.4-1.fc20.noarch requires kanagram >= 0:4.10.4 [kdegraphics] 7:kdegraphics-4.10.4-1.fc20.noarch requires gwenview >= 0:4.10.4 [kdeutils] 6:kdeutils-minimal-4.10.4-1.fc20.noarch requires ark >= 0:4.10.4 [koji] koji-vm-1.8.0-1.fc20.noarch requires python-virtinst [
