6:38 a.m.
I've just installed F12beta (x86_64) in a KVM virtual machine without
problems. When trying to update through System->Administration->Software
Update it failed because of a missing dependency. Not really a surprise
there. I then update through a yum update --skip-broken, that worked.
Is there a way to do a '--skip-broken' via de gui updater? That would be
a really useful feature. Now you have to find the misbehaving package(s)
and deselect them before you can do a update. To longer the list of
updates...
Jurgen
8:37 a.m.
On Fri, 2009-10-23 at 13:38 +0200, Jurgen Kramer wrote:
I've just installed F12beta (x86_64) in a KVM virtual machine
without
problems. When trying to update through System->Administration->Software
Update it failed because of a missing dependency. Not really a surprise
there. I then update through a yum update --skip-broken, that worked.
Is there a way to do a '--skip-broken' via de gui updater? That would be
a really useful feature. Now you have to find the misbehaving package(s)
and deselect them before you can do a update. To longer the list of
updates...
Can't you just uncheck the box to the package that is causing the
problem? But I guess if you have more than one that can be time
consuming?
--
Mike Chambers
Madisonville, KY
"Best lil town on Earth!"
9:06 a.m.
2009/10/24 Mike Chambers <mike(a)miketc.net>:
On Fri, 2009-10-23 at 13:38 +0200, Jurgen Kramer wrote:
> Is there a way to do a '--skip-broken' via de gui updater? That would be
> a really useful feature. Now you have to find the misbehaving package(s)
> and deselect them before you can do a update. To longer the list of
> updates...
Can't you just uncheck the box to the package that is causing the
problem? But I guess if you have more than one that can be time
consuming?
In theory, yes, but the most recent time this happened it was in a the
middle of over 100 total updates (rawhide), many of which had similar
names (it was xorg-x11-something that was causing the problem), so I
just resorted to yum --skip-broken instead of scrolling through the
massive list to un-check one of them.
MEF
--
Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/
Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab
School of Mathematical and Computer Sciences, Heriot-Watt University
Heriot-Watt University is a Scottish charity registered under charity
number SC000278
11:14 a.m.
On Sat, Oct 24, 2009 at 03:06:02PM +0100, Mary Ellen Foster wrote:
(it was xorg-x11-something that was causing the problem)
Quite likely xorg-x11-proto-devel.noarch. It needs newer
libXxf86dga-devel and that is missing. See
https://bugzilla.redhat.com/show_bug.cgi?id=530449
Michal
5:01 p.m.
On Sat, Oct 24, 2009 at 10:14:37 -0600,
Michal Jaegermann <michal(a)harddata.com> wrote:
On Sat, Oct 24, 2009 at 03:06:02PM +0100, Mary Ellen Foster wrote:
> (it was xorg-x11-something that was causing the problem)
Quite likely xorg-x11-proto-devel.noarch. It needs newer
libXxf86dga-devel and that is missing. See
https://bugzilla.redhat.com/show_bug.cgi?id=530449
It's not missing, it's a conflict. I ended up uninstalling libXxf86dga-devel
to get the update. It might be that there is a missing obsoletes here.
(If libXxf86dga-devel's function is now provided by xorg-x11-proto-devel.)
5:38 p.m.
On Sat, Oct 24, 2009 at 05:01:24PM -0500, Bruno Wolff III wrote:
On Sat, Oct 24, 2009 at 10:14:37 -0600,
Michal Jaegermann <michal(a)harddata.com> wrote:
> On Sat, Oct 24, 2009 at 03:06:02PM +0100, Mary Ellen Foster wrote:
> > (it was xorg-x11-something that was causing the problem)
>
> Quite likely xorg-x11-proto-devel.noarch. It needs newer
> libXxf86dga-devel and that is missing. See
> https://bugzilla.redhat.com/show_bug.cgi?id=530449
It's not missing, it's a conflict.
Missing is a suitable version of libXxf86dga-devel. That was
a shorthand and is said "newer". You can find details in
https://bugzilla.redhat.com/show_bug.cgi?id=530449
M.
6:59 a.m.
On 10/23/2009 05:08 PM, Jurgen Kramer wrote:
I've just installed F12beta (x86_64) in a KVM virtual machine
without
problems. When trying to update through System->Administration->Software
Update it failed because of a missing dependency. Not really a surprise
there. I then update through a yum update --skip-broken, that worked.
Is there a way to do a '--skip-broken' via de gui updater? That would be
a really useful feature. Now you have to find the misbehaving package(s)
and deselect them before you can do a update. To longer the list of
updates...
PackageKit already uses --skip-broken by default anyway. So the problem
was likely something like a conflict which cannot be detected before the
transaction (unlike a dependency failure) and hence would not be solved
via --skip-broken.
Rahul
8:28 p.m.
On Sun, 25 Oct 2009, Rahul Sundaram wrote:
On 10/23/2009 05:08 PM, Jurgen Kramer wrote:
> I've just installed F12beta (x86_64) in a KVM virtual machine without
> problems. When trying to update through System->Administration->Software
> Update it failed because of a missing dependency. Not really a surprise
> there. I then update through a yum update --skip-broken, that worked.
>
> Is there a way to do a '--skip-broken' via de gui updater? That would be
> a really useful feature. Now you have to find the misbehaving package(s)
> and deselect them before you can do a update. To longer the list of
> updates...
PackageKit already uses --skip-broken by default anyway. So the problem
was likely something like a conflict which cannot be detected before the
transaction (unlike a dependency failure) and hence would not be solved
via --skip-broken.
file-conflicts can't be detected before the ts - but explicit conflicts
can.
-sv
1:36 p.m.
On Sun, 2009-10-25 at 17:29 +0530, Rahul Sundaram wrote:
On 10/23/2009 05:08 PM, Jurgen Kramer wrote:
> I've just installed F12beta (x86_64) in a KVM virtual machine without
> problems. When trying to update through System->Administration->Software
> Update it failed because of a missing dependency. Not really a surprise
> there. I then update through a yum update --skip-broken, that worked.
> Is there a way to do a '--skip-broken' via de
gui updater? That would be
> a really useful feature. Now you have to find the misbehaving package(s)
> and deselect them before you can do a update. To longer the list of
> updates...
PackageKit already uses --skip-broken by default anyway. So the problem
was likely something like a conflict which cannot be detected before the
transaction (unlike a dependency failure) and hence would not be solved
via --skip-broken.
Rahul
Thanks, I've just experienced the same dependency resolution problem
while trying to update my F12 beta install today:
It states: xorg-x11-proto-devel conflicts with libXxf86-dga-devel
Via the GUI I cannot continue without removing xorg-x11-proto-devel from
the install list. This is not a problem when there's only one conflict.
It would be nice if PacketKit would be able to circumvent those problems
or present a list of offending/conflicting packages to deselect.
Jurgen
1:55 p.m.
On Mon, 2009-10-26 at 19:36 +0100, Jurgen Kramer wrote:
On Sun, 2009-10-25 at 17:29 +0530, Rahul Sundaram wrote:
> On 10/23/2009 05:08 PM, Jurgen Kramer wrote:
> > I've just installed F12beta (x86_64) in a KVM virtual machine without
> > problems. When trying to update through System->Administration->Software
> > Update it failed because of a missing dependency. Not really a surprise
> > there. I then update through a yum update --skip-broken, that worked.
> >
> > Is there a way to do a '--skip-broken' via de gui updater? That would
be
> > a really useful feature. Now you have to find the misbehaving package(s)
> > and deselect them before you can do a update. To longer the list of
> > updates...
>
> PackageKit already uses --skip-broken by default anyway. So the problem
> was likely something like a conflict which cannot be detected before the
> transaction (unlike a dependency failure) and hence would not be solved
> via --skip-broken.
>
> Rahul
Thanks, I've just experienced the same dependency resolution problem
while trying to update my F12 beta install today:
It states: xorg-x11-proto-devel conflicts with libXxf86-dga-devel
Via the GUI I cannot continue without removing xorg-x11-proto-devel from
the install list. This is not a problem when there's only one conflict.
It would be nice if PacketKit would be able to circumvent those problems
or present a list of offending/conflicting packages to deselect.
Jurgen,
With a painfully slow network connection I'm slogging through a
work-around that in 2-3 more days may complete a GUI install. I simply
deselected the Development groups I think contain one or both of those
packages and let 'er rip. As I write this the progress bar is at 2148 of
5607 packages. After the initial installatin is comlete, I can go back
and install the Development groups I skipped, isolating the one or two
errant packages (if they haven't been fixed by then).
--Doc
2:29 p.m.
On Mon, 2009-10-26 at 19:36 +0100, Jurgen Kramer wrote:
Thanks, I've just experienced the same dependency resolution
problem
while trying to update my F12 beta install today:
It states: xorg-x11-proto-devel conflicts with libXxf86-dga-devel
Via the GUI I cannot continue without removing xorg-x11-proto-devel from
the install list. This is not a problem when there's only one conflict.
It would be nice if PacketKit would be able to circumvent those problems
or present a list of offending/conflicting packages to deselect.
Jurgen,
It appears that this problem has been fixed:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1767972
https://fedorahosted.org/rel-eng/ticket/2715
--Doc
2:09 p.m.
On Mon, 2009-10-26 at 14:29 -0500, Robert G. (Doc) Savage wrote:
On Mon, 2009-10-26 at 19:36 +0100, Jurgen Kramer wrote:
> Thanks, I've just experienced the same dependency resolution problem
> while trying to update my F12 beta install today:
>
> It states: xorg-x11-proto-devel conflicts with libXxf86-dga-devel
>
> Via the GUI I cannot continue without removing xorg-x11-proto-devel from
> the install list. This is not a problem when there's only one conflict.
> It would be nice if PacketKit would be able to circumvent those problems
> or present a list of offending/conflicting packages to deselect.
Jurgen,
It appears that this problem has been fixed:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1767972
https://fedorahosted.org/rel-eng/ticket/2715
--Doc
OK, thanks. I just used the actual dep problem a way for me see if there
more people who would like to see PackageKit more smarter about fixing
dep probs (from the GUI). I guess editing yum.conf would work as well
but maybe not for the less techie people.
Jurgen
2:48 p.m.
On Mon, 26 Oct 2009 19:36:36 +0100
Jurgen Kramer wrote:
Via the GUI I cannot continue without removing xorg-x11-proto-devel
from
the install list. This is not a problem when there's only one conflict.
It would be nice if PacketKit would be able to circumvent those problems
or present a list of offending/conflicting packages to deselect.
Or if skip-broken were just made the default: For quite a while now
skip-broken has actually been working well (a long time ago it used
to just spend 20 minutes to tell you it couldn't resolve the conflict :-).
I believe you can enable it by default in /etc/yum.conf (though I'd
have to research exactly how), I think it is stable enough these days
to just make it be on by default in the yum.conf shipped with the
systems.
2:47 p.m.
On 10/27/2009 01:18 AM, Tom Horsley wrote:
I believe you can enable it by default in /etc/yum.conf (though
I'd
have to research exactly how), I think it is stable enough these days
to just make it be on by default in the yum.conf shipped with the
systems.
set skip-broken=1 in /etc/yum.conf if you want it there by default.
Simple. I agree it should be the default as well.
http://mether.wordpress.com/2009/10/01/preventing-dependency-breakage-par...
Rahul
5339
days inactive
5343
days old
13 comments
9 participants
participants (9)
-
Bruno Wolff III -
Jurgen Kramer -
Mary Ellen Foster -
Michal Jaegermann -
Mike Chambers -
Rahul Sundaram -
Robert G. (Doc) Savage -
Seth Vidal -
Tom Horsley