Control: severity -1 critical Hi Michael,
On Wed, 06 Feb 2019 14:33:34 +0100 Johannes Schauer <jo...@debian.org> wrote: > Quoting Michael Stone (2019-02-06 14:22:10) > > On Wed, Feb 06, 2019 at 10:47:12AM +0100, Johannes Schauer wrote: > > >On Wed, 30 Jan 2019 12:07:37 +0100 Jonas Smedegaard <d...@jones.dk> wrote: > > >> Jus a friendly nudge: It would be great if this bug was fixed in time for > > >> Buster. > > >> > > >> Do you think you can find the time to have a look at the patches > > >> provided by Josch? > > >> > > >> Do you need some help? > > > > > >another week passed since Jonas' email. And more than seven weeks since > > >your > > >last activity in this bug. Unfortunately, fakechroot is not really usable > > >without mv(1). The mv(1) tool is used in apt and dash postinst maintainer > > >scripts, so this also affects debootstrap and mmdebstrap and thus in turn > > >also > > >packages using these tools. > > > > > >I thus hereby announce my intention to NMU coreutils with my two patches > > >in one > > >week (February 13) and a delay of 10 days (then in unstable by February > > >23). > > > > > >Please speak up if you are not okay with that plan. > > > > I'm not ok with that plan. > > what is your opinion about this bug and my proposed patch? > > What do you think would be the best way forward? Again, more than a week passed since my last message. You manage to reply within hours when it's about dismissing my offers to fix this bug in coreutils but when it is about explaining your reasoning you stay silent for weeks. Maybe my patch has a fatal flaw in it, maybe you want us to work together differently, maybe you want to fix the problem yourself (as indicated by your message "please just wait") or maybe I was missing something essential which makes my patch completely unacceptable. But so far you only left 9 words of text in this bug report offering no explanation at all. This is honestly very frustrating for me. :( I'm now raising the severity of this bug to "critical" because this bug "makes unrelated software on the system break" -- in this case it directly breaks fakechroot and it indirectly breaks the software using fakechroot. In case you do not agree with this severity level, please explain why you think that this bug is not RC even though it leads to another package becoming nearly unusable. Thanks! cheers, josch
signature.asc
Description: signature
