Bug#863479: perl-base should add Breaks: debconf (<< 1.5.57~)
On Wed, Jun 07, 2017 at 07:13:56PM +0100, Dominic Hargreaves wrote: > On Wed, May 31, 2017 at 12:39:57PM +0100, Dominic Hargreaves wrote: > > On Mon, May 29, 2017 at 10:16:08PM +0300, Niko Tyni wrote: > > > - update debconf in a jessie point release to minimize the impact > > > (this feels right to me, but won't help the immediate stretch upgraders) > > > > > > Cc'ing Colin. What do you think about the latter option? > > > > Agree, the third option looks correct to me, we don't have time for > > anything else. > > I'm reassigning this bug to debconf now as this seems to be the obvious > way forward. Colin, let us know if you would like a hand with preparing an > update for jessie for this. Yep, this seems like the best thing we can do in practice, and I'm sorry for taking a while to respond. I have the update ready locally and have filed #864910. -- Colin Watson [cjwat...@debian.org]
Bug#863479: perl-base should add Breaks: debconf (<< 1.5.57~)
Control: reassign -1 debconf On Wed, May 31, 2017 at 12:39:57PM +0100, Dominic Hargreaves wrote: > On Mon, May 29, 2017 at 10:16:08PM +0300, Niko Tyni wrote: > > On Sat, May 27, 2017 at 03:42:14PM +0200, Julien Cristau wrote: > > > On Sat, May 27, 2017 at 16:36:50 +0300, Adrian Bunk wrote: > > > > > > Package: perl-base > > > > Version: 5.24.1-2 > > > > > > Technically #786705 is just a harmless warning, but when > > > > during a jessie -> stretch upgrade perl-base is upgraded > > > > before debconf is upgraded the user might see a lot scary > > > > warnings as if something was seriously broken. > > > > > > > [...] > > > > > > > > perl-base should add a Breaks: debconf (<< 1.5.57~). > > > > > > Adding Breaks in a core package a couple of weeks before the release > > > sounds like a very, very, very bad idea. > > > > Indeed it seems too late in the cycle for this. > > > > Other possible solutions that come to mind: > > > > - silence the warnings during maintainer scripts, much like > > > > https://sources.debian.net/src/perl/5.24.1-2/debian/patches/debian/squelch-locale-warnings.diff/ > > (but it's late for even this IMO) > > > > - update debconf in a jessie point release to minimize the impact > > (this feels right to me, but won't help the immediate stretch upgraders) > > > > Cc'ing Colin. What do you think about the latter option? > > Agree, the third option looks correct to me, we don't have time for > anything else. I'm reassigning this bug to debconf now as this seems to be the obvious way forward. Colin, let us know if you would like a hand with preparing an update for jessie for this. Cheers, Dominic.
Bug#863479: perl-base should add Breaks: debconf (<< 1.5.57~)
On Mon, May 29, 2017 at 10:16:08PM +0300, Niko Tyni wrote: > On Sat, May 27, 2017 at 03:42:14PM +0200, Julien Cristau wrote: > > On Sat, May 27, 2017 at 16:36:50 +0300, Adrian Bunk wrote: > > > > Package: perl-base > > > Version: 5.24.1-2 > > > > Technically #786705 is just a harmless warning, but when > > > during a jessie -> stretch upgrade perl-base is upgraded > > > before debconf is upgraded the user might see a lot scary > > > warnings as if something was seriously broken. > > > > > [...] > > > > > > perl-base should add a Breaks: debconf (<< 1.5.57~). > > > > Adding Breaks in a core package a couple of weeks before the release > > sounds like a very, very, very bad idea. > > Indeed it seems too late in the cycle for this. > > Other possible solutions that come to mind: > > - silence the warnings during maintainer scripts, much like > > https://sources.debian.net/src/perl/5.24.1-2/debian/patches/debian/squelch-locale-warnings.diff/ > (but it's late for even this IMO) > > - update debconf in a jessie point release to minimize the impact > (this feels right to me, but won't help the immediate stretch upgraders) > > Cc'ing Colin. What do you think about the latter option? Agree, the third option looks correct to me, we don't have time for anything else. Cheers, Dominic.
Bug#863479: perl-base should add Breaks: debconf (<< 1.5.57~)
On Sat, May 27, 2017 at 03:42:14PM +0200, Julien Cristau wrote: > On Sat, May 27, 2017 at 16:36:50 +0300, Adrian Bunk wrote: > > Package: perl-base > > Version: 5.24.1-2 > > Technically #786705 is just a harmless warning, but when > > during a jessie -> stretch upgrade perl-base is upgraded > > before debconf is upgraded the user might see a lot scary > > warnings as if something was seriously broken. > > > [...] > > > > perl-base should add a Breaks: debconf (<< 1.5.57~). > > Adding Breaks in a core package a couple of weeks before the release > sounds like a very, very, very bad idea. Indeed it seems too late in the cycle for this. Other possible solutions that come to mind: - silence the warnings during maintainer scripts, much like https://sources.debian.net/src/perl/5.24.1-2/debian/patches/debian/squelch-locale-warnings.diff/ (but it's late for even this IMO) - update debconf in a jessie point release to minimize the impact (this feels right to me, but won't help the immediate stretch upgraders) Cc'ing Colin. What do you think about the latter option? -- Niko Tyni nt...@debian.org
Bug#863479: perl-base should add Breaks: debconf (<< 1.5.57~)
Control: severity -1 wishlist Control: tag -1 moreinfo On Sat, May 27, 2017 at 16:36:50 +0300, Adrian Bunk wrote: > Package: perl-base > Version: 5.24.1-2 > Severity: serious > > Technically #786705 is just a harmless warning, but when > during a jessie -> stretch upgrade perl-base is upgraded > before debconf is upgraded the user might see a lot scary > warnings as if something was seriously broken. > [...] > > perl-base should add a Breaks: debconf (<< 1.5.57~). Adding Breaks in a core package a couple of weeks before the release sounds like a very, very, very bad idea. Cheers, Julien
Bug#863479: perl-base should add Breaks: debconf (<< 1.5.57~)
Package: perl-base
Version: 5.24.1-2
Severity: serious
Technically #786705 is just a harmless warning, but when
during a jessie -> stretch upgrade perl-base is upgraded
before debconf is upgraded the user might see a lot scary
warnings as if something was seriously broken.
Example with debconf 1.5.56 and perl-base 5.24.1-2 installed:
# apt-get install libpam-modules
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libpam-modules-bin
The following packages will be upgraded:
libpam-modules libpam-modules-bin
2 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B/412 kB of archives.
After this operation, 18.4 kB disk space will be freed.
Do you want to continue? [Y/n]
Unescaped left brace in regex is deprecated, passed through in regex; marked by
<-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked by
<-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line
30.
Preconfiguring packages ...
(Reading database ... 10801 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.1.8-3.5_amd64.deb ...
Unpacking libpam-modules-bin (1.1.8-3.5) over (1.1.8-3.1+deb8u2) ...
Setting up libpam-modules-bin (1.1.8-3.5) ...
(Reading database ... 10801 files and directories currently installed.)
Preparing to unpack .../libpam-modules_1.1.8-3.5_amd64.deb ...
Unescaped left brace in regex is deprecated, passed through in regex; marked by
<-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked by
<-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line
30.
Unpacking libpam-modules:amd64 (1.1.8-3.5) over (1.1.8-3.1+deb8u2) ...
Setting up libpam-modules:amd64 (1.1.8-3.5) ...
Installing new version of config file /etc/security/namespace.init ...
Processing triggers for man-db (2.7.6.1-2) ...
#
perl-base should add a Breaks: debconf (<< 1.5.57~).
