On Tue, Jun 07, 2005 at 10:05:15AM -0700, Paul Telford wrote: > 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?
No, only in the aptitude view of the world apparently. We will see what we can do when the next version of the release note will be prepared. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
