Ask Your Question
1

golang-libguestfs blocks F20 update

asked 2014-08-10 04:03:23 -0600

updated 2014-09-30 11:12:07 -0600

mether gravatar image

This is an update problem due to a failed dependency. I wasn't sure which package it should be logged against, if at all, because it is more a build system problem, so I didn't use bugzilla. What is the best way of raising issue like that--this forum? devel list? bugzilla?

Anyway, package libguestfs was recently updated from 1.26.5-1.fc20 to 1.26.7-2.fc20 Unfortunately golang-guestfs-1.26.5-1.fc20.noarch has a dependency on libguestfs = 1:1.26.5-1.fc20 and the updates are blocked currently require --skip-broken.

The libguestfs block prevents

libguestfs-tools-1.26.7-2.fc20.noarch

libguestfs-tools-c-1.26.7-2.fc20.x86_64

perl-Sys-Guestfs-1.26.7-2.fc20.x86_64

python-libguestfs-1.26.7-2.fc20.x86_64

edit retag flag offensive close merge delete

Comments

Where did you get golang-guestfs-1.26.5-1.fc20.noarch? That does not seem to be present in one of the official repositories? Try yum distro-sync golang-guestfs..

thm gravatar imagethm ( 2014-08-10 09:41:43 -0600 )edit

2 Answers

Sort by ยป oldest newest most voted
2

answered 2014-08-11 06:16:05 -0600

rjones gravatar image

The reason is because golang is broken in Fedora 20 and above. Therefore it is not possible to build the golang subpackage. To fix this do:

yum remove golang-guestfs

and continue with the update as normal.

There is no Provides/Obsolete because there is no replacement for this package at this time. You can help by fixing golang ( https://bugzilla.redhat.com/show_bug.cgi?id=1099206 ).

edit flag offensive delete link more
0

answered 2014-08-10 04:37:27 -0600

hedayat gravatar image

Ask Fedora is certainly not a good place for this. This is probably the mistake of package maintainer, which should have pushed updates simultaneously. IMHO, you should either contact the maintainer directly or post in -devel list. Filling a bug against the update is also a reasonable alternative. It is not a bug in the package itself, but in how its update is being pushed to stable repository.

Thinking again, I think there should be either a discussion in -devel list or a bug against Fedora update infrastructure, because IMHO we should open a feature reguest against the infrastructure (e.g. AutoQA), so that it should check if the dependencies of a package are all available in Fedora/Updates repository, and only allow packages to be pushed to updates repository when their dependencies are resolved from the repositories including the packages which are being pushed. Currently, this is a manual process: the maintainer should be carefull enough to push dependend updates simultaneously. But I think updates with dependency problems should remain in a queue and only pushed (automatically) when their dependencies are also going to be pushed.

edit flag offensive delete link more

Question Tools

2 followers

Stats

Asked: 2014-08-10 04:03:23 -0600

Seen: 154 times

Last updated: Aug 11 '14