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
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:
> >
>
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, b
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
> >
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
>
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.
6 matches
Mail list logo