Re: backport python-astropy for jessie?
Hi Leo and Andreas,
Am 26.01.2017 um 09:05 schrieb Andreas Tille:
> On Thu, Jan 26, 2017 at 08:51:20AM +0100, Ole Streicher wrote:
>> In principle, you now just need a sponsor, and discuss the remaining
>> things (if any) with him. I don't want to do this myself, since I never
>> did a backport myself, and so I don't have the experiences of the
>> possible pitfalls here. I put Andreas and Steffen into Cc:, maybe they
>> could have a look and sponsor these packages for the first time. Once
>> they are there, I have no problem to set the maintainer-allowed flag for
>> the packages so that you can maintain the backports directly yourself.
>
> I have not checked Debian Astro policy but for dealing with backports in
> Git repositories I'd recommend to follow what we agreed upon in Debian
> Med:
>
> https://debian-med.alioth.debian.org/docs/policy.html#backports
>
> I admit I'm not very motivated to sponsor backports. I somehow need to
> draw a line what I can do and what not. However, I'd recommend to read
> the backport guidelines. As far as I remember its not necessary to be
> a DD but rather to get accepted by the backport team.
We don't have a specific policy for Debian Astro and mainly use the
Debian Science policy as a guide (and I insist in using git). So, it
would probably wise to follow Debian-Meds guide to put the backports
into a "jessie-backports" branch of the reporitories, and to follow
https://backports.debian.org/Contribute/
Leo, maybe you could ask on the backports mailing list for a first
sponsorship/upload? After this is done, I give you the upload rights for
all backported packages.
Best regards
Ole
Reply to: