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 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 > 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 So, I was bitten by this as well. It seems that this bug is breaking Subversion on upgrades on systems that don't have a correct hostname. Having a broken hostname is of course bad, but this shouldn't stop Subversion from working, esp. since it's a regression from squeeze. It appears that it's not that uncommon: we had two separate bug reports with multiple reporters in Debian, there's a similar openSUSE¹ bug, a similar MacPorts bug² etc. It also affects more than Subversion; KMail & Kontact have been explictly mentioned. So, I'm bumping the severity to important -- I also considered serious/RC, but I'll leave that up to the maintainer. The issue seems to have been fixed upstream with commit 8fc14fd702897e652a38384af2f55e51752e8c15, as mentioned in the upstream bug report³, so I think it'd be great if this ended up backported into wheezy. Thanks, Faidon ¹: https://bugzilla.novell.com/show_bug.cgi?id=771983 ²: https://trac.macports.org/ticket/34861 ³: https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org