On Sun, May 05, 2019 at 09:55:41AM +0200, Bastian Blank wrote:
> On Sun, May 05, 2019 at 12:12:00AM +0100, Colin Watson wrote:
> > > I also ran into this on upgrading from stretch to buster. Fortunately I
> > > was keeping enough of an eye on console output from the upgrade that I
> > > was able
Hi Colin
On Sun, May 05, 2019 at 12:12:00AM +0100, Colin Watson wrote:
> > I also ran into this on upgrading from stretch to buster. Fortunately I
> > was keeping enough of an eye on console output from the upgrade that I
> > was able to find this bug and I worked around it as you describe here.
On Sat, May 04, 2019 at 06:59:22PM +0100, Colin Watson wrote:
> On Fri, Jan 18, 2019 at 03:16:26AM +0100, Andreas Bombe wrote:
> > This has worked for all these years until the update, which rejects the
> > VG with system ID without advance warning during package upgrade. Systems
> > may become
On Fri, Jan 18, 2019 at 03:16:26AM +0100, Andreas Bombe wrote:
> This has worked for all these years until the update, which rejects the
> VG with system ID without advance warning during package upgrade. Systems
> may become unbootable after upgrade if these VGs contain filesystems
> that are
Package: lvm2
Version: 2.03.02-1
Severity: important
There are possibly 2 different bugs in here, please clone as needed.
This computer has multiple VGs and had last been updated on Dec 13
before I ran an update on Jan 13. After this update it wouldn't complete
boot because one VG would not be
5 matches
Mail list logo
