On Tue, 7 Jun 2005, Bill Allombert wrote:
> > 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 think this is bug #146207.
Yikes.. been hanging around since 2002. I think the release notes should
be updated. Is there a workaround? Does using "aptitude hold" put the
package *really* on hold?
--
Paul Telford | 1024D/431B38BA | [EMAIL PROTECTED] | [EMAIL PROTECTED]
C903 0E85 9AF5 1B80 6A5F F169 D7E9 4363 431B 38BA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
