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. Sent from my iPhone > On 7 Jun 2019, at 22:26, Reinhard Tartler <siret...@gmail.com> wrote: > > > >> On Wed, Jun 5, 2019 at 7:46 PM Chris Wilson <chris+goo...@qwirx.com> wrote: >> Hi Reinhard, >> >> Could you have a look at this patch (documented here) to see if it's >> something like what you were hoping for? >> > > Hi Chris, > > I've uploaded this patch now to unstable, looks good, thanks for the patch. > It is still about 80k big, thoguh :-( - quite a lot to review manually. Most > of it is actually test code though! > > Unfortunately, I have bad news. I totally missed that boxbackup has already > been removed on 23 Sep 2018: > https://tracker.debian.org/news/989096/boxbackup-removed-from-testing/ > That's a bummer, because the freeze guidelines rule out migration of packages > that aren't part of testing since beginning of February (cf. > https://release.debian.org/buster/freeze_policy.html). > > Sorry about that, that's totally on me, I should have been more vocal about > this end of last year and totally dropped the ball here. > > I guess we'll have to go the backports route then. > > Best, > -rt > -- > regards, > Reinhard
