From n0nb at n0nb.us  Fri Mar  1 13:15:34 2019
From: n0nb at n0nb.us (Nate Bargmann)
Date: Fri, 1 Mar 2019 07:15:34 -0600
Subject: [Slackbuilds-users] virtualbox-kernel-addons fails build with
 kernel 4.4.172
Message-ID: <20190301131534.34m4yoowqknzni6v@n0nb.us>

I run a 32 and a 64 bit instance of Slackware 14.2 in VirtualBox for
making sure my Slackbuilds work in as clean of an environment as
possible.  A couple of days ago I upgraded the 32 bit VM to the latest
Slackware updates and kernel 4.4.172 was installed.  After rebooting I
performed the usual SBO upgrades and now find that
virtualbox-kernel-addons fails to build against the 4.4.172 kernel tree.

I don't see any mention of this in the list archives, so I may be the
first bitten by this bug.

I have attached screenshots of the failing build.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: http://www.n0nb.us  GPG key: D55A8819  GitHub: N0NB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2019-03-01 06-41-03.jpg
Type: image/jpeg
Size: 117317 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/45c67d16/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2019-03-01 06-44-27.jpg
Type: image/jpeg
Size: 342084 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/45c67d16/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2019-03-01 06-45-20.jpg
Type: image/jpeg
Size: 232580 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/45c67d16/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2019-03-01 06-45-38.jpg
Type: image/jpeg
Size: 210345 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/45c67d16/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/45c67d16/attachment-0001.asc>

From matteo.bernardini at gmail.com  Fri Mar  1 17:04:41 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 1 Mar 2019 18:04:41 +0100
Subject: [Slackbuilds-users] virtualbox-kernel-addons fails build with
 kernel 4.4.172
In-Reply-To: <20190301131534.34m4yoowqknzni6v@n0nb.us>
References: <20190301131534.34m4yoowqknzni6v@n0nb.us>
Message-ID: <CAPsDuS6j-3hSNHsQ8utPPfAKPoejN6v-ixCry81=BuQg73PF-g@mail.gmail.com>

Il giorno ven 1 mar 2019 alle ore 17:56 Nate Bargmann <n0nb at n0nb.us> ha scritto:
>
> I run a 32 and a 64 bit instance of Slackware 14.2 in VirtualBox for
> making sure my Slackbuilds work in as clean of an environment as
> possible.  A couple of days ago I upgraded the 32 bit VM to the latest
> Slackware updates and kernel 4.4.172 was installed.  After rebooting I
> performed the usual SBO upgrades and now find that
> virtualbox-kernel-addons fails to build against the 4.4.172 kernel tree.
>
> I don't see any mention of this in the list archives, so I may be the
> first bitten by this bug.
>
> I have attached screenshots of the failing build.
>
> - Nate

Hi Nate,

are you sure that you are using the latest version of the script?

I'm asking because three weeks ago it has been updated

https://git.slackbuilds.org/slackbuilds/commit/?id=8ac827899d38d11cf747fc0de9ed6afd84fc9823

Matteo

From n0nb at n0nb.us  Fri Mar  1 18:10:48 2019
From: n0nb at n0nb.us (Nate Bargmann)
Date: Fri, 1 Mar 2019 12:10:48 -0600
Subject: [Slackbuilds-users] virtualbox-kernel-addons fails build with
 kernel 4.4.172
In-Reply-To: <CAPsDuS6j-3hSNHsQ8utPPfAKPoejN6v-ixCry81=BuQg73PF-g@mail.gmail.com>
References: <20190301131534.34m4yoowqknzni6v@n0nb.us>
 <CAPsDuS6j-3hSNHsQ8utPPfAKPoejN6v-ixCry81=BuQg73PF-g@mail.gmail.com>
Message-ID: <20190301181047.cxux7u44r3aowrgf@n0nb.us>

* On 2019 01 Mar 11:06 -0600, Matteo Bernardini wrote:
> Il giorno ven 1 mar 2019 alle ore 17:56 Nate Bargmann <n0nb at n0nb.us> ha scritto:
> Hi Nate,
> 
> are you sure that you are using the latest version of the script?
> 
> I'm asking because three weeks ago it has been updated
> 
> https://git.slackbuilds.org/slackbuilds/commit/?id=8ac827899d38d11cf747fc0de9ed6afd84fc9823

Hi Matteo.

I'm not sure.  I don't recall if sbotools downloaded the most recent
version.  I'll try removing the package and then installing it anew.

Thanks!

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: http://www.n0nb.us  GPG key: D55A8819  GitHub: N0NB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/ba2f53c1/attachment.asc>

From n0nb at n0nb.us  Fri Mar  1 18:47:02 2019
From: n0nb at n0nb.us (Nate Bargmann)
Date: Fri, 1 Mar 2019 12:47:02 -0600
Subject: [Slackbuilds-users] virtualbox-kernel-addons fails build with
 kernel 4.4.172
In-Reply-To: <CAPsDuS6j-3hSNHsQ8utPPfAKPoejN6v-ixCry81=BuQg73PF-g@mail.gmail.com>
References: <20190301131534.34m4yoowqknzni6v@n0nb.us>
 <CAPsDuS6j-3hSNHsQ8utPPfAKPoejN6v-ixCry81=BuQg73PF-g@mail.gmail.com>
Message-ID: <20190301184702.3cv2gus6wv54yyg3@n0nb.us>

Well, I verified the latest script is available to sbotools and even
forced a download of the source package as well as trying to build the
package by directly running the script.  All to no avail as the build
fails at the same point each time as with my screenshots from my OP.

Hope that helps.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: http://www.n0nb.us  GPG key: D55A8819  GitHub: N0NB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/830c761c/attachment.asc>

From pprkut at slackbuilds.org  Fri Mar  1 18:48:24 2019
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Fri, 01 Mar 2019 19:48:24 +0100
Subject: [Slackbuilds-users] virtualbox-kernel-addons fails build with
 kernel 4.4.172
In-Reply-To: <20190301181047.cxux7u44r3aowrgf@n0nb.us>
References: <20190301131534.34m4yoowqknzni6v@n0nb.us>
 <CAPsDuS6j-3hSNHsQ8utPPfAKPoejN6v-ixCry81=BuQg73PF-g@mail.gmail.com>
 <20190301181047.cxux7u44r3aowrgf@n0nb.us>
Message-ID: <2135161.RuIJoqm8r6@titania.liwjatan.org>

On Friday, 1 March 2019 19:10:48 CET Nate Bargmann wrote:
> * On 2019 01 Mar 11:06 -0600, Matteo Bernardini wrote:
> > Il giorno ven 1 mar 2019 alle ore 17:56 Nate Bargmann <n0nb at n0nb.us> ha
> > scritto: Hi Nate,
> > 
> > are you sure that you are using the latest version of the script?
> > 
> > I'm asking because three weeks ago it has been updated
> > 
> > https://git.slackbuilds.org/slackbuilds/commit/?id=8ac827899d38d11cf747fc0
> > de9ed6afd84fc9823
> Hi Matteo.
> 
> I'm not sure.  I don't recall if sbotools downloaded the most recent
> version.  I'll try removing the package and then installing it anew.

There is a small bug in the script that makes it fail with the 32bit smp 
kernel. I didn't have time to fix that yet, but will try to get to it 
tomorrow.

In the meantime, if you want to "hack" it, there is a sed call guarded by a 
kernel version check in the script. If you remove the kernel version check and 
just execute the sed call you should be good.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/cfa291d5/attachment.asc>

From n0nb at n0nb.us  Fri Mar  1 19:15:31 2019
From: n0nb at n0nb.us (Nate Bargmann)
Date: Fri, 1 Mar 2019 13:15:31 -0600
Subject: [Slackbuilds-users] virtualbox-kernel-addons fails build with
 kernel 4.4.172
In-Reply-To: <2135161.RuIJoqm8r6@titania.liwjatan.org>
References: <20190301131534.34m4yoowqknzni6v@n0nb.us>
 <CAPsDuS6j-3hSNHsQ8utPPfAKPoejN6v-ixCry81=BuQg73PF-g@mail.gmail.com>
 <20190301181047.cxux7u44r3aowrgf@n0nb.us>
 <2135161.RuIJoqm8r6@titania.liwjatan.org>
Message-ID: <20190301191531.764vipj7f65k64p3@n0nb.us>

* On 2019 01 Mar 12:49 -0600, Heinz Wiesinger wrote:
> There is a small bug in the script that makes it fail with the 32bit smp 
> kernel. I didn't have time to fix that yet, but will try to get to it 
> tomorrow.
> 
> In the meantime, if you want to "hack" it, there is a sed call guarded by a 
> kernel version check in the script. If you remove the kernel version check and 
> just execute the sed call you should be good.

Thanks, for the information, Heinz.  Yes, the hack worked and the
package built and the addons are working again.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: http://www.n0nb.us  GPG key: D55A8819  GitHub: N0NB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190301/6661904f/attachment.asc>

From willysr at slackbuilds.org  Sat Mar  2 00:57:30 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 2 Mar 2019 07:57:30 +0700
Subject: [Slackbuilds-users] Updates - 20190302.1
Message-ID: <b1eb2576-80e4-376c-42c7-9783e6686181@slackbuilds.org>

Hi

Welcome to the first update in March.
We merged the python 3.7 changes in this batch, so people will have to
start rebuilding packages that depends on python3.

The easiest way is to look up for files under
/usr/lib{64}/python3.6/site-packages/
You can mostly guess the package it belongs to just by looking the name
of the files. Let us know if something is broken due to the changes in
Python 3.7.

Another note is that wireshark 3.0 is now out, but since it's just less
than few days, i would wait for another week for more testing.
Meanwhile, i have pushed the changes in a separate branch:
wireshark-review. Please give it a good review and hopefully we can
merge it next week. Please note that wireshark 3.0 is no longer
supporting the legacy GTK+3 UI. It's all based on Qt5.

I also made a small mistake of not taking Larry's changes in this week
batch of updates. Let's hope everything is included in next week's update.

Sat Mar  2 00:41:10 UTC 2019
audio/clementine: Update to 1.3.1_560_g248f1d8
audio/qmmp-plugin-pack-qt5: Updated for version 1.3.0.
audio/qmmp-qt5: Updated for version 1.3.0.
desktop/anki: Fix DOWNLOAD.
desktop/bubblemon-dockapp: Added (Dockapp-style system monitor).
desktop/jgmenu: Updated for version 2.1.
development/adoptopenjdk: Updated for version 11.0.2+9.
development/dart: Updated for version 2.1.1.
development/evemu: Added (event recording and replaying tools).
development/hub: Add MD5SUM.
development/pkgconf: Add compatibility.
gis/rasterio: Updated for version 1.0.21.
gis/saga-gis: Updated for version 7.2.0.
graphics/wine-nine-standalone: Added (Gallium Nine support).
libraries/allegro: Updated for version 5.2.5.0.
libraries/appstream-glib: Updated for version 0.7.15.
libraries/live555: Updated for version 2019.02.27
libraries/opencv: Better location of site-packages directories
misc/sbo-templates: Updated for version 1.0.9.
multimedia/audio-recorder: Added (Open Source audio recorder).
multimedia/get_iplayer: Updated for version 3.20.
multimedia/obs-studio: Updated for version 23.0.1
multimedia/podcastparser: Updated for version 0.6.4.
network/brave-browser: Updated for version 0.60.45.
network/clipgrab: Updated for version 3.8.1.
network/opera-developer: Updated for version 60.0.3236.0.
network/opera: Updated for version 58.0.3135.68.
network/riot-web: update to version 1.0.1
network/shorewall-core: Updated for version 5.2.3.1.
network/shorewall6: Updated for version 5.2.3.1.
network/shorewall: Updated for version 5.2.3.1.
network/vivaldi: Updated for version 2.3.1440.57.
network/wireshark: Updated for version 2.6.7.
office/pdfstudio2018: Updated for version 18.3.1.
python/jedi: Updated for version 0.13.3.
python/pySmartDL: Updated for version 1.3.1.
python/python3-isort: Updated for version 4.3.9.
python/python3-jedi: Updated for version 0.13.3.
python/python3: Updated for version 3.7.2.
python/snuggs: Updated for version 1.4.3.
ruby/ruby-json: Updated for version 2.2.0.
ruby/rubygem-parallel: Updated for version 1.14.0.
ruby/rubygem-parser: Updated for version 2.6.0.0.
system/ProFont: Really fix download link.
system/fish: Updated for version 3.0.2.
system/fwupd: Updated for version 1.2.5.
system/jdupes: Updated for version 1.12.
system/nvidia-driver: Updated for version 418.43.
system/nvidia-kernel: Updated for version 418.43.
system/nvidia-legacy390-driver: Updated for version 390.116.
system/nvidia-legacy390-kernel: Updated for version 390.116.
system/quake-par: Added (Quake archiver).
system/slack-scripts: Update README
system/telegraf: Updated for version 1.9.5.
system/thinkfan: Updated for version 1.0.2.
system/vagrant: Updated for version 2.2.4.
+--------------------------+


-- 
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/20190302/d16b4094/attachment-0001.asc>

From yth at ythogtha.org  Sun Mar  3 20:01:51 2019
From: yth at ythogtha.org (Arnaud)
Date: Sun, 3 Mar 2019 21:01:51 +0100
Subject: [Slackbuilds-users] Updates - 20190302.1
In-Reply-To: <b1eb2576-80e4-376c-42c7-9783e6686181@slackbuilds.org>
References: <b1eb2576-80e4-376c-42c7-9783e6686181@slackbuilds.org>
Message-ID: <20190303210151.07335701c6d529618b3d9cdd@ythogtha.org>

> Hi
> 
> Welcome to the first update in March.
> We merged the python 3.7 changes in this batch, so people will have to
> start rebuilding packages that depends on python3.
> 
> The easiest way is to look up for files under
> /usr/lib{64}/python3.6/site-packages/
> You can mostly guess the package it belongs to just by looking the name
> of the files. Let us know if something is broken due to the changes in
> Python 3.7.

Hi !

It looks like python3-PyYAML does not build anymore.
However a simple version bump from 3.11 to 3.13(latest) builds fine.

opencolorio has another problem : the download URL does not exists anymore,
however even with a version bump from 1.0.9.20170426 to 1.1.0, even with
-std=c++11 or std=gnu++11, it doesn't seem to build.
So I can't tell if it does work or not with python 3.7.

All the other packages I tried to rebuild went fine, but I haven't had time to
test wether they are actually working !

-- 
Arnaud <yth at ythogtha.org>

From jebrhansen+SBo at gmail.com  Sun Mar  3 20:28:49 2019
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 3 Mar 2019 13:28:49 -0700
Subject: [Slackbuilds-users] Updates - 20190302.1
In-Reply-To: <20190303210151.07335701c6d529618b3d9cdd@ythogtha.org>
References: <b1eb2576-80e4-376c-42c7-9783e6686181@slackbuilds.org>
 <20190303210151.07335701c6d529618b3d9cdd@ythogtha.org>
Message-ID: <CANi9qSsj5bEO=MNwubwkCEsihoH0TY3jS2w6T0i28yrdSW5WKA@mail.gmail.com>

On Sun, Mar 3, 2019, 1:08 PM Arnaud <yth at ythogtha.org> wrote:

> > Hi
> >
> > Welcome to the first update in March.
> > We merged the python 3.7 changes in this batch, so people will have to
> > start rebuilding packages that depends on python3.
> >
> > The easiest way is to look up for files under
> > /usr/lib{64}/python3.6/site-packages/
> > You can mostly guess the package it belongs to just by looking the name
> > of the files. Let us know if something is broken due to the changes in
> > Python 3.7.
>
> Hi !
>
> It looks like python3-PyYAML does not build anymore.
> However a simple version bump from 3.11 to 3.13(latest) builds fine.
>
> opencolorio has another problem : the download URL does not exists anymore,
> however even with a version bump from 1.0.9.20170426 to 1.1.0, even with
> -std=c++11 or std=gnu++11, it doesn't seem to build.
> So I can't tell if it does work or not with python 3.7.
>
> All the other packages I tried to rebuild went fine, but I haven't had
> time to
> test wether they are actually working !
>
> --
> Arnaud <yth at ythogtha.org>
>


I'll be pushing an update for python3-PyYAML, but I am hoping the
maintainer for PyYAML, will update that version as well to keep them in
sync. I'll be reaching out later today.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190303/c8b1bf11/attachment.html>

From chris.willing at linux.com  Sun Mar  3 20:52:13 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Mon, 4 Mar 2019 06:52:13 +1000
Subject: [Slackbuilds-users] Updates - 20190302.1
In-Reply-To: <20190303210151.07335701c6d529618b3d9cdd@ythogtha.org>
References: <b1eb2576-80e4-376c-42c7-9783e6686181@slackbuilds.org>
 <20190303210151.07335701c6d529618b3d9cdd@ythogtha.org>
Message-ID: <65af7f6c-e7c2-6135-008f-0531b99386c2@linux.com>

On 4/3/19 6:01 am, Arnaud wrote:
> 
> opencolorio has another problem : the download URL does not exists anymore,
> however even with a version bump from 1.0.9.20170426 to 1.1.0,

the existing version is already 1.1.0 (since April 2018) so no version
bump should be needed. Do you have a recent version of the SBo tree?


> even with
> -std=c++11 or std=gnu++11, it doesn't seem to build.
> So I can't tell if it does work or not with python 3.7.

Version 1.1.0 of opencolorio builds fine here in a fresh x86_64 VM
without any change to the SlackBuild and using latest python3-3.7.2.

chris

From willysr at slackbuilds.org  Sun Mar  3 23:55:49 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 4 Mar 2019 06:55:49 +0700
Subject: [Slackbuilds-users] Updates - 20190302.1
In-Reply-To: <CANi9qSsj5bEO=MNwubwkCEsihoH0TY3jS2w6T0i28yrdSW5WKA@mail.gmail.com>
References: <b1eb2576-80e4-376c-42c7-9783e6686181@slackbuilds.org>
 <20190303210151.07335701c6d529618b3d9cdd@ythogtha.org>
 <CANi9qSsj5bEO=MNwubwkCEsihoH0TY3jS2w6T0i28yrdSW5WKA@mail.gmail.com>
Message-ID: <7345d6bf-30c1-638d-ac62-388ede2a917e@slackbuilds.org>

> I'll be pushing an update for python3-PyYAML, but I am hoping the
> maintainer for PyYAML, will update that version as well to keep them in
> sync. I'll be reaching out later today.

I have pushed both PyYAML and python3-PyYAML to 3.13 in my branch
no changes needed :)


-- 
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/20190304/03ecd0a4/attachment.asc>

From isaacyu1 at isaacyu1.com  Mon Mar  4 00:19:24 2019
From: isaacyu1 at isaacyu1.com (=?utf-8?q?isaacyu1=40isaacyu1=2Ecom?=)
Date: Mon, 04 Mar 2019 01:19:24 +0100
Subject: [Slackbuilds-users] =?utf-8?q?Nitrogen_is_at_1=2E6=2E1?=
Message-ID: <1c1-5c7c6f00-f-45966680@41618634>


Two weeks ago (Feb 15), I emailed the maintainer (G Edward Whiteside,?gedwardwhiteside at gmail.com), requesting an update to the slackbuild. I have not received a response, and the script has not been updated.

The currently maintained version is at 20120806_692fdf7, while upstream contains version 1.6.1.

I wish to take over maintainership of the slackbuild. I have the script ready for uploading.

- Isaac
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190304/1db8fd25/attachment.html>

From larryhaja at gmail.com  Mon Mar  4 01:01:42 2019
From: larryhaja at gmail.com (Larry Hajali)
Date: Sun, 3 Mar 2019 17:01:42 -0800
Subject: [Slackbuilds-users] MuseScore Slackbuild.
In-Reply-To: <4902d3c4-8fb6-8ab2-c3ce-900afc792272@googlemail.com>
References: <4c8fe995-e863-1c8c-f441-70905027889f@googlemail.com>
 <a80100a0b10d4dbc56e33c3a3263c420@mixedsignals.ml>
 <4902d3c4-8fb6-8ab2-c3ce-900afc792272@googlemail.com>
Message-ID: <CAAZPBMjrQEbNdScLCs9m8DH=1mQdYZcO2BgwJAgFXzOhEDfpnA@mail.gmail.com>

On Tue, Feb 26, 2019 at 5:19 AM Tim Dickson via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> On 25/02/2019 22:55, klaatu at mixedsignals.ml wrote:
> > On 2019-02-25 16:03, Tim Dickson via SlackBuilds-users wrote:
> >> Just sending this via sbo mailing list in case klaatu didn't get my
> >> email sent a couple of weeks ago..
> >>
> >> Hi Klaatu, any chance of an update to Musescore? The current one is
> >> 3.0.2
>
Current version upstream as of this writing is 3.0.4.


> >> changing the version number, and adding the line
> >> sed -i 's| qmake| qmake-qt5|' build/FindQt5.cmake
> >> just before the "make " lines in the buildscript is all that is
> >> required to make it work with v3.0.2.
>
That didn't have any affect for the build process.

>> Regards, Tim
> >>
> >>
> >
> > Thanks, Tim. I did get your email and did mean to respond.
> >
> > I can't get it to build even with your suggested patch, so I need to
> > dig into why that's not working for me. What version of Qt5 are you
> > building against?
> >
> qt 5.9.7 (SBo version) built with following DOCS=yes PROPRIETARY_CODECS=yes
> graphviz built with gts, qt5 built with optional freetds,  OpenAL,
> libwebp, opus, pcre2, snappy and wayland
> qt5-webkit 5.9.0 with optional libwebp
>
I built qt5 and qt5-webkit with no extra options or optional packages.

I was able to build MuseScore with version 3.0.4 but I did add a lot of
changes to the build script.  Most were superficial but some were setting
new options available in the Makefile.  I am adding an attachment of the
diff between the MuseScore 3.0.4 and 2.1.0.

On a side note.  I was not able to build it with QtWebEngine.  I get an
error that is described here.
https://musescore.org/en/node/281322
and something similar here.
https://musescore.org/en/node/276196

Thanks,
--Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190303/183df09d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MuseScore.diff
Type: text/x-patch
Size: 4094 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190303/183df09d/attachment-0001.bin>

From jebrhansen+SBo at gmail.com  Mon Mar  4 03:15:31 2019
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 3 Mar 2019 20:15:31 -0700
Subject: [Slackbuilds-users] Updates - 20190302.1
In-Reply-To: <7345d6bf-30c1-638d-ac62-388ede2a917e@slackbuilds.org>
References: <b1eb2576-80e4-376c-42c7-9783e6686181@slackbuilds.org>
 <20190303210151.07335701c6d529618b3d9cdd@ythogtha.org>
 <CANi9qSsj5bEO=MNwubwkCEsihoH0TY3jS2w6T0i28yrdSW5WKA@mail.gmail.com>
 <7345d6bf-30c1-638d-ac62-388ede2a917e@slackbuilds.org>
Message-ID: <CANi9qStggEXDT8LTcHJu5C1fWwKE1pje-f3X0oL=_Q8EKJ0WKQ@mail.gmail.com>

On Sun, Mar 3, 2019, 4:55 PM Willy Sudiarto Raharjo <willysr at slackbuilds.org>
wrote:

> > I'll be pushing an update for python3-PyYAML, but I am hoping the
> > maintainer for PyYAML, will update that version as well to keep them in
> > sync. I'll be reaching out later today.
>
> I have pushed both PyYAML and python3-PyYAML to 3.13 in my branch
> no changes needed :)
>
>
> --
> Willy Sudiarto Raharjo
>

Thanks Willy!

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190303/db97d9a7/attachment.html>

From yth at ythogtha.org  Mon Mar  4 06:45:57 2019
From: yth at ythogtha.org (Arnaud)
Date: Mon, 4 Mar 2019 07:45:57 +0100
Subject: [Slackbuilds-users] Updates - 20190302.1
In-Reply-To: <65af7f6c-e7c2-6135-008f-0531b99386c2@linux.com>
References: <b1eb2576-80e4-376c-42c7-9783e6686181@slackbuilds.org>
 <20190303210151.07335701c6d529618b3d9cdd@ythogtha.org>
 <65af7f6c-e7c2-6135-008f-0531b99386c2@linux.com>
Message-ID: <20190304074557.426920dbf01b15bd960c9e0f@ythogtha.org>

> On 4/3/19 6:01 am, Arnaud wrote:
> > 
> > opencolorio has another problem : the download URL does not exists anymore,
> > however even with a version bump from 1.0.9.20170426 to 1.1.0,
> 
> the existing version is already 1.1.0 (since April 2018) so no version
> bump should be needed. Do you have a recent version of the SBo tree?
> 
> 
> > even with
> > -std=c++11 or std=gnu++11, it doesn't seem to build.
> > So I can't tell if it does work or not with python 3.7.
> 
> Version 1.1.0 of opencolorio builds fine here in a fresh x86_64 VM
> without any change to the SlackBuild and using latest python3-3.7.2.
> 
> chris

Hmm, so there definitely is something rotten in the kingdom of my bloated box.
Hence ma diagnostic becomes :
? opencolorio may not build on a bloated 14.2+SBo box for whatever reason, but
it builds pretty fine on a clean VM/chrooted 14.2 installation ! ?

Case closed, thanks :)


-- 
Arnaud <yth at ythogtha.org>

From klaatu at mixedsignals.ml  Mon Mar  4 07:21:54 2019
From: klaatu at mixedsignals.ml (Klaatu)
Date: Mon, 04 Mar 2019 20:21:54 +1300
Subject: [Slackbuilds-users] MuseScore Slackbuild.
In-Reply-To: <CAAZPBMjrQEbNdScLCs9m8DH=1mQdYZcO2BgwJAgFXzOhEDfpnA@mail.gmail.com>
References: <4c8fe995-e863-1c8c-f441-70905027889f@googlemail.com>
 <a80100a0b10d4dbc56e33c3a3263c420@mixedsignals.ml>
 <4902d3c4-8fb6-8ab2-c3ce-900afc792272@googlemail.com>
 <CAAZPBMjrQEbNdScLCs9m8DH=1mQdYZcO2BgwJAgFXzOhEDfpnA@mail.gmail.com>
Message-ID: <D94942C5-6B3E-4ED5-80AC-8D402F259612@mixedsignals.ml>

Thanks,  i've updated it and a PR is pending. 

On 4 March 2019 2:01:42 PM NZDT, Larry Hajali <larryhaja at gmail.com> wrote:
>On Tue, Feb 26, 2019 at 5:19 AM Tim Dickson via SlackBuilds-users <
>slackbuilds-users at slackbuilds.org> wrote:
>
>> On 25/02/2019 22:55, klaatu at mixedsignals.ml wrote:
>> > On 2019-02-25 16:03, Tim Dickson via SlackBuilds-users wrote:
>> >> Just sending this via sbo mailing list in case klaatu didn't get
>my
>> >> email sent a couple of weeks ago..
>> >>
>> >> Hi Klaatu, any chance of an update to Musescore? The current one
>is
>> >> 3.0.2
>>
>Current version upstream as of this writing is 3.0.4.
>
>
>> >> changing the version number, and adding the line
>> >> sed -i 's| qmake| qmake-qt5|' build/FindQt5.cmake
>> >> just before the "make " lines in the buildscript is all that is
>> >> required to make it work with v3.0.2.
>>
>That didn't have any affect for the build process.
>
>>> Regards, Tim
>> >>
>> >>
>> >
>> > Thanks, Tim. I did get your email and did mean to respond.
>> >
>> > I can't get it to build even with your suggested patch, so I need
>to
>> > dig into why that's not working for me. What version of Qt5 are you
>> > building against?
>> >
>> qt 5.9.7 (SBo version) built with following DOCS=yes
>PROPRIETARY_CODECS=yes
>> graphviz built with gts, qt5 built with optional freetds,  OpenAL,
>> libwebp, opus, pcre2, snappy and wayland
>> qt5-webkit 5.9.0 with optional libwebp
>>
>I built qt5 and qt5-webkit with no extra options or optional packages.
>
>I was able to build MuseScore with version 3.0.4 but I did add a lot of
>changes to the build script.  Most were superficial but some were
>setting
>new options available in the Makefile.  I am adding an attachment of
>the
>diff between the MuseScore 3.0.4 and 2.1.0.
>
>On a side note.  I was not able to build it with QtWebEngine.  I get an
>error that is described here.
>https://musescore.org/en/node/281322
>and something similar here.
>https://musescore.org/en/node/276196
>
>Thanks,
>--Larry

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190304/812c970f/attachment.html>

From 1.41421 at gmail.com  Tue Mar  5 22:47:56 2019
From: 1.41421 at gmail.com (JCA)
Date: Tue, 5 Mar 2019 15:47:56 -0700
Subject: [Slackbuilds-users] crmsh not working
Message-ID: <CAFy1yb3Wg4O-ryb=xuMVWM7HVf=adLwviPaBqLwrkh4C6=GDdg@mail.gmail.com>

I installed the crmsh package into two freshly installed Slackware 14.2
systems, fully patched. According to the info file for this package, it
does not have any explicit dependencies. I nevertheless installed
pacemaker, and all of its dependencies, for that's the context in which I
am going to use crmsh.

When I try to invoke the crm executable that is distributed with crmsh,
here is what I am getting:

# crm
Fatal error:
        No module named lxml
        No module named modules

    Failed to start crmsh! This is likely due to a broken
    installation or a missing dependency.

    If you are using a packaged version of crmsh, please try
    reinstalling the package. Also check your PYTHONPATH and
    make sure that the crmsh module is reachable.

    Please file an issue describing your installation at
    https://github.com/Clusterlabs/crmsh/issues/ .

PYTHONPATH is not set in my shell, and it is not found in any file in
/etc/profile.d. I tried setting it myself with

export PYTHONPATH=/usr/lib64/python2.7/site-packages/crmsh

and a few variations of the above, but it made no difference.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190305/83ea9ce9/attachment.html>

From jebrhansen+SBo at gmail.com  Wed Mar  6 05:05:32 2019
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 5 Mar 2019 22:05:32 -0700
Subject: [Slackbuilds-users] crmsh not working
In-Reply-To: <CAFy1yb3Wg4O-ryb=xuMVWM7HVf=adLwviPaBqLwrkh4C6=GDdg@mail.gmail.com>
References: <CAFy1yb3Wg4O-ryb=xuMVWM7HVf=adLwviPaBqLwrkh4C6=GDdg@mail.gmail.com>
Message-ID: <CANi9qSsgXz3BX0X3Dq+kPOfakkJSkuEKjOG-dHaGWkxT7EPn2Q@mail.gmail.com>

On Tue, Mar 5, 2019, 6:23 PM JCA <1.41421 at gmail.com> wrote:

> I installed the crmsh package into two freshly installed Slackware 14.2
> systems, fully patched. According to the info file for this package, it
> does not have any explicit dependencies. I nevertheless installed
> pacemaker, and all of its dependencies, for that's the context in which I
> am going to use crmsh.
>
> When I try to invoke the crm executable that is distributed with crmsh,
> here is what I am getting:
>
> # crm
> Fatal error:
>         No module named lxml
>         No module named modules
>
>     Failed to start crmsh! This is likely due to a broken
>     installation or a missing dependency.
>
>     If you are using a packaged version of crmsh, please try
>     reinstalling the package. Also check your PYTHONPATH and
>     make sure that the crmsh module is reachable.
>
>     Please file an issue describing your installation at
>     https://github.com/Clusterlabs/crmsh/issues/ .
>
> PYTHONPATH is not set in my shell, and it is not found in any file in
> /etc/profile.d. I tried setting it myself with
>
> export PYTHONPATH=/usr/lib64/python2.7/site-packages/crmsh
>
> and a few variations of the above, but it made no difference.
>

Looks like there might be some undocumented dependencies somewhere. Based
on your error message, I'm assuming you need
https://slackbuilds.org/repository/14.2/python/lxml/ for the missing
"lxml", but I'm not sure what you'd need for the missing "modules".

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190305/f7993212/attachment-0001.html>

From 1.41421 at gmail.com  Wed Mar  6 14:40:30 2019
From: 1.41421 at gmail.com (JCA)
Date: Wed, 6 Mar 2019 07:40:30 -0700
Subject: [Slackbuilds-users] crmsh not working
In-Reply-To: <CANi9qSsgXz3BX0X3Dq+kPOfakkJSkuEKjOG-dHaGWkxT7EPn2Q@mail.gmail.com>
References: <CAFy1yb3Wg4O-ryb=xuMVWM7HVf=adLwviPaBqLwrkh4C6=GDdg@mail.gmail.com>
 <CANi9qSsgXz3BX0X3Dq+kPOfakkJSkuEKjOG-dHaGWkxT7EPn2Q@mail.gmail.com>
Message-ID: <CAFy1yb1sPZreU8R=Y-hOVO808cKCdpYeiRBo-V0-rZc+fB2q2w@mail.gmail.com>

Thanks. After installing the lxml Python component, crm starts with no
problem.

On Tue, Mar 5, 2019 at 10:05 PM Jeremy Hansen <jebrhansen+SBo at gmail.com>
wrote:

> On Tue, Mar 5, 2019, 6:23 PM JCA <1.41421 at gmail.com> wrote:
>
>> I installed the crmsh package into two freshly installed Slackware 14.2
>> systems, fully patched. According to the info file for this package, it
>> does not have any explicit dependencies. I nevertheless installed
>> pacemaker, and all of its dependencies, for that's the context in which I
>> am going to use crmsh.
>>
>> When I try to invoke the crm executable that is distributed with crmsh,
>> here is what I am getting:
>>
>> # crm
>> Fatal error:
>>         No module named lxml
>>         No module named modules
>>
>>     Failed to start crmsh! This is likely due to a broken
>>     installation or a missing dependency.
>>
>>     If you are using a packaged version of crmsh, please try
>>     reinstalling the package. Also check your PYTHONPATH and
>>     make sure that the crmsh module is reachable.
>>
>>     Please file an issue describing your installation at
>>     https://github.com/Clusterlabs/crmsh/issues/ .
>>
>> PYTHONPATH is not set in my shell, and it is not found in any file in
>> /etc/profile.d. I tried setting it myself with
>>
>> export PYTHONPATH=/usr/lib64/python2.7/site-packages/crmsh
>>
>> and a few variations of the above, but it made no difference.
>>
>
> Looks like there might be some undocumented dependencies somewhere. Based
> on your error message, I'm assuming you need
> https://slackbuilds.org/repository/14.2/python/lxml/ for the missing
> "lxml", but I'm not sure what you'd need for the missing "modules".
>
> Jeremy
>
>> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190306/6964e85a/attachment.html>

From dickson.tim at googlemail.com  Wed Mar  6 20:15:46 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Wed, 6 Mar 2019 20:15:46 +0000
Subject: [Slackbuilds-users] opencv-legacy issue
Message-ID: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>

since updating python to 3.7.2 opencv-legacy fails to build with ..

[ 85%] Generating pyopencv_generated_include.h, 
pyopencv_generated_funcs.h, pyopencv_generated_types.h, 
pyopencv_generated_type_reg.h, pyopencv_generated_ns_reg.h
cd /tmp/SBo/opencv-3.1.0/build/modules/python3 && /usr/bin/python3 
/tmp/SBo/opencv-3.1.0/modules/python/python3/..//src2/gen2.py 
/tmp/SBo/opencv-3.1.0/build/modules/python3 
/tmp/SBo/opencv-3.1.0/build/modules/python3/headers.txt
Note: Class l has more than 1 base class (not supported by Python C 
extensions)
 ????? Bases:? cv::a, cv::s, cv::s, cv::A, cv::l, cv::g, cv::o, cv::r, 
cv::i, cv::t, cv::h, cv::m
 ????? Only the first base class will be used
Note: Class l has more than 1 base class (not supported by Python C 
extensions)
 ????? Bases:? cv::a, cv::s, cv::s, cv::F, cv::i, cv::l, cv::e, cv::S, 
cv::t, cv::o, cv::r, cv::a, cv::g, cv::e
 ????? Only the first base class will be used
Generator error: class l (cname=cv::l) already exists
modules/python3/CMakeFiles/opencv_python3.dir/build.make:276: recipe for 
target 'modules/python3/pyopencv_generated_include.h' failed
make[2]: *** [modules/python3/pyopencv_generated_include.h] Error 255
make[2]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
CMakeFiles/Makefile2:14021: recipe for target 
'modules/python3/CMakeFiles/opencv_python3.dir/all' failed
make[1]: *** [modules/python3/CMakeFiles/opencv_python3.dir/all] Error 2
make[1]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2

I've checked, and made sure? opencv-legacy was not previously installed 
when trying to recreate the package.
any ideas?
regards ,Tim


From fernando.lopezjr at gmail.com  Thu Mar  7 03:00:20 2019
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 6 Mar 2019 20:00:20 -0700
Subject: [Slackbuilds-users] libpgf download file not found.
Message-ID: <CALrQ46D-y-PvWPkSgBOgk9NRaxhQWeGC=wi2SZXsbOo4QpxDsA@mail.gmail.com>

libpgf download file not found.

-- 

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

From chris.willing at linux.com  Thu Mar  7 07:31:28 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Thu, 7 Mar 2019 17:31:28 +1000
Subject: [Slackbuilds-users] opencv-legacy issue
In-Reply-To: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
References: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
Message-ID: <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>

On 7/3/19 6:15 am, Tim Dickson via SlackBuilds-users wrote:
> since updating python to 3.7.2 opencv-legacy fails to build with ..
> 
> [ 85%] Generating pyopencv_generated_include.h,
> pyopencv_generated_funcs.h, pyopencv_generated_types.h,
> pyopencv_generated_type_reg.h, pyopencv_generated_ns_reg.h
> cd /tmp/SBo/opencv-3.1.0/build/modules/python3 && /usr/bin/python3
> /tmp/SBo/opencv-3.1.0/modules/python/python3/..//src2/gen2.py
> /tmp/SBo/opencv-3.1.0/build/modules/python3
> /tmp/SBo/opencv-3.1.0/build/modules/python3/headers.txt
> Note: Class l has more than 1 base class (not supported by Python C
> extensions)
> ????? Bases:? cv::a, cv::s, cv::s, cv::A, cv::l, cv::g, cv::o, cv::r,
> cv::i, cv::t, cv::h, cv::m
> ????? Only the first base class will be used
> Note: Class l has more than 1 base class (not supported by Python C
> extensions)
> ????? Bases:? cv::a, cv::s, cv::s, cv::F, cv::i, cv::l, cv::e, cv::S,
> cv::t, cv::o, cv::r, cv::a, cv::g, cv::e
> ????? Only the first base class will be used
> Generator error: class l (cname=cv::l) already exists
> modules/python3/CMakeFiles/opencv_python3.dir/build.make:276: recipe for
> target 'modules/python3/pyopencv_generated_include.h' failed
> make[2]: *** [modules/python3/pyopencv_generated_include.h] Error 255
> make[2]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
> CMakeFiles/Makefile2:14021: recipe for target
> 'modules/python3/CMakeFiles/opencv_python3.dir/all' failed
> make[1]: *** [modules/python3/CMakeFiles/opencv_python3.dir/all] Error 2
> make[1]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
> Makefile:160: recipe for target 'all' failed
> make: *** [all] Error 2
> 
> I've checked, and made sure? opencv-legacy was not previously installed
> when trying to recreate the package.
> any ideas?

It seems python3-3.7.2 is necessary but not sufficient by itself to
trigger this fault. It's actually the presence of the optional numpy3
(which requires python3) during configuration that enables building of
the python3 wrappers, generating the error above during compilation.

The simplest fix is to remove numpy3 from the system. Even with python3
still installed (perhaps needed for other packages), the python3
wrappers will not be generated if numpy is not available during
configuration.

This strategy allows opencv-legacy to build to completion but, of course
without python3 wrappings. Is that a bit deal? Maybe but mitigated by:
    1. possible use of python2 wrappings instead by installing numpy
(not numpy3) which will use built in python2 to generate python2 wrappings.
    2. initially, the only reason for having the opencv-legacy
SlackBuild at all was to satisfy building a particular version of
libkface which was required, in turn, for a particular version of
digikam. AFAIK the python3 wrappings are not needed for this use case.

Serious opencv users that may want the python3 bindings won't be using
opencv-legacy anyway; rather the main opencv. The building of the main
opencv package doesn't suffer this python3/numpy3 problem so I'm
prepared to leave things as they are for opencv-legacy. Of course, if
someone wants to research a fix, I'll happily apply it.

chris

From z.coldplayer at gmail.com  Thu Mar  7 07:43:31 2019
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Thu, 7 Mar 2019 11:43:31 +0400
Subject: [Slackbuilds-users] opencv-legacy issue
In-Reply-To: <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
References: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
 <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
Message-ID: <CAEWL1_-t8CG6AvZB6=g3Oabkzd6zag0DVaf+2gbgpLGV5ASBBA@mail.gmail.com>

I had been able to build digikam with opencv-legacy only.

I'll give it a try next time.


On Thu, 7 Mar 2019, 11:31 Christoph Willing, <chris.willing at linux.com>
wrote:

> On 7/3/19 6:15 am, Tim Dickson via SlackBuilds-users wrote:
> > since updating python to 3.7.2 opencv-legacy fails to build with ..
> >
> > [ 85%] Generating pyopencv_generated_include.h,
> > pyopencv_generated_funcs.h, pyopencv_generated_types.h,
> > pyopencv_generated_type_reg.h, pyopencv_generated_ns_reg.h
> > cd /tmp/SBo/opencv-3.1.0/build/modules/python3 && /usr/bin/python3
> > /tmp/SBo/opencv-3.1.0/modules/python/python3/..//src2/gen2.py
> > /tmp/SBo/opencv-3.1.0/build/modules/python3
> > /tmp/SBo/opencv-3.1.0/build/modules/python3/headers.txt
> > Note: Class l has more than 1 base class (not supported by Python C
> > extensions)
> >       Bases:  cv::a, cv::s, cv::s, cv::A, cv::l, cv::g, cv::o, cv::r,
> > cv::i, cv::t, cv::h, cv::m
> >       Only the first base class will be used
> > Note: Class l has more than 1 base class (not supported by Python C
> > extensions)
> >       Bases:  cv::a, cv::s, cv::s, cv::F, cv::i, cv::l, cv::e, cv::S,
> > cv::t, cv::o, cv::r, cv::a, cv::g, cv::e
> >       Only the first base class will be used
> > Generator error: class l (cname=cv::l) already exists
> > modules/python3/CMakeFiles/opencv_python3.dir/build.make:276: recipe for
> > target 'modules/python3/pyopencv_generated_include.h' failed
> > make[2]: *** [modules/python3/pyopencv_generated_include.h] Error 255
> > make[2]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
> > CMakeFiles/Makefile2:14021: recipe for target
> > 'modules/python3/CMakeFiles/opencv_python3.dir/all' failed
> > make[1]: *** [modules/python3/CMakeFiles/opencv_python3.dir/all] Error 2
> > make[1]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
> > Makefile:160: recipe for target 'all' failed
> > make: *** [all] Error 2
> >
> > I've checked, and made sure  opencv-legacy was not previously installed
> > when trying to recreate the package.
> > any ideas?
>
> It seems python3-3.7.2 is necessary but not sufficient by itself to
> trigger this fault. It's actually the presence of the optional numpy3
> (which requires python3) during configuration that enables building of
> the python3 wrappers, generating the error above during compilation.
>
> The simplest fix is to remove numpy3 from the system. Even with python3
> still installed (perhaps needed for other packages), the python3
> wrappers will not be generated if numpy is not available during
> configuration.
>
> This strategy allows opencv-legacy to build to completion but, of course
> without python3 wrappings. Is that a bit deal? Maybe but mitigated by:
>     1. possible use of python2 wrappings instead by installing numpy
> (not numpy3) which will use built in python2 to generate python2 wrappings.
>     2. initially, the only reason for having the opencv-legacy
> SlackBuild at all was to satisfy building a particular version of
> libkface which was required, in turn, for a particular version of
> digikam. AFAIK the python3 wrappings are not needed for this use case.
>
> Serious opencv users that may want the python3 bindings won't be using
> opencv-legacy anyway; rather the main opencv. The building of the main
> opencv package doesn't suffer this python3/numpy3 problem so I'm
> prepared to leave things as they are for opencv-legacy. Of course, if
> someone wants to research a fix, I'll happily apply it.
>
> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190307/3349596e/attachment-0001.html>

From arkadiusz at drabczyk.org  Thu Mar  7 09:55:16 2019
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Thu, 7 Mar 2019 09:55:16 +0000
Subject: [Slackbuilds-users] libpgf download file not found.
In-Reply-To: <CALrQ46D-y-PvWPkSgBOgk9NRaxhQWeGC=wi2SZXsbOo4QpxDsA@mail.gmail.com>
References: <CALrQ46D-y-PvWPkSgBOgk9NRaxhQWeGC=wi2SZXsbOo4QpxDsA@mail.gmail.com>
Message-ID: <20190307095516.GA1195@raspberrypi>

On Wed, Mar 06, 2019 at 08:00:20pm -0700, Fernando Lopez wrote:
> libpgf download file not found.

It's now at
https://sourceforge.net/projects/libpgf/files/libpgf/7.15.32/libPGF-codec-and-console-src.zip.
Newest release is 7.19.3.

-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From 1.41421 at gmail.com  Wed Mar  6 20:29:10 2019
From: 1.41421 at gmail.com (JCA)
Date: Wed, 6 Mar 2019 13:29:10 -0700
Subject: [Slackbuilds-users] crmsh not working
In-Reply-To: <CAFy1yb1sPZreU8R=Y-hOVO808cKCdpYeiRBo-V0-rZc+fB2q2w@mail.gmail.com>
References: <CAFy1yb3Wg4O-ryb=xuMVWM7HVf=adLwviPaBqLwrkh4C6=GDdg@mail.gmail.com>
 <CANi9qSsgXz3BX0X3Dq+kPOfakkJSkuEKjOG-dHaGWkxT7EPn2Q@mail.gmail.com>
 <CAFy1yb1sPZreU8R=Y-hOVO808cKCdpYeiRBo-V0-rZc+fB2q2w@mail.gmail.com>
Message-ID: <CAFy1yb3f+GNagyr054UiLx0a1JH9MKTEWjmoeUcnkVmdP-PmCA@mail.gmail.com>

By the way, the crmsh version in Slackbuilds (2.2.1) is almost three years
old. I used the Slackbuilds build script to build the latest stable release
(3.0.3) as retrieved from the crmsh github repository; it builds correctly,
and seems to run fine. Interestingly, it reports itself to be version
3.0.1, not 3.0.3. That seems to be something in the build framework as
packaged by the crmsh people - nothing to do with the Slackbuilds build
script.

On Wed, Mar 6, 2019 at 7:40 AM JCA <1.41421 at gmail.com> wrote:

> Thanks. After installing the lxml Python component, crm starts with no
> problem.
>
> On Tue, Mar 5, 2019 at 10:05 PM Jeremy Hansen <jebrhansen+SBo at gmail.com>
> wrote:
>
>> On Tue, Mar 5, 2019, 6:23 PM JCA <1.41421 at gmail.com> wrote:
>>
>>> I installed the crmsh package into two freshly installed Slackware 14.2
>>> systems, fully patched. According to the info file for this package, it
>>> does not have any explicit dependencies. I nevertheless installed
>>> pacemaker, and all of its dependencies, for that's the context in which I
>>> am going to use crmsh.
>>>
>>> When I try to invoke the crm executable that is distributed with crmsh,
>>> here is what I am getting:
>>>
>>> # crm
>>> Fatal error:
>>>         No module named lxml
>>>         No module named modules
>>>
>>>     Failed to start crmsh! This is likely due to a broken
>>>     installation or a missing dependency.
>>>
>>>     If you are using a packaged version of crmsh, please try
>>>     reinstalling the package. Also check your PYTHONPATH and
>>>     make sure that the crmsh module is reachable.
>>>
>>>     Please file an issue describing your installation at
>>>     https://github.com/Clusterlabs/crmsh/issues/ .
>>>
>>> PYTHONPATH is not set in my shell, and it is not found in any file in
>>> /etc/profile.d. I tried setting it myself with
>>>
>>> export PYTHONPATH=/usr/lib64/python2.7/site-packages/crmsh
>>>
>>> and a few variations of the above, but it made no difference.
>>>
>>
>> Looks like there might be some undocumented dependencies somewhere. Based
>> on your error message, I'm assuming you need
>> https://slackbuilds.org/repository/14.2/python/lxml/ for the missing
>> "lxml", but I'm not sure what you'd need for the missing "modules".
>>
>> Jeremy
>>
>>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190306/70affd4d/attachment.html>

From dickson.tim at googlemail.com  Thu Mar  7 17:23:28 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Thu, 7 Mar 2019 17:23:28 +0000
Subject: [Slackbuilds-users] opencv-legacy issue
In-Reply-To: <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
References: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
 <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
Message-ID: <c000ad41-11ce-040d-08b8-2a989d8ebeba@googlemail.com>



On 07/03/2019 07:31, Christoph Willing wrote:
> On 7/3/19 6:15 am, Tim Dickson via SlackBuilds-users wrote:
>> since updating python to 3.7.2 opencv-legacy fails to build with ..
>>
>> [ 85%] Generating pyopencv_generated_include.h,
>> pyopencv_generated_funcs.h, pyopencv_generated_types.h,
>> pyopencv_generated_type_reg.h, pyopencv_generated_ns_reg.h
>> cd /tmp/SBo/opencv-3.1.0/build/modules/python3 && /usr/bin/python3
>> /tmp/SBo/opencv-3.1.0/modules/python/python3/..//src2/gen2.py
>> /tmp/SBo/opencv-3.1.0/build/modules/python3
>> /tmp/SBo/opencv-3.1.0/build/modules/python3/headers.txt
>> Note: Class l has more than 1 base class (not supported by Python C
>> extensions)
>>  ????? Bases:? cv::a, cv::s, cv::s, cv::A, cv::l, cv::g, cv::o, cv::r,
>> cv::i, cv::t, cv::h, cv::m
>>  ????? Only the first base class will be used
>> Note: Class l has more than 1 base class (not supported by Python C
>> extensions)
>>  ????? Bases:? cv::a, cv::s, cv::s, cv::F, cv::i, cv::l, cv::e, cv::S,
>> cv::t, cv::o, cv::r, cv::a, cv::g, cv::e
>>  ????? Only the first base class will be used
>> Generator error: class l (cname=cv::l) already exists
>> modules/python3/CMakeFiles/opencv_python3.dir/build.make:276: recipe for
>> target 'modules/python3/pyopencv_generated_include.h' failed
>> make[2]: *** [modules/python3/pyopencv_generated_include.h] Error 255
>> make[2]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
>> CMakeFiles/Makefile2:14021: recipe for target
>> 'modules/python3/CMakeFiles/opencv_python3.dir/all' failed
>> make[1]: *** [modules/python3/CMakeFiles/opencv_python3.dir/all] Error 2
>> make[1]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
>> Makefile:160: recipe for target 'all' failed
>> make: *** [all] Error 2
>>
>> I've checked, and made sure? opencv-legacy was not previously installed
>> when trying to recreate the package.
>> any ideas?
> It seems python3-3.7.2 is necessary but not sufficient by itself to
> trigger this fault. It's actually the presence of the optional numpy3
> (which requires python3) during configuration that enables building of
> the python3 wrappers, generating the error above during compilation.
>
> The simplest fix is to remove numpy3 from the system. Even with python3
> still installed (perhaps needed for other packages), the python3
> wrappers will not be generated if numpy is not available during
> configuration.
>
> This strategy allows opencv-legacy to build to completion but, of course
> without python3 wrappings. Is that a bit deal? Maybe but mitigated by:
>      1. possible use of python2 wrappings instead by installing numpy
> (not numpy3) which will use built in python2 to generate python2 wrappings.
>      2. initially, the only reason for having the opencv-legacy
> SlackBuild at all was to satisfy building a particular version of
> libkface which was required, in turn, for a particular version of
> digikam. AFAIK the python3 wrappings are not needed for this use case.
>
> Serious opencv users that may want the python3 bindings won't be using
> opencv-legacy anyway; rather the main opencv. The building of the main
> opencv package doesn't suffer this python3/numpy3 problem so I'm
> prepared to leave things as they are for opencv-legacy. Of course, if
> someone wants to research a fix, I'll happily apply it.
>
> chris
>
I use it for frei0r (an ffmpeg optional dep), and vsxu (a vlc optional 
dep), and vlc (a direct optional dep)

vlc fails to build (with the opencv option) with opencv (as opposed to 
opencv-legacy )
regards, Tim


From 1.41421 at gmail.com  Thu Mar  7 16:30:45 2019
From: 1.41421 at gmail.com (JCA)
Date: Thu, 7 Mar 2019 09:30:45 -0700
Subject: [Slackbuilds-users] crmsh not working
In-Reply-To: <CAFy1yb3f+GNagyr054UiLx0a1JH9MKTEWjmoeUcnkVmdP-PmCA@mail.gmail.com>
References: <CAFy1yb3Wg4O-ryb=xuMVWM7HVf=adLwviPaBqLwrkh4C6=GDdg@mail.gmail.com>
 <CANi9qSsgXz3BX0X3Dq+kPOfakkJSkuEKjOG-dHaGWkxT7EPn2Q@mail.gmail.com>
 <CAFy1yb1sPZreU8R=Y-hOVO808cKCdpYeiRBo-V0-rZc+fB2q2w@mail.gmail.com>
 <CAFy1yb3f+GNagyr054UiLx0a1JH9MKTEWjmoeUcnkVmdP-PmCA@mail.gmail.com>
Message-ID: <CAFy1yb2SpS5rOXvYxds6nWv=1wWHBzkT_eWEhuWm5i2Z0Mzmrw@mail.gmail.com>

I am beginning to wonder if this is at all useable under Slackware. With
version 2.2.1 I am getting the following:

# crm
crm(live)# cluster
crm(live)cluster# init
ERROR: cluster.init: Error when loading script init: Failed to load yaml
module: No module named yaml

I installed PyYAML from Slackbuilds, and this error disappeared. But things
were not any better afterwards:

# crm cluster init --name FirstCluster --nodes "NodeOne NodeTwo"
INFO: Initialize a new cluster
INFO: Nodes: --name, FirstCluster, --nodes, NodeOne, NodeTwo
Traceback (most recent call last):
  File "/usr/sbin/crm", line 54, in <module>
    rc = main.run()
  File "/usr/lib64/python2.7/site-packages/crmsh/main.py", line 362, in run
    return main_input_loop(context, user_args)
  File "/usr/lib64/python2.7/site-packages/crmsh/main.py", line 244, in
main_input_loop
    rc = handle_noninteractive_use(context, user_args)
  File "/usr/lib64/python2.7/site-packages/crmsh/main.py", line 200, in
handle_noninteractive_use
    if context.run(' '.join(l)):
  File "/usr/lib64/python2.7/site-packages/crmsh/ui_context.py", line 75,
in run
    rv = self.execute_command() is not False
  File "/usr/lib64/python2.7/site-packages/crmsh/ui_context.py", line 245,
in execute_command
    rv = self.command_info.function(*arglist)
  File "/usr/lib64/python2.7/site-packages/crmsh/ui_cluster.py", line 110,
in do_init
    return scripts.run(script, script_args(args), script_printer())
  File "/usr/lib64/python2.7/site-packages/crmsh/scripts.py", line 2059, in
run
    opts = _make_options(params)
  File "/usr/lib64/python2.7/site-packages/crmsh/scripts.py", line 391, in
_make_options
    opts = parallax.Options()
NameError: global name 'parallax' is not defined

This is getting more and more disappointing. With version 3.0.3 things are,
if anything, even more discouraging - it seems to assume the presence of an
infrastructure found in distributions such as Red Hat, Ubuntu and Debian,
but not in Slackware:

# crm cluster init --name ClusterOne --nodes "nodeone nodetwo"
! NTP is not configured to start at system boot.
! No watchdog device found. If SBD is used, the cluster will be unable to
start without a watchdog.
Do you want to continue anyway (y/n)? y
! Firewall: Could not open ports tcp=30865|5560|7630|21064, udp=
ERROR: cluster.init: Failed to start sshd.service

Just about every output line above represents what I described:
   1) The ntpd daemon is running in this system, and /etc/rc.d/rc.ntpd is
executable. Either it is trying to do something with the concourse of
systemd, or it is looking for SystemV init files.
   2) No clue about the watchdog warning.
   3) There are no iptables rules in this system - root can open any ports
it wants. Maybe it is looking for the firewalld daemon?
   4) sshd.service is how one would typically refer to the SSH daemon in
the Linux distributions above, which start it with incantations like
"service sshd start", which does not exist in Slackware. The SSH daemon was
already running in this system, anyway, and /etc/rc.d/rc.sshd is executable.

Anybody been able to get this (either version) to work at all under
Slackware?


On Wed, Mar 6, 2019 at 1:29 PM JCA <1.41421 at gmail.com> wrote:

> By the way, the crmsh version in Slackbuilds (2.2.1) is almost three years
> old. I used the Slackbuilds build script to build the latest stable release
> (3.0.3) as retrieved from the crmsh github repository; it builds correctly,
> and seems to run fine. Interestingly, it reports itself to be version
> 3.0.1, not 3.0.3. That seems to be something in the build framework as
> packaged by the crmsh people - nothing to do with the Slackbuilds build
> script.
>
> On Wed, Mar 6, 2019 at 7:40 AM JCA <1.41421 at gmail.com> wrote:
>
>> Thanks. After installing the lxml Python component, crm starts with no
>> problem.
>>
>> On Tue, Mar 5, 2019 at 10:05 PM Jeremy Hansen <jebrhansen+SBo at gmail.com>
>> wrote:
>>
>>> On Tue, Mar 5, 2019, 6:23 PM JCA <1.41421 at gmail.com> wrote:
>>>
>>>> I installed the crmsh package into two freshly installed Slackware 14.2
>>>> systems, fully patched. According to the info file for this package, it
>>>> does not have any explicit dependencies. I nevertheless installed
>>>> pacemaker, and all of its dependencies, for that's the context in which I
>>>> am going to use crmsh.
>>>>
>>>> When I try to invoke the crm executable that is distributed with crmsh,
>>>> here is what I am getting:
>>>>
>>>> # crm
>>>> Fatal error:
>>>>         No module named lxml
>>>>         No module named modules
>>>>
>>>>     Failed to start crmsh! This is likely due to a broken
>>>>     installation or a missing dependency.
>>>>
>>>>     If you are using a packaged version of crmsh, please try
>>>>     reinstalling the package. Also check your PYTHONPATH and
>>>>     make sure that the crmsh module is reachable.
>>>>
>>>>     Please file an issue describing your installation at
>>>>     https://github.com/Clusterlabs/crmsh/issues/ .
>>>>
>>>> PYTHONPATH is not set in my shell, and it is not found in any file in
>>>> /etc/profile.d. I tried setting it myself with
>>>>
>>>> export PYTHONPATH=/usr/lib64/python2.7/site-packages/crmsh
>>>>
>>>> and a few variations of the above, but it made no difference.
>>>>
>>>
>>> Looks like there might be some undocumented dependencies somewhere.
>>> Based on your error message, I'm assuming you need
>>> https://slackbuilds.org/repository/14.2/python/lxml/ for the missing
>>> "lxml", but I'm not sure what you'd need for the missing "modules".
>>>
>>> Jeremy
>>>
>>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190307/fe3e6b0e/attachment-0001.html>

From chris.willing at linux.com  Thu Mar  7 22:32:50 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Fri, 8 Mar 2019 08:32:50 +1000
Subject: [Slackbuilds-users] opencv-legacy issue
In-Reply-To: <c000ad41-11ce-040d-08b8-2a989d8ebeba@googlemail.com>
References: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
 <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
 <c000ad41-11ce-040d-08b8-2a989d8ebeba@googlemail.com>
Message-ID: <cd3565b3-41ee-dc00-89e7-24065f81c6f4@linux.com>

On 8/3/19 3:23 am, Tim Dickson via SlackBuilds-users wrote:
> 
> 
> On 07/03/2019 07:31, Christoph Willing wrote:
>> On 7/3/19 6:15 am, Tim Dickson via SlackBuilds-users wrote:
>>> since updating python to 3.7.2 opencv-legacy fails to build with ..
>>>
>>> [ 85%] Generating pyopencv_generated_include.h,
>>> pyopencv_generated_funcs.h, pyopencv_generated_types.h,
>>> pyopencv_generated_type_reg.h, pyopencv_generated_ns_reg.h
>>> cd /tmp/SBo/opencv-3.1.0/build/modules/python3 && /usr/bin/python3
>>> /tmp/SBo/opencv-3.1.0/modules/python/python3/..//src2/gen2.py
>>> /tmp/SBo/opencv-3.1.0/build/modules/python3
>>> /tmp/SBo/opencv-3.1.0/build/modules/python3/headers.txt
>>> Note: Class l has more than 1 base class (not supported by Python C
>>> extensions)
>>> ?????? Bases:? cv::a, cv::s, cv::s, cv::A, cv::l, cv::g, cv::o, cv::r,
>>> cv::i, cv::t, cv::h, cv::m
>>> ?????? Only the first base class will be used
>>> Note: Class l has more than 1 base class (not supported by Python C
>>> extensions)
>>> ?????? Bases:? cv::a, cv::s, cv::s, cv::F, cv::i, cv::l, cv::e, cv::S,
>>> cv::t, cv::o, cv::r, cv::a, cv::g, cv::e
>>> ?????? Only the first base class will be used
>>> Generator error: class l (cname=cv::l) already exists
>>> modules/python3/CMakeFiles/opencv_python3.dir/build.make:276: recipe for
>>> target 'modules/python3/pyopencv_generated_include.h' failed
>>> make[2]: *** [modules/python3/pyopencv_generated_include.h] Error 255
>>> make[2]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
>>> CMakeFiles/Makefile2:14021: recipe for target
>>> 'modules/python3/CMakeFiles/opencv_python3.dir/all' failed
>>> make[1]: *** [modules/python3/CMakeFiles/opencv_python3.dir/all] Error 2
>>> make[1]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
>>> Makefile:160: recipe for target 'all' failed
>>> make: *** [all] Error 2
>>>
>>> I've checked, and made sure? opencv-legacy was not previously installed
>>> when trying to recreate the package.
>>> any ideas?
>> It seems python3-3.7.2 is necessary but not sufficient by itself to
>> trigger this fault. It's actually the presence of the optional numpy3
>> (which requires python3) during configuration that enables building of
>> the python3 wrappers, generating the error above during compilation.
>>
>> The simplest fix is to remove numpy3 from the system. Even with python3
>> still installed (perhaps needed for other packages), the python3
>> wrappers will not be generated if numpy is not available during
>> configuration.
>>
>> This strategy allows opencv-legacy to build to completion but, of course
>> without python3 wrappings. Is that a bit deal? Maybe but mitigated by:
>> ???? 1. possible use of python2 wrappings instead by installing numpy
>> (not numpy3) which will use built in python2 to generate python2
>> wrappings.
>> ???? 2. initially, the only reason for having the opencv-legacy
>> SlackBuild at all was to satisfy building a particular version of
>> libkface which was required, in turn, for a particular version of
>> digikam. AFAIK the python3 wrappings are not needed for this use case.
>>
>> Serious opencv users that may want the python3 bindings won't be using
>> opencv-legacy anyway; rather the main opencv. The building of the main
>> opencv package doesn't suffer this python3/numpy3 problem so I'm
>> prepared to leave things as they are for opencv-legacy. Of course, if
>> someone wants to research a fix, I'll happily apply it.
>>
>> chris
>>
> I use it for frei0r (an ffmpeg optional dep), and vsxu (a vlc optional
> dep), and vlc (a direct optional dep)
> 
Yes, thanks for pointing that out. I only took hard deps into account;
various optional deps will increase the range of use cases. However in
these cases, I  don't believe that it (opencv-legacy) needs to be built
with python3 bindings so this python3/numpy3 issue doesn't affect your
particular use case.


> vlc fails to build (with the opencv option) with opencv (as opposed to
> opencv-legacy )>
That's not quite right; the build log for vlc on my desktop machine
shows that plain opencv is available during the build but not recognised
and therefore not used (source file
modules/video_filter/opencv_wrapper.c is not compiled). However the
build itself runs fine, as does the resulting vlc executable.


chris

From chris.willing at linux.com  Fri Mar  8 01:33:38 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Fri, 8 Mar 2019 11:33:38 +1000
Subject: [Slackbuilds-users] crmsh not working
In-Reply-To: <CAFy1yb2SpS5rOXvYxds6nWv=1wWHBzkT_eWEhuWm5i2Z0Mzmrw@mail.gmail.com>
References: <CAFy1yb3Wg4O-ryb=xuMVWM7HVf=adLwviPaBqLwrkh4C6=GDdg@mail.gmail.com>
 <CANi9qSsgXz3BX0X3Dq+kPOfakkJSkuEKjOG-dHaGWkxT7EPn2Q@mail.gmail.com>
 <CAFy1yb1sPZreU8R=Y-hOVO808cKCdpYeiRBo-V0-rZc+fB2q2w@mail.gmail.com>
 <CAFy1yb3f+GNagyr054UiLx0a1JH9MKTEWjmoeUcnkVmdP-PmCA@mail.gmail.com>
 <CAFy1yb2SpS5rOXvYxds6nWv=1wWHBzkT_eWEhuWm5i2Z0Mzmrw@mail.gmail.com>
Message-ID: <ee5b9886-948b-ffbf-d8ae-84743ee3b06c@linux.com>

On 8/3/19 2:30 am, JCA wrote:
> I am beginning to wonder if this is at all useable under Slackware. With
> version 2.2.1 I am getting the following:
> 
> # crm
> crm(live)# cluster
> crm(live)cluster# init
> ERROR: cluster.init: Error when loading script init: Failed to load yaml
> module: No module named yaml
> 
> I installed PyYAML from Slackbuilds, and this error disappeared. But
> things were not any better afterwards:
> 
There's an updated PyYAML in the SBo "ready" queue - for release this
weekend I guess, or right now at:

https://git.slackbuilds.org/slackbuilds/tree/libraries/PyYAML?id=7e4ee9e95

Perhaps the updated PyYAML will help your crmsh issues.

chris

From kristofru at gmail.com  Fri Mar  8 10:09:02 2019
From: kristofru at gmail.com (Chris Abela)
Date: Fri, 8 Mar 2019 11:09:02 +0100
Subject: [Slackbuilds-users] python3-Cython will not build against
 python3-3.7.2
Message-ID: <CAJ2_kYonoxUrCSGYuL2N6RT08kgymokfYezqA5vGKkejxTrXkQ@mail.gmail.com>

python3-Cython built fine against python3-3.6.7 but not against
python3-3.7.2
This is the trace:

running build_ext
cythoning /tmp/SBo/Cython-0.23.4/Cython/Plex/Scanners.py to
/tmp/SBo/Cython-0.23.4/Cython/Plex/Scanners.c
Traceback (most recent call last):
  File "setup.py", line 306, in <module>
    **setup_args
  File "/usr/lib64/python3.7/site-packages/setuptools/__init__.py", line
143, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib64/python3.7/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib64/python3.7/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib64/python3.7/site-packages/setuptools/command/install.py",
line 61, in run
    return orig.install.run(self)
  File "/usr/lib64/python3.7/distutils/command/install.py", line 545, in run
    self.run_command('build')
  File "/usr/lib64/python3.7/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib64/python3.7/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib64/python3.7/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/SBo/Cython-0.23.4/Cython/Distutils/build_ext.py", line 164, in
run
    _build_ext.build_ext.run(self)
  File "/usr/lib64/python3.7/distutils/command/build_ext.py", line 339, in
run
    self.build_extensions()
  File "/tmp/SBo/Cython-0.23.4/Cython/Distutils/build_ext.py", line 171, in
build_extensions
    ext.sources = self.cython_sources(ext.sources, ext)
  File "/tmp/SBo/Cython-0.23.4/Cython/Distutils/build_ext.py", line 320, in
cython_sources
    full_module_name=module_name)
  File "/tmp/SBo/Cython-0.23.4/Cython/Compiler/Main.py", line 677, in
compile
    return compile_single(source, options, full_module_name)
  File "/tmp/SBo/Cython-0.23.4/Cython/Compiler/Main.py", line 630, in
compile_single
    return run_pipeline(source, options, full_module_name)
  File "/tmp/SBo/Cython-0.23.4/Cython/Compiler/Main.py", line 447, in
run_pipeline
    from . import Pipeline
  File "/tmp/SBo/Cython-0.23.4/Cython/Compiler/Pipeline.py", line 9, in
<module>
    from .Visitor import CythonTransform
  File "/tmp/SBo/Cython-0.23.4/Cython/Compiler/Visitor.py", line 15, in
<module>
    from . import ExprNodes
  File "/tmp/SBo/Cython-0.23.4/Cython/Compiler/ExprNodes.py", line 2713
    await = None
          ^
SyntaxError: invalid syntax
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190308/60369b44/attachment.html>

From chris.willing at linux.com  Fri Mar  8 11:04:42 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Fri, 8 Mar 2019 21:04:42 +1000
Subject: [Slackbuilds-users] python3-Cython will not build against
 python3-3.7.2
In-Reply-To: <CAJ2_kYonoxUrCSGYuL2N6RT08kgymokfYezqA5vGKkejxTrXkQ@mail.gmail.com>
References: <CAJ2_kYonoxUrCSGYuL2N6RT08kgymokfYezqA5vGKkejxTrXkQ@mail.gmail.com>
Message-ID: <0abe8aa0-9065-a8f1-1c99-8360725dd02f@linux.com>

On 8/3/19 8:09 pm, Chris Abela wrote:
> python3-Cython built fine against python3-3.6.7 but not against
> python3-3.7.2
>
There's a fix in the ready queue for next SBo update at the weekend. If
you need it sooner, it's at:

https://git.slackbuilds.org/slackbuilds/tree/python/python3-Cython?id=c2f908c8f

chris

From dickson.tim at googlemail.com  Fri Mar  8 12:10:09 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Fri, 8 Mar 2019 12:10:09 +0000
Subject: [Slackbuilds-users] opencv-legacy issue
In-Reply-To: <cd3565b3-41ee-dc00-89e7-24065f81c6f4@linux.com>
References: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
 <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
 <c000ad41-11ce-040d-08b8-2a989d8ebeba@googlemail.com>
 <cd3565b3-41ee-dc00-89e7-24065f81c6f4@linux.com>
Message-ID: <a8f6f281-d2c9-7de8-d461-a76c89e42012@googlemail.com>

On 07/03/2019 22:32, Christoph Willing wrote:
> On 8/3/19 3:23 am, Tim Dickson via SlackBuilds-users wrote:
>>
>> On 07/03/2019 07:31, Christoph Willing wrote:
>>> On 7/3/19 6:15 am, Tim Dickson via SlackBuilds-users wrote:
>>>> since updating python to 3.7.2 opencv-legacy fails to build with ..
>>>>
>>>> [ 85%] Generating pyopencv_generated_include.h,
>>>> pyopencv_generated_funcs.h, pyopencv_generated_types.h,
>>>> pyopencv_generated_type_reg.h, pyopencv_generated_ns_reg.h
>>>> cd /tmp/SBo/opencv-3.1.0/build/modules/python3 && /usr/bin/python3
>>>> /tmp/SBo/opencv-3.1.0/modules/python/python3/..//src2/gen2.py
>>>> /tmp/SBo/opencv-3.1.0/build/modules/python3
>>>> /tmp/SBo/opencv-3.1.0/build/modules/python3/headers.txt
>>>> Note: Class l has more than 1 base class (not supported by Python C
>>>> extensions)
>>>>  ?????? Bases:? cv::a, cv::s, cv::s, cv::A, cv::l, cv::g, cv::o, cv::r,
>>>> cv::i, cv::t, cv::h, cv::m
>>>>  ?????? Only the first base class will be used
>>>> Note: Class l has more than 1 base class (not supported by Python C
>>>> extensions)
>>>>  ?????? Bases:? cv::a, cv::s, cv::s, cv::F, cv::i, cv::l, cv::e, cv::S,
>>>> cv::t, cv::o, cv::r, cv::a, cv::g, cv::e
>>>>  ?????? Only the first base class will be used
>>>> Generator error: class l (cname=cv::l) already exists
>>>> modules/python3/CMakeFiles/opencv_python3.dir/build.make:276: recipe for
>>>> target 'modules/python3/pyopencv_generated_include.h' failed
>>>> make[2]: *** [modules/python3/pyopencv_generated_include.h] Error 255
>>>> make[2]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
>>>> CMakeFiles/Makefile2:14021: recipe for target
>>>> 'modules/python3/CMakeFiles/opencv_python3.dir/all' failed
>>>> make[1]: *** [modules/python3/CMakeFiles/opencv_python3.dir/all] Error 2
>>>> make[1]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
>>>> Makefile:160: recipe for target 'all' failed
>>>> make: *** [all] Error 2
>>>>
>>>> I've checked, and made sure? opencv-legacy was not previously installed
>>>> when trying to recreate the package.
>>>> any ideas?
>>> It seems python3-3.7.2 is necessary but not sufficient by itself to
>>> trigger this fault. It's actually the presence of the optional numpy3
>>> (which requires python3) during configuration that enables building of
>>> the python3 wrappers, generating the error above during compilation.
>>>
>>> The simplest fix is to remove numpy3 from the system. Even with python3
>>> still installed (perhaps needed for other packages), the python3
>>> wrappers will not be generated if numpy is not available during
>>> configuration.
>>>
>>> This strategy allows opencv-legacy to build to completion but, of course
>>> without python3 wrappings. Is that a bit deal? Maybe but mitigated by:
>>>  ???? 1. possible use of python2 wrappings instead by installing numpy
>>> (not numpy3) which will use built in python2 to generate python2
>>> wrappings.
>>>  ???? 2. initially, the only reason for having the opencv-legacy
>>> SlackBuild at all was to satisfy building a particular version of
>>> libkface which was required, in turn, for a particular version of
>>> digikam. AFAIK the python3 wrappings are not needed for this use case.
>>>
>>> Serious opencv users that may want the python3 bindings won't be using
>>> opencv-legacy anyway; rather the main opencv. The building of the main
>>> opencv package doesn't suffer this python3/numpy3 problem so I'm
>>> prepared to leave things as they are for opencv-legacy. Of course, if
>>> someone wants to research a fix, I'll happily apply it.
>>>
>>> chris
>>>
>> I use it for frei0r (an ffmpeg optional dep), and vsxu (a vlc optional
>> dep), and vlc (a direct optional dep)
>>
> Yes, thanks for pointing that out. I only took hard deps into account;
> various optional deps will increase the range of use cases. However in
> these cases, I  don't believe that it (opencv-legacy) needs to be built
> with python3 bindings so this python3/numpy3 issue doesn't affect your
> particular use case.
>
>
>> vlc fails to build (with the opencv option) with opencv (as opposed to
>> opencv-legacy )>
> That's not quite right; the build log for vlc on my desktop machine
> shows that plain opencv is available during the build but not recognised
> and therefore not used (source file
> modules/video_filter/opencv_wrapper.c is not compiled). However the
> build itself runs fine, as does the resulting vlc executable.
>
>
> chris
>
i get
checking for libbluray >= 0.6.2... yes
checking for opencv > 2.0... no
configure: error: Library opencv > 2.0 needed for opencv was not found
even though ls /var/log/packages/opencv* gives
/var/log/packages/opencv-4.0.1-x86_64-3_SBo

I think the problem is that opencv version 4 reports itself as opencv4 
to pkg-config whereas opencv-legacy reports itself as opencv
copying /usr/lib64/pkgconfig/opencv4 to /usr/lib64/pkgconfig/opencv gets 
further and bails at

/usr/include/opencv4/opencv2/core/cvdef.h:109:47: warning: "__cplusplus" 
is not defined [-Wundef]
 ?#? if (defined(__GXX_EXPERIMENTAL_CXX0X__) || __cplusplus >= 201103L)
 ?????????????????????????????????????????????? ^
In file included from /usr/include/opencv4/opencv2/core/types_c.h:82:0,
 ???????????????? from /usr/include/opencv4/opencv2/core/core_c.h:48,
 ???????????????? from video_filter/opencv_wrapper.c:42:
/usr/include/opencv4/opencv2/core/cvdef.h:647:7: warning: "__cplusplus" 
is not defined [-Wundef]
 ?#? if __cplusplus >= 201103L || (defined(_MSC_VER) && _MSC_VER >= 1800)
 ?????? ^
/usr/include/opencv4/opencv2/core/cvdef.h:656:4: error: #error "OpenCV 
4.x+ requires enabled C++11 support"
 ?#? error "OpenCV 4.x+ requires enabled C++11 support"
 ??? ^
/usr/include/opencv4/opencv2/core/cvdef.h:661:17: fatal error: array: No 
such file or directory
compilation terminated.
Makefile:21527: recipe for target 
'video_filter/libopencv_wrapper_plugin_la-opencv_wrapper.lo' failed
make[4]: *** 
[video_filter/libopencv_wrapper_plugin_la-opencv_wrapper.lo] Error 1
make[4]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
Makefile:26254: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
Makefile:11314: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
Makefile:1539: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/vlc-3.0.6'
Makefile:1424: recipe for target 'all' failed
make: *** [all] Error 2

To fix that error I had to modify the slackbuild, specifically the line 
calling ./configure see below
CXXFLAGS="$SLKCFLAGS -std=c++11" \

Once I did this, vlc completed with just opencv4 installed, and played a 
test mp4 file.

If you had both opencv and opencv-legacy installed at the same time you 
would not notice, but vlc would be built with the legacy version, 
instead of v4, because they are stored in different locations. ( 
..../opencv verses ..../opencv4/opencv? ) and vlc checks the old version 
not the new one.
whether the pkg-config issue is an opencv one or a vlc one is open to 
question.
regards, Tim



From melikamp at melikamp.com  Fri Mar  8 15:06:50 2019
From: melikamp at melikamp.com (Ivan Zaigralin)
Date: Fri, 08 Mar 2019 07:06:50 -0800
Subject: [Slackbuilds-users] R statistics
In-Reply-To: <448d00c09e0e50697c6d6cb854df6f70.squirrel@email.fatcow.com>
References: <448d00c09e0e50697c6d6cb854df6f70.squirrel@email.fatcow.com>
Message-ID: <2100536.th7SbBIgJe@ithil>

That's fine by me :)

On Friday, March 08, 2019 02:32:18 you wrote:
> Hi, would you be interested in letting me maintain R for Slackware?  I use
> it daily so updating it is a routine for me.
> 
> Cheers,
> Andrew
> 
> phalange on LQ and IRC
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190308/250ec671/attachment.asc>

From kristofru at gmail.com  Fri Mar  8 16:37:13 2019
From: kristofru at gmail.com (Chris Abela)
Date: Fri, 8 Mar 2019 17:37:13 +0100
Subject: [Slackbuilds-users] python3-Cython will not build against
 python3-3.7.2
In-Reply-To: <0abe8aa0-9065-a8f1-1c99-8360725dd02f@linux.com>
References: <CAJ2_kYonoxUrCSGYuL2N6RT08kgymokfYezqA5vGKkejxTrXkQ@mail.gmail.com>
 <0abe8aa0-9065-a8f1-1c99-8360725dd02f@linux.com>
Message-ID: <CAJ2_kYr7EWuuqvL-EyT6ZAcO+JWvsuV4qPRurzV3h3rZkYd3Bw@mail.gmail.com>

Thank You

On Fri, 8 Mar 2019, 12:04 Christoph Willing, <chris.willing at linux.com>
wrote:

> On 8/3/19 8:09 pm, Chris Abela wrote:
> > python3-Cython built fine against python3-3.6.7 but not against
> > python3-3.7.2
> >
> There's a fix in the ready queue for next SBo update at the weekend. If
> you need it sooner, it's at:
>
>
> https://git.slackbuilds.org/slackbuilds/tree/python/python3-Cython?id=c2f908c8f
>
> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190308/121f9b51/attachment.html>

From didier at slint.fr  Fri Mar  8 20:45:42 2019
From: didier at slint.fr (Didier Spaier)
Date: Fri, 8 Mar 2019 21:45:42 +0100
Subject: [Slackbuilds-users] Is it doable to have two glib2 versions
 installed?
Message-ID: <2c6f3e85-b462-df60-29e2-8b8564ee52d9@slint.fr>

Hello,

I just asked this question on LQ ,but  maybe not everyone here will read it, so...

Currently glib2-2.46.2 is included in Slackware version 14.2

However I want to upgrade a software to a version that needs glib2 >= 2.48.0.

Upgrading glib2 is easy but I fear that would break other software that depend on it. Am I right?

If the answer is yes, is there a way to make two versions of glib2 coexist, and then how?

Maybe something like installing the newer version in another location and indicate it to the dependent software that needs this one at build time, although that'd make maintenance harder.

Any clue appreciated.

Best,

Didier

From dickson.tim at googlemail.com  Sat Mar  9 11:55:25 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Sat, 9 Mar 2019 11:55:25 +0000
Subject: [Slackbuilds-users] python update report
Message-ID: <b758c98d-0b81-89e3-c802-d8d84f19e6eb@googlemail.com>

the following python modules appear to work with the new python (3.7.2)

alabaster 0.7.10-1
atomicwrites 1.1.5-1
attrs 18.2.0
babel 2.5.3-1
docutils 0.14
funcsigs 1.0.2-1
idna 2.6
Jinja2 2.10-1
pytz 2018.3-1
imagesize 0.7.1
MarkupSafe 1.1.0-1
more-itertools 4.1.0-1
mypy_extensions 0.4.1
mypy 0.670-1
packaging 17.1
pathlib2 2.3.2
pluggy 0.6.0-1
py 1.6.0
Pygments 2.1.3
pyparsing 2.3.1
PyStemmer 1.3.0
pytest 3.8.2-1
pytest-runner 4.2
python-certifi 2018.11.29
python-chardet 3.0.4
python-requests 2.20.1-1
python-scandir 1.8-1
python-urllib3 1.23
python3-astroid 2.1.0-1
python3-docutils 0.14-1
python3-isort 4.3.9-1
python3-jedi 0.13.2-1
python3-lazy-object-proxy 1.3.1-1
python3-mccabe 0.6.1-1
python3-parso 0.3.4-1
python3-pylint 2.2.2-1
python3-pyserial 3.4-1
python3-wrapt 1.11.1-1
setuptools-scm 3.1.0
six 1.12.0
snowballstemmer 1.2.1-2
Sphinx 1.8.4-1
sphinxcontrib-websupport 1.1.0-1
thonny 3.0.8
typed_ast 1.3.1-1
typing 3.6.4

(at least thonny, which uses them all works :-)? )

I also noticed that libwebp has a python3 binding, so it may be worth 
mentioning it as an optional dep
(it created content in /usr/lib64/python3.x ) where x is 6 or 7
regards, Tim

From 1.41421 at gmail.com  Fri Mar  8 16:27:54 2019
From: 1.41421 at gmail.com (JCA)
Date: Fri, 8 Mar 2019 09:27:54 -0700
Subject: [Slackbuilds-users] crmsh not working
In-Reply-To: <ee5b9886-948b-ffbf-d8ae-84743ee3b06c@linux.com>
References: <CAFy1yb3Wg4O-ryb=xuMVWM7HVf=adLwviPaBqLwrkh4C6=GDdg@mail.gmail.com>
 <CANi9qSsgXz3BX0X3Dq+kPOfakkJSkuEKjOG-dHaGWkxT7EPn2Q@mail.gmail.com>
 <CAFy1yb1sPZreU8R=Y-hOVO808cKCdpYeiRBo-V0-rZc+fB2q2w@mail.gmail.com>
 <CAFy1yb3f+GNagyr054UiLx0a1JH9MKTEWjmoeUcnkVmdP-PmCA@mail.gmail.com>
 <CAFy1yb2SpS5rOXvYxds6nWv=1wWHBzkT_eWEhuWm5i2Z0Mzmrw@mail.gmail.com>
 <ee5b9886-948b-ffbf-d8ae-84743ee3b06c@linux.com>
Message-ID: <CAFy1yb3vzFVWqP6Tt_oKQc8RTgqAwQ1_m0YK+o8+Ssiq5OhWOA@mail.gmail.com>

I don't think that'll do it. I believe another dependency is missing -
something called python-parallax, which does not seem to be available in
Slackbuilds.

On Thu, Mar 7, 2019 at 6:33 PM Christoph Willing <chris.willing at linux.com>
wrote:

> On 8/3/19 2:30 am, JCA wrote:
> > I am beginning to wonder if this is at all useable under Slackware. With
> > version 2.2.1 I am getting the following:
> >
> > # crm
> > crm(live)# cluster
> > crm(live)cluster# init
> > ERROR: cluster.init: Error when loading script init: Failed to load yaml
> > module: No module named yaml
> >
> > I installed PyYAML from Slackbuilds, and this error disappeared. But
> > things were not any better afterwards:
> >
> There's an updated PyYAML in the SBo "ready" queue - for release this
> weekend I guess, or right now at:
>
> https://git.slackbuilds.org/slackbuilds/tree/libraries/PyYAML?id=7e4ee9e95
>
> Perhaps the updated PyYAML will help your crmsh issues.
>
> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190308/15c9de79/attachment.html>

From chris.willing at linux.com  Sun Mar 10 07:32:01 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Sun, 10 Mar 2019 17:32:01 +1000
Subject: [Slackbuilds-users] opencv-legacy issue
In-Reply-To: <a8f6f281-d2c9-7de8-d461-a76c89e42012@googlemail.com>
References: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
 <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
 <c000ad41-11ce-040d-08b8-2a989d8ebeba@googlemail.com>
 <cd3565b3-41ee-dc00-89e7-24065f81c6f4@linux.com>
 <a8f6f281-d2c9-7de8-d461-a76c89e42012@googlemail.com>
Message-ID: <9af29761-f6e5-a244-cdfd-a9469bd5df0f@linux.com>

On 8/3/19 10:10 pm, Tim Dickson via SlackBuilds-users wrote:
> I think the problem is that opencv version 4 reports itself as opencv4
> to pkg-config whereas opencv-legacy reports itself as opencv
> copying /usr/lib64/pkgconfig/opencv4 to /usr/lib64/pkgconfig/opencv gets
> further and bails at
> 
> /usr/include/opencv4/opencv2/core/cvdef.h:109:47: warning: "__cplusplus"
> is not defined [-Wundef]
> ?#? if (defined(__GXX_EXPERIMENTAL_CXX0X__) || __cplusplus >= 201103L)
> ?????????????????????????????????????????????? ^
> In file included from /usr/include/opencv4/opencv2/core/types_c.h:82:0,
> ???????????????? from /usr/include/opencv4/opencv2/core/core_c.h:48,
> ???????????????? from video_filter/opencv_wrapper.c:42:
> /usr/include/opencv4/opencv2/core/cvdef.h:647:7: warning: "__cplusplus"
> is not defined [-Wundef]
> ?#? if __cplusplus >= 201103L || (defined(_MSC_VER) && _MSC_VER >= 1800)
> ?????? ^
> /usr/include/opencv4/opencv2/core/cvdef.h:656:4: error: #error "OpenCV
> 4.x+ requires enabled C++11 support"
> ?#? error "OpenCV 4.x+ requires enabled C++11 support"
> ??? ^
> /usr/include/opencv4/opencv2/core/cvdef.h:661:17: fatal error: array: No
> such file or directory
> compilation terminated.
> Makefile:21527: recipe for target
> 'video_filter/libopencv_wrapper_plugin_la-opencv_wrapper.lo' failed
> make[4]: ***
> [video_filter/libopencv_wrapper_plugin_la-opencv_wrapper.lo] Error 1
> make[4]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
> Makefile:26254: recipe for target 'all-recursive' failed
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
> Makefile:11314: recipe for target 'all' failed
> make[2]: *** [all] Error 2
> make[2]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
> Makefile:1539: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/vlc-3.0.6'
> Makefile:1424: recipe for target 'all' failed
> make: *** [all] Error 2
> 
> To fix that error I had to modify the slackbuild, specifically the line
> calling ./configure see below
> CXXFLAGS="$SLKCFLAGS -std=c++11" \
> 
Hi Tim,

I thought I'd try this out but even with the -std=c++11 added to
CXXFLAGS, I still see the same error about missing c++11 suport. Do you
recall doing anything else to help the compilation along?

chris

From arkadiusz at drabczyk.org  Sun Mar 10 13:46:54 2019
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Sun, 10 Mar 2019 14:46:54 +0100
Subject: [Slackbuilds-users] multimedia/dirac: ERROR 404: Not Found
Message-ID: <20190310134654.GA20406@comp.lan>

The funny thing is that previous download link
http://pkgs.fedoraproject.org/repo/pkgs/dirac/dirac-1.0.2.tar.gz/a57c2c5e58062d437d9ab13dffb28f0f/dirac-1.0.2.tar.gz
works well.
-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From dickson.tim at googlemail.com  Sun Mar 10 14:20:43 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Sun, 10 Mar 2019 14:20:43 +0000
Subject: [Slackbuilds-users] opencv-legacy issue
In-Reply-To: <9af29761-f6e5-a244-cdfd-a9469bd5df0f@linux.com>
References: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
 <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
 <c000ad41-11ce-040d-08b8-2a989d8ebeba@googlemail.com>
 <cd3565b3-41ee-dc00-89e7-24065f81c6f4@linux.com>
 <a8f6f281-d2c9-7de8-d461-a76c89e42012@googlemail.com>
 <9af29761-f6e5-a244-cdfd-a9469bd5df0f@linux.com>
Message-ID: <e90155e7-edfa-9441-a304-4eae3f889f4c@googlemail.com>



On 10/03/2019 07:32, Christoph Willing wrote:
> On 8/3/19 10:10 pm, Tim Dickson via SlackBuilds-users wrote:
>> I think the problem is that opencv version 4 reports itself as opencv4
>> to pkg-config whereas opencv-legacy reports itself as opencv
>> copying /usr/lib64/pkgconfig/opencv4 to /usr/lib64/pkgconfig/opencv gets
>> further and bails at
>>
>> /usr/include/opencv4/opencv2/core/cvdef.h:109:47: warning: "__cplusplus"
>> is not defined [-Wundef]
>>  ?#? if (defined(__GXX_EXPERIMENTAL_CXX0X__) || __cplusplus >= 201103L)
>>  ?????????????????????????????????????????????? ^
>> In file included from /usr/include/opencv4/opencv2/core/types_c.h:82:0,
>>  ???????????????? from /usr/include/opencv4/opencv2/core/core_c.h:48,
>>  ???????????????? from video_filter/opencv_wrapper.c:42:
>> /usr/include/opencv4/opencv2/core/cvdef.h:647:7: warning: "__cplusplus"
>> is not defined [-Wundef]
>>  ?#? if __cplusplus >= 201103L || (defined(_MSC_VER) && _MSC_VER >= 1800)
>>  ?????? ^
>> /usr/include/opencv4/opencv2/core/cvdef.h:656:4: error: #error "OpenCV
>> 4.x+ requires enabled C++11 support"
>>  ?#? error "OpenCV 4.x+ requires enabled C++11 support"
>>  ??? ^
>> /usr/include/opencv4/opencv2/core/cvdef.h:661:17: fatal error: array: No
>> such file or directory
>> compilation terminated.
>> Makefile:21527: recipe for target
>> 'video_filter/libopencv_wrapper_plugin_la-opencv_wrapper.lo' failed
>> make[4]: ***
>> [video_filter/libopencv_wrapper_plugin_la-opencv_wrapper.lo] Error 1
>> make[4]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
>> Makefile:26254: recipe for target 'all-recursive' failed
>> make[3]: *** [all-recursive] Error 1
>> make[3]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
>> Makefile:11314: recipe for target 'all' failed
>> make[2]: *** [all] Error 2
>> make[2]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
>> Makefile:1539: recipe for target 'all-recursive' failed
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory '/tmp/SBo/vlc-3.0.6'
>> Makefile:1424: recipe for target 'all' failed
>> make: *** [all] Error 2
>>
>> To fix that error I had to modify the slackbuild, specifically the line
>> calling ./configure see below
>> CXXFLAGS="$SLKCFLAGS -std=c++11" \
>>
> Hi Tim,
>
> I thought I'd try this out but even with the -std=c++11 added to
> CXXFLAGS, I still see the same error about missing c++11 suport. Do you
> recall doing anything else to help the compilation along?
>
> chris
>
my appologies, when I tested it last, it was from a command prompt so I 
forgot to add the OPENCV=yes WAYLAND=yes before calling the build script.
I too am getting it complaining about c++11 for opencv despite it being 
added to the CXXFLAGS in configure, and thus in the makefile. It may be 
that opencv is being called as c instead of c++ but I haven't managed to 
find out more yet.
regards, Tims

From willysr at slackbuilds.org  Sun Mar 10 15:59:38 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 10 Mar 2019 22:59:38 +0700
Subject: [Slackbuilds-users] multimedia/dirac: ERROR 404: Not Found
In-Reply-To: <20190310134654.GA20406@comp.lan>
References: <20190310134654.GA20406@comp.lan>
Message-ID: <734e3dae-2eb7-4798-c470-6e762eaff231@slackbuilds.org>

> The funny thing is that previous download link
> http://pkgs.fedoraproject.org/repo/pkgs/dirac/dirac-1.0.2.tar.gz/a57c2c5e58062d437d9ab13dffb28f0f/dirac-1.0.2.tar.gz
> works well.

FIxed in my branch

Thanks


-- 
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/20190310/4f5c160f/attachment-0001.asc>

From willysr at slackbuilds.org  Sun Mar 10 16:50:36 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 10 Mar 2019 23:50:36 +0700
Subject: [Slackbuilds-users] Nitrogen is at 1.6.1
In-Reply-To: <1c1-5c7c6f00-f-45966680@41618634>
References: <1c1-5c7c6f00-f-45966680@41618634>
Message-ID: <4f1c9e9f-d128-ade5-7293-05b89dabf00e@slackbuilds.org>

> Two weeks ago (Feb 15), I emailed the maintainer (G Edward
> Whiteside,?gedwardwhiteside at gmail.com), requesting an update to the
> slackbuild. I have not received a response, and the script has not been
> updated.
> 
> The currently maintained version is at 20120806_692fdf7, while upstream
> contains version 1.6.1.
> 
> I wish to take over maintainership of the slackbuild. I have the script
> ready for uploading.

Yes sure
the original maintainer never update the script since 9 years ago


-- 
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/20190310/5477fa42/attachment.asc>

From willysr at slackbuilds.org  Sun Mar 10 16:55:56 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 10 Mar 2019 23:55:56 +0700
Subject: [Slackbuilds-users] libpgf download file not found.
In-Reply-To: <20190307095516.GA1195@raspberrypi>
References: <CALrQ46D-y-PvWPkSgBOgk9NRaxhQWeGC=wi2SZXsbOo4QpxDsA@mail.gmail.com>
 <20190307095516.GA1195@raspberrypi>
Message-ID: <b3720ec7-d84e-472b-5a96-bed0085fc70b@slackbuilds.org>

> It's now at
> https://sourceforge.net/projects/libpgf/files/libpgf/7.15.32/libPGF-codec-and-console-src.zip.
> Newest release is 7.19.3.

Thanks
updated in my branch now


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

From chris.willing at linux.com  Sun Mar 10 22:30:14 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Mon, 11 Mar 2019 08:30:14 +1000
Subject: [Slackbuilds-users] opencv-legacy issue
In-Reply-To: <e90155e7-edfa-9441-a304-4eae3f889f4c@googlemail.com>
References: <c0700ed3-9493-8a44-447e-14285e9ced93@googlemail.com>
 <16d91dd3-28b3-81c6-7e6c-b0095b12b11f@linux.com>
 <c000ad41-11ce-040d-08b8-2a989d8ebeba@googlemail.com>
 <cd3565b3-41ee-dc00-89e7-24065f81c6f4@linux.com>
 <a8f6f281-d2c9-7de8-d461-a76c89e42012@googlemail.com>
 <9af29761-f6e5-a244-cdfd-a9469bd5df0f@linux.com>
 <e90155e7-edfa-9441-a304-4eae3f889f4c@googlemail.com>
Message-ID: <dbf0892d-a74f-40e5-b27a-42cb8a14d8c9@linux.com>

On 11/3/19 12:20 am, Tim Dickson wrote:
> 
> 
> On 10/03/2019 07:32, Christoph Willing wrote:
>> On 8/3/19 10:10 pm, Tim Dickson via SlackBuilds-users wrote:
>>> I think the problem is that opencv version 4 reports itself as opencv4
>>> to pkg-config whereas opencv-legacy reports itself as opencv
>>> copying /usr/lib64/pkgconfig/opencv4 to /usr/lib64/pkgconfig/opencv gets
>>> further and bails at
>>>
>>> /usr/include/opencv4/opencv2/core/cvdef.h:109:47: warning: "__cplusplus"
>>> is not defined [-Wundef]
>>> ??#? if (defined(__GXX_EXPERIMENTAL_CXX0X__) || __cplusplus >= 201103L)
>>> ??????????????????????????????????????????????? ^
>>> In file included from /usr/include/opencv4/opencv2/core/types_c.h:82:0,
>>> ????????????????? from /usr/include/opencv4/opencv2/core/core_c.h:48,
>>> ????????????????? from video_filter/opencv_wrapper.c:42:
>>> /usr/include/opencv4/opencv2/core/cvdef.h:647:7: warning: "__cplusplus"
>>> is not defined [-Wundef]
>>> ??#? if __cplusplus >= 201103L || (defined(_MSC_VER) && _MSC_VER >=
>>> 1800)
>>> ??????? ^
>>> /usr/include/opencv4/opencv2/core/cvdef.h:656:4: error: #error "OpenCV
>>> 4.x+ requires enabled C++11 support"
>>> ??#? error "OpenCV 4.x+ requires enabled C++11 support"
>>> ???? ^
>>> /usr/include/opencv4/opencv2/core/cvdef.h:661:17: fatal error: array: No
>>> such file or directory
>>> compilation terminated.
>>> Makefile:21527: recipe for target
>>> 'video_filter/libopencv_wrapper_plugin_la-opencv_wrapper.lo' failed
>>> make[4]: ***
>>> [video_filter/libopencv_wrapper_plugin_la-opencv_wrapper.lo] Error 1
>>> make[4]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
>>> Makefile:26254: recipe for target 'all-recursive' failed
>>> make[3]: *** [all-recursive] Error 1
>>> make[3]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
>>> Makefile:11314: recipe for target 'all' failed
>>> make[2]: *** [all] Error 2
>>> make[2]: Leaving directory '/tmp/SBo/vlc-3.0.6/modules'
>>> Makefile:1539: recipe for target 'all-recursive' failed
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory '/tmp/SBo/vlc-3.0.6'
>>> Makefile:1424: recipe for target 'all' failed
>>> make: *** [all] Error 2
>>>
>>> To fix that error I had to modify the slackbuild, specifically the line
>>> calling ./configure see below
>>> CXXFLAGS="$SLKCFLAGS -std=c++11" \
>>>
>> Hi Tim,
>>
>> I thought I'd try this out but even with the -std=c++11 added to
>> CXXFLAGS, I still see the same error about missing c++11 suport. Do you
>> recall doing anything else to help the compilation along?
>>
>> chris
>>
> my appologies, when I tested it last, it was from a command prompt so I
> forgot to add the OPENCV=yes WAYLAND=yes before calling the build script.
> I too am getting it complaining about c++11 for opencv despite it being
> added to the CXXFLAGS in configure, and thus in the makefile. It may be
> that opencv is being called as c instead of c++ but I haven't managed to
> find out more yet.
> regards, Tims
> 

I just progressed a little further but am stuck again now - reporting
progress in case you (or anyone else?) have any ideas ...

I renamed opencv_wrapper.c as opencv_wrapper.cpp and changed the
appropriate references in modules/video_filter/Makefile.am and ran:
    CXXFLAGS="-fpermissive" ./configure
    make

which successfully build
modules/video_filter/libopencv_wrapper_plugin_la-opencv-wrapper.lo

The associated example is already c++ (opencv_example.cpp) so no
trickery applied but compilation stopped with:

  CXX      video_filter/libopencv_example_plugin_la-opencv_example.lo
video_filter/opencv_example.cpp: In function 'int
OpenFilter(vlc_object_t*)':
video_filter/opencv_example.cpp:119:76: error: 'cvLoad' was not declared
in this scope
     p_sys->p_cascade = (CvHaarClassifierCascade*)cvLoad( filename, 0,
0, 0 );

video_filter/opencv_example.cpp: In function 'void
CloseFilter(vlc_object_t*)':
video_filter/opencv_example.cpp:135:59: error:
'cvReleaseHaarClassifierCascade' was not declared in this scope
         cvReleaseHaarClassifierCascade( &p_sys->p_cascade );
                                                           ^
video_filter/opencv_example.cpp: In function 'picture_t*
Filter(filter_t*, picture_t*)':
video_filter/opencv_example.cpp:178:45: error:
'CV_HAAR_DO_CANNY_PRUNING' was not declared in this scope
                                             CV_HAAR_DO_CANNY_PRUNING,
                                             ^
video_filter/opencv_example.cpp:179:60: error: 'cvHaarDetectObjects' was
not declared in this scope
                                             cvSize(20, 20) );
                                                            ^
video_filter/opencv_example.cpp:204:57: warning: ISO C++ forbids
converting a string constant to 'char*' [-Wwrite-strings]
             p_sys->event_info.p_region[i].p_description = "Face Detected";
                                                         ^
Makefile:23518: recipe for target
'video_filter/libopencv_example_plugin_la-opencv_example.lo' failed



I looked around but couldn't find a cvLoad function (the first error
mentioned) in the opencv4 headers - I guess it's from a very early
opencv version.

I'm not sure where to go from here so any help would be appreciated.

chris

From 1.41421 at gmail.com  Mon Mar 11 15:24:12 2019
From: 1.41421 at gmail.com (JCA)
Date: Mon, 11 Mar 2019 09:24:12 -0600
Subject: [Slackbuilds-users] Syncthing package is old
Message-ID: <CAFy1yb138v9o3bN6Zw1K_G395EvLOsY-ur4VxRuKUiLrnoMe-A@mail.gmail.com>

At version 0.14.43, the Syncthing version in Slackbuilds is over one year
old. There have already been several new versions between 0.14.43 and the
latest - 1.1.0. I have just tested with 1.1.0 under Slackware, and it seems
to work fine, even with remote systems running 0.14.43.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190311/e5f06dd6/attachment.html>

From s.arcus at open-t.co.uk  Tue Mar 12 07:55:30 2019
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Tue, 12 Mar 2019 07:55:30 +0000
Subject: [Slackbuilds-users] Syncthing package is old
In-Reply-To: <CAFy1yb138v9o3bN6Zw1K_G395EvLOsY-ur4VxRuKUiLrnoMe-A@mail.gmail.com>
References: <CAFy1yb138v9o3bN6Zw1K_G395EvLOsY-ur4VxRuKUiLrnoMe-A@mail.gmail.com>
Message-ID: <580b1199-509a-34e1-9e66-3a6cd6ff04b7@open-t.co.uk>

On 11/03/19 15:24, JCA wrote:
> At version 0.14.43, the Syncthing version in Slackbuilds is over one 
> year old. There have already been several new versions between 0.14.43 
> and the latest - 1.1.0. I have just tested with 1.1.0 under Slackware, 
> and it seems to work fine, even with remote systems running 0.14.43.

Thank you for flagging it up - I will submit an updated version in the 
next few days

Sebastian

From matteo.bernardini at gmail.com  Tue Mar 12 09:23:41 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 12 Mar 2019 10:23:41 +0100
Subject: [Slackbuilds-users] qemu and capstone
In-Reply-To: <abfa8427-5b75-fa26-ce0d-d7ae989b201a@gmail.com>
References: <20190225100635.GA4066@giustizia.org>
 <CAPsDuS4WXJwVShwvm5X13hDpk2Vx-gKZVNZTJCUo8cdFJd4Rgw@mail.gmail.com>
 <abfa8427-5b75-fa26-ce0d-d7ae989b201a@gmail.com>
Message-ID: <CAPsDuS7cqW9UKXh2xGfJBwSX7T_AFQbFnDwcXPwWW0D6YNKjLQ@mail.gmail.com>

Il giorno mar 26 feb 2019 alle ore 02:29 King Beowulf
<kingbeowulf at gmail.com> ha scritto:
>
> On 2/25/19 5:19 AM, Matteo Bernardini wrote:
> > I think the build system detects the external capstone and then
> > wrongly tries to use the internal capstone headers in ./include/disas/
> > instead of the system's ones: there's a related discussion on the qemu
> > mailing list
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg04159.html
> >
> > actually, if capstone is installed, with this patch applied qemu builds fine.
> >
> > Matteo
> >
>
> That patch is a year old, for the 2.x series. From the thread, it looks
> like they abandoned it.  qemu "should" be smart enough to find the
> correct headers via pkg-config.
>
> I'll double check for the next release.  This is the 1st time I recall
> anyone mentioning qemu with capstone.
>
> -Ed

BTW, just to give some more elements, today I tried to build qemu from
the script we have in the repository and I noticed that, by default,
it builds end enables the internal capstone.
seems the issues manifest only when an external capstone is installed
prior to building qemu.

Matteo

From slackbuilds at schoepfer.info  Thu Mar 14 11:08:00 2019
From: slackbuilds at schoepfer.info (Franzen)
Date: Thu, 14 Mar 2019 12:08:00 +0100
Subject: [Slackbuilds-users] i3 up for grabs / new maintainer for
 herbstluftwm
In-Reply-To: <CAFhPZZe46ePGfoR6eCLDe2_7-2t=k9d4b=u1RGm7UwN6WiMW0Q@mail.gmail.com>
References: <fd862e6c659371c059c13a5c528aa96f@schoepfer.info>
 <CAFhPZZfRiMGYUpmBsTBmiYLjhCk-Ldnx=QtCzkDy2URb7yXxsQ@mail.gmail.com>
 <e1a99a79f8031990c4f235919f5892a6@schoepfer.info>
 <CAFhPZZe46ePGfoR6eCLDe2_7-2t=k9d4b=u1RGm7UwN6WiMW0Q@mail.gmail.com>
Message-ID: <df01b0d3-e1c2-f982-1737-8fd08f4a6f64@schoepfer.info>

Am 17.11.18 um 14:37 schrieb Emmanuel:
> 
> 
> On Sat, Nov 17, 2018 at 9:38 AM Franzen <slackbuilds at schoepfer.info 
> <mailto:slackbuilds at schoepfer.info>> wrote:
> 
>     On 2018-11-16 21:56, Emmanuel wrote:
>      > Hi All,
>      >
>      > I can take i3 if no one else wants it.
> 
>     As Ricardo is taking "yajl", would you(Emmanuel) also take these?
>     perl-AnyEvent
>     xcb-util-xrm
>     i3status
> 
>     As nothing else depend on these, it is likely they get orphaned
>     otherwise.
> 
> 
> Yes, I can take all 4 packages.

Hi Emmanuel,

i'm still listed as maintainer, would you
please take over?

Johannes

From emmanueln at gmail.com  Thu Mar 14 11:18:28 2019
From: emmanueln at gmail.com (Emmanuel)
Date: Thu, 14 Mar 2019 08:18:28 -0300
Subject: [Slackbuilds-users] i3 up for grabs / new maintainer for
 herbstluftwm
In-Reply-To: <df01b0d3-e1c2-f982-1737-8fd08f4a6f64@schoepfer.info>
References: <fd862e6c659371c059c13a5c528aa96f@schoepfer.info>
 <CAFhPZZfRiMGYUpmBsTBmiYLjhCk-Ldnx=QtCzkDy2URb7yXxsQ@mail.gmail.com>
 <e1a99a79f8031990c4f235919f5892a6@schoepfer.info>
 <CAFhPZZe46ePGfoR6eCLDe2_7-2t=k9d4b=u1RGm7UwN6WiMW0Q@mail.gmail.com>
 <df01b0d3-e1c2-f982-1737-8fd08f4a6f64@schoepfer.info>
Message-ID: <CAFhPZZd+4MDp7iwF99fU=6rkZtsMv=A8O3=BV8E2hV_pMBmbDQ@mail.gmail.com>

Yes, sorry about that, this weekend I will submit a new version.

Best regards

On Thu, Mar 14, 2019 at 8:08 AM Franzen <slackbuilds at schoepfer.info> wrote:

> Am 17.11.18 um 14:37 schrieb Emmanuel:
> >
> >
> > On Sat, Nov 17, 2018 at 9:38 AM Franzen <slackbuilds at schoepfer.info
> > <mailto:slackbuilds at schoepfer.info>> wrote:
> >
> >     On 2018-11-16 21:56, Emmanuel wrote:
> >      > Hi All,
> >      >
> >      > I can take i3 if no one else wants it.
> >
> >     As Ricardo is taking "yajl", would you(Emmanuel) also take these?
> >     perl-AnyEvent
> >     xcb-util-xrm
> >     i3status
> >
> >     As nothing else depend on these, it is likely they get orphaned
> >     otherwise.
> >
> >
> > Yes, I can take all 4 packages.
>
> Hi Emmanuel,
>
> i'm still listed as maintainer, would you
> please take over?
>
> Johannes
>


-- 
*****************
   Emmanuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190314/1f9bca54/attachment.html>

From dave at tty1.uk  Fri Mar 15 15:39:14 2019
From: dave at tty1.uk (Dave Woodfall)
Date: Fri, 15 Mar 2019 15:39:14 +0000
Subject: [Slackbuilds-users] Strawberry (fork of Clementine)
Message-ID: <20190315153914.GA10886@blackholeuniverse.ru>

Matthew asked me if I minded him submitting Strawberry.  This is just
to say it's fine by me.

I didn't get a reply when I emailed him directly so I think my email
is going straight to his spam folder or something, but hopefully he
reads the list.

--

"What is wanted is not the will to believe, but the will to find out,
which is the exact opposite."
    -- Bertrand Russell, "Skeptical_Essays", 1928
-------------- 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/20190315/9ab712e4/attachment.asc>

From slackalaxy at gmail.com  Fri Mar 15 15:44:32 2019
From: slackalaxy at gmail.com (Petar Petrov)
Date: Fri, 15 Mar 2019 17:44:32 +0200
Subject: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a
 scientific publication
Message-ID: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>

Dear All,

I am happy to let you know Slackware and SlackBuilds.org were cited in
the most recent publication of our group. The paper is called
"Computational analysis of the evolutionarily conserved Missing In
Metastasis/Metastasis Suppressor 1 gene predicts novel interactions,
regulatory regions and transcriptional control" and was published in
Scientific Reports:

https://www.nature.com/articles/s41598-019-40697-1

I would like to express my sincere gratitude to Slackware and the SBo community.

Almost all bioinformatics software used in the work was installed from
SBo. Slackware and SBo are credited in Materials and Methods >
Software and data

Here's a post in my humble blog, if you want more details:
https://slackalaxy.com/2019/03/15/slackware-and-slackbuilds-org-cited-in-a-scientific-publication/

...and of course you are very welcome to read the paper!

all the best,

Petar

From lists at osh.id.au  Fri Mar 15 17:11:52 2019
From: lists at osh.id.au (David O'Shaughnessy)
Date: Fri, 15 Mar 2019 13:11:52 -0400
Subject: [Slackbuilds-users] 
 =?utf-8?q?Slackware_and_SlackBuilds=2Eorg_ci?=
 =?utf-8?q?ted_in_a_scientific_publication?=
In-Reply-To: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
Message-ID: <d9241b42-653d-4dc8-bfae-0aefb4c176af@www.fastmail.com>

On Fri, 15 Mar 2019, at 8:44 AM, Petar Petrov wrote:
> Dear All,
> 
> I am happy to let you know Slackware and SlackBuilds.org were cited in
> the most recent publication of our group. The paper is called
> "Computational analysis of the evolutionarily conserved Missing In
> Metastasis/Metastasis Suppressor 1 gene predicts novel interactions,
> regulatory regions and transcriptional control" and was published in
> Scientific Reports:
> 
> https://www.nature.com/articles/s41598-019-40697-1

Very cool, thanks for sharing this :)

--
Dave

From atelszewski at gmail.com  Fri Mar 15 17:49:49 2019
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 15 Mar 2019 18:49:49 +0100
Subject: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a
 scientific publication
In-Reply-To: <d9241b42-653d-4dc8-bfae-0aefb4c176af@www.fastmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
 <d9241b42-653d-4dc8-bfae-0aefb4c176af@www.fastmail.com>
Message-ID: <b6b4484e-d10e-91f3-3837-812e79e5ac77@gmail.com>

On 15/03/2019 18:11, David O'Shaughnessy wrote:
> On Fri, 15 Mar 2019, at 8:44 AM, Petar Petrov wrote:
>> Dear All,
>>
>> I am happy to let you know Slackware and SlackBuilds.org were cited in
>> the most recent publication of our group. The paper is called
>> "Computational analysis of the evolutionarily conserved Missing In
>> Metastasis/Metastasis Suppressor 1 gene predicts novel interactions,
>> regulatory regions and transcriptional control" and was published in
>> Scientific Reports:
>>
>> https://www.nature.com/articles/s41598-019-40697-1
> 
> Very cool, thanks for sharing this :)
> 

Really cool! :-)


-- 
Best regards,
Andrzej Telszewski

From rworkman at slackbuilds.org  Fri Mar 15 18:51:40 2019
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 15 Mar 2019 13:51:40 -0500
Subject: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a
 scientific publication
In-Reply-To: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
Message-ID: <20190315135140.40a0ec78@home.rlworkman.net>

On Fri, 15 Mar 2019 17:44:32 +0200
Petar Petrov <slackalaxy at gmail.com> wrote:

> Dear All,
> 
> I am happy to let you know Slackware and SlackBuilds.org were cited in
> the most recent publication of our group. The paper is called
> "Computational analysis of the evolutionarily conserved Missing In
> Metastasis/Metastasis Suppressor 1 gene predicts novel interactions,
> regulatory regions and transcriptional control" and was published in
> Scientific Reports:
> 
> https://www.nature.com/articles/s41598-019-40697-1
> 
> I would like to express my sincere gratitude to Slackware and the SBo
> community.
> 
> Almost all bioinformatics software used in the work was installed from
> SBo. Slackware and SBo are credited in Materials and Methods >
> Software and data
> 
> Here's a post in my humble blog, if you want more details:
> https://slackalaxy.com/2019/03/15/slackware-and-slackbuilds-org-cited-in-a-scientific-publication/
> 
> ...and of course you are very welcome to read the paper!
> 
> all the best,
> 
> Petar


Very nice, Petar - thanks!!!

-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/20190315/475ab5af/attachment.asc>

From klaatu at mixedsignals.ml  Fri Mar 15 20:39:28 2019
From: klaatu at mixedsignals.ml (klaatu at mixedsignals.ml)
Date: Fri, 15 Mar 2019 15:39:28 -0500
Subject: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a
 scientific publication
In-Reply-To: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
Message-ID: <fd331ddf49016d3ea5b3f74f93f43b29@mixedsignals.ml>

On 2019-03-15 10:44, Petar Petrov wrote:
> Dear All,
> 
> I am happy to let you know Slackware and SlackBuilds.org were cited in
> the most recent publication of our group. The paper is called
> "Computational analysis of the evolutionarily conserved Missing In
> Metastasis/Metastasis Suppressor 1 gene predicts novel interactions,
> regulatory regions and transcriptional control" and was published in
> Scientific Reports:
> 
> https://www.nature.com/articles/s41598-019-40697-1
> 
> I would like to express my sincere gratitude to Slackware and the SBo 
> community.
> 
> Almost all bioinformatics software used in the work was installed from
> SBo. Slackware and SBo are credited in Materials and Methods >
> Software and data
> 
> Here's a post in my humble blog, if you want more details:
> https://slackalaxy.com/2019/03/15/slackware-and-slackbuilds-org-cited-in-a-scientific-publication/
> 
> ...and of course you are very welcome to read the paper!
> 
> all the best,
> 
> Petar
> _______________________________________________
> 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/

Helping to cure cancer? Yes, I'm happy to have had ANY part in that.

I can't pretend to have understood what I've read, but it's very 
impressive and quite an honour to be involved with SBo.

Nice work, Petar (et al)!

From willysr at slackbuilds.org  Sat Mar 16 00:19:24 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 16 Mar 2019 07:19:24 +0700
Subject: [Slackbuilds-users] Updates - 20190316.1
Message-ID: <a2df53f9-78ae-4279-299b-40e82f98a576@slackbuilds.org>

Hello,

This is a rather long list of changes (222 commits), accumulating from
two weeks of work from maintainers across the globe. Big thanks to
everyone who had contributed to SBo and i apologized for missing last
week public update.

Anyway, in this week's update, we identified some broken script with
Python 3.7 and we managed to fix those. There might be more, so we need
your help on finding those who needed a patch or an update to the latest
version.

We have a new major version of wireshark which removes the GTK-based UI,
some security updates (flashplayer, pepperflash, nodejs, nodejs6), and
many interesting updates such as LibreOffice 6.2.1, R, Octave, Audacity,
postgis, wine-staging, jenkins, and of course the fixes for VirtualBox.

Also, we would like to give a big thanks for Petar Petrov for citing SBo
project in his publication paper. We are looking forward for more
academic-related scripts in SBo soon :)


Have a nice weekend everyone


Sat Mar 16 00:00:00 UTC 2019
academic/R: Updated for version 3.5.2 + new maintainer.
academic/SU2: Added (Open Source CFD Code).
academic/gwyddion: Updated for version 2.53.
academic/octave: Updated for version 5.1.0.
academic/scidavis: Updated for version 1.25.
audio/audacity: Updated for version 2.3.1, changed homepage.
audio/mixxx: Updated for version 2.1.7.
audio/muse: Updated for version 4.0.7.
audio/qmmp-qt5: Updated for version 1.3.1.
audio/snd: Updated for version 19.1.
desktop/dwm: Add optional system tray patch
desktop/gnome-menus: Updated for version 3.31.92.
desktop/herbstluftwm: Updated for version 0.7.1.
desktop/lxpanel: Updated for version 0.10.0.
desktop/nitrogen: Updated for version 1.6.1 + new maintainer.
development/ChezScheme: Updated for version 9.5.1_674e218.
development/acc: Added (ZDoom ACS compiler).
development/d-tools: Updated for version 2.085.0
development/dart: Updated for version 2.2.0.
development/dmd: Updated for version 2.085.0
development/dpkg: Updated for version 1.19.5.
development/git-lfs: Remove install.sh after building.
development/git-lfs: Updated for version 2.7.1.
development/hub: Updated for version 2.10.0.
development/jupyter-notebook: Updated for version 5.7.6.
development/lcov: Updated for version 1.14.
development/nexus: Updated for version 3.15.2_01.
development/nodejs: Fix some file paths.
development/nodejs: Updated for version 8.15.1.
development/postman: Updated for version 6.7.4.
development/rtags: Updated for version 2.22.
development/samurai: Updated for version 0.6.
development/sbcl: Updated for version 1.5.0.
development/tanya: Updated for version 0.16.0
development/tiled: Updated for version 1.2.3.
development/universal-ctags: Updated for version 6cecfb9
development/yarn: Updated for version 1.15.2.
games/instead: Updated for version 3.3.0.
games/mednafen: Updated for version 1.22.1.
games/planetblupi: Updated for version 1.14.1.
gis/basemap: Updated for version 1.2.0 + new maintainer.
gis/gpxsee: Updated for version 7.4.
gis/ossim: Updated for version 2.7.0.
gis/postgis: Updated for version 2.5.2.
gis/pyproj: Fix build for Python 3.7.
gis/python3-basemap: Added (matplotlib library).
gis/pytrainer: Updated for version 1.12.2.
gis/rasterio: Fix md5sum.
graphics/feh: Updated for version 3.1.3.
graphics/scantailor-advanced: Added (post-processing tool).
graphics/trimage: Updated for version 1.0.6.
graphics/white_dune: Updated for version 0.99pl1432.
graphics/wine-nine-standalone: Update README.
graphics/xdot: Updated for version 1.0.
ham/tqsl: Updated for version 2.4.3.
ham/wsjtx: Updated for version 2.0.1
libraries/PyYAML: Updated for version 3.13.
libraries/SOPE: Updated for version 4.0.7.
libraries/dav1d: Updated for version 0.2.0.
libraries/futures: Removed python3 support.
libraries/greenlet: Updated for version 0.4.15.
libraries/http-parser: Updated for version 2.9.0
libraries/libaaio: Update maintainer info.
libraries/libbde: Updated for version 20190102.
libraries/libcoap: Updated for version 4.2.0.
libraries/libesedb: Updated for version 20181229.
libraries/libevt: Updated for version 20181227.
libraries/libevtx: Updated for version 20181227.
libraries/libewf: Updated for version 20140806.
libraries/libfvde: Updated for version 20190104.
libraries/libfwnt: Updated for version 20181227.
libraries/libfwsi: Updated for version 20181227.
libraries/libgit2: Updated for version 0.28.1
libraries/liblnk: Updated for version 20181227.
libraries/libmirage: Updated for version 3.2.1.
libraries/libnfs: Updated for version 4.0.0
libraries/libolecf: Updated for version 20181231.
libraries/libpgf: Updated for version 7.19.3.
libraries/libregf: Updated for version 20181231.
libraries/libscca: Updated for version 20181227.
libraries/libsigscan: Updated for version 20190103.
libraries/libtermkey: Updated for version 0.22.
libraries/libtorrent-rasterbar: Add support for examples & tools
libraries/libvhdi: Updated for version 20181227.
libraries/libvmdk: Updated for version 20181227.
libraries/libvshadow: Updated for version 20190127.
libraries/libxkbcommon: Updated for version 0.8.4.
libraries/libxlsxwriter: Update to 0.8.5
libraries/libxmlb: Updated for version 0.1.7.
libraries/libxnvctrl: Updated for version 418.43.
libraries/live555: Updated for version 2019.03.06
libraries/nv-codec-headers: Updated for version 9.0.18.1.
libraries/pylast: Updated for version 2.4.0.
libraries/pymediainfo: Updated for version 3.1.
libraries/python3-PyYAML: Updated for version 3.13.
libraries/qt5-pbfimageplugin: Updated for version 1.3.
libraries/vcglib: Added (Visualization+Computer Graphics Library).
libraries/wxSQLite3: Updated for version 4.4.2.
misc/mosquitto: Updated for version 1.5.8
multimedia/AtomicParsley: Update to 0.9.6
multimedia/dirac: Update DOWNLOAD.
multimedia/flashplayer-plugin: Updated for version 32.0.0.156.
multimedia/obs-studio: Updated for version 23.0.2
multimedia/pepperflash-plugin: Updated for version 32.0.0.156.
multimedia/plexmediaserver: Updated for version 1.15.1.
multimedia/strawberry: Added (fork of Clementine).
multimedia/vivaldi-codecs-ffmpeg-extra: Updated for v 72.0.3626.121.
multimedia/vlc: Restored support for OpenCV
multimedia/xawtv: Updated for version 3.106.
network/amavisd-new: Added DKIM patch.
network/asterisk: Updated for version 16.2.1.
network/brave-browser: Updated for version 0.60.47.
network/clipgrab: Updated for version 3.8.2.
network/filezilla: Updated for version 3.41.1.
network/onionshare: update to version 2.0
network/opera-developer: Updated for version 60.0.3248.0.
network/opera: Updated for version 58.0.3135.90.
network/prosody-mod-smacks: Updated for version hg3479.
network/speedtest-cli: Updated for version 2.1.0.
network/ssllabs-scan: Updated for version 1.5.0.
network/strongswan: Updated for version 5.7.2.
network/vivaldi: Updated for version 2.3.1440.61.
network/waterfox: Updated for version 56.2.8.
network/wildfly: Updated for version 16.0.0.
network/wireshark: Updated for version 3.0.0.
network/you-get: Updated for version 0.4.1270.
office/LibreOffice: Updated for version 6.2.1.2
office/MasterPDFEditor: Updated for version 5.3.20.
office/SOGo: Updated for version 4.0.7.
office/libreoffice-helppack: Updated for version 6.2.1
office/libreoffice-langpack: Updated for version 6.2.1
office/libreoffice: Updated for version 6.2.1
office/notmuch: Updated for version 0.28.2.
office/sigil: Updated for version 0.9.12
office/taskopen: Updated for version 1.1.4.
perl/MoarVM: Updated for version 2019.03.
perl/nqp: Updated for version 2019.13.
perl/perl-Date-Manip: Updated for version 6.76.
perl/perl-IO-Socket-SSL: Updated for version 2.066.
perl/perl-Sub-Quote: Updated for version 2.006003.
perl/perl-strictures: Updated for version 2.000006.
perl/perl6-Readline: Updated for version 0.1.5.
perl/rakudo: Updated for version 2019.03.
perl/zef: Updated for version 0.7.1.
python/XlsxWriter: Updated for version 1.1.2.
python/arrow: Updated for version 0.13.1.
python/artifacts: Updated for version 20190113.
python/async-timeout: Added (asyncio-compatible timeout class).
python/dfdatetime: Updated for version 20190116.
python/dfvfs: Updated for version 20190128.
python/dfwinreg: Updated for version 20190122.
python/dtfabric: Updated for version 20190120.
python/gunicorn: Updated for version 19.9.0.
python/obspy: Updated for version 1.1.1.
python/plaso: Updated for version 20190131.
python/pluggy: Updated for version 0.9.0.
python/purl: Updated for version 1.5.
python/pycodestyle: Downgraded to version 2.3.1.
python/python-certifi: Updated for version 2019.3.9.
python/python-progress: Updated for version 1.5.
python/python-scandir: Updated for version 1.10.0.
python/python3-Cython: Updated for version 0.29.6.
python/python3-aiorpcX: Added (Generic async RPC implementation).
python/python3-astroid: Updated for version 2.2.4.
python/python3-isort: Updated for version 4.3.10.
python/python3-multidict: Added (Asyncio-based multidict).
python/python3-obspy: Added (A Python Framework for Seismology).
python/python3-pyzmq: Updated for version 18.0.1
python/pytsk: Updated for version 20190121.
python/pyusb: Add optional python3 support.
python/pyzmq: Updated for version 18.0.1.
python/regex: Updated for version 2019.03.09.
python/scikit-learn: Updated for version 0.20.3.
python/sqlalchemy-migrate: Updated for version 0.12.0.
python/suds-jurko: Add python3 support.
python/tempita: Add optional python3 support.
python/yarl: Added (Yet another URL library).
ruby/ruby-build: Updated for version 20190314.
ruby/sequel: Updated for version 5.18.0.
ruby/sqlite3: Updated for version 1.4.0.
system/ansible: Updated for version 2.7.9.
system/bit-babbler: Update script.
system/cdemu-client: Updated for version 3.2.1.
system/cdemu-daemon: Updated for version 3.2.2.
system/cnijfilter2: Added (Canon IJ Printer Driver).
system/dar: Updated for version 2.6.2.
system/ddrescue-gui: Updated for version 2.0.2.
system/dieharder: Update maintainer info.
system/dosbox-dev: Updated for version 0.74.r4194.
system/dosbox-x: Added (Accurate emulation and retro-development).
system/gcdemu: Updated for version 3.2.1.
system/isdct: Updated for version 3.0.18.
system/jenkins: Updated for version 2.167.
system/kbfs: Updated for version 3.1.2_20190312133549.
system/kitchen-sync: Updated for version 1.12.
system/letsencrypt: Updated for version 0.32.0.
system/lxrandr: Updated for version 0.3.2.
system/lxsession: Updated for version 0.5.4.
system/lxtask: Updated for version 0.1.9.
system/lynis: Updated for version 2.7.2.
system/netdata: Updated for version 1.13.0.
system/openrc-services: Updated for version 20190302.
system/pixma: Added (Canon PIXMA printer driver).
system/plymouth: Added (graphical boot animation and logger).
system/pycp: Updated for version 8.0.7.
system/ranger: Fix man page and add examples
system/sandbox: Updated for version 2.16.
system/spl-solaris: Updated for version 0.7.13.
system/telegraf: Updated for version 1.10.0.
system/unar: Updated for version 1.10.3.
system/vhba-module: Updated for version 20190302.
system/virtualbox-kernel-addons: Fix kernel version check on 32bit
system/virtualbox-kernel: Fix kernel version check on 32bit systems
system/wine-staging: Updated for version 4.3.
system/zfs-on-linux: Updated for version 0.7.13.
+--------------------------+


-- 
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/20190316/679c6353/attachment.asc>

From fellype at gmail.com  Sat Mar 16 04:42:31 2019
From: fellype at gmail.com (Fellype)
Date: Sat, 16 Mar 2019 01:42:31 -0300
Subject: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a
 scientific publication
In-Reply-To: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
Message-ID: <CAJJ5XvFhcLid994b2mAkXrugVi1WFobzf5=pZSG2qJfOBnJV6g@mail.gmail.com>

Hi Petar!

A work using open source software published in an open access journal: very
good!
Congratulations and best regards.

Fellype

Em sex, 15 de mar de 2019 ?s 12:44, Petar Petrov <slackalaxy at gmail.com>
escreveu:

> Dear All,
>
> I am happy to let you know Slackware and SlackBuilds.org were cited in
> the most recent publication of our group. The paper is called
> "Computational analysis of the evolutionarily conserved Missing In
> Metastasis/Metastasis Suppressor 1 gene predicts novel interactions,
> regulatory regions and transcriptional control" and was published in
> Scientific Reports:
>
> https://www.nature.com/articles/s41598-019-40697-1
>
> I would like to express my sincere gratitude to Slackware and the SBo
> community.
>
> Almost all bioinformatics software used in the work was installed from
> SBo. Slackware and SBo are credited in Materials and Methods >
> Software and data
>
> Here's a post in my humble blog, if you want more details:
>
> https://slackalaxy.com/2019/03/15/slackware-and-slackbuilds-org-cited-in-a-scientific-publication/
>
> ...and of course you are very welcome to read the paper!
>
> all the best,
>
> Petar
> _______________________________________________
> 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/
>
>

-- 
Fellype
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190316/74afa8be/attachment-0001.html>

From alik at ejik.org  Sat Mar 16 10:50:28 2019
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 16 Mar 2019 06:50:28 -0400
Subject: [Slackbuilds-users] 
 =?utf-8?q?Slackware_and_SlackBuilds=2Eorg_ci?=
 =?utf-8?q?ted_in_a_scientific_publication?=
In-Reply-To: <CAJJ5XvFhcLid994b2mAkXrugVi1WFobzf5=pZSG2qJfOBnJV6g@mail.gmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
 <CAJJ5XvFhcLid994b2mAkXrugVi1WFobzf5=pZSG2qJfOBnJV6g@mail.gmail.com>
Message-ID: <755ef696-a21f-4379-a201-2ca85740ccce@www.fastmail.com>

Hello,

> A work using open source software published in an open access journal:
> very good!

I'm also very happy to see SBo cited in a scientific publication in an
important journal, thank you Petar!

As for "open access journal", in such journals the authors pay for
publications, for example, $1790 for a paper in this journal
https://www.nature.com/srep/about/article-processing-charges
One among many bad consequences of such approach is that authors from
poor University (e.g., from a poor country) must have a coauthor from a
rich University.

Best regards,
Alexander

From rshepard at appl-ecosys.com  Sat Mar 16 14:08:29 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 16 Mar 2019 07:08:29 -0700 (PDT)
Subject: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a
 scientific publication
In-Reply-To: <755ef696-a21f-4379-a201-2ca85740ccce@www.fastmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
 <CAJJ5XvFhcLid994b2mAkXrugVi1WFobzf5=pZSG2qJfOBnJV6g@mail.gmail.com>
 <755ef696-a21f-4379-a201-2ca85740ccce@www.fastmail.com>
Message-ID: <alpine.LNX.2.20.1903160703210.15396@salmo.appl-ecosys.com>

On Sat, 16 Mar 2019, Alexander Verbovetsky wrote:

> As for "open access journal", in such journals the authors pay for
> publications, for example, $1790 for a paper in this journal
> https://www.nature.com/srep/about/article-processing-charges One among
> many bad consequences of such approach is that authors from poor
> University (e.g., from a poor country) must have a coauthor from a rich
> University.

Alexander, et al.:

Slightly off-topic.

This is true for those journals that charged for subscriptions to their dead
tree versions. Others are strictly on-line and have no author charges. In
2016 I published a paper in the Journal of Regulatory Science. While its
focus is on medical/pharmaceutical/agricultural chemical regulation it did
accept my article on environmental regulatory science. These may not be
"prestigious" journals but if the quality of the published article is
sufficiently high it will be noticed.

Rich

From alik at ejik.org  Sat Mar 16 14:29:56 2019
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 16 Mar 2019 10:29:56 -0400
Subject: [Slackbuilds-users] 
 =?utf-8?q?Slackware_and_SlackBuilds=2Eorg_ci?=
 =?utf-8?q?ted_in_a_scientific_publication?=
In-Reply-To: <alpine.LNX.2.20.1903160703210.15396@salmo.appl-ecosys.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
 <CAJJ5XvFhcLid994b2mAkXrugVi1WFobzf5=pZSG2qJfOBnJV6g@mail.gmail.com>
 <755ef696-a21f-4379-a201-2ca85740ccce@www.fastmail.com>
 <alpine.LNX.2.20.1903160703210.15396@salmo.appl-ecosys.com>
Message-ID: <80b99275-68be-41f0-8ce6-31a9237ef34f@www.fastmail.com>

> This is true for those journals that charged for subscriptions to
> their dead tree versions. Others are strictly on-line and have no
> author charges.

The journal "Scientific Reports" we are discussing is pure online. "Open
access" means: "no payment, no publication".

Best regards,
Alexander

From kingbeowulf at gmail.com  Sat Mar 16 18:52:48 2019
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 16 Mar 2019 11:52:48 -0700
Subject: [Slackbuilds-users] OT: open access publication (WAS: Re: Slackware
 and SlackBuilds.org cited in a scientific publication)
In-Reply-To: <80b99275-68be-41f0-8ce6-31a9237ef34f@www.fastmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
 <CAJJ5XvFhcLid994b2mAkXrugVi1WFobzf5=pZSG2qJfOBnJV6g@mail.gmail.com>
 <755ef696-a21f-4379-a201-2ca85740ccce@www.fastmail.com>
 <alpine.LNX.2.20.1903160703210.15396@salmo.appl-ecosys.com>
 <80b99275-68be-41f0-8ce6-31a9237ef34f@www.fastmail.com>
Message-ID: <d52bb60c-7ff6-df84-d00d-d000ec972948@gmail.com>

On 3/16/19 7:29 AM, Alexander Verbovetsky wrote:
>> This is true for those journals that charged for subscriptions to
>> their dead tree versions. Others are strictly on-line and have no
>> author charges.
> 
> The journal "Scientific Reports" we are discussing is pure online. "Open
> access" means: "no payment, no publication".
> 
> Best regards,
> Alexander

"Scientific Reports" (i.e. Nature) publication fee is on par with most
other journals that then often then place the paper behind a paywall. At
least anyone can read/access an open access paper.  Those journal
publishers who charge authors a small or no fee, will charge sometimes
large fees to libraries and individual article downloads. In the pre-web
era, we added publication fees to the grant application.  We would get
10-20 reprints, if we wanted more we had to buy them. Even when
publishers waived submissions fees, there were color charges, page
charges, charges for supplemental materials, etc. The open access trend
is far superior to the old model.

Also, had you bothered to look more closely at "Scientific Reports" you
would have seen the publication fee waiver program as well as a large
list of granting agencies that will help pay to have research published
as open access.

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

From kingbeowulf at gmail.com  Sat Mar 16 18:54:43 2019
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 16 Mar 2019 11:54:43 -0700
Subject: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a
 scientific publication
In-Reply-To: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
References: <CAKXpWBfMtQ5v2jeXH0TBz-1PG6gFbmHiqjRRcHjo=UnCXbLQ+A@mail.gmail.com>
Message-ID: <8407073b-c893-8574-e4bf-1d8480022b1c@gmail.com>

On 3/15/19 8:44 AM, Petar Petrov wrote:
> Dear All,
> 
> I am happy to let you know Slackware and SlackBuilds.org were cited in
> the most recent publication of our group. The paper is called
> "Computational analysis of the evolutionarily conserved Missing In
> Metastasis/Metastasis Suppressor 1 gene predicts novel interactions,
> regulatory regions and transcriptional control" and was published in
> Scientific Reports:
> 
> https://www.nature.com/articles/s41598-019-40697-1
> 
> I would like to express my sincere gratitude to Slackware and the SBo community.
> 
> Almost all bioinformatics software used in the work was installed from
> SBo. Slackware and SBo are credited in Materials and Methods >
> Software and data
> 
> Here's a post in my humble blog, if you want more details:
> https://slackalaxy.com/2019/03/15/slackware-and-slackbuilds-org-cited-in-a-scientific-publication/
> 
> ...and of course you are very welcome to read the paper!
> 
> all the best,
> 
> Petar

Well done! Not my field but I have it on my reading list.

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

From chris.willing at linux.com  Sun Mar 17 04:36:47 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Sun, 17 Mar 2019 14:36:47 +1000
Subject: [Slackbuilds-users] Updates - 20190316.1
In-Reply-To: <a2df53f9-78ae-4279-299b-40e82f98a576@slackbuilds.org>
References: <a2df53f9-78ae-4279-299b-40e82f98a576@slackbuilds.org>
Message-ID: <adf26f6d-4415-4bb9-0040-39a2bc59683b@linux.com>

On 16/3/19 10:19 am, Willy Sudiarto Raharjo wrote:

> libraries/libpgf: Updated for version 7.19.3.
Since this update to libpgf, is anyone else seeing the following error
when building digikam?

/var/tmp/SBo/digikam-4.14.0/core/libs/dimg/loaders/pgfloader.cpp: In
member function 'virtual bool Digikam::PGFLoader::save(const QString&,
Digikam::DImgLoaderObserver*)':
/var/tmp/SBo/digikam-4.14.0/core/libs/dimg/loaders/pgfloader.cpp:447:16:
error: 'struct PGFHeader' has no member named 'background'
         header.background.rgbtBlue  = 0;

(similar additional errors for header.background.rgbtGreen &
header.background.rgbtRed)

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/20190317/a44fb945/attachment-0001.asc>

From yth at ythogtha.org  Sun Mar 17 09:01:06 2019
From: yth at ythogtha.org (Arnaud)
Date: Sun, 17 Mar 2019 10:01:06 +0100
Subject: [Slackbuilds-users] Updates - 20190316.1
In-Reply-To: <a2df53f9-78ae-4279-299b-40e82f98a576@slackbuilds.org>
References: <a2df53f9-78ae-4279-299b-40e82f98a576@slackbuilds.org>
Message-ID: <20190317100106.ad0d0e2eee5585beeccde267@ythogtha.org>

> Hello,
> 
> This is a rather long list of changes (222 commits), accumulating from
> two weeks of work from maintainers across the globe. Big thanks to
> everyone who had contributed to SBo and i apologized for missing last
> week public update.

Great work:)

> office/LibreOffice: Updated for version 6.2.1.2

Well, I'm still trying to get what I'm doing wrong with that one, but for now
I'm pretty sure there's an error :
 * mysql-connector-c++ is listed as optional dependency in the .info, if it is
present the build will use it, else it'll use internal version.
 * Inside the .SlackBuild file it'll set the --with-system-mysql-cppconn
compilation option.
 * But when cofiguration goes it complains, and fails, saying that :
configure: error: unrecognized options: --with-system-mysql-cppconn

I don't see any reference to it in ./configure --help, so I'm guessing it can
simply be removed, Libreoffice doesn't seem to use it anymore.


Cheers!

-- 
Arnaud <yth at ythogtha.org>

From willysr at slackbuilds.org  Sun Mar 17 10:42:57 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 17 Mar 2019 17:42:57 +0700
Subject: [Slackbuilds-users] Updates - 20190316.1
In-Reply-To: <adf26f6d-4415-4bb9-0040-39a2bc59683b@linux.com>
References: <a2df53f9-78ae-4279-299b-40e82f98a576@slackbuilds.org>
 <adf26f6d-4415-4bb9-0040-39a2bc59683b@linux.com>
Message-ID: <b4de34d6-24dc-ad3e-84a1-ed50b4108251@slackbuilds.org>

> Since this update to libpgf, is anyone else seeing the following error
> when building digikam?
> 
> /var/tmp/SBo/digikam-4.14.0/core/libs/dimg/loaders/pgfloader.cpp: In
> member function 'virtual bool Digikam::PGFLoader::save(const QString&,
> Digikam::DImgLoaderObserver*)':
> /var/tmp/SBo/digikam-4.14.0/core/libs/dimg/loaders/pgfloader.cpp:447:16:
> error: 'struct PGFHeader' has no member named 'background'
>          header.background.rgbtBlue  = 0;
> 
> (similar additional errors for header.background.rgbtGreen &
> header.background.rgbtRed)

Thanks for spotting that Chris

i have pushed a patch for that 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/20190317/4b4172e1/attachment.asc>

From willysr at slackbuilds.org  Sun Mar 17 10:45:39 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 17 Mar 2019 17:45:39 +0700
Subject: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos
In-Reply-To: <md5:jenPDIyiRjcNGZ4tC4y4iQ==>
References: <md5:jenPDIyiRjcNGZ4tC4y4iQ==>
Message-ID: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>

Hi

Anyone want to take over this scripts?


-------- Forwarded Message --------
Subject: New Maintainer Needed for SBos
Date: Sun, 17 Mar 2019 10:03:48 +0000
From: awg <awg at cock.li>
To: willysr at slackbuilds.org

Hi Willy,

I no longer use the following packages:
* development/ChezScheme
* libraries/libaaio
* system/dieharder
* office/keepassx

If someone else could take over maintainership for these packages,
I'd be grateful.

Unlike the other three, ChezScheme is still actively maintained by
its developers.  Whoever takes this over should run the full test
battery on both threaded and unthreaded builds after each update to
check for regressions.

Thank you!

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

From artourter at gmail.com  Sun Mar 17 10:56:40 2019
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Sun, 17 Mar 2019 10:56:40 +0000
Subject: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos
In-Reply-To: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
References: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
Message-ID: <CAK09-vnB8Hr8QUe=3QYMfp2jyY+D1kH6v0D8xTUXHUFEjc6vDA@mail.gmail.com>

Hi,

I can take over keepassx if no-one else wants it as I use it a lot.

Cheers

Greg

On Sun, 17 Mar 2019 at 10:45, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> Hi
>
> Anyone want to take over this scripts?
>
>
> -------- Forwarded Message --------
> Subject: New Maintainer Needed for SBos
> Date: Sun, 17 Mar 2019 10:03:48 +0000
> From: awg <awg at cock.li>
> To: willysr at slackbuilds.org
>
> Hi Willy,
>
> I no longer use the following packages:
> * development/ChezScheme
> * libraries/libaaio
> * system/dieharder
> * office/keepassx
>
> If someone else could take over maintainership for these packages,
> I'd be grateful.
>
> Unlike the other three, ChezScheme is still actively maintained by
> its developers.  Whoever takes this over should run the full test
> battery on both threaded and unthreaded builds after each update to
> check for regressions.
>
> Thank you!
>
> --
> 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/20190317/c65cee4c/attachment.html>

From chris.willing at linux.com  Sun Mar 17 13:21:23 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Sun, 17 Mar 2019 23:21:23 +1000
Subject: [Slackbuilds-users] Updates - 20190316.1
In-Reply-To: <20190317100106.ad0d0e2eee5585beeccde267@ythogtha.org>
References: <a2df53f9-78ae-4279-299b-40e82f98a576@slackbuilds.org>
 <20190317100106.ad0d0e2eee5585beeccde267@ythogtha.org>
Message-ID: <31a478aa-565c-ffff-bd15-d0489a650580@linux.com>

On 17/3/19 7:01 pm, Arnaud wrote:
>> Hello,
>>
>> This is a rather long list of changes (222 commits), accumulating from
>> two weeks of work from maintainers across the globe. Big thanks to
>> everyone who had contributed to SBo and i apologized for missing last
>> week public update.
> 
> Great work:)
> 
>> office/LibreOffice: Updated for version 6.2.1.2
> 
> Well, I'm still trying to get what I'm doing wrong with that one, but for now
> I'm pretty sure there's an error :
>  * mysql-connector-c++ is listed as optional dependency in the .info, if it is
> present the build will use it, else it'll use internal version.
>  * Inside the .SlackBuild file it'll set the --with-system-mysql-cppconn
> compilation option.
>  * But when cofiguration goes it complains, and fails, saying that :
> configure: error: unrecognized options: --with-system-mysql-cppconn
> 
> I don't see any reference to it in ./configure --help, so I'm guessing it can
> simply be removed, Libreoffice doesn't seem to use it anymore.
> 

Thanks for reporting. Looks like that option has been dropped in the
6.2.x releases.

chris

From sebastien.neuville at riseup.net  Sun Mar 17 23:15:57 2019
From: sebastien.neuville at riseup.net (sebastien.neuville at riseup.net)
Date: Sun, 17 Mar 2019 16:15:57 -0700
Subject: [Slackbuilds-users] cups-bjnp
Message-ID: <3322aa7bf4b0b5c32936048b32de5ec1@riseup.net>

Hi,

I'm a user of cups-bjnp, which allows me to print and scan with my Canon
mp620.

The slackbuilds version is still 1.2, while a version 2 exists, which
adds ink-level reporting.

I managed to modify the slackbuild easily (juste the version number to
replace) ; would-it be possible to modify this build ?

Thanks
S?b

From phalange at komputermatrix.com  Mon Mar 18 17:26:18 2019
From: phalange at komputermatrix.com (Andrew Payne)
Date: Mon, 18 Mar 2019 13:26:18 -0400
Subject: [Slackbuilds-users] Pandoc binary alternative
Message-ID: <90b198854a97c1bdf7a86849f90c5066.squirrel@email.fatcow.com>

Hi all, I made a slackbuild for the binary of pandoc.  The
build-from-source version exists on SBo, but given the daunting build time
and the massive list of Haskell dependencies, I think a binary build would
be a valuable alternative.  I know this parallel scenario exists with
LibreOffice for example.

Is the team open to me maintaining the pandoc binary slackbuild?

Best,
Andrew
phalange on LQ and IRC





From rshepard at appl-ecosys.com  Mon Mar 18 17:31:33 2019
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Mon, 18 Mar 2019 10:31:33 -0700 (PDT)
Subject: [Slackbuilds-users] Pandoc binary alternative
In-Reply-To: <90b198854a97c1bdf7a86849f90c5066.squirrel@email.fatcow.com>
References: <90b198854a97c1bdf7a86849f90c5066.squirrel@email.fatcow.com>
Message-ID: <alpine.LNX.2.20.1903181028500.26939@salmo.appl-ecosys.com>

On Mon, 18 Mar 2019, Andrew Payne wrote:

> Hi all, I made a slackbuild for the binary of pandoc. The
> build-from-source version exists on SBo, but given the daunting build time
> and the massive list of Haskell dependencies, I think a binary build would
> be a valuable alternative. I know this parallel scenario exists with
> LibreOffice for example.

Andrew,

While I cannot speak for the SBo team, I would greatly appreciate using
your pandoc binary (as I use the LO binary). I started installing it last
year but gave up after installin a bunch of Haskell packages. I have no need
for that language other than pandoc so I removed them all and decided I'd
live without pandoc.

Regards,

Rich

From rworkman at slackbuilds.org  Mon Mar 18 18:29:40 2019
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 18 Mar 2019 13:29:40 -0500
Subject: [Slackbuilds-users] Pandoc binary alternative
In-Reply-To: <90b198854a97c1bdf7a86849f90c5066.squirrel@email.fatcow.com>
References: <90b198854a97c1bdf7a86849f90c5066.squirrel@email.fatcow.com>
Message-ID: <20190318132940.7cf8feda@home.rlworkman.net>

On Mon, 18 Mar 2019 13:26:18 -0400
"Andrew Payne" <phalange at komputermatrix.com> wrote:

> Hi all, I made a slackbuild for the binary of pandoc.  The
> build-from-source version exists on SBo, but given the daunting build
> time and the massive list of Haskell dependencies, I think a binary
> build would be a valuable alternative.  I know this parallel scenario
> exists with LibreOffice for example.
> 
> Is the team open to me maintaining the pandoc binary slackbuild?


Absolutely yes, assuming it's something along the lines of "a binary
from official sources exists and this repackages it." If you're talking
about building a package and then distributing it using SBo, then
I'm not comfortable with that at all. It's not about you personally, but
rather that it's exactly what led to the creation of this project and
I don't want to lead users back down that road.

-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/20190318/5140bc3e/attachment.asc>

From klaatu at mixedsignals.ml  Mon Mar 18 18:37:32 2019
From: klaatu at mixedsignals.ml (klaatu at mixedsignals.ml)
Date: Mon, 18 Mar 2019 13:37:32 -0500
Subject: [Slackbuilds-users] Pandoc binary alternative
In-Reply-To: <alpine.LNX.2.20.1903181028500.26939@salmo.appl-ecosys.com>
References: <90b198854a97c1bdf7a86849f90c5066.squirrel@email.fatcow.com>
 <alpine.LNX.2.20.1903181028500.26939@salmo.appl-ecosys.com>
Message-ID: <927b9bf7c8fac3341d71b50461c19e60@mixedsignals.ml>

Rich, I used to steal a binary (pandoc-static) from Fedora repos and it 
worked nicely.

It seems pandoc releases a binary these days themselves, though (which 
hopefully is what Andrew has packaged).

Nobody should ever have to live without pandoc :-)



On 2019-03-18 12:31, Rich Shepard wrote:
> On Mon, 18 Mar 2019, Andrew Payne wrote:
> 
>> Hi all, I made a slackbuild for the binary of pandoc. The
>> build-from-source version exists on SBo, but given the daunting build 
>> time
>> and the massive list of Haskell dependencies, I think a binary build 
>> would
>> be a valuable alternative. I know this parallel scenario exists with
>> LibreOffice for example.
> 
> Andrew,
> 
> While I cannot speak for the SBo team, I would greatly appreciate using
> your pandoc binary (as I use the LO binary). I started installing it 
> last
> year but gave up after installin a bunch of Haskell packages. I have no 
> need
> for that language other than pandoc so I removed them all and decided 
> I'd
> live without pandoc.
> 
> Regards,
> 
> 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/

From phalange at komputermatrix.com  Mon Mar 18 18:40:42 2019
From: phalange at komputermatrix.com (Andrew Payne)
Date: Mon, 18 Mar 2019 14:40:42 -0400
Subject: [Slackbuilds-users] Pandoc binary alternative
In-Reply-To: <20190318132940.7cf8feda@home.rlworkman.net>
References: <90b198854a97c1bdf7a86849f90c5066.squirrel@email.fatcow.com>
 <20190318132940.7cf8feda@home.rlworkman.net>
Message-ID: <439a02fbcdf288e23250308fae958087.squirrel@email.fatcow.com>

That's right, binary straight from official Pandoc project, repackaged for
Slackware.

(Sorry for the duplicate Robby, I didn't reply-all)

> On Mon, 18 Mar 2019 13:26:18 -0400
> "Andrew Payne" <phalange at komputermatrix.com> wrote:
>
>> Hi all, I made a slackbuild for the binary of pandoc.  The
>> build-from-source version exists on SBo, but given the daunting build
>> time and the massive list of Haskell dependencies, I think a binary
>> build would be a valuable alternative.  I know this parallel scenario
>> exists with LibreOffice for example.
>>
>> Is the team open to me maintaining the pandoc binary slackbuild?
>
>
> Absolutely yes, assuming it's something along the lines of "a binary
> from official sources exists and this repackages it." If you're talking
> about building a package and then distributing it using SBo, then
> I'm not comfortable with that at all. It's not about you personally, but
> rather that it's exactly what led to the creation of this project and
> I don't want to lead users back down that road.
>
> -RW
>



From rworkman at slackbuilds.org  Mon Mar 18 18:43:05 2019
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 18 Mar 2019 13:43:05 -0500
Subject: [Slackbuilds-users] Pandoc binary alternative
In-Reply-To: <439a02fbcdf288e23250308fae958087.squirrel@email.fatcow.com>
References: <90b198854a97c1bdf7a86849f90c5066.squirrel@email.fatcow.com>
 <20190318132940.7cf8feda@home.rlworkman.net>
 <439a02fbcdf288e23250308fae958087.squirrel@email.fatcow.com>
Message-ID: <20190318134305.0649772f@home.rlworkman.net>

Okay, then yes, absolutely. Go for it.

-RW

On Mon, 18 Mar 2019 14:40:42 -0400
"Andrew Payne" <phalange at komputermatrix.com> wrote:

> That's right, binary straight from official Pandoc project,
> repackaged for Slackware.
> 
> (Sorry for the duplicate Robby, I didn't reply-all)
> 
> > On Mon, 18 Mar 2019 13:26:18 -0400
> > "Andrew Payne" <phalange at komputermatrix.com> wrote:
> >  
> >> Hi all, I made a slackbuild for the binary of pandoc.  The
> >> build-from-source version exists on SBo, but given the daunting
> >> build time and the massive list of Haskell dependencies, I think a
> >> binary build would be a valuable alternative.  I know this
> >> parallel scenario exists with LibreOffice for example.
> >>
> >> Is the team open to me maintaining the pandoc binary slackbuild?  
> >
> >
> > Absolutely yes, assuming it's something along the lines of "a binary
> > from official sources exists and this repackages it." If you're
> > talking about building a package and then distributing it using
> > SBo, then I'm not comfortable with that at all. It's not about you
> > personally, but rather that it's exactly what led to the creation
> > of this project and I don't want to lead users back down that road.
> >
> > -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/20190318/41732787/attachment.asc>

From ewfalor at gmail.com  Tue Mar 19 03:27:20 2019
From: ewfalor at gmail.com (Erik Falor)
Date: Mon, 18 Mar 2019 21:27:20 -0600
Subject: [Slackbuilds-users] Upcoming version of EFL build fails on 14.2
Message-ID: <20190319032720.6w52ueeypfar7rpb@viking2.falor>

I've been meaning to push out an update to libraries/efl
(Enlightenment Foundation Libraries, a.k.a. EFL) for some time, but
I've been hung up on an odd build issue on 14.2.

If the previous version of this package is already installed on 14.2
(efl-1.20.7), the build fails because a tool built as part
of the process called `lt-edje_cc` loads a .so installed by efl-1.20.7
into /usr/lib64 and crashes because

    undefined symbol: EINA_ERROR_FUTURE_CANCEL

The thing that puzzles me is that `ldd` reports that `lt-edje_cc`
correctly locates many other EFL shared objects under /tmp/SBo instead
of the system library path /usr/lib64.

The build succeeds on 14.2 if you first manually uninstall EFL.

Curiously, this error does not occur in -current.  I originally
thought that the issue may have been due to a difference as regards
libtool, but both -14.2 and -current use the same version of libtool
"(GNU libtool) 2.4.6"

After many weeks of not making any headway, I'm ready to release this
now with the caveat "you must uninstall your existing EFL package
before updating", and hold faith that 15.0 will make the bugs go away.

My question to the group is, is this an acceptable course of action?

If somebody more knowledgable than I would like to take a stab at it,
you can find the new SlackBuilds here:

https://bitbucket.org/erikfalor/enlightenment-slackbuilds/src

-- 
Erik Falor
Registered Linux User #445632                    http://unnovative.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190318/40b9665b/attachment-0001.asc>

From willysr at slackbuilds.org  Tue Mar 19 04:32:01 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 19 Mar 2019 11:32:01 +0700
Subject: [Slackbuilds-users] Upcoming version of EFL build fails on 14.2
In-Reply-To: <20190319032720.6w52ueeypfar7rpb@viking2.falor>
References: <20190319032720.6w52ueeypfar7rpb@viking2.falor>
Message-ID: <ecf8ce55-d952-39aa-777d-b88abb0f9d89@slackbuilds.org>

> I've been meaning to push out an update to libraries/efl
> (Enlightenment Foundation Libraries, a.k.a. EFL) for some time, but
> I've been hung up on an odd build issue on 14.2.
> 
> If the previous version of this package is already installed on 14.2
> (efl-1.20.7), the build fails because a tool built as part
> of the process called `lt-edje_cc` loads a .so installed by efl-1.20.7
> into /usr/lib64 and crashes because
> 
>     undefined symbol: EINA_ERROR_FUTURE_CANCEL
> 
> The thing that puzzles me is that `ldd` reports that `lt-edje_cc`
> correctly locates many other EFL shared objects under /tmp/SBo instead
> of the system library path /usr/lib64.
> 
> The build succeeds on 14.2 if you first manually uninstall EFL.
> 
> Curiously, this error does not occur in -current.  I originally
> thought that the issue may have been due to a difference as regards
> libtool, but both -14.2 and -current use the same version of libtool
> "(GNU libtool) 2.4.6"
> 
> After many weeks of not making any headway, I'm ready to release this
> now with the caveat "you must uninstall your existing EFL package
> before updating", and hold faith that 15.0 will make the bugs go away.
> 
> My question to the group is, is this an acceptable course of action?
> 
> If somebody more knowledgable than I would like to take a stab at it,
> you can find the new SlackBuilds here:
> 
> https://bitbucket.org/erikfalor/enlightenment-slackbuilds/src

Yes, we do have some scripts with same warning in the README


-- 
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/20190319/46c62081/attachment.asc>

From dickson.tim at googlemail.com  Tue Mar 19 09:38:07 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Tue, 19 Mar 2019 09:38:07 +0000
Subject: [Slackbuilds-users] Upcoming version of EFL build fails on 14.2
In-Reply-To: <ecf8ce55-d952-39aa-777d-b88abb0f9d89@slackbuilds.org>
References: <20190319032720.6w52ueeypfar7rpb@viking2.falor>
 <ecf8ce55-d952-39aa-777d-b88abb0f9d89@slackbuilds.org>
Message-ID: <878a97a7-717a-74f1-25af-0c3a01c45efc@googlemail.com>

On 19/03/2019 04:32, Willy Sudiarto Raharjo wrote:
>> I've been meaning to push out an update to libraries/efl
>> (Enlightenment Foundation Libraries, a.k.a. EFL) for some time, but
>> I've been hung up on an odd build issue on 14.2.
>>
>> If the previous version of this package is already installed on 14.2
>> (efl-1.20.7), the build fails because a tool built as part
>> of the process called `lt-edje_cc` loads a .so installed by efl-1.20.7
>> into /usr/lib64 and crashes because
>>
>>      undefined symbol: EINA_ERROR_FUTURE_CANCEL
>>
>> The thing that puzzles me is that `ldd` reports that `lt-edje_cc`
>> correctly locates many other EFL shared objects under /tmp/SBo instead
>> of the system library path /usr/lib64.
>>
>> The build succeeds on 14.2 if you first manually uninstall EFL.
>>
>> Curiously, this error does not occur in -current.  I originally
>> thought that the issue may have been due to a difference as regards
>> libtool, but both -14.2 and -current use the same version of libtool
>> "(GNU libtool) 2.4.6"
>>
>> After many weeks of not making any headway, I'm ready to release this
>> now with the caveat "you must uninstall your existing EFL package
>> before updating", and hold faith that 15.0 will make the bugs go away.
>>
>> My question to the group is, is this an acceptable course of action?
>>
>> If somebody more knowledgable than I would like to take a stab at it,
>> you can find the new SlackBuilds here:
>>
>> https://bitbucket.org/erikfalor/enlightenment-slackbuilds/src
> Yes, we do have some scripts with same warning in the README
>
>
gambas3 is one such example. In creating the package it uses itself to 
create some modules, but if it is already installed, it uses those 
binaries to create them instead, leaving you with a package linked to 
stuff from a previous install that will no longer be available. You have 
to do a removepkg before creating a new one.
On that subject, is it worth adding a test for previous version in the 
slackbuild, and should the build just stop if one exists, or should it 
be allowed to remove the previous existing installed version?
Regards, Tim

From heiko.rosemann at web.de  Tue Mar 19 19:08:04 2019
From: heiko.rosemann at web.de (Heiko Rosemann)
Date: Tue, 19 Mar 2019 20:08:04 +0100
Subject: [Slackbuilds-users] Upcoming version of EFL build fails on 14.2
In-Reply-To: <878a97a7-717a-74f1-25af-0c3a01c45efc@googlemail.com>
References: <20190319032720.6w52ueeypfar7rpb@viking2.falor>
 <ecf8ce55-d952-39aa-777d-b88abb0f9d89@slackbuilds.org>
 <878a97a7-717a-74f1-25af-0c3a01c45efc@googlemail.com>
Message-ID: <f1555b01-3d3b-7f36-2e7a-8a13a3227a87@web.de>

On 3/19/19 10:38 AM, Tim Dickson via SlackBuilds-users wrote:
>>> After many weeks of not making any headway, I'm ready to release this
>>> now with the caveat "you must uninstall your existing EFL package
>>> before updating", and hold faith that 15.0 will make the bugs go away.
>>> [...]
> On that subject, is it worth adding a test for previous version in the 
> slackbuild, and should the build just stop if one exists, or should it 
> be allowed to remove the previous existing installed version?
> Regards, Tim

gnucash is doing exactly that - failing the build if there already is a
version of gnucash installed:

# First, make sure a previous Gnucash installation is removed:
if [ -e /usr/bin/gnucash ]; then
  echo "A previous Gnucash installation has been found."
  echo "Please remove it before running this script."
  exit 1
fi

Best Regards,
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/20190319/4f961e84/attachment.asc>

From s.arcus at open-t.co.uk  Wed Mar 20 16:29:27 2019
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Wed, 20 Mar 2019 16:29:27 +0000
Subject: [Slackbuilds-users] Syncthing package is old
In-Reply-To: <CAFy1yb138v9o3bN6Zw1K_G395EvLOsY-ur4VxRuKUiLrnoMe-A@mail.gmail.com>
References: <CAFy1yb138v9o3bN6Zw1K_G395EvLOsY-ur4VxRuKUiLrnoMe-A@mail.gmail.com>
Message-ID: <277e3ba7-dbf2-efe8-ee3d-2a57069624b8@open-t.co.uk>

On 11/03/19 15:24, JCA wrote:
> At version 0.14.43, the Syncthing version in Slackbuilds is over one 
> year old. There have already been several new versions between 0.14.43 
> and the latest - 1.1.0. I have just tested with 1.1.0 under Slackware, 
> and it seems to work fine, even with remote systems running 0.14.43.

I've just submitted a version update to 1.1.0 yesterday. Thank you for 
the reminder and for testing the new version!

From dickson.tim at googlemail.com  Wed Mar 20 17:20:15 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Wed, 20 Mar 2019 17:20:15 +0000
Subject: [Slackbuilds-users] MuseScore Slackbuild.
In-Reply-To: <CAAZPBMjrQEbNdScLCs9m8DH=1mQdYZcO2BgwJAgFXzOhEDfpnA@mail.gmail.com>
References: <4c8fe995-e863-1c8c-f441-70905027889f@googlemail.com>
 <a80100a0b10d4dbc56e33c3a3263c420@mixedsignals.ml>
 <4902d3c4-8fb6-8ab2-c3ce-900afc792272@googlemail.com>
 <CAAZPBMjrQEbNdScLCs9m8DH=1mQdYZcO2BgwJAgFXzOhEDfpnA@mail.gmail.com>
Message-ID: <512355b2-8eb2-c162-bece-eab346a90f72@googlemail.com>

just in case Klaatu didn't get my email, i'm sending a copy on the list. 
Attached is an updated slackbuild for musescore 3.0.5 if he is 
interested in updating it.
it contains updates thanks to larry, to make use of new configure 
features and save a compile-time download, and a patch to allow 
qtwebengine thanks to me.
regards, Tim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MuseScore.tar.gz
Type: application/x-gzip
Size: 2491 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190320/0d08eaab/attachment-0001.bin>

From thomas at beingboiled.info  Thu Mar 21 00:39:02 2019
From: thomas at beingboiled.info (Thomas Morper)
Date: Thu, 21 Mar 2019 01:39:02 +0100 (CET)
Subject: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer
In-Reply-To: <ede8c0b6-1480-8d3b-8a3d-79cb44a9bbd8@slackbuilds.org>
References: <CAPh+tzNGHnfts=of0jCFySMrCnH73Y-HyApDPCm-LZqkrcK-pA@mail.gmail.com>
 <ede8c0b6-1480-8d3b-8a3d-79cb44a9bbd8@slackbuilds.org>
Message-ID: <alpine.BSF.2.21.9999.1903210131130.56765@cyber.tty23.com>

On Mon, 8 Oct 2018, Willy Sudiarto Raharjo wrote:

> I will take slack

Any progress on that?

The info file still lists Harald as the maintainer and there has been no 
update since. The old 3.1.1 version works well enough but propably has a 
number of security issues by now with its "bundled everything" approach.

-- 

From artourter at gmail.com  Thu Mar 21 10:51:51 2019
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Thu, 21 Mar 2019 10:51:51 +0000
Subject: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos
In-Reply-To: <CAK09-vnB8Hr8QUe=3QYMfp2jyY+D1kH6v0D8xTUXHUFEjc6vDA@mail.gmail.com>
References: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
 <CAK09-vnB8Hr8QUe=3QYMfp2jyY+D1kH6v0D8xTUXHUFEjc6vDA@mail.gmail.com>
Message-ID: <CAK09-v=BfpWENTYyWuQwodd7p-7YgRpGrzxNE8eePFiCOCoExQ@mail.gmail.com>

Actually, the one I use is keepassxc, so if it is ok, I'll put that one
back in the open. Sorry about this.

Cheers

Greg

On Sun, 17 Mar 2019 at 10:56, Greg' Ar Tourter <artourter at gmail.com> wrote:

> Hi,
>
> I can take over keepassx if no-one else wants it as I use it a lot.
>
> Cheers
>
> Greg
>
> On Sun, 17 Mar 2019 at 10:45, Willy Sudiarto Raharjo <
> willysr at slackbuilds.org> wrote:
>
>> Hi
>>
>> Anyone want to take over this scripts?
>>
>>
>> -------- Forwarded Message --------
>> Subject: New Maintainer Needed for SBos
>> Date: Sun, 17 Mar 2019 10:03:48 +0000
>> From: awg <awg at cock.li>
>> To: willysr at slackbuilds.org
>>
>> Hi Willy,
>>
>> I no longer use the following packages:
>> * development/ChezScheme
>> * libraries/libaaio
>> * system/dieharder
>> * office/keepassx
>>
>> If someone else could take over maintainership for these packages,
>> I'd be grateful.
>>
>> Unlike the other three, ChezScheme is still actively maintained by
>> its developers.  Whoever takes this over should run the full test
>> battery on both threaded and unthreaded builds after each update to
>> check for regressions.
>>
>> Thank you!
>>
>> --
>> 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/20190321/f4bdc7c1/attachment.html>

From slackbuilds at go4it2day.com  Thu Mar 21 12:53:26 2019
From: slackbuilds at go4it2day.com (SlackBuilds)
Date: Thu, 21 Mar 2019 06:53:26 -0600
Subject: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos
In-Reply-To: <CAK09-v=BfpWENTYyWuQwodd7p-7YgRpGrzxNE8eePFiCOCoExQ@mail.gmail.com>
References: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
 <CAK09-vnB8Hr8QUe=3QYMfp2jyY+D1kH6v0D8xTUXHUFEjc6vDA@mail.gmail.com>
 <CAK09-v=BfpWENTYyWuQwodd7p-7YgRpGrzxNE8eePFiCOCoExQ@mail.gmail.com>
Message-ID: <b51ada5df3263214c640f37d4bd355af@go4it2day.com>

Hello,

I'll take over maintenance of keepassx if nobody else feels the need to 
do so. I've been using it for a few years now.

Regards,
Stu



On 2019-03-21 04:51, Greg' Ar Tourter wrote:
> Actually, the one I use is keepassxc, so if it is ok, I'll put that
> one back in the open. Sorry about this.
> 
> Cheers
> 
> Greg
> 
> On Sun, 17 Mar 2019 at 10:56, Greg' Ar Tourter <artourter at gmail.com>
> wrote:
> 
>> Hi,
>> 
>> I can take over keepassx if no-one else wants it as I use it a lot.
>> 
>> Cheers
>> 
>> Greg
>> 
>> On Sun, 17 Mar 2019 at 10:45, Willy Sudiarto Raharjo
>> <willysr at slackbuilds.org> wrote:
>> 
>>> Hi
>>> 
>>> Anyone want to take over this scripts?
>>> 
>>> -------- Forwarded Message --------
>>> Subject: New Maintainer Needed for SBos
>>> Date: Sun, 17 Mar 2019 10:03:48 +0000
>>> From: awg <awg at cock.li>
>>> To: willysr at slackbuilds.org
>>> 
>>> Hi Willy,
>>> 
>>> I no longer use the following packages:
>>> * development/ChezScheme
>>> * libraries/libaaio
>>> * system/dieharder
>>> * office/keepassx
>>> 
>>> If someone else could take over maintainership for these packages,
>>> I'd be grateful.
>>> 
>>> Unlike the other three, ChezScheme is still actively maintained by
>>> its developers.  Whoever takes this over should run the full test
>>> battery on both threaded and unthreaded builds after each update
>>> to
>>> check for regressions.
>>> 
>>> Thank you!
>>> 
>>> --
>>> 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/
> _______________________________________________
> 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 mab974 at gmail.com  Thu Mar 21 13:09:51 2019
From: mab974 at gmail.com (mab974)
Date: Thu, 21 Mar 2019 17:09:51 +0400
Subject: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos
In-Reply-To: <CAK09-v=BfpWENTYyWuQwodd7p-7YgRpGrzxNE8eePFiCOCoExQ@mail.gmail.com>
References: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
 <CAK09-vnB8Hr8QUe=3QYMfp2jyY+D1kH6v0D8xTUXHUFEjc6vDA@mail.gmail.com>
 <CAK09-v=BfpWENTYyWuQwodd7p-7YgRpGrzxNE8eePFiCOCoExQ@mail.gmail.com>
Message-ID: <20190321170951.852f36612ba4d23d91e767b7@gmail.com>

Hi,

I can take over keepassx as i use it but this is my first try so please be
cool.

Michel

Selon "Greg' Ar Tourter" <artourter at gmail.com> :
> Actually, the one I use is keepassxc, so if it is ok, I'll put that one
> back in the open. Sorry about this.
> 
> Cheers
> 
> Greg
> 
> On Sun, 17 Mar 2019 at 10:56, Greg' Ar Tourter <artourter at gmail.com> wrote:
> 
> > Hi,
> >
> > I can take over keepassx if no-one else wants it as I use it a lot.
> >
> > Cheers
> >
> > Greg
> >
> > On Sun, 17 Mar 2019 at 10:45, Willy Sudiarto Raharjo <
> > willysr at slackbuilds.org> wrote:
> >
> >> Hi
> >>
> >> Anyone want to take over this scripts?
> >>
> >>
> >> -------- Forwarded Message --------
> >> Subject: New Maintainer Needed for SBos
> >> Date: Sun, 17 Mar 2019 10:03:48 +0000
> >> From: awg <awg at cock.li>
> >> To: willysr at slackbuilds.org
> >>
> >> Hi Willy,
> >>
> >> I no longer use the following packages:
> >> * development/ChezScheme
> >> * libraries/libaaio
> >> * system/dieharder
> >> * office/keepassx
> >>
> >> If someone else could take over maintainership for these packages,
> >> I'd be grateful.
> >>
> >> Unlike the other three, ChezScheme is still actively maintained by
> >> its developers.  Whoever takes this over should run the full test
> >> battery on both threaded and unthreaded builds after each update to
> >> check for regressions.
> >>
> >> Thank you!
> >>
> >> --
> >> 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/
> >>
> >>


-*- 
mab974<mab974 at gmail.com>

From slackbuilds at go4it2day.com  Thu Mar 21 13:17:41 2019
From: slackbuilds at go4it2day.com (SlackBuilds)
Date: Thu, 21 Mar 2019 07:17:41 -0600
Subject: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos
In-Reply-To: <20190321170951.852f36612ba4d23d91e767b7@gmail.com>
References: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
 <CAK09-vnB8Hr8QUe=3QYMfp2jyY+D1kH6v0D8xTUXHUFEjc6vDA@mail.gmail.com>
 <CAK09-v=BfpWENTYyWuQwodd7p-7YgRpGrzxNE8eePFiCOCoExQ@mail.gmail.com>
 <20190321170951.852f36612ba4d23d91e767b7@gmail.com>
Message-ID: <66d77e6e61f1de542b241e8637240ea4@go4it2day.com>

Michel,

I'll step aside on keepassx. All yours from my perspective.

Regards,
Stu


On 2019-03-21 07:09, mab974 wrote:
> Hi,
> 
> I can take over keepassx as i use it but this is my first try so please 
> be
> cool.
> 
> Michel
> 
> Selon "Greg' Ar Tourter" <artourter at gmail.com> :
>> Actually, the one I use is keepassxc, so if it is ok, I'll put that 
>> one
>> back in the open. Sorry about this.
>> 
>> Cheers
>> 
>> Greg
>> 
>> On Sun, 17 Mar 2019 at 10:56, Greg' Ar Tourter <artourter at gmail.com> 
>> wrote:
>> 
>> > Hi,
>> >
>> > I can take over keepassx if no-one else wants it as I use it a lot.
>> >
>> > Cheers
>> >
>> > Greg
>> >
>> > On Sun, 17 Mar 2019 at 10:45, Willy Sudiarto Raharjo <
>> > willysr at slackbuilds.org> wrote:
>> >
>> >> Hi
>> >>
>> >> Anyone want to take over this scripts?
>> >>
>> >>
>> >> -------- Forwarded Message --------
>> >> Subject: New Maintainer Needed for SBos
>> >> Date: Sun, 17 Mar 2019 10:03:48 +0000
>> >> From: awg <awg at cock.li>
>> >> To: willysr at slackbuilds.org
>> >>
>> >> Hi Willy,
>> >>
>> >> I no longer use the following packages:
>> >> * development/ChezScheme
>> >> * libraries/libaaio
>> >> * system/dieharder
>> >> * office/keepassx
>> >>
>> >> If someone else could take over maintainership for these packages,
>> >> I'd be grateful.
>> >>
>> >> Unlike the other three, ChezScheme is still actively maintained by
>> >> its developers.  Whoever takes this over should run the full test
>> >> battery on both threaded and unthreaded builds after each update to
>> >> check for regressions.
>> >>
>> >> Thank you!
>> >>
>> >> --
>> >> 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/
>> >>
>> >>
> 
> 
> -*-
> mab974<mab974 at gmail.com>
> _______________________________________________
> 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 mab974 at gmail.com  Thu Mar 21 13:51:53 2019
From: mab974 at gmail.com (mab974)
Date: Thu, 21 Mar 2019 17:51:53 +0400
Subject: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos
In-Reply-To: <66d77e6e61f1de542b241e8637240ea4@go4it2day.com>
References: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
 <CAK09-vnB8Hr8QUe=3QYMfp2jyY+D1kH6v0D8xTUXHUFEjc6vDA@mail.gmail.com>
 <CAK09-v=BfpWENTYyWuQwodd7p-7YgRpGrzxNE8eePFiCOCoExQ@mail.gmail.com>
 <20190321170951.852f36612ba4d23d91e767b7@gmail.com>
 <66d77e6e61f1de542b241e8637240ea4@go4it2day.com>
Message-ID: <20190321175153.96f57494a222db4fb1258c7b@gmail.com>

Ok, 

Thanks Stu

Michel

Selon SlackBuilds <slackbuilds at go4it2day.com> :
> Michel,
> 
> I'll step aside on keepassx. All yours from my perspective.
> 
> Regards,
> Stu
> 
> 
> On 2019-03-21 07:09, mab974 wrote:
> > Hi,
> > 
> > I can take over keepassx as i use it but this is my first try so please 
> > be
> > cool.
> > 
> > Michel
> > 
> > Selon "Greg' Ar Tourter" <artourter at gmail.com> :
> >> Actually, the one I use is keepassxc, so if it is ok, I'll put that 
> >> one
> >> back in the open. Sorry about this.
> >> 
> >> Cheers
> >> 
> >> Greg
> >> 
> >> On Sun, 17 Mar 2019 at 10:56, Greg' Ar Tourter <artourter at gmail.com> 
> >> wrote:
> >> 
> >> > Hi,
> >> >
> >> > I can take over keepassx if no-one else wants it as I use it a lot.
> >> >
> >> > Cheers
> >> >
> >> > Greg
> >> >
> >> > On Sun, 17 Mar 2019 at 10:45, Willy Sudiarto Raharjo <
> >> > willysr at slackbuilds.org> wrote:
> >> >
> >> >> Hi
> >> >>
> >> >> Anyone want to take over this scripts?
> >> >>
> >> >>
> >> >> -------- Forwarded Message --------
> >> >> Subject: New Maintainer Needed for SBos
> >> >> Date: Sun, 17 Mar 2019 10:03:48 +0000
> >> >> From: awg <awg at cock.li>
> >> >> To: willysr at slackbuilds.org
> >> >>
> >> >> Hi Willy,
> >> >>
> >> >> I no longer use the following packages:
> >> >> * development/ChezScheme
> >> >> * libraries/libaaio
> >> >> * system/dieharder
> >> >> * office/keepassx
> >> >>
> >> >> If someone else could take over maintainership for these packages,
> >> >> I'd be grateful.
> >> >>
> >> >> Unlike the other three, ChezScheme is still actively maintained by
> >> >> its developers.  Whoever takes this over should run the full test
> >> >> battery on both threaded and unthreaded builds after each update to
> >> >> check for regressions.
> >> >>
> >> >> Thank you!
> >> >>
> >> >> --
> >> >> 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/
> >> >>
> >> >>
> > 
> > 
> > -*-
> > mab974<mab974 at gmail.com>
> > _______________________________________________
> > 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/
> 


-*- 
mab974<mab974 at gmail.com>

From dickson.tim at googlemail.com  Thu Mar 21 17:46:48 2019
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Thu, 21 Mar 2019 17:46:48 +0000
Subject: [Slackbuilds-users] OpenBLAS issue
Message-ID: <c88e5055-96cb-a09a-e98b-d3a06d03e796@googlemail.com>

I'm having an issue with OpenBLAS slackbuild.
if I use a qemu vm with -cpu host ?? (the actual host cpu is AMD 
A10-9700) and pass the variable TARGET=ATHLON
then the build fails part way through.

if I use the same qemu vm with -cpu qemu64 and pass the variable 
TARGET=ATHLON
then the build completes.

This is the reverse of the previous behaviour of the openblas script.

I am guessing because if you use cpu=host, the real cpu is reported, and 
for whatever reason, OpenBLAS does not like the combination of AMD 
A10-9700 being reported when actually running in a vm without TARGET 
being specified (and it is not used in the script if a qemu vm is not 
detected).

the script uses a uname -p to detect if it is in a qemu vm
using
 ?if [ "x`dmidecode |grep Manufacturer|head -n1|awk '{print $NF}'`" = 
"xQEMU" ]; then

allows it to detect more reliably if it is running in a qemu vm.
I tested the script modified with the above qemu detection, and it 
completes in both scenarios
regards, Tim

From mariolpantunes at gmail.com  Thu Mar 21 21:48:34 2019
From: mariolpantunes at gmail.com (=?UTF-8?Q?M=c3=a1rio_Antunes?=)
Date: Thu, 21 Mar 2019 21:48:34 +0000
Subject: [Slackbuilds-users] OpenBLAS issue
In-Reply-To: <c88e5055-96cb-a09a-e98b-d3a06d03e796@googlemail.com>
References: <c88e5055-96cb-a09a-e98b-d3a06d03e796@googlemail.com>
Message-ID: <7a1c7845-22ef-4e79-dfb3-24ee87a4f185@gmail.com>

I will update the script,


Thanks

On 21/03/2019 17:46, Tim Dickson wrote:
> I'm having an issue with OpenBLAS slackbuild.
> if I use a qemu vm with -cpu host ?? (the actual host cpu is AMD 
> A10-9700) and pass the variable TARGET=ATHLON
> then the build fails part way through.
>
> if I use the same qemu vm with -cpu qemu64 and pass the variable 
> TARGET=ATHLON
> then the build completes.
>
> This is the reverse of the previous behaviour of the openblas script.
>
> I am guessing because if you use cpu=host, the real cpu is reported, 
> and for whatever reason, OpenBLAS does not like the combination of AMD 
> A10-9700 being reported when actually running in a vm without TARGET 
> being specified (and it is not used in the script if a qemu vm is not 
> detected).
>
> the script uses a uname -p to detect if it is in a qemu vm
> using
> ?if [ "x`dmidecode |grep Manufacturer|head -n1|awk '{print $NF}'`" = 
> "xQEMU" ]; then
>
> allows it to detect more reliably if it is running in a qemu vm.
> I tested the script modified with the above qemu detection, and it 
> completes in both scenarios
> regards, Tim

From slackbuilds at schoepfer.info  Fri Mar 22 15:37:34 2019
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 22 Mar 2019 16:37:34 +0100
Subject: [Slackbuilds-users] Download url help
Message-ID: <45aded80a5e818527b4e8b7cd5d4b22a@schoepfer.info>

Hi all,

i need help getting a valid download link for the info-file of a new 
slackbuild,
the website is 
http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=summary ,
the source-file/snapshot is "Add forgotten files 1.4.70b snapshot"
http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=snapshot;h=5904a294b3b33dfd3ca11e4e48133151787f0d8f;sf=tgz

When downloaded via firefox, i get polyglot-5904a29.tar.gz, but wget 
doesn't work, i get
gitweb.cgi?p=polyglot.git with the website content.

Any help appreciated, thanks,

Johannes

From xpetrl at aol.com  Fri Mar 22 17:15:10 2019
From: xpetrl at aol.com (xpetrl)
Date: Fri, 22 Mar 2019 18:15:10 +0100
Subject: [Slackbuilds-users] Download url help
In-Reply-To: <45aded80a5e818527b4e8b7cd5d4b22a@schoepfer.info>
References: <45aded80a5e818527b4e8b7cd5d4b22a@schoepfer.info>
Message-ID: <217561d9-ea6e-3356-64ca-ee8d420795f6@aol.com>

> i need help getting a valid download link for the info-file of a new 
> slackbuild, the website is 
> http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=summary ,
> the source-file/snapshot is "Add forgotten files 1.4.70b snapshot"
> http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=snapshot;h=5904a294b3b33dfd3ca11e4e48133151787f0d8f;sf=tgz 
> 
> 
> When downloaded via firefox, i get polyglot-5904a29.tar.gz, but wget 
> doesn't work, i get
> gitweb.cgi?p=polyglot.git with the website content.
> 

wget has an option to write the file name output (-O).
If the link you'd to download has some special character,
surround it with quotation.

wget 
"http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=snapshot;h=5904a294b3b33dfd3ca11e4e48133151787f0d8f;sf=tgz" 
-O polyglot-5904a29.tar.gz


--
xpetrl

From jebrhansen+SBo at gmail.com  Fri Mar 22 17:32:43 2019
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Fri, 22 Mar 2019 11:32:43 -0600
Subject: [Slackbuilds-users] Download url help
In-Reply-To: <217561d9-ea6e-3356-64ca-ee8d420795f6@aol.com>
References: <45aded80a5e818527b4e8b7cd5d4b22a@schoepfer.info>
 <217561d9-ea6e-3356-64ca-ee8d420795f6@aol.com>
Message-ID: <CANi9qSvYKRv=WiqbTUwn02HT+Aob98YZSAWHP8Tr-PDNfbT0eQ@mail.gmail.com>

On Fri, Mar 22, 2019, 11:15 AM xpetrl via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> > i need help getting a valid download link for the info-file of a new
> > slackbuild, the website is
> > http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=summary ,
> > the source-file/snapshot is "Add forgotten files 1.4.70b snapshot"
> >
> http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=snapshot;h=5904a294b3b33dfd3ca11e4e48133151787f0d8f;sf=tgz
> >
> >
> > When downloaded via firefox, i get polyglot-5904a29.tar.gz, but wget
> > doesn't work, i get
> > gitweb.cgi?p=polyglot.git with the website content.
> >
>
> wget has an option to write the file name output (-O).
> If the link you'd to download has some special character,
> surround it with quotation.
>
> wget
> "
> http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=snapshot;h=5904a294b3b33dfd3ca11e4e48133151787f0d8f;sf=tgz"
>
> -O polyglot-5904a29.tar.gz
>

Looks like that is an older version and there's an active version on GitHub
with recent releases.

https://github.com/DraqueT/PolyGlot/

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190322/4285396d/attachment.html>

From slackbuilds at schoepfer.info  Fri Mar 22 18:36:16 2019
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 22 Mar 2019 19:36:16 +0100
Subject: [Slackbuilds-users] Download url help
In-Reply-To: <CANi9qSvYKRv=WiqbTUwn02HT+Aob98YZSAWHP8Tr-PDNfbT0eQ@mail.gmail.com>
References: <45aded80a5e818527b4e8b7cd5d4b22a@schoepfer.info>
 <217561d9-ea6e-3356-64ca-ee8d420795f6@aol.com>
 <CANi9qSvYKRv=WiqbTUwn02HT+Aob98YZSAWHP8Tr-PDNfbT0eQ@mail.gmail.com>
Message-ID: <60dcebc39923b68f87e3c694f51e3881@schoepfer.info>

On 2019-03-22 18:32, Jeremy Hansen wrote:
> On Fri, Mar 22, 2019, 11:15 AM xpetrl via SlackBuilds-users
> <slackbuilds-users at slackbuilds.org> wrote:
> 
>>> i need help getting a valid download link for the info-file of a
>> new
>>> slackbuild, the website is
>>> http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=summary
>> ,
>>> the source-file/snapshot is "Add forgotten files 1.4.70b snapshot"
>>> 
>> 
> http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=snapshot;h=5904a294b3b33dfd3ca11e4e48133151787f0d8f;sf=tgz
>> 
>>> 
>>> 
>>> When downloaded via firefox, i get polyglot-5904a29.tar.gz, but
>> wget
>>> doesn't work, i get
>>> gitweb.cgi?p=polyglot.git with the website content.
>>> 
>> 
>> wget has an option to write the file name output (-O).
>> If the link you'd to download has some special character,
>> surround it with quotation.

I guess that's not valid for an slackbuild info-file.

> Looks like that is an older version and there's an active version on
> GitHub with recent releases.
> 
> https://github.com/DraqueT/PolyGlot/

No, that's a complete diffrent project, with the same name.

Thanks anyway, if there's no solution like with e.g. sourgeforge links, 
i'll ask if it may be hostet
on https://slackware.uk/sbosrcarch/ .

Johannes

From willysr at slackbuilds.org  Sat Mar 23 03:19:56 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 23 Mar 2019 10:19:56 +0700
Subject: [Slackbuilds-users] Updates - 20190323.1
Message-ID: <5b631ec1-4b0e-91f4-3f5d-3d0696ce7eae@slackbuilds.org>

Sat Mar 23 03:00:15 UTC 2019
academic/copasi: Updated for version 4.25.207.
academic/cvc4: Added (Theorem Solver).
academic/ed-v6: Added (old version of ed).
academic/z3: Added (theorem solver).
desktop/Zafiro-icons: Updated for version 0.9.
desktop/awesome: Updated for version 4.3.
desktop/gnome-menus: Updated for version 3.32.0.
desktop/i3: Updated for version 4.16.1 + new maintainer.
desktop/i3status: Updated for version 2.12 + new maintainer.
desktop/jgmenu: Updated for version 2.2.1.
desktop/qt5ct: Updated for version 0.38.
development/eclipse-cpp: Updated for version 201903.
development/eclipse-java: Updated for version 201903.
development/eclipse-jee: Updated for version 201903.
development/openjdk8: Updated for version 8u201.
development/pahole: Added (Show data structure layout).
development/postman: Updated for version 7.0.5.
development/rtags: Updated for version 2.30.
development/sublime_text: Updated for version 3.2.00.
games/CorsixTH: Added (clone of Theme Hospital).
games/edgar: Updated for version 1.31.
games/stockfish: Updated for version 10.
games/vkQuake: Updated for version 1.01.0.
gis/Fiona: Updated for version 1.8.6.
graphics/digikam: Fix build with latest libpgf.
graphics/vsxu: Fix plugins location
graphics/white_dune: Updated for version 0.99pl1436.
libraries/dav1d: Updated for version 0.2.1.
libraries/libdatrie: Added (An Implementation of Double-Array Trie).
libraries/libgda: Updated for version 5.2.8.
libraries/libopenshot-audio: Updated for version 2.4.4
libraries/libopenshot: Updated for version 2.4.4
libraries/librelp: Updated for version 1.4.0.
libraries/libseccomp: Updated for version 2.4.0
libraries/libthai: Added (A set of Thai language support routines).
libraries/libuv: Updated for version 1.27.0.
libraries/physfs: Updated for version 3.0.2.
libraries/smpeg2: Added (MP3 support for SDL2_mixer).
libraries/xcb-util-xrm: New maintainer.
multimedia/MuseScore: Updated for version 3.0.4
multimedia/openshot: Updated for version 2.4.4
multimedia/plexmediaserver: Updated for version 1.15.2.793.
multimedia/vlc: Update README
network/brave-browser: Updated for version 0.61.51.
network/discord: Update to 0.0.9.
network/filezilla: Updated for version 3.41.2.
network/lurch: Updated for version 0.6.8.
network/opera-developer: Updated for version 60.0.3254.0.
network/opera: Updated for version 58.0.3135.107.
network/prosody-mod-smacks: Updated for version hg3493.
network/putty: Updated for version 0.71.
network/qutebrowser: Update to 1.6.0
network/slurm: Updated for version 18.08.6_2.
network/sshblock: Update README.
network/syncthing: Updated for version 1.1.0.
network/telegram: Updated for version 1.6.0.
network/w3m: Update to 0.5.3_37
network/youtube-dl: Updated for version 2019.03.09.
office/LibreOffice: Updated for version 6.2.2.2
office/ProjectLibre: Updated for version 1.9.0.
office/libreoffice-helppack: Updated for version 6.2.2.
office/libreoffice-langpack: Updated for version 6.2.2.
office/libreoffice: Updated for version 6.2.2.
perl/nqp: Fix VERSION.
perl/perl-AnyEvent: Updated for version 7.15 + new maintainer.
perl/perl-Test-Inter: Updated for version 1.09.
python/GeoIP-Python: enable Python3
python/distorm: Updated for version 3.4.1.
python/git-fame: Updated for version 1.8.0.
python/pycryptodome: Updated for version 3.8.0.
python/pyotp: enable Python3
python/python-configargparse: Updated for version 0.14.0.
python/python-fonttools: Updated for version 3.39.0.
python/python-jsonrpclib: Updated for version 0.4.0.
python/python3-astroid: Updated for version 2.2.5.
python/python3-isort: Updated for version 4.3.15.
python/python3-multidict: Update script.
python/python3-pylint: Updated for version 2.3.1.
python/python3-tornado: Updated for version 6.0.1.
python/sphinxcontrib-plantuml: Updated for version 0.14.
python/websocket-client: Updated for version 0.56.0.
python/werkzeug: enable Python3
ruby/gem2tgz: Update homepage and download.
ruby/ruby-build: Updated for version 20190320.
system/aide: Updated for version 0.16.1.
system/bit-babbler: Update script.
system/chronograf: Updated for version 1.7.9.
system/cnijfilter2: Updated for version 5.80.1.
system/isdct: Updated for version 3.0.19.
system/openmpi: Updated for version 4.0.0.
system/pixma: Mention related cnijfilter2 package
system/pytrash: Updated for version 1.1.4.
system/qtfm: Updated for version 6.1.8.
system/rsyslog: Updated for version 8.1903.0.
system/telegraf: Updated for version 1.10.1.
system/volatility: Updated for version 2.6.1.
system/wine-staging: Updated for version 4.4.
+--------------------------+


-- 
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/20190323/cc593c00/attachment-0001.asc>

From jens at tuxane.com  Mon Mar 25 08:32:12 2019
From: jens at tuxane.com (burro-net <jens@tuxane.com>)
Date: Mon, 25 Mar 2019 09:32:12 +0100
Subject: [Slackbuilds-users] New maintainer or remove from SBo
Message-ID: <2be0cc72-028b-58ae-8ec5-f9ba78ad9e68@tuxane.com>

Hello,

I still maintain these two slack-build scripts:

system/unetbootin

desktop/quadkonsole4


I would like to hand them over to somebody, but I guess the admins
should decide if it's worth keeping them at all.

- desktop/quadkonsole4: it's QT4 only and not maintained from it's
author for ages. And QT4 is obsolete .

- system/unetbootin: Does someone use it still ? It has a quite fast
development progress, so it should be kept updated on a regularly basis
to be useful
( what I can' t assure at the moment) .
So in times of dd, Etcher and image writers for embedded, I think it
only makes sense to keep it on SBo, if s.o really needs it and is able
to keep up with the sources .


Thanks,
Jens


-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190325/b951a948/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature_mail.png
Type: image/png
Size: 13147 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190325/b951a948/attachment.png>

From korgie at gmail.com  Mon Mar 25 12:11:58 2019
From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=)
Date: Mon, 25 Mar 2019 14:11:58 +0200
Subject: [Slackbuilds-users] New maintainer or remove from SBo
In-Reply-To: <2be0cc72-028b-58ae-8ec5-f9ba78ad9e68@tuxane.com>
References: <2be0cc72-028b-58ae-8ec5-f9ba78ad9e68@tuxane.com>
Message-ID: <1797697C-0DE8-4A42-A3B1-22BA8FC4BDF8@gmail.com>

25 ??? 2019, 10:32 ??, ? ??????? ?burro-net <jens at tuxane.com> <jens at tuxane.com>? ??????:

> - system/unetbootin: Does someone use it still ? It has a quite fast development progress, so it should be kept updated on a regularly basis to be useful

I use it sporadically. I manually Download the iso and unebootin does the rest. Let it  sink if you don?t have time, no reason to abandon. If someone want newer version can use as your work as starting point.

From richard at aaazen.com  Mon Mar 25 17:27:30 2019
From: richard at aaazen.com (Richard Narron)
Date: Mon, 25 Mar 2019 10:27:30 -0700 (PDT)
Subject: [Slackbuilds-users] Memtest86+-5.01 patch for hang with SMP test #7
 at 22% done
Message-ID: <alpine.LNX.2.20.1903251003060.9644@thursday.test>

Two of my machines hang in the exact same spot when using the Slackware
memtest with SMP (F2) at 22% done in test #7.

There is a patch on forum.canardpc.com that fixes the problem:

https://forum.canardpc.com/threads/117454-PATCH-Fix-for-Freeze-on-test-7-in-SMP-mode

Also posted as memtest86+-7-smp.patch on debian in:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795421#25

So with this patch and applying the 5 patches from Debian sid:

https://sources.debian.org/src/memtest86+/5.01-3/debian/patches/

I modified the memtest86+.SlackBuild for version 5.01, built it on
Slackware 14.2 32-bit and got it working.

It works well. There are no more hangs on test #7

From matteo.bernardini at gmail.com  Mon Mar 25 18:22:40 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 25 Mar 2019 19:22:40 +0100
Subject: [Slackbuilds-users] Memtest86+-5.01 patch for hang with SMP
 test #7 at 22% done
In-Reply-To: <alpine.LNX.2.20.1903251003060.9644@thursday.test>
References: <alpine.LNX.2.20.1903251003060.9644@thursday.test>
Message-ID: <CAPsDuS57xPrr45Vr-rnggMbTeuD4EPvuv8OqskzpsHUBivygcA@mail.gmail.com>

Il giorno lun 25 mar 2019 alle ore 18:34 Richard Narron
<richard at aaazen.com> ha scritto:
>
> Two of my machines hang in the exact same spot when using the Slackware
> memtest with SMP (F2) at 22% done in test #7.
>
> There is a patch on forum.canardpc.com that fixes the problem:
>
> https://forum.canardpc.com/threads/117454-PATCH-Fix-for-Freeze-on-test-7-in-SMP-mode
>
> Also posted as memtest86+-7-smp.patch on debian in:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795421#25
>
> So with this patch and applying the 5 patches from Debian sid:
>
> https://sources.debian.org/src/memtest86+/5.01-3/debian/patches/
>
> I modified the memtest86+.SlackBuild for version 5.01, built it on
> Slackware 14.2 32-bit and got it working.
>
> It works well. There are no more hangs on test #7

forwarding this to the maintainer.

From kristofru at gmail.com  Tue Mar 26 06:25:47 2019
From: kristofru at gmail.com (Chris Abela)
Date: Tue, 26 Mar 2019 07:25:47 +0100
Subject: [Slackbuilds-users] libopenshot and libopenshot-audio
Message-ID: <CAJ2_kYrRyqmVepiQctquX1duGcBVwkkVZXdruZ-zyNWfnmY9dg@mail.gmail.com>

I am unable to download the sources for libopenshot and libopenshot-audio;
I am getting an HTTP 404 Error. Is anyone willing to provide alternative
links or share the code?

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190326/dabf433a/attachment.html>

From chris.willing at linux.com  Tue Mar 26 06:59:17 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Tue, 26 Mar 2019 16:59:17 +1000
Subject: [Slackbuilds-users] libopenshot and libopenshot-audio
In-Reply-To: <CAJ2_kYrRyqmVepiQctquX1duGcBVwkkVZXdruZ-zyNWfnmY9dg@mail.gmail.com>
References: <CAJ2_kYrRyqmVepiQctquX1duGcBVwkkVZXdruZ-zyNWfnmY9dg@mail.gmail.com>
Message-ID: <57d2c3f6-95c1-3f88-4853-adba771dce0f@linux.com>

On 26/3/19 4:25 pm, Chris Abela wrote:
> I am unable to download the sources for libopenshot and
> libopenshot-audio; I am getting an HTTP 404 Error. Is anyone willing to
> provide alternative links or share the code?
> 

Looks like they've pulled the 2.4.4 version and 0.2.3 is now the latest
(0.1.8 for -audio). I'll update the SlackBuild but in the meantime I
think you could just substitute the VERSION and it will build/work OK.

I have copies the 2.4.4 source tarballs here but not sure if it's a good
thing to share them if upstream have deliberately pulled that version.

My guess is that they just misnamed the lib tarballs; 2.4.4 is the new
openshot application version and they probably inadvertently used the
same number for the new lib releases.

chris

From matteo.bernardini at gmail.com  Tue Mar 26 07:04:45 2019
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 26 Mar 2019 08:04:45 +0100
Subject: [Slackbuilds-users] libopenshot and libopenshot-audio
In-Reply-To: <CAJ2_kYrRyqmVepiQctquX1duGcBVwkkVZXdruZ-zyNWfnmY9dg@mail.gmail.com>
References: <CAJ2_kYrRyqmVepiQctquX1duGcBVwkkVZXdruZ-zyNWfnmY9dg@mail.gmail.com>
Message-ID: <CAPsDuS4jui90rSMYMfQQNEue6V+CiT3CvPRTX+khhkS4u=w__g@mail.gmail.com>

Il mar 26 mar 2019, 07:26 Chris Abela <kristofru at gmail.com> ha scritto:

> I am unable to download the sources for libopenshot and libopenshot-audio;
> I am getting an HTTP 404 Error. Is anyone willing to provide alternative
> links or share the code?
>

For alternative download links, I usually check here

https://slackware.uk/sbosrcarch/

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190326/ded2b713/attachment.html>

From chris.willing at linux.com  Tue Mar 26 08:23:14 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Tue, 26 Mar 2019 18:23:14 +1000
Subject: [Slackbuilds-users] libopenshot and libopenshot-audio
In-Reply-To: <57d2c3f6-95c1-3f88-4853-adba771dce0f@linux.com>
References: <CAJ2_kYrRyqmVepiQctquX1duGcBVwkkVZXdruZ-zyNWfnmY9dg@mail.gmail.com>
 <57d2c3f6-95c1-3f88-4853-adba771dce0f@linux.com>
Message-ID: <11bef3d6-1a7c-f7db-424f-99d7795a75e7@linux.com>

On 26/3/19 4:59 pm, Christoph Willing wrote:
> On 26/3/19 4:25 pm, Chris Abela wrote:
>> I am unable to download the sources for libopenshot and
>> libopenshot-audio; I am getting an HTTP 404 Error. Is anyone willing to
>> provide alternative links or share the code?
>>
> 
> Looks like they've pulled the 2.4.4 version and 0.2.3 is now the latest
> (0.1.8 for -audio). I'll update the SlackBuild but in the meantime I
> think you could just substitute the VERSION and it will build/work OK.
> 
> I have copies the 2.4.4 source tarballs here but not sure if it's a good
> thing to share them if upstream have deliberately pulled that version.
> 
> My guess is that they just misnamed the lib tarballs; 2.4.4 is the new
> openshot application version and they probably inadvertently used the
> same number for the new lib releases.
> 

Updated SlackBuilds are at:

https://git.slackbuilds.org/slackbuilds/tree/libraries/libopenshot-audio?h=user/chris.willing/updates&id=c1506d50bb55d3318daf7dad2cd55229f61282a3
and:

https://git.slackbuilds.org/slackbuilds/tree/libraries/libopenshot?h=user/chris.willing/updates&id=07090f964c91c4fd92a864c1e7739251cdec7db0

chris

From kristofru at gmail.com  Tue Mar 26 14:11:56 2019
From: kristofru at gmail.com (Chris Abela)
Date: Tue, 26 Mar 2019 15:11:56 +0100
Subject: [Slackbuilds-users] libopenshot and libopenshot-audio
In-Reply-To: <CAPsDuS4jui90rSMYMfQQNEue6V+CiT3CvPRTX+khhkS4u=w__g@mail.gmail.com>
References: <CAJ2_kYrRyqmVepiQctquX1duGcBVwkkVZXdruZ-zyNWfnmY9dg@mail.gmail.com>
 <CAPsDuS4jui90rSMYMfQQNEue6V+CiT3CvPRTX+khhkS4u=w__g@mail.gmail.com>
Message-ID: <CAJ2_kYoaQ6=S5hzw0voTdY-u+rGZjH0T7VEdorStq2C6uwazLg@mail.gmail.com>

Hi Matteo,

Thank You for the link.

Chris

On Tue, Mar 26, 2019 at 8:05 AM Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

>
> Il mar 26 mar 2019, 07:26 Chris Abela <kristofru at gmail.com> ha scritto:
>
>> I am unable to download the sources for libopenshot and
>> libopenshot-audio; I am getting an HTTP 404 Error. Is anyone willing to
>> provide alternative links or share the code?
>>
>
> For alternative download links, I usually check here
>
> https://slackware.uk/sbosrcarch/
>
>> _______________________________________________
> 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/20190326/abc5345c/attachment-0001.html>

From kristofru at gmail.com  Tue Mar 26 14:13:39 2019
From: kristofru at gmail.com (Chris Abela)
Date: Tue, 26 Mar 2019 15:13:39 +0100
Subject: [Slackbuilds-users] libopenshot and libopenshot-audio
In-Reply-To: <11bef3d6-1a7c-f7db-424f-99d7795a75e7@linux.com>
References: <CAJ2_kYrRyqmVepiQctquX1duGcBVwkkVZXdruZ-zyNWfnmY9dg@mail.gmail.com>
 <57d2c3f6-95c1-3f88-4853-adba771dce0f@linux.com>
 <11bef3d6-1a7c-f7db-424f-99d7795a75e7@linux.com>
Message-ID: <CAJ2_kYqJPYYM2UUd=CMcVmwYbJyJw2FTqAsDjTVOJM9FO6ZaBA@mail.gmail.com>

Thank You Christoph,

As soon as I find some time, I will try them out.

Chris

On Tue, Mar 26, 2019 at 9:23 AM Christoph Willing <chris.willing at linux.com>
wrote:

> On 26/3/19 4:59 pm, Christoph Willing wrote:
> > On 26/3/19 4:25 pm, Chris Abela wrote:
> >> I am unable to download the sources for libopenshot and
> >> libopenshot-audio; I am getting an HTTP 404 Error. Is anyone willing to
> >> provide alternative links or share the code?
> >>
> >
> > Looks like they've pulled the 2.4.4 version and 0.2.3 is now the latest
> > (0.1.8 for -audio). I'll update the SlackBuild but in the meantime I
> > think you could just substitute the VERSION and it will build/work OK.
> >
> > I have copies the 2.4.4 source tarballs here but not sure if it's a good
> > thing to share them if upstream have deliberately pulled that version.
> >
> > My guess is that they just misnamed the lib tarballs; 2.4.4 is the new
> > openshot application version and they probably inadvertently used the
> > same number for the new lib releases.
> >
>
> Updated SlackBuilds are at:
>
>
> https://git.slackbuilds.org/slackbuilds/tree/libraries/libopenshot-audio?h=user/chris.willing/updates&id=c1506d50bb55d3318daf7dad2cd55229f61282a3
> and:
>
>
> https://git.slackbuilds.org/slackbuilds/tree/libraries/libopenshot?h=user/chris.willing/updates&id=07090f964c91c4fd92a864c1e7739251cdec7db0
>
> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190326/5d6a2630/attachment.html>

From richard at aaazen.com  Tue Mar 26 20:26:29 2019
From: richard at aaazen.com (Richard Narron)
Date: Tue, 26 Mar 2019 13:26:29 -0700 (PDT)
Subject: [Slackbuilds-users] Memtest86+-5.01 patch for hang with SMP
 test #7 at 22% done
In-Reply-To: <CAPsDuS57xPrr45Vr-rnggMbTeuD4EPvuv8OqskzpsHUBivygcA@mail.gmail.com>
References: <alpine.LNX.2.20.1903251003060.9644@thursday.test>
 <CAPsDuS57xPrr45Vr-rnggMbTeuD4EPvuv8OqskzpsHUBivygcA@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1903261317540.11963@thursday.test>

On Mon, 25 Mar 2019, Matteo Bernardini wrote:

> Il giorno lun 25 mar 2019 alle ore 18:34 Richard Narron
> <richard at aaazen.com> ha scritto:
> >
> > Two of my machines hang in the exact same spot when using the Slackware
> > memtest with SMP (F2) at 22% done in test #7.
> >
> > There is a patch on forum.canardpc.com that fixes the problem:
> >
> > https://forum.canardpc.com/threads/117454-PATCH-Fix-for-Freeze-on-test-7-in-SMP-mode
> >
> > Also posted as memtest86+-7-smp.patch on debian in:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795421#25
> >
> > So with this patch and applying the 5 patches from Debian sid:
> >
> > https://sources.debian.org/src/memtest86+/5.01-3/debian/patches/
> >
> > I modified the memtest86+.SlackBuild for version 5.01, built it on
> > Slackware 14.2 32-bit and got it working.
> >
> > It works well. There are no more hangs on test #7
>
> forwarding this to the maintainer.

Thanks Matteo.  Apparently the "Cc:" addresses on posts are removed so
nobody sees them.  I put all the names on the "To:".

The Memtest86+ package only builds on 32-bit Slackware 14.2 and maybe
earlier.

I tried building on 32-bit Slackware-current and it built ok, but it froze
when running test #1. So I have to do some more research/testing...

Richard Narron

From elyk03 at gmail.com  Wed Mar 27 00:56:26 2019
From: elyk03 at gmail.com (Kyle Guinn)
Date: Tue, 26 Mar 2019 19:56:26 -0500
Subject: [Slackbuilds-users] Memtest86+-5.01 patch for hang with SMP
 test #7 at 22% done
In-Reply-To: <alpine.LNX.2.20.1903261317540.11963@thursday.test>
References: <alpine.LNX.2.20.1903251003060.9644@thursday.test>
 <CAPsDuS57xPrr45Vr-rnggMbTeuD4EPvuv8OqskzpsHUBivygcA@mail.gmail.com>
 <alpine.LNX.2.20.1903261317540.11963@thursday.test>
Message-ID: <CAJCpn83cP0dSiW5gBgq9kQ3pdNvR_caAB24q7ZwkmztbPy5H7g@mail.gmail.com>

On 3/26/19, Richard Narron <richard at aaazen.com> wrote:
> On Mon, 25 Mar 2019, Matteo Bernardini wrote:
>
>> Il giorno lun 25 mar 2019 alle ore 18:34 Richard Narron
>> <richard at aaazen.com> ha scritto:
>> >
>> > Two of my machines hang in the exact same spot when using the Slackware
>> > memtest with SMP (F2) at 22% done in test #7.
>> >
>> > There is a patch on forum.canardpc.com that fixes the problem:
>> >
>> > https://forum.canardpc.com/threads/117454-PATCH-Fix-for-Freeze-on-test-7-in-SMP-mode
>> >
>> > Also posted as memtest86+-7-smp.patch on debian in:
>> >
>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795421#25
>> >
>> > So with this patch and applying the 5 patches from Debian sid:
>> >
>> > https://sources.debian.org/src/memtest86+/5.01-3/debian/patches/
>> >
>> > I modified the memtest86+.SlackBuild for version 5.01, built it on
>> > Slackware 14.2 32-bit and got it working.
>> >
>> > It works well. There are no more hangs on test #7
>>
>> forwarding this to the maintainer.
>
> Thanks Matteo.  Apparently the "Cc:" addresses on posts are removed so
> nobody sees them.  I put all the names on the "To:".
>
> The Memtest86+ package only builds on 32-bit Slackware 14.2 and maybe
> earlier.
>
> I tried building on 32-bit Slackware-current and it built ok, but it froze
> when running test #1. So I have to do some more research/testing...

I've held back on updating both memtest86 and memtest86+ due to
problems trying to get them to run.  I'll take another try with those
patches and see if I have any better luck.

Thanks for the report!
-Kyle

From ewfalor at gmail.com  Wed Mar 27 03:36:18 2019
From: ewfalor at gmail.com (Erik Falor)
Date: Tue, 26 Mar 2019 21:36:18 -0600
Subject: [Slackbuilds-users] Fwd: New Maintainer Needed for SBos
In-Reply-To: <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
References: <md5:jenPDIyiRjcNGZ4tC4y4iQ==>
 <9ce2cca3-f3a6-10f3-f504-57e8acaa483b@slackbuilds.org>
Message-ID: <20190327033618.3c5nfxjczvtki562@viking2.falor>

On Sun, Mar 17, 2019 at 05:45:39PM +0700, Willy Sudiarto Raharjo wrote:
> Hi
> 
> Anyone want to take over this scripts?
>
> * development/ChezScheme
 
I'm a Schemer, and I'd like to take ChezScheme.

> Unlike the other three, ChezScheme is still actively maintained by
> its developers.  Whoever takes this over should run the full test
> battery on both threaded and unthreaded builds after each update to
> check for regressions.

Duly noted.

-- 
Erik Falor
Registered Linux User #445632                    http://unnovative.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190326/37aa43d6/attachment.asc>

From ricardo at palmtx.com.ar  Wed Mar 27 21:34:20 2019
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Wed, 27 Mar 2019 18:34:20 -0300
Subject: [Slackbuilds-users] i3 up for grabs / new maintainer for
 herbstluftwm
In-Reply-To: <1f691d06-2a95-0b95-a9de-d8b953b1edf9@schoepfer.info>
References: <fd862e6c659371c059c13a5c528aa96f@schoepfer.info>
 <201811162001.52606.ricardo@palmtx.com.ar>
 <1f691d06-2a95-0b95-a9de-d8b953b1edf9@schoepfer.info>
Message-ID: <201903271834.20854.ricardo@palmtx.com.ar>

Hello list,

I'm taking over yajl, should I submit a tar.gz through the form [1] or is 
there another preferred method?

[1] https://slackbuilds.org/submit/

El Martes 26/03/2019 a las 11:31, Franzen escribi?:
> Hi Ricardo,
>
> If you're still interested in maintaining yajl, pleaso do so, so that
> i'm not listed as maintainer anymore.
>
> Johannes

El Mi?rcoles 27/03/2019 a las 08:32, Emmanuel escribi?:
> Hola Ricardo, si quer?s podes manterlo vos o si no quer?s agregarte un
> paquete mas a tu lista avisame y me hago cargo yo, no hay problema :-).
>
> Saludos
>
> On Tue, Mar 26, 2019 at 6:51 PM Ricardo J. Barberis <ricardo at palmtx.com.ar>
> wrote:
> > Hi!
> >
> > Are you still up for taking yajl?
> >
> > If you don't want it or can't maintain it I can take it, as it's a
> > dependency for collectd, which I maintain.
> >
> > Cheers!

-- 
Ricardo J. Barberis
Usuario Linux N? 250625: http://counter.li.org/
Usuario LFS N? 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com

From ricardo at palmtx.com.ar  Wed Mar 27 21:37:44 2019
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Wed, 27 Mar 2019 18:37:44 -0300
Subject: [Slackbuilds-users] Taking over yajl
Message-ID: <201903271837.44880.ricardo@palmtx.com.ar>

Sorry for my previous email semi-hijacking the "i3 up for grabs / new 
maintainer for herbstluftwm" thread, I'm sending it again as a new thread so 
it doesn't get lost in the noise.

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

Hello list,

I'm taking over yajl, should I submit a tar.gz through the form [1] or is 
there another preferred method?

[1] https://slackbuilds.org/submit/

El Martes 26/03/2019 a las 11:31, Franzen escribi?:
> Hi Ricardo,
>
> If you're still interested in maintaining yajl, pleaso do so, so that
> i'm not listed as maintainer anymore.
>
> Johannes

El Mi?rcoles 27/03/2019 a las 08:32, Emmanuel escribi?:
> Hola Ricardo, si quer?s podes manterlo vos o si no quer?s agregarte un
> paquete mas a tu lista avisame y me hago cargo yo, no hay problema :-).
>
> Saludos
>
> On Tue, Mar 26, 2019 at 6:51 PM Ricardo J. Barberis <ricardo at palmtx.com.ar>
> wrote:
> > Hi!
> >
> > Are you still up for taking yajl?
> >
> > If you don't want it or can't maintain it I can take it, as it's a
> > dependency for collectd, which I maintain.
> >
> > Cheers!
-- 
Ricardo J. Barberis
Usuario Linux N? 250625: http://counter.li.org/
Usuario LFS N? 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com

From kristofru at gmail.com  Thu Mar 28 08:18:03 2019
From: kristofru at gmail.com (Chris Abela)
Date: Thu, 28 Mar 2019 09:18:03 +0100
Subject: [Slackbuilds-users] vlc patch to build against libssh-21.8.1
Message-ID: <CAJ2_kYpVViN84u_Coe5KUYF9ooRAuwrqno2AvOXQYtsR9CnLeA@mail.gmail.com>

On my 14.2 systems, vlc does not build:

access/sftp.c:319:42: error: 'LIBSSH2_KNOWNHOST_KEY_ECDSA_521' undeclared
(first use in this function)
             knownhost_fingerprint_algo = LIBSSH2_KNOWNHOST_KEY_ECDSA_521;

I found a solution here:
http://www.linuxfromscratch.org/blfs/view/cvs/multimedia/vlc.html

$ cat patch_sftp.diff

--- modules/access/sftp.c.orig    2019-03-28 08:47:06.471817961 +0100
+++ modules/access/sftp.c    2019-03-28 08:48:09.146979881 +0100
@@ -306,7 +306,7 @@
         case LIBSSH2_HOSTKEY_TYPE_DSS:
             knownhost_fingerprint_algo = LIBSSH2_KNOWNHOST_KEY_SSHDSS;
             break;
-#if LIBSSH2_VERSION_NUM >= *0x010801*
+#if LIBSSH2_VERSION_NUM >= *0x010900*
         case LIBSSH2_HOSTKEY_TYPE_ECDSA_256:
             knownhost_fingerprint_algo = LIBSSH2_KNOWNHOST_KEY_ECDSA_256;
             break;

on vlc.SlackBuild
patch -p0 < $CWD/patch-projectM-fontpath.diff
patch -p0 < $CWD/patch_vlc_cache_gen.diff
*patch -p0 < $CWD/patch_sftp.diff*

Now it builds and runs fine here.

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190328/a1e27798/attachment.html>

From kristofru at gmail.com  Thu Mar 28 08:21:00 2019
From: kristofru at gmail.com (Chris Abela)
Date: Thu, 28 Mar 2019 09:21:00 +0100
Subject: [Slackbuilds-users] vlc patch to build against libssh-21.8.1
In-Reply-To: <CAJ2_kYpVViN84u_Coe5KUYF9ooRAuwrqno2AvOXQYtsR9CnLeA@mail.gmail.com>
References: <CAJ2_kYpVViN84u_Coe5KUYF9ooRAuwrqno2AvOXQYtsR9CnLeA@mail.gmail.com>
Message-ID: <CAJ2_kYqcfOwXra_hPscbYf75DXywOmwnGY28L-8Nd64kn1BCqg@mail.gmail.com>

Typo in the title; should read libssh2-1.8.1

On Thu, Mar 28, 2019 at 9:18 AM Chris Abela <kristofru at gmail.com> wrote:

> On my 14.2 systems, vlc does not build:
>
> access/sftp.c:319:42: error: 'LIBSSH2_KNOWNHOST_KEY_ECDSA_521' undeclared
> (first use in this function)
>              knownhost_fingerprint_algo = LIBSSH2_KNOWNHOST_KEY_ECDSA_521;
>
> I found a solution here:
> http://www.linuxfromscratch.org/blfs/view/cvs/multimedia/vlc.html
>
> $ cat patch_sftp.diff
>
> --- modules/access/sftp.c.orig    2019-03-28 08:47:06.471817961 +0100
> +++ modules/access/sftp.c    2019-03-28 08:48:09.146979881 +0100
> @@ -306,7 +306,7 @@
>          case LIBSSH2_HOSTKEY_TYPE_DSS:
>              knownhost_fingerprint_algo = LIBSSH2_KNOWNHOST_KEY_SSHDSS;
>              break;
> -#if LIBSSH2_VERSION_NUM >= *0x010801*
> +#if LIBSSH2_VERSION_NUM >= *0x010900*
>          case LIBSSH2_HOSTKEY_TYPE_ECDSA_256:
>              knownhost_fingerprint_algo = LIBSSH2_KNOWNHOST_KEY_ECDSA_256;
>              break;
>
> on vlc.SlackBuild
> patch -p0 < $CWD/patch-projectM-fontpath.diff
> patch -p0 < $CWD/patch_vlc_cache_gen.diff
> *patch -p0 < $CWD/patch_sftp.diff*
>
> Now it builds and runs fine here.
>
> Chris
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190328/3d776804/attachment.html>

From chris.willing at linux.com  Thu Mar 28 08:42:41 2019
From: chris.willing at linux.com (Christoph Willing)
Date: Thu, 28 Mar 2019 18:42:41 +1000
Subject: [Slackbuilds-users] vlc patch to build against libssh-21.8.1
In-Reply-To: <CAJ2_kYpVViN84u_Coe5KUYF9ooRAuwrqno2AvOXQYtsR9CnLeA@mail.gmail.com>
References: <CAJ2_kYpVViN84u_Coe5KUYF9ooRAuwrqno2AvOXQYtsR9CnLeA@mail.gmail.com>
Message-ID: <96bc3c4e-58ab-176b-c5f9-a5e0e0aeff8d@linux.com>

On 28/3/19 6:18 pm, Chris Abela wrote:
> On my 14.2 systems, vlc does not build:
> 
> access/sftp.c:319:42: error: 'LIBSSH2_KNOWNHOST_KEY_ECDSA_521'
> undeclared (first use in this function)
> ???????????? knownhost_fingerprint_algo = LIBSSH2_KNOWNHOST_KEY_ECDSA_521;
> 

Already patched in the update due at the weekend or see:

https://git.slackbuilds.org/slackbuilds/tree/multimedia/vlc?h=user/chris.willing/updates&id=caf2f1c43bcafa28eae165592e1d427cb8bdca80

chris

From kristofru at gmail.com  Thu Mar 28 09:11:46 2019
From: kristofru at gmail.com (Chris Abela)
Date: Thu, 28 Mar 2019 10:11:46 +0100
Subject: [Slackbuilds-users] vlc patch to build against libssh-21.8.1
In-Reply-To: <96bc3c4e-58ab-176b-c5f9-a5e0e0aeff8d@linux.com>
References: <CAJ2_kYpVViN84u_Coe5KUYF9ooRAuwrqno2AvOXQYtsR9CnLeA@mail.gmail.com>
 <96bc3c4e-58ab-176b-c5f9-a5e0e0aeff8d@linux.com>
Message-ID: <CAJ2_kYoD3XbkdhVioHpMWT6fp928egJc9wKqXOgREtUOBWG1FA@mail.gmail.com>

Thank You.

Next time, I should check the git repo before claiming any bug fix.

Cheers,
Chris

On Thu, Mar 28, 2019 at 9:42 AM Christoph Willing <chris.willing at linux.com>
wrote:

> On 28/3/19 6:18 pm, Chris Abela wrote:
> > On my 14.2 systems, vlc does not build:
> >
> > access/sftp.c:319:42: error: 'LIBSSH2_KNOWNHOST_KEY_ECDSA_521'
> > undeclared (first use in this function)
> >              knownhost_fingerprint_algo =
> LIBSSH2_KNOWNHOST_KEY_ECDSA_521;
> >
>
> Already patched in the update due at the weekend or see:
>
>
> https://git.slackbuilds.org/slackbuilds/tree/multimedia/vlc?h=user/chris.willing/updates&id=caf2f1c43bcafa28eae165592e1d427cb8bdca80
>
> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190328/419b3367/attachment.html>

From willysr at slackbuilds.org  Fri Mar 29 00:49:20 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 29 Mar 2019 07:49:20 +0700
Subject: [Slackbuilds-users] Taking over yajl
In-Reply-To: <201903271837.44880.ricardo@palmtx.com.ar>
References: <201903271837.44880.ricardo@palmtx.com.ar>
Message-ID: <536bb11d-6ed8-0a83-f9b7-7a107f65a62e@slackbuilds.org>

> Sorry for my previous email semi-hijacking the "i3 up for grabs / new 
> maintainer for herbstluftwm" thread, I'm sending it again as a new thread so 
> it doesn't get lost in the noise.
> 
> ----------------------------------------------------------------------------
> 
> Hello list,
> 
> I'm taking over yajl, should I submit a tar.gz through the form [1] or is 
> there another preferred method?
> 
> [1] https://slackbuilds.org/submit/

It's better to use the normal submission form if you want to take over,
but you can do PR/MR for future updates


-- 
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/20190329/f5727c17/attachment-0001.asc>

From ricardo at palmtx.com.ar  Fri Mar 29 19:45:12 2019
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Fri, 29 Mar 2019 16:45:12 -0300
Subject: [Slackbuilds-users] Taking over yajl
In-Reply-To: <536bb11d-6ed8-0a83-f9b7-7a107f65a62e@slackbuilds.org>
References: <201903271837.44880.ricardo@palmtx.com.ar>
 <536bb11d-6ed8-0a83-f9b7-7a107f65a62e@slackbuilds.org>
Message-ID: <201903291645.12590.ricardo@palmtx.com.ar>

El Jueves 28/03/2019 a las 21:49, Willy Sudiarto Raharjo escribi?:
> > Sorry for my previous email semi-hijacking the "i3 up for grabs / new
> > maintainer for herbstluftwm" thread, I'm sending it again as a new thread
> > so it doesn't get lost in the noise.
> >
> > -------------------------------------------------------------------------
> >
> > Hello list,
> >
> > I'm taking over yajl, should I submit a tar.gz through the form [1] or is
> > there another preferred method?
> >
> > [1] https://slackbuilds.org/submit/
>
> It's better to use the normal submission form if you want to take over,
> but you can do PR/MR for future updates

Cool, I sent it through the form.

Cheers!
-- 
Ricardo J. Barberis
Usuario Linux N? 250625: http://counter.li.org/
Usuario LFS N? 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com

From willysr at slackbuilds.org  Sat Mar 30 00:33:07 2019
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 30 Mar 2019 07:33:07 +0700
Subject: [Slackbuilds-users] Updates - 20190330.1
Message-ID: <68a31624-8cbd-8cbb-8643-44b0993f7f31@slackbuilds.org>

Sat Mar 30 00:19:10 UTC 2019
academic/R: Updated for version 3.5.3.
academic/cryptominisat: Updated for version 5.6.8.
desktop/enlightenment: Updated for version 0.22.4.
development/anjuta: Updated for version 3.28.0.
development/hopper: Updated for version 4.5.7.
development/pycharm: Updated for version 2018.3.5.
games/scid_vs_pc: Updated for version 4.20.
gis/geopy: Updated for version 1.19.0.
graphics/Blender: Patch for python3.7
graphics/potrace: Patched for newer versions of ghostscript.
graphics/pqiv: Added (Powerful image viewer).
graphics/shalbum: Added (Image Gallery Creator).
graphics/white_dune: Updated for version 0.99pl1482.
libraries/efl: Updated for version 1.21.1.
libraries/hidapi: Update HOMEPAGE.
libraries/leptonica: Updated for version 1.78.0.
libraries/libetpan: Updated for version 1.9.3.
libraries/libopenshot-audio: Updated for version 0.1.8
libraries/libopenshot: Updated for version 0.2.3
libraries/libu2f-host: Updated for version 1.1.9.
libraries/libxmlb: Updated for version 0.1.8.
libraries/opensaml: Updated for version 3.0.1.
libraries/python-efl: Updated for version 1.21.0.
libraries/xmltooling: Updated for version 3.0.4.
libraries/yajl: New maintainer.
misc/fcitx-mozc: Fix build + download urls.
misc/lastpass-cli: Added (Password Manager).
multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 73.0.
multimedia/vlc: Patch for latest libssh2
network/claws-mail: Updated for version 3.17.3.
network/dropbear: Updated for version 2019.78.
network/inadyn: Added (A Small and Simple DDNS Client).
network/mattermost-desktop: Updated for version 4.2.1
network/purple-telegram: Added (Telegram plugin for libpurple).
network/shibboleth-sp: Updated for version 3.0.4.
network/signal-desktop: Updated for version 1.23.1.
network/sslscan: Updated for version 1.11.13.
network/telegram: Updated for version 1.6.3.
network/tor: Updated for version 0.3.5.8.
network/vivaldi: Updated for version 2.4.1488.35.
office/keepassxc: Updated for version 2.4.0.
office/pandoc-bin: Added (a universal document converter).
python/python-fonttools: Fix python3 support.
python/python-requests: Updated for version 2.21.0.
python/python3-aiohttp-socks: Added (SOCKS proxy connector).
python/python3-ipython: Updated for version 7.4.0.
python/python3-isort: Updated for version 4.3.16.
python/python3-tornado: Updated for version 6.0.2.
python/sphinxcontrib-websupport: Add Python 3 support.
ruby/rbenv: Updated for version 1.1.2.
system/fwupd: Updated for version 1.2.6.
system/keybase: Updated for version 3.1.2.
system/lynis: Updated for version 2.7.3.
system/pspg: Updated for version 1.6.4.
system/qdirstat: Updated for version 1.5.
system/terminology: Updated for version 1.3.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/20190330/c90d8bf6/attachment.asc>