Bug#964718: ITS: python-invoke
On 2021-03-05 08:49:03, Thomas Goirand wrote: > On 3/5/21 3:26 AM, Antoine Beaupré wrote: >> On 2020-11-22 12:44:52, Thomas Goirand wrote: >>> Hi Antoine, >>> >>> I'm sorry it took me so long to reply (I'm doing this now as part of a >>> bug triaging session). >>> >>> Please, feel free to take over the maintenance of python-invoke under >>> the DPMT. The OpenStack team no longer needs that package anyway, and it >>> may be a bit neglected as you wrote. Please just keep me as uploader. >> >> Hi! >> >> Thanks for your vote of confidence! :) >> >> I started the work here: >> >> https://salsa.debian.org/anarcat/python-invoke >> >> I'm afraid I kind of forgot about this ITS and this is likely to miss >> the freeze. I've been struggling to add autopkgtest so that it kind of >> goes under the radar, but alas, some build-deps are missing for that >> (pytest_relaxed, for one). >> >> Also, if someone in the openstack team has access to both the openstack >> project and the python team, it might be nice if they could *move* the >> repository between the two teams, so that we benefit from the nice >> GitLab redirections. > > Done. > > However, be aware that the OpenStack team uses a git tag workflow (ie: > we import the upstream git history) while the Python team uses a > pristine-tar workflow. So you may as well start from scratch (the > redirection is there though...). I'm kind of an heretic in the Python team in that i am in between: i use import-orig with an upstream source, but not pristine-tar. I did base myself on your work though. Thanks for the rename! -- The individual has always had to struggle to keep from being overwhelmed by the tribe. If you try it, you will be lonely often, and sometimes frightened. But no price is too high to pay for the privilege of owning yourself.- Friedrich Nietzsche
Bug#964718: ITS: python-invoke
On 3/5/21 3:26 AM, Antoine Beaupré wrote: > On 2020-11-22 12:44:52, Thomas Goirand wrote: >> Hi Antoine, >> >> I'm sorry it took me so long to reply (I'm doing this now as part of a >> bug triaging session). >> >> Please, feel free to take over the maintenance of python-invoke under >> the DPMT. The OpenStack team no longer needs that package anyway, and it >> may be a bit neglected as you wrote. Please just keep me as uploader. > > Hi! > > Thanks for your vote of confidence! :) > > I started the work here: > > https://salsa.debian.org/anarcat/python-invoke > > I'm afraid I kind of forgot about this ITS and this is likely to miss > the freeze. I've been struggling to add autopkgtest so that it kind of > goes under the radar, but alas, some build-deps are missing for that > (pytest_relaxed, for one). > > Also, if someone in the openstack team has access to both the openstack > project and the python team, it might be nice if they could *move* the > repository between the two teams, so that we benefit from the nice > GitLab redirections. Done. However, be aware that the OpenStack team uses a git tag workflow (ie: we import the upstream git history) while the Python team uses a pristine-tar workflow. So you may as well start from scratch (the redirection is there though...). Cheers, Thomas Goirand (zigo)
Bug#964718: ITS: python-invoke
On 2020-11-22 12:44:52, Thomas Goirand wrote: > Hi Antoine, > > I'm sorry it took me so long to reply (I'm doing this now as part of a > bug triaging session). > > Please, feel free to take over the maintenance of python-invoke under > the DPMT. The OpenStack team no longer needs that package anyway, and it > may be a bit neglected as you wrote. Please just keep me as uploader. Hi! Thanks for your vote of confidence! :) I started the work here: https://salsa.debian.org/anarcat/python-invoke I'm afraid I kind of forgot about this ITS and this is likely to miss the freeze. I've been struggling to add autopkgtest so that it kind of goes under the radar, but alas, some build-deps are missing for that (pytest_relaxed, for one). Also, if someone in the openstack team has access to both the openstack project and the python team, it might be nice if they could *move* the repository between the two teams, so that we benefit from the nice GitLab redirections. Otherwise, the Openstack repo should probably just be archived, see: https://salsa.debian.org/openstack-team/python/python-invoke/-/issues/1 Thanks! a. -- One has a moral responsibility to disobey unjust laws. - Martin Luther King, Jr.
Bug#964718: ITS: python-invoke
Hi Antoine, I'm sorry it took me so long to reply (I'm doing this now as part of a bug triaging session). Please, feel free to take over the maintenance of python-invoke under the DPMT. The OpenStack team no longer needs that package anyway, and it may be a bit neglected as you wrote. Please just keep me as uploader. Cheers, Thomas Goirand (zigo)
Bug#964718: ITS: python-invoke
Package: python3-invoke Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Python Modules People (and Fabric maintainer)! It seems that the python-invoke package is not very well maintained by the Openstack team anymore. They used to require it as a dependency, but do not anymore, which explains the lag. They do not have the interest or capacity to keep on maintaining it and the current maintainer(s) agree that the package should be moved out of the openstack umbrella. I can think of two options: 1. the invoke package is moved to team maintenance, under the DPMT umbrella 2. the current Fabric maintainer (asb, in CC), takes over the invoke package, since the two are so close to each other... It can be a combination of those two, ie. the invoke package could move under to DPMT and asb could be uploader, for example... I am also volunteering to be an uploader, but would probably also put the package under DPMT... I have already uploaded a NMU+10 for the 1.4.1 release, yesterday, along with a backport of 1.3.0 to buster... And for the record, I plan to also backport Fabric when the latter lands. I should also mention that zigo, the current invoke maintainer, is the one who suggested to move to DPMT and agrees with this salvage operation. So I guess we have already passed the 5.12.2 bar in that the salvage operation is approve. We just need to figure out who will carry this package forward from here on. Thanks! -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAl8HHZoACgkQPqHd3bJh 2XtT3Af9HuOsDJ9TFmgUjEm9NF1QqljhTGh1VGn5XFi6hARgZG9WXd/pgqSXzM7U vvTxdne4Kyl6kNtqiql4tSGuUZalhE1SrCH31TU7KD9GsNXVukD9la+X6xWsA+tp aW/NcwG4gzv8jyEKDpJF6GIBR7tdxkWd/NrD2myWVsiruecrnnEY/NmcKoZAGymj ZT+GPT+OoGthO+tLxVUiwfAEQIsPs9dL7l7n7vjeZDXo6LlmrOq6Jexb4T2Erkgc EHdKtBPROdYwHjERtQKq9PdKSFDEEiOHmVCvCZjsK3c1gh7i0qgEuU9EId9xtPI6 bgoK63UUO2tp53N71L3pD4i29/G0Yw== =DX9k -END PGP SIGNATURE-
