On (23/11/06 20:30), James Westby wrote: > 2) If you do not want to add a new upstream version to etch now then remove > the warning from the code. As far as I know there is no > functionality loss from this. > > I attach two patches, one for each solution. (Please note the second is > not tested exactly, but it is the workaround I used when this problem > started. The first patch is an svn diff from current trunk of what it > would take to package a clean 0.11.0 tarball. The changes to > debian/control could even be left out.
Ok, sorry, I said it wasn't tested, it doesn't even work. It should of course pass in the if clause, or comment out the if as well. Apologies for getting this wrong, but I think you get the idea of the intent. James > > Index: bzrtools-0.10.0/__init__.py > =================================================================== > --- bzrtools-0.10.0.orig/__init__.py 2006-11-23 20:17:19.000000000 +0000 > +++ bzrtools-0.10.0/__init__.py 2006-11-23 20:17:54.000000000 +0000 > @@ -38,7 +38,7 @@ > ' \nThere should be a newer version available, e.g. %i.%i.' > % (bzrlib.__version__, bzrlib_version[0], bzrlib_version[1])) > if bzrlib_version != desired_plus: > - raise Exception, 'Version mismatch' > +# raise Exception, 'Version mismatch' > > > check_bzrlib_version(version_info[:2]) -- James Westby -- GPG Key ID: B577FE13 -- http://jameswestby.net/ seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
