On Thu, Sep 14, 2017 at 02:23:33PM +0200, Balint Reczey wrote:
> That's great. If you push it to collab-maint I would happily check it and
> step-in as a co-maintainer if you are looking for one.
https://anonscm.debian.org/git/collab-maint/znc-push.git
Yes, if you step in as comaintainer I'd gladly see it uploaded with my
name on it.
I didn't want to uplaod something with the issue below and then be alone
in dealing with it.
> > One annoyance of znc extensions is that znc upstream recommends to
> > rebuild them for the version of znc they are going to run with. That
> > means that I had to go to extra lenghts to make sure it's installable
> > only with the same znc version it was compiled with.
>
> 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.
Feel free to take it over from where I left.
--
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