On Tue, Aug 21, 2018 at 05:07:47PM +0200, Matthias Klose wrote:
> On 21.08.2018 17:01, Stéphane Graber wrote:
> > On Tue, Aug 21, 2018 at 04:58:21PM +0200, Matthias Klose wrote:
> >> On 21.08.2018 16:56, Stéphane Graber wrote:
> >>> On Tue, Aug 21, 2018 at 11:46:34AM +0200, Matthias Klose wrote:
> >>>> On 20.08.2018 23:13, Stéphane Graber wrote:
> >>>>> If you're running downstream software which interacts with LXD, I'd
> >>>>> strongly recommend you try switching to the snap, either using the
> >>>>> package in that PPA or manually by installing the LXD snap and then
> >>>>> running "lxd.migrate".
> >>>> there are (and for are for a while) currently failing lxd autopkg tests
> >>>> triggered by other packages (see update_excuses). What's the future of these?
> >>>> Short term fixing those please, and long term?
> >>> LXD 3.0.2 which we'll be uploading this week has a "fix" for those
> >>> errors (effectively shellcheck becoming more verbose).
> >>> The empty LXD deb will not contain any autopkgtest so once the
> >>> transition to the snap is done, autopkgtest will effectively always be a
> >>> no-op.
> >> ... which is interpreted as a failing autopkg test. You have to add an always
> >> succeeding autopkg test.
> > Sure but as I said just a paragraph above this, LXD 3.0.2, which we'll
> > be uploading this week, has a "fix" for this.
> so if we have to wait for every autopkg test fix several weeks, that doesn't
> work in the archive. we have a feature freeze tomorrow, and other packages
> depend on that. From my point of view there is something very wrong if we have
> to wait that long. Multiply that time by other needed autopkg test fixes, and
> we are at this point again accumulating packages in the -proposed pocket for no
> reason ...
Can you relax a bit maybe? LXD 3.0.2 was tagged last Thursday, we're
finishing the release announcement so that it can go in the changelog
and then we'll upload it.
The LXD testsuite takes quite a while to run, so it'd be a waste of time
to have to figure out what to cherry-pick, testbuild, upload, get things
to the release pocket to then do it all over again a few hours later for
the upstream bugfix release.
> sorry, but that's not pro-active archive work.