On Sat, Jul 28, 2007 at 01:08:52AM +0200, Jiří Paleček <[EMAIL PROTECTED]> was heard to say: > On Fri, 27 Jul 2007 15:27:52 +0200, Daniel Burrows <[EMAIL PROTECTED]> > wrote: > The darcs problem is basicly the same, a hand installed package is marked > as auto. The difference is that in the darcs case, it is not a previously > installed package (as in the OOo case), but a package which is installed > by hand in the same session. (ie. I select an uninstallable version -> > resolver offers a (higher) installable version -> apply solution -> > aptitude marks it as auto -> no version is installed).
Ah, right. I wasn't thinking properly about the problem before and produced a patch that was wrong. Could you see if this one fixes your problem? > >aptitude-create-state-bundle (assuming you have aptitude 0.4.6) and send > >me the output? > > I don't have aptitude 0.4.6, and probably won't upgrade till apt 0.7.4 gets > into testing. Maybe I could create a repository which exhibits the > behaviour, > would that be OK? Basically, I'd need the following stuff in a tarball: $HOME/.aptitude /var/lib/aptitude /var/lib/apt /var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin /etc/apt /var/lib/dpkg/status > BTW, there's something bad about aptitude package's uploads (which might > not be > caused by you). There are some versions (eg. 0.4.5-1 and 0.4.6-1) in the > changelog > whose uploads are not seen on packages.qa.d.o and bugs closed by these > versions > are still open in the BTS. AFAIK I've done the right thing; the BTS seems to have gotten really flaky about closing bugs since version awareness was introduced, though. I just noticed that 0.4.6 was missing a moment ago -- but I hadn't noticed that 0.4.5's bugs didn't get closed. Good catch there! Daniel
