Le 04/06/2024 à 17:38, Vaclav Petras a écrit :
Thanks Even. This is not clear to me. I see OSGeo/grass enabled. I
can't manage that because it says that it is managed by another user
of my org. Screenshot attached.
yeah, just after I posted my message, I refreshed the page and GRASS
Hi,
see below. I also see in https://zenodo.org/account/settings/github/
that the OSGeo/GRASS repository is disabled. I suspect it needs to be
turned on again, otherwise the next GRASS release will probably lack a
Zenodo record
Even
Message transféré
Sujet : Re:
Hi,
this is quite typical of a program linking to 2 different version of
libproj at the same time, often when mixing repositories, where some
components of one haven't been rebuilt against updated components of the
other one
Check the output of "ldd /path/to/g.proj"
Even
Le 24/04/2024 à
FYI I see this thread referencing the GDAL github team organization. As
far as I know, nobody has "designed" it with deep thoughts. It has the
current structure most likely as an accident of history... If I were to
design it, I would keep it simple and stupid. With git workflows, the
concept
