Bug#930551: nmu: znc-backlog_0.20180824-1
Hi,
On Sat, Jun 15, 2019 at 12:43:29PM +0200, Ivo De Decker wrote:
> Hi,
>
> On Sat, Jun 15, 2019 at 12:20:10PM +0200, Salvatore Bonaccorso wrote:
> > Apparently, cf. #916764 znc-backlog has quite strict dependency
> > relations to znc, so once znc is updated, znc-backlog needs a rebuild.
> >
> > Can you please schedule binNMU's for znc-backlog? (This will need as
> > well to move to testing, as znc itself got an unblock to fix
> > CVE-2019-12816).
> >
> > nmu znc-backlog_0.20180824-1 . ANY . unstable . -m "Rebuild against 1.7.2-3"
>
> Scheduled and unblocked.
Thank you, much appreciated so we can get the znc fixes into buster!
> Obviously this will also be an issue if there are security updates for znc
> once buster is stable.
Yes even worse, if a DSA would be needed, then znc-backlog would need
a sourcefull upload (the first time) because of the schedule binNMU in
security archive issue.
> I'm wondering if it wouldn't be better if znc-backlog was just built by
> src:znc. There is only a single znc plugin, and it's very small, so having the
> overhead of this mini-transition for every znc update seems excessive.
Right, that or having the #917222 implemented, but guess in any case
that's now to late for buster.
maintainers of both packages CC'ed.
Salvatore
Reply to: