FWIW, I tried doing a blank install with the Buster Alpha 3 installer, putting /usr on a separate LVM volume to see if Debian Buster would also be affected of this. It was not - /usr was mounted without any obvious problems during bootup. (This seems to be different from Ubuntu 18.04, but I haven't tried that install myself, only seen others failing with it when /usr was on a separate LVM volume.)
So, the severity of this is rightfully "normal". Would you like me to re-route it to the liblz4-1 package instead of lvm2? (I guess the proper fix for this would be to fix the build script for liblz4-1 so that it's build output gets packaged into /lib instead of /usr/lib) On Fri, Dec 7, 2018 at 4:57 PM Debian Bug Tracking System <ow...@bugs.debian.org> wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 915880: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915880. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > per...@gmail.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian LVM Team <pkg-lvm-maintain...@lists.alioth.debian.org> > > If you wish to submit further information on this problem, please > send it to 915...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 915880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915880 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
