** Changed in: charm-lxd
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788040
Title:
Replace LXD deb by snap in Ubuntu 18.10
To manage notifications about this bu
** Changed in: charm-lxd
Status: New => Triaged
** Changed in: charm-lxd
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788040
Title:
Replace LXD deb by sn
This bug was fixed in the package lxd - 1:0.3
---
lxd (1:0.3) cosmic; urgency=medium
* Install the snap on package installation too, not just upgrades
* Make snapd a Pre-Depends for the case where snapd isn't installed
-- Stéphane Graber Thu, 13 Sep 2018 14:28:29
-0400
** Cha
As planned, releasing this to the release pocket by removing the blocker
tag.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788040
Title:
Replace LXD deb by snap in
All autopkgtest failures have been dealt with, we're now all green and
only held by this bug's tag.
I intend to clear the tag, allowing for lxd to transition to the release
pocket on Monday.
There will likely be a bit of bumpiness afterwards as seeds and meta
packages get updated (2-3 hours), the
** Also affects: charm-lxd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788040
Title:
Replace LXD deb by snap in Ubuntu 18.10
To manage notifications a
And package has now been uploaded to cosmic-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788040
Title:
Replace LXD deb by snap in Ubuntu 18.10
To manage notifications about this bug go
Marking bug as block-proposed so we keep the transitional package in
proposed for now.
** No longer affects: autopkgtest (Ubuntu)
** No longer affects: adapt (Ubuntu)
** No longer affects: nova-compute-lxd (Ubuntu)
** No longer affects: snapcraft (Ubuntu)
** Tags added: block-proposed
** Chan
Ok, going to close the nova-compute-lxd task then as it sounds like from
a packaging point of view we're good, it's external integration (charms)
that may run into problems.
Note that since we will still have a "lxd" package in the archive which
auto-installs the snap for you, things may just work
>From the perspective of nova-lxd, there isn't a problem with the snap
version (as pylxd already works with a snap version of lxd). However,
the lxd charm will need to be altered to ensure that it installs /
otherwise manages the fact that lxd is supplied in snap form.
We do have some utilities t
And confirmed that snapcraft (cleanbuild) similarly works just fine.
** Changed in: snapcraft (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788040
Title:
Rep
I've confirmed that adapt from the cosmic archive works just as well
with the snap as it does the deb.
** Changed in: adapt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
So looks like we're in good shape with removal of "lxd-client" and "lxd-
tools" as only Suggests remains and that's autopkgtest which will be
switched over to "lxd" soon enough.
I'm now checking the rdepends of lxd to ensure that they deal with the
snap as expected.
--
You received this bug noti
Thanks Martin!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788040
Title:
Replace LXD deb by snap in Ubuntu 18.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Ah, it used to be useful for running the containers on a remote servers.
I. e. what we used to do for armhf testing, they were running on remote
arm64 OpenStack instances.
I adjusted the Suggests: https://salsa.debian.org/ci-
team/autopkgtest/commit/4d4a7d9b16f
Thanks!
** Changed in: autopkgtest
The only binary package left post-transition will be "lxd". The "lxc-
client" and "lxd-tools" binary packages will be removed from the
archive.
For autopkgtest, it sounds like we'll just need to change the Suggests
to point to lxd rather than lxd-client which should be fine even in the
current wor
autopkgtest *only* uses the `lxc` CLI and documents the `lxd` setup CLI
from $PATH. The package has a "Suggests: lxd-client". You mention that
the "lxd" deb will remain around, does that apply to "lxd-client" as
well?
** Changed in: autopkgtest (Ubuntu)
Status: New => Incomplete
--
You re
17 matches
Mail list logo
