Synaptic lock version not working

[guille]

There is a problem with the current pidgin-plugin-pack version, so I had to manually build it from sources.
After installing it, the update manager says that there is an update for that package, which I don't want to install.
I open Synaptic, select the package and "package->lock version". It is marked as locked as expected.
The update manager keeps on notificating that there are updates available for that package.
I run "aptitude hold pidgin-plugin-pack" but the update manager keeps on notificating available updates.
I expect the update manager to stop notifying updates for that package.

I suppose it doesn't depend on the package being installed, but I didn't check it.

No related info found in ubuntu forums.

The version I manually installed has the same numbers as the one in the repository (2.2.0-1).

I'm running Ubuntu 8.10, synaptic 0.62.1ubuntu10 and aptitude 0.4.11.3-1ubuntu3.

[goto (gotolaunchpad)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in synaptic.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

If you compile yourself, why don't you remove the old package? Then there should be no update notifications?
But yes, if locking isn't working, this is a bug.

[guille (guizzzmo)]

I don't know if I understood your comment. What do you mean by remove the old package?

1. I uninstalled/removed the "old package" (the one on the repository)
2. I installed the package I compiled myself.
3. I opened Synaptic and mark the package as "lock version"
4. the update manager still notifies "available updates".

Please, tell me if you need more information.

[goto (gotolaunchpad)]

Ah, I see. You removed the package. Okay, this is a bug. I just wondered, why there should be updates for a package, which isn't even installed.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? May you please try the same with Jaunty and comment back? Thanks in advance.

[Andrew Dodd (atd7)]

goto - I think you misunderstood him, based on how he's wording it, he manually rebuilt a .deb and installed it. Now update-notifier keeps wanting to update that package, since it is installed (just a different version, his version).

This is still a problem in Karmic. More specifically, update-notifier, kpackagekit, adept, and basically every package manager other than synaptic do NOT respect Synaptic's "force version" option.

As a result, even if people have a package version-locked in Synaptic, they will always have to be careful not to accidentally upgrade the package when they get an update prompt. Also, they will have to live with update notifications for packages they don't want updating until the end of time.

Another example of this is the MythTV 0.21 packages in J. Y. Avenard's MythTV repo - http://avenard.org/media/Ubuntu_Repository/Ubuntu_Repository.html - If you install MythTV 0.21 using Synaptic's force version option (for example, to allow compatibility with a Myth 0.21 backend you won't be able to upgrade for a few weeks), all other package managers in the system will continuously prompt you to update to 0.22.

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 42178, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.