bzr-svn still broken in 2.0rc2

[Óscar Fuentes]

Hello Martin.

Martin Pool <mbp at canonical.com> writes:

> 2009/9/19 Óscar Fuentes <ofv at wanadoo.es>:
>> Upgrading to 1.18 broke bzr-svn, as it triggers a bug on subvertpy that
>> prevents pushing changes to svn repos. Well, this is in Windows, in
>> Ubuntu bzr-svn is removed when you upgrade to bzr 1.18 via
>> http://ppa.launchpad.net/bzr/ppa/ubuntu because the bzr-svn package
>> there is marked as incompatible with bzr 1.18. Same for the beta/rc
>> ppa. IIRC someone promised to update bzr-svn on the ppa as soon as
>> Jelmer returned from vacation, but things stay the same.
>>
>> Just downloaded the bzr-2.0.0rc2-4-setup.exe installer for Windows and
>> the outdated buggy bzr-svn and subvertpy are still there.
>>
>> What's the point of a rc that contains known critical bugs on popular
>> plugins? What's the point of a rc which final release will contain (I
>> hope) a different version of a popular plugin?
>
> Thanks for raising it, this does sound like a problem.
>
> So just to be clear, you're saying that bzr-svn is now fixed (in its
> latest release?) but not yet updated into the ppa and the windows
> installer?  Which bugs?

My understanding is that the bug is on subvertpy (the subversion
bindings that bzr-svn uses, which are are maintained by Jelmer too).

https://bugs.launchpad.net/bzr-svn/+bug/413113

Even if the bug report says that it hits people with subversion 1.6.4
installed, the truth is that 1.5.4 is affected too, which is the current
version on Jaunty, and problably on other installs too, because 1.5.4
and 1.6.4 are security fixes.

Although subvertpy is distributed on the bzr Windows installer, I don't
know if it is considered a part of bzr-svn from the point of view of the
packagers of bzr or just another packaged component.

The situation rigth now is this:

 1. the bzr-svn package on bzr's ppa is restricted to bzr<1.18, so when
 people upgrade to bzr 1.18 bzr-svn is removed. AFAIK, Synaptic does not
 show the option of downgrading to bzr 1.17.

 2. even if you install bzr-svn as an ordinary package (bzr branch on
 the plugins directory etc) it is still buggy, because the real bug is
 in the subvertpy package. So you have to manually install subvertpy,
 which is not as easy as installing the bzr-svn plugin, because it is a
 C python extension. This introduces a problem of a mixed ppa + manual
 installation, which is harder to maintain.

 3. on Windows the situation is that the installer comes with everything
 on a single package, but containing an outdated bzr-svn (0.6.5). Jelmer
 is on 1.0.1 and before that the last on the 0.6 series was 0.6.9. And
 it comes with the buggy subvertpy too.

Please let me know if you need more info.

-- 
Óscar