On 12/23/18 8:04 PM, Antonio Valentino wrote: > Just a question: pylibtiff already has a repository on salsa > (https://salsa.debian.org/debian/pylibtiff). > Should I just push all branches to the new one or it is better to move > tho old one?
Pushing all branches & tags to the new repo should suffice, and updating the packaging accordingly of course. >>> Regarding pylibtiff, it already has a git repository but probably it >>> would be better to move it under debian-gis. >>> In any case I will wait for an OK before changing the #705208 into an ITA. >> >> Is the communication to adopt pylibtiff public somewhere? I don't see >> anything on [email protected] in the last three months. >> >> Following the procedure documented in the devref should suffice: >> >> >> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#adopting > > You are right, there is no communication yet. > I have never done it before. > If my understanding of the procedure is correct I should send a mail to > Debian QA Group <[email protected]> (that is the current maintainer > of the package) and to #705208 declaring my intention to adopt the package. > Than I should change the title of #705208 replacing "O" with "ITA" and > reassign the #705208 to myself. > Is it correct? That's correct, except that you won't reassign #705208, you will claim it by setting yourself as the owner: https://www.debian.org/Bugs/server-control#owner Also note that wnpp documentation linked in devref 5.9.5 mentions "To actually adopt the package, upload it with your name in its Maintainer: field" which is not entirely correct for team maintained packages where the Maintainer field uses the team address and Uploaders field the actual person. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
