On Tuesday 07 June 2005 10:05 am, 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?
"aptitude hold" should work. aptitude's parsing of the dselect state has been buggy for a while, mainly because I don't use dselect much and the people who do use it don't seem interested in tracking bugs down and sending me a patch :P. I've done some work on this in experimental (i.e., for etch), but obviously that doesn't help woody -> sarge upgrades. Daniel -- /------------------- Daniel Burrows <[EMAIL PROTECTED]> ------------------\ | "Next, consider a circle passing through infinity; that | | is, a straight line.." | \--- Be like the kid in the movie! Play chess! -- http://www.uschess.org --/
pgp0aufhYcgnT.pgp
Description: PGP signature
