I think that the current 1.2.2-3 is a nice check-point. When you are not bound by maintaining patches anymore you will want to add a pyproject.toml, switch to UV-build or Flit or whatever instead of Setuptools ; and so feature creep might delay a once perfectly fine release.
Greetings Le dim. 11 oct. 2026 à 14:49, Nico Della Torre <[email protected]> a écrit : > > Hi Alexandre, > > good point. Upstream has been dead since 2020 and dh-virtualenv is a > debhelper add-on that only makes sense for building .debs, so carrying > 16 patches against a frozen tarball doesn't buy much. > > I'm happy to turn it into a native package: apply the patches to the > tree, switch to 3.0 (native), drop debian/watch and the upstream / > pristine-tar handling, and release it as 1.3. > > Would you prefer that as the first upload under the team, or should I > first upload the current patch-based 1.2.2-3 and convert afterwards? > > Thanks, > > nicoz > > Il 11/10/26 14:43, Alexandre Detiste ha scritto: > > Hi, > > > > Why even bother with patches and not turning this into a native package ? > > > > Greetings > > > > Alexandre > > > > Le dim. 11 oct. 2026 à 14:37, Nico Della Torre <[email protected]> a écrit > > : > >> The package I would like to adopt is dh-virtualenv, orphaned in #1141903: > >> ...pristine-tar, patches unapplied, managed with gbp pq... > >> > >> Upstream (spotify/dh-virtualenv) has been inactive since 2020, so the > >> fixes are carried as patches and will be forwarded upstream.
