bzr-svn still broken in 2.0rc2

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

>> Well, as the primary windows packager, I rarely know what version of
>> bzr-svn to use. And I'm subscribed to the whole bzr wiki.
> The wiki page lists the versions of bzr-svn and what versions of bzr
> they are compatible with. What more info can I provide?

Well, I'm pretty sure I subscribed to the whole wiki a while back, but I
don't remember seeing the update for 1.0.0rc1. Then again, I may just be
mentally filtering wiki updates out of my 'things-to-read' list.

If you are keeping that page up to date, then I'll certainly look there
in the future.

Though that still leaves me hanging for:
  subvertpy
  bzr-rebase/rewrite
...

>> And given that we *do* need to package a new bzr-svn if there is a
>> "minor API change that we have to cope with", it would be good to know
>> about.
>>
>> One possibility is if you just want to track the
>> 'bzr-windows-installers' project, and when you release a new bzr-svn,
>> just update the appropriate field in 'tools/win32/buildout.cfg'
> Ian and I discussed this a bit more on IRC. I'll update the versions in
> buildout.cfg when I do new releases.

That is certainly easier for me :). And if you do it across all the
plugins that you maintain that we are packaging, then it is a consistent
location to get updates.

Also, once we get the buildbot stuff sorted out, it means that the
windows 'nightly builds' that we'll end up will also start packaging the
latest versions right away.

>> I don't want it to be a burden to you, but as it stands, you also don't
>> update the Launchpad bzr-svn page, so I can't even just go there and see
>> what the latest version is. Is there a better page that you do keep up
>> to date? Perhaps something on the debian pages?
> I've never updated the bzr-svn page on Launchpad manually, Launchpad
> (should) automatically detect new releases on the main download site
> (http://samba.org/~jelmer/bzr/).
> 
> Cheers,
> 
> Jelmer
> 
> 

Fair enough, I'm not really sure how that side of things works. Anyway,
thanks for working with me on this. I really do want to keep up to date
with your work. It has just felt that somehow I was missing info on what
was actually the 'latest' work when I went to start packaging.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq6JtsACgkQJdeBCYSNAAP/BACeJ4DSExySB0ehmfEnPOWRdq/v
j80AoIJUb2+q6B716sP2GJNhbggCvcrB
=Rnbd
-----END PGP SIGNATURE-----