On Tue, Jun 07, 2005 at 09:02:22AM -0700, Paul Telford wrote: > Upgrade sequence: > - updated sources.list > - dpkg --get-selections | grep hold > # Noted that one package, 'mantis', was intentionally on hold > - apt-get install aptitude > - aptitude -f --with-recommends dist-upgrade > # Watch as mantis gets upgraded anyway > - dpkg --get-selections | grep hold > # Mantis still marked as on hold > > > The release notes state: > If you changed and recompiled a package locally, and didn't rename it or > put an epoch in the version, you must put it on hold to prevent it from > being upgraded. > > > I expected that my package and any dependencies would not be upgraded, or > that aptitude would give me an error message if this somehow caused an > unresolvable situation. Unfortunately, it upgraded the package anyway, > wiping out some local changes. Not catastrophic in this case, but > contrary to the information in the release notes at least.
I think this is bug #146207. Cheers, Bill. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
