[Slackbuilds-users] Updates - 20240120.1

[Willy Sudiarto Raharjo]

> Hi Willy, I took the slackbuild of osm2pgsql because orphanized for a 
> long time, but the latest release supports only 64-bit architectures. So 
> I sumitted osm2pgsql-legacy (new) that is the same slackbuild of 
> Benjamin Trigona-Harany update to the latest release compatible also 
> with 32-bit architectures (version 1.9.2). This slackbuild will remain 
> as is without any update in the future, whereas osm2pgsql should be 
> updated for any new release (with 32-bit unsupported).
> 
> I submitted also the new osm2pgsql update for version 1.10.0 (the 
> latest) but something was wrong because it does not appears in the 
> updates. The current osm2pgsql is still at the version of Benjamin 
> (1.4.2) that is older than the legacy version (updated to 1.9.2). Why is 
> it lost? the build has ben tested in current and 15.0 stable updated 
> with the patches, both sbopkglint and sbolint returned OK and the 
> tarball submitted has remained for a few days in pending, but not 
> appeared in the approved list. No reports by admins I received about it, 
> so I don't know if there is issues.
> 
> Do I have to send again the same tarball?
> 
> PS: if it is useful, a copy of the updated version of osm2pgsql is 
> available in my github repository: 
> https://github.com/giandex/slackbuilds.org/tree/main/gis/osm2pgsql

My bad
i commented that it was merged, but i didn't merged the PR
https://github.com/SlackBuildsOrg/slackbuilds/pull/4594

it's already pushed to my branch now, so it will be shown in the next 
update.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240121/29d7af4d/attachment.asc>