[packagekit] exclude some upgrades

Richard Hughes hughsient at gmail.com
Mon Nov 12 09:58:17 PST 2007

On Mon, 2007-11-12 at 12:43 -0500, David Zeuthen wrote:
> On Mon, 2007-11-12 at 17:33 +0000, Richard Hughes wrote:
> > The only way I think this makes sense is to have a "Update just this
> > package" button on the update detail for users that want "I only want to
> > try out the gimp update" although the use case for this seems slim
> > indeed. Yell if you want this, this would take a matter of minutes to
> > add.
> Yeah, I was thinking about this too. The ability to cherry-pick what
> updates you want is probably what we want.

How is a user going to know what package caused the _automatic update_
to fail because libnm_glib.so.5 couldn't be found. The link between
unticking NetworkManager _manually_ in the update viewer and the
random.so.5 error isn't very obvious.

> Though, even that may be a
> stretch. But it's probably useful in instances where the user have some
> kind of dep problem; it happens even on stable distros especially if the
> user throws 3rd party repos and RPM's into the mix.

We can't and shouldn't add this interaction into PackageKit - it should
be fixed in one of two ways:

1) Repositories shouldn't be pushed is they don't depsolve.
2) yum should auto-ignore packages that don't depsolve.

This isn't a PackageKit problem; rawhide is very unstable and applying
the same logic to new user installing software and developers trying to
work around a broken development repo is just too different in my


More information about the PackageKit mailing list