Processed: Re: Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-22 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #905772 [libvirt] virtlogd dependency loop causing upgrade failures Severity set to 'normal' from 'serious' -- 905772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905772 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-22 Thread Sam Hartman
control: severity -1 normal Hi. I ran a number of other upgrades today of libvirtd from stretch to buster and was not able to reproduce the problem in the environments I thought would cause it. I don't know what's up, but I don't think characterizing this as RC given the data we have is correct.

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-17 Thread Sam Hartman
When I marked the bug RC, I thought it was happening all the time; I then went to reproduce yet again in a controlled environment to be more in a position to test a fix. That's when I discovered things are more complex. Obviously if this is a fringe situation, then it shouldn't be RC.

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-17 Thread Guido Günther
Hi, On Wed, Apr 17, 2019 at 02:47:41PM -0400, Sam Hartman wrote: > but I haven't been able to reproduce on a clean install. > It's frustrating: on my machines where I really want the upgrade to be > smoothe this bit me, but on all my toy tests, it didn't happen. > What I think may be necessary is f

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-17 Thread Sam Hartman
> "Guido" == Guido Günther writes: Guido> Hi, Guido> On Mon, Apr 15, 2019 at 02:38:27PM -0400, Sam Hartman wrote: >> control: severity -1 serious >> >> justification: libvirtd upgrades from stretch to buster break >> causing apt to fail and requiring the admin to get

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-17 Thread Guido Günther
Hi, On Mon, Apr 15, 2019 at 02:38:27PM -0400, Sam Hartman wrote: > control: severity -1 serious > > justification: libvirtd upgrades from stretch to buster break causing > apt to fail and requiring the admin to get the systemd units into a > consistent state before things can continue > > > Unfo

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-16 Thread Niels Thykier
On Mon, 15 Apr 2019 22:27:57 +0200 Guido =?iso-8859-1?Q?G=FCnther?= wrote: > Hi, > On Mon, Apr 15, 2019 at 10:18:18PM +0200, Michael Biebl wrote: > > Hi Sam > > > > Am 15.04.2019 um 20:38 schrieb Sam Hartman: > > > control: severity -1 serious > > > > > > justification: libvirtd upgrades from st

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Sam Hartman
Guido let me know if you need any help or prod me on IRC if I'm needed. Will certainly test the result, but if you get stuck would be happy to spend time on this.

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Guido Günther
Hi, On Mon, Apr 15, 2019 at 10:18:18PM +0200, Michael Biebl wrote: > Hi Sam > > Am 15.04.2019 um 20:38 schrieb Sam Hartman: > > control: severity -1 serious > > > > justification: libvirtd upgrades from stretch to buster break causing > > apt to fail and requiring the admin to get the systemd uni

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Michael Biebl
Am 15.04.19 um 22:18 schrieb Michael Biebl: > Using debhelper compat level 12, you are able to completely decouple > dh_installinit and dh_installsystemd which would give you the ability to > implement what you want afaics. From debhelper's changelog: debhelper (12.1) unstable; urgency=medium [

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Michael Biebl
Hi Sam Am 15.04.2019 um 20:38 schrieb Sam Hartman: > control: severity -1 serious > > justification: libvirtd upgrades from stretch to buster break causing > apt to fail and requiring the admin to get the systemd units into a > consistent state before things can continue > > > Unfortunately bas