[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-12-02 Thread Launchpad Bug Tracker
[Expired for lxc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lxc (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-12-02 Thread Launchpad Bug Tracker
[Expired for lxc (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: lxc (Ubuntu Xenial) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-10-03 Thread Robie Basak
Mirroring the development release's Incomplete status in Xenial - see comment 15. ** Changed in: lxc (Ubuntu Xenial) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-09-30 Thread Jon Grimm
Marked Vivid and Wily as Won't Fix as EOL releases. ** Changed in: lxc (Ubuntu Vivid) Status: Confirmed => Won't Fix ** Changed in: lxc (Ubuntu Wily) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

Re: [Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-04-25 Thread Serge Hallyn
If you have reproduced this recently, please show us exactly how and on what version of lxc. This should have been fixed as of commits 3b392519: lxcapi_clone: restore the unexpanded config len and 5eea90e8: clone: clear the rootfs out of unexpanded config for github issue 694. status

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu Wily) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-04-25 Thread Rolf Leggewie
** Changed in: lxc (Ubuntu) Importance: Undecided => High ** Changed in: lxc (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu Vivid) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-02-18 Thread Stéphane Graber
** No longer affects: lxc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1285850 Title: interuppting lxc-clone can destroy source container Status in lxc package in Ubuntu:

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-01-07 Thread Serge Hallyn
This was fixed by commit 5eea90e8505d9f336bb28379d8575be159fdd2e1, it was github issue http://github.com/lxc/lxc/issues/694. It needs to be SRUd somewhat urgently. ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-01-07 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1285850 Title: interuppting lxc-clone can destroy source container Status in lxc: Triaged Status in lxc

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-01-07 Thread Serge Hallyn
Should also need fix in trusty-backports The fix will come in 1.1.6. ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided