[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#567945: lsh-server: Does not configure on mipsel



On Sun, 2010-03-14 at 22:49 +0100, Andreas Barth wrote:
> Hi,
> 
> * Magnus Holmgren (holmgren@debian.org) [100314 22:15]:
> > On tisdagen den 2 februari 2010, Magnus Holmgren wrote:
> > > On måndagen den 1 februari 2010, Adam C Powell IV wrote:
> > > > lsh-server fails to configure on mipsel, as can be seen in the buildd
> > > > log for scalapack:
> > > >
> > > > Setting up lsh-server (2.0.4-dfsg-6+b1) ...
> > > > Creating lsh random seed file (this may take a while) ... done.
> > > > Creating lsh host key ... ................
> > > > ..
> > > >
> > > > done.
> > > > Starting secure shell v2 server: lshdClosed spurious fd 3
> > > >  failed!
> > > 
> > > Can someone please check if there's any syslog output from lshd?
> > 
> > I've successfully tried installing lsh-server on a virtual mipsel machine 
> > under QEMU. I could really use some help here.
> > 
> > I think there's also a bug in lam, though. Either liblam4 should merely 
> > suggest lam-runtime, or lam-runtime should merely suggest ssh-server, or it 
> > should prefer a specific ssh-server implementation.

liblam4 recommends lam-runtime, which seems appropriate.  Most of the
time someone installing liblam4 will need lam-runtime (on all of the
node machines as well as the head), it's only unnecessary for compiling
purposes.

I agree though that lam-runtime should prefer a specific ssh-server
implementation.  Filing a bug.

> > On onsdagen den 3 februari 2010, Niels =?UTF-8?Q?M=C3=B6ller wrote:
> > > Magnus Holmgren <holmgren@debian.org> writes:
> > > >> Starting secure shell v2 server: lshdClosed spurious fd 3
> > > 
> > > I also think this message is suspicious. lshd tries to close all fd:s
> > > between 3 and getdtablesize() (to avoid that any spurious open fd leaks
> > > to user processes it spawns). Expected result is that all these close
> > > calls should fail with EBADF. So what is fd 3, and why is it open?
> > 
> > Probably the pipe for writing commands to Debconf. I could try closing it, but 
> > I don't think it's the problem as lshd started successfully in spite of it 
> > when I tested.
> 
> If the tests are all successfull, I think marking this as
> "unreproducible" and/or closing it is ok.

That will be an acceptable outcome when packages which reverse-depend on
this can successfully install it on the mipsel buildd.

-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: