[elbe-devel] elbe initvm attach -> login does not work after upgrading from 1.1 to 1.2 stable

[Manuel Traut]

On Tue, Apr 10, 2018 at 03:31:35PM -0700, Richard Cochran wrote:
> On Tue, Apr 10, 2018 at 8:02 AM, Manuel Traut
> <manuel.traut at linutronix.de> wrote:
> > install python-apt AND import elbe-repo.pub with apt-key add ..
> 
> Still trying to find out what is going here.
> 
> In the *bad* case (ubuntu 16.4 in a VM)  the 'eble init' command does this:
> 
> --2018-04-10 13:52:18--
> http://debian.linutronix.de/elbe-common/pool/main/e/elbe-bootstrap/elbe-bootstrap_20150422+deb8u4_amd64.deb
> Resolving debian.linutronix.de (debian.linutronix.de)... 146.0.238.70
> Connecting to debian.linutronix.de
> (debian.linutronix.de)|146.0.238.70|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 24546432 (23M) [application/x-debian-package]
> Saving to: '/tmp/tmp7vVSri/pkg.deb'
> 
> But on my *good* machine I see:
> 
> --2018-04-10 15:24:25--
> http://debian.linutronix.de/elbe-common/pool/main/e/elbe-bootstrap/elbe-bootstrap_20150422+deb8u5+jessie141_amd64.deb
> Resolving debian.linutronix.de (debian.linutronix.de)... 146.0.238.70
> Connecting to debian.linutronix.de
> (debian.linutronix.de)|146.0.238.70|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 24585876 (23M) [application/x-debian-package]
> Saving to: ‘/tmp/tmpVq2lDO/pkg.deb’
> 
> What causes the bad machine to pick the other package?

Is the 'elbe-repo.pub' is missing in the apt keyring on one machine?

> (BTW the bad machine is a random developer's machine, with a different
> set of locally installed debs.
> We looked at likely candidates, like apt, python-apt, etc, but we
> didn't see any different versions
> between the good and bad machines.)
> 
> Thanks,
> Richard