Re: some issues with "lp:epics-base" in bazaar

[Andrew Johnson <anj@aps.anl.gov>]

On Friday 13 August 2010 16:26:27 Jeff Hill wrote:
>
> I found two significant bugs in base today, and if I fix them only on my
> cvs main trunk ancestor branch there is a risk that they will be lost when
> attempting to break that tree into independent merges. So I tried to
> refresh my existing R3.14 development area. That didn?t work so I threw out
> that one and tried to load a fresh one but there are still some issues.
>
> In any case when I try to download from the URL "lp:epics-base" using
> bazaar explorer I see the error message below. I think this worked before,
> but perhaps I am doing something stupid? In any case loading code from
> "https://code.launchpad.net/epics-base"; does work just fine.
>
> Invalid url supplied to transport:
> "file:///home/phoebus3/ANJ/epics/base/export/base.bzr/trunk/": Win32 file
> urls start with file:///x:/, where x is a valid drive letter

This is a known but benign problem with Bazaar explorer when you point it to a 
lightweight checkout.  I reported it as a bug several months ago, see here:
  https://bugs.launchpad.net/bzr-explorer/+bug/550989

If you want to get rid of the message don't do a lightweight checkout.  I 
think a regular checkout should be fine, but I do know for sure that a normal 
branch is.  However you can just ignore the message if you have disk space 
issues and prefer to stay lightweight.

BTW there is a known issue with the current 3.14 branch version that crept in 
with the ca-over-tcp branch merge; it segfaults at shutdown of the client 
library when the tcpSendThread tries to use an already dead mutex.  Ralph is 
looking at that right now, so don't go chasing it yourself without checking 
with him first.

- Andrew
-- 
The best FOSS code is written to be read by other humans -- Harald Welte