From yalhcru at gmail.com  Fri Feb  2 00:24:04 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 1 Feb 2018 19:24:04 -0500
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <2061442.gaO3zonlXd@titania.liwjatan.org>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
Message-ID: <CAN1hMuBuGszeWaCOmgbjznx-cydBHHXDyDbBVMrhaPU07ccbfQ@mail.gmail.com>

On 1/20/18, Heinz Wiesinger <pprkut at liwjatan.at> wrote:

> audio/fluidsynth

I'll take this one, if it's not already spoken for. I maintain a lot of
games that have it as a required or optional dependency.

From yalhcru at gmail.com  Fri Feb  2 00:32:39 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 1 Feb 2018 19:32:39 -0500
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <CAPsDuS5nKHCC51bH4V7JAU5JBU9knqbWWL20iHibk41y2DHu-g@mail.gmail.com>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
 <CAPsDuS5nKHCC51bH4V7JAU5JBU9knqbWWL20iHibk41y2DHu-g@mail.gmail.com>
Message-ID: <CAN1hMuCf5qvY77RKhNuOeYudm_psTQiB+bq_6j-nF4ELDLZucQ@mail.gmail.com>

On 1/20/18, Matteo Bernardini <matteo.bernardini at gmail.com> wrote:
> 2018-01-20 14:35 GMT+01:00 Heinz Wiesinger <pprkut at liwjatan.at>:
>> audio/ardour
>
> if noone else wants them badly for whatever reason I'll get those as
> most of them are optional dependencies of audacity and I also always
> wanted to play with ardour!

Matteo, I don't want to maintain ardour, but would you accept a patch from
me?

For years I've been seeing error messages from ardour that advise me to
edit PAM-related files that just don't exist on Slackware. If I patch
all these error/warning messages so they make sense for us (tell the
user to edit a file that actually exists, or whatever's required),
would you add that to the build?

Also, at one time, for ardour 3, I had a patch that allowed it to run
with elevated capabilities (using filesystem cap bits), the way JACK
applications are supposed to, without having to wrap it in set_rlimits.

>> audio/jack-audio-connection-kit

I have some ideas for audio/jack-audio-connection-kit also. Are you
dead-set on taking this one, or can I have it? (If you look in the repo,
you'll see I maintain a lot of audio stuff that depends on it...)

From herminio.hernandezjr at gmail.com  Fri Feb  2 04:15:59 2018
From: herminio.hernandezjr at gmail.com (Herminio Hernandez, Jr.)
Date: Thu, 1 Feb 2018 21:15:59 -0700
Subject: [Slackbuilds-users] multibootusb run error
Message-ID: <CAJRA9dyc-nj5Jn1HB96uMw1meHQtFo0pYxMCN_nGx20RBfu+Dw@mail.gmail.com>

I installed multibookusb on my machine running Salix. However when I tried
to launch from the icon nothing happened. When I tried to run from the
terminal I got the following error.

rican-linux[~]$ multibootusb-pkexec
Error executing command as another user: No authentication agent found.
rican-linux[~]$ gksudo multibootusb-pkexec
Running multibootusb version 8.9.0 from installed system...
Starting multibootusb GUI...
Connection: Could not connect to display
/usr/bin/multibootusb-pkexec: line 22: 27376 Aborted                 pkexec
--disable-internal-agent "/usr/bin/multibootusb" "$@"

I have verified that I have the listed dependency installed.

rican-linux[~]$ spi -s pyqt5
Available packages:
PyQt5 [Installed]: PyQt5 (Python bindings for Qt)
python3-PyQt5 [Not installed]: PyQt5 (Python bindings for Qt)

Available SlackBuilds:
None

I tried running via cli below and got the GUI to launch but when I selected
the USB drive it crashed with the following error

root[rican-linux]# python2.7 /usr/bin/multibootusb
Running multibootusb version 8.9.0 from installed system...
Starting multibootusb GUI...
Cleaning old multibootusb directory...
Syslinux exist in multibootusb directory...
Using pyudev for detecting USB drives...
    /dev/sdc
    /dev/sdc1
Selected device /dev/sdc
Device /dev/sdc is a MBR disk...
USB disk is not mounted and can't update list widget...
No USB disk found...
Using pyudev for detecting USB drives...
    /dev/sdc
    /dev/sdc1
Selected device /dev/sdc
Device /dev/sdc is a MBR disk...
USB disk is not mounted and can't update list widget...
Selected device /dev/sdc1
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/scripts/mbusb_gui.py", line 149,
in onComboChange
    config.usb_details = usb.details(config.usb_disk)
  File "/usr/lib64/python2.7/site-packages/scripts/usb.py", line 463, in
details
    details = details_udisks2(usb_disk_part)
  File "/usr/lib64/python2.7/site-packages/scripts/usb.py", line 323, in
details_udisks2
    size_total = shutil.disk_usage(mount_point)[0]
AttributeError: 'module' object has no attribute 'disk_usage'
Aborted


Has anyone ran into this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180201/de8b4485/attachment-0001.html>

From matteo.bernardini at gmail.com  Fri Feb  2 07:59:54 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 2 Feb 2018 08:59:54 +0100
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <CAN1hMuCf5qvY77RKhNuOeYudm_psTQiB+bq_6j-nF4ELDLZucQ@mail.gmail.com>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
 <CAPsDuS5nKHCC51bH4V7JAU5JBU9knqbWWL20iHibk41y2DHu-g@mail.gmail.com>
 <CAN1hMuCf5qvY77RKhNuOeYudm_psTQiB+bq_6j-nF4ELDLZucQ@mail.gmail.com>
Message-ID: <CAPsDuS6KgBov3aJd-siq5fr4pLOH5H48e46TYEh47OexOwPDSQ@mail.gmail.com>

2018-02-02 1:32 GMT+01:00 B Watson <yalhcru at gmail.com>:
> On 1/20/18, Matteo Bernardini <matteo.bernardini at gmail.com> wrote:
>> 2018-01-20 14:35 GMT+01:00 Heinz Wiesinger <pprkut at liwjatan.at>:
>>> audio/ardour
>>
>> if noone else wants them badly for whatever reason I'll get those as
>> most of them are optional dependencies of audacity and I also always
>> wanted to play with ardour!
>
> Matteo, I don't want to maintain ardour, but would you accept a patch from
> me?
>
> For years I've been seeing error messages from ardour that advise me to
> edit PAM-related files that just don't exist on Slackware. If I patch
> all these error/warning messages so they make sense for us (tell the
> user to edit a file that actually exists, or whatever's required),
> would you add that to the build?
>
> Also, at one time, for ardour 3, I had a patch that allowed it to run
> with elevated capabilities (using filesystem cap bits), the way JACK
> applications are supposed to, without having to wrap it in set_rlimits.

np, just send me the patches.

>>> audio/jack-audio-connection-kit
>
> I have some ideas for audio/jack-audio-connection-kit also. Are you
> dead-set on taking this one, or can I have it? (If you look in the repo,
> you'll see I maintain a lot of audio stuff that depends on it...)

np at all for that too, just submit an update in your branch with your
data as MAINTAINER.

Matteo

From matteo.bernardini at gmail.com  Fri Feb  2 09:20:23 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 2 Feb 2018 10:20:23 +0100
Subject: [Slackbuilds-users] multibootusb run error
In-Reply-To: <CAJRA9dyc-nj5Jn1HB96uMw1meHQtFo0pYxMCN_nGx20RBfu+Dw@mail.gmail.com>
References: <CAJRA9dyc-nj5Jn1HB96uMw1meHQtFo0pYxMCN_nGx20RBfu+Dw@mail.gmail.com>
Message-ID: <CAPsDuS6TOwPPsPpoCuwB38wu13aac8Ts8j3_cpgzWcHSU-KaAQ@mail.gmail.com>

2018-02-02 5:15 GMT+01:00 Herminio Hernandez, Jr.
<herminio.hernandezjr at gmail.com>:
> I installed multibookusb on my machine running Salix. However when I tried
> to launch from the icon nothing happened. When I tried to run from the
> terminal I got the following error.
>
> rican-linux[~]$ multibootusb-pkexec
> Error executing command as another user: No authentication agent found.
> rican-linux[~]$ gksudo multibootusb-pkexec
> Running multibootusb version 8.9.0 from installed system...
> Starting multibootusb GUI...
> Connection: Could not connect to display
> /usr/bin/multibootusb-pkexec: line 22: 27376 Aborted                 pkexec
> --disable-internal-agent "/usr/bin/multibootusb" "$@"
>
> I have verified that I have the listed dependency installed.
>
> rican-linux[~]$ spi -s pyqt5
> Available packages:
> PyQt5 [Installed]: PyQt5 (Python bindings for Qt)
> python3-PyQt5 [Not installed]: PyQt5 (Python bindings for Qt)
>
> Available SlackBuilds:
> None
>
> I tried running via cli below and got the GUI to launch but when I selected
> the USB drive it crashed with the following error
>
> root[rican-linux]# python2.7 /usr/bin/multibootusb
> Running multibootusb version 8.9.0 from installed system...
> Starting multibootusb GUI...
> Cleaning old multibootusb directory...
> Syslinux exist in multibootusb directory...
> Using pyudev for detecting USB drives...
>     /dev/sdc
>     /dev/sdc1
> Selected device /dev/sdc
> Device /dev/sdc is a MBR disk...
> USB disk is not mounted and can't update list widget...
> No USB disk found...
> Using pyudev for detecting USB drives...
>     /dev/sdc
>     /dev/sdc1
> Selected device /dev/sdc
> Device /dev/sdc is a MBR disk...
> USB disk is not mounted and can't update list widget...
> Selected device /dev/sdc1
> Traceback (most recent call last):
>   File "/usr/lib64/python2.7/site-packages/scripts/mbusb_gui.py", line 149,
> in onComboChange
>     config.usb_details = usb.details(config.usb_disk)
>   File "/usr/lib64/python2.7/site-packages/scripts/usb.py", line 463, in
> details
>     details = details_udisks2(usb_disk_part)
>   File "/usr/lib64/python2.7/site-packages/scripts/usb.py", line 323, in
> details_udisks2
>     size_total = shutil.disk_usage(mount_point)[0]
> AttributeError: 'module' object has no attribute 'disk_usage'
> Aborted

Hi Herminio,

FYI I've just tried launching it from a slackware full installation
with "kdesu multibootusb" and it launched fine.
I also tried installing ktsuss and launching it with "ktsuss
multibootusb" and it went fine too.

Matteo

From willysr at slackbuilds.org  Sat Feb  3 00:15:17 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Feb 2018 07:15:17 +0700
Subject: [Slackbuilds-users] Updates - 20180203.1
Message-ID: <63a1125c-4d4b-7c59-8897-e0c7e3a4b0d3@slackbuilds.org>

Welcome to February updates

As usual, we have browser-galore updates every week and we also have a
major new release of LibreOffice in form of binary repackaging. The
source-based compilation will follow soon.

There's a plan to bump opencv to latest version (3.4) in the next
following weeks, but some scripts still requires the old opencv (3.1),
so there will be a new opencv-legacy which will be at 3.1 and opencv can
move on to 3.4. AFAIK, digikam/libkface are the one who are still stuck
at 3.1.

Sat Feb  3 00:00:00 UTC 2018
audio/sunvox: Updated for version 1.9.3b.
audio/whipper: Updated for version 0.6.0.
desktop/9menu: Updated for version 1.9.
desktop/cnslock: Added (dock application).
desktop/docfetcher: Fix patch.
desktop/lxde-common: Call makepkg with the full path.
desktop/lxlauncher: Call makepkg with the full path.
desktop/lxmenu-data: Call makepkg with the full path.
desktop/oranchelo-icon-theme: Updated for version 0.7.4.4.
development/4th: Updated for version 3.62.5.
development/SQLAlchemy: Updated for version 1.2.2.
development/astyle: Updated for version 3.1
development/atom-amd64: Updated for version 1.23.3.
development/gcc-d: Updated for version 2.076.0_b3
development/hhvm: Updated for version 3.24.1
development/jupyter-ipykernel: New deps for jupyter-notebook.
development/jupyter-notebook: Updated for version 5.4.0.
development/pycharm: Updated for version 2017.3.3.
development/tig: Updated for version 2.3.3.
games/mame: Updated for version 0.194.
gis/geographiclib-python: Updated for version 1.49.
graphics/feh: Updated for version 2.23.1.
graphics/openimageio: Updated for version 1.8.8
libraries/adns: Added (C library).
libraries/leptonica: Updated for version 1.75.0.
libraries/libaudclient: Switch to https for the homepage.
libraries/libbsd: Updated for version 0.8.7.
libraries/liblxi: Added (support library for LAN eXtensions).
libraries/libupnp: Fix build on 32 bit.
libraries/liburcu: Updated for version 0.10.1.
misc/sigrok-firmware-fx2lafw: Updated for version 0.1.6.
misc/xbanish: Updated for version 1.5.
multimedia/beets: Updated for version 1.4.6.
multimedia/mkvtoolnix: Updated for version 20.0.0.
multimedia/opera-developer-ffmpeg-codecs: Updated for version 65.0.
multimedia/spotify: Remove whitespaces.
multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 64.0.
network/PaleMoon: Updated for version 27.7.2.
network/basilisk: Added (Web browser).
network/brave: Updated for version 0.20.29.
network/dothost: Added (DNS lookup utility).
network/dropbox: Updated for version 42.4.114.
network/geomyidae: Updated for version v0.30.
network/gtorrentviewer: Script cleanup.
network/guacamole-client: Updated for version 0.9.14.
network/guacamole-server: Updated for version 0.9.14.
network/heimdal: Updated for version 7.5.0.
network/lxi-tools: Added LAN eXtensions for Instrumentation).
network/openldap-server: Call makepkg with the full path.
network/opera-developer: Updated for version 52.0.2852.0.
network/palemoon: Updated for version 27.7.2.
network/postfix: Updated for version 3.2.5.
network/prosody-mod-block-strangers: Added (block messages).
network/shorewall-core: Updated for version 5.1.11.2.
network/shorewall6: Updated for version 5.1.11.2.
network/shorewall: Updated for version 5.1.11.2.
network/skypeforlinux: Updated for version 8.14.0.10.
network/sylpheed: Updated for version 3.7.0.
network/vivaldi: Updated for version 1.14.1077.41.
network/waterfox: Updated for version 56.0.4.
network/youtube-dl: Updated for version 2018.01.27.
office/MasterPDFEditor: Updated for version 4.3.82.
office/anorack: Added (Spell checker).
office/libreoffice-helppack: Updated for version 6.0.0.
office/libreoffice-langpack: Updated for version 6.0.0.
office/libreoffice: Updated for version 6.0.0.
office/openoffice.org: Reduce package size.
office/paps: Updated for version 0.7.0.
python/Flask-HTMLmin: Fix DOWNLOAD url.
python/Flask-Mail: Fix DOWNLOAD url.
python/Flask-Principal: Fix DOWNLOAD url.
python/Flask-WTF: Fix DOWNLOAD url.
python/python-mimeparse: Fix DOWNLOAD url.
python/python3-jupyter-ipykernel: New deps for jupyter-notebook.
system/alacritty: Updated for version gitb82622.
system/f3: Updated for version 7.0.
system/forkstat: Updated for version 0.02.02.
system/iucode_tool: Updated for version 2.3.
system/kbfs: Updated for version 1.0.40_20180127033950.
system/laptop-mode-tools: Updated for version 1.72.
system/letsencrypt: Updated for version 0.21.1.
system/lxrandr: Call makepkg with the full path.
system/lxsession: Call makepkg with the full path.
system/lxtask: Call makepkg with the full path.
system/lynis: Updated for version 2.6.1.
system/mailutils: Added (email handling).
system/sboui: Updated for version 1.0.
system/symbola-font-ttf: Updated for version 10.24.
system/vagrant: Updated for version 2.0.2.
system/xdiskusage: Call makepkg with the full path.
+--------------------------+


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

From sombragris at sombragris.org  Sat Feb  3 15:27:07 2018
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Sat, 3 Feb 2018 12:27:07 -0300
Subject: [Slackbuilds-users] Minor problem in Brave browser in update
 20180203.1
Message-ID: <neov9.2572351dbc.20180203122707.516aef74@loli.sombragris.org>

Hi,

I use SBo in -current but I believes this applies to everyone.

The Brave browser cannot be installed with the SlackBuild shipped in
update 20180203.1.

The issue is trivial: looks like upstream changed its tarball filename
from Brave.tar.bz2 (and this is what the SlackBuild expected) to
brave.tar.bz2. The sbopkg tool downloads the tarball, and then promptly
complains that the source is nowhere to be found.

Editing the SlackBuild solves the issue.

Thanks,


Eduardo

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

From chytraeu at sdf.org  Sat Feb  3 16:38:28 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sat, 3 Feb 2018 10:38:28 -0600
Subject: [Slackbuilds-users] Fwd: Re: Minor problem in Brave browser in
 update 20180203.1
In-Reply-To: <e4c0b5cf-14a9-8c6b-f54c-89165b0c0557@sdf.org>
References: <e4c0b5cf-14a9-8c6b-f54c-89165b0c0557@sdf.org>
Message-ID: <79571ed4-78d0-f0cd-0668-08b2ba6ef8c9@sdf.org>




-------- Forwarded Message --------
Subject: Re: [Slackbuilds-users] Minor problem in Brave browser in
update 20180203.1
Date: Sat, 3 Feb 2018 10:37:17 -0600
From: Donald Cooley <chytraeu at sdf.org>
To: Eduardo Sanchez <sombragris at sombragris.org>

On 02/03/2018 09:27 AM, Eduardo Sanchez wrote:
> Hi,
> 
> I use SBo in -current but I believes this applies to everyone.
> 
> The Brave browser cannot be installed with the SlackBuild shipped in
> update 20180203.1.
> 
> The issue is trivial: looks like upstream changed its tarball filename
> from Brave.tar.bz2 (and this is what the SlackBuild expected) to
> brave.tar.bz2. The sbopkg tool downloads the tarball, and then promptly
> complains that the source is nowhere to be found.
> 
> Editing the SlackBuild solves the issue.
> 
> Thanks,
> 
> 
> Eduardo
> 
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

Hi Eduardo. I updated the SlackBuild. Thanks for the report.

Regards,
Donald Cooley

From chytraeu at sdf.org  Sat Feb  3 23:06:33 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sat, 3 Feb 2018 17:06:33 -0600
Subject: [Slackbuilds-users] log4net failure and dbus-sharp epic fail and
 unneeded cryptoki
Message-ID: <eb6e6648-45c2-ca70-c9f0-4d470b5a01e5@sdf.org>

hello,
log4net fails to build with the 2.0.7 and the more recent 2.0.8 releases.

I only care because I have been beating my head against the table for
the better part of the day trying to get dbus-sharp to build.

I opened a bug report last year for dbus-sharp here:
https://github.com/mono/dbus-sharp/issues/64

As smuxi and dbus-sharp-glib at slackbuilds.org are the only packages
that depend on dbus-sharp, I am now trying to build smuxi and see if it
has a hard dependency on it.

I personally would like to remove dbus-sharp and dbus-sharp-glib if they
are no longer needed since ostensibly smuxi is the only package that
needs them.

I have applied a patch from Debian and patches from Fedora 27 to try and
get dbus-sharp to compile but I *still* get the same error as I did last
year.

Also, can cryptoki be removed because truecrypt is dead and cryptoki is
no longer useful?

Regards,
Donald Cooley

From skaendo at excite.com  Sun Feb  4 01:01:59 2018
From: skaendo at excite.com (Ed Ender)
Date: Sat, 03 Feb 2018 20:01:59 -0500
Subject: [Slackbuilds-users] log4net failure and dbus-sharp epic fail
 and unneeded cryptoki
Message-ID: <20180203200159.6927@web005.roc2.bluetie.com>

Hey Donald,

 I had to downgrade mono to 4.8.1.0 in order to get dbus-sharp to build.
I don't know if this is the optimal way to do this but it is what I found to work.

-----Original Message-----
From: "Donald Cooley" [chytraeu at sdf.org]
Date: 02/03/2018 05:06 PM
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: [Slackbuilds-users] log4net failure and dbus-sharp epic fail and
 unneeded cryptoki

hello,
log4net fails to build with the 2.0.7 and the more recent 2.0.8 releases.

I only care because I have been beating my head against the table for
the better part of the day trying to get dbus-sharp to build.

I opened a bug report last year for dbus-sharp here:
https://github.com/mono/dbus-sharp/issues/64

As smuxi and dbus-sharp-glib at slackbuilds.org are the only packages
that depend on dbus-sharp, I am now trying to build smuxi and see if it
has a hard dependency on it.

I personally would like to remove dbus-sharp and dbus-sharp-glib if they
are no longer needed since ostensibly smuxi is the only package that
needs them.

I have applied a patch from Debian and patches from Fedora 27 to try and
get dbus-sharp to compile but I *still* get the same error as I did last
year.

Also, can cryptoki be removed because truecrypt is dead and cryptoki is
no longer useful?

Regards,
Donald Cooley
_______________________________________________
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 yalhcru at gmail.com  Sun Feb  4 01:36:24 2018
From: yalhcru at gmail.com (B Watson)
Date: Sat, 3 Feb 2018 20:36:24 -0500
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <CAPsDuS6KgBov3aJd-siq5fr4pLOH5H48e46TYEh47OexOwPDSQ@mail.gmail.com>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
 <CAPsDuS5nKHCC51bH4V7JAU5JBU9knqbWWL20iHibk41y2DHu-g@mail.gmail.com>
 <CAN1hMuCf5qvY77RKhNuOeYudm_psTQiB+bq_6j-nF4ELDLZucQ@mail.gmail.com>
 <CAPsDuS6KgBov3aJd-siq5fr4pLOH5H48e46TYEh47OexOwPDSQ@mail.gmail.com>
Message-ID: <CAN1hMuAA79YCQ=WD6UCwC+sMEc9eRV+2_Y17mzCQOnBW8p-2rQ@mail.gmail.com>

On 2/2/18, Matteo Bernardini <matteo.bernardini at gmail.com> wrote:

>> Also, at one time, for ardour 3, I had a patch that allowed it to run
>> with elevated capabilities (using filesystem cap bits), the way JACK
>> applications are supposed to, without having to wrap it in set_rlimits.
>
> np, just send me the patches.

Will do, thanks. Might take a while though.

>>>> audio/jack-audio-connection-kit
>
> np at all for that too, just submit an update in your branch with your
> data as MAINTAINER.

Thanks for that. I'm about ready to submit it, but am in the middle
of writing up some README notes on how to get jack to play nicely with
pulseaudio. My own solution (disable pulseaudio completely) isn't really
applicable to general SBo users.

From kingbeowulf at gmail.com  Sun Feb  4 03:34:31 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 3 Feb 2018 19:34:31 -0800
Subject: [Slackbuilds-users] Kodi and ffmpeg
Message-ID: <835db362-1ac1-d1fa-6253-f20bc16c638e@gmail.com>

The kodi Slackbuild states:

# The version of ffmpeg on SBo is too old to compile kodi

and provides ffmpeg-3.1.11 however SBo provides ffmpeg-3.2.4

-Ed

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

From bmg.andre at gmail.com  Sun Feb  4 14:25:22 2018
From: bmg.andre at gmail.com (=?UTF-8?Q?Andr=C3=A9_Barboza?=)
Date: Sun, 4 Feb 2018 12:25:22 -0200
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
Message-ID: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>

Hi guys,

Unfortunately I cannot maintain my SlackBuilds anymore.
So, here is the list. Please take care of them.

academic/abntex
audio/opencore-amr
development/boost-di
development/Catch
development/cim
development/conan
development/fpc
development/g3log
development/gplcver
development/lazarus
development/libcutl
development/libodb
development/libodb-boost
development/libodb-mysql
development/libodb-pgsql
development/libodb-qt
development/libodb-sqlite
development/libxbgi
development/mono
development/mono-addins
development/mono-debugger
development/monodevelop
development/mstch
development/netbeans
development/nuget
development/odb
development/qt-creator
development/qt-creator2
development/reckless
development/referenceassemblies-pcl
development/sauce
development/scala
development/spdlog
development/vscode
development/xsp
graphics/uniconvertor
libraries/asio
libraries/capnproto
libraries/cpp-netlib
libraries/cpprestsdk
libraries/dlib
libraries/double-conversion
libraries/flatbuffers
libraries/folly
libraries/gflags
libraries/glog
libraries/gnome-sharp
libraries/google-fruit
libraries/gperftools
libraries/hinnant-date
libraries/hpx
libraries/Hypodermic
libraries/kashmir
libraries/libgdiplus
libraries/libgraphqlparser
libraries/libr3
libraries/proxygen
libraries/rapidjson
libraries/restbed
libraries/rocksdb
libraries/RxCpp
libraries/sqlpp11
libraries/sqlpp11-connector-mysql
libraries/sqlpp11-connector-sqlite3
libraries/upscaledb
libraries/wangle
multimedia/gaupol
multimedia/subtitleripper
network/knemo
python/cfgparse
python/fasteners
python/monotonic
python/node-semver
python/pluginbase
python/pyjwt
python/python-patch
python/sk1libs
system/displaylink
system/evdi
system/evdi-kernel
system/fxload
system/jmtpfs
system/kafka
system/rabbitmq-server
system/zookeeper

Thanks to all admins for helping me all these years.
A special thanks to Willy Sudiarto Raharjo and Robby Workman.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180204/fcbcc049/attachment.html>

From dstein614 at gmail.com  Sun Feb  4 14:54:06 2018
From: dstein614 at gmail.com (Daniel Stein)
Date: Sun, 4 Feb 2018 09:54:06 -0500
Subject: [Slackbuilds-users] Kodi and ffmpeg
In-Reply-To: <835db362-1ac1-d1fa-6253-f20bc16c638e@gmail.com>
References: <835db362-1ac1-d1fa-6253-f20bc16c638e@gmail.com>
Message-ID: <CABrRyLn0TT0YLJ+F5ees0SfrB-8R-kJi+6b=ntkO3XS_zG6q+Q@mail.gmail.com>

Doesn't the Kodi build use it's own ffmpeg for the build?

On Feb 3, 2018 10:34 PM, "King Beowulf" <kingbeowulf at gmail.com> wrote:

> The kodi Slackbuild states:
>
> # The version of ffmpeg on SBo is too old to compile kodi
>
> and provides ffmpeg-3.1.11 however SBo provides ffmpeg-3.2.4
>
> -Ed
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180204/d72c3f2c/attachment.html>

From atelszewski at gmail.com  Sun Feb  4 15:11:28 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 4 Feb 2018 16:11:28 +0100
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>
References: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>
Message-ID: <c63bbb1d-ca71-1050-1272-03865d4bd087@gmail.com>

On 04/02/18 15:25, Andr? Barboza wrote:
> Hi guys,
> 
> Unfortunately I cannot maintain my SlackBuilds anymore.
> So, here is the list. Please take care of them.
> 

I'll take those:

> development/qt-creator
> development/qt-creator2

> 
> Thanks to all admins for helping me all these years.
> A special thanks to Willy Sudiarto Raharjo and Robby Workman.
> 

Thank you Andr? for maintaning all of those.
Communicating with you has always been a pleasure.

-- 
Best regards,
Andrzej Telszewski

From andreas.guldstrand at gmail.com  Sun Feb  4 16:01:10 2018
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Sun, 4 Feb 2018 17:01:10 +0100
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <c63bbb1d-ca71-1050-1272-03865d4bd087@gmail.com>
References: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>
 <c63bbb1d-ca71-1050-1272-03865d4bd087@gmail.com>
Message-ID: <CAEQ5t82ht34DCKd+fZ8K2Qf3F2DkWzfFAmVB0HehMVxx-zh1WQ@mail.gmail.com>

I'll take

> development/vscode

Thanks for all your contributions

From fernando.lopezjr at gmail.com  Sun Feb  4 17:44:17 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sun, 4 Feb 2018 10:44:17 -0700
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <CAEQ5t82ht34DCKd+fZ8K2Qf3F2DkWzfFAmVB0HehMVxx-zh1WQ@mail.gmail.com>
References: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>
 <c63bbb1d-ca71-1050-1272-03865d4bd087@gmail.com>
 <CAEQ5t82ht34DCKd+fZ8K2Qf3F2DkWzfFAmVB0HehMVxx-zh1WQ@mail.gmail.com>
Message-ID: <CALrQ46BvroENyo1fpk=pv20fgk3t_uFNJc6-rwEJx+U_hhoo4Q@mail.gmail.com>

ill take:

development/lazarus


On Sun, Feb 4, 2018 at 9:01 AM, Andreas Guldstrand <
andreas.guldstrand at gmail.com> wrote:

> I'll take
>
> > development/vscode
>
> Thanks for all your contributions
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 

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

From rworkman at slackbuilds.org  Sun Feb  4 17:51:07 2018
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 4 Feb 2018 11:51:07 -0600
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>
References: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>
Message-ID: <20180204115107.1056aa77@home.rlworkman.net>

On Sun, 4 Feb 2018 12:25:22 -0200
Andr? Barboza <bmg.andre at gmail.com> wrote:

> Unfortunately I cannot maintain my SlackBuilds anymore.


Sorry to hear that, but alas, time marches on...


> Thanks to all admins for helping me all these years.
> A special thanks to Willy Sudiarto Raharjo and Robby Workman.


So long, and thanks for all the fish :-) 

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

From harald.achitz at gmail.com  Sun Feb  4 18:23:01 2018
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sun, 4 Feb 2018 19:23:01 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAN1hMuATYrBfk1RqM9BU1Q1EQAiNEb5ZRXDSL1AUGtuU63qmqg@mail.gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
 <CAN1hMuATYrBfk1RqM9BU1Q1EQAiNEb5ZRXDSL1AUGtuU63qmqg@mail.gmail.com>
Message-ID: <CAPh+tzPfAwmoB36Sv_V15weQtNdTdgPzV14bRdcXg0RpJ+EzUg@mail.gmail.com>

just seen that the layout improved over the first versions.
great work, thanks !
/Harald

2018-01-25 23:48 GMT+01:00 B Watson <yalhcru at gmail.com>:

> On 1/25/18, Didier Spaier <didier at slint.fr> wrote:
> >
> > So, short of finding a volunteer to review 6918 READMEs one by one
> > (anyone?), I suggest that maintainers edit manually their READMEs if
> > they want, on the occasion of an update for instance.
>
> Edit them how?
>
> Getting rid of line breaks, so a paragraph is on one line, might fix the
> wrapping issue on the website, but the README isn't exclusively used by
> the site (if it were, we could just decree that it has to be written in
> HTML instead of plain text). Extra-long lines would probably cause problems
> with tools like sbopkg and sbotools.
>
> It would also at least be annoying for anyone running SlackBuilds
> manually: I usually use "cat README", and it comes out nicely
> word-wrapped, with whatever list/etc formatting the author used looking
> like it's supposed to look.
> _______________________________________________
> 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/20180204/93899cf3/attachment.html>

From chytraeu at sdf.org  Mon Feb  5 03:12:27 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sun, 4 Feb 2018 21:12:27 -0600
Subject: [Slackbuilds-users] Call for testing for hiawatha-10.7
Message-ID: <ec9b94fc-ab43-1b15-ea71-ed3b6457cbe1@sdf.org>

Hello,
I've taken over as maintainer for the Web server Hiawatha. I've done
some light testing of it and if others could also test it it would be great.

I've made a couple of changes. I've changed the install from /usr to
/usr/sbin as that seemed more appropriate. Also, I've changed the
server's directory from /srv/hiawatha to /var/hiawatha.

It has letsencrypt integration but I haven't tested that yet.

Constructive feedback is what I'm after.

Regards,
Donald Cooley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hiawatha.tar.gz
Type: application/gzip
Size: 4239 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180204/30594ef6/attachment.bin>

From korgie at gmail.com  Mon Feb  5 06:07:31 2018
From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=)
Date: Mon, 5 Feb 2018 08:07:31 +0200
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAPh+tzPfAwmoB36Sv_V15weQtNdTdgPzV14bRdcXg0RpJ+EzUg@mail.gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
 <CAN1hMuATYrBfk1RqM9BU1Q1EQAiNEb5ZRXDSL1AUGtuU63qmqg@mail.gmail.com>
 <CAPh+tzPfAwmoB36Sv_V15weQtNdTdgPzV14bRdcXg0RpJ+EzUg@mail.gmail.com>
Message-ID: <53D6BA50-470A-4824-B89E-4C21C09F665A@gmail.com>

I had *terrified* with some comments here so I was skeptical before visiting.

_I like the new site._ It's better for me.

Thank you guys.

From lists at osh.id.au  Mon Feb  5 07:02:13 2018
From: lists at osh.id.au (David O'Shaughnessy)
Date: Mon, 5 Feb 2018 17:02:13 +1000
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <53D6BA50-470A-4824-B89E-4C21C09F665A@gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
 <CAN1hMuATYrBfk1RqM9BU1Q1EQAiNEb5ZRXDSL1AUGtuU63qmqg@mail.gmail.com>
 <CAPh+tzPfAwmoB36Sv_V15weQtNdTdgPzV14bRdcXg0RpJ+EzUg@mail.gmail.com>
 <53D6BA50-470A-4824-B89E-4C21C09F665A@gmail.com>
Message-ID: <e8c6867d-0de0-65b2-1b69-e71480ee8171@osh.id.au>

On 02/05/2018 04:07 PM, ??????? ?????????? wrote:
> I had *terrified* with some comments here so I was skeptical before visiting.
> 
> _I like the new site._ It's better for me.
> 
> Thank you guys.

I'm happy with it too, looks like a worthwhile update to me.

--
Dave

From xavier at maillard.im  Mon Feb  5 12:44:38 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Mon, 05 Feb 2018 13:44:38 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <e8c6867d-0de0-65b2-1b69-e71480ee8171@osh.id.au>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
 <CAN1hMuATYrBfk1RqM9BU1Q1EQAiNEb5ZRXDSL1AUGtuU63qmqg@mail.gmail.com>
 <CAPh+tzPfAwmoB36Sv_V15weQtNdTdgPzV14bRdcXg0RpJ+EzUg@mail.gmail.com>
 <53D6BA50-470A-4824-B89E-4C21C09F665A@gmail.com>
 <e8c6867d-0de0-65b2-1b69-e71480ee8171@osh.id.au>
Message-ID: <87zi4nr4g9.fsf@smugg>


David O'Shaughnessy <lists at osh.id.au> writes:

> On 02/05/2018 04:07 PM, ??????? ?????????? wrote:
>> I had *terrified* with some comments here so I was skeptical 
>> before visiting.
>>
>> _I like the new site._ It's better for me.
>>
>> Thank you guys.
>
> I'm happy with it too, looks like a worthwhile update to me.

I have absolutely no opinion on this given the fact I rarely visit 
it and even less using any "modern GUI" tool.

Keep up the good SBo work !

--
Xavier

From xavier at maillard.im  Tue Feb  6 05:50:08 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Tue, 06 Feb 2018 06:50:08 +0100
Subject: [Slackbuilds-users] SlackBuild script for grab from Ryan
In-Reply-To: <3073d57b-c24f-c392-7855-51469d4a3ea6@slackbuilds.org>
References: <3073d57b-c24f-c392-7855-51469d4a3ea6@slackbuilds.org>
Message-ID: <87bmh2u0of.fsf@smugg>


Willy Sudiarto Raharjo <willysr at slackbuilds.org> writes:

> development/leiningen

If still applicable, I am willing to take this one.

I just have to review the maintainership guide.

Is it ok ?

Regards
--
Xavier

From xavier at maillard.im  Tue Feb  6 18:13:35 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Tue, 06 Feb 2018 19:13:35 +0100
Subject: [Slackbuilds-users] Can't build spotify
In-Reply-To: <e04254f7-b459-9d19-7c6a-33713a678df3@slackbuilds.org>
References: <871sik1cru.fsf@smugg>
 <e04254f7-b459-9d19-7c6a-33713a678df3@slackbuilds.org>
Message-ID: <87a7wm7zqo.fsf@smugg>

Hey Willy,

Willy Sudiarto Raharjo <willysr at slackbuilds.org> writes:

>> I just want to tell that spotify-client can't be built with 
>> current SBo
>> repo. The download link is either obsolete or false (it is 
>> getting a 404
>> error when tryin to get the .deb file).
>
> try here
> http://slackware.uk/sbosrcarch/by-name/multimedia/spotify/
>
> Spotify upstream has a bad habit of deleting the old sources 
> when they
> release a new one and only keep 1 version behind

I did not thank you for your answer: done now :)

Sadly, spotify refuses to work on my poor old eeepc. I am so 
sad. At least, the SBo script is now perfectly working.


Regards
--
Xavier

From khronosschoty at posteo.org  Wed Feb  7 02:03:55 2018
From: khronosschoty at posteo.org (Vasily Sora)
Date: Tue, 6 Feb 2018 18:03:55 -0800
Subject: [Slackbuilds-users] basilisk.SlackBuild
In-Reply-To: <mailman.3658.1517810885.21966.slackbuilds-users@slackbuilds.org>
References: <mailman.3658.1517810885.21966.slackbuilds-users@slackbuilds.org>
Message-ID: <20180207020355.GA14726@darkstar.localhost>

Hi

I was wondering if basilisk.SlackBuild could be renamed to
basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source
for some time now. I just have not submitted it to SBo but I plan to
very shortly and think it would be better this way. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180206/32b4a449/attachment.asc>

From willysr at slackbuilds.org  Wed Feb  7 02:05:32 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 7 Feb 2018 09:05:32 +0700
Subject: [Slackbuilds-users] basilisk.SlackBuild
In-Reply-To: <20180207020355.GA14726@darkstar.localhost>
References: <mailman.3658.1517810885.21966.slackbuilds-users@slackbuilds.org>
 <20180207020355.GA14726@darkstar.localhost>
Message-ID: <16163ada-ba76-fdc4-38e5-400876366a25@slackbuilds.org>

> I was wondering if basilisk.SlackBuild could be renamed to
> basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source
> for some time now. I just have not submitted it to SBo but I plan to
> very shortly and think it would be better this way. 

there's no need to rename the SlackBuild, just add a note in the README
that it uses binary repackaging instead of compiling from source.


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

From skaendo at excite.com  Wed Feb  7 03:32:58 2018
From: skaendo at excite.com (Ed Ender)
Date: Tue, 06 Feb 2018 22:32:58 -0500
Subject: [Slackbuilds-users] basilisk.SlackBuild
Message-ID: <20180206223258.15821@web005.roc2.bluetie.com>

Or you can do like what was done with the Pale Moon SlackBuilds, the repackage one is smallcase, and the compile one is capitalized. 

-----Original Message-----
From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org]
Date: 02/06/2018 08:08 PM
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] basilisk.SlackBuild

> I was wondering if basilisk.SlackBuild could be renamed to
> basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source
> for some time now. I just have not submitted it to SBo but I plan to
> very shortly and think it would be better this way. 

there's no need to rename the SlackBuild, just add a note in the README
that it uses binary repackaging instead of compiling from source.


-- 
Willy Sudiarto Raharjo




From chris.willing at iinet.net.au  Wed Feb  7 03:45:27 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Wed, 7 Feb 2018 13:45:27 +1000
Subject: [Slackbuilds-users] basilisk.SlackBuild
In-Reply-To: <20180206223258.15821@web005.roc2.bluetie.com>
References: <20180206223258.15821@web005.roc2.bluetie.com>
Message-ID: <2fd8d8b2-0bc4-3329-50f2-7ac569dc52db@iinet.net.au>

On 07/02/18 13:32, Ed Ender wrote:
> Or you can do like what was done with the Pale Moon SlackBuilds, the repackage one is smallcase, and the compile one is capitalized. 

Other examples of this method are:
	libreoffice & LibreOffice
	blender & Blender

where the all lower case SlackBuilds are repackings of binaries and
capitalised versions are "build from source".

Of course it really only makes sense to do that if both types of package
are going to be kept in the repo. Otherwise, as Willy says, there's no
real need to rename.

chris


> -----Original Message-----
> From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org]
> Date: 02/06/2018 08:08 PM
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] basilisk.SlackBuild
> 
>> I was wondering if basilisk.SlackBuild could be renamed to
>> basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source
>> for some time now. I just have not submitted it to SBo but I plan to
>> very shortly and think it would be better this way. 
> 
> there's no need to rename the SlackBuild, just add a note in the README
> that it uses binary repackaging instead of compiling from source.
> 
> 


From xavier at maillard.im  Wed Feb  7 13:56:54 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Wed, 07 Feb 2018 14:56:54 +0100
Subject: [Slackbuilds-users] package submission
Message-ID: <87o9l0aont.fsf@smugg>

Hello,

what's the prefered way to share/distribute a new slackbuild to 
the SBo project ?
Should I use the git method (pull request) or the webform ?

Regards
--
Xavier

From willysr at slackbuilds.org  Wed Feb  7 13:29:48 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 7 Feb 2018 20:29:48 +0700
Subject: [Slackbuilds-users] package submission
In-Reply-To: <87o9l0aont.fsf@smugg>
References: <87o9l0aont.fsf@smugg>
Message-ID: <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>

> what's the prefered way to share/distribute a new slackbuild to the SBo
> project ?
> Should I use the git method (pull request) or the webform ?

Use the submission form


-- 
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/20180207/50a70001/attachment-0001.asc>

From xavier at maillard.im  Wed Feb  7 14:58:24 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Wed, 07 Feb 2018 15:58:24 +0100
Subject: [Slackbuilds-users] package submission
In-Reply-To: <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>
Message-ID: <87eflwaltb.fsf@smugg>


Willy Sudiarto Raharjo <willysr at slackbuilds.org> writes:

>> what's the prefered way to share/distribute a new slackbuild to 
>> the SBo
>> project ?
>> Should I use the git method (pull request) or the webform ?
>
> Use the submission form

Ok.

Just to satisfy my curiosity, is the SBo git repo open to external 
contributors ?

Regards
--
Xavier

From yth at ythogtha.org  Wed Feb  7 14:34:14 2018
From: yth at ythogtha.org (Ythogtha)
Date: Wed, 7 Feb 2018 15:34:14 +0100
Subject: [Slackbuilds-users] package submission
In-Reply-To: <87eflwaltb.fsf@smugg>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>
 <87eflwaltb.fsf@smugg>
Message-ID: <20180207153414.ee3b592135ea69f5e158b6dd@ythogtha.org>

> Just to satisfy my curiosity, is the SBo git repo open to external 
> contributors ?

Only When Thou Hast Been Deemed Worthy, petit scarab?e !

-- 
Arnaud <yth at ythogtha.org>

From xavier at maillard.im  Wed Feb  7 15:09:51 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Wed, 07 Feb 2018 16:09:51 +0100
Subject: [Slackbuilds-users] package submission
In-Reply-To: <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>
Message-ID: <87d11gala8.fsf@smugg>


Willy Sudiarto Raharjo <willysr at slackbuilds.org> writes:

>> what's the prefered way to share/distribute a new slackbuild to 
>> the SBo
>> project ?
>> Should I use the git method (pull request) or the webform ?
>
> Use the submission form

While at it, do I have to submit the .asc file accompanying each 
SBo tarball ?

Regards
--
Xavier

From willysr at slackbuilds.org  Wed Feb  7 14:44:55 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 7 Feb 2018 21:44:55 +0700
Subject: [Slackbuilds-users] package submission
In-Reply-To: <87d11gala8.fsf@smugg>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org> <87d11gala8.fsf@smugg>
Message-ID: <c09a3b00-edbc-dc1d-1442-a5f08376dc8d@slackbuilds.org>

> While at it, do I have to submit the .asc file accompanying each SBo
> tarball ?

No, it will be generated during public update


-- 
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/20180207/711c0ef5/attachment.asc>

From xavier at maillard.im  Wed Feb  7 15:21:30 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Wed, 07 Feb 2018 16:21:30 +0100
Subject: [Slackbuilds-users] package submission
In-Reply-To: <20180207153414.ee3b592135ea69f5e158b6dd@ythogtha.org>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org> <87eflwaltb.fsf@smugg>
 <20180207153414.ee3b592135ea69f5e158b6dd@ythogtha.org>
Message-ID: <87bmh0akqt.fsf@smugg>


Ythogtha <yth at ythogtha.org> writes:

>> Just to satisfy my curiosity, is the SBo git repo open to 
>> external
>> contributors ?
>
> Only When Thou Hast Been Deemed Worthy, petit scarab?e !

:)

So it useless to clone the git repo and work with it to update any 
SBo (for later submission), right ?
I'd better get the packages I want to contribute (or take over 
maintainership if applicable) than cloning the full repo 
presumably.

Cheers
--
Xavier

From yth at ythogtha.org  Wed Feb  7 15:04:35 2018
From: yth at ythogtha.org (Ythogtha)
Date: Wed, 7 Feb 2018 16:04:35 +0100
Subject: [Slackbuilds-users] package submission
In-Reply-To: <87bmh0akqt.fsf@smugg>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>
 <87eflwaltb.fsf@smugg>
 <20180207153414.ee3b592135ea69f5e158b6dd@ythogtha.org>
 <87bmh0akqt.fsf@smugg>
Message-ID: <20180207160435.2dfe7b021cfc02cda94e4f9d@ythogtha.org>

> >> Just to satisfy my curiosity, is the SBo git repo open to 
> >> external
> >> contributors ?
> >
> > Only When Thou Hast Been Deemed Worthy, petit scarab?e !
> 
> :)
> 
> So it useless to clone the git repo and work with it to update any 
> SBo (for later submission), right ?
> I'd better get the packages I want to contribute (or take over 
> maintainership if applicable) than cloning the full repo 
> presumably.

Well, I do clone the repo, mostly for the purpose of using it, and building
packages for my own use.
	But I use a set of homemade scripts (which I'm trying to clean and make
available for everybody) to help me with submissions, looking up differences
between my own slackbuilds and the commited ones, mostly to make sure of what I
have been doing while tweaking the code before submitting.
	And to make sure my auto-build tool uses my version instead of the SBo
one.

	I guess everyone has its own workflow, you could also work on a local
branch to keep track of your work.
	The workflow would have been easier with mercurial instead of git,
because git disallow uncommited local changes before pulling changes, you have
to stash or do dark magic stuffs, while mercurial would merge, let you know if
there seems to be a conflict, and keep track of everything elegangtly, without
you having to commit anything, all while being up-to-date with upstream.


-- 
Arnaud <yth at ythogtha.org>

From khronosschoty at posteo.org  Wed Feb  7 16:53:43 2018
From: khronosschoty at posteo.org (Vasily Sora)
Date: Wed, 7 Feb 2018 08:53:43 -0800
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 142, Issue 5
In-Reply-To: <mailman.3712.1518010217.21966.slackbuilds-users@slackbuilds.org>
References: <mailman.3712.1518010217.21966.slackbuilds-users@slackbuilds.org>
Message-ID: <20180207165343.GC24984@darkstar.localhost>

I was really hoping I would not have to have my SlackBuild be named with
the capital letter this time but w/e ;p  moreover I think its confusing. 


> Message: 6
> Date: Wed, 7 Feb 2018 09:05:32 +0700
> From: Willy Sudiarto Raharjo <willysr at slackbuilds.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] basilisk.SlackBuild
> Message-ID: <16163ada-ba76-fdc4-38e5-400876366a25 at slackbuilds.org>
> Content-Type: text/plain; charset="windows-1252"
> 
> > I was wondering if basilisk.SlackBuild could be renamed to
> > basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source
> > for some time now. I just have not submitted it to SBo but I plan to
> > very shortly and think it would be better this way. 
> 
> there's no need to rename the SlackBuild, just add a note in the README
> that it uses binary repackaging instead of compiling from source.
> 
> 
> -- 
> 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/20180207/d6cb642d/attachment-0001.asc>
> 
> ------------------------------
> 
> Message: 7
> Date: Tue, 06 Feb 2018 22:32:58 -0500
> From: "Ed Ender" <skaendo at excite.com>
> To: "SlackBuilds.org Users List"<slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] basilisk.SlackBuild
> Message-ID: <20180206223258.15821 at web005.roc2.bluetie.com>
> Content-Type: text/plain; charset=UTF-8
> 
> Or you can do like what was done with the Pale Moon SlackBuilds, the repackage one is smallcase, and the compile one is capitalized. 
> 
> -----Original Message-----
> From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org]
> Date: 02/06/2018 08:08 PM
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] basilisk.SlackBuild
> 
> > I was wondering if basilisk.SlackBuild could be renamed to
> > basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source
> > for some time now. I just have not submitted it to SBo but I plan to
> > very shortly and think it would be better this way. 
> 
> there's no need to rename the SlackBuild, just add a note in the README
> that it uses binary repackaging instead of compiling from source.
> 
> 
> -- 
> Willy Sudiarto Raharjo
> 
> 
> 
> 
> 
> ------------------------------
> > -----Original Message-----
> > From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org]
> > Date: 02/06/2018 08:08 PM
> > To: slackbuilds-users at slackbuilds.org
> > Subject: Re: [Slackbuilds-users] basilisk.SlackBuild
> > 
> >> I was wondering if basilisk.SlackBuild could be renamed to
> >> basilisk-bin.SlackBuild. I've had a SlackBuild to build this from source
> >> for some time now. I just have not submitted it to SBo but I plan to
> >> very shortly and think it would be better this way. 
> > 
> > there's no need to rename the SlackBuild, just add a note in the README
> > that it uses binary repackaging instead of compiling from source.
> > 
> > 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180207/0039cb92/attachment.asc>

From n0nb at n0nb.us  Wed Feb  7 18:00:31 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Wed, 7 Feb 2018 12:00:31 -0600
Subject: [Slackbuilds-users] package submission
In-Reply-To: <87bmh0akqt.fsf@smugg>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>
 <87eflwaltb.fsf@smugg>
 <20180207153414.ee3b592135ea69f5e158b6dd@ythogtha.org>
 <87bmh0akqt.fsf@smugg>
Message-ID: <20180207180031.GU32488@n0nb.us>

* On 2018 07 Feb 08:55 -0600, Xavier Maillard wrote:
> So it useless to clone the git repo and work with it to update any SBo (for
> later submission), right ?

I have forked the GitHub repo:

https://github.com/SlackBuildsOrg/slackbuilds

and pushed my updates to existing SlackBuilds to a branch in my own
forked repository.  Willy has picked them up after I sent a pull request
and merged them into his repository.

Willy had posted some instructions for doing this workflow last year.
They should be in the list archives.

- Nate

-- 

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

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180207/343b5a9e/attachment.asc>

From erik at slackbuilds.org  Wed Feb  7 18:08:46 2018
From: erik at slackbuilds.org (Erik Hanson)
Date: Wed, 7 Feb 2018 12:08:46 -0600
Subject: [Slackbuilds-users] package submission
In-Reply-To: <87eflwaltb.fsf@smugg>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org> <87eflwaltb.fsf@smugg>
Message-ID: <49a973db-b517-db48-abf3-81b1bb4db0a7@slackbuilds.org>

On 02/07/2018 08:58 AM, Xavier Maillard wrote:
> 
> Willy Sudiarto Raharjo <willysr at slackbuilds.org> writes:
> 
>>> what's the prefered way to share/distribute a new slackbuild to the SBo
>>> project ?
>>> Should I use the git method (pull request) or the webform ?
>>
>> Use the submission form
> 
> Ok.
> 
> Just to satisfy my curiosity, is the SBo git repo open to external
> contributors ?

Yes, access can be given to long-time maintainers to ease submitting
updates, but not for new submissions. Those need to go through the
submission form.


-- 
Erik

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

From jebrhansen+SBo at gmail.com  Wed Feb  7 19:51:14 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Wed, 07 Feb 2018 19:51:14 +0000
Subject: [Slackbuilds-users] package submission
In-Reply-To: <87bmh0akqt.fsf@smugg>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org>
 <87eflwaltb.fsf@smugg> <20180207153414.ee3b592135ea69f5e158b6dd@ythogtha.org>
 <87bmh0akqt.fsf@smugg>
Message-ID: <CANi9qSvWp05uvpbZ6qFykNMsG3qL0GfY8EZSL-37q3WraNHrnQ@mail.gmail.com>

On Wed, Feb 7, 2018, 8:54 AM Xavier Maillard <xavier at maillard.im> wrote:

>
> Ythogtha <yth at ythogtha.org> writes:
>
> >> Just to satisfy my curiosity, is the SBo git repo open to
> >> external
> >> contributors ?
> >
> > Only When Thou Hast Been Deemed Worthy, petit scarab?e !
>
> :)
>
> So it useless to clone the git repo and work with it to update any
> SBo (for later submission), right ?
> I'd better get the packages I want to contribute (or take over
> maintainership if applicable) than cloning the full repo
> presumably.
>
> Cheers
> --
> Xavier
>

It should also be mentioned that if you want to make changes to a
SlackBuild that someone else maintains, you'd submit the change to that
person. They are the maintainer and they have the right to accept your
changes and incorporate them into their script.

Jeremy

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

From fernando.lopezjr at gmail.com  Wed Feb  7 21:37:03 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 7 Feb 2018 14:37:03 -0700
Subject: [Slackbuilds-users] article about slackware.
Message-ID: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>

https://hackaday.com/2018/01/30/making-the-case-for-slackware-in-2018/

-- 

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

From herminio.hernandezjr at gmail.com  Thu Feb  8 03:37:25 2018
From: herminio.hernandezjr at gmail.com (Herminio Hernandez Jr. )
Date: Wed, 7 Feb 2018 22:37:25 -0500
Subject: [Slackbuilds-users] article about slackware.
In-Reply-To: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
References: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
Message-ID: <C0165A5E-158F-44E9-B49A-96B84B985102@gmail.com>

I shared this on IRC. Great read. 

Sent from my iPhone

> On Feb 7, 2018, at 4:37 PM, Fernando Lopez <fernando.lopezjr at gmail.com> wrote:
> 
> https://hackaday.com/2018/01/30/making-the-case-for-slackware-in-2018/
> 
> -- 
> 
> ------------
> Regards,
>     Fernando Lopez Jr.
> _______________________________________________
> 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/20180207/0c90021e/attachment.html>

From kingbeowulf at gmail.com  Thu Feb  8 06:41:03 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Wed, 7 Feb 2018 22:41:03 -0800
Subject: [Slackbuilds-users] Kodi and ffmpeg
In-Reply-To: <CABrRyLn0TT0YLJ+F5ees0SfrB-8R-kJi+6b=ntkO3XS_zG6q+Q@mail.gmail.com>
References: <835db362-1ac1-d1fa-6253-f20bc16c638e@gmail.com>
 <CABrRyLn0TT0YLJ+F5ees0SfrB-8R-kJi+6b=ntkO3XS_zG6q+Q@mail.gmail.com>
Message-ID: <b7044ff8-ad74-8da3-8d09-6899815d7015@gmail.com>

On 02/04/2018 06:54 AM, Daniel Stein wrote:
> Doesn't the Kodi build use it's own ffmpeg for the build?
> 
> On Feb 3, 2018 10:34 PM, "King Beowulf" <kingbeowulf at gmail.com
> <mailto:kingbeowulf at gmail.com>> wrote:
> 
>     The kodi Slackbuild states:
> 
>     # The version of ffmpeg on SBo is too old to compile kodi
> 
>     and provides ffmpeg-3.1.11 however SBo provides ffmpeg-3.2.4
> 
>     -Ed
> 

Maybe I was too terse: the version of ffmpeg supported by the kodi
script maintainer is older than the one provided by the script to
compile kodi.  The comment in the build script is now misleading.  It is
NOT that SBo ffmpeg is too old, rather that kodi devs REQUIRE a
ffmpeg-3.1.x as they have patched it for kodi "krypton"

Whether ffmpeg upstream is aware of these patches, I'm too tired to
research...

-Ed



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

From xavier at maillard.im  Thu Feb  8 07:34:52 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Thu, 08 Feb 2018 08:34:52 +0100
Subject: [Slackbuilds-users] package submission
In-Reply-To: <CANi9qSvWp05uvpbZ6qFykNMsG3qL0GfY8EZSL-37q3WraNHrnQ@mail.gmail.com>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org> <87eflwaltb.fsf@smugg>
 <20180207153414.ee3b592135ea69f5e158b6dd@ythogtha.org> <87bmh0akqt.fsf@smugg>
 <CANi9qSvWp05uvpbZ6qFykNMsG3qL0GfY8EZSL-37q3WraNHrnQ@mail.gmail.com>
Message-ID: <87372c9boj.fsf@smugg>


Jeremy Hansen <jebrhansen+SBo at gmail.com> writes:

> It should also be mentioned that if you want to make changes to 
> a
> SlackBuild that someone else maintains, you'd submit the change 
> to that
> person. They are the maintainer and they have the right to 
> accept your
> changes and incorporate them into their script.

Yeah, I know the rules ;)

I am a lazy man with not that much time so I won't touch scripts 
still maintained by others :)

--
Xavier

From xavier at maillard.im  Thu Feb  8 07:36:24 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Thu, 08 Feb 2018 08:36:24 +0100
Subject: [Slackbuilds-users] package submission
In-Reply-To: <20180207180031.GU32488@n0nb.us>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org> <87eflwaltb.fsf@smugg>
 <20180207153414.ee3b592135ea69f5e158b6dd@ythogtha.org> <87bmh0akqt.fsf@smugg>
 <20180207180031.GU32488@n0nb.us>
Message-ID: <871shw9blz.fsf@smugg>


Nate Bargmann <n0nb at n0nb.us> writes:

> Willy had posted some instructions for doing this workflow last 
> year.
> They should be in the list archives.

Any chance you can give me the corresponding message-id ? That 
sounds great anyway.

--
Xavier

From xavier at maillard.im  Thu Feb  8 07:37:36 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Thu, 08 Feb 2018 08:37:36 +0100
Subject: [Slackbuilds-users] package submission
In-Reply-To: <49a973db-b517-db48-abf3-81b1bb4db0a7@slackbuilds.org>
References: <87o9l0aont.fsf@smugg>
 <db680d91-d9a7-87a2-c63b-b248886c7bb7@slackbuilds.org> <87eflwaltb.fsf@smugg>
 <49a973db-b517-db48-abf3-81b1bb4db0a7@slackbuilds.org>
Message-ID: <87zi4k7wzj.fsf@smugg>


Erik Hanson <erik at slackbuilds.org> writes:

> On 02/07/2018 08:58 AM, Xavier Maillard wrote:
>>
>> Willy Sudiarto Raharjo <willysr at slackbuilds.org> writes:
>>
>>>> what's the prefered way to share/distribute a new slackbuild 
>>>> to the SBo
>>>> project ?
>>>> Should I use the git method (pull request) or the webform ?
>>>
>>> Use the submission form
>>
>> Ok.
>>
>> Just to satisfy my curiosity, is the SBo git repo open to 
>> external
>> contributors ?
>
> Yes, access can be given to long-time maintainers to ease 
> submitting
> updates, but not for new submissions. Those need to go through 
> the
> submission form.

That's ok. I have submited a new version for the leiningen package 
since it has been abandonned and I am using it here.

Thank you.

--
Xavier

From xavier at maillard.im  Thu Feb  8 07:32:41 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Thu, 08 Feb 2018 08:32:41 +0100
Subject: [Slackbuilds-users] article about slackware.
In-Reply-To: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
References: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
Message-ID: <874lms9bs6.fsf@smugg>


Fernando Lopez <fernando.lopezjr at gmail.com> writes:

> https://hackaday.com/2018/01/30/making-the-case-for-slackware-in-2018/

I agree with the author; I have never found any simpler distro to 
use than my beloved slackware.
This is as simple as install, enjoy.

I wish it will stay as is still for years !

--
Xavier

From larryhaja at gmail.com  Thu Feb  8 13:12:47 2018
From: larryhaja at gmail.com (Larry Hajali)
Date: Thu, 8 Feb 2018 05:12:47 -0800
Subject: [Slackbuilds-users] Kodi and ffmpeg
In-Reply-To: <b7044ff8-ad74-8da3-8d09-6899815d7015@gmail.com>
References: <835db362-1ac1-d1fa-6253-f20bc16c638e@gmail.com>
 <CABrRyLn0TT0YLJ+F5ees0SfrB-8R-kJi+6b=ntkO3XS_zG6q+Q@mail.gmail.com>
 <b7044ff8-ad74-8da3-8d09-6899815d7015@gmail.com>
Message-ID: <CAAZPBMjh1uSkfDYZzM7-yjN5q_v9J-huOjqxYFoh7JWEQ34Miw@mail.gmail.com>

On Wed, Feb 7, 2018 at 10:41 PM, King Beowulf <kingbeowulf at gmail.com> wrote:

> On 02/04/2018 06:54 AM, Daniel Stein wrote:
> > Doesn't the Kodi build use it's own ffmpeg for the build?
> >
> > On Feb 3, 2018 10:34 PM, "King Beowulf" <kingbeowulf at gmail.com
> > <mailto:kingbeowulf at gmail.com>> wrote:
> >
> >     The kodi Slackbuild states:
> >
> >     # The version of ffmpeg on SBo is too old to compile kodi
> >
> >     and provides ffmpeg-3.1.11 however SBo provides ffmpeg-3.2.4
> >
> >     -Ed
> >
>
> Maybe I was too terse: the version of ffmpeg supported by the kodi
> script maintainer is older than the one provided by the script to
> compile kodi.  The comment in the build script is now misleading.  It is
> NOT that SBo ffmpeg is too old, rather that kodi devs REQUIRE a
> ffmpeg-3.1.x as they have patched it for kodi "krypton"
>
> Yes, the message is the README is old and I haven't updated/removed it.
The main thing is that I don't really support that option and I haven't
tried building Kodi with SBo ffmpeg in the build script even though it is
still there.  The maintainers of Kodi highly recommend their version of
ffmpeg.

I can test it if it works but not sure if I want to support that option.

Thanks,
--Larry


> Whether ffmpeg upstream is aware of these patches, I'm too tired to
> research...
>
> -Ed
>
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180208/f676a7db/attachment.html>

From ricardo at palmtx.com.ar  Thu Feb  8 16:16:42 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Thu, 8 Feb 2018 13:16:42 -0300
Subject: [Slackbuilds-users] package submission
In-Reply-To: <871shw9blz.fsf@smugg>
References: <87o9l0aont.fsf@smugg> <20180207180031.GU32488@n0nb.us>
 <871shw9blz.fsf@smugg>
Message-ID: <201802081316.42872.ricardo@palmtx.com.ar>

El Jueves 08/02/2018 a las 04:36, Xavier Maillard escribi?:
> Nate Bargmann <n0nb at n0nb.us> writes:
> > Willy had posted some instructions for doing this workflow last
> > year.
> > They should be in the list archives.
>
> Any chance you can give me the corresponding message-id ? That
> sounds great anyway.

I saved that email for future reference :)

The thread starts here:
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-March/018514.html

And this is the meat:
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-March/018539.html

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 thedoogster at gmail.com  Thu Feb  8 17:25:02 2018
From: thedoogster at gmail.com (Doogster)
Date: Thu, 8 Feb 2018 09:25:02 -0800
Subject: [Slackbuilds-users] article about slackware.
In-Reply-To: <C0165A5E-158F-44E9-B49A-96B84B985102@gmail.com>
References: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
 <C0165A5E-158F-44E9-B49A-96B84B985102@gmail.com>
Message-ID: <CAE5oDaZ+SUhm9KvzVbOiO41ikvoosz19rJ2jv9vmo4aPYtqOcQ@mail.gmail.com>

Where do Slackers go to irc?

On Wed, Feb 7, 2018 at 7:37 PM, Herminio Hernandez Jr.
<herminio.hernandezjr at gmail.com> wrote:
> I shared this on IRC. Great read.
>
> Sent from my iPhone
>
> On Feb 7, 2018, at 4:37 PM, Fernando Lopez <fernando.lopezjr at gmail.com>
> wrote:
>
> https://hackaday.com/2018/01/30/making-the-case-for-slackware-in-2018/
>
> --
>
> ------------
> Regards,
>     Fernando Lopez Jr.
>
> _______________________________________________
> 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 lists at osh.id.au  Thu Feb  8 17:41:13 2018
From: lists at osh.id.au (David O'Shaughnessy)
Date: Fri, 9 Feb 2018 03:41:13 +1000
Subject: [Slackbuilds-users] article about slackware.
In-Reply-To: <CAE5oDaZ+SUhm9KvzVbOiO41ikvoosz19rJ2jv9vmo4aPYtqOcQ@mail.gmail.com>
References: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
 <C0165A5E-158F-44E9-B49A-96B84B985102@gmail.com>
 <CAE5oDaZ+SUhm9KvzVbOiO41ikvoosz19rJ2jv9vmo4aPYtqOcQ@mail.gmail.com>
Message-ID: <6af24ff2-0d09-ae98-1bfa-62a3ced264cf@osh.id.au>

On 02/09/2018 03:25 AM, Doogster wrote:
> Where do Slackers go to irc?
> 

##slackware on Freenode seems like the main game. There's a Matrix
channel (https://matrix.to/#/#slackware:matrix.org), but nothing much
happening there yet.

--
Dave

From yalhcru at gmail.com  Thu Feb  8 19:57:04 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 8 Feb 2018 14:57:04 -0500
Subject: [Slackbuilds-users] jack2
Message-ID: <CAN1hMuC7sigGPs8La37Rn-PZAwV+KfoipC5nw_Cup+nvHUGusQ@mail.gmail.com>

Has anyone heard from Marcel Saegebarth (marc at mos6581.de) lately? Sent
him a mail 6 days ago, haven't got a response. Posting here in case he's
monitoring this list.

jack2 hasn't been updated since he took it over in October 2014. I'd
like to take this one (since I'm taking the JACK 1 build already).

From herminio.hernandezjr at gmail.com  Thu Feb  8 23:45:39 2018
From: herminio.hernandezjr at gmail.com (Herminio Hernandez Jr. )
Date: Thu, 8 Feb 2018 18:45:39 -0500
Subject: [Slackbuilds-users] article about slackware.
In-Reply-To: <6af24ff2-0d09-ae98-1bfa-62a3ced264cf@osh.id.au>
References: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
 <C0165A5E-158F-44E9-B49A-96B84B985102@gmail.com>
 <CAE5oDaZ+SUhm9KvzVbOiO41ikvoosz19rJ2jv9vmo4aPYtqOcQ@mail.gmail.com>
 <6af24ff2-0d09-ae98-1bfa-62a3ced264cf@osh.id.au>
Message-ID: <B888E297-C195-4617-9E72-2231ECB738DB@gmail.com>

##slackware is pretty active

Sent from my iPhone

> On Feb 8, 2018, at 12:41 PM, David O'Shaughnessy <lists at osh.id.au> wrote:
> 
>> On 02/09/2018 03:25 AM, Doogster wrote:
>> Where do Slackers go to irc?
>> 
> 
> ##slackware on Freenode seems like the main game. There's a Matrix
> channel (https://matrix.to/#/#slackware:matrix.org), but nothing much
> happening there yet.
> 
> --
> Dave
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From willysr at slackbuilds.org  Fri Feb  9 01:16:18 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 9 Feb 2018 08:16:18 +0700
Subject: [Slackbuilds-users] FedoraProject Repository
Message-ID: <ad7b9301-9c41-52e1-4f98-3e6947d5257c@slackbuilds.org>

Hi all,

i noticed that pkgs.fedoraproject.org repository returned forbidden as
of today (perhaps earlier).

Here are the list of scripts that are hosted in that repository

audio/pyalsaaudio/
audio/xmms-scrobbler/
desktop/kfaenza-icon-theme/
development/cvsps/
development/eric/
development/generatorrunner/
development/hugs98/
development/jam/
development/leveldb/
development/lmdb/
development/mono-debugger/
games/cowsay/
games/fortune_firefly/
games/rogue/
graphics/gpscorrelate/
libraries/edelib/
libraries/freealut/
libraries/gtk-qt-engine/
libraries/iksemel/
libraries/libdaemon/
libraries/libewf/
libraries/libkate/
libraries/libmp4v2/
libraries/libmpd/
libraries/libofa/
libraries/qt-assistant-compat/
libraries/qt3/
libraries/wvstreams/
misc/xdelta/
multimedia/dirac/
multimedia/ivtv-utils/
multimedia/schroedinger/
multimedia/sfnt2woff/
multimedia/w_scan/
network/skylable-sx/
network/synergy/
network/tucan/
network/wavemon/
network/wvdial/
perl/perl-DateTime-Locale/
python/ipaddr-py/
system/cdrkit/
system/dfu-util/
system/geoclue/

Maintainers who have GIt access can update the DOWNLOAD url directly.
If anyone knows a valid URL containing the same source and checksum for
above scripts, please let us know and we will fix them ASAP.

I'm looking forward to fix this issue before tomorrow's public update.


-- 
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/20180209/53ea7cb8/attachment.asc>

From skaendo at excite.com  Fri Feb  9 01:49:50 2018
From: skaendo at excite.com (Ed Ender)
Date: Thu, 08 Feb 2018 20:49:50 -0500
Subject: [Slackbuilds-users] FedoraProject Repository
Message-ID: <20180208204950.29337@web006.roc2.bluetie.com>

I had told Ponce about this a few days ago relating to geoclue, I have since found an alternate download for it (and possibly more at: http://distfiles.gentoo.org/distfiles/

-----Original Message-----
From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org]
Date: 02/08/2018 07:16 PM
To: slackbuilds-users at slackbuilds.org
Subject: [Slackbuilds-users] FedoraProject Repository

Hi all,

i noticed that pkgs.fedoraproject.org repository returned forbidden as
of today (perhaps earlier).

Here are the list of scripts that are hosted in that repository

audio/pyalsaaudio/
audio/xmms-scrobbler/
desktop/kfaenza-icon-theme/
development/cvsps/
development/eric/
development/generatorrunner/
development/hugs98/
development/jam/
development/leveldb/
development/lmdb/
development/mono-debugger/
games/cowsay/
games/fortune_firefly/
games/rogue/
graphics/gpscorrelate/
libraries/edelib/
libraries/freealut/
libraries/gtk-qt-engine/
libraries/iksemel/
libraries/libdaemon/
libraries/libewf/
libraries/libkate/
libraries/libmp4v2/
libraries/libmpd/
libraries/libofa/
libraries/qt-assistant-compat/
libraries/qt3/
libraries/wvstreams/
misc/xdelta/
multimedia/dirac/
multimedia/ivtv-utils/
multimedia/schroedinger/
multimedia/sfnt2woff/
multimedia/w_scan/
network/skylable-sx/
network/synergy/
network/tucan/
network/wavemon/
network/wvdial/
perl/perl-DateTime-Locale/
python/ipaddr-py/
system/cdrkit/
system/dfu-util/
system/geoclue/

Maintainers who have GIt access can update the DOWNLOAD url directly.
If anyone knows a valid URL containing the same source and checksum for
above scripts, please let us know and we will fix them ASAP.

I'm looking forward to fix this issue before tomorrow's public update.


-- 
Willy Sudiarto Raharjo




From willysr at slackbuilds.org  Fri Feb  9 01:52:06 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 9 Feb 2018 08:52:06 +0700
Subject: [Slackbuilds-users] FedoraProject Repository
In-Reply-To: <20180208204950.29337@web006.roc2.bluetie.com>
References: <20180208204950.29337@web006.roc2.bluetie.com>
Message-ID: <11e7515f-181e-1cf7-24bd-026f850b4827@slackbuilds.org>

> I had told Ponce about this a few days ago relating to geoclue, I have since found an alternate download for it (and possibly more at: http://distfiles.gentoo.org/distfiles/

Some of them are now fixed on my branch, while i will continue to fix
the rest later on

please have a look at https://slackbuilds.org/ready/ to make sure it
hasn't been fixed in one of the admin's branch before pushing any 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/20180209/23421990/attachment.asc>

From kjhambrick at gmail.com  Fri Feb  9 10:27:31 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 9 Feb 2018 04:27:31 -0600
Subject: [Slackbuilds-users] Minor Typo in kmymoney README
Message-ID: <CANBHt+NpxQ_7kKMOk7K8tzmji+FyNcqzASFht2v0N0jV_kp7cA@mail.gmail.com>

Christophe --

Reporting a very minor typo ...

The Slackware 14.2 kmymoney README File misspells aqbanking with a 'g'
instead of with a 'q'.

Unified diff is below my sig line.

Thanks for all the SlackBuilds Christophe !

-- kjh

--- /tmp/README.orig    2018-02-09 04:21:28.661073947 -0600
+++ /tmp/README.        2018-02-09 04:21:54.591072556 -0600
@@ -1,4 +1,4 @@
 KmyMoney is a simple financial accounting manager for KDE for personal or
 small-business use.  It is a full double-entry accounting software package.
 libofx 0.9.4+ is an optional dependency to support ofxbanking.
-agbanking and gwenhywfar are optional dependencies to support Kbanking.
+aqbanking and gwenhywfar are optional dependencies to support Kbanking.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180209/13776f40/attachment.html>

From willysr at slackbuilds.org  Fri Feb  9 11:54:53 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 9 Feb 2018 18:54:53 +0700
Subject: [Slackbuilds-users] Minor Typo in kmymoney README
In-Reply-To: <CANBHt+NpxQ_7kKMOk7K8tzmji+FyNcqzASFht2v0N0jV_kp7cA@mail.gmail.com>
References: <CANBHt+NpxQ_7kKMOk7K8tzmji+FyNcqzASFht2v0N0jV_kp7cA@mail.gmail.com>
Message-ID: <1957b666-2fb0-7a40-6535-d01105937f5d@slackbuilds.org>

> Reporting a very minor typo ...
> 
> The Slackware 14.2 kmymoney README File misspells aqbanking with a 'g'
> instead of with a 'q'.
> 
> Unified diff is below my sig line.
> 
> Thanks for all the SlackBuilds Christophe !
> 
> -- kjh
> 
> --- /tmp/README.orig??? 2018-02-09 04:21:28.661073947 -0600
> +++ /tmp/README.??????? 2018-02-09 04:21:54.591072556 -0600
> @@ -1,4 +1,4 @@
> ?KmyMoney is a simple financial accounting manager for KDE for personal or
> ?small-business use.? It is a full double-entry accounting software package.
> ?libofx 0.9.4+ is an optional dependency to support ofxbanking.
> -agbanking and gwenhywfar are optional dependencies to support Kbanking.
> +aqbanking and gwenhywfar are optional dependencies to support Kbanking.

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/20180209/32c06415/attachment.asc>

From n0nb at n0nb.us  Fri Feb  9 14:08:27 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Fri, 9 Feb 2018 08:08:27 -0600
Subject: [Slackbuilds-users] article about slackware.
In-Reply-To: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
References: <CALrQ46Dp8vkSTTAJg0peaUTkFYjUpLXSi6qRWGXSzbXdt9MKvg@mail.gmail.com>
Message-ID: <20180209140827.GY32488@n0nb.us>

* On 2018 07 Feb 15:38 -0600, Fernando Lopez wrote:
> https://hackaday.com/2018/01/30/making-the-case-for-slackware-in-2018/

I have to disagree with this statement:

"So what should you do if you?re looking for the ?classic? Linux
experience? Where automatic configuration is a dirty word, and every
aspect of your system can be manipulated with nothing more exotic than a
text editor?"

Slackware is quite automated these days owing to the kernel's ability to
recognize hardware and load modules and udev setting things up.  Then we
have X that detects and auto-configures the graphics adapter and other
devices.  Then KDE is right there to take care of many things for the
user.  IMO, automation is hardly a "dirty word" but is the order of the
day.

The following is true just not of Slackware but of all current
distributions.  Gone are the days of:

* Compiling the kernel to support a mouse/modem/network adapter, etc.
* Consulting the manual for a given monitor to get its parameters to
  write a mode line for X.
* Damaging a monitor when the mode line was wrong (I never did but did
  hear some interesting squeals a few times).
* Manually selecting the mouse driver for X.
* Manually mounting a floppy disk.
* Carefully selecting hardware known to work with Linux.
* Feeling like the world was conquered when sound worked!

Most of these items are obsolete due to the industry developing
standards for the hardware to assist the OS to be able to recognize and
configure hardware.  The PCI bus and the capability built into monitors
to report their capabilities were major steps forward.  The kernel and X
were rewritten to take full advantage of these industry initiatives.
Slackware, just as all current distributions, has benefited greatly from
all of this work.  Automation is everywhere one cares to look.

Oh, a text editor is required to edit /etc/inittab to set the runlevel
to 4 so that the graphical login manager is started, so there is that.
;-)

- Nate

-- 

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

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180209/0b1e14d2/attachment.asc>

From cnguyenminhtan at free.fr  Fri Feb  9 16:39:59 2018
From: cnguyenminhtan at free.fr (cnguyenminhtan at free.fr)
Date: Fri, 9 Feb 2018 17:39:59 +0100 (CET)
Subject: [Slackbuilds-users] Minor Typo in kmymoney README
In-Reply-To: <CANBHt+NpxQ_7kKMOk7K8tzmji+FyNcqzASFht2v0N0jV_kp7cA@mail.gmail.com>
Message-ID: <939426700.287011058.1518194399649.JavaMail.root@zimbra75-e12.priv.proxad.net>

kjh,

Thanks for spotting the typo error.

Credit for the Slackbuilds script goes to the previous maintainer, Gilcio Amaral. I'm just keeping it up-to-date with each new minor release.

Much re-work is expected when/if Slackware switches to QT5.

Regards,

Christophe

----- Mail original -----
De: "Konrad J Hambrick" <kjhambrick at gmail.com>
?: cnguyenminhtan at free.fr, "SlackBuilds.org Users List" <SlackBuilds-users at slackbuilds.org>
Cc: "Konrad J Hambrick" <kjhambrick at gmail.com>
Envoy?: Vendredi 9 F?vrier 2018 11:27:31
Objet: Minor Typo in kmymoney README



Christophe -- 


Reporting a very minor typo ... 


The Slackware 14.2 kmymoney README File misspells aqbanking with a 'g' instead of with a 'q'. 


Unified diff is below my sig line. 


Thanks for all the SlackBuilds Christophe ! 


-- kjh 

--- /tmp/README.orig 2018-02-09 04:21:28.661073947 -0600 
+++ /tmp/README. 2018-02-09 04:21:54.591072556 -0600 
@@ -1,4 +1,4 @@ 
KmyMoney is a simple financial accounting manager for KDE for personal or 
small-business use. It is a full double-entry accounting software package. 
libofx 0.9.4+ is an optional dependency to support ofxbanking. 
-agbanking and gwenhywfar are optional dependencies to support Kbanking. 
+aqbanking and gwenhywfar are optional dependencies to support Kbanking. 


From kjhambrick at gmail.com  Fri Feb  9 16:49:13 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 9 Feb 2018 10:49:13 -0600
Subject: [Slackbuilds-users] Minor Typo in kmymoney README
In-Reply-To: <939426700.287011058.1518194399649.JavaMail.root@zimbra75-e12.priv.proxad.net>
References: <CANBHt+NpxQ_7kKMOk7K8tzmji+FyNcqzASFht2v0N0jV_kp7cA@mail.gmail.com>
 <939426700.287011058.1518194399649.JavaMail.root@zimbra75-e12.priv.proxad.net>
Message-ID: <CANBHt+OBqbhndm_eGonB2ZSAAged1hJZb7sjex7x1AyyZVTkew@mail.gmail.com>

You're welcome Christophe.

I saw this LWN Article:  KMyMoney 5.0.0 released
<https://lwn.net/Articles/746770/> and it got me wondering whether there
was a kmymoney.SlackBuild.

Thanks again.

-- kjh



On Fri, Feb 9, 2018 at 10:39 AM, <cnguyenminhtan at free.fr> wrote:

> kjh,
>
> Thanks for spotting the typo error.
>
> Credit for the Slackbuilds script goes to the previous maintainer, Gilcio
> Amaral. I'm just keeping it up-to-date with each new minor release.
>
> Much re-work is expected when/if Slackware switches to QT5.
>
> Regards,
>
> Christophe
>
> ----- Mail original -----
> De: "Konrad J Hambrick" <kjhambrick at gmail.com>
> ?: cnguyenminhtan at free.fr, "SlackBuilds.org Users List" <
> SlackBuilds-users at slackbuilds.org>
> Cc: "Konrad J Hambrick" <kjhambrick at gmail.com>
> Envoy?: Vendredi 9 F?vrier 2018 11:27:31
> Objet: Minor Typo in kmymoney README
>
>
>
> Christophe --
>
>
> Reporting a very minor typo ...
>
>
> The Slackware 14.2 kmymoney README File misspells aqbanking with a 'g'
> instead of with a 'q'.
>
>
> Unified diff is below my sig line.
>
>
> Thanks for all the SlackBuilds Christophe !
>
>
> -- kjh
>
> --- /tmp/README.orig 2018-02-09 04:21:28.661073947 -0600
> +++ /tmp/README. 2018-02-09 04:21:54.591072556 -0600
> @@ -1,4 +1,4 @@
> KmyMoney is a simple financial accounting manager for KDE for personal or
> small-business use. It is a full double-entry accounting software package.
> libofx 0.9.4+ is an optional dependency to support ofxbanking.
> -agbanking and gwenhywfar are optional dependencies to support Kbanking.
> +aqbanking and gwenhywfar are optional dependencies to support Kbanking.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180209/c99f12f7/attachment.html>

From willysr at slackbuilds.org  Sat Feb 10 01:28:12 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Feb 2018 08:28:12 +0700
Subject: [Slackbuilds-users] Updates - 20180210.1
Message-ID: <6d78fb98-f43e-7419-d0fc-99ae2a23ce26@slackbuilds.org>

Hi

all the broken link from pkgs.fedoraproject.org has been resolved in
this batch. Let us know if there's more broken link in the repository
and we will try to fix it in the next batch.

flashplayer-plugin and pepperflash-plugin are updated to 28.0.0.161 to
fix security vulnerabilities. Please refer to
https://helpx.adobe.com/security/products/flash-player/apsb18-03.html
for more information.

LibreOffice has been bumped to 6.0.0.3, while libreoffice is bumped to
6.0.1. LO 6.0.1 was released yesterday so source-based compilation will
have to wait until next batch of update to be in par with the
binary-repackaging.

As promised, opencv is now bumped to latest version (3.4) while an
opencv-legacy is provided for those who can't move on to 3.4 (libkface).
If you found any other scripts that can't work with latest opencv, let
us know.


Sat Feb 10 01:10:45 UTC 2018
academic/fet: Updated for version 5.35.2.
academic/gwyddion: Updated for version 2.50.
audio/jack-audio-connection-kit: Updated for version 0.125.0.
audio/ladspa_sdk: Update DOWNLOAD url.
audio/pyalsaaudio: Update DOWNLOAD url.
audio/xmms-scrobbler: Update DOWNLOAD url.
desktop/cnslock: Fix version.
desktop/kfaenza-icon-theme: Update DOWNLOAD url.
desktop/nitrokey-app: Updated for version 1.2.
development/chibi-scheme: Updated for version 0.8.0.
development/composer: Updated for version 1.6.3
development/cvsps: Update DOWNLOAD url.
development/dwarf: Updated for version 20180129
development/eric: Update DOWNLOAD url.
development/generatorrunner: Update DOWNLOAD url.
development/hhvm: Updated for version 3.24.2
development/hugs98: Update DOWNLOAD url.
development/jam: Update DOWNLOAD url.
development/leiningen: Updated for version 2.8.1 + new maintainer.
development/leveldb: Update DOWNLOAD url.
development/lmdb: Update DOWNLOAD url.
development/mono-debugger: Update DOWNLOAD url.
development/perf: Updated for version 4.4.115.
development/psycopg2: Updated for version 2.7.4.
development/rtags: Updated for version 2.18.
development/sbcl: Updated for version 1.4.4.
development/slibtool: Updated for version 0.5.18.
development/tidy-html5: Updated for version 5.6.0.
development/tiled: Updated for version 1.1.2.
development/universal-ctags: Updated for version 7918d19
development/vscode: New maintainer.
games/adom: Updated for version 3.0.6.
games/advancemame: Updated for version 3.7.
games/cowsay: Update DOWNLOAD url.
games/fortune_firefly: Fix homepage.
games/freeciv: Updated for version 2.6.0_beta2.
games/pioneer: Updated for version 20180203.
games/planetblupi: Updated for version 1.12.2.
games/rogue: Update DOWNLOAD url.
games/stella: Updated for version 5.1.
gis/pktools: Updated for version 2.6.7.3.
git/gitignore: Added phar.
graphics/brlcad: Updated for version 7.26.4 + new maintainer.
graphics/frescobaldi: Updated for version 2.20.0.
graphics/gpscorrelate: Update DOWNLOAD url.
graphics/mirage: New maintainer.
graphics/trimage: Added (image compressor).
ham/codec2: Added (low bit rate speech codec).
ham/freedv: Added (Open source amateur digital voice).
libraries/SDL_kitchensink: Updated for version 0.0.7.
libraries/adns: Fix ownership & perms.
libraries/edelib: Update DOWNLOAD url.
libraries/freealut: Update DOWNLOAD url.
libraries/gtk-qt-engine: Update DOWNLOAD url.
libraries/gtk-sharp: Updated for version 2.12.45.
libraries/iksemel: Update DOWNLOAD url.
libraries/leptonica: Updated for version 1.75.1.
libraries/libdaemon: Update DOWNLOAD url.
libraries/libewf: Update DOWNLOAD url.
libraries/libkate: Update DOWNLOAD url.
libraries/libkface: Switch to opencv-legacy.
libraries/libkgeomap4: Update DOWNLOAD url.
libraries/liblrdf: Fix tarball handling.
libraries/libminizip: Updated for version 1.2.11.
libraries/libmp4v2: Update DOWNLOAD url.
libraries/libmpd: Update DOWNLOAD url.
libraries/libofa: Update DOWNLOAD url.
libraries/libsass: Updated for version 3.4.9.
libraries/libversion: Updated for version 2.5.0.
libraries/libwacom: Updated for version 0.28.
libraries/opal: Updated for version 3.10.10.
libraries/opencv-legacy: Added (Open Source Computer Vision).
libraries/opencv: Updated for version 3.4.0
libraries/qt-assistant-compat: Update DOWNLOAD url.
libraries/qt3: Fix download link.
libraries/unibilium: Updated for version 2.0.0.
libraries/uriparser: Updated for version 0.8.5, changed homepage.
libraries/wvstreams: Update DOWNLOAD url.
misc/KeePass: Remove VERSION.
misc/mosquitto: Update README, slack-desc
misc/xdelta: Update DOWNLOAD url.
multimedia/dirac: Update DOWNLOAD url.
multimedia/flashplayer-plugin: Updated for version 28.0.0.161.
multimedia/freshplayerplugin: Updated for version 0.3.9.
multimedia/ivtv-utils: Update DOWNLOAD url.
multimedia/pepperflash-plugin: Updated for version 28.0.0.161.
multimedia/schroedinger: Update DOWNLOAD url.
multimedia/sfnt2woff: Updated for version 2009.10.03.
multimedia/vivaldi-codecs-ffmpeg-extra: Updated for v 64.0.3282.140.
multimedia/w_scan: Update DOWNLOAD url.
network/Electrum: Updated for version 3.0.6.
network/WireGuard: Updated for version 0.0.20180202.
network/aMule: Added a patch for libupnp-1.8.x.
network/basilisk: Updated for version 2018.02.02.
network/brave: Update script.
network/hiawatha: Updated for version 10.7 + new maintainer.
network/opera: Updated for version 51.0.2830.26.
network/prosody-mod-csi: Updated for version hg2876.
network/skylable-sx: Update DOWNLOAD url.
network/slack: Updated for version 3.0.5.
network/slimjet: Updated for version 17.0.9.0.
network/synergy: Update DOWNLOAD url.
network/thttpd: Updated for version 2.28.
network/tixati: Updated for version 2.56_1.
network/transmission: Updated for version 2.93.
network/tucan: Update DOWNLOAD url.
network/urlwatch: Updated for version 2.8.
network/vivaldi: Updated for version 1.14.1077.45.
network/waterfox: Updated for version 56.0.4.1.
network/wavemon: Updated for version 0.8.1.
network/wvdial: Update DOWNLOAD url.
network/x11vnc: Updated for version 0.9.15
network/yandex-browser-beta: Updated for version 17.11.1.1120.
office/LibreOffice: Updated for version 6.0.0.3
office/kmymoney: Fix README.
office/libreoffice-helppack: Updated for version 6.0.1.
office/libreoffice-langpack: Updated for version 6.0.1.
office/libreoffice: Updated for version 6.0.1.
perl/perl-DateTime-Locale: Update DOWNLOAD url.
perl/perl-Sub-Quote: Updated for version 2.005000.
python/ipaddr-py: Update DOWNLOAD url.
python/mechanize: Update download url
python/pycodestyle: Added python3 support.
python/python-configargparse: Updated for version 0.13.0.
python/python-fonttools: Updated for version 3.22.0.
python/python-neovim: Updated for version 0.2.1.
system/Iosevka: Updated for version 1.14.0.
system/bitrot: Added (dectects bit rotten files).
system/cdrkit: Update DOWNLOAD url.
system/chipsec: Added (Platform Security Assessment Framework).
system/dfu-util: Update DOWNLOAD url.
system/dosbox-dev: Updated for version 0.74.r4074.
system/etsh: Added (extended Thompson shell).
system/geoclue: Update DOWNLOAD url.
system/hack-font-ttf: Updated for version 3.002.
system/herculesstudio: Update DOWNLOAD url.
system/innotop: Update DOWNLOAD url.
system/isdct: Updated for version 3.0.10.
system/iucode_tool: Updated for version 2.3.1.
system/keybase: Updated for version 1.0.41.
system/laptop-mode-tools: Updated for version 1.72.2.
system/mailutils: Compress manpages.
system/man-db: Updated for version 2.8.0.
system/numlockx: Update DOWNLOAD url.
system/pax: Update DOWNLOAD url.
system/schedtool: Update DOWNLOAD url.
system/stress: Update DOWNLOAD url.
system/tilda: Updated for version 1.4.1.
system/vifm: Updated for version 0.9.1.
system/wmfsm: Updated for version 0.36.
system/worker: Updated for version 3.15.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From skaendo at excite.com  Sat Feb 10 01:40:14 2018
From: skaendo at excite.com (Ed Ender)
Date: Fri, 09 Feb 2018 20:40:14 -0500
Subject: [Slackbuilds-users] Updates - 20180210.1
Message-ID: <20180209204014.3384@web005.roc2.bluetie.com>

Hey Willy,

I rewrote the slimjet Slackbuild to use only the icons in the slimjet package, so the icon folder can be removed.
No rush, no big deal, just letting you know. I should have probably mentioned this when submitting, sorry about that.

Thanks,
Ed

-----Original Message-----
From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org]
Date: 02/09/2018 07:28 PM
To: slackbuilds-users at slackbuilds.org
Subject: [Slackbuilds-users] Updates - 20180210.1

Hi

all the broken link from pkgs.fedoraproject.org has been resolved in
this batch. Let us know if there's more broken link in the repository
and we will try to fix it in the next batch.

flashplayer-plugin and pepperflash-plugin are updated to 28.0.0.161 to
fix security vulnerabilities. Please refer to
https://helpx.adobe.com/security/products/flash-player/apsb18-03.html
for more information.

LibreOffice has been bumped to 6.0.0.3, while libreoffice is bumped to
6.0.1. LO 6.0.1 was released yesterday so source-based compilation will
have to wait until next batch of update to be in par with the
binary-repackaging.

As promised, opencv is now bumped to latest version (3.4) while an
opencv-legacy is provided for those who can't move on to 3.4 (libkface).
If you found any other scripts that can't work with latest opencv, let
us know.

-- 
Willy Sudiarto Raharjo




From willysr at slackbuilds.org  Sat Feb 10 01:40:41 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Feb 2018 08:40:41 +0700
Subject: [Slackbuilds-users] Updates - 20180210.1
In-Reply-To: <20180209204014.3384@web005.roc2.bluetie.com>
References: <20180209204014.3384@web005.roc2.bluetie.com>
Message-ID: <2023c147-3d96-d5d3-1990-52f5ca4fe113@slackbuilds.org>

> I rewrote the slimjet Slackbuild to use only the icons in the slimjet package, so the icon folder can be removed.
> No rush, no big deal, just letting you know. I should have probably mentioned this when submitting, sorry about that.

Hi Ed

Thanks for notifying
i will delete them on my branch ASAP


-- 
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/20180210/8f5ec46c/attachment.asc>

From skaendo at excite.com  Sat Feb 10 07:13:23 2018
From: skaendo at excite.com (Ed Ender)
Date: Sat, 10 Feb 2018 02:13:23 -0500
Subject: [Slackbuilds-users] Broken link
Message-ID: <20180210021323.11409@web001.roc2.bluetie.com>

I just came across another broken link.

python3-ptyprocess, same md5sum.

Old link: https://files.pythonhosted.org/packages/source/p/ptyprocess/ptyprocess-0.5.2.tar.gz

New link: https://pypi.python.org/packages/51/83/5d07dc35534640b06f9d9f1a1d2bc2513fb9cc7595a1b0e28ae5477056ce/ptyprocess-0.5.2.tar.gz

From willysr at slackbuilds.org  Sat Feb 10 07:58:00 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Feb 2018 14:58:00 +0700
Subject: [Slackbuilds-users] Broken link
In-Reply-To: <20180210021323.11409@web001.roc2.bluetie.com>
References: <20180210021323.11409@web001.roc2.bluetie.com>
Message-ID: <3694b529-1330-bd2b-5a26-0611a92ddf97@slackbuilds.org>

> I just came across another broken link.
> 
> python3-ptyprocess, same md5sum.
> 
> Old link: https://files.pythonhosted.org/packages/source/p/ptyprocess/ptyprocess-0.5.2.tar.gz
> 
> New link: https://pypi.python.org/packages/51/83/5d07dc35534640b06f9d9f1a1d2bc2513fb9cc7595a1b0e28ae5477056ce/ptyprocess-0.5.2.tar.gz

Hi Ed

the current link works fine here


-- 
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/20180210/d6817fda/attachment-0001.asc>

From chris.willing at iinet.net.au  Sat Feb 10 11:08:37 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Sat, 10 Feb 2018 21:08:37 +1000
Subject: [Slackbuilds-users] dfu-util version
Message-ID: <c3b23343-1c39-d7dc-2c18-c7463ad90526@iinet.net.au>

I'm just processing updates from 20180210.1 and find that
system/dfu-util has changed version from 0.8 to 0.3 along with a change
in DOWNLOAD url to slackbuildsdirectlinks, presumably because version
0.3 is no longer available from the originating software repo (where,
incidentally, the current version is 0.9).

Any reason for reverting to 0.3 rather than upgrading to 0.9?

chris

From willysr at slackbuilds.org  Sat Feb 10 11:50:47 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Feb 2018 18:50:47 +0700
Subject: [Slackbuilds-users] dfu-util version
In-Reply-To: <c3b23343-1c39-d7dc-2c18-c7463ad90526@iinet.net.au>
References: <c3b23343-1c39-d7dc-2c18-c7463ad90526@iinet.net.au>
Message-ID: <f110c9c8-d403-aeed-9be2-e9d6780c52d3@slackbuilds.org>

> I'm just processing updates from 20180210.1 and find that
> system/dfu-util has changed version from 0.8 to 0.3 along with a change
> in DOWNLOAD url to slackbuildsdirectlinks, presumably because version
> 0.3 is no longer available from the originating software repo (where,
> incidentally, the current version is 0.9).
> 
> Any reason for reverting to 0.3 rather than upgrading to 0.9?

0.3 is the current version we had in our repo and the problem was a
broken link, so i tried not to change the version unless there's no
other choice.

We never had 0.8 based on git history

-- 
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/20180210/69b8eed1/attachment.asc>

From chris.willing at iinet.net.au  Sat Feb 10 12:01:12 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Sat, 10 Feb 2018 22:01:12 +1000
Subject: [Slackbuilds-users] dfu-util version
In-Reply-To: <f110c9c8-d403-aeed-9be2-e9d6780c52d3@slackbuilds.org>
References: <c3b23343-1c39-d7dc-2c18-c7463ad90526@iinet.net.au>
 <f110c9c8-d403-aeed-9be2-e9d6780c52d3@slackbuilds.org>
Message-ID: <cf0dd976-9b28-6eae-ec3b-dc23a16f49be@iinet.net.au>

On 10/02/18 21:50, Willy Sudiarto Raharjo wrote:
>> I'm just processing updates from 20180210.1 and find that
>> system/dfu-util has changed version from 0.8 to 0.3 along with a change
>> in DOWNLOAD url to slackbuildsdirectlinks, presumably because version
>> 0.3 is no longer available from the originating software repo (where,
>> incidentally, the current version is 0.9).
>>
>> Any reason for reverting to 0.3 rather than upgrading to 0.9?
> 
> 0.3 is the current version we had in our repo and the problem was a
> broken link, so i tried not to change the version unless there's no
> other choice.
> 
> We never had 0.8 based on git history
>

Sorry, I asked the wrong question. I just realised I was comparing
versions in a personal branch which I had updated locally in 2015 to 0.8.

The version in master was updated to 0.3 back in 2010 and the maintainer
at that time doesn't appear in the git log again since then (although
there have been some small script changes by admins since then). I'll
try emailing the maintainer about an update - if I hear nothing back in
a week or so (and no one objects), I'll take it over and update it.

chris

From ideutsch763 at yahoo.com  Sat Feb 10 12:27:29 2018
From: ideutsch763 at yahoo.com (Ira Deutsch)
Date: Sat, 10 Feb 2018 12:27:29 +0000 (UTC)
Subject: [Slackbuilds-users] Optimizing X86-64 builds
References: <1569994557.123308.1518265649286.ref@mail.yahoo.com>
Message-ID: <1569994557.123308.1518265649286@mail.yahoo.com>

Dear Sirs,

  When running SlackBuild scripts for x86-64 installations, the optimization
flags are -O2 -fPIC.  Would there be any advantage to adding flags depending
on the processor used?  If so, is there any convenient way to do this in the
SlackBuild script?

  Sincerely yours,
  Ira

From n0nb at n0nb.us  Sat Feb 10 18:49:09 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 10 Feb 2018 12:49:09 -0600
Subject: [Slackbuilds-users] Testing a script with options with sboinstall
Message-ID: <20180210184909.GC32488@n0nb.us>

I've used sboinstall enough now to know that some scripts prompt for
options.  I would like to test a script I am working on that will have a
build option with sboinstall to be sure that the user is prompted
correctly.  Looking through the HOWTOs on the Web site, I've not found
that document yet.

TIA

- Nate

-- 

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

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180210/d6c86b9a/attachment.asc>

From erik at slackbuilds.org  Sat Feb 10 19:05:04 2018
From: erik at slackbuilds.org (Erik Hanson)
Date: Sat, 10 Feb 2018 13:05:04 -0600
Subject: [Slackbuilds-users] Testing a script with options with
 sboinstall
In-Reply-To: <20180210184909.GC32488@n0nb.us>
References: <20180210184909.GC32488@n0nb.us>
Message-ID: <f5e53089-f0c6-0cbf-e738-f1ee1e9c2684@slackbuilds.org>

On 02/10/2018 12:49 PM, Nate Bargmann wrote:
> I've used sboinstall enough now to know that some scripts prompt for
> options.  I would like to test a script I am working on that will have a
> build option with sboinstall to be sure that the user is prompted
> correctly.  Looking through the HOWTOs on the Web site, I've not found
> that document yet.

Scripts in our repo are not allowed to prompt users, and we don't
support third-party tools. You should look at the sboinstall
documentation/code to figure out what it's doing.


-- 
Erik

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

From skaendo at excite.com  Sat Feb 10 19:25:47 2018
From: skaendo at excite.com (Ed Ender)
Date: Sat, 10 Feb 2018 14:25:47 -0500
Subject: [Slackbuilds-users] Testing a script with options with
 sboinstall
Message-ID: <20180210142547.20718@web002.roc2.bluetie.com>

https://pink-mist.github.io/sbotools/documentation/sboinstall.1.html

-----Original Message-----
From: "Erik Hanson" [erik at slackbuilds.org]
Date: 02/10/2018 01:05 PM
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] Testing a script with options with
 sboinstall

On 02/10/2018 12:49 PM, Nate Bargmann wrote:
> I've used sboinstall enough now to know that some scripts prompt for
> options.  I would like to test a script I am working on that will have a
> build option with sboinstall to be sure that the user is prompted
> correctly.  Looking through the HOWTOs on the Web site, I've not found
> that document yet.

Scripts in our repo are not allowed to prompt users, and we don't
support third-party tools. You should look at the sboinstall
documentation/code to figure out what it's doing.


-- 
Erik




From n0nb at n0nb.us  Sat Feb 10 19:35:47 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 10 Feb 2018 13:35:47 -0600
Subject: [Slackbuilds-users] Testing a script with options with
 sboinstall
In-Reply-To: <20180210142547.20718@web002.roc2.bluetie.com>
References: <20180210142547.20718@web002.roc2.bluetie.com>
Message-ID: <20180210193547.GD32488@n0nb.us>

* On 2018 10 Feb 13:27 -0600, Ed Ender wrote:
> https://pink-mist.github.io/sbotools/documentation/sboinstall.1.html

That is just an HTML version of the man page which I already read and
found lacking in the "howto test" department.  ;-)

- Nate

-- 

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

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180210/1e996607/attachment.asc>

From n0nb at n0nb.us  Sat Feb 10 19:36:40 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 10 Feb 2018 13:36:40 -0600
Subject: [Slackbuilds-users] Testing a script with options with
 sboinstall
In-Reply-To: <f5e53089-f0c6-0cbf-e738-f1ee1e9c2684@slackbuilds.org>
References: <20180210184909.GC32488@n0nb.us>
 <f5e53089-f0c6-0cbf-e738-f1ee1e9c2684@slackbuilds.org>
Message-ID: <20180210193640.GE32488@n0nb.us>

* On 2018 10 Feb 13:06 -0600, Erik Hanson wrote:
> Scripts in our repo are not allowed to prompt users, and we don't
> support third-party tools. You should look at the sboinstall
> documentation/code to figure out what it's doing.

The script does not prompt the user.  I modeled it after the avahi
script.

- Nate

-- 

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

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180210/638233c8/attachment-0001.asc>

From baildon.research at googlemail.com  Sat Feb 10 21:47:05 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Sat, 10 Feb 2018 21:47:05 +0000
Subject: [Slackbuilds-users] Optimizing X86-64 builds
In-Reply-To: <1569994557.123308.1518265649286@mail.yahoo.com>
References: <1569994557.123308.1518265649286.ref@mail.yahoo.com>
 <1569994557.123308.1518265649286@mail.yahoo.com>
Message-ID: <CAMt7G9RZkwxCAmX6QEsABTJxZsb9nVndNKK6JnOtbFzn3DK5rw@mail.gmail.com>

>   When running SlackBuild scripts for x86-64 installations, the optimization
> flags are -O2 -fPIC.  Would there be any advantage to adding flags depending
> on the processor used?  If so, is there any convenient way to do this in the
> SlackBuild script?

Hi Ira,

The traditional answer is that tuning for the specific processor
(-march=native) doesn't make much difference on x86_64.

Changing the compiler optimisation from -O2 to -O3 might plausibly
make a measurable difference, depending on the specific package.
Slackware traditionally uses -O2, which reflects Patrick's
long-standing preference for stability over performance. SBo follows
that precedent. Most other distros mostly use -O3, fwiw. There are a
few packages in both Slackware and SBo (where -O2 is buggy, or not
recommended upstream, or it's difficult to force -O2) that use
something else.

It would be very interesting if someone did some carefully performed
up-to-date benchmarks to see what difference there really is. Until
someone gives us some numbers, we see more advantage in keeping the
scripts (mostly) consistent.  There isn't any convenient way of
changing the flags -- but, like anything else, if someone made a
really really good case, we might be open to a rethink.

Thanks
-D.

From andreas.guldstrand at gmail.com  Sat Feb 10 23:02:10 2018
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Sun, 11 Feb 2018 00:02:10 +0100
Subject: [Slackbuilds-users] Testing a script with options with
 sboinstall
In-Reply-To: <20180210193640.GE32488@n0nb.us>
References: <20180210184909.GC32488@n0nb.us>
 <f5e53089-f0c6-0cbf-e738-f1ee1e9c2684@slackbuilds.org>
 <20180210193640.GE32488@n0nb.us>
Message-ID: <CAEQ5t83NvNRFGcru2gKR=r+Z-iinqDyi1xG6GVKKpqTR1Ccbaw@mail.gmail.com>

Hi, as the current maintainer of sbotools, I can tell you both how to
test, as well as what it looks for to know to ask:

How to test:
Make use of the local overrides option described in the sboconfig(1)
or sbotools.conf(5) man-pages, namely: create a sub-directory with
your slackbuild inside it (including .info, .SlackBuild, README and
slack-desc files), named the same as your slackbuild, for instance,
using mpv as an example:

base/mpv/
base/mpv/mpv.info
base/mpv/mpv.SlackBuild
base/mpv/README
base/mpv/slack-desc

Then point the local-overrides option to the base/ directory:
  # sboconfig -o /path/to/base

And then you should be able to sboinstall the slackbuild even before
it gets submitted to slackbuilds.org


How to make it ask the user to set options:
In the README make sure you have text of the form FOO=something
That's really all it looks for. A bunch of capital letters (or
numbers) followed by an equal sign and some text afterwards. No
whitespace.

Hope this helps / Andreas

From n0nb at n0nb.us  Sun Feb 11 00:13:32 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 10 Feb 2018 18:13:32 -0600
Subject: [Slackbuilds-users] Testing a script with options with
 sboinstall
In-Reply-To: <CAEQ5t83NvNRFGcru2gKR=r+Z-iinqDyi1xG6GVKKpqTR1Ccbaw@mail.gmail.com>
References: <20180210184909.GC32488@n0nb.us>
 <f5e53089-f0c6-0cbf-e738-f1ee1e9c2684@slackbuilds.org>
 <20180210193640.GE32488@n0nb.us>
 <CAEQ5t83NvNRFGcru2gKR=r+Z-iinqDyi1xG6GVKKpqTR1Ccbaw@mail.gmail.com>
Message-ID: <20180211001332.GF32488@n0nb.us>

* On 2018 10 Feb 17:03 -0600, Andreas Guldstrand wrote:
> Hi, as the current maintainer of sbotools, I can tell you both how to
> test, as well as what it looks for to know to ask:

Thanks, Andreas.

That worked perfectly for testing.  Your explanation is very much
appreciated.

- Nate

-- 

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

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180210/de2eb79c/attachment.asc>

From kjhambrick at gmail.com  Sun Feb 11 12:44:15 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 11 Feb 2018 06:44:15 -0600
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
Message-ID: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>

Andzej --

Just a heads up ...

Intel has pulled intel-microcode Version 20180108 and they've reverted to
version 20171117.

This causes download fail on the link on the SlackBuilds Page.

Unified diff on the intel-microcode.info files is below my sig.

Otherwise, all I did was change the VERSION= Line in the
intel-microcode.SlackBuild file.

Thanks for all the SlackBuilds !

-- kjh

# diff -Naur intel-microcode~01.info intel-microcode.info

--- intel-microcode~01.info     2018-01-10 12:34:17.644304756 -0600
+++ intel-microcode.info        2018-02-10 02:50:27.764732671 -0600
@@ -1,8 +1,8 @@
 PRGNAM="intel-microcode"
-VERSION="20180108"
+VERSION="20171117"
 HOMEPAGE="https://downloadcenter.intel.com/"
-DOWNLOAD="https://downloadmirror.intel.com/27431/eng/microcode-20180108.tgz
"
-MD5SUM="871df55f0ab010ee384dabfc424f2c12"
+DOWNLOAD="https://downloadmirror.intel.com/27431/eng/microcode-20171117.tgz
"
+MD5SUM="b294245d1f7f6c20f01edba53185f258"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180211/46093061/attachment.html>

From kjhambrick at gmail.com  Sun Feb 11 12:51:52 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 11 Feb 2018 06:51:52 -0600
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
In-Reply-To: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
References: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
Message-ID: <CANBHt+Pd53jJJOgu=qJvxTPUyvNgv8wpWX-U7Qqj_+RWH+ogKQ@mail.gmail.com>

Andrzej --

Oops !

The 'old link' in the intel-microcode.info file does not work either.

-- kjh

On Sun, Feb 11, 2018 at 6:44 AM, Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

> Andzej --
>
> Just a heads up ...
>
> Intel has pulled intel-microcode Version 20180108 and they've reverted to
> version 20171117.
>
> This causes download fail on the link on the SlackBuilds Page.
>
> Unified diff on the intel-microcode.info files is below my sig.
>
> Otherwise, all I did was change the VERSION= Line in the
> intel-microcode.SlackBuild file.
>
> Thanks for all the SlackBuilds !
>
> -- kjh
>
> # diff -Naur intel-microcode~01.info intel-microcode.info
>
> --- intel-microcode~01.info     2018-01-10 12:34:17.644304756 -0600
> +++ intel-microcode.info        2018-02-10 02:50:27.764732671 -0600
> @@ -1,8 +1,8 @@
>  PRGNAM="intel-microcode"
> -VERSION="20180108"
> +VERSION="20171117"
>  HOMEPAGE="https://downloadcenter.intel.com/"
> -DOWNLOAD="https://downloadmirror.intel.com/27431/eng/microcode-20180108.
> tgz"
> -MD5SUM="871df55f0ab010ee384dabfc424f2c12"
> +DOWNLOAD="https://downloadmirror.intel.com/27431/eng/microcode-20171117.
> tgz"
> +MD5SUM="b294245d1f7f6c20f01edba53185f258"
>  DOWNLOAD_x86_64=""
>  MD5SUM_x86_64=""
>  REQUIRES=""
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180211/6cd36ce7/attachment.html>

From kjhambrick at gmail.com  Sun Feb 11 12:59:58 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 11 Feb 2018 06:59:58 -0600
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
In-Reply-To: <CANBHt+Pd53jJJOgu=qJvxTPUyvNgv8wpWX-U7Qqj_+RWH+ogKQ@mail.gmail.com>
References: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
 <CANBHt+Pd53jJJOgu=qJvxTPUyvNgv8wpWX-U7Qqj_+RWH+ogKQ@mail.gmail.com>
Message-ID: <CANBHt+MBehx59s=_HjdZExA2q-6SJ1uSfiEJGaySV2azA6bfVw@mail.gmail.com>

Dang !

Sorry about the spam ...

I figured out how to extract the direct download URI from the full URI thru
the License Agreement Page.

Unified diff with the WORKING download link is below.

-- kjh

# diff -Naur intel-microcode~01.info intel-microcode.info

--- intel-microcode~01.info     2018-01-10 12:34:17.644304756 -0600
+++ intel-microcode.info        2018-02-11 06:55:39.987309384 -0600
@@ -1,8 +1,8 @@
 PRGNAM="intel-microcode"
-VERSION="20180108"
+VERSION="20171117"
 HOMEPAGE="https://downloadcenter.intel.com/"
-DOWNLOAD="https://downloadmirror.intel.com/27431/eng/microcode-20180108.tgz
"
-MD5SUM="871df55f0ab010ee384dabfc424f2c12"
+DOWNLOAD="https://downloadmirror.intel.com/27337/eng/microcode-20171117.tgz
"
+MD5SUM="b294245d1f7f6c20f01edba53185f258"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""


On Sun, Feb 11, 2018 at 6:51 AM, Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

> Andrzej --
>
> Oops !
>
> The 'old link' in the intel-microcode.info file does not work either.
>
> -- kjh
>
> On Sun, Feb 11, 2018 at 6:44 AM, Konrad J Hambrick <kjhambrick at gmail.com>
> wrote:
>
>> Andzej --
>>
>> Just a heads up ...
>>
>> Intel has pulled intel-microcode Version 20180108 and they've reverted to
>> version 20171117.
>>
>> This causes download fail on the link on the SlackBuilds Page.
>>
>> Unified diff on the intel-microcode.info files is below my sig.
>>
>> Otherwise, all I did was change the VERSION= Line in the
>> intel-microcode.SlackBuild file.
>>
>> Thanks for all the SlackBuilds !
>>
>> -- kjh
>>
>> # diff -Naur intel-microcode~01.info intel-microcode.info
>>
>> --- intel-microcode~01.info     2018-01-10 12:34:17.644304756 -0600
>> +++ intel-microcode.info        2018-02-10 02:50:27.764732671 -0600
>> @@ -1,8 +1,8 @@
>>  PRGNAM="intel-microcode"
>> -VERSION="20180108"
>> +VERSION="20171117"
>>  HOMEPAGE="https://downloadcenter.intel.com/"
>> -DOWNLOAD="https://downloadmirror.intel.com/27431/eng/
>> microcode-20180108.tgz"
>> -MD5SUM="871df55f0ab010ee384dabfc424f2c12"
>> +DOWNLOAD="https://downloadmirror.intel.com/27431/eng/
>> microcode-20171117.tgz"
>> +MD5SUM="b294245d1f7f6c20f01edba53185f258"
>>  DOWNLOAD_x86_64=""
>>  MD5SUM_x86_64=""
>>  REQUIRES=""
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180211/cd34dc5e/attachment-0001.html>

From dave at dawoodfall.net  Sun Feb 11 14:07:05 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Sun, 11 Feb 2018 14:07:05 +0000
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
In-Reply-To: <CANBHt+MBehx59s=_HjdZExA2q-6SJ1uSfiEJGaySV2azA6bfVw@mail.gmail.com>
References: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
 <CANBHt+Pd53jJJOgu=qJvxTPUyvNgv8wpWX-U7Qqj_+RWH+ogKQ@mail.gmail.com>
 <CANBHt+MBehx59s=_HjdZExA2q-6SJ1uSfiEJGaySV2azA6bfVw@mail.gmail.com>
Message-ID: <20180211140705.GB25859@Blackswan>

>Dang !
>
>Sorry about the spam ...
>
>I figured out how to extract the direct download URI from the full URI thru
>the License Agreement Page.

Should you really be bypassing the license agreement like that?


>Unified diff with the WORKING download link is below.
>
>-- kjh
>
># diff -Naur intel-microcode~01.info intel-microcode.info
>
>--- intel-microcode~01.info     2018-01-10 12:34:17.644304756 -0600
>+++ intel-microcode.info        2018-02-11 06:55:39.987309384 -0600
>@@ -1,8 +1,8 @@
> PRGNAM="intel-microcode"
>-VERSION="20180108"
>+VERSION="20171117"
> HOMEPAGE="https://downloadcenter.intel.com/"
>-DOWNLOAD="https://downloadmirror.intel.com/27431/eng/microcode-20180108.tgz
>"
>-MD5SUM="871df55f0ab010ee384dabfc424f2c12"
>+DOWNLOAD="https://downloadmirror.intel.com/27337/eng/microcode-20171117.tgz
>"
>+MD5SUM="b294245d1f7f6c20f01edba53185f258"
> DOWNLOAD_x86_64=""
> MD5SUM_x86_64=""
> REQUIRES=""
>
>
>On Sun, Feb 11, 2018 at 6:51 AM, Konrad J Hambrick <kjhambrick at gmail.com>
>wrote:
>
>> Andrzej --
>>
>> Oops !
>>
>> The 'old link' in the intel-microcode.info file does not work either.
>>
>> -- kjh
>>
>> On Sun, Feb 11, 2018 at 6:44 AM, Konrad J Hambrick <kjhambrick at gmail.com>
>> wrote:
>>
>>> Andzej --
>>>
>>> Just a heads up ...
>>>
>>> Intel has pulled intel-microcode Version 20180108 and they've reverted to
>>> version 20171117.
>>>
>>> This causes download fail on the link on the SlackBuilds Page.
>>>
>>> Unified diff on the intel-microcode.info files is below my sig.
>>>
>>> Otherwise, all I did was change the VERSION= Line in the
>>> intel-microcode.SlackBuild file.
>>>
>>> Thanks for all the SlackBuilds !
>>>
>>> -- kjh
>>>
>>> # diff -Naur intel-microcode~01.info intel-microcode.info
>>>
>>> --- intel-microcode~01.info     2018-01-10 12:34:17.644304756 -0600
>>> +++ intel-microcode.info        2018-02-10 02:50:27.764732671 -0600
>>> @@ -1,8 +1,8 @@
>>>  PRGNAM="intel-microcode"
>>> -VERSION="20180108"
>>> +VERSION="20171117"
>>>  HOMEPAGE="https://downloadcenter.intel.com/"
>>> -DOWNLOAD="https://downloadmirror.intel.com/27431/eng/
>>> microcode-20180108.tgz"
>>> -MD5SUM="871df55f0ab010ee384dabfc424f2c12"
>>> +DOWNLOAD="https://downloadmirror.intel.com/27431/eng/
>>> microcode-20171117.tgz"
>>> +MD5SUM="b294245d1f7f6c20f01edba53185f258"
>>>  DOWNLOAD_x86_64=""
>>>  MD5SUM_x86_64=""
>>>  REQUIRES=""
>>>
>>>
>>

>_______________________________________________
>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 kjhambrick at gmail.com  Sun Feb 11 17:49:45 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 11 Feb 2018 11:49:45 -0600
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
In-Reply-To: <20180211140705.GB25859@Blackswan>
References: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
 <CANBHt+Pd53jJJOgu=qJvxTPUyvNgv8wpWX-U7Qqj_+RWH+ogKQ@mail.gmail.com>
 <CANBHt+MBehx59s=_HjdZExA2q-6SJ1uSfiEJGaySV2azA6bfVw@mail.gmail.com>
 <20180211140705.GB25859@Blackswan>
Message-ID: <CANBHt+MkCxVwAck7GEbkkemOV-JToHjacDmDXCtavaNSucHOXg@mail.gmail.com>

Maybe not.

The DOWNLOAD= URI always did a direct download.

But I don't know whether it was bypassing or if the license agreement is a
new feature.

-- kjh


On Sun, Feb 11, 2018 at 8:07 AM, David Woodfall <dave at dawoodfall.net> wrote:

> Dang !
>>
>> Sorry about the spam ...
>>
>> I figured out how to extract the direct download URI from the full URI
>> thru
>> the License Agreement Page.
>>
>
> Should you really be bypassing the license agreement like that?
>
>
>
> Unified diff with the WORKING download link is below.
>>
>> -- kjh
>>
>> # diff -Naur intel-microcode~01.info intel-microcode.info
>>
>> --- intel-microcode~01.info     2018-01-10 12:34:17.644304756 -0600
>> +++ intel-microcode.info        2018-02-11 06:55:39.987309384 -0600
>> @@ -1,8 +1,8 @@
>> PRGNAM="intel-microcode"
>> -VERSION="20180108"
>> +VERSION="20171117"
>> HOMEPAGE="https://downloadcenter.intel.com/"
>> -DOWNLOAD="https://downloadmirror.intel.com/27431/eng/
>> microcode-20180108.tgz
>> "
>> -MD5SUM="871df55f0ab010ee384dabfc424f2c12"
>> +DOWNLOAD="https://downloadmirror.intel.com/27337/eng/
>> microcode-20171117.tgz
>> "
>> +MD5SUM="b294245d1f7f6c20f01edba53185f258"
>> DOWNLOAD_x86_64=""
>> MD5SUM_x86_64=""
>> REQUIRES=""
>>
>>
>> On Sun, Feb 11, 2018 at 6:51 AM, Konrad J Hambrick <kjhambrick at gmail.com>
>> wrote:
>>
>> Andrzej --
>>>
>>> Oops !
>>>
>>> The 'old link' in the intel-microcode.info file does not work either.
>>>
>>> -- kjh
>>>
>>> On Sun, Feb 11, 2018 at 6:44 AM, Konrad J Hambrick <kjhambrick at gmail.com
>>> >
>>> wrote:
>>>
>>> Andzej --
>>>>
>>>> Just a heads up ...
>>>>
>>>> Intel has pulled intel-microcode Version 20180108 and they've reverted
>>>> to
>>>> version 20171117.
>>>>
>>>> This causes download fail on the link on the SlackBuilds Page.
>>>>
>>>> Unified diff on the intel-microcode.info files is below my sig.
>>>>
>>>> Otherwise, all I did was change the VERSION= Line in the
>>>> intel-microcode.SlackBuild file.
>>>>
>>>> Thanks for all the SlackBuilds !
>>>>
>>>> -- kjh
>>>>
>>>> # diff -Naur intel-microcode~01.info intel-microcode.info
>>>>
>>>> --- intel-microcode~01.info     2018-01-10 12:34:17.644304756 -0600
>>>> +++ intel-microcode.info        2018-02-10 02:50:27.764732671 -0600
>>>> @@ -1,8 +1,8 @@
>>>>  PRGNAM="intel-microcode"
>>>> -VERSION="20180108"
>>>> +VERSION="20171117"
>>>>  HOMEPAGE="https://downloadcenter.intel.com/"
>>>> -DOWNLOAD="https://downloadmirror.intel.com/27431/eng/
>>>> microcode-20180108.tgz"
>>>> -MD5SUM="871df55f0ab010ee384dabfc424f2c12"
>>>> +DOWNLOAD="https://downloadmirror.intel.com/27431/eng/
>>>> microcode-20171117.tgz"
>>>> +MD5SUM="b294245d1f7f6c20f01edba53185f258"
>>>>  DOWNLOAD_x86_64=""
>>>>  MD5SUM_x86_64=""
>>>>  REQUIRES=""
>>>>
>>>>
>>>>
>>>
> _______________________________________________
>> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180211/e2d4b353/attachment.html>

From atelszewski at gmail.com  Sun Feb 11 18:54:42 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 11 Feb 2018 19:54:42 +0100
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
In-Reply-To: <CANBHt+MkCxVwAck7GEbkkemOV-JToHjacDmDXCtavaNSucHOXg@mail.gmail.com>
References: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
 <CANBHt+Pd53jJJOgu=qJvxTPUyvNgv8wpWX-U7Qqj_+RWH+ogKQ@mail.gmail.com>
 <CANBHt+MBehx59s=_HjdZExA2q-6SJ1uSfiEJGaySV2azA6bfVw@mail.gmail.com>
 <20180211140705.GB25859@Blackswan>
 <CANBHt+MkCxVwAck7GEbkkemOV-JToHjacDmDXCtavaNSucHOXg@mail.gmail.com>
Message-ID: <bb208f5e-486f-ef49-7bc4-75dfa7214725@gmail.com>

On 11/02/18 18:49, Konrad J Hambrick wrote:
> Maybe not.
> 
> The DOWNLOAD= URI always did a direct download.
> 
> But I don't know whether it was bypassing or if the license agreement is 
> a new feature.
> 
> -- kjh
> 
> 
> On Sun, Feb 11, 2018 at 8:07 AM, David Woodfall <dave at dawoodfall.net 
> <mailto:dave at dawoodfall.net>> wrote:
> 
>         Dang !
> 
>         Sorry about the spam ...
> 
>         I figured out how to extract the direct download URI from the
>         full URI thru
>         the License Agreement Page.
> 
> 
>     Should you really be bypassing the license agreement like that?

Hard to tell.

For me the border line works in the following way:
- if I can copy direct download URL from Firefox, I do it,
- otherwise, I put the link to license agreement in the DOWNLOAD=.

-- 
Best regards,
Andrzej Telszewski

From kjhambrick at gmail.com  Sun Feb 11 19:01:47 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 11 Feb 2018 13:01:47 -0600
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
In-Reply-To: <bb208f5e-486f-ef49-7bc4-75dfa7214725@gmail.com>
References: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
 <CANBHt+Pd53jJJOgu=qJvxTPUyvNgv8wpWX-U7Qqj_+RWH+ogKQ@mail.gmail.com>
 <CANBHt+MBehx59s=_HjdZExA2q-6SJ1uSfiEJGaySV2azA6bfVw@mail.gmail.com>
 <20180211140705.GB25859@Blackswan>
 <CANBHt+MkCxVwAck7GEbkkemOV-JToHjacDmDXCtavaNSucHOXg@mail.gmail.com>
 <bb208f5e-486f-ef49-7bc4-75dfa7214725@gmail.com>
Message-ID: <CANBHt+PSQTng3v-gHo=vD2=B5MWggb3nxnye5DyTjv0qgq1+7g@mail.gmail.com>

Fair enough.

Thanks for the clarification Andrzej.

-- kjh

On Sun, Feb 11, 2018 at 12:54 PM, Andrzej Telszewski <atelszewski at gmail.com>
wrote:

> On 11/02/18 18:49, Konrad J Hambrick wrote:
>
>> Maybe not.
>>
>> The DOWNLOAD= URI always did a direct download.
>>
>> But I don't know whether it was bypassing or if the license agreement is
>> a new feature.
>>
>> -- kjh
>>
>>
>> On Sun, Feb 11, 2018 at 8:07 AM, David Woodfall <dave at dawoodfall.net
>> <mailto:dave at dawoodfall.net>> wrote:
>>
>>         Dang !
>>
>>         Sorry about the spam ...
>>
>>         I figured out how to extract the direct download URI from the
>>         full URI thru
>>         the License Agreement Page.
>>
>>
>>     Should you really be bypassing the license agreement like that?
>>
>
> Hard to tell.
>
> For me the border line works in the following way:
> - if I can copy direct download URL from Firefox, I do it,
> - otherwise, I put the link to license agreement in the DOWNLOAD=.
>
> --
> Best regards,
> Andrzej Telszewski
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180211/e906d6a8/attachment-0001.html>

From andreas.guldstrand at gmail.com  Sun Feb 11 19:46:02 2018
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Sun, 11 Feb 2018 20:46:02 +0100
Subject: [Slackbuilds-users] mujs
Message-ID: <CAEQ5t83kXiD1fsnUFvy2pMaA+wNw+_PM-7ukupz18oeTWf8mVA@mail.gmail.com>

Hi Navigare [CC: SlackBuilds.org-users]

I was wondering if you would consider updating the mujs SlackBuild for
version 1.0.0 or higher?

I'm the maintainer of mpv, and it can optionally link to mujs to
support javascript enhancements, and I would like to allow users to do
that if they want to, but the version of mujs that is currently on
SlackBuilds.org is too old.

If you don't have time for maintaining the mujs SlackBuild script, I
would be willing to take it over.

Best regards / Andreas Guldstrand

From atelszewski at gmail.com  Mon Feb 12 15:10:26 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 12 Feb 2018 16:10:26 +0100
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
In-Reply-To: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
References: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
Message-ID: <5acadafd-8dde-a47d-3c8a-7510b927f11e@gmail.com>

On 11/02/18 13:44, Konrad J Hambrick wrote:
> Just a heads up ...
> 
> Intel has pulled intel-microcode Version 20180108 and they've reverted 
> to version 20171117.

Hi,

I've just sent an update.

-- 
Best regards,
Andrzej Telszewski

From aubreylegendre at gmail.com  Mon Feb 12 19:19:51 2018
From: aubreylegendre at gmail.com (Aubrey Legendre)
Date: Mon, 12 Feb 2018 13:19:51 -0600
Subject: [Slackbuilds-users] VLC build for Slackware 14.2
In-Reply-To: <9c044324-f5d9-cdf9-4a65-3cfd2d212fec@gmail.com>
References: <9c044324-f5d9-cdf9-4a65-3cfd2d212fec@gmail.com>
Message-ID: <CAAHjNPY171ACuV14Mo+2czoe3FZ9ct=54N6DyBGj0UrdvFUkbQ@mail.gmail.com>

Hey guys, I hope I'm not sending this to the wrong group, please excuse me
if it's not correct.

I have installed full version of all software for Slackware 14.2, not added
anything other than what's on the install disk.  Then I came to
slackbuilds.org to get everything needed to build VLC.  In the list of
dependencies is QT5.  I compiled it (and it's dependencies) and I think it
breaks something for QT4 that's already installed, and this disables VLC
from compiling.  Once I removed the QT5 package, then reinstalled the QT4
package from disk, and re-compiled VLC again, it works.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180212/d1d2aa61/attachment.html>

From kjhambrick at gmail.com  Mon Feb 12 20:15:57 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 12 Feb 2018 14:15:57 -0600
Subject: [Slackbuilds-users] intel-microcode version 'unbump'
In-Reply-To: <5acadafd-8dde-a47d-3c8a-7510b927f11e@gmail.com>
References: <CANBHt+N76tpqPsut4z75se-QCCDn5vbHE6+1KosS84YAL+VUGw@mail.gmail.com>
 <5acadafd-8dde-a47d-3c8a-7510b927f11e@gmail.com>
Message-ID: <CANBHt+PBVpicMbzdqXs7QJPMJyHhCiuX5iYu7adeX0Z2zJWREQ@mail.gmail.com>

Thank you Andrzej !

I imagine all the Victims of Spectre and Meltdown will be thanking you too
:)

-- kjh

On Mon, Feb 12, 2018 at 9:10 AM, Andrzej Telszewski <atelszewski at gmail.com>
wrote:

> On 11/02/18 13:44, Konrad J Hambrick wrote:
>
>> Just a heads up ...
>>
>> Intel has pulled intel-microcode Version 20180108 and they've reverted to
>> version 20171117.
>>
>
> Hi,
>
> I've just sent an update.
>
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180212/e7ee32d2/attachment.html>

From chris.willing at iinet.net.au  Mon Feb 12 22:06:07 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 13 Feb 2018 08:06:07 +1000
Subject: [Slackbuilds-users] VLC build for Slackware 14.2
In-Reply-To: <CAAHjNPY171ACuV14Mo+2czoe3FZ9ct=54N6DyBGj0UrdvFUkbQ@mail.gmail.com>
References: <9c044324-f5d9-cdf9-4a65-3cfd2d212fec@gmail.com>
 <CAAHjNPY171ACuV14Mo+2czoe3FZ9ct=54N6DyBGj0UrdvFUkbQ@mail.gmail.com>
Message-ID: <91236aa3-fd38-5cae-3035-3f56dd42f46d@iinet.net.au>

On 13/02/18 05:19, Aubrey Legendre wrote:
> Hey guys, I hope I'm not sending this to the wrong group, please excuse
> me if it's not correct.
> 
> I have installed full version of all software for Slackware 14.2, not
> added anything other than what's on the install disk.>
>From the SBo "SlackBuild Usage HOWTO" page:

"Caveat

 All of our scripts are written and tested for usage on the latest
stable release of Slackware with full installation and updated with
latest patches; ..."

The install disk was released over 18 months ago. A multitude of
official patches have been issued since then (see
http://www.slackware.com/changelog/stable.php?cpu=x86_64). Have these
updates been applied?

Without these updates also installed, you don't have the fully updated
system required. Of course many SlackBuilds will still build & run OK on
an incomplete system but looks like the VLC build needs an up to date
system.


>Then I came to
> slackbuilds.org <http://slackbuilds.org> to get everything needed to
> build VLC.? In the list of dependencies is QT5.? I compiled it (and it's
> dependencies) and I think it breaks something for QT4 that's already
> installed, and this disables VLC from compiling.? Once I removed the QT5
> package, then reinstalled the QT4 package from disk, and re-compiled VLC
> again, it works.
> 
I guess this is a tip for those building on an incomplete system but the
best advice would really be to fully update the installation first. Odd
workarounds like this should not then be necessary.

Apart from that, many of the missing updates are security related and,
without them, your system would be pretty unsafe at the moment.

chris

From timcowchip at gorge.net  Mon Feb 12 23:21:35 2018
From: timcowchip at gorge.net (Chris Farrell)
Date: Mon, 12 Feb 2018 15:21:35 -0800
Subject: [Slackbuilds-users] conky version bump
Message-ID: <20180212152135.5543a0d4@slack.gorge.net>

https://github.com/brndnmtthws/conky/pull/455
This bug is fixed with version 1.10.8. It isn't a problem for conky on
the desktop, but you pipe conky to i3status or lemonbar, version 1.10.7
won't work properly.
 

From matteo.bernardini at gmail.com  Thu Feb 15 08:09:39 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 15 Feb 2018 09:09:39 +0100
Subject: [Slackbuilds-users] ANNOUNCE: Qemu SBo script follows even
 branch stable releases
In-Reply-To: <CAPsDuS7qGNBU0cVK6=388kT1jVF1BrAgWteMJ-gb5_c1py9pSA@mail.gmail.com>
References: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>
 <117a3614-543c-1a9f-320d-d95062ea0ca4@gmail.com>
 <debec4f5-2f7b-4df9-1347-529e3d85755e@gmail.com>
 <8b4c1544-979a-7a42-d078-89f566a34058@gmail.com>
 <CAPsDuS7qGNBU0cVK6=388kT1jVF1BrAgWteMJ-gb5_c1py9pSA@mail.gmail.com>
Message-ID: <CAPsDuS7DFEVK1yx-WjuZ7L21OHWcntnnb35vVMzemsMyS2P1Pw@mail.gmail.com>

2018-01-29 21:16 GMT+01:00 Matteo Bernardini <matteo.bernardini at gmail.com>:
> I think those bugs were addressed in the 2.11.0 release first. I think
> they updated 2.10.x for whoever can't update it, but reading the
> following statement on their blogs I assume 2.11.x is the latest
> stable release
>
> https://www.qemu.org/2018/01/04/spectre/

BTW, 2.11.1 is out today with various CVE fixes and new IBRS versions
of the intel emulated cpus to mitigate spectre v1

https://download.qemu.org/qemu-2.11.1.tar.xz
https://git.qemu.org/?p=qemu.git;a=log;h=refs/heads/stable-2.11
https://www.qemu.org/2018/02/14/qemu-2-11-1-and-spectre-update/

Matteo

From z.coldplayer at gmail.com  Fri Feb 16 08:29:14 2018
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Fri, 16 Feb 2018 12:29:14 +0400
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
Message-ID: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>

With the forthcoming of Slackware 15.0, I have been nostalgic of the
days when I tried crazy thing with my Slackbox. One of those was using
BSD's ports and portage within Slackware. It was a succees and a
failure too. In those times, I was not using slackbuilds.org.
The big question:::
Is it worthwhile for a ports/portage/pacman like package manager for
Slackware that manages both binary and source packages?


It could be tool on top of pkgtool and sbopkg.

What is your opinion?

From noryungi at gmail.com  Fri Feb 16 10:11:30 2018
From: noryungi at gmail.com (Noryungi)
Date: Fri, 16 Feb 2018 11:11:30 +0100
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
Message-ID: <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>

If you go that way, may I draw your attention to the fact that NetBSD
pkgsrc exists and works very well under Slackware?

Why reinvent the wheel?

On Feb 16, 2018 09:29, "Jheengut Pritvi" <z.coldplayer at gmail.com> wrote:

> With the forthcoming of Slackware 15.0, I have been nostalgic of the
> days when I tried crazy thing with my Slackbox. One of those was using
> BSD's ports and portage within Slackware. It was a succees and a
> failure too. In those times, I was not using slackbuilds.org.
> The big question:::
> Is it worthwhile for a ports/portage/pacman like package manager for
> Slackware that manages both binary and source packages?
>
>
> It could be tool on top of pkgtool and sbopkg.
>
> What is your opinion?
> _______________________________________________
> 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/20180216/ae436725/attachment.html>

From dickson.tim at googlemail.com  Fri Feb 16 10:38:58 2018
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Fri, 16 Feb 2018 10:38:58 +0000
Subject: [Slackbuilds-users] lilo
Message-ID: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>

hi all, this may be off-topic,? as lilo comes with slackware, but I have 
created a patch to allow lilo to work with nvme disks. I am working on 
patching liloconf? to do the same.there are 2 questions I have, as lilo 
is "no longer developed" - but works just fine - apart from for nvme 
disks :-)
1. what is the best way of seeing if patrick is interested in the patch, and
2. is anyone interested in testing the patch?
At the moment I have patched the source for lilo, and after manually 
configuring the lilo.conf it works for me, but I only have 1 nvme disk, 
so am not sure how it presents for multiple nvme "disks".
a quick
dd if=/dev/nvme0n1 bs=512 count=1|grep LILO
 ?comes up with a match. where previously I had to use sys/extlinux as 
lilo refused to work.
specifically if someone has more than 1 nvme drive i am interested in 
the output from
cat /proc/devices
 ?and
cat /proc/partitions

many thanks, Tim

From didier at slint.fr  Fri Feb 16 11:00:58 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 16 Feb 2018 12:00:58 +0100
Subject: [Slackbuilds-users] lilo
In-Reply-To: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
References: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
Message-ID: <1eae8282-1bac-1656-075e-81a9167f6aff@slint.fr>

Hello Tim,

Le 16/02/2018 ? 11:38, Tim Dickson a ?crit :
> hi all, this may be off-topic,  as lilo comes with slackware, but I
> have created a patch to allow lilo to work with nvme disks. I am
> working on patching liloconf to do the same.there are 2 questions I
> have, as lilo is "no longer developed" - but works just fine - apart
> from for nvme disks :
> 1. what is the best way of seeing if patrick is interested in the
> patch

Just post in the Slackware forum. Ptricks reads all threads.
As an example he ecently applied in -current a patch that I have
proposed there more than one year ago and almost forgot about.

> 2. is anyone interested in testing the patch?

I am. if that works I will provide an updated package in Slint and ship
it in the next Slint ISO, among other enhancements of the installer.

> At the moment I have patched the source for lilo, and after manually
> configuring the lilo.conf it works for me, but I only have 1 nvme
> disk, so am not sure how it presents for multiple nvme "disks".
> a quick > dd if=/dev/nvme0n1 bs=512 count=1|grep LILO
> comes up with a match. where previously I had to use sys/extlinux as
> lilo refused to work. Specifically if someone has more than 1 nvme
> drive i am interested in the output from
> cat /proc/devices
>  and
> cat /proc/partitions

You can do this: Fire up a VirtualBox virtual machine with the VB
extensions and set up two NVME devices. That's how I have tested patches
for NVME handling (now applied in -current) when using UEFI, as I have
no "physical" NVME device.

Cheers, Didier

From sombragris at sombragris.org  Fri Feb 16 18:03:20 2018
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Fri, 16 Feb 2018 15:03:20 -0300
Subject: [Slackbuilds-users] libechonest: upstream site moved - tarball file
 format changed
Message-ID: <neov9.75857951da.20180216150320.4b9d291a@loli.sombragris.org>

Hi there:

I'm trying to rebuild clementine and one of its dependencies is
libechonest.

1. Bear in mind that the software seems to be available here and not at
the url provided in SBo:

https://github.com/lfranchi/libechonest

2. The tarball format is now tar.gz and not tar.bz2 as previously
expected.

Thanks


Eduardo

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

From matteo.bernardini at gmail.com  Fri Feb 16 18:17:30 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 16 Feb 2018 19:17:30 +0100
Subject: [Slackbuilds-users] libechonest: upstream site moved - tarball
 file format changed
In-Reply-To: <neov9.75857951da.20180216150320.4b9d291a@loli.sombragris.org>
References: <neov9.75857951da.20180216150320.4b9d291a@loli.sombragris.org>
Message-ID: <CAPsDuS66csru32hMPmW=xhQ2mCzR0imBDU4AgHwaHVGdU5EDpQ@mail.gmail.com>

2018-02-16 19:03 GMT+01:00 Eduardo Sanchez <sombragris at sombragris.org>:
> Hi there:
>
> I'm trying to rebuild clementine and one of its dependencies is
> libechonest.
>
> 1. Bear in mind that the software seems to be available here and not at
> the url provided in SBo:
>
> https://github.com/lfranchi/libechonest
>
> 2. The tarball format is now tar.gz and not tar.bz2 as previously
> expected.

Hi Eduardo,

I provided an alternative donwload url and committed it in my git
branch: it should be fixed also in the main repository soon.

Matteo

From yth at ythogtha.org  Fri Feb 16 18:18:37 2018
From: yth at ythogtha.org (Ythogtha)
Date: Fri, 16 Feb 2018 19:18:37 +0100
Subject: [Slackbuilds-users] lilo
In-Reply-To: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
References: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
Message-ID: <20180216191837.26472238a12881d3079fb0b0@ythogtha.org>

> hi all, this may be off-topic,? as lilo comes with slackware, but I have 
> created a patch to allow lilo to work with nvme disks. I am working on 
> patching liloconf? to do the same.there are 2 questions I have, as lilo 
> is "no longer developed" - but works just fine - apart from for nvme 
> disks :-)
> 1. what is the best way of seeing if patrick is interested in the patch, and
> 2. is anyone interested in testing the patch?
> At the moment I have patched the source for lilo, and after manually 
> configuring the lilo.conf it works for me, but I only have 1 nvme disk, 
> so am not sure how it presents for multiple nvme "disks".
> a quick
> dd if=/dev/nvme0n1 bs=512 count=1|grep LILO
>  ?comes up with a match. where previously I had to use sys/extlinux as 
> lilo refused to work.
> specifically if someone has more than 1 nvme drive i am interested in 
> the output from
> cat /proc/devices
>  ?and
> cat /proc/partitions
> 
> many thanks, Tim

	From what I've read, it seems that Patrick is mostly the de facto
maintainer of lilo because no other distribution seems to really use it anymore.
	This nvme problem is really the only one that had bothered me recently,
and I didn't dig enough to find a solution, but I am very glad that you did ! My
work laptop has an nvme main disk, and I had to put a /boot partition on the
secondary non-nvme disk for lilo to work.

	So, I, for one, would be ok - and happy - to test your patch, although
not on a real 2-nvme system, but on 2 nvme systems ;)

	Maybe, for easy testing purposes, you could create some sort of
lilo-nvme SlackBuild ? I don't know if it is worth it, but it might make for
easier testing.

-- 
Arnaud <yth at ythogtha.org>

From rshepard at appl-ecosys.com  Fri Feb 16 18:42:15 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 16 Feb 2018 10:42:15 -0800 (PST)
Subject: [Slackbuilds-users] lilo
In-Reply-To: <20180216191837.26472238a12881d3079fb0b0@ythogtha.org>
References: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
 <20180216191837.26472238a12881d3079fb0b0@ythogtha.org>
Message-ID: <alpine.LNX.2.20.1802161040120.27723@salmo.appl-ecosys.com>

On Fri, 16 Feb 2018, Ythogtha wrote:

> This nvme problem is really the only one that had bothered me recently,
> and I didn't dig enough to find a solution, but I am very glad that you
> did ! My work laptop has an nvme main disk, and I had to put a
> /boot partition on the secondary non-nvme disk for lilo to work.

   Excuse my ignorance, but a web search did not tell me if a NVMe disk is
different from a SSD; I assume so, but aren't they both non-volitile memory
disks? Is the difference the bus: SATA vs PCI-express?

Rich



From arnaud.garcia-fernandez at laposte.net  Fri Feb 16 18:55:43 2018
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 16 Feb 2018 19:55:43 +0100
Subject: [Slackbuilds-users] lilo
In-Reply-To: <alpine.LNX.2.20.1802161040120.27723@salmo.appl-ecosys.com>
References: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
 <20180216191837.26472238a12881d3079fb0b0@ythogtha.org>
 <alpine.LNX.2.20.1802161040120.27723@salmo.appl-ecosys.com>
Message-ID: <40B8E4F6-BA12-44E0-8563-AA904F1A4C4C@laposte.net>

It's a problem of some kind of ID number which isn't recognised by lilo for nvme disks, it thinks the disk is something else and refuses to install itself there.

Le 16 f?vrier 2018 19:42:15 GMT+01:00, Rich Shepard <rshepard at appl-ecosys.com> a ?crit :
>On Fri, 16 Feb 2018, Ythogtha wrote:
>
>> This nvme problem is really the only one that had bothered me
>recently,
>> and I didn't dig enough to find a solution, but I am very glad that
>you
>> did ! My work laptop has an nvme main disk, and I had to put a
>> /boot partition on the secondary non-nvme disk for lilo to work.
>
>Excuse my ignorance, but a web search did not tell me if a NVMe disk is
>different from a SSD; I assume so, but aren't they both non-volitile
>memory
>disks? Is the difference the bus: SATA vs PCI-express?
>
>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/

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

From rshepard at appl-ecosys.com  Fri Feb 16 19:07:53 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 16 Feb 2018 11:07:53 -0800 (PST)
Subject: [Slackbuilds-users] lilo
In-Reply-To: <40B8E4F6-BA12-44E0-8563-AA904F1A4C4C@laposte.net>
References: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
 <20180216191837.26472238a12881d3079fb0b0@ythogtha.org>
 <alpine.LNX.2.20.1802161040120.27723@salmo.appl-ecosys.com>
 <40B8E4F6-BA12-44E0-8563-AA904F1A4C4C@laposte.net>
Message-ID: <alpine.LNX.2.20.1802161106410.27723@salmo.appl-ecosys.com>

On Fri, 16 Feb 2018, Arnaud wrote:

> It's a problem of some kind of ID number which isn't recognised by lilo
> for nvme disks, it thinks the disk is something else and refuses to
> install itself there.

Arnaud,

   Thanks for explaining. I've used lilo for 20+ years and have no issues
with it; I like it for its simplicity and the fact that, so far, it Just
Works.

Regards,

Rich

From dickson.tim at googlemail.com  Fri Feb 16 19:12:00 2018
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Fri, 16 Feb 2018 19:12:00 +0000
Subject: [Slackbuilds-users] lilo
In-Reply-To: <20180216191837.26472238a12881d3079fb0b0@ythogtha.org>
References: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
 <20180216191837.26472238a12881d3079fb0b0@ythogtha.org>
Message-ID: <3051578c-5111-76d6-9b33-38f160f0a5b1@googlemail.com>


On 16/02/2018 18:18, Ythogtha wrote:
>> hi all, this may be off-topic,? as lilo comes with slackware, but I have
>> created a patch to allow lilo to work with nvme disks. I am working on
>> patching liloconf? to do the same.there are 2 questions I have, as lilo
>> is "no longer developed" - but works just fine - apart from for nvme
>> disks :-)
>> 1. what is the best way of seeing if patrick is interested in the patch, and
>> 2. is anyone interested in testing the patch?
>> At the moment I have patched the source for lilo, and after manually
>> configuring the lilo.conf it works for me, but I only have 1 nvme disk,
>> so am not sure how it presents for multiple nvme "disks".
>> a quick
>> dd if=/dev/nvme0n1 bs=512 count=1|grep LILO
>>   ?comes up with a match. where previously I had to use sys/extlinux as
>> lilo refused to work.
>> specifically if someone has more than 1 nvme drive i am interested in
>> the output from
>> cat /proc/devices
>>   ?and
>> cat /proc/partitions
>>
>> many thanks, Tim
> 	From what I've read, it seems that Patrick is mostly the de facto
> maintainer of lilo because no other distribution seems to really use it anymore.
> 	This nvme problem is really the only one that had bothered me recently,
> and I didn't dig enough to find a solution, but I am very glad that you did ! My
> work laptop has an nvme main disk, and I had to put a /boot partition on the
> secondary non-nvme disk for lilo to work.
>
> 	So, I, for one, would be ok - and happy - to test your patch, although
> not on a real 2-nvme system, but on 2 nvme systems ;)
>
> 	Maybe, for easy testing purposes, you could create some sort of
> lilo-nvme SlackBuild ? I don't know if it is worth it, but it might make for
> easier testing.
>
basically it would just be the existing slackware build with the extra 
patches applied.
 ?I have a test qemu virtual machine with up to 3 nvme drives on it, as 
well as a single real nvme drive.
to Richard Shepard.? nvme drives use the pcie bus instead of sata (and 
so can work up to 3 times faster).
Amaude is correct. nvme disks have device macjor 259, and minor number 
starts at 0 and goes up one at a time, as you add partitions or opther 
nvme devices. My patch increases the size of the block device table, so 
that nvme devices (typically device 252) are visible in the table, and 
if an nvme device is present, it allows the? 259 major device to be used 
by lilo.? I still have to work on liloconfig, but if I find somewhere I 
can use online I can post the current patch for those interested. PS. 
usuall disclaimer. it works for me YMMV. don't test on real system.

From didier at slint.fr  Fri Feb 16 19:17:47 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 16 Feb 2018 20:17:47 +0100
Subject: [Slackbuilds-users] lilo
In-Reply-To: <3051578c-5111-76d6-9b33-38f160f0a5b1@googlemail.com>
References: <d64e444b-0e79-fe57-945b-83c7af69fed7@googlemail.com>
 <20180216191837.26472238a12881d3079fb0b0@ythogtha.org>
 <3051578c-5111-76d6-9b33-38f160f0a5b1@googlemail.com>
Message-ID: <6db6d85f-69b0-735d-f5e4-f757f7d96e1f@slint.fr>

Le 16/02/2018 ? 20:12, Tim Dickson a ?crit?:
I still have to work on liloconfig, but if I find somewhere I can use online I can post the current patch for those interested.

If you send me just the patch for lilo itself I can test it.

Didier 

From willysr at slackbuilds.org  Sat Feb 17 01:02:54 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 17 Feb 2018 08:02:54 +0700
Subject: [Slackbuilds-users] Updates - 20180217.1
Message-ID: <3d7687a2-e871-9dac-1296-ea1f44f12796@slackbuilds.org>

Hi folks,

We have another busy week and we have some interesting update on this batch:
- LibreOffice is now sync with libreoffice at 6.0.1
- wine is updated  to 3.0
- postgresql is updated to 10.2
- intel-microcode is reverted to previous release after upstream recall
- vlc is updated to 3.0.0
- rust is updated to 1.24.0
- google-earth is updated to 7.3.1.4507
- skypeforlinux is updated to 8.15.0.4

Patrick has pushed a new GCC and Kernel in Slackware{64} 14.2 to support
full mitigation against Spectre v2. Please make sure to upgrade to that
version if you haven't done so.

Welcome to the Year of the Earth Dog according to the Chinese Calendar


Sat Feb 17 00:43:50 UTC 2018
academic/aliview: Added (Alignment viewer and editor).
academic/genius: Updated for version 1.0.23.
academic/qcl: Added (A Programming Language for Quantum Computers).
desktop/dunst: Updated for version 1.3.1, make cleanup
desktop/jgmenu: Updated for version 0.8.1.
desktop/kwalletcli: Updated for version 3.01.
desktop/obbrowser: Updated for version 0.09.
desktop/oranchelo-icon-theme: Updated for version 0.7.5.7.
development/Sphinx: Updated for version 1.6.7.
development/bas55: Updated for version 1.13.
development/d-tools: Updated for version 2.078.3
development/dmd: Updated for version 2.078.3
development/dwarf: Fixed md5sum.
development/eclim: Updated for version 2.7.2.
development/extra-cmake-modules: Updated for version 5.43.0.
development/jupyter-ipykernel: Updated for version 4.8.1.
development/kotlin: Updated for version 1.2.21.
development/obnc: Updated for version 0.11.1.
development/pkgconf: Updated for version 1.4.2.
development/rust: Updated for version 1.24.0.
development/tanya: Updated for version 0.7.8
development/universal-ctags: Updated for version 30ce6ee
games/Genesis-Plus-GX: Updated for version 2018.01.31_726b711.
games/crispy-doom: Updated for version 5.1.
games/cyphesis: Patched to build with postgresql-10.2.
games/instead: Updated for version 3.2.0.
games/javacpc: Updated for version 2.9.6.
games/nethack: Switch to i586, fix maintainer typo.
gis/gj2ascii: Added (render spatial vectors as ASCII).
gis/google-earth: Updated for version 7.3.1.4507.
gis/gpxsee: Added (GPX viewer and analyzer).
gis/openorienteering-mapper: Updated for version 0.8.0.
graphics/PureRef: Unsupported except on x86_64.
libraries/appstream-glib: Updated for version 0.7.6.
libraries/efivar: Updated for version 34.
libraries/leptonica: Updated for version 1.75.2.
libraries/libechonest: Fixed download url.
libraries/liblxi: Updated for version 1.11.
libraries/libwebp: Updated for version 0.6.1.
libraries/live555: Updated for version 2018.02.12
libraries/tbb: Updated for version 2018u2.
libraries/wxSQLite3: Updated for version 3.5.9.
misc/Publican: Added (Tool for publishing DocBook XML).
misc/discount: Updated for version 2.2.2 + new maintainer.
misc/wkhtmltox: Added (Render HTML into PDF).
multimedia/mpv: Updated for version 0.27.2, deps.
multimedia/opera-ffmpeg-codecs: Updated for version 64.0.3282.119.
multimedia/sfnt2woff: Fixed md5sum.
multimedia/smplayer: Updated for version 18.2.0.
multimedia/vivaldi-codecs-ffmpeg-extra: Updated for v 64.0.3282.167.
multimedia/vlc: Updated for version 3.0.0
network/asciinema: Updated for version 2.0.0.
network/exim: Updated for version 4.90.1.
network/frostwire: Updated for version 6.6.2 + new maintainer.
network/lxi-tools: Updated for version 1.18.
network/opera-developer: Updated for version 52.0.2857.0.
network/opera: Added Terms, Privacy and EULA files.
network/qutebrowser: Updated for version 1.1.1.
network/skypeforlinux: Updated for version 8.15.0.4.
network/slimjet: Remove icons folder.
network/slimjet: Updated for version 18.0.1.0.
network/speedtest-cli: Updated for version 2.0.0.
network/vivaldi: Updated for version 1.14.1077.50.
network/xdman: Updated for version 2018.7.1.2.
network/yle-dl: Updated for version 2.31.
office/LibreOffice: Updated for version 6.0.1.1
office/krop: Updated for version 0.5.0.
office/latexdiff: Added (diff utility for LaTeX files).
office/onlyoffice-desktopeditors: Updated for version 4.8.7.392.
perl/perl-CGI-Application: Added (Framework for web-applications).
perl/perl-CSS: Added (Object oriented Cascading Style Sheets).
perl/perl-Class-ISA: Added (search path for class's ISA tree).
perl/perl-DateTime-Format-DateParse: Added (Date::Parse parser).
perl/perl-File-Inplace: Added (in-place editing of files).
perl/perl-HTML-FormatText-WithLinks-AndTables: Added (HTML to Text).
perl/perl-HTML-FormatText-WithLinks: Added (HTML to text).
perl/perl-HTML-Formatter: Added (Base class for HTML formatters).
perl/perl-HTML-WikiConverter-Markdown: Added (HTML to Markdown).
perl/perl-HTML-WikiConverter: Added (Convert HTML to wiki markup).
perl/perl-Lingua-EN-Fathom: Added (readability of English text).
perl/perl-Lingua-EN-Syllable: Added (short description of app).
perl/perl-Locale-Maketext-Gettext: Added (gettext and Maketext).
perl/perl-Locale-Msgfmt: Added (Compile .po files to .mo files).
perl/perl-Locale-PO: Added (Manipulate .po from GNU gettext).
perl/perl-Params-ValidationCompiler: Updated for version 0.27.
perl/perl-String-Similarity: Added (similarity of two strings).
perl/perl-Syntax-Highlight-Engine-Kate: Added (kate highlight).
perl/perl-XML-Catalog: Added (perl library for xml catalogs).
perl/perl-XML-TreeBuilder: Added (tree of XML::Element objects).
python/alabaster: Updated for version 0.7.10.
python/babel: Updated for version 2.5.3.
python/coverage: Updated for version 4.5.1.
python/foolscap: Update md5sum.
python/imagesize: Add python3 support.
python/python-emoji: Added (emoji terminal output).
python/python3-jupyter-ipykernel: Updated for version 4.8.1.
python/python3-pexpect: Updated for version 4.4.0.
python/python3-pyzmq: Updated for version 17.0.0
python/pyzmq: Updated for version 17.0.0.
python/snowballstemmer: Add python3 support.
python/typing: Updated for version 3.6.4.
system/TLP: Updated for version 1.1 and corrected README.
system/cantarell-fonts: Updated for version 0.100.
system/dfu-util: Updated for version 0.9 + new maintainer
system/fd: Updated for version 6.3.0.
system/hack-font-ttf: Fixed SlackBuild.
system/intel-microcode: Updated for version 20171117.
system/inxi: Updated for version 2.3.56.
system/ioninja: Added (terminal emulator).
system/jpnevulator: Added (serial sniffer).
system/lynis: Updated for version 2.6.2.
system/noto-fonts: Updated for version 20180111.
system/phoronix-test-suite: Updated for version 7.8.0.
system/postgresql: Updated for version 10.2.
system/pspg: Updated for version 0.9.3.
system/ripgrep: Updated for version 0.8.0.
system/sbotools: Updated for version 2.5.
system/ttf-crosscorefonts: Updated for version 20180111.
system/wine: Updated for version 3.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From falsetti at clansco.org  Sat Feb 17 13:06:05 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Sat, 17 Feb 2018 14:06:05 +0100
Subject: [Slackbuilds-users] vlc fails
Message-ID: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>

/tmp/SBo/vlc-3.0.0/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonDataModel.so.1: undefined symbol: _ZN49vtkInformationQuadratureSchemeDefinitionVectorKeyD1Ev
Makefile:1789?: la recette pour la cible ??../modules/plugins.dat?? a ?chou?e
make[2]: *** [../modules/plugins.dat] Erreur 127
make[2]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.0/bin??

From ml at mareichelt.com  Sat Feb 17 14:30:25 2018
From: ml at mareichelt.com (Markus Reichelt)
Date: Sat, 17 Feb 2018 15:30:25 +0100
Subject: [Slackbuilds-users] python-mock up for grabs
In-Reply-To: <CANCo2a2LF_38F18T3gni+-J+D8Bh2TRaierffVKs1fGxm5EdEQ@mail.gmail.com>
References: <20150801095635.GA31122@pc21.mareichelt.com>
 <CANCo2a2LF_38F18T3gni+-J+D8Bh2TRaierffVKs1fGxm5EdEQ@mail.gmail.com>
Message-ID: <20180217143025.GA2338@pc21.mareichelt.com>

Hi Glenn,

It's been some time and I get requests to update mock from time to
time cos I'm still listed as maintainer.

Are you going to adopt mock or not?

Cos if not, it's up for grabs still/again.

Thanks.
-me

* Glenn Becker <glenn.becker at gmail.com> wrote:

> Date: Sat, 1 Aug 2015 16:57:23 -0400
> From: Glenn Becker <glenn.becker at gmail.com>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] python-mock up for grabs
> 
> I am willing to adopt.
> 
> - Glenn
> 
> <http://projecteuler.net/profile/gbecker.png>
> 
> On Sat, Aug 1, 2015 at 5:56 AM, Markus Reichelt <ml at mareichelt.com> wrote:
> 
> > Aloha!
> >
> > http://slackbuilds.org/repository/14.1/python/mock/ is up for grabs
> >
> > since v1.10.2 it's no longer a dep of allmydata-tahoe[1] but it may be
> > useful for someone else maintaining a python project with unit tests.
> 

From sombragris at sombragris.org  Sat Feb 17 15:52:06 2018
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Sat, 17 Feb 2018 12:52:06 -0300
Subject: [Slackbuilds-users] asciinema: MD5 error
Message-ID: <neov9.258647e2e8.20180217125206.7ab06079@loli.sombragris.org>

Hi there:

I use -current but I think this is general so I write to report it here.

MD5 sum for asciinema-2.0 fails in the latest SBo update.

Since the package is downloaded from GitHub, it might be one of those
shenaningans played by wget with compression, or maybe not.

Thanks

Eduardo

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

From willysr at slackbuilds.org  Sat Feb 17 15:54:21 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 17 Feb 2018 22:54:21 +0700
Subject: [Slackbuilds-users] asciinema: MD5 error
In-Reply-To: <neov9.258647e2e8.20180217125206.7ab06079@loli.sombragris.org>
References: <neov9.258647e2e8.20180217125206.7ab06079@loli.sombragris.org>
Message-ID: <b960d496-47c7-c585-6007-020025ea8de3@slackbuilds.org>

> I use -current but I think this is general so I write to report it here.
> 
> MD5 sum for asciinema-2.0 fails in the latest SBo update.
> 
> Since the package is downloaded from GitHub, it might be one of those
> shenaningans played by wget with compression, or maybe not.

Thanks
Fixed in my branch


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Sat Feb 17 16:10:50 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 17 Feb 2018 23:10:50 +0700
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
Message-ID: <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>

> /tmp/SBo/vlc-3.0.0/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonDataModel.so.1: undefined symbol: _ZN49vtkInformationQuadratureSchemeDefinitionVectorKeyD1Ev
> Makefile:1789?: la recette pour la cible ??../modules/plugins.dat?? a ?chou?e
> make[2]: *** [../modules/plugins.dat] Erreur 127
> make[2]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.0/bin??

Hi

Have you tried to rebuild all vlc dependencies?



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

From falsetti at clansco.org  Sat Feb 17 19:01:37 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Sat, 17 Feb 2018 20:01:37 +0100
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
Message-ID: <20180217200137.7b9b38ac2fa1db20586ee0e6@clansco.org>

On Sat, 17 Feb 2018 23:10:50 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:


> 
> Hi
> 
> Have you tried to rebuild all vlc dependencies?
oups, sorry, no
> 
> -- 
> Willy Sudiarto Raharjo
> 

From chris.willing at iinet.net.au  Sun Feb 18 00:47:21 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Sun, 18 Feb 2018 10:47:21 +1000
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
Message-ID: <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>

On 18/02/18 02:10, Willy Sudiarto Raharjo wrote:
>> /tmp/SBo/vlc-3.0.0/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonDataModel.so.1: undefined symbol: _ZN49vtkInformationQuadratureSchemeDefinitionVectorKeyD1Ev
>> Makefile:1789?: la recette pour la cible ??../modules/plugins.dat?? a ?chou?e
>> make[2]: *** [../modules/plugins.dat] Erreur 127
>> make[2]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.0/bin??
> 
> Hi
> 
> Have you tried to rebuild all vlc dependencies?
> 

About vlc dependencies - I have seen this particular error and believe
it is due to vlc building with optional opencv support (and opencv is
built with VTK support - the default). It (vlc) certainly builds OK when
opencv if _not_ present at build time.

Alternatively, opencv could be built without VTK support:
    CVVTK=no sh opencv.SlackBuild
although I haven't tried this since I think VTK is probably more
valuable to opencv's functionality than opencv is to vlc's functionality.

I'll investigate this further during the coming week.

chris

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

From z.coldplayer at gmail.com  Sun Feb 18 07:25:41 2018
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Sun, 18 Feb 2018 11:25:41 +0400
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
 <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>
Message-ID: <CAEWL1_8ax=rF2EhKyf6F-u+Sc5PTF9ZV8SWDZQRD1FEJ0+ndeA@mail.gmail.com>

But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages.

On 16 February 2018 at 14:11, Noryungi <noryungi at gmail.com> wrote:
> If you go that way, may I draw your attention to the fact that NetBSD pkgsrc
> exists and works very well under Slackware?
>
> Why reinvent the wheel?
>
> On Feb 16, 2018 09:29, "Jheengut Pritvi" <z.coldplayer at gmail.com> wrote:
>>
>> With the forthcoming of Slackware 15.0, I have been nostalgic of the
>> days when I tried crazy thing with my Slackbox. One of those was using
>> BSD's ports and portage within Slackware. It was a succees and a
>> failure too. In those times, I was not using slackbuilds.org.
>> The big question:::
>> Is it worthwhile for a ports/portage/pacman like package manager for
>> Slackware that manages both binary and source packages?
>>
>>
>> It could be tool on top of pkgtool and sbopkg.
>>
>> What is your opinion?
>> _______________________________________________
>> 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 yalhcru at gmail.com  Sun Feb 18 07:37:54 2018
From: yalhcru at gmail.com (B Watson)
Date: Sun, 18 Feb 2018 02:37:54 -0500
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <CAEWL1_8ax=rF2EhKyf6F-u+Sc5PTF9ZV8SWDZQRD1FEJ0+ndeA@mail.gmail.com>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
 <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>
 <CAEWL1_8ax=rF2EhKyf6F-u+Sc5PTF9ZV8SWDZQRD1FEJ0+ndeA@mail.gmail.com>
Message-ID: <CAN1hMuBNrm-XRHT3eKO6ZEe_9DL9qmBdjdTF2EcR7LR0pDLNDw@mail.gmail.com>

On 2/18/18, Jheengut Pritvi <z.coldplayer at gmail.com> wrote:
> But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages.

Have you looked at sbotools? It's at least somewhat similar to
ports/pkgsrc (or anyway it's been described to me that way, I haven't
actually used it).

One problem with using actual NetBSD pkgsrc on Slackware is that it
has its own package database. It doesn't know about the Slack package
db in /var/log/packages, and when you use pkgsrc to install something,
no record of it gets created in /var/log/packages.

If you google for Slackware + pkgsrc, you probably will find an ancient
set of directions that you should *not* follow (it involves replacing
most of the OS with pkgsrc equivalents, and "rm -rf /var/log/packages"
is one of the steps in the procedure...)

From falsetti at clansco.org  Sun Feb 18 08:18:54 2018
From: falsetti at clansco.org (falsetti at clansco.org)
Date: Sun, 18 Feb 2018 09:18:54 +0100
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
 <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
Message-ID: <09929c3519cf6f625d359eea270cb06c@clansco.org>

Le 2018-02-18 01:47, Christoph Willing a ?crit?:

> About vlc dependencies - I have seen this particular error and believe
> it is due to vlc building with optional opencv support (and opencv is
> built with VTK support - the default). It (vlc) certainly builds OK 
> when
> opencv if _not_ present at build time.
> 
> Alternatively, opencv could be built without VTK support:
>     CVVTK=no sh opencv.SlackBuild
> although I haven't tried this since I think VTK is probably more
> valuable to opencv's functionality than opencv is to vlc's 
> functionality.
> 
> I'll investigate this further during the coming week.
> 
> chris
> 
  I tried first ' --without-opencv ' without success, then I removed
opencv, build vlc and reinstall opencv.

Thanks Christoph!


From yth at ythogtha.org  Sun Feb 18 08:29:55 2018
From: yth at ythogtha.org (Ythogtha)
Date: Sun, 18 Feb 2018 09:29:55 +0100
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
 <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
Message-ID: <20180218092955.8a5935ef5d262a5dfaf627df@ythogtha.org>

> On 18/02/18 02:10, Willy Sudiarto Raharjo wrote:
> >> /tmp/SBo/vlc-3.0.0/bin/.libs/lt-vlc-cache-gen: symbol lookup
> >> error: /usr/lib/libvtkCommonDataModel.so.1: undefined symbol:
> >> _ZN49vtkInformationQuadratureSchemeDefinitionVectorKeyD1Ev Makefile:1789?:
> >> la recette pour la cible ??../modules/plugins.dat?? a ?chou?e make[2]: ***
> >> [../modules/plugins.dat] Erreur 127 make[2]?: on quitte le r?pertoire
> >> ??/tmp/SBo/vlc-3.0.0/bin??
> > 
> > Hi
> > 
> > Have you tried to rebuild all vlc dependencies?
> > 
> 
> About vlc dependencies - I have seen this particular error and believe
> it is due to vlc building with optional opencv support (and opencv is
> built with VTK support - the default). It (vlc) certainly builds OK when
> opencv if _not_ present at build time.
> 
> Alternatively, opencv could be built without VTK support:
>     CVVTK=no sh opencv.SlackBuild
> although I haven't tried this since I think VTK is probably more
> valuable to opencv's functionality than opencv is to vlc's functionality.
> 
> I'll investigate this further during the coming week.
> 
> chris
> 

I was exactly there.
VLC fails complaining about a missing symbol in
/usr/lib64/libvtkCommonDataModel.so.1
So I rebuilt VTK, then opencv, then VLC, and it failed again.

And VLC builds fine without opencv.
As VTK and opencv are both the latest releases available, I guess there isn't
much we can do about it here.
I haven't found any help on google for now...

-- 
Arnaud <yth at ythogtha.org>

From z.coldplayer at gmail.com  Sun Feb 18 09:52:44 2018
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Sun, 18 Feb 2018 13:52:44 +0400
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <CAN1hMuBNrm-XRHT3eKO6ZEe_9DL9qmBdjdTF2EcR7LR0pDLNDw@mail.gmail.com>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
 <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>
 <CAEWL1_8ax=rF2EhKyf6F-u+Sc5PTF9ZV8SWDZQRD1FEJ0+ndeA@mail.gmail.com>
 <CAN1hMuBNrm-XRHT3eKO6ZEe_9DL9qmBdjdTF2EcR7LR0pDLNDw@mail.gmail.com>
Message-ID: <CAEWL1_88OUHj1cuQ1T6mAav-+Q3i6EStpjQbTC476_akeGN9=A@mail.gmail.com>

On 16 February 2018 at 12:29, Jheengut Pritvi <z.coldplayer at gmail.com> wrote:

> The big question:::
> Is it worthwhile for a ports/portage/pacman like package manager for
> Slackware that manages both binary and source packages?
>
>
> It could be tool on top of pkgtool and sbopkg.


On 18 February 2018 at 11:37, B Watson <yalhcru at gmail.com> wrote:
> On 2/18/18, Jheengut Pritvi <z.coldplayer at gmail.com> wrote:
>> But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages.
>


> Have you looked at sbotools? It's at least somewhat similar to
> ports/pkgsrc (or anyway it's been described to me that way, I haven't
> actually used it).
>

Sbotools provide a big overhead in providing dependency resolution in
the form of  handling of requirements from a slackbuild?s .info file,

I am looking forward for something that can manage packages from both
Slackware and slackbuilds.org.
Slackpkg+ deals with multiple online/offline repositories.

Slax used to build a Live ISO from Slackbuilds from the Slackware Source repo.

In the long run, I am projecting to alleviate between building
packages from scratch like gentoo for an optimized built for my
SlackBoxes,
for testing purposes.


> If you google for Slackware + pkgsrc, you probably will find an ancient
> set of directions that you should *not* follow (it involves replacing
> most of the OS with pkgsrc equivalents, and "rm -rf /var/log/packages"
> is one of the steps in the procedure...)

I tried it along time back and still not fancy it that much.


My supposition  is the ability to manage packages from a singular
command from maybe multiple binary repo and source repo.


Slackware is meant to be installed as a whole.
What if you want the simplicity of Slackware and the ability to
install a small base along with with a few other packages and optimize
it with reduced dependencies for new packages. This is a lot to ask,
other distro offer some of these options but gives you too much
overhead and headache.

The answer might lie in using something else, I am unable to put it in words,..

From didier at slint.fr  Sun Feb 18 10:28:34 2018
From: didier at slint.fr (Didier Spaier)
Date: Sun, 18 Feb 2018 11:28:34 +0100
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <CAEWL1_88OUHj1cuQ1T6mAav-+Q3i6EStpjQbTC476_akeGN9=A@mail.gmail.com>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
 <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>
 <CAEWL1_8ax=rF2EhKyf6F-u+Sc5PTF9ZV8SWDZQRD1FEJ0+ndeA@mail.gmail.com>
 <CAN1hMuBNrm-XRHT3eKO6ZEe_9DL9qmBdjdTF2EcR7LR0pDLNDw@mail.gmail.com>
 <CAEWL1_88OUHj1cuQ1T6mAav-+Q3i6EStpjQbTC476_akeGN9=A@mail.gmail.com>
Message-ID: <6cffca02-b019-8ac8-dc19-9ff93231f853@slint.fr>

Hello,

Le 18/02/2018 ? 10:52, Jheengut Pritvi a ?crit :
<<snip>>> My supposition  is the ability to manage packages from a singular
> command from maybe multiple binary repo and source repo.
> 
> 
> Slackware is meant to be installed as a whole.
> What if you want the simplicity of Slackware and the ability to
> install a small base along with with a few other packages and optimize
> it with reduced dependencies for new packages. This is a lot to ask,
> other distro offer some of these options but gives you too much
> overhead and headache.
> 
> The answer might lie in using something else, I am unable to put it in words,..

A possible answer is spi from George Vlahavas:
https://github.com/gapan/spi

>From the README:

> spi (Salix Package Installer) is a command line tool that acts as a
> wrapper around slapt-get and slapt-src.
>
> It searches both package (slapt-get) and SlackBuild (slapt-get) local
> caches for software. It can also update both local caches.
>
> When installing software, if a package is available through slapt-get,
> it will install it, otherwise it will install it through slapt-src. If
> any SlackBuild dependencies are available through slapt-get, it will
> install them through slapt-get.

slap-src, slapt-get, their GUIs gslapt and sourcery and spi are included
in Salix, Slackel and Slint and usable on Slackware. All command-line
tools have associated man pages.

Several packages repositories can be used with priorities and automatic
dependencies management is provided and optional. Usual caveat for these
features: know what you are doing and be aware of the limitations of the
tools.

If you want to begin with a small base (as do Salix and Slackel) you
will need dependency information about genuine Slackware packages.
To do that, just include as SOURCE in /etc/slapt-get/slapt-getrc e.g.
this repository: http://slackware.uk/salix/x86_64/slackware-14.2/
as George has computed the deps listed in PACKAGES.TXT in the PACKAGE
REQUIRED field.

Some other repos also provided this information as e.g. the repositories
sbrepos kindly provided by Eric:
http://slackware.uk/people/alien/sbrepos/

Be aware though that deps can vary upon the environment in which the
package has been built. For instance sbrepos assume a full Slackware
installation hence only list dependencies beyond that.

And in case anyone wonders: this post is *not* a request to include
these tools in Slackware.

Have a good day,

Didier

From atelszewski at gmail.com  Sun Feb 18 14:08:45 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 18 Feb 2018 15:08:45 +0100
Subject: [Slackbuilds-users] uripareser requires graphviz
Message-ID: <ba42967e-0609-a586-62df-8745210dce50@gmail.com>

Hi,

It looks that uripareser requires graphviz in order to build.

-- 
Best regards,
Andrzej Telszewski
-------------- next part --------------
diff --git a/libraries/uriparser/uriparser.info b/libraries/uriparser/uriparser.info
index 4499490d60..fc7a0829d8 100644
--- a/libraries/uriparser/uriparser.info
+++ b/libraries/uriparser/uriparser.info
@@ -5,6 +5,6 @@ DOWNLOAD="https://github.com/uriparser/uriparser/releases/download/uriparser-0.8
 MD5SUM="80c110ec22b70570ec124563a7a63075"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES=""
+REQUIRES="graphviz"
 MAINTAINER="Matteo Bernardini"
 EMAIL="ponce at slackbuilds.org"

From matteo.bernardini at gmail.com  Sun Feb 18 14:42:30 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 18 Feb 2018 15:42:30 +0100
Subject: [Slackbuilds-users] uripareser requires graphviz
In-Reply-To: <ba42967e-0609-a586-62df-8745210dce50@gmail.com>
References: <ba42967e-0609-a586-62df-8745210dce50@gmail.com>
Message-ID: <CAPsDuS5UDbmpciD+VdDw+64EZLq3QpraK9=WZmPP7pWxFcVpRw@mail.gmail.com>

2018-02-18 15:08 GMT+01:00 Andrzej Telszewski <atelszewski at gmail.com>:
> Hi,
>
> It looks that uripareser requires graphviz in order to build.

thanks Andrzej, I removed by mistake in the update.
It will get fixed soon.

Matteo

From falsetti at clansco.org  Sun Feb 18 17:19:39 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Sun, 18 Feb 2018 18:19:39 +0100
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <09929c3519cf6f625d359eea270cb06c@clansco.org>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
 <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
 <09929c3519cf6f625d359eea270cb06c@clansco.org>
Message-ID: <20180218181939.10378a6bd467e54c8b32c8fe@clansco.org>

On Sun, 18 Feb 2018 09:18:54 +0100
falsetti at clansco.org wrote:


>   I tried first ' --without-opencv ' without success, then I removed
> opencv, build vlc and reinstall opencv.
> 
--enable-opencv=no do the job

From yalhcru at gmail.com  Sun Feb 18 20:19:44 2018
From: yalhcru at gmail.com (B Watson)
Date: Sun, 18 Feb 2018 15:19:44 -0500
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <6cffca02-b019-8ac8-dc19-9ff93231f853@slint.fr>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
 <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>
 <CAEWL1_8ax=rF2EhKyf6F-u+Sc5PTF9ZV8SWDZQRD1FEJ0+ndeA@mail.gmail.com>
 <CAN1hMuBNrm-XRHT3eKO6ZEe_9DL9qmBdjdTF2EcR7LR0pDLNDw@mail.gmail.com>
 <CAEWL1_88OUHj1cuQ1T6mAav-+Q3i6EStpjQbTC476_akeGN9=A@mail.gmail.com>
 <6cffca02-b019-8ac8-dc19-9ff93231f853@slint.fr>
Message-ID: <CAN1hMuDiOcXLM7OXg-zzdy3Lf20Zn+geVVoTr6dKY91wQuvCWQ@mail.gmail.com>

On 2/18/18, Didier Spaier <didier at slint.fr> wrote:
>>
>> When installing software, if a package is available through slapt-get,
>> it will install it, otherwise it will install it through slapt-src. If
>> any SlackBuild dependencies are available through slapt-get, it will
>> install them through slapt-get.

This sounds like a recipe for disaster. SBo packages are tested with
dependencies from SBo, this thing would install binaries from elsewhere if
it can find them?

Right now there's a guy on IRC complaining that alienbob's vlc package
segfaults, and it turns out to be because he's using SBo's qt5 instead
of alienbob's. Mixing and matching repos is the cause, in other words.

From didier at slint.fr  Sun Feb 18 20:47:28 2018
From: didier at slint.fr (Didier Spaier)
Date: Sun, 18 Feb 2018 21:47:28 +0100
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <CAN1hMuDiOcXLM7OXg-zzdy3Lf20Zn+geVVoTr6dKY91wQuvCWQ@mail.gmail.com>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
 <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>
 <CAEWL1_8ax=rF2EhKyf6F-u+Sc5PTF9ZV8SWDZQRD1FEJ0+ndeA@mail.gmail.com>
 <CAN1hMuBNrm-XRHT3eKO6ZEe_9DL9qmBdjdTF2EcR7LR0pDLNDw@mail.gmail.com>
 <CAEWL1_88OUHj1cuQ1T6mAav-+Q3i6EStpjQbTC476_akeGN9=A@mail.gmail.com>
 <6cffca02-b019-8ac8-dc19-9ff93231f853@slint.fr>
 <CAN1hMuDiOcXLM7OXg-zzdy3Lf20Zn+geVVoTr6dKY91wQuvCWQ@mail.gmail.com>
Message-ID: <4161bb3e-fc5b-c858-f5d3-77a5a69d6f2e@slint.fr>

Le 18/02/2018 ? 21:19, B Watson a ?crit?:
> On 2/18/18, Didier Spaier <didier at slint.fr> wrote:
>>>
>>> When installing software, if a package is available through slapt-get,
>>> it will install it, otherwise it will install it through slapt-src. If
>>> any SlackBuild dependencies are available through slapt-get, it will
>>> install them through slapt-get.
> 
> This sounds like a recipe for disaster.

Possibly,indeed, it it's misused. 

> SBo packages are tested with
> dependencies from SBo, this thing would install binaries from elsewhere if
> it can find them?

>From elsewhere but not from anywhere.

I did my best to warn at least the Slint users, cf.
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-get/slapt-getrc.x86_64
which links to:
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-get/README.slaptgetrc.Slint

But have all users read the docs won't happen, I know...
 
> Right now there's a guy on IRC complaining that alienbob's vlc package
> segfaults, and it turns out to be because he's using SBo's qt5 instead
> of alienbob's. Mixing and matching repos is the cause, in other words.

Yes. Incidentally that's why I ended up including in the Slint repo a
vlc-2.2.8 package built against qt4, using Eric's SlackBuild.

Cheers, Didier

From chris.willing at iinet.net.au  Mon Feb 19 00:21:48 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Mon, 19 Feb 2018 10:21:48 +1000
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
 <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
Message-ID: <2fb7fc7e-8f09-d682-3948-7d392bcdadd3@iinet.net.au>

Since this issue involves three different projects (VTK, opencv, vlc), I
don't expect a speedy resolution. I've therefore updated the SlackBuild
to disable opencv support. Experimenters can explicitly turn it back on
at build time with the OPENCV environment variable e.g.
    OPENCV=yes sh vlc.SlackBuild

At the same time (but unrelated) I've added libnfs and protobuf to
REQUIRES, adding support for NFS and Chromecast.

chris

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

From yalhcru at gmail.com  Mon Feb 19 01:20:01 2018
From: yalhcru at gmail.com (B Watson)
Date: Sun, 18 Feb 2018 20:20:01 -0500
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <2fb7fc7e-8f09-d682-3948-7d392bcdadd3@iinet.net.au>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
 <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
 <2fb7fc7e-8f09-d682-3948-7d392bcdadd3@iinet.net.au>
Message-ID: <CAN1hMuAaPekbHCWOLdFAbHAgxvTm9L5kB+YVE-0892qyh0h-Uw@mail.gmail.com>

On 2/18/18, Christoph Willing <chris.willing at iinet.net.au> wrote:
> Since this issue involves three different projects (VTK, opencv, vlc), I
> don't expect a speedy resolution. I've therefore updated the SlackBuild
> to disable opencv support. Experimenters can explicitly turn it back on
> at build time with the OPENCV environment variable e.g.
>     OPENCV=yes sh vlc.SlackBuild

For those of us who don't use vlc regularly... what vlc feature(s)
depend on opencv? From the description, is for "computer vision and
machine learning". What does vlc use it for, exactly?

Also, I notice there's an older opencv version in the repo, as
opencv-legacy. Does it work with vlc?

From willysr at slackbuilds.org  Mon Feb 19 01:39:48 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 19 Feb 2018 08:39:48 +0700
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <CAN1hMuAaPekbHCWOLdFAbHAgxvTm9L5kB+YVE-0892qyh0h-Uw@mail.gmail.com>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
 <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
 <2fb7fc7e-8f09-d682-3948-7d392bcdadd3@iinet.net.au>
 <CAN1hMuAaPekbHCWOLdFAbHAgxvTm9L5kB+YVE-0892qyh0h-Uw@mail.gmail.com>
Message-ID: <7bed9dcb-17e8-4ea2-5eb1-e600edf742b7@slackbuilds.org>

> Also, I notice there's an older opencv version in the repo, as
> opencv-legacy. Does it work with vlc?

opencv-legacy was needed by libkface since it's not working well with
latest opencv, so Christoph has decided to put opencv-legacy in order
for libkface to build properly while other scripts depending on opencv
can work with the latest version.


-- 
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/20180219/164637a2/attachment.asc>

From chris.willing at linux.com  Mon Feb 19 04:55:04 2018
From: chris.willing at linux.com (Christoph Willing)
Date: Mon, 19 Feb 2018 14:55:04 +1000
Subject: [Slackbuilds-users] vlc fails
In-Reply-To: <CAN1hMuAaPekbHCWOLdFAbHAgxvTm9L5kB+YVE-0892qyh0h-Uw@mail.gmail.com>
References: <20180217140605.8008948e5b00f2ae5a8742cf@clansco.org>
 <f0ca8b66-edb1-093a-b211-fcb59e921b4a@slackbuilds.org>
 <d4f14289-1812-d762-7719-60fb88b35c29@iinet.net.au>
 <2fb7fc7e-8f09-d682-3948-7d392bcdadd3@iinet.net.au>
 <CAN1hMuAaPekbHCWOLdFAbHAgxvTm9L5kB+YVE-0892qyh0h-Uw@mail.gmail.com>
Message-ID: <1795cbf3-1062-22c1-a2c8-25a3ee579ef5@linux.com>

On 19/02/18 11:20, B Watson wrote:
> On 2/18/18, Christoph Willing <chris.willing at iinet.net.au> wrote:
>> Since this issue involves three different projects (VTK, opencv, vlc), I
>> don't expect a speedy resolution. I've therefore updated the SlackBuild
>> to disable opencv support. Experimenters can explicitly turn it back on
>> at build time with the OPENCV environment variable e.g.
>>     OPENCV=yes sh vlc.SlackBuild
> 
> For those of us who don't use vlc regularly... what vlc feature(s)
> depend on opencv? From the description, is for "computer vision and
> machine learning". What does vlc use it for, exactly?
> 
OpenCV as well as other "computer vision and machine learning" software
often use video streams as their input. Although OpenCV has its own
video input module, it's easy to imagine that a specialised video tool
like vlc might have greater functionality that make it more attractive
as a video reader than OpenCV's native video reader. The opencv plugin
for vlc enables opencv's video processing tools to be applied directly
within vlc.

The example plugin (the one causing the build problem with the latest
vlc at the moment) is a face recognition filter. A simple non-opencv
filter that gives an idea of how these filters work is the built in
motion detection tool. Test it as follows: play a video and select
Tools->Effects & Filters, then select Video Effects tab in the resulting
window, then the Advanced tab and its Motion detect selector. See moving
parts of video highlighted. Not great for watching movies but useful for
those who find these things useful :)


> Also, I notice there's an older opencv version in the repo, as
> opencv-legacy. Does it work with vlc?
> 
Yes, good point. I'll add that to the README.

chris

From slackalaxy at gmail.com  Tue Feb 20 13:32:23 2018
From: slackalaxy at gmail.com (Petar Petrov)
Date: Tue, 20 Feb 2018 15:32:23 +0200
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
Message-ID: <CAKXpWBeJ3yM6T2XTE7tf9FkNai0B4SmvnU-gW2WZD7aJVbT8rg@mail.gmail.com>

heh... i really wish CRUX's prt-get could work with SBo

https://crux.nu/doc/prt-get%20-%20User%20Manual.html

2018-02-16 10:29 GMT+02:00 Jheengut Pritvi <z.coldplayer at gmail.com>:
> With the forthcoming of Slackware 15.0, I have been nostalgic of the
> days when I tried crazy thing with my Slackbox. One of those was using
> BSD's ports and portage within Slackware. It was a succees and a
> failure too. In those times, I was not using slackbuilds.org.
> The big question:::
> Is it worthwhile for a ports/portage/pacman like package manager for
> Slackware that manages both binary and source packages?
>
>
> It could be tool on top of pkgtool and sbopkg.
>
> What is your opinion?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From z.coldplayer at gmail.com  Tue Feb 20 18:27:49 2018
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Tue, 20 Feb 2018 22:27:49 +0400
Subject: [Slackbuilds-users] Is it worthwhile for a ports like package
 manager for Slackware
In-Reply-To: <4161bb3e-fc5b-c858-f5d3-77a5a69d6f2e@slint.fr>
References: <CAEWL1_9wberNmHVzGW2okScmTRYvg+HOqN=hoLsXkz62v3J30w@mail.gmail.com>
 <CAA_Lw38mCi47NDOLwjZ3LknPbgZ-ccehKhXUCU7ZwkzwbLvqWw@mail.gmail.com>
 <CAEWL1_8ax=rF2EhKyf6F-u+Sc5PTF9ZV8SWDZQRD1FEJ0+ndeA@mail.gmail.com>
 <CAN1hMuBNrm-XRHT3eKO6ZEe_9DL9qmBdjdTF2EcR7LR0pDLNDw@mail.gmail.com>
 <CAEWL1_88OUHj1cuQ1T6mAav-+Q3i6EStpjQbTC476_akeGN9=A@mail.gmail.com>
 <6cffca02-b019-8ac8-dc19-9ff93231f853@slint.fr>
 <CAN1hMuDiOcXLM7OXg-zzdy3Lf20Zn+geVVoTr6dKY91wQuvCWQ@mail.gmail.com>
 <4161bb3e-fc5b-c858-f5d3-77a5a69d6f2e@slint.fr>
Message-ID: <CAEWL1_9b6_rE2zGkzwGLzqPAJWReSsFkHm++ZN_ZC1_wXN94+A@mail.gmail.com>

On 19 Feb 2018 12:47 am, "Didier Spaier" <didier at slint.fr> wrote:

Le 18/02/2018 ? 21:19, B Watson a ?crit :
> On 2/18/18, Didier Spaier <didier at slint.fr> wrote:
>>>
>>> When installing software, if a package is available through slapt-get,
>>> it will install it, otherwise it will install it through slapt-src. If
>>> any SlackBuild dependencies are available through slapt-get, it will
>>> install them through slapt-get.
>
> This sounds like a recipe for disaster.

Possibly,indeed, it it's misused.

> SBo packages are tested with
> dependencies from SBo, this thing would install binaries from elsewhere if
> it can find them?

>From elsewhere but not from anywhere.

I did my best to warn at least the Slint users, cf.
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-
get/slapt-getrc.x86_64
which links to:
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-
get/README.slaptgetrc.Slint

But have all users read the docs won't happen, I know...

> Right now there's a guy on IRC complaining that alienbob's vlc package
> segfaults, and it turns out to be because he's using SBo's qt5 instead
> of alienbob's. Mixing and matching repos is the cause, in other words.

Yes. Incidentally that's why I ended up including in the Slint repo a
vlc-2.2.8 package built against qt4, using Eric's SlackBuild.

Cheers, Didier
_______________________________________________



I will look into the slapt-xxx,

Cheers Pritvi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180220/41f607fd/attachment.html>

From yth at ythogtha.org  Thu Feb 22 12:24:34 2018
From: yth at ythogtha.org (Ythogtha)
Date: Thu, 22 Feb 2018 13:24:34 +0100
Subject: [Slackbuilds-users] LibreOffice compilation fails
Message-ID: <20180222132434.22b9da46911445992ebbbda9@ythogtha.org>

Hi everybody!

	I'm almost sure I should have found how to deal with that, because it
feels like I did before, or heard of it here, but I couldn't find anything.

So I'm trying to build LibreOffice, and it fails at the point described below.
I have removed any previous LibreOffice (or libreoffice, or even openoffice)
package.
It fails wether I set USE_CCACHE=yes or USE_CCACHE=no
It fails whatever value I set to MAKEFLAGS=-j1/-j2/-j4/-j8
I have openjdk8 installed, and it fails wether I set JAVA=openjdk8 or JAVA=none.
It fails wether I set VLC=yes or VLC=no.
I have 130Go in the build and tmp directory.
I have 32Go of RAM.
None of my partitions are even near full.
And it fails always at the same place.

Here is the end of the build output
[......]
[BIN] sc
[MOD] sc
[BIN] postprocess
[GAL] arrows
[GAL] computers
[GAL] diagrams
Bootstrap exception 'component context fails to supply service
com.sun.star.ucb.UniversalContentBroker of type
com.sun.star.ucb.XUniversalContentBroker' /tmp/fs/SBo/libreoffice-6.0.1.1/solenv/gbuild/Gallery.mk:58:
recipe for target '/tmp/fs/SBo/libreoffice-6.0.1.1/workdir/Gallery/arrows.done'
failed make[1]: ***
[/tmp/fs/SBo/libreoffice-6.0.1.1/workdir/Gallery/arrows.done] Error 1 make[1]:
*** Waiting for unfinished jobs.... Bootstrap exception 'component context fails
to supply service com.sun.star.ucb.UniversalContentBroker of type
com.sun.star.ucb.XUniversalContentBroker' /tmp/fs/SBo/libreoffice-6.0.1.1/solenv/gbuild/Gallery.mk:58:
recipe for target
'/tmp/fs/SBo/libreoffice-6.0.1.1/workdir/Gallery/computers.done' failed make[1]:
*** [/tmp/fs/SBo/libreoffice-6.0.1.1/workdir/Gallery/computers.done] Error 1
Makefile:268: recipe for target 'build' failed make: *** [build] Error 2

Any insight would be greatly appreciated, thanks !

-- 
Arnaud <yth at ythogtha.org>

From chris.willing at iinet.net.au  Thu Feb 22 22:58:59 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Fri, 23 Feb 2018 08:58:59 +1000
Subject: [Slackbuilds-users] LibreOffice compilation fails
In-Reply-To: <20180222132434.22b9da46911445992ebbbda9@ythogtha.org>
References: <20180222132434.22b9da46911445992ebbbda9@ythogtha.org>
Message-ID: <d7e7c572-d01f-4e36-d5aa-2c641002765a@iinet.net.au>

On 22/02/18 22:24, Ythogtha wrote:
> Hi everybody!
> 
> 	I'm almost sure I should have found how to deal with that, because it
> feels like I did before, or heard of it here, but I couldn't find anything.
> 
> So I'm trying to build LibreOffice, and it fails at the point described below.
> I have removed any previous LibreOffice (or libreoffice, or even openoffice)
> package.
> It fails wether I set USE_CCACHE=yes or USE_CCACHE=no
> It fails whatever value I set to MAKEFLAGS=-j1/-j2/-j4/-j8
> I have openjdk8 installed, and it fails wether I set JAVA=openjdk8 or JAVA=none.
> It fails wether I set VLC=yes or VLC=no.
> I have 130Go in the build and tmp directory.
> I have 32Go of RAM.
> None of my partitions are even near full.
> And it fails always at the same place.
> 
> Here is the end of the build output
> [......]
> [BIN] sc
> [MOD] sc
> [BIN] postprocess
> [GAL] arrows
> [GAL] computers
> [GAL] diagrams
> Bootstrap exception 'component context fails to supply service
> com.sun.star.ucb.UniversalContentBroker of type
> com.sun.star.ucb.XUniversalContentBroker' /tmp/fs/SBo/libreoffice-6.0.1.1/solenv/gbuild/Gallery.mk:58:
> recipe for target '/tmp/fs/SBo/libreoffice-6.0.1.1/workdir/Gallery/arrows.done'
> failed make[1]: ***
> [/tmp/fs/SBo/libreoffice-6.0.1.1/workdir/Gallery/arrows.done] Error 1 make[1]:
> *** Waiting for unfinished jobs.... Bootstrap exception 'component context fails
> to supply service com.sun.star.ucb.UniversalContentBroker of type
> com.sun.star.ucb.XUniversalContentBroker' /tmp/fs/SBo/libreoffice-6.0.1.1/solenv/gbuild/Gallery.mk:58:
> recipe for target
> '/tmp/fs/SBo/libreoffice-6.0.1.1/workdir/Gallery/computers.done' failed make[1]:
> *** [/tmp/fs/SBo/libreoffice-6.0.1.1/workdir/Gallery/computers.done] Error 1
> Makefile:268: recipe for target 'build' failed make: *** [build] Error 2
> 
> Any insight would be greatly appreciated, thanks !
> 

I sometimes saw this type of output in my i586 test builds in a VM, even
after allocating more and more resources (RAM, disk space) to it. BTW,
no such problems with x86_64 VM, so I've long suspected some sort of
memory addressing problem.

After running with MAKEFLAGS-=-j1, I noticed a mention about virtual
memory exhaustion. This led to more resource allocation increases in the
VM, including adding more swap space but still no conclusive improvement
(sometimes failure, sometimes success).

Eventually, based on an idea which is not quite clear enough in my own
mind to try to explain, I set TMP=/var/tmp/SBo when running the
SlackBuild (overriding its TMP=/tmp/SBo). Since then the i586 VM has
built LO without problems using MAKEFLAGS=-j4 (LO versions 6.0.0.3 &
6.0.1.1).

chris

From klaatu at member.fsf.org  Thu Feb 22 23:41:27 2018
From: klaatu at member.fsf.org (Klaatu)
Date: Fri, 23 Feb 2018 12:41:27 +1300
Subject: [Slackbuilds-users] Lilypond compile failure
Message-ID: <22926e97-2d8c-1c6d-79c4-d4d2da0f034e@member.fsf.org>

Is anyone else having trouble building lilypond?

I get failure during ./configure, hinting that i need a more robust Tex
stack.

checking for epsf.tex... ./configure: line 13764: kpsewhich: command not
found
not found
checking for Cyrillic characters support in TeX... ./configure: line
13777: kpsewhich: command not found
not found

I am *not* attempting to build its docs, which the SlackBuild's README
specifically says cannot be done without installing texi2html.

The project docs mention some dependencies that don't appear in the
SlackBuild .info file, so that might be part of the problem, but the
error I'm getting doesn't really seem to correlate to Metafont or
Metapost (two things listed in the project docs but not the SlackBuild
docs).

Anybody try this lately?

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

From willysr at slackbuilds.org  Fri Feb 23 00:00:07 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 23 Feb 2018 07:00:07 +0700
Subject: [Slackbuilds-users] Lilypond compile failure
In-Reply-To: <22926e97-2d8c-1c6d-79c4-d4d2da0f034e@member.fsf.org>
References: <22926e97-2d8c-1c6d-79c4-d4d2da0f034e@member.fsf.org>
Message-ID: <1997a529-f0a1-aaf2-dd78-74338be75d7c@slackbuilds.org>

> Is anyone else having trouble building lilypond?
> 
> I get failure during ./configure, hinting that i need a more robust Tex
> stack.
> 
> checking for epsf.tex... ./configure: line 13764: kpsewhich: command not
> found
> not found
> checking for Cyrillic characters support in TeX... ./configure: line
> 13777: kpsewhich: command not found
> not found
> 
> I am *not* attempting to build its docs, which the SlackBuild's README
> specifically says cannot be done without installing texi2html.
> 
> The project docs mention some dependencies that don't appear in the
> SlackBuild .info file, so that might be part of the problem, but the
> error I'm getting doesn't really seem to correlate to Metafont or
> Metapost (two things listed in the project docs but not the SlackBuild
> docs).
> 
> Anybody try this lately?

Just to make sure
did you use "su" or "su -" ?


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

From kjhambrick at gmail.com  Fri Feb 23 10:48:40 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 23 Feb 2018 04:48:40 -0600
Subject: [Slackbuilds-users] Postfix Version 3.3.0
Message-ID: <CANBHt+NZadodvMevoKfZtHGzGhj3sX2FWWoDvWf9ZBL6GY=nmw@mail.gmail.com>

Mario --

I've been running Postfix 3.3.0 since Wednesday on Slackware64 14.2 +
Multilib.

It works fine in place of the previous Stable Version 3.2.5.

All I had to change was the default VERSION=${VERSION:-3.3.0} Line in the
postfix.SlackBuild

A new postfix.info.txt file is attached for your consideration.

I checked postfix-3.3.0.tar.gz against wietse.pgp before generating the
md5sum.

Thanks for the postfix.SlackBuild !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180223/2bf4c6ea/attachment-0001.html>
-------------- next part --------------
PRGNAM="postfix"
VERSION="3.3.0"
HOMEPAGE="http://www.postfix.org/"
DOWNLOAD="http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/postfix-3.3.0.tar.gz"
MD5SUM="26529f3fdb668482176355e90a546a11"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
REQUIRES=""
MAINTAINER="Mario Preksavec"
EMAIL="mario at slackware dot hr"

From xavier at maillard.im  Fri Feb 23 21:45:16 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Fri, 23 Feb 2018 22:45:16 +0100
Subject: [Slackbuilds-users] binary package of qt5 ?
Message-ID: <87po4vidn7.fsf@maillard.im>

Hi,

Due to bad performance on my machine, I can't build the qt5 SBo.
Can anybody gently pass me an x86_64 binary package of it ? (or a 
link to an existing one ?).

Regards
--
Xavier

From didier at slint.fr  Fri Feb 23 21:59:49 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 23 Feb 2018 22:59:49 +0100
Subject: [Slackbuilds-users] binary package of qt5 ?
In-Reply-To: <87po4vidn7.fsf@maillard.im>
References: <87po4vidn7.fsf@maillard.im>
Message-ID: <48285481-9bcd-a64a-0512-b62a32840631@slint.fr>

Hi,

Le 23/02/2018 ? 22:45, Xavier Maillard a ?crit:
> Due to bad performance on my machine, I can't build the qt5 SBo.
> Can anybody gently pass me an x86_64 binary package of it ? (or a link to an existing one ?).
In Eric Hameleers' sbrepos:
http://slackware.uk/people/alien/sbrepos/14.2/x86_64/qt5/

It has libinput and libxkbcommon as deps. In the same repo:
http://slackware.uk/people/alien/sbrepos/14.2/x86_64/libinput/
http://slackware.uk/people/alien/sbrepos/14.2/x86_64/libxkbcommon/

Or you can get one from the Salix repo:
http://slackware.uk/salix/x86_64/14.2/salix/l/

But then you would have to handle the deps yourself, as
http://slackware.uk/salix/x86_64/14.2/salix/l/qt5-5.6.1-x86_64-1gv.dep
included deps shipped in a full Slackware installation.

So if you don't have slapt-get getting Eric's package is easier.
It's also a more recent version, if that matters. 

In any case take all packages from the same repo.

Didier

From willysr at slackbuilds.org  Sat Feb 24 00:16:10 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Feb 2018 07:16:10 +0700
Subject: [Slackbuilds-users] Updates - 20180224.1
Message-ID: <b1ed1cc3-ddc5-b408-f54d-72f8c8aed5db@slackbuilds.org>

Hi all,

this would be the last update for February

We have security update in phpmyadmin and qemu, nvidia-{driver,kernel}
are updated to 390.25, and other changes in around 118 commits.

Big thanks to all maintainers and contributors for the hard work

Happy weekend

Sat Feb 24 00:01:03 UTC 2018
academic/engauge: Fixed build with openjpeg-2.3.0.
audio/audacious-aac: Update HOMEPAGE and DOWNLOAD url.
audio/audacious-cue: Update HOMEPAGE and DOWNLOAD url.
audio/audacious-ffmpeg: Update HOMEPAGE and DOWNLOAD url.
audio/rubberband: Fixed download link.
audio/tuxguitar: Updated for version 1.5.
desktop/buttonmaker: Added (dockapps).
desktop/compton: Updated for version 316eac0.
desktop/jgmenu: Updated for version 0.8.2.
desktop/mh5000: Updated for version 1.3.
desktop/oranchelo-icon-theme: Updated for version 0.7.5.8.
desktop/subtle: Update HOMEPAGE and DOWNLOAD url.
desktop/wmbutton: Added (3 button actions).
desktop/wmcpuwatch: Added (form of wmmon).
desktop/wmfishtime: Added (clock dockapp).
desktop/wmix: Added (dockapp mixer).
desktop/wmshutdown: Added (dockapp for shutdown).
desktop/wmuptime: Added (LED display of your uptime).
desktop/xxkb: Update HOMEPAGE url.
development/Sphinx: Updated for version 1.7.0.
development/atom-amd64: Updated for version 1.24.0.
development/bpython: Updated for version 0.17.1.
development/d-tools: Fixed version in .info.
development/docutils: Updated for version 0.14.
development/extra-cmake-modules: Compress manpages.
development/gcclegacy494: Updated for version 4.9.4.
development/jupyter-ipykernel: Updated for version 4.8.2.
development/jupyter-ipywidgets: Updated for version 7.1.2.
development/ripgrep: Updated for version 0.8.1.
development/robomongo: Update HOMEPAGE and DOWNLOAD url.
development/sbt: Update HOMEPAGE url.
development/zeal: Updated for version 0.6.0.
games/RetroArch: Updated for version 1.7.1.
games/bastet: Fix -current build.
games/d1x-rebirth: Update HOMEPAGE and DOWNLOAD url.
games/d2x-rebirth: Update HOMEPAGE and DOWNLOAD url.
games/doomretro: Updated for version 2.6.7.
games/exult: Updated for version 2018.02.01_c3d7afb.
games/freedoom: Update HOMEPAGE url.
games/nuvie: Updated for version 2018.01.13_1fa4044.
games/retux: Updated for version 1.3.5.
games/zdbsp: Move binary to /usr/games.
games/zennode: Move binaries to /usr/games.
gis/GMT: Updated for version 5.4.3.
gis/cartopy: Updated for version 0.16.0.
gis/gpxsee: Updated for version 5.2.
gis/navit: Fixed build.
graphics/feh: Updated for version 2.23.2.
libraries/Jinja2: Updated for version 2.10 + new maintainer.
libraries/gloox: Update HOMEPAGE and DOWNLOAD url.
libraries/leptonica: Updated for version 1.75.3.
libraries/libAfterImage: Fix DOWNLOAD url.
libraries/libfilezilla: Updated for versoin 0.12.1.
libraries/libmpeg2: Fixed download link.
libraries/libmusicbrainz3: Fixed download link.
libraries/libtorrent-rasterbar: Change compiler & build options.
libraries/libuv: Updated for version 1.19.2.
libraries/uriparser: Re-add the dependency graphviz.
multimedia/get_iplayer: Updated for version 3.12.
multimedia/l-smash: Updated for version 2.14.5.
multimedia/obs-studio: Updated for version 21.0.3
multimedia/opera-ffmpeg-codecs: Updated for version 64.0.3282.140.
multimedia/vlc: Temporarily remove default opencv support
multimedia/x265: Updated for version 2.7.
network/Pafy: Updated for version 0.5.4.
network/WireGuard: Updated for version 0.0.20180218.
network/asciinema: Fix MD5SUM.
network/basilisk: Updated for version 2018.02.14.
network/clipgrab: Updated for version 3.6.7.
network/dianara: Don't split the makepkg line.
network/dropbox: Update HOMEPAGE url.
network/filezilla: Updated for version 3.31.0.
network/gajim: Remove redundant space.
network/geoipupdate: Update HOMEPAGE url.
network/geomyidae: Updated for version v0.31.1.
network/libmaxminddb: Update HOMEPAGE url.
network/mps-youtube: Updated for version 0.2.8.
network/openntpd: Updated for version 6.2p3.
network/opera: Updated for version 51.0.2830.34.
network/phpmyadmin: Updated for version 4.7.8.
network/purple-facebook: Updated for version 0.9.5 + new maintainer.
network/qbittorrent-qt5: Updated for version 4.0.4.
network/qutebrowser: Update README and fix deps.
network/r8168: Added patch for linux-4.15 kernels.
network/shorewall-core: Updated for version 5.1.12.2.
network/shorewall6: Updated for version 5.1.12.2.
network/shorewall: Updated for version 5.1.12.2.
network/skypeforlinux: Updated for version 8.16.0.4.
network/youtube-dl: Updated for version 2018.02.11.
network/yturl: Updated for version 2.0.2.
office/abiword: fix screen flicker with gtk+3 >= 3.22.x
office/adobe-reader-fontpacks: Switch to https.
office/adobe-reader: Switch to https.
office/ganttproject: Updated for version 2.8.6.
perl/perl-Carp-Clan: Updated for version 6.06.
perl/perl-IO-Socket-SSL: Updated for version 2.056.
perl/perl-Module-Manifest: Update HOMEPAGE url.
perl/perl-Sidef: Updated for version 3.15.
python/mistune: Updated for version 0.8.3.
python/python-certifi: Updated for version 2018.1.18.
python/python-scandir: Updated for version 1.7.
python/python-urllib3: Updated for version 1.22 + New maintainer.
python/python3-jupyter-ipykernel: Updated for version 4.8.2.
python/s3cmd: Updated for version 2.0.1
system/afdko: Switch to https.
system/conky: Updated for version 1.10.8.
system/fwupd: Updated for version 1.0.5.
system/kbfs: Updated for version 1.0.41_20180221190021.
system/keybase: Updated for version 1.0.42.
system/nvidia-driver: Updated for version 390.25.
system/nvidia-kernel: Updated for version 390.25.
system/passwordsafe: Update HOMEPAGE url.
system/qemu: Updated for version 2.11.1.
system/spl-solaris: Updated for version 0.7.6.
system/virt-manager: Updated for version 1.5.0.
system/wine: Updated for version 3.1.
system/zfs-on-linux: Updated for version 0.7.6.
+--------------------------+


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

From edps.mundognu at gmail.com  Sat Feb 24 00:18:54 2018
From: edps.mundognu at gmail.com (Edinaldo)
Date: Fri, 23 Feb 2018 21:18:54 -0300
Subject: [Slackbuilds-users] binary package of qt5 ?
Message-ID: <op.zewy5sbz9z09aw@localhost>

Hello, another alternative would be the SlackOnly repository (which you  
can use if you know how to configure slackpkg++, in any case follow the  
list of links:

deps:

https://packages.slackonly.com/pub/packages/14.2-x86_64/libraries/libwacom/libwacom-0.27-x86_64-1_slonly.txz
https://packages.slackonly.com/pub/packages/14.2-x86_64/libraries/libinput/libinput-1.8.3-x86_64-2_slonly.txz
https://packages.slackonly.com/pub/packages/14.2-x86_64/libraries/libxkbcommon/libxkbcommon-0.7.1-x86_64-1_slonly.txz

* you can build all of them, and download only the qt5 package if you wish.

qt5:

https://packages.slackonly.com/pub/packages/14.2-x86_64/libraries/qt5/qt5-5.7.1-x86_64-10_slonly.txz


extra:

https://packages.slackonly.com/pub/packages/14.2-x86_64/libraries/qt5-webkit/qt5-webkit-5.7.1-x86_64-1_slonly.txz

Cheers,

Edinaldo.

From dpross1100 at msn.com  Sat Feb 24 04:43:13 2018
From: dpross1100 at msn.com (Daniel Prosser)
Date: Sat, 24 Feb 2018 04:43:13 +0000
Subject: [Slackbuilds-users] Missing Noto Sans in latest noto-fonts
Message-ID: <CY4PR22MB02942FC7504921846AB1E6A7CCC30@CY4PR22MB0294.namprd22.prod.outlook.com>

Hi Edinaldo,

I'm not sure if this is expected or not, but when I installed the latest
update of noto-fonts, it was missing Noto Sans. It had the million
variations of Noto Sans, like Noto Sans Adlam, Noto Sans Arabic, Noto
Sans Hebrew, etc., but not plain Noto Sans.


Regards,
Dan

From xavier at maillard.im  Sat Feb 24 07:28:51 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Sat, 24 Feb 2018 08:28:51 +0100
Subject: [Slackbuilds-users] binary package of qt5 ?
In-Reply-To: <op.zewy5sbz9z09aw@localhost>
References: <op.zewy5sbz9z09aw@localhost>
Message-ID: <871shalubw.fsf@maillard.im>

Hey Edinaldo,

Edinaldo <edps.mundognu at gmail.com> writes:

> Hello, another alternative would be the SlackOnly repository 
> (which you  
> can use if you know how to configure slackpkg++, in any case 
> follow the  

I never have used slackpkg but I will for sure now :)
That's pretty hard to wait 1day or so to wait for qt5 build 
end.. (if it succeed).

Anyway, thank you very much for these links.

I will try to configure slackpkg.

--
Xavier

From xavier at maillard.im  Sat Feb 24 07:35:04 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Sat, 24 Feb 2018 08:35:04 +0100
Subject: [Slackbuilds-users] binary package of qt5 ?
In-Reply-To: <48285481-9bcd-a64a-0512-b62a32840631@slint.fr>
References: <87po4vidn7.fsf@maillard.im>
 <48285481-9bcd-a64a-0512-b62a32840631@slint.fr>
Message-ID: <87y3jikfh3.fsf@maillard.im>


Didier Spaier <didier at slint.fr> writes:

> Hi,
>
> Le 23/02/2018 ? 22:45, Xavier Maillard a ?crit:
>> Due to bad performance on my machine, I can't build the qt5 
>> SBo.
>> Can anybody gently pass me an x86_64 binary package of it ? (or 
>> a link to an existing one ?).
> In Eric Hameleers' sbrepos:
> http://slackware.uk/people/alien/sbrepos/14.2/x86_64/qt5/

As a last resort, I will check his whole repo to see if I can get 
all the deps needed to install qutebrowser.

Thank you

--
Xavier

From kjhambrick at gmail.com  Sat Feb 24 11:24:14 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 24 Feb 2018 05:24:14 -0600
Subject: [Slackbuilds-users] Sphinx Version 1.7.0 build failure
Message-ID: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>

Benjamin --

I am running Slackware64 14.2 + Multilib and this morning when I attempted
to build Sphinx Version 1.7.0 I experienced a python install failure:

   Installing sphinx-autogen script to /tmp/SBo/package-Sphinx/usr/bin
   make: Entering directory '/tmp/SBo/Sphinx-1.7.0/doc'
   Traceback (most recent call last):
     File "/tmp/SBo/package-Sphinx/usr/bin/sphinx-build", line 5, in
<module>
       from pkg_resources import load_entry_point
     File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 2927, in <module>
       @_call_aside
     File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 2913, in _call_aside
       f(*args, **kwargs)
     File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 2940, in _initialize_master_working_set
       working_set = WorkingSet._build_master()
     File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 635, in _build_master
       ws.require(__requires__)
     File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 943, in require
       needed = self.resolve(parse_requirements(requirements))
     File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 829, in resolve
       raise DistributionNotFound(req, requirers)
   pkg_resources.DistributionNotFound: The 'packaging' distribution was not
found and is required by Sphinx
   Makefile:20: recipe for target 'html' failed
   make: *** [html] Error 1
   make: Leaving directory '/tmp/SBo/Sphinx-1.7.0/doc'

I hesitate to attach my full Sphinx.SlackBuild-1.7.0.log ( 212 KB ) but I
have it if you need it.

I was able to build, install and run the previous version ( Sphinx-1.6.7 )
without error.

I BELIEVE I have the REQUIRED= Packages installed.

Note that Willy's SBo Updates for today ( 2018-02-24 ) included Version
Bumps for Jinja2 ( 2.7.3 -> 2.10 ) and docutils ( 0.13.1 -> 0.14 ).

These are the REQUIRES= Packages on my System:

# ls -1d
/var/log/packages/{alabaster,babel,docutils,imagesize,Jinja2,Pygments,python-requests,six,snowballstemmer,sphinxcontrib-websupport,typing}*

  /var/log/packages/Jinja2-2.10-x86_64-1_SBo
  /var/log/packages/Pygments-2.1.3-x86_64-1_SBo
  /var/log/packages/alabaster-0.7.10-x86_64-1_SBo
  /var/log/packages/babel-2.5.3-x86_64-1_SBo
  /var/log/packages/docutils-0.14-x86_64-1_SBo
  /var/log/packages/imagesize-0.7.1-x86_64-1_SBo
  /var/log/packages/python-requests-2.18.4-x86_64-1_SBo
  /var/log/packages/six-1.11.0-x86_64-1_SBo
  /var/log/packages/snowballstemmer-1.2.1-x86_64-1_SBo
  /var/log/packages/sphinxcontrib-websupport-1.0.1-x86_64-1_SBo
  /var/log/packages/typing-3.6.4-x86_64-1_SBo


Do you have any idea what's wrong with my system ?

Thank you !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180224/10c6d1c3/attachment.html>

From kjhambrick at gmail.com  Sat Feb 24 11:37:21 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 24 Feb 2018 05:37:21 -0600
Subject: [Slackbuilds-users] Sphinx Version 1.7.0 build failure
In-Reply-To: <ce71870c-0a09-47ac-6616-25fc0e85f097@gmail.com>
References: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>
 <ce71870c-0a09-47ac-6616-25fc0e85f097@gmail.com>
Message-ID: <CANBHt+M+GpNEed+bQ707CU=LYMFwOJVFT8qY_Nb8=av3J5b9Gw@mail.gmail.com>

Thanks for the reply Dimitris.

Yes.  As I noted in my OP, I think so ...

>From Sphinx.info:

REQUIRES="alabaster babel docutils imagesize Jinja2 Pygments
python-requests six snowballstemmer sphinxcontrib-websupport typing"

And these are the Packages from the REQUIRES= List that are installed on my
machine ( here is an `ls -lad` listing this time ):

# ls -lad
/var/log/packages/{alabaster,babel,docutils,imagesize,Jinja2,Pygments,python-requests,six,snowballstemmer,sphinxcontrib-websupport,typing}*

  -rw-r--r-- 1 root root  4163 Feb 24 04:13
/var/log/packages/Jinja2-2.10-x86_64-1_SBo
  -rw-r--r-- 1 root root 28100 Jan 29 10:11
/var/log/packages/Pygments-2.1.3-x86_64-1_SBo
  -rw-r--r-- 1 root root  2090 Feb 17 05:31
/var/log/packages/alabaster-0.7.10-x86_64-1_SBo
  -rw-r--r-- 1 root root 48626 Feb 17 05:33
/var/log/packages/babel-2.5.3-x86_64-1_SBo
  -rw-r--r-- 1 root root 23969 Feb 24 04:15
/var/log/packages/docutils-0.14-x86_64-1_SBo
  -rw-r--r-- 1 root root  1408 Jan 29 09:53
/var/log/packages/imagesize-0.7.1-x86_64-1_SBo
  -rw-r--r-- 1 root root  5604 Jan 29 09:40
/var/log/packages/python-requests-2.18.4-x86_64-1_SBo
  -rw-r--r-- 1 root root  1313 Oct 22 09:47
/var/log/packages/six-1.11.0-x86_64-1_SBo
  -rw-r--r-- 1 root root  3791 Jan 29 10:00
/var/log/packages/snowballstemmer-1.2.1-x86_64-1_SBo
  -rw-r--r-- 1 root root  4515 Jan 29 10:02
/var/log/packages/sphinxcontrib-websupport-1.0.1-x86_64-1_SBo
  -rw-r--r-- 1 root root  1187 Feb 17 05:29
/var/log/packages/typing-3.6.4-x86_64-1_SBo

Note that Jinja2 and docutils were updated this morning without error
BEFORE I tried to build Sphinx 1.7.0 ...

Thanks again !

-- kjh


On Sat, Feb 24, 2018 at 5:28 AM, Dimitris Zlatanidis <d.zlatanidis at gmail.com
> wrote:

> Have you install all the requirements?
>
> On 02/24/2018 12:24 PM, Konrad J Hambrick wrote:
>
> Benjamin --
>
> I am running Slackware64 14.2 + Multilib and this morning when I attempted
> to build Sphinx Version 1.7.0 I experienced a python install failure:
>
>    Installing sphinx-autogen script to /tmp/SBo/package-Sphinx/usr/bin
>    make: Entering directory '/tmp/SBo/Sphinx-1.7.0/doc'
>    Traceback (most recent call last):
>      File "/tmp/SBo/package-Sphinx/usr/bin/sphinx-build", line 5, in
> <module>
>        from pkg_resources import load_entry_point
>      File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 2927, in <module>
>        @_call_aside
>      File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 2913, in _call_aside
>        f(*args, **kwargs)
>      File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 2940, in _initialize_master_working_set
>        working_set = WorkingSet._build_master()
>      File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 635, in _build_master
>        ws.require(__requires__)
>      File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 943, in require
>        needed = self.resolve(parse_requirements(requirements))
>      File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 829, in resolve
>        raise DistributionNotFound(req, requirers)
>    pkg_resources.DistributionNotFound: The 'packaging' distribution was
> not found and is required by Sphinx
>    Makefile:20: recipe for target 'html' failed
>    make: *** [html] Error 1
>    make: Leaving directory '/tmp/SBo/Sphinx-1.7.0/doc'
>
> I hesitate to attach my full Sphinx.SlackBuild-1.7.0.log ( 212 KB ) but I
> have it if you need it.
>
> I was able to build, install and run the previous version ( Sphinx-1.6.7 )
> without error.
>
> I BELIEVE I have the REQUIRED= Packages installed.
>
> Note that Willy's SBo Updates for today ( 2018-02-24 ) included Version
> Bumps for Jinja2 ( 2.7.3 -> 2.10 ) and docutils ( 0.13.1 -> 0.14 ).
>
> These are the REQUIRES= Packages on my System:
>
> # ls -1d /var/log/packages/{alabaster,babel,docutils,imagesize,
> Jinja2,Pygments,python-requests,six,snowballstemmer,
> sphinxcontrib-websupport,typing}*
>
>   /var/log/packages/Jinja2-2.10-x86_64-1_SBo
>   /var/log/packages/Pygments-2.1.3-x86_64-1_SBo
>   /var/log/packages/alabaster-0.7.10-x86_64-1_SBo
>   /var/log/packages/babel-2.5.3-x86_64-1_SBo
>   /var/log/packages/docutils-0.14-x86_64-1_SBo
>   /var/log/packages/imagesize-0.7.1-x86_64-1_SBo
>   /var/log/packages/python-requests-2.18.4-x86_64-1_SBo
>   /var/log/packages/six-1.11.0-x86_64-1_SBo
>   /var/log/packages/snowballstemmer-1.2.1-x86_64-1_SBo
>   /var/log/packages/sphinxcontrib-websupport-1.0.1-x86_64-1_SBo
>   /var/log/packages/typing-3.6.4-x86_64-1_SBo
>
>
> Do you have any idea what's wrong with my system ?
>
> Thank you !
>
> -- kjh
>
>
>
> _______________________________________________
> SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
> --
> Dimitris Zlatanidis
> Github: https://github.com/dslackw
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180224/3fb6ca3c/attachment.html>

From didier at slint.fr  Sat Feb 24 11:42:06 2018
From: didier at slint.fr (Didier Spaier)
Date: Sat, 24 Feb 2018 12:42:06 +0100
Subject: [Slackbuilds-users] Sphinx Version 1.7.0 build failure
In-Reply-To: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>
References: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>
Message-ID: <9ec00ecd-1371-9cd3-61d8-838433f48ec5@slint.fr>

Hello,

Le 24/02/2018 ? 12:24, Konrad J Hambrick a ?crit?:
> Benjamin --
> 
> I am running Slackware64 14.2 + Multilib and this morning when I attempted
> to build Sphinx Version 1.7.0 I experienced a python install failure:
> 
> ?? Installing sphinx-autogen script to /tmp/SBo/package-Sphinx/usr/bin
> ?? make: Entering directory '/tmp/SBo/Sphinx-1.7.0/doc'
> ?? Traceback (most recent call last):
> ???? File "/tmp/SBo/package-Sphinx/usr/bin/sphinx-build", line 5, in <module>
> ?????? from pkg_resources import load_entry_point
> ???? File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 2927, in <module>
> ?????? @_call_aside
> ???? File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 2913, in _call_aside
> ?????? f(*args, **kwargs)
> ???? File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 2940, in _initialize_master_working_set
> ?????? working_set = WorkingSet._build_master()
> ???? File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 635, in _build_master
> ?????? ws.require(__requires__)
> ???? File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 943, in require
> ?????? needed = self.resolve(parse_requirements(requirements))
> ???? File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 829, in resolve
> ?????? raise DistributionNotFound(req, requirers)
> ?? pkg_resources.DistributionNotFound: The 'packaging' distribution was not found and is required by Sphinx
> ?? Makefile:20: recipe for target 'html' failed
> ?? make: *** [html] Error 1
> ?? make: Leaving directory '/tmp/SBo/Sphinx-1.7.0/doc'
> 
> I hesitate to attach my full Sphinx.SlackBuild-1.7.0.log ( 212 KB ) but I have it if you need it.
> 
> I was able to build, install and run the previous version ( Sphinx-1.6.7 ) without error.
> 
> I BELIEVE I have the REQUIRED= Packages installed.?
> 
> Note that Willy's SBo Updates for today ( 2018-02-24 ) included Version Bumps for Jinja2 ( 2.7.3 -> 2.10 ) and docutils ( 0.13.1 -> 0.14 ).
> 
> These are the REQUIRES= Packages on my System:
> 
> # ls -1d /var/log/packages/{alabaster,babel,docutils,imagesize,Jinja2,Pygments,python-requests,six,snowballstemmer,sphinxcontrib-websupport,typing}*
> 
> ? /var/log/packages/Jinja2-2.10-x86_64-1_SBo
> ? /var/log/packages/Pygments-2.1.3-x86_64-1_SBo
> ? /var/log/packages/alabaster-0.7.10-x86_64-1_SBo
> ? /var/log/packages/babel-2.5.3-x86_64-1_SBo
> ? /var/log/packages/docutils-0.14-x86_64-1_SBo
> ? /var/log/packages/imagesize-0.7.1-x86_64-1_SBo
> ? /var/log/packages/python-requests-2.18.4-x86_64-1_SBo
> ? /var/log/packages/six-1.11.0-x86_64-1_SBo
> ? /var/log/packages/snowballstemmer-1.2.1-x86_64-1_SBo
> ? /var/log/packages/sphinxcontrib-websupport-1.0.1-x86_64-1_SBo
> ? /var/log/packages/typing-3.6.4-x86_64-1_SBo
> 
> 
> Do you have any idea what's wrong with my system ?

Not sure that helps but I installed virtualenv-15.1.0 then used pip to install Sphinx.

Here:
didier[~/ENV/bin]$ ./pip list --format=legacy
alabaster (0.7.10)
argh (0.26.2)
Babel (2.5.3)
backports-abc (0.5)
beautifulsoup4 (4.4.1)
ccsm (0.9.13.1)
certifi (2018.1.18)
chardet (3.0.4)
compizconfig-python (0.9.13.1)
configparser (3.5.0)
cupshelpers (1.0)
Cython (0.23.4)
docutils (0.14)
getmail (4.54.0)
idna (2.6)
imagesize (1.0.0)
include-server (3.1)
isc (1.0)
Jinja2 (2.10)
livereload (2.5.1)
lxml (3.6.0)
M2Crypto (0.23.0)
MarkupSafe (1.0)
mercurial (4.3.1)
netsnmp-python (1.0a1)
numpy (1.11.0)
packaging (16.8)
pathtools (0.1.2)
Pillow (3.0.0)
pip (9.0.1)
port-for (0.3.1)
pssh (2.3.1)
pycups (1.9.73)
pycurl (7.43.0)
Pygments (2.2.0)
pygobject (3.18.2)
pyparsing (2.2.0)
Pyrex (0.9.9)
python-libpisock (0.12.5)
python-sane (2.8.2)
pytz (2018.3)
pyxdg (0.25)
PyYAML (3.12)
requests (2.18.4)
scons (2.4.1)
setproctitle (1.1.10)
setuptools (38.5.1)
simpleconfig (0.2)
singledispatch (3.4.0.3)
six (1.11.0)
snowballstemmer (1.2.1)
Sphinx (1.7.0)
sphinx-autobuild (0.7.1)
sphinxcontrib-websupport (1.0.1)
tornado (4.5.3)
transifex-client (0.12.2)
txt2tags (2.6)
typing (3.6.4)
urlgrabber (3.9.1)
urllib3 (1.22)
urwid (1.0.3)
vboxapi (1.0)
virtualenv (15.1.0)
watchdog (0.8.3)
wheel (0.30.0)
zenmap (7.12)


Didier

From slackbuilds at jaxartes.net  Sat Feb 24 11:52:32 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Sat, 24 Feb 2018 11:52:32 +0000
Subject: [Slackbuilds-users] Sphinx Version 1.7.0 build failure
In-Reply-To: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>
References: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>
Message-ID: <9243A53C-5C8C-478E-A386-7F1127D15072@jaxartes.net>



On February 24, 2018 11:24:14 AM UTC, Konrad J Hambrick <kjhambrick at gmail.com> wrote:
>Benjamin --
>
>I am running Slackware64 14.2 + Multilib and this morning when I
>attempted
>to build Sphinx Version 1.7.0 I experienced a python install failure:

Hi Konrad, please install the packaging SlackBuild. I will add this dependency to .info in the next update.

Best, Ben

From chris.willing at iinet.net.au  Sat Feb 24 11:53:58 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Sat, 24 Feb 2018 21:53:58 +1000
Subject: [Slackbuilds-users] Sphinx Version 1.7.0 build failure
In-Reply-To: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>
References: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>
Message-ID: <f836f59d-b83c-9492-2641-8e48f6c5ab7a@iinet.net.au>

On 24/02/18 21:24, Konrad J Hambrick wrote:
> Benjamin --
> 
> I am running Slackware64 14.2 + Multilib and this morning when I attempted
> to build Sphinx Version 1.7.0 I experienced a python install failure:
> 
> ?? Installing sphinx-autogen script to /tmp/SBo/package-Sphinx/usr/bin
> ?? make: Entering directory '/tmp/SBo/Sphinx-1.7.0/doc'
> ?? Traceback (most recent call last):
> ???? File "/tmp/SBo/package-Sphinx/usr/bin/sphinx-build", line 5, in
> <module>
> ?????? from pkg_resources import load_entry_point
> ???? File
> "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> 2927, in <module>
> ?????? @_call_aside
> ???? File
> "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> 2913, in _call_aside
> ?????? f(*args, **kwargs)
> ???? File
> "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> 2940, in _initialize_master_working_set
> ?????? working_set = WorkingSet._build_master()
> ???? File
> "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> 635, in _build_master
> ?????? ws.require(__requires__)
> ???? File
> "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> 943, in require
> ?????? needed = self.resolve(parse_requirements(requirements))
> ???? File
> "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> 829, in resolve
> ?????? raise DistributionNotFound(req, requirers)
> ?? pkg_resources.DistributionNotFound: The 'packaging' distribution was
> not found and is required by Sphinx
> ?? Makefile:20: recipe for target 'html' failed
> ?? make: *** [html] Error 1
> ?? make: Leaving directory '/tmp/SBo/Sphinx-1.7.0/doc'
> 

I also had the same problem building the new Sphinx. The problem was
fixed by preinstalling python/packaging, as suggested by the error
message. It should be added to the REQUIRES line.

chris

From mario at slackware.hr  Sat Feb 24 12:32:01 2018
From: mario at slackware.hr (Mario)
Date: Sat, 24 Feb 2018 13:32:01 +0100
Subject: [Slackbuilds-users] Postfix Version 3.3.0
In-Reply-To: <CANBHt+NZadodvMevoKfZtHGzGhj3sX2FWWoDvWf9ZBL6GY=nmw@mail.gmail.com>
References: <CANBHt+NZadodvMevoKfZtHGzGhj3sX2FWWoDvWf9ZBL6GY=nmw@mail.gmail.com>
Message-ID: <e91908e0-f061-371c-3f77-50b672f8ad79@slackware.hr>

On 02/23/2018 11:48 AM, Konrad J Hambrick wrote:
> Mario --
> 
> I've been running Postfix 3.3.0 since Wednesday on Slackware64 14.2 + 
> Multilib.
> 
> It works fine in place of the previous Stable Version 3.2.5.
> 
> All I had to change was the default VERSION=${VERSION:-3.3.0} Line in 
> the postfix.SlackBuild
> 
> A new postfix.info.txt file is attached for your consideration.
> 
> I checked postfix-3.3.0.tar.gz against wietse.pgp before generating the 
> md5sum.
> 
> Thanks for the postfix.SlackBuild !
> 
> -- kjh

Thanks. Tested it on my servers as well. Update is in my branch!

Regards,

-- 
Mario

From kjhambrick at gmail.com  Sat Feb 24 12:36:53 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 24 Feb 2018 06:36:53 -0600
Subject: [Slackbuilds-users] Sphinx Version 1.7.0 build failure
In-Reply-To: <f836f59d-b83c-9492-2641-8e48f6c5ab7a@iinet.net.au>
References: <CANBHt+Pdmy815LcfA44XUo8az=C2RTJOcyxCOw75c=70vmaG=A@mail.gmail.com>
 <f836f59d-b83c-9492-2641-8e48f6c5ab7a@iinet.net.au>
Message-ID: <CANBHt+MuuV3onUfe3qTYFXt2Frw73PhVbCfFxup+nyT1h=9aXg@mail.gmail.com>

All --

As Chris said, I should have figured it out for myself from this particular
error message in my SlackBuild.log:  "The 'packaging' distribution ..."

However, I am not much of a Python Guy, so thanks for the hint Chris ! :)

Anyhow ... I built and installed pyparsing ( REQUIRED for packaging ) and
then packaging and then Sphinx-1.7.0 built and installed without error.

Playing with it now but it looks good !

Thanks to Dimitris, Didier and Chris and especially to Ben for the
Sphinx.SlackBuild !

-- kjh


On Sat, Feb 24, 2018 at 5:53 AM, Christoph Willing <
chris.willing at iinet.net.au> wrote:

> On 24/02/18 21:24, Konrad J Hambrick wrote:
> > Benjamin --
> >
> > I am running Slackware64 14.2 + Multilib and this morning when I
> attempted
> > to build Sphinx Version 1.7.0 I experienced a python install failure:
> >
> >    Installing sphinx-autogen script to /tmp/SBo/package-Sphinx/usr/bin
> >    make: Entering directory '/tmp/SBo/Sphinx-1.7.0/doc'
> >    Traceback (most recent call last):
> >      File "/tmp/SBo/package-Sphinx/usr/bin/sphinx-build", line 5, in
> > <module>
> >        from pkg_resources import load_entry_point
> >      File
> > "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> > 2927, in <module>
> >        @_call_aside
> >      File
> > "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> > 2913, in _call_aside
> >        f(*args, **kwargs)
> >      File
> > "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> > 2940, in _initialize_master_working_set
> >        working_set = WorkingSet._build_master()
> >      File
> > "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> > 635, in _build_master
> >        ws.require(__requires__)
> >      File
> > "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> > 943, in require
> >        needed = self.resolve(parse_requirements(requirements))
> >      File
> > "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line
> > 829, in resolve
> >        raise DistributionNotFound(req, requirers)
> >    pkg_resources.DistributionNotFound: The 'packaging' distribution was
> > not found and is required by Sphinx
> >    Makefile:20: recipe for target 'html' failed
> >    make: *** [html] Error 1
> >    make: Leaving directory '/tmp/SBo/Sphinx-1.7.0/doc'
> >
>
> I also had the same problem building the new Sphinx. The problem was
> fixed by preinstalling python/packaging, as suggested by the error
> message. It should be added to the REQUIRES line.
>
> 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/20180224/b17df681/attachment.html>

From kjhambrick at gmail.com  Sat Feb 24 12:41:03 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 24 Feb 2018 06:41:03 -0600
Subject: [Slackbuilds-users] Postfix Version 3.3.0
In-Reply-To: <e91908e0-f061-371c-3f77-50b672f8ad79@slackware.hr>
References: <CANBHt+NZadodvMevoKfZtHGzGhj3sX2FWWoDvWf9ZBL6GY=nmw@mail.gmail.com>
 <e91908e0-f061-371c-3f77-50b672f8ad79@slackware.hr>
Message-ID: <CANBHt+O9wun+1x=wChwxsgjhUUJw0=GJuxKOUPWV3kmhMShO3A@mail.gmail.com>

You're welcome Mario !

Thank you for sharing your postfix.SlackBuild Package.

-- kjh

On Sat, Feb 24, 2018 at 6:32 AM, Mario <mario at slackware.hr> wrote:

> On 02/23/2018 11:48 AM, Konrad J Hambrick wrote:
>
>> Mario --
>>
>> I've been running Postfix 3.3.0 since Wednesday on Slackware64 14.2 +
>> Multilib.
>>
>> It works fine in place of the previous Stable Version 3.2.5.
>>
>> All I had to change was the default VERSION=${VERSION:-3.3.0} Line in the
>> postfix.SlackBuild
>>
>> A new postfix.info.txt file is attached for your consideration.
>>
>> I checked postfix-3.3.0.tar.gz against wietse.pgp before generating the
>> md5sum.
>>
>> Thanks for the postfix.SlackBuild !
>>
>> -- kjh
>>
>
> Thanks. Tested it on my servers as well. Update is in my branch!
>
> Regards,
>
> --
> Mario
> _______________________________________________
> 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/20180224/694f2431/attachment.html>

From Jim.Diamond at acadiau.ca  Sat Feb 24 13:12:24 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Sat, 24 Feb 2018 09:12:24 -0400
Subject: [Slackbuilds-users] opera-ffmpeg-codecs failure
In-Reply-To: <20170121013000.GA17597@jdiamond-nb.acadiau.ca>
References: <6ee80313-4b99-e37d-96bd-5782daa2e5fd@slackbuilds.org>
 <20170121003417.GB10026@jdiamond-nb.acadiau.ca>
 <5fc4152e-5507-4200-7d63-2d09720712f4@slackbuilds.org>
 <20170121011328.GA12309@jdiamond-nb.acadiau.ca>
 <20170121012015.GA16469@jdiamond-nb.acadiau.ca>
 <20170121013000.GA17597@jdiamond-nb.acadiau.ca>
Message-ID: <20180224131224.GA23384@jdiamond-mb.acadiau.ca>

# sboupgrade opera-ffmpeg-codecs

opera-ffmpeg-codecs (Extra ffmpeg codec for Opera browser)

Additional support for proprietary codecs for Opera Stable.

This will add H.264 support to Opera Developer and not replacing the
default /usr/lib/opera/libffmpeg.so.

For tests, go to:

 * https://html5test.com
 * https://www.youtube.com/html5
 * http://www.quirksmode.org/html5/tests/video.html

Proceed with opera-ffmpeg-codecs? [y] 
opera-ffmpeg-codecs added to upgrade queue.

Upgrade queue: opera-ffmpeg-codecs

Are you sure you wish to continue? [y] 
--2018-02-24 09:10:54--  http://mirrors.niyawe.de/archlinux/community/os/x86_64/opera-ffmpeg-codecs-64.0.3282.140-1-x86_64.pkg.tar.xz
Resolving mirrors.niyawe.de... 176.9.79.197, 88.198.44.43, 85.10.246.235, ...
Connecting to mirrors.niyawe.de|176.9.79.197|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-02-24 09:10:54 ERROR 404: Not Found.

--2018-02-24 09:10:54--  ftp://slackware.uk/sbosrcarch/by-md5/2/2/2241528bd55b9f146609a5993989c15e/opera-ffmpeg-codecs-64.0.3282.140-1-x86_64.pkg.tar.xz
           => ?opera-ffmpeg-codecs-64.0.3282.140-1-x86_64.pkg.tar.xz?
Resolving slackware.uk... 91.109.244.240
Connecting to slackware.uk|91.109.244.240|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /sbosrcarch/by-md5/2/2/2241528bd55b9f146609a5993989c15e ... 
No such directory ?sbosrcarch/by-md5/2/2/2241528bd55b9f146609a5993989c15e?.

Unable to download/verify source file(s) for opera-ffmpeg-codecs:
  Unable to wget http://mirrors.niyawe.de/archlinux/community/os/x86_64/opera-ffmpeg-codecs-64.0.3282.140-1-x86_64.pkg.tar.xz.

Do you want to proceed? [n] 
Failures:
  opera-ffmpeg-codecs: Unable to wget http://mirrors.niyawe.de/archlinux/community/os/x86_64/opera-ffmpeg-codecs-64.0.3282.140-1-x86_64.pkg.tar.xz.

From edps.mundognu at gmail.com  Sat Feb 24 16:14:03 2018
From: edps.mundognu at gmail.com (Edinaldo)
Date: Sat, 24 Feb 2018 13:14:03 -0300
Subject: [Slackbuilds-users] opera-ffmpeg-codecs failure
Message-ID: <op.zex7dpb29z09aw@localhost>

I'm sorry man!

They removed the old source (current for us: 64.0.3282.140), follow the  
new link (version=64.0.3282.168) if you wish update this SlackBuild:

http://mirrors.niyawe.de/archlinux/community/os/x86_64/opera-ffmpeg-codecs-64.0.3282.168-1-x86_64.pkg.tar.xz

So... just run:

# wget  
http://slackbuilds.org/slackbuilds/14.2/multimedia/opera-ffmpeg-codecs.tar.gz
# tar xvf opera-ffmpeg-codecs.tar.gz
# cd opera-ffmpeg-codecs
# wget  
http://mirrors.niyawe.de/archlinux/community/os/x86_64/opera-ffmpeg-codecs-64.0.3282.168-1-x86_64.pkg.tar.xz
# VERSION=64.0.3282.168 sh opera-ffmpeg-codecs.SlackBuild
# upgradepkg /tmp/opera-ffmpeg-codecs-64.0.3282.168-x86_64-1_SBo.tgz

Cheers,

Edinaldo.

From yth at ythogtha.org  Sat Feb 24 19:57:04 2018
From: yth at ythogtha.org (Ythogtha)
Date: Sat, 24 Feb 2018 20:57:04 +0100
Subject: [Slackbuilds-users] LibreOffice compilation fails
In-Reply-To: <d7e7c572-d01f-4e36-d5aa-2c641002765a@iinet.net.au>
References: <20180222132434.22b9da46911445992ebbbda9@ythogtha.org>
 <d7e7c572-d01f-4e36-d5aa-2c641002765a@iinet.net.au>
Message-ID: <20180224205704.b900c95f85a2ead4d713c5c3@ythogtha.org>

> I sometimes saw this type of output in my i586 test builds in a VM, even
> after allocating more and more resources (RAM, disk space) to it. BTW,
> no such problems with x86_64 VM, so I've long suspected some sort of
> memory addressing problem.
> 
> After running with MAKEFLAGS-=-j1, I noticed a mention about virtual
> memory exhaustion. This led to more resource allocation increases in the
> VM, including adding more swap space but still no conclusive improvement
> (sometimes failure, sometimes success).
> 
> Eventually, based on an idea which is not quite clear enough in my own
> mind to try to explain, I set TMP=/var/tmp/SBo when running the
> SlackBuild (overriding its TMP=/tmp/SBo). Since then the i586 VM has
> built LO without problems using MAKEFLAGS=-j4 (LO versions 6.0.0.3 &
> 6.0.1.1).
> 
> chris

Well, thanks Chris, this has been helpful !
I changed the TMP dir and it builds fine.

Now I'll try to find why sometimes it works and why sometimes it doesn't,
depending on the TMP directory.
If I find a pattern or anything useful, I'll get back here to tell about it.

-- 
Arnaud <yth at ythogtha.org>

From rshepard at appl-ecosys.com  Sun Feb 25 00:07:10 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Feb 2018 16:07:10 -0800 (PST)
Subject: [Slackbuilds-users] goffice-0.10.38 and gnumeric-1.12.38
Message-ID: <alpine.LNX.2.20.1802241604150.20565@salmo.appl-ecosys.com>

   New versions available.

   For goffice download NEWIST-IS-0.10.38 and rename to
goffice-0.10.38.tar.gz. Change version in the SlackBuild script to match and
it builds.

   For gnumeric, upgrade existing goffice-0.10.34, change version in the
SlackBuild script to 1.12.38 and it builds.

Regards,

Rich

From rshepard at appl-ecosys.com  Sun Feb 25 00:09:20 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Feb 2018 16:09:20 -0800 (PST)
Subject: [Slackbuilds-users] goffice-0.10.38 and gnumeric-1.12.38
In-Reply-To: <alpine.LNX.2.20.1802241604150.20565@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1802241604150.20565@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.20.1802241608490.20565@salmo.appl-ecosys.com>

On Sat, 24 Feb 2018, Rich Shepard wrote:

>  For goffice download NEWIST-IS-0.10.38 and rename to

   Oops. That should be NEWEST-IS-0.10.38.

Rich

From edps.mundognu at gmail.com  Sun Feb 25 01:25:54 2018
From: edps.mundognu at gmail.com (Edinaldo)
Date: Sat, 24 Feb 2018 22:25:54 -0300
Subject: [Slackbuilds-users] Missing Noto Sans in latest noto-fonts
Message-ID: <op.zeywxgg09z09aw@localhost>

Thanks for your report @Daniel Prosser!

This will be fixed in next update, sorry for this inconvenience.

Best Regards,

Edinaldo.

From slackbuilds at jaxartes.net  Sun Feb 25 03:12:30 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Sat, 24 Feb 2018 19:12:30 -0800
Subject: [Slackbuilds-users] QScintilla2 for Python3 and PyQt5
Message-ID: <2300213.gGAgdbaPst@wintermute.sprawl.net>

I'm trying to write a SlackBuild QScintila2 for Python 3 and PyQt5 and can't 
seem to get past a particular stumbling block.

Anyone have any suggestions for resolving the error showing in the attached 
error.txt file? The SlackBuild and patch file are also attached and the source 
is from https://sourceforge.net/projects/pyqt/files/QScintilla2/
QScintilla-2.10.2/QScintilla_gpl-2.10.2.tar.gz.

This is on a clean copy of Slackware64 14.2 (clean other than python3-PyQt5 
and its dependencies). 

There's lots of prior art out there for other distros but nothing I can find 
regarding this particular error.

Thanks, Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: QScintilla-qt5.SlackBuild
Type: application/x-shellscript
Size: 3316 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180224/a4dfee96/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python-config.diff
Type: text/x-patch
Size: 825 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180224/a4dfee96/attachment-0001.bin>
-------------- next part --------------
cd Qsci/ && ( test -e Makefile || /usr/bin/qmake-qt5
/tmp/SBo/QScintilla_gpl-2.10.2/Python/Qsci/Qsci.pro -o Makefile ) && make -f
Makefile install
make[1]: Entering directory '/tmp/SBo/QScintilla_gpl-2.10.2/Python/Qsci'
g++ -c -pipe -fno-exceptions -O2 -fPIC -std=gnu++11 -Wall -W -D_REENTRANT
-fPIC -DSIP_PROTECTED_IS_PUBLIC -Dprotected=public -DQT_NO_DEBUG -DQT_PLUGIN
-DQT_GUI_LIB -DQT_CORE_LIB -I. -isystem /usr/include/qt5/QtWidgets -isystem
/usr/include/qt5/QtPrintSupport
-I../../../package-QScintilla-qt5/usr/include/qt5 -isystem
/usr/include/python3.6 -isystem /usr/include/python3.6m -isystem
/usr/include/qt5 -isystem /usr/include/qt5/QtGui -isystem
/usr/include/qt5/QtCore -I. -I/usr/lib64/qt5/mkspecs/linux-g++ -o
sipQscipart0.o sipQscipart0.cpp
/usr/share/sip/PyQt5/QtCore/qpycore_qlist.sip: In function 'int
convertTo_QList_0101QsciCommand(PyObject*, void**, int*, PyObject*)':
/usr/share/sip/PyQt5/QtCore/qpycore_qlist.sip:228:33: error: invalid use of
incomplete type 'struct _typeobject'
                     Py_TYPE(itm)->tp_name);
                                 ^
In file included from /usr/include/python3.6m/Python.h:68:0,
                 from /usr/include/python3.6/sip.h:32,
                 from sipAPIQsci.h:31,
                 from sipQscipart0.cpp:24:
/usr/include/python3.6m/object.h:109:12: note: forward declaration of 'struct
_typeobject'
     struct _typeobject *ob_type;
            ^
/usr/share/sip/PyQt5/QtCore/qpycore_qlist.sip: In function 'PyObject*
convertFrom_QList_0101QsciCommand(void*, PyObject*)':
/usr/share/sip/PyQt5/QtCore/qpycore_qlist.sip:172:35: error: 'PyList_SET_ITEM'
was not declared in this scope
         PyList_SET_ITEM(l, i, tobj);
                                   ^
/usr/share/sip/PyQt5/QtCore/qpycore_qlist.sip: In function 'int
convertTo_QList_0100QsciStyledText(PyObject*, void**, int*, PyObject*)':
/usr/share/sip/PyQt5/QtCore/qpycore_qlist.sip:118:33: error: invalid use of
incomplete type 'struct _typeobject'
                     Py_TYPE(itm)->tp_name);
                                 ^
In file included from /usr/include/python3.6m/Python.h:68:0,
                 from /usr/include/python3.6/sip.h:32,
                 from sipAPIQsci.h:31,
                 from sipQscipart0.cpp:24:
/usr/include/python3.6m/object.h:109:12: note: forward declaration of 'struct
_typeobject'
     struct _typeobject *ob_type;
            ^
/usr/share/sip/PyQt5/QtCore/qpycore_qlist.sip: In function 'PyObject*
convertFrom_QList_0100QsciStyledText(void*, PyObject*)':
/usr/share/sip/PyQt5/QtCore/qpycore_qlist.sip:61:35: error: 'PyList_SET_ITEM'
was not declared in this scope
         PyList_SET_ITEM(l, i, tobj);
                                   ^
Makefile:658: recipe for target 'sipQscipart0.o' failed
make[1]: *** [sipQscipart0.o] Error 1
make[1]: Leaving directory '/tmp/SBo/QScintilla_gpl-2.10.2/Python/Qsci'
Makefile:66: recipe for target 'sub-Qsci-install_subtargets-ordered' failed
make: *** [sub-Qsci-install_subtargets-ordered] Error 2
root at testbox:~/qgis3-slackbuild/QScintilla-qt5# 


From 1.41421 at gmail.com  Sun Feb 25 16:44:53 2018
From: 1.41421 at gmail.com (JCA)
Date: Sun, 25 Feb 2018 09:44:53 -0700
Subject: [Slackbuilds-users] Sage build still broken?
Message-ID: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>

I built Sage 8.0 as available to Slackware 14.2 using the relevant sbopkg
queue.  The build process closes as follows:

RROR:  The Sage installation tree has moved

from /tmp/SBo/sage-8.0
  to /opt/sage

This is not supported, and Sage will not work. To install Sage from a
binary package:

1. Open the .tar.bz2 archive (or .dmg on OSX)

2. Move the SageMath folder/app to where you want it to be. You can
   also rename the directory now.

3. Start sage for the first time. This will then automatically patch
   paths in binaries.

After starting Sage for the first time you cannot change the
installation any more. To install Sage elsewhere, start over from the
binary package. Or recompile Sage from scratch in the new location
("make distclean && make")

Package sage-8.0-x86_64-1_SBo.tgz installed.


Done upgrading/installing package.

+++++++++++++++++++++++++++++++++++++++++++
SUMMARY LOG
Using the SBo repository for Slackware 14.2
Queue Process:  Download, build, and install

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

+++++++++++++++++++++++++++++++++++++++++++

###########################################
          Queue process complete!
###########################################

   When trying to use it, this is what I am getting:

$ sage
************************************************************************
It seems that you are attempting to run Sage from an unpacked source
tarball, but you have not compiled it yet (or maybe the build has not
finished). You should run `make` in the Sage root directory first.
If you did not intend to build Sage from source, you should download
a binary tarball instead. Read README.txt for more information.
************************************************************************

   This in a freshly installed 14.2 system, with 24G RAM and 1TB disk
space. The compilation was completed normally, ending up with 13GB worth of
files in /tmp/SBo, and more than 5GB in /opt/sage.

   What have I done wrong? If nothing, is there any point in keeping Sage
in Slackbuilds? Even in a beefy system, compiling Sage takes a several
hours - and ending up with lots of GBs eaten up in your hard drive and a
nonfunctional application is frustrating.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180225/c1f0c0f8/attachment-0001.html>

From kingbeowulf at gmail.com  Sun Feb 25 18:59:25 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 25 Feb 2018 10:59:25 -0800
Subject: [Slackbuilds-users] Sage build still broken?
In-Reply-To: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>
References: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>
Message-ID: <00e0f742-ca9e-ae5f-5565-f59664e12ca3@gmail.com>

On 02/25/2018 08:44 AM, JCA wrote:
> I built Sage 8.0 as available to Slackware 14.2 using the relevant
> sbopkg queue.? The build process closes as follows:
> 
> RROR:? The Sage installation tree has moved
> 
> from /tmp/SBo/sage-8.0
> ? to /opt/sage
> 
---snip----
> 
> ? ?This in a freshly installed 14.2 system, with 24G RAM and 1TB disk
> space. The compilation was completed normally, ending up with 13GB worth
> of files in /tmp/SBo, and more than 5GB in /opt/sage.
> 
> ? ?What have I done wrong? If nothing, is there any point in keeping
> Sage in Slackbuilds? Even in a beefy system, compiling Sage takes a
> several hours - and ending up with lots of GBs eaten up in your hard
> drive and a nonfunctional application is frustrating.
> 

I feel your pain, and I do not have a workable solution yet.  Sage
upstream is completely hostile to relocatable packages it seems...  The
core problem is in how the sage devs have designed their build system.

There are 2 options to get sage working:
1. Download their compiled binary and run their script which will patch
the hard coded paths.
2. Compile the sage source in a specific path and leave it there.  You
will note that after running sage.Slackbuild it works just fine when
invoked from /tmp/SBo/sage-8.0
3. Compile the sage source in a specific path (/opt/sage) and package it
from there.
4. Compile the sage source in /tmp/sage-x but have a script to patch the
paths to make the package relocatable.  This is what the devs do for
their binary.

I could just do (1) and forgo compiling.  SBo does that for some, but
that is not optimal. (2) is non-starter: we just can't leave stuff
littering /tmp!  Perhaps (3) in a chroot, etc, but I think (4) is
cleaner if I can ever figure out how the script works in (1).  I'm
missing a path or variable somewhere.

tl;dr

I'm working on it.

-Ed



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

From didier at slint.fr  Sun Feb 25 19:02:20 2018
From: didier at slint.fr (Didier Spaier)
Date: Sun, 25 Feb 2018 20:02:20 +0100
Subject: [Slackbuilds-users] Sage build still broken?
In-Reply-To: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>
References: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>
Message-ID: <9f22edf1-9724-f5f2-b607-ea110a917de5@slint.fr>

Hello,

Le 25/02/2018 ? 17:44, JCA a ?crit?:
<snip>
> ? ?When trying to use it, this is what I am getting:
> 
> $ sage
> ************************************************************************
> It seems that you are attempting to run Sage from an unpacked source
> tarball, but you have not compiled it yet (or maybe the build has not
> finished). You should run `make` in the Sage root directory first.
> If you did not intend to build Sage from source, you should download
> a binary tarball instead. Read README.txt for more information.
> ************************************************************************
> 
> ? ?This in a freshly installed 14.2 system, with 24G RAM and 1TB disk space. The compilation was completed normally, ending up with 13GB worth of files in /tmp/SBo, and more than 5GB in /opt/sage.
> 
> ? ?What have I done wrong? If nothing, is there any point in keeping Sage in Slackbuilds? Even in a beefy system, compiling Sage takes a several hours - and ending up with lots of GBs eaten up in your hard drive and a nonfunctional application is frustrating.
> 

As it happens I have compiled (but not pacakaged) sage-8.1 15 days ago, just to check for a bind friend where the pdf were stored when e.g. drawing a sphere.

I just unpacked  a git archive then ran:

tar xf sage-8.1.tar.gz 
cd sage-8.1
./configure | tee /tmp/config.LOG
time make 2>/tmp/sageERR |tee /tmp/sageLOG

I attach config.LOG but not sageLOG, too heavy (25M), but here is hw it ends:

>Testing that Sage starts...
>[2018-02-06 23:26:22] SageMath version 8.1, Release Date: 2017-12-07
>This looks like the first time you are running Sage.
>Cleaning up, do not interrupt this.
>Done cleaning.
>Yes, Sage starts.
>make[2]?: on quitte le r?pertoire ??/tmp/sage-8.1/build/make??
>make[1]?: on quitte le r?pertoire ??/tmp/sage-8.1/build/make??
>
>real	257m49.177s
>user	262m42.133s
>sys	11m29.261s
>Sage build/upgrade complete!
>
>To install small scripts to directly run Sage's versions of GAP,
>the PARI/GP interpreter, Maxima, or Singular etc. (by typing e.g.
>just 'gap' or 'gp') into a standard 'bin' directory, start Sage
>by typing 'sage' (or './sage') and enter something like
>
>    install_scripts('/usr/local/bin')
>
>at the Sage command prompt ('sage:').

My laptop didn't burn this time...

didier[/tmp]$ du -sh sage-8.1/
7,7G	sage-8.1/

It worked here, that's all I know.

Didier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.LOG
Type: text/x-log
Size: 9637 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180225/9da7c816/attachment.bin>

From 1.41421 at gmail.com  Sun Feb 25 20:39:51 2018
From: 1.41421 at gmail.com (JCA)
Date: Sun, 25 Feb 2018 13:39:51 -0700
Subject: [Slackbuilds-users] Sage build still broken?
In-Reply-To: <9f22edf1-9724-f5f2-b607-ea110a917de5@slint.fr>
References: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>
 <9f22edf1-9724-f5f2-b607-ea110a917de5@slint.fr>
Message-ID: <CAFy1yb3z9kzATWY0RqE4VD87omYFhW-3+MCeG3BJ3+p=vn9jHw@mail.gmail.com>

The Sage website offers a number of binaries for Linux that can be
installed under Slackware without any problems. With a bit of care, they
can be installed anywhere, and be made available to anyone. At least, as
far as I can tell - I can't discard the possibility of Sage complaining
once you start making a heavy use of it.

The point is, why is a Sage package being kept in Slackbuilds, if it is
known to lead to a nonworking installation? It's worse than not having it
there at all - were it not part of the Slackbuilds packages, one would at
least waste no time running the Slackbuilds build and install script,
which, as anybody who has tried can attest, takes a good many hours and
lots of disk space. If, because the Sage packaging/development team are a
bunch of dicks, a Slackbuilds package can't be properly built, shouldn't
the latter be removed, until such time that the issue is fixed?

In the meantime, one could use an approach based on the Linux binaries
mentioned above; I believe that is solution #1 as proposed. No patching
seems to be necessary though - just unpack it in the directory where it is
supposed to be installed, run it once as root, in order for it to set the
environment correctly, change ownership/permissions of the unpacked tree,
as necessary, and create a relevant soft link to /usr/bin. With this, it
does not seem terribly difficult to end up with a working Slackware package
for Sage, and a similar approach is already taken in Slackbuilds for other
software, like LibreOffice or Chromium. I agree that it is preferable to
able to build it for your target system, but only if things work properly
in the end.

On Sun, Feb 25, 2018 at 12:02 PM, Didier Spaier <didier at slint.fr> wrote:

> Hello,
>
> Le 25/02/2018 ? 17:44, JCA a ?crit :
> <snip>
> >    When trying to use it, this is what I am getting:
> >
> > $ sage
> > ************************************************************************
> > It seems that you are attempting to run Sage from an unpacked source
> > tarball, but you have not compiled it yet (or maybe the build has not
> > finished). You should run `make` in the Sage root directory first.
> > If you did not intend to build Sage from source, you should download
> > a binary tarball instead. Read README.txt for more information.
> > ************************************************************************
> >
> >    This in a freshly installed 14.2 system, with 24G RAM and 1TB disk
> space. The compilation was completed normally, ending up with 13GB worth of
> files in /tmp/SBo, and more than 5GB in /opt/sage.
> >
> >    What have I done wrong? If nothing, is there any point in keeping
> Sage in Slackbuilds? Even in a beefy system, compiling Sage takes a several
> hours - and ending up with lots of GBs eaten up in your hard drive and a
> nonfunctional application is frustrating.
> >
>
> As it happens I have compiled (but not pacakaged) sage-8.1 15 days ago,
> just to check for a bind friend where the pdf were stored when e.g. drawing
> a sphere.
>
> I just unpacked  a git archive then ran:
>
> tar xf sage-8.1.tar.gz
> cd sage-8.1
> ./configure | tee /tmp/config.LOG
> time make 2>/tmp/sageERR |tee /tmp/sageLOG
>
> I attach config.LOG but not sageLOG, too heavy (25M), but here is hw it
> ends:
>
> >Testing that Sage starts...
> >[2018-02-06 23:26:22] SageMath version 8.1, Release Date: 2017-12-07
> >This looks like the first time you are running Sage.
> >Cleaning up, do not interrupt this.
> >Done cleaning.
> >Yes, Sage starts.
> >make[2] : on quitte le r?pertoire ? /tmp/sage-8.1/build/make ?
> >make[1] : on quitte le r?pertoire ? /tmp/sage-8.1/build/make ?
> >
> >real   257m49.177s
> >user   262m42.133s
> >sys    11m29.261s
> >Sage build/upgrade complete!
> >
> >To install small scripts to directly run Sage's versions of GAP,
> >the PARI/GP interpreter, Maxima, or Singular etc. (by typing e.g.
> >just 'gap' or 'gp') into a standard 'bin' directory, start Sage
> >by typing 'sage' (or './sage') and enter something like
> >
> >    install_scripts('/usr/local/bin')
> >
> >at the Sage command prompt ('sage:').
>
> My laptop didn't burn this time...
>
> didier[/tmp]$ du -sh sage-8.1/
> 7,7G    sage-8.1/
>
> It worked here, that's all I know.
>
> Didier
>
> _______________________________________________
> 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/20180225/50fde861/attachment-0001.html>

From fernando.lopezjr at gmail.com  Sun Feb 25 22:38:23 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sun, 25 Feb 2018 15:38:23 -0700
Subject: [Slackbuilds-users] 403 numpy
Message-ID: <CALrQ46ABPajLNa-XKGoNVYh9e-D1J+9gXmyc3ousKTyAAULNfQ@mail.gmail.com>

required dep for inkscape.

slackbuilds.org/repository/14.2/development/numpy/

-- 

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

From chris.willing at iinet.net.au  Sun Feb 25 23:04:23 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Mon, 26 Feb 2018 09:04:23 +1000
Subject: [Slackbuilds-users] 403 numpy
In-Reply-To: <CALrQ46ABPajLNa-XKGoNVYh9e-D1J+9gXmyc3ousKTyAAULNfQ@mail.gmail.com>
References: <CALrQ46ABPajLNa-XKGoNVYh9e-D1J+9gXmyc3ousKTyAAULNfQ@mail.gmail.com>
Message-ID: <3b343ca2-a93d-74ec-3cf1-36f2b2d6e61f@iinet.net.au>

On 26/02/18 08:38, Fernando Lopez wrote:
> required dep for inkscape.
> 
> slackbuilds.org/repository/14.2/development/numpy/
> <http://slackbuilds.org/repository/14.2/development/numpy/>
> 

Your mean the source tarball? It's available at:

https://pypi.python.org/packages/e0/4c/515d7c4ac424ff38cc919f7099bf293dd064ba9a600e1e3835b3edefdb18/numpy-1.11.1.tar.gz#md5=2f44a895a8104ffac140c3a70edbd450


>From memory, the contents were slightly different from the version
available from sourceforge - just minor documentation things.

Also, version 1.14.1 is actually the latest.

chris

From jbernts at broadpark.no  Tue Feb 27 02:03:23 2018
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Tue, 27 Feb 2018 03:03:23 +0100
Subject: [Slackbuilds-users] Ledger version
In-Reply-To: <CAO9GfX+4ByX8eeqY+y2+UgHKnX7m0+b3bCERhW2rFSRotERsJw@mail.gmail.com>
References: <20171214123847.GA17131@jbsupah>
 <CAO9GfX+4ByX8eeqY+y2+UgHKnX7m0+b3bCERhW2rFSRotERsJw@mail.gmail.com>
Message-ID: <20180227020323.GD7316@jbsupah>

On 19.12.17,00:53, Simotrone wrote:
> 2017-12-14 13: 38 GMT+01:00 Jostein Berntsen <jbernts at broadpark.no>:
> 
> > Hi,
> >
> > Would it be a point to update version of ledger from 3.1 to 3.1.1 as
> > this has several fixes?
> 
> Hi Jostein,
> I submitted the new ledger sbo package right now.
> Version 3.1.1 incoming.
> Regards,
> Simone
> 
> 

When ledger is installed from the repo it is still version 3.1.0. Was 
this upgrade accepted? 


Jostein



From willysr at slackbuilds.org  Tue Feb 27 02:38:43 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 27 Feb 2018 09:38:43 +0700
Subject: [Slackbuilds-users] Ledger version
In-Reply-To: <20180227020323.GD7316@jbsupah>
References: <20171214123847.GA17131@jbsupah>
 <CAO9GfX+4ByX8eeqY+y2+UgHKnX7m0+b3bCERhW2rFSRotERsJw@mail.gmail.com>
 <20180227020323.GD7316@jbsupah>
Message-ID: <17e222cf-8804-7480-27f5-196d623c699e@slackbuilds.org>

> When ledger is installed from the repo it is still version 3.1.0. Was 
> this upgrade accepted? 

Yes, it was accepted
https://git.slackbuilds.org/slackbuilds/commit/?id=a05b3275875bd963b9f9f05b805a6c585bc3781c


-- 
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/20180227/703ad369/attachment.asc>

From jebrhansen+SBo at gmail.com  Tue Feb 27 03:18:56 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 27 Feb 2018 03:18:56 +0000
Subject: [Slackbuilds-users] Ledger version
In-Reply-To: <20180227020323.GD7316@jbsupah>
References: <20171214123847.GA17131@jbsupah>
 <CAO9GfX+4ByX8eeqY+y2+UgHKnX7m0+b3bCERhW2rFSRotERsJw@mail.gmail.com>
 <20180227020323.GD7316@jbsupah>
Message-ID: <CANi9qSsP2yzPdDYBmZt2XPh9SfXDA26ro=UmXhG9zUB8BUJPCw@mail.gmail.com>

On Mon, Feb 26, 2018, 8:02 PM Jostein Berntsen <jbernts at broadpark.no> wrote:

> On 19.12.17,00:53, Simotrone wrote:
> > 2017-12-14 13: 38 GMT+01:00 Jostein Berntsen <jbernts at broadpark.no>:
> >
> > > Hi,
> > >
> > > Would it be a point to update version of ledger from 3.1 to 3.1.1 as
> > > this has several fixes?
> >
> > Hi Jostein,
> > I submitted the new ledger sbo package right now.
> > Version 3.1.1 incoming.
> > Regards,
> > Simone
> >
> >
>
> When ledger is installed from the repo it is still version 3.1.0. Was
> this upgrade accepted?
>
>
> Jostein
>

Make sure you're updating whatever program you're using to build
SlackBuilds. It's showing 3.1.1 on SBo.

https://slackbuilds.org/repository/14.2/business/ledger/

Jeremy

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

From hamradioea7 at gmail.com  Wed Feb 28 16:40:01 2018
From: hamradioea7 at gmail.com (radio radio)
Date: Wed, 28 Feb 2018 16:40:01 +0000
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
Message-ID: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>

I opened a post in linuxquestions.org slackware forum, about "Retroshare
6.0.3" slackbuild.

https://www.linuxquestions.org/questions/showthread.php?p=5825342#post5825342

Ponce suspect an issue with the newer " libupnp ".

Thanks for your time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180228/d728265a/attachment.html>

From hamradioea7 at gmail.com  Wed Feb 28 17:21:49 2018
From: hamradioea7 at gmail.com (radio radio)
Date: Wed, 28 Feb 2018 17:21:49 +0000
Subject: [Slackbuilds-users] Link corrupted dnscrypt-proxy (1.9.5)
 SlackBuilds
Message-ID: <CAK9UmyJhifsgVvcw72M3ACgbD2oRZbEKrdV87w+Y+wLB6cZsEg@mail.gmail.com>

Hello, I was trying to install dnscryp-proxy from SlackBuilds, but link do
not work.

I think because of Cisco bought dnscrypt.org now is called opendns.com

Thanks for your time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180228/15d0279c/attachment.html>

From matteo.bernardini at gmail.com  Wed Feb 28 17:59:40 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 28 Feb 2018 18:59:40 +0100
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
Message-ID: <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>

2018-02-28 17:40 GMT+01:00 radio radio <hamradioea7 at gmail.com>:
> I opened a post in linuxquestions.org slackware forum, about "Retroshare
> 6.0.3" slackbuild.
>
> https://www.linuxquestions.org/questions/showthread.php?p=5825342#post5825342
>
> Ponce suspect an issue with the newer " libupnp ".

I'll try to clarify a little: retroshare.SlackBuild lacks a "set -e"
line so a package is created also if build breaks and this might have
lead into the belief that compiling had been succesful.

the error is this:

g++ -c -pipe -Wno-deprecated -Wno-deprecated-declarations -Wno-cpp
-std=c++0x -Wall -D_FILE_OFFSET_BITS=64 -O2 -pthread -fPIC -Wall -W
-DRS_ENABLE_GXS -DENABLE_WEBUI -DRS_NO_WARN_DEPRECATED
-DRS_NO_WARN_CPP -DRS_GXS_TRANS -DRS_USE_BITDHT -DPATCHED_LIBUPNP
-DPLUGIN_DIR="\"/usr/lib64/retroshare/extensions6\""
-DDATA_DIR="\"/usr/share/retroshare\"" -DRS_USE_LIBUPNP
-DSQLITE_HAS_CODEC -DGXS_ENABLE_SYNC_MSGS
-I/usr/lib64/qt/mkspecs/linux-g++ -I. -I. -I../../libbitdht/src
-I../../openpgpsdk/src -I/usr/include/upnp -o
temp/linux-g++/obj/rsinit.o rsserver/rsinit.cc
In file included from ./upnp/UPnPBase.h:35:0,
                 from ./upnp/upnphandler_linux.h:13,
                 from rsserver/rsinit.cc:805:
/usr/include/upnp/upnpdebug.h:40:24: fatal error: ThreadPool.h: No
such file or directory
compilation terminated.
Makefile.libretroshare:5411: recipe for target
'temp/linux-g++/obj/rsinit.o' failed
make[1]: *** [temp/linux-g++/obj/rsinit.o] Error 1
make[1]: Leaving directory '/tmp/SBo/RetroShare-0.6.3/libretroshare/src'
Makefile:90: recipe for target
'sub-libretroshare-src-libretroshare-pro-make_default' failed
make: *** [sub-libretroshare-src-libretroshare-pro-make_default] Error 2

Matteo

From willysr at slackbuilds.org  Wed Feb 28 18:05:09 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 1 Mar 2018 01:05:09 +0700
Subject: [Slackbuilds-users] Link corrupted dnscrypt-proxy (1.9.5)
 SlackBuilds
In-Reply-To: <CAK9UmyJhifsgVvcw72M3ACgbD2oRZbEKrdV87w+Y+wLB6cZsEg@mail.gmail.com>
References: <CAK9UmyJhifsgVvcw72M3ACgbD2oRZbEKrdV87w+Y+wLB6cZsEg@mail.gmail.com>
Message-ID: <03a7d354-bba9-9b6e-7d7d-76672d9c32f6@slackbuilds.org>

> Hello, I was trying to install dnscryp-proxy from SlackBuilds, but link
> do not work.
> 
> I think because of Cisco bought dnscrypt.org <http://dnscrypt.org> now
> is called opendns.com <http://opendns.com>

I have this fixed on my branch
You can get this from
https://sources.lede-project.org/dnscrypt-proxy-1.9.5.tar.bz2


-- 
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/20180301/90c1a4b9/attachment.asc>

From Jim.Diamond at acadiau.ca  Wed Feb 28 18:44:52 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Wed, 28 Feb 2018 14:44:52 -0400
Subject: [Slackbuilds-users] runc build error
Message-ID: <20180228184452.GA10582@tux3.acadiau.ca>

Hi,

Using S64-14.2, trying
        sboinstall runc
I get
...
runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_openbsd_386.go
runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_openbsd_amd64.go
runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_solaris_amd64.go
go build -i  -ldflags "-X main.gitCommit=3f2f8b84a77f73d38244dd690525642a72156c64 -X main.version=1.0.0-rc4+dev " -tags "seccomp" -o runc .
build/src/github.com/opencontainers/runc/libcontainer/configs/namespaces_syscall.go:5:8: C source files not allowed when not using cgo: gccgo_c.c
make: *** [runc] Error 1
Makefile:28: recipe for target 'runc' failed
Failures:
  runc: runc.SlackBuild return non-zero
- sboinstall runc  21.34s user 2.11s system 75% cpu 31.207 total


Anyone have any suggestions for me, before I spend too much time
digging around?


Thanks.
                                Jim

From rundstutzen at gmx.de  Wed Feb 28 19:28:35 2018
From: rundstutzen at gmx.de (rundstutzen at gmx.de)
Date: Wed, 28 Feb 2018 20:28:35 +0100
Subject: [Slackbuilds-users] runc build error
In-Reply-To: <20180228184452.GA10582@tux3.acadiau.ca>
References: <20180228184452.GA10582@tux3.acadiau.ca>
Message-ID: <20180228202835.6179d4f8@fiete.bug.net>

did you make sure you installed (and use) the google-go-lang slackbuild?
the go compiler that comes with slackware (gcc-go) is not sufficient.
"go version" will tell you if you use the right compiler.

On Wed, 28 Feb 2018 14:44:52 -0400
Jim Diamond <Jim.Diamond at acadiau.ca> wrote:

> Hi,
> 
> Using S64-14.2, trying
>         sboinstall runc
> I get
> ...
> runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_openbsd_386.go
> runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_openbsd_amd64.go
> runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_solaris_amd64.go
> go build -i  -ldflags "-X
> main.gitCommit=3f2f8b84a77f73d38244dd690525642a72156c64 -X
> main.version=1.0.0-rc4+dev " -tags "seccomp" -o runc .
> build/src/github.com/opencontainers/runc/libcontainer/configs/namespaces_syscall.go:5:8:
> C source files not allowed when not using cgo: gccgo_c.c make: ***
> [runc] Error 1 Makefile:28: recipe for target 'runc' failed Failures:
> runc: runc.SlackBuild return non-zero
> - sboinstall runc  21.34s user 2.11s system 75% cpu 31.207 total
> 
> 
> Anyone have any suggestions for me, before I spend too much time
> digging around?
> 
> 
> Thanks.
>                                 Jim
> _______________________________________________
> 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 x80 at telus.net  Wed Feb 28 20:57:13 2018
From: x80 at telus.net (x80)
Date: Wed, 28 Feb 2018 12:57:13 -0800
Subject: [Slackbuilds-users] Lilypond compile failure
Message-ID: <7fd5067e-adac-2d81-05bd-d6d5f68656bb@telus.net>



On 02/22/2018 03:41 PM, Klaatu wrote:
> Is anyone else having trouble building lilypond?
>
> I get failure during ./configure, hinting that i need a more robust Tex
> stack.
>
> checking for epsf.tex... ./configure: line 13764: kpsewhich: command not
> found
> not found
> checking for Cyrillic characters support in TeX... ./configure: line
> 13777: kpsewhich: command not found
> not found
>
> I am *not* attempting to build its docs, which the SlackBuild's README
> specifically says cannot be done without installing texi2html.
>
> The project docs mention some dependencies that don't appear in the
> SlackBuild .info file, so that might be part of the problem, but the
> error I'm getting doesn't really seem to correlate to Metafont or
> Metapost (two things listed in the project docs but not the SlackBuild
> docs).
>
> Anybody try this lately?
>
>
No problems on a fresh 64-14.2 fully updated.

Jack is giving me problems tho - I get no sound in rosegarden, and 
apparently I need to install a synth. I haven't a clue, I've never got 
rosegarden to compile before and I don't know how to set it up.
Time to rtfm I guess.

From t3slider at gmail.com  Wed Feb 28 22:05:25 2018
From: t3slider at gmail.com (T3 slider)
Date: Wed, 28 Feb 2018 17:05:25 -0500
Subject: [Slackbuilds-users] Link corrupted dnscrypt-proxy (1.9.5)
 SlackBuilds
In-Reply-To: <03a7d354-bba9-9b6e-7d7d-76672d9c32f6@slackbuilds.org>
References: <CAK9UmyJhifsgVvcw72M3ACgbD2oRZbEKrdV87w+Y+wLB6cZsEg@mail.gmail.com>
 <03a7d354-bba9-9b6e-7d7d-76672d9c32f6@slackbuilds.org>
Message-ID: <CAM4-3vRCrr_8gp8dHCJkLqR1G3pHCcF0_6_rGxBNqKhj7SQNSg@mail.gmail.com>

Thanks for updating the links Willy, I'll look at updating the version over
the weekend.

-T3slider

On Feb 28, 2018 1:05 PM, "Willy Sudiarto Raharjo" <willysr at slackbuilds.org>
wrote:

> Hello, I was trying to install dnscryp-proxy from SlackBuilds, but link
> do not work.
>
> I think because of Cisco bought dnscrypt.org <http://dnscrypt.org> now
> is called opendns.com <http://opendns.com>

I have this fixed on my branch
You can get this from
https://sources.lede-project.org/dnscrypt-proxy-1.9.5.tar.bz2


--
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/20180228/72273afe/attachment.html>

From klaatu at member.fsf.org  Wed Feb 28 23:38:13 2018
From: klaatu at member.fsf.org (Klaatu)
Date: Thu, 01 Mar 2018 12:38:13 +1300
Subject: [Slackbuilds-users] Lilypond compile failure
In-Reply-To: <7fd5067e-adac-2d81-05bd-d6d5f68656bb@telus.net>
References: <7fd5067e-adac-2d81-05bd-d6d5f68656bb@telus.net>
Message-ID: <8EAC74FA-4D9E-401C-984D-C8FB411301E2@member.fsf.org>

Funny you mention that. I have it on good authority that a tutorial article on Rosegarden is going to be published on opensource.com soon. I also happen to know that the author of the article writes his tutorials on Slackware with packages from SBo. I'll try to remember to post a link when it is released.

On 1 March 2018 9:57:13 AM NZDT, x80 <x80 at telus.net> wrote:
>
>
>On 02/22/2018 03:41 PM, Klaatu wrote:
>> Is anyone else having trouble building lilypond?
>>
>> I get failure during ./configure, hinting that i need a more robust
>Tex
>> stack.
>>
>> checking for epsf.tex... ./configure: line 13764: kpsewhich: command
>not
>> found
>> not found
>> checking for Cyrillic characters support in TeX... ./configure: line
>> 13777: kpsewhich: command not found
>> not found
>>
>> I am *not* attempting to build its docs, which the SlackBuild's
>README
>> specifically says cannot be done without installing texi2html.
>>
>> The project docs mention some dependencies that don't appear in the
>> SlackBuild .info file, so that might be part of the problem, but the
>> error I'm getting doesn't really seem to correlate to Metafont or
>> Metapost (two things listed in the project docs but not the
>SlackBuild
>> docs).
>>
>> Anybody try this lately?
>>
>>
>No problems on a fresh 64-14.2 fully updated.
>
>Jack is giving me problems tho - I get no sound in rosegarden, and 
>apparently I need to install a synth. I haven't a clue, I've never got 
>rosegarden to compile before and I don't know how to set it up.
>Time to rtfm I guess.
>_______________________________________________
>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/

-- 
Klaatu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180301/01c2ba1b/attachment.html>