reassign 683555 libsasl2-2
forcemerge 636534 683555
forwarded 636534 https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589
tags 636534 + fixed-upstream
severity 636534 important
thanks
On Thu, Aug 02, 2012 at 01:59:36AM +0900, Norbert Preining wrote:
> due to a broken laptop I had to switch to an ol
[Stephen Fox]
> I rebuilt subversion without SASL after realizing SASL is an optional
> dependency, and svn is working fine. I suppose a way to isolate it to
> the ABI issue would be rebuilding the SASL libs, and building svn
> against that? I don't entirely understand the implications of Bug
> #6
HI all,
On Sa, 04 Aug 2012, Stephen Fox wrote:
> Could be indeed. I rebuilt subversion without SASL after realizing SASL
> is an optional dependency, and svn is working fine. I suppose a way to
Agreed, I did now the same, rebuild a NMU and changed the configure
to --without-sasl and woops everyth
On 08/02/2012 10:44 AM, Peter Samuelson wrote:
> I do wonder if it is somehow related to Bug #665476. I mean, probably
> not, but possibly? Peter
Could be indeed. I rebuilt subversion without SASL after realizing SASL
is an optional dependency, and svn is working fine. I suppose a way to
isolate i
[Norbert Preining]
> $ svn up
> Updating '.':
> svn: E170001: Unable to connect to a repository at URL
> 'svn://u...@server.org/some/path'
> svn: E170001: Could not create SASL context: generic failure: No such file or
> directory
>
> The same happens with svn+ssh://... on svn.debian.org
This
Package: subversion
Severity: serious
Version: 1.7.5-1
Hi everyone,
due to a broken laptop I had to switch to an old one. After upgrading
from a about 2 year old system, suddenly my svn is completely
broken wrt to svn:// URLs. ALl trials (co, up, ...) terminate with
the same error:
$ svn up
Upda
6 matches
Mail list logo
