Hi,
Tarantool came up as a candidate for the Bug of the Day[1]. When
inspecting the situation I learned that the Debian packaging was held up
with a series of four Non-Maintainer Uploads[2] while your upstream
packages evolved in the Git declared as Vcs-Git[3]. This is not a good
situation for our users.
Users who install tarantool right from the Debian mirror will not profit
from your upstream development and those users who are installing by the
method suggested at your web site do not profit from the Debian update
mechanism. Both situations seem unfortunate to me,
Also bugs like
#1099946 please move away from CDBS, /usr/share/cdbs/1/class/cmake.mk is
being removed
will not be fixed properly. I intended to tackle this but it makes no
sense to me to do this in old code and I've seen that it remains inside
your packaging on Github. I did not checked whether
#1097968 ftbfs with GCC-15
is addressed or not but I want to clarify first the best way to proceed
from here.
>From my Debian biased perspective its always the best to not ship the
debian/ dir inside your upstream code and rather maintain it on
salsa.debian.org. This might ensure that some Debian developer can
serve as a sponsor of your package effectively (and I would volunteer
to do so for any first upload implementing this).
Please let me know whether I should be more verbose about this and if
you agree with this plan. I'd happily help you migrating your latest
upstream code to update the Debian package and maintain the packaging
on salsa.debian.org.
Kind regards
Andreas.
[1]
https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks#bug-of-the-day
[2] https://tracker.debian.org/pkg/tarantool
[3] https://github.com/tarantool/tarantool
--
https://fam-tille.de
