[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#692465: Interested in maintenance of aiccu



Hi Jeroen,

On So 09 Jun 2013 02:24:02 CEST Jeroen Massar wrote:

On 2013-06-08 16:16, Mike Gabriel wrote:
Hi Jeroen,

as a regular user of aiccu (and a DD) I will be happy to take over
maintenance of the aiccu package.

I will also be happy to place you guys from upstream into the Uploaders:
field and train people from Sixxs in Debian packaging (and the distro
workflow) if there is the need.

There would be no need for that, as we know how Debian packaging works,
noting that we have been 'playing' with Debian since 1.2 era (heck, I
have a p200 which was upgraded from there to the current unstable ;) and
that the original Debian packaging was performed by us, and then
extended to support the debconf support by Gary Coady which we
integrated into that packaging and then somewhere along the way it
finally ended up in Debian.

Ack. Good to hear.

Please also see the note in the very bug referenced by your email:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692465#10

Yes, noted.

We still intend to do that and given some free time will come around to
doing that including a full push of that work out to
https://github.com/SixXS/aiccu but this all in due time, real life and
work has to come first.

Here I'd like to step in. I highly recommend sticking to the git-buildpackage workflow here. This means having two independent Git repositories. The first is the upstream Git project of aiccu (e.g. on Github). Upstream releases are done in this repos and tagged properly. The second repos is the Debian packaging repos. It imports your upstream releases (via uscan --force-download --rename and a proper watch file pointing to the upstream tags of aiccu on Github).

The packaging achievements can in regular intervals be adapted on the upstream repos (if you like to ship the /debian folder upstream).

Mixing upstream development and debian packaging turns aiccu into some sort of a native package which I do disrecommend, as it mixes two workflows (upstream, downstream) that should IMHO stay separate.

Greets,
 Jeroen

Greets,
Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

Attachment: pgpf9zBodw06j.pgp
Description: Digitale PGP-Unterschrift


Reply to: