On 29 July 2013 16:55, Klaus Ethgen <kl...@ethgen.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hello, > > Am Mo den 29. Jul 2013 um 16:00 schrieb Dmitrijs Ledkovs: >> Both btrfs and fsck.btrfs are now unconditionally included in the >> initramfs, and thus should be available on your system to boot & mount >> '/' and '/usr'. Together with the ongoing work to mount and fsck '/' >> and '/usr' from initramfs, you should have less problems booting going >> into the future. > > Not really as I use no initrd on all of my systems at all. (Well, on > some very few I use it but this an other story.) >
I see. That's fine. Without or without initrd, I agree this is a valid bug and should be fixed. >> It is unfortunate that lzo2 is not installed into >> /lib/, I will request the maintainer of that package to do so, by >> reassigning the bug there. > > Well, btrfs-tools was not depending on lzo2 before and now it depends on > it. So it is still a bug and still a grave one breaking the debian > policy. Sorry to say this. > Sure. I'll provide a patch to fix the issue in the liblzo2 package, unless maintainer does it before me. I understand that btrfs is the cause for the bug affecting two package, with a correct fix, IMHO, going into lzo2 package to move library into /lib/. Not sure what is the correct way to express this in BTS. > Is the liblzo2 really needed by btrfs fsck? Or could that tool be > compiled without the need for this library? > To support / check compressed btrfs filesystems, yes. And the general debian policy is to enable all/most options. I wouldn't want to disable lzo2 support, you may wish to either statically link fsck.btrfs or compile without lzo2 if you don't use that feature. https://btrfs.wiki.kernel.org/index.php/Compression Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
