On Thu, 10 Jul 2014 10:33:35 +0200 Joachim Breitner <nomeata@debian.org> wrote: > Hi, > > Am Donnerstag, den 10.07.2014, 10:31 +0200 schrieb Sven Bartscher: > > On Thu, 10 Jul 2014 09:50:38 +0200 > > Joachim Breitner <nomeata@debian.org> wrote: > > > > > Dear Sven, > > > > > > Am Mittwoch, den 09.07.2014, 23:33 +0200 schrieb Sven Bartscher: > > > > To solve this problem, I rewrote the setlocale binding with the same API > > > > under the BSD3-clause. > > > > > > thanks for that. Can you, independently of the hackage process, upload > > > that package to Debian, so that hgettext works again? I guess you’ll > > > want to leave out the Homepage field for now, to not make false > > > pretenses, but if it is API compatible there is nothing wrong with > > > Debian providing a different package, if the original one is unusable. > > > > Okay. For that reason I'm going to delete the original setlocale > > repository from alioth and upload the new package as a native package. > > Any problems with that? > > it’s not a native package just because a DD is upstream; a native Thanks for calling me DD. I'm really honoured :). > package is something that makes no sense outside of Debian (think > debian-policy). > > I recommend to stick to the usual procedure completely, just to reduce > friction. Where would you suggest to put the upstream sources until I (hopefully) can take it over at hackage? Regards Sven
Attachment:
signature.asc
Description: PGP signature