Bug#1111116: Example renderd.conf in trixie has incorrect Mapnik plugins dir

[Sebastiaan Couwenberg]

On 8/15/25 2:12 AM, Andy Townsend wrote:
> On 14/08/2025 20:56, Sebastiaan Couwenberg wrote:
>> How badly do you want to get this fixed in trixie?
> 
> The guides I've written such as https://switch2osm.org/serving-tiles/manually-building-a-tile-server-debian-12/#Configure-renderd already caveat this somewhat ("The version of Mapnik provided by Debian 12 at release was 3.1...").  I'll need to update that anyway as people may carry over their own customised renderd.conf files, the error when it is set up incorrectly has changed and the location now depends on architecture.
> 
> It'd obviously be nice if the new "renderd.conf" worked out of the box though.
> 
>> The package is on life-support since Felix stopped contributing, it would benefit from have actual users involved in its maintenance.
> 
> What actually needs to be done?  Testing and documentation I can certainly help with, but beyond that would be a challenge.

To get the issue fixed in trixie, it first needs to get fixed in testing & unstable which requires an upload.

Then the stable update need to be prepared in git, and a PU bugreport filed against release.debian.org, once that gets approved the update packages needs to be uploaded to trixie.

Your contribution would initially be most valuable if you could test the packages before they get into the next stable release, i.e. in a testing/unstable environment.

Triaging bugreports is also helpful in general, but these OSM packages only get a few due to its small userbase.

Once you get more acquainted with Debian packing you could also package new upstream releases, become a DM and/or DD and upload packages yourself, etc.

I'll have to take care of the uploads for the time being (along with stable updates), but have increasing difficulty finding the motivation to spend time on packages I don't actually use myself.

In this specific case I don't plan to upload the fixed package to unstable until the next upstream release or until it needs an upload to fix RC bugs. So it will likely take a few months before a stable update can be prepared.

Kind Regards,

Bas

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