[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#907135: [Box Backup] Debian now requires 2048bit RSA keys



Hi Reinhard,

I don't blame you. I think that for Debian to upgrade a package, changing a global setting, break some of its dependencies, and then kick out the resulting broken packages a month later (nearly a year before the expected release date) seems pretty harsh. In this case it took me 4.5 months to fix the issue from when you reported it to me, so unless a package has at least one full-time developer, a month simply isn't enough to fix this issue. Not even close for a hobbyist like myself.

Thanks, Chris.

On Sun, 9 Jun 2019 at 23:26, Reinhard Tartler <siretart@gmail.com> wrote:
Agreed! 

In this case, the bug was reported on Aug 24 2018 by Adrian Bunk. It was removed about a months later, namely on September 23, for failing to build from source. Four weeks is arguably quite fast. Or quite slow, depending on whom you talk to.

I probably could have reacted by disabling the test suite. Or by prodding you in those four weeks harder. Or at last have the bug fixed by end of last year, which would have left enough time to re-migrate to testing. In the future, I'll know better.

Again, sorry. I'm happy to help with getting the package to buster-backports once it opens.

-rt

On Sun, Jun 9, 2019 at 5:29 PM Chris Wilson <chris@simply-italian.co.uk> wrote:
Hi all,

It seems a bit egregious to kick out packages that were broken by a minor version upgrade in one of their dependencies (which after all is not supposed to break anything), without any warning, let alone time to fix such a complex issue properly.

I hope that Debian will consider carefully whether this course of action was really in the best interests of its users. 

Thanks, Chris. 
 
--
regards,
    Reinhard

Reply to: