On Sun, Jan 18, 2009 at 01:56:27AM -0600, "Boyd Stephen Smith Jr." <b...@iguanasuicide.net> was heard to say: > On Saturday 17 January 2009, Daniel Burrows <dburr...@debian.org> wrote > about 'Re: aptitude freezes after install': > >On Sat, Jan 17, 2009 at 08:55:10PM -0500, microwaverich <richg...@one.net> > was heard to say: > >> If I understand you correctly, I should try installing the above > >> aptitudes (in reverse order?) and then installing some other package > >> (any package?). > > > > Yes -- starting with the most recent ones, install each aptitude > >version (just the ones I listed would be fine for now), then try > >installing or removing some small package. I use xsoldier for this > >sort of test, but you can pick a different victim if you like. The > >goal is to find the most recent broken version (i.e., the one where > >the breaking change was introduced). > > Wow, this sounds like a job for "git bisect". Unfortuntely, I can't use > that method as the issue doesn't manifest itself on any of my systems.
The problem is, the earliest version of aptitude which is known to be free of the bug is so old that it no longer builds with the current toolchain in Debian. And if you run "hg bisect", giving that version as the starting point, "bisect" picks a version that requires a version of libcwidget-dev that is no longer in the archive. I'm trying to find a way of doing this without posting the horribly convoluted instructions that would be necessary to deal with that situation. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
