Re: Bug#666767: libnet-dns-perl: Please build with hardening flags
Florian Hinzmann wrote (27 Jun 2012 15:26:08 GMT) :
> On Mon, 25 Jun 2012 18:13:23 +0200 intrigeri <email@example.com> wrote:
>> Do you think you will have time to consider this request before the
>> Wheezy freeze?
> Yes, I will upload a new version before the deadline.
>> I'd be happy to help as part of the Debian Perl Group.
>> What do you think?
> My wish would be to:
> - keep being the primary maintainer for libnet-dns-perl
> - allow the Debian Perl Group to upload the package if I fail to do so
> (generally, not just for this upload)
Well, technically, there's no need to "allow the Debian Perl Group to
upload the package", given any DD who is part of the Debian Perl group
may upload it already.
However, possible ways to express your intentions may be to:
- add himself to the LowThresholdNmu page:
- send an email to the list (firstname.lastname@example.org) stating
that our NMUs are welcome, when you are lagging behind
What do you think?
> - later: join the Debian Perl Group, possibly working on other
> packages, too.
You are much welcome to join us!
> I did not read about the different(?) ways the Debian Perl
> Group assigns people to packages or spreads its workload.
I don't think we have any formally described process to do so. And I'm
not part of the group for long enough to be in a good position to
describe the informal way things work.
Personally, I tend to have a look to debian/changelog and to the
Uploaders: control field, and if I see a single person in there who
appears to "be in charge", that is, is doing all the work for a while,
I'd at least ask them for a quick review before uploading.
> [...] but as my time available
> before sunday is tight I would be thankful for any reading
> recommendations for a quick start or short instructions like:
> - Make yourself an Uploader and foo-debian-perl the Maintainer.
This is exactly the idea:
Maintainer: Debian Perl Group <email@example.com>
However, I'm not sure it would be wise to do it in a hurry, before you
have read our policy and checked our workflow/toolkit suit you well.
This can wait for after the freeze, right?
> Source code is within svn/svn-buildpackage currently, I'd like to
> switch to git/git-buildpackage, though. I am happy to push the
> sources to group repositories later.
There's a takeover-for-pkg-perl.sh script in our Git repository, that
should do the right thing on this topic. When you're ready to do it,
the process is documented there, and I'm sure you will easily find one
or two of us to either do it themselves, or help you if needed along
the way: http://pkg-perl.alioth.debian.org/howto/adopt.html
> Right now I would prefer to concentrate on the jobs, which should be
> done before the freeze respective package upload.
I perfectly agree.
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc