Run on Bullseye to use pyproj as recommended.

[wscherphof]

Omschrijving

Mapproxy warns in the log that we should use pyproj. Pyproj requires proj >=7.2, which is proj-bin on Bullseye, while on Buster, it's 5.2.

Type verandering

• Verbetering oude feature

Checklist:

• [v] Ik heb de code in deze PR zelf nogmaals nagekeken
• [v] Ik heb mijn code beter achtergelaten dan dat ik het aantrof
• [v] De code is leesbaar en de moeilijke onderdelen zijn voorzien van commentaar
• [v] Ik heb de tests toegevoegd/uitgebreid indien nodig
• [v] Ik heb de tests gedraaid die de werking van mijn wijziging bewijst
• [v] De PDOK documentatie is bijgewerkt indien nodig.
• [v] Er zit geen gevoelig informatie in deze PR (wachtwoorden etc)

[WouterVisscher]

Hi @wscherphof, thanks for the pull request
We recently created a PR for Mapproxy regarding Azure blobstore mapproxy/mapproxy#608
When mapproxy has new release (tag) we will include your PR for a new release of the PDOK/Mapproxy

[roelarents]

bookworm (current debian stable) has proj 9.1. Also fine?
https://packages.debian.org/source/stable/proj

Also, we use our common lighttpd image now for mapproxy. So we'll have to upgrade there and also test other uses of that image (e.g. mapserver).

[wscherphof]

I'm not sure why mapproxy recommends pyproj. Can't really answer your question. Op di 11 jul. 2023 11:41 schreef Roel Arents ***@***.***>:

…

bookworm (current debian stable) has proj 9.1. Also fine? https://packages.debian.org/source/stable/proj — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFCQPSSY4IKXNIOMD7WXVDXPUNVJANCNFSM6AAAAAAUBU7KAI> . You are receiving this because you were mentioned.Message ID: ***@***.***>