Hi,
On Tue, Dec 18, 2018 at 8:33 AM Andreas Beckmann <a...@debian.org> wrote:
> Package: znc-backlog
> Version: 0.20170713-1
> Severity: serious
>
Hmm, not sure this is warranted.
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> do you really need a dependency on the exact binary version of znc
> available at the build time of znc-backlog? I.e., every time znc
> gets uploaded *or binNMUed*, a binNMU of znc-backlog is needed, too.
> Wouldn't a dependency computed from the upstream version be sufficient?
> E.g. znc (>= ${znc:upstreamversion}), znc (<< ${znc:upstreamversion}+)
>
>
I'm using the same as the znc plugins shipped by znc itself. AFAIK, the znc
ABI is not stable, so backporting an upstream patch could potentially break
other plugins.
Perhaps znc could Provide: znc-plugin-$somenumber, which could be used by
out-of-tree plugins? Adding the znc maintainers to the loop for their input
--
Saludos,
Felipe Sateler
