Re: [Slackbuilds-users] Call for Help

[fourtysixandtwo]

On Sun, Apr 28, 2024 at 2:25 PM KB_SBo  wrote:
> Using python3-meson-opt works here. Although unshare said "file not
> found", no matter, I just turned off networking for the VM.  This also
> means device-tree-compiler is another hard dependency to provide libftd
> otherwise a bunch of emulators don't get built.

Sorry, copied that from another window where I had it wrong.  But I
always test my own slackbuilds with "unshare -n" after it was pointed
out to me as an issuea bit easier than disabling networking on the
vm.

BRIDGE_HELPER_SETUID=yes SLIRP=yes unshare -n sh ./qemu.SlackBuild

Ahh, I was building this on my main install(for max speed) and already
had device-tree-compiler installed.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Call for Help

[fourtysixandtwo]

Can build offline with the python3-meson-opt added as a dep and
PYTHONPATH added to the slackbuild.

Doing a build test(about 1/3 done) right now with "unshare -n
BRIDGE_HELPER_SETUID=yes SLIRP=yes sh ./qemu.SlackBuild"

diff --git a/system/qemu/qemu.SlackBuild b/system/qemu/qemu.SlackBuild
index 73604dc9e3..59ec768c5e 100644
--- a/system/qemu/qemu.SlackBuild
+++ b/system/qemu/qemu.SlackBuild
@@ -93,6 +93,9 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} + || true

+PYVER=$(python3 -c 'import sys; print("%d.%d" % sys.version_info[:2])')
+export PYTHONPATH=/opt/python$PYVER/site-packages
+
 # Remove double CFLAGS
 sed -i "s|^\ \ CFLAGS=\"-O2\ |  CFLAGS=\"|" configure

diff --git a/system/qemu/qemu.info b/system/qemu/qemu.info
index 7e9f20f028..db06361012 100644
--- a/system/qemu/qemu.info
+++ b/system/qemu/qemu.info
@@ -5,6 +5,6 @@ DOWNLOAD="https://download.qemu.org/qemu-8.2.2.tar.xz;
 MD5SUM="e43091262671c1728b09522932b75b1d"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES=""
+REQUIRES="python3-meson-opt"
 MAINTAINER="Edward W. Koenig"
 EMAIL="kingbeow...@linuxgalaxy.org"

On Sat, Apr 27, 2024 at 8:05 PM Willy Sudiarto Raharjo
 wrote:
>
> > and was told qemu will use it's "internal" meson.  Guess what?  There is
> > no "internal" meson.  Any build system requirements qemu needs it will
> > download.
>
> internal means it's maintained by qemu team :)
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] sbotools config issues

[fourtysixandtwo]

An instance where seeing the full error message would be helpful.

On Sun, Mar 10, 2024 at 7:30 PM K. Eugene Carlson  wrote:
>
> Hi,
>
> SBo packages that have been added to -current are removed from Ponce's repo 
> to avoid file conflicts, which is why sbotools didn't find python3-wheel and 
> python3-build.
>
> When the "unable to locate" message comes up (and it often does for Python 
> stuff), I just select "y" to ignore and continue. That should work provided 
> that the corresponding Slackware packages have been installed.
>
> Gene
>
> On Mon, Mar 11, 2024 at 9:51 AM J. Milgram  wrote:
>>
>>
>> Thanks, and thanks Didier too.
>>
>> ( I misunderstood ... item #15 at https://slackbuilds.org/faq/ says:
>> "Slackware -current is not supported, but as a general rule, the scripts
>> should work on it as well." so I didn't think to look for a -current repo. )
>>
>> So I did:
>>
>> sboconfig -r https://github.com/Ponce/slackbuilds.git
>> sboconfig -l # to confirm sbo was in fact pointed at that URL
>> sbocheck
>>
>> It ran, didn't seem to download anything new. But no improvement, still got 
>> "Unable to locate..."
>>
>> Then just to be sure, started from scratch:
>>
>> rm -rf /usr/sbo
>> sbosnap fetch
>> sboinstall python3-matplotlib
>>
>> ... but same problem. FWIW sbotools is 2.7.
>>
>> So tried it with sbopkg, selected the -current git repo and it seems to have 
>> worked. Good enough for me, though I would still like to know what went 
>> wrong with sbotools.
>>
>> Is sbopkg more actively maintained than sbotools?
>>
>> thx
>> Judah
>>
>> On 3/10/24 19:07, fourtysixandtwo wrote:
>> > Both work fine pointed at ponce's repo for -current.
>> >
>> > sbotools by default does point to ponce's repo, but maybe try pointing
>> > at it explicitly.
>> >
>> > sboconfig -r https://github.com/Ponce/slackbuilds.git
>> > sbocheck
>> >
>> > Cheers
>> >
>> > On Sun, Mar 10, 2024 at 4:35 PM J. Milgram  wrote:
>> >>
>> >> ... or maybe I just need to switch to sbopkg?
>> >>
>> >>
>> >> On 3/10/24 18:21, J. Milgram wrote:
>> >>> Hello.
>> >>>
>> >>> Once again having problems installing with sbotools. There's evidently
>> >>> some config subtlety I'm not grasping, hopefully someone can set me
>> >>> straight.
>> >>>
>> >>> I have a fresh -current install and am using the default 15.0 repo.
>> >>> Many slackbuilds installed fine, but then:
>> >>>
>> >>> /usr/sbin/sboinstall XXX fails with:
>> >>>
>> >>> "Unable to locate XXX in the SlackBuilds.org tree."
>> >>>
>> >>> Where XXX is in [ python3-build, python3-wheel ] ... and maybe others.
>> >>> May be just python3 packages that fail but haven't investigated. I do
>> >>> see these slackbuilds in the slackbuilds repo so they're not mirages.
>> >>>
>> >>> Some config stuff:
>> >>>
>> >>>>> cat /etc/slackware-version
>> >>> Slackware 15.0+
>> >>>
>> >>>>> cat /etc/sbotools/sbotools.conf
>> >>> JOBS=5
>> >>> DISTCLEAN=TRUE
>> >>>
>> >>>>> /usr/sbin/sboconfig -l
>> >>> sboconfig -d|--distclean:
>> >>>  DISTCLEAN=TRUE
>> >>> sboconfig -j|--jobs:
>> >>>  JOBS=5
>> >>> sboconfig -o|--local-overrides:
>> >>>  LOCAL_OVERRIDES=FALSE
>> >>> sboconfig -c|--noclean:
>> >>>  NOCLEAN=FALSE
>> >>> sboconfig -p|--pkg-dir:
>> >>>  PKG_DIR=FALSE
>> >>> sboconfig -r|--repo:
>> >>>  REPO=FALSE
>> >>> sboconfig -s|--sbo-home:
>> >>>  SBO_HOME=/usr/sbo
>> >>> sboconfig -V|--slackware-version:
>> >>>  SLACKWARE_VERSION=FALSE
>> >>>
>> >>> /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for
>> >>> python3-build or python3-wheel.
>> >>>
>> >>> /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and
>> >>> have also done sboclean -d.
>> >>>
>> >>> /usr/sbin/sbosnap and sboupdate both run seemingly without error, but
>> 

Re: [Slackbuilds-users] sbotools config issues

[fourtysixandtwo]

Both work fine pointed at ponce's repo for -current.

sbotools by default does point to ponce's repo, but maybe try pointing
at it explicitly.

sboconfig -r https://github.com/Ponce/slackbuilds.git
sbocheck

Cheers

On Sun, Mar 10, 2024 at 4:35 PM J. Milgram  wrote:
>
>
> ... or maybe I just need to switch to sbopkg?
>
>
> On 3/10/24 18:21, J. Milgram wrote:
> >
> > Hello.
> >
> > Once again having problems installing with sbotools. There's evidently
> > some config subtlety I'm not grasping, hopefully someone can set me
> > straight.
> >
> > I have a fresh -current install and am using the default 15.0 repo.
> > Many slackbuilds installed fine, but then:
> >
> > /usr/sbin/sboinstall XXX fails with:
> >
> > "Unable to locate XXX in the SlackBuilds.org tree."
> >
> > Where XXX is in [ python3-build, python3-wheel ] ... and maybe others.
> > May be just python3 packages that fail but haven't investigated. I do
> > see these slackbuilds in the slackbuilds repo so they're not mirages.
> >
> > Some config stuff:
> >
> > >> cat /etc/slackware-version
> > Slackware 15.0+
> >
> > >> cat /etc/sbotools/sbotools.conf
> > JOBS=5
> > DISTCLEAN=TRUE
> >
> > >> /usr/sbin/sboconfig -l
> > sboconfig -d|--distclean:
> > DISTCLEAN=TRUE
> > sboconfig -j|--jobs:
> > JOBS=5
> > sboconfig -o|--local-overrides:
> > LOCAL_OVERRIDES=FALSE
> > sboconfig -c|--noclean:
> > NOCLEAN=FALSE
> > sboconfig -p|--pkg-dir:
> > PKG_DIR=FALSE
> > sboconfig -r|--repo:
> > REPO=FALSE
> > sboconfig -s|--sbo-home:
> > SBO_HOME=/usr/sbo
> > sboconfig -V|--slackware-version:
> > SLACKWARE_VERSION=FALSE
> >
> > /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for
> > python3-build or python3-wheel.
> >
> > /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and
> > have also done sboclean -d.
> >
> > /usr/sbin/sbosnap and sboupdate both run seemingly without error, but
> > don't pick up the missing slackbuilds.
> >
> > I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas.
> > Grateful for any advice!
> >
> > Maybe I need to install these problem packages by hand ... if it must
> > be, so be it. But in the long term it would be nice to get everything
> > configured properly.
> >
> > thanks!
> >
> > Judah
> >
>
> --
> =
> milg...@cgpp.com
> 301-257-7069
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@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] SQLAlchemy 2.0.x upgrade

[fourtysixandtwo]

Hi all,

I've submitted a PR.  Here's the patch.
https://github.com/SlackBuildsOrg/slackbuilds/commit/d3cd6e0ecfeff64ecc315ca92a2e940eeccc9fa2.diff

Any further testing and questions or concerns would be appreciated.

Here's a list of the builds that have issues with the upgrade:

-  sickchill
  -have emailed maintainer to remove patch to make it work with SQLAlchemy 1.x
- buildbot
  -seems to run fine, but has warning
-buildbot 3.11.0 has requirement sqlalchemy<1.5,>=1.3.0, but you
have sqlalchemy 2.0.28.
  -have emailed maintainer for further testing

Slackbuilds suggested for removal:

- alembic (python2 only and previously broken)
  -replaced by python3-alembic.
  -maintainer is not active (3 years)
- Pyfa
  -unless someone would like to take it over and upgrade it
  -maintainer is not active (4 years)
- sqlalchemy-migrate
  -Kyle has given ok to remove as it is no longer a dep of pytrainer
  -no updates to project since 2019.
- gourmet (python2)
  -believe it is broken, SQLAlchemy's python2 support was removed
before I took it over
  -maintainer is not active (9 years)

Here is the remaining list of builds that have SQLAlchemy as a dep.
Basic testing shows no issues:

flexget
python3-cinemagoer
zope.sqlalchemy
python3-paginate_sqlalchemy
python3-obspy
slpkg
python3-Flask-SQLAlchemy
pytrainer
python3-alembic
python3-mailman
Kallithea
kallithea-frontend
buildbot-badges
pychess
python3-ipython-sql

Cheers
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Packages up for grabs

[fourtysixandtwo]

FYI newer meson is available with python3-meson-opt so that isn't a
limitation.  Just follow the instructions in the README.

There are a couple other *-opt builds available, see below, and I'm
currently prepping the latest setuptools and setuptools_scm(not quite
latest) versions:

# sbopkg -g python*-opt
Searching for python*-opt
Found the following matches for python*-opt:
NAMEVERSION
python/python3-meson-opt1.3.0
python/python3-setuptools-opt   65.1.1
python/python3-setuptools-rust-opt  1.8.1
python/python3-setuptools-scm-opt   7.1.0

Cheers

On Sat, Dec 23, 2023 at 8:24 AM Bob Funk  wrote:
>
> Hi Aditya,
>
> I looked into the newer geoclue2 versions (2.7.x releases), and they required 
> a newer meson version to build than the one provided with Slackware 15.0. 
> Newer versions of geoclue build fine in slackware-current of course, but with 
> stable I guess it will be best to stay with the version you have until the 
> next Slackware release.
>
> Since there's nothing to change here, you might as well retain maintainer 
> status. If at the next Slackware release you are still not using this and 
> want to get rid of it I can take it then to upgrade it.
>
> Regards,
>
> Bob
>
> On Fri, Dec 22, 2023 at 11:10 AM Aditya via SlackBuilds-users 
>  wrote:
>>
>> Hi Bob,
>>
>> Feel free to take over geoclue2 if you use it a lot and want the latest 
>> versions quickly :)
>> If being on an older version is not an issue, I can hold on to it.
>>
>> Thanks,
>> Aditya
>>
>> On 12/21/23 22:52, slackbuilds-users-requ...@slackbuilds.org wrote:
>>
>> Date: Thu, 21 Dec 2023 11:22:06 -0600
>> From: Bob Funk 
>> To: "SlackBuilds.org Users List" 
>> Subject: Re: [Slackbuilds-users] Packages up for grabs
>> Message-ID:
>> 
>> Content-Type: text/plain; charset="utf-8"
>>
>> I have a handful of SlackBuilds that depend on 'geoclue2'. If you are no
>> longer interested in maintaining it then I can take it over.
>>
>> The rest I don't use and would be better suited for other maintainers who
>> do.
>>
>> Regards,
>>
>> Bob
>>
>> On Thu, Dec 21, 2023 at 6:29?AM Aditya via SlackBuilds-users <
>> slackbuilds-users@slackbuilds.org> wrote:
>>
>> Hi everyone,
>>
>> Hope you are doing well.
>>
>> I've not been using these packages actively for some time now, so it would
>> be good if someone can pick them up and maintain them.
>>
>> Dividing them into 2 categories:
>>
>> A. *Optional*. It would be good if someone can take over for active
>> maintenance. Otherwise will maintain them when I can. These include:
>> * system/geoclue2
>> * system/TLP
>>
>> B. *Unused and Pending deletion*. Not using these, and if no one wants to
>> maintain them, will request the SBo admins to drop these packages moving
>> forwards. These include:
>> * desktop/faba-icon-theme
>> * desktop/moka-icon-theme
>> * system/openrc
>> * system/socklog
>> * network/xinetd
>>
>> Thanks for your time and help
>>
>> Warm regards,
>> Aditya
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@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@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@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] python3-django 4.2.8 missing dependency

[fourtysixandtwo]

Willy,

I just checked and it is asgiref that is missing the dep.

On Sun, Dec 10, 2023, 8:02 a.m. Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > 1. I tried to build django 4.2.8 and 5.0, builds fine but doesn't launch
> > as typing-extensions seems to be missing.
> > I'm getting ModuleNotFoundError: No module named 'typing_extensions',
> > when I try launch django
> > Guessing this is the same situation for current, missing
> typing-extensions.
>
> It's fixed on my branch
>
>
> > 2. Why the name change on slackbuild? I ended up unable to upgrade my
> > previous installation due to new name (not a big problem for me, but...)
>
> It was due to python 2/3 split
> We do this in most of the python scripts to help with python 2->3
> transition for next SBo repository
>
> I assume you didn't follow our -users list?
> please join the list so you know what happened in the project
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20231202.1

[fourtysixandtwo]

Luiz,

I wouldn't bother looking at meson, that message is from the "build"
module.  It must be finding another version of Cython somewhere.

Cheers

On Mon, Dec 4, 2023 at 5:27 PM Luiz Carlos Ramos via SlackBuilds-users
 wrote:
>
> Hi,
>
> the system was patched just some days ago...
>
>   root@giustizia:~# cython --version
>   Cython version 0.29.36
>
> First, thanks for the reply. As a matter of fact, I was just wondering
> if someone else had this problem. By what could be understood, it seems
> that it's something specific to this installation.
>
> I'll look at how meson evaluates the dependencies as far the time
> permits and try to find out what's happening.
>
> Many thanks,
> Luiz
>
>
> On Sun, Dec 03, 2023 at 04:34:37PM -0700, fourtysixandtwo wrote:
> > Luiz,
> >
> > When was the last time you patched your system?  Cython was upgraded
> > to 0.29.36 in September.
> >
> > Cheers
> >
> > On Sun, Dec 3, 2023 at 4:14 PM Luiz Carlos Ramos via SlackBuilds-users
> >  wrote:
> > >
> > > Hello,
> > >
> > > I got an error here with python3-numpy. It gives me this:
> > >
> > >   * Getting build dependencies for wheel...
> > >
> > >   ERROR Missing dependencies:
> > >   Cython<3.1,>=0.29.34
> > >
> > > Managing to remove the dependency on Cython from pyproject.toml made it
> > > to work again. Anyway I would not understand what the problem could be,
> > > as Cython is the Python engine used in the base install AFAIK.
> > > Eventually it could have something with Python2/3 search order.
> > >
> > > Would it happen with someone else?
> > >
> > > Thanks,
> > > Luiz Ramos
> > > São Paulo - Brazil
> > > lramos dot prof at yahoo dot com dot br
> > >
> > > On Sat, Dec 02, 2023 at 08:04:23AM +0700, Willy Sudiarto Raharjo wrote:
> > > > Sat Dec  2 00:55:28 UTC 2023
> > > > academic/copasi: Updated for version 4.42.284.
> > > > academic/cvc4: Update dependencies.
> > > > academic/fet: Updated for version 6.13.2.
> > > > academic/qhull: Updated for version 8.0.2.
> > > > academic/scmutils: Added (scm utils).
> > > > accessibility/mbrola-voices: Added (speech synth. data).
> > > > audio/audacity: Added the dependencies lilv and suil.
> > > > audio/audacity: Fix VERSION.
> > > > audio/qpwgraph: Updated for version 0.6.0
> > > > audio/spectmorph: Updated for version 0.6.1.
> > > > desktop/nwg-displays: Updated for version 0.3.9
> > > > desktop/nwg-drawer: Updated for version 0.4.3
> > > > desktop/nwg-shell-config: Updated for version 0.5.28
> > > > development/aspnetcore-runtime-7.0: Updated to version 7.0.14
> > > > development/aspnetcore-runtime-8.0: Added (ASP.NET Runtime 8.0).
> > > > development/dotnet-runtime-6.0: Updated to version 6.0.25
> > > > development/dotnet-runtime-7.0: Updated to version 7.0.14
> > > > development/dotnet-runtime-8.0: Added (.NET Runtime 8.0).
> > > > development/dotnet-sdk-6.0: Updated to version 6.0.417
> > > > development/dotnet-sdk-7.0: Updated to version 7.0.404
> > > > development/dotnet-sdk-8.0: Added (.NET SDK 8.0).
> > > > development/github-cli: Updated for version 2.39.2
> > > > development/github-desktop: Updated for version 3.3.5
> > > > development/haxe-bin: Updated for version 4.3.3.
> > > > development/hugo: Updated for version 0.120.4.
> > > > development/kForth-32: Updated for version 2.4.3.
> > > > development/kForth-64: Updated for version 0.4.3.
> > > > development/kforth: Updated for version 1.8.0.
> > > > development/mit-scheme: Updated for version 12.1.
> > > > development/mold: Updated for version 2.4.0.
> > > > development/openjdk8: Updated for version 8u392.
> > > > development/pahole: Updated for version 1.25.
> > > > development/python3-numpy-legacy: Added (Legacy Numpy).
> > > > development/python3-numpy: Updated for version 1.26.0
> > > > games/ace: New maintainer, icon/desktop.
> > > > games/ags: updated for version 3.6.0.54
> > > > games/bzflag: Updated for version 2.4.26.
> > > > games/mrboom: Updated for version 5.3.
> > > > games/warzone2100: updated for version 4.4.2
> > > > gis/librttopo: Added (RT Topology Library).
> > > > gis/librttopo: Support content-disposition DOWNLOAD.
> > > > gis/libspatialite: Ne

Re: [Slackbuilds-users] Updates - 20231202.1

[fourtysixandtwo]

Luiz,

When was the last time you patched your system?  Cython was upgraded
to 0.29.36 in September.

Cheers

On Sun, Dec 3, 2023 at 4:14 PM Luiz Carlos Ramos via SlackBuilds-users
 wrote:
>
> Hello,
>
> I got an error here with python3-numpy. It gives me this:
>
>   * Getting build dependencies for wheel...
>
>   ERROR Missing dependencies:
>   Cython<3.1,>=0.29.34
>
> Managing to remove the dependency on Cython from pyproject.toml made it
> to work again. Anyway I would not understand what the problem could be,
> as Cython is the Python engine used in the base install AFAIK.
> Eventually it could have something with Python2/3 search order.
>
> Would it happen with someone else?
>
> Thanks,
> Luiz Ramos
> São Paulo - Brazil
> lramos dot prof at yahoo dot com dot br
>
> On Sat, Dec 02, 2023 at 08:04:23AM +0700, Willy Sudiarto Raharjo wrote:
> > Sat Dec  2 00:55:28 UTC 2023
> > academic/copasi: Updated for version 4.42.284.
> > academic/cvc4: Update dependencies.
> > academic/fet: Updated for version 6.13.2.
> > academic/qhull: Updated for version 8.0.2.
> > academic/scmutils: Added (scm utils).
> > accessibility/mbrola-voices: Added (speech synth. data).
> > audio/audacity: Added the dependencies lilv and suil.
> > audio/audacity: Fix VERSION.
> > audio/qpwgraph: Updated for version 0.6.0
> > audio/spectmorph: Updated for version 0.6.1.
> > desktop/nwg-displays: Updated for version 0.3.9
> > desktop/nwg-drawer: Updated for version 0.4.3
> > desktop/nwg-shell-config: Updated for version 0.5.28
> > development/aspnetcore-runtime-7.0: Updated to version 7.0.14
> > development/aspnetcore-runtime-8.0: Added (ASP.NET Runtime 8.0).
> > development/dotnet-runtime-6.0: Updated to version 6.0.25
> > development/dotnet-runtime-7.0: Updated to version 7.0.14
> > development/dotnet-runtime-8.0: Added (.NET Runtime 8.0).
> > development/dotnet-sdk-6.0: Updated to version 6.0.417
> > development/dotnet-sdk-7.0: Updated to version 7.0.404
> > development/dotnet-sdk-8.0: Added (.NET SDK 8.0).
> > development/github-cli: Updated for version 2.39.2
> > development/github-desktop: Updated for version 3.3.5
> > development/haxe-bin: Updated for version 4.3.3.
> > development/hugo: Updated for version 0.120.4.
> > development/kForth-32: Updated for version 2.4.3.
> > development/kForth-64: Updated for version 0.4.3.
> > development/kforth: Updated for version 1.8.0.
> > development/mit-scheme: Updated for version 12.1.
> > development/mold: Updated for version 2.4.0.
> > development/openjdk8: Updated for version 8u392.
> > development/pahole: Updated for version 1.25.
> > development/python3-numpy-legacy: Added (Legacy Numpy).
> > development/python3-numpy: Updated for version 1.26.0
> > games/ace: New maintainer, icon/desktop.
> > games/ags: updated for version 3.6.0.54
> > games/bzflag: Updated for version 2.4.26.
> > games/mrboom: Updated for version 5.3.
> > games/warzone2100: updated for version 4.4.2
> > gis/librttopo: Added (RT Topology Library).
> > gis/librttopo: Support content-disposition DOWNLOAD.
> > gis/libspatialite: New maintainer. updated DEPS
> > gis/proj-data: Updated for version 1.16.
> > gis/proj: Updated for version 9.3.1.
> > gis/python3-xarray: Updated for version 2023.11.0.
> > graphics/GraphicsMagick: Update optional deps in README.
> > graphics/converseen: Updated for version 0.12.0.0.
> > graphics/nomacs: Updated for version 3.17.2287.
> > graphics/pd-gears: Added (parametrized gear generator).
> > graphics/photoqt: Updated for version 3.4.
> > ham/SoapyRTLSDR: Added (SoapySDR RTL-SDR Support Module).
> > ham/glrpt: Added (decode LRPT images).
> > ham/qlog: Updated for version 0.30.0.
> > libraries/QDarkStyle: Updated for version 3.2.3
> > libraries/aspnetcore-runtime-6.0: Updated to version 6.0.25
> > libraries/botocore: Updated for version 1.33.1.
> > libraries/field3d: Added (voxel data library).
> > libraries/libconfig: Updated for version 1.7.3, new maintainer.
> > libraries/libsixel: Updated for version 1.10.3.
> > libraries/log4cplus: Updated for version 2.1.0.
> > libraries/protobuf-c: Updated for version 1.5.0.
> > libraries/pykdtree: Removed (unmaintained).
> > libraries/qtermwidget: Updated for version 1.4.0.
> > libraries/skalibs: Updated for version 2.14.0.1
> > libraries/wimlib: Updated to version 1.14.3.
> > misc/fcitx5-chewing: Updated for version 5.1.1.
> > misc/fcitx5-chinese-addons: Updated for version 5.1.2.
> > misc/fcitx5-configtool: Updated for version 5.1.2.
> > misc/fcitx5-qt: Updated for version 5.1.3.
> > misc/libime: Updated for version 1.1.3.
> > multimedia/beets: fix deps.
> > network/awscli-v2: Updated for version 2.14.1.
> > network/awscli: Updated for version 1.31.1.
> > network/brave-browser: Updated for version 1.60.125.
> > network/etherpoke: Update script.
> > network/flexget: fix deps.
> > network/kea: Updated for version 2.5.3.
> > network/mailspring: Updated for version 1.13.1
> > network/malheur: Fix download URL.
> > network/nordvpn: Updated to 

Re: [Slackbuilds-users] Updates - 20231202.1

[fourtysixandtwo]

I would look at the following as a start and focus on why you are
getting the setuptools is too old message. :

# python3 -V
Python 3.9.18

# python3 -c "import setuptools; print(setuptools.__file__);
print(setuptools.__version__)"
/usr/lib64/python3.9/site-packages/setuptools/__init__.py
57.5.0

On Sun, Dec 3, 2023 at 9:29 AM fourtysixandtwo
 wrote:
>
> They all build fine here on my 15.0 vm.
>
> On Sun, Dec 3, 2023 at 9:22 AM mickski56  wrote:
> >
> > > Do you have a specific problem you are encountering that leads you to
> > > that question?
> > >
> >
> > Yes all of the named slackbuilds fail without adding the PYTHONPATH.
> > The failures all say setuptools is too old and are fixed by adding the
> > PYTHONPATH variable.
> >
> > Also sent to
> > SlackBuilds.org Users List
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20231202.1

[fourtysixandtwo]

They all build fine here on my 15.0 vm.

On Sun, Dec 3, 2023 at 9:22 AM mickski56  wrote:
>
> > Do you have a specific problem you are encountering that leads you to
> > that question?
> >
>
> Yes all of the named slackbuilds fail without adding the PYTHONPATH.
> The failures all say setuptools is too old and are fixed by adding the
> PYTHONPATH variable.
>
> Also sent to
> SlackBuilds.org Users List
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20231202.1

[fourtysixandtwo]

Do you have a specific problem you are encountering that leads you to
that question?

The quick answer without knowing more information:

Of those listed only python3-mesonpy requires the PYTHONPATH line and
has it to use the newer meson installed by python3-meson-opt.  Any
other slackbuilds that require python3-mesonpy, of which there are
currently three, also need that PYTHONPATH line.  Orany other
slackbuilds requiring a python3-*-opt slackbuild at build time need
that line.

Cheers

On Sun, Dec 3, 2023 at 7:33 AM mickski56  wrote:
>
> Have I missed something or are the following SlackBuilds now requiring
> "export PYTHONPATH=/opt/python3.9/site-packages/" adding to them ?
>
> python3-wcwidth-0.2.12
> python3-trove-classifiers-2023.11.22
> python3-pyproject-metadata-0.7.1
> python3-meson-opt-1.3.0
> python3-mesonpy-0.14.0
>
> Thanks
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20231014.1

[fourtysixandtwo]

On Mon, Oct 16, 2023 at 7:25 AM Erich Ritz via SlackBuilds-users
 wrote:
>
> I also use OpenBLAS as much as possible for all builds requiring BLAS/LAPACK:
>
> Erich

Forgot to mention it, but lapack should be removed as a dep from
python3-scipy too.

All this begs the question, would it be advisable to standardize on
OpenBLAS instead of blas/lapack?  Kyle mentions in the readme of the
latter "If you want good performance, then use the BLAS libraries
provided by your CPU vendor, or OpenBLAS or atlas provided by SlackBuilds.org."
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20231014.1

[fourtysixandtwo]

Me neither, I've just followed the information from the numpy slackbuild
and gone with OpenBLAS the majority of the time while testing my builds and
their dependees.

"It is highly recommended to install libraries implementing BLAS and
LAPACK before installing numpy. You may choose between:
   a) BLAS and LAPACK (reference but unoptimized and thus slow)
   b) OpenBLAS (optimized, provides LAPACK too)
   c) ATLAS and LAPACK (optimized), good to read README.ATLAS
All these are available on SlackBuilds.org."

On Sun, Oct 15, 2023 at 4:48 PM Jeremy Hansen 
wrote:

> On Sun, Oct 15, 2023, 9:38 AM fourtysixandtwo 
> wrote:
>
>> Tried it on my build vm and saw the same thing.   python3-mesonpy is also
>> missing as a dep.
>>
>> I was able to build scipy without openBLAS by adding cblas as a dep and
>> making the following change to the slackbuild.  (Everything needs to be
>> rebuilt without openBLAS):
>>
>> -python3 -m build --wheel --no-isolation
>> +python3 -m build --wheel --no-isolation -Csetup-args="-Dblas=blas"
>> -Csetup-args="-Dlapack=lapack"
>>
>
> Is there a benefit with cblas over openBLAS? I'm not familiar enough with
> either of them.
>
> Jeremy
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20231014.1

[fourtysixandtwo]

Tried it on my build vm and saw the same thing.   python3-mesonpy is also
missing as a dep.

I was able to build scipy without openBLAS by adding cblas as a dep and
making the following change to the slackbuild.  (Everything needs to be
rebuilt without openBLAS):

-python3 -m build --wheel --no-isolation
+python3 -m build --wheel --no-isolation -Csetup-args="-Dblas=blas"
-Csetup-args="-Dlapack=lapack"


On Sun, Oct 15, 2023 at 8:48 AM Greg Tourte  wrote:

> It appears that scipy now requires openBLAS but it is not listed in the
> required list.
>
> On Sat, 14 Oct 2023 at 11:06, Willy Sudiarto Raharjo <
> will...@slackbuilds.org> wrote:
>
>> Sat Oct 14 03:33:09 UTC 2023
>> academic/python3-scipy: Version bump to 1.11.3
>>
>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@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] Added python3-meson-opt

[fourtysixandtwo]

Hi all,

Thanks to a comment on LQ by brobr (not sure if you are on this list) I've
uploaded three new builds that will allow builds like numpy and pandas to
be upgraded to their latest versions and use the PEP517 build process.  In
both cases this significantly decreases the build time due to the meson
backend making use of all cores.

Here's all 5 slackbuilds and the build queue for python3-pandas.  Please
test.
https://slackware.uk/~fourtysixandtwo/src/python3-meson-opt-test.tar.gz

FYI Jeremy, when you get a chance to look at it let me know if you're ok
with the newer versions of meson and meson-python (mesonpy) than what
pandas 2.1.1 was pinned to.

Cheers.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] *.rej files creeping in to git commits

[fourtysixandtwo]

I've also fixed the problem (for a second time) at my end.  (I was hoping
no one would notice :)

On Mon, Oct 2, 2023 at 12:12 PM B. Watson  wrote:

>
>
> On Mon, 2 Oct 2023, Erich Ritz wrote:
>
> > 1) Add a check to sbolint (this is why I've included B. Watson in the
> email).
>
> Easily done.
>
> > Comments?  Good idea?  Bad idea?
>
> I can't see a reason why anything would ever need rejects from patch
> as part of its build process. Seems like a good idea to me.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Intent for python SlackBuilds with SLKCFLAGS and LIBDIRSUFFIX

[fourtysixandtwo]

> It would be easier when we do this thing during development cycle, not
> during normal cycle like today. We can write anything into the git
> during development cycle

It will be indeed...instead of just getting involved at the end of the
FTBFS stage.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Intent for python SlackBuilds with SLKCFLAGS and LIBDIRSUFFIX

[fourtysixandtwo]

I stick to the template as much as possible and think it's best just to
leave them there.  They are just NOTE's and can be ignored as such, or at
least I do.  It's more work to add or remove them and I like the
consistency.

I diff my builds against the template as another check (one without the
extra comments) and it's much easier to note what should change or be
unique to each build.

And like you mentioned, mass edits are much easier which I found out doing
the i486 -> i586 changes.

That's my $0.02


On Wed, Sep 20, 2023 at 5:48 PM Jeremy Hansen 
wrote:

> Since sbolint (from system/sbo-maintainer-tools) is being ran on github PR
> requests and newer versions of sbolint are catching when SLKCFLAGS and
> LIBDIRSUFFIX are not being used, are we expected to not include them on the
> SlackBuilds? If so, should we remove the entire if/then block for the ARCH
> detection since that's typically all it does?
>
> I ask because the templates for python SlackBuilds still include the ARCH
> detection block and I don't want to remove it from my SlackBuilds if the
> admins are expecting them to be there to simplify mass edits in the future.
>
> I imagine this also applies to other SlackBuilds, but have only noticed it
> so far with python ones. I expect there is a desire for consistency when
> possible, so I'd love some clarification!
>
> Thanks for everyone's work!
> Jeremy (aka bassmadrigal)
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@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] Brent Earl's slackbuilds

[fourtysixandtwo]

Hi all,

As per Brent's attached email, if anyone would like to take over any of his
slackbuilds, here's the list.

I'm claiming fio and passlib so have removed them from the list.

audio/pianobar
desktop/numix-blue-theme
desktop/numix-folders
desktop/numix-gtk-theme
desktop/numix-ocean-theme
desktop/numix-pack
desktop/numix-sx-theme
desktop/xfce4-wavelan-plugin
development/textadept
games/nsudoku
libraries/Impacket
libraries/libnids
libraries/libwhisker2
libraries/python-ntlm
network/amap
network/corkscrew
network/driftnet
network/dsniff
network/hostapd
network/hping3
network/nikto
network/packit
network/polipo
network/sqlmap
network/ufw
office/impressive
office/pdf2djvu
office/xpad
perl/perl-File-Slurp-Tiny
perl/perl-tree-dagnode
perl/perl-www-mechanize
python/darts.util.lru
python/halberd
python/hpack
python/phply
python/pybloomfiltermmap
python/pyperclip
python/python-pcapy
python/python2-clamd
python/python2-esmre
python/python2-pdfminer
python/python2-tblib
python/python2-vulndb
python/stopit
system/autojump


-- Forwarded message -
From: Brent Earl 
Date: Sun, Sep 17, 2023 at 4:59 PM
Subject: Re: passlib slackbuild
To: fourtysixandtwo 


Hello,

That would be fine if you want to maintain it.  If there are any other
scripts you would like to take over ownership, that is fine too.  I've
neglected my scripts for quite a while now due to other work.  Feel free to
forward this to the maintainers mailing list.

Regards,
Brent Earl
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Edit suggested of intel-microcode.SlackBuild

[fourtysixandtwo]

I second Didier's suggestion.

Here's  a snippet from the grub docs, the default images it looks for are
at the bottom:

'GRUB_EARLY_INITRD_LINUX_CUSTOM'
'GRUB_EARLY_INITRD_LINUX_STOCK'
 List of space-separated early initrd images to be loaded from
 '/boot'.  This is for loading things like CPU microcode, firmware,
 ACPI tables, crypto keys, and so on.  These early images will be
 loaded in the order declared, and all will be loaded before the
 actual functional initrd image.

 'GRUB_EARLY_INITRD_LINUX_STOCK' is for your distribution to declare
 images that are provided by the distribution.  It should not be
 modified without understanding the consequences.  They will be
 loaded first.

 'GRUB_EARLY_INITRD_LINUX_CUSTOM' is for your custom created images.

 The default stock images are as follows, though they may be
 overridden by your distribution:
  intel-uc.img intel-ucode.img amd-uc.img amd-ucode.img
early_ucode.cpio microcode.cpio

Cheers

On Wed, Sep 6, 2023 at 5:08 AM Andrzej Telszewski 
wrote:

> On 06/09/2023 12:37, Didier Spaier wrote:
> > Hi Andrzej (in BCC) and all.,
> >
> > I suggest to replae this line:
> > iucode_tool -v --write-earlyfw=$PKG/boot/intel-ucode.cpio \
> > by
> > iucode_tool -v --write-earlyfw=$PKG/boot/intel-ucode.img \
> >
> >
> > so that grub users running update-grub have this early initrd
> automatically
> > included in /grub.cfg, in a line like this one:
> >
> > initrd/@/boot/intel-ucode.img /@/boot/initramfs-6.1.46.img
> >
> >
> > Cheers,
> > Didier
> >
> >
>
> Hi Didier,
>
> looking for _intel-ucode.img_ on my system, I don't find anything
> interesting.
>
> So, if it's not already _pre-configured_ in some of the _grub_ files,
> you could simple put
> _intel-ucode.cpio_ instead of _intel-ucode.img_.
>
> Or it wouldn't work, because grub does not like _*.cpio_?
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Building xournalpp v1.2.0

[fourtysixandtwo]

Hi Cristiano,

It did fail if lua was also installed.  Adding the following works though.

+# set lua version to use otherwise it will use an older version \
+# if more than one installed
+sed -i 's/^find_package(Lua/find_package(Lua 5.3/' CMakeLists.txt
+
mkdir -p build
cd build

Cheers

On Sun, Jul 30, 2023 at 5:41 AM Cristiano Urban 
wrote:

> Great! I didn't notice lua52 and lua53 packages!
>
> Just tested with lua53 and it works fine. I will submit the slackbuild
> ASAP.
>
> Thank you very much!
>
> All the best,
> Cristiano.
>
> Il 30 lug 2023 13:01, J via SlackBuilds-users <
> slackbuilds-users@slackbuilds.org> ha scritto:
>
> Hi Christiano,
>
> Requiring lua 5.3 shouldn’t be a problem as sbo contains a package (lua53)
> that can co-exist with a regular lua install. I keep an install of lua53 on
> my systems without any noticeable problems with other packages and it may
> even satisfy deps for the lua packages you have the regular lua installed
> for.
>
> Give it a shot with xournalpp!
>
> — Jay
>
>
> On Jul 30, 2023 at 6:05 AM, >
> wrote:
>
> Hi,
> it seems that the new version of xournalpp doesn't build because it
> requires lua v5.3.
>
> Since lua is required by other packages on SBo, I'm aware that upgrading
> lua could break some of these packages. If this is the case, I can get
> stuck at the current version (1.1.3) for now.
>
> Thank you!
>
> Cheers,
> Cristiano.
> ___ SlackBuilds-users mailing
> list SlackBuilds-users@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@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Building xournalpp v1.2.0

[fourtysixandtwo]

If you update the REQs to use the lua53 slackbuild instead, xournalpp
v1.2.0 builds fine here.

Cheers

On Sun, Jul 30, 2023 at 4:05 AM Cristiano Urban 
wrote:

> Hi,
> it seems that the new version of xournalpp doesn't build because it
> requires lua v5.3.
>
> Since lua is required by other packages on SBo, I'm aware that upgrading
> lua could break some of these packages. If this is the case, I can get
> stuck at the current version (1.1.3) for now.
>
> Thank you!
>
> Cheers,
> Cristiano.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Solaar gui fails to run

[fourtysixandtwo]

Doing a bit of digging I see Willy reported a similar issue back in Nov.
Maybe he can chime in?  But it seems to have fixed itself.
https://github.com/giampaolo/psutil/issues/2181

The author talks about it possibly finding "_psutil_posix.so" in the path,
but it's only installed in the python2 version.  Do you have python2-psutil
or the old psutil slackbuild still installed?  I would try removing them
and reinstalling python3-psutil.  I would also check if you have any pip
installed packages.

I can't get anything to fail here, both solaar and locust build and run
without errors.


On Sun, Jun 18, 2023 at 8:46 PM KB_SBo  wrote:

> Hello all,
>
> I'm trying to an old logitech keyboard paired to another receiver - lost
> the original.  When running the GUI version the negative result is
>
> $ solaar
> solaar: error: Traceback (most recent call last):
>File "/usr/lib64/python3.9/site-packages/solaar/gtk.py", line 165, in
> main
>  import solaar.listener as listener
>File "/usr/lib64/python3.9/site-packages/solaar/listener.py", line
> 34, in 
>  from logitech_receiver import notifications as _notifications
>File
> "/usr/lib64/python3.9/site-packages/logitech_receiver/notifications.py",
> line 27, in 
>  from . import diversion as _diversion
>File
> "/usr/lib64/python3.9/site-packages/logitech_receiver/diversion.py",
> line 33, in 
>  import psutil
>File "/usr/lib64/python3.9/site-packages/psutil/__init__.py", line
> 102, in 
>  from . import _pslinux as _psplatform
>File "/usr/lib64/python3.9/site-packages/psutil/_pslinux.py", line
> 87, in 
>  PAGESIZE = cext_posix.getpagesize()
> AttributeError: module 'psutil._psutil_posix' has no attribute
> 'getpagesize'
>
>
> I used 'slpkg' and it looks like all was built in the right order
> (unless I missed something):
>
>• python3-flit_core.SlackBuild ✔️
>• python3-flit_core-3.9.0-x86_64-1_SBo.tgz ✔️
>• python3-installer.SlackBuild ✔️
>• python3-installer-0.7.0-x86_64-1_SBo.tgz ✔️
>• python3-pyproject-hooks.SlackBuild ✔️
>• python3-pyproject-hooks-1.0.0-x86_64-1_SBo.tgz ✔️
>• python3-wheel.SlackBuild ✔️
>• python3-wheel-0.40.0-x86_64-1_SBo.tgz ✔️
>• python3-build.SlackBuild ✔️
>• python3-build-0.10.0-x86_64-1_SBo.tgz ✔️
>• python3-psutil.SlackBuild ✔️
>• python3-psutil-5.9.5-x86_64-1_SBo.tgz ✔️
>• python3-xlib.SlackBuild ✔️
>• python3-xlib-0.33-x86_64-1_SBo.tgz ✔️
>• pyudev.SlackBuild ✔️
>• pyudev-0.24.1-x86_64-1_SBo.tgz ✔️
>• python-evdev.SlackBuild ✔️
>• python-evdev-1.6.1-x86_64-1_SBo.tgz ✔️
>• Solaar.SlackBuild ✔️
>• Solaar-1.1.9-x86_64-1_SBo.tgz ✔️
>
> Command line work exit for "pair" (did not test "config")
>
> $ solaar pair
> solaar: error: Traceback (most recent call last):
>File "/usr/lib64/python3.9/site-packages/solaar/cli/__init__.py",
> line 208, in run
>  m = import_module('.' + action, package=__name__)
>File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in
> import_module
>  return _bootstrap._gcd_import(name[level:], package, level)
>File "", line 1030, in _gcd_import
>File "", line 1007, in _find_and_load
>File "", line 986, in
> _find_and_load_unlocked
>File "", line 680, in _load_unlocked
>File "", line 850, in exec_module
>File "", line 228, in
> _call_with_frames_removed
>File "/usr/lib64/python3.9/site-packages/solaar/cli/pair.py", line
> 23, in 
>  from logitech_receiver import notifications as _notifications
>File
> "/usr/lib64/python3.9/site-packages/logitech_receiver/notifications.py",
> line 27, in 
>  from . import diversion as _diversion
>File
> "/usr/lib64/python3.9/site-packages/logitech_receiver/diversion.py",
> line 33, in 
>  import psutil
>File "/usr/lib64/python3.9/site-packages/psutil/__init__.py", line
> 102, in 
>  from . import _pslinux as _psplatform
>File "/usr/lib64/python3.9/site-packages/psutil/_pslinux.py", line
> 87, in 
>  PAGESIZE = cext_posix.getpagesize()
> AttributeError: module 'psutil._psutil_posix' has no attribute
> 'getpagesize'
>
> -kb
>
>
>
>
>
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [python3-setuptools] A Question about a SlackBuild.

[fourtysixandtwo]

On Fri, Jun 9, 2023 at 6:20 AM Arnaud via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

>
> I like the idea of installing it in /opt
> I would become a requirement of python3-dulwich, and the Slackbuild itself
> would
> set the right PYTHONPATH, while not altering the stock slackware's
> packages.
>
> That does work, I've just removed my own updated setuptools and replaced
> the
> proper slackware one, checked dulwich build still doesn't work, then
> installed
> your slackbuild, and confirmed it builds fine when adding the proper
> PYTHONPATH
> in the SlackBuild script.
>
> In the absence of your package, the dulwich build ignores the PYTHONPATH,
> meaning that on a -current box the SlackBuild will also work fine, without
> python3-setuptools-opt
>
> Please, do submit your slackbuild, it works for me :)
>
> - Yth.
>
> PS : Urk, where do you live to have such heat at night ? I'm almost
> suffering
> with 26°C during the day already...
>

Thanks for testing, I'll get it finished up and submit it next week.

With that added I can get around to adding maturin.  That's the one missing
build system I've come across that we don't have yet.

Cheers

P.S. In southern Alberta and that was just in the house.  A/C has always
been very optional here, but it's quickly becoming necessary.  At least
it's humid.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [python3-setuptools] A Question about a SlackBuild.

[fourtysixandtwo]

Hi Yth,

I have a slackbuild for setuptools, using the same version (65.1.1) and
patch from current source that I've been thinking of uploading.  I've
tested it with a newer version as well, so I'm not set on using the one
from current.

I've attached the slackbuild if you want to give it a try.  It could use
another set of eyes and testing.  Let me know your thoughts.

Here's a snippet from the README on how to use it.

Installs to /opt/python3.9/site-packages.

Add the following before the python3 build commands in your
Slackbuild to use this version over the stock one in 15.0:

export PYTHONPATH=/opt/python3.9/site-packages/

Cheers

P.S. It's currently 26C in my house and I can't sleep so you're getting
this reply now instead of later

On Fri, Jun 9, 2023 at 1:44 AM Arnaud via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Hi everybody !
>
> I'm facing a slight problem.
> I've updated python3-dulwich, apparently more than a month ago.
> It is used by Kallithea and hg-git which I also maintain, I'm not using
> hg-git
> often, but I have a working and updated Kallithea service around.
> Well it seems I didn't test this update as throughly as I thought.
> Or at all, for that matter.
>
> The build is broken and produces those files :
>
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/PKG-INFO
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/SOURCES.txt
>
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/dependency_links.txt
>
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/top_level.txt
>
> That, obviously, doesn't work as expected.
>
> The problem resides in the python-setuptools package of Slackware 15.0
> which is
> at version 57.5.0.
> In dulwich/pyproject.toml lies the answer :
> [build-system]
> requires = ["setuptools>=61.2"]
>
>
> Here I've got three solutions :
>
>  * revert dulwich to earlier version, 0.21.3, and wait for Slackware 15.1.
>
>  * create a python3-setuptools package which'll overwrite Slackware's stock
> python-setuptools with a newer version. Could even name it
> python-setuptools for
> obvious, and transparent, replacement. It'll probably be updated naturally
> when
> Slackware releases 15.1 is out.
>  -> I have it working with latest setuptools 67.8.0, and dulwich builds
> fine.
>
>  * somehow prepare a local setuptools to use for building dulwich, adding
> the
> source to dulwich's info file, and building both while installing only
> dulwich.
>
>
> Does anyone have any advice on that ?
> I mean, apart from the obvious « test your friggin' SlackBuilds before
> submitting them », I've got it in a loop between my ears, and in French...
>
>  - Yth.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


python3-setuptools-opt.tar.gz
Description: application/gzip
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Next week, I will no longer maintain and update SlackBuilds

[fourtysixandtwo]

Thanks for the work you've put in Isaac.

At first glance I think anything I might have taken over is already spoken
for.

Cheers

On Sun, Jun 4, 2023 at 5:34 PM isaac...@isaacyu1.com 
wrote:

> Hi everyone,
>
> ​I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework, I am going to have a harder time
> maintaining it all.
>
> This is the last week in which I will maintain and update SlackBuilds.
>
> I will also switch my email address (on SlackBuilds) to
> isaa...@protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
> I need to pay a small yearly subscription fee (to Gandi, the company) for
> the isaacyu1.com domain. However, the ProtonMail email service is free.
> Hence the email address change.
>
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
>
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
>
> - Isaac ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20230520.1

[fourtysixandtwo]

Hi Daniil,

That should already happen via python3-build.  If you are using sbopkg,
have you rebuilt the queues lately?

Here's the queue I see:
# cat /var/lib/sbopkg/queues/python3-editables.sqf
python3-flit_core
python3-installer
python3-wheel
python3-pyproject-hooks
python3-build
python3-editables

It also works fine with sbotools and slpkg on my build VM.

Cheers

On Sun, May 21, 2023 at 9:16 AM Daniil Bratashov  wrote:

> It seems that the python3-pyproject-hooks should be now added as
> dependency for a number of python3 libraries - build of
> python3-editables or python3-hatchling is broken on my system.
>
> WBR, Daniil Bratashov.
>
> On Sat, May 20, 2023 at 8:57 AM Willy Sudiarto Raharjo
>  wrote:
> >
> > Sat May 20 04:18:53 UTC 2023
> > academic/CAFS_divergence: Fix ARCH section.
> > academic/CAPS_coevolution: Fix ARCH section.
> > academic/Gblocks: Fix ARCH section.
> > academic/amd: Align with template.
> > academic/amplifx: Fix ARCH section.
> > academic/arpack-ng: Align with template.
> > academic/btf: Align with template.
> > academic/camd: Align with template.
> > academic/cblas: Align with template.
> > academic/ccolamd: Align with template.
> > academic/cdo: Updated for version 2.2.0.
> > academic/cholmod: Align with template.
> > academic/colamd: Align with template.
> > academic/colin: Use template TMP assignment.
> > academic/csparse: Align with template.
> > academic/cxsparse: Align with template.
> > academic/fiji: Fix ARCH section.
> > academic/finchtv: Fix ARCH section.
> > academic/gresistor: Align with template.
> > academic/klu: Align with template.
> > academic/lapacke: Align with template.
> > academic/ldl: Align with template.
> > academic/megax: Fix and mv ARCH sect.
> > academic/metis: Align with template.
> > academic/ncbi-blast: Fix and mv ARCH sect.
> > academic/octave: Align with template.
> > academic/plus42: Updated for version 1.0.19.
> > academic/pyfits: Align with template.
> > academic/python2-kiwisolver: Align with template.
> > academic/python2-scipy: Align with template.
> > academic/python3-scipy: Align with template.
> > academic/qrupdate: Align with template.
> > academic/rbio: Align with template.
> > academic/seqkit: Fix ARCH sect.
> > academic/spidey: Fix and mv ARCH sect.
> > academic/spqr: Align with template.
> > academic/suitesparseconfig: Align with template.
> > academic/ucsc-blat: Fix and mv ARCH sect, http->https.
> > academic/umfpack: Align with template.
> > academic/xoscope: Align with template.
> > academic/xsimd: Updated for version 11.1.0.
> > audio/TiMidity++: Align with template.
> > audio/easymp3gain: Fix ARCH section. Change to i586.
> > audio/freepats: Align with template.
> > audio/pipewire-native-jack: Align with template.
> > audio/sonata: Align with template.
> > desktop/dbgl-legacy: New maintainer, builds from source.
> > desktop/ee: Align with template.
> > desktop/engrampa: Added (archive manager for the MATE desktop)
> > desktop/gnome-screenshot: slack-desc nitpick.
> > desktop/mate-desktop-environment: Added (continuation of GNOME 2)
> > desktop/mate-media: Added (media tools for the MATE desktop)
> > desktop/mate-power-manager: Added (power session daemon for MATE)
> > desktop/mate-screensaver: Updated for version 1.26.2.
> > desktop/mate-session-manager: Updated for version 1.26.1.
> > desktop/mate-settings-daemon: Updated for version 1.26.1.
> > desktop/mate-terminal: Added (terminal emulator for MATE)
> > desktop/mate-utils: Added (various utilities for the MATE desktop)
> > desktop/nwg-dock: Updated for version 0.3.4.
> > desktop/rss-guard: Align with template.
> > desktop/thunar-custom-actions: Change of maintainer
> > desktop/todoman: change atomicwrites to python3-atomicwrites
> > desktop/vinagre: Added (remote desktop viewer for GNOME)
> > development/Pivy: Align with template.
> > development/amazon-corretto: Align with template.
> > development/cpan2tgz: Align with template.
> > development/cppunit: Align with template.
> > development/cudatoolkit: Fix ARCH sect. amd symlinks.
> > development/d-tools: Updated for version 2.103.1
> > development/dis6502: Updated for version 0.15+2857fc3_20180311.
> > development/dmd: Updated for version 2.103.1
> > development/ecl: Align with template.
> > development/elixir: Align with template.
> > development/erlang-otp: Align with template.
> > development/gcc5: Fix -march for i486, keep sbolint quiet.
> > development/gcc5: slack-desc nitpick.
> > development/icon: Align with template.
> > development/jdk: Align with template.
> > development/jupyter-ipykernel: Updated for version 6.23.1.
> > development/kForth-32: Fix SlackBuild.
> > development/kForth-64: Fix SlackBuild.
> > development/nickle: Align with template.
> > development/nodejs: Updated for version 20.2.0.
> > development/noweb: Align with template.
> > development/numpy-legacy: Align with template.
> > development/openjdk8: Updated for version 8u372.
> > development/poedit: Updated for version 3.3.1.
> > 

[Slackbuilds-users] MD5SUM error python3-debugpy

[fourtysixandtwo]

python3-debugpy:
 MD5SUM check for debugpy-1.6.7.tar.gz ... FAILED!
   Expected: a5fa42316f03e2dd71339875643db9e9
   Found:71f70f440a93c077ea878cee0cc8adba
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] slackbuilds up for grabs

[fourtysixandtwo]

I'll take the following to rename/remove python2 unless someone else
wants/uses them.

python-iso3166
python-iso639
pyqt-distutils
xlsx2csv

cheers

On Sun, May 7, 2023 at 2:34 PM Ozan Türkyılmaz 
wrote:

> Hey All,
>
> I'll take thunar-custom-actions.
>
> Regards,
> Ozan
>
>>
>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] remove wheel slackbuild

[fourtysixandtwo]

Thanks Andrew.  I thought I'd done that, but obviously not..doh!

I've submitted python2-wheel (minus usr/bin/wheel) and tested building
those three builds against it successfully.  That will be better than
keeping the wheel slackbuild around.

Attached are the dep changes I used for those 3 slackbuilds.

Cheers

On Mon, May 1, 2023 at 4:43 AM Andrew Clemons 
wrote:

> On 1/05/23 07:16, fourtysixandtwo wrote:
> > Arnaud's tests backup my findings and why I didn't create a
> > python2-wheel and suggest the removal of the old wheel slackbuild
> > sooner rather than later.  It's just not needed and would only cause a
> > conflict (/usr/bin/wheel) with python3-wheel.  And we don't need more
> > wxPython-like conflicts!
> >
> > The other two builds (rencode and pynacl) that have those same
> > warnings need to be split/renamed, but also build just fine despite
> > the wheel missing warning. (as mentioned in my PR)
> >
> > My testing included comparing the build log and packages between no
> > wheel , old wheel slackbuild, and just python3-wheel installed.  There
> > is no difference except the warning and functionality tests are
> > successful.  (except for python2-automat which seems to be broken and
> > more testing would be moot given Arnaud planning it's removal)
> >
> > So I suggest removing the 3 commits to "fix wheel dependency" sitting
> > in Andrew's branch and we remove the old wheel slackbuild.
>
>  > It's just not needed
>
> That is not quite true.
>
> The reason we see the warning is because there is no python2 version of
> wheel and pip is downloading it as root.
>
> Take pynacl for example:
>
> ```
> # ls -A /var/lib/pkgtools/packages/*SBo*
> /var/lib/pkgtools/packages/cffi-1.13.2-x86_64-1_SBo
> /var/lib/pkgtools/packages/python3-flit_core-3.8.0-x86_64-2_SBo
> /var/lib/pkgtools/packages/python3-wheel-0.40.0-x86_64-1_SBo
> /var/lib/pkgtools/packages/pycparser-2.19-x86_64-1_SBo
> /var/lib/pkgtools/packages/python3-installer-0.5.1-x86_64-1_SBo
>
> # unshare -n bash pynacl.SlackBuild
> [...]
> WARNING: The wheel package is not available.
> DEPRECATION: Python 2.7 reached the end of its life on January 1st,
> 2020. Please upgrade your Python as Python 2.7 is no longer maintained.
> A future version of pip will drop support for Python 2.7. More details
> about Python 2 support in pip, can be found at
> https://pip.pypa.io/en/latest/development/release-process/#python-2-support
> WARNING: Retrying (Retry(total=4, connect=None, read=None,
> redirect=None, status=None)) after connection broken by
> 'NewConnectionError('
> object at 0x7f6c213b07d0>: Failed to establish a new connection: [Errno
> -3] Temporary failure in name resolution',)': /simple/wheel/
> WARNING: Retrying (Retry(total=3, connect=None, read=None,
> redirect=None, status=None)) after connection broken by
> 'NewConnectionError('
> object at 0x7f6c213b0e10>: Failed to establish a new connection: [Errno
> -3] Temporary failure in name resolution',)': /simple/wheel/
> WARNING: Retrying (Retry(total=2, connect=None, read=None,
> redirect=None, status=None)) after connection broken by
> 'NewConnectionError('
> object at 0x7f6c213b0d50>: Failed to establish a new connection: [Errno
> -3] Temporary failure in name resolution',)': /simple/wheel/
> WARNING: Retrying (Retry(total=1, connect=None, read=None,
> redirect=None, status=None)) after connection broken by
> 'NewConnectionError('
> object at 0x7f6c213b0a10>: Failed to establish a new connection: [Errno
> -3] Temporary failure in name resolution',)': /simple/wheel/
> WARNING: Retrying (Retry(total=0, connect=None, read=None,
> redirect=None, status=None)) after connection broken by
> 'NewConnectionError('
> object at 0x7f6c213b0c50>: Failed to establish a new connection: [Errno
> -3] Temporary failure in name resolution',)': /simple/wheel/
> ERROR: Could not find a version that satisfies the requirement wheel
> (from versions: none)
> ERROR: No matching distribution found for wheel
> Traceback (most recent call last):
>File "setup.py", line 264, in 
>  "Programming Language :: Python :: 3.8",
>File "/usr/lib64/python2.7/site-packages/setuptools/__init__.py",
> line 144, in setup
>  _install_setup_requires(attrs)
>File "/usr/lib64/python2.7/site-packages/setuptools/__init__.py",
> line 139, in _install_setup_requires
>  dist.fetch_build_eggs(dist.setup_requires)
>File "/usr/lib64/python2.7/site-packages/setuptools/dist.py", line
> 721, in fetch_build_eggs
>  replace_conflicting=True,
>File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 7

Re: [Slackbuilds-users] remove wheel slackbuild

[fourtysixandtwo]

Arnaud's tests backup my findings and why I didn't create a
python2-wheel and suggest the removal of the old wheel slackbuild
sooner rather than later.  It's just not needed and would only cause a
conflict (/usr/bin/wheel) with python3-wheel.  And we don't need more
wxPython-like conflicts!

The other two builds (rencode and pynacl) that have those same
warnings need to be split/renamed, but also build just fine despite
the wheel missing warning. (as mentioned in my PR)

My testing included comparing the build log and packages between no
wheel , old wheel slackbuild, and just python3-wheel installed.  There
is no difference except the warning and functionality tests are
successful.  (except for python2-automat which seems to be broken and
more testing would be moot given Arnaud planning it's removal)

So I suggest removing the 3 commits to "fix wheel dependency" sitting
in Andrew's branch and we remove the old wheel slackbuild.

Cheers

On Sun, Apr 30, 2023 at 10:41 AM Arnaud via SlackBuilds-users
 wrote:
>
> > > With everything switched to python3-wheel, the wheel slackbuild can now be
> > > removed.
> >
> > i'll keep them for a week and remove them if no reports of scripts broken
> >
> > --
> > Willy Sudiarto Raharjo
> >
>
> Well, there's no python2-wheel.
> It looks fine because it seems it mostly is an shell executable, so whatever
> Python version is used should be ok.
>
> But...
>
> python2-automat builds with python3-wheel with this message :
>
> WARNING: The wheel package is not available.
> DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. 
> Please
> upgrade your Python as Python 2.7 is no longer maintained. A future version of
> pip will drop support for Python 2.7. More details about Python 2 support in
> pip, can be found at
> https://pip.pypa.io/en/latest/development/release-process/#python-2-support
>
> Which looks like its making a call to pip, but not installing wheel, and not
> seeming to do much.
> The package builds fine.
> Keeping the old wheel package there removes the warning, and the
> python2-Automat package builds... well exactly the same.
> Removing all wheel packages, old and python3-wheel, well, doesn't change
> anything, the warning is there, the package builds fine.
>
> Anyway, this does not seem that big a problem, but I guess we could just drop
> the python3-wheel requirement altogether, since it builds the same.
>
> My whole not very useful point being that we might see some problems with the
> removal of python2 version of wheel.
>
> But...
>
> I don't care, and all python2 packages should be removed, or presenting
> themselves at the morgue soon ^^
>
> But... (again, I know)
>
> A package like python2-automat is used by python2-twisted, itself used by :
> Nevow TaskCoach python2-txaio Parsley txi2p Scrapy python2-orbited sslstrip
> python2-klein txrequests txsocksx graphite-carbon foolscap
>
> Most of which are probable outdated, not really maintained, and might not work
> at all, but will require some work to know what's what, ask for people to 
> update
> and step up as maintainers, or be removed (then I may at last kill
> python2-twisted and be rid of that old stuff).
>
> Cheers :)
>
> - Yth / Arnaud.
>
> PS : on a side note, problems might appear at a very late time, because the 
> old
> wheel package is not removed by the name change, therefore the python2 wheel
> will stay in many slackware box used by real people, masking any problem that
> might arise.
> So things will break, but I think those things are either already broken, or
> needs to be updated.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@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] remove wheel slackbuild

[fourtysixandtwo]

With everything switched to python3-wheel, the wheel slackbuild can now be
removed.

Cheers
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20230128.1

[fourtysixandtwo]

It's been added again in Willy's branch for the next update.  In the
meantime, I've also attached the slackbuild.

Cheers.

On Fri, Jan 27, 2023 at 8:52 PM netrixtardis 
wrote:

> python/python3-glances: Updated for version 3.3.1.1.
>
>
> missing python3-ujson from tree as indicated from REQUIRED. Currently
> broken.
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


python3-ujson.tar.xz
Description: application/xz
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Wrong version number for pending python3-setuptools-scm

[fourtysixandtwo]

Hi Tonus,

If you haven't noticed yet, the python3 version comes with 15.0 as
python-setuptools_scm so no need to add it.

Cheers

P.S.  Re: the recipe, you're welcome!

On Sun, Jan 15, 2023 at 3:26 PM Tonus  wrote:

> Hi all,
>
> I wanted to warn that I let the last working python2 version number in
> my python3 submission for setuptools-scm, python3-setuptools-scm.
>
> When I tried to correct that, I couldn't remove the pending file because
> another of my uploads (and a chain of others) is depending on it.
> The real problem is this version will not suffice to build a more recent
> submission (even if it's a simple version bump).
>
> Is it possible for an admin to substitute the attached archive to the
> uploaded one ?
>
> --
> Regards,
>
> Tonus
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Package a pip only module

[fourtysixandtwo]

Hi Tonus,

You need to check the pyproject.toml build-system section to figure out
which new method is needed.  In this case you need to add 3 deps and the
following lines instead of the setup.py one.

#add to REQUIRES
python3-build python3-installer wheel

#to the slackbuild
python3 -m build --no-isolation
python3 -m installer -d "$PKG" dist/*.whl

Cheers!

On Sat, Jan 14, 2023 at 7:06 PM Tonus  wrote:

> Hi everybody,
>
> I'm looking on a satisfying process to package pytest-asyncio (
> https://github.com/pytest-dev/pytest-asyncio).
> I'm a bit stuck since there's no setup.py I'm used to in the sources.
> Could someone kindly point me in some direction ? Even a SlackBuild
> achieving similar task ?
>
> Many thanks
>
> Regards
>
> Tonus
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20221223.1

[fourtysixandtwo]

I suggest installing "hoorex" and using that.  Works well if you
remember to re-process the repo data (hoorex -f) after an update.
Works in both directions and has a few other useful features.

On Fri, Dec 23, 2022 at 2:56 PM Tonus  wrote:
>
> Hi all,
>
> May I suggest something like :
> for x in $(cat my_builds.txt) ; do find SBo-15.0/ -name "$x.info" grep 
> "REQUIRE" {} \; ; done
>
> Beware, wrote that on my phone, can't test it.
>
> Since I feel more comfortable with such one-liner I would be glad to have 
> advices.
>
> Regards
>
> Le 23 décembre 2022 19:27:57 GMT+01:00, "B. Watson"  a 
> écrit :
> >
> >
> >On Fri, 23 Dec 2022, Alexander Verbovetsky wrote:
> >
> >> On Fri, Dec 23, 2022 at 10:28:04AM +0700, Willy Sudiarto Raharjo wrote:
> >>
> >>> libraries/leptopnica: Updated for version 1.83.0.
> >>
> >> This breaks graphics/tesseract. Can be fixed by straightforward bumping
> >> the tesseract version from 5.0.1 to 5.3.0 (the support for latest
> >> releases of leptonica is mentioned in the changelog for 5.2.0).
> >
> >Do people not even check to see if their updates break the builds that
> >depend on it?
> >
> >Open letter to all maintainers: before you submit an update, look
> >up your build using the reverse dependency search on the "Advanced
> >Search" page here: https://slackbuilds.org/advsearch.php
> >
> >For leptonica, this shows 2 builds: jbi2genc and tesseract. These
> >are exactly the ones that got broken by the update...
> >
> >*Test* the dependees with your updated build before submitting it.
> >If it breaks something, the *least* you can do is notify the
> >maintainers of the builds you're about to break. Even better if you
> >fix the breakage in their builds and *send them patches*.
> >___
> >SlackBuilds-users mailing list
> >SlackBuilds-users@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@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] SlackBuilds updates still not working

[fourtysixandtwo]

Thanks Willy, working here now too.

Cheers!


On Sat, Dec 17, 2022 at 7:02 PM Willy Sudiarto Raharjo
 wrote:
>
> > SlackBuilds updates are being reflected on git; however, they are not being 
> > reflected on the SlackBuilds.org website.
> > Using slpkg, I still am not able to update SlackBuilds (for example, 
> > nodejs).
> > You and Dave fixed SQLAlchemy; however, every other package (for the 
> > previous week) still doesn't update.
>
> ok, i have found the issue
> i forgot to create a tag for last public update and that messed up the
> tarball/sigs creation and also the database update part
>
> i have fixed the issue just now, please let us know if it's working
> i checked with sbopkg and it's working fine on google-earth and i assume
> it should be working on all scripts that were updated in the last public
> update.
>
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20221217.1

[fourtysixandtwo]

Dave,

The tar.gz and asc files haven't been updated yet either, so the updates
get overwritten.

# ls -l /var/lib/sbopkg/SBo/15.0/development/SQLAlchemy*
-rw-r--r-- 1 root root 2425 Nov 18 20:12
/var/lib/sbopkg/SBo/15.0/development/SQLAlchemy.tar.gz
-rw-r--r-- 1 root root  195 Nov 18 20:13
/var/lib/sbopkg/SBo/15.0/development/SQLAlchemy.tar.gz.asc

/var/lib/sbopkg/SBo/15.0/development/SQLAlchemy:
total 16
-rw-r--r-- 1 root root  205 Jul  1  2016 README
-rw-r--r-- 1 root root 3230 Dec 16 19:20 SQLAlchemy.SlackBuild
-rw-r--r-- 1 root root  333 Dec 16 19:20 SQLAlchemy.info
-rw-r--r-- 1 root root  864 Jul  1  2016 slack-desc



On Sat, Dec 17, 2022 at 5:06 AM Dave  wrote:

> There seems to be a problem in the database.  Git had the right
> version .45, but querying the DB returned .44.
>
> I've no idea how this happened but seems to be a glitch somewhere.
> I may have fixed it, but can you try again with slpkg?
>
> Thanks
>
> On 17/12/22 11:31,
> marav  put forth the proposition:
> > I'm a little confused
> >
> > On SBo, we have:
> >
> >15.0  > Development
> > > SQLAlchemy
> >(1.4.44)
> >
> > But in the .SlackBuilds :
> >
> > VERSION=${VERSION:-1.4.45}
> >
> > What happened ?
> >
> > So, when I slpkg upgrade:
> >
> > SQLAlchemy-1.4.45.tar.gz
>
> 100%[>]
> >   8.14M  25.9MB/sin 0.3s 2022-12-17 11:28:16 (25.9 MB/s) -
> > ‘/tmp/slpkg/build/SQLAlchemy/SQLAlchemy-1.4.45.tar.gz’ saved
> > [8535958/8535958] tar:
> /tmp/slpkg/build/SQLAlchemy/SQLAlchemy-1.4.44.tar.gz:
> > Cannot open: No such file or directory And it seems to be the same for
> > almost all the package in the last commit
> >
> > Le 17/12/2022 à 03:34, Willy Sudiarto Raharjo a écrit :
> > > hey guys,
> > >
> > > i might not be available for next week public update, so unless other
> > > admin steps up, next public update will be on last day in 2022 :)
> > >
> > >
> > > Sat Dec 17 02:17:12 UTC 2022
> > > academic/laghos: Added (LAGrangian High-Order Solver)
> > > desktop/alarm: Removed (abandoned project).
> > > desktop/gnome-shell-extension-appindicator: Updated for version 46.
> > > desktop/libqtxdg: Updated for version 3.10.0.
> > > desktop/lxqt-panel: Updated for version 1.2.0.
> > > desktop/lxqt-themes: Updated for version 1.2.0.
> > > development/SQLAlchemy: Updated for version 1.4.45.
> > > development/eclipse-cpp: Updated for version 4.26.
> > > development/eclipse-java: Updated for version 4.26.
> > > development/eclipse-jee: Updated for version 4.26.
> > > development/eclipse-php: Updated for version 4.26.
> > > development/fossil: Update MD5SUM.
> > > development/jupyterlab_server: Update README.
> > > development/nodejs: Updated for version 19.3.0.
> > > development/racer: Updated for version 2.2.1.
> > > development/regina-rexx: Updated for version 3.9.5.
> > > development/rstudio-desktop: Update for 2022.12.0+353
> > > development/uprog2: Added (Universeller Programmer fur Linux)
> > > development/vasm: Added (portable multi-target cross assembler)
> > > development/vscodium: Updated for version 1.74.1.22349.
> > > games/wolfmame: Updated for version 0.250.
> > > gis/gdal: Updated for version 3.6.1.
> > > gis/google-earth: Updated for version 7.3.6.
> > > gis/python3-cartopy: Updated for version 0.21.1.
> > > graphics/screengrab: Updated for version 2.5.0.
> > > haskell/haskell-Diff: Updated for version 0.4.1, new maint.
> > > haskell/haskell-ShellCheck: Updated for version 0.9.0.
> > > libraries/libfm-qt: Updated for version 1.2.0.
> > > libraries/liblxqt: Updated for version 1.2.0.
> > > libraries/libslirp: Fix script.
> > > libraries/lxqt-build-tools: Updated for version 0.12.0.
> > > libraries/lxqt-notificationd: Updated for version 1.2.0.
> > > libraries/lxqt-qtplugin: Updated for version 1.2.0.
> > > libraries/lxqt-sudo: Updated for version 1.2.0.
> > > libraries/python3-rpyc: Updated for version 5.3.0.
> > > misc/bitwarden-desktop: Updated for version 2022.12.0.
> > > misc/sbo-templates: Removed (renamed sbo-create).
> > > multimedia/freetube: Updated for version 0.18.0.
> > > multimedia/plexmediaserver: Updated for v 1.30.0.6486_629d58034.
> > > network/AdGuardHome: Updated for version 0.107.21.
> > > network/bitcoin: Updated for version 24.0.1.
> > > network/ddclient: Updated for version 3.10.0.
> > > network/jitsi-meet-desktop: Update for 2022.12.0
> > > network/netcat-openbsd: Updated for version 7.2_1.
> > > network/qutebrowser-bin: Update pdfjs to 3.1.81.
> > > network/signal-desktop: Updated for version 6.1.0.
> > > network/toot: Updated for version 0.32.1.
> > > network/vivaldi: Updated for version 5.6.2867.40.
> > > office/calibre-bin: Updated for version 6.10.0.
> > > office/khard: Updated for version 0.18.0. New EMAIL.
> > > python/autopep8: Updated for version 2.0.0.
> > > 

Re: [Slackbuilds-users] Updates - 20221217.1

[fourtysixandtwo]

Actually, I think I spoke too soon.

The initial "sbopkg -r" and subsequent "sbopkg -c" showed the updates,
but when I went to do the upgrade (after my previous email) the old
versions were used again.

My other testing was in my build vm with sbopkg pointed at a local git
copy, which of course worked fine.  And sbotools uses git as well.

On Sat, Dec 17, 2022 at 4:09 AM marav  wrote:
>
> Yes,
> Thanks for the confirmation
>
> As we don't want to bother the mailing list, I actually talk directly with 
> Dimitris.
>
>
> Le 17/12/2022 à 12:06, fourtysixandtwo a écrit :
>
> Hi marav,
>
> I see the same thing with slpkg.  Works fine with sbopkg and sbotools.
>
> Added Dimitris to cc.
>
> Cheers.
>
> On Sat, Dec 17, 2022 at 3:31 AM marav  wrote:
>>
>> I'm a little confused
>>
>> On SBo, we have:
>>
>> 15.0 > Development > SQLAlchemy (1.4.44)
>>
>> But in the .SlackBuilds :
>>
>> VERSION=${VERSION:-1.4.45}
>>
>> What happened ?
>>
>> So, when I slpkg upgrade:
>>
>> SQLAlchemy-1.4.45.tar.gz
>> 100%[>]
>>8.14M  25.9MB/sin 0.3s
>> 2022-12-17 11:28:16 (25.9 MB/s) - 
>> ‘/tmp/slpkg/build/SQLAlchemy/SQLAlchemy-1.4.45.tar.gz’ saved 
>> [8535958/8535958]
>>
>> tar: /tmp/slpkg/build/SQLAlchemy/SQLAlchemy-1.4.44.tar.gz: Cannot open: No 
>> such file or directory
>>
>>
>> And it seems to be the same for almost all the package in the last commit
>>
>> Le 17/12/2022 à 03:34, Willy Sudiarto Raharjo a écrit :
>>
>> hey guys,
>>
>> i might not be available for next week public update, so unless other admin 
>> steps up, next public update will be on last day in 2022 :)
>>
>>
>> Sat Dec 17 02:17:12 UTC 2022
>> academic/laghos: Added (LAGrangian High-Order Solver)
>> desktop/alarm: Removed (abandoned project).
>> desktop/gnome-shell-extension-appindicator: Updated for version 46.
>> desktop/libqtxdg: Updated for version 3.10.0.
>> desktop/lxqt-panel: Updated for version 1.2.0.
>> desktop/lxqt-themes: Updated for version 1.2.0.
>> development/SQLAlchemy: Updated for version 1.4.45.
>> development/eclipse-cpp: Updated for version 4.26.
>> development/eclipse-java: Updated for version 4.26.
>> development/eclipse-jee: Updated for version 4.26.
>> development/eclipse-php: Updated for version 4.26.
>> development/fossil: Update MD5SUM.
>> development/jupyterlab_server: Update README.
>> development/nodejs: Updated for version 19.3.0.
>> development/racer: Updated for version 2.2.1.
>> development/regina-rexx: Updated for version 3.9.5.
>> development/rstudio-desktop: Update for 2022.12.0+353
>> development/uprog2: Added (Universeller Programmer fur Linux)
>> development/vasm: Added (portable multi-target cross assembler)
>> development/vscodium: Updated for version 1.74.1.22349.
>> games/wolfmame: Updated for version 0.250.
>> gis/gdal: Updated for version 3.6.1.
>> gis/google-earth: Updated for version 7.3.6.
>> gis/python3-cartopy: Updated for version 0.21.1.
>> graphics/screengrab: Updated for version 2.5.0.
>> haskell/haskell-Diff: Updated for version 0.4.1, new maint.
>> haskell/haskell-ShellCheck: Updated for version 0.9.0.
>> libraries/libfm-qt: Updated for version 1.2.0.
>> libraries/liblxqt: Updated for version 1.2.0.
>> libraries/libslirp: Fix script.
>> libraries/lxqt-build-tools: Updated for version 0.12.0.
>> libraries/lxqt-notificationd: Updated for version 1.2.0.
>> libraries/lxqt-qtplugin: Updated for version 1.2.0.
>> libraries/lxqt-sudo: Updated for version 1.2.0.
>> libraries/python3-rpyc: Updated for version 5.3.0.
>> misc/bitwarden-desktop: Updated for version 2022.12.0.
>> misc/sbo-templates: Removed (renamed sbo-create).
>> multimedia/freetube: Updated for version 0.18.0.
>> multimedia/plexmediaserver: Updated for v 1.30.0.6486_629d58034.
>> network/AdGuardHome: Updated for version 0.107.21.
>> network/bitcoin: Updated for version 24.0.1.
>> network/ddclient: Updated for version 3.10.0.
>> network/jitsi-meet-desktop: Update for 2022.12.0
>> network/netcat-openbsd: Updated for version 7.2_1.
>> network/qutebrowser-bin: Update pdfjs to 3.1.81.
>> network/signal-desktop: Updated for version 6.1.0.
>> network/toot: Updated for version 0.32.1.
>> network/vivaldi: Updated for version 5.6.2867.40.
>> office/calibre-bin: Updated for version 6.10.0.
>> office/khard: Updated for version 0.1

Re: [Slackbuilds-users] Updates - 20221217.1

[fourtysixandtwo]

Hi marav,

I see the same thing with slpkg.  Works fine with sbopkg and sbotools.

Added Dimitris to cc.

Cheers.

On Sat, Dec 17, 2022 at 3:31 AM marav  wrote:

> I'm a little confused
>
> On SBo, we have:
> 15.0  > Development
>  > SQLAlchemy
> (1.4.44)
>
> But in the .SlackBuilds :
>
> VERSION=${VERSION:-1.4.45}
>
> What happened ?
>
> So, when I slpkg upgrade:
> SQLAlchemy-1.4.45.tar.gz
> 100%[>]
>8.14M  25.9MB/sin 0.3s
> 2022-12-17 11:28:16 (25.9 MB/s) - 
> ‘/tmp/slpkg/build/SQLAlchemy/SQLAlchemy-1.4.45.tar.gz’ saved [8535958/8535958]
>
> tar: /tmp/slpkg/build/SQLAlchemy/SQLAlchemy-1.4.44.tar.gz: Cannot open: No 
> such file or directory
>
>
> And it seems to be the same for almost all the package in the last commit
>
>
> Le 17/12/2022 à 03:34, Willy Sudiarto Raharjo a écrit :
>
> hey guys,
>
> i might not be available for next week public update, so unless other
> admin steps up, next public update will be on last day in 2022 :)
>
>
> Sat Dec 17 02:17:12 UTC 2022
> academic/laghos: Added (LAGrangian High-Order Solver)
> desktop/alarm: Removed (abandoned project).
> desktop/gnome-shell-extension-appindicator: Updated for version 46.
> desktop/libqtxdg: Updated for version 3.10.0.
> desktop/lxqt-panel: Updated for version 1.2.0.
> desktop/lxqt-themes: Updated for version 1.2.0.
> development/SQLAlchemy: Updated for version 1.4.45.
> development/eclipse-cpp: Updated for version 4.26.
> development/eclipse-java: Updated for version 4.26.
> development/eclipse-jee: Updated for version 4.26.
> development/eclipse-php: Updated for version 4.26.
> development/fossil: Update MD5SUM.
> development/jupyterlab_server: Update README.
> development/nodejs: Updated for version 19.3.0.
> development/racer: Updated for version 2.2.1.
> development/regina-rexx: Updated for version 3.9.5.
> development/rstudio-desktop: Update for 2022.12.0+353
> development/uprog2: Added (Universeller Programmer fur Linux)
> development/vasm: Added (portable multi-target cross assembler)
> development/vscodium: Updated for version 1.74.1.22349.
> games/wolfmame: Updated for version 0.250.
> gis/gdal: Updated for version 3.6.1.
> gis/google-earth: Updated for version 7.3.6.
> gis/python3-cartopy: Updated for version 0.21.1.
> graphics/screengrab: Updated for version 2.5.0.
> haskell/haskell-Diff: Updated for version 0.4.1, new maint.
> haskell/haskell-ShellCheck: Updated for version 0.9.0.
> libraries/libfm-qt: Updated for version 1.2.0.
> libraries/liblxqt: Updated for version 1.2.0.
> libraries/libslirp: Fix script.
> libraries/lxqt-build-tools: Updated for version 0.12.0.
> libraries/lxqt-notificationd: Updated for version 1.2.0.
> libraries/lxqt-qtplugin: Updated for version 1.2.0.
> libraries/lxqt-sudo: Updated for version 1.2.0.
> libraries/python3-rpyc: Updated for version 5.3.0.
> misc/bitwarden-desktop: Updated for version 2022.12.0.
> misc/sbo-templates: Removed (renamed sbo-create).
> multimedia/freetube: Updated for version 0.18.0.
> multimedia/plexmediaserver: Updated for v 1.30.0.6486_629d58034.
> network/AdGuardHome: Updated for version 0.107.21.
> network/bitcoin: Updated for version 24.0.1.
> network/ddclient: Updated for version 3.10.0.
> network/jitsi-meet-desktop: Update for 2022.12.0
> network/netcat-openbsd: Updated for version 7.2_1.
> network/qutebrowser-bin: Update pdfjs to 3.1.81.
> network/signal-desktop: Updated for version 6.1.0.
> network/toot: Updated for version 0.32.1.
> network/vivaldi: Updated for version 5.6.2867.40.
> office/calibre-bin: Updated for version 6.10.0.
> office/khard: Updated for version 0.18.0. New EMAIL.
> python/autopep8: Updated for version 2.0.0.
> python/autopep8: Updated for version 2.0.1.
> python/flake8: Updated for version 6.0.0.
> python/ptpython: Fix MD5SUM.
> python/ptpython: Fixed the version and checksum.
> python/pycodestyle: Updated for version 2.10.0.
> python/pysed: Removed (abandoned project).
> python/python-executing: Removed (renamed python3-executing)
> python/python3-autocommand: Updated for version 2.2.2.
> python/python3-cheroot: Updated for version 9.0.0, fixed homepage.
> python/python3-comm: Updated for version 0.1.2.
> python/python3-dill: Added (python modules).
> python/python3-hatch_vcs: Updated for version 0.3.0.
> python/python3-hatchling: Fix deps.
> python/python3-httpcore: Updated for version 0.16.2.
> python/python3-httpx: Updated for version 0.23.1.
> python/python3-jaraco.context: Updated for version 4.2.0.
> python/python3-jaraco.text: Updated for version 3.11.0.
> python/python3-libtmux: Updated for version 0.16.0.
> python/python3-mpi4py: Added (Message Passing Interface bindings)
> python/python3-netifaces: Updated for version 0.11.0.
> python/python3-pathspec: Updated for version 0.10.3.
> python/python3-pyflakes: 

Re: [Slackbuilds-users] issues with some deps.

[fourtysixandtwo]

Hi Tim,

Having a closer look and double checking the deps, you were correct about
python3-hatchling.  However, I can't agree on the other changes you
suggest.  I've noted the following discrepancies:

-python3-hatch_fancy_pypi_readme and python3-hatch_vcs are build time deps
only and neither depend on each other.
-several of the versions you list are outdated (primarily
python3-jsonschema 3.17.3-1)
-python3-pyrsistent does not have a dep for BeautifulSoup4

Here's the output from pipdeptree (does not show build deps) on my build vm:

jsonschema==4.17.3
 - attrs [required: >=17.4.0, installed: 21.4.0]
 - pyrsistent [required: >=0.14.0,!=0.17.2,!=0.17.1,!=0.17.0, installed:
0.19.2]

hatch-fancy-pypi-readme==22.8.0
 - hatchling [required: Any, installed: 1.11.1]
   - editables [required: >=0.3, installed: 0.3]
   - packaging [required: >=21.3, installed: 21.3]
 - pyparsing [required: >=2.0.2,!=3.0.5, installed: 2.4.7]
   - pathspec [required: >=0.10.1, installed: 0.10.3]
   - pluggy [required: >=1.0.0, installed: 1.0.0]
   - tomli [required: >=1.2.2, installed: 1.2.2]
 - tomli [required: Any, installed: 1.2.2]

hatch-vcs==0.3.0
 - hatchling [required: >=1.1.0, installed: 1.11.1]
   - editables [required: >=0.3, installed: 0.3]
   - packaging [required: >=21.3, installed: 21.3]
 - pyparsing [required: >=2.0.2,!=3.0.5, installed: 2.4.7]
   - pathspec [required: >=0.10.1, installed: 0.10.3]
   - pluggy [required: >=1.0.0, installed: 1.0.0]
   - tomli [required: >=1.2.2, installed: 1.2.2]
 - setuptools-scm [required: >=6.3.2, installed: 6.3.2]
   - packaging [required: >=20.0, installed: 21.3]
 - pyparsing [required: >=2.0.2,!=3.0.5, installed: 2.4.7]
   - setuptools [required: Any, installed: 57.5.0]
   - tomli [required: >=1.0.0, installed: 1.2.2]

Hope that clears things up and I'll get python3-hatchling updated.

Cheers

On Sun, Dec 11, 2022 at 7:32 AM Tim Dickson via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> python3-jsonschema lists a couple of new deps
> python3-hatch-fancy_pypi_readme and python3_hatch_vcs but as
> python3_hatch_vcs is a dep of python3-hatch-fancy_pypi_readme it
> shouldn't be listed (no deps of deps)
> in the same vein, python3-hatchling lists python3-build and
> python3-installer among it's deps list, both of which are already deps
> of python3-edittables and python3-pathspec, which are also deps of
> python3-hatchling.
>
> the dep tree is
> python3-jsonschema 3.17.3-1
>   -requires
>python3-importlib_metadata
>python3-attrs 21.4.0-1
>python3-pyrsistent 0.19.2-1
>python3-hatch_fancy_pypi_readme
>-requires
> python3-hatch_vcs 0.2.0-1
> -requires
>  python3-hatchling 1.11.1-1
>  -requires
>   python3-editables 0.3-1
>   -requires
>python3-build
>python3-installer
>wheel
>   python3-pathspec 0.10.2-1
>   -requires
>python3-build
>python3-installer
>wheel
>   python3-pluggy 1.0.0-1
>BeautifulSoup4
>-requires
> python3-soupsieve 2.3.1-2
>
> to summerise,
>
> so python3-jsonschema deps should be
>
> python3-importlib_metadata
> python3-attrs
> python3-pyrsistent
>   python3-hatch_fancy_pypi_readme
>   BeautifulSoup4
>
> and python3-hatchling_vcs deps should be
>
> python3-hatchling
>
> and  python3-hatchling deps should be
>
> python3-editables
> python3-pathspec
> python3-pluggy
>
>
> regards, Tim
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] issues with some deps.

[fourtysixandtwo]

Thanks for catching that Tim.  I'll get those fixes submitted later today.

Cheers

On Sun, Dec 11, 2022 at 7:32 AM Tim Dickson via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> python3-jsonschema lists a couple of new deps
> python3-hatch-fancy_pypi_readme and python3_hatch_vcs but as
> python3_hatch_vcs is a dep of python3-hatch-fancy_pypi_readme it
> shouldn't be listed (no deps of deps)
> in the same vein, python3-hatchling lists python3-build and
> python3-installer among it's deps list, both of which are already deps
> of python3-edittables and python3-pathspec, which are also deps of
> python3-hatchling.
>
> the dep tree is
> python3-jsonschema 3.17.3-1
>   -requires
>python3-importlib_metadata
>python3-attrs 21.4.0-1
>python3-pyrsistent 0.19.2-1
>python3-hatch_fancy_pypi_readme
>-requires
> python3-hatch_vcs 0.2.0-1
> -requires
>  python3-hatchling 1.11.1-1
>  -requires
>   python3-editables 0.3-1
>   -requires
>python3-build
>python3-installer
>wheel
>   python3-pathspec 0.10.2-1
>   -requires
>python3-build
>python3-installer
>wheel
>   python3-pluggy 1.0.0-1
>BeautifulSoup4
>-requires
> python3-soupsieve 2.3.1-2
>
> to summerise,
>
> so python3-jsonschema deps should be
>
> python3-importlib_metadata
> python3-attrs
> python3-pyrsistent
>   python3-hatch_fancy_pypi_readme
>   BeautifulSoup4
>
> and python3-hatchling_vcs deps should be
>
> python3-hatchling
>
> and  python3-hatchling deps should be
>
> python3-editables
> python3-pathspec
> python3-pluggy
>
>
> regards, Tim
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@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] python3-jsonschema stuck in pending

[fourtysixandtwo]

Hi, I can't resubmit python3-jsonschema as it says the file still exists
and still pending approval.

Thanks in advance!
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] BuildScripts up for grabs

[fourtysixandtwo]

To add to what Matteo said,

anki had Markdown removed in May, but looks like it snuck back in by
accident.

Can remove pelican from that list too as it's been updated.

Cheers

On Fri, Oct 14, 2022 at 9:52 AM Matteo Bernardini <
matteo.bernard...@gmail.com> wrote:

> Il giorno ven 14 ott 2022 alle ore 14:44 Markus Reichelt via
> SlackBuilds-users  ha scritto:
>
>> Markdown: Also, there is the issue of Markdown; it's in stock
>> Slackware 15.0 by now.  Dependees as shown on
>>
>> https://slackbuilds.org/advsearch.php?q=Markdown=revdep1
>>
>> should check if stuff works with the stock Slackware Markdown install
>> instead, and if so, let's remove the SBo legacy script.  If not,
>> SBo's Markdown needs a new maintainer too.
>>
>
> Slackware provides python-markdown that is the python3 module while
> Markdown on SBo is the python2 version of the module.
>
> I had a look and Markdown is listed as used by the following SlackBuilds:
> - anki
> - apprise
> - diskscan
> - gmusicbrowser
> - pelican
> - vmd
>
> anki and vmd look python3-based now, so they should be ok with the
> python-markdown in Slackware (and Markdown should be removed from the
> dependencies).
>
> pelican, being built for python2, actually seems to use it as an optional
> dependency (but could be also been built for python3, together with his own
> dependencies, other distro do this).
>
> gmusicbrowser lists it between the dependencies but I'm not sure it's used
> https://aur.archlinux.org/packages/gmusicbrowser
>
> apprise needs a depper look by its maintainer because it's a mix of
> python2 and python3 dependencies at the moment (I doubt it works).
>
> the latest diskscan version (0.20) uses just python-PyYAML in Slackware
> and no other deps.
>
> I invite all the interested maintainers to please have a look and submit
> the needed changes, thanks in advance.
>
> Matteo Bernardini
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] OT qmake not found

[fourtysixandtwo]

Hi Peter,

I just tested on a 32bit 15.0 VM and am not seeing the same issue and qtmib
starts normally as either a regular user or as root.

Have you tried running it with a freshly created user to isolate whether
it's your user level issue or a system level one?

Cheers

On Fri, Sep 23, 2022 at 11:15 AM Peter Dambier 
wrote:

> On Fri, 23 Sep 2022 11:27:07 +0200
> Arnaud via SlackBuilds-users  wrote:
>
> > > Hello and have a nice weekend dear fellow Slack Builders,
> > >
> > > the trouble qtmib complained qmake missing
> > >
> > > "wich" finds "qmake" in "/usr/lib/qt5/bin".
> > >
> > > In "/usr/bin" I see "qmake-qt5 -> ../lib/qt5/bin/qmake".
> > >
> > > After
> > >
> > > ln -s /usr/lib/qt5/bin/qmake /usr/bin/qmake
> > >
> > > qtmib successfully built and I guess qtmib is not the only one.
> > >
> > > Kind regards and sorry for the noise
> > > Peter Dambier, DL2FBA
> >
> > /usr/lib64/qt5/bin should be added to $PATH by /etc/profile.d/qt5.sh
> > So either you're not in a full root shell (eg: use "su -", and not
> > just "su"), or something else is wrong on your end.
> >
> > You should have :
> > $ which qmake
> > /usr/lib64/qt5/bin/qmake
> >
> > Cheers,
> >
> >   - Yth.
> >
> Thankyou Arnaud,
>
> I have a 32 bit system but google ... this seems to be a recuring
> Qt problem, not specific Qt-5 and agnostic of X84, AMD64, ...
>
> "which" did find it in the path so "make" and "qmake" might be part
> of the party as well, automake spoiling the path or something.
>
> qt5.sh is there and did its work, adding "$QT5PATH"
>
> Google did not mention "qtmib" but others got bitten by a missing
> "qmake" as well.
>
> Cheers
> Peter Dambier, DL2FBA
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@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] python2 builds that can possibly be removed?

[fourtysixandtwo]

Hi,

The following python2 builds have no other dependencies and python3-*
versions have been uploaded in their place.  I believe they can be removed.

APScheduler
zxcvbn-python
rpyc
plumbum
PyRSS2Gen
pynzb
rebulk
babelfish
guessit
zc.lockfile
jaraco.classes
tempora
portend
cheroot
CherryPy
CherryMusic

Cheers
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] gaupol slackbuild up for grab

[fourtysixandtwo]

I can take over as maintainer.

I just finished updating and testing the build on 15.0 and current.
I'll upload it shortly if no one has any objections.

Cheers

On Wed, Sep 7, 2022 at 10:04 AM KG Hammarlund  wrote:
>
> I contacted the maintainer Andrés Barboza, suggesting updating to latest
> version and changing to Python3. Got the following reply:
>
> "I'm no longer maintaining Slackbuilds scripts. Feel free to update it
> and take the ownership."
>
> Since I'm running Slackware-current and haven't the time to manage a
> parallel stable 15.0 system plus that I also lack the skill to make
> other than very simple script adjustment I'm sorry to say that
> maintenance is beyond my capabilities. Maybe someone else is interested?
>
> Best,
>
> Karl
>
>
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Letter in version number

[fourtysixandtwo]

There's actually quite a few slackbuilds that have versions ending in
a letter(179, about half of which include a year or git commits) so it
is allowed, just not very common.

Cheers

On Mon, Aug 22, 2022 at 2:45 PM Didier Spaier  wrote:
>
> As a SlackBuild end user, I have no issue with version "number" including a 
> letter.
>
> I would only have one for a hyphen (unicode 002d).
>
> Cheers,
> Didier
>
> Le 22/08/2022 à 20:27, Brandon Pribula a écrit :
> > I'm sure I've read about this before on this mailing list but I can't 
> > remember
> > how we're supposed to deal with packages which have a letter in the version
> > number such as
> >
> > package-name-2.7.1b
> >
> > IIRC letters are not allowed. So what is the solution? If the letter is 
> > removed
> > then the user can't easily identify which version they're using. Could we 
> > just
> > increase the build number?
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Bad md5sum building python/python3-babel

[fourtysixandtwo]

Builds without issue on a 15.0 VM here.  Made sure downloads were
fresh and not previously cached.

On Tue, Jun 28, 2022 at 1:43 AM Duncan Roe  wrote:
>
> Hi,
>
> python3-babel.SlackBuild errorred out as below:
>
> > ++ python3 setup.py import_cldr
> > running import_cldr
> > Traceback (most recent call last):
> >   File "/tmp/SBo/babel-2.10.1/scripts/download_import_cldr.py", line 106, 
> > in 
> > main()
> >   File "/tmp/SBo/babel-2.10.1/scripts/download_import_cldr.py", line 81, in 
> > main
> > while not is_good_file(zip_path):
> >   File "/tmp/SBo/babel-2.10.1/scripts/download_import_cldr.py", line 66, in 
> > is_good_file
> > raise RuntimeError('Checksum mismatch: %r != %r'
> > RuntimeError: Checksum mismatch: 
> > 'cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e'
> >  != 
> > 'c64f3338e292962817b043dd11e9c47f533c9b70d432f83e80654e20f4937c72b37e66a60485df43f734b1ff94ebf0452547a063076917889303c9653b4d6ce5'
> > Traceback (most recent call last):
> >   File "/tmp/SBo/babel-2.10.1/setup.py", line 29, in 
> > setup(
> >   File "/usr/lib64/python3.9/site-packages/setuptools/__init__.py", line 
> > 153, in setup
> > return distutils.core.setup(**attrs)
> >   File "/usr/lib64/python3.9/distutils/core.py", line 148, in setup
> > dist.run_commands()
> >   File "/usr/lib64/python3.9/distutils/dist.py", line 966, in run_commands
> > self.run_command(cmd)
> >   File "/usr/lib64/python3.9/distutils/dist.py", line 985, in run_command
> > cmd_obj.run()
> >   File "/tmp/SBo/babel-2.10.1/setup.py", line 26, in run
> > subprocess.check_call([sys.executable, 
> > 'scripts/download_import_cldr.py'])
> >   File "/usr/lib64/python3.9/subprocess.py", line 373, in check_call
> > raise CalledProcessError(retcode, cmd)
> > subprocess.CalledProcessError: Command '['/usr/bin/python3', 
> > 'scripts/download_import_cldr.py']' returned non-zero exit status 1.
>
> When I checked the md5sum of cldr-common-41.0.zip it was wrong:
>
> > 17:34:52$ echo d346710d2beb5133bdb1d14f966ae2cd;md5sum cldr-common-41.0.zip
> > d346710d2beb5133bdb1d14f966ae2cd
> > d41d8cd98f00b204e9800998ecf8427e  cldr-common-41.0.zip
>
> I downloaded cldr-common-41.0.zip again, but had the same wrong md5sum as last
> time.
>
> Do you have a good file you can put up somewhere?
>
> Could you contact the site and let them know about this?
>
> Cheers ... Duncan.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] couple of DEP fixes

[fourtysixandtwo]

> Can all these be removed now?
>
> python/Flask-Babel
> python/Flask-Bcrypt
> python/Flask-Compress
> python/Flask-Dance
> python/Flask-Login
> python/Flask-Mail
> python/Flask-Principal
> python/Flask-SQLAlchemy
> python/Flask-WTF
> python/flask-paginate

Yes, they are all "broken" builds.  I would also add the following as
they broken and unmaintained projects.

python/Flask-Security
python/restplus

Cheers
___
SlackBuilds-users mailing list
SlackBuilds-users@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] couple of DEP fixes

[fourtysixandtwo]

Hi all,

Now that the prerequisites are in place the following dependencies need to
be updated.

desktop/anki
  -change Flask-Cors to python3-Flask-Cors
python/python3-Flask-RESTful
  -change aniso8601 to python3-aniso8601

Cheers
___
SlackBuilds-users mailing list
SlackBuilds-users@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] [PATCH] network/EarthReader-Web: Updated for version 0.3.0, changed REQUIRES.

[fourtysixandtwo]

This is needed to work with the Flask update.

Cheers.
From a505f8e65f1beb82c3f28aa10f507306d451b6fb Mon Sep 17 00:00:00 2001
From: fourtysixandtwo 
Date: Thu, 12 May 2022 13:51:49 -0600
Subject: [PATCH 11/52] network/EarthReader-Web: Updated for version 0.3.0,
 changed REQUIRES.

---
 network/EarthReader-Web/EarthReader-Web.SlackBuild | 6 --
 network/EarthReader-Web/EarthReader-Web.info   | 8 
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/network/EarthReader-Web/EarthReader-Web.SlackBuild b/network/EarthReader-Web/EarthReader-Web.SlackBuild
index bf2847139..a18152aa2 100644
--- a/network/EarthReader-Web/EarthReader-Web.SlackBuild
+++ b/network/EarthReader-Web/EarthReader-Web.SlackBuild
@@ -22,10 +22,13 @@
 #  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
+# 20220512 46and2: Removed python2 as it was missing requirements.
+#   -Updated for v0.3.0.
+
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=EarthReader-Web
-VERSION=${VERSION:-0.2.1}
+VERSION=${VERSION:-0.3.0}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -79,7 +82,6 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-python2 setup.py install --root=$PKG
 python3 setup.py install --root=$PKG
 
 find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \
diff --git a/network/EarthReader-Web/EarthReader-Web.info b/network/EarthReader-Web/EarthReader-Web.info
index f845e2ce8..2b6cc005b 100644
--- a/network/EarthReader-Web/EarthReader-Web.info
+++ b/network/EarthReader-Web/EarthReader-Web.info
@@ -1,10 +1,10 @@
 PRGNAM="EarthReader-Web"
-VERSION="0.2.1"
+VERSION="0.3.0"
 HOMEPAGE="http://earthreader.org/;
-DOWNLOAD="https://pypi.python.org/packages/source/E/EarthReader-Web/EarthReader-Web-0.2.1.tar.gz;
-MD5SUM="d392961ec1e9d2778b841bd938692553"
+DOWNLOAD="https://pypi.python.org/packages/source/E/EarthReader-Web/EarthReader-Web-0.3.0.tar.gz;
+MD5SUM="cfb14e190a10ba736cc7db099b5d937b"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES="python-libsass Flask libearth waitress python3-waitress"
+REQUIRES="python-libsass Flask libearth python3-waitress"
 MAINTAINER="Dimitris Zlatanidis"
 EMAIL="d.zlatani...@gmail.com"
-- 
2.35.3

___
SlackBuilds-users mailing list
SlackBuilds-users@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] [PATCH] anki: Update DEP.

[fourtysixandtwo]

Hi,

Here's a patch to update/add a couple of dependencies for python3 to work
with the new Flask, click, and werkzeug.

It also needs an updated Flask-Cors (sitting in the pending queue) and
complains about missing orjson (no slackbuild) but appears to work fine
without it.

Cheers.
From 98aca8c547a438831a7d94ec62d7599a0ce3bc3b Mon Sep 17 00:00:00 2001
From: fourtysixandtwo 
Date: Sun, 15 May 2022 15:39:21 -0600
Subject: [PATCH 52/52] desktop/anki: Update DEP.

---
 desktop/anki/anki.info | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/desktop/anki/anki.info b/desktop/anki/anki.info
index bd681f433..dc1b768fc 100644
--- a/desktop/anki/anki.info
+++ b/desktop/anki/anki.info
@@ -7,6 +7,6 @@ DOWNLOAD_x86_64="https://files.pythonhosted.org/packages/19/71/6622dcad9d1c6988e
 https://files.pythonhosted.org/packages/77/06/3ee5c1ee4d71f1fe96bb961a1d8104dcdfb492eb6a27f9f3a73883395eb4/aqt-2.1.51-py3-none-any.whl;
 MD5SUM_x86_64="98ffc4b8dcd0dc4f58f1b9f9bf3cb752 \
 703e288310b82dda9677f549f2f6acc1"
-REQUIRES="python3-PyQtWebEngine send2trash decorator Markdown python3-jsonschema BeautifulSoup4 Flask Flask-Cors waitress"
+REQUIRES="python3-PyQtWebEngine send2trash decorator Markdown python3-jsonschema BeautifulSoup4 Flask Flask-Cors python3-waitress protobuf3"
 MAINTAINER="Caterino Tommaso, T.O.P."
 EMAIL="alan_avern...@lavaspambit.com (remove NO and SPAM)"
-- 
2.35.3

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] eyeD3 slackbuild

[fourtysixandtwo]

Noted, and will do.

On Fri, May 13, 2022 at 8:52 PM Dave Woodfall  wrote:

> On 14/05/22 03:30,
> Dave Woodfall  put forth the proposition:
> > On 11/05/22 17:24,
> > fourtysixandtwo  put forth the proposition:
> > > Hi all,
> > > I found eyeD3 was broken while testing updates to pylast.  I've emailed
> > > Larry a couple of times in the last 10 days but he hasn't responded.
> > > I've attached both format-patches I have for eyeD3.
> > > Cheers
> > Hi
> > Can you make a single patch of the whole folder next time please?
> > Thanks
>
> In fact Willy made a good blog post on how to make patches to send to
> the list:
>
> https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html
>
> Could you also put [PATCH] at the start of the message subject too,
> so it's more obvious there is one.
>
> --
> Dave
>
> sbo-maintainer-tools:
> https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> SBo templates:
> https://slackbuilds.org/templates/
> How to format github downloads:
> https://slackbuilds.org/GITHUB_URLs.txt
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@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] werkzeug, click, and Flask upgrades

[fourtysixandtwo]

Hi all,

I uploaded upgrades today along with two legacy builds, werkzeug-legacy1
and click-legacy7.

Since these upgrades have many dependant slackbuilds (51 in total), I'd
like to give an update on the result of my testing.  If you're a maintainer
of one of those builds, you'll be getting an email from me in the next
couple days.

-the following builds were already non-functional
  network/FireWorks (upgrade available, but needs work)
  network/flexget (upgrade available, but needs a lot of work)
  python/odoo (upgrade available, but needs work and a form filled out to
download)
  python/Flask-Security (unmaintained, but there's an updated fork)
  python/flask-restplus (unmaintained, but there's a replacement)
-the following need to use the legacy builds as specified to work
  network/onionshare  (werkzeug-legacy1)
  python/Kallithea  (click-legacy7)
  gis/gj2ascii  (click-legacy7)
  office/watson  (click-legacy7)
-everything else I have a patch for to get working and passes a rudimentary
functional test
  -most of the Flask related builds are python2 and Jinja2 (now included in
15) is only python3.
  -majority are easily fixed by adding python3 to the build and an updated
version.

Cheers
___
SlackBuilds-users mailing list
SlackBuilds-users@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] eyeD3 slackbuild

[fourtysixandtwo]

Hi all,

I found eyeD3 was broken while testing updates to pylast.  I've emailed
Larry a couple of times in the last 10 days but he hasn't responded.

I've attached both format-patches I have for eyeD3.

Cheers
From e2a96f9eb0c0e4cf756702e1eb76205c25da92bb Mon Sep 17 00:00:00 2001
From: fourtysixandtwo 
Date: Fri, 18 Mar 2022 19:47:33 -0600
Subject: [PATCH 0124/1126] audio/eyeD3: Change i486 to i586

---
 audio/eyeD3/eyeD3.SlackBuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/audio/eyeD3/eyeD3.SlackBuild b/audio/eyeD3/eyeD3.SlackBuild
index b727e7843..10a2b214e 100644
--- a/audio/eyeD3/eyeD3.SlackBuild
+++ b/audio/eyeD3/eyeD3.SlackBuild
@@ -38,7 +38,7 @@ PKGTYPE=${PKGTYPE:-tgz}
 
 if [ -z "$ARCH" ]; then
   case "$( uname -m )" in
-i?86) ARCH=i486 ;;
+i?86) ARCH=i586 ;;
 arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
   esac
-- 
2.35.3

From 277975cfc0a7ac398b34b06271dd1e15f17c1cd9 Mon Sep 17 00:00:00 2001
From: fourtysixandtwo 
Date: Mon, 2 May 2022 17:37:11 -0600
Subject: [PATCH 07/17] audio/eyeD3: Fix REQUIRES.

---
 audio/eyeD3/eyeD3.info | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/audio/eyeD3/eyeD3.info b/audio/eyeD3/eyeD3.info
index 4119d1f6b..a3e290edf 100644
--- a/audio/eyeD3/eyeD3.info
+++ b/audio/eyeD3/eyeD3.info
@@ -5,6 +5,6 @@ DOWNLOAD="http://eyed3.nicfit.net/releases/eyeD3-0.9.6.tar.gz;
 MD5SUM="4e5ee817d59ad94a39301ee981171990"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES="pathlib2 python-magic pylast"
+REQUIRES="python3-deprecation python3-filetype pylast"
 MAINTAINER="Larry Hajali"
 EMAIL="larryhaja[at]gmail[dot]com"
-- 
2.35.3

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/