Hi, On Thu, Jun 22, 2017 at 11:09:43PM +0200, Rene Engelhard wrote: > It basically boils down just to > > $ cat debdiff | filterdiff -i '*debian*' > diff -Nru xmlsec1-1.2.23/debian/changelog xmlsec1-1.2.24/debian/changelog > --- xmlsec1-1.2.23/debian/changelog 2016-12-15 21:09:18.000000000 +0100 > +++ xmlsec1-1.2.24/debian/changelog 2017-06-22 18:54:56.000000000 +0200 > @@ -1,3 +1,10 @@ > +xmlsec1 (1.2.24-0.1) unstable; urgency=medium > + > + * Non-maintainer upload > + * New upstream release (closes: #865539) > + > + -- Rene Engelhard <r...@debian.org> Thu, 22 Jun 2017 18:54:56 +0200 > + > xmlsec1 (1.2.23-0.1) unstable; urgency=medium > > * Non-maintainer upload. > > OK, one might want to run the tests (see #774631) but that also can be done > later... > > Used ratt to rebuild the 3 r-deps against 1.2.24 and they succeeded.
It occurred to me that you probably can't upload anyway since your key is 1024 and probably removed from the keyring. What do you think of putting xmlsec1 under the umbrealla of the Debian XML/SGML Group which also maintains other XML related packages: https://qa.debian.org/developer.php?login=debian-xml-sgml-p...@lists.alioth.debian.org If you agree I would change Maintainer:, and add you and me to Uploaders: (if you still want to be co-maintainer) Otherwise I probably would NMU it relatively quickly, since LO 5.4.0 will be released end of July and we have waited so long to be able to ditch the internal copy of libxmlsec that it would be a pity to not (be able to) just do it :) Regards, Rene
