Control: severity 766216 important
On Wed, Oct 22, 2014 at 11:01:36AM +0200, Holger Levsen wrote:
3. jessie host with jessie lxc containers (=does work with systemd in the
container)
This does not work in my experience (reported as #766216), so at the
moment is not possible to run jessie
On Wed, 22 Oct 2014, Daniel Baumann wrote:
On 10/21/2014 11:54 PM, Tomas Pospisek wrote:
2) release an updated lxc package for wheezy, that warns the user about
the problem.
i don't really see how that would be possible, without doing an abuse of
debconf.
I'd add that to the NEWS file.
On Wed, 22 Oct 2014, Tomas Pospisek wrote:
On Wed, 22 Oct 2014, Holger Levsen wrote:
ain't there a 5th option, providing an lxc 1.0.x backport for
wheezy [corrected - tpo]? u...@451f.org has one prepared on mentors.d.n
but I was reluctant to sponsor it (so far) as it was only 1.0.5-x,
while
Hi,
On Mittwoch, 22. Oktober 2014, Tomas Pospisek wrote:
And yes, documenting this issue in the release notes would be good
anyway/also! ;-)
I can do that, however I think it'd be good to know beforehand how this
problem will be tackled, so I can document the possible solutions.
great!
Package: lxc
Version: 0.8.0~rc1-8+deb7u2
Severity: critical
Hello,
After upgrading VMs stops to work i.e. 'break' which fullfills for me
the criterion of 'Severity: critical'.
I'm reporting this bug against lxc after consultation on #debian-systemd,
please reassign as you feel is correct. In
severity 766233 important
close 766233 1:1.0.6-3
thanks
On 10/21/2014 07:07 PM, Tomas Pospisek wrote:
I've upgraded a jessie lxc VM. The jessie lxc VM was running on a wheezy
host.
unfortunately, lxc in wheezy lacks support for different things, running
a system with systemd in it is not
Hoi Daniel,
On Tue, 21 Oct 2014, Daniel Baumann wrote:
On 10/21/2014 07:07 PM, Tomas Pospisek wrote:
I've upgraded a jessie lxc VM. The jessie lxc VM was running on a wheezy
host.
unfortunately, lxc in wheezy lacks support for different things, running
a system with systemd in it is not
On 10/21/2014 11:54 PM, Tomas Pospisek wrote:
1) document it in jessie's Release Notes.
would be great if someone could do that, additionally and regardless of
any other options. would you be willing to take care of that (by opening
a bug against release-notes)?
2) release an updated lxc
Hi,
ain't there a 5th option, providing an lxc 1.0.x backport for jessie?
u...@451f.org has one prepared on mentors.d.n but I was reluctant to sponsor it
(so far) as it was only 1.0.5-x, while 1.0.6-1 just had hit sid...
But a backport should fix this issue, possible in combination with a
On Wed, 22 Oct 2014, Holger Levsen wrote:
ain't there a 5th option, providing an lxc 1.0.x backport for jessie?
You mean a backport to wheezy? Beacause the problem seems to be that if a
pre-1:1.0.6-3 (as in wheezy) lxc starts a jessie container that's using
systemd, then that wheezy lxc
On 10/22/2014 07:38 AM, Tomas Pospisek wrote:
What do you think about this solution Daniel?
if someone wants to do the work for that, sure.
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Internet:
11 matches
Mail list logo
