On Wed, Mar 06, 2013 at 10:41:05PM +0100, Daniel Baumann wrote: > On 03/06/2013 09:51 PM, Roger Leigh wrote: > >>> 3) fsck.btrfs does not support the standard fsck options > >> > >> easy fixable, but hasn't much to do with the current remaining problem > >> in sid. > > > > Yes, it does. > > no, it does not. > > even if fsck.btrfs ignores all required options, it still fails because > of sysvinits /run/rootdev. > > >>> 4) fsck.btrfs error codes > >>> > >>> I haven't tested this due to point (2) above > >> > >> me neither, but that's easy fixable too and hasn't much to do with the > >> current remaining problem in sid. > > > > Yes, it does. > > no, it does not. > > even if fsck.btrfs returns equal values, it still fails because of > sysvinits /run/rootdev.
When the /run/rootdev issue is fixed, all of the above are points of failure. Both point (2) and (3) in my original mail *are* failure points *right now*, while (4) is potential. I've personally tested (2) and (3), and they do fail. Thus fixing the /run/rootdev issue (which is really also a Btrfs bug), is only fixing the first problem. The others are just as serious. > > You broke booting with the default init system for all people using a > > btrfs rootfs. > > keep in mind that eventhough it is not desirable nor intended, bugs do > happen. also in unstable. This one was totally avoidable. It happened because you didn't do your job, and you didn't respect the code freeze. I have wasted three nights working on this now, time which I wanted to spend on fixing issues for the release, and which has instead been spent on this. And during all this time, lots of other people have been suffering the consequences of this. > unrelated to that, i would appreciate if you could calm down your tone a > bit, it is more productive that way, thank you. Err, we do have a very serious problem here. Systems will no longer boot. If I appear frustrated about the situation, it's because I am frustrated. You don't appear to be very concerned about the very real breakage caused here. Please could you answer the question in my previous email which you appear to not have addressed: What are you going to do to rectify this? Are you going to revert to the previous version? Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
