Hi James, many thanks for trying so hard on this bug. Hopefully if it doesn't occur on sarge -> etch there won't be too many people bitten by it.
I found that removing the dpkg-diversion and reinstalling the vim packages was not sufficient to fix the problem -- but with the additional step of deleting /usr/bin/vim, it worked. On 11/12/06, James Vega <[EMAIL PROTECTED]> wrote:
On Tue, Dec 05, 2006 at 09:23:43AM -0500, James Vega wrote: > On Mon, Dec 04, 2006 at 04:31:18PM -0500, James Vega wrote: > > Ah, you're right. The /usr/bin/vim binary you have is probably a > > version of Vim 6.3 so it'll be looking for /usr/share/vim/vim63. The > > URL you posted in a previous email isn't working, but I'll give try a > > stable -> etch upgrade in the next couple days and see if I can > > reproduce your problem. > > Ok, after taking a look at this, sarge -> etch upgrades work fine. It > seems like your series of updates happened to include our initial switch > to alternatives (1:6.4-001+1) which had some problems cleaning up the > old diversions. I'll setup another sandbox and try upgrading from sarge > to that version and see what goes wrong from there to the current > version in etch. I just tried upgrading from sarge -> 1:6.4-001+2 -> 1:6.4-006+2 -> 1:7.0-122+1 which seems to follow what your logs show. I'm not sure what version you upgraded to 1:6.4-001+2 from but I was unable to reproduce this bug with that series of upgrades. I'm running out of options for reproducing this to debug what went wrong but hopefully my previous emails gave you the information you need to fix your setup. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iEYEARECAAYFAkV9khwACgkQDb3UpmEybUC/zACeK/y+cR+BQXFWP2ejdZljQ8An NycAoJAYpG8ycd9wBWR4a+5BKmnUL4oR =5stl -----END PGP SIGNATURE-----
-- Peter
