From jebrhansen+SBo at gmail.com  Mon Jan  1 01:00:17 2024
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 31 Dec 2023 17:00:17 -0800
Subject: [Slackbuilds-users] xmlsec download link has moved
In-Reply-To: <cb2deb897395d31b60ace630a853c3ef@compukix.net>
References: <cb2deb897395d31b60ace630a853c3ef@compukix.net>
Message-ID: <CANi9qSv0EOtRKRuX=ikuweNk9eg8hu_zFtuAsug+4SvftwgYOg@mail.gmail.com>

On Sun, Dec 31, 2023, 2:27?PM Jason Graham <jgraham at compukix.net> wrote:

> The download link for the SBo xmlsec version is now in older-releases
> download folder:
> https://www.aleksey.com/xmlsec/download/older-releases/xmlsec1-1.2.38.tar.gz
> .
>
> Best,
> Jason
>

Releases are also available on GitHub, which might be the better option if
the website is changing folders of older releases.

https://github.com/lsh123/xmlsec/releases

Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20231231/bab7183e/attachment.htm>

From slackbuilds at schoepfer.info  Mon Jan  1 12:21:11 2024
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 01 Jan 2024 13:21:11 +0100
Subject: [Slackbuilds-users] Please remove vala-12
Message-ID: <ec3d0f6cf7c9a210299ff7672b6c4c4b@schoepfer.info>

Hi,

http://slackbuilds.org/repository/15.0/development/vala-12/
is not used by anything on SBo, i think it should be removed.

Johannes

From j at lngn.net  Tue Jan  2 06:50:54 2024
From: j at lngn.net (Jay Lanagan)
Date: Tue, 02 Jan 2024 01:50:54 -0500
Subject: [Slackbuilds-users] I need a uid/gid for a SlackBuild
Message-ID: <2c48b59f0a5f6f4655860f60614482bc@lngn.net>

Hey all,

I've been working on a SlackBuild for 'greetd' as a initial greeter to 
be passed along to a graphical greeter 'nwg-hello' (which also has a 
impending SlackBuild), but for the greetd package, I need a uid/gid 
assigned for my uses. Last I checked UDI/GID '381' was the next 
available, and I'd like the user/group to be 'greeter'.

https://slackware.lngn.net/pub/source/greetd/
https://slackware.lngn.net/pub/source/nwg-hello/
(these scripts are "under construction", please don't just willy-nilly 
install them, they aren't quite right yet).

I've a few things to change yet on each, so I plan to submit for this 
week, but I'd like to secure the UID/GID in advance.

Thanks all, and Happy New Year!

--
Jay Lanagan

From rworkman at slackbuilds.org  Tue Jan  2 07:11:32 2024
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 2 Jan 2024 01:11:32 -0600
Subject: [Slackbuilds-users] I need a uid/gid for a SlackBuild
In-Reply-To: <2c48b59f0a5f6f4655860f60614482bc@lngn.net>
References: <2c48b59f0a5f6f4655860f60614482bc@lngn.net>
Message-ID: <20240102011132.3a780346@home.rlworkman.net>

On Tue, 02 Jan 2024 01:50:54 -0500
Jay Lanagan via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:

> Hey all,
> 
> I've been working on a SlackBuild for 'greetd' as a initial greeter
> to be passed along to a graphical greeter 'nwg-hello' (which also has
> a impending SlackBuild), but for the greetd package, I need a uid/gid 
> assigned for my uses. Last I checked UDI/GID '381' was the next 
> available, and I'd like the user/group to be 'greeter'.
> 
> https://slackware.lngn.net/pub/source/greetd/
> https://slackware.lngn.net/pub/source/nwg-hello/
> (these scripts are "under construction", please don't just
> willy-nilly install them, they aren't quite right yet).
> 
> I've a few things to change yet on each, so I plan to submit for this 
> week, but I'd like to secure the UID/GID in advance.
> 
> Thanks all, and Happy New Year!


Done.  Happy new year to you as well!

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240102/ffbe2b62/attachment.asc>

From dev at iotib.net  Wed Jan  3 00:56:12 2024
From: dev at iotib.net (Charadon)
Date: Wed, 3 Jan 2024 00:56:12 +0000
Subject: [Slackbuilds-users] www.eterna.com.au is gone
Message-ID: <643a17de-ae30-43cf-8161-d6360d183297@iotib.net>

Hey all, I was trying to install bozohttpd when I noticed that 
www.eterna.com.au was down/gone.

Aside from bozohttpd, this also means that ircII won't build either.

If the mirror is replaced, I recommend using NetBSD's pkgsrc distfiles 
located here: http://ftp.netbsd.org/pub/pkgsrc/distfiles/ as it has the 
source tarballs there. Either that, or archive.org would work.


From willysr at slackbuilds.org  Wed Jan  3 03:16:42 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 3 Jan 2024 10:16:42 +0700
Subject: [Slackbuilds-users] www.eterna.com.au is gone
In-Reply-To: <643a17de-ae30-43cf-8161-d6360d183297@iotib.net>
References: <643a17de-ae30-43cf-8161-d6360d183297@iotib.net>
Message-ID: <b0e26efa-55a4-4d46-88d2-6b1cfbc9a753@slackbuilds.org>

> Hey all, I was trying to install bozohttpd when I noticed that 
> www.eterna.com.au was down/gone.
> 
> Aside from bozohttpd, this also means that ircII won't build either.
> 
> If the mirror is replaced, I recommend using NetBSD's pkgsrc distfiles 
> located here: http://ftp.netbsd.org/pub/pkgsrc/distfiles/ as it has the 
> source tarballs there. Either that, or archive.org would work.

Fixed on my branch and on SBo server

-- 
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/20240103/e083b205/attachment.asc>

From josiahb at gmail.com  Wed Jan  3 22:26:44 2024
From: josiahb at gmail.com (Josiah Boothby)
Date: Wed, 3 Jan 2024 14:26:44 -0800
Subject: [Slackbuilds-users] relinquishing scripts (e16, e16-themes, fmit,
 rfk, skulpture)
Message-ID: <CABEGoxJqz0xTMxwrjZzBn_sV1d2rm0PpF3Ap6QvCeFA6xE3i=w@mail.gmail.com>

All my scripts are available to new and loving homes!

I am no longer able to be a sufficiently diligent maintainer for e16 and
its themes, would like someone else to take these over:

desktop/e16
desktop/e16.theme.pack

I am willing to continue to maintain rfk but would relinquish this if
someone wants it:

games/robotfindskitten

The following should be removed unless anybody wants to take over
maintainership:

audio/fmit
desktop/skulpture

?Josiah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240103/288738fc/attachment.htm>

From urchlay at slackware.uk  Wed Jan  3 22:38:26 2024
From: urchlay at slackware.uk (B. Watson)
Date: Wed, 3 Jan 2024 17:38:26 -0500 (EST)
Subject: [Slackbuilds-users] relinquishing scripts (e16, e16-themes, fmit,
 rfk, skulpture)
In-Reply-To: <CABEGoxJqz0xTMxwrjZzBn_sV1d2rm0PpF3Ap6QvCeFA6xE3i=w@mail.gmail.com>
References: <CABEGoxJqz0xTMxwrjZzBn_sV1d2rm0PpF3Ap6QvCeFA6xE3i=w@mail.gmail.com>
Message-ID: <f221f365-f1af-4bd0-3b2-d064d132beb@slackware.uk>



On Wed, 3 Jan 2024, Josiah Boothby wrote:

> All my scripts are available to new and loving homes!

Sad to hear that...

> audio/fmit

I'll take fmit, I was the last one to touch it anyway (version updated
it in Feb 2022).

From urchlay at slackware.uk  Wed Jan  3 22:43:28 2024
From: urchlay at slackware.uk (B. Watson)
Date: Wed, 3 Jan 2024 17:43:28 -0500 (EST)
Subject: [Slackbuilds-users] relinquishing scripts (e16, e16-themes, fmit,
 rfk, skulpture)
In-Reply-To: <CABEGoxJqz0xTMxwrjZzBn_sV1d2rm0PpF3Ap6QvCeFA6xE3i=w@mail.gmail.com>
References: <CABEGoxJqz0xTMxwrjZzBn_sV1d2rm0PpF3Ap6QvCeFA6xE3i=w@mail.gmail.com>
Message-ID: <e45d5a70-269a-d1e6-7fc4-77229f92274@slackware.uk>



On Wed, 3 Jan 2024, Josiah Boothby wrote:

> audio/fmit

For fmit, do you mind if I change the license? I prefer WTFPL for my scripts.

From josiahb at gmail.com  Wed Jan  3 22:57:11 2024
From: josiahb at gmail.com (Josiah Boothby)
Date: Wed, 3 Jan 2024 14:57:11 -0800
Subject: [Slackbuilds-users] relinquishing scripts (e16, e16-themes, fmit,
 rfk, skulpture)
In-Reply-To: <e45d5a70-269a-d1e6-7fc4-77229f92274@slackware.uk>
References: <CABEGoxJqz0xTMxwrjZzBn_sV1d2rm0PpF3Ap6QvCeFA6xE3i=w@mail.gmail.com>
 <e45d5a70-269a-d1e6-7fc4-77229f92274@slackware.uk>
Message-ID: <CABEGoxL0s9rne_96YfaW31arU4Rnoox8nmWxi01rs1FSkb2_ag@mail.gmail.com>

No objection from me...please do as you will!

On Wed, Jan 3, 2024 at 2:43?PM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Wed, 3 Jan 2024, Josiah Boothby wrote:
>
> > audio/fmit
>
> For fmit, do you mind if I change the license? I prefer WTFPL for my
> scripts.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240103/e08620ab/attachment.htm>

From urchlay at slackware.uk  Wed Jan  3 23:07:43 2024
From: urchlay at slackware.uk (B. Watson)
Date: Wed, 3 Jan 2024 18:07:43 -0500 (EST)
Subject: [Slackbuilds-users] relinquishing scripts (e16, e16-themes, fmit,
 rfk, skulpture)
In-Reply-To: <CABEGoxL0s9rne_96YfaW31arU4Rnoox8nmWxi01rs1FSkb2_ag@mail.gmail.com>
References: <CABEGoxJqz0xTMxwrjZzBn_sV1d2rm0PpF3Ap6QvCeFA6xE3i=w@mail.gmail.com>
 <e45d5a70-269a-d1e6-7fc4-77229f92274@slackware.uk>
 <CABEGoxL0s9rne_96YfaW31arU4Rnoox8nmWxi01rs1FSkb2_ag@mail.gmail.com>
Message-ID: <2679e4b-5882-a8b2-f2ce-4cc4b5cb88bc@slackware.uk>



On Wed, 3 Jan 2024, Josiah Boothby wrote:

> No objection from me...please do as you will!

Many thanks.

From szycha at gmail.com  Thu Jan  4 10:44:18 2024
From: szycha at gmail.com (Marcin Szychowski)
Date: Thu, 4 Jan 2024 11:44:18 +0100
Subject: [Slackbuilds-users] [Slackware-15.1] Building virt-viewer with
 meson 0.61+
Message-ID: <CAJZww4iZxeWd3D4r_UMh=kXWEMtmxUPMy2CA+wXtpVvJQns=Tg@mail.gmail.com>

Hi,

As of now, Slackware 15.0 is using meson-0.59.x, since it has been reverted
from 0.60 two years ago:

    +--------------------------+
    Sun Oct 31 19:59:15 UTC 2021
    d/meson-0.59.3-x86_64-1.txz:  Upgraded.
      Reverted to a version that works better for us. Thanks to nobodino.


Meanwhile in order to build virt-viewer on -current, a patch similar to
this one from Gentoo project needs to be applied:

https://gitweb.gentoo.org/repo/gentoo.git/tree/app-emulation/virt-viewer/files/virt-viewer-10.0_p20210730-meson-0.61.patch

Please find attached patch that modifies the .SlackBuild and adds the above
patch as well for your convenience.  Feel free to use it for 15.1 ;-)

-- 
Pozdrawiam,
Marcin Szychowski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240104/edb5a93d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: slackware-current-virt-viewer-meson-0.61-or-newer.patch
Type: text/x-patch
Size: 2257 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240104/edb5a93d/attachment.bin>

From tonus1 at free.fr  Thu Jan  4 10:50:50 2024
From: tonus1 at free.fr (Tonus)
Date: Thu, 4 Jan 2024 11:50:50 +0100
Subject: [Slackbuilds-users] python packages needing new setuptools
Message-ID: <nys2nxm7jwixc7qq4igkt7rkxfqflphsc3inyv2l3xss5rx7u7@2zlg676kypr2>

Hi all,

Just came accross an error in a python package I maintain.
A module would not be detected. While using `pip check` I found 
following problems as well :

```
sphinx 4.5.0 has requirement importlib-metadata>=4.4, but you have importlib-metadata 0.0.0.
pytest-timeout 2.1.0 has requirement pytest>=5.0.0, but you have pytest 0.0.0.
importlib-metadata 0.0.0 has requirement zipp>=0.5, but you have zipp 0.0.0.
build 1.0.3 has requirement importlib-metadata>=4.6; python_version < "3.10", but you have importlib-metadata 0.0.0.
```

Using python3-setuptools-opt solved the problem for holidays module.

Il will put maintainers in copy of this mail (not sure for pytest).

Best wishes for this new year

-- 
Regards,

Tonus

From j at lngn.net  Fri Jan  5 13:18:02 2024
From: j at lngn.net (Jay Lanagan)
Date: Fri, 5 Jan 2024 08:18:02 -0500
Subject: [Slackbuilds-users] I need a uid/gid for a SlackBuild
In-Reply-To: <20240102011132.3a780346@home.rlworkman.net>
References: <2c48b59f0a5f6f4655860f60614482bc@lngn.net>
 <20240102011132.3a780346@home.rlworkman.net>
Message-ID: <C7C23D66-518F-4A40-85E5-2846E984F177@edison.tech>

      
  

 Heya,
  

  
I had a look at the uid_gid.txt in the website and noticed a typo in the addition. The uid/gid is to be named ?greeter? but the package is ?greetd? which is falsely listed as ?greeter? as well. The slackbuild has been submitted as of yesterday, but obviously isn?t live yet (pending approval) so there?s still time for corrections either way.   
  

  
Thanks,
  
  
  
? Jay Lanagan
  
  
  

  
  
>   
> On Jan 2, 2024 at 2:11 AM,  <Robby Workman (mailto:rworkman at slackbuilds.org)>  wrote:
>   
>   
>   
>  On Tue, 02 Jan 2024 01:50:54 -0500 Jay Lanagan via SlackBuilds-users  <slackbuilds-users at slackbuilds.org>  wrote:  >  Hey all,  >   >  I've been working on a SlackBuild for 'greetd' as a initial greeter  >  to be passed along to a graphical greeter 'nwg-hello' (which also has  >  a impending SlackBuild), but for the greetd package, I need a uid/gid  >  assigned for my uses. Last I checked UDI/GID '381' was the next  >  available, and I'd like the user/group to be 'greeter'.  >   >  https://slackware.lngn.net/pub/source/greetd/  >  https://slackware.lngn.net/pub/source/nwg-hello/  >  (these scripts are "under construction", please don't just  >  willy-nilly install them, they aren't quite right yet).  >   >  I've a few things to change yet on each, so I plan to submit for this  >  week, but I'd like to secure the UID/GID in advance.  >   >  Thanks all, and Happy New Year! Done. Happy new year to you as well! -RW  
>
>   
  
  
     
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240105/2d6f2fda/attachment-0001.htm>

From willysr at slackbuilds.org  Fri Jan  5 14:22:56 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 5 Jan 2024 21:22:56 +0700
Subject: [Slackbuilds-users] python packages needing new setuptools
In-Reply-To: <nys2nxm7jwixc7qq4igkt7rkxfqflphsc3inyv2l3xss5rx7u7@2zlg676kypr2>
References: <nys2nxm7jwixc7qq4igkt7rkxfqflphsc3inyv2l3xss5rx7u7@2zlg676kypr2>
Message-ID: <2bf43620-a491-42ea-9ad0-7e2bcbcbe834@slackbuilds.org>

> Just came accross an error in a python package I maintain.
> A module would not be detected. While using `pip check` I found 
> following problems as well :
> 
> ```
> sphinx 4.5.0 has requirement importlib-metadata>=4.4, but you have 
> importlib-metadata 0.0.0.
> pytest-timeout 2.1.0 has requirement pytest>=5.0.0, but you have pytest 
> 0.0.0.
> importlib-metadata 0.0.0 has requirement zipp>=0.5, but you have zipp 
> 0.0.0.
> build 1.0.3 has requirement importlib-metadata>=4.6; python_version < 
> "3.10", but you have importlib-metadata 0.0.0.
> ```
> 
> Using python3-setuptools-opt solved the problem for holidays module.
> 
> Il will put maintainers in copy of this mail (not sure for pytest).

https://git.slackbuilds.org/slackbuilds/commit/?id=d69fac608
https://git.slackbuilds.org/slackbuilds/commit/?id=1d31a47d6

-- 
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/20240105/4b7f3c18/attachment.asc>

From willysr at slackbuilds.org  Sat Jan  6 01:47:31 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Jan 2024 08:47:31 +0700
Subject: [Slackbuilds-users] Updates - 20240106.1
Message-ID: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>

Happy new year 2024 to everyone

We start 2024 with a strong start with over 200+ commits
Some people were wondering about the new workflow and find their 
submission were not in pending/ready list, so i'll give some brief 
explanation behind the new workflow.

So basically we utilize Github to perform semi automatic CI checking on 
all submissions (new or updates) by making a pull request. In order to 
avoid double PR when we send another batch of new submissions, we have 
to move the tarball (in /pending) to another place so that's why people 
can't find them in /pending anymore. Once it's approved, it will be 
listed in /ready as usual. In the meantime, you can see the progress in 
github https://github.com/SlackBuildsOrg/slackbuilds/pulls

Please note that all new submission MUST be submitted via normal 
submisison form in order to get it populated in the database during 
public update. Updates to existing scripts can be done in both ways (via 
Github PR or Gitlab MR or normal submission form).

have a nice weekend


Sat Jan  6 01:09:44 UTC 2024
academic/AstroImageJ: Fix permission.
academic/fet: Updated for version 6.15.0.
academic/gerbv: Updated for version 2.7.0.
academic/gwyddion: Updated for version 2.65.
academic/rpy2: Update to version 3.5.15
academic/wcalc: Added (scientific calculator).
audio/SongRec: Updated for version 0.3.3.
audio/ario: Fix HOMEPAGE and DOWNLOAD URLs.
audio/clap: Updated for 1.1.10
audio/fdk-aac: Script cleanup
audio/fmit: New maintainer, fix issues.
audio/gvolwheel: Updated for version 1.0.3.
audio/libfreeaptx: Script cleanup.
audio/mpc: Fix Doc.
audio/mpc: Updated for version 0.35
audio/yabridge: Updated for version 5.1.0
desktop/adwaita-qt: Updated for version 1.4.2.
desktop/calcure: Updated for version 3.0.1.
desktop/disper: Updated for version 0.3.1.1, new maint.
desktop/e16: Remove /usr/share/doc.
desktop/e16: Update MD5SUM.
desktop/e16: Updated for version 1.0.29.
desktop/foot: Fix MD5SUM.
desktop/gsimplecal: Update for 2.5.1 (+new maintainer)
desktop/lxqt-panel: Do not install files that conflict with lxqt-menu-data
desktop/lxqt-panel: Update README and SlackBuild
desktop/mint-l-icons: Updated for version 1.6.7.
desktop/mint-l-theme: Updated for version 1.9.6.
desktop/nwg-hello: Added (GTK3-based greeter).
desktop/nwg-shell-config: Updated for version 0.5.30
desktop/nwg-shell: Updated for version 0.5.25
desktop/qtile: Update README and slack-desc
desktop/xfce4-docklike-plugin: Updated for version 0.4.2.
development/SQLAlchemy: Updated for version 1.4.51.
development/Sphinx: Updated for version 5.3.0.
development/bashdb: Fix HOMEPAGE URL.
development/bfg: Updated for version 1.14.0.
development/cargo-vendor-filterer: Build fixes.
development/d-tools: Updated for version 2.106.1
development/decklink-sdk: Updated for version 12.7
development/dmd: Updated for version 2.106.1
development/github-desktop: Updated for 3.3.6 Build 3
development/godot: Added (Game Engine).
development/gtest: Updated for version 1.14.0.
development/hugo: Updated for version 0.121.2.
development/icon: Updated for version 9.5.23a
development/jupyter-nbclient: Update for 0.9.0
development/jupyter-nbconvert: Update for 7.13.1
development/jupyter-nbformat: Update for 5.9.2
development/jupyter_events: Update .info - remove unnecessary DEPs
development/jupyter_server: Update for 2.10.0
development/jupyter_server_terminals: Update for 0.5.0
development/jupyterlab_pygments: Update README
development/neovim: Updated for version 0.9.5.
development/noweb: Updated for version 2.13
development/pycharm: Fix email.
development/python3-numpy: Updated for version 1.26.3
development/python3-spyder-kernels: Update for 2.5.0
development/ratfor: Added (rational fortran).
development/sbcl: Remove INSTALL.
development/sbcl: Updated for version 2.4.0
development/sonarqube: Updated for version 10.3.0.82913.
development/spyder: Update for 5.4.0 (+new maintainer)
development/universal-ctags: Updated for version 6.1.0
development/vala-12: Removed (No longer needed).
development/vstudio: Updated for version 13.7.
development/xxd-standalone: Updated for version 9.1.0006.
development/xxdiff: Update to build against Qt5
development/zulu-openjdk11: Updated for version 11.0.21.
development/zulu-openjdk17: Updated for version 17.0.9.
development/zulu-openjdk8: Updated for version 8.0.392.
games/blupimania: Added (new port of an old Blupi game).
games/blupimania: Fix 32bit build.
games/brutalchess: Fix HOMEPAGE and DOWNLOAD URLs.
games/minetest_game: Updated for version 5.8.0.
games/principia: Added (physics-based sandbox game).
games/robotfindskitten: Updated for version 2.8284271.702.
games/scummvm: Updated for version 2.8.0
games/zod-engine: Update script & email.
gis/libspatialite: Fix profiling references to build path
gis/osgEarth: Updated for version 3.5
gis/python3-basemap: Updated for version 1.3.9.
graphics/MaterialX: Added (Open standard for computer graphics).
graphics/OpenCASCADE: Handle latest VTK version
graphics/hugin: Updated for version 2023.0.0.
graphics/paraview: Updated for version 5.11.2
graphics/vuescan: Updated MD5SUMs.
graphics/vuescan: Updated for version 9.8.23.
graphics/xdot: Updated for version 1.3
ham/gridtracker: Updated for version 1.23.1226.
ham/qlog: Updated for version 0.31.0.
haskell/haskell-emojis: Updated for version 0.1.3.
haskell/haskell-indexed-traversable-instances: Updated for 0.1.1.1.
haskell/haskell-text-conversions: Updated for version 0.3.1.1.
haskell/haskell-unicode-collation: Updated for version 0.1.3.6.
libraries/Ipopt: Updated for version 3.14.13.
libraries/VTK: Updated for version 9.3.0
libraries/asio: Fix url
libraries/asio: Updated for 1.28.2
libraries/bitsery: Updated for version 5.2.3
libraries/botocore: Updated for version 1.34.11.
libraries/cloog: Change email.
libraries/dcmtk: Updated for version 3.6.8
libraries/function2: Remove test to avoid build failure.
libraries/function2: Updated for version 4.2.3
libraries/ghc_filesystem: Updated for version 1.5.14
libraries/goffice: Apply patch for 686.
libraries/libfdk-aac: Updated for version 2.0.3
libraries/libfm-qt: Update for 1.4.0
libraries/libmpdclient: Fix Doc.
libraries/libmpdclient: Updated for version 22.2
libraries/libpano13: Updated for version 2.9.22.
libraries/libqtpas: Updated for version 2.9.
libraries/tomlplusplus: Updated for version 3.4.0
libraries/vst3sdk: Updated for version 3.7.9
libraries/wxpdfdoc: Added (Generate PDF Documents).
multimedia/jellyfin-bin: Updated to 10.8.13
multimedia/opera-ffmpeg-codecs: Updated for version 0.83.0.
multimedia/pipe-viewer: Fix broken patch.
multimedia/rav1e: Updated for version 0.7.0.
multimedia/vokoscreenNG: Updated for version 4.0.0.
network/awscli: Updated for version 1.32.11.
network/bozohttpd: Update source URL.
network/brave-browser: Updated for version 1.61.114.
network/dnscrypt-proxy: Updated for version 2.1.5
network/emailrelay: Updated for version 2.5.1.
network/ip2location-c: Updated for version 8.6.1.
network/ipv6calc: Updated for version 4.1.0.
network/lighttpd: Updated for version 1.4.73.
network/mod_evasive: Fix DOWNLOAD url.
network/opera: Updated for version 106.0.4998.28.
network/packETH: Updated for version 3.0.
network/signal-desktop: Updated for version 6.43.1.
network/spice: Updated for version 0.15.2.
network/synergy: Updated for version 1.14.6.19
network/teamviewer: Updated for version 15.49.2.
network/telegram: Updated for version 4.14.2.
network/tixati: Updated for version 3.19_1.
network/unbound: Update script.
network/vivaldi: Updated for version 6.5.3206.50.
network/x11spice: Updated for version 20230803_33a9af7.
office/calibre-bin: Updated for version 7.3.0.
office/pdftk: Fix email address within .info
office/pyspread: Updated for version 2.2.3.
python/Flask: Updated for version 3.0.0.
python/PyGreSQL: Updated for version 6.0
python/coverage: Updated for version 7.4.0.
python/feedparser: Updated for version 6.0.11
python/holidays: Update DEP.
python/holidays: Updated for version 0.40.
python/jellyfish: Build fixes.
python/kitchen: Added (Useful code).
python/python-mysql-replication: Updated for version 1.0.5.
python/python2-netaddr: Updated for version 0.10.1
python/python3-Flask-Dance: Updated for version 7.0.1.
python/python3-Flask-Security-Too: Updated for version 5.3.3.
python/python3-construct: Fix email address
python/python3-cookiecutter: Update for 2.5.0
python/python3-django: Updated for version 4.2.9.
python/python3-docstring-to-markdown: Fix email address
python/python3-exiv2: Fix email address
python/python3-fastjsonschema: Update for 2.19.1
python/python3-hatch-nodejs-version: Update for 0.3.2
python/python3-hatch_fancy_pypi_readme: Updated for version 24.1.0.
python/python3-lsp-server: Update for 1.6.0
python/python3-maturin: Build fixes.
python/python3-overrides: Update for 7.4.0
python/python3-patsy: Update for 0.5.5
python/python3-prometheus_client: Update for 0.19.0
python/python3-pydantic-core: Build fixes.
python/python3-pykeepass: Fix email address
python/python3-pylint-venv: Update for 3.0.3
python/python3-pyzmq: Updated for version 25.1.2
python/python3-qtawesome: Update for 1.3.0
python/python3-shtab: Orphan maintenance of python3-shtab
python/python3-statsmodels: Update for 0.14.1
python/python3-textdistance: Update for 4.6.1
python/python3-tomlkit: Update for 0.12.3
python/s3transfer: Updated for version 0.10.0.
python/sphinxcontrib-applehelp: Updated for version 1.0.7, new maintainer.
python/sphinxcontrib-devhelp: Updated for version 1.0.5, new maintainer.
python/sphinxcontrib-htmlhelp: Updated for version 2.0.4, new maintainer.
python/sphinxcontrib-jsmath: New maintainer.
python/sphinxcontrib-qthelp: Updated for version 1.0.6, new maintainer.
python/sphinxcontrib-serializinghtml: Updated for version 1.1.9, new 
maintainer.
python/taskw: Added (python taskwarrior api).
python/terminado: Update for 0.18.0
python/tzdata: Updated for version 2023.4.
python/werkzeug: Updated for version 3.0.1.
ruby/rubygem-native-package-installer: Updated for version 1.1.9.
ruby/rubygem-parallel: Updated for version 1.24.0.
ruby/rubygem-parser: updated for version 3.2.2.4.
system/B-em: Updated for version e624e51.
system/FontAwesome: Update for 6.5.1 (+new maintainer)
system/Iosevka-aile: Updated for version 28.0.3.
system/Iosevka-etoile: Updated for version 28.0.3.
system/Iosevka-slab: Updated for version 28.0.3
system/Iosevka: Updated for version 28.0.3
system/dool: Added (fork of dstat).
system/edk2-ovmf: Updated for version 202311.
system/fish: Updated for version 3.7.0.
system/fonts-kannada-extra: Updated for version 1.2.
system/fonts-tamil-libre: Updated for version 1.4.
system/fzf: Updated for version 0.45.0.
system/greetd: Added (minimal and flexible login manager daemon).
system/greetd: Avoid writing to $HOME/.cargo.
system/greetd: Fix rc.4.greetd ownership.
system/greetd: Handle content-disposition filenames.
system/lxqt-config: Add lxqt-menu-data dependency
system/nomarch: update email address.
system/pcmanfm-qt: Update for 1.4.0
system/sarasa-gothic: Updated for version 1.0.2.
system/slackrepo-hints: Updated for version 20240105.
system/ttf-nerd-fonts-symbols: Added (system font).
system/usbview: Updated for version 3.1
system/virtualxt: Fix 32bit lib dir.
system/virtualxt: Fix github tarball handling.
system/virtualxt: Updated for version 0.11.
system/worker: Remove INSTALL.
system/worker: Updated for version 5.0.0
system/xstow: Updated for version 1.1.0.
+--------------------------+


-- 
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/20240106/4d026437/attachment.asc>

From slack at giand.it  Sat Jan  6 12:51:18 2024
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=)
Date: Sat, 6 Jan 2024 13:51:18 +0100
Subject: [Slackbuilds-users] Update for latest ITK
Message-ID: <e0915815-008a-4325-a8fe-129f13250315@giand.it>

Happy new year to all

since the orphanized ITK has remained outdated for a long time, I 
decided to try the upgrade of the slackbuild, although KB_Sbo proposed 
himself as new maintainer.

I've just submitted the update for the latest release of Insight 
Toolkit, but if KB_Sbo would take it can do it at any time. The 
slackbuild requires possible improvements and/or implementations as 
including the support to some system dependencies instead of the build 
of internal static libraries or possible extensions to optional deps (I 
found and added dcmtk for example).

greetings

Giancarlo

-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it

Slackware Linux... because it works!
*********************************************************


From bocke at slackware-srbija.org  Sun Jan  7 11:45:32 2024
From: bocke at slackware-srbija.org (Bojan Popovic)
Date: Sun, 7 Jan 2024 12:45:32 +0100
Subject: [Slackbuilds-users] Using Web Archive links for the sites and
 downloads that are not available anymore?
Message-ID: <7deca795-8826-572f-5c3e-3907ea661a78@slackware-srbija.org>

Hi!

I was nudged by your recent maintainer status "call-out" to update a few 
of my scripts. I found out that download link for ancient X Bitmap 
browser is not available anymore. Someone of good people from mod team 
backed-up the source at an alternative location (Thank you!).

I was just trying to see if the original is still available via Internet 
Archive's "Web Archive" and it is. Should in these cases (when there is 
an archived version at IA) maybe try and post IA links instead?

The last version of the web page that contian XbmBrowser is from 2019:

https://web.archive.org/web/20190910064117/http://www.ict.griffith.edu.au/anthony/software/

Bojan.



From urchlay at slackware.uk  Sun Jan  7 17:19:18 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 7 Jan 2024 12:19:18 -0500 (EST)
Subject: [Slackbuilds-users] Using Web Archive links for the sites and
 downloads that are not available anymore?
In-Reply-To: <7deca795-8826-572f-5c3e-3907ea661a78@slackware-srbija.org>
References: <7deca795-8826-572f-5c3e-3907ea661a78@slackware-srbija.org>
Message-ID: <eec0fff7-cbec-bc61-c716-8a9969846952@slackware.uk>



On Sun, 7 Jan 2024, Bojan Popovic wrote:

> I was just trying to see if the original is still available via Internet 
> Archive's "Web Archive" and it is. Should in these cases (when there is an 
> archived version at IA) maybe try and post IA links instead?
>
> The last version of the web page that contian XbmBrowser is from 2019:
>
> https://web.archive.org/web/20190910064117/http://www.ict.griffith.edu.au/anthony/software/

I'd say yes, use the IA link.

It's better to have the DOWNLOAD hosted somewhere besides
slackware.uk, if possible, because slackware.uk is also where the SBo
source archive is hosted.

While you're at it, you could use the IA copy of the site as HOMEPAGE,
since the current version of the page doesn't mention xbmbrowser
at all.

From ewfalor at gmail.com  Mon Jan  8 23:43:46 2024
From: ewfalor at gmail.com (Erik Falor)
Date: Mon, 8 Jan 2024 16:43:46 -0700
Subject: [Slackbuilds-users] Question about rolling source packages and
 version numbers
Message-ID: <CAKwJTQ5yEuvO9XFKQpUdeYmmpDGacaNbgYY_NAp0WAnPLUr=vg@mail.gmail.com>

Hi all,

LuaJIT uses rolling releases. There are no release tarballs available for
download.  Instead of manual increments for each release, the build process
uses the POSIX time stamp of the latest commit as the release number of the
semantic version.

The full version number is in the format `$major.$minor.$timestamp`.  For
instance, the latest SlackBuild I'm preparing has this version number:
2.1.1703358377.

One can download a tarball of a specific commit from their GitHub mirror[1].
Because they aren't given tags with the version number, you have to refer to
them by the commit ID:

https://github.com/LuaJIT/LuaJIT/archive/c525bcb9024510cad9e170e12b6209aedb330f83/LuaJIT-c525bcb9024510cad9e170e12b6209aedb330f83.tar.gz

Of course, this means that the tarball expands to a subdirectory that
contains
the commit ID instead of a version number in its name.

I can reconcile this by adding the $REVISION variable to the SlackBuild:

PRGNAM=luajit
REVISION=${REVISION:-c525bcb9024510cad9e170e12b6209aedb330f83}
VERSION=${VERSION:-2.1.1703358377}

Is this a satisfactory solution, or has this problem been solved in a
better way
by another maintainer?


[1] https://github.com/LuaJIT/LuaJIT

-- 
Erik Falor
Registered Linux User #445632 http://counter.li.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240108/d304b950/attachment.htm>

From jebrhansen+SBo at gmail.com  Mon Jan  8 23:53:48 2024
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 8 Jan 2024 18:53:48 -0500
Subject: [Slackbuilds-users] Question about rolling source packages and
 version numbers
In-Reply-To: <CAKwJTQ5yEuvO9XFKQpUdeYmmpDGacaNbgYY_NAp0WAnPLUr=vg@mail.gmail.com>
References: <CAKwJTQ5yEuvO9XFKQpUdeYmmpDGacaNbgYY_NAp0WAnPLUr=vg@mail.gmail.com>
Message-ID: <CANi9qSuj=G0ESV8hq+g3cX9HjJb1UpcCCm=MHHiUyZ16PS7wPg@mail.gmail.com>

On Mon, Jan 8, 2024, 6:44?PM Erik Falor <ewfalor at gmail.com> wrote:

> Hi all,
>
> LuaJIT uses rolling releases. There are no release tarballs available for
> download.  Instead of manual increments for each release, the build process
> uses the POSIX time stamp of the latest commit as the release number of the
> semantic version.
>
> The full version number is in the format `$major.$minor.$timestamp`.  For
> instance, the latest SlackBuild I'm preparing has this version number:
> 2.1.1703358377.
>
> One can download a tarball of a specific commit from their GitHub
> mirror[1].
> Because they aren't given tags with the version number, you have to refer
> to
> them by the commit ID:
>
>
> https://github.com/LuaJIT/LuaJIT/archive/c525bcb9024510cad9e170e12b6209aedb330f83/LuaJIT-c525bcb9024510cad9e170e12b6209aedb330f83.tar.gz
>
> Of course, this means that the tarball expands to a subdirectory that
> contains
> the commit ID instead of a version number in its name.
>
> I can reconcile this by adding the $REVISION variable to the SlackBuild:
>
> PRGNAM=luajit
> REVISION=${REVISION:-c525bcb9024510cad9e170e12b6209aedb330f83}
> VERSION=${VERSION:-2.1.1703358377}
>
> Is this a satisfactory solution, or has this problem been solved in a
> better way
> by another maintainer?
>
>
> [1] https://github.com/LuaJIT/LuaJIT
>
> --
> Erik Falor
>

I do something similar with picard-plugins [1]. They don't do formal
releases, just I just grab the commit that was current at the time of the
version of picard I'm packaging when it was released.

I don't think there is a formalized process to handle different versions
within the source name and folder structure. I like using SRCNAM, but
REVISION works well in your case as well.

[1] https://slackbuilds.org/repository/15.0/multimedia/picard-plugins/

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240108/86500f58/attachment-0001.htm>

From arnaud.garcia-fernandez at laposte.net  Tue Jan  9 08:31:56 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Tue, 9 Jan 2024 09:31:56 +0100
Subject: [Slackbuilds-users] Qt6 and QTWEBENGINE_RESOURCES_PATH
Message-ID: <20240109093156.1a156001bfd66b063ee80316@laposte.net>

Hi fellow Slackers, and wishing you all a happy and healthy new year.

I'm having some questions with a Qt6 build :
rss-guard recently bumped to Qt6, still allowing to build with Qt5, and I'm
willing to allow people to build with either one.

Everything goes fine except when launching the Qt6 version, I have the following
error :

time="     0.432" type="fatal" -> The following paths were searched for Qt
WebEngine resources: /usr/resources
  /usr
  /usr/bin
  $HOME/.RSS Guard
but could not find any.
You may override the default search paths by using QTWEBENGINE_RESOURCES_PATH
environment variable.

The file for Qt6 is there :
/usr/share/qt6/resources/qtwebengine_resources.pak
So if I `export QTWEBENGINE_RESOURCES_PATH=/usr/share/qt6/resources/` rssguard
starts and works fine.

The /etc/profile.d/qt6.sh only sets up QT6DIR=/usr/lib64/qt6

Solutions :
1 - asking nicely for people to setup their QTWEBENGINE_RESOURCES_PATH. That'll
lead to people being unhappy because rssguard won't work, because nobody reads
anything: I wouldn't.
2 - create a wrapper around /usr/bin/rssguard to setup this variable, which
seems a bit overcomplicated.
3 - ask the qt6 maintainer to update the /etc/profile.d/qt6.sh, but is that
really why the problem happens ?
4 - update the /etc/profile.d/qt6.sh in rssguard's doinst.sh, which is nice and
hacky, but very ugly, and nightmarish after a Qt6 update.
5 - Ask people on SBo, because brain-loop.

Hence I'm asking...

To be noted : we do have a QT6DIR environment setup to /usr/lib64/qt6, but
knowing that, there is no way of finding that some Qt6 stuffs are located
at /usr/share/qt6/, so maybe there is another more generic export for
QT6's /usr/share location ?

 - Yth.


From alessandro.baggi at gmail.com  Tue Jan  9 10:23:44 2024
From: alessandro.baggi at gmail.com (Alessandro Baggi)
Date: Tue, 9 Jan 2024 11:23:44 +0100
Subject: [Slackbuilds-users] Wireshark download link broken
Message-ID: <c078f603-8e37-490f-8000-1a95c1d997f1@gmail.com>

Hi,
I tried to install wireshark but I found the download link is broken 
because version 4.2.0 is no more available. I downloaded version 4.2.2 
and worked.


From ctrlaltca at gmail.com  Tue Jan  9 10:42:44 2024
From: ctrlaltca at gmail.com (Ctrlaltca)
Date: Tue, 9 Jan 2024 11:42:44 +0100
Subject: [Slackbuilds-users] Qt6 and QTWEBENGINE_RESOURCES_PATH
In-Reply-To: <20240109093156.1a156001bfd66b063ee80316@laposte.net>
References: <20240109093156.1a156001bfd66b063ee80316@laposte.net>
Message-ID: <2d3f4b6e-2379-42a4-983d-783702acd5b0@gmail.com>

Qt should be able to find that directory by itself using 
|QLibraryInfo::DataPath.|
Can you try to run this command and see what it returns?

qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath

In my case it returns

ArchDataPath: /usr/lib64/qt6
DataPath: /usr/share/qt6

So the chromium resource pack path should be discovered automatically.

Il 09/01/24 09:31, Arnaud via SlackBuilds-users ha scritto:
> Hi fellow Slackers, and wishing you all a happy and healthy new year.
>
> I'm having some questions with a Qt6 build :
> rss-guard recently bumped to Qt6, still allowing to build with Qt5, and I'm
> willing to allow people to build with either one.
>
> Everything goes fine except when launching the Qt6 version, I have the following
> error :
>
> time="     0.432" type="fatal" -> The following paths were searched for Qt
> WebEngine resources: /usr/resources
>    /usr
>    /usr/bin
>    $HOME/.RSS Guard
> but could not find any.
> You may override the default search paths by using QTWEBENGINE_RESOURCES_PATH
> environment variable.
>
> The file for Qt6 is there :
> /usr/share/qt6/resources/qtwebengine_resources.pak
> So if I `export QTWEBENGINE_RESOURCES_PATH=/usr/share/qt6/resources/` rssguard
> starts and works fine.
>
> The /etc/profile.d/qt6.sh only sets up QT6DIR=/usr/lib64/qt6
>
> Solutions :
> 1 - asking nicely for people to setup their QTWEBENGINE_RESOURCES_PATH. That'll
> lead to people being unhappy because rssguard won't work, because nobody reads
> anything: I wouldn't.
> 2 - create a wrapper around /usr/bin/rssguard to setup this variable, which
> seems a bit overcomplicated.
> 3 - ask the qt6 maintainer to update the /etc/profile.d/qt6.sh, but is that
> really why the problem happens ?
> 4 - update the /etc/profile.d/qt6.sh in rssguard's doinst.sh, which is nice and
> hacky, but very ugly, and nightmarish after a Qt6 update.
> 5 - Ask people on SBo, because brain-loop.
>
> Hence I'm asking...
>
> To be noted : we do have a QT6DIR environment setup to /usr/lib64/qt6, but
> knowing that, there is no way of finding that some Qt6 stuffs are located
> at /usr/share/qt6/, so maybe there is another more generic export for
> QT6's /usr/share location ?
>
>   - Yth.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240109/6f31f4da/attachment.htm>

From arnaud.garcia-fernandez at laposte.net  Tue Jan  9 11:10:28 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Tue, 9 Jan 2024 12:10:28 +0100
Subject: [Slackbuilds-users] Qt6 and QTWEBENGINE_RESOURCES_PATH
In-Reply-To: <2d3f4b6e-2379-42a4-983d-783702acd5b0@gmail.com>
References: <20240109093156.1a156001bfd66b063ee80316@laposte.net>
 <2d3f4b6e-2379-42a4-983d-783702acd5b0@gmail.com>
Message-ID: <20240109121028.598d5203b64df011b0d9871e@laposte.net>

> Qt should be able to find that directory by itself using 
> |QLibraryInfo::DataPath.|
> Can you try to run this command and see what it returns?
> 
> qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath
> 
> In my case it returns
> 
> ArchDataPath: /usr/lib64/qt6
> DataPath: /usr/share/qt6
> 
> So the chromium resource pack path should be discovered automatically.

Well :
$ qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath
  ArchDataPath: /usr/lib64
  DataPath: /usr

Even though I do have :
Environment:
  QT5DIR="/usr/lib64/qt5"
  QT6DIR="/usr/lib64/qt6"

So I guess something is wrong on my box.


From lists at osh.id.au  Tue Jan  9 12:35:11 2024
From: lists at osh.id.au (David O'Shaughnessy)
Date: Tue, 09 Jan 2024 20:35:11 +0800
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
Message-ID: <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>

On Sat, 6 Jan 2024, at 9:47 AM, Willy Sudiarto Raharjo wrote:
> Please note that all new submission MUST be submitted via normal 
> submisison form in order to get it populated in the database during 
> public update. Updates to existing scripts can be done in both ways (via 
> Github PR or Gitlab MR or normal submission form).

Thanks Willy. So does this mean that for regular version updates (not new scripts) we can submit using git? Are there any docs outlining the basic workflow for GitLab and/or GitHub with the SBo repo specifically?

From arnaud.garcia-fernandez at laposte.net  Tue Jan  9 12:57:46 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Tue, 9 Jan 2024 13:57:46 +0100
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
Message-ID: <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>

> On Sat, 6 Jan 2024, at 9:47 AM, Willy Sudiarto Raharjo wrote:
> > Please note that all new submission MUST be submitted via normal 
> > submisison form in order to get it populated in the database during 
> > public update. Updates to existing scripts can be done in both ways (via 
> > Github PR or Gitlab MR or normal submission form).
> 
> Thanks Willy. So does this mean that for regular version updates (not new
> scripts) we can submit using git? Are there any docs outlining the basic
> workflow for GitLab and/or GitHub with the SBo repo specifically?

I have forked the https://github.com/SlackBuildsOrg/slackbuilds on my own
github account. And I update my master branch when there is an update on the
upstream repository.
Also I have sbo-maintainer-tools installed

My workflow is, when I want to update, say rss-guard package :
 * I am on master branch
 * sbolint desktop/rss-guard/
 * sbopkglint /path/to/rss-guard-x.y.z.txz  # Doesn't validate for other ARCH
 * git checkout -b rss-guard
 * git add desktop/rss-guard/*
 * git commit -m "desktop/rss-guard: updated for version x.y.z"
 * git push --set-upstream origin rss-guard
And then on github I simply make a pull request, usually without comments, if it
is a straightforward update.

If I want to group some updates, for example if I have an update on libjodycode
and jdupes at the same time :
 * commit for jdupes only
 * commit for libjodycode only
 * push both commit on a jdupes branch
 * PR from jdupes branch with message stating that it is an update of jdupes and
its library libjodycode.


Corner cases :
 * Renaming a package is adding a new package using the submit web form, then a
github PR deleting the old package, with a message stating that it is a
renaming, with the new name, so that admins knows to wait for the new package
before merging.
 * If I change the name of a dependency (that has happened a lot with python
package renaming), I still make one commit per package updated, stating that it
is a REQUIRES update, and one commit to remove the old package.

I never group PR for unrelated packages.
A single commit should only be on one package, not multiple packages.

That's mostly my way of doing things.

 - Yth.

From jebrhansen+SBo at gmail.com  Tue Jan  9 13:19:41 2024
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 9 Jan 2024 08:19:41 -0500
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
Message-ID: <CANi9qSsq_q0WrgtRSZWsMsbHpDvMZB=OfXQJszNKYf5uUf2aeQ@mail.gmail.com>

On Tue, Jan 9, 2024, 7:58?AM Arnaud via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> I never group PR for unrelated packages.
> A single commit should only be on one package, not multiple packages.
>

I've always grouped unrelated packages into a single PR. I've asked in the
past if they'd prefer one PR per package (or related packages) or all in
one PR and they said it doesn't matter.

I just create an updates branch after each public update and will update my
packages throughout the week on my local machine. Towards the end of the
week, I'll push my changes to GitHub and submit a PR.

I have no issues changing my workflow if SBo admins would prefer a certain
method, but when I've asked in the past, they said whatever works best for
me.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240109/9a5c1c20/attachment.htm>

From willysr at slackbuilds.org  Tue Jan  9 13:51:17 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 9 Jan 2024 20:51:17 +0700
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <CANi9qSsq_q0WrgtRSZWsMsbHpDvMZB=OfXQJszNKYf5uUf2aeQ@mail.gmail.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CANi9qSsq_q0WrgtRSZWsMsbHpDvMZB=OfXQJszNKYf5uUf2aeQ@mail.gmail.com>
Message-ID: <f3ef97b6-6f78-4468-8870-dace0f960693@slackbuilds.org>

>> I never group PR for unrelated packages.
>> A single commit should only be on one package, not multiple packages.
>>
> 
> I've always grouped unrelated packages into a single PR. I've asked in the
> past if they'd prefer one PR per package (or related packages) or all in
> one PR and they said it doesn't matter.
> 
> I just create an updates branch after each public update and will update my
> packages throughout the week on my local machine. Towards the end of the
> week, I'll push my changes to GitHub and submit a PR.
> 
> I have no issues changing my workflow if SBo admins would prefer a certain
> method, but when I've asked in the past, they said whatever works best for
> me.

basically it doesn't matter whether it's one big PR or separate PR, but 
personally i prefer split PR, unless it's a dependency, then it must be 
in one big PR

having split PR is just easier for us (admins) to review the build 
process and also to write the trigger command to run the build.

also, make sure to write the commit message as "category/package: 
Updated for x.y.z" format or other informative message and never leave 
blank message.


-- 
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/20240109/d07a87df/attachment.asc>

From jebrhansen+SBo at gmail.com  Tue Jan  9 13:57:51 2024
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 9 Jan 2024 08:57:51 -0500
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <f3ef97b6-6f78-4468-8870-dace0f960693@slackbuilds.org>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CANi9qSsq_q0WrgtRSZWsMsbHpDvMZB=OfXQJszNKYf5uUf2aeQ@mail.gmail.com>
 <f3ef97b6-6f78-4468-8870-dace0f960693@slackbuilds.org>
Message-ID: <CANi9qSuw5Tb+LBwyySdZTjui5pmu5FNqi2Na4-MG2QAb=ank5g@mail.gmail.com>

On Tue, Jan 9, 2024, 8:51?AM Willy Sudiarto Raharjo <willysr at slackbuilds.org>
wrote:

> >> I never group PR for unrelated packages.
> >> A single commit should only be on one package, not multiple packages.
> >>
> >
> > I've always grouped unrelated packages into a single PR. I've asked in
> the
> > past if they'd prefer one PR per package (or related packages) or all in
> > one PR and they said it doesn't matter.
> >
> > I just create an updates branch after each public update and will update
> my
> > packages throughout the week on my local machine. Towards the end of the
> > week, I'll push my changes to GitHub and submit a PR.
> >
> > I have no issues changing my workflow if SBo admins would prefer a
> certain
> > method, but when I've asked in the past, they said whatever works best
> for
> > me.
>
> basically it doesn't matter whether it's one big PR or separate PR, but
> personally i prefer split PR, unless it's a dependency, then it must be
> in one big PR
>
> having split PR is just easier for us (admins) to review the build
> process and also to write the trigger command to run the build.
>

That works for me. I'll update my process to simplify the admins' job. With
how many you guys review, I want to embrace KISS for you guys.

Also, can we trigger the build bot ourselves so it might be finished by the
time you see it? I've thought about trying it, but haven't yet.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240109/92688285/attachment.htm>

From willysr at slackbuilds.org  Tue Jan  9 14:00:23 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 9 Jan 2024 21:00:23 +0700
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <CANi9qSuw5Tb+LBwyySdZTjui5pmu5FNqi2Na4-MG2QAb=ank5g@mail.gmail.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CANi9qSsq_q0WrgtRSZWsMsbHpDvMZB=OfXQJszNKYf5uUf2aeQ@mail.gmail.com>
 <f3ef97b6-6f78-4468-8870-dace0f960693@slackbuilds.org>
 <CANi9qSuw5Tb+LBwyySdZTjui5pmu5FNqi2Na4-MG2QAb=ank5g@mail.gmail.com>
Message-ID: <a64f0ca1-d241-4920-a190-c2586f3d8cc0@slackbuilds.org>

> Also, can we trigger the build bot ourselves so it might be finished by the
> time you see it? I've thought about trying it, but haven't yet.

So far, only me and aclemons who can trigger the CI build.
i was hoping it can be triggered by every PR automatically, but i leave 
that to aclemons.


-- 
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/20240109/b468402c/attachment-0001.asc>

From slackalaxy at gmail.com  Tue Jan  9 14:26:43 2024
From: slackalaxy at gmail.com (Petar Petrov)
Date: Tue, 9 Jan 2024 16:26:43 +0200
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
Message-ID: <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>

>And then on github I simply make a pull request
how do you "simply make a pull request"?

-p

On Tue, 9 Jan 2024 at 14:58, Arnaud via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
>
> > On Sat, 6 Jan 2024, at 9:47 AM, Willy Sudiarto Raharjo wrote:
> > > Please note that all new submission MUST be submitted via normal
> > > submisison form in order to get it populated in the database during
> > > public update. Updates to existing scripts can be done in both ways (via
> > > Github PR or Gitlab MR or normal submission form).
> >
> > Thanks Willy. So does this mean that for regular version updates (not new
> > scripts) we can submit using git? Are there any docs outlining the basic
> > workflow for GitLab and/or GitHub with the SBo repo specifically?
>
> I have forked the https://github.com/SlackBuildsOrg/slackbuilds on my own
> github account. And I update my master branch when there is an update on the
> upstream repository.
> Also I have sbo-maintainer-tools installed
>
> My workflow is, when I want to update, say rss-guard package :
>  * I am on master branch
>  * sbolint desktop/rss-guard/
>  * sbopkglint /path/to/rss-guard-x.y.z.txz  # Doesn't validate for other ARCH
>  * git checkout -b rss-guard
>  * git add desktop/rss-guard/*
>  * git commit -m "desktop/rss-guard: updated for version x.y.z"
>  * git push --set-upstream origin rss-guard
> And then on github I simply make a pull request, usually without comments, if it
> is a straightforward update.
>
> If I want to group some updates, for example if I have an update on libjodycode
> and jdupes at the same time :
>  * commit for jdupes only
>  * commit for libjodycode only
>  * push both commit on a jdupes branch
>  * PR from jdupes branch with message stating that it is an update of jdupes and
> its library libjodycode.
>
>
> Corner cases :
>  * Renaming a package is adding a new package using the submit web form, then a
> github PR deleting the old package, with a message stating that it is a
> renaming, with the new name, so that admins knows to wait for the new package
> before merging.
>  * If I change the name of a dependency (that has happened a lot with python
> package renaming), I still make one commit per package updated, stating that it
> is a REQUIRES update, and one commit to remove the old package.
>
> I never group PR for unrelated packages.
> A single commit should only be on one package, not multiple packages.
>
> That's mostly my way of doing things.
>
>  - Yth.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From matteo.bernardini at gmail.com  Tue Jan  9 14:39:30 2024
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 9 Jan 2024 15:39:30 +0100
Subject: [Slackbuilds-users] Qt6 and QTWEBENGINE_RESOURCES_PATH
In-Reply-To: <20240109121028.598d5203b64df011b0d9871e@laposte.net>
References: <20240109093156.1a156001bfd66b063ee80316@laposte.net>
 <2d3f4b6e-2379-42a4-983d-783702acd5b0@gmail.com>
 <20240109121028.598d5203b64df011b0d9871e@laposte.net>
Message-ID: <CAPsDuS6bRqXpqiLO-vuSYHxvvqb67NSvm1kzcm11CK6+XE_GgA@mail.gmail.com>

Il giorno mar 9 gen 2024 alle ore 12:11 Arnaud via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> ha scritto:

> > Qt should be able to find that directory by itself using
> > |QLibraryInfo::DataPath.|
> > Can you try to run this command and see what it returns?
> >
> > qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath
> >
> > In my case it returns
> >
> > ArchDataPath: /usr/lib64/qt6
> > DataPath: /usr/share/qt6
> >
> > So the chromium resource pack path should be discovered automatically.
>
> Well :
> $ qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath
>   ArchDataPath: /usr/lib64
>   DataPath: /usr
>
> Even though I do have :
> Environment:
>   QT5DIR="/usr/lib64/qt5"
>   QT6DIR="/usr/lib64/qt6"
>
> So I guess something is wrong on my box.
>

I think this actually happens because one of the cmake options in the
qt6.SlackBuild is missing

-DINSTALL_DATADIR=./share/qt6

if I add that between the others then the qtdiag6 output show the correct
DataPath.

I'll put the maintainer in cc.

Matteo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240109/cc49dccf/attachment.htm>

From willysr at slackbuilds.org  Tue Jan  9 14:47:53 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 9 Jan 2024 21:47:53 +0700
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>
Message-ID: <ec2b1c03-e8ab-4704-99a4-b7ba094794d1@slackbuilds.org>

>> And then on github I simply make a pull request
> how do you "simply make a pull request"?

you can use github-cli to do that or just push it to your github account 
and you will see a PR button in your github page to send PR to the 
original project (SBo in this case)

-- 
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/20240109/be31237f/attachment.asc>

From arnaud.garcia-fernandez at laposte.net  Tue Jan  9 15:16:59 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Tue, 9 Jan 2024 16:16:59 +0100
Subject: [Slackbuilds-users] Qt6 and QTWEBENGINE_RESOURCES_PATH
In-Reply-To: <CAPsDuS6bRqXpqiLO-vuSYHxvvqb67NSvm1kzcm11CK6+XE_GgA@mail.gmail.com>
References: <20240109093156.1a156001bfd66b063ee80316@laposte.net>
 <2d3f4b6e-2379-42a4-983d-783702acd5b0@gmail.com>
 <20240109121028.598d5203b64df011b0d9871e@laposte.net>
 <CAPsDuS6bRqXpqiLO-vuSYHxvvqb67NSvm1kzcm11CK6+XE_GgA@mail.gmail.com>
Message-ID: <20240109161659.e304141bf3597e1360a97d52@laposte.net>

> Il giorno mar 9 gen 2024 alle ore 12:11 Arnaud via SlackBuilds-users <
> slackbuilds-users at slackbuilds.org> ha scritto:
> 
> > > Qt should be able to find that directory by itself using
> > > |QLibraryInfo::DataPath.|
> > > Can you try to run this command and see what it returns?
> > >
> > > qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath
> > >
> > > In my case it returns
> > >
> > > ArchDataPath: /usr/lib64/qt6
> > > DataPath: /usr/share/qt6
> > >
> > > So the chromium resource pack path should be discovered automatically.
> >
> > Well :
> > $ qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath
> >   ArchDataPath: /usr/lib64
> >   DataPath: /usr
> >
> > Even though I do have :
> > Environment:
> >   QT5DIR="/usr/lib64/qt5"
> >   QT6DIR="/usr/lib64/qt6"
> >
> > So I guess something is wrong on my box.
> >
> 
> I think this actually happens because one of the cmake options in the
> qt6.SlackBuild is missing
> 
> -DINSTALL_DATADIR=./share/qt6
> 
> if I add that between the others then the qtdiag6 output show the correct
> DataPath.
> 
> I'll put the maintainer in cc.
> 
> Matteo

I'll try rebuilding qt6 on my end.
Dreadfully waiting for this bloatingly huge monster to stuff my whole RAM
without any hope...
See you... later !

 - Yth...

From ewfalor at gmail.com  Tue Jan  9 15:53:19 2024
From: ewfalor at gmail.com (Erik Falor)
Date: Tue, 9 Jan 2024 08:53:19 -0700
Subject: [Slackbuilds-users] Question about rolling source packages and
 version numbers
In-Reply-To: <CANi9qSuj=G0ESV8hq+g3cX9HjJb1UpcCCm=MHHiUyZ16PS7wPg@mail.gmail.com>
References: <CAKwJTQ5yEuvO9XFKQpUdeYmmpDGacaNbgYY_NAp0WAnPLUr=vg@mail.gmail.com>
 <CANi9qSuj=G0ESV8hq+g3cX9HjJb1UpcCCm=MHHiUyZ16PS7wPg@mail.gmail.com>
Message-ID: <CAKwJTQ5PadF2mi5R8s1m9tfVrq9V=ErOi-s_ZSTEFS2jz-tLpQ@mail.gmail.com>

Thanks, Jeremy.  I noticed that in picard-plugins you named the variable
COMMIT.  I think I'll follow your lead and call it by that name.

-Erik


On Mon, Jan 8, 2024 at 4:54?PM Jeremy Hansen <jebrhansen+SBo at gmail.com>
wrote:

> On Mon, Jan 8, 2024, 6:44?PM Erik Falor <ewfalor at gmail.com> wrote:
>
>> Hi all,
>>
>> LuaJIT uses rolling releases. There are no release tarballs available for
>> download.  Instead of manual increments for each release, the build
>> process
>> uses the POSIX time stamp of the latest commit as the release number of
>> the
>> semantic version.
>>
>> The full version number is in the format `$major.$minor.$timestamp`.  For
>> instance, the latest SlackBuild I'm preparing has this version number:
>> 2.1.1703358377.
>>
>> One can download a tarball of a specific commit from their GitHub
>> mirror[1].
>> Because they aren't given tags with the version number, you have to refer
>> to
>> them by the commit ID:
>>
>>
>> https://github.com/LuaJIT/LuaJIT/archive/c525bcb9024510cad9e170e12b6209aedb330f83/LuaJIT-c525bcb9024510cad9e170e12b6209aedb330f83.tar.gz
>>
>> Of course, this means that the tarball expands to a subdirectory that
>> contains
>> the commit ID instead of a version number in its name.
>>
>> I can reconcile this by adding the $REVISION variable to the SlackBuild:
>>
>> PRGNAM=luajit
>> REVISION=${REVISION:-c525bcb9024510cad9e170e12b6209aedb330f83}
>> VERSION=${VERSION:-2.1.1703358377}
>>
>> Is this a satisfactory solution, or has this problem been solved in a
>> better way
>> by another maintainer?
>>
>>
>> [1] https://github.com/LuaJIT/LuaJIT
>>
>> --
>> Erik Falor
>>
>
> I do something similar with picard-plugins [1]. They don't do formal
> releases, just I just grab the commit that was current at the time of the
> version of picard I'm packaging when it was released.
>
> I don't think there is a formalized process to handle different versions
> within the source name and folder structure. I like using SRCNAM, but
> REVISION works well in your case as well.
>
> [1] https://slackbuilds.org/repository/15.0/multimedia/picard-plugins/
>
> Jeremy
>
>> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

-- 
Erik Falor
Registered Linux User #445632 http://counter.li.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240109/264355c5/attachment-0001.htm>

From jebrhansen+SBo at gmail.com  Tue Jan  9 17:24:46 2024
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 9 Jan 2024 12:24:46 -0500
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>
Message-ID: <CANi9qSs0=wpxVXxzf_NUEZ0nvDZaZ7Dj-SJm+yEPRhXR4tD+_w@mail.gmail.com>

On Tue, Jan 9, 2024, 9:26?AM Petar Petrov <slackalaxy at gmail.com> wrote:

> >And then on github I simply make a pull request
> how do you "simply make a pull request"?
>
> -p
>

I'm a relative git and GitHub newb, but here's what I did to start working
with GitHub. (For those who are far more knowledgeable than me, if there
are improvements to be made, please let me know.) I'm sure GitLab is
similar, but they have slight variations in terminology.

This is aimed at other git/GitHub newbs... if you aren't one, I apologize.

To get started, do the following:

1. Fork SBo's GitHub repo through the GitHub interface (you need to have a
GitHub account and be logged into it to fork).
2. Clone your newly forked repo onto your computer.
  git clone $your_new_repo_address
3. Set SBo's GitHub as upstream to make getting public updates easier.
  git remote add upstream git://github.com/SlackBuildsOrg/slackbuilds.git

If you've never used git on your computer to make commits before, you'll
need to tell git who you are so it can know who to attribute your commits
to:

  git config --global user.email "you at example.com"
  git config --global user.name "Your Name"

Now you're ready to start updating on your local computer.

1. Create a new branch for the package you're updating and switch to that
branch. Typically this will be the package name that you're updating, but
naming schemes are more for you than anything. The name of the branch won't
affect the SBo admins reviewing your pull request.
  git checkout -B $branch_name
2. Make the changes to the files and verify everything works. This may
require moving those files to a clean VM to verify they build properly in a
clean environment.
3. Commit those changes to that branch on your local repo:
  git commit -m "network/discord: Update version to 1.2.3"
location/to/changes
(If there are multiple package changes due to dependency bumps or similar,
do an individual commit for each package.)
4. Once all commits are complete that apply to your update, push those
commits to your GitHub repo, forcing GitHub to create a new remote branch
(since it only exists locally):
  git push -f origin $branch_name
5. Git will provide a link in the output you can visit to submit the pull
request (PR) or you can just browse to your GitHub repo and you can submit
the PR yourself (if the push was recent, it'll list the option at the top
of the nation page, otherwise you can go into the branches area and can
submit it that way.
6. Explain your changes, if necessary, when submitting the PR back to SBo's
repo.

Then it's just a matter of waiting for SBo admins to review your
submission. If changes are needed, they'll suggest them. Once the changes
are accepted, you can delete the branch on your repo online and on your
local repo:
  git checkout master  # first make sure you're on your master branch
  git branch -D $branch_name

Once a public update is released, you can then update your local copy on
the master branch using:
  git checkout master
  git pull upstream master

>From here, you can then create a new branch again to make more changes,
commit them, push them back to GitHub, and submit a new PR.

Always commit changes into a separate branch. If you commit changes to
master, it'll give you problems when trying to sync with upstream after
public updates.

Hopefully this all makes sense. If there are any suggestions others have
that might improve this, feel free to add them.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240109/55a83f0a/attachment.htm>

From slackalaxy at gmail.com  Tue Jan  9 17:47:58 2024
From: slackalaxy at gmail.com (Petar Petrov)
Date: Tue, 9 Jan 2024 19:47:58 +0200
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <CANi9qSs0=wpxVXxzf_NUEZ0nvDZaZ7Dj-SJm+yEPRhXR4tD+_w@mail.gmail.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>
 <CANi9qSs0=wpxVXxzf_NUEZ0nvDZaZ7Dj-SJm+yEPRhXR4tD+_w@mail.gmail.com>
Message-ID: <CAKXpWBdfFmQKGH+kzNfc+gS+FqZ+PRLFyNqMqS708wUZDYpM7w@mail.gmail.com>

thank you, that's very useful!

-p

On Tue, 9 Jan 2024 at 19:25, Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
>
>
>
> On Tue, Jan 9, 2024, 9:26?AM Petar Petrov <slackalaxy at gmail.com> wrote:
>>
>> >And then on github I simply make a pull request
>> how do you "simply make a pull request"?
>>
>> -p
>
>
> I'm a relative git and GitHub newb, but here's what I did to start working with GitHub. (For those who are far more knowledgeable than me, if there are improvements to be made, please let me know.) I'm sure GitLab is similar, but they have slight variations in terminology.
>
> This is aimed at other git/GitHub newbs... if you aren't one, I apologize.
>
> To get started, do the following:
>
> 1. Fork SBo's GitHub repo through the GitHub interface (you need to have a GitHub account and be logged into it to fork).
> 2. Clone your newly forked repo onto your computer.
>   git clone $your_new_repo_address
> 3. Set SBo's GitHub as upstream to make getting public updates easier.
>   git remote add upstream git://github.com/SlackBuildsOrg/slackbuilds.git
>
> If you've never used git on your computer to make commits before, you'll need to tell git who you are so it can know who to attribute your commits to:
>
>   git config --global user.email "you at example.com"
>   git config --global user.name "Your Name"
>
> Now you're ready to start updating on your local computer.
>
> 1. Create a new branch for the package you're updating and switch to that branch. Typically this will be the package name that you're updating, but naming schemes are more for you than anything. The name of the branch won't affect the SBo admins reviewing your pull request.
>   git checkout -B $branch_name
> 2. Make the changes to the files and verify everything works. This may require moving those files to a clean VM to verify they build properly in a clean environment.
> 3. Commit those changes to that branch on your local repo:
>   git commit -m "network/discord: Update version to 1.2.3" location/to/changes
> (If there are multiple package changes due to dependency bumps or similar, do an individual commit for each package.)
> 4. Once all commits are complete that apply to your update, push those commits to your GitHub repo, forcing GitHub to create a new remote branch (since it only exists locally):
>   git push -f origin $branch_name
> 5. Git will provide a link in the output you can visit to submit the pull request (PR) or you can just browse to your GitHub repo and you can submit the PR yourself (if the push was recent, it'll list the option at the top of the nation page, otherwise you can go into the branches area and can submit it that way.
> 6. Explain your changes, if necessary, when submitting the PR back to SBo's repo.
>
> Then it's just a matter of waiting for SBo admins to review your submission. If changes are needed, they'll suggest them. Once the changes are accepted, you can delete the branch on your repo online and on your local repo:
>   git checkout master  # first make sure you're on your master branch
>   git branch -D $branch_name
>
> Once a public update is released, you can then update your local copy on the master branch using:
>   git checkout master
>   git pull upstream master
>
> From here, you can then create a new branch again to make more changes, commit them, push them back to GitHub, and submit a new PR.
>
> Always commit changes into a separate branch. If you commit changes to master, it'll give you problems when trying to sync with upstream after public updates.
>
> Hopefully this all makes sense. If there are any suggestions others have that might improve this, feel free to add them.
>
> Jeremy
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From antonioleal at yahoo.com  Tue Jan  9 19:51:47 2024
From: antonioleal at yahoo.com (Antonio Leal)
Date: Tue, 9 Jan 2024 19:51:47 +0000
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <CANi9qSs0=wpxVXxzf_NUEZ0nvDZaZ7Dj-SJm+yEPRhXR4tD+_w@mail.gmail.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>
 <CANi9qSs0=wpxVXxzf_NUEZ0nvDZaZ7Dj-SJm+yEPRhXR4tD+_w@mail.gmail.com>
Message-ID: <3d5a0130-9eb5-416f-a1c9-6362df2a8e76@yahoo.com>

Great explanation. Thank you.

Maybe is should be in the site FAQ :-)


On 09/01/24 17:24, Jeremy Hansen wrote:
>
>
> On Tue, Jan 9, 2024, 9:26?AM Petar Petrov <slackalaxy at gmail.com> wrote:
>
>     >And then on github I simply make a pull request
>     how do you "simply make a pull request"?
>
>     -p
>
>
> I'm a relative git and GitHub newb, but here's what I did to start 
> working with GitHub. (For those who are far more knowledgeable than 
> me, if there are improvements to be made, please let me know.) I'm 
> sure GitLab is similar, but they have slight variations in terminology.
>
> This is aimed at other git/GitHub newbs... if you aren't one, I apologize.
>
> To get started, do the following:
>
> 1. Fork SBo's GitHub repo through the GitHub interface (you need to 
> have a GitHub account and be logged into it to fork).
> 2. Clone your newly forked repo onto your computer.
> ? git clone $your_new_repo_address
> 3. Set SBo's GitHub as upstream to make getting public updates easier.
> ??git remote add upstream 
> git://github.com/SlackBuildsOrg/slackbuilds.git 
> <http://github.com/SlackBuildsOrg/slackbuilds.git>
>
> If you've never used git on your computer to make commits before, 
> you'll need to tell git who you are so it can know who to attribute 
> your commits to:
>
> ? git config --global user.email "you at example.com"
> ? git config --global user.name <http://user.name> "Your Name"
>
> Now you're ready to start updating on your local computer.
>
> 1. Create a new branch for the package you're updating and switch to 
> that branch. Typically this will be the package name that you're 
> updating, but naming schemes are more for you than anything. The name 
> of the branch won't affect the SBo admins reviewing your pull request.
> ? git checkout -B $branch_name
> 2. Make the changes to the files and verify everything works. This may 
> require moving those files to a clean VM to verify they build properly 
> in a clean environment.
> 3. Commit those changes to that branch on your local repo:
> ? git commit -m "network/discord: Update version to 1.2.3" 
> location/to/changes
> (If there are multiple package changes due to dependency bumps or 
> similar, do an individual commit for each package.)
> 4. Once all commits are complete that apply to your update, push those 
> commits to your GitHub repo, forcing GitHub to create a new remote 
> branch (since it only exists locally):
> ? git push -f origin $branch_name
> 5. Git will provide a link in the output you can visit to submit the 
> pull request (PR) or you can just browse to your GitHub repo and you 
> can submit the PR yourself (if the push was recent, it'll list the 
> option at the top of the nation page, otherwise you can go into the 
> branches area and can submit it that way.
> 6. Explain your changes, if necessary, when submitting the PR back to 
> SBo's repo.
>
> Then it's just a matter of waiting for SBo admins to review your 
> submission. If changes are needed, they'll suggest them. Once the 
> changes are accepted, you can delete the branch on your repo online 
> and on your local repo:
> ? git checkout master? # first make sure you're on your master branch
> ? git branch -D $branch_name
>
> Once a public update is released, you can then update your local copy 
> on the master branch using:
> ? git checkout master
> ? git pull upstream master
>
> From here, you can then create a new branch again to make more 
> changes, commit them, push them back to GitHub, and submit a new PR.
>
> Always commit changes into a separate branch. If you commit changes to 
> master, it'll give you problems when trying to sync with upstream 
> after public updates.
>
> Hopefully this all makes sense. If there are any suggestions others 
> have that might improve this, feel free to add them.
>
> Jeremy
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240109/b7342c3a/attachment-0001.htm>

From bru.barwal at SDF.ORG  Tue Jan  9 19:58:26 2024
From: bru.barwal at SDF.ORG (Bru Barwal)
Date: Tue, 9 Jan 2024 19:58:26 +0000
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <CANi9qSs0=wpxVXxzf_NUEZ0nvDZaZ7Dj-SJm+yEPRhXR4tD+_w@mail.gmail.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>
 <CANi9qSs0=wpxVXxzf_NUEZ0nvDZaZ7Dj-SJm+yEPRhXR4tD+_w@mail.gmail.com>
Message-ID: <ZZ2lYqfTGPgQpZgF@SDF.ORG>

On Tue, Jan 09, 2024 at 12:24:46PM -0500, Jeremy Hansen wrote:
> On Tue, Jan 9, 2024, 9:26???AM Petar Petrov <slackalaxy at gmail.com> wrote:
> 
> > >And then on github I simply make a pull request
> > how do you "simply make a pull request"?
> >
> > -p
> >
> 
> I'm a relative git and GitHub newb, but here's what I did to start working
> with GitHub. (For those who are far more knowledgeable than me, if there
> are improvements to be made, please let me know.) I'm sure GitLab is
> similar, but they have slight variations in terminology.
> 
> This is aimed at other git/GitHub newbs... if you aren't one, I apologize.

Thanks for sharing. As another newb, I found this very helpful!
 
> 1. Create a new branch for the package you're updating and switch to that
> branch. Typically this will be the package name that you're updating, but
> naming schemes are more for you than anything. The name of the branch won't
> affect the SBo admins reviewing your pull request.
>   git checkout -B $branch_name
> 2. Make the changes to the files and verify everything works. This may
> require moving those files to a clean VM to verify they build properly in a
> clean environment.

This is where I had to `git add` the changed files

> 3. Commit those changes to that branch on your local repo:
>   git commit -m "network/discord: Update version to 1.2.3"
> location/to/changes
> (If there are multiple package changes due to dependency bumps or similar,
> do an individual commit for each package.)


-- 
Matt Egger
bru.barwal at sdf.org

From arnaud.garcia-fernandez at laposte.net  Tue Jan  9 20:06:47 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Tue, 9 Jan 2024 21:06:47 +0100
Subject: [Slackbuilds-users] Updates - 20240106.1
In-Reply-To: <3d5a0130-9eb5-416f-a1c9-6362df2a8e76@yahoo.com>
References: <e7fbf0b8-988f-4dc2-89a7-5c97c6273edc@slackbuilds.org>
 <a9125985-91df-405d-ac0f-57039bbe08ed@app.fastmail.com>
 <20240109135746.2b9fdfc941e191b7ef3de4bf@laposte.net>
 <CAKXpWBedLvwCErirBps=76HqQ4vTtW784-oGYpXrA0-1UPODQA@mail.gmail.com>
 <CANi9qSs0=wpxVXxzf_NUEZ0nvDZaZ7Dj-SJm+yEPRhXR4tD+_w@mail.gmail.com>
 <3d5a0130-9eb5-416f-a1c9-6362df2a8e76@yahoo.com>
Message-ID: <20240109210647.f7f106c0a1aef38c205a8d3c@laposte.net>

For examples, I've just sent a bunch of PRs, which can be seen here :
https://github.com/SlackBuildsOrg/slackbuilds/pulls
Most are just one package update.
Some are batches, like for the new PyPy version, there are 4 packages (pypy,
pypy3, PyPy and PyPy3), therefore 4 commits, one for each package.
I could have sent 4 PRs, but I want them to be either all updated at the same
time, or none of them.

As a side note about batch updates : if one package in the batch has a problem,
it's not very easy to just update that one inside the batch, and admins will
block the whole batch.
You need either to push new commits, but there'll be unuseful ones inside the
batch, or you have to do some medium-advanced git-jutsu to change one commit in
the lot, or even restart your commit/push from the beginning.
With separate PRs, everything that works is put out of the way, and there
remains only the problems to be handled.

Of course, usually there are no problems, but they happen from time to time...

I am taking a chance with my buildbot update : 5 packages, 3 for buildbot itself,
that should all be at the same version, and two from REQUIRES.
But I could have (and maybe should have) separated the requirements from the
buildbot ones : if, let's say, python3-klein has a problem, I won't have my
buildbot update, even though it would have worked fine with the actual
non-updated python3-klein.

 - Yth.



> Great explanation. Thank you.
> 
> Maybe is should be in the site FAQ :-)
> 
> 
> On 09/01/24 17:24, Jeremy Hansen wrote:
> >
> >
> > On Tue, Jan 9, 2024, 9:26?AM Petar Petrov <slackalaxy at gmail.com> wrote:
> >
> >     >And then on github I simply make a pull request
> >     how do you "simply make a pull request"?
> >
> >     -p
> >
> >
> > I'm a relative git and GitHub newb, but here's what I did to start 
> > working with GitHub. (For those who are far more knowledgeable than 
> > me, if there are improvements to be made, please let me know.) I'm 
> > sure GitLab is similar, but they have slight variations in terminology.
> >
> > This is aimed at other git/GitHub newbs... if you aren't one, I apologize.
> >
> > To get started, do the following:
> >
> > 1. Fork SBo's GitHub repo through the GitHub interface (you need to 
> > have a GitHub account and be logged into it to fork).
> > 2. Clone your newly forked repo onto your computer.
> > ? git clone $your_new_repo_address
> > 3. Set SBo's GitHub as upstream to make getting public updates easier.
> > ??git remote add upstream 
> > git://github.com/SlackBuildsOrg/slackbuilds.git 
> > <http://github.com/SlackBuildsOrg/slackbuilds.git>
> >
> > If you've never used git on your computer to make commits before, 
> > you'll need to tell git who you are so it can know who to attribute 
> > your commits to:
> >
> > ? git config --global user.email "you at example.com"
> > ? git config --global user.name <http://user.name> "Your Name"
> >
> > Now you're ready to start updating on your local computer.
> >
> > 1. Create a new branch for the package you're updating and switch to 
> > that branch. Typically this will be the package name that you're 
> > updating, but naming schemes are more for you than anything. The name 
> > of the branch won't affect the SBo admins reviewing your pull request.
> > ? git checkout -B $branch_name
> > 2. Make the changes to the files and verify everything works. This may 
> > require moving those files to a clean VM to verify they build properly 
> > in a clean environment.
> > 3. Commit those changes to that branch on your local repo:
> > ? git commit -m "network/discord: Update version to 1.2.3" 
> > location/to/changes
> > (If there are multiple package changes due to dependency bumps or 
> > similar, do an individual commit for each package.)
> > 4. Once all commits are complete that apply to your update, push those 
> > commits to your GitHub repo, forcing GitHub to create a new remote 
> > branch (since it only exists locally):
> > ? git push -f origin $branch_name
> > 5. Git will provide a link in the output you can visit to submit the 
> > pull request (PR) or you can just browse to your GitHub repo and you 
> > can submit the PR yourself (if the push was recent, it'll list the 
> > option at the top of the nation page, otherwise you can go into the 
> > branches area and can submit it that way.
> > 6. Explain your changes, if necessary, when submitting the PR back to 
> > SBo's repo.
> >
> > Then it's just a matter of waiting for SBo admins to review your 
> > submission. If changes are needed, they'll suggest them. Once the 
> > changes are accepted, you can delete the branch on your repo online 
> > and on your local repo:
> > ? git checkout master? # first make sure you're on your master branch
> > ? git branch -D $branch_name
> >
> > Once a public update is released, you can then update your local copy 
> > on the master branch using:
> > ? git checkout master
> > ? git pull upstream master
> >
> > From here, you can then create a new branch again to make more 
> > changes, commit them, push them back to GitHub, and submit a new PR.
> >
> > Always commit changes into a separate branch. If you commit changes to 
> > master, it'll give you problems when trying to sync with upstream 
> > after public updates.
> >
> > Hopefully this all makes sense. If there are any suggestions others 
> > have that might improve this, feel free to add them.
> >
> > Jeremy
> >
> >
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ -https://slackbuilds.org/faq/
> >



From arnaud.garcia-fernandez at laposte.net  Wed Jan 10 08:56:05 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Wed, 10 Jan 2024 09:56:05 +0100
Subject: [Slackbuilds-users] Qt6 and QTWEBENGINE_RESOURCES_PATH
In-Reply-To: <20240109161659.e304141bf3597e1360a97d52@laposte.net>
References: <20240109093156.1a156001bfd66b063ee80316@laposte.net>
 <2d3f4b6e-2379-42a4-983d-783702acd5b0@gmail.com>
 <20240109121028.598d5203b64df011b0d9871e@laposte.net>
 <CAPsDuS6bRqXpqiLO-vuSYHxvvqb67NSvm1kzcm11CK6+XE_GgA@mail.gmail.com>
 <20240109161659.e304141bf3597e1360a97d52@laposte.net>
Message-ID: <20240110095605.67a43e02dc529eb13bb39115@laposte.net>

> > I think this actually happens because one of the cmake options in the
> > qt6.SlackBuild is missing
> > 
> > -DINSTALL_DATADIR=./share/qt6
> > 
> > if I add that between the others then the qtdiag6 output show the correct
> > DataPath.
> > 
> > I'll put the maintainer in cc.
> > 
> > Matteo
> 
> I'll try rebuilding qt6 on my end.
> Dreadfully waiting for this bloatingly huge monster to stuff my whole RAM
> without any hope...
> See you... later !
> 
>  - Yth...

And 7 hours later, my new and shiny qt6 works perfectly, and rssguqrd doesn't
need a hack anymore !
That's a good catch Matteo, thanks.

 - Yth.

From didier at slint.fr  Thu Jan 11 17:36:30 2024
From: didier at slint.fr (Didier Spaier)
Date: Thu, 11 Jan 2024 17:36:30 +0000
Subject: [Slackbuilds-users] Error when starting grk-pipe-viewer (package
 pipe-viewer)
Message-ID: <12d02647-2d53-4f1e-98e7-07341990cfb4@slint.fr>

Hello,

typing in a graphical terminal: gtk-pipe-viewer spits an error message.

Ceveat: this is not typed in a stock full Slackware installation and I do not
have all packages mentioned in the sql file installed

However as it worked some months ago (I don't remember exactly when) I'd
appreciate that someone tries before I investigate further.

I attach the error message and the list of installed perl packages.

Cheers,
Didier

From urchlay at slackware.uk  Thu Jan 11 16:47:06 2024
From: urchlay at slackware.uk (B. Watson)
Date: Thu, 11 Jan 2024 11:47:06 -0500 (EST)
Subject: [Slackbuilds-users] Error when starting grk-pipe-viewer
 (package pipe-viewer)
In-Reply-To: <12d02647-2d53-4f1e-98e7-07341990cfb4@slint.fr>
References: <12d02647-2d53-4f1e-98e7-07341990cfb4@slint.fr>
Message-ID: <61c60e2-cfd9-e6e3-df5b-7efecc9fad3@slackware.uk>



On Thu, 11 Jan 2024, Didier Spaier wrote:

> I attach the error message and the list of installed perl packages.

I don't see the attachment...

However, I just updated pipe-viewer on January 3, with a fix for a
gtk-pipe-viewer issue. Are you using the latest? That'd be version
0.4.8, BUILD=2.

From slack at giand.it  Thu Jan 11 17:24:53 2024
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=)
Date: Thu, 11 Jan 2024 18:24:53 +0100
Subject: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a
 Slackware 32 bit
Message-ID: <c5dad648-bad9-43cb-9097-1b3b97ddd964@giand.it>

Hi

I have a Slackware 15.0 (32 bit) installed in a virtual machine. I use 
it for testing my slackbuilds, but I have problems when I have to build 
webkit2gtk or webkit2gtk4.1 required as dependencies for some packages. 
The script crashes due to the high resources absorbed by ninja and I 
can't continue with the tests.

A solution could be the installation of a prebuilt package, but I don't 
find these packages for 32-bit. Does anyone know where I can possibly 
find them? I need both webkit2gtk and webkit2gtk4.1

Thanks for help

Giancarlo

-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it
https://github.com/giandex

Slackware Linux... because it works!
*********************************************************


From didier at slint.fr  Thu Jan 11 18:49:59 2024
From: didier at slint.fr (Didier Spaier)
Date: Thu, 11 Jan 2024 18:49:59 +0000
Subject: [Slackbuilds-users] Error when starting grk-pipe-viewer
 (package pipe-viewer)
In-Reply-To: <61c60e2-cfd9-e6e3-df5b-7efecc9fad3@slackware.uk>
References: <12d02647-2d53-4f1e-98e7-07341990cfb4@slint.fr>
 <61c60e2-cfd9-e6e3-df5b-7efecc9fad3@slackware.uk>
Message-ID: <085569ff-c5d4-49b2-ade5-48879562b708@slint.fr>

Hello,

Le 11/01/2024 ? 16:47, B. Watson a ?crit?:
> 
> 
> On Thu, 11 Jan 2024, Didier Spaier wrote:
> 
>> I attach the error message and the list of installed perl packages.
> 
> I don't see the attachment...

I forgot them, sorry. ?ow they should be there.

> However, I just updated pipe-viewer on January 3, with a fix for a
> gtk-pipe-viewer issue. Are you using the latest? That'd be version
> 0.4.8, BUILD=2.

The issue remains: does not work here (TM)

Thanks,
Didier
-------------- next part --------------
syntax error at /usr/bin/gtk-pipe-viewer line 320, near ")"
Global symbol "%CONFIG" requires explicit package name (did you forget to declare "my %CONFIG"?) at /usr/bin/gtk-pipe-viewer line 338.
Type of arg 1 to List::Util::any must be block or sub {} (not reference constructor) at /usr/bin/gtk-pipe-viewer line 491, near ");"
Type of arg 1 to List::Util::any must be block or sub {} (not reference constructor) at /usr/bin/gtk-pipe-viewer line 1116, near "@FEATURES)"
BEGIN not safe after errors--compilation aborted at /usr/bin/gtk-pipe-viewer line 1755.
-------------- next part --------------
perl-5.34.0-x86_64-2_slack15.0
perl-AnyEvent-7.17-x86_64-1slint
perl-CDDB-get-2.28.1-x86_64-2slint
perl-Cairo-GObject-1.005-x86_64-1slint
perl-Canary-Stability-2013-x86_64-1slint
perl-Class-Inspector-1.36-x86_64-1slint
perl-Encode-EUCJPASCII-0.03-x86_64-2slint
perl-Encode-HanExtra-0.23-x86_64-2slint
perl-Encode-ISO2022-0.04-x86_64-2slint
perl-Encode-JISX0213-0.04-x86_64-2slint
perl-ExtUtils-CChecker-0.11-noarch-1slint
perl-ExtUtils-Config-0.008-x86_64-1slint
perl-ExtUtils-Helpers-0.026-x86_64-1slint
perl-ExtUtils-InstallPaths-0.012-x86_64-1slint
perl-File-ShareDir-1.102-noarch-1slint
perl-Glib-Object-Introspection-0.049-x86_64-1slint
perl-Gtk3-0.038-x86_64-1slint
perl-IO-HTML-1.004-x86_64-1slint
perl-IO-Socket-SSL-2.074-x86_64-1slint
perl-JSON-4.05-x86_64-1slint
perl-JSON-MaybeXS-1.004000-x86_64-1salix15.0
perl-JSON-XS-4.03-x86_64-1slint
perl-LWP-Protocol-https-6.10-x86_64-1slint
perl-Locale-Gettext-1.07-x86_64-3slint
perl-MIME-Charset-1.012.2-x86_64-1slint
perl-Module-Build-0.4231-x86_64-1slint
perl-Module-Build-Tiny-0.039-x86_64-1slint
perl-Module-Install-1.19-x86_64-1slint
perl-Mojolicious-9.22-x86_64-1slint
perl-Mozilla-CA-20211001-x86_64-1slint
perl-MusicBrainz-DiscID-0.06-x86_64-1slint
perl-Net-LibIDN-0.12-x86_64-2slint
perl-Net-SSLeay-1.92-x86_64-1slint
perl-Pod-Parser-1.63-x86_64-2slint
perl-Role-Tiny-2.002004-x86_64-1slint
perl-Sub-Uplevel-0.2800-x86_64-1slint
perl-Syntax-Keyword-Try-0.27-x86_64-1slint
perl-Term-ReadLine-Gnu-1.42-x86_64-1slint
perl-Test-Fatal-0.016-x86_64-1slint
perl-Test-Needs-0.002009-noarch-1slint
perl-Test-Pod-1.52-x86_64-2slint
perl-Test-RequiresInternet-0.05-x86_64-2slint
perl-Text-CharWidth-0.04-x86_64-2slint
perl-Text-Unidecode-1.30-x86_64-1slint
perl-Text-WrapI18N-0.06-x86_64-2slint
perl-Try-Tiny-0.31-x86_64-1slint
perl-Types-Serialiser-1.01-x86_64-1slint
perl-Unicode-LineBreak-2019.001-x86_64-1slint
perl-WebService-MusicBrainz-1.0.5-x86_64-1slint
perl-XS-Parse-Keyword-0.25-x86_64-1slint
perl-YAML-Tiny-1.73-x86_64-2slint
perl-cairo-1.109-x86_64-1slint
perl-common-sense-3.75-x86_64-1slint
perl-data-dump-1.25-x86_64-1slint
perl-encode-locale-1.05-x86_64-2slint
perl-extutils-depends-0.8001-x86_64-1slint
perl-extutils-pkgconfig-1.16-x86_64-2slint
perl-file-listing-6.14-x86_64-1slint
perl-glib-1.3293-x86_64-2slint
perl-html-parser-3.76-x86_64-1slint
perl-html-tagset-3.20-x86_64-2slint
perl-http-cookies-6.10-x86_64-1slint
perl-http-daemon-6.13-x86_64-1slint
perl-http-date-6.05-x86_64-1slint
perl-http-message-6.36-x86_64-1slint
perl-http-negotiate-6.01-x86_64-2slint
perl-inc-latest-0.500-x86_64-2slint
perl-lwp-mediatypes-6.04-x86_64-1slint
perl-lwp-useragent-cached-0.08-x86_64-2slint
perl-mp3-tag-1.15-x86_64-1slint
perl-net-http-6.22-x86_64-1slint
perl-pango-1.227-x86_64-2salix15.0
perl-parallel-forkmanager-2.02-x86_64-1slint
perl-test-warn-0.37-x86_64-1slint
perl-www-robotrules-6.02-x86_64-2slint

From urchlay at slackware.uk  Thu Jan 11 19:02:11 2024
From: urchlay at slackware.uk (B. Watson)
Date: Thu, 11 Jan 2024 14:02:11 -0500 (EST)
Subject: [Slackbuilds-users] Error when starting grk-pipe-viewer
 (package pipe-viewer)
In-Reply-To: <085569ff-c5d4-49b2-ade5-48879562b708@slint.fr>
References: <12d02647-2d53-4f1e-98e7-07341990cfb4@slint.fr>
 <61c60e2-cfd9-e6e3-df5b-7efecc9fad3@slackware.uk>
 <085569ff-c5d4-49b2-ade5-48879562b708@slint.fr>
Message-ID: <814645a-2ce8-3988-6637-942f326730a@slackware.uk>



On Thu, 11 Jan 2024, Didier Spaier wrote:

> The issue remains: does not work here (TM)

One thing I see you're missing in your list of installed perl packages
is libwww-perl. That's pretty important for pipe-viewer... but you
might have it installed, you just did a "ls perl-*", and that one
doesn't start with "perl".

2 more that are listed in the .sqf:

perl-PAR-Dist
perl-File-ShareDir-Install

Just to be sure, can you gzip your /usr/bin/gtk-pipe-viewer and attach
it to an email? It works out to about 30KB compressed, not too much
for a mail attachment, and that way I can make sure we're both looking
at the same thing.

Also... does pipe-viewer (the non-GTK one) work OK for you?

From didier at slint.fr  Thu Jan 11 21:36:41 2024
From: didier at slint.fr (Didier Spaier)
Date: Thu, 11 Jan 2024 21:36:41 +0000
Subject: [Slackbuilds-users] Error when starting grk-pipe-viewer
 (package pipe-viewer)
In-Reply-To: <814645a-2ce8-3988-6637-942f326730a@slackware.uk>
References: <12d02647-2d53-4f1e-98e7-07341990cfb4@slint.fr>
 <61c60e2-cfd9-e6e3-df5b-7efecc9fad3@slackware.uk>
 <085569ff-c5d4-49b2-ade5-48879562b708@slint.fr>
 <814645a-2ce8-3988-6637-942f326730a@slackware.uk>
Message-ID: <69ba9a9f-7a32-42cb-883d-8e4cb3403c24@slint.fr>



Le 11/01/2024 ? 19:02, B. Watson a ?crit?:
> 
> 
> On Thu, 11 Jan 2024, Didier Spaier wrote:
> 
>> The issue remains: does not work here (TM)
> 
> One thing I see you're missing in your list of installed perl packages
> is libwww-perl. That's pretty important for pipe-viewer... but you
> might have it installed, you just did a "ls perl-*", and that one
> doesn't start with "perl".
> 
> 2 more that are listed in the .sqf:
> 
> perl-PAR-Dist
> perl-File-ShareDir-Install

libwww-perl was already installed. I installed the two others, to no avail


> Just to be sure, can you gzip your /usr/bin/gtk-pipe-viewer and attach
> it to an email? It works out to about 30KB compressed, not too much
> for a mail attachment, and that way I can make sure we're both looking
> at the same thing.

Attached.
> Also... does pipe-viewer (the non-GTK one) work OK for you?
Yes, it does.

Thanks,
Didier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gtk-pipe-viewer.gz
Type: application/gzip
Size: 30412 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240111/89c93d5c/attachment-0001.bin>

From urchlay at slackware.uk  Thu Jan 11 20:51:02 2024
From: urchlay at slackware.uk (B. Watson)
Date: Thu, 11 Jan 2024 15:51:02 -0500 (EST)
Subject: [Slackbuilds-users] Error when starting grk-pipe-viewer
 (package pipe-viewer)
In-Reply-To: <69ba9a9f-7a32-42cb-883d-8e4cb3403c24@slint.fr>
References: <12d02647-2d53-4f1e-98e7-07341990cfb4@slint.fr>
 <61c60e2-cfd9-e6e3-df5b-7efecc9fad3@slackware.uk>
 <085569ff-c5d4-49b2-ade5-48879562b708@slint.fr>
 <814645a-2ce8-3988-6637-942f326730a@slackware.uk>
 <69ba9a9f-7a32-42cb-883d-8e4cb3403c24@slint.fr>
Message-ID: <925ac5d8-5e1f-546-598d-ad9021dcc288@slackware.uk>



On Thu, 11 Jan 2024, Didier Spaier wrote:

> Attached.

Diffed the two...

200d199
<                              },

Meaning, your gtk-pipe-viewer is old, it doesn't have the corrected
restore_mplayer.diff from January 3. It probably is the BUILD=1
version (the updated one is BUILD=2).

From didier at slint.fr  Thu Jan 11 22:03:41 2024
From: didier at slint.fr (Didier Spaier)
Date: Thu, 11 Jan 2024 22:03:41 +0000
Subject: [Slackbuilds-users] Error when starting grk-pipe-viewer
 (package pipe-viewer)
In-Reply-To: <925ac5d8-5e1f-546-598d-ad9021dcc288@slackware.uk>
References: <12d02647-2d53-4f1e-98e7-07341990cfb4@slint.fr>
 <61c60e2-cfd9-e6e3-df5b-7efecc9fad3@slackware.uk>
 <085569ff-c5d4-49b2-ade5-48879562b708@slint.fr>
 <814645a-2ce8-3988-6637-942f326730a@slackware.uk>
 <69ba9a9f-7a32-42cb-883d-8e4cb3403c24@slint.fr>
 <925ac5d8-5e1f-546-598d-ad9021dcc288@slackware.uk>
Message-ID: <7b647fa5-32f4-4880-93aa-650d308acadb@slint.fr>

Le 11/01/2024 ? 20:51, B. Watson a ?crit?
> 
> On Thu, 11 Jan 2024, Didier Spaier wrote:
> 
>> Attached.
> 
> Diffed the two...
> 
> 200d199

I have done some (more) mistake, you were right the GUI works now.

Thanks again, and sorry for the noise.

Cheers,
Didier

From zhu.qunying at gmail.com  Thu Jan 11 22:18:25 2024
From: zhu.qunying at gmail.com (Qun-Ying)
Date: Thu, 11 Jan 2024 14:18:25 -0800
Subject: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a
 Slackware 32 bit
In-Reply-To: <c5dad648-bad9-43cb-9097-1b3b97ddd964@giand.it>
References: <c5dad648-bad9-43cb-9097-1b3b97ddd964@giand.it>
Message-ID: <CAHiy0bRDTs5kqv6dUva21EvqZ4msTVeNf+ci19UFNYWrJXLa6w@mail.gmail.com>

You may try to modified the build script to disable parallel build:
"${NINJA:=ninja}" -j$(expr $(nproc) / 2)
=>
"${NINJA:=ninja}" -j1


On 1/11/24, Giancarlo Dess? <slack at giand.it> wrote:
> Hi
>
> I have a Slackware 15.0 (32 bit) installed in a virtual machine. I use
> it for testing my slackbuilds, but I have problems when I have to build
> webkit2gtk or webkit2gtk4.1 required as dependencies for some packages.
> The script crashes due to the high resources absorbed by ninja and I
> can't continue with the tests.
>
> A solution could be the installation of a prebuilt package, but I don't
> find these packages for 32-bit. Does anyone know where I can possibly
> find them? I need both webkit2gtk and webkit2gtk4.1
>
> Thanks for help
>
> Giancarlo
>
> --
> *********************************************************
> Giancarlo Dess?
> https://www.giand.it
> https://github.com/giandex
>
> Slackware Linux... because it works!
> *********************************************************
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 
Qun-Ying

From urchlay at slackware.uk  Fri Jan 12 05:31:41 2024
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 12 Jan 2024 00:31:41 -0500 (EST)
Subject: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a
 Slackware 32 bit
In-Reply-To: <CAHiy0bRDTs5kqv6dUva21EvqZ4msTVeNf+ci19UFNYWrJXLa6w@mail.gmail.com>
References: <c5dad648-bad9-43cb-9097-1b3b97ddd964@giand.it>
 <CAHiy0bRDTs5kqv6dUva21EvqZ4msTVeNf+ci19UFNYWrJXLa6w@mail.gmail.com>
Message-ID: <593225f-58fa-be78-ff4-d18cb161ad8e@slackware.uk>



On Thu, 11 Jan 2024, Qun-Ying wrote:

> "${NINJA:=ninja}" -j$(expr $(nproc) / 2)

What maniac wrote this? If you run it on a single-core box, nproc says
1, integer-divided by 2... means it runs "ninja -j0". And according to
ninja's --help, -j0 means "infinity". This might be the cause of the
OP's problem.

It'd be better to extract the -j# from MAKEFLAGS (if set) and use that
for ninja's -j option (or, if MAKEFLAGS not set, don't pass ninja a -j
at all, which works the same way as make: 1 job).

From slack at giand.it  Fri Jan 12 06:16:12 2024
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=)
Date: Fri, 12 Jan 2024 07:16:12 +0100
Subject: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a
 Slackware 32 bit
In-Reply-To: <593225f-58fa-be78-ff4-d18cb161ad8e@slackware.uk>
References: <c5dad648-bad9-43cb-9097-1b3b97ddd964@giand.it>
 <CAHiy0bRDTs5kqv6dUva21EvqZ4msTVeNf+ci19UFNYWrJXLa6w@mail.gmail.com>
 <593225f-58fa-be78-ff4-d18cb161ad8e@slackware.uk>
Message-ID: <9811e5f3-e4d5-4ea7-9791-ad36138595be@giand.it>

Il 12/01/24 06:31, B. Watson ha scritto:
>
>
> On Thu, 11 Jan 2024, Qun-Ying wrote:
>
>> "${NINJA:=ninja}" -j$(expr $(nproc) / 2)
>
> What maniac wrote this? If you run it on a single-core box, nproc says
> 1, integer-divided by 2... means it runs "ninja -j0". And according to
> ninja's --help, -j0 means "infinity". This might be the cause of the
> OP's problem.
>
> It'd be better to extract the -j# from MAKEFLAGS (if set) and use that
> for ninja's -j option (or, if MAKEFLAGS not set, don't pass ninja a -j
> at all, which works the same way as make: 1 job).

Thanks a lot for replies. I'm completely ignorant about ninja, so I 
didn't know the solution was so simple! I'll change the script, thanks

Giancarlo



> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it
https://github.com/giandex

Slackware Linux... because it works!
*********************************************************


From 475.chris.willing at gmail.com  Fri Jan 12 08:28:27 2024
From: 475.chris.willing at gmail.com (Christoph Willing)
Date: Fri, 12 Jan 2024 18:28:27 +1000
Subject: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a
 Slackware 32 bit
In-Reply-To: <03d05940-93b2-45e9-b2d9-1d78bcd639e3@linux.com>
References: <03d05940-93b2-45e9-b2d9-1d78bcd639e3@linux.com>
Message-ID: <b0449040-07e2-4d0b-82be-698b54ed993d@linux.com>

On 12/1/24 15:31, B. Watson wrote:

>> "${NINJA:=ninja}" -j$(expr $(nproc) / 2)
>
> What maniac wrote this? If you run it on a single-core box, nproc says
> 1, integer-divided by 2... means it runs "ninja -j0". And according to
> ninja's --help, -j0 means "infinity". This might be the cause of the
> OP's problem.
>
> It'd be better to extract the -j# from MAKEFLAGS (if set) and use that
> for ninja's -j option (or, if MAKEFLAGS not set, don't pass ninja a -j
> at all, which works the same way as make: 1 job).

Is this idiom a thing that sbolint could check for and warn about (or 
fail)? I thought using -j option like this in SBo SlackBuilds was banned 
(or at least highly discouraged).

chris


From urchlay at slackware.uk  Fri Jan 12 20:45:51 2024
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 12 Jan 2024 15:45:51 -0500 (EST)
Subject: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a
 Slackware 32 bit
In-Reply-To: <b0449040-07e2-4d0b-82be-698b54ed993d@linux.com>
References: <03d05940-93b2-45e9-b2d9-1d78bcd639e3@linux.com>
 <b0449040-07e2-4d0b-82be-698b54ed993d@linux.com>
Message-ID: <7114b8fe-c61a-ab54-3ee1-ef2f27c4652f@slackware.uk>



On Fri, 12 Jan 2024, Christoph Willing wrote:

> Is this idiom a thing that sbolint could check for and warn about (or fail)?

It could... though, it's complex enough that it might not be all that reliable.

Also consider... The original code was:

"${NINJA:=ninja}" -j$(expr $(nproc) / 2)

But this actually would have been OK and not resulted in "-j0" on a single-proc
system:

"${NINJA:=ninja}" -j$(expr $(nproc) / 2 + 1)

That would have done what the author intended: use half the available
cores, or 1 core on a single-core box.

Possibly sbolint could just warn if it sees -j passed to ninja at all
(not an error, just a "make sure this does what you expect" kind of
thing).

> I thought using -j option like this in SBo SlackBuilds was banned (or at 
> least highly discouraged).

For make, that's true. The only 'approved' use of -j for make is -j1, for
stuff that fails to build with parallelism.

Reading up a bit on ninja... without the -j, its default number of jobs
is based on the number of cores. On mine, with 8 cores, "ninja --help" says:

   -j N     run N jobs in parallel (0 means infinity) [default=10 on this system]

So there's theoretically no need for a MAKEFLAGS-like setting for ninja.

In practice, for large projects like webkit2gtk, the limiting factor
becomes virtual memory (RAM + swap). If I don't have enough memory to
support 10 jobs, the build fails. Whoever added the -j$(expr $(nproc) / 2)
to webkit2gtk was probably trying to avoid running out of
memory... ninja doesn't have an environment variable to set options
like make does, or else it could have just been a comment in the
README. Sigh.

Personally, I like the idea of having a ninja-using SlackBuild grab
the -jN option from MAKEFLAGS in the environment, to give the user
some control that's otherwise lacking. But I wouldn't try to make that
a requirement for everyone else.

Another idea, we could define our own NINJAFLAGS. Code in the SlackBuild
would be simple:

"${NINJA:=ninja}" $NINJAFLAGS

That could become part of meson.template.

Opinions?

From urchlay at slackware.uk  Fri Jan 12 22:05:29 2024
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 12 Jan 2024 17:05:29 -0500 (EST)
Subject: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a
 Slackware 32 bit
In-Reply-To: <7114b8fe-c61a-ab54-3ee1-ef2f27c4652f@slackware.uk>
References: <03d05940-93b2-45e9-b2d9-1d78bcd639e3@linux.com>
 <b0449040-07e2-4d0b-82be-698b54ed993d@linux.com>
 <7114b8fe-c61a-ab54-3ee1-ef2f27c4652f@slackware.uk>
Message-ID: <fdbca36d-2eb3-549f-c7d-9d8d2749e165@slackware.uk>



On Fri, 12 Jan 2024, B. Watson wrote:

> But this actually would have been OK and not resulted in "-j0" on a 
> single-proc
> system:
>
> "${NINJA:=ninja}" -j$(expr $(nproc) / 2 + 1)
>
> That would have done what the author intended: use half the available
> cores, or 1 core on a single-core box.

The perils of posting code in an email without testing it. Slight correction:

"${NINJA:=ninja}" -j$(expr \( $(nproc) + 1 \) / 2 )

...works out to -j1 if you have 1, 2, or 3 cores, -j2 if you
have 4 or 5, -j4 if you have 8...

From willysr at slackbuilds.org  Sat Jan 13 00:28:40 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 13 Jan 2024 07:28:40 +0700
Subject: [Slackbuilds-users] Updates - 20240113.1
Message-ID: <5720086d-039d-4be0-a5d4-1ae63afc1164@slackbuilds.org>

Sat Jan 13 00:15:21 UTC 2024
academic/arpack-ng: Updated for version 3.9.1
academic/cblas: Updated for version 3.12.0
academic/fet: Updated for version 6.15.1.
academic/gerbv: Updated for version 2.10.0.
academic/lapacke: Updated for version 3.12.0
academic/octave: Updated for version 8.4.0
academic/stellarium: Updated for version 23.4.
audio/JDSP4Linux: Updated for version 2.7.
audio/yabridge: Fix typo
desktop/breeze-snow-cursor-theme: Removed (included in Slackware)
desktop/enlightenment: Updated for version 0.26.0.
desktop/lxqt-panel: Explicitly require lxqt-menu-data for compliation
desktop/nwg-clipman: Added (a GTK3-based GUI for cliphist).
desktop/nwg-panel: Updated for version 0.9.21
desktop/nwg-shell-config: Updated for version 0.5.31
desktop/nwg-shell: Updated for version 0.5.28
desktop/rss-guard: updated for version 4.6.3
development/Editra: Removed (Unmaintained).
development/abseil-cpp: Added (collection of C++).
development/actionlint: Fix DOWNLOAD.
development/arduino-cli: Updated for version 0.35.0
development/avrdude: Updated for version 7.2.
development/aws-cdk: Updated for version 2.118.0.
development/bbcsdl: Update script.
development/byacc: Updated for version 20240109.
development/github-cli: Updated for version 2.42.0
development/hopper: Updated for version 5.13.5.
development/jupyter_packaging: Update README
development/kforth: Script update.
development/lua-language-server: Updated for version 3.7.4.
development/nodejs: Updated for version 20.11.0.
development/postman: Updated for version 10.22.0
development/protoc-gen-go-grpc: Added (implementation of gRPC).
development/protoc-gen-go: Added (Go support for protobuf).
development/qb64pe: Updated for version 3.11.0.
development/tofuenv: Added (development tool).
development/xxd-standalone: Updated for version 9.1.0023.
development/zulu-openjdk21: Added (Java Development Kit).
games/Sokoban: Update deps & email.
games/ags: updated for version 3.6.0.56
games/ardentryst: Update deps & email.
games/assaultcube-reloaded: Updated for version 2.18.2.
games/asteroidsinfinity: Update deps.
games/cosmic_assault: Update deps.
games/endgame-singularity: Update deps.
games/freeorion: Updated for version 0.5.
games/fuse-emulator: Updated for version 1.5.7.
games/lightyears: Update deps.
games/openttd: Updated for version 13.4.
games/pgn-extract: Added (chess game).
games/solarwolf: Update deps.
games/unvanquished: Removed (Unmaintained).
games/vcmi: updated for version 1.4.2
gis/python3-basemap: Updated for version 1.4.0.
graphics/FotoKilof: Updated for version 4.4.3.
graphics/MaterialX: Update script.
graphics/OpenShadingLanguage: Updated for version 1.12.14.0.
graphics/birdfont: Update README.
graphics/converseen: Updated for version 0.12.0.2.
graphics/gnofract4d: Updated for version 4.3.
graphics/lilypond: Updated for version 2.24.3
graphics/mirage: updated for version 0.11.2
graphics/vuescan: Updated for version 9.8.24.
ham/gridtracker: Updated for version 1.24.0104.
ham/sdrangel: Updated for version 7.17.3.
ham/tucnak: Updated for version 4.54.
libraries/allegro: updated for version 5.2.9.0
libraries/bitsery: Remove test
libraries/blas: Updated for version 3.12.0
libraries/botocore: Updated for version 1.34.14.
libraries/efl: Updated for version 1.27.0.
libraries/facebook-python: Removed (Unmaintained).
libraries/gwenhywfar: Updated for version 5.10.2.
libraries/lapack: Updated for version 3.12.0
libraries/leptonica: Updated for version 1.84.1.
libraries/librepfunc: Added (function collection).
libraries/libspectrum: Updated for version 1.5.0.
libraries/libxmlbird: Updated for version 1.2.15.
libraries/libzia: Updated for version 4.54.
libraries/oath-toolkit: Updated for version 2.6.10.
libraries/oath-toolkit: Updated for version 2.6.11.
libraries/python-efl: Updated for version 1.26.1.
libraries/re2: Update for 2023_11_01 (+new maintainer)
misc/bitwarden-desktop: Updated for version 2024.1.0
misc/cliphist: Added (wayland-based clipboard).
misc/open-simh: Update for version c077c22
multimedia/MediathekView: Updated for version 14.0.0.
multimedia/OpenLP: Removed (Unmaintained).
multimedia/rav1e: Updated for version 0.7.1.
multimedia/winff: Updated for version 20231003_31b79e3.
network/DarTui: Removed (Unmaintained).
network/Electrum: Updated for version 4.5.0.
network/awscli: Updated for version 1.32.14.
network/brave-browser: Updated for version 1.61.116.
network/dnscrypt-proxy: Align to template.
network/dnscrypt-proxy: Updated for v2.1.5
network/dropbox: Updated for version 190.4.6383.
network/element-desktop: Updated for version 1.11.53
network/exim: Updated for version 4.97.1.
network/gmvault: Removed (Unmaintained).
network/go-sendxmpp: Updated for version 0.8.0.
network/goimapnotify: Updated for version 2.3.10.
network/light-firefox: Removed (Unmaintained).
network/livestreamer-curses: Removed (Unmaintained).
network/livestreamer: Removed (Unmaintained).
network/otter: Updated for version 1.0.03.
network/protonmail-bridge: Updated for version 3.8.1.
network/rclone: Updated for version 1.65.1.
network/signal-desktop: Updated for version 6.44.0.
network/suricata: Removed (Unmaintained).
network/telegram: Updated for version 4.14.3.
network/telegram: Updated for version 4.14.4.
network/vivaldi: Updated for version 6.5.3206.53.
network/wireshark: Updated for version 4.2.2.
office/impressive: Update deps.
office/openoffice.org: Updated for version 4.1.15.
office/pandoc-bin: Updated for version 3.1.11.1.
perl/perl-Date-Manip: Updated for version 6.94.
python/Logbook: Removed (Unmaintained).
python/PyPy3: updated for version 7.3.14
python/PyPy: updated for version 7.3.14
python/buildbot-badges: updated for version 3.10.1
python/buildbot-worker: updated for version 3.10.1
python/buildbot: updated for version 3.10.1
python/cryptography: Add mkvendor script.
python/cryptography: Updated for version 41.0.7.
python/flake8: Updated for version 7.0.0.
python/i3expo-ng: Update deps.
python/jsonpointer: Update for 2.4
python/odoo: Update deps.
python/pipdeptree: Updated for version 2.13.2.
python/pyOpenSSL: Updated for version 22.1.0.
python/pycodestyle: Updated for version 2.11.1.
python/pygame: Removed (splitted to python2 & python3).
python/pypy3: updated for version 7.3.14
python/pypy: updated for version 7.3.14
python/pysass: Update deps.
python/python-libsass: Removed (replaced by python3-libsass).
python/python2-pygame: Added (python2 version of pygame).
python/python3-Flask-Dance: Fix build.
python/python3-WTForms: Updated for version 3.1.2.
python/python3-alembic: updated for version 1.13.1
python/python3-anyio: Update README
python/python3-attrs: Updated for version 23.2.0.
python/python3-boto3: Update for 1.34.11
python/python3-cattrs: Updated for version 23.2.3.
python/python3-comm: Update for 0.2.1
python/python3-gensim: Update for 4.3.2
python/python3-icalendar: Added (Calendar Application).
python/python3-klein: updated for version 23.12.0
python/python3-kombu: updated REQUIRES
python/python3-libsass: Added (sass module).
python/python3-logbook: Added (Python Logger).
python/python3-more-itertools: Updated for version 10.2.0.
python/python3-patsy: Update for 0.5.6
python/python3-pyflakes: Updated for version 3.2.0.
python/python3-pygame: Added (python3 version of pygame).
python/python3-pynvim: Updated for version 0.5.0.
python/python3-pyrsistent: Update for 0.20.0
python/python3-pywayland: Update README
python/python3-regex: Update for 2023.12.25
python/python3-seaborn: Update for 0.13.1
python/python3-sge: Update deps.
python/python3-smart_open: Update for 6.4.0
python/python3-trove-classifiers: Updated for version 2024.1.8.
python/python3-vine: Added (Python3 version of Vine).
python/python3-wcwidth: updated for version 0.2.13
python/python3-webcolors: Update for 1.13
python/sge-pygame: Removed (Unmaintained).
python/vine: Removed (replaced by python3-vine)
system/B-em: Update for version 12d7ba4.
system/CPU-X: Updated for version 5.0.3.
system/FreeFileSync: Updated for version 13.3.
system/Iosevka-aile: Updated for version 28.0.4.
system/Iosevka-etoile: Updated for version 28.0.4.
system/apparmor: Updated for version 3.1.6.
system/atop: Fix doinst.sh.
system/atop: Updated for version 2.10.0.
system/b2: Updated for version 20231011_172305_4bd1939.
system/docker-buildx: Updated for version 0.12.1.
system/dust: Updated for version 0.9.0.
system/eaglemode: Updated for version 0.96.1.
system/fonts-bengali-extra: Added (system fonts).
system/fonts-indic-archaic: Added (system fonts).
system/fonts-indic-ne: Added (system fonts).
system/fonts-indic-other: Added (system fonts).
system/fonts-oriya-extra: Added (system fonts).
system/fonts-telugu-extra: Updated for version 1.3.
system/fonts-tibetan-extra: Added (system fonts).
system/gnupg-pkcs11-scd: Added (gnupg pkcs11).
system/greetd: Update greetd.info
system/kbfs: Added (kbfs client).
system/libtrash: Update for 3.8
system/limine: Updated for version 6.20240107.0
system/locust: Updated for version 2.20.1.
system/mbuffer: Update version to 20240107
system/memtest86+: Updated for version 7.00
system/mongo-tools: Updated for version 100.9.4.
system/mongodb: Updated for version .
system/pam_ssh_agent_auth: Added (SSH Agent).
system/pgbadger: updated for version 12.4
system/redis: updated for version 7.2.4
system/sarasa-gothic: Updated for version 1.0.3.
system/slpkg: Updated for version 4.9.7.
system/terminology: Updated for version 1.13.0.
system/winetricks: updated for version 20240105
system/yubico-piv-tool: Added (PIV application of Yubikey).
+--------------------------+


-- 
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/20240113/e55f2573/attachment.asc>

From slackbuilds at schoepfer.info  Sat Jan 13 05:18:05 2024
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 13 Jan 2024 06:18:05 +0100
Subject: [Slackbuilds-users] lightdm
Message-ID: <B9FD5C9A-99CC-4AB1-BAF0-714AD2EF871B@schoepfer.info>

Hi,

in https://slackbuilds.org/uid_gid.txt i saw that a uid/gid for lightdm is listet, but there is no buildscript on SBo.
Is someone already working on this?

If not, i'd like to put some work on this for a submission.

Johannes 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240113/79d8128a/attachment.htm>

From rworkman at slackbuilds.org  Sat Jan 13 06:00:13 2024
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 13 Jan 2024 00:00:13 -0600
Subject: [Slackbuilds-users] lightdm
In-Reply-To: <B9FD5C9A-99CC-4AB1-BAF0-714AD2EF871B@schoepfer.info>
References: <B9FD5C9A-99CC-4AB1-BAF0-714AD2EF871B@schoepfer.info>
Message-ID: <20240113000013.76de949e@home.rlworkman.net>

On Sat, 13 Jan 2024 06:18:05 +0100
Franzen via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:

> in https://slackbuilds.org/uid_gid.txt i saw that a uid/gid for
> lightdm is listet, but there is no buildscript on SBo. Is someone
> already working on this?
> 
> If not, i'd like to put some work on this for a submission.


I gave this a start, and it works here and tested out fine for a
few others, but I'm just short on time and never got around to
doing any (possibly) needed final touches.

See attached. Feel free to use/modify as desired.
Tarball has both lightdm and lightdm-gtk-greeter in it.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ldm.tar.gz
Type: application/gzip
Size: 5984 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240113/39580400/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240113/39580400/attachment-0001.asc>

From didier at slint.fr  Sat Jan 13 13:12:54 2024
From: didier at slint.fr (Didier Spaier)
Date: Sat, 13 Jan 2024 13:12:54 +0000
Subject: [Slackbuilds-users] lightdm
In-Reply-To: <20240113000013.76de949e@home.rlworkman.net>
References: <B9FD5C9A-99CC-4AB1-BAF0-714AD2EF871B@schoepfer.info>
 <20240113000013.76de949e@home.rlworkman.net>
Message-ID: <5c918773-0ece-4de2-8ae2-63becb87bec0@slint.fr>

Hi,

Le 13/01/2024 ? 06:00, Robby Workman a ?crit?:
> I gave this a start, and it works here and tested out fine for a
> few others, but I'm just short on time and never got around to
> doing any (possibly) needed final touches.
> 
> See attached. Feel free to use/modify as desired.
> Tarball has both lightdm and lightdm-gtk-greeter in it.

You can add a package for the lighdm-gtk-greeter-settings. Salix, and following
suite Slint provide it, alongside the two other packages, for instance the
sources for Salix are  in:
https://slackware.uk/salix/x86_64/15.0/source/xap/
and for Slint in:
https://slackware.uk/slint/x86_64/slint-15.0/source/

Caveats:
1. No SlackBuilds there but SLKBUILDs to be processed by slkbuild:
https://github.com/gapan/slkbuild

However someone wrote a script to convert a PKGBUILD from Arch (similar to a
SLKBUILD) to a SlackBuild. If I can find it again I will post a link here.

2. There are some discrepancies, eg. for the uuid.guid

Also, several distros including Arch now ship lightdm-slick-greeter as an
alternative:
https://github.com/linuxmint/slick-greeter"
which is also based on GTK.

Cheers,
Didier


From zhu.qunying at gmail.com  Sat Jan 13 23:17:50 2024
From: zhu.qunying at gmail.com (Qun-Ying)
Date: Sat, 13 Jan 2024 15:17:50 -0800
Subject: [Slackbuilds-users] Please remove the package refind
Message-ID: <CAHiy0bRDfk6=6YX9EhEcLZC+sJjMvWv8nDLrmnV-V2fJFG95pg@mail.gmail.com>

Hi,

Please remove refind, it has renamed to refind-bin.


-- 
Qun-Ying

From willysr at slackbuilds.org  Sun Jan 14 01:43:12 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 14 Jan 2024 08:43:12 +0700
Subject: [Slackbuilds-users] Please remove the package refind
In-Reply-To: <CAHiy0bRDfk6=6YX9EhEcLZC+sJjMvWv8nDLrmnV-V2fJFG95pg@mail.gmail.com>
References: <CAHiy0bRDfk6=6YX9EhEcLZC+sJjMvWv8nDLrmnV-V2fJFG95pg@mail.gmail.com>
Message-ID: <db156148-f300-4f60-9c47-3a0b71ca9939@slackbuilds.org>

> Please remove refind, it has renamed to refind-bin.

Done on my branch

-- 
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/20240114/a46ceae5/attachment.asc>

From antonioleal at yahoo.com  Sun Jan 14 20:25:19 2024
From: antonioleal at yahoo.com (Antonio Leal)
Date: Sun, 14 Jan 2024 20:25:19 +0000
Subject: [Slackbuilds-users] Tests updating Lazarus to version 3.0
In-Reply-To: <988024fa-17f2-4770-8de6-706183ec3cb7@yahoo.com>
References: <15b44e05-d11d-4e90-a9a6-07a5cd510880.ref@yahoo.com>
 <15b44e05-d11d-4e90-a9a6-07a5cd510880@yahoo.com>
 <dc6d772-ad82-2a40-4714-67daa78cad73@slackware.uk>
 <988024fa-17f2-4770-8de6-706183ec3cb7@yahoo.com>
Message-ID: <3a44ab36-1384-4c62-858e-82fa6297c9dc@yahoo.com>

Hi all,

I have started the update of Lazarus to version 3.0. Two points:

a) The package libqtpas requires to be updated to use Lazarus 3.0. I 
successfully contacted the maintainer Vijay Marcel which will update 
libqtpas during this week.

b) Last December I tried to contact the doublecmd-qt5 package at 
"no at no.noooo.ooo" and got no reply.

 ??? Since current doublecmd-qt breaks with Lazarus 3.0 which I've 
updated today, I kindly *ask an SBo admin* to step in and also update 
doublecmd-qt to the new version released today. I submitted a proposal 
in the SBo site.

 ??? Current doublecmd-qt does not build on 32 bits as it needs a 
reference to "i386". So my update proposal is:


diff --unified doublecmd-qt5/doublecmd-qt5.SlackBuild 
doublecmd-qt5.new/doublecmd-qt5.SlackBuild
--- doublecmd-qt5/doublecmd-qt5.SlackBuild??? 2023-11-18 
02:19:55.000000000 +0000
+++ doublecmd-qt5.new/doublecmd-qt5.SlackBuild??? 2024-01-14 
17:33:20.138867724 +0000
@@ -25,7 +25,7 @@
 ?cd $(dirname $0) ; CWD=$(pwd)
 ?PRGNAM=doublecmd-qt5
 ?UPSTR_PRGNAME=doublecmd
-VERSION=${VERSION:-1.0.11}
+VERSION=${VERSION:-1.1.9}
 ?BUILD=${BUILD:-1}
 ?TAG=${TAG:-_SBo}
 ?OUTPUT=${OUTPUT:-/tmp}
@@ -35,7 +35,7 @@

 ?if [ -z "$ARCH" ]; then
 ? case "$( uname -m )" in
-?? i?86) ARCH=i586 ;;
+?? i?86) ARCH=i386 ;;
 ??? arm*) ARCH=arm ;;
 ??? *) ARCH=$( uname -m ) ;;
 ? esac
@@ -46,7 +46,9 @@
 ?? exit 0
 ?fi

-if [ "$ARCH" = "i586" ]; then
+if [ "$ARCH" = "i386" ]; then
+??? SLKLAZBUILDFLAGS="--cpu=i386"
+elif [ "$ARCH" = "i586" ]; then
 ???? SLKLAZBUILDFLAGS="--cpu=i586"
 ?elif [ "$ARCH" = "i686" ]; then
 ???? SLKLAZBUILDFLAGS="--cpu=i686"
@@ -65,6 +67,10 @@
 ?cd "$TMP/$PRGNAM-$VERSION"
 ?tar -zxvf "$CWD"/${UPSTR_PRGNAME}-$VERSION-src.tar.gz
 ?cd ${UPSTR_PRGNAME}-${VERSION}
+
+# 20240113 ALe: this symlink is mistargeted... removed
+rm -rf doublecmd.app/Contents/MacOS/doublecmd
+
 ?chown -R root:root .
 ?chmod -R u+w,go+r-w,a-s .
 ?find -L . \
@@ -102,6 +108,7 @@
 ?# Gzip man page
 ?gzip $PKG/usr/man/man1/doublecmd.1

+
 ?# Make package.
 ?mkdir -p $PKG/install
 ?mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
diff --unified doublecmd-qt5/doublecmd-qt5.info 
doublecmd-qt5.new/doublecmd-qt5.info
--- doublecmd-qt5/doublecmd-qt5.info??? 2023-11-18 02:19:55.000000000 +0000
+++ doublecmd-qt5.new/doublecmd-qt5.info??? 2024-01-14 
17:26:36.888204475 +0000
@@ -1,10 +1,10 @@
 ?PRGNAM="doublecmd-qt5"
-VERSION="1.0.11"
+VERSION="1.1.9"
 ?HOMEPAGE="http://doublecmd.sourceforge.net/"
-DOWNLOAD="https://downloads.sourceforge.net/project/doublecmd/Double%20Commander%20Source/doublecmd-1.0.11-src.tar.gz"
-MD5SUM="f55d4fcfe1c3206a015cfb65e3936fed"
+DOWNLOAD="https://downloads.sourceforge.net/project/doublecmd/Double%20Commander%20Source/doublecmd-1.1.9-src.tar.gz"
+MD5SUM="c7920140bc2f2cb17ca151e5d94eebeb"
 ?DOWNLOAD_x86_64=""
 ?MD5SUM_x86_64=""
-REQUIRES="lazarus"
+REQUIRES="lazarus libqtpas"
 ?MAINTAINER="Hao Chi Kiang"
 ?EMAIL="no at no.noooo.ooo"

Regards

Ant?nio



On 26/12/23 23:54, Antonio Leal via SlackBuilds-users wrote:
> Indeed I could build both latest doublecmd-qt5 and winff with new 
> Lazarus directly from source.
>
> But doublecmd-qt5 is in beta.
>
> I contacted the maintainers so maybe an upgrade can be coordinated.
>
> Thanks for the help.
>
>
> On 26/12/23 22:04, B. Watson wrote:
>>
>>
>> Sorry this got so long & verbose, hopefully it'll be helpful.
>>
>> On Tue, 26 Dec 2023, Antonio Leal via SlackBuilds-users wrote:
>>
>>> So doublecmd-qt5 and winff don't build with new Lazarus.
>>
>> Looks like doublecmd development moved from sourceforge to github,
>> see https://github.com/doublecmd/doublecmd/releases
>>
>> Possibly the latest 1.1.x release will build & work with lazarus 3.0?
>>
>> This would be a case where you coordinate with the maintainer. However,
>> he's given his email address as "no at no.noooo.ooo" which doesn't look 
>> like
>> a real address. Maybe he's subscribed to this mailing list, and will see
>> this thread...?
>>
>> For winff, there's also new releases. What we've got in our repo is a 
>> random
>> git commit from September 2022. If you look here:
>>
>> https://github.com/WinFF/winff/tags
>>
>> ...you'll see that there have been several releases since
>> then. Perhaps the latest will work with lazarus 3.0. Here, the SBo
>> maintainer is active and has a real email address, so you should
>> coordinate with him.
>>
>>> What is the SlackBuilds policy in this situation?
>>>
>>> a) Stay with current Lazarus 2.2.6 and hope that all packages will 
>>> eventually build correctly? Who keeps checking this and how?
>>
>> You're the lazarus maintainer, so you check it... which you have done,
>> and are doing. Also the maintainers of the other builds should check.
>>
>>> b) Notify maintainers and upgrade Lazarus to 3.0 anyway?
>>
>> Breaking peoples' builds by updating their dependencies is
>> rude. Notifying them that you're about to do it is slightly less rude,
>> but it's still a hassle: puts pressure on the maintainer to drop
>> whatever else he's doing and fix his build (that wasn't broken until
>> you broke it). Not a good way to treat unpaid volunteers...
>>
>>> c) Other?
>>
>> My preferred way of dealing with this situation is, I'd patch
>> the dependees (doublecmd-qt5 and winff), possibly updating them
>> to new versions. Get them working with the new lazarus. Then send
>> the diffs to their builds (and lazarus) to the maintainers for their
>> consideration. If they're OK with your changes, either they can submit
>> the updates, or allow you to do it.
>>
>> If you use github or some other public git repo, you can do it as a
>> fork/branch. If you'd rather, you can just email the diffs (I'd say
>> gzip them first). Since the doublecmd-qt5 maintainer's email address
>> is bogus, I guess you have to mail the diffs to this mailing list too.
>> If you do that, and we don't hear from him within some reasonable
>> amount of time, most likely an SBo admin will step in and update his
>> build.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240114/114fe01f/attachment-0001.htm>

From juanma1980 at disroot.org  Mon Jan 15 09:58:31 2024
From: juanma1980 at disroot.org (juanma1980 at disroot.org)
Date: Mon, 15 Jan 2024 10:58:31 +0100
Subject: [Slackbuilds-users] Hi all, first question about package naming
Message-ID: <9370061fdbf0a05c86b1ffc792c0b68e@disroot.org>

Hi all.

I've created a slackbuild for gbinder-python ( 
https://github.com/waydroid/gbinder-python ) but I''ve doubts about how 
shall be the package named: python3-gbinder as usual with python modules 
or gbinder-python as the real name of the project?

Thx in advance,

-- 
=== In soft we trust ===
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240115/a99cf394/attachment.htm>

From willysr at slackbuilds.org  Mon Jan 15 10:08:39 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 15 Jan 2024 17:08:39 +0700
Subject: [Slackbuilds-users] Hi all, first question about package naming
In-Reply-To: <9370061fdbf0a05c86b1ffc792c0b68e@disroot.org>
References: <9370061fdbf0a05c86b1ffc792c0b68e@disroot.org>
Message-ID: <c977aa30-8983-4664-98c3-5215fa1dc5e4@slackbuilds.org>

> I've created a slackbuild for gbinder-python ( 
> https://github.com/waydroid/gbinder-python ) but I''ve doubts about how 
> shall be the package named: python3-gbinder as usual with python modules 
> or gbinder-python as the real name of the project?

python3-gbinder is good

-- 
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/20240115/955729f3/attachment.asc>

From slack at giand.it  Mon Jan 15 10:11:27 2024
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=)
Date: Mon, 15 Jan 2024 11:11:27 +0100
Subject: [Slackbuilds-users] Please remove or fix qgis from approved
Message-ID: <b66d8bb5-c10c-4d9c-9082-49e2e5aebae5@giand.it>

Sorry, I found just now that the new version of the slackbuild submitted 
includes the command "make -j 10"

I you remove from approved I'll send a correct tarball, but it could be 
enough to remove the option -j

thanks

Giancarlo

-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it
https://github.com/giandex

Slackware Linux... because it works!
*********************************************************


From willysr at slackbuilds.org  Mon Jan 15 10:19:00 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 15 Jan 2024 17:19:00 +0700
Subject: [Slackbuilds-users] Please remove or fix qgis from approved
In-Reply-To: <b66d8bb5-c10c-4d9c-9082-49e2e5aebae5@giand.it>
References: <b66d8bb5-c10c-4d9c-9082-49e2e5aebae5@giand.it>
Message-ID: <d5a47b35-cda2-4e51-be38-f58b57f89a14@slackbuilds.org>

> Sorry, I found just now that the new version of the slackbuild submitted 
> includes the command "make -j 10"
> 
> I you remove from approved I'll send a correct tarball, but it could be 
> enough to remove the option -j

Fixed on my branch, no need to resubmit

-- 
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/20240115/d43c1ef8/attachment.asc>

From arnaud.garcia-fernandez at laposte.net  Mon Jan 15 10:17:57 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Mon, 15 Jan 2024 11:17:57 +0100
Subject: [Slackbuilds-users] Hi all, first question about package naming
In-Reply-To: <9370061fdbf0a05c86b1ffc792c0b68e@disroot.org>
References: <9370061fdbf0a05c86b1ffc792c0b68e@disroot.org>
Message-ID: <20240115111757.0dd3ae428e17436dee1cbfb1@laposte.net>

> Hi all.
> 
> I've created a slackbuild for gbinder-python ( 
> https://github.com/waydroid/gbinder-python ) but I''ve doubts about how 
> shall be the package named: python3-gbinder as usual with python modules 
> or gbinder-python as the real name of the project?
> 
> Thx in advance,
> 
> -- 
> === In soft we trust ===

You can look on repology here :
https://repology.org/projects/?search=gbinder
Clicking on the * next to gbinder-python shows that :
https://repology.org/project/gbinder-python/related
Where you can see that this package has different names, and that's fine.
So python3-gbinder or even python3-gbinder-python both looks OK.
gbinder-python doesn't specify which python, and the decision has been to
prefix python packages with python2/3.

I say that because sometime it's not that easy, for exemple for
python3-python-editor, I need that name, because python-editor
and editor are two different projects, so we could have a
python3-editor and a python3-python-editor.

And, well, repology is not a reference, but it's useful, or at least
practical, to be properly referenced there.

 - Yth.

From juanma1980 at disroot.org  Mon Jan 15 10:36:34 2024
From: juanma1980 at disroot.org (juanma1980 at disroot.org)
Date: Mon, 15 Jan 2024 11:36:34 +0100
Subject: [Slackbuilds-users] Hi all, first question about package naming
In-Reply-To: <20240115111757.0dd3ae428e17436dee1cbfb1@laposte.net>
References: <9370061fdbf0a05c86b1ffc792c0b68e@disroot.org>
 <20240115111757.0dd3ae428e17436dee1cbfb1@laposte.net>
Message-ID: <8b655f4aabd4f961088032c31c9032a8@disroot.org>

Ok, I see.. So in this case I think the name should be 
"python3-gbinder-python", perhaps a bit complex but clearly identifies 
python release and real name of the project.

Cheers

El 2024-01-15 11:17, Arnaud via SlackBuilds-users va escriure:

>> Hi all.
>> 
>> I've created a slackbuild for gbinder-python (
>> https://github.com/waydroid/gbinder-python ) but I''ve doubts about 
>> how
>> shall be the package named: python3-gbinder as usual with python 
>> modules
>> or gbinder-python as the real name of the project?
>> 
>> Thx in advance,
>> 
>> --
>> === In soft we trust ===
> 
> You can look on repology here :
> https://repology.org/projects/?search=gbinder
> Clicking on the * next to gbinder-python shows that :
> https://repology.org/project/gbinder-python/related
> Where you can see that this package has different names, and that's 
> fine.
> So python3-gbinder or even python3-gbinder-python both looks OK.
> gbinder-python doesn't specify which python, and the decision has been 
> to
> prefix python packages with python2/3.
> 
> I say that because sometime it's not that easy, for exemple for
> python3-python-editor, I need that name, because python-editor
> and editor are two different projects, so we could have a
> python3-editor and a python3-python-editor.
> 
> And, well, repology is not a reference, but it's useful, or at least
> practical, to be properly referenced there.
> 
> - Yth.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

-- 
=== In soft we trust ===
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240115/10036cfc/attachment-0001.htm>

From willysr at slackbuilds.org  Mon Jan 15 10:37:33 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 15 Jan 2024 17:37:33 +0700
Subject: [Slackbuilds-users] Hi all, first question about package naming
In-Reply-To: <8b655f4aabd4f961088032c31c9032a8@disroot.org>
References: <9370061fdbf0a05c86b1ffc792c0b68e@disroot.org>
 <20240115111757.0dd3ae428e17436dee1cbfb1@laposte.net>
 <8b655f4aabd4f961088032c31c9032a8@disroot.org>
Message-ID: <0119ee9b-1888-44ae-8ec4-1a48d295be9d@slackbuilds.org>

> Ok, I see.. So in this case I think the name should be 
> "python3-gbinder-python", perhaps a bit complex but clearly identifies 
> python release and real name of the project.

python3-gbinder is enough, no need to have another python at the back

-- 
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/20240115/975b43dd/attachment.asc>

From arnaud.garcia-fernandez at laposte.net  Mon Jan 15 10:42:07 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Mon, 15 Jan 2024 11:42:07 +0100
Subject: [Slackbuilds-users] Hi all, first question about package naming
In-Reply-To: <0119ee9b-1888-44ae-8ec4-1a48d295be9d@slackbuilds.org>
References: <9370061fdbf0a05c86b1ffc792c0b68e@disroot.org>
 <20240115111757.0dd3ae428e17436dee1cbfb1@laposte.net>
 <8b655f4aabd4f961088032c31c9032a8@disroot.org>
 <0119ee9b-1888-44ae-8ec4-1a48d295be9d@slackbuilds.org>
Message-ID: <20240115114207.a2d192f6bc7c05d5e700808c@laposte.net>

On Mon, 15 Jan 2024 17:37:33 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> > Ok, I see.. So in this case I think the name should be 
> > "python3-gbinder-python", perhaps a bit complex but clearly identifies 
> > python release and real name of the project.
> 
> python3-gbinder is enough, no need to have another python at the back
> 
> -- 
> Willy Sudiarto Raharjo

It would only become a problem if a python project called only ? gbinder ? appears.
Looking at the choices made by other distributions, people don't think it's very likely.

 - Yth.

From dev at iotib.net  Mon Jan 15 16:20:05 2024
From: dev at iotib.net (Charadon)
Date: Mon, 15 Jan 2024 16:20:05 +0000
Subject: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a
 Slackware 32 bit
In-Reply-To: <7114b8fe-c61a-ab54-3ee1-ef2f27c4652f@slackware.uk>
References: <03d05940-93b2-45e9-b2d9-1d78bcd639e3@linux.com>
 <b0449040-07e2-4d0b-82be-698b54ed993d@linux.com>
 <7114b8fe-c61a-ab54-3ee1-ef2f27c4652f@slackware.uk>
Message-ID: <75f07e8d-c0d2-40aa-8c9a-13da255dfaac@iotib.net>

We could go even simpler, and just have an environment variable called 
JOBS that gets applied, and then if it's not defined, use the original 
method of using half of the cores. So the code would look like:

`-j${JOBS:-"$(expr "$(nproc)" / 2 + 1)"}`

On 1/12/24 8:45 PM, B. Watson wrote:
>
>
> On Fri, 12 Jan 2024, Christoph Willing wrote:
>
>> Is this idiom a thing that sbolint could check for and warn about (or 
>> fail)?
>
> It could... though, it's complex enough that it might not be all that 
> reliable.
>
> Also consider... The original code was:
>
> "${NINJA:=ninja}" -j$(expr $(nproc) / 2)
>
> But this actually would have been OK and not resulted in "-j0" on a 
> single-proc
> system:
>
> "${NINJA:=ninja}" -j$(expr $(nproc) / 2 + 1)
>
> That would have done what the author intended: use half the available
> cores, or 1 core on a single-core box.
>
> Possibly sbolint could just warn if it sees -j passed to ninja at all
> (not an error, just a "make sure this does what you expect" kind of
> thing).
>
>> I thought using -j option like this in SBo SlackBuilds was banned (or 
>> at least highly discouraged).
>
> For make, that's true. The only 'approved' use of -j for make is -j1, for
> stuff that fails to build with parallelism.
>
> Reading up a bit on ninja... without the -j, its default number of jobs
> is based on the number of cores. On mine, with 8 cores, "ninja --help" 
> says:
>
> ? -j N???? run N jobs in parallel (0 means infinity) [default=10 on 
> this system]
>
> So there's theoretically no need for a MAKEFLAGS-like setting for ninja.
>
> In practice, for large projects like webkit2gtk, the limiting factor
> becomes virtual memory (RAM + swap). If I don't have enough memory to
> support 10 jobs, the build fails. Whoever added the -j$(expr $(nproc) 
> / 2)
> to webkit2gtk was probably trying to avoid running out of
> memory... ninja doesn't have an environment variable to set options
> like make does, or else it could have just been a comment in the
> README. Sigh.
>
> Personally, I like the idea of having a ninja-using SlackBuild grab
> the -jN option from MAKEFLAGS in the environment, to give the user
> some control that's otherwise lacking. But I wouldn't try to make that
> a requirement for everyone else.
>
> Another idea, we could define our own NINJAFLAGS. Code in the SlackBuild
> would be simple:
>
> "${NINJA:=ninja}" $NINJAFLAGS
>
> That could become part of meson.template.
>
> Opinions?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

From erich.public at protonmail.com  Mon Jan 15 16:30:17 2024
From: erich.public at protonmail.com (Erich Ritz)
Date: Mon, 15 Jan 2024 16:30:17 +0000
Subject: [Slackbuilds-users] python3-attrs requires python3-hatch_vcs
Message-ID: <PfL9psFJsxslOGLPFuUOsO2ANiEaeirznXSpdrwV2goCkHRF5PRdxeKbaAZlz2VnQtjGvN6xCi0l6Bfnqbf77mLzAdjiOhTi6zhjVGoBaoM=@protonmail.com>

Hi Dave,

Trying to build python3-attrs after latest update results in:

ERROR Missing dependencies:
	hatch-vcs
python/python3-attrs: python3-attrs.SlackBuild failed (status 1)        14:59:58
Unmounting chroot ... 
:-( python/python3-attrs FAILED )-:

Adding:

# cat /var/lib/slackrepo/etr/hintfiles/python3-attrs.hint
ADDREQUIRES="python3-hatch_vcs"


Results in a successful build.

Erich

From erich.public at protonmail.com  Mon Jan 15 16:33:36 2024
From: erich.public at protonmail.com (Erich Ritz)
Date: Mon, 15 Jan 2024 16:33:36 +0000
Subject: [Slackbuilds-users] python3-attrs requires python3-hatch_vcs
In-Reply-To: <PfL9psFJsxslOGLPFuUOsO2ANiEaeirznXSpdrwV2goCkHRF5PRdxeKbaAZlz2VnQtjGvN6xCi0l6Bfnqbf77mLzAdjiOhTi6zhjVGoBaoM=@protonmail.com>
References: <PfL9psFJsxslOGLPFuUOsO2ANiEaeirznXSpdrwV2goCkHRF5PRdxeKbaAZlz2VnQtjGvN6xCi0l6Bfnqbf77mLzAdjiOhTi6zhjVGoBaoM=@protonmail.com>
Message-ID: <-g8fjOx_ASDafXsN62Oh5Y1XLKowitFKMNHj0L6LBKYX_cE9Pevffc3XlbkzW_l_sdnMYz5g46XVQzBFxkkGLqH_Uvc3K7N-GZHwsuU41lQ=@protonmail.com>

On Monday, January 15th, 2024 at 10:30 AM, Erich Ritz via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:


> 
> 
> Hi Dave,
> 
> Trying to build python3-attrs after latest update results in:
> 
> ERROR Missing dependencies:
> hatch-vcs
> python/python3-attrs: python3-attrs.SlackBuild failed (status 1) 14:59:58
> Unmounting chroot ...
> :-( python/python3-attrs FAILED )-:
> 
> Adding:
> 
> # cat /var/lib/slackrepo/etr/hintfiles/python3-attrs.hint
> ADDREQUIRES="python3-hatch_vcs"
> 
> 
> Results in a successful build.
> 
> Erich

Sorry, should have checked git.  Already fixed: https://git.slackbuilds.org/slackbuilds/commit/?h=user/aclemons/updates&id=3b73de557c4aa335838bc1bf6ca88ad70c76e455

Erich

From sbo at linuxgalaxy.org  Tue Jan 16 17:45:44 2024
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Tue, 16 Jan 2024 17:45:44 +0000
Subject: [Slackbuilds-users] RFC: remove cdw or new maintainer?
Message-ID: <42f016f4-ab47-479f-9cef-b314afea8aca@linuxgalaxy.org>

Hello All:

cdw (CLI frontend for cdrtools etc) was last updated in 2016.  From 
upstream:

2023-01-01
This project has been closed
Version 0.8.1 was the last version released by its current developer 
(acerion) and published on cdw.sf.net. There will be no new releases, no 
bug fixes, and no support will be provided by or through cdw.sf.net. The 
project may be picked up by someone else, but the developer of this 
project (acerion) will not be involved in that new project.

On 2023.01.01 this project has been closed.

It still compiles on 15.0, however I have not fully tested cdw, nor plan 
to, as I no longer use this software.  There are newer tools, both CLI 
and GUI).  I recommend that cdw be dropped when Current -> Stable 
because after then cdw will be dead to me.

Unless, of course, there is someone who wants to take it over and hunt 
for the inevitable patches.

-kb


From alik at ejik.org  Thu Jan 18 17:47:10 2024
From: alik at ejik.org (Alexander Verbovetsky)
Date: Thu, 18 Jan 2024 20:47:10 +0300
Subject: [Slackbuilds-users] ocserv uid/gid
Message-ID: <ZalkHjok0tOB0pW/@mail.ejik.org>

Hello,

I'm writing an ocserv SlackBuild. This is an openconnect vpn ssl server,
which should be run as ocserv user. Shall I use 382 for it?

Best regards,
Alexander

From willysr at slackbuilds.org  Fri Jan 19 01:51:00 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 19 Jan 2024 08:51:00 +0700
Subject: [Slackbuilds-users] ocserv uid/gid
In-Reply-To: <ZalkHjok0tOB0pW/@mail.ejik.org>
References: <ZalkHjok0tOB0pW/@mail.ejik.org>
Message-ID: <35dbff2c-3ffa-4c58-b6db-f530e0c20dff@slackbuilds.org>

> I'm writing an ocserv SlackBuild. This is an openconnect vpn ssl server,
> which should be run as ocserv user. Shall I use 382 for it?

yes, i reserved 382 for ocserv already

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240119/1ff50abc/attachment-0001.bin>
-------------- 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/20240119/1ff50abc/attachment-0001.asc>

From dchmelik at gmail.com  Fri Jan 19 07:23:47 2024
From: dchmelik at gmail.com (dchmelik at gmail.com)
Date: Thu, 18 Jan 2024 23:23:47 -0800
Subject: [Slackbuilds-users] Dungeon Crawl Stone Soup RPG/fantasy/roguelike
 game v0.31 (update available, revising?)
Message-ID: <10c6659d-2738-2135-cce7-1e0c793dc1ed@gmail.com>

Uploaded Dungeon Crawl Stone Soup (DCSS, crawl) 0.31.0 SlackBuild to my 
servers; almost ready to submit to SlackBuilds.org but noticed strange 
thing.? One or more people (maybe freenode, now libera IRC, #slackbuilds 
) helped me create this in 2010s, and possibly staff revised, and for 
some reason says 'make $TARGET', but $TARGET is undefined... what should 
be done?? If anyone likes this game they're free to takeover 
crawl.SlackBuild; I prefer older versions and Stoat Soup so may not 
always get around to updates unless requested.

http://mirror.davidchmelik.com/math/slackbuilds/games/crawl.tar.xz (most 
uptime)
http://davidchmelik.com/math/slackbuilds/games/crawl.tar.xz (updated first)


From riza.dindir at gmail.com  Fri Jan 19 09:26:18 2024
From: riza.dindir at gmail.com (Riza Dindir)
Date: Fri, 19 Jan 2024 12:26:18 +0300
Subject: [Slackbuilds-users] Gradle version upgrade
Message-ID: <CA+ek4BG0XsrUWOqNf64LhP--s_CYs3nk4ZH21OPs_zn1juaZ4g@mail.gmail.com>

Hello

This message would be for the site administrator, but I am not sure.

I wanted to use gradle on slackware (I am using slackware 15.0 with the
latest 5.15.145 kernel). The current version of the gradle package is
5.5.1. The current version of gradle is 8.5.

I contacted the maintainer of the package, in the hope that maybe they
could upgrade the version. But the mail seems to be invalid. The mail
bounces back with an "address not found" message.

In the meantime, I have changed the gradle package to use the latest gradle
version. Have created and installed it on my machine. It seems to be
working, and I am able to build C++, and java packages, besides other
projects that use gradle.

I was wondering if it would be ok if I submit that package to
slackbuilds.org?

Regards
Riza Dindir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240119/a91692f6/attachment.htm>

From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net  Fri Jan 19 09:41:26 2024
From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Vladimir Nikishkin)
Date: Fri, 19 Jan 2024 17:41:26 +0800
Subject: [Slackbuilds-users] Gradle version upgrade
In-Reply-To: <CA+ek4BG0XsrUWOqNf64LhP--s_CYs3nk4ZH21OPs_zn1juaZ4g@mail.gmail.com>
References: <CA+ek4BG0XsrUWOqNf64LhP--s_CYs3nk4ZH21OPs_zn1juaZ4g@mail.gmail.com>
Message-ID: <87y1cl64m8.fsf@laptop.lockywolf.net>

Gradle 5.5.1 is very old, I suspect that it is that old because it is
the last version which was used with a systemwide installation.

Nowadays most projects use Gradle through the "gradle wrapper",
gradlew/gradlew.bat, so I suggest looking into that. It might fit you
better.


Riza Dindir <riza.dindir at gmail.com> writes:

> Hello
>
> This message would be for the site administrator, but I am not sure.
>
> I wanted to use gradle on slackware (I am using slackware 15.0 with the latest 5.15.145 kernel). The current
> version of the gradle package is 5.5.1. The current version of gradle is 8.5.
>
> I contacted the maintainer of the package, in the hope that maybe they could upgrade the version. But the mail
> seems to be invalid. The mail bounces back with an "address not found" message.
>
> In the meantime, I have changed the gradle package to use the latest gradle version. Have created and
> installed it on my machine. It seems to be working, and I am able to build C++, and java packages, besides
> other projects that use gradle.
>
> I was wondering if it would be ok if I submit that package to slackbuilds.org?
>
> Regards
> Riza Dindir
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


-- 
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)

From riza.dindir at gmail.com  Fri Jan 19 13:05:12 2024
From: riza.dindir at gmail.com (Riza Dindir)
Date: Fri, 19 Jan 2024 16:05:12 +0300
Subject: [Slackbuilds-users] Gradle version upgrade
Message-ID: <CA+ek4BEJDrnwPrGH0XwPiEUAJQUF33goaO8gfumd6iOHFd6cbw@mail.gmail.com>

Hello Vladimir

Yes you might use gradlew to upgrade your projects, and maybe gradle
itself. I am not familiar with that. But you would need to have a gradle
project for that to function I believe.

I did not have gradle, and no gradle project at hand. So I needed to
install gradle.

When we would have the latest gradle version in the slackbuilds packages,
this would make it easier for people who did not install gradle yet.

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240119/e62662d1/attachment.htm>

From urchlay at slackware.uk  Fri Jan 19 13:40:42 2024
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 19 Jan 2024 08:40:42 -0500 (EST)
Subject: [Slackbuilds-users] Gradle version upgrade
In-Reply-To: <CA+ek4BG0XsrUWOqNf64LhP--s_CYs3nk4ZH21OPs_zn1juaZ4g@mail.gmail.com>
References: <CA+ek4BG0XsrUWOqNf64LhP--s_CYs3nk4ZH21OPs_zn1juaZ4g@mail.gmail.com>
Message-ID: <3b95472d-538e-c95d-8011-5ab7b78e15df@slackware.uk>



On Fri, 19 Jan 2024, Riza Dindir wrote:

> I was wondering if it would be ok if I submit that package to slackbuilds.org?

Since the maintainer hasn't been active for 3.5 years (last activitiy
May 2020), yes, go ahead.

From dickson.tim at googlemail.com  Fri Jan 19 22:56:08 2024
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Fri, 19 Jan 2024 22:56:08 +0000
Subject: [Slackbuilds-users] issue with openimageio after pybind11 update
Message-ID: <db5a1931-b60e-4c2d-8a6b-91b82c4808ae@googlemail.com>

since the pybind11 update opencolorio is no longer building for me.
at 86% it gives
[ 86%] Linking CXX executable ociolutimage
/usr/bin/ld: warning: libdcmimage.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libdcmimgle.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libdcmdata.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: liboflog.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libofstd.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFString::OFString()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmStack::top() const'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFLog::configure(OFLogger::LogLevel)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmFileFormat::getDataset()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFFilename::OFFilename(char const*, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetFloat32(DcmTagKey const&, float&, unsigned long, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DiRegister::DiRegister()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmTag::getTagName()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmFileFormat::loadFile(OFFilename const&, E_TransferSyntax, 
E_GrpLenEncoding, unsigned int, E_FileReadMode)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DicomImage::DicomImage(char const*, unsigned long, unsigned long, 
unsigned long)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetOFString(DcmTagKey const&, OFString&, unsigned long, 
bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DiRegister::~DiRegister()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmFileFormat::DcmFileFormat()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetSint32(DcmTagKey const&, int&, unsigned long, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetUint32(DcmTagKey const&, unsigned int&, unsigned 
long, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFString::~OFString()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmStack::DcmStack()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmStack::~DcmStack()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetFloat64(DcmTagKey const&, double&, unsigned long, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFFilename::~OFFilename()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetUint16(DcmTagKey const&, unsigned short&, unsigned 
long, bool)'
collect2: error: ld returned 1 exit status
make[2]: *** 
[src/apps/ociolutimage/CMakeFiles/ociolutimage.dir/build.make:100: 
src/apps/ociolutimage/ociolutimage] Error 1
make[1]: *** [CMakeFiles/Makefile2:1690: 
src/apps/ociolutimage/CMakeFiles/ociolutimage.dir/all] Error 2
make: *** [Makefile:146: all] Error 2

I don't know why it's trying to link to libOpenImageIO files when it is 
not marked as a dependency (I do have openimageio-2.2.21.0-4 installed)
anyone else seeing this or got a fix?
thanks,Tim

From 475.chris.willing at gmail.com  Sat Jan 20 01:31:51 2024
From: 475.chris.willing at gmail.com (Christoph Willing)
Date: Sat, 20 Jan 2024 11:31:51 +1000
Subject: [Slackbuilds-users] issue with openimageio after pybind11 update
In-Reply-To: <db5a1931-b60e-4c2d-8a6b-91b82c4808ae@googlemail.com>
References: <db5a1931-b60e-4c2d-8a6b-91b82c4808ae@googlemail.com>
Message-ID: <359c07af-49f6-4352-b809-2ac22fd45adb@linux.com>

On 20/1/24 08:56, Tim Dickson via SlackBuilds-users wrote:
> since the pybind11 update opencolorio is no longer building for me.
> []
>
> I don't know why it's trying to link to libOpenImageIO files when it 
> is not marked as a dependency (I do have openimageio-2.2.21.0-4 
> installed)
> anyone else seeing this or got a fix?
> thanks,Tim

openimageio and opencolorio will each try to link against the other if 
present. It's an unfortunate "natural" recursive dependency which I try 
to minimise in the .info files by setting opencolorio as a dependency of 
openimageio but _not_ setting openimageio as a dependency of 
opencolorio. This attempted minimisation fails in the case where 
openimageio is already installed when building opencolorio, which is 
exactly your situation.

If a clean VM for building is not available, I would recommend that you 
temporarily remove openimageio, then build opencolorio, then reinstall 
(or even better: rebuild & install) openimageio.

chris


From willysr at slackbuilds.org  Sat Jan 20 02:31:31 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 20 Jan 2024 09:31:31 +0700
Subject: [Slackbuilds-users] Updates - 20240120.1
Message-ID: <e89f269d-387d-4afc-92f6-832dc13d5c77@slackbuilds.org>

hi

just to give some update about our CI engine
In this batch of update, aclemons have started to put some basic 
foundation for our gitlab platform in order to have similar experience 
we have in github.
For now, it is able to run sbolint to check for your submissions 
compliance toward our template, but hopefully we can have full CI engine 
soon.


Sat Jan 20 02:17:00 UTC 2024
academic/boinc: Updated for version 7.24.1
academic/gmsh: Updated for version 4.12.1.
academic/gpredict: Added aarch64 flags
academic/pspp: Updated for version 2.0.0.
academic/qhull: Remove outdated octave symlinks.
academic/sword-data-kjv: Fix install location.
desktop/artix-backgrounds: Update for 2023.12
desktop/nwg-clipman: Updated for version 0.2.0.
desktop/nwg-displays: Updated for version 0.3.12.
desktop/py3status: Updated for version 3.55.
desktop/todoman: update deps
desktop/xfce4-battery-plugin: Updated for version 1.1.5.
desktop/xfce4-eyes-plugin: Updated for version 4.6.0.
desktop/xfce4-fsguard-plugin: Updated for version 1.1.3.
desktop/xfdashboard: Added (Dashboard for XFCE).
development/CImg: Updated for version 3.3.3
development/argagg: Added aarch64 flags
development/aws-cdk: Updated for version 2.121.0.
development/azuredatastudio: Updated for version 1.47.1
development/bluefish: Updated for version 2.2.14
development/fpc: Update script.
development/github-cli: Updated for version 2.42.1
development/gradle: Updated for version 8.5.
development/jupyter-nbconvert: Update for 7.14.1
development/kaaedit: Updated for version 0.54.0.
development/lazarus: Updated for version 3.0.
development/liberica-jdk-bin: Updated for version 21.0.2+14.
development/mysql-workbench: Updated for version 8.0.36.
development/php82: Updated for version 8.2.15
development/sqlcl: Updated for version 23.3.0.270.1251.
development/terraform: Updated for version 1.7.0.
development/tiled: Added aarch64 flags
development/vscode-bin: Updated for version 1.85.2.
development/xxd-standalone: Updated for version 9.1.0041.
games/berusky2-data: Updated for version 0.12.
games/berusky2: Updated for version 0.12.
games/edgar: Updated for version 1.37.
games/flare-game: Added aarch64 flags
games/flare: Added aarch64 flags
games/gargoyle: Added aarch64 flags
games/openclonk: Updated for version 8.1.
games/planetblupi: Added aarch64 flags
games/puzzles: Updated for version 20240103.7a93ae5.
games/tome: Updated for version 1.7.6.
games/wesnoth: Updated for version 1.16.11
gis/gdal: Updated for version 3.8.3.
gis/gpsbabel: Updated for version 1.9.0
gis/libgeotiff: Updated for versino 1.7.1. New maintainer.
gis/osm2pgsql-legacy: Added (legacy version of osm2pgsql).
gis/pgrouting: Updated for version 3.6.1.
gis/python3-xarray: Updated for version 2024.01.0.
gis/pytrainer: Updated for version 2.2.1
gis/qgis: Remove parallel.
gis/qgis: Updated for version 3.34.2.
gis/therion: Updated for version 6.2.0.
graphics/FotoKilof: Updated for version 4.4.4.
graphics/advancecomp: Updated for version 2.6.
graphics/chafa: Update chafa.SlackBuild
graphics/graphviz: Added aarch64 flags
graphics/vuescan: Updated for version 9.8.25.
libraries/DevIL: Added aarch64 flags
libraries/GitPython: Updated for version 3.1.41.
libraries/SDL2_sound: Added aarch64 flags
libraries/discogs-client: Removed (Unmaintained).
libraries/dropbox-python: Updated for version 11.36.2.
libraries/dumb: Added aarch64 flags
libraries/grpc: Remove Python 3 support
libraries/highway: Update highway.SlackBuild
libraries/htmlcxx: Added aarch64 flags
libraries/libavif: Update libavif.SlackBuild
libraries/libcbor: Added aarch64 flags
libraries/libfabric: Update libfabric.SlackBuild
libraries/libgbinder: Added (GLib-style interface to binder).
libraries/libglibutil: Added (Android GLIB).
libraries/libindi-drivers: Updated for version 2.0.5
libraries/libindi-libraries: Updated for version 2.0.5
libraries/libindi-libraries: update dependencies
libraries/libindi: Updated for version 2.0.5
libraries/libjodycode: Added aarch64 flags
libraries/libjwt: Added aarch64 flags
libraries/libjxl: Update libjxl.SlackBuild
libraries/libqtpas: Updated for version 2.15.
libraries/libslirp: Update libslirp.SlackBuild
libraries/libyuv: Update libyuv.SlackBuild
libraries/orcania: Added aarch64 flags
libraries/poco: Updated for version 1.12.5, rm stale patch
libraries/setproctitle: Updated for version 1.3.3.
libraries/yder: Added aarch64 flags
multimedia/ffmpegfs: Update ffmpegfs.SlackBuild
multimedia/goom: Update goom.SlackBuild
multimedia/gxine: Update gxine.SlackBuild
multimedia/inputstream.adaptive: Version bump to 20.3.16
multimedia/kodi: Version bump to 20.3
multimedia/kvazaar: Update kvazaar.SlackBuild
multimedia/openh264: Update openh264.SlackBuild
multimedia/pocketsphinx: Update pocketsphinx.SlackBuild
multimedia/videomass: Added (GUI for ffmpeg).
multimedia/w_scan2: Updated for version 1.0.15.
multimedia/w_scan_cpp: Added (DVB Scanner).
network/Electrum: Updated for version 4.5.1.
network/Flootty: Removed (Unmaintained).
network/TeamSpeak3: Updated for version 3.6.1
network/darkhttpd: updated for version 1.15
network/discord: Version bump to 0.0.40
network/dkimproxy: Added aarch64 flags
network/go-sendxmpp: Updated for version 0.8.2.
network/goimapnotify: Fix CVE-2022-28948.
network/jitsi-meet-desktop: Updated for version 2024.1.0
network/nessus: Added (vulnerability scanner).
network/nss-tls: Added (dns over https).
network/opera: Updated for version 106.0.4998.52.
network/sshuttle: Added aarch64 flags
network/telegram: Updated for version 4.14.8.
network/thttpd: Added aarch64 flags
network/translate: Updated for version 3.6.1.
network/vivaldi: Updated for version 6.5.3206.55.
office/calibre-bin: Updated for version 7.4.0.
office/focuswriter-qt6: Added aarch64 flags
office/focuswriter: Added aarch64 flags
office/khal: update deps
office/khard: update to version 0.19.1
office/mu: upgrade to version 1.10.8
python/PyPy3: updated for version 7.3.15
python/PyPy: updated for version 7.3.15
python/click-plugins: Added aarch64 flags
python/esptool: Updated for version 4.7.0.
python/freetype-py: Update freetype-py.SlackBuild
python/hg-git: updated for version 1.1.0
python/jsonpatch: Update for 1.33 (+new maintainer)
python/license-expression: Update license-expression.SlackBuild
python/mypy: Updated for version 1.8.0.
python/pandocfilters: Update for 1.5.1
python/pypy3: updated for version 7.3.15
python/pypy: updated for version 7.3.15
python/python-debian: Update python-debian.SlackBuild
python/python2-attrs: Added aarch64 flags
python/python2-pyasn1-modules: Added aarch64 flags
python/python2-pyasn1: Added aarch64 flags
python/python3-aksharamukha: Update python3-aksharamukha.SlackBuild
python/python3-anyio: Update for 4.2.0
python/python3-argcomplete: Update python3-argcomplete.SlackBuild
python/python3-asn1crypto: Added aarch64 flags
python/python3-attrs: Add missing dependency.
python/python3-authheaders: updated for version 0.16.1
python/python3-automat: Added aarch64 flags
python/python3-cachecontrol: Added (httplib2 caching algorithms).
python/python3-cffsubr: Update python3-cffsubr.SlackBuild
python/python3-compreffor: Update python3-compreffor.SlackBuild
python/python3-dep-logic: Added (python dependency specs).
python/python3-findpython: Added (Find python version).
python/python3-grpcio: Added (Python 3 build of grpc.).
python/python3-kodipydent: Fix pip check warning
python/python3-kombu: updated for version 5.3.5
python/python3-libretranslatepy: Added (Python bindings).
python/python3-lsp-black: Update README
python/python3-lsp-jsonrpc: Update for 1.1.2
python/python3-lsp-server: Remove python3-setuptools-opt dependency
python/python3-parso: Added aarch64 flags
python/python3-pdm-backend: Version bump to 2.1.8
python/python3-pdm: Version bump to 2.12.1
python/python3-pmw: Added (Python megawidgets).
python/python3-pyasn1-modules: Added aarch64 flags
python/python3-pyjwt: Added aarch64 flags
python/python3-python-editor: Added aarch64 flags
python/python3-resolvelib: Added (Resolve abstract deps).
python/python3-service-identity: updated for version 24.1.0
python/python3-shellingham: Added (Tool to Detect Surrounding Shell).
python/python3-stone: Added (Dropbox API).
python/python3-tubes: Added aarch64 flags
python/python3-txaio: Added aarch64 flags
python/python3-types-python-dateutil: Added (Typing stubs for 
python-dateutil).
python/python3-unearth: Added (fetch and download python packages).
python/python3-waitress: Added aarch64 flags
python/python3-webencodings: Added aarch64 flags
python/python3-webob: Added aarch64 flags
python/tinycss2: Updated for version 1.2.1.
python/tinycss: Removed (Unmaintained).
system/brlaser: Updated for version 6.2.6.
system/docker-compose: Updated for version 2.24.1
system/dosbox: Added aarch64 flags
system/doublecmd-qt5: Updated for version 1.1.9.
system/fastfetch: Updated for version 2.6.0.
system/forkstat: Updated for version 0.03.02.
system/geckodriver: Updated for version 0.34.0.
system/hivex: Update hivex.SlackBuild
system/jdupes: Added aarch64 flags
system/memkind: Update memkind.SlackBuild
system/osquery-bin: Updated for version 5.11.0.
system/pmdk: Update pmdk.SlackBuild
system/redis-py: Added aarch64 flags
system/refind: Removed (use refind-bin).
system/restic: Updated for version 0.16.3
system/sqldiff: Added aarch64 flags
system/telegraf: Updated for version 1.29.2
system/timeshift: Updated for version 24.01.1.
system/usermin: Updated for version 2.005.
system/webmin: Updated for version 2.105.
system/wine-staging: Updated for version 9.0.
system/wine: Updated for version 9.0.
system/xonsh: Updated for version 0.14.4.
+--------------------------+


-- 
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/20240120/9906ca23/attachment.asc>

From dickson.tim at googlemail.com  Sat Jan 20 09:11:16 2024
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Sat, 20 Jan 2024 09:11:16 +0000
Subject: [Slackbuilds-users] issue with openimageio after pybind11 update
In-Reply-To: <359c07af-49f6-4352-b809-2ac22fd45adb@linux.com>
References: <db5a1931-b60e-4c2d-8a6b-91b82c4808ae@googlemail.com>
 <359c07af-49f6-4352-b809-2ac22fd45adb@linux.com>
Message-ID: <529e3256-fd58-4d94-a27b-e0589dd4c2b4@googlemail.com>

thanks for the heads up chris, I wondered if that might be the case.
Maybe a note in the opencolorio readme to temporarily uninstall 
openimageio if present before building the package would be useful?
regards, Tim

On 20/01/2024 01:31, Christoph Willing wrote:
> On 20/1/24 08:56, Tim Dickson via SlackBuilds-users wrote:
>> since the pybind11 update opencolorio is no longer building for me.
>> []
>>
>> I don't know why it's trying to link to libOpenImageIO files when it 
>> is not marked as a dependency (I do have openimageio-2.2.21.0-4 
>> installed)
>> anyone else seeing this or got a fix?
>> thanks,Tim
>
> openimageio and opencolorio will each try to link against the other if 
> present. It's an unfortunate "natural" recursive dependency which I 
> try to minimise in the .info files by setting opencolorio as a 
> dependency of openimageio but _not_ setting openimageio as a 
> dependency of opencolorio. This attempted minimisation fails in the 
> case where openimageio is already installed when building opencolorio, 
> which is exactly your situation.
>
> If a clean VM for building is not available, I would recommend that 
> you temporarily remove openimageio, then build opencolorio, then 
> reinstall (or even better: rebuild & install) openimageio.
>
> chris
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


From 475.chris.willing at gmail.com  Sat Jan 20 11:24:29 2024
From: 475.chris.willing at gmail.com (Christoph Willing)
Date: Sat, 20 Jan 2024 21:24:29 +1000
Subject: [Slackbuilds-users] issue with openimageio after pybind11 update
In-Reply-To: <529e3256-fd58-4d94-a27b-e0589dd4c2b4@googlemail.com>
References: <db5a1931-b60e-4c2d-8a6b-91b82c4808ae@googlemail.com>
 <359c07af-49f6-4352-b809-2ac22fd45adb@linux.com>
 <529e3256-fd58-4d94-a27b-e0589dd4c2b4@googlemail.com>
Message-ID: <7c1997bb-cff0-4533-b9e1-da88a87a7d8b@linux.com>

On 20/1/24 19:11, Tim Dickson via SlackBuilds-users wrote:
> thanks for the heads up chris, I wondered if that might be the case.
> Maybe a note in the opencolorio readme to temporarily uninstall 
> openimageio if present before building the package would be useful?
> regards, Tim

The problem with that is that while it solves the problem you had, it's 
not necessarily true in all situations.

Usually, after building opencolorio successfully, you would use that new 
build to rebuild openimageio. Having done that (new openimagio based on 
successful opencolorio), you will find that you can now rebuild 
opencolorio while leaving openimgeio in place. Now there will be some 
new optimisations in opencolorio using components available in 
openimageio. At that point you could rebuild openimageio against the 
updated opencolorio, presumably resulting in an optimised openimageio.

I'm unsure how to express all that simply enough without causing 
confusion for the average user who is probably just passing through on 
their way to a build of Blender. I'll think of something ...


chris


> On 20/01/2024 01:31, Christoph Willing wrote:
>> On 20/1/24 08:56, Tim Dickson via SlackBuilds-users wrote:
>>> since the pybind11 update opencolorio is no longer building for me.
>>> []
>>>
>>> I don't know why it's trying to link to libOpenImageIO files when it 
>>> is not marked as a dependency (I do have openimageio-2.2.21.0-4 
>>> installed)
>>> anyone else seeing this or got a fix?
>>> thanks,Tim
>>
>> openimageio and opencolorio will each try to link against the other 
>> if present. It's an unfortunate "natural" recursive dependency which 
>> I try to minimise in the .info files by setting opencolorio as a 
>> dependency of openimageio but _not_ setting openimageio as a 
>> dependency of opencolorio. This attempted minimisation fails in the 
>> case where openimageio is already installed when building 
>> opencolorio, which is exactly your situation.
>>
>> If a clean VM for building is not available, I would recommend that 
>> you temporarily remove openimageio, then build opencolorio, then 
>> reinstall (or even better: rebuild & install) openimageio.
>>
>> chris
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


From alik at ejik.org  Sat Jan 20 15:32:30 2024
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 20 Jan 2024 18:32:30 +0300
Subject: [Slackbuilds-users] gnustep-base fails to build with libxml2 ver.
 2.11.x
Message-ID: <ZavnjuCBs8VJ/NEV@mail.ejik.org>

Hello,

gnustep-base fails due to this bug:
https://github.com/gnustep/libs-base/issues/294

The fix is to remove 4 lines from Source/Additions/GSXML.m:

sed -i '/if (ret->checked == 0)/,+3d' Source/Additions/GSXML.m

or apply this patch:
https://github.com/gnustep/libs-base/commit/37913d0

Best regards,
Alexander

From tonus1 at free.fr  Sat Jan 20 16:12:04 2024
From: tonus1 at free.fr (Tonus)
Date: Sat, 20 Jan 2024 17:12:04 +0100
Subject: [Slackbuilds-users] Can't get this build right : trello-cli
Message-ID: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>

Hi all

I'm trying to update the trello-cli SlackBuild I maintain but fail to 
get it pass the sbopkglint tests.

I tryed to use the stripping binaries lines from the how-to but makes 
the build silently fail.

I don't know either how I should manage the symlinks.

If someone has a pointer or two...

Files are attached, sbopkglint output there :

??????? sbopkglint /tmp/trello-cli-1.0.6-x86_64-1_SBo.tgz 
Using tests from /usr/share/sbo-maintainer-tools/sbopkglint.d
Exploding /tmp/trello-cli-1.0.6-x86_64-1_SBo.tgz to /tmp/SBo/sbopkglint.cyELrX ...OK
Running pre-doinst test...
--- package contains actual symlinks:
lrwxrwxrwx 1 root root 40 janv. 20 17:04 ./usr/bin/trello -> ../lib64/node_modules/trello-cli/bin/run
lrwxrwxrwx 1 root root 18 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/acorn -> ../acorn/bin/acorn
lrwxrwxrwx 1 root root 22 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/cdl -> ../cardinal/bin/cdl.js
lrwxrwxrwx 1 root root 17 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/ejs -> ../ejs/bin/cli.js
lrwxrwxrwx 1 root root 25 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/esparse -> ../esprima/bin/esparse.js
lrwxrwxrwx 1 root root 28 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/esvalidate -> ../esprima/bin/esvalidate.js
lrwxrwxrwx 1 root root 19 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/is-docker -> ../is-docker/cli.js
lrwxrwxrwx 1 root root 18 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/jake -> ../jake/bin/cli.js
lrwxrwxrwx 1 root root 25 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/js-yaml -> ../js-yaml/bin/js-yaml.js
lrwxrwxrwx 1 root root 27 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/json2csv -> ../json2csv/bin/json2csv.js
lrwxrwxrwx 1 root root 23 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/node-which -> ../which/bin/node-which
lrwxrwxrwx 1 root root 26 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/prebuild-install -> ../prebuild-install/bin.js
lrwxrwxrwx 1 root root 12 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/rc -> ../rc/cli.js
lrwxrwxrwx 1 root root 23 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/semver -> ../semver/bin/semver.js
lrwxrwxrwx 1 root root 22 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/ts-node -> ../ts-node/dist/bin.js
lrwxrwxrwx 1 root root 26 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/ts-node-cwd -> ../ts-node/dist/bin-cwd.js
lrwxrwxrwx 1 root root 26 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/ts-node-esm -> ../ts-node/dist/bin-esm.js
lrwxrwxrwx 1 root root 29 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/ts-node-script -> ../ts-node/dist/bin-script.js
lrwxrwxrwx 1 root root 32 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/ts-node-transpile-only -> ../ts-node/dist/bin-transpile.js
lrwxrwxrwx 1 root root 40 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/ts-script -> ../ts-node/dist/bin-script-deprecated.js
lrwxrwxrwx 1 root root 21 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/tsc -> ../typescript/bin/tsc
lrwxrwxrwx 1 root root 26 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/tsserver -> ../typescript/bin/tsserver
lrwxrwxrwx 1 root root 19 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/yarn -> ../yarn/bin/yarn.js
lrwxrwxrwx 1 root root 19 janv. 20 17:04 ./usr/lib64/node_modules/trello-cli/node_modules/.bin/yarnpkg -> ../yarn/bin/yarn.js
FAILED
Installing /tmp/trello-cli-1.0.6-x86_64-1_SBo.tgz to /tmp/SBo/sbopkglint.cyELrX ...OK
Running test: 05-basic-sanity...OK
Running test: 10-docs...OK
Running test: 15-noarch...OK
Running test: 20-arch...
--- ELF object(s) not stripped:
-rwxr-xr-x 1 tonus 127 2038672 janv. 17 01:27 usr/lib64/node_modules/trello-cli/node_modules/better-sqlite3/build/Release/better_sqlite3.node
FAILED
Running test: 25-lafiles...OK
Running test: 30-manpages...OK
Running test: 35-desktop...OK
Running test: 40-newconfig...OK
Running test: 45-doinst...OK
Running test: 50-icons...OK
Running test: 60-usr_info...OK
Running test: 65-python...OK
Running test: 70-tmp_path...OK
Running test: 75-static_libs...OK
Running test: 85-perl...OK
!!! trello-cli-1.0.6-x86_64-1_SBo.tgz: 2 failures

-- 
Regards,

Tonus
-------------- next part --------------
#!/bin/bash

# Slackware build script for trello-cli

# Copyright 2020 Tonus
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

cd $(dirname $0) ; CWD=$(pwd)

PRGNAM=trello-cli
VERSION=${VERSION:-1.0.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
PKGTYPE=${PKGTYPE:-tgz}

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i586 ;;
    arm*) ARCH=arm ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
  echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
  exit 0
fi

TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}

set -e

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xvf $CWD/$PRGNAM-$VERSION.tgz
cd package
chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

DESTDIR=$PKG npm install -g $CWD/$PRGNAM-$VERSION.tgz

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a \
  README.md \
  $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

cd $PKG
/sbin/makepkg -l n -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE
-------------- next part --------------
PRGNAM="trello-cli"
VERSION="1.0.6"
HOMEPAGE="https://github.com/mheap/trello-cli/"
DOWNLOAD="https://registry.npmjs.org/trello-cli/-/trello-cli-1.0.6.tgz"
MD5SUM="2c35fd4b8327a38229d3db96833c9ac6"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
REQUIRES="google-go-lang nodejs"
MAINTAINER="Tonus"
EMAIL="tonus1 at free.fr"

From urchlay at slackware.uk  Sat Jan 20 16:58:21 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 20 Jan 2024 11:58:21 -0500 (EST)
Subject: [Slackbuilds-users] Can't get this build right : trello-cli
In-Reply-To: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
References: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
Message-ID: <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>



On Sat, 20 Jan 2024, Tonus wrote:

> I don't know either how I should manage the symlinks.
>
> If someone has a pointer or two...

You used "-l n" with makepkg (last line of the script), so the
package .tgz contains actual symlinks. The correct thing to do is
"-l y", which causes makepkg to generate a doinst.sh which creates the
symlinks at package install time.

I haven't tried to build this yet so I'm not sure about stripping the
binary, or why you're having problems with it. Will get back to you.

From willysr at slackbuilds.org  Sat Jan 20 17:16:15 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 21 Jan 2024 00:16:15 +0700
Subject: [Slackbuilds-users] gnustep-base fails to build with libxml2
 ver. 2.11.x
In-Reply-To: <ZavnjuCBs8VJ/NEV@mail.ejik.org>
References: <ZavnjuCBs8VJ/NEV@mail.ejik.org>
Message-ID: <c4401ac8-600d-42a1-b110-b1c21b948e2e@slackbuilds.org>

> gnustep-base fails due to this bug:
> https://github.com/gnustep/libs-base/issues/294
> 
> The fix is to remove 4 lines from Source/Additions/GSXML.m:
> 
> sed -i '/if (ret->checked == 0)/,+3d' Source/Additions/GSXML.m
> 
> or apply this patch:
> https://github.com/gnustep/libs-base/commit/37913d0

is this for -stable or -current?
i tested on -stable and it still build just fine

-- 
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/e7c5958f/attachment.asc>

From tonus1 at free.fr  Sat Jan 20 17:51:24 2024
From: tonus1 at free.fr (Tonus)
Date: Sat, 20 Jan 2024 18:51:24 +0100
Subject: [Slackbuilds-users] Can't get this build right : trello-cli
In-Reply-To: <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>
References: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
 <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>
Message-ID: <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>


On Sat, Jan 20, 2024 at 11:58:21AM -0500, B. Watson wrote:
>
>
>I haven't tried to build this yet so I'm not sure about stripping the
>binary, or why you're having problems with it. Will get back to you.
>_______________________________________________

Thanks a lot for your answer. It solves the link issues.

I think I looked at the wrong template and am on the right way for 
stripping the binairies.


-- 
Regards,

Tonus

From tonus1 at free.fr  Sat Jan 20 18:00:56 2024
From: tonus1 at free.fr (Tonus)
Date: Sat, 20 Jan 2024 19:00:56 +0100
Subject: [Slackbuilds-users] Can't get this build right : trello-cli
In-Reply-To: <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>
References: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
 <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>
 <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>
Message-ID: <i4auidb74fmy6iernubgrzsuf2vlw667flriiwwk2be2shqwtd@gi7p67jet7ld>

On Sat, Jan 20, 2024 at 06:51:24PM +0100, Tonus wrote:
>
>I think I looked at the wrong template and am on the right way for 
>stripping the binairies.
>

All tests pass fine now.

Thanks for the help.

I will update the script.

-- 
Regards,

Tonus

From slack at giand.it  Sat Jan 20 18:21:33 2024
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=)
Date: Sat, 20 Jan 2024 19:21:33 +0100
Subject: [Slackbuilds-users] issue with openimageio after pybind11 update
In-Reply-To: <7c1997bb-cff0-4533-b9e1-da88a87a7d8b@linux.com>
References: <db5a1931-b60e-4c2d-8a6b-91b82c4808ae@googlemail.com>
 <359c07af-49f6-4352-b809-2ac22fd45adb@linux.com>
 <529e3256-fd58-4d94-a27b-e0589dd4c2b4@googlemail.com>
 <7c1997bb-cff0-4533-b9e1-da88a87a7d8b@linux.com>
Message-ID: <2a4bdc5b-2e14-4b8e-a8fa-f07991a6fcfc@giand.it>


Il 20/01/24 12:24, Christoph Willing ha scritto:
> On 20/1/24 19:11, Tim Dickson via SlackBuilds-users wrote:
>> thanks for the heads up chris, I wondered if that might be the case.
>> Maybe a note in the opencolorio readme to temporarily uninstall 
>> openimageio if present before building the package would be useful?
>> regards, Tim
>
> The problem with that is that while it solves the problem you had, 
> it's not necessarily true in all situations.
>
> Usually, after building opencolorio successfully, you would use that 
> new build to rebuild openimageio. Having done that (new openimagio 
> based on successful opencolorio), you will find that you can now 
> rebuild opencolorio while leaving openimgeio in place. Now there will 
> be some new optimisations in opencolorio using components available in 
> openimageio. At that point you could rebuild openimageio against the 
> updated opencolorio, presumably resulting in an optimised openimageio.
>
> I'm unsure how to express all that simply enough without causing 
> confusion for the average user who is probably just passing through on 
> their way to a build of Blender. I'll think of something ...
>
>
If it's useful, I usually store a copy of the last package build for 
each slackbuild. This allows to install/reinstall a package for tests or 
issues that the recursive dependency OIIO/OCIO

Everytime we have to build OpenColorIO we make this without OpenImageIO 
installed in the system because it's autodetected and is not possible to 
disable the build of OCIO against OIIO

1) removepkg OpenImageIO

2) build of OpenColorIO and install

After this OpenImageIO must be rebuilt and reinstalled against the new 
version of OpenColorIO and the package stored in a repository-folder

It works for me


-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it
https://github.com/giandex

Slackware Linux... because it works!
*********************************************************


From alik at ejik.org  Sat Jan 20 18:51:23 2024
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 20 Jan 2024 21:51:23 +0300
Subject: [Slackbuilds-users] gnustep-base fails to build with libxml2
 ver. 2.11.x
In-Reply-To: <c4401ac8-600d-42a1-b110-b1c21b948e2e@slackbuilds.org>
References: <ZavnjuCBs8VJ/NEV@mail.ejik.org>
 <c4401ac8-600d-42a1-b110-b1c21b948e2e@slackbuilds.org>
Message-ID: <ZawWKwVFiRogVV0m@mail.ejik.org>

On Sun, Jan 21, 2024 at 12:16:15AM +0700, Willy Sudiarto Raharjo wrote:
> > gnustep-base fails due to this bug:
> > https://github.com/gnustep/libs-base/issues/294
> >
> > The fix is to remove 4 lines from Source/Additions/GSXML.m:
> >
> > sed -i '/if (ret->checked == 0)/,+3d' Source/Additions/GSXML.m
> >
> > or apply this patch:
> > https://github.com/gnustep/libs-base/commit/37913d0
>
> is this for -stable or -current?
> i tested on -stable and it still build just fine

Stable, completely patched 15.0, libxml2 is of version 2.11.6.

Best regards,
Alexander

From urchlay at slackware.uk  Sat Jan 20 18:55:45 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 20 Jan 2024 13:55:45 -0500 (EST)
Subject: [Slackbuilds-users] Can't get this build right : trello-cli
In-Reply-To: <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>
References: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
 <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>
 <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>
Message-ID: <2832a845-745f-deb5-a2f9-88181cb6b0@slackware.uk>



On Sat, 20 Jan 2024, Tonus wrote:

> Thanks a lot for your answer. It solves the link issues.
>
> I think I looked at the wrong template and am on the right way for stripping 
> the binairies.

I see one serious problem with your build: It requires network access
when it runs. npm downloads stuff from the 'net. See if you can come
up a way to do a purely local build... maybe just pre-download the
files npm wants to download, add them to your DOWNLOAD in the .info
file, have the script copy them to where npm would put them? I'm not a
npm expert so I don't know if this would be feasible...

From slack at giand.it  Sat Jan 20 19:05:43 2024
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=)
Date: Sat, 20 Jan 2024 20:05:43 +0100
Subject: [Slackbuilds-users] Updates - 20240120.1
In-Reply-To: <e89f269d-387d-4afc-92f6-832dc13d5c77@slackbuilds.org>
References: <e89f269d-387d-4afc-92f6-832dc13d5c77@slackbuilds.org>
Message-ID: <2126dd66-fddb-404d-9270-37376ff2137d@giand.it>


Il 20/01/24 03:31, Willy Sudiarto Raharjo ha scritto:
> hi
>
> just to give some update about our CI engine
> In this batch of update, aclemons have started to put some basic 
> foundation for our gitlab platform in order to have similar experience 
> we have in github.
> For now, it is able to run sbolint to check for your submissions 
> compliance toward our template, but hopefully we can have full CI 
> engine soon.
>
>
> Sat Jan 20 02:17:00 UTC 2024

[cut]

gis/osm2pgsql-legacy: Added (legacy version of osm2pgsql).

[cut]

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

-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it
https://github.com/giandex

Slackware Linux... because it works!
*********************************************************


From tonus1 at free.fr  Sat Jan 20 19:27:05 2024
From: tonus1 at free.fr (Tonus)
Date: Sat, 20 Jan 2024 20:27:05 +0100
Subject: [Slackbuilds-users] Can't get this build right : trello-cli
In-Reply-To: <2832a845-745f-deb5-a2f9-88181cb6b0@slackware.uk>
References: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
 <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>
 <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>
 <2832a845-745f-deb5-a2f9-88181cb6b0@slackware.uk>
Message-ID: <FAA95908-DF41-4F7D-97AA-7BC98209B013@free.fr>

Thank you for the alert, I didn't realize that.
Previous build hadn't this problem and will investigate that. 
Shall I cancel my submission or let admins do ? 

Regards 

Le 20 janvier 2024 19:55:45 GMT+01:00, "B. Watson" <urchlay at slackware.uk> a ?crit?:
>
>
>On Sat, 20 Jan 2024, Tonus wrote:
>
>> Thanks a lot for your answer. It solves the link issues.
>> 
>> I think I looked at the wrong template and am on the right way for stripping the binairies.
>
>I see one serious problem with your build: It requires network access
>when it runs. npm downloads stuff from the 'net. See if you can come
>up a way to do a purely local build... maybe just pre-download the
>files npm wants to download, add them to your DOWNLOAD in the .info
>file, have the script copy them to where npm would put them? I'm not a
>npm expert so I don't know if this would be feasible...
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
>

From urchlay at slackware.uk  Sat Jan 20 19:30:40 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 20 Jan 2024 14:30:40 -0500 (EST)
Subject: [Slackbuilds-users] Can't get this build right : trello-cli
In-Reply-To: <FAA95908-DF41-4F7D-97AA-7BC98209B013@free.fr>
References: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
 <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>
 <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>
 <2832a845-745f-deb5-a2f9-88181cb6b0@slackware.uk>
 <FAA95908-DF41-4F7D-97AA-7BC98209B013@free.fr>
Message-ID: <7ff642a7-28ea-ec9d-4aca-52ecc3db4c4@slackware.uk>



On Sat, 20 Jan 2024, Tonus wrote:

> Thank you for the alert, I didn't realize that.
> Previous build hadn't this problem and will investigate that. 
> Shall I cancel my submission or let admins do ?

Go ahead and cancel it.

From tonus1 at free.fr  Sat Jan 20 22:08:56 2024
From: tonus1 at free.fr (Tonus)
Date: Sat, 20 Jan 2024 23:08:56 +0100
Subject: [Slackbuilds-users] Trying to build offline trello-cli with npm
In-Reply-To: <7ff642a7-28ea-ec9d-4aca-52ecc3db4c4@slackware.uk>
References: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
 <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>
 <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>
 <2832a845-745f-deb5-a2f9-88181cb6b0@slackware.uk>
 <FAA95908-DF41-4F7D-97AA-7BC98209B013@free.fr>
 <7ff642a7-28ea-ec9d-4aca-52ecc3db4c4@slackware.uk>
Message-ID: <riqqd62e7crmmcx2fwsp4fh23afclyotcckuh42cdpdrjwe2rj@mdtephqypteq>

On Sat, Jan 20, 2024 at 02:30:40PM -0500, B. Watson wrote:
>Go ahead and cancel it.

So I cancelled my previous attempt. Will think about a way to shut down 
the network on my VM snapshot.

I am working on an offline build that is like :
- generate a package-lock.json from the trello-cli package.json
- extract the download urls for the dependencies to populate the .info 
- add a deps.txt file to work with the command `npm cache add dep.tgz`
- add in the SlackBuild a for loop
   `for dep in $(cat deps.txt); do npm cache add $dep; done`
- add the --offline flag to `npm install` in the SlackBuild

My problem to get further :
The integrity checks are against sha512 for the deps.

Is there a way to get the verification passed directly ?
Or shall I download, check against sha512 and create a md5sum 
fingerprint ?

Any advice on the path I'm following is welcome.

-- 
Regards,

Tonus

From geminijim at gmail.com  Sat Jan 20 22:17:57 2024
From: geminijim at gmail.com (Jim Brewster)
Date: Sat, 20 Jan 2024 17:17:57 -0500
Subject: [Slackbuilds-users] edk2-ovmf
Message-ID: <CAKmRSCKJAuyLYLjsVvbUzNzkmUDkacPXQsnvEoVwWCBpANmX+A@mail.gmail.com>

Hi all,

I got a 404 trying to fetch the source for this package (it's actually a
Fedora binary), and when I did some snooping, I couldn't find that exact
version or one I could trivially substitute. The Slackbuild is looking for
both an x86_64 binary and one for ia32, and that's where I'm hitting a
brick wall.

If someone is maintaining the package, I don't want to reinvent the wheel;
otherwise I could dig deeper. Maybe it's just a temporary issue with
accessing the source?

Thanks for your help,
Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240120/e875a2e5/attachment.htm>

From urchlay at slackware.uk  Sat Jan 20 22:19:46 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 20 Jan 2024 17:19:46 -0500 (EST)
Subject: [Slackbuilds-users] Trying to build offline trello-cli with npm
In-Reply-To: <riqqd62e7crmmcx2fwsp4fh23afclyotcckuh42cdpdrjwe2rj@mdtephqypteq>
References: <uf22rlextzuf34ztqnxgrll4c2py2kaxmowhcj3q336i4th5c7@ewvn7lbunp4b>
 <2996fc1c-1d42-b799-4142-1bd37684253@slackware.uk>
 <pbjhpn4gjhbgi7i2b5bkgdjjzjhbugvohlhg5hbmydqkr4w3rf@bvpess57gwxo>
 <2832a845-745f-deb5-a2f9-88181cb6b0@slackware.uk>
 <FAA95908-DF41-4F7D-97AA-7BC98209B013@free.fr>
 <7ff642a7-28ea-ec9d-4aca-52ecc3db4c4@slackware.uk>
 <riqqd62e7crmmcx2fwsp4fh23afclyotcckuh42cdpdrjwe2rj@mdtephqypteq>
Message-ID: <95317255-e8f1-4b2b-9973-1585105f5063@slackware.uk>



On Sat, 20 Jan 2024, Tonus wrote:

> Or shall I download, check against sha512 and create a md5sum fingerprint ?

Since .info files only support md5sums, yes, you'll have to list the
md5sums there.

From geminijim at gmail.com  Sat Jan 20 23:05:48 2024
From: geminijim at gmail.com (Jim Brewster)
Date: Sat, 20 Jan 2024 18:05:48 -0500
Subject: [Slackbuilds-users] edk2-ovmf
In-Reply-To: <CAKmRSCKJAuyLYLjsVvbUzNzkmUDkacPXQsnvEoVwWCBpANmX+A@mail.gmail.com>
References: <CAKmRSCKJAuyLYLjsVvbUzNzkmUDkacPXQsnvEoVwWCBpANmX+A@mail.gmail.com>
Message-ID: <CAKmRSCJ4KkJrV-Ec7QYsVBbA5YroZc8vd4h700Gi6W=m1TzRAg@mail.gmail.com>

UPDATE: I went straight to the URL
https://kojipkgs.fedoraproject.org/packages/edk2/20231122/14.fc39/noarch/
and downloaded the following to my edk2-ovmf Slackbuilds folder:

edk2-ovmf-20231122-14.fc39.noarch.rpm
<https://kojipkgs.fedoraproject.org/packages/edk2/20231122/14.fc39/noarch/edk2-ovmf-20231122-14.fc39.noarch.rpm>

edk2-ovmf-ia32-20231122-14.fc39.noarch.rpm
<https://kojipkgs.fedoraproject.org/packages/edk2/20231122/14.fc39/noarch/edk2-ovmf-ia32-20231122-14.fc39.noarch.rpm>

I edited the line in the Slackbuild:

< FEDVER=${FEDVER:-22-11.fc39}
---
> FEDVER=${FEDVER:-22-14.fc39}

And it built fine. Still need to test...


On Sat, Jan 20, 2024 at 5:17?PM Jim Brewster <geminijim at gmail.com> wrote:

> Hi all,
>
> I got a 404 trying to fetch the source for this package (it's actually a
> Fedora binary), and when I did some snooping, I couldn't find that exact
> version or one I could trivially substitute. The Slackbuild is looking for
> both an x86_64 binary and one for ia32, and that's where I'm hitting a
> brick wall.
>
> If someone is maintaining the package, I don't want to reinvent the wheel;
> otherwise I could dig deeper. Maybe it's just a temporary issue with
> accessing the source?
>
> Thanks for your help,
> Jim
>


-- 
Jim Brewster
geminijim at gmail.com
http://www.jimbrewster.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240120/c96db8b6/attachment-0001.htm>

From urchlay at slackware.uk  Sat Jan 20 23:05:27 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 20 Jan 2024 18:05:27 -0500 (EST)
Subject: [Slackbuilds-users] edk2-ovmf
In-Reply-To: <CAKmRSCKJAuyLYLjsVvbUzNzkmUDkacPXQsnvEoVwWCBpANmX+A@mail.gmail.com>
References: <CAKmRSCKJAuyLYLjsVvbUzNzkmUDkacPXQsnvEoVwWCBpANmX+A@mail.gmail.com>
Message-ID: <9d4cd6c7-84c3-a48-59d5-7aaebe6bf9e9@slackware.uk>



On Sat, 20 Jan 2024, Jim Brewster wrote:

> Hi all,
> I got a 404 trying to fetch the source for this package (it's actually a Fedora binary), and when I did some snooping, I couldn't find that exact
> version or one I could trivially substitute. The Slackbuild is looking for both an x86_64 binary and one for ia32, and that's where I'm hitting a
> brick wall.?

Archived copies here:

https://slackware.uk/sbosrcarch/by-name/system/edk2-ovmf/

The fact that sbosrcarch has the files means the URLs were good at one
time... maybe Fedora rearranged things on their site?

> If someone is maintaining the package, I don't want to reinvent?the wheel; otherwise I could dig deeper. Maybe it's just a temporary issue with
> accessing the source?

Looks like the maintainer is active:

commit df72ea1966c19c9b25f7b67574c7abe7180f1800
Author: Gene Carlson <kvngncrlsn at gmail.com>
Date:   Thu Jan 4 09:13:02 2024 +0900

     system/edk2-ovmf: Updated for version 202311.

     Signed-off-by: Willy Sudiarto Raharjo <willysr at slackbuilds.org>

From willysr at slackbuilds.org  Sun Jan 21 01:28:33 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 21 Jan 2024 08:28:33 +0700
Subject: [Slackbuilds-users] Updates - 20240120.1
In-Reply-To: <2126dd66-fddb-404d-9270-37376ff2137d@giand.it>
References: <e89f269d-387d-4afc-92f6-832dc13d5c77@slackbuilds.org>
 <2126dd66-fddb-404d-9270-37376ff2137d@giand.it>
Message-ID: <c2d44062-e356-4ee8-a4a3-7283b4bd42ed@slackbuilds.org>

> 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>

From kvngncrlsn at gmail.com  Sun Jan 21 01:56:58 2024
From: kvngncrlsn at gmail.com (K. Eugene Carlson)
Date: Sun, 21 Jan 2024 10:56:58 +0900
Subject: [Slackbuilds-users] edk2-ovmf
In-Reply-To: <9d4cd6c7-84c3-a48-59d5-7aaebe6bf9e9@slackware.uk>
References: <CAKmRSCKJAuyLYLjsVvbUzNzkmUDkacPXQsnvEoVwWCBpANmX+A@mail.gmail.com>
 <9d4cd6c7-84c3-a48-59d5-7aaebe6bf9e9@slackware.uk>
Message-ID: <CAHjLZv1qbHUZi8Hn+_4wBJtR405NhpCt5RNhLMrgOjtZV3SYVQ@mail.gmail.com>

Thanks for the heads-up, Jim!

> The fact that sbosrcarch has the files means the URLs were good at one
> time... maybe Fedora rearranged things on their site?

It looks like they had a rebuild and the subversion in edk2-ovmf.info was
removed from kojipkgs. If I can't find a cumulative archive (which would be
ideal), I'll bump to the new subversion and keep a closer eye on the
situation going forward. Either way, a fix will be in for this coming week.

Best regards,

Gene Carlson

On Sun, Jan 21, 2024 at 8:05?AM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Sat, 20 Jan 2024, Jim Brewster wrote:
>
> > Hi all,
> > I got a 404 trying to fetch the source for this package (it's actually a
> Fedora binary), and when I did some snooping, I couldn't find that exact
> > version or one I could trivially substitute. The Slackbuild is looking
> for both an x86_64 binary and one for ia32, and that's where I'm hitting a
> > brick wall.
>
> Archived copies here:
>
> https://slackware.uk/sbosrcarch/by-name/system/edk2-ovmf/
>
> The fact that sbosrcarch has the files means the URLs were good at one
> time... maybe Fedora rearranged things on their site?
>
> > If someone is maintaining the package, I don't want to reinvent the
> wheel; otherwise I could dig deeper. Maybe it's just a temporary issue with
> > accessing the source?
>
> Looks like the maintainer is active:
>
> commit df72ea1966c19c9b25f7b67574c7abe7180f1800
> Author: Gene Carlson <kvngncrlsn at gmail.com>
> Date:   Thu Jan 4 09:13:02 2024 +0900
>
>      system/edk2-ovmf: Updated for version 202311.
>
>      Signed-off-by: Willy Sudiarto Raharjo <willysr at slackbuilds.org
> >_______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240121/5afec1f5/attachment.htm>

From slack at giand.it  Sun Jan 21 11:04:48 2024
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=)
Date: Sun, 21 Jan 2024 12:04:48 +0100
Subject: [Slackbuilds-users] Updates - 20240120.1
In-Reply-To: <c2d44062-e356-4ee8-a4a3-7283b4bd42ed@slackbuilds.org>
References: <e89f269d-387d-4afc-92f6-832dc13d5c77@slackbuilds.org>
 <2126dd66-fddb-404d-9270-37376ff2137d@giand.it>
 <c2d44062-e356-4ee8-a4a3-7283b4bd42ed@slackbuilds.org>
Message-ID: <ea88d6a3-6345-4f98-8aa5-693ae29b8377@giand.it>


Il 21/01/24 02:28, Willy Sudiarto Raharjo ha scritto:
>> 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.
>
Good

thanks

-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it
https://github.com/giandex

Slackware Linux... because it works!
*********************************************************


From dickson.tim at googlemail.com  Sun Jan 21 23:01:31 2024
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Sun, 21 Jan 2024 23:01:31 +0000
Subject: [Slackbuilds-users] kicad md5sum mismatch
Message-ID: <1cda9f15-601b-4bb2-8da3-a0448d0a4f90@googlemail.com>

I'm getting 126e593e5990a1a3bb7768bfb2317da8 for the kicad-7.0.9 source, not
what is in the info file.

The kicad seems to build ok.
anyone else got the same problem?
regards, Tim


From jerry at woodmanstudio.co.uk  Mon Jan 22 10:57:28 2024
From: jerry at woodmanstudio.co.uk (Jerry Barker)
Date: Mon, 22 Jan 2024 10:57:28 +0000
Subject: [Slackbuilds-users] kicad md5sum mismatch
In-Reply-To: <1cda9f15-601b-4bb2-8da3-a0448d0a4f90@googlemail.com>
References: <1cda9f15-601b-4bb2-8da3-a0448d0a4f90@googlemail.com>
Message-ID: <dd1ef591-09c8-401d-9fd5-44c5fe63e4b4@woodmanstudio.co.uk>

Yep, same here. The program built fine though.

Cheers Jerry

On 1/21/24 23:01, Tim Dickson via SlackBuilds-users wrote:
> I'm getting 126e593e5990a1a3bb7768bfb2317da8 for the kicad-7.0.9 
> source, not
> what is in the info file.
>
> The kicad seems to build ok.
> anyone else got the same problem?
> regards, Tim
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From willysr at slackbuilds.org  Wed Jan 24 02:54:53 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 24 Jan 2024 09:54:53 +0700
Subject: [Slackbuilds-users] kicad md5sum mismatch
In-Reply-To: <1cda9f15-601b-4bb2-8da3-a0448d0a4f90@googlemail.com>
References: <1cda9f15-601b-4bb2-8da3-a0448d0a4f90@googlemail.com>
Message-ID: <63052644-d969-49e3-ab9a-7985070a739d@slackbuilds.org>

> I'm getting 126e593e5990a1a3bb7768bfb2317da8 for the kicad-7.0.9 source, 
> not
> what is in the info file.
> 
> The kicad seems to build ok.
> anyone else got the same problem?

it's now fixed on my branch

thanks

-- 
Willy Sudiarto Raharjo


From fernando.lopezjr at gmail.com  Sat Jan 27 05:30:46 2024
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 26 Jan 2024 23:30:46 -0600
Subject: [Slackbuilds-users] potrace download error.
Message-ID: <CALrQ46DdW7f9eLAhR5Q-6oqJh8s2pmOzGtRW2Yg8EueDNo7Lhg@mail.gmail.com>

Processing potrace

potrace:
potrace not found in /var/cache/sbopkg.
URL transformed to HTTPS due to an HSTS policy
--2024-01-26 23:29:31--
https://potrace.sourceforge.net/download/1.16/potrace-1.16.tar.gz
Resolving potrace.sourceforge.net (potrace.sourceforge.net)... failed:
Temporary failure in name resolution.
wget: unable to resolve host address ?potrace.sourceforge.net?

potrace:
Would you like to continue processing the rest of the
queue or would you like to abort?  If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

(Y)es to continue, (N)o to abort, (R)etry the build?:

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240126/b4786592/attachment.htm>

From fernando.lopezjr at gmail.com  Sat Jan 27 05:33:12 2024
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 26 Jan 2024 23:33:12 -0600
Subject: [Slackbuilds-users] potrace download error.
In-Reply-To: <CALrQ46DdW7f9eLAhR5Q-6oqJh8s2pmOzGtRW2Yg8EueDNo7Lhg@mail.gmail.com>
References: <CALrQ46DdW7f9eLAhR5Q-6oqJh8s2pmOzGtRW2Yg8EueDNo7Lhg@mail.gmail.com>
Message-ID: <CALrQ46BMWfu+GRUS-HwUrYB_gzsR4=ggaF5t0hUhyU2q5-GhGQ@mail.gmail.com>

nevermind it is my internet connection.

On Fri, Jan 26, 2024 at 11:30?PM Fernando Lopez <fernando.lopezjr at gmail.com>
wrote:

> Processing potrace
>
> potrace:
> potrace not found in /var/cache/sbopkg.
> URL transformed to HTTPS due to an HSTS policy
> --2024-01-26 23:29:31--
> https://potrace.sourceforge.net/download/1.16/potrace-1.16.tar.gz
> Resolving potrace.sourceforge.net (potrace.sourceforge.net)... failed:
> Temporary failure in name resolution.
> wget: unable to resolve host address ?potrace.sourceforge.net?
>
> potrace:
> Would you like to continue processing the rest of the
> queue or would you like to abort?  If this failed
> package is a dependency of another package in the queue
> then it may not make sense to continue.
>
> (Y)es to continue, (N)o to abort, (R)etry the build?:
>
> --
>
> ------------
> Regards,
>     Fernando Lopez Jr.
>


-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240126/443dee1f/attachment.htm>

From urchlay at slackware.uk  Sat Jan 27 06:12:56 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 27 Jan 2024 01:12:56 -0500 (EST)
Subject: [Slackbuilds-users] potrace download error.
In-Reply-To: <CALrQ46DdW7f9eLAhR5Q-6oqJh8s2pmOzGtRW2Yg8EueDNo7Lhg@mail.gmail.com>
References: <CALrQ46DdW7f9eLAhR5Q-6oqJh8s2pmOzGtRW2Yg8EueDNo7Lhg@mail.gmail.com>
Message-ID: <a7807b7-f33-98ce-2f10-3ba73e3d8347@slackware.uk>



On Fri, 26 Jan 2024, Fernando Lopez wrote:

> Resolving potrace.sourceforge.net (potrace.sourceforge.net)... failed: Temporary failure in name resolution.

Did you try again, a bit later? "Temporary"...

Anyway, it works here. Either a network hiccup in sourceforge's CDN,
or your ISP, or whatever.

From willysr at slackbuilds.org  Sat Jan 27 08:48:24 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 27 Jan 2024 15:48:24 +0700
Subject: [Slackbuilds-users] Updates - 20240127.1
Message-ID: <bd418ee0-338b-4102-ab29-7b184d92ccdf@slackbuilds.org>

Sat Jan 27 08:38:29 UTC 2024
academic/AstroImageJ: Update to 5.3.2.00
academic/bowtie2: Upgrade to version 2.5.3
academic/cadabra2: Updated for version 2.4.5.4.
academic/ngspice: Updated for version 42.
academic/wcalc: Use correct sourceforge link.
audio/plug: Updated for version 1.4.5.
audio/yabridge: Fix set buildtype
desktop/BlockstreamGreen: Updated for version 1.2.9.
desktop/dwmblocks: Update for 20231219.
development/SmallBASIC: Added (SmallBASIC).
development/abseil-cpp: Update for 20230802.1
development/android-tools: updated for version 34.0.4
development/arduino-cli: Updated for version 0.35.1
development/aws-cdk: Updated for version 2.123.0.
development/kicad: Update MD5SUM.
development/obsidian: Added (Markdown Editor).
development/reuse-tool: Update reuse-tool.SlackBuild
development/tofuenv: Updated for version 1.0.4.
development/xxd-standalone: Updated for version 9.1.0052.
development/zulu-openjdk21: Updated for version 21.0.2.
games/lbreakouthd: Updated for version 1.1.6.
games/vcmi: updated for version 1.4.4
gis/osm2pgsql: Updated for version 1.10.0.
gis/python3-xarray: Updated for version 2024.01.1.
gis/qgis: Updated for version 3.34.3.
gis/saga-gis: Updated for version 9.3.1.
graphics/tesseract: Updated for version 5.3.4.
graphics/ttfautohint: Update ttfautohint.SlackBuild
graphics/vimiv-qt: Update vimiv-qt.SlackBuild
graphics/vuescan: Updated for version 9.8.26.
libraries/allegro: updated for version 5.2.9.1
libraries/grpc: Update for 1.48.4 (+new maintainer)
libraries/libdraco: Updated for version 1.5.7.
libraries/libjcat: Updated for version 0.2.1.
libraries/libwpe: Updated for version 1.14.2.
libraries/libxmlb: Updated for version 0.3.15.
libraries/python3-gbinder: Added (Python bindings for libgbinder).
libraries/secp256k1: Updated for version 0.4.1.
libraries/tree-sitter: Updated for version 0.20.9.
misc/dos2unix: Updated for version 7.5.2.
multimedia/makemkv: Updated for version 1.17.6.
multimedia/svt-av1: Update svt-av1.SlackBuild
multimedia/uavs3d: Update uavs3d.SlackBuild
multimedia/uavs3e: Update uavs3e.SlackBuild
multimedia/videomass: Updated for version 5.0.4.
multimedia/winff: Add hardening flags.
network/Electrum: Updated for version 4.5.2.
network/GlobalProtect-openconnect: Added (VPN Service).
network/dog: Added (DNS Lookup).
network/dropbox: Updated for version 191.4.4995.
network/librewolf: Updated for version 121.0
network/nyxt: Updated for version 3.11.1.
network/opera: Updated for version 106.0.4998.66.
network/postfix-pgsql: Updated for version 3.6.14
network/rspamd: Updated for version 3.8.0
network/signal-desktop: Updated for version 6.45.1.
network/slack: Updated for version 4.35.138.
network/squid: Updated for version 6.6.
network/sslscan: Updated for version 2.1.3.
network/teamviewer: Updated for version 15.50.5.
network/telegram: Updated for version 4.14.9.
network/tor-browser: Update README.
network/tor-browser: Updated for version 13.0.9.
network/vivaldi: Updated for version 6.5.3206.57.
network/vnstat: Updated for version 2.12.
network/whalebird: Update for 6.0.0
network/zeek: Updated for version 6.0.3.
network/zoom-linux: Updated for version 5.17.5.2543
office/focuswriter-qt6: updated for version 1.8.6
office/ledger-live: Updated for version 2.73.1
office/navi: Update to 2.23.0 with correct url
office/semantik: Update semantik.SlackBuild
python/BeautifulSoup4: Updated for version 4.12.3.
python/buildbot-badges: updated for version 3.11.0
python/buildbot-worker: updated for version 3.11.0
python/buildbot: updated for version 3.11.0
python/python3-aiostream: updated for version 0.5.2
python/python3-arrow: Update for 1.3.0
python/python3-authheaders: updated for version 0.16.2
python/python3-bcrypt: updated for version 4.1.2
python/python3-dnspython: updated for version 2.5.0
python/python3-fontmake: Update python3-fontmake.SlackBuild
python/python3-fonttools: Update python3-fonttools.SlackBuild
python/python3-glyphslib: Update python3-glyphslib.SlackBuild
python/python3-grpcio: Update for 1.48.4
python/python3-hupper: updated for version 1.12.1
python/python3-jaconv: Update python3-jaconv.SlackBuild
python/python3-klepto: Update python3-klepto.SlackBuild
python/python3-langcodes: Update python3-langcodes.SlackBuild
python/python3-language-data: Update python3-language-data.SlackBuild
python/python3-marisa-trie: Update python3-marisa-trie.SlackBuild
python/python3-outcome: Added (python module).
python/python3-overrides: Update for 7.6.0
python/python3-pipx: Update python3-pipx.SlackBuild
python/python3-pox: Update python3-pox.SlackBuild
python/python3-pykakasi: Update python3-pykakasi.SlackBuild
python/python3-seaborn: Update for 0.13.2
python/python3-setuptools-git-ls-files: Update flag.
python/python3-ufo2ft: Update python3-ufo2ft.SlackBuild
python/python3-uharfbuzz: Update python3-uharfbuzz.SlackBuild
python/python3-userpath: Update python3-userpath.SlackBuild
ruby/ruby-build: Updated for version 20240119.
system/86box: Added (x86box emulator).
system/B-em: Updated for version 388e1d8.
system/Iosevka-aile: Updated for version 28.0.6.
system/Iosevka-etoile: Updated for version 28.0.6.
system/Iosevka-slab: Updated for version 28.0.6.
system/Iosevka: Updated for version 28.0.6.
system/OpenSnitch: Added (GNU/Linux interactive application firewall).
system/alacritty: Updated for version 0.13.1.
system/colord: Updated for version 1.4.7.
system/edk2-ovmf: Replace unavailable binaries.
system/fonts-gujarati-extra: Added (system fonts).
system/fonts-gurmukhi-extra: Added (system fonts).
system/fsviewer: Updated for version 0.2.6+20220428_38b38a6.
system/fwupd: Updated for version 1.9.12.
system/fzf: Updated for version 0.46.0.
system/gslapt: Update gslapt.SlackBuild
system/jenkins: Updated for version 2.426.3.
system/kitty: Updated for version 0.32.0
system/nvidia-driver: Updated for version 535.154.05.
system/nvidia-kernel: Updated for version 535.154.05.
system/nvidia-open-kernel: Updated for version 535.154.05.
system/rar2fs: Updated for version 1.29.6.
system/sarasa-gothic: Updated for version 1.0.4.
system/slackrepo-hints: Updated for version 20240127.
system/slackrepo: Updated for version 20240126.
system/slackroll: Updated for version v53.
system/slapt-get: Update slapt-get.SlackBuild
system/slapt-src: Update slapt-src.SlackBuild
system/slapt-update-service: Update slapt-update-service.SlackBuild
system/smokeping: Added (Network Monitoring).
system/thermald: Updated for version 2.5.6.
system/unrar: Updated for version 6.2.12.
system/worker: Updated for version 5.0.1.
system/zramen: Update README.
+--------------------------+


-- 
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/20240127/5dd7a79d/attachment-0001.asc>

From rasp at spitzner.org  Sat Jan 27 16:22:45 2024
From: rasp at spitzner.org (Ralph Spitzner)
Date: Sat, 27 Jan 2024 17:22:45 +0100
Subject: [Slackbuilds-users] ngspice42
Message-ID: <a80ff5a2-8b2f-87d0-686b-7a2cbc165b82@spitzner.org>

gives me this:
make[2]: Leaving directory '/tmp/SBo/ngspice-42/release'
make[1]: Leaving directory '/tmp/SBo/ngspice-42/release'
chmod: cannot access 
'ngspice-42/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib': 
No such file or directory



     -rasp

-- 
Chaos ist die h?chste form der Ordnung.....


From s.arcus at open-t.co.uk  Sat Jan 27 17:37:30 2024
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Sat, 27 Jan 2024 17:37:30 +0000
Subject: [Slackbuilds-users] Is it possible to test build packages using
 chroot?
Message-ID: <cae2302b-3a28-94fd-c71c-282b7e7a99fd@open-t.co.uk>

As per title, is it possible to use chroot to test build packages 
against a different version of Slackware? For example if I have 
slackware -current on my machine, instead of setting up a full virtual 
machine, could I have a Slackware 15.0 install in a directory, and just 
chroot to it to test build a package? I confess I only have a general 
understanding of how chroot works - so there might be a reason why this 
can't work.

From sombragris at sombragris.org  Sat Jan 27 17:38:32 2024
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Sat, 27 Jan 2024 14:38:32 -0300
Subject: [Slackbuilds-users] Iosevka 28.0.6 not found
Message-ID: <j8idF.9756c0f973.20240127143832.3cb43c8a@tiki.sombragris.org>

Good afternoon,

Slackware-current user here but I think this issue is global so I
report here.

Iosevka-28.0.6 source cannot be downloaded. With sbopkg it gives a Not
Found error. Other packages from the Iosevka family download and build
just fine.

Best regards,

Eduardo

-- 
Eduardo S?nchez Gauto, Abog., Th.M.
Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol
Oficina: https://goo.gl/maps/mccgBNM7Zw32
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow - 
Tel?fono: (0991) 755-355 - Asunci?n, Paraguay 
==================================================================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240127/ccb13551/attachment.asc>

From didier at slint.fr  Sat Jan 27 17:58:50 2024
From: didier at slint.fr (Didier Spaier)
Date: Sat, 27 Jan 2024 18:58:50 +0100
Subject: [Slackbuilds-users] isodate is a python package
Message-ID: <a6d95c72-27a2-43a6-8a2a-8c5f63f2cce6@slint.fr>

...So I assume that following the current naming rules @ SBo it should be split
in two or (as it has zero dependee @ SBo) just remove one line and name it
python3-isodate.

Before someone asks how I came across this: it is dependency of python-rdflib,
itself a dependency of zeitgest that I will build to add a feature to mate-tweak
(converting the PKGBUILDs from Arch to SLKBUILDs, sorry I do not have the time
needed to maintain SlackBuilds any more).

Cheers,
Didier

From matteo.bernardini at gmail.com  Sat Jan 27 18:32:49 2024
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 27 Jan 2024 19:32:49 +0100
Subject: [Slackbuilds-users] ngspice42
In-Reply-To: <a80ff5a2-8b2f-87d0-686b-7a2cbc165b82@spitzner.org>
References: <a80ff5a2-8b2f-87d0-686b-7a2cbc165b82@spitzner.org>
Message-ID: <CAPsDuS6Wx3Mf+pFOPnz7+49sk1-n8K_28nPS4DQV0WSSV3BjSw@mail.gmail.com>

Hi Ralph,

thanks for the report! actually there is an error in the SlackBuild but I
fixed it in out git, it will go in the repository next week

--- a/academic/ngspice/ngspice.SlackBuild
+++ b/academic/ngspice/ngspice.SlackBuild
@@ -134,7 +134,7 @@ ln -s "libngspice.so.0.0.9"
"$PKG/usr/lib${LIBDIRSUFFIX}/libngspice.so"
 install -Dm644 ./src/include/ngspice/sharedspice.h
$PKG/usr/include/ngspice/sharedspice.h
 # Move the configure output file.
 mv $TMP/$PRGNAM-$VERSION/release/src/include/ngspice/config.h
$PKG/usr/include/ngspice/
-chmod 644
$PRGNAM-$VERSION/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib
+chmod 644 $PKG/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib

 install -Dm644 $CWD/$PRGNAM.png
$PKG/usr/share/icons/hicolor/48x48/apps/$PRGNAM.png

if you edit it locally and change manually that line it should work.

Matteo

Il giorno sab 27 gen 2024 alle ore 17:23 Ralph Spitzner via
SlackBuilds-users <slackbuilds-users at slackbuilds.org> ha scritto:

> gives me this:
> make[2]: Leaving directory '/tmp/SBo/ngspice-42/release'
> make[1]: Leaving directory '/tmp/SBo/ngspice-42/release'
> chmod: cannot access
> 'ngspice-42/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib':
> No such file or directory
>
>
>
>      -rasp
>
> --
> Chaos ist die h?chste form der Ordnung.....
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240127/6e0ac2a1/attachment.htm>

From lramos.prof at yahoo.com.br  Sat Jan 27 18:52:28 2024
From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos)
Date: Sat, 27 Jan 2024 15:52:28 -0300
Subject: [Slackbuilds-users] ngspice42
In-Reply-To: <a80ff5a2-8b2f-87d0-686b-7a2cbc165b82@spitzner.org>
References: <a80ff5a2-8b2f-87d0-686b-7a2cbc165b82@spitzner.org>
Message-ID: <ZbVQ7EAiv/2zNAGO@giustizia.lan>

Hello all,

me too.

Seems to be a little thing, almost a typo: substituting $PRGNAM-$VERSION
for $PKG in line 137 of ngspice.SlackBuild does the trick.

Hope it helps,

Luiz Carlos Ramos
lramos.prof at yahoo.com.br
Sao Paulo - Brazil

On Sat, Jan 27, 2024 at 05:22:45PM +0100, Ralph Spitzner via SlackBuilds-users wrote:
> gives me this:
> make[2]: Leaving directory '/tmp/SBo/ngspice-42/release'
> make[1]: Leaving directory '/tmp/SBo/ngspice-42/release'
> chmod: cannot access
> 'ngspice-42/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib': No
> such file or directory
> 
> 
> 
>     -rasp
> 
> -- 
> Chaos ist die h?chste form der Ordnung.....
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From andrzej at telszewski.com  Sat Jan 27 18:55:21 2024
From: andrzej at telszewski.com (Andrzej Telszewski)
Date: Sat, 27 Jan 2024 19:55:21 +0100
Subject: [Slackbuilds-users] Is it possible to test build packages using
 chroot?
In-Reply-To: <cae2302b-3a28-94fd-c71c-282b7e7a99fd@open-t.co.uk>
References: <cae2302b-3a28-94fd-c71c-282b7e7a99fd@open-t.co.uk>
Message-ID: <3c2e99ab-058b-4528-847a-233907621183@telszewski.com>

On 27/01/2024 18:37, Sebastian Arcus wrote:
> As per title, is it possible to use chroot to test build packages 
> against a different version of Slackware? For example if I have 
> slackware -current on my machine, instead of setting up a full virtual 
> machine, could I have a Slackware 15.0 install in a directory, and 
> just chroot to it to test build a package? I confess I only have a 
> general understanding of how chroot works - so there might be a reason 
> why this can't work.

Sure it is! :-)

You might want to give `slackrepo` a chance.
It has capability to build in chroot, exactly what you want.


From damagedone at gmx.com  Sat Jan 27 21:50:36 2024
From: damagedone at gmx.com (Eugene M.)
Date: Sat, 27 Jan 2024 22:50:36 +0100
Subject: [Slackbuilds-users] Iosevka 28.0.6 not found
In-Reply-To: <j8idF.9756c0f973.20240127143832.3cb43c8a@tiki.sombragris.org>
References: <j8idF.9756c0f973.20240127143832.3cb43c8a@tiki.sombragris.org>
Message-ID: <c339a655-31a1-4e3e-9bf9-f4f62aa5204a@gmx.com>

Hi, It seems that I made a mistake and haven't checked the URL properly.

Could someone update the link on server? I'm planing to send a new PR
this weekend.


On 1/27/24 18:38, Eduardo Sanchez wrote:
> Good afternoon,
>
> Slackware-current user here but I think this issue is global so I
> report here.
>
> Iosevka-28.0.6 source cannot be downloaded. With sbopkg it gives a Not
> Found error. Other packages from the Iosevka family download and build
> just fine.
>
> Best regards,
>
> Eduardo
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From s.arcus at open-t.co.uk  Sat Jan 27 22:02:28 2024
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Sat, 27 Jan 2024 22:02:28 +0000
Subject: [Slackbuilds-users] Is it possible to test build packages using
 chroot?
In-Reply-To: <3c2e99ab-058b-4528-847a-233907621183@telszewski.com>
References: <cae2302b-3a28-94fd-c71c-282b7e7a99fd@open-t.co.uk>
 <3c2e99ab-058b-4528-847a-233907621183@telszewski.com>
Message-ID: <a4f21548-07dd-ed88-b056-5f841e408876@open-t.co.uk>



On 27/01/2024 18:55, Andrzej Telszewski wrote:
> On 27/01/2024 18:37, Sebastian Arcus wrote:
>> As per title, is it possible to use chroot to test build packages 
>> against a different version of Slackware? For example if I have 
>> slackware -current on my machine, instead of setting up a full virtual 
>> machine, could I have a Slackware 15.0 install in a directory, and 
>> just chroot to it to test build a package? I confess I only have a 
>> general understanding of how chroot works - so there might be a reason 
>> why this can't work.
> 
> Sure it is! :-)
> 
> You might want to give `slackrepo` a chance.
> It has capability to build in chroot, exactly what you want.

Thank you for that - I didn't know about slackrepo - I'll take a look

From rogerkrowiak+slackbuilds at gmail.com  Sun Jan 28 20:38:32 2024
From: rogerkrowiak+slackbuilds at gmail.com (Roger Krowiak)
Date: Sun, 28 Jan 2024 21:38:32 +0100
Subject: [Slackbuilds-users] letsencrypt not working on slackware15
Message-ID: <CAGpsf_H80cEOeb-fTHA-_pQnTXBtBhHgLz3L0UYAG6_1TgdxXA@mail.gmail.com>

Hello guys,

I've found a problem with the let's encrypt package. I've full installation
of Slackware 15 and I've installed the letsencrypt package using sboui.

But when I try to use it, it complains about "Problem in Augeas
installation". Both augeas and python3-augeas are installed.

Here is report from "/var/log/letsencrypt/letsencrypt.log":

2024-01-28 21:34:58,018:DEBUG:certbot._internal.main:certbot version: 2.8.0
2024-01-28 21:34:58,019:DEBUG:certbot._internal.main:Location of certbot
entry point: /usr/bin/certbot
2024-01-28 21:34:58,019:DEBUG:certbot._internal.main:Arguments: []
2024-01-28 21:34:58,020:DEBUG:certbot._internal.main:Discovered plugins:
PluginsRegistry(PluginEntryPoint#apache,PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2024-01-28 21:34:58,057:DEBUG:certbot._internal.log:Root logging level set
at 30
2024-01-28 21:34:58,058:DEBUG:certbot._internal.plugins.selection:Requested
authenticator None and installer None
2024-01-28 21:34:58,169:DEBUG:certbot_apache._internal.configurator:Apache
version is 2.4.58
2024-01-28 21:34:58,170:DEBUG:certbot._internal.plugins.disco:No
installation (PluginEntryPoint#apache): Problem in Augeas installation
Traceback (most recent call last):
  File
"/usr/lib64/python3.9/site-packages/certbot/_internal/plugins/disco.py",
line 112, in prepare
    self._initialized.prepare()
  File
"/usr/lib64/python3.9/site-packages/certbot_apache/_internal/configurator.py",
line 376, in prepare
    self.parser = self.get_parser()
  File
"/usr/lib64/python3.9/site-packages/certbot_apache/_internal/configurator.py",
line 482, in get_parser
    return parser.ApacheParser(
  File
"/usr/lib64/python3.9/site-packages/certbot_apache/_internal/parser.py",
line 60, in __init__
    self.aug: Augeas = init_augeas()
  File
"/usr/lib64/python3.9/site-packages/certbot_apache/_internal/parser.py",
line 956, in init_augeas
    raise errors.NoInstallationError("Problem in Augeas installation")
certbot.errors.NoInstallationError: Problem in Augeas installation
2024-01-28 21:34:58,173:DEBUG:certbot._internal.plugins.selection:No
candidate plugin


*Best regards,*


*Roger Krowiak*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240128/2cb43e2c/attachment.htm>

From riza.dindir at gmail.com  Wed Jan 17 10:41:39 2024
From: riza.dindir at gmail.com (Riza Dindir)
Date: Wed, 17 Jan 2024 13:41:39 +0300
Subject: [Slackbuilds-users] Gradle version upgrade
Message-ID: <CA+ek4BHo4mQ6JdzMeWp4Lfr1wPOm2bc_am3Z34wQ2insuKc4gw@mail.gmail.com>

Hello All.

Is it possible to upgrade the version of gradle in slackbuilds.org. The
current version of the gradle package on slackbuild is 5.5.1 . The latest
version of gradle is 8.5.

I contacted the maintainer of the slackbuild package and did not get any
answers (I received a response stating that the mail address is not
existing).

Regards
Riza Dindir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240117/cea73bd7/attachment-0001.htm>

From viel.losero at gmail.com  Sun Jan 28 17:57:53 2024
From: viel.losero at gmail.com (viel.losero at gmail.com)
Date: Sun, 28 Jan 2024 18:57:53 +0100
Subject: [Slackbuilds-users] Missed CHECKSUMS.md5.asc ??
Message-ID: <71d2001b-d7ed-4c11-96e4-e95303357cd5@gmail.com>

Hi,

Seems that CHECKSUMS.md5 is not signed.

########## From mi last rsync and gpg check :)

system/unrar/unrar.info
 ??????????? 280 100%??? 0.76kB/s??? 0:00:00 (xfr#573, to-chk=713/76325)
system/worker/
system/worker/worker.SlackBuild
 ????????? 3,521 100%??? 5.64kB/s??? 0:00:00 (xfr#574, to-chk=370/76325)
system/worker/worker.info
 ??????????? 308 100%??? 0.49kB/s??? 0:00:00 (xfr#575, to-chk=369/76325)
system/zramen/
system/zramen/README
 ??????????? 319 100%??? 0.44kB/s??? 0:00:00 (xfr#576, to-chk=23/76325)
system/zramen/zramen.SlackBuild
 ????????? 2,235 100%??? 3.01kB/s??? 0:00:00 (xfr#577, to-chk=20/76325)

sent 79,944 bytes? received 5,241,076 bytes? 99,458.32 bytes/sec
total size is 127,929,191? speedup is 24.04
gpg: Signature made Sat 20 Jan 2024 04:00:33 AM CET using DSA key ID 
9C7BA3B6
gpg: BAD signature from "SlackBuilds.org Development Team 
<slackbuilds-devel at slackbuilds.org>"


Thanks for your awesome work.


From viel.losero at gmail.com  Sun Jan 28 18:00:03 2024
From: viel.losero at gmail.com (viel.losero at gmail.com)
Date: Sun, 28 Jan 2024 19:00:03 +0100
Subject: [Slackbuilds-users] Fwd: Missed CHECKSUMS.md5.asc ??
In-Reply-To: <71d2001b-d7ed-4c11-96e4-e95303357cd5@gmail.com>
References: <71d2001b-d7ed-4c11-96e4-e95303357cd5@gmail.com>
Message-ID: <ac62466e-7d07-4f79-923d-2d62cabffaef@gmail.com>

U make awesome work maintaining slackbuilds.

I appreciate it to much.

Happy to help you.



-------- Forwarded Message --------
From: 	- Sun <>, 58 GMT <>
X-Mozilla-Status: 	0001
X-Mozilla-Status2: 	00800000
Message-ID: 	<71d2001b-d7ed-4c11-96e4-e95303357cd5 at gmail.com>
Date: 	Sun, 28 Jan 2024 18:57:53 +0100
MIME-Version: 	1.0
User-Agent: 	Mozilla Thunderbird
Content-Language: 	en-US
To: 	slackbuilds-users at slackbuilds.org
From: 	viel.losero at gmail.com <viel.losero at gmail.com>
Subject: 	Missed CHECKSUMS.md5.asc ??
Content-Type: 	text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 	8bit



Hi,

Seems that CHECKSUMS.md5 is not signed.

########## From mi last rsync and gpg check :)

system/unrar/unrar.info
 ??????????? 280 100%??? 0.76kB/s??? 0:00:00 (xfr#573, to-chk=713/76325)
system/worker/
system/worker/worker.SlackBuild
 ????????? 3,521 100%??? 5.64kB/s??? 0:00:00 (xfr#574, to-chk=370/76325)
system/worker/worker.info
 ??????????? 308 100%??? 0.49kB/s??? 0:00:00 (xfr#575, to-chk=369/76325)
system/zramen/
system/zramen/README
 ??????????? 319 100%??? 0.44kB/s??? 0:00:00 (xfr#576, to-chk=23/76325)
system/zramen/zramen.SlackBuild
 ????????? 2,235 100%??? 3.01kB/s??? 0:00:00 (xfr#577, to-chk=20/76325)

sent 79,944 bytes? received 5,241,076 bytes? 99,458.32 bytes/sec
total size is 127,929,191? speedup is 24.04
gpg: Signature made Sat 20 Jan 2024 04:00:33 AM CET using DSA key ID 
9C7BA3B6
gpg: BAD signature from "SlackBuilds.org Development Team 
<slackbuilds-devel at slackbuilds.org>"


Thanks for your awesome work.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240128/4f3fe01b/attachment.htm>

From lramos.prof at yahoo.com.br  Sun Jan 28 22:55:23 2024
From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos)
Date: Sun, 28 Jan 2024 19:55:23 -0300
Subject: [Slackbuilds-users] Podofo and Cppunit
References: <ZbbbO9RsQyoU0792.ref@giustizia.lan>
Message-ID: <ZbbbO9RsQyoU0792@giustizia.lan>

Hello,

just reporting some errors I got when compiling podofo and a workaround
that helped me here.

The problem happens with the build of podofo. After some time compiling,
it shows a lot of errors that suggest there's something wrong related to
Cppunit.

In my system, cppunit is installed (cppunit-1.15.1-x86_64-1_SBo).

After some thinking, I tried to uninstall cppunit before building
podofo, to see what happens. And it worked.

Next, I managed to do a trick in CMakeFiles.txt in order to allow doing
all the magic as if Cppunit was not installed. Then I got to this patch,
which is supposed to be applied to CMakeFiles.txt before building:

=== 01-dont-run-unit-test.patch =======================================
diff -urpN a/CMakeLists.txt b/CMakeLists.txt
--- a/CMakeLists.txt	2024-01-27 20:22:44.720125177 -0300
+++ b/CMakeLists.txt	2024-01-27 20:27:51.120130890 -0300
@@ -382,6 +382,11 @@ ELSE(UNISTRING_FOUND)
 ENDIF(UNISTRING_FOUND)
 
 
+IF(PODOFO_BYPASS_UNIT_TESTS)
+  MESSAGE("Unit tests bypassed by user request")
+
+ELSE(PODOFO_BYPASS_UNIT_TESTS)
+
 IF(NOT PODOFO_BUILD_LIB_ONLY)
 
 FIND_PACKAGE(CppUnit)
@@ -396,6 +401,8 @@ ENDIF(CppUnit_FOUND)
 
 ENDIF(NOT PODOFO_BUILD_LIB_ONLY)
 
+ENDIF(PODOFO_BYPASS_UNIT_TESTS)
+
 FIND_PACKAGE(OpenSSL)
 
 FIND_PACKAGE(FREETYPE REQUIRED)
=== 01-dont-run-unit-test.patch =======================================

The intention is to bypass CppUnit detection when the key
PODOFO_BYPASS_UNIT_TESTS is set to TRUE by user request. When this
happens, a message is printed, allowing the user to know what is
happening, and CppUnit detection is bypassed, as if it was not present.

After that, I managed to change the SlackBuild, including that key in
the "cmake" invocation, like that:

    (...)
    -DWANT_BOOST:BOOL=1 \
    -DLIB_SUFFIX:STRING="$LIBDIRSUFFIX" \
    -DPODOFO_BYPASS_UNIT_TESTS:BOOL=TRUE \
    -DCMAKE_BUILD_TYPE=Release ..
    (...)

and it ultimately this worked (with some degree of surprise by myself).

So, this may save some time to people who are in the same context as I.
I think the first thing to check is if the Cppunit interference happens
as here (and if there is no other way to make it work).

Hope this helps,

Luiz Carlos Ramos
lramos.prof at yahoo.com.br
Sao Paulo - Brazil


From willysr at slackbuilds.org  Mon Jan 29 02:42:00 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 29 Jan 2024 09:42:00 +0700
Subject: [Slackbuilds-users] Missed CHECKSUMS.md5.asc ??
In-Reply-To: <71d2001b-d7ed-4c11-96e4-e95303357cd5@gmail.com>
References: <71d2001b-d7ed-4c11-96e4-e95303357cd5@gmail.com>
Message-ID: <23895b86-3d17-4b53-81aa-2e680cf2543e@slackbuilds.org>

> Seems that CHECKSUMS.md5 is not signed.

> gpg: BAD signature from "SlackBuilds.org Development Team 
> <slackbuilds-devel at slackbuilds.org>"

Sorry, forgot to sign it
now it should be fixed

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240129/fad66089/attachment-0001.bin>
-------------- 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/20240129/fad66089/attachment-0001.asc>

From urchlay at slackware.uk  Mon Jan 29 08:07:15 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 29 Jan 2024 03:07:15 -0500 (EST)
Subject: [Slackbuilds-users] ngspice42
In-Reply-To: <a80ff5a2-8b2f-87d0-686b-7a2cbc165b82@spitzner.org>
References: <a80ff5a2-8b2f-87d0-686b-7a2cbc165b82@spitzner.org>
Message-ID: <3ff07fec-f0e0-c062-bf8f-ba5d539ad3b8@slackware.uk>



On Sat, 27 Jan 2024, Ralph Spitzner via SlackBuilds-users wrote:

> gives me this:
> make[2]: Leaving directory '/tmp/SBo/ngspice-42/release'
> make[1]: Leaving directory '/tmp/SBo/ngspice-42/release'
> chmod: cannot access 
> 'ngspice-42/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib': 
> No such file or directory

Confirmed, I get the same thing here, and an IRC user says he does too.
Looks broken.

From ltlnx at disroot.org  Tue Jan 30 08:36:43 2024
From: ltlnx at disroot.org (Wen-Wei Kao)
Date: Tue, 30 Jan 2024 16:36:43 +0800
Subject: [Slackbuilds-users] libime and librime category placement
Message-ID: <2141724.9o76ZdvQCi@localhost.localdomain>

Hello,

Currently libime (dependency of fcitx5-chinese-addons) is placed in category 
"Misc", so I uploaded librime (dependency of fcitx5-rime) to "Misc" too. 
However should they be moved to the "Libraries" category? Will there be any 
consequences of moving? Thanks in advance.

Cheers,
ltlnx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240130/10d3ad68/attachment.asc>

From fernando.lopezjr at gmail.com  Tue Jan 30 08:58:14 2024
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Tue, 30 Jan 2024 01:58:14 -0700
Subject: [Slackbuilds-users] libime and librime category placement
In-Reply-To: <2141724.9o76ZdvQCi@localhost.localdomain>
References: <2141724.9o76ZdvQCi@localhost.localdomain>
Message-ID: <CALrQ46CCAnZhme-v-dta8jKtfqNa5Q2CjT+MeoeoosOWuXOe-A@mail.gmail.com>

They are libraries. should be moved to the library category.

On Tue, Jan 30, 2024 at 1:36?AM Wen-Wei Kao via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> Hello,
>
> Currently libime (dependency of fcitx5-chinese-addons) is placed in
> category
> "Misc", so I uploaded librime (dependency of fcitx5-rime) to "Misc" too.
> However should they be moved to the "Libraries" category? Will there be
> any
> consequences of moving? Thanks in advance.
>
> Cheers,
> ltlnx_______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240130/85e4da8a/attachment.htm>

From ltlnx at disroot.org  Tue Jan 30 09:02:17 2024
From: ltlnx at disroot.org (Wen-Wei Kao)
Date: Tue, 30 Jan 2024 17:02:17 +0800
Subject: [Slackbuilds-users] libime and librime category placement
In-Reply-To: <CALrQ46CCAnZhme-v-dta8jKtfqNa5Q2CjT+MeoeoosOWuXOe-A@mail.gmail.com>
References: <2141724.9o76ZdvQCi@localhost.localdomain>
 <CALrQ46CCAnZhme-v-dta8jKtfqNa5Q2CjT+MeoeoosOWuXOe-A@mail.gmail.com>
Message-ID: <2688290.lGaqSPkdTl@localhost.localdomain>

Hi, 

Got it. Can anyone move libime to libraries? I'll reupload librime.

-- ltlnx

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240130/0b6a20b7/attachment.asc>

From alik at ejik.org  Wed Jan 31 19:45:41 2024
From: alik at ejik.org (Alexander Verbovetsky)
Date: Wed, 31 Jan 2024 22:45:41 +0300
Subject: [Slackbuilds-users] dnsproxy uid/gid
Message-ID: <ZbqjZWG/PJ+XCV7u@mail.ejik.org>

Hello,

I'm writing a dnsproxy SlackBuild, which needs a dnsproxy user. Can I
use 383 for it?

Best regards,
Alexander