On 11/14/26 10:18 AM, Florian Lohoff wrote:
On Sat, Nov 14, 2026 at 09:59:49AM +0100, Sebastiaan Couwenberg wrote:
Control: tags -1 upstream moreinfo

On 11/14/26 9:02 AM, Florian Lohoff via Pkg-grass-devel wrote:
First ... thanks for maintaining tilemaker in Debian ..

The package is on life-support since Felix is not as actively involved in its 
maintenance anymore.

I am running tilemaker in a Debian/Trixie based Docker container i built myself 
every 30 minutes on a pretty small input.

As someone who actually uses the package, would you be willing to maintain the 
backport for trixie?

Although i am DD i havent maintained a package in 20? Years :) I faded away 
when i got Kids - I guess my last Debconf was Helsinki or Oslo.
And the Archs i bootstrapped (mips and mipsel) have meanwhile been removed.

Are you trying to drag me in again? :)

Yes, we need people involved in maintenance of packages they use themselves.

I'm the team's maintainer of last resort, who has increasing difficulty finding 
the motivation to work on packages I don't actually use myself.

It's completely understandable if you want to limit your involvement to just 
sharing your patches, you've already gone beyond only fixing the issue in your 
local environment.

To make your patches eligible for a stable update we'd need to confirm that the 
issues are fixed in the version (3.2.0) in testing, but reproducing race 
conditions is difficult.

If your issues are fixed in 3.2.0, ideally we'd cherry-pick the upstream fixes, 
but it's easier to just rebuild the version in testing for trixie.

Code has drastically changed in 3.2.0 so i dont think one can easily 
cherry-pick the upstream fixes.

For the 2nd race i made a pull request upstream but i had to refactor the code 
as upstream meanwhile most likely also saw crashes and fixed it
differently by using std::deqeue instead of std::vector - which does sort of 
make it a lot more unlikely but IMHO does not completely fix it.

https://github.com/systemed/tilemaker/pull/992

What do you want to happen in Debian?

It seems that the issues are already fixed in testing & unstable, although the 
second case can be made more reliable which is likely to happen in next upstream 
release after they merge your PR.

We could cherry-pick your PR for inclusion in the next upload to unstable, but 
those generally only happen to fix an RC bug, for the next upstream release, or 
shortly before the freeze, which even comes first.

We could include your patches in a stable update, but I don't want to take 
responsibility for that as I don't actually use the package myself.

Kind Regards,

Bas

--
 PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Reply via email to