Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #10696 > unrolled thread

pyacoustid: upstream update and various packaging improvements

Started byLars Kruse <lists@sumpfralle.de>
First post2018-07-16 01:30 +0200
Last post2018-07-18 15:50 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.maint.python


Contents

  pyacoustid: upstream update and various packaging improvements Lars Kruse <lists@sumpfralle.de> - 2018-07-16 01:30 +0200
    Re: pyacoustid: upstream update and various packaging improvements Sebastian Ramacher <sramacher@debian.org> - 2018-07-18 15:50 +0200

#10696 — pyacoustid: upstream update and various packaging improvements

FromLars Kruse <lists@sumpfralle.de>
Date2018-07-16 01:30 +0200
Subjectpyacoustid: upstream update and various packaging improvements
Message-ID<wbYCJ-4Ez-1@gated-at.bofh.it>
Hello,

I am a member of the DPMT, but no DD or DM.
This is supposed to be my first package upload within the DPMT, thus please be
patient, in case I misunderstand the procedure.

My proposed changes of the package include the following:
* migrate from git-dpm to gbp
* update upstream (closing all open bugs)
* add initial autopkgtests
* updates of policy version and compat level

I prepared a merge request with my changes:
  https://salsa.debian.org/python-team/modules/pyacoustid/merge_requests/1

The git-dpm migration requires a branch renaming ("master" -> "debian/master").
The upstream update requires an update of the upstream branch.
Thus the merge request is not fully self-contained. See my forked repository for
the complete updated environment:
  https://salsa.debian.org/sumpfralle-guest/pyacoustid/

I am not sure, how to proceed now, but I could imagine the following steps:
1) someone takes the time to review my changes (maybe followed by fixes from me)
2) I push my changes (including a debian/??? version tag) to the
   packaging repository within DPMT (and delete my forked repository)
3) the reviewer sponsors the upload of the package

I am looking forward to your comments or reviews.

Cheers,
Lars

[toc] | [next] | [standalone]


#10711

FromSebastian Ramacher <sramacher@debian.org>
Date2018-07-18 15:50 +0200
Message-ID<wcV05-66L-1@gated-at.bofh.it>
In reply to#10696

[Multipart message — attachments visible in raw view] — view raw

Hi Lars

On 2018-07-16 01:25:37, Lars Kruse wrote:
> Hello,
> 
> I am a member of the DPMT, but no DD or DM.
> This is supposed to be my first package upload within the DPMT, thus please be
> patient, in case I misunderstand the procedure.
> 
> My proposed changes of the package include the following:
> * migrate from git-dpm to gbp
> * update upstream (closing all open bugs)
> * add initial autopkgtests
> * updates of policy version and compat level
> 
> I prepared a merge request with my changes:
>   https://salsa.debian.org/python-team/modules/pyacoustid/merge_requests/1
> 
> The git-dpm migration requires a branch renaming ("master" -> "debian/master").
> The upstream update requires an update of the upstream branch.
> Thus the merge request is not fully self-contained. See my forked repository for
> the complete updated environment:
>   https://salsa.debian.org/sumpfralle-guest/pyacoustid/
> 
> I am not sure, how to proceed now, but I could imagine the following steps:
> 1) someone takes the time to review my changes (maybe followed by fixes from me)
> 2) I push my changes (including a debian/??? version tag) to the
>    packaging repository within DPMT (and delete my forked repository)
> 3) the reviewer sponsors the upload of the package
> 
> I am looking forward to your comments or reviews.

Thanks for taking care of pyacoustid. I'm no longer active in the Python teams,
but as long as you follow their best practices, it should be easy enough to find
a sponsor on the Python mailing list (or via sponsorhip-requests).

Cheers
-- 
Sebastian Ramacher

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web