From msi at malbolge.net  Fri Aug  2 21:29:45 2019
From: msi at malbolge.net (Michael Siegel)
Date: Fri, 2 Aug 2019 23:29:45 +0200
Subject: [Slackbuilds-users] Suggestions for SlackBuild Usage Howto
In-Reply-To: <CAEWL1_-w_EBSSJu2D4FZKOD84i_+90NBY9BX9t6_pxmqsPh==A@mail.gmail.com>
References: <d45a0e5b-2d9a-80bc-eab9-d87749ff2623@malbolge.net>
 <CAEWL1_-w_EBSSJu2D4FZKOD84i_+90NBY9BX9t6_pxmqsPh==A@mail.gmail.com>
Message-ID: <429c1db6-4712-753f-6ff4-7d642114f046@malbolge.net>


Am 28.07.19 um 21:52 schrieb Jheengut Pritvi:
> Hi,
> 
> Great initiative.
> 
> Keep up the good work.

Thanks for the kind words.

The problem is that keeping up that good work doesn't really make any
sense if no one with write access to that page agrees to merge it. So,
I'm just gonna wait.


Michael

> On Sun, 21 Jul 2019 at 20:19, Michael Siegel <msi at malbolge.net> wrote:
> 
>> Hello,
>>
>> I have some suggestions for improving the SlackBuild Usage HOWTO at
>> http://slackbuilds.org/howto/.
>>
>> The first section (?Caveat?) currently reads like this:
>>
>>   All of our scripts are written and tested for usage on the latest
>>   stable release of Slackware with full installation and updated with
>>   latest patches; if you're trying them on older versions of Slackware,
>>   you should read this page referenced in our FAQ.
>>
>> My suggestion is to change that to:
>>
>>   All of our scripts are written and tested for usage on a full
>>   installation of the latest stable release of Slackware updated with
>>   the latest patches. If you're trying them on older versions of
>>   Slackware, you should read this page referenced in our FAQ.
>>
>> Then, the Howto does not mention verification of the downloaded source
>> packages. I think this should either be added to step one or be
>> step two. It could be worded like this:
>>
>>   To verify the downloaded source's integrity, first run `md5sum
>>   chemtool-1.6.14.tar.gz' to get the MD5 sum of the downloaded source
>>   archive. Then compare it to the MD5 sum shown in the `chemtool.info'
>>   file. If they don't match, something is wrong.
>>
>> I just realized that Step 1 already doesn't mention verifying the
>> SlackBuild's GPG signature. I think that should be included in the Howto
>> as well.
>>
>> So, maybe, it would be best to split Step 1 up like this:
>>
>>   * Step 1 ? Download and verify the SlackBuild archive
>>   * Step 2 ? Download and verify the application's source archive
>>
>> What do you think?
>>
>>
>> Best
>> Michael

From rshepard at appl-ecosys.com  Fri Aug  2 22:49:40 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 2 Aug 2019 15:49:40 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
Message-ID: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>

On my current 32-bit desktop there are 331 installed SBo packages. The
replacement 64-bit desktop has only 200 installed SBo packages (some of
which are not on the old desktop).

I've been using sbopkg to update installed packages on the new desktop and
just installed and read about sbotools and sboui. All three appear to me to
work with the SBo repo (including the local copy), but not with to-be
recompiled packages in the /opt/slackbuilds/ directory tree copied to the
new host.

When packages are upgraded using sbopkg they do not update the build script
or source tarball in /opt/slackbuilds/. I ask for suggestions on the most
efficient way to go through the package directories here, download the
current tarballs and build scripts, and build those that are not yet
installed on the new desktop.

Resolving dependencies (which sbotools appears to do) would be _really_
helpful if it would work on what's in the local directories (not the SBo
synchronized tree).

Thanks in advance,

Rich


From willysr at slackbuilds.org  Sat Aug  3 01:05:02 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Aug 2019 08:05:02 +0700
Subject: [Slackbuilds-users] Updates - 20190803.1
Message-ID: <87239898-f318-d646-4578-3ede28f76b02@slackbuilds.org>

Welcome to the first update in August

we have 2 new JDK in our repository. JDK11 is the LTS version, while
JDK12 is the latest version provided by Oracle. We kept the origin jdk
version at 8 since it's still being maintained by Oracle and it still
support x86 (32 bit) architecture, while the rest are only spesific for
x86_64 (64 bit) only.

Sat Aug  3 00:55:47 UTC 2019
academic/DendroPy: Added (A Phylogenetic Computing Library).
academic/MetaPhlAn2: Added (Metagenomic Phylogenetic Analysis).
academic/PhyML: Updated for version 3.3.20190321.
academic/RAxML: Added (Randomized Axelerated Maximum Likelihood).
academic/RepeatMasker: Updated for version 4.0.9_p2.
academic/aliview: Updated for version 1.26.
academic/bedtools: Updated for version 2.28.0.
academic/biopython: Added (Python tools for biological computation).
academic/cadabra2: Updated for version 2.2.7_d81535e.
academic/clark-ugene: Updated for version git_6917bf9.
academic/copasi: Updated for version 4.26.213.
academic/diamond: Updated for version 0.9.25.
academic/fet: Updated for version 5.39.0.
academic/fiji: Updated for version 20190718.
academic/gelemental: Updated for version 2.0.0.
academic/kraken: Updated for version 1.1.1.
academic/mafft: Updated for version 7.429.
academic/mrbayes: Updated for version 3.2.7a.
academic/muscle: Updated for version 3.8.1551.
academic/ncbi-blast+: Updated for version 2.9.0.
academic/novocraft: Updated for version 3.09.03.
academic/perlprimer: Updated for version 1.2.4.
academic/pysam: Updated for version 0.15.3.
academic/stringtie: Updated for version 1.3.6.
academic/t_coffee: Updated for version 13.00_git33cdeb8.
academic/tophat: Updated for version 2.1.2.
academic/ugene: Updated for version 1.32.0.
desktop/dunst: Fix DOWNLOAD url.
desktop/icewm: Updated for version 1.5.5.
development/gradle: Update SOURCE.
development/ioncube-loader: Updated for version 10.3.7
development/jdk11: Added (Java Platform SDK).
development/jdk12: Added (Java Platform SDK).
development/jdk: Updated for version 8u221.
development/jupyter-nbdime: Updated for version 1.0.7.
development/pycharm: Updated for version 2019.2.
development/universal-ctags: Updated for version 920e791
games/gnurobbo: Added (Atari XE game FOOS Implementation).
games/larn: Update script.
games/qxw: Updated for version 20190722.
graphics/Blender: Updated for version 2.80
graphics/opencollada: Updated for version 1.6.68
libraries/libedit: Updated for version 20190324_3.1.
libraries/libregf: Updated for version 20190303.
libraries/live555: Updated for version 2019.07.27
libraries/opencv: Updated for version 4.1.1
misc/mosquitto: Updated for version 1.6.4
multimedia/x265: Updated for version 3.1.2.
network/asterisk: Updated for version 16.5.0.
network/brave-browser: Updated for version 0.66.101.
network/prosody-mod-smacks: Updated for version hg3634.
network/rdma-core: Added (RDMA core userspace libraries/daemons).
network/youtube-dl: Updated for version 2019.07.27.
network/zoom-linux: Updated for version 2.9.265650.0716.
office/calcurse: Add DST patch.
office/calibre-bin: Added (Ebook manager).
office/lyx: Updated for version 2.3.3.
office/pdfstudio: Updated for version 2019.1.1.
office/pdfstudioviewer: Updated for version 2019.1.1.
office/remind: Updated for version 03.01.16.
perl/MoarVM: Updated for version 2019.07.1.
perl/nqp: Updated for version 2019.07.1.
perl/perl-Role-Tiny: Updated for version 2.000007.
perl/rakudo: Updated for version 2019.07.1.
perl/zef: Updated for version 0.7.4.
python/parso: Updated for version 0.5.1.
python/python3-gitdb2: Added (IO of git-style object databases).
python/python3-gmpy2: Added (multi-precision arithmetic).
python/python3-mpmath: Update README.
python/python3-smmap2: Added (A sliding memory map manager).
python/sympy: Moved to python.
ruby/sequel: Fix MD5SUM.
system/ansible: Updated for version 2.8.3.
system/epson-inkjet-printer-escpr2: Updated for version 1.1.1.
system/keybase: Updated for version 4.2.1.
system/mailutils: Updated for version 3.7.
system/netdata: Updated for version 1.16.1.
system/passwordsafe: Fix DOWNLOAD url.
system/pspg: Updated for version 1.6.8.
system/rush: Added (Restricted User Shell).
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From jebrhansen+SBo at gmail.com  Sat Aug  3 19:06:36 2019
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sat, 3 Aug 2019 13:06:36 -0600
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
Message-ID: <CANi9qSt=yzbm3qqJa_cfbhWDhgguBga=_qMz4dcXe2zfz7dcYA@mail.gmail.com>

On Fri, Aug 2, 2019, 4:49 PM Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On my current 32-bit desktop there are 331 installed SBo packages. The
> replacement 64-bit desktop has only 200 installed SBo packages (some of
> which are not on the old desktop).
>
> I've been using sbopkg to update installed packages on the new desktop and
> just installed and read about sbotools and sboui. All three appear to me to
> work with the SBo repo (including the local copy), but not with to-be
> recompiled packages in the /opt/slackbuilds/ directory tree copied to the
> new host.
>
> When packages are upgraded using sbopkg they do not update the build script
> or source tarball in /opt/slackbuilds/. I ask for suggestions on the most
> efficient way to go through the package directories here, download the
> current tarballs and build scripts, and build those that are not yet
> installed on the new desktop.
>
> Resolving dependencies (which sbotools appears to do) would be _really_
> helpful if it would work on what's in the local directories (not the SBo
> synchronized tree).
>

What is in /opt/slackbuilds/ as that is not a default directory for any
programs I'm aware of?

So, are you just wanting to get a list of all the missing packages on the
64bit host compared to the 32bit host and then build them on the 64bit host?

If so, what I've done in the past is get a list of all those programs, add
them into the requires line in a .info, run sqg against that program, then
built everything with sbopkg. When I switched to 14.2, I actually ended up
doing a similar thing, but with slackrepo. I would just put on the command
line all three programs I wanted to install and it figured out all the
dependencies and build order.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190803/5ae679ef/attachment-0001.htm>

From rshepard at appl-ecosys.com  Sat Aug  3 22:05:11 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 3 Aug 2019 15:05:11 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>

On Sat, 3 Aug 2019, Chris Abela wrote:

> I confess that I have not understood your query well but I will attempt to
> reply.

Chris,

I'll try to be more clear.

> Sbopkg has an included script to write queue files for selected
> applications and it can also resolve dependencies via the queue files.

When I run sbopkg I first sync to the SBo repository, then check for updates
to packages already installed. Those are saved to the queue for processing.

Am I correct in understanding that after syncing to the SBo repo I can next
select the Queue menu option and get a list of all packages? If so, then I
can select those not yet installed and process them.

Thanks,

Rich


From rshepard at appl-ecosys.com  Sat Aug  3 22:10:37 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 3 Aug 2019 15:10:37 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <CANi9qSt=yzbm3qqJa_cfbhWDhgguBga=_qMz4dcXe2zfz7dcYA@mail.gmail.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CANi9qSt=yzbm3qqJa_cfbhWDhgguBga=_qMz4dcXe2zfz7dcYA@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1908031505270.12955@salmo.appl-ecosys.com>

On Sat, 3 Aug 2019, Jeremy Hansen wrote:

> What is in /opt/slackbuilds/ as that is not a default directory for any
> programs I'm aware of?

Jeremy,

/opt/slackbuilds/ and its subdirectories hold the SBo packages I've manually
installed. Not using sbopkg, but downloading the package subdirectory
tarball and the executable.

> So, are you just wanting to get a list of all the missing packages on the
> 64bit host compared to the 32bit host and then build them on the 64bit host?

I created such a list and, yes, I want to build those missing packages on
the 64-bit host.

> If so, what I've done in the past is get a list of all those programs, add
> them into the requires line in a .info, run sqg against that program, then
> built everything with sbopkg. When I switched to 14.2, I actually ended up
> doing a similar thing, but with slackrepo. I would just put on the command
> line all three programs I wanted to install and it figured out all the
> dependencies and build order.

I've not before known of sqg and will look for it. I can list the packages
that are in the list of those installed on the 32-bit host but not on the
64-bit host, and learn how to use the requires line in an .info file.

Will look at doing this; may have more questions.

Thanks very much,

Rich

From kristofru at gmail.com  Sun Aug  4 01:34:18 2019
From: kristofru at gmail.com (Chris Abela)
Date: Sun, 4 Aug 2019 03:34:18 +0200
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
Message-ID: <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>

Try

sbopkg -R -k -i "queue1.sqf queue2.sqf ...."


On Sun, 4 Aug 2019, 00:05 Rich Shepard, <rshepard at appl-ecosys.com> wrote:

> On Sat, 3 Aug 2019, Chris Abela wrote:
>
> > I confess that I have not understood your query well but I will attempt
> to
> > reply.
>
> Chris,
>
> I'll try to be more clear.
>
> > Sbopkg has an included script to write queue files for selected
> > applications and it can also resolve dependencies via the queue files.
>
> When I run sbopkg I first sync to the SBo repository, then check for
> updates
> to packages already installed. Those are saved to the queue for processing.
>
> Am I correct in understanding that after syncing to the SBo repo I can next
> select the Queue menu option and get a list of all packages? If so, then I
> can select those not yet installed and process them.
>
> Thanks,
>
> Rich
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190804/00efe1b6/attachment.htm>

From slackalaxy at gmail.com  Sun Aug  4 19:08:55 2019
From: slackalaxy at gmail.com (Petar Petrov)
Date: Sun, 4 Aug 2019 22:08:55 +0300
Subject: [Slackbuilds-users] anyone wants clamtk?
Message-ID: <CAKXpWBeyD48DQh3OvmAncLH+etET4WvrsfH5U+Mc5n7i5AA-nA@mail.gmail.com>

hi All!

Is anyone interested to take ClamTK?

http://slackbuilds.org/repository/14.2/system/clamtk/

bye

Petar

From jdashiel at panix.com  Mon Aug  5 14:16:02 2019
From: jdashiel at panix.com (Jude DaShiell)
Date: Mon, 5 Aug 2019 10:16:02 -0400
Subject: [Slackbuilds-users] bas package updates
Message-ID: <alpine.NEB.2.21.1908051011510.8158@panix1.panix.com>

bas-2.4 got updated to bas-2.5 on its home page and when I discovered
that, I also updated line 8 in bas.SlackBuild to have version 2.5 on it
rather than version 2.4.  The good news so far as I can tell is these were
the only updates necessary to get this package update to build.



--


From rshepard at appl-ecosys.com  Mon Aug  5 17:42:21 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Mon, 5 Aug 2019 10:42:21 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <CANi9qSt=yzbm3qqJa_cfbhWDhgguBga=_qMz4dcXe2zfz7dcYA@mail.gmail.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CANi9qSt=yzbm3qqJa_cfbhWDhgguBga=_qMz4dcXe2zfz7dcYA@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1908051041020.1601@salmo.appl-ecosys.com>

On Sat, 3 Aug 2019, Jeremy Hansen wrote:

> If so, what I've done in the past is get a list of all those programs, add
> them into the requires line in a .info, run sqg against that program, ...

Jeremy,

What's 'sqg?' My web search for 'sqg software' turned up nothing relevant.

Thanks,

Rich

From dave at slackbuilds.org  Mon Aug  5 18:26:36 2019
From: dave at slackbuilds.org (Dave Woodfall)
Date: Mon, 5 Aug 2019 19:26:36 +0100
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <alpine.LNX.2.20.1908051041020.1601@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CANi9qSt=yzbm3qqJa_cfbhWDhgguBga=_qMz4dcXe2zfz7dcYA@mail.gmail.com>
 <alpine.LNX.2.20.1908051041020.1601@salmo.appl-ecosys.com>
Message-ID: <20190805182012.GA10385@blackholeuniverse.ru>

On Mon 5 Aug 2019 10:42,
Rich Shepard <rshepard at appl-ecosys.com> put forth the proposition:
> On Sat, 3 Aug 2019, Jeremy Hansen wrote:
>
> > If so, what I've done in the past is get a list of all those programs, add
> > them into the requires line in a .info, run sqg against that program, ...
>
> Jeremy,
>
> What's 'sqg?' My web search for 'sqg software' turned up nothing relevant.

sqg is the queue file creator that is part of sbopkg:

sqg -p <package>

will make a queue for <package> in /var/lib/sbopkg/queues, which you
can then install using sbopkg -i or load in the 'queue' menu in the
GUI.

-Dave

--

Those who make peaceful revolution impossible will make violent
revolution inevitable.
    -- John F. Kennedy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190805/2260b4cc/attachment.asc>

From z.coldplayer at gmail.com  Mon Aug  5 18:42:22 2019
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Mon, 5 Aug 2019 22:42:22 +0400
Subject: [Slackbuilds-users] Suggestions for SlackBuild Usage Howto
In-Reply-To: <429c1db6-4712-753f-6ff4-7d642114f046@malbolge.net>
References: <d45a0e5b-2d9a-80bc-eab9-d87749ff2623@malbolge.net>
 <CAEWL1_-w_EBSSJu2D4FZKOD84i_+90NBY9BX9t6_pxmqsPh==A@mail.gmail.com>
 <429c1db6-4712-753f-6ff4-7d642114f046@malbolge.net>
Message-ID: <CAEWL1_8v2AQ4CeH7_TxU-Rf18MZvpNC8+HaQqfTNiP5jmMmL8Q@mail.gmail.com>

Hi,

unfortunately, there is no public source code of the how-to similar to the
slacbuilds repo


https://gitlab.com/SlackBuilds.org/slackbuilds



cheers Pritvi

On Sat, 3 Aug 2019 at 01:37, Michael Siegel <msi at malbolge.net> wrote:

>
> Am 28.07.19 um 21:52 schrieb Jheengut Pritvi:
> > Hi,
> >
> > Great initiative.
> >
> > Keep up the good work.
>
> Thanks for the kind words.
>
> The problem is that keeping up that good work doesn't really make any
> sense if no one with write access to that page agrees to merge it. So,
> I'm just gonna wait.
>
>
> Michael
>
> > On Sun, 21 Jul 2019 at 20:19, Michael Siegel <msi at malbolge.net> wrote:
> >
> >> Hello,
> >>
> >> I have some suggestions for improving the SlackBuild Usage HOWTO at
> >> http://slackbuilds.org/howto/.
> >>
> >> The first section (?Caveat?) currently reads like this:
> >>
> >>   All of our scripts are written and tested for usage on the latest
> >>   stable release of Slackware with full installation and updated with
> >>   latest patches; if you're trying them on older versions of Slackware,
> >>   you should read this page referenced in our FAQ.
> >>
> >> My suggestion is to change that to:
> >>
> >>   All of our scripts are written and tested for usage on a full
> >>   installation of the latest stable release of Slackware updated with
> >>   the latest patches. If you're trying them on older versions of
> >>   Slackware, you should read this page referenced in our FAQ.
> >>
> >> Then, the Howto does not mention verification of the downloaded source
> >> packages. I think this should either be added to step one or be
> >> step two. It could be worded like this:
> >>
> >>   To verify the downloaded source's integrity, first run `md5sum
> >>   chemtool-1.6.14.tar.gz' to get the MD5 sum of the downloaded source
> >>   archive. Then compare it to the MD5 sum shown in the `chemtool.info'
> >>   file. If they don't match, something is wrong.
> >>
> >> I just realized that Step 1 already doesn't mention verifying the
> >> SlackBuild's GPG signature. I think that should be included in the Howto
> >> as well.
> >>
> >> So, maybe, it would be best to split Step 1 up like this:
> >>
> >>   * Step 1 ? Download and verify the SlackBuild archive
> >>   * Step 2 ? Download and verify the application's source archive
> >>
> >> What do you think?
> >>
> >>
> >> Best
> >> Michael
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190805/84fa37cb/attachment-0001.htm>

From rshepard at appl-ecosys.com  Mon Aug  5 20:11:48 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Mon, 5 Aug 2019 13:11:48 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <20190805182012.GA10385@blackholeuniverse.ru>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CANi9qSt=yzbm3qqJa_cfbhWDhgguBga=_qMz4dcXe2zfz7dcYA@mail.gmail.com>
 <alpine.LNX.2.20.1908051041020.1601@salmo.appl-ecosys.com>
 <20190805182012.GA10385@blackholeuniverse.ru>
Message-ID: <alpine.LNX.2.20.1908051309580.1601@salmo.appl-ecosys.com>

On Mon, 5 Aug 2019, Dave Woodfall wrote:

> sqg is the queue file creator that is part of sbopkg:
>
> sqg -p <package>
>
> will make a queue for <package> in /var/lib/sbopkg/queues, which you
> can then install using sbopkg -i or load in the 'queue' menu in the
> GUI.

Dave,

Thank you. I've started to read the sbopkg man page, but diverted to make a
list of the packages needing to be installed. I'll finish that list and
reading the man page before asking more questions about it.

Regards,

Rich

From rshepard at appl-ecosys.com  Mon Aug  5 21:32:22 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Mon, 5 Aug 2019 14:32:22 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>

On Sun, 4 Aug 2019, Chris Abela wrote:

> Try
> sbopkg -R -k -i "queue1.sqf queue2.sqf ...."

Thanks, Chris.

After reading the sbopkg man page and the README-queuefiles I have a
few questions remaining.

The pending queue file has 195 packages. Should I separate these by repo
category into separate .sqf files?

Does the sequence of packages in [a|the] queue file matter?

The dependency chains, particularly with libraries, can be several levels.
Will sbopkg resolve these dependencies or do I need to manually sequence the
packages in each .sqf file so requirements are built/installed before the
dependent package?

Might it be worth the time to check each package in the SBo repo to
determine whether options should be appended to the package name in the
queue file? Or, should I have them built with defaults and wait for
something to not run?

Regards,

Rich

From jebrhansen+SBo at gmail.com  Mon Aug  5 21:49:10 2019
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 5 Aug 2019 15:49:10 -0600
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
 <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
Message-ID: <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>

On Mon, Aug 5, 2019, 3:32 PM Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Sun, 4 Aug 2019, Chris Abela wrote:
>
> > Try
> > sbopkg -R -k -i "queue1.sqf queue2.sqf ...."
>
> Thanks, Chris.
>
> After reading the sbopkg man page and the README-queuefiles I have a
> few questions remaining.
>
> The pending queue file has 195 packages. Should I separate these by repo
> category into separate .sqf files?
>

I wouldn't. One file will make it easier.

Does the sequence of packages in [a|the] queue file matter?
>

Yes! This is the order sbopkg will build them in, so they need to be in the
right build order. sqg generates queue files based on the needed build
order for the SlackBuilds.

The dependency chains, particularly with libraries, can be several levels.
> Will sbopkg resolve these dependencies or do I need to manually sequence
> the
> packages in each .sqf file so requirements are built/installed before the
> dependent package?
>

sbopkg does not resolve any dependencies. It relies on the build order
listed in the queue files, which sqg should generate correctly.


> Might it be worth the time to check each package in the SBo repo to
> determine whether options should be appended to the package name in the
> queue file? Or, should I have them built with defaults and wait for
> something to not run?
>

I've always found it worthwhile, but it can be a lot of work to dig through
all of that.

Jeremy

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

From rshepard at appl-ecosys.com  Tue Aug  6 00:09:54 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Mon, 5 Aug 2019 17:09:54 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
 <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
 <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1908051707270.1601@salmo.appl-ecosys.com>

On Mon, 5 Aug 2019, Jeremy Hansen wrote:

>> The pending queue file has 195 packages. Should I separate these by repo
>> category into separate .sqf files?

> I wouldn't. One file will make it easier.

Jeremy,

Okay. I'll leave them all in one file.

> Does the sequence of packages in [a|the] queue file matter?
>
> Yes! This is the order sbopkg will build them in, so they need to be in
> the right build order. sqg generates queue files based on the needed build
> order for the SlackBuilds.

I thought so yet hoped for a command line option that would make life
simpler. :-)

> sbopkg does not resolve any dependencies. It relies on the build order
> listed in the queue files, which sqg should generate correctly.

As above, worth asking anyway.

> I've always found it worthwhile, but it can be a lot of work to dig
> through all of that.

Yep. I'll go through the list, find dependencies and options, and
re-organize the package sequence.

Thanks very much,

Rich

From andrew.david.strong at gmail.com  Tue Aug  6 00:34:09 2019
From: andrew.david.strong at gmail.com (andrew)
Date: Tue, 6 Aug 2019 10:34:09 +1000
Subject: [Slackbuilds-users] For grabs: gimp-plugin-export-layers
Message-ID: <20190806003409.GA5211@ilium.andrews-corner.org>

Hi,

Would anybody like to take over gimp-plugin-export-layers? It is here:

https://slackbuilds.org/repository/14.2/graphics/gimp-plugin-export-layers/

It is long overdue for a version bump and a script cleanup and I would
like to concentrate on some of my other projects...

Andrew

-- 
You think that's air you're breathing now?

From jebrhansen+SBo at gmail.com  Tue Aug  6 00:36:05 2019
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 5 Aug 2019 18:36:05 -0600
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <alpine.LNX.2.20.1908051707270.1601@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
 <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
 <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>
 <alpine.LNX.2.20.1908051707270.1601@salmo.appl-ecosys.com>
Message-ID: <CANi9qSupahvjgb_vY3NU9-V7sbpFdPNACvZ5DroHYT5agA-RFA@mail.gmail.com>

On Mon, Aug 5, 2019, 6:10 PM Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Mon, 5 Aug 2019, Jeremy Hansen wrote:
>
> >> The pending queue file has 195 packages. Should I separate these by repo
> >> category into separate .sqf files?
>
> > I wouldn't. One file will make it easier.
>
> Jeremy,
>
> Okay. I'll leave them all in one file.
>
> > Does the sequence of packages in [a|the] queue file matter?
> >
> > Yes! This is the order sbopkg will build them in, so they need to be in
> > the right build order. sqg generates queue files based on the needed
> build
> > order for the SlackBuilds.
>
> I thought so yet hoped for a command line option that would make life
> simpler. :-)
>

This actually reminded me of a request I made for sqg almost 4 years ago
that Willy implemented 2 years ago. You should be able to run sqg with the
programs you you want with a -o after it and it will write a
/var/lib/sbopkg/queues/custom.sqf file

sqg -p "krusader filezilla mediainfo" -o

You could use this to have sqg create a custom.sqf file, which you should
then be able to run sbopkg -i custom and then tell it to do the queuefile.

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

From rshepard at appl-ecosys.com  Tue Aug  6 14:33:12 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Aug 2019 07:33:12 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <CANi9qSupahvjgb_vY3NU9-V7sbpFdPNACvZ5DroHYT5agA-RFA@mail.gmail.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
 <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
 <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>
 <alpine.LNX.2.20.1908051707270.1601@salmo.appl-ecosys.com>
 <CANi9qSupahvjgb_vY3NU9-V7sbpFdPNACvZ5DroHYT5agA-RFA@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1908060730380.18423@salmo.appl-ecosys.com>

On Mon, 5 Aug 2019, Jeremy Hansen wrote:

> This actually reminded me of a request I made for sqg almost 4 years ago
> that Willy implemented 2 years ago. You should be able to run sqg with the
> programs you you want with a -o after it and it will write a
> /var/lib/sbopkg/queues/custom.sqf file
>
> sqg -p "krusader filezilla mediainfo" -o
>
> You could use this to have sqg create a custom.sqf file, which you should
> then be able to run sbopkg -i custom and then tell it to do the queuefile.

Jeremy,

I'll keep this for reference.

Reading the hoorex man page I think that running it with the -m (multilevel)
option is a good first step. I'll also try the -s and -r options to gain
insight into the information each returns.

Thanks again.

Best regards,

Rich

From root at slackjeff.com.br  Mon Aug  5 22:24:14 2019
From: root at slackjeff.com.br (Jefferson Rocha)
Date: Mon, 05 Aug 2019 19:24:14 -0300
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 160, Issue 2
In-Reply-To: <mailman.669.1565030558.24174.slackbuilds-users@slackbuilds.org>
References: <mailman.669.1565030558.24174.slackbuilds-users@slackbuilds.org>
Message-ID: <e51ddba278f9bf90a618e07739543245@slackjeff.com.br>

 CLAMTK? (PETAR PETROV) 

I'm interested!

---

SOCIAL 

https://slackjeff.com.br/ 

https://youtube.com/slackjeff 

https://github.com/slackjeff 

https://www.vivaolinux.com.br/~slackjeff  

Em 05/08/2019 15:42, slackbuilds-users-request at slackbuilds.org escreveu:

> Send SlackBuilds-users mailing list submissions to
> slackbuilds-users at slackbuilds.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> or, via email, send a message with subject or body 'help' to
> slackbuilds-users-request at slackbuilds.org
> 
> You can reach the person managing the list at
> slackbuilds-users-owner at slackbuilds.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SlackBuilds-users digest..."
> 
> Today's Topics:
> 
> 1. Re: Rebuilding packages on new host (Rich Shepard)
> 2. Re: Rebuilding packages on new host (Rich Shepard)
> 3. Re: Rebuilding packages on new host (Chris Abela)
> 4. anyone wants clamtk? (Petar Petrov)
> 5. bas package updates (Jude DaShiell)
> 6. Re: Rebuilding packages on new host (Rich Shepard)
> 7. Re: Rebuilding packages on new host (Dave Woodfall)
> 8. Re: Suggestions for SlackBuild Usage Howto (Jheengut Pritvi)
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 3 Aug 2019 15:05:11 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] Rebuilding packages on new host
> Message-ID:
> <alpine.LNX.2.20.1908031500430.12955 at salmo.appl-ecosys.com>
> Content-Type: text/plain; format=flowed; charset=US-ASCII
> 
> On Sat, 3 Aug 2019, Chris Abela wrote:
> 
>> I confess that I have not understood your query well but I will attempt to
>> reply.
> 
> Chris,
> 
> I'll try to be more clear.
> 
>> Sbopkg has an included script to write queue files for selected
>> applications and it can also resolve dependencies via the queue files.
> 
> When I run sbopkg I first sync to the SBo repository, then check for updates
> to packages already installed. Those are saved to the queue for processing.
> 
> Am I correct in understanding that after syncing to the SBo repo I can next
> select the Queue menu option and get a list of all packages? If so, then I
> can select those not yet installed and process them.
> 
> Thanks,
> 
> Rich
> 
> ------------------------------
> 
> Message: 2
> Date: Sat, 3 Aug 2019 15:10:37 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> To: slackbuilds-users <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] Rebuilding packages on new host
> Message-ID:
> <alpine.LNX.2.20.1908031505270.12955 at salmo.appl-ecosys.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
> 
> On Sat, 3 Aug 2019, Jeremy Hansen wrote:
> 
>> What is in /opt/slackbuilds/ as that is not a default directory for any
>> programs I'm aware of?
> 
> Jeremy,
> 
> /opt/slackbuilds/ and its subdirectories hold the SBo packages I've manually
> installed. Not using sbopkg, but downloading the package subdirectory
> tarball and the executable.
> 
>> So, are you just wanting to get a list of all the missing packages on the
>> 64bit host compared to the 32bit host and then build them on the 64bit host?
> 
> I created such a list and, yes, I want to build those missing packages on
> the 64-bit host.
> 
>> If so, what I've done in the past is get a list of all those programs, add
>> them into the requires line in a .info, run sqg against that program, then
>> built everything with sbopkg. When I switched to 14.2, I actually ended up
>> doing a similar thing, but with slackrepo. I would just put on the command
>> line all three programs I wanted to install and it figured out all the
>> dependencies and build order.
> 
> I've not before known of sqg and will look for it. I can list the packages
> that are in the list of those installed on the 32-bit host but not on the
> 64-bit host, and learn how to use the requires line in an .info file.
> 
> Will look at doing this; may have more questions.
> 
> Thanks very much,
> 
> Rich
> 
> ------------------------------
> 
> Message: 3
> Date: Sun, 4 Aug 2019 03:34:18 +0200
> From: Chris Abela <kristofru at gmail.com>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] Rebuilding packages on new host
> Message-ID:
> <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Try
> 
> sbopkg -R -k -i "queue1.sqf queue2.sqf ...."
> 
> On Sun, 4 Aug 2019, 00:05 Rich Shepard, <rshepard at appl-ecosys.com> wrote:
> 
> On Sat, 3 Aug 2019, Chris Abela wrote:
> 
> I confess that I have not understood your query well but I will attempt to reply. 
> Chris,
> 
> I'll try to be more clear.
> 
> Sbopkg has an included script to write queue files for selected
> applications and it can also resolve dependencies via the queue files. 
> When I run sbopkg I first sync to the SBo repository, then check for
> updates
> to packages already installed. Those are saved to the queue for processing.
> 
> Am I correct in understanding that after syncing to the SBo repo I can next
> select the Queue menu option and get a list of all packages? If so, then I
> can select those not yet installed and process them.
> 
> Thanks,
> 
> Rich
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
 -------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190804/00efe1b6/attachment-0001.htm>

------------------------------

Message: 4
Date: Sun, 4 Aug 2019 22:08:55 +0300
From: Petar Petrov <slackalaxy at gmail.com>
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: [Slackbuilds-users] anyone wants clamtk?
Message-ID:
    <CAKXpWBeyD48DQh3OvmAncLH+etET4WvrsfH5U+Mc5n7i5AA-nA at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

hi All!

Is anyone interested to take ClamTK?

http://slackbuilds.org/repository/14.2/system/clamtk/

bye

Petar

------------------------------

Message: 5
Date: Mon, 5 Aug 2019 10:16:02 -0400
From: Jude DaShiell <jdashiel at panix.com>
To: slackbuilds-users at slackbuilds.org
Subject: [Slackbuilds-users] bas package updates
Message-ID: <alpine.NEB.2.21.1908051011510.8158 at panix1.panix.com>
Content-Type: text/plain; charset=US-ASCII

bas-2.4 got updated to bas-2.5 on its home page and when I discovered
that, I also updated line 8 in bas.SlackBuild to have version 2.5 on it
rather than version 2.4.  The good news so far as I can tell is these
were
the only updates necessary to get this package update to build.

--

------------------------------

Message: 6
Date: Mon, 5 Aug 2019 10:42:21 -0700 (PDT)
From: Rich Shepard <rshepard at appl-ecosys.com>
To: slackbuilds-users <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] Rebuilding packages on new host
Message-ID: <alpine.LNX.2.20.1908051041020.1601 at salmo.appl-ecosys.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed

On Sat, 3 Aug 2019, Jeremy Hansen wrote:

> If so, what I've done in the past is get a list of all those programs, add
> them into the requires line in a .info, run sqg against that program, ...

Jeremy,

What's 'sqg?' My web search for 'sqg software' turned up nothing
relevant.

Thanks,

Rich

------------------------------

Message: 7
Date: Mon, 5 Aug 2019 19:26:36 +0100
From: Dave Woodfall <dave at slackbuilds.org>
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] Rebuilding packages on new host
Message-ID: <20190805182012.GA10385 at blackholeuniverse.ru>
Content-Type: text/plain; charset="utf-8"

On Mon 5 Aug 2019 10:42,
Rich Shepard <rshepard at appl-ecosys.com> put forth the proposition: 

> On Sat, 3 Aug 2019, Jeremy Hansen wrote:
> 
>> If so, what I've done in the past is get a list of all those programs, add
>> them into the requires line in a .info, run sqg against that program, ...
> 
> Jeremy,
> 
> What's 'sqg?' My web search for 'sqg software' turned up nothing relevant.

sqg is the queue file creator that is part of sbopkg:

sqg -p <package>

will make a queue for <package> in /var/lib/sbopkg/queues, which you
can then install using sbopkg -i or load in the 'queue' menu in the
GUI.

-Dave

--

Those who make peaceful revolution impossible will make violent
revolution inevitable.
    -- John F. Kennedy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL:
<http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190805/2260b4cc/attachment-0001.asc>

------------------------------

Message: 8
Date: Mon, 5 Aug 2019 22:42:22 +0400
From: Jheengut Pritvi <z.coldplayer at gmail.com>
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] Suggestions for SlackBuild Usage
    Howto
Message-ID:
    <CAEWL1_8v2AQ4CeH7_TxU-Rf18MZvpNC8+HaQqfTNiP5jmMmL8Q at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

unfortunately, there is no public source code of the how-to similar to
the
slacbuilds repo

https://gitlab.com/SlackBuilds.org/slackbuilds

cheers Pritvi

On Sat, 3 Aug 2019 at 01:37, Michael Siegel <msi at malbolge.net> wrote:

> Am 28.07.19 um 21:52 schrieb Jheengut Pritvi: 
> 
>> Hi,
>> 
>> Great initiative.
>> 
>> Keep up the good work.
> 
> Thanks for the kind words.
> 
> The problem is that keeping up that good work doesn't really make any
> sense if no one with write access to that page agrees to merge it. So,
> I'm just gonna wait.
> 
> Michael
> 
> On Sun, 21 Jul 2019 at 20:19, Michael Siegel <msi at malbolge.net> wrote:
> 
> Hello,
> 
> I have some suggestions for improving the SlackBuild Usage HOWTO at
> http://slackbuilds.org/howto/.
> 
> The first section (?Caveat?) currently reads like this:
> 
> All of our scripts are written and tested for usage on the latest
> stable release of Slackware with full installation and updated with
> latest patches; if you're trying them on older versions of Slackware,
> you should read this page referenced in our FAQ.
> 
> My suggestion is to change that to:
> 
> All of our scripts are written and tested for usage on a full
> installation of the latest stable release of Slackware updated with
> the latest patches. If you're trying them on older versions of
> Slackware, you should read this page referenced in our FAQ.
> 
> Then, the Howto does not mention verification of the downloaded source
> packages. I think this should either be added to step one or be
> step two. It could be worded like this:
> 
> To verify the downloaded source's integrity, first run `md5sum
> chemtool-1.6.14.tar.gz' to get the MD5 sum of the downloaded source
> archive. Then compare it to the MD5 sum shown in the `chemtool.info'
> file. If they don't match, something is wrong.
> 
> I just realized that Step 1 already doesn't mention verifying the
> SlackBuild's GPG signature. I think that should be included in the Howto
> as well.
> 
> So, maybe, it would be best to split Step 1 up like this:
> 
> * Step 1 ? Download and verify the SlackBuild archive
> * Step 2 ? Download and verify the application's source archive
> 
> What do you think?
> 
> Best
> Michael
 _______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

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

------------------------------

Subject: Digest Footer

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users

------------------------------

End of SlackBuilds-users Digest, Vol 160, Issue 2
*************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190805/0933fd1e/attachment-0001.htm>

From slackalaxy at gmail.com  Tue Aug  6 20:45:09 2019
From: slackalaxy at gmail.com (Petar Petrov)
Date: Tue, 6 Aug 2019 23:45:09 +0300
Subject: [Slackbuilds-users] ClamTK
Message-ID: <CAKXpWBfkP5C4XzS+gPjXcfD3BuP0UoouzHWbco5T3A0OZUMSXQ@mail.gmail.com>

ok, great! Please, take over. I got some tips from Karl G. Hammarlund
(thanks!), which I will paste for you:

1) clamtk have switched from gtk2 to gtk3. This means that perl-gtk2
is no longer a dependency, but perl-Gtk3 is (which in turn is
dependent on perl-Glib-Object-Introspection and perl-Cairo-GObject).
There are SBo scripts for these, so it's easy to build and install
them.

2) New URL to source file:
https://bitbucket.org/davem_/clamtk-gtk3/downloads/clamtk-6.01.tar.xz

bye

Petar


On 06/08/2019, Jefferson Rocha <root at slackjeff.com.br> wrote:
>  CLAMTK? (PETAR PETROV)
>
> I'm interested!
>
> ---
>
> SOCIAL
>
> https://slackjeff.com.br/
>
> https://youtube.com/slackjeff
>
> https://github.com/slackjeff
>
> https://www.vivaolinux.com.br/~slackjeff
>

From chris.willing at linux.com  Tue Aug  6 21:53:09 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Wed, 7 Aug 2019 07:53:09 +1000
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <alpine.LNX.2.20.1908060730380.18423@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
 <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
 <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>
 <alpine.LNX.2.20.1908051707270.1601@salmo.appl-ecosys.com>
 <CANi9qSupahvjgb_vY3NU9-V7sbpFdPNACvZ5DroHYT5agA-RFA@mail.gmail.com>
 <alpine.LNX.2.20.1908060730380.18423@salmo.appl-ecosys.com>
Message-ID: <1b84ddf5-dd2a-98f2-e4ac-d1d0cabe70db@linux.com>

On 7/8/19 12:33 am, Rich Shepard wrote:
[]
> 
> Reading the hoorex man page I think that running it with the -m
> (multilevel)
> option is a good first step. I'll also try the -s and -r options to gain
> insight into the information each returns.
> 

Please be aware that the -r option gives a list of packages required by
the target(s). I think that is the mode you want for your particular
need at the moment - something like:
   hoorex -rl1 target1 target2 target3 ...

Without the -r option, hoorex tells what packages depend on the target
i.e. the reverse of the other mode.

chris

From rshepard at appl-ecosys.com  Tue Aug  6 22:07:49 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Aug 2019 15:07:49 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <1b84ddf5-dd2a-98f2-e4ac-d1d0cabe70db@linux.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
 <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
 <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>
 <alpine.LNX.2.20.1908051707270.1601@salmo.appl-ecosys.com>
 <CANi9qSupahvjgb_vY3NU9-V7sbpFdPNACvZ5DroHYT5agA-RFA@mail.gmail.com>
 <alpine.LNX.2.20.1908060730380.18423@salmo.appl-ecosys.com>
 <1b84ddf5-dd2a-98f2-e4ac-d1d0cabe70db@linux.com>
Message-ID: <alpine.LNX.2.20.1908061503380.18423@salmo.appl-ecosys.com>

On Wed, 7 Aug 2019, Christoph Willing wrote:

> Please be aware that the -r option gives a list of packages required by
> the target(s). I think that is the mode you want for your particular need
> at the moment - something like:
>   hoorex -rl1 target1 target2 target3 ...
>
> Without the -r option, hoorex tells what packages depend on the target
> i.e. the reverse of the other mode.

Chris,

Very true. It took me a few readings of the man page and trying various
options to fully understand hoorex.

Using hoorex without any other options shows me what packages depend on the
target mentioned on the command line. If one of those packages is higher up
the list from the target I move it to preceed the package depending on it.
This appears to be working for me. If sbopkg chokes somewhere processing the
queue list I'll fix those instances as necessary.

I'm learning a lot from all of you and appreciate your comments.

Best regards,

Rich

From milgram at cgpp.com  Wed Aug  7 12:07:34 2019
From: milgram at cgpp.com (Judah Milgram)
Date: Wed, 7 Aug 2019 08:07:34 -0400
Subject: [Slackbuilds-users] webkitgtk & webkit2gtk
Message-ID: <0f7043a9-124b-64bd-5d8d-e0f8bc7977ab@cgpp.com>


Hello,

Is webkit2gtk a replacement for webkitgtk, or can I have both installed? 
(To be clear, these are the SBo script names.)

I'm guessing the latter but was uncertain because there seems only to be 
a minor version number change (2.4.11 to 2.20.5) in the webkitgtk source 
tarballs.

thanks!
Judah


-- 
Judah Milgram
milgram at cgpp.com
301-257-7069

From matteo.bernardini at gmail.com  Wed Aug  7 18:50:06 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 7 Aug 2019 20:50:06 +0200
Subject: [Slackbuilds-users] webkitgtk & webkit2gtk
In-Reply-To: <0f7043a9-124b-64bd-5d8d-e0f8bc7977ab@cgpp.com>
References: <0f7043a9-124b-64bd-5d8d-e0f8bc7977ab@cgpp.com>
Message-ID: <CAPsDuS7ua4D7kPwhS-0Luh8JDJt8Rj2Nn4Uv4XZ-1Spx708z_A@mail.gmail.com>

Il giorno mer 7 ago 2019 alle ore 14:10 Judah Milgram
<milgram at cgpp.com> ha scritto:
>
>
> Hello,
>
> Is webkit2gtk a replacement for webkitgtk, or can I have both installed?
> (To be clear, these are the SBo script names.)
>
> I'm guessing the latter but was uncertain because there seems only to be
> a minor version number change (2.4.11 to 2.20.5) in the webkitgtk source
> tarballs.
>
> thanks!
> Judah

they are two different libraries that you can install at the same time.
also applications depend on one and cannot use the other as a replacement.

From rshepard at appl-ecosys.com  Thu Aug  8 01:21:33 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 7 Aug 2019 18:21:33 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
Message-ID: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>

My thanks to all who taught me how to use sbopkg to install packages from a
locally-generated queue.

One package would not build:

Traceback (most recent call last):
   File "setup.py", line 474, in <module>
     setup_package()
   File "setup.py", line 450, in setup_package
     from numpy.distutils.core import setup
ModuleNotFoundError: No module named 'numpy'

scipy3:
Traceback (most recent call last):
   File "setup.py", line 474, in <module>
     setup_package()
   File "setup.py", line 450, in setup_package
     from numpy.distutils.core import setup
ModuleNotFoundError: No module named 'numpy'

However, both numpy and numpy3 are installed.

The same error showed up when I tried building the package from a fresh
directory and tarball.

Where might I look for the reason scipy3 fails to find numpy3?

Regards,

Rich

From milgram at cgpp.com  Thu Aug  8 01:28:05 2019
From: milgram at cgpp.com (Judah Milgram)
Date: Wed, 7 Aug 2019 21:28:05 -0400
Subject: [Slackbuilds-users] webkitgtk & webkit2gtk
In-Reply-To: <CAPsDuS7ua4D7kPwhS-0Luh8JDJt8Rj2Nn4Uv4XZ-1Spx708z_A@mail.gmail.com>
References: <0f7043a9-124b-64bd-5d8d-e0f8bc7977ab@cgpp.com>
 <CAPsDuS7ua4D7kPwhS-0Luh8JDJt8Rj2Nn4Uv4XZ-1Spx708z_A@mail.gmail.com>
Message-ID: <29f78bab-3bfe-b1c0-576b-9c1b540deb32@cgpp.com>


Thanks! And indeed, I forged ahead and installed it, and everything 
worked out fine.

thanks again
Judah

On 8/7/19 2:50 PM, Matteo Bernardini wrote:
> Il giorno mer 7 ago 2019 alle ore 14:10 Judah Milgram
> <milgram at cgpp.com> ha scritto:
>>
>>
>> Hello,
>>
>> Is webkit2gtk a replacement for webkitgtk, or can I have both installed?
>> (To be clear, these are the SBo script names.)
>>
>> I'm guessing the latter but was uncertain because there seems only to be
>> a minor version number change (2.4.11 to 2.20.5) in the webkitgtk source
>> tarballs.
>>
>> thanks!
>> Judah
> 
> they are two different libraries that you can install at the same time.
> also applications depend on one and cannot use the other as a replacement.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 


-- 
Judah Milgram
milgram at cgpp.com
301-257-7069

From rshepard at appl-ecosys.com  Thu Aug  8 12:45:24 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Aug 2019 05:45:24 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>

On Wed, 7 Aug 2019, Rich Shepard wrote:

> One package would not build:
> scipy3:

Actually, matplotlib also fails to find numpy/numpy3. But, I've found a
work-around so this is no longer an issue for me.

Rich

From alik at ejik.org  Thu Aug  8 14:07:07 2019
From: alik at ejik.org (Alexander Verbovetsky)
Date: Thu, 08 Aug 2019 17:07:07 +0300
Subject: [Slackbuilds-users] 
 =?utf-8?q?scipy3=3A_cannot_find_numpy3_when_?=
 =?utf-8?q?building_=5BRESOLVED=5D?=
In-Reply-To: <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
Message-ID: <d3c1243d-5f2a-4661-a13a-56a30e5a7097@www.fastmail.com>

On Thu, 8 Aug 2019, at 15:45, Rich Shepard wrote:
> 
> > One package would not build:
> > scipy3:
> 
> Actually, matplotlib also fails to find numpy/numpy3. But, I've found
> a work-around so this is no longer an issue for me.

Is this related to having both numpy and numpy3 installed?

I have only numpy3, scipy3 and python3-matplotlib build and work without
problems.

Best regards,
Alexander

From rshepard at appl-ecosys.com  Thu Aug  8 14:59:06 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Aug 2019 07:59:06 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <d3c1243d-5f2a-4661-a13a-56a30e5a7097@www.fastmail.com>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <d3c1243d-5f2a-4661-a13a-56a30e5a7097@www.fastmail.com>
Message-ID: <alpine.LNX.2.20.1908080757490.9087@salmo.appl-ecosys.com>

On Thu, 8 Aug 2019, Alexander Verbovetsky wrote:

> Is this related to having both numpy and numpy3 installed?

Alexander,

I don't know. I need numpy2 for grass while all my new python work is done
with python3.

> I have only numpy3, scipy3 and python3-matplotlib build and work without
> problems.

I'll try removing numpy2 and see if that makes a difference.

Thanks,

Rich

From rshepard at appl-ecosys.com  Thu Aug  8 15:43:55 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Aug 2019 08:43:55 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <alpine.LNX.2.20.1908080757490.9087@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <d3c1243d-5f2a-4661-a13a-56a30e5a7097@www.fastmail.com>
 <alpine.LNX.2.20.1908080757490.9087@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.20.1908080842330.9087@salmo.appl-ecosys.com>

On Thu, 8 Aug 2019, Rich Shepard wrote:

> I don't know. I need numpy2 for grass while all my new python work is done
> with python3.

Well, it turns out that I don't need numpy2 to run grass-7.git.

> I'll try removing numpy2 and see if that makes a difference.

Makes no difference: the build script fails to find numpy3.

Thanks,

Rich

From didier at slint.fr  Thu Aug  8 16:28:34 2019
From: didier at slint.fr (Didier Spaier)
Date: Thu, 8 Aug 2019 18:28:34 +0200
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
Message-ID: <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>

Hello,

On 08/08/2019 14:45, Rich Shepard wrote:
> Actually, matplotlib also fails to find numpy/numpy3. But, I've found a
> work-around so this is no longer an issue for me.

Please tell us what you did as workaround.

This could help others.

Best,

Didier

From rshepard at appl-ecosys.com  Thu Aug  8 17:38:23 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Aug 2019 10:38:23 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>
Message-ID: <alpine.LNX.2.20.1908081036090.9087@salmo.appl-ecosys.com>

On Thu, 8 Aug 2019, Didier Spaier wrote:

> Please tell us what you did as workaround. This could help others.

Didier,

Because this issue seems to be specific to my new desktop and Dell Latitude
E5410 I decided to use pip rather than the SlackBuild scripts.

There were no issues with python2 packages but for reasons still unknown
there are local issues.

Regards,

Rich

From didier at slint.fr  Thu Aug  8 18:54:41 2019
From: didier at slint.fr (Didier Spaier)
Date: Thu, 8 Aug 2019 20:54:41 +0200
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <alpine.LNX.2.20.1908081036090.9087@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>
 <alpine.LNX.2.20.1908081036090.9087@salmo.appl-ecosys.com>
Message-ID: <29ed8587-9638-082d-4739-96236e2ac837@slint.fr>

On 08/08/2019 19:38, Rich Shepard wrote:
> On Thu, 8 Aug 2019, Didier Spaier wrote:
> 
>> Please tell us what you did as workaround. This could help others.
> 
> Didier,
> 
> Because this issue seems to be specific to my new desktop and Dell Latitude
> E5410 I decided to use pip rather than the SlackBuild scripts.

I very much doubt that this be a hardware issue.

> There were no issues with python2 packages but for reasons still unknown
> there are local issues.

Maybe the same reasons that caused the initial issue.

So we didn't learn anything :sigh:

Best,

Didier

From rshepard at appl-ecosys.com  Thu Aug  8 19:16:54 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Aug 2019 12:16:54 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <29ed8587-9638-082d-4739-96236e2ac837@slint.fr>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>
 <alpine.LNX.2.20.1908081036090.9087@salmo.appl-ecosys.com>
 <29ed8587-9638-082d-4739-96236e2ac837@slint.fr>
Message-ID: <alpine.LNX.2.20.1908081215000.9087@salmo.appl-ecosys.com>

On Thu, 8 Aug 2019, Didier Spaier wrote:

> I very much doubt that this be a hardware issue.

Didier,

It makes no sense, but I and others have not been able to explain why these
few problems exist. All 64-bit systems are clean installations of -14.2 and
fully patched.

> Maybe the same reasons that caused the initial issue. So we didn't learn
> anything :sigh:

Yep. It's disappointing.

Best regards,

Rich


From didier at slint.fr  Thu Aug  8 19:47:21 2019
From: didier at slint.fr (Didier Spaier)
Date: Thu, 8 Aug 2019 21:47:21 +0200
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <alpine.LNX.2.20.1908081215000.9087@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>
 <alpine.LNX.2.20.1908081036090.9087@salmo.appl-ecosys.com>
 <29ed8587-9638-082d-4739-96236e2ac837@slint.fr>
 <alpine.LNX.2.20.1908081215000.9087@salmo.appl-ecosys.com>
Message-ID: <1f4a171f-3e30-97c9-e2cd-8d819225e756@slint.fr>

On 08/08/2019 21:16, Rich Shepard wrote:
> It makes no sense, but I and others have not been able to explain why these
> few problems exist.

This doesn't imply that this be a hardware issue.

Please run from the systems in concern as root:
updateb

then provide the full output of this command:
locate numpy.py

Best,

Didier

From didier at slint.fr  Thu Aug  8 19:48:10 2019
From: didier at slint.fr (Didier Spaier)
Date: Thu, 8 Aug 2019 21:48:10 +0200
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <1f4a171f-3e30-97c9-e2cd-8d819225e756@slint.fr>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>
 <alpine.LNX.2.20.1908081036090.9087@salmo.appl-ecosys.com>
 <29ed8587-9638-082d-4739-96236e2ac837@slint.fr>
 <alpine.LNX.2.20.1908081215000.9087@salmo.appl-ecosys.com>
 <1f4a171f-3e30-97c9-e2cd-8d819225e756@slint.fr>
Message-ID: <324f4935-c56f-4758-790f-a3b5c5a3693f@slint.fr>

Erratum:
updatedb, not updateb

On 08/08/2019 21:47, Didier Spaier wrote:
> On 08/08/2019 21:16, Rich Shepard wrote:
>> It makes no sense, but I and others have not been able to explain why these
>> few problems exist.
> 
> This doesn't imply that this be a hardware issue.
> 
> Please run from the systems in concern as root:
> updateb
> 
> then provide the full output of this command:
> locate numpy.py
> 
> Best,
> 
> Didier

From rshepard at appl-ecosys.com  Thu Aug  8 21:06:36 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Aug 2019 14:06:36 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <1f4a171f-3e30-97c9-e2cd-8d819225e756@slint.fr>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>
 <alpine.LNX.2.20.1908081036090.9087@salmo.appl-ecosys.com>
 <29ed8587-9638-082d-4739-96236e2ac837@slint.fr>
 <alpine.LNX.2.20.1908081215000.9087@salmo.appl-ecosys.com>
 <1f4a171f-3e30-97c9-e2cd-8d819225e756@slint.fr>
Message-ID: <alpine.LNX.2.20.1908081401330.9087@salmo.appl-ecosys.com>

On Thu, 8 Aug 2019, Didier Spaier wrote:

> Please run from the systems in concern as root: updateb

Didier,

updatedb runs automatically overnight. The system is not turned off when I
log out.

> then provide the full output of this command:
> locate numpy.py

# locate numpy.py
/usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
/usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
/usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
/usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
/usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
/home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py

But, ...

# find / -name numpy
/usr/lib64/python2.7/site-packages/numpy
/usr/lib64/python2.7/site-packages/pandas/compat/numpy
/usr/lib64/python2.7/site-packages/Cython/Includes/numpy
/usr/lib64/R/library/BH/include/boost/python/numpy
/usr/lib64/python3.7/site-packages/numpy
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy
/var/lib/sbopkg/SBo/14.2/development/numpy
/opt/slackbuilds/Development/numpy

Rich

From duncan_roe at optusnet.com.au  Fri Aug  9 01:22:24 2019
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Fri, 9 Aug 2019 11:22:24 +1000
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <alpine.LNX.2.20.1908081401330.9087@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908071818200.12111@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1908080543540.9087@salmo.appl-ecosys.com>
 <0d6d3413-0866-f378-5c4b-11c624a006f9@slint.fr>
 <alpine.LNX.2.20.1908081036090.9087@salmo.appl-ecosys.com>
 <29ed8587-9638-082d-4739-96236e2ac837@slint.fr>
 <alpine.LNX.2.20.1908081215000.9087@salmo.appl-ecosys.com>
 <1f4a171f-3e30-97c9-e2cd-8d819225e756@slint.fr>
 <alpine.LNX.2.20.1908081401330.9087@salmo.appl-ecosys.com>
Message-ID: <20190809012224.GB13423@dimstar.local.net>

Hey Rich,

On Thu, Aug 08, 2019 at 02:06:36PM -0700, Rich Shepard wrote:
> On Thu, 8 Aug 2019, Didier Spaier wrote:
>
> > Please run from the systems in concern as root: updateb
>
> Didier,
>
> updatedb runs automatically overnight. The system is not turned off when I
> log out.
>
> > then provide the full output of this command:
> > locate numpy.py
>
> # locate numpy.py
> /usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
> /home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py
>
> But, ...
>
> # find / -name numpy
> /usr/lib64/python2.7/site-packages/numpy
> /usr/lib64/python2.7/site-packages/pandas/compat/numpy
> /usr/lib64/python2.7/site-packages/Cython/Includes/numpy
> /usr/lib64/R/library/BH/include/boost/python/numpy
> /usr/lib64/python3.7/site-packages/numpy
> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy
> /var/lib/sbopkg/SBo/14.2/development/numpy
> /opt/slackbuilds/Development/numpy

These are all directories. If you try again with "-tye f" you won't see them.
(Quick check: find /usr/lib64 -type f -name numpy).
>
> Rich
> _______________________________________________
I tried this:

09:12:16# find /usr/lib64 /usr/src/slackbuilds -type f -name '*numpy*'
/usr/lib64/python3.7/site-packages/numpy/core/__pycache__/generate_numpy_api.cpython-37.pyc
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy/numpyconfig.h
/usr/lib64/python3.7/site-packages/numpy/core/generate_numpy_api.py
/usr/lib64/python3.7/site-packages/numpy/distutils/__pycache__/numpy_distribution.cpython-37.pyc
/usr/lib64/python3.7/site-packages/numpy/distutils/numpy_distribution.py
/usr/lib64/python3.7/site-packages/numpy/tests/test_numpy_version.py
/usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.pyc
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/numpyconfig.h
/usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.py
/usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.pyc
/usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.py
/usr/lib64/python2.7/site-packages/numpy/tests/test_numpy_version.py
/usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.py
/usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.pyc
/usr/lib64/python2.7/site-packages/vtk/util/numpy_support.py
/usr/lib64/python2.7/site-packages/vtk/util/numpy_support.pyc
/usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.py
/usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.pyc
/usr/src/slackbuilds/python/numpydoc/numpydoc.SlackBuild
/usr/src/slackbuilds/python/numpydoc/numpydoc.info
/usr/src/slackbuilds/development/numpy3/numpy3.SlackBuild
/usr/src/slackbuilds/development/numpy3/numpy3.info
/usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.info
/usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.SlackBuild
/usr/src/slackbuilds/development/numpy/numpy.info
/usr/src/slackbuilds/development/numpy/numpy.SlackBuild
/usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.info
/usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.SlackBuild

Here's the rub: I *do* have numpy3 installed. But no files named '*numpy3*'
anywhere in the system except /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo

Cheers ... Duncan.

From dpross1100 at msn.com  Fri Aug  9 01:44:02 2019
From: dpross1100 at msn.com (Daniel Prosser)
Date: Fri, 9 Aug 2019 01:44:02 +0000
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <20190809012224.GB13423@dimstar.local.net>
Message-ID: <DM5PR22MB0460541088330769D691A68ECCD60@DM5PR22MB0460.namprd22.prod.outlook.com>

That's because the software itself is just called numpy. The package was named numpy3 to distinguish it from the Python 2 version. The numpy stuff in /usr/lib64/python3.7 comes from the numpy3 package.

Dan


On Aug 8, 2019 9:22 PM, Duncan Roe <duncan_roe at optusnet.com.au> wrote:

Hey Rich,

On Thu, Aug 08, 2019 at 02:06:36PM -0700, Rich Shepard wrote:
> On Thu, 8 Aug 2019, Didier Spaier wrote:
>
> > Please run from the systems in concern as root: updateb
>
> Didier,
>
> updatedb runs automatically overnight. The system is not turned off when I
> log out.
>
> > then provide the full output of this command:
> > locate numpy.py
>
> # locate numpy.py
> /usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
> /home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py
>
> But, ...
>
> # find / -name numpy
> /usr/lib64/python2.7/site-packages/numpy
> /usr/lib64/python2.7/site-packages/pandas/compat/numpy
> /usr/lib64/python2.7/site-packages/Cython/Includes/numpy
> /usr/lib64/R/library/BH/include/boost/python/numpy
> /usr/lib64/python3.7/site-packages/numpy
> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy
> /var/lib/sbopkg/SBo/14.2/development/numpy
> /opt/slackbuilds/Development/numpy

These are all directories. If you try again with "-tye f" you won't see them.
(Quick check: find /usr/lib64 -type f -name numpy).
>
> Rich
> _______________________________________________
I tried this:

09:12:16# find /usr/lib64 /usr/src/slackbuilds -type f -name '*numpy*'
/usr/lib64/python3.7/site-packages/numpy/core/__pycache__/generate_numpy_api.cpython-37.pyc
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy/numpyconfig.h
/usr/lib64/python3.7/site-packages/numpy/core/generate_numpy_api.py
/usr/lib64/python3.7/site-packages/numpy/distutils/__pycache__/numpy_distribution.cpython-37.pyc
/usr/lib64/python3.7/site-packages/numpy/distutils/numpy_distribution.py
/usr/lib64/python3.7/site-packages/numpy/tests/test_numpy_version.py
/usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.pyc
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/numpyconfig.h
/usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.py
/usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.pyc
/usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.py
/usr/lib64/python2.7/site-packages/numpy/tests/test_numpy_version.py
/usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.py
/usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.pyc
/usr/lib64/python2.7/site-packages/vtk/util/numpy_support.py
/usr/lib64/python2.7/site-packages/vtk/util/numpy_support.pyc
/usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.py
/usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.pyc
/usr/src/slackbuilds/python/numpydoc/numpydoc.SlackBuild
/usr/src/slackbuilds/python/numpydoc/numpydoc.info
/usr/src/slackbuilds/development/numpy3/numpy3.SlackBuild
/usr/src/slackbuilds/development/numpy3/numpy3.info
/usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.info
/usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.SlackBuild
/usr/src/slackbuilds/development/numpy/numpy.info
/usr/src/slackbuilds/development/numpy/numpy.SlackBuild
/usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.info
/usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.SlackBuild

Here's the rub: I *do* have numpy3 installed. But no files named '*numpy3*'
anywhere in the system except /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo

Cheers ... Duncan.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


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

From duncan_roe at optusnet.com.au  Fri Aug  9 02:32:43 2019
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Fri, 9 Aug 2019 12:32:43 +1000
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <DM5PR22MB0460541088330769D691A68ECCD60@DM5PR22MB0460.namprd22.prod.outlook.com>
References: <20190809012224.GB13423@dimstar.local.net>
 <DM5PR22MB0460541088330769D691A68ECCD60@DM5PR22MB0460.namprd22.prod.outlook.com>
Message-ID: <20190809023243.GA17775@dimstar.local.net>

On Fri, Aug 09, 2019 at 01:44:02AM +0000, Daniel Prosser wrote:
> That's because the software itself is just called numpy. The package was named numpy3 to distinguish it from the Python 2 version. The numpy stuff in /usr/lib64/python3.7 comes from the numpy3 package.
>
> Dan
>
So the original message, "scipy3: cannot find numpy3 when building" is output
by an SBo script when it sees REQUIRES="numpy3 ..." and
/var/log/packages/numpy3-1.14.3-x86_64-1P_SBo does not exist.

Could that be the underlying problem?

Cheers ... Duncan.
>
> On Aug 8, 2019 9:22 PM, Duncan Roe <duncan_roe at optusnet.com.au> wrote:
>
> Hey Rich,
>
> On Thu, Aug 08, 2019 at 02:06:36PM -0700, Rich Shepard wrote:
> > On Thu, 8 Aug 2019, Didier Spaier wrote:
> >
> > > Please run from the systems in concern as root: updateb
> >
> > Didier,
> >
> > updatedb runs automatically overnight. The system is not turned off when I
> > log out.
> >
> > > then provide the full output of this command:
> > > locate numpy.py
> >
> > # locate numpy.py
> > /usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
> > /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
> > /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
> > /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
> > /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
> > /home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py
> >
> > But, ...
> >
> > # find / -name numpy
> > /usr/lib64/python2.7/site-packages/numpy
> > /usr/lib64/python2.7/site-packages/pandas/compat/numpy
> > /usr/lib64/python2.7/site-packages/Cython/Includes/numpy
> > /usr/lib64/R/library/BH/include/boost/python/numpy
> > /usr/lib64/python3.7/site-packages/numpy
> > /usr/lib64/python3.7/site-packages/numpy/core/include/numpy
> > /var/lib/sbopkg/SBo/14.2/development/numpy
> > /opt/slackbuilds/Development/numpy
>
> These are all directories. If you try again with "-tye f" you won't see them.
> (Quick check: find /usr/lib64 -type f -name numpy).
> >
> > Rich
> > _______________________________________________
> I tried this:
>
> 09:12:16# find /usr/lib64 /usr/src/slackbuilds -type f -name '*numpy*'
> /usr/lib64/python3.7/site-packages/numpy/core/__pycache__/generate_numpy_api.cpython-37.pyc
> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy/numpyconfig.h
> /usr/lib64/python3.7/site-packages/numpy/core/generate_numpy_api.py
> /usr/lib64/python3.7/site-packages/numpy/distutils/__pycache__/numpy_distribution.cpython-37.pyc
> /usr/lib64/python3.7/site-packages/numpy/distutils/numpy_distribution.py
> /usr/lib64/python3.7/site-packages/numpy/tests/test_numpy_version.py
> /usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.pyc
> /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
> /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/numpyconfig.h
> /usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.py
> /usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.pyc
> /usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.py
> /usr/lib64/python2.7/site-packages/numpy/tests/test_numpy_version.py
> /usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.py
> /usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.pyc
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.pyc
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.py
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.py
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.pyc
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.py
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.pyc
> /usr/lib64/python2.7/site-packages/vtk/util/numpy_support.py
> /usr/lib64/python2.7/site-packages/vtk/util/numpy_support.pyc
> /usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.py
> /usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.pyc
> /usr/src/slackbuilds/python/numpydoc/numpydoc.SlackBuild
> /usr/src/slackbuilds/python/numpydoc/numpydoc.info
> /usr/src/slackbuilds/development/numpy3/numpy3.SlackBuild
> /usr/src/slackbuilds/development/numpy3/numpy3.info
> /usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.info
> /usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.SlackBuild
> /usr/src/slackbuilds/development/numpy/numpy.info
> /usr/src/slackbuilds/development/numpy/numpy.SlackBuild
> /usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.info
> /usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.SlackBuild
>
> Here's the rub: I *do* have numpy3 installed. But no files named '*numpy3*'
> anywhere in the system except /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo
>
> Cheers ... Duncan.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


From dpross1100 at msn.com  Fri Aug  9 02:47:19 2019
From: dpross1100 at msn.com (Daniel Prosser)
Date: Fri, 9 Aug 2019 02:47:19 +0000
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <20190809023243.GA17775@dimstar.local.net>
References: <20190809012224.GB13423@dimstar.local.net>
 <DM5PR22MB0460541088330769D691A68ECCD60@DM5PR22MB0460.namprd22.prod.outlook.com>
 <20190809023243.GA17775@dimstar.local.net>
Message-ID: <DM5PR22MB04609506F368AC7F92BB24A6CCD60@DM5PR22MB0460.namprd22.prod.outlook.com>

Hm, I doubt it. I checked Rich's original email, and this was the actual 
error message when he tried to build scipy3:

Traceback (most recent call last):
 ? File "setup.py", line 474, in <module>
 ??? setup_package()
 ? File "setup.py", line 450, in setup_package
 ??? from numpy.distutils.core import setup
ModuleNotFoundError: No module named 'numpy'

On 8/8/19 10:32 PM, Duncan Roe wrote:
> On Fri, Aug 09, 2019 at 01:44:02AM +0000, Daniel Prosser wrote:
>> That's because the software itself is just called numpy. The package was named numpy3 to distinguish it from the Python 2 version. The numpy stuff in /usr/lib64/python3.7 comes from the numpy3 package.
>>
>> Dan
>>
> So the original message, "scipy3: cannot find numpy3 when building" is output
> by an SBo script when it sees REQUIRES="numpy3 ..." and
> /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo does not exist.
>
> Could that be the underlying problem?
>
> Cheers ... Duncan.
>> On Aug 8, 2019 9:22 PM, Duncan Roe <duncan_roe at optusnet.com.au> wrote:
>>
>> Hey Rich,
>>
>> On Thu, Aug 08, 2019 at 02:06:36PM -0700, Rich Shepard wrote:
>>> On Thu, 8 Aug 2019, Didier Spaier wrote:
>>>
>>>> Please run from the systems in concern as root: updateb
>>> Didier,
>>>
>>> updatedb runs automatically overnight. The system is not turned off when I
>>> log out.
>>>
>>>> then provide the full output of this command:
>>>> locate numpy.py
>>> # locate numpy.py
>>> /usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
>>> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
>>> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
>>> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
>>> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
>>> /home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py
>>>
>>> But, ...
>>>
>>> # find / -name numpy
>>> /usr/lib64/python2.7/site-packages/numpy
>>> /usr/lib64/python2.7/site-packages/pandas/compat/numpy
>>> /usr/lib64/python2.7/site-packages/Cython/Includes/numpy
>>> /usr/lib64/R/library/BH/include/boost/python/numpy
>>> /usr/lib64/python3.7/site-packages/numpy
>>> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy
>>> /var/lib/sbopkg/SBo/14.2/development/numpy
>>> /opt/slackbuilds/Development/numpy
>> These are all directories. If you try again with "-tye f" you won't see them.
>> (Quick check: find /usr/lib64 -type f -name numpy).
>>> Rich
>>> _______________________________________________
>> I tried this:
>>
>> 09:12:16# find /usr/lib64 /usr/src/slackbuilds -type f -name '*numpy*'
>> /usr/lib64/python3.7/site-packages/numpy/core/__pycache__/generate_numpy_api.cpython-37.pyc
>> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
>> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy/numpyconfig.h
>> /usr/lib64/python3.7/site-packages/numpy/core/generate_numpy_api.py
>> /usr/lib64/python3.7/site-packages/numpy/distutils/__pycache__/numpy_distribution.cpython-37.pyc
>> /usr/lib64/python3.7/site-packages/numpy/distutils/numpy_distribution.py
>> /usr/lib64/python3.7/site-packages/numpy/tests/test_numpy_version.py
>> /usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.pyc
>> /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
>> /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/numpyconfig.h
>> /usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.py
>> /usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.pyc
>> /usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.py
>> /usr/lib64/python2.7/site-packages/numpy/tests/test_numpy_version.py
>> /usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.py
>> /usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.pyc
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.pyc
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.py
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.py
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.pyc
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.py
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.pyc
>> /usr/lib64/python2.7/site-packages/vtk/util/numpy_support.py
>> /usr/lib64/python2.7/site-packages/vtk/util/numpy_support.pyc
>> /usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.py
>> /usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.pyc
>> /usr/src/slackbuilds/python/numpydoc/numpydoc.SlackBuild
>> /usr/src/slackbuilds/python/numpydoc/numpydoc.info
>> /usr/src/slackbuilds/development/numpy3/numpy3.SlackBuild
>> /usr/src/slackbuilds/development/numpy3/numpy3.info
>> /usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.info
>> /usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.SlackBuild
>> /usr/src/slackbuilds/development/numpy/numpy.info
>> /usr/src/slackbuilds/development/numpy/numpy.SlackBuild
>> /usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.info
>> /usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.SlackBuild
>>
>> Here's the rub: I *do* have numpy3 installed. But no files named '*numpy3*'
>> anywhere in the system except /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo
>>
>> Cheers ... Duncan.
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From chris.willing at linux.com  Fri Aug  9 12:16:18 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Fri, 9 Aug 2019 22:16:18 +1000
Subject: [Slackbuilds-users] configure: error: GCC 5.5.0 is too old
Message-ID: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>

I'm working on an update of the SlackBuild for LibreOffice (build from
source) to version 6.3.0.4 but it very soon leads to:

checking the GCC version... gcc 5.5.0 (50500)
configure: error: GCC 5.5.0 is too old, must be at least GCC 7.0.0
Error running configure at ./autogen.sh line 302.


Is anyone interested in submitting a SlackBuild for gcc7 along the lines
of gcclegacy494  i.e. an updated gcc >= 7.0.0 that can coexist with
14.2's gcc-5.5.0? I'm not sure whether this is the first SlackBuild that
finds the standard gcc too old but it will probably not be the last, so
an updated gcc would be good contribution.

chris

From davidnchmelik at gmail.com  Fri Aug  9 12:23:43 2019
From: davidnchmelik at gmail.com (David Chmelik)
Date: Fri, 9 Aug 2019 05:23:43 -0700
Subject: [Slackbuilds-users] configure: error: GCC 5.5.0 is too old
In-Reply-To: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
References: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
Message-ID: <1f609dbc-b39f-49c3-8900-902097b69fb9@gmail.com>

On 8/9/19 5:16 AM, Christoph Willing wrote:
> [...] Is anyone interested in submitting a SlackBuild for gcc7 along the lines
> of gcclegacy494  i.e. an updated gcc >= 7.0.0 that can coexist with
> 14.2's gcc-5.5.0? I'm not sure whether this is the first SlackBuild that
> finds the standard gcc too old but it will probably not be the last, so
> an updated gcc would be good contribution.

It's not. Tome-ah and probably ToME-SX needed newer gcc years ago; 
that's why I haven't updated classic tome SlackBuilds in years. Building 
a compiler sounds like something bigger than I want to take on right 
now.? Updating those games is not so important but I hope the problem is 
solved at least for Libre Office...

From rshepard at appl-ecosys.com  Fri Aug  9 12:43:50 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 9 Aug 2019 05:43:50 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <DM5PR22MB0460541088330769D691A68ECCD60@DM5PR22MB0460.namprd22.prod.outlook.com>
References: <DM5PR22MB0460541088330769D691A68ECCD60@DM5PR22MB0460.namprd22.prod.outlook.com>
Message-ID: <alpine.LNX.2.20.1908090539530.9134@salmo.appl-ecosys.com>

On Fri, 9 Aug 2019, Daniel Prosser wrote:

> That's because the software itself is just called numpy. The package was
> named numpy3 to distinguish it from the Python 2 version. The numpy stuff
> in /usr/lib64/python3.7 comes from the numpy3 package.

Dan, et al.:

Related to this name issue of distinguishing between python versions is
something I learned just yesterday. When using pip to download and isntall
numpy3 the correct syntax is 'pip3 install numpy'. There are still two
versions of pip, but by using pip3 it will grab the proper version of numpy.

Thanks for all the insights,

Rich

From rshepard at appl-ecosys.com  Fri Aug  9 12:46:33 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 9 Aug 2019 05:46:33 -0700 (PDT)
Subject: [Slackbuilds-users] scipy3: cannot find numpy3 when building
 [RESOLVED]
In-Reply-To: <20190809023243.GA17775@dimstar.local.net>
References: <20190809012224.GB13423@dimstar.local.net>
 <DM5PR22MB0460541088330769D691A68ECCD60@DM5PR22MB0460.namprd22.prod.outlook.com>
 <20190809023243.GA17775@dimstar.local.net>
Message-ID: <alpine.LNX.2.20.1908090544130.9134@salmo.appl-ecosys.com>

On Fri, 9 Aug 2019, Duncan Roe wrote:

> So the original message, "scipy3: cannot find numpy3 when building" is
> output by an SBo script when it sees REQUIRES="numpy3 ..." and
> /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo does not exist.
>
> Could that be the underlying problem?

Duncan,

Could be. See my last message about specifying only numpy (rather than
numpy3) when using pip to install it.

And, fwiw, python2 reaches EOL on 1 January 2020. That should clear things
up a but.

Interesting insight.

Best regards,

Rich


From belka at caraus.de  Fri Aug  9 13:05:29 2019
From: belka at caraus.de (Eugen Wissner)
Date: Fri, 09 Aug 2019 15:05:29 +0200
Subject: [Slackbuilds-users] configure: error: GCC 5.5.0 is too old
In-Reply-To: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
References: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
Message-ID: <1565355929.1747.1.camel@caraus.de>

You can use gcc-d, it includes gcc-8 (gcc and g++), compatible with
gcc5.

Am Freitag, den 09.08.2019, 22:16 +1000 schrieb Christoph Willing:
> I'm working on an update of the SlackBuild for LibreOffice (build
> from
> source) to version 6.3.0.4 but it very soon leads to:
> 
> checking the GCC version... gcc 5.5.0 (50500)
> configure: error: GCC 5.5.0 is too old, must be at least GCC 7.0.0
> Error running configure at ./autogen.sh line 302.
> 
> 
> Is anyone interested in submitting a SlackBuild for gcc7 along the
> lines
> of gcclegacy494??i.e. an updated gcc >= 7.0.0 that can coexist with
> 14.2's gcc-5.5.0? I'm not sure whether this is the first SlackBuild
> that
> finds the standard gcc too old but it will probably not be the last,
> so
> an updated gcc would be good contribution.
> 
> chris
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From willysr at slackbuilds.org  Fri Aug  9 17:28:45 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Aug 2019 00:28:45 +0700
Subject: [Slackbuilds-users] configure: error: GCC 5.5.0 is too old
In-Reply-To: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
References: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
Message-ID: <dbe92b43-0cdf-0118-907c-d9190fba5564@slackbuilds.org>

> I'm working on an update of the SlackBuild for LibreOffice (build from
> source) to version 6.3.0.4 but it very soon leads to:
> 
> checking the GCC version... gcc 5.5.0 (50500)
> configure: error: GCC 5.5.0 is too old, must be at least GCC 7.0.0
> Error running configure at ./autogen.sh line 302.
> 
> 
> Is anyone interested in submitting a SlackBuild for gcc7 along the lines
> of gcclegacy494  i.e. an updated gcc >= 7.0.0 that can coexist with
> 14.2's gcc-5.5.0? I'm not sure whether this is the first SlackBuild that
> finds the standard gcc too old but it will probably not be the last, so
> an updated gcc would be good contribution.

I think it's good to keep LO at 6.2.x since they drop support for x86 as
well in 6.3.x.


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Fri Aug  9 18:21:44 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Aug 2019 01:21:44 +0700
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <CANi9qSupahvjgb_vY3NU9-V7sbpFdPNACvZ5DroHYT5agA-RFA@mail.gmail.com>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
 <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
 <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>
 <alpine.LNX.2.20.1908051707270.1601@salmo.appl-ecosys.com>
 <CANi9qSupahvjgb_vY3NU9-V7sbpFdPNACvZ5DroHYT5agA-RFA@mail.gmail.com>
Message-ID: <68cf1f4a-7dcb-7636-6e77-4dd7954f3e77@slackbuilds.org>

> This actually reminded me of a request I made for sqg almost 4 years ago
> that Willy implemented 2 years ago. You should be able to run sqg with
> the programs you you want with a -o after it and it will write a
> /var/lib/sbopkg/queues/custom.sqf file
> 
> sqg -p "krusader filezilla mediainfo" -o
> 
> You could use this to have sqg create a custom.sqf file, which you
> should then be able to run sbopkg -i custom and then tell it to do the
> queuefile.

This feature is only available in master branch for now, so it won't be
available for those using 0.38.1


-- 
Willy Sudiarto Raharjo

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

From rshepard at appl-ecosys.com  Fri Aug  9 18:24:57 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 9 Aug 2019 11:24:57 -0700 (PDT)
Subject: [Slackbuilds-users] Rebuilding packages on new host
In-Reply-To: <68cf1f4a-7dcb-7636-6e77-4dd7954f3e77@slackbuilds.org>
References: <alpine.LNX.2.20.1908021537050.17685@salmo.appl-ecosys.com>
 <CAJ2_kYoe4e-S4uPbhqS-rZ5RbHXpvv6MVO8ZW5Hsd6w8j3b-LA@mail.gmail.com>
 <alpine.LNX.2.20.1908031500430.12955@salmo.appl-ecosys.com>
 <CAJ2_kYovxjt_Tzq7xbnXrKU_H3pnNYhCrZM56Tn52qMPxTT-Dg@mail.gmail.com>
 <alpine.LNX.2.20.1908051425220.1601@salmo.appl-ecosys.com>
 <CANi9qSu+m4j0puuMBr6DofhYbBqANc_UBg=igGSLz_A+u0qpyg@mail.gmail.com>
 <alpine.LNX.2.20.1908051707270.1601@salmo.appl-ecosys.com>
 <CANi9qSupahvjgb_vY3NU9-V7sbpFdPNACvZ5DroHYT5agA-RFA@mail.gmail.com>
 <68cf1f4a-7dcb-7636-6e77-4dd7954f3e77@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1908091123220.9134@salmo.appl-ecosys.com>

On Sat, 10 Aug 2019, Willy Sudiarto Raharjo wrote:

> This feature is only available in master branch for now, so it won't be
> available for those using 0.38.1

Willy,

I didn't try using it. I made the queue.sqf from the packages installed on the
old host that were not on the new host.

Regards,

Rich

From chris.willing at linux.com  Fri Aug  9 22:51:35 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Sat, 10 Aug 2019 08:51:35 +1000
Subject: [Slackbuilds-users] configure: error: GCC 5.5.0 is too old
In-Reply-To: <1565355929.1747.1.camel@caraus.de>
References: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
 <1565355929.1747.1.camel@caraus.de>
Message-ID: <6ad6898a-df51-eb74-7cf1-bc0e530a947b@linux.com>

On 9/8/19 11:05 pm, Eugen Wissner wrote:
> You can use gcc-d, it includes gcc-8 (gcc and g++), compatible with
> gcc5.
> 

Thanks Eugen,

That's good information I didn't know about. I'll give it a try.

chris

From chris.willing at linux.com  Fri Aug  9 22:51:40 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Sat, 10 Aug 2019 08:51:40 +1000
Subject: [Slackbuilds-users] configure: error: GCC 5.5.0 is too old
In-Reply-To: <dbe92b43-0cdf-0118-907c-d9190fba5564@slackbuilds.org>
References: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
 <dbe92b43-0cdf-0118-907c-d9190fba5564@slackbuilds.org>
Message-ID: <12b79625-b371-ecf2-f440-5f183dd5eb36@linux.com>

On 10/8/19 3:28 am, Willy Sudiarto Raharjo wrote:
>> I'm working on an update of the SlackBuild for LibreOffice (build from
>> source) to version 6.3.0.4 but it very soon leads to:
>>
>> checking the GCC version... gcc 5.5.0 (50500)
>> configure: error: GCC 5.5.0 is too old, must be at least GCC 7.0.0
>> Error running configure at ./autogen.sh line 302.
>>
>>
>> Is anyone interested in submitting a SlackBuild for gcc7 along the lines
>> of gcclegacy494  i.e. an updated gcc >= 7.0.0 that can coexist with
>> 14.2's gcc-5.5.0? I'm not sure whether this is the first SlackBuild that
>> finds the standard gcc too old but it will probably not be the last, so
>> an updated gcc would be good contribution.
> 
> I think it's good to keep LO at 6.2.x since they drop support for x86 as
> well in 6.3.x.
> 

I'd forgotten that they're dropping x86 support in 6.3.x. However I
noticed that on the LO development list, they're helping people from a
specialist x86 distro to make their own packages. No success with that
yet but the fact that they're being assisted by the developers gives
some hope that it's possible.

As for the compiler verion problem, I'm going to try Eugen's suggestion
to use ggc-d and if it works for x86_64 then I'll try it with x86. If
both work then I'll update but otherwise leave it where it is.

chris

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190810/d910a50b/attachment-0001.asc>

From andrew.david.strong at gmail.com  Sat Aug 10 00:42:03 2019
From: andrew.david.strong at gmail.com (andrew)
Date: Sat, 10 Aug 2019 10:42:03 +1000
Subject: [Slackbuilds-users] For grabs: gimp-plugin-export-layers
In-Reply-To: <20190806003409.GA5211@ilium.andrews-corner.org>
References: <20190806003409.GA5211@ilium.andrews-corner.org>
Message-ID: <20190810004203.GA9994@ilium.andrews-corner.org>

On Tue, Aug 06, 2019 at 10:34:13AM +1000, andrew wrote:

> Would anybody like to take over gimp-plugin-export-layers? It is here:
> 
> https://slackbuilds.org/repository/14.2/graphics/gimp-plugin-export-layers/

Does not look like I can sell that one :(

Andrew
-- 
You think that's air you're breathing now?

From willysr at slackbuilds.org  Sat Aug 10 01:46:44 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Aug 2019 08:46:44 +0700
Subject: [Slackbuilds-users] Updates - 20190810.1
Message-ID: <dcf46215-566b-3053-4309-93a700e789dd@slackbuilds.org>

Sat Aug 10 01:31:09 UTC 2019
academic/R: Updated for version 3.6.1.
academic/abella: Added (interactive theorem prover).
academic/scidavis: Add patches.
audio/FAudio: Added (Accuracy-focused XAudio reimplementation).
desktop/rofi: Updated for version 1.5.4.
development/adoptopenjdk: Updated for version 12.0.2+10.
development/beautysh: Updated for version 5.0.2.
development/composer: Updated for version 1.9.0
development/d-tools: Updated for version 2.087.1
development/dmd: Updated for version 2.087.1
development/hhvm: Updated for version 4.8.2
development/jupyter-nbconvert: Updated for version 5.6.0.
development/jupyter-nbdime: Updated for version 1.1.0.
development/neovim-qt: Updated for version 0.2.13.
development/sbcl: Updated for version 1.5.5.
development/universal-ctags: Updated for version b818539
games/manaplus: Updated for version 1.9.3.23.
gis/ossim: Updated for version 2.8.2.
gis/qmapshack: Updated for version 1.13.1.
gis/rasterio: Updated for version 1.0.25.
graphics/feh: Updated for version 3.2.1.
graphics/libplacebo: Added (GPU rendering library).
graphics/shaderc: Added (Shader tools, libraries and tests).
graphics/vulkan-sdk: Updated for version 1.1.114.0.
libraries/libuv: Updated for version 1.31.0.
libraries/robin-map: Added (C++ fast hash map).
libraries/zeromq: Updated for version 4.3.2.
misc/floating-IPS: Update URLs.
multimedia/spotify: Updated for version 1.0.79.
network/bitcoin: Updated for version 0.18.1.
network/bluejeans: Added (Audio/Video conferencing client).
network/brave-browser: Updated for version 0.67.123.
network/opensm: Added (InfiniBand Subnet Manager and Administrator).
network/opensmtpd: Apply OpenBSD 6.4 patch 20.
network/packETH: Updated for version 2.0.
network/prosody-mod-smacks: Updated for version hg3640.
network/rdma-core: Fix text.
network/scapy: Updated for version 2.4.3.
network/wavemon: Updated for version 0.9.0.
office/zim: Updated for version 0.71.1.
python/pybind11: Added (Python bindings for C++11).
python/python-emoji: Updated for version 0.5.3.
python/python-fonttools: Updated for version 3.44.0.
python/python3-jupyter-ipykernel: Updated for version 5.1.2.
python/pyzmq: Updated for version 18.1.0.
system/ack: Updated for version 3.0.2.
system/avfs: Updated for version 1.1.0.
system/clamav: Updated for version 0.101.3.
system/epson-inkjet-printer-escpr: Updated for version 1.7.0.
system/exa: Updated for version 0.9.0.
system/fwupd: Updated for version 1.2.10.
system/ksh-openbsd: Updated for version 20190804.
system/ripgrep: Updated for version 11.0.2.
system/rmw: Updated for version 0.7.03.
system/worker: Updated for version 4.0.1.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From mickski56 at hotmail.com  Sat Aug 10 08:07:16 2019
From: mickski56 at hotmail.com (mickski 56)
Date: Sat, 10 Aug 2019 08:07:16 +0000
Subject: [Slackbuilds-users] qmapshack fails to build
In-Reply-To: <dcf46215-566b-3053-4309-93a700e789dd@slackbuilds.org>
References: <dcf46215-566b-3053-4309-93a700e789dd@slackbuilds.org>
Message-ID: <HE1P191MB024937CC53D05182980EB973B1D10@HE1P191MB0249.EURP191.PROD.OUTLOOK.COM>

Have I missed something, qmapshack fails to build because it can't find
proj4. FindPROJ4.cmake is no longer refereced in the slackbuild even
though proj built from sbo is still not built with cmake.

re-adding the line and of course the file allows qmapshack-1.3.1 to
build.

HTH :-)

From mickski56 at hotmail.com  Sat Aug 10 08:09:07 2019
From: mickski56 at hotmail.com (mickski 56)
Date: Sat, 10 Aug 2019 08:09:07 +0000
Subject: [Slackbuilds-users] qmapshack fails to build
In-Reply-To: <HE1P191MB024937CC53D05182980EB973B1D10@HE1P191MB0249.EURP191.PROD.OUTLOOK.COM>
References: <dcf46215-566b-3053-4309-93a700e789dd@slackbuilds.org>
 <HE1P191MB024937CC53D05182980EB973B1D10@HE1P191MB0249.EURP191.PROD.OUTLOOK.COM>
Message-ID: <HE1P191MB02495E7346753248DEA99A3CB1D10@HE1P191MB0249.EURP191.PROD.OUTLOOK.COM>

> Have I missed something, qmapshack fails to build because it can't
> find proj4. FindPROJ4.cmake is no longer refereced in the slackbuild
> even though proj built from sbo is still not built with cmake.
> 
> re-adding the line and of course the file allows 133.1 to
> build.
> 
> HTH :-)
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
 That should of course be qmapshack-1.13.1

From heiko.rosemann at web.de  Sat Aug 10 18:13:16 2019
From: heiko.rosemann at web.de (Heiko Rosemann)
Date: Sat, 10 Aug 2019 20:13:16 +0200
Subject: [Slackbuilds-users] vuescan / openjfx: Anyone up for taking over?
Message-ID: <ab8168ce-4157-e6c6-b432-12859df01bde@web.de>

Hello everyone,

tl,dr: if anyone wants to put effort into vuescan or openjfx, feel free
to do so :)

Currently, I'm not using vuescan, so I'm hardly ever updating it, and
probably the md5sum checks for the download file(s) fail (the download
files get replaced in place). Nobody asked me about this for a long
time, so maybe nobody else is using it, which would be fine...

I _am_ using openjfx, but the SlackBuild I made for it was just a quick
hack from a binary build that's no longer maintained. I planned to
switch over to a source build, but never managed to do so, so if
anyone's up for it, go for it. This might "fix itself" with Java 11.

I'm fine with keeping those SlackBuilds and just continuing not to
update them as well :)

Best regards,
Heiko

-- 
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190810/a9097101/attachment-0001.asc>

From chris.willing at linux.com  Sun Aug 11 05:44:02 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Sun, 11 Aug 2019 15:44:02 +1000
Subject: [Slackbuilds-users] configure: error: GCC 5.5.0 is too old
In-Reply-To: <12b79625-b371-ecf2-f440-5f183dd5eb36@linux.com>
References: <7fd8ba03-d995-9615-837c-cc4059bc95c2@linux.com>
 <dbe92b43-0cdf-0118-907c-d9190fba5564@slackbuilds.org>
 <12b79625-b371-ecf2-f440-5f183dd5eb36@linux.com>
Message-ID: <22169f78-17f9-44d3-0b34-3f62d70d938c@linux.com>

On 10/8/19 8:51 am, Christoph Willing wrote:
> On 10/8/19 3:28 am, Willy Sudiarto Raharjo wrote:
>>> I'm working on an update of the SlackBuild for LibreOffice (build from
>>> source) to version 6.3.0.4 but it very soon leads to:
>>>
>>> checking the GCC version... gcc 5.5.0 (50500)
>>> configure: error: GCC 5.5.0 is too old, must be at least GCC 7.0.0
>>> Error running configure at ./autogen.sh line 302.
>>>
>>>
>>> Is anyone interested in submitting a SlackBuild for gcc7 along the lines
>>> of gcclegacy494  i.e. an updated gcc >= 7.0.0 that can coexist with
>>> 14.2's gcc-5.5.0? I'm not sure whether this is the first SlackBuild that
>>> finds the standard gcc too old but it will probably not be the last, so
>>> an updated gcc would be good contribution.
>>
>> I think it's good to keep LO at 6.2.x since they drop support for x86 as
>> well in 6.3.x.
>>
> 
> I'd forgotten that they're dropping x86 support in 6.3.x. However I
> noticed that on the LO development list, they're helping people from a
> specialist x86 distro to make their own packages. No success with that
> yet but the fact that they're being assisted by the developers gives
> some hope that it's possible.
> 
> As for the compiler verion problem, I'm going to try Eugen's suggestion
> to use ggc-d and if it works for x86_64 then I'll try it with x86. If
> both work then I'll update but otherwise leave it where it is.
> 

Well using gcc-d works (at least autogen.sh finds & accepts it), however
another problem then arises - that 14.2's gperf-3.0.4 as also too old. I
can imagine arranging a special version of gperf just to compile
LO-6.3.x and then finding that some other tool is also too old etc.,
etc., so I'll just leave LibreOffice at 6.2.x.

chris

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

From andrew.david.strong at gmail.com  Sun Aug 11 08:51:07 2019
From: andrew.david.strong at gmail.com (andrew)
Date: Sun, 11 Aug 2019 18:51:07 +1000
Subject: [Slackbuilds-users] For grabs: gimp-plugin-export-layers
In-Reply-To: <20190810004203.GA9994@ilium.andrews-corner.org>
References: <20190806003409.GA5211@ilium.andrews-corner.org>
 <20190810004203.GA9994@ilium.andrews-corner.org>
Message-ID: <20190811085107.GA75770@ilium.andrews-corner.org>

On Sat, Aug 10, 2019 at 10:42:07AM +1000, andrew wrote:

> Does not look like I can sell that one :(

Forgive the noise, I am in the process of updating the script and
fixing a few rather embarassing errors in it :)

Andrew
-- 
You think that's air you're breathing now?

From andrew.david.strong at gmail.com  Tue Aug 13 07:17:09 2019
From: andrew.david.strong at gmail.com (andrew)
Date: Tue, 13 Aug 2019 17:17:09 +1000
Subject: [Slackbuilds-users] Web upload broken?
Message-ID: <20190813071709.GA59399@ilium.andrews-corner.org>

Hi,

I have just successfully uploaded libaom update via:

https://slackbuilds.org/submit/

but I cannot upload my next update which is for nv-codecs-headers.
Error message is:

Submission failed:
Could not find nv-codecs-headers/nv-codecs-headers.info
Could not find nv-codecs-headers/nv-codecs-headers.SlackBuild

All of which are in the archive:

andrew at ilium~/tmp$ tar -tf nv-codecs-headers.tar.gz
nv-codecs-headers/
nv-codecs-headers/README
nv-codecs-headers/slack-desc
nv-codecs-headers/nv-codec-headers.info
nv-codecs-headers/nv-codec-headers.SlackBuild
andrew at ilium~/tmp$

It has been a bad day for me so possibly I am making yet another
mistake...

Andrew
-- 
You think that's air you're breathing now?

From andrew.david.strong at gmail.com  Tue Aug 13 07:22:06 2019
From: andrew.david.strong at gmail.com (andrew)
Date: Tue, 13 Aug 2019 17:22:06 +1000
Subject: [Slackbuilds-users] Web upload broken?
In-Reply-To: <20190813071709.GA59399@ilium.andrews-corner.org>
References: <20190813071709.GA59399@ilium.andrews-corner.org>
Message-ID: <20190813072206.GA59971@ilium.andrews-corner.org>

On Tue, Aug 13, 2019 at 05:17:14PM +1000, andrew wrote:

> but I cannot upload my next update which is for nv-codecs-headers.
> Error message is:
> 
> Submission failed:
> Could not find nv-codecs-headers/nv-codecs-headers.info
> Could not find nv-codecs-headers/nv-codecs-headers.SlackBuild
> 
> All of which are in the archive:
> 
> andrew at ilium~/tmp$ tar -tf nv-codecs-headers.tar.gz
> nv-codecs-headers/
> nv-codecs-headers/README
> nv-codecs-headers/slack-desc
> nv-codecs-headers/nv-codec-headers.info
> nv-codecs-headers/nv-codec-headers.SlackBuild
> andrew at ilium~/tmp$
> 
> It has been a bad day for me so possibly I am making yet another
> mistake...

Sigh.... now I see the renegade 's' ..... sorry for the noise.

Andrew
-- 
You think that's air you're breathing now?

From phalange at komputermatrix.com  Tue Aug 13 19:18:59 2019
From: phalange at komputermatrix.com (Andrew Payne)
Date: Tue, 13 Aug 2019 15:18:59 -0400
Subject: [Slackbuilds-users] SBo doesn't reflect updates to Slackbuild README
Message-ID: <7dde6893a19cb71279d552d975a56148.squirrel@email.fatcow.com>

I'm seeing that when I update slackbuilds I maintain, files other than
*.SlackBuild, *.info and slack-desc are not changed on the SBo website.

My question then is, should I do PRs for changes to other files (e.g., the
README), or make a note in the submission form that changes to other files
have been made?

Thanks all,
Andrew


From rworkman at slackbuilds.org  Wed Aug 14 04:07:09 2019
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 13 Aug 2019 23:07:09 -0500
Subject: [Slackbuilds-users] SBo doesn't reflect updates to Slackbuild
 README
In-Reply-To: <7dde6893a19cb71279d552d975a56148.squirrel@email.fatcow.com>
References: <7dde6893a19cb71279d552d975a56148.squirrel@email.fatcow.com>
Message-ID: <20190813230709.741200e3@home.rlworkman.net>

On Tue, 13 Aug 2019 15:18:59 -0400
"Andrew Payne" <phalange at komputermatrix.com> wrote:

> I'm seeing that when I update slackbuilds I maintain, files other than
> *.SlackBuild, *.info and slack-desc are not changed on the SBo
> website.
> 
> My question then is, should I do PRs for changes to other files
> (e.g., the README), or make a note in the submission form that
> changes to other files have been made?


Hmmm, do you know who committed the update(s) in question?
I recall doing a few in which the README change(s) looked either
inconsequential (i.e. probably accidental, e.g. added whitespace
at the end of a line) or they were more confusing than the copy
that was already in the git repo, so I overwrite the new copy
with our current one. I have no idea which specific builds those
were or who maintained them though.

I don't know everyone else's workflow, but for me, there's no
way to accidentally miss changes to the README - once I make
whatever fixups I need to make to a submission, I move the entire
$app directory over to the git repo in place of the old $app dir,
and then a combination of "git status" and "git diff" are used to
make sure I didn't miss e.g. a new patch and review the changes 
to everything against the current version in the repo.

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

From rshepard at appl-ecosys.com  Wed Aug 14 22:37:48 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 14 Aug 2019 15:37:48 -0700 (PDT)
Subject: [Slackbuilds-users] Utility to identify required python version?
Message-ID: <alpine.LNX.2.20.1908141537100.30697@salmo.appl-ecosys.com>

I think that GRASS gis was the last application installed here that used
python2. Now that it requires python3 I would like to determine if there's
any reason to also have python2 installed.

I assume that a python2 prerequisite would apply to only SBo packages. Is
there a sbopkg option to do this? The -g option finds packages with the
argument in its name, not as a requirement.

When I run 'hoorex python2' or 'hoorex python' nothing is returned.

Regards,

Rich

From slackbuilds at jaxartes.net  Wed Aug 14 22:50:48 2019
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Wed, 14 Aug 2019 15:50:48 -0700
Subject: [Slackbuilds-users] Utility to identify required python version?
In-Reply-To: <alpine.LNX.2.20.1908141537100.30697@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908141537100.30697@salmo.appl-ecosys.com>
Message-ID: <973f170d-d60b-dcb3-e409-f5cb6e490099@jaxartes.net>

On 2019-08-14 3:37 p.m., Rich Shepard wrote:
> I think that GRASS gis was the last application installed here that used
> python2. Now that it requires python3 I would like to determine if there's
> any reason to also have python2 installed.
> 
> I assume that a python2 prerequisite would apply to only SBo packages. Is
> there a sbopkg option to do this? The -g option finds packages with the
> argument in its name, not as a requirement.
> 
> When I run 'hoorex python2' or 'hoorex python' nothing is returned.

Python 2 (Slackware package "python") is a system package so you will 
not see it referenced as a SlackBuild requirement and it's definitely 
inadvisable to uninstall it.



From rshepard at appl-ecosys.com  Wed Aug 14 23:03:15 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 14 Aug 2019 16:03:15 -0700 (PDT)
Subject: [Slackbuilds-users] Utility to identify required python version?
In-Reply-To: <973f170d-d60b-dcb3-e409-f5cb6e490099@jaxartes.net>
References: <alpine.LNX.2.20.1908141537100.30697@salmo.appl-ecosys.com>
 <973f170d-d60b-dcb3-e409-f5cb6e490099@jaxartes.net>
Message-ID: <alpine.LNX.2.20.1908141602050.30697@salmo.appl-ecosys.com>

On Wed, 14 Aug 2019, Benjamin Trigona-Harany wrote:

> Python 2 (Slackware package "python") is a system package so you will not
> see it referenced as a SlackBuild requirement and it's definitely
> inadvisable to uninstall it.

Ben,

Okay. Makes sense to me. I still need to get the latest github grass code to
see python3 rather than python2.

Regards,

Rich

From chris.willing at linux.com  Thu Aug 15 06:52:01 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Thu, 15 Aug 2019 16:52:01 +1000
Subject: [Slackbuilds-users] Utility to identify required python version?
In-Reply-To: <alpine.LNX.2.20.1908141537100.30697@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1908141537100.30697@salmo.appl-ecosys.com>
Message-ID: <3fd8acd0-85c6-0f4e-845e-6e4b2b206673@linux.com>

On 15/8/19 8:37 am, Rich Shepard wrote:
[snip]
> 
> When I run 'hoorex python2' or 'hoorex python' nothing is returned.
>

Hoorex uses SBo package .info files to determine relationships between
the various packages. It doesn't know anything about Slackware's stock
system packages, like python, because they don't have .info files.

chris

From dickson.tim at googlemail.com  Thu Aug 15 10:28:53 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Thu, 15 Aug 2019 11:28:53 +0100
Subject: [Slackbuilds-users] audacity slackbuild bug/fix
Message-ID: <b3ecf2f2-307a-0244-6cdf-a0ed63a98c93@googlemail.com>

There's a typo in the audacity slackbuild
the line

rm -rf $PRGNAM-src-$VERSION

should read

rm -rf $PRGNAM-$SRCNAM-$VERSION

Without this change, if you try to rebuild the same version of audacity 
on a machine (using sbo for example) the build fails.
regards, Tim

From kingbeowulf at gmail.com  Thu Aug 15 21:50:07 2019
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 15 Aug 2019 14:50:07 -0700
Subject: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted
Message-ID: <88efcfe4-e0d2-106e-005a-2235b11fe6d5@gmail.com>

Hello all

Nvidia is getting ready to drop non-GLVND libraries.  This is my first
pass to refactor the SBo scripts and get ready for 15.0 "real soon now."

430.40 mainly adds support for RTX 2080 Super cards and some minor bug
fixes.

These WILL NOT work on -current, at all, as of yet, since I need to
resolve Mesa library conflicts and any version conflicts with libglvnd
in the driver vs. the version in current.  I haven't had time yet to
build a box with current and a Nvidia GPU.  All the extra Nvidia GPUs I
have are too old for the 4xx Nvidia driver generation. Come to think of
it, I also need a newer mobo, CPU and memory....

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190815/6f1a9cf8/attachment.asc>

From z.coldplayer at gmail.com  Fri Aug 16 07:35:59 2019
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Fri, 16 Aug 2019 11:35:59 +0400
Subject: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted
In-Reply-To: <88efcfe4-e0d2-106e-005a-2235b11fe6d5@gmail.com>
References: <88efcfe4-e0d2-106e-005a-2235b11fe6d5@gmail.com>
Message-ID: <CAEWL1__ds2WqRVgJy6uy-RuxaTE2eYkEnghCd=nvKmRkDD+CNg@mail.gmail.com>

Hi,

Do you mean changes about dropping support for non-GLVND libraries!

https://devtalk.nvidia.com/default/topic/1060977

My NVIDIA GPU's might be a bit old too, GTX840m.

Cheers
Pritvi


On Fri, 16 Aug 2019 at 01:50, King Beowulf <kingbeowulf at gmail.com> wrote:

> Hello all
>
> Nvidia is getting ready to drop non-GLVND libraries.  This is my first
> pass to refactor the SBo scripts and get ready for 15.0 "real soon now."
>
> 430.40 mainly adds support for RTX 2080 Super cards and some minor bug
> fixes.
>
> These WILL NOT work on -current, at all, as of yet, since I need to
> resolve Mesa library conflicts and any version conflicts with libglvnd
> in the driver vs. the version in current.  I haven't had time yet to
> build a box with current and a Nvidia GPU.  All the extra Nvidia GPUs I
> have are too old for the 4xx Nvidia driver generation. Come to think of
> it, I also need a newer mobo, CPU and memory....
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190816/8e8cc3cc/attachment.htm>

From matteo.bernardini at gmail.com  Fri Aug 16 09:26:53 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 16 Aug 2019 11:26:53 +0200
Subject: [Slackbuilds-users] audacity slackbuild bug/fix
In-Reply-To: <b3ecf2f2-307a-0244-6cdf-a0ed63a98c93@googlemail.com>
References: <b3ecf2f2-307a-0244-6cdf-a0ed63a98c93@googlemail.com>
Message-ID: <CAPsDuS6ya-RcXqrDzUOBKDnE7Pgbzk-a34euCh9+QFmc-cTx8A@mail.gmail.com>

Il giorno gio 15 ago 2019 alle ore 12:29 Tim Dickson
<dickson.tim at googlemail.com> ha scritto:
>
> There's a typo in the audacity slackbuild
> the line
>
> rm -rf $PRGNAM-src-$VERSION
>
> should read
>
> rm -rf $PRGNAM-$SRCNAM-$VERSION
>
> Without this change, if you try to rebuild the same version of audacity
> on a machine (using sbo for example) the build fails.
> regards, Tim

good catch, thanks for reporting!
I just pushed it in our git.

Matteo

From z.coldplayer at gmail.com  Fri Aug 16 09:36:26 2019
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Fri, 16 Aug 2019 13:36:26 +0400
Subject: [Slackbuilds-users] Hacktoberfest 2019
Message-ID: <CAEWL1_-hSjC6nXQ43yVWTN6xDi2=ei6GY26nYQoavmrOK=xcWg@mail.gmail.com>

Hi,

I have been participating in Hacktoberfest organised by DigitalOcean and
Github.

This year, I am organising some hackathon sessions during the month of
october in different
venues, including upcoming Google Devfest.


Would it be possible to use the Slackbuilds mirror repo on github.com for
the Hacktoberfest?

The idea is to make more people involve in Open Source, FLOSS.

Salutations
Pritvi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190816/f060ebba/attachment.htm>

From willysr at slackbuilds.org  Fri Aug 16 13:17:27 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Aug 2019 20:17:27 +0700
Subject: [Slackbuilds-users] Hacktoberfest 2019
In-Reply-To: <CAEWL1_-hSjC6nXQ43yVWTN6xDi2=ei6GY26nYQoavmrOK=xcWg@mail.gmail.com>
References: <CAEWL1_-hSjC6nXQ43yVWTN6xDi2=ei6GY26nYQoavmrOK=xcWg@mail.gmail.com>
Message-ID: <83c0cbd6-2239-9b48-728e-22e9356d0fca@slackbuilds.org>

> I have been participating in Hacktoberfest organised by DigitalOcean and
> Github.
> 
> This year, I am organising some hackathon sessions during the month of
> october in different
> venues, including upcoming Google Devfest.
> 
> 
> Would it be possible to use the Slackbuilds mirror repo on github.com
> <http://github.com> for the Hacktoberfest?
> 
> The idea is to make more people involve in Open Source, FLOSS.

What are your plans for SBo?


-- 
Willy Sudiarto Raharjo

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

From kingbeowulf at gmail.com  Fri Aug 16 17:22:34 2019
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 16 Aug 2019 10:22:34 -0700
Subject: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted
In-Reply-To: <CAEWL1__ds2WqRVgJy6uy-RuxaTE2eYkEnghCd=nvKmRkDD+CNg@mail.gmail.com>
References: <88efcfe4-e0d2-106e-005a-2235b11fe6d5@gmail.com>
 <CAEWL1__ds2WqRVgJy6uy-RuxaTE2eYkEnghCd=nvKmRkDD+CNg@mail.gmail.com>
Message-ID: <722fe724-637c-4a2b-c2a1-4fcf56eefc57@gmail.com>

On 8/16/19 12:35 AM, Jheengut Pritvi wrote:
> Hi,
> 
> Do you mean changes about dropping support for non-GLVND libraries!
> 
> https://devtalk.nvidia.com/default/topic/1060977
> 
> My NVIDIA GPU's might be a bit old too, GTX840m.
> 
> Cheers
> Pritvi
> 

Yes, that was the announcement for the new beta driver. 435.17-beta
still supports the GT[X] 8xx series GPUs.  The cutoff is the GTX 600
series, and my spare cards are older than that. Yours is still "new"!

-Ed


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

From aclemons at runbox.no  Sat Aug 17 02:36:23 2019
From: aclemons at runbox.no (Andrew Clemons)
Date: Sat, 17 Aug 2019 14:36:23 +1200
Subject: [Slackbuilds-users] vuescan / openjfx: Anyone up for taking
 over?
In-Reply-To: <ab8168ce-4157-e6c6-b432-12859df01bde@web.de>
References: <ab8168ce-4157-e6c6-b432-12859df01bde@web.de>
Message-ID: <20190817023623.GA12487@runbox.no>

On 2019-08-10 20:13:16 +0200, heiko.rosemann at web.de wrote:
> [...]
> Currently, I'm not using vuescan, so I'm hardly ever updating it, and
> probably the md5sum checks for the download file(s) fail (the download
> files get replaced in place). Nobody asked me about this for a long
> time, so maybe nobody else is using it, which would be fine...
> [...]

I use vuescan and have been keeping the download and md5sum locally
updated, so I'm happy to take it over.

Thanks,
Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190817/24a6eebd/attachment.asc>

From heiko.rosemann at web.de  Sat Aug 17 08:29:48 2019
From: heiko.rosemann at web.de (Heiko Rosemann)
Date: Sat, 17 Aug 2019 10:29:48 +0200
Subject: [Slackbuilds-users] vuescan / openjfx: Anyone up for taking
 over?
In-Reply-To: <20190817023623.GA12487@runbox.no>
References: <ab8168ce-4157-e6c6-b432-12859df01bde@web.de>
 <20190817023623.GA12487@runbox.no>
Message-ID: <1b246bbc-a0a6-b941-b752-c4f0f9df6cac@web.de>

On 8/17/19 4:36 AM, Andrew Clemons wrote:
> On 2019-08-10 20:13:16 +0200, heiko.rosemann at web.de wrote:
>> [...]
>> Currently, I'm not using vuescan, so I'm hardly ever updating it, and
>> probably the md5sum checks for the download file(s) fail (the download
>> files get replaced in place). Nobody asked me about this for a long
>> time, so maybe nobody else is using it, which would be fine...
>> [...]
> 
> I use vuescan and have been keeping the download and md5sum locally
> updated, so I'm happy to take it over.

Thank you, Andrew!

Heiko

-- 
eMails verschl?sseln mit PGP - privacy is your right!
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190817/5ff54f22/attachment.asc>

From z.coldplayer at gmail.com  Sat Aug 17 15:05:32 2019
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Sat, 17 Aug 2019 19:05:32 +0400
Subject: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted
In-Reply-To: <722fe724-637c-4a2b-c2a1-4fcf56eefc57@gmail.com>
References: <88efcfe4-e0d2-106e-005a-2235b11fe6d5@gmail.com>
 <CAEWL1__ds2WqRVgJy6uy-RuxaTE2eYkEnghCd=nvKmRkDD+CNg@mail.gmail.com>
 <722fe724-637c-4a2b-c2a1-4fcf56eefc57@gmail.com>
Message-ID: <CAEWL1_8eFeCmsoFxMSKbnrvGfaY2qOHcE4qUHRyojuFd86oX4A@mail.gmail.com>

On Fri, 16 Aug 2019 at 21:22, King Beowulf <kingbeowulf at gmail.com> wrote:

> On 8/16/19 12:35 AM, Jheengut Pritvi wrote:
> > Hi,
> >
> > Do you mean changes about dropping support for non-GLVND libraries!
> >
> > https://devtalk.nvidia.com/default/topic/1060977
> >
> > My NVIDIA GPU's might be a bit old too, GTX840m.
> >
> > Cheers
> > Pritvi
> >
>
> Yes, that was the announcement for the new beta driver. 435.17-beta
> still supports the GT[X] 8xx series GPUs.  The cutoff is the GTX 600
> series, and my spare cards are older than that. Yours is still "new"!
>
> -Ed
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

 From this link , I found out what you mean.

https://www.geforce.co.uk/drivers


thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190817/89d1817d/attachment-0001.htm>

From kingbeowulf at gmail.com  Sat Aug 17 18:32:19 2019
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 17 Aug 2019 11:32:19 -0700
Subject: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted
In-Reply-To: <CAEWL1_8eFeCmsoFxMSKbnrvGfaY2qOHcE4qUHRyojuFd86oX4A@mail.gmail.com>
References: <88efcfe4-e0d2-106e-005a-2235b11fe6d5@gmail.com>
 <CAEWL1__ds2WqRVgJy6uy-RuxaTE2eYkEnghCd=nvKmRkDD+CNg@mail.gmail.com>
 <722fe724-637c-4a2b-c2a1-4fcf56eefc57@gmail.com>
 <CAEWL1_8eFeCmsoFxMSKbnrvGfaY2qOHcE4qUHRyojuFd86oX4A@mail.gmail.com>
Message-ID: <31dbeb29-05d5-b2c4-5315-30df9960dc0d@gmail.com>

On 8/17/19 8:05 AM, Jheengut Pritvi wrote:
> 
> 
> On Fri, 16 Aug 2019 at 21:22, King Beowulf <kingbeowulf at gmail.com
> <mailto:kingbeowulf at gmail.com>> wrote:
> 
>     On 8/16/19 12:35 AM, Jheengut Pritvi wrote:
>     > Hi,
>     >
>     > Do you mean changes about dropping support for non-GLVND libraries!
>     >
>     > https://devtalk.nvidia.com/default/topic/1060977
>     >
>     > My NVIDIA GPU's might be a bit old too, GTX840m.
>     >
>     > Cheers
>     > Pritvi
>     >
> 
>     Yes, that was the announcement for the new beta driver. 435.17-beta
>     still supports the GT[X] 8xx series GPUs.? The cutoff is the GTX 600
>     series, and my spare cards are older than that. Yours is still "new"!
> 
>     -Ed
> 

> ?
> ?From this link , I found out what you mean.
> 
> https://www.geforce.co.uk/drivers
> 
> 
> thanks
> 

I thought I was obvious, but ok.  Geforce.com is primarily for Windows
users. These links are also more direct:

https://www.nvidia.com/en-gb/drivers/unix/
https://www.nvidia.com/en-gb/drivers/unix/linux-amd64-display-archive/

https://www.nvidia.com/en-us/drivers/unix/
https://www.nvidia.com/en-us/drivers/unix/linux-amd64-display-archive/

And the primary support and news location is:

https://devtalk.nvidia.com/
https://devtalk.nvidia.com/default/board/98/linux/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190817/16c3d81f/attachment.asc>

From willysr at slackbuilds.org  Sun Aug 18 01:17:09 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 18 Aug 2019 08:17:09 +0700
Subject: [Slackbuilds-users] Updates - 20190818.1
Message-ID: <a0d1997c-6b7d-6169-6fc1-9ed78399b306@slackbuilds.org>

Sun Aug 18 01:03:12 UTC 2019
academic/gspiceui: Updated for version 1.2.36.
academic/zotero: Updated for version 5.0.73.
audio/audacity: Fix cleaning of previous builds.
audio/mixxx: Updated for version 2.2.2.
desktop/bukubrow: Added (Application for Bukubrow WebExtension).
desktop/simplenote: Updated for version 1.7.0.
development/FreeBASIC: Update REQUIRES.
development/SQLAlchemy: Updated for version 1.3.7.
development/hhvm: Updated for version 4.8.3
development/jupyter-ipywidgets: Updated for version 7.5.1.
development/jupyter-qtconsole: Updated for version 4.5.3.
development/jupyter-widgetsnbextension: Upgraded for version 3.5.1.
development/mg-troglobit: Added (Emacs-like Editor).
development/portaudio: Updated for version v190600_20161030.
games/flare-game: Updated for version 1.11.
games/flare: Updated for version 1.11.
games/mrboom: Updated for version 4.8.
gis/ossim: Updated for version 2.9.0.
gis/qmapshack: Restore FindPROJ4 file.
graphics/gimp-plugin-export-layers: Updated for version 3.3.1.
graphics/openimageio: Updated for version 2.0.10
graphics/vuescan: Updated for version 9.6.46.
libraries/aqbanking: Updated for version 5.8.0beta.
libraries/belle-sip: Remove 2nd level dep.
libraries/bzrtp: Remove 2nd level dep.
libraries/dav1d: Updated for version 0.4.0.
libraries/gwenhywfar: Updated for version 4.20.1.
libraries/jsoncpp: Updated for version 1.9.1
libraries/libaom: Updated for version 1.0.0.r2236.g0233da474.
libraries/libbtbb: Added (Bluetooth baseband decoding library).
libraries/libsodium: Updated for version 1.0.18.
libraries/live555: Updated for version 2019.08.16
libraries/mbedtls: Updated for version 2.16.2.
libraries/nv-codec-headers: Updated for version 9.0.18.2.
libraries/opencv: Add qt5 requirement
libraries/qmltermwidget: Updated for version 0.2.0.
misc/protobuf3: Updated for version 3.9.1.
misc/subsurface: Updated for version 4.9.1
misc/ykpers: Updated for version 1.20.0.
multimedia/pepperflash-plugin: Updated for version 32.0.0.238.
multimedia/strawberry: Updated for version 0.6.3.
multimedia/vivaldi-codecs-ffmpeg-extra: Updated for v 76.0.3809.87.
network/NetworkManager-l2tp: Added (VPN Plugin for NM).
network/acme.sh: Updated for version 2.8.2.
network/brave-browser: Updated for version 0.67.125.
network/dnscrypt-proxy: Updated for version 2.0.25.
network/gui-ufw: Updated for version 19.10.0.
network/ii: Updated for version 1.8.
network/lighttpd: Updated for version 1.4.54.
network/linphone: Remove 2nd level dep.
network/msmtp: Updated for version 1.8.5.
network/packETH: Updated for version 2.1.
network/palemoon-bin: Updated for version 28.6.1.
network/palemoon: Updated for version 28.6.1.
network/sfeed: Updated for version 0.9.13.
network/signal-desktop: Updated for version 1.26.2.
network/telegram: Updated for version 1.8.1.
network/vivaldi: Updated for version 2.6.1566.51.
network/youtube-dl: Updated for version 2019.08.13.
office/smoffice2018: Updated for version 2018_968.
office/xournalpp: Added (handwriting software).
perl/perl-Class-Method-Modifiers: Updated for version 2.13.
perl/perl-DBD-SQLite: Updated for version 1.64.
perl/perl-Role-Tiny: Updated for version 2.000008.
pis/postgis: Updated for version 2.5.3.
python/python-joblib: Added (lightweight pipelining in Python).
python/python3-ipython: Updated for version 7.7.0.
python/python3-packaging: Updated for version 19.1.
python/python3-pyzmq: Updated for version 18.1.0
python/scikit-learn: Updated for version 0.21.3.
python/thonny: Updated for version 3.2.0.
system/afdko: Fix script.
system/clamav: Fix clamav-milter command in rc.clamav.
system/cool-retro-term: Updated for version 1.1.1.
system/dosbox-dev: Updated for revision 0.74.3.r4253.
system/epson-inkjet-printer-escpr: Updated for version 2.8.2.
system/gnu-unifont: Updated for version 12.1.03.
system/jdupes: Updated for version 1.13.2.
system/letsencrypt: Updated for version 0.37.1.
system/nvidia-driver: Updated for version 430.40.
system/nvidia-kernel: Updated for version 430.40.
system/nvidia-legacy390-driver: Updated for version 390.129.
system/nvidia-legacy390-kernel: Updated for version 390.129.
system/nvme-cli: Updated for version 1.9.
system/rmw: Updated for version 0.7.04.
system/telegraf: Add missing file.
system/telegraf: Updated for version 1.11.4.
system/thermald: Updated for version 1.9.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From alik at ejik.org  Sun Aug 18 13:37:52 2019
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sun, 18 Aug 2019 16:37:52 +0300
Subject: [Slackbuilds-users] portaudio
In-Reply-To: <a0d1997c-6b7d-6169-6fc1-9ed78399b306@slackbuilds.org>
References: <a0d1997c-6b7d-6169-6fc1-9ed78399b306@slackbuilds.org>
Message-ID: <a1877659-6a6d-4d2f-903e-2bed3c5af05d@www.fastmail.com>

Hello,

On Sun, 18 Aug 2019, at 04:17, Willy Sudiarto Raharjo wrote:
> development/portaudio: Updated for version v190600_20161030.

For me it fails:

-----
...
mv -f .deps/StreamParameters.Tpo .deps/StreamParameters.Plo
mv -f .deps/SystemDeviceIterator.Tpo .deps/SystemDeviceIterator.Plo
mv -f .deps/SystemHostApiIterator.Tpo .deps/SystemHostApiIterator.Plo
mv -f .deps/System.Tpo .deps/System.Plo
make[2]: Leaving directory '/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp/lib'
Makefile:431: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp'
Makefile:251: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 2
make: *** Waiting for unfinished jobs....
-----

Is it just me?

Best regards,
Alexander

From emmanueln at gmail.com  Sun Aug 18 13:42:38 2019
From: emmanueln at gmail.com (Emmanuel)
Date: Sun, 18 Aug 2019 10:42:38 -0300
Subject: [Slackbuilds-users] openmpi request
In-Reply-To: <e55be074-3d25-0721-9a29-138b9c3741b4@online.be>
References: <f9a95d21-deae-b582-6190-25ba999af2eb@online.be>
 <20190725030431.2fd1c0e9@home.rlworkman.net>
 <CAFhPZZfZYdj8WKRZgzT+AUwAzCe+PL-qPFX+=yybJjUUZ2LHxQ@mail.gmail.com>
 <e55be074-3d25-0721-9a29-138b9c3741b4@online.be>
Message-ID: <CAFhPZZdn=Qr7WBF4bvqQ7BHuai6FOzyQppf-Ypk8SzNwe5657Q@mail.gmail.com>

Hi Karel, I've just updated the openmpi slackbuild.

The option --with-pmi=pmi2  was giving me the following errors:

checking if user requested PMI support... yes
checking for pmi.h in pmi2... not found
checking for pmi.h in pmi2/include... not found
checking for pmi.h in pmi2/include/slurm... not found
checking for libpmi in pmi2/lib... checking for libpmi in pmi2/lib64... not
found
checking for pmi2.h in pmi2... not found
checking for pmi2.h in pmi2/include... not found
checking for pmi2.h in pmi2/include/slurm... not found
checking for libpmi2 in pmi2/lib... checking for libpmi2 in pmi2/lib64...
not found
checking for pmix.h in pmi2... not found
checking for pmix.h in pmi2/include... not found
checking can PMI support be built... no
configure: WARNING: PMI support requested (via --with-pmi) but neither
pmi.h,
configure: WARNING: pmi2.h or pmix.h were found under locations:
configure: WARNING:     pmi2
configure: WARNING:     pmi2/slurm
configure: WARNING: Specified path: pmi2
configure: WARNING: OR neither libpmi, libpmi2, or libpmix were found under:
configure: WARNING:     /lib
configure: WARNING:     /lib64
configure: WARNING: Specified path:
configure: error: Aborting

What version of slurm are you using?
I've added --with-slurm --with-pmix as optional dependencies to openmpi and
also updated slurm to the latest version.

Let me know if you find any more problems :-)

Best regards.




On Thu, Jul 25, 2019 at 12:54 PM Karel Venken <k.venken at online.be> wrote:

> Emmanuel wrote:
> >
> >
> > On Thu, Jul 25, 2019 at 5:04 AM Robby Workman
> > <rworkman at slackbuilds.org <mailto:rworkman at slackbuilds.org>> wrote:
> >
> >     On Thu, 25 Jul 2019 09:58:03 +0200
> >     Karel Venken <kava0418 at online.be <mailto:kava0418 at online.be>> wrote:
> >
> >     > Hi,
> >     >
> >     > For installing our cluster we need to add to the
> >     openmpi.Slackbuilds
> >     > with --with-pmi=pmi2 configure option. So it becomes:
> >     >
> >     > ./configure \
> >     >    --prefix=/usr \
> >     >    --sysconfdir=/etc \
> >     >    --localstatedir=/var/lib \
> >     >    --mandir=/usr/man/ \
> >     >    --enable-mpi1-compability \
> >     >    --docdir=/usr/doc/$PRGNAM-$VERSION \
> >     >    --disable-static \
> >     >    --libdir=/usr/lib${LIBDIRSUFFIX} \
> >     >    --build=$ARCH-slackware-linux \
> >     >    --with-pmi=pmi2
> >     >
> >     >
> >     > The background is to use mpi with slurm and a NUMA kernel - we
> build
> >     > it ourself. Without this parameter openmpi crashes. Would this be
> an
> >     > option?
> >
> >
> >     CCing SBo maintainer of openmpi; if there's no response and/or an
> >     update with that fixed within a few weeks, follow up with us and
> >     we'll handle it directly.
> >
> >     -RW
> >
> >
> > Hi Karel,
> >
> > I'm the maintainer of openmpi and slurm, let me try this parameter in
> > my cluster because we haven't had issues with the current package and
> > slurm (and also with several versions of openmpi, 1.8.x, 1.10.x,
> > 2.1.1). Can you send me the exact error? Have you modified the slurm
> > build script to add --with-pmi?  are you running mpirun in the slurm
> > submit job script or srun?
> >
> > In any case, I will submit a new version of the script in the next few
> > days.
> >
>
> Hi Emmanuel,
>
> Thanks for answering so soon. I added optional dependencies numactl
> hwloc and rrdtool to slurm and of course for building I set the
> environment with HWLOC=yes RRDTOOL=yes
>
> (We also integrate slurm with ganglia, but that's besides the point
> here, just to mention we activated rrdtool there as well)
>
> The error was produced by one of our applications warning about numa and
> then crashing/hanging at the mpi request. Everything then worked fine
> when we changed this compilation. (I have had a discussion in the
> slackware newsgroup about NUMA)
>
> I am sorry that I didn't keep the log of the application.
>
> FWW, to allow this application to use memory shared over different nodes
> we also had to recompile the kernel with NUMA option enabled (the stock
> kernel has it turned off, but, if I am correct, the current version has
> it activated)
>
> If this goes beyond what you can/want to investigate, that's OK. I am
> already thankful you want to give it a look. Anf, of course, if it is a
> problem in version 14.2, we 'll pick it up again if needed when a new
> version arrives.
>
> kind regards,
>
> Karel.
>
>
>
>
>
>
>
>

-- 
*****************
   Emmanuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190818/da139073/attachment-0001.htm>

From dpross1100 at msn.com  Sun Aug 18 14:22:22 2019
From: dpross1100 at msn.com (Daniel Prosser)
Date: Sun, 18 Aug 2019 14:22:22 +0000
Subject: [Slackbuilds-users] portaudio
In-Reply-To: <a1877659-6a6d-4d2f-903e-2bed3c5af05d@www.fastmail.com>
Message-ID: <CH2PR22MB205587D1355DC68E7C3B3464CCA90@CH2PR22MB2055.namprd22.prod.outlook.com>

I updated last night and it worked for me.

Dan

On Aug 18, 2019 9:37 AM, Alexander Verbovetsky <alik at ejik.org> wrote:

Hello,

On Sun, 18 Aug 2019, at 04:17, Willy Sudiarto Raharjo wrote:
> development/portaudio: Updated for version v190600_20161030.

For me it fails:

-----
...
mv -f .deps/StreamParameters.Tpo .deps/StreamParameters.Plo
mv -f .deps/SystemDeviceIterator.Tpo .deps/SystemDeviceIterator.Plo
mv -f .deps/SystemHostApiIterator.Tpo .deps/SystemHostApiIterator.Plo
mv -f .deps/System.Tpo .deps/System.Plo
make[2]: Leaving directory '/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp/lib'
Makefile:431: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp'
Makefile:251: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 2
make: *** Waiting for unfinished jobs....
-----

Is it just me?

Best regards,
Alexander
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


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

From willysr at slackbuilds.org  Sun Aug 18 14:31:01 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 18 Aug 2019 21:31:01 +0700
Subject: [Slackbuilds-users] portaudio
In-Reply-To: <a1877659-6a6d-4d2f-903e-2bed3c5af05d@www.fastmail.com>
References: <a0d1997c-6b7d-6169-6fc1-9ed78399b306@slackbuilds.org>
 <a1877659-6a6d-4d2f-903e-2bed3c5af05d@www.fastmail.com>
Message-ID: <1886a4e4-ab9a-3800-cd37-a406750860b4@slackbuilds.org>

>> development/portaudio: Updated for version v190600_20161030.
> 
> For me it fails:
> 
> -----
> ...
> mv -f .deps/StreamParameters.Tpo .deps/StreamParameters.Plo
> mv -f .deps/SystemDeviceIterator.Tpo .deps/SystemDeviceIterator.Plo
> mv -f .deps/SystemHostApiIterator.Tpo .deps/SystemHostApiIterator.Plo
> mv -f .deps/System.Tpo .deps/System.Plo
> make[2]: Leaving directory '/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp/lib'
> Makefile:431: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp'
> Makefile:251: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 2
> make: *** Waiting for unfinished jobs....
> -----
> 
> Is it just me?

I tested on 14.2 and current and it worked just fine


-- 
Willy Sudiarto Raharjo

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

From larryhaja at gmail.com  Sun Aug 18 21:01:41 2019
From: larryhaja at gmail.com (Larry Hajali)
Date: Sun, 18 Aug 2019 14:01:41 -0700
Subject: [Slackbuilds-users] ignition-transport fails to download
Message-ID: <CAAZPBMhm9FMKUVWKFNyk=9N8t_C0x_jkJOFtNMPbngDKQ6pbNQ@mail.gmail.com>

Hi All,

I tried building ignition-transport but got an md5sum error.  The actual
download seems to be an html file.

Found ignition-transport-0.7.0.tar.bz2 in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for ignition-transport-0.7.0.tar.bz2 ... FAILED!
    Expected: e7a69c622bf3145bdb7061f13eacd985
    Found:    fa26e8de4a0b0fe9980d89300222dd86


# file /var/cache/sbopkg/ignition-transport-0.7.0.tar.bz2
/var/cache/sbopkg/ignition-transport-0.7.0.tar.bz2: HTML document, ASCII
text

In the fedora spec file they use the following url.

https://osrf-distributions.s3.us-east-1.amazonaws.com/ign-transport/releases/ignition-transport-0.7.0.tar.bz2

Thanks,
--Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190818/477dc6d7/attachment.htm>

From sombragris at sombragris.org  Sun Aug 18 21:28:18 2019
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Sun, 18 Aug 2019 17:28:18 -0400
Subject: [Slackbuilds-users] Unstated REQUIRE for subtitleeditor
Message-ID: <qWxSq.81333b130e.20190818172818.28e074f8@loli.sombragris.org>

Hi there,

I run -current and use Ponce slackbuilds but I think this also applies
to 14.2 SBo so I post this on the list.
.
subtitleeditor 0.52.1 seems to require enchant2. Build failed at the
configure stage due to lack of that package.

After building enchant2, subtitleeditor built without problems.

I recommend updating the REQUIRES information to account for that
dependence.

Best regards,


Eduardo

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

From matteo.bernardini at gmail.com  Mon Aug 19 05:04:44 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 19 Aug 2019 07:04:44 +0200
Subject: [Slackbuilds-users] Unstated REQUIRE for subtitleeditor
In-Reply-To: <qWxSq.81333b130e.20190818172818.28e074f8@loli.sombragris.org>
References: <qWxSq.81333b130e.20190818172818.28e074f8@loli.sombragris.org>
Message-ID: <CAPsDuS7qzVJkP_dO7a1pQa=LHVRH+fW9iiQLaD9WkFjrzUNGcA@mail.gmail.com>

Il giorno dom 18 ago 2019 alle ore 23:29 Eduardo Sanchez
<sombragris at sombragris.org> ha scritto:
>
> Hi there,
>
> I run -current and use Ponce slackbuilds but I think this also applies
> to 14.2 SBo so I post this on the list.
> .
> subtitleeditor 0.52.1 seems to require enchant2. Build failed at the
> configure stage due to lack of that package.
>
> After building enchant2, subtitleeditor built without problems.
>
> I recommend updating the REQUIRES information to account for that
> dependence.
>
> Best regards,
>
>
> Eduardo

Hi Eduardo!

yes, enchant2 is a new dependency but only of the git snapshot of
subtitleeditor I upgraded to in my personal repository for current,
the version of SBo actually doesn't need it to build.
thanks for reporting it!

Matteo

From z.coldplayer at gmail.com  Mon Aug 19 08:27:34 2019
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Mon, 19 Aug 2019 12:27:34 +0400
Subject: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted
In-Reply-To: <31dbeb29-05d5-b2c4-5315-30df9960dc0d@gmail.com>
References: <88efcfe4-e0d2-106e-005a-2235b11fe6d5@gmail.com>
 <CAEWL1__ds2WqRVgJy6uy-RuxaTE2eYkEnghCd=nvKmRkDD+CNg@mail.gmail.com>
 <722fe724-637c-4a2b-c2a1-4fcf56eefc57@gmail.com>
 <CAEWL1_8eFeCmsoFxMSKbnrvGfaY2qOHcE4qUHRyojuFd86oX4A@mail.gmail.com>
 <31dbeb29-05d5-b2c4-5315-30df9960dc0d@gmail.com>
Message-ID: <CAEWL1_8Gd1z+HiN9qD0s4CV6SyLtXXRC=mNgdX5rR30YqvtyCg@mail.gmail.com>

Thanks for the information


Kool

On Sat, 17 Aug 2019 at 22:32, King Beowulf <kingbeowulf at gmail.com> wrote:

> On 8/17/19 8:05 AM, Jheengut Pritvi wrote:
> >
> >
> > On Fri, 16 Aug 2019 at 21:22, King Beowulf <kingbeowulf at gmail.com
> > <mailto:kingbeowulf at gmail.com>> wrote:
> >
> >     On 8/16/19 12:35 AM, Jheengut Pritvi wrote:
> >     > Hi,
> >     >
> >     > Do you mean changes about dropping support for non-GLVND libraries!
> >     >
> >     > https://devtalk.nvidia.com/default/topic/1060977
> >     >
> >     > My NVIDIA GPU's might be a bit old too, GTX840m.
> >     >
> >     > Cheers
> >     > Pritvi
> >     >
> >
> >     Yes, that was the announcement for the new beta driver. 435.17-beta
> >     still supports the GT[X] 8xx series GPUs.  The cutoff is the GTX 600
> >     series, and my spare cards are older than that. Yours is still "new"!
> >
> >     -Ed
> >
>
> >
> >  From this link , I found out what you mean.
> >
> > https://www.geforce.co.uk/drivers
> >
> >
> > thanks
> >
>
> I thought I was obvious, but ok.  Geforce.com is primarily for Windows
> users. These links are also more direct:
>
> https://www.nvidia.com/en-gb/drivers/unix/
> https://www.nvidia.com/en-gb/drivers/unix/linux-amd64-display-archive/
>
> https://www.nvidia.com/en-us/drivers/unix/
> https://www.nvidia.com/en-us/drivers/unix/linux-amd64-display-archive/
>
> And the primary support and news location is:
>
> https://devtalk.nvidia.com/
> https://devtalk.nvidia.com/default/board/98/linux/
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190819/acdb638d/attachment.htm>

From matteo.bernardini at gmail.com  Mon Aug 19 16:04:04 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 19 Aug 2019 18:04:04 +0200
Subject: [Slackbuilds-users] trac available for grabs
Message-ID: <CAPsDuS4va3ha8YJGHq6nsZ+XcN2OzVro1h3+KtPuJdhV1j+51w@mail.gmail.com>

Hi guys,

as I'm not using it since some time I'm dropping maintainership of
trac: if anybody wants to step in {,s}he's welcome.

Matteo

From jim.diamond at acadiau.ca  Mon Aug 19 19:19:57 2019
From: jim.diamond at acadiau.ca (James Diamond)
Date: Mon, 19 Aug 2019 19:19:57 +0000
Subject: [Slackbuilds-users] portaudio
In-Reply-To: <a1877659-6a6d-4d2f-903e-2bed3c5af05d@www.fastmail.com>
References: <a0d1997c-6b7d-6169-6fc1-9ed78399b306@slackbuilds.org>
 <a1877659-6a6d-4d2f-903e-2bed3c5af05d@www.fastmail.com>
Message-ID: <20190819191955.GB23502@jdiamond-mb.acadiau.ca>

On Sun, Aug 18, 2019 at 16:37 (+0300), Alexander Verbovetsky wrote:

> Hello,

> On Sun, 18 Aug 2019, at 04:17, Willy Sudiarto Raharjo wrote:
>> development/portaudio: Updated for version v190600_20161030.

> For me it fails:

> -----
> ...
> mv -f .deps/StreamParameters.Tpo .deps/StreamParameters.Plo
> mv -f .deps/SystemDeviceIterator.Tpo .deps/SystemDeviceIterator.Plo
> mv -f .deps/SystemHostApiIterator.Tpo .deps/SystemHostApiIterator.Plo
> mv -f .deps/System.Tpo .deps/System.Plo
> make[2]: Leaving directory '/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp/lib'
> Makefile:431: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp'
> Makefile:251: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 2
> make: *** Waiting for unfinished jobs....
> -----

> Is it just me?

Yes and no.

Try
        sboupgrade -j 1 portaudio
and see if that helps.

For me it fails with more than one compile job running at a time.
(Broken make file?)

Cheers
                        Jim

From alik at ejik.org  Mon Aug 19 20:39:28 2019
From: alik at ejik.org (Alexander Verbovetsky)
Date: Mon, 19 Aug 2019 23:39:28 +0300
Subject: [Slackbuilds-users] portaudio
In-Reply-To: <20190819191955.GB23502@jdiamond-mb.acadiau.ca>
References: <a0d1997c-6b7d-6169-6fc1-9ed78399b306@slackbuilds.org>
 <a1877659-6a6d-4d2f-903e-2bed3c5af05d@www.fastmail.com>
 <20190819191955.GB23502@jdiamond-mb.acadiau.ca>
Message-ID: <a3b7c4ee-301a-4c86-b88a-f6c9b5135ba5@www.fastmail.com>

> Try
>         sboupgrade -j 1 portaudio
> and see if that helps.
> 
> For me it fails with more than one compile job running at a time.

Yes, it is! Of course! Thank you very much!

I think the SlackBuild should be modified.

Best regards,
Alexander

From jim.diamond at acadiau.ca  Mon Aug 19 21:06:10 2019
From: jim.diamond at acadiau.ca (James Diamond)
Date: Mon, 19 Aug 2019 21:06:10 +0000
Subject: [Slackbuilds-users] portaudio
In-Reply-To: <a3b7c4ee-301a-4c86-b88a-f6c9b5135ba5@www.fastmail.com>
References: <a0d1997c-6b7d-6169-6fc1-9ed78399b306@slackbuilds.org>
 <a1877659-6a6d-4d2f-903e-2bed3c5af05d@www.fastmail.com>
 <20190819191955.GB23502@jdiamond-mb.acadiau.ca>
 <a3b7c4ee-301a-4c86-b88a-f6c9b5135ba5@www.fastmail.com>
Message-ID: <20190819210609.GA20050@jdiamond-mb.acadiau.ca>

On Mon, Aug 19, 2019 at 23:39 (+0300), Alexander Verbovetsky wrote:

>> Try
>> sboupgrade -j 1 portaudio
>> and see if that helps.

>> For me it fails with more than one compile job running at a time.

> Yes, it is! Of course! Thank you very much!

> I think the SlackBuild should be modified.

I agree 100%.  If you have 8 cores, you may as well use them.

                                Jim

From richard at aaazen.com  Wed Aug 21 22:51:46 2019
From: richard at aaazen.com (Richard Narron)
Date: Wed, 21 Aug 2019 15:51:46 -0700 (PDT)
Subject: [Slackbuilds-users] Webmin 1.920 is hacked at sourceforge.net
Message-ID: <alpine.LNX.2.20.1908211543300.18191@thursday.test>

The Webmin program is in the news as their sourceforge.net downloads were
hacked to include a back door with versions 1.822 through 1.920

  https://thehackernews.com/2019/08/webmin-vulnerability-hacking.html

There is a new version1.930 from github that is supposed to be good...

  https://github.com/webmin/webmin



From willysr at slackbuilds.org  Thu Aug 22 00:27:06 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 22 Aug 2019 07:27:06 +0700
Subject: [Slackbuilds-users] Webmin 1.920 is hacked at sourceforge.net
In-Reply-To: <alpine.LNX.2.20.1908211543300.18191@thursday.test>
References: <alpine.LNX.2.20.1908211543300.18191@thursday.test>
Message-ID: <8d176380-90ca-618d-57e7-16822a043bd9@slackbuilds.org>

> The Webmin program is in the news as their sourceforge.net downloads were
> hacked to include a back door with versions 1.822 through 1.920
> 
>   https://thehackernews.com/2019/08/webmin-vulnerability-hacking.html
> 
> There is a new version1.930 from github that is supposed to be good...
> 
>   https://github.com/webmin/webmin

it has been updated in my branch


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Sat Aug 24 00:15:48 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Aug 2019 07:15:48 +0700
Subject: [Slackbuilds-users] ignition-transport fails to download
In-Reply-To: <CAAZPBMhm9FMKUVWKFNyk=9N8t_C0x_jkJOFtNMPbngDKQ6pbNQ@mail.gmail.com>
References: <CAAZPBMhm9FMKUVWKFNyk=9N8t_C0x_jkJOFtNMPbngDKQ6pbNQ@mail.gmail.com>
Message-ID: <5a563c04-3ac4-b69c-bb47-b05e9b58e6f0@slackbuilds.org>

> I tried building ignition-transport but got an md5sum error.? The actual
> download seems to be an html file.
> 
> Found ignition-transport-0.7.0.tar.bz2 in /var/cache/sbopkg.
> Checking MD5SUM:
> ? MD5SUM check for ignition-transport-0.7.0.tar.bz2 ... FAILED!
> ? ? Expected: e7a69c622bf3145bdb7061f13eacd985
> ? ? Found: ? ?fa26e8de4a0b0fe9980d89300222dd86
> 
> 
> # file /var/cache/sbopkg/ignition-transport-0.7.0.tar.bz2
> /var/cache/sbopkg/ignition-transport-0.7.0.tar.bz2: HTML document, ASCII
> text
> 
> In the fedora spec file they use the following url.
> 
> https://osrf-distributions.s3.us-east-1.amazonaws.com/ign-transport/releases/ignition-transport-0.7.0.tar.bz2

Thanks
i have fixed it in my branch


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Sat Aug 24 01:36:28 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Aug 2019 08:36:28 +0700
Subject: [Slackbuilds-users] Updates - 20190824.1
Message-ID: <0df19576-60da-0fa5-6a84-0383db9eca83@slackbuilds.org>

Sat Aug 24 01:25:40 UTC 2019
audio/eyeD3: Updated for version 0.8.10
audio/mixx: Remove dep (included in Slackware).
audio/opus-tools: Updated for version 0.2.
desktop/i3: Updated for version 4.17.
desktop/i3status: Updated for version 2.13.
desktop/qtpass: Updated for version 1.3.0.
development/Fennel: Added (Lisp dialect that compiles to Lua).
development/Sphinx: Updated for version 2.2.0.
development/android-studio: Added missing file.
development/android-studio: Updated for version 3.5.0_191.5791312>
development/colm: Updated for version 0.13.0.7.
development/dart: Updated for version 2.4.1.
development/glm: Updated for version 0.9.9.5.
development/hopper: Updated for version 4.5.14.
development/jupyter-notebook: Updated for version 6.0.1.
development/kotlin: Updated for version 1.3.50.
development/obnc-libext: Updated for version 0.6.1.
development/obnc: Updated for version 0.15.2.
development/ragel: Updated for version 7.0.0.12.
development/vscode-bin: Updated for version 1.37.1.
games/dustrac: Updated for version 2.0.3
games/etlegacy: Updated for version 2.76.
games/puNES: Updated for version 0.105.
games/solarus-quest-editor: Updated for version 1.6.1.
games/solarus: Updated for version 1.6.1.
games/zbom: Added (Zelda fangame for the solarus engine).
games/zelda-roth-se: Updated for version 1.2.1.
games/zelda-xd2-mercuris-chess: Added (Parodic Zelda fangame).
games/zsdx: Updated for version 1.12.2.
games/zsxd: Updated for version 1.12.2.
gis/basemap: Updated for version 1.2.1.
gis/python3-basemap: Updated for version 1.2.1.
graphics/libplacebo: Fix build with SPIRV-Tools.
graphics/openimageio: Fix MD5SUM
ham/csdr: Added (DSP Library).
ham/inspectrum: Added (offline radio signal analyser).
libraries/GitPython: Updated for version 3.0.2.
libraries/grpc: Added (High performance general RPC framework).
libraries/ignition-transport: Update DOWNLOAD url.
libraries/libcacard: Updated for version 2.7.0.
libraries/libev: Updated for version 4.27.
libraries/libgee: Updated for version 0.20.2.
libraries/liblo: Updated for version 0.30.
libraries/libosinfo: Updated for version 1.6.0.
libraries/libstatgrab: Updated for version 0.92, cleanups.
libraries/libwebp: Updated for version 1.0.3.
libraries/lua-posix: Added (Lua bindings for POSIX).
libraries/lua-readline: Added (Interface to the readline library).
libraries/lua-std._debug: Added (Debug Hints Library).
libraries/lua-std.normalize: Added (Normalized Lua Functions).
libraries/lxqt-build-tools: Updated for version 0.6.0.
libraries/png++: Updated for version 0.2.10.
libraries/qtermwidget: Updated for version 0.14.1.
libraries/quazip-qt5: Updated for version 0.8.1.
libraries/quazip: Updated for version 0.8.1.
libraries/tinyxml2: Updated for version 7.1.0
libraries/wxsvg: Updated for version 1.5.20.
multimedia/avidemux: Updated for version 2.7.4.
multimedia/dvdstyler: Updated for version 3.1.2.
multimedia/freshplayerplugin: Updated for version 0.3.11.
multimedia/plexmediaserver: Updated for v 1.16.4.1469_6d5612c2f.
multimedia/smtube: Updated for version 19.6.0.
multimedia/vivaldi-codecs-ffmpeg-extra: Updated for v 76.0.3809.100.
multimedia/vlc: Updated for version 3.0.8
network/courier-unicode: Updated for version 2.1.
network/ettercap: Updated for version 0.8.3.
network/liferea: Updated for version 1.12.7.
network/maildrop: Updated for version 3.0.0.
network/modemu2k: Updated for version 0.0.5.
network/opensmtpd-extras: Added (backends for OpenSMTPD tables).
network/redir: Updated for version 3.3, changed homepage.
network/slurm: Updated for version 19.05.2.
network/socat: Updated for version 1.7.3.3
network/speedtest-cli: Updated for version 2.1.2.
network/telegram: Updated for version 1.8.2.
network/ubertooth: Added (wireless development platform).
network/vivaldi: Updated for version 2.7.1628.30.
network/vnstat: Updated for version 2.4.
office/kmymoney: Updated for version 4.8.4.
office/texmacs: Updated for version 1.99.11.
perl/perl-AnyEvent: Updated for version 7.16.
python/Markdown: Updated for version 2.6.11.
python/odict: Added (ordered dictionary).
python/python-odict: Removed (replaced with odict).
python/python3-lazy-object-proxy: Updated for version 1.4.2.
python/typing: Updated for version 3.7.4.1.
system/aide: Updated for version 0.16.2.
system/android-file-transfer: Updated for version 3.9.
system/clamav: Updated for version 0.101.4.
system/epson-inkjet-printer-escpr: Updated for version 1.7.2.
system/fzf: Simplify using bash/zsh keybindings.
system/keybase: Updated for version 4.3.2.
system/kyotocabinet: Updated for version 1.2.77.
system/letsencrypt: Updated for version 0.37.2.
system/modules: Updated for version 4.3.0.
system/openmpi: Added new option.
system/osinfo-db-tools: Updated for version 1.6.0.
system/osinfo-db: Updated for version 20190805.
system/qemu: Updated for version 4.1.0.
system/qterminal: Updated for version 0.14.1.
system/sysdig: Updated for version 0.26.2
system/usermin: Updated for version 1.780.
system/webmin: Updated for version 1.930.
system/wine: Updated for version 4.0.2.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From alik at ejik.org  Sat Aug 24 02:15:09 2019
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 24 Aug 2019 05:15:09 +0300
Subject: [Slackbuilds-users] fontforge
Message-ID: <81dd4809-952c-4665-bf93-736232de9e32@www.fastmail.com>

Hello,

One of sources for fontforge is
http://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.10.0.tar.lz

It doesn't exist, now it's:
https://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.10.1.tar.xz

Best regards,
Alexander

From molbolom at gmail.com  Sat Aug 24 02:16:58 2019
From: molbolom at gmail.com (Bolom Stzo')
Date: Fri, 23 Aug 2019 21:16:58 -0500
Subject: [Slackbuilds-users] Giving up on my Slackbuilds
Message-ID: <CAPfNs2ShUHvM5D3kLyQgG+EcA9XWAYKN5hb9+Vt=ONJ2Rk2MAA@mail.gmail.com>

Health has been getting much worse, and I'm having too many difficulties
with concentration, so I'm letting my stuff go to work on things I'm still
good at, heh.


Anyway:

system/vifm (Has an update and I haven't been able to fully comprehend the
documentation on what the sixel library inclusion does. Maybe it's just
because I use urxvt, as I did find out it doesn't work with it).
academic/equalx (Hasn't been updated in a while, but in a pinch, it's still
very handy).
desktop/echinus (Has not been updated since 2011. I'd say just get rid of
it).

Well, if no one takes vifm, I still rely on that heavily, so I'll keep it
up to date (I can still code. Just don't ask me to explain anything, heh).

Anyway, thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190823/3cfe7c8e/attachment.htm>

From alleytrotter at gmail.com  Sat Aug 24 04:03:51 2019
From: alleytrotter at gmail.com (John Yost)
Date: Sat, 24 Aug 2019 00:03:51 -0400
Subject: [Slackbuilds-users] Qemu-4.1.0
Message-ID: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>

The slackbuild fails for me with:

contrib/vhost-user-gpu/vugbm.c: In function 'map_bo':
contrib/vhost-user-gpu/vugbm.c:161:17: warning: implicit declaration of
function 'gbm_bo_map' [-Wimplicit-function-declaration]
     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
                 ^
contrib/vhost-user-gpu/vugbm.c:161:5: warning: nested extern declaration
of 'gbm_bo_map' [-Wnested-externs]
     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
     ^
contrib/vhost-user-gpu/vugbm.c:162:28: error:
'GBM_BO_TRANSFER_READ_WRITE' undeclared (first use in this function)
                            GBM_BO_TRANSFER_READ_WRITE, &stride,
                            ^
contrib/vhost-user-gpu/vugbm.c:162:28: note: each undeclared identifier
is reported only once for each function it appears in
contrib/vhost-user-gpu/vugbm.c: In function 'unmap_bo':
contrib/vhost-user-gpu/vugbm.c:173:5: warning: implicit declaration of
function 'gbm_bo_unmap' [-Wimplicit-function-declaration]
     gbm_bo_unmap(buf->bo, buf->mmap_data);
     ^
contrib/vhost-user-gpu/vugbm.c:173:5: warning: nested extern declaration
of 'gbm_bo_unmap' [-Wnested-externs]
/tmp/SBo/qemu-4.1.0/rules.mak:69: recipe for target
'contrib/vhost-user-gpu/vugbm.o' failed
make: *** [contrib/vhost-user-gpu/vugbm.o] Error 1

Any suggestions ?
Thanks in Advance
-- 
John David Yost
AlleyTrotter
pub   2048D/F3BDEB55 2014-05-23 [expires: Never]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x2C7AF6BEF3BDEB55.asc
Type: application/pgp-keys
Size: 2294 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190824/ce916171/attachment.bin>

From mrvladislavovich at gmail.com  Sat Aug 24 07:21:05 2019
From: mrvladislavovich at gmail.com (MyRequiem)
Date: Sat, 24 Aug 2019 11:21:05 +0400
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
Message-ID: <20190824072105.GA10378@slack.myrequiem.net>

Re: John Yost 24.08.2019 <a1a42c9b-0d3a-ec21-cfba-c48a9137310a at gmail.com>

I have the same problem (Slackware64 14.2)

>The slackbuild fails for me with:
>
>contrib/vhost-user-gpu/vugbm.c: In function 'map_bo':
>contrib/vhost-user-gpu/vugbm.c:161:17: warning: implicit declaration of
>function 'gbm_bo_map' [-Wimplicit-function-declaration]
>     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
>                 ^
>contrib/vhost-user-gpu/vugbm.c:161:5: warning: nested extern declaration
>of 'gbm_bo_map' [-Wnested-externs]
>     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
>     ^
>contrib/vhost-user-gpu/vugbm.c:162:28: error:
>'GBM_BO_TRANSFER_READ_WRITE' undeclared (first use in this function)
>                            GBM_BO_TRANSFER_READ_WRITE, &stride,
>                            ^
>contrib/vhost-user-gpu/vugbm.c:162:28: note: each undeclared identifier
>is reported only once for each function it appears in
>contrib/vhost-user-gpu/vugbm.c: In function 'unmap_bo':
>contrib/vhost-user-gpu/vugbm.c:173:5: warning: implicit declaration of
>function 'gbm_bo_unmap' [-Wimplicit-function-declaration]
>     gbm_bo_unmap(buf->bo, buf->mmap_data);
>     ^
>contrib/vhost-user-gpu/vugbm.c:173:5: warning: nested extern declaration
>of 'gbm_bo_unmap' [-Wnested-externs]
>/tmp/SBo/qemu-4.1.0/rules.mak:69: recipe for target
>'contrib/vhost-user-gpu/vugbm.o' failed
>make: *** [contrib/vhost-user-gpu/vugbm.o] Error 1
>
>Any suggestions ?
>Thanks in Advance
>-- 
>John David Yost
>AlleyTrotter
>pub   2048D/F3BDEB55 2014-05-23 [expires: Never]


>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
>


From matteo.bernardini at gmail.com  Sat Aug 24 08:51:59 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 24 Aug 2019 10:51:59 +0200
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <20190824072105.GA10378@slack.myrequiem.net>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
Message-ID: <CAPsDuS4ZDBEJc4H=WdAf+EECPWyQviLMPKn03BsYYoBmGnXoeg@mail.gmail.com>

Il giorno sab 24 ago 2019 alle ore 09:21 MyRequiem
<mrvladislavovich at gmail.com> ha scritto:
>
> Re: John Yost 24.08.2019 <a1a42c9b-0d3a-ec21-cfba-c48a9137310a at gmail.com>
>
> I have the same problem (Slackware64 14.2)
>
> >The slackbuild fails for me with:
> >
> >contrib/vhost-user-gpu/vugbm.c: In function 'map_bo':
> >contrib/vhost-user-gpu/vugbm.c:161:17: warning: implicit declaration of
> >function 'gbm_bo_map' [-Wimplicit-function-declaration]
> >     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
> >                 ^
> >contrib/vhost-user-gpu/vugbm.c:161:5: warning: nested extern declaration
> >of 'gbm_bo_map' [-Wnested-externs]
> >     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
> >     ^
> >contrib/vhost-user-gpu/vugbm.c:162:28: error:
> >'GBM_BO_TRANSFER_READ_WRITE' undeclared (first use in this function)
> >                            GBM_BO_TRANSFER_READ_WRITE, &stride,
> >                            ^
> >contrib/vhost-user-gpu/vugbm.c:162:28: note: each undeclared identifier
> >is reported only once for each function it appears in
> >contrib/vhost-user-gpu/vugbm.c: In function 'unmap_bo':
> >contrib/vhost-user-gpu/vugbm.c:173:5: warning: implicit declaration of
> >function 'gbm_bo_unmap' [-Wimplicit-function-declaration]
> >     gbm_bo_unmap(buf->bo, buf->mmap_data);
> >     ^
> >contrib/vhost-user-gpu/vugbm.c:173:5: warning: nested extern declaration
> >of 'gbm_bo_unmap' [-Wnested-externs]
> >/tmp/SBo/qemu-4.1.0/rules.mak:69: recipe for target
> >'contrib/vhost-user-gpu/vugbm.o' failed
> >make: *** [contrib/vhost-user-gpu/vugbm.o] Error 1
> >
> >Any suggestions ?
> >Thanks in Advance
> >--
> >John David Yost
> >AlleyTrotter

I think this happens because of the introduction of vhost-user-gpu

https://patchwork.kernel.org/cover/10941551/

this seems to require a newer version of the gbm library (part of
mesa) than the one shipped with 14.2.

Matteo

From duncan_roe at optusnet.com.au  Sat Aug 24 09:22:32 2019
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sat, 24 Aug 2019 19:22:32 +1000
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <20190824072105.GA10378@slack.myrequiem.net>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
Message-ID: <20190824092232.GB21783@dimstar.local.net>

On Sat, Aug 24, 2019 at 11:21:05AM +0400, MyRequiem wrote:
> Re: John Yost 24.08.2019 <a1a42c9b-0d3a-ec21-cfba-c48a9137310a at gmail.com>
>
> I have the same problem (Slackware64 14.2)
>
> >The slackbuild fails for me with:
> >
> >contrib/vhost-user-gpu/vugbm.c: In function 'map_bo':
> >contrib/vhost-user-gpu/vugbm.c:161:17: warning: implicit declaration of
> >function 'gbm_bo_map' [-Wimplicit-function-declaration]
> >     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
> >                 ^
> >contrib/vhost-user-gpu/vugbm.c:161:5: warning: nested extern declaration
> >of 'gbm_bo_map' [-Wnested-externs]
> >     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
> >     ^
> >contrib/vhost-user-gpu/vugbm.c:162:28: error:
> >'GBM_BO_TRANSFER_READ_WRITE' undeclared (first use in this function)
> >                            GBM_BO_TRANSFER_READ_WRITE, &stride,
> >                            ^
> >contrib/vhost-user-gpu/vugbm.c:162:28: note: each undeclared identifier
> >is reported only once for each function it appears in
> >contrib/vhost-user-gpu/vugbm.c: In function 'unmap_bo':
> >contrib/vhost-user-gpu/vugbm.c:173:5: warning: implicit declaration of
> >function 'gbm_bo_unmap' [-Wimplicit-function-declaration]
> >     gbm_bo_unmap(buf->bo, buf->mmap_data);
> >     ^
> >contrib/vhost-user-gpu/vugbm.c:173:5: warning: nested extern declaration
> >of 'gbm_bo_unmap' [-Wnested-externs]
> >/tmp/SBo/qemu-4.1.0/rules.mak:69: recipe for target
> >'contrib/vhost-user-gpu/vugbm.o' failed
> >make: *** [contrib/vhost-user-gpu/vugbm.o] Error 1
> >
> >Any suggestions ?
> >Thanks in Advance
> >--
> >John David Yost
> >AlleyTrotter
> >pub   2048D/F3BDEB55 2014-05-23 [expires: Never]
>
The missing gbm_bo_map() and GBM_BO_TRANSFER_READ_WRITE are satisfied by a newer
version of mesa than comes with 14.2 (or Current which has the same version of
mesa)

I don't have time to pursue this further at present :(

Cheers ... Duncan.

From willysr at slackbuilds.org  Sat Aug 24 12:42:25 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Aug 2019 19:42:25 +0700
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <20190824092232.GB21783@dimstar.local.net>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
 <20190824092232.GB21783@dimstar.local.net>
Message-ID: <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>

>> I have the same problem (Slackware64 14.2)
>>
>>> The slackbuild fails for me with:
>>>
>>> contrib/vhost-user-gpu/vugbm.c: In function 'map_bo':
>>> contrib/vhost-user-gpu/vugbm.c:161:17: warning: implicit declaration of
>>> function 'gbm_bo_map' [-Wimplicit-function-declaration]
>>>     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
>>>                 ^
>>> contrib/vhost-user-gpu/vugbm.c:161:5: warning: nested extern declaration
>>> of 'gbm_bo_map' [-Wnested-externs]
>>>     buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
>>>     ^
>>> contrib/vhost-user-gpu/vugbm.c:162:28: error:
>>> 'GBM_BO_TRANSFER_READ_WRITE' undeclared (first use in this function)
>>>                            GBM_BO_TRANSFER_READ_WRITE, &stride,
>>>                            ^
>>> contrib/vhost-user-gpu/vugbm.c:162:28: note: each undeclared identifier
>>> is reported only once for each function it appears in
>>> contrib/vhost-user-gpu/vugbm.c: In function 'unmap_bo':
>>> contrib/vhost-user-gpu/vugbm.c:173:5: warning: implicit declaration of
>>> function 'gbm_bo_unmap' [-Wimplicit-function-declaration]
>>>     gbm_bo_unmap(buf->bo, buf->mmap_data);
>>>     ^
>>> contrib/vhost-user-gpu/vugbm.c:173:5: warning: nested extern declaration
>>> of 'gbm_bo_unmap' [-Wnested-externs]
>>> /tmp/SBo/qemu-4.1.0/rules.mak:69: recipe for target
>>> 'contrib/vhost-user-gpu/vugbm.o' failed
>>> make: *** [contrib/vhost-user-gpu/vugbm.o] Error 1
>>>
>>> Any suggestions ?
>>> Thanks in Advance
>>> --
>>> John David Yost
>>> AlleyTrotter
>>> pub   2048D/F3BDEB55 2014-05-23 [expires: Never]
>>
> The missing gbm_bo_map() and GBM_BO_TRANSFER_READ_WRITE are satisfied by a newer
> version of mesa than comes with 14.2 (or Current which has the same version of
> mesa)
> 
> I don't have time to pursue this further at present :(

I have just tested in my 14.2 VM and it built fine

SDL2:
  MD5SUM check for SDL2-2.0.9.tar.gz ... OK
  Building package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK
  Installing package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK

qemu:
  MD5SUM check for qemu-4.1.0.tar.xz ... OK
  Building package qemu-4.1.0-x86_64-1_SBo.tgz ... OK
  Installing package qemu-4.1.0-x86_64-1_SBo.tgz ... OK


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190824/070d7efd/attachment-0001.asc>

From atelszewski at gmail.com  Sat Aug 24 13:26:04 2019
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 24 Aug 2019 15:26:04 +0200
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
 <20190824092232.GB21783@dimstar.local.net>
 <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>
Message-ID: <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>

On 24/08/2019 14:42, Willy Sudiarto Raharjo wrote:
>> The missing gbm_bo_map() and GBM_BO_TRANSFER_READ_WRITE are satisfied by a newer
>> version of mesa than comes with 14.2 (or Current which has the same version of
>> mesa)
>>
>> I don't have time to pursue this further at present :(
> I have just tested in my 14.2 VM and it built fine
> 
> SDL2:
>    MD5SUM check for SDL2-2.0.9.tar.gz ... OK
>    Building package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK
>    Installing package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK
> 
> qemu:
>    MD5SUM check for qemu-4.1.0.tar.xz ... OK
>    Building package qemu-4.1.0-x86_64-1_SBo.tgz ... OK
>    Installing package qemu-4.1.0-x86_64-1_SBo.tgz ... OK
> 
> 
> -- Willy Sudiarto Raharjo

Hi,

Did you install any additional deps?

My wild guess is that if one of /spice/ or /virglrenderer/ is installed 
then the build will fail.

Haven't tested it though.

-- 
Best regards,
Andrzej Telszewski

From jdashiel at panix.com  Sat Aug 24 13:42:44 2019
From: jdashiel at panix.com (Jude DaShiell)
Date: Sat, 24 Aug 2019 09:42:44 -0400
Subject: [Slackbuilds-users] cclive build failure
Message-ID: <alpine.NEB.2.21.1908240935030.9598@panix1.panix.com>

Failure happens near end of build when the build system can't find the
quvi andlibquvi files.  Before trying to build cclive, if I remember
properly I installed all dependencies.  The typescript file is very long
and I really would like to find out how to clean all the stuff out of
typescript files that isn't ascii before putting any more of them on the
internet.  Unless maybe tee or y could be used but I need to learn how to
do that.



--


From mrvladislavovich at gmail.com  Sat Aug 24 13:48:16 2019
From: mrvladislavovich at gmail.com (MyRequiem)
Date: Sat, 24 Aug 2019 17:48:16 +0400
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
 <20190824092232.GB21783@dimstar.local.net>
 <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>
 <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>
Message-ID: <20190824134816.GA12342@slack.myrequiem.net>

Re: Andrzej Telszewski 24.08.2019 <5abccafb-cf90-5f36-5679-8faa4938952c at gmail.com>
>On 24/08/2019 14:42, Willy Sudiarto Raharjo wrote:
>> > The missing gbm_bo_map() and GBM_BO_TRANSFER_READ_WRITE are satisfied by a newer
>> > version of mesa than comes with 14.2 (or Current which has the same version of
>> > mesa)
>> > 
>> > I don't have time to pursue this further at present :(
>> I have just tested in my 14.2 VM and it built fine
>> 
>> SDL2:
>>    MD5SUM check for SDL2-2.0.9.tar.gz ... OK
>>    Building package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK
>>    Installing package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK
>> 
>> qemu:
>>    MD5SUM check for qemu-4.1.0.tar.xz ... OK
>>    Building package qemu-4.1.0-x86_64-1_SBo.tgz ... OK
>>    Installing package qemu-4.1.0-x86_64-1_SBo.tgz ... OK
>> 
>> 
>> -- Willy Sudiarto Raharjo
>
>Hi,
>
>Did you install any additional deps?
>
>My wild guess is that if one of /spice/ or /virglrenderer/ is installed then
>the build will fail.
>
>Haven't tested it though.
>
>-- 
>Best regards,
>Andrzej Telszewski
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
>

Yes, I removed the 'spice' and 'virglrenderer' packages (SBo repository)
at build time and the build 'quemu' was successful.
Something needs to be done with this:)

From alleytrotter at gmail.com  Sat Aug 24 13:49:00 2019
From: alleytrotter at gmail.com (John Yost)
Date: Sat, 24 Aug 2019 09:49:00 -0400
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
 <20190824092232.GB21783@dimstar.local.net>
 <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>
 <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>
Message-ID: <ff1064cd-50df-0582-54f5-43baa99648ae@gmail.com>

On 8/24/19 9:26 AM, Andrzej Telszewski wrote:
> On 24/08/2019 14:42, Willy Sudiarto Raharjo wrote:
>>> The missing gbm_bo_map() and GBM_BO_TRANSFER_READ_WRITE are satisfied
>>> by a newer
>>> version of mesa than comes with 14.2 (or Current which has the same
>>> version of
>>> mesa)
>>>
>>> I don't have time to pursue this further at present :(
>> I have just tested in my 14.2 VM and it built fine
>>
>> SDL2:
>> ?? MD5SUM check for SDL2-2.0.9.tar.gz ... OK
>> ?? Building package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK
>> ?? Installing package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK
>>
>> qemu:
>> ?? MD5SUM check for qemu-4.1.0.tar.xz ... OK
>> ?? Building package qemu-4.1.0-x86_64-1_SBo.tgz ... OK
>> ?? Installing package qemu-4.1.0-x86_64-1_SBo.tgz ... OK
>>
>>
>> -- Willy Sudiarto Raharjo
> 
> Hi,
> 
> Did you install any additional deps?
> 
> My wild guess is that if one of /spice/ or /virglrenderer/ is installed
> then the build will fail.
> 
> Haven't tested it though.
> 

Your guess is correct. I removed both packages and Qemu-4.1.0 builds,
installs, and works as expected.
After reinstalling both packages (spice virglrenderer) qemu-4.1.0
appears to continue to function properly.
Thanks Andrzej

John

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x2C7AF6BEF3BDEB55.asc
Type: application/pgp-keys
Size: 2294 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190824/c721c54c/attachment.bin>

From willysr at slackbuilds.org  Sat Aug 24 13:49:24 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Aug 2019 20:49:24 +0700
Subject: [Slackbuilds-users] cclive build failure
In-Reply-To: <alpine.NEB.2.21.1908240935030.9598@panix1.panix.com>
References: <alpine.NEB.2.21.1908240935030.9598@panix1.panix.com>
Message-ID: <d4d421e7-ecb8-b632-95b1-812b63eaceee@slackbuilds.org>

> Failure happens near end of build when the build system can't find the
> quvi andlibquvi files.  Before trying to build cclive, if I remember
> properly I installed all dependencies.  The typescript file is very long
> and I really would like to find out how to clean all the stuff out of
> typescript files that isn't ascii before putting any more of them on the
> internet.  Unless maybe tee or y could be used but I need to learn how to
> do that.

Tested here and built fine

lua:
  MD5SUM check for lua-5.1.5.tar.gz ... OK
  Building package lua-5.1.5-x86_64-1_SBo.tgz ... OK
  Installing package lua-5.1.5-x86_64-1_SBo.tgz ... OK

luasocket:
  MD5SUM check for luasocket-3.0-rc1.tar.gz ... OK
  Building package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK
  Installing package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK

libquvi-scripts:
  MD5SUM check for libquvi-scripts-0.9.20131130.tar.xz ... OK
  Building package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK
  Installing package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK

libquvi:
  MD5SUM check for libquvi-0.9.4.tar.xz ... OK
  Building package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK
  Installing package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK

quvi:
  MD5SUM check for quvi-0.9.5.tar.xz ... OK
  Building package quvi-0.9.5-x86_64-1_SBo.tgz ... OK
  Installing package quvi-0.9.5-x86_64-1_SBo.tgz ... OK

cclive:
  MD5SUM check for cclive-0.9.3.tar.xz ... OK
  Building package cclive-0.9.3-x86_64-1_SBo.tgz ... OK
  Installing package cclive-0.9.3-x86_64-1_SBo.tgz ... OK


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Sat Aug 24 13:51:34 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Aug 2019 20:51:34 +0700
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <ff1064cd-50df-0582-54f5-43baa99648ae@gmail.com>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
 <20190824092232.GB21783@dimstar.local.net>
 <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>
 <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>
 <ff1064cd-50df-0582-54f5-43baa99648ae@gmail.com>
Message-ID: <0682b0de-d52b-b99d-7987-6e9967f546d4@slackbuilds.org>

>> My wild guess is that if one of /spice/ or /virglrenderer/ is installed
>> then the build will fail.
>>
>> Haven't tested it though.
>>
> 
> Your guess is correct. I removed both packages and Qemu-4.1.0 builds,
> installs, and works as expected.
> After reinstalling both packages (spice virglrenderer) qemu-4.1.0
> appears to continue to function properly.
> Thanks Andrzej

Send a cc to maintainer so he get noticed :)
hopely a workaround is available in the next public update or a simple
note in the README should do as well

-- 
Willy Sudiarto Raharjo

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

From matteo.bernardini at gmail.com  Sat Aug 24 14:08:44 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 24 Aug 2019 16:08:44 +0200
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <0682b0de-d52b-b99d-7987-6e9967f546d4@slackbuilds.org>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
 <20190824092232.GB21783@dimstar.local.net>
 <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>
 <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>
 <ff1064cd-50df-0582-54f5-43baa99648ae@gmail.com>
 <0682b0de-d52b-b99d-7987-6e9967f546d4@slackbuilds.org>
Message-ID: <CAPsDuS5ha+TEvArWF-qQpa0+sPyv-yB5vEtxJ+zzQHzcM0JXUA@mail.gmail.com>

I think qemu doesn't use the optional dependencies at all if it
doesn't build against them, so I don't think installing them after
building it is actually an option if you want, for example, spice or
virgl support in qemu...

From mrvladislavovich at gmail.com  Sat Aug 24 14:14:17 2019
From: mrvladislavovich at gmail.com (MyRequiem)
Date: Sat, 24 Aug 2019 18:14:17 +0400
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <0682b0de-d52b-b99d-7987-6e9967f546d4@slackbuilds.org>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
 <20190824092232.GB21783@dimstar.local.net>
 <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>
 <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>
 <ff1064cd-50df-0582-54f5-43baa99648ae@gmail.com>
 <0682b0de-d52b-b99d-7987-6e9967f546d4@slackbuilds.org>
Message-ID: <20190824141417.GA29643@slack.myrequiem.net>

Re: Willy Sudiarto Raharjo 24.08.2019 <0682b0de-d52b-b99d-7987-6e9967f546d4 at slackbuilds.org>
>>> My wild guess is that if one of /spice/ or /virglrenderer/ is installed
>>> then the build will fail.
>>>
>>> Haven't tested it though.
>>>
>> 
>> Your guess is correct. I removed both packages and Qemu-4.1.0 builds,
>> installs, and works as expected.
>> After reinstalling both packages (spice virglrenderer) qemu-4.1.0
>> appears to continue to function properly.
>> Thanks Andrzej
>
>Send a cc to maintainer so he get noticed :)
>hopely a workaround is available in the next public update or a simple
>note in the README should do as well
>
>-- 
>Willy Sudiarto Raharjo
>




>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
>

The 'virglrenderer' is to blame for everything (building quemu with
spice without any problems). If you build without spice, then we
can?t use the spice graphics either:
"spice graphics are not supported with this QEMU"

From jdashiel at panix.com  Sat Aug 24 15:25:57 2019
From: jdashiel at panix.com (Jude DaShiell)
Date: Sat, 24 Aug 2019 11:25:57 -0400
Subject: [Slackbuilds-users] cclive build failure
In-Reply-To: <d4d421e7-ecb8-b632-95b1-812b63eaceee@slackbuilds.org>
References: <alpine.NEB.2.21.1908240935030.9598@panix1.panix.com>
 <d4d421e7-ecb8-b632-95b1-812b63eaceee@slackbuilds.org>
Message-ID: <alpine.NEB.2.21.1908241123290.23422@panix1.panix.com>

It turns out I was missing a dependency, as soon as that got installed
cclive installed correctly.  It helps me with dependency lists to braille
those from time to time then check them off as I find things on
slackbuilds.org.

Fortunately adobe will discontinue flash I think in about 2 years.


-- 
-------------- next part --------------
> Failure happens near end of build when the build system can't find the
> quvi andlibquvi files.  Before trying to build cclive, if I remember
> properly I installed all dependencies.  The typescript file is very long
> and I really would like to find out how to clean all the stuff out of
> typescript files that isn't ascii before putting any more of them on the
> internet.  Unless maybe tee or y could be used but I need to learn how to
> do that.

Tested here and built fine

lua:
  MD5SUM check for lua-5.1.5.tar.gz ... OK
  Building package lua-5.1.5-x86_64-1_SBo.tgz ... OK
  Installing package lua-5.1.5-x86_64-1_SBo.tgz ... OK

luasocket:
  MD5SUM check for luasocket-3.0-rc1.tar.gz ... OK
  Building package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK
  Installing package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK

libquvi-scripts:
  MD5SUM check for libquvi-scripts-0.9.20131130.tar.xz ... OK
  Building package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK
  Installing package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK

libquvi:
  MD5SUM check for libquvi-0.9.4.tar.xz ... OK
  Building package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK
  Installing package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK

quvi:
  MD5SUM check for quvi-0.9.5.tar.xz ... OK
  Building package quvi-0.9.5-x86_64-1_SBo.tgz ... OK
  Installing package quvi-0.9.5-x86_64-1_SBo.tgz ... OK

cclive:
  MD5SUM check for cclive-0.9.3.tar.xz ... OK
  Building package cclive-0.9.3-x86_64-1_SBo.tgz ... OK
  Installing package cclive-0.9.3-x86_64-1_SBo.tgz ... OK


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190824/36d8beb5/attachment.asc>
-------------- next part --------------
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


From didier at slint.fr  Sat Aug 24 15:50:50 2019
From: didier at slint.fr (Didier Spaier)
Date: Sat, 24 Aug 2019 17:50:50 +0200
Subject: [Slackbuilds-users] cclive build failure
In-Reply-To: <alpine.NEB.2.21.1908241123290.23422@panix1.panix.com>
References: <alpine.NEB.2.21.1908240935030.9598@panix1.panix.com>
 <d4d421e7-ecb8-b632-95b1-812b63eaceee@slackbuilds.org>
 <alpine.NEB.2.21.1908241123290.23422@panix1.panix.com>
Message-ID: <32d22726-796f-8ce7-c828-d45c145ff4b7@slint.fr>

Hello Jude and all,

I just checked, cclive is already shipped in Slint.
Out of curiosity, why did you need to build it? for another
distribution?

Else you could have just used slapt-get to check:

root[/home/didier]# LANG=en_US.utf8 slapt-get --search cclive
cclive-0.9.3-x86_64-1slint [inst=yes]: cclive (flash video downloader)
root[/home/didier]#

Best,

Didier

On 24/08/2019 17:25, Jude DaShiell wrote:
> It turns out I was missing a dependency, as soon as that got installed
> cclive installed correctly.  It helps me with dependency lists to braille
> those from time to time then check them off as I find things on
> slackbuilds.org.
> 
> Fortunately adobe will discontinue flash I think in about 2 years.
> 
> 
> 
>> Failure happens near end of build when the build system can't find the
>> quvi andlibquvi files.  Before trying to build cclive, if I remember
>> properly I installed all dependencies.  The typescript file is very long
>> and I really would like to find out how to clean all the stuff out of
>> typescript files that isn't ascii before putting any more of them on the
>> internet.  Unless maybe tee or y could be used but I need to learn how to
>> do that.
> 
> Tested here and built fine
> 
> lua:
>    MD5SUM check for lua-5.1.5.tar.gz ... OK
>    Building package lua-5.1.5-x86_64-1_SBo.tgz ... OK
>    Installing package lua-5.1.5-x86_64-1_SBo.tgz ... OK
> 
> luasocket:
>    MD5SUM check for luasocket-3.0-rc1.tar.gz ... OK
>    Building package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK
>    Installing package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK
> 
> libquvi-scripts:
>    MD5SUM check for libquvi-scripts-0.9.20131130.tar.xz ... OK
>    Building package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK
>    Installing package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK
> 
> libquvi:
>    MD5SUM check for libquvi-0.9.4.tar.xz ... OK
>    Building package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK
>    Installing package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK
> 
> quvi:
>    MD5SUM check for quvi-0.9.5.tar.xz ... OK
>    Building package quvi-0.9.5-x86_64-1_SBo.tgz ... OK
>    Installing package quvi-0.9.5-x86_64-1_SBo.tgz ... OK
> 
> cclive:
>    MD5SUM check for cclive-0.9.3.tar.xz ... OK
>    Building package cclive-0.9.3-x86_64-1_SBo.tgz ... OK
>    Installing package cclive-0.9.3-x86_64-1_SBo.tgz ... OK
> 
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From willysr at slackbuilds.org  Sat Aug 24 17:02:17 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 25 Aug 2019 00:02:17 +0700
Subject: [Slackbuilds-users] fontforge
In-Reply-To: <81dd4809-952c-4665-bf93-736232de9e32@www.fastmail.com>
References: <81dd4809-952c-4665-bf93-736232de9e32@www.fastmail.com>
Message-ID: <25cceedd-e5a3-3972-88ad-6f65df2d6ff6@slackbuilds.org>

> One of sources for fontforge is
> http://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.10.0.tar.lz
> 
> It doesn't exist, now it's:
> https://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.10.1.tar.xz

Thanks
fixed in my branch


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190825/345f42a1/attachment-0001.asc>

From jdashiel at panix.com  Sat Aug 24 17:26:44 2019
From: jdashiel at panix.com (Jude DaShiell)
Date: Sat, 24 Aug 2019 13:26:44 -0400
Subject: [Slackbuilds-users] cclive build failure
In-Reply-To: <32d22726-796f-8ce7-c828-d45c145ff4b7@slint.fr>
References: <alpine.NEB.2.21.1908240935030.9598@panix1.panix.com>
 <d4d421e7-ecb8-b632-95b1-812b63eaceee@slackbuilds.org>
 <alpine.NEB.2.21.1908241123290.23422@panix1.panix.com>
 <32d22726-796f-8ce7-c828-d45c145ff4b7@slint.fr>
Message-ID: <alpine.NEB.2.21.1908241322500.17802@panix1.panix.com>

some of these packages fail on the fakeroot command line.  That recently
happened for me while trying to build android-file-transfer.  That could
have been why I built cclive from source with slackbuilds-recommended
build procedure.  I also found out the source package had its name
changed for android-file-transfer-3.9.tar.gz to
android-file-transfer-linux-3.9.tar.gz.  I renamed the source package to
conform to the SlackBuild script and the build went like a Swiss Watch.

On Sat, 24 Aug 2019, Didier Spaier wrote:

> Date: Sat, 24 Aug 2019 11:50:50
> From: Didier Spaier <didier at slint.fr>
> Reply-To: SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] cclive build failure
>
> Hello Jude and all,
>
> I just checked, cclive is already shipped in Slint.
> Out of curiosity, why did you need to build it? for another
> distribution?
>
> Else you could have just used slapt-get to check:
>
> root[/home/didier]# LANG=en_US.utf8 slapt-get --search cclive
> cclive-0.9.3-x86_64-1slint [inst=yes]: cclive (flash video downloader)
> root[/home/didier]#
>
> Best,
>
> Didier
>
> On 24/08/2019 17:25, Jude DaShiell wrote:
> > It turns out I was missing a dependency, as soon as that got installed
> > cclive installed correctly.  It helps me with dependency lists to braille
> > those from time to time then check them off as I find things on
> > slackbuilds.org.
> >
> > Fortunately adobe will discontinue flash I think in about 2 years.
> >
> >
> >
> >> Failure happens near end of build when the build system can't find the
> >> quvi andlibquvi files.  Before trying to build cclive, if I remember
> >> properly I installed all dependencies.  The typescript file is very long
> >> and I really would like to find out how to clean all the stuff out of
> >> typescript files that isn't ascii before putting any more of them on the
> >> internet.  Unless maybe tee or y could be used but I need to learn how to
> >> do that.
> >
> > Tested here and built fine
> >
> > lua:
> >    MD5SUM check for lua-5.1.5.tar.gz ... OK
> >    Building package lua-5.1.5-x86_64-1_SBo.tgz ... OK
> >    Installing package lua-5.1.5-x86_64-1_SBo.tgz ... OK
> >
> > luasocket:
> >    MD5SUM check for luasocket-3.0-rc1.tar.gz ... OK
> >    Building package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK
> >    Installing package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK
> >
> > libquvi-scripts:
> >    MD5SUM check for libquvi-scripts-0.9.20131130.tar.xz ... OK
> >    Building package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK
> >    Installing package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK
> >
> > libquvi:
> >    MD5SUM check for libquvi-0.9.4.tar.xz ... OK
> >    Building package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK
> >    Installing package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK
> >
> > quvi:
> >    MD5SUM check for quvi-0.9.5.tar.xz ... OK
> >    Building package quvi-0.9.5-x86_64-1_SBo.tgz ... OK
> >    Installing package quvi-0.9.5-x86_64-1_SBo.tgz ... OK
> >
> > cclive:
> >    MD5SUM check for cclive-0.9.3.tar.xz ... OK
> >    Building package cclive-0.9.3-x86_64-1_SBo.tgz ... OK
> >    Installing package cclive-0.9.3-x86_64-1_SBo.tgz ... OK
> >
> >
> >
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> >
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>

-- 


From z.coldplayer at gmail.com  Sat Aug 24 19:31:37 2019
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Sat, 24 Aug 2019 23:31:37 +0400
Subject: [Slackbuilds-users] Hacktoberfest 2019
In-Reply-To: <83c0cbd6-2239-9b48-728e-22e9356d0fca@slackbuilds.org>
References: <CAEWL1_-hSjC6nXQ43yVWTN6xDi2=ei6GY26nYQoavmrOK=xcWg@mail.gmail.com>
 <83c0cbd6-2239-9b48-728e-22e9356d0fca@slackbuilds.org>
Message-ID: <CAEWL1__G8HK=D=YxXk=4LS2u0hf=JsCCVaJBLRRNzF8vCus1pw@mail.gmail.com>

On Fri, 16 Aug 2019 at 17:17, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > I have been participating in Hacktoberfest organised by DigitalOcean and
> > Github.
> >
> > This year, I am organising some hackathon sessions during the month of
> > october in different
> > venues, including upcoming Google Devfest.
> >
> >
> > Would it be possible to use the Slackbuilds mirror repo on github.com
> > <http://github.com> for the Hacktoberfest?
> >
> > The idea is to make more people involve in Open Source, FLOSS.
>
> What are your plans for SBo?
>
>
> --
> Willy Sudiarto Raharjo
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
Hi Willy,

I am assuming you and the rest of the Slackbuild users are aware about the
Hacktoberfest and how
it is organised. If not, ping me, I'll try my best.

For a first, it is going to be difficult to find updates to many/most
packages. In this view, is to build a
list of Slackbuilds with no maintainers or those difficult to contact. If I
get a few Slackbuilds updated,
with no active maintainers would be cool.

Secondly, I would to test some rarely used Slackbuilds under different
environments.

I have already contacted some lecturers to use one of their session for a
hackathon.
I will target future System Administrators to become acquainted in the know
how of
building your own packages.

This is a bit of an idea what I can help through this hackathon.

Salutations,
Pritvi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190824/a4bed90a/attachment.htm>

From kingbeowulf at gmail.com  Sat Aug 24 20:55:40 2019
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 24 Aug 2019 13:55:40 -0700
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <20190824141417.GA29643@slack.myrequiem.net>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
 <20190824072105.GA10378@slack.myrequiem.net>
 <20190824092232.GB21783@dimstar.local.net>
 <4e35d828-3532-1e74-1a60-41fff8cf614c@slackbuilds.org>
 <5abccafb-cf90-5f36-5679-8faa4938952c@gmail.com>
 <ff1064cd-50df-0582-54f5-43baa99648ae@gmail.com>
 <0682b0de-d52b-b99d-7987-6e9967f546d4@slackbuilds.org>
 <20190824141417.GA29643@slack.myrequiem.net>
Message-ID: <19024668-39f1-121e-c583-5032e7012c6b@gmail.com>

On 8/24/19 7:14 AM, MyRequiem wrote:
...
> 
> The 'virglrenderer' is to blame for everything (building quemu with
> spice without any problems). If you build without spice, then we
> can?t use the spice graphics either:
> "spice graphics are not supported with this QEMU"


Thanks for the testing. my qemu VMs stay mainly in CLI and its not
possible for me to test all uses case scenarios.  Qemu devs also dn't
make it easy to figure out what's they are changing.  I really don't
feel like sifting through git logs!

there was a big virgl patchset approved just before 4.1.0, but so far I
don't see anything too odd.

I'll check it out soonest in a clean VM.  right now I need to check out
the Trek Dual Sport 1 I just got free via hotel loyalty points. Woot!
(or ugh I travel for work too much?)

-Ed

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

From willysr at slackbuilds.org  Sun Aug 25 00:05:13 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 25 Aug 2019 07:05:13 +0700
Subject: [Slackbuilds-users] Hacktoberfest 2019
In-Reply-To: <CAEWL1__G8HK=D=YxXk=4LS2u0hf=JsCCVaJBLRRNzF8vCus1pw@mail.gmail.com>
References: <CAEWL1_-hSjC6nXQ43yVWTN6xDi2=ei6GY26nYQoavmrOK=xcWg@mail.gmail.com>
 <83c0cbd6-2239-9b48-728e-22e9356d0fca@slackbuilds.org>
 <CAEWL1__G8HK=D=YxXk=4LS2u0hf=JsCCVaJBLRRNzF8vCus1pw@mail.gmail.com>
Message-ID: <670f941b-ac27-8650-7228-d7ccf384baca@slackbuilds.org>

> I am assuming you and the rest of the Slackbuild users are aware about
> the Hacktoberfest and how
> it is organised. If not, ping me, I'll try my best.
> 
> For a first, it is going to be difficult to find updates to many/most
> packages. In this view, is to build a
> list of Slackbuilds with no maintainers or those difficult to contact.
> If I get a few Slackbuilds updated,
> with no active maintainers would be cool.

You can start with scripts listed in pasture
https://git.slackbuilds.org/slackbuilds/log/?h=pasture

most (if not all) of it have no maintainers


-- 
Willy Sudiarto Raharjo

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

From kingbeowulf at gmail.com  Sun Aug 25 07:43:16 2019
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 25 Aug 2019 00:43:16 -0700
Subject: [Slackbuilds-users] Qemu-4.1.0
In-Reply-To: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
References: <a1a42c9b-0d3a-ec21-cfba-c48a9137310a@gmail.com>
Message-ID: <c419adde-7e1c-b304-b42e-7e65833c7035@gmail.com>

On 8/23/19 9:03 PM, John Yost wrote:
> The slackbuild fails for me with:
>...
>      
> contrib/vhost-user-gpu/vugbm.c:162:28: error:
> 'GBM_BO_TRANSFER_READ_WRITE' undeclared (first use in this function)
>                             GBM_BO_TRANSFER_READ_WRITE, &stride,
>                             ^


Well, the slackbuild is fine and qemu is fine.  The error above is
because 14.2's mesa-11.2.2 is too old.  qemu with virglrenderer expects
to use mesa's GBM (Graphics Buffer Manager) and gbm_bo_* is declared in
mesa source:

.../src/gbm/main/gbm.h

GBM_BO_TRANSFER_* etc were committed on May 3, 2016
but not added until release mesa-12.0.0

Either upgrade mesa (hint: Mako is required), upgrade to
Slackware-current or revert to an earlier qemu.

"not a bug - won't fix."


Admins,
Patch attached for the qemu README.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qemu_README-virgl.patch
Type: text/x-patch
Size: 481 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190825/b521f1b0/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190825/b521f1b0/attachment-0001.asc>

From z.coldplayer at gmail.com  Sun Aug 25 19:53:51 2019
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Sun, 25 Aug 2019 23:53:51 +0400
Subject: [Slackbuilds-users] Hacktoberfest 2019
In-Reply-To: <670f941b-ac27-8650-7228-d7ccf384baca@slackbuilds.org>
References: <CAEWL1_-hSjC6nXQ43yVWTN6xDi2=ei6GY26nYQoavmrOK=xcWg@mail.gmail.com>
 <83c0cbd6-2239-9b48-728e-22e9356d0fca@slackbuilds.org>
 <CAEWL1__G8HK=D=YxXk=4LS2u0hf=JsCCVaJBLRRNzF8vCus1pw@mail.gmail.com>
 <670f941b-ac27-8650-7228-d7ccf384baca@slackbuilds.org>
Message-ID: <CAEWL1_9bOf35Z0=kC9B_hXd1XgQgig5Rfvnjbg8Ujx=LXbP0GQ@mail.gmail.com>

Thanks

I will surely start here and try to convert people to Slackware.

Cheers
Pritvi

On Sun, 25 Aug 2019 at 04:05, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > I am assuming you and the rest of the Slackbuild users are aware about
> > the Hacktoberfest and how
> > it is organised. If not, ping me, I'll try my best.
> >
> > For a first, it is going to be difficult to find updates to many/most
> > packages. In this view, is to build a
> > list of Slackbuilds with no maintainers or those difficult to contact.
> > If I get a few Slackbuilds updated,
> > with no active maintainers would be cool.
>
> You can start with scripts listed in pasture
> https://git.slackbuilds.org/slackbuilds/log/?h=pasture
>
> most (if not all) of it have no maintainers
>
>
> --
> Willy Sudiarto Raharjo
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190825/f58663f0/attachment.htm>

From rshepard at appl-ecosys.com  Mon Aug 26 14:28:18 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Mon, 26 Aug 2019 07:28:18 -0700 (PDT)
Subject: [Slackbuilds-users] OpenJDK11/openJFX11 and JabRef5.x
Message-ID: <alpine.LNX.2.20.1908260722120.15370@salmo.appl-ecosys.com>

Several maintainers provide the packages involved with running JabRef so I'm
posting this to the mail list rather than to individuals.

I'm running JabRef-4.3.1 and had an issue with references from my database
not allowing a LyX document to compile. This was resolved by changing the
reference style because some bibtex .bst style files use deprecated font
commands, specifically \sc and \bf.

As I worked to resolve this issue I communicated with several JabRef
developers on the application's mail list and want to share what I've
learned because several SBo packages need revision. I discovered this need
because the JabRef devs asked me to test JabRef-5.x and it turns out I
cannot ... yet.

JabRef-5.x requires JDK11. Oracle has split this into parts so the JavaFK
part is now a separate package. A JabRef dev confirmed that it will run with
openjdk11 and openjfx11. The SBo repository has a zulu-openjdk11-11.0.1-lts
package, but the only openjfx package is version 8.

My request of the maintainers is to provide an openjfx package compatible
with the zulu-openjdk-11.0.1 package, or any other openjdk11/openjfx11 pair,
so JabRef on SBo can be upgraded from it's current very old version to 5.x.

For what it's worth, I've run JabRef-3.8.2 with openjdk8/openjfx8 and now
run -4.3.1 using Oracle's jdk8 (via the SBo package); I would prefer to use
open source versions of java.

Thanks in advance,

Rich






From didier at slint.fr  Tue Aug 27 22:56:58 2019
From: didier at slint.fr (Didier Spaier)
Date: Wed, 28 Aug 2019 00:56:58 +0200
Subject: [Slackbuilds-users] cclive build failure
In-Reply-To: <alpine.NEB.2.21.1908241322500.17802@panix1.panix.com>
References: <alpine.NEB.2.21.1908240935030.9598@panix1.panix.com>
 <d4d421e7-ecb8-b632-95b1-812b63eaceee@slackbuilds.org>
 <alpine.NEB.2.21.1908241123290.23422@panix1.panix.com>
 <32d22726-796f-8ce7-c828-d45c145ff4b7@slint.fr>
 <alpine.NEB.2.21.1908241322500.17802@panix1.panix.com>
Message-ID: <4f033c16-3ee1-de8a-053b-27a5b44d67c3@slint.fr>

Hello,

I just realized that I had compiled and installed cclive but not
uploaded this package to a Slint repository, so I understand now
why you needed to build it. Sorry for my misleading question.

Best,

Didier

On 8/24/19 7:26 PM, Jude DaShiell wrote:
> some of these packages fail on the fakeroot command line.  That recently
> happened for me while trying to build android-file-transfer.  That could
> have been why I built cclive from source with slackbuilds-recommended
> build procedure.  I also found out the source package had its name
> changed for android-file-transfer-3.9.tar.gz to
> android-file-transfer-linux-3.9.tar.gz.  I renamed the source package to
> conform to the SlackBuild script and the build went like a Swiss Watch.
> 
> On Sat, 24 Aug 2019, Didier Spaier wrote:
> 
>> Date: Sat, 24 Aug 2019 11:50:50
>> From: Didier Spaier <didier at slint.fr>
>> Reply-To: SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
>> To: slackbuilds-users at slackbuilds.org
>> Subject: Re: [Slackbuilds-users] cclive build failure
>>
>> Hello Jude and all,
>>
>> I just checked, cclive is already shipped in Slint.
>> Out of curiosity, why did you need to build it? for another
>> distribution?
>>
>> Else you could have just used slapt-get to check:
>>
>> root[/home/didier]# LANG=en_US.utf8 slapt-get --search cclive
>> cclive-0.9.3-x86_64-1slint [inst=yes]: cclive (flash video downloader)
>> root[/home/didier]#
>>
>> Best,
>>
>> Didier
>>
>> On 24/08/2019 17:25, Jude DaShiell wrote:
>>> It turns out I was missing a dependency, as soon as that got installed
>>> cclive installed correctly.  It helps me with dependency lists to braille
>>> those from time to time then check them off as I find things on
>>> slackbuilds.org.
>>>
>>> Fortunately adobe will discontinue flash I think in about 2 years.
>>>
>>>
>>>
>>>> Failure happens near end of build when the build system can't find the
>>>> quvi andlibquvi files.  Before trying to build cclive, if I remember
>>>> properly I installed all dependencies.  The typescript file is very long
>>>> and I really would like to find out how to clean all the stuff out of
>>>> typescript files that isn't ascii before putting any more of them on the
>>>> internet.  Unless maybe tee or y could be used but I need to learn how to
>>>> do that.
>>>
>>> Tested here and built fine
>>>
>>> lua:
>>>     MD5SUM check for lua-5.1.5.tar.gz ... OK
>>>     Building package lua-5.1.5-x86_64-1_SBo.tgz ... OK
>>>     Installing package lua-5.1.5-x86_64-1_SBo.tgz ... OK
>>>
>>> luasocket:
>>>     MD5SUM check for luasocket-3.0-rc1.tar.gz ... OK
>>>     Building package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK
>>>     Installing package luasocket-3.0_rc1-x86_64-1_SBo.tgz ... OK
>>>
>>> libquvi-scripts:
>>>     MD5SUM check for libquvi-scripts-0.9.20131130.tar.xz ... OK
>>>     Building package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK
>>>     Installing package libquvi-scripts-0.9.20131130-x86_64-1_SBo.tgz ... OK
>>>
>>> libquvi:
>>>     MD5SUM check for libquvi-0.9.4.tar.xz ... OK
>>>     Building package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK
>>>     Installing package libquvi-0.9.4-x86_64-1_SBo.tgz ... OK
>>>
>>> quvi:
>>>     MD5SUM check for quvi-0.9.5.tar.xz ... OK
>>>     Building package quvi-0.9.5-x86_64-1_SBo.tgz ... OK
>>>     Installing package quvi-0.9.5-x86_64-1_SBo.tgz ... OK
>>>
>>> cclive:
>>>     MD5SUM check for cclive-0.9.3.tar.xz ... OK
>>>     Building package cclive-0.9.3-x86_64-1_SBo.tgz ... OK
>>>     Installing package cclive-0.9.3-x86_64-1_SBo.tgz ... OK
>>>
>>>
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>>
> 

From hedgehog87 at hotmail.it  Wed Aug 28 10:36:19 2019
From: hedgehog87 at hotmail.it (Cristiano Urban)
Date: Wed, 28 Aug 2019 10:36:19 +0000
Subject: [Slackbuilds-users] Sphinx fails in GMT
Message-ID: <VI1PR02MB57741E5D41B9E0755756EE14B7A30@VI1PR02MB5774.eurprd02.prod.outlook.com>

Hi,
I've tried to build GMT on a clean Slackware VM and it fails near the end of the compilation procedure (see the attached file). I solved this issue by installing python3-attrs. After this, the GMT slack build builds correctly.

Should python3-attrs be added as Sphinx dependency? Or should I add a note on the GMT README, instead?

Thank you in advance for your time.

Best regards,
Cristiano Urban.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190828/3e141ee6/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: GMT_failure.txt
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190828/3e141ee6/attachment.txt>

From slackbuilds at jaxartes.net  Wed Aug 28 11:45:42 2019
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Wed, 28 Aug 2019 04:45:42 -0700
Subject: [Slackbuilds-users] Sphinx fails in GMT
In-Reply-To: <VI1PR02MB57741E5D41B9E0755756EE14B7A30@VI1PR02MB5774.eurprd02.prod.outlook.com>
References: <VI1PR02MB57741E5D41B9E0755756EE14B7A30@VI1PR02MB5774.eurprd02.prod.outlook.com>
Message-ID: <2390438.hWKNCZl7q8@wintermute.sprawl.net>

On Wednesday, 28 August 2019 03:36:19 PDT Cristiano Urban wrote:
> Hi,
> I've tried to build GMT on a clean Slackware VM and it fails near the end of
> the compilation procedure (see the attached file). I solved this issue by
> installing python3-attrs. After this, the GMT slack build builds
> correctly.
 
> Should python3-attrs be added as Sphinx dependency? Or should I add a note
> on the GMT README, instead?

This is a dependency-of-a-dependency issue. python3-attrs should be added as a 
dependency of python3-packaging, which I can take care of.
 
> Thank you in advance for your time.

Thanks for the report!

> Best regards,
> Cristiano Urban.
> 





From fellype at gmail.com  Wed Aug 28 15:12:53 2019
From: fellype at gmail.com (Fellype)
Date: Wed, 28 Aug 2019 12:12:53 -0300
Subject: [Slackbuilds-users] scikit-learn fails to build
Message-ID: <CAJJ5XvFp1zGEVduKduvp9_P21_E59v74-n+2oGuS0F3vsZc8Kw@mail.gmail.com>

Hi,
scikit-learn 0.21.3 fails to build on my system (Slackware 14.2, 64 bits).
I tried to rebuild the deps, but it still failing. The build errors are
below.
Did I miss something?


---------------------------
sklearn/utils/_cython_blas.pyx:203:43: Converting to Python object not
allowed without gil
Traceback (most recent call last):
  File "setup.py", line 290, in <module>
Compiling sklearn/utils/sparsefuncs_fast.pyx because it changed.
Compiling sklearn/utils/_cython_blas.pyx because it changed.
Compiling sklearn/utils/arrayfuncs.pyx because it changed.
Compiling sklearn/utils/murmurhash.pyx because it changed.
Compiling sklearn/utils/lgamma.pyx because it changed.
Compiling sklearn/utils/graph_shortest_path.pyx because it changed.
Compiling sklearn/utils/fast_dict.pyx because it changed.
Compiling sklearn/utils/seq_dataset.pyx because it changed.
Compiling sklearn/utils/weight_vector.pyx because it changed.
Compiling sklearn/utils/_random.pyx because it changed.
Compiling sklearn/utils/_logistic_sigmoid.pyx because it changed.
[ 1/11] Cythonizing sklearn/utils/_cython_blas.pyx
    setup_package()
  File "setup.py", line 286, in setup_package
    setup(**metadata)
  File "/usr/lib64/python3.7/site-packages/numpy/distutils/core.py", line
135, in setup
    config = configuration()
  File "setup.py", line 174, in configuration
    config.add_subpackage('sklearn')
  File "/usr/lib64/python3.7/site-packages/numpy/distutils/misc_util.py",
line 1024, in add_subpackage
    caller_level = 2)
  File "/usr/lib64/python3.7/site-packages/numpy/distutils/misc_util.py",
line 993, in get_subpackage
    caller_level = caller_level + 1)
  File "/usr/lib64/python3.7/site-packages/numpy/distutils/misc_util.py",
line 930, in _get_configuration_from_setup_py
    config = setup_module.configuration(*args)
  File "sklearn/setup.py", line 76, in configuration
    maybe_cythonize_extensions(top_path, config)
  File "/tmp/SBo/scikit-learn-0.21.3/sklearn/_build_utils/__init__.py",
line 66, in maybe_cythonize_extensions
    compiler_directives={'language_level': 3})
  File "/usr/lib64/python3.7/site-packages/Cython/Build/Dependencies.py",
line 1097, in cythonize
    cythonize_one(*args)
  File "/usr/lib64/python3.7/site-packages/Cython/Build/Dependencies.py",
line 1220, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: sklearn/utils/_cython_blas.pyx
Failures:
  scikit-learn: scikit-learn.SlackBuild return non-zero
bash-4.3#

-- 
Fellype
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190828/41bfa711/attachment.htm>

From slackbuilds at jaxartes.net  Wed Aug 28 15:47:51 2019
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Wed, 28 Aug 2019 08:47:51 -0700
Subject: [Slackbuilds-users] scikit-learn fails to build
In-Reply-To: <CAJJ5XvFp1zGEVduKduvp9_P21_E59v74-n+2oGuS0F3vsZc8Kw@mail.gmail.com>
References: <CAJJ5XvFp1zGEVduKduvp9_P21_E59v74-n+2oGuS0F3vsZc8Kw@mail.gmail.com>
Message-ID: <3699679.Zc2Zy9pGhA@wintermute.sprawl.net>

On Wednesday, 28 August 2019 08:12:53 PDT Fellype wrote:
> Hi,
> scikit-learn 0.21.3 fails to build on my system (Slackware 14.2, 64 bits).
> I tried to rebuild the deps, but it still failing. The build errors are
> below.
> Did I miss something?
> 
> 
> ---------------------------
> sklearn/utils/_cython_blas.pyx:203:43: Converting to Python object not
> allowed without gil

I'm not sure to be honest. I built/tested on a clean 14.2 64-bit system and 
didn't hit a problem. A good check would be to confirm that your numpy, scipy 
and python3-Cython are installed and working as expected.

Ben





From hedgehog87 at hotmail.it  Fri Aug 30 07:53:58 2019
From: hedgehog87 at hotmail.it (Cristiano Urban)
Date: Fri, 30 Aug 2019 07:53:58 +0000
Subject: [Slackbuilds-users] Sphinx fails in GMT
In-Reply-To: <2390438.hWKNCZl7q8@wintermute.sprawl.net>
Message-ID: <AM7PR02MB5767896348F47394A2759296B7BD0@AM7PR02MB5767.eurprd02.prod.outlook.com>

Ok! Thank you Benjamin!

Il 28 ago 2019 1:45 PM, Benjamin Trigona-Harany <slackbuilds at jaxartes.net> ha scritto:

On Wednesday, 28 August 2019 03:36:19 PDT Cristiano Urban wrote:
> Hi,
> I've tried to build GMT on a clean Slackware VM and it fails near the end of
> the compilation procedure (see the attached file). I solved this issue by
> installing python3-attrs. After this, the GMT slack build builds
> correctly.

> Should python3-attrs be added as Sphinx dependency? Or should I add a note
> on the GMT README, instead?

This is a dependency-of-a-dependency issue. python3-attrs should be added as a
dependency of python3-packaging, which I can take care of.

> Thank you in advance for your time.

Thanks for the report!

> Best regards,
> Cristiano Urban.
>




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


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

From thedoogster at gmail.com  Fri Aug 30 14:07:12 2019
From: thedoogster at gmail.com (Doogster)
Date: Fri, 30 Aug 2019 07:07:12 -0700
Subject: [Slackbuilds-users] Orphaning all my SlackBuilds
Message-ID: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>

I'm sorry to have to make this announcement, but I want to become a
distro hopper again.

The SlackBuilds I'll no longer be maintaining are, well, let me generate a list:

? rg MAINTAINER=\"Dugan\ Chen\"
python/python-evdev/python-evdev.info
9:MAINTAINER="Dugan Chen"

development/gnome-inform7/gnome-inform7.info
11:MAINTAINER="Dugan Chen"

python/pycdio/pycdio.info
9:MAINTAINER="Dugan Chen"

development/love/love.info
9:MAINTAINER="Dugan Chen"

python/pygpgme/pygpgme.info
9:MAINTAINER="Dugan Chen"

desktop/lxappearance/lxappearance.info
9:MAINTAINER="Dugan Chen"

desktop/tint2/tint2.info
9:MAINTAINER="Dugan Chen"

libraries/gtkglextmm/gtkglextmm.info
9:MAINTAINER="Dugan Chen"

libraries/DevIL/DevIL.info
9:MAINTAINER="Dugan Chen"

desktop/compiz-boxmenu/compiz-boxmenu.info
9:MAINTAINER="Dugan Chen"

system/ds4drv/ds4drv.info
9:MAINTAINER="Dugan Chen"

system/adobe-source-code-pro-font/adobe-source-code-pro-font.info
9:MAINTAINER="Dugan Chen"

multimedia/munt/munt.info
9:MAINTAINER="Dugan Chen"

system/adobe-source-sans-pro-font/adobe-source-sans-pro-font.info
9:MAINTAINER="Dugan Chen"

system/ciopfs/ciopfs.info
9:MAINTAINER="Dugan Chen"

audio/rubyripper/rubyripper.info
9:MAINTAINER="Dugan Chen"

system/webcore-fonts/webcore-fonts.info
11:MAINTAINER="Dugan Chen"

audio/deadbeef/deadbeef.info
9:MAINTAINER="Dugan Chen"

graphics/vulkan-sdk-bin/vulkan-sdk-bin.info
9:MAINTAINER="Dugan Chen"

system/GentiumPlus/GentiumPlus.info
9:MAINTAINER="Dugan Chen"

games/ags/ags.info
13:MAINTAINER="Dugan Chen"

games/gargoyle/gargoyle.info
9:MAINTAINER="Dugan Chen"

games/innoextract/innoextract.info
9:MAINTAINER="Dugan Chen"

ruby/rubygem-atk/rubygem-atk.info
9:MAINTAINER="Dugan Chen"

ruby/rubygem-pango/rubygem-pango.info
9:MAINTAINER="Dugan Chen"

ruby/rubygem-cairo/rubygem-cairo.info
9:MAINTAINER="Dugan Chen"

ruby/rubygem-gdk_pixbuf2/rubygem-gdk_pixbuf2.info
9:MAINTAINER="Dugan Chen"

ruby/rubygem-glib2/rubygem-glib2.info
9:MAINTAINER="Dugan Chen"

ruby/rubygem-gtk2/rubygem-gtk2.info
9:MAINTAINER="Dugan Chen"

ruby/rubygem-pkg-config/rubygem-pkg-config.info
9:MAINTAINER="Dugan Chen"

games/eureka/eureka.info
9:MAINTAINER="Dugan Chen"

games/lmpc/lmpc.info
9:MAINTAINER="Dugan Chen"

system/adobe-source-serif-pro-font/adobe-source-serif-pro-font.info
9:MAINTAINER="Dugan Chen"

games/qzdl/qzdl.info
9:MAINTAINER="Dugan Chen"

games/crispy-doom/crispy-doom.info
9:MAINTAINER="Dugan Chen"

games/nestopia/nestopia.info
11:MAINTAINER="Dugan Chen"

games/SLADE/SLADE.info
9:MAINTAINER="Dugan Chen"

games/mgba/mgba.info
11:MAINTAINER="Dugan Chen"

games/ppsspp/ppsspp.info
13:MAINTAINER="Dugan Chen"

games/prboom-plus/prboom-plus.info
9:MAINTAINER="Dugan Chen"

games/doomretro/doomretro.info
9:MAINTAINER="Dugan Chen"

games/yamagi-quake2/yamagi-quake2.info
15:MAINTAINER="Dugan Chen"

That should be fairly accurate.

I'll stay subscribed to this mailing list for another week.

From gerardo.zamudio at linux.com  Fri Aug 30 14:35:00 2019
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Fri, 30 Aug 2019 09:35:00 -0500
Subject: [Slackbuilds-users] Orphaning all my SlackBuilds
In-Reply-To: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
References: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
Message-ID: <5405773.KZ2TYVNLzH@hades.slack.lan>

On Friday, August 30, 2019 9:07:12 AM CDT Doogster wrote:
> I'm sorry to have to make this announcement, but I want to become a
> distro hopper again.
> 
> The SlackBuilds I'll no longer be maintaining are, well, let me generate a 
list:
> 
> I'll stay subscribed to this mailing list for another week.


Very sad to see you go!

I'm more concerned about https://github.com/duganchen/slackware-libretro

I sent a pull request in the past to update the scripts for all the newer 
versions of the programs which was accepted. I have been *meaning to* do it 
again lately as I recently got new hardware and a revived interest in gaming.

I can volunteer to maintain this. Last commit was in 2017 so I will have to do 
some work to get it up to date with 14.2 and of course create a branch for -
current.

Regards,
Gerardo Zamudio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190830/130a8bcf/attachment-0001.asc>

From thedoogster at gmail.com  Fri Aug 30 14:42:49 2019
From: thedoogster at gmail.com (Doogster)
Date: Fri, 30 Aug 2019 07:42:49 -0700
Subject: [Slackbuilds-users] Orphaning all my SlackBuilds
In-Reply-To: <5405773.KZ2TYVNLzH@hades.slack.lan>
References: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
 <5405773.KZ2TYVNLzH@hades.slack.lan>
Message-ID: <CAE5oDaZhWR3uT_Uy77dAJywMamhW3FN8x35JmgUmPGvUci1r2A@mail.gmail.com>

The only SlackBuild in my slackware-libretro that that's still worth
using is libretro-RetroArch.sh. The rest were written before RetroArch
had a working core-downloader built into the program.

On Fri, Aug 30, 2019 at 7:35 AM Gerardo Zamudio
<gerardo.zamudio at linux.com> wrote:
>
> On Friday, August 30, 2019 9:07:12 AM CDT Doogster wrote:
> > I'm sorry to have to make this announcement, but I want to become a
> > distro hopper again.
> >
> > The SlackBuilds I'll no longer be maintaining are, well, let me generate a
> list:
> >
> > I'll stay subscribed to this mailing list for another week.
>
>
> Very sad to see you go!
>
> I'm more concerned about https://github.com/duganchen/slackware-libretro
>
> I sent a pull request in the past to update the scripts for all the newer
> versions of the programs which was accepted. I have been *meaning to* do it
> again lately as I recently got new hardware and a revived interest in gaming.
>
> I can volunteer to maintain this. Last commit was in 2017 so I will have to do
> some work to get it up to date with 14.2 and of course create a branch for -
> current.
>
> Regards,
> Gerardo Zamudio_______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From pomfland at tfwno.gf  Fri Aug 30 16:18:36 2019
From: pomfland at tfwno.gf (pomfland)
Date: Fri, 30 Aug 2019 18:18:36 +0200
Subject: [Slackbuilds-users] Orphaning all my SlackBuilds
In-Reply-To: <CAE5oDaZhWR3uT_Uy77dAJywMamhW3FN8x35JmgUmPGvUci1r2A@mail.gmail.com>
References: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
 <5405773.KZ2TYVNLzH@hades.slack.lan>
 <CAE5oDaZhWR3uT_Uy77dAJywMamhW3FN8x35JmgUmPGvUci1r2A@mail.gmail.com>
Message-ID: <20190830181836.b99fffdb4090e94ab7470926@tfwno.gf>

On Fri, 30 Aug 2019 07:42:49 -0700, Doogster <thedoogster at gmail.com>
wrote:

> The only SlackBuild in my slackware-libretro that that's still worth
> using is libretro-RetroArch.sh. The rest were written before RetroArch
> had a working core-downloader built into the program.
> 
> On Fri, Aug 30, 2019 at 7:35 AM Gerardo Zamudio
> <gerardo.zamudio at linux.com> wrote:
> >
> > On Friday, August 30, 2019 9:07:12 AM CDT Doogster wrote:
> > > I'm sorry to have to make this announcement, but I want to become a
> > > distro hopper again.
> > >
> > > The SlackBuilds I'll no longer be maintaining are, well, let me generate a
> > list:
> > >
> > > I'll stay subscribed to this mailing list for another week.
> >
> >
> > Very sad to see you go!
> >
> > I'm more concerned about https://github.com/duganchen/slackware-libretro
> >
> > I sent a pull request in the past to update the scripts for all the newer
> > versions of the programs which was accepted. I have been *meaning to* do it
> > again lately as I recently got new hardware and a revived interest in gaming.
> >
> > I can volunteer to maintain this. Last commit was in 2017 so I will have to do
> > some work to get it up to date with 14.2 and of course create a branch for -
> > current.
> >
> > Regards,
> > Gerardo Zamudio_______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
I would say that the ability to compile your own binaries from official
sources instead of relying on a foreign buildbot that /may/ be
compromised is an important one. That being said I don't use, nor like
retroarch, so what do I know about its userbase habits ;)

-- 
pomfland <pomfland at tfwno.gf>
(^_^)/ signatures over 2 lines long are bloat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190830/6c487cb0/attachment.asc>

From matteo.bernardini at gmail.com  Fri Aug 30 16:33:54 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 30 Aug 2019 18:33:54 +0200
Subject: [Slackbuilds-users] Orphaning all my SlackBuilds
In-Reply-To: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
References: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
Message-ID: <CAPsDuS5bzavR7=e+xqA1XDxDGij57Ddcw0GSi9n26wZmpFPx1Q@mail.gmail.com>

Il giorno ven 30 ago 2019 alle ore 16:07 Doogster
<thedoogster at gmail.com> ha scritto:
> desktop/lxappearance/lxappearance.info
> system/adobe-source-code-pro-font/adobe-source-code-pro-font.info
> system/adobe-source-sans-pro-font/adobe-source-sans-pro-font.info
> system/webcore-fonts/webcore-fonts.info
> system/adobe-source-serif-pro-font/adobe-source-serif-pro-font.info

I'll take these.
thanks for all your work during these years and good luck in your new
adventures!

Matteo

From lenardrspencer at gmail.com  Fri Aug 30 16:54:42 2019
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Fri, 30 Aug 2019 12:54:42 -0400
Subject: [Slackbuilds-users] Orphaning all my SlackBuilds
In-Reply-To: <CAPsDuS5bzavR7=e+xqA1XDxDGij57Ddcw0GSi9n26wZmpFPx1Q@mail.gmail.com>
References: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
 <CAPsDuS5bzavR7=e+xqA1XDxDGij57Ddcw0GSi9n26wZmpFPx1Q@mail.gmail.com>
Message-ID: <CANSA5-tobeNzqHE0F=L6AF_8vrFGR=V4hVFZCMbRxK+tuNjqhQ@mail.gmail.com>

I can take crispy-doom.

On Fri, Aug 30, 2019, 12:34 Matteo Bernardini <matteo.bernardini at gmail.com>
wrote:

> Il giorno ven 30 ago 2019 alle ore 16:07 Doogster
> <thedoogster at gmail.com> ha scritto:
> > desktop/lxappearance/lxappearance.info
> > system/adobe-source-code-pro-font/adobe-source-code-pro-font.info
> > system/adobe-source-sans-pro-font/adobe-source-sans-pro-font.info
> > system/webcore-fonts/webcore-fonts.info
> > system/adobe-source-serif-pro-font/adobe-source-serif-pro-font.info
>
> I'll take these.
> thanks for all your work during these years and good luck in your new
> adventures!
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190830/a75148b8/attachment.htm>

From lin.ruohshoei at gmail.com  Sat Aug 31 01:42:10 2019
From: lin.ruohshoei at gmail.com (Ruoh-Shoei Lin)
Date: Sat, 31 Aug 2019 01:42:10 +0000
Subject: [Slackbuilds-users] Orphaning all my SlackBuilds
In-Reply-To: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
References: <CAE5oDabCQA_9Zug-v53mJk8ycL-5PM2V2BO89yAZVDemQt9Jag@mail.gmail.com>
Message-ID: <1bd6b7f8-c1bd-df45-6416-5d57e7ff3aa1@gmail.com>

games/yamagi-quake2
games/ppsspp
games/mgba
games/nestopia
audio/deadbeef
games/innoextract

I would like to take these.
Thanks for all your works.

Regards
Lin

Doogster:
> I'm sorry to have to make this announcement, but I want to become a
> distro hopper again.
>
> The SlackBuilds I'll no longer be maintaining are, well, let me generate a list:
>
> ? rg MAINTAINER=\"Dugan\ Chen\"
> python/python-evdev/python-evdev.info
> 9:MAINTAINER="Dugan Chen"
>
> development/gnome-inform7/gnome-inform7.info
> 11:MAINTAINER="Dugan Chen"
>
> python/pycdio/pycdio.info
> 9:MAINTAINER="Dugan Chen"
>
> development/love/love.info
> 9:MAINTAINER="Dugan Chen"
>
> python/pygpgme/pygpgme.info
> 9:MAINTAINER="Dugan Chen"
>
> desktop/lxappearance/lxappearance.info
> 9:MAINTAINER="Dugan Chen"
>
> desktop/tint2/tint2.info
> 9:MAINTAINER="Dugan Chen"
>
> libraries/gtkglextmm/gtkglextmm.info
> 9:MAINTAINER="Dugan Chen"
>
> libraries/DevIL/DevIL.info
> 9:MAINTAINER="Dugan Chen"
>
> desktop/compiz-boxmenu/compiz-boxmenu.info
> 9:MAINTAINER="Dugan Chen"
>
> system/ds4drv/ds4drv.info
> 9:MAINTAINER="Dugan Chen"
>
> system/adobe-source-code-pro-font/adobe-source-code-pro-font.info
> 9:MAINTAINER="Dugan Chen"
>
> multimedia/munt/munt.info
> 9:MAINTAINER="Dugan Chen"
>
> system/adobe-source-sans-pro-font/adobe-source-sans-pro-font.info
> 9:MAINTAINER="Dugan Chen"
>
> system/ciopfs/ciopfs.info
> 9:MAINTAINER="Dugan Chen"
>
> audio/rubyripper/rubyripper.info
> 9:MAINTAINER="Dugan Chen"
>
> system/webcore-fonts/webcore-fonts.info
> 11:MAINTAINER="Dugan Chen"
>
> audio/deadbeef/deadbeef.info
> 9:MAINTAINER="Dugan Chen"
>
> graphics/vulkan-sdk-bin/vulkan-sdk-bin.info
> 9:MAINTAINER="Dugan Chen"
>
> system/GentiumPlus/GentiumPlus.info
> 9:MAINTAINER="Dugan Chen"
>
> games/ags/ags.info
> 13:MAINTAINER="Dugan Chen"
>
> games/gargoyle/gargoyle.info
> 9:MAINTAINER="Dugan Chen"
>
> games/innoextract/innoextract.info
> 9:MAINTAINER="Dugan Chen"
>
> ruby/rubygem-atk/rubygem-atk.info
> 9:MAINTAINER="Dugan Chen"
>
> ruby/rubygem-pango/rubygem-pango.info
> 9:MAINTAINER="Dugan Chen"
>
> ruby/rubygem-cairo/rubygem-cairo.info
> 9:MAINTAINER="Dugan Chen"
>
> ruby/rubygem-gdk_pixbuf2/rubygem-gdk_pixbuf2.info
> 9:MAINTAINER="Dugan Chen"
>
> ruby/rubygem-glib2/rubygem-glib2.info
> 9:MAINTAINER="Dugan Chen"
>
> ruby/rubygem-gtk2/rubygem-gtk2.info
> 9:MAINTAINER="Dugan Chen"
>
> ruby/rubygem-pkg-config/rubygem-pkg-config.info
> 9:MAINTAINER="Dugan Chen"
>
> games/eureka/eureka.info
> 9:MAINTAINER="Dugan Chen"
>
> games/lmpc/lmpc.info
> 9:MAINTAINER="Dugan Chen"
>
> system/adobe-source-serif-pro-font/adobe-source-serif-pro-font.info
> 9:MAINTAINER="Dugan Chen"
>
> games/qzdl/qzdl.info
> 9:MAINTAINER="Dugan Chen"
>
> games/crispy-doom/crispy-doom.info
> 9:MAINTAINER="Dugan Chen"
>
> games/nestopia/nestopia.info
> 11:MAINTAINER="Dugan Chen"
>
> games/SLADE/SLADE.info
> 9:MAINTAINER="Dugan Chen"
>
> games/mgba/mgba.info
> 11:MAINTAINER="Dugan Chen"
>
> games/ppsspp/ppsspp.info
> 13:MAINTAINER="Dugan Chen"
>
> games/prboom-plus/prboom-plus.info
> 9:MAINTAINER="Dugan Chen"
>
> games/doomretro/doomretro.info
> 9:MAINTAINER="Dugan Chen"
>
> games/yamagi-quake2/yamagi-quake2.info
> 15:MAINTAINER="Dugan Chen"
>
> That should be fairly accurate.
>
> I'll stay subscribed to this mailing list for another week.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From duncan_roe at optusnet.com.au  Sat Aug 31 07:33:32 2019
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sat, 31 Aug 2019 17:33:32 +1000
Subject: [Slackbuilds-users] Qt5 build failure
Message-ID: <20190831073332.GC25467@dimstar.local.net>

Hi,

When building qt5 5.9.8, this error appeared:

> g++ -L/usr/lib64 -Wl,--no-undefined -Wl,-O1 -Wl,--enable-new-dtags -shared -o libqsqltds.so .obj/qsql_tds.o .obj/main.o .obj/moc_qsql_tds_p.o  -L/tmp/SBo/qt-everywhere-opensource-src-5.9.8/qtbase/lib -lQt5Sql -lQt5Core -lpthread -L/opt/sybase/lib
> .obj/qsql_tds.o: In function `qFieldType(QTDSResultPrivate*, int)':
> qsql_tds.cpp:(.text+0x34f): undefined reference to `dbcoltype'
> .obj/qsql_tds.o: In function `QTDSDriver::init()':
> qsql_tds.cpp:(.text+0x426): undefined reference to `dbinit'
> qsql_tds.cpp:(.text+0x43c): undefined reference to `dberrhandle'
> .obj/qsql_tds.o: In function `QTDSDriver::~QTDSDriver()':
> qsql_tds.cpp:(.text+0x805): undefined reference to `dberrhandle'
> qsql_tds.cpp:(.text+0x80c): undefined reference to `dbmsghandle'
> qsql_tds.cpp:(.text+0x811): undefined reference to `dbexit'
> .obj/qsql_tds.o: In function `QTDSDriver::open(QString const&, QString const&, QString const&, QString const&, int, QString const&)':
> qsql_tds.cpp:(.text+0x892): undefined reference to `dblogin'
> qsql_tds.cpp:(.text+0x8e1): undefined reference to `dbsetlname'
> qsql_tds.cpp:(.text+0x938): undefined reference to `dbsetlname'
> qsql_tds.cpp:(.text+0x978): undefined reference to `tdsdbopen'
> qsql_tds.cpp:(.text+0x9bf): undefined reference to `dbuse'
> qsql_tds.cpp:(.text+0x9e9): undefined reference to `dbclose'
> .obj/qsql_tds.o: In function `QTDSDriver::close()':
> qsql_tds.cpp:(.text+0xc18): undefined reference to `dbloginfree'
> .obj/qsql_tds.o: In function `qTdsErrHandler':
> qsql_tds.cpp:(.text+0x163f): undefined reference to `dbdead'
> .obj/qsql_tds.o: In function `QTDSResult::cleanup()':
> qsql_tds.cpp:(.text+0x1f69): undefined reference to `dbcanquery'
> qsql_tds.cpp:(.text+0x1f76): undefined reference to `dbfreebuf'
> .obj/qsql_tds.o: In function `QTDSResult::reset(QString const&)':
> qsql_tds.cpp:(.text+0x205b): undefined reference to `dbcmd'
> qsql_tds.cpp:(.text+0x2085): undefined reference to `dbsqlexec'
> qsql_tds.cpp:(.text+0x2095): undefined reference to `dbresults'
> qsql_tds.cpp:(.text+0x20b6): undefined reference to `dbfreebuf'
> qsql_tds.cpp:(.text+0x210f): undefined reference to `dbcmdrow'
> qsql_tds.cpp:(.text+0x212a): undefined reference to `dbnumcols'
> qsql_tds.cpp:(.text+0x2191): undefined reference to `dbcoltype'
> qsql_tds.cpp:(.text+0x21b6): undefined reference to `dbcolname'
> qsql_tds.cpp:(.text+0x222a): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x228d): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x2395): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x23ab): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x23c8): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x23e2): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x2415): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x242b): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x2448): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x2462): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x2480): undefined reference to `dbcolname'
> qsql_tds.cpp:(.text+0x2578): undefined reference to `dbnullbind'
> .obj/qsql_tds.o: In function `QTDSResult::gotoNext(QVector<QVariant>&, int)':
> qsql_tds.cpp:(.text+0x2ed3): undefined reference to `dbnextrow'
> .obj/qsql_tds.o: In function `QTDSResult::~QTDSResult()':
> qsql_tds.cpp:(.text+0x36f9): undefined reference to `dbclose'
> .obj/qsql_tds.o: In function `QTDSResult::QTDSResult(QTDSDriver const*)':
> qsql_tds.cpp:(.text+0x3970): undefined reference to `tdsdbopen'
> qsql_tds.cpp:(.text+0x39f9): undefined reference to `dbuse'
> qsql_tds.cpp:(.text+0x3b7a): undefined reference to `dbcmd'
> qsql_tds.cpp:(.text+0x3b86): undefined reference to `dbsqlexec'
> .obj/qsql_tds.o: In function `QTDSResult::numRowsAffected()':
> qsql_tds.cpp:(.text+0x1c): undefined reference to `dbcount'
> .obj/qsql_tds.o: In function `QTDSDriver::init()':
> qsql_tds.cpp:(.text+0x449): undefined reference to `dbmsghandle'
> collect2: error: ld returned 1 exit status

Looking back, I found I had the same problem with qt5 5.9.7, but must have
gotten around it somehow.

I have freetds installed, and found that the missing references were all
satisfied by libsybdb from that package.

After patching
/tmp/SBo/qt-everywhere-opensource-src-5.9.8/qtbase/src/plugins/sqldrivers/tds/Makefile
as follows:

> 40c40
> < LFLAGS        = -L/usr/lib64 -Wl,--no-undefined -Wl,-O1 -Wl,--enable-new-dtags -shared
> ---
> > LFLAGS        = -L/usr/lib64 -Wl,--no-undefined -Wl,-O1 -Wl,--enable-new-dtags -shared -lsybdb

"make" proceeds.

I don't know is this is an upstream problem with configure or what.

Cheers ... Duncan.

From willysr at slackbuilds.org  Sat Aug 31 10:27:54 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 31 Aug 2019 17:27:54 +0700
Subject: [Slackbuilds-users] Updates - 20190831.1
Message-ID: <ac4c3e11-1bd1-fce3-de54-3775ac697f97@slackbuilds.org>

Sat Aug 31 10:14:16 UTC 2019
audio/asunder: Updated for version 2.9.4.
desktop/Zafiro-icons: Updated for version 1.0.
desktop/compton-conf: Updated for version 0.14.1.
desktop/lxappearance: Changed maintainer.
development/apache-jmeter: Updated for version 5.1.1.
development/arm-binutils: Updated for version 2.32.
development/arm-gcc: Updated for version 9.2.0.
development/arm-gdb: Updated for version 8.3.
development/fossil: Updated for version 2.9.
development/idea: Updated for version 2019.1.1.
development/ioncube-loader: Updated for version 10.3.8
development/jupyter-qtconsole: Updated for version 4.5.4.
development/universal-ctags: Updated for version 0484191
games/7kaa: Updated for version 2.15.2.
games/FlightGear-data: Updated for version 2019.1.1.
games/FlightGear: Updated for version 2019.1.1.
games/RetroArch: Fix Qt5 support.
games/SimGear: Updated for version 2019.1.1, Moved from Libraries.
games/ioquake3: Updated for version r20190822.
games/solarus-quest-editor: Updated for version 1.6.2.
games/solarus: Updated for version 1.6.2.
games/zbom: Fix white spaces.
gis/gpxsee: Updated for version 7.12.
gis/rasterio: Updated for version 1.0.26.
graphics/fontforge: Update source url.
graphics/vuescan: Updated for version 9.6.47.
libraries/CoinMP: Updated for version 1.8.4.
libraries/fmt: Added (A modern formatting library).
libraries/libabw: Updated for version 0.1.3.
libraries/libetonyek: Fix mdds version.
libraries/libgta: Updated for version 1.2.0
libraries/libinput: Updated for version 1.14.1.
libraries/libixion: Updated for version 0.15.0.
libraries/libmwaw: Updated for version 0.3.15.
libraries/liborcus: Updated for version 0.15.1.
libraries/libwacom: Updated for version 1.0.
libraries/live555: Updated for version 2019.08.28
libraries/mdds: Updated for version 1.5.0.
libraries/nltk: Updated for version 3.4.5.
libraries/spdlog: Updated for version 1.3.1, moved from development.
libraries/wxSQLite3: Updated for version 4.4.5.
network/avahi: Update maintainer
network/bro: Updated for version 2.6.3.
network/clipgrab: Updated for version 3.8.4.
network/courier-authlib: Updated for version 0.69.1.
network/courier-imap: Updated for version 5.0.7.
network/ipscan: Updated for version 3.6.0.
network/monkey: Updated for version 1.6.9.
network/nordvpn: Added (Protect your privacy online).
network/nss-mdns: Look in /run for avahi daemon socket
network/opensmtpd: Fix bug.
network/opera-developer: Updated for version 64.0.3416.0.
network/opera: Updated for version 63.0.3368.53.
network/palemoon: Updated for version 28.7.0.
network/prosody-mod-http-upload: Updated for version hg3649.
network/prosody-mod-smacks: Updated for version hg3646.
network/s-nail: Updated for version 14.9.15.
network/teamviewer: Updated for version 14.5.1691.
office/calibre-bin: Updated for version 3.47.0.
office/onlyoffice-desktopeditors: Updated for version 5.3.5.
office/pdfstudio: Updated for version 2019.1.2.
office/pdfstudioviewer: Updated for version 2019.1.2.
office/smoffice2018: Updated for version 2018_970.
office/vmd: Added (Terminal Markdown Viewer).
perl/perl-Class-Method-Modifiers: Fix build.
perl/perl-Sidef: Updated for version 3.85.
perl/perl-glib: Updated for version 1.3291.
perl/perl-gtk2: Updated for version 1.24993.
python/git-fame: Updated for version 1.10.0.
python/pycryptodome: Updated for version 3.9.0.
ruby/ruby-build: Updated for version 20190828.
system/adobe-source-code-pro-font: Changed maintainer.
system/adobe-source-sans-pro-font: Changed maintainer.
system/adobe-source-serif-pro-font: Changed maintainer.
system/btrbk: Updated for version 0.28.3.
system/chronograf: Updated for version 1.7.14.
system/forkstat: Updated for version 0.02.11.
system/fwupd: Update homepage.
system/gtk-vnc: Updated for version 1.0.0.
system/isdct: Updated for version 3.0.20.
system/qemu: Update README.
system/telegraf: Updated for version 1.11.5.
system/webcore-fonts: Changed maintainer.
system/wine-staging: Updated for version 4.14.
system/zuluCrypt: Updated for version 5.6.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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