Bug#930551: marked as done (nmu: znc-backlog_0.20180824-1)
Your message dated Sat, 15 Jun 2019 12:43:29 +0200
with message-id <20190615104327.roxsyrfcwjwqk2hg@debian.org>
and subject line Re: nmu: znc-backlog_0.20180824-1
has caused the Debian Bug report #930551,
regarding nmu: znc-backlog_0.20180824-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
930551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930551
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
Hi
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"
Thanks for your work!
Regards,
Salvatore
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
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.
Obviously this will also be an issue if there are security updates for znc
once buster is stable.
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.
Ivo
--- End Message ---
Reply to: