On Mon, Mar 11, 2019 at 09:54:14AM +0100, Harald Dunkel wrote:
> Hi Pierre,
>
> On 3/8/19 2:30 PM, Pierre-Elliott Bécue wrote:
> >
> > I'm sorry, but lxc-templates is not needed to have lxc3 working, so it
> > won't become a Dependency. Moving the files from src:lxc-templates to
> > src:lxc and
Hi Pierre,
On 3/8/19 2:30 PM, Pierre-Elliott Bécue wrote:
I'm sorry, but lxc-templates is not needed to have lxc3 working, so it
won't become a Dependency. Moving the files from src:lxc-templates to
src:lxc and subsequently creating two DS uploads is not a fine solution
either.
Control: tags -1 + wontfix
Le vendredi 08 mars 2019 à 10:09:14+0100, Harald Dunkel a écrit :
> Hi Antonio,
>
> wven if Recommends is turned off, its obvious that the template
> specific include files are *required* for a successful migration
> to lxc 3. It shouldn't matter that Recommends is
Hi Antonio,
wven if Recommends is turned off, its obvious that the template
specific include files are *required* for a successful migration
to lxc 3. It shouldn't matter that Recommends is turned off.
Platform specific template scripts might be considered as deprecated
by upstream [1], but
*
On Thu, Mar 07, 2019 at 12:49:21PM +0100, Harald Dunkel wrote:
> Package: lxc
> Version: 1:3.1.0+really3.0.3-5
>
> After the upgrade to lxc 3 the old containers created by
> lxc 2 don't work anymore, even though lxc-update-config has
> been run (manually). The config files still contain template
Package: lxc
Version: 1:3.1.0+really3.0.3-5
After the upgrade to lxc 3 the old containers created by
lxc 2 don't work anymore, even though lxc-update-config has
been run (manually). The config files still contain template
specific include statements, e.g.
lxc.include =
6 matches
Mail list logo
