Hi Andreas,
On Thu, Apr 04, 2024 at 02:32:45PM +0200, Andreas Tille wrote:
Hi,
in the light of the previous discussion I have a question to all voters.
Due to bug #1066377 more than 30 testing removal warnings hit my mailbox today (I stopped counting after 30). While the Debian Med package
clustalo is the only package that's responsible for this due to its Build-Dependency from libargtable2-dev there is quite some dependency
tree inside Debian Med team also affecting packages relevant for
COVID-19 etc. This small lib is not a key package which is important
for all things I'm writing below. Its used as Build-Depends by 6 other packages.
Our always busy team member �tienne Mollier provided a patch 10 days ago (thanks again �tienne). The package had its last maintainer Upload
-- Shachar Shemesh <[email protected]> Sat, 16 Jul 2016 20:45:15 +0300
(Shachar in CC) and a NMU
-- Holger Levsen <[email protected]> Fri, 01 Jan 2021 17:15:04 +0100
(reproducible build, no changes - in other words no problems since
2016). However, the BTS view of Sanchar might hinting for some
inactivity when looking at two RC bugs in other packages:
#965787 privbind: Removal of obsolete debhelper compat 5 and 6 in bookworm
#998987 [src:privbind] privbind: missing required debian/rules targets build-arch and/or build-indep
As I wrote to Marc here on this list also the explicit hint to Shachar:
Its not about blaming you - I just want to analyse the current situation
to act properly. Given that you had no capacity to respond to two bugs
that are RC since 2 years makes me wonder how long I need to wait for
your OK to a team upload I'm proposing below. I'm perfectly aware that
we as volunteers can't be blamed about those things. I simply want to
find new ways how to deal with those situations appropriately.
There is the possilbity to salavage the packagei [1], but that of course will only work if the person agrees to take over maintainance and add their name to Uploaders: or Maintainer: [2].
The package can be put into a team's umbrella at the ITS time. This
does not need an explicit OK, though the maintainer can veto.
[1]
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
https://wiki.debian.org/PackageSalvaging
[2] This is a feature, the ITS procedure has been designed exactly that
way, to avoid that people just do an upload and drop the package
immediatly afterwards, as this will likely only upset the current
maintainer without long-term benefits to the package - kind of to
avoid the reaction Marc predicted.
If taking over the maintaince is not the goal, remember NMU allow
one to fix almost every bug, also wishlist bugs are regularily in
scope. And bugs can be filed, if needed.
Some Background story:
https://lists.debian.org/debian-devel/2018/07/msg00453.html
--
tobi
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmYO6poACgkQkWT6HRe9 XTbE5A/+KsA54CrxWANE4/OMQ3GrcnvcT72YkpbYg59Cox0/GIOsX/P0N+OVz4qy K5ca66K3trzeo0eEZZwH+OvKW4+fc4x7Gs9ZwssiJSmqNkKslUJ1mHzok8PbgEEu AjmVFcCy0vXsn5fS/3DzNUbmJeuJFWZcng0zsxEWGgK0fklyXTdHdgb1w5Kb5OIy jBolndACur1o1rpBejASwznWflKT6O4HWm7ECw2J9/cIeq0s1l3FFxamk585B3U9 QV+voYEYqPrU9HBhJGa6HlJpD7gq9rHPYVS/foCY+viYawO3F4gwsxUP5+d8nx/2 fmgcOJrj0K+TPXO+HeZrCU5jdx7xXj/ilFxtQHVq/63ZarDwTzquCWiSYESgc5OG zh2Jv95BRis0vzNPqSje3aOcX00fiXYsibT1iBhUOqz8GwRtJOy+as0x/QwoTfG3 eM2Gi0I9uRXCuD/ZlQkKcvR8t4odM8KJ7zIMi8RnJid+/1dS110aDIspqSwvvn3a pYOaZ/Z47XXTFDNkvoxh3p2vjQUxZumENo3g9Wq91BBrn/xMqP9YzCHLCOYEp46A sHLaZMc4w+gcN5tRasOq5bcYDOZgyeBe0a9ANIrsPZvA1KHrnVCLSiprozZfQAUM AggWB1rfWDcd1umQYMZrEFaM7uLCyzODHHEWzdoXHm/aGzdeuR4=
=hSVq
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)