Hold packages

Bug #35836 reported by MKersloot on 2006-03-21
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Wishlist
Unassigned
Nominated for Intrepid by jasonwc

Bug Description

It would be nice if it is possible to hold a package from the update manager. If a package is hold, update-manager shouldn't report on it any further.

The idea is a little from OS/X where you can ignore updates if you don't care about them, or if you know the update will couse problems.

Sebastian Heinlein (glatzor) wrote :

I cannot reproduce this on dapper.

Regards,

Sebastian

Sebastian Heinlein (glatzor) wrote :

Ok my last comment is obsolete. Sorry.

There is a discussion of this in another bug report. I will look for it later.

Sebastian

Michael Vogt (mvo) wrote :

Thanks for your bugreport.

You could use synaptic if you need this option. It can "lock" packages.

I'm not sure if it's very useful for update-manager given that update-manager is mostely about important and security updates. Usually you want all of them.

Cheers,
 Michael

MKersloot (micha-kovoks) wrote :

I thought that myself, but I got 'complains' from a user why his computer had to update all those programs he never uses. It's surely not a big issue, but I know that OS/X has the possibility to ignore updates. I only added these two pieces of information together and thought.... Well let's tell the developers about this, that's all..

Greets,

Micha

Tom Badran (tom-badran) wrote :

It is possible to pin package versions, but its not in update-manager (many package functions are not, its a really simple update tool). As far as gui support for this feature goes, synaptic is capable of doing this (Package->Lock Version).

MKersloot (micha-kovoks) wrote :

I can understand it is not possible to set the pinning in update-manager, but it would be nice if update-manager would take into account packages wich are pinned by other means.

Xoby (xoby) wrote :

I am not sure that my request is the same as this one, but before opening another bug repport I'll try here first :

Due to a bug in gusty with my hardware, I have to use install another version of the package "network-manager", but the update manager keeps telling me that an update for network-manager is available.

Of course, I don't want to upgrade to this version (which is bugus with my hardware) so I opened aptitude changed the state of the package to "hold". But, the update notification is still here.

I think that the update-notifier should be aware of the "hold" flag and have an option in the preferences like : "don't bother me with updates of packages with the hold flag".

Until this bug is solved, I have to remove update notifier because having a "you have 1 update" message at each login is quite boring ...

Xamusk (ronanpaixao) wrote :

That's actually a good idea.
I'm also having a problem that an "ignore held packages" would solve, like the VMWare player package I have, that keeps trying to reinstall itself (the same version). The package is held at aptitude, but not in update-manager.

Cassiano Leal (cbl-via-rs) wrote :

Just to add up. There is a workaround:

http://ubuntuforums.org/showthread.php?t=43631

Basically, set the package on hold with wajig:

# wajig hold <packagename>

Yashka Oreza (yashka) wrote :

Any thoughts as to what wajig's doing that makes it work better than aptitude in this regard?

Juri Pakaste (juri) wrote :

I don't know what aptitude is doing, but if you put your package on hold using dpkg (echo "packagename hold" | sudo dpkg --set-selections), update-manager and apt-get don't suggest it for upgrade. Also, doing only the dpkg --set-selections thing doesn't seem to affect aptitude; if you want to use it, too, you need to do the aptitude specific hold operation in addition to the one with dpkg.

This might be more of an aptitude issue.

Mackenzie Morgan (maco.m) wrote :

I'm marking this as confirmed since multiple users have commented saying it ignores aptitude's holds.

Changed in update-manager:
status: New → Confirmed
jasonwc (jwittlincohen) wrote :

I can confirm that this bug affects Intrepid as well. "wajig" fixed the problem, though.

Guillaume Duveau (guix) wrote :

Thanks for the trick Juri.

Regarding the latest comments, the issue reported originally is about the possibility to hold a package directly from update-manager, not the fact that update-manager ignores aptitude's holds. This has been reported in bug 75332 .

Setting to "triaged/wishlist" and let the dev handle it from there.

Thanks for your time and don't hesitate to submit any new bug.

Changed in update-manager:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers