Bug#944099: CVE-2019-14433 / OSSA-2019-003: buster-pu: package nova/2:18.1.0-6 -> 18.1.0-6+deb10u1

To: Thomas Goirand <zigo@debian.org>, 944099@bugs.debian.org
Subject: Bug#944099: CVE-2019-14433 / OSSA-2019-003: buster-pu: package nova/2:18.1.0-6 -> 18.1.0-6+deb10u1
From: Julien Cristau <jcristau@debian.org>
Date: Sat, 23 Nov 2019 18:09:47 +0100
Message-id: <[🔎] 20191123170947.GA6173@tomate.cristau.org>
Reply-to: Julien Cristau <jcristau@debian.org>, 944099@bugs.debian.org
In-reply-to: <[🔎] 157286483228.14443.11314232019216025750.reportbug@zbuz.infomaniak.ch>
References: <[🔎] 157286483228.14443.11314232019216025750.reportbug@zbuz.infomaniak.ch> <[🔎] 157286483228.14443.11314232019216025750.reportbug@zbuz.infomaniak.ch>

Control: tag -1 moreinfo

On Mon, Nov 04, 2019 at 11:53:52AM +0100, Thomas Goirand wrote:
> We would like to update Nova in Buster for 2 reasons. First, there's
> OSSA-2019-003 / CVE-2019-14433 which we would like to fix. Second,
> in non-interactive mode, upgrading Nova can lead to some configuration
> changes, which is an RC bug.
> 
This doesn't sound like it should require new debconf templates.  What's
the logic there?  Why does upgrading touch the configuration at all?

Cheers,
Julien

Reply to:

Follow-Ups:
- Bug#944099: CVE-2019-14433 / OSSA-2019-003: buster-pu: package nova/2:18.1.0-6 -> 18.1.0-6+deb10u1
  - From: Thomas Goirand <zigo@debian.org>

References:
- Bug#944099: CVE-2019-14433 / OSSA-2019-003: buster-pu: package nova/2:18.1.0-6 -> 18.1.0-6+deb10u1
  - From: Thomas Goirand <zigo@debian.org>

Prev by Date: Processed: Re: Bug#944099: CVE-2019-14433 / OSSA-2019-003: buster-pu: package nova/2:18.1.0-6 -> 18.1.0-6+deb10u1
Next by Date: Bug#944348: buster-pu: package schleuder/3.4.0-2+deb10u1
Previous by thread: Processed: Re: Bug#944099: CVE-2019-14433 / OSSA-2019-003: buster-pu: package nova/2:18.1.0-6 -> 18.1.0-6+deb10u1
Next by thread: Bug#944099: CVE-2019-14433 / OSSA-2019-003: buster-pu: package nova/2:18.1.0-6 -> 18.1.0-6+deb10u1
Index(es):
- Date
- Thread