|
Hello Jeroen,
thanks for the input, actually the repository is in pretty bad shape, build artifacts were committed to master and the upstream tags are not matching the upstream repository at all (maybe someone rewrote history at some point), given that, would it be ok if I just overwrite the branches to have them clean?
From: Jeroen Ploemen
Sent: Thursday, September 11, 2025 7:40 AM To: Gabriel Barrantes Cc: debian-python@lists.debian.org Subject: Re: RFS: dj-database-url -- Django utility to utilize a DB env var (Python 3) On Tue, 2 Sep 2025 17:50:38 +0000
Gabriel Barrantes <gabriel.barrantes.dev@outlook.com> wrote: > Hello, > I am adopting the package dj-database-url per bug #986931, I am > requesting a sponsor to upload the package. > > https://mentors.debian.net/package/dj-database-url/ hi Gabriel, since you set the maintainer to the Python team and there was a sponsorship request on the team's IRC channel, it looks like you want this to be a team package. If so, you will need to move the package's git repository from its current location in the Debian group to the Python team repo at [0]. You won't have sufficient access rights to execute this move yourself (and neither do I), so you'll have to open a support ticket for this with the salsa overlords at [1]. Once that move is complete, enable the CI on salsa and push your changes to team repo; as a team member, you will have write access to the repository, eliminating the need for merge requests. Once things look good, send your sponsorship request to the team's main discussion list or add it to the topic on #debian-python IRC channel (OFTC network). A quick glance at your work as uploaded to mentors didn't show any major issues, just some minor stuff: * copyright: LICENSE file gives 'Kenneth Reitz & individual contributors' as the upstream copyright holders. * d/tests: in its current form the custom autopkgtest only does a simple module import for the default python version only, basically duplicating in a bad way what "Testsuite: autopkgtest-pkg-python" already provides. Please remove the current d/tests directory. * control: the package could gain a non-trivial autopkgtest simply by setting Testsuite to 'autopkgtest-pkg-pybuild' instead of -python, which would run the full upstream testsuite in an autopkgtest context. * control: VCS fields need to point to the team repo. [0]https://salsa.debian.org/python-team/packages/ [1]https://salsa.debian.org/salsa/support |