On Thu, Sep 14, 2017 at 04:32:22PM +0200, Mattia Rizzolo wrote:
> > That's something i could live with. Maybe znc upstream will start stabilizing
> > API/ABI after some time and we can have more relaxed dependencies.
>
> See the following commits for what I'm talking about:
> https://anonscm.debian.org/git/collab-maint/znc-push.git/commit/?id=0de616a06fac00ddf38d4a6e34f500d47efd3162
> https://anonscm.debian.org/git/collab-maint/znc-push.git/commit/?id=474fb1f4ca8f62d8fbcd54fdb3b96488913dacc5
>
> The last one is probably not OK for unstable, as locking it that way
> would prever binNMUs to be enough after new ZNC uploads.
> The first commit, I've done it that way, but could also be done with
> e.g.
> Depends: znc (>> ${zncver})
> Breaks: znc (<< ${zncver}+)
> if you think it would be somewhat better.
That's not even good enough: I was running with znc 1.6.5-1~bpo8+1 from
jessie-backports and the version tagged as
debian/1.0.0+git20170403.dcb1939-1 built in a jessie-bpo chroot.
Today I upgraded to stretch, so with znc 1.6.5-1; the breaks on the
znc-push package allowed coinstallation, but znc segfaulted at startup,
until I did a rebuild in a stretch chroot of the same thing (and bumped
the version because I want to call me sane, see the -2 tag).
> Feel free to take it over from where I left.
It would be great if whoever picks it up could take care of these
incompatibilities.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature