From willysr at slackbuilds.org  Sun Jan  1 00:03:32 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 1 Jan 2017 07:03:32 +0700
Subject: [Slackbuilds-users] BUG: cannot run pioneer in -current
In-Reply-To: <CAJ6MA1GKSfLaVHedLtphovk7Z0-76PStB5LCZK0ZeJorW8GY9w@mail.gmail.com>
References: <20161231130340.0953c2fd@loli.sombragris.org>
 <neov9.317344ffe7.20161231183608.62ea7a1f@loli.sombragris.org>
 <CAJ6MA1GKSfLaVHedLtphovk7Z0-76PStB5LCZK0ZeJorW8GY9w@mail.gmail.com>
Message-ID: <a1880913-d371-396a-4c96-5b98f9bc044a@slackbuilds.org>

> It is not mandatory, if you have some non-free driver, you don't need it
> installed, it is only for intel or amd with free drivers. However, I'll
> also suggest to mention it as optional dependence.

Thanks for the suggestions
README updated in my branch


-- 
Willy Sudiarto Raharjo

-------------- 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/20170101/0db3daec/attachment.asc>

From willysr at slackbuilds.org  Sun Jan  1 00:36:52 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 1 Jan 2017 07:36:52 +0700
Subject: [Slackbuilds-users] atlas failed to build with recent updates
In-Reply-To: <CAJ6MA1HfDivB6KH0jtObaN=vAmpPOdtmECPvbdOudqTwmtWC5w@mail.gmail.com>
References: <CAJ6MA1HfDivB6KH0jtObaN=vAmpPOdtmECPvbdOudqTwmtWC5w@mail.gmail.com>
Message-ID: <2901d765-8835-89eb-5373-4a230876a8bc@slackbuilds.org>

> When I've tried to build atlas on the fresh-installed slackware64-14.2
> machine with all recent updates installed, I've got an error (the complete
> log is in attachment). Similar problems was with -current installations,
> but it is reasonable since it is not supported. The machine is HP ProDesk
> 400
> (Pentium 4400, all integrated in H110 chipset).

Tested here in clean VM

lapack-atlas:
  MD5SUM check for lapack-3.6.1.tgz ... OK
  Building package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK
  Installing package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK

atlas:
  MD5SUM check for atlas3.10.3.tar.bz2 ... OK
  Building package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
  Installing package atlas-3.10.3-x86_64-1_SBo.tgz ... OK


-- 
Willy Sudiarto Raharjo

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

From reedych at reedych.pw  Sun Jan  1 06:08:32 2017
From: reedych at reedych.pw (Reedych)
Date: Sun, 01 Jan 2017 12:08:32 +0600
Subject: [Slackbuilds-users] Updates - 20161231.1
Message-ID: <20170101090834.8YiKDtxc@smtp3h.mail.yandex.net>

And yes, 2 virtualbox's .pdf-s has not correct md5.

1 ???. 2017 05:41, ?????????? Willy Sudiarto Raharjo <willysr at slackbuilds.org> ???????:
>
> > Unable to download/verify source file(s) for lxml: 
> >?? md5sum failure for /usr/local/poo/usr-sbo-142/distfiles/lxml-lxml-3.7.1.tar.gz. 
>
> Fixed already on my branch :) 
>
>
> -- 
> Willy Sudiarto Raharjo 
>
> _______________________________________________ 
> SlackBuilds-users mailing list 
> SlackBuilds-users at slackbuilds.org 
> http://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  Sun Jan  1 06:52:51 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 1 Jan 2017 13:52:51 +0700
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <20170101090834.8YiKDtxc@smtp3h.mail.yandex.net>
References: <20170101090834.8YiKDtxc@smtp3h.mail.yandex.net>
Message-ID: <04e9f8be-1479-501a-02f6-57750adf0e97@slackbuilds.org>

> And yes, 2 virtualbox's .pdf-s has not correct md5.

I tested the PDFs and they do have the correct MD5 values

md5sum *.pdf
1503b03024f790b2344c4728c27a8e2a  SDKRef.pdf
7bb5e3dcfa06bb8ff7d5d7cfc1f80e69  UserManual.pdf

MD5SUM="9ba8ff724dadfb7327dc4c6401afb7a8 \
        b484878eaafcf6b62b3a290a28495e56 \
->      7bb5e3dcfa06bb8ff7d5d7cfc1f80e69 \
->      1503b03024f790b2344c4728c27a8e2a"


-- 
Willy Sudiarto Raharjo

-------------- 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/20170101/63ce6f31/attachment.asc>

From hostmaster at slackonly.com  Sun Jan  1 09:42:11 2017
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Sun, 1 Jan 2017 01:42:11 -0800
Subject: [Slackbuilds-users] barnyard2
Message-ID: <b933b7a2-89c7-45ef-feed-ba9d16e61ffa@slackonly.com>

Hi,

barnyard2 SlackBuild need to change:

- tar xvf $CWD/$PRGNAM-2-$VERSION.tar.gz
+tar xvf $CWD/v2-$VERSION.tar.gz

Thanks and Happy new year to all!

From willysr at slackbuilds.org  Sun Jan  1 11:33:05 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 1 Jan 2017 18:33:05 +0700
Subject: [Slackbuilds-users] barnyard2
In-Reply-To: <b933b7a2-89c7-45ef-feed-ba9d16e61ffa@slackonly.com>
References: <b933b7a2-89c7-45ef-feed-ba9d16e61ffa@slackonly.com>
Message-ID: <e2dec02c-7fa1-38ec-aa18-2e2081dab433@slackbuilds.org>

> barnyard2 SlackBuild need to change:
> 
> - tar xvf $CWD/$PRGNAM-2-$VERSION.tar.gz
> +tar xvf $CWD/v2-$VERSION.tar.gz

Hi

Thanks for reporting
i have fixed it on my branch along with other cleanups


-- 
Willy Sudiarto Raharjo

-------------- 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/20170101/9be002d0/attachment.asc>

From audrius at neutrino.lt  Sun Jan  1 16:10:44 2017
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Sun, 1 Jan 2017 18:10:44 +0200
Subject: [Slackbuilds-users] Questions about pending python3 changes
Message-ID: <20170101161044.GA12481@varna>

Hi,

I noticed that Willy added a patch for python3 to change a comment in
one of header files from C++ style to C.  I'm not objecting it, just
want to understand if there's a particular reason for this change, e.g.
suppressing compiler warning or some build issues.  And may I suggest
that you change the patch filename to something more specific like
python3.fix-comment-style.patch.

Regarding a fix for enum34, which disables python3 support, I was
surprised that it was there in the first place, because starting from
version 3.4 (hence the name enum34) enum module is part of Python's
standard library.  The purpose of enum34 is to bring this functionality
to previous Python versions.  Maybe the maintainer, Dimitris Zlatanidis,
could comment on why enum34 SlackBuild had python3 support.

-- 
Audrius Ka?ukauskas
http://neutrino.lt/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170101/3853649d/attachment.asc>

From willysr at slackbuilds.org  Sun Jan  1 16:50:08 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 1 Jan 2017 23:50:08 +0700
Subject: [Slackbuilds-users] Questions about pending python3 changes
In-Reply-To: <20170101161044.GA12481@varna>
References: <20170101161044.GA12481@varna>
Message-ID: <96D127A4-0E14-4D39-AD75-A09D7B590DF9@slackbuilds.org>



> I noticed that Willy added a patch for python3 to change a comment in
> one of header files from C++ style to C.  I'm not objecting it, just
> want to understand if there's a particular reason for this change, e.g.
> suppressing compiler warning or some build issues.  And may I suggest
> that you change the patch filename to something more specific like
> python3.fix-comment-style.patch.

It caused pygobject3-python3 to break. It was reported in LQ
Yes, i will rename the patch tomorrow

> Regarding a fix for enum34, which disables python3 support, I was
> surprised that it was there in the first place, because starting from
> version 3.4 (hence the name enum34) enum module is part of Python's
> standard library.  The purpose of enum34 is to bring this functionality
> to previous Python versions.  Maybe the maintainer, Dimitris Zlatanidis,
> could comment on why enum34 SlackBuild had python3 support.

The idea was to backport 3.2 functionality but somehow python3 was added.
I agree that it should not have python 3 support at all.


--
Willy Sudiarto Raharjo

From chytraeu at sdf.org  Sun Jan  1 20:38:55 2017
From: chytraeu at sdf.org (chytraeu)
Date: Sun, 01 Jan 2017 14:38:55 -0600
Subject: [Slackbuilds-users] remove sparkleshare
Message-ID: <13317ce8f672efab021cc06d6a3122e2@sdf.org>

Can we remove sparkleshare.
I'm the maintainer but do not use it and it's very outdated.
I think webkit-sharp and notify-sharp can also be removed if no one is 
using them.
I think they are only there to support sparkleshare, but I could be 
wrong.

---
Regards,
Donald Cooley


From chytraeu at sdf.org  Sun Jan  1 20:06:48 2017
From: chytraeu at sdf.org (chytraeu)
Date: Sun, 01 Jan 2017 14:06:48 -0600
Subject: [Slackbuilds-users] remove sparkleshare
Message-ID: <c3e9350d4568051929718b5a207845be@sdf.org>

Can we remove sparkleshare.
I'm the maintainer but do not use it and it's very outdated.
I think webkit-sharp and notify-sharp can also be removed if no one is 
using them.
I think they are only there to support sparkleshare, but I could be 
wrong.

---
Regards,
Donald Cooley


From atelszewski at gmail.com  Sun Jan  1 23:53:57 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 2 Jan 2017 00:53:57 +0100
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
Message-ID: <e12ff27a-8b2f-25af-39c0-5a08f24be156@gmail.com>

On 31/12/16 03:07, Willy Sudiarto Raharjo wrote:
> libraries/chromaprint: Updated for version 1.4.

clementine fails to build here with the following:


/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp: 
In member function 'QString Chromaprinter::CreateFingerprint()':
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35: 
error: invalid conversion from 'void*' to 'const int16_t* {aka const 
short int*}' [-fpermissive]
                     data.size() / 2);
                                    ^
In file included from 
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0:
/usr/include/chromaprint.h:235:45: note:   initializing argument 2 of 
'int chromaprint_feed(ChromaprintContext*, const int16_t*, int)'
  CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const 
int16_t *data, int size);
                                              ^
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:152:72: 
error: invalid conversion from 'void**' to 'uint32_t** {aka unsigned 
int**}' [-fpermissive]
    int ret = chromaprint_get_raw_fingerprint(chromaprint, &fprint, &size);
                                                                         ^
In file included from 
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0:
/usr/include/chromaprint.h:273:45: note:   initializing argument 2 of 
'int chromaprint_get_raw_fingerprint(ChromaprintContext*, uint32_t**, int*)'
  CHROMAPRINT_API int chromaprint_get_raw_fingerprint(ChromaprintContext 
*ctx, uint32_t **fingerprint, int *size);
                                              ^
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62: 
error: invalid conversion from 'void*' to 'const uint32_t* {aka const 
unsigned int*}' [-fpermissive]
                                     &encoded, &encoded_size, 1);
                                                               ^
In file included from 
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0:
/usr/include/chromaprint.h:331:45: note:   initializing argument 1 of 
'int chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, 
int*, int)'
  CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t *fp, 
int size, int algorithm, char **encoded_fp, int *encoded_size, int base64);
                                              ^
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62: 
error: invalid conversion from 'void**' to 'char**' [-fpermissive]
                                     &encoded, &encoded_size, 1);
                                                               ^
In file included from 
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0:
/usr/include/chromaprint.h:331:45: note:   initializing argument 4 of 
'int chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, 
int*, int)'
  CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t *fp, 
int size, int algorithm, char **encoded_fp, int *encoded_size, int base64);
                                              ^
At global scope:
cc1plus: error: unrecognized command line option 
'-Wno-unknown-warning-option' [-Werror]
cc1plus: error: unrecognized command line option 
'-Wno-unused-private-field' [-Werror]
cc1plus: all warnings being treated as errors
src/CMakeFiles/clementine_lib.dir/build.make:7366: recipe for target 
'src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o' failed
make[2]: *** 
[src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CMakeFiles/Makefile2:1071: recipe for target 
'src/CMakeFiles/clementine_lib.dir/all' failed
make[1]: *** [src/CMakeFiles/clementine_lib.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Mon Jan  2 00:04:44 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 2 Jan 2017 01:04:44 +0100
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
Message-ID: <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>

On 01/01/17 00:40, Willy Sudiarto Raharjo wrote:
>>> python/python3: Updated for version 3.6.0.
>>
>> I'm not entirely sure if the updated Python is the reason for borgbackup
>> failing to build, but it surely was building before.
>>
>> Anyways, adding setuptools-scm as requirement for borgbackup allows for
>> successful build.
>>
>> So, please add setuptools-scm to REQUIRES of borgbackup, or wait until I
>> push an updated version.
>>
>>
>> All this being said, thanks and happy new year ;-)
>> See you soon :-)
>
> Well, it's working fine here
>
> msgpack-python:
>   MD5SUM check for msgpack-python-0.4.8.tar.gz ... OK
>   Building package msgpack-python-0.4.8-x86_64-1_SBo.tgz ... OK
>   Installing package msgpack-python-0.4.8-x86_64-1_SBo.tgz ... OK
>
> lz4:
>   MD5SUM check for r131.tar.gz ... OK
>   Building package lz4-r131-x86_64-1_SBo.tgz ... OK
>   Installing package lz4-r131-x86_64-1_SBo.tgz ... OK
>
> python3:
>   MD5SUM check for Python-3.6.0.tar.xz ... OK
>   Building package python3-3.6.0-x86_64-1_SBo.tgz ... OK
>   Installing package python3-3.6.0-x86_64-1_SBo.tgz ... OK
>
> borgbackup:
>   MD5SUM check for borgbackup-1.0.7.tar.gz ... OK
>   Building package borgbackup-1.0.7-x86_64-1_SBo.tgz ... OK
>   Installing package borgbackup-1.0.7-x86_64-1_SBo.tgz ... OK
>

I tried building the packages by hand (i.e. without any help of any 
tool) and it indeed succeeded.

Then I tried again using slackrepo and that's what I get:


Download error on https://pypi.python.org/simple/setuptools_scm/: [Errno 
-3] Temporary failure in name resolution -- Some packages may not be found!
Download error on https://pypi.python.org/simple/setuptools-scm/: [Errno 
-3] Temporary failure in name resolution -- Some packages may not be found!
Couldn't find index page for 'setuptools_scm' (maybe misspelled?)
Download error on https://pypi.python.org/simple/: [Errno -3] Temporary 
failure in name resolution -- Some packages may not be found!
No local packages or working download links found for setuptools_scm>=1.7
Traceback (most recent call last):
   File "setup.py", line 278, in <module>
     extras_require=extras_require,
   File "/usr/lib64/python3.6/distutils/core.py", line 108, in setup
     _setup_distribution = dist = klass(attrs)
   File "/usr/lib64/python3.6/site-packages/setuptools/dist.py", line 
315, in __init__
     self.fetch_build_eggs(attrs['setup_requires'])
   File "/usr/lib64/python3.6/site-packages/setuptools/dist.py", line 
361, in fetch_build_eggs
     replace_conflicting=True,
   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", 
line 850, in resolve
     dist = best[req.key] = env.best_match(req, ws, installer)
   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", 
line 1122, in best_match
     return self.obtain(req, installer)
   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", 
line 1134, in obtain
     return installer(requirement)
   File "/usr/lib64/python3.6/site-packages/setuptools/dist.py", line 
429, in fetch_build_egg
     return cmd.easy_install(req)
   File 
"/usr/lib64/python3.6/site-packages/setuptools/command/easy_install.py", 
line 659, in easy_install
     raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution 
for Requirement.parse('setuptools_scm>=1.7')


I don't know why this error occurs, but anyways, maybe it's a signal 
that setuptools-scm should be actually in the REQUIRES?

Why the hell the install script tries to download anything?

-- 
Best regards,
Andrzej Telszewski

From ryan.q at linux.com  Mon Jan  2 00:14:06 2017
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 1 Jan 2017 16:14:06 -0800
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
Message-ID: <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>

> I tried building the packages by hand (i.e. without any help of any
> tool) and it indeed succeeded.
>
> Then I tried again using slackrepo and that's what I get:


Could it be a bug with slackrepo?

-- 
-Ryan
[ryanpcmcquen.org]

From atelszewski at gmail.com  Mon Jan  2 00:16:32 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 2 Jan 2017 01:16:32 +0100
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
Message-ID: <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>

On 02/01/17 01:14, Ryan P.C. McQuen wrote:
>> I tried building the packages by hand (i.e. without any help of any
>> tool) and it indeed succeeded.
>>
>> Then I tried again using slackrepo and that's what I get:
>
>
> Could it be a bug with slackrepo?
>

If so, then I would say, indirectly.

Maybe slackrepo does not allow to download something needed by the 
Python install script.

But it shouldn't be downloaded in the first place.

I don't know enough about Python installation scripts to say the final word.

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Mon Jan  2 00:34:16 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 2 Jan 2017 07:34:16 +0700
Subject: [Slackbuilds-users] remove sparkleshare
In-Reply-To: <c3e9350d4568051929718b5a207845be@sdf.org>
References: <c3e9350d4568051929718b5a207845be@sdf.org>
Message-ID: <001f3de0-9af5-e7aa-5b18-3f7f99924c59@slackbuilds.org>

> Can we remove sparkleshare.
> I'm the maintainer but do not use it and it's very outdated.
> I think webkit-sharp and notify-sharp can also be removed if no one is
> using them.
> I think they are only there to support sparkleshare, but I could be wrong.

Removed in a separate branch
if no objection is raised until next public update, it will be removed
permanently


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Mon Jan  2 01:12:17 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 2 Jan 2017 08:12:17 +0700
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <e12ff27a-8b2f-25af-39c0-5a08f24be156@gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <e12ff27a-8b2f-25af-39c0-5a08f24be156@gmail.com>
Message-ID: <72e52fc1-3adf-891b-ff6f-931a9d8ebf7f@slackbuilds.org>

>> libraries/chromaprint: Updated for version 1.4.
> 
> clementine fails to build here with the following:

Fixed in my branch
Thanks for reporting


-- 
Willy Sudiarto Raharjo

-------------- 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/20170102/61dd1354/attachment.asc>

From jgraha8 at gmail.com  Mon Jan  2 04:15:33 2017
From: jgraha8 at gmail.com (Jason Graham)
Date: Sun, 1 Jan 2017 23:15:33 -0500
Subject: [Slackbuilds-users] libpng12-legacy: upstream upgrade
Message-ID: <CALDF-3z0=ESe=i3xaL+tP5wiYoXt+xznmsKHsJE63_UoKBwung@mail.gmail.com>

Hi,

The upstream libpng package has been upgraded to 1.4.20 which leaves the
current download link for libpng12-legacy broken. The new links and
checksums are

DOWNLOAD="
http://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/libpng-1.4.20-i486-1_slack14.1.txz
"
MD5SUM="c706d0ab66ee2ef36570daf8f6bddd0a"
DOWNLOAD_x86_64="
http://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/libpng-1.4.20-x86_64-1_slack14.1.txz
"
MD5SUM_x86_64="0dab89c2e0203c5d81f99d53a83adf76"


Cheers,
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170101/fe55a80a/attachment.html>

From willysr at slackbuilds.org  Mon Jan  2 05:36:55 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 2 Jan 2017 12:36:55 +0700
Subject: [Slackbuilds-users] libpng12-legacy: upstream upgrade
In-Reply-To: <CALDF-3z0=ESe=i3xaL+tP5wiYoXt+xznmsKHsJE63_UoKBwung@mail.gmail.com>
References: <CALDF-3z0=ESe=i3xaL+tP5wiYoXt+xznmsKHsJE63_UoKBwung@mail.gmail.com>
Message-ID: <b17932e7-91f4-cf2d-4368-b18839ea63b5@slackbuilds.org>

> The upstream libpng package has been upgraded to 1.4.20 which leaves the
> current download link for libpng12-legacy broken. The new links and
> checksums are
> 
> DOWNLOAD="
> http://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/libpng-1.4.20-i486-1_slack14.1.txz
> "
> MD5SUM="c706d0ab66ee2ef36570daf8f6bddd0a"
> DOWNLOAD_x86_64="
> http://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/libpng-1.4.20-x86_64-1_slack14.1.txz
> "
> MD5SUM_x86_64="0dab89c2e0203c5d81f99d53a83adf76"


Thanks
Fixed in my branch and cc to maintainer


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Mon Jan  2 05:51:03 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 2 Jan 2017 12:51:03 +0700
Subject: [Slackbuilds-users] BUG: pdftk decrypt doesn't work
In-Reply-To: <neov9.816236e814.20161220120044.7580f169@loli.sombragris.org>
References: <neov9.816236e814.20161220120044.7580f169@loli.sombragris.org>
Message-ID: <cf977cc9-8b6a-7f6c-8dee-aa2978393342@slackbuilds.org>

> This was observed in Slackware64-current but it could well be the case
> with Slackware-14.2.
> 
> Using the latest pdftk from SBo, an attempt to decrypt a PDF fails:
> 
> Command Line:
> 
> $ pdftk secured.pdf input_pw mypasswd output \
> unsecured.pdf 
> 
> Output:
> 
> Error: Unexpected Exception in open_reader()
> Unhandled Java Exception in main():
> java.lang.NullPointerException
>    at gnu.gcj.runtime.NameFinder.lookup(libgcj.so.16)
>    at java.lang.Throwable.getStackTrace(libgcj.so.16)
>    at java.lang.Throwable.stackTraceString(libgcj.so.16)
>    at java.lang.Throwable.printStackTrace(libgcj.so.16)
>    at java.lang.Throwable.printStackTrace(libgcj.so.16)
> 
> 
> Thankfully I was able to decrypt the PDF afterwards using Slackware's
> stock qpdf, but I nevertheless wanted to report this in case you guys
> could find a workaround.

Hi Eduardo

I tested on slackware-current and it worked fine
I created a blank PDF with password willysr using LibreOffice export
feature and then i decrypt the file using this command:
pdftk test.pdf input_pw willysr output test_decrypted.pdf

i can open the decrypted file in Atril



-- 
Willy Sudiarto Raharjo

-------------- 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/20170102/6f249828/attachment-0001.asc>

From serban.udrea at skmail.ikp.physik.tu-darmstadt.de  Mon Jan  2 11:30:56 2017
From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea)
Date: Mon, 2 Jan 2017 12:30:56 +0100
Subject: [Slackbuilds-users] atlas failed to build with recent updates
In-Reply-To: <2901d765-8835-89eb-5373-4a230876a8bc@slackbuilds.org>
References: <CAJ6MA1HfDivB6KH0jtObaN=vAmpPOdtmECPvbdOudqTwmtWC5w@mail.gmail.com>
 <2901d765-8835-89eb-5373-4a230876a8bc@slackbuilds.org>
Message-ID: <7de976fb-649b-0577-d474-59030a624b23@skmail.ikp.physik.tu-darmstadt.de>

On 01/01/2017 01:36 AM, Willy Sudiarto Raharjo wrote:
>> When I've tried to build atlas on the fresh-installed slackware64-14.2
>> machine with all recent updates installed, I've got an error (the complete
>> log is in attachment). Similar problems was with -current installations,
>> but it is reasonable since it is not supported. The machine is HP ProDesk
>> 400
>> (Pentium 4400, all integrated in H110 chipset).
>
> Tested here in clean VM
>
> lapack-atlas:
>   MD5SUM check for lapack-3.6.1.tgz ... OK
>   Building package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK
>   Installing package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK
>
> atlas:
>   MD5SUM check for atlas3.10.3.tar.bz2 ... OK
>   Building package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
>   Installing package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
>...

Hello and Happy New Year!

Last year I got two reports about errors during ATLAS compilation, one was from 
Daniil. As Willy, I too cannot reproduce the error, which seems to be platform 
dependent and related to the fact that on the affected machines ATLAS's configure 
decides at some point to use g++ for further compilation. I'll try again to find a 
solution and probably file a bug report with ATLAS's maintainer but I cannot 
promise a solution very soon.

Best regards,

Serban Udrea

From audrius at neutrino.lt  Mon Jan  2 17:37:46 2017
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Mon, 2 Jan 2017 19:37:46 +0200
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
 <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
Message-ID: <20170102173746.GA11430@varna>

On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote:
> Maybe slackrepo does not allow to download something needed by the Python
> install script.

I don't know slackrepo well enough, but this seems likely.

> But it shouldn't be downloaded in the first place.
> 
> I don't know enough about Python installation scripts to say the final word.

borgbackup's setup.py contains the following line:

  setup_requires=['setuptools_scm>=1.7'],

Thus setuptools_scm should really be a requirement for borgbackup.

setuptools documentation has this description of setup_requires field:

  A string or list of strings specifying what other distributions need
  to be present in order for the setup script to run.  setuptools will
  attempt to obtain these (even going so far as to download them using
  EasyInstall) before processing the rest of the setup script or
  commands. <...>

This explains why the build succeeded for Willy and, if slackrepo does
indeed disable network access, why it didn't for you.

-- 
Audrius Ka?ukauskas
http://neutrino.lt/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170102/9581e4d9/attachment.asc>

From atelszewski at gmail.com  Mon Jan  2 19:13:02 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 2 Jan 2017 20:13:02 +0100
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <20170102173746.GA11430@varna>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
 <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
 <20170102173746.GA11430@varna>
Message-ID: <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>

On 02/01/17 18:37, Audrius Ka?ukauskas wrote:
> On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote:
>> Maybe slackrepo does not allow to download something needed by the Python
>> install script.
>
> I don't know slackrepo well enough, but this seems likely.
>
>> But it shouldn't be downloaded in the first place.
>>
>> I don't know enough about Python installation scripts to say the final word.
>
> borgbackup's setup.py contains the following line:
>
>   setup_requires=['setuptools_scm>=1.7'],
>
> Thus setuptools_scm should really be a requirement for borgbackup.
>
> setuptools documentation has this description of setup_requires field:
>
>   A string or list of strings specifying what other distributions need
>   to be present in order for the setup script to run.  setuptools will
>   attempt to obtain these (even going so far as to download them using
>   EasyInstall) before processing the rest of the setup script or
>   commands. <...>
>
> This explains why the build succeeded for Willy and, if slackrepo does
> indeed disable network access, why it didn't for you.
>

Thanks for clarification.
That is what I was thinking is more or less happening.

Do you know if it's possible to disable automatic downloading by the 
setup script (on the command line)?

If it is, I think we should apply this rule to SlackBuilds and then we 
had the true dependencies ;-)

-- 
Best regards,
Andrzej Telszewski

From jebrhansen+SBo at gmail.com  Mon Jan  2 20:09:20 2017
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 02 Jan 2017 20:09:20 +0000
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
 <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
 <20170102173746.GA11430@varna>
 <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>
Message-ID: <CANi9qSuUhY-bKEumTD8p_S_U_bx7t3NF8az2RHrkN6hY6JgTLQ@mail.gmail.com>

Best I could find is modifying the program's setup.cfg and add the
following:

[easy_install]
allow_hosts: None

This doesn't disable attempting to download packages (I couldn't find
anything for that), but it does prevents connections because it, obviously,
doesn't have any allowable hosts.

On Mon, Jan 2, 2017, 2:17 PM Andrzej Telszewski <atelszewski at gmail.com>
wrote:

> On 02/01/17 18:37, Audrius Ka?ukauskas wrote:
> > On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote:
> >> Maybe slackrepo does not allow to download something needed by the
> Python
> >> install script.
> >
> > I don't know slackrepo well enough, but this seems likely.
> >
> >> But it shouldn't be downloaded in the first place.
> >>
> >> I don't know enough about Python installation scripts to say the final
> word.
> >
> > borgbackup's setup.py contains the following line:
> >
> >   setup_requires=['setuptools_scm>=1.7'],
> >
> > Thus setuptools_scm should really be a requirement for borgbackup.
> >
> > setuptools documentation has this description of setup_requires field:
> >
> >   A string or list of strings specifying what other distributions need
> >   to be present in order for the setup script to run.  setuptools will
> >   attempt to obtain these (even going so far as to download them using
> >   EasyInstall) before processing the rest of the setup script or
> >   commands. <...>
> >
> > This explains why the build succeeded for Willy and, if slackrepo does
> > indeed disable network access, why it didn't for you.
> >
>
> Thanks for clarification.
> That is what I was thinking is more or less happening.
>
> Do you know if it's possible to disable automatic downloading by the
> setup script (on the command line)?
>
> If it is, I think we should apply this rule to SlackBuilds and then we
> had the true dependencies ;-)
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170102/1408aa3b/attachment.html>

From ryan.q at linux.com  Mon Jan  2 20:46:29 2017
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Mon, 2 Jan 2017 12:46:29 -0800
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
 <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
 <20170102173746.GA11430@varna>
 <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>
Message-ID: <CAAcyf-oabzRK-_SaY_AU74fXUzRsibncmpx1==AZmTAGUWMetQ@mail.gmail.com>

> Do you know if it's possible to disable automatic downloading by the setup
> script (on the command line)?
>
> If it is, I think we should apply this rule to SlackBuilds and then we had
> the true dependencies ;-)
>
This would be nearly impossible for some packages. atom, for instance has
hundreds of module dependencies.
?


-- 
-Ryan
[ryanpcmcquen.org]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170102/c1570b85/attachment-0001.html>

From atelszewski at gmail.com  Mon Jan  2 21:16:54 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 2 Jan 2017 22:16:54 +0100
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <CAAcyf-oabzRK-_SaY_AU74fXUzRsibncmpx1==AZmTAGUWMetQ@mail.gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
 <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
 <20170102173746.GA11430@varna>
 <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>
 <CAAcyf-oabzRK-_SaY_AU74fXUzRsibncmpx1==AZmTAGUWMetQ@mail.gmail.com>
Message-ID: <18771369-ab63-92c0-d10c-72c547a753d3@gmail.com>

On 02/01/17 21:46, Ryan P.C. McQuen wrote:
>
>     Do you know if it's possible to disable automatic downloading by the
>     setup script (on the command line)?
>
>     If it is, I think we should apply this rule to SlackBuilds and then
>     we had the true dependencies ;-)
>
> This would be nearly impossible for some packages. |atom|, for instance
> has hundreds of module dependencies.
>

OK. That's a bit of a shame, because it's against the philosophy we try 
to keep here (i.e. SlackBuild shall not download on its own).

-- 
Best regards,
Andrzej Telszewski

From jebrhansen+SBo at gmail.com  Mon Jan  2 21:27:54 2017
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 02 Jan 2017 21:27:54 +0000
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <18771369-ab63-92c0-d10c-72c547a753d3@gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
 <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
 <20170102173746.GA11430@varna>
 <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>
 <CAAcyf-oabzRK-_SaY_AU74fXUzRsibncmpx1==AZmTAGUWMetQ@mail.gmail.com>
 <18771369-ab63-92c0-d10c-72c547a753d3@gmail.com>
Message-ID: <CANi9qSvfx6QgeVO__KyS2EHjpChaBYfUA1-na5GMeJf45kG+LQ@mail.gmail.com>

If the dependencies are properly listed by the package maintainer, and
they're installed prior to trying to install the main package, it obviously
won't need to download any.

But if there is no real option to pass to the build/install process to
prevent downloading additional modules, that's a little frustrating. It's a
nice option for those who like it, but it should be easily disableable.

On Mon, Jan 2, 2017, 4:21 PM Andrzej Telszewski <atelszewski at gmail.com>
wrote:

> On 02/01/17 21:46, Ryan P.C. McQuen wrote:
> >
> >     Do you know if it's possible to disable automatic downloading by the
> >     setup script (on the command line)?
> >
> >     If it is, I think we should apply this rule to SlackBuilds and then
> >     we had the true dependencies ;-)
> >
> > This would be nearly impossible for some packages. |atom|, for instance
> > has hundreds of module dependencies.
> >
>
> OK. That's a bit of a shame, because it's against the philosophy we try
> to keep here (i.e. SlackBuild shall not download on its own).
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170102/e497b748/attachment.html>

From ryan.q at linux.com  Mon Jan  2 21:29:47 2017
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Mon, 02 Jan 2017 21:29:47 +0000
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <18771369-ab63-92c0-d10c-72c547a753d3@gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
 <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
 <20170102173746.GA11430@varna>
 <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>
 <CAAcyf-oabzRK-_SaY_AU74fXUzRsibncmpx1==AZmTAGUWMetQ@mail.gmail.com>
 <18771369-ab63-92c0-d10c-72c547a753d3@gmail.com>
Message-ID: <CAAcyf-riWhZVhTPTb9VhCpqCwBeLDYEww+DRiezw-4G0Ypeecw@mail.gmail.com>

This would be nearly impossible for some packages. |atom|, for instance
has hundreds of module dependencies.

OK. That?s a bit of a shame, because it?s against the philosophy we try
to keep here (i.e. SlackBuild shall not download on its own).

It?s a good philosophy, but it is not practical for a tool like slackrepo
to block scripts from doing *anything*. The classic Unix way is to allow
the user to shoot themselves in the foot ? this is why no tools are
officially endorsed by SBo other than the old fashioned way of running
everything manually. Like I said before, I?d call this a slackrepo issue,
and it should be reported to their issue tracker/mailing list.

?
-Ryan
[ryanpcmcquen.org]
?
-- 
--
[ryanpcmcquen.org]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170102/09e476d1/attachment.html>

From info at microlinux.fr  Mon Jan  2 22:00:17 2017
From: info at microlinux.fr (Nicolas Kovacs)
Date: Mon, 2 Jan 2017 23:00:17 +0100
Subject: [Slackbuilds-users] skippy-xd source missing
Message-ID: <86888f4f-07d8-6125-7250-1aed4256db30@microlinux.fr>

Hi,

Source tarball for skippy-xd is not available.

Cheers,

Niki
-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

From edps.mundognu at gmail.com  Mon Jan  2 23:10:28 2017
From: edps.mundognu at gmail.com (edps.mundognu at gmail.com)
Date: Mon, 2 Jan 2017 23:10:28 +0000 (UTC)
Subject: [Slackbuilds-users] skippy-xd source missing
References: <1720542377.5589778.1483398628672.ref@mail.yahoo.com>
Message-ID: <1720542377.5589778.1483398628672@mail.yahoo.com>

Hi!
Try this:
http://slackware.uk/sbosrcarch/by-md5/5/7/57bb5c943059ae959efd4a035d4f7279/skippy-xd-0.5.1.tar.xz

Cheers,
Edinaldo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170102/7444f986/attachment.html>

From kingbeowulf at gmail.com  Mon Jan  2 23:48:55 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 2 Jan 2017 15:48:55 -0800
Subject: [Slackbuilds-users]  Nvidia updates 375.26 commentary
Message-ID: <2c430b1c-4cbc-001c-6363-2d23fc23e118@gmail.com>

I've refactored the nvidia-drive script to use nvidia-installer instead
of sifting through all the libs and symlinks manually. This was getting
unwieldy and error-prone. The script should now be able to be updated by
just changing $VERSION. Also, GLVND and vulkan support is now possible.

As a result of these changes, nvidia-switch is gone for now. See README
to restore mesa and xorg F/OSS functionality.

Issues and help request:
1. nvidia-installer peforms a backup of mesa and xorg files but mangles
them into a weird directory tree. Is there a way to get the installer to
leave them alone for an out-of-tree install to $PKG? The
nvidia-installer backups and log are archived here:
/var/lib/nvidia-archive-2017-01-02.bz2
/var/log/nvidia-installer-2017-01-02.log
after the script runs.

2. libwfb.so does not seem to get backed up (see error below)? I've
kludged a stanza to restore libwfb after nvidia-installer's mangling but
its ugly.  The nvidia version give the error below which I can't figure
out to fix properly.

(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
[(II) Loading /usr/lib64/xorg/modules/libwfb.so
(EE) Failed to load /usr/lib64/xorg/modules/libwfb.so:
/usr/lib64/xorg/modules/libwfb.so: undefined symbol:
PictureScreenPrivateIndex
(II) UnloadModule: "wfb"
(II) Unloading wfb
(EE) Failed to load module "wfb" (loader failed, 7)
...
(EE) NVIDIA(0): Need libwfb but wfbScreenInit not found

3. COMPAT32 feedback is appreciated.  So far it looks ok (Steam and WINE).

4. I am currently unable to fully test on Slackware 32-bit.

As always, let me know if you spot anything weird.
-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/20170102/78c67b3c/attachment-0001.asc>

From willysr at slackbuilds.org  Tue Jan  3 00:37:58 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 3 Jan 2017 07:37:58 +0700
Subject: [Slackbuilds-users] skippy-xd source missing
In-Reply-To: <1720542377.5589778.1483398628672@mail.yahoo.com>
References: <1720542377.5589778.1483398628672.ref@mail.yahoo.com>
 <1720542377.5589778.1483398628672@mail.yahoo.com>
Message-ID: <71a3cab9-f04f-cf9e-c53c-069dbbafdffe@slackbuilds.org>

> Try this:
> http://slackware.uk/sbosrcarch/by-md5/5/7/57bb5c943059ae959efd4a035d4f7279/skippy-xd-0.5.1.tar.xz

Thanks
fixed in my branch


-- 
Willy Sudiarto Raharjo

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

From sombragris at sombragris.org  Tue Jan  3 02:58:29 2017
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Mon, 2 Jan 2017 23:58:29 -0300
Subject: [Slackbuilds-users] BUG: Cannot build clementine after chromaprint
 upgrade
Message-ID: <neov9.5176f41f1a.20170102235829.4e7f0565@loli.sombragris.org>

Hi there,

I'm using -current but this might happen as well with 14.2 so I report
it here.

After SBo's last ChangeLog and its chromaprint-1.4 update, clementine
cannot run anymore.

Trying to rebuild fails with the following errors:

[ 61%] Building CXX object
src/CMakeFiles/clementine_lib.dir/musicbrainz/acoustidclient.cpp.o
[ 61%] Building CXX object
src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:
In member function ?QString
Chromaprinter::CreateFingerprint()?: /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
error: invalid conversion from ?void*? to ?const int16_t* {aka const
short int*}? [-fpermissive] data.size() / 2); ^ In file included
from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:235:45:
note:   initializing argument 2 of ?int
chromaprint_feed(ChromaprintContext*, const int16_t*, int)?
CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const
int16_t *data, int size);
^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:152:72:
error: invalid conversion from ?void**? to ?uint32_t** {aka unsigned
int**}? [-fpermissive] int ret =
chromaprint_get_raw_fingerprint(chromaprint, &fprint, &size); ^ In file
included
from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:273:45:
note:   initializing argument 2 of ?int
chromaprint_get_raw_fingerprint(ChromaprintContext*, uint32_t**, int*)?
CHROMAPRINT_API int chromaprint_get_raw_fingerprint(ChromaprintContext
*ctx, uint32_t **fingerprint, int *size);
^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
error: invalid conversion from ?void*? to ?const uint32_t* {aka const
unsigned int*}? [-fpermissive] &encoded, &encoded_size, 1); ^ In file
included
from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:331:45:
note:   initializing argument 1 of ?int
chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, int*,
int)? CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t
*fp, int size, int algorithm, char **encoded_fp, int *encoded_size, int
base64);
^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
error: invalid conversion from ?void**? to ?char**? [-fpermissive]
&encoded, &encoded_size, 1); ^ In file included
from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:331:45:
note:   initializing argument 4 of ?int
chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, int*,
int)? CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t
*fp, int size, int algorithm, char **encoded_fp, int *encoded_size, int
base64); ^ At global scope: cc1plus: error: unrecognized command line
option ?-Wno-unknown-warning-option? [-Werror] cc1plus: error:
unrecognized command line option ?-Wno-unused-private-field? [-Werror]
cc1plus: all warnings being treated as errors
src/CMakeFiles/clementine_lib.dir/build.make:7366: recipe for target
'src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o'
failed make[2]: ***
[src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o]
Error 1 CMakeFiles/Makefile2:1071: recipe for target
'src/CMakeFiles/clementine_lib.dir/all' failed make[1]: ***
[src/CMakeFiles/clementine_lib.dir/all] Error 2 Makefile:127: recipe
for target 'all' failed make: *** [all] Error 2

===

btw, I'm not at all interested in "audio fingerprints". Is there a way
to get rid of this dependency?

Thanks,


Eduardo


-- 
Eduardo S?nchez Gauto, Abog., Th.M.
Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow
Tel?fono: (0991) 755-355 - Asunci?n, Paraguay
==================================================================

From willysr at slackbuilds.org  Tue Jan  3 03:04:21 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 3 Jan 2017 10:04:21 +0700
Subject: [Slackbuilds-users] BUG: Cannot build clementine after
 chromaprint upgrade
In-Reply-To: <neov9.5176f41f1a.20170102235829.4e7f0565@loli.sombragris.org>
References: <neov9.5176f41f1a.20170102235829.4e7f0565@loli.sombragris.org>
Message-ID: <7f33efa3-2431-254a-8842-cc119657670d@slackbuilds.org>

> I'm using -current but this might happen as well with 14.2 so I report
> it here.
> 
> After SBo's last ChangeLog and its chromaprint-1.4 update, clementine
> cannot run anymore.
> 
> Trying to rebuild fails with the following errors:
> 
> [ 61%] Building CXX object
> src/CMakeFiles/clementine_lib.dir/musicbrainz/acoustidclient.cpp.o
> [ 61%] Building CXX object
> src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:
> In member function ?QString
> Chromaprinter::CreateFingerprint()?: /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
> error: invalid conversion from ?void*? to ?const int16_t* {aka const
> short int*}? [-fpermissive] data.size() / 2); ^ In file included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:235:45:
> note:   initializing argument 2 of ?int
> chromaprint_feed(ChromaprintContext*, const int16_t*, int)?
> CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const
> int16_t *data, int size);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:152:72:
> error: invalid conversion from ?void**? to ?uint32_t** {aka unsigned
> int**}? [-fpermissive] int ret =
> chromaprint_get_raw_fingerprint(chromaprint, &fprint, &size); ^ In file
> included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:273:45:
> note:   initializing argument 2 of ?int
> chromaprint_get_raw_fingerprint(ChromaprintContext*, uint32_t**, int*)?
> CHROMAPRINT_API int chromaprint_get_raw_fingerprint(ChromaprintContext
> *ctx, uint32_t **fingerprint, int *size);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
> error: invalid conversion from ?void*? to ?const uint32_t* {aka const
> unsigned int*}? [-fpermissive] &encoded, &encoded_size, 1); ^ In file
> included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:331:45:
> note:   initializing argument 1 of ?int
> chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, int*,
> int)? CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t
> *fp, int size, int algorithm, char **encoded_fp, int *encoded_size, int
> base64);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
> error: invalid conversion from ?void**? to ?char**? [-fpermissive]
> &encoded, &encoded_size, 1); ^ In file included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:331:45:
> note:   initializing argument 4 of ?int
> chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, int*,
> int)? CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t
> *fp, int size, int algorithm, char **encoded_fp, int *encoded_size, int
> base64); ^ At global scope: cc1plus: error: unrecognized command line
> option ?-Wno-unknown-warning-option? [-Werror] cc1plus: error:
> unrecognized command line option ?-Wno-unused-private-field? [-Werror]
> cc1plus: all warnings being treated as errors
> src/CMakeFiles/clementine_lib.dir/build.make:7366: recipe for target
> 'src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o'
> failed make[2]: ***
> [src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o]
> Error 1 CMakeFiles/Makefile2:1071: recipe for target
> 'src/CMakeFiles/clementine_lib.dir/all' failed make[1]: ***
> [src/CMakeFiles/clementine_lib.dir/all] Error 2 Makefile:127: recipe
> for target 'all' failed make: *** [all] Error 2
> 
> ===
> 
> btw, I'm not at all interested in "audio fingerprints". Is there a way
> to get rid of this dependency?

It's fixed in my branch already
https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=9c5f47526eaef77727c6ff4eb53cdeb90c4e95b4



-- 
Willy Sudiarto Raharjo

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

From sombragris at sombragris.org  Tue Jan  3 03:08:35 2017
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Tue, 3 Jan 2017 00:08:35 -0300
Subject: [Slackbuilds-users] BUG: pdftk decrypt doesn't work
In-Reply-To: <20161220120044.7580f169@loli.sombragris.org>
References: <20161220120044.7580f169@loli.sombragris.org>
Message-ID: <neov9.317675e4c6.20170103000835.4eba650d@loli.sombragris.org>

> Hi Eduardo
> 
> I tested on slackware-current and it worked fine
> I created a blank PDF with password willysr using LibreOffice export
> feature and then i decrypt the file using this command:
> pdftk test.pdf input_pw willysr output test_decrypted.pdf
> 
> i can open the decrypted file in Atril

Hi Willy:

This leaves me completely dumbfounded.

Something I have must be messing with my system.

Thanks,

Eduardo


-- 
Eduardo S?nchez Gauto, Abog., Th.M.
Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow
Tel?fono: (0991) 755-355 - Asunci?n, Paraguay
==================================================================

From atelszewski at gmail.com  Tue Jan  3 09:59:56 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 3 Jan 2017 10:59:56 +0100
Subject: [Slackbuilds-users] Updates - 20161231.1
In-Reply-To: <CAAcyf-riWhZVhTPTb9VhCpqCwBeLDYEww+DRiezw-4G0Ypeecw@mail.gmail.com>
References: <287169e1-3659-ed67-a38b-81dbaaf93906@slackbuilds.org>
 <ba0c1349-1e3b-979e-816b-afd752729f59@gmail.com>
 <91f68c2e-ecb5-d321-2891-c59887a377f6@slackbuilds.org>
 <c9eaf585-8065-22e4-cfd4-de65fd167082@gmail.com>
 <CAAcyf-rdjJ1_4XkXARP1qE7W33M0MnsSHDDXqeb+BQ0vU45f=g@mail.gmail.com>
 <4bed6185-5eb5-4d30-c3f6-d0b0dbbfa082@gmail.com>
 <20170102173746.GA11430@varna>
 <afe974de-5354-407a-4585-9e67e06e76ce@gmail.com>
 <CAAcyf-oabzRK-_SaY_AU74fXUzRsibncmpx1==AZmTAGUWMetQ@mail.gmail.com>
 <18771369-ab63-92c0-d10c-72c547a753d3@gmail.com>
 <CAAcyf-riWhZVhTPTb9VhCpqCwBeLDYEww+DRiezw-4G0Ypeecw@mail.gmail.com>
Message-ID: <fe52798f-78ed-9fc0-10af-010c5f28a1d4@gmail.com>

On 02/01/17 22:29, Ryan P.C. McQuen wrote:
>         This would be nearly impossible for some packages. |atom|, for
>         instance
>         has hundreds of module dependencies.
>
>     OK. That?s a bit of a shame, because it?s against the philosophy we try
>     to keep here (i.e. SlackBuild shall not download on its own).
>
> It?s a good philosophy, but it is not practical for a tool like
> |slackrepo| to block scripts from doing /anything/. The classic Unix way
> is to allow the user to shoot themselves in the foot ? this is why no
> tools are officially endorsed by SBo other than the old fashioned way of
> running everything manually. Like I said before, I?d call this a
> |slackrepo| issue, and it should be reported to their issue
> tracker/mailing list.
>

Well, no ;-)

I don't blame slackrepo officially, because I don't know where the 
problem really is.

But what I really meant was that it is against SBo philosophy, forget 
about slackrepo (slackrepo just discovered the problem).

-- 
Best regards,
Andrzej Telszewski

From sombragris at sombragris.org  Tue Jan  3 13:48:55 2017
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Tue, 3 Jan 2017 10:48:55 -0300
Subject: [Slackbuilds-users] BUG: Cannot build clementine after
 chromaprint upgrade
In-Reply-To: <20170102235829.4e7f0565@loli.sombragris.org>
References: <20170102235829.4e7f0565@loli.sombragris.org>
Message-ID: <neov9.3176f8f249.20170103104855.1ae34117@loli.sombragris.org>

> It's fixed in my branch already
> https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=9c5f47526eaef77727c6ff4eb53cdeb90c4e95b4
> 

Hi Willy, now I cannot build clementine.

CMake complains of a Protobuf static library missing.

===
Building Clementine version: 1.3.1

The following components will be built:
   Box support
   D-Bus support
   Devices: Audio CD support
   Devices: DeviceKit backend
   Devices: GIO device backend
   Devices: MTP support
   Devices: iPod classic support
   Dropbox support
   Google Drive support
   Last.fm support
   Moodbar support
   Pulse audio integration
   Seafile support
   Skydrive support
   Spotify support: non-GPL binary helper
   Visualisations
   Vk.com support
   Wiimote support

The following components WILL NOT be built:
   Amazon Cloud Drive support (disabled in CMake config)
   Crash reporting (disabled in CMake config)
   Sparkle integration (missing Mac OS X, Sparkle)

CMake Error: The following variables are used in this project, but they
are set to NOTFOUND. Please set them or make sure they are set and
tested correctly in the CMake files: PROTOBUF_STATIC_LIBRARY
    linked by target "clementine-spotifyblob" in
directory /tmp/SBo/Clementine-1.3.1/ext/clementine-spotifyblob

-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/Clementine-1.3.1/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/SBo/Clementine-1.3.1/build/CMakeFiles/CMakeError.log".

===

I don't know what happened. The previous SlackBuild used to build
Clementine OK but I didn't see any changes on your branch which merited
this behavior.

Thanks,

Eduardo

En respuesta al mensaje de Eduardo Sanchez <sombragris at sombragris.org>
el Mon, 2 Jan 2017 23:58:29 -0300

> Hi there,
> 
> I'm using -current but this might happen as well with 14.2 so I report
> it here.
> 
> After SBo's last ChangeLog and its chromaprint-1.4 update, clementine
> cannot run anymore.
> 
> Trying to rebuild fails with the following errors:
> 
> [ 61%] Building CXX object
> src/CMakeFiles/clementine_lib.dir/musicbrainz/acoustidclient.cpp.o
> [ 61%] Building CXX object
> src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:
> In member function ?QString
> Chromaprinter::CreateFingerprint()?: /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
> error: invalid conversion from ?void*? to ?const int16_t* {aka const
> short int*}? [-fpermissive] data.size() / 2); ^ In file included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:235:45:
> note:   initializing argument 2 of ?int
> chromaprint_feed(ChromaprintContext*, const int16_t*, int)?
> CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const
> int16_t *data, int size);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:152:72:
> error: invalid conversion from ?void**? to ?uint32_t** {aka unsigned
> int**}? [-fpermissive] int ret =
> chromaprint_get_raw_fingerprint(chromaprint, &fprint, &size); ^ In
> file included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:273:45:
> note:   initializing argument 2 of ?int
> chromaprint_get_raw_fingerprint(ChromaprintContext*, uint32_t**,
> int*)? CHROMAPRINT_API int
> chromaprint_get_raw_fingerprint(ChromaprintContext *ctx, uint32_t
> **fingerprint, int *size);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
> error: invalid conversion from ?void*? to ?const uint32_t* {aka const
> unsigned int*}? [-fpermissive] &encoded, &encoded_size, 1); ^ In file
> included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:331:45:
> note:   initializing argument 1 of ?int
> chromaprint_encode_fingerprint(const uint32_t*, int, int, char**,
> int*, int)? CHROMAPRINT_API int chromaprint_encode_fingerprint(const
> uint32_t *fp, int size, int algorithm, char **encoded_fp, int
> *encoded_size, int base64);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
> error: invalid conversion from ?void**? to ?char**? [-fpermissive]
> &encoded, &encoded_size, 1); ^ In file included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:331:45:
> note:   initializing argument 4 of ?int
> chromaprint_encode_fingerprint(const uint32_t*, int, int, char**,
> int*, int)? CHROMAPRINT_API int chromaprint_encode_fingerprint(const
> uint32_t *fp, int size, int algorithm, char **encoded_fp, int
> *encoded_size, int base64); ^ At global scope: cc1plus: error:
> unrecognized command line option
> ?-Wno-unknown-warning-option? [-Werror] cc1plus: error: unrecognized
> command line option ?-Wno-unused-private-field? [-Werror] cc1plus:
> all warnings being treated as errors
> src/CMakeFiles/clementine_lib.dir/build.make:7366: recipe for target
> 'src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o'
> failed make[2]: ***
> [src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o]
> Error 1 CMakeFiles/Makefile2:1071: recipe for target
> 'src/CMakeFiles/clementine_lib.dir/all' failed make[1]: ***
> [src/CMakeFiles/clementine_lib.dir/all] Error 2 Makefile:127: recipe
> for target 'all' failed make: *** [all] Error 2
> 
> ===
> 
> btw, I'm not at all interested in "audio fingerprints". Is there a way
> to get rid of this dependency?
> 
> Thanks,
> 
> 
> Eduardo
> 
> 


-- 
Eduardo S?nchez Gauto, Abog., Th.M.
Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow
Tel?fono: (0991) 755-355 - Asunci?n, Paraguay
==================================================================

From willysr at slackbuilds.org  Tue Jan  3 13:54:28 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 3 Jan 2017 20:54:28 +0700
Subject: [Slackbuilds-users] BUG: Cannot build clementine after
 chromaprint upgrade
In-Reply-To: <neov9.3176f8f249.20170103104855.1ae34117@loli.sombragris.org>
References: <20170102235829.4e7f0565@loli.sombragris.org>
 <neov9.3176f8f249.20170103104855.1ae34117@loli.sombragris.org>
Message-ID: <b365a0bd-ecb6-9ef6-ffa6-889722fd1f61@slackbuilds.org>

>> It's fixed in my branch already
>> https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=9c5f47526eaef77727c6ff4eb53cdeb90c4e95b4
>>
> 
> Hi Willy, now I cannot build clementine.
> 
> CMake complains of a Protobuf static library missing.
> 
> ===
> Building Clementine version: 1.3.1
> 
> The following components will be built:
>    Box support
>    D-Bus support
>    Devices: Audio CD support
>    Devices: DeviceKit backend
>    Devices: GIO device backend
>    Devices: MTP support
>    Devices: iPod classic support
>    Dropbox support
>    Google Drive support
>    Last.fm support
>    Moodbar support
>    Pulse audio integration
>    Seafile support
>    Skydrive support
>    Spotify support: non-GPL binary helper
>    Visualisations
>    Vk.com support
>    Wiimote support
> 
> The following components WILL NOT be built:
>    Amazon Cloud Drive support (disabled in CMake config)
>    Crash reporting (disabled in CMake config)
>    Sparkle integration (missing Mac OS X, Sparkle)
> 
> CMake Error: The following variables are used in this project, but they
> are set to NOTFOUND. Please set them or make sure they are set and
> tested correctly in the CMake files: PROTOBUF_STATIC_LIBRARY
>     linked by target "clementine-spotifyblob" in
> directory /tmp/SBo/Clementine-1.3.1/ext/clementine-spotifyblob
> 
> -- Configuring incomplete, errors occurred!
> See also "/tmp/SBo/Clementine-1.3.1/build/CMakeFiles/CMakeOutput.log".
> See also "/tmp/SBo/Clementine-1.3.1/build/CMakeFiles/CMakeError.log".
> 
> ===
> 
> I don't know what happened. The previous SlackBuild used to build
> Clementine OK but I didn't see any changes on your branch which merited
> this behavior.

protobuf hasn't been changed for a long time except for deps, which was
in 2015. It never built static library AFAIK.
Since you are using current, probably best to rebuilt every deps of
Clementine just to be sure


-- 
Willy Sudiarto Raharjo

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

From matteo.bernardini at gmail.com  Tue Jan  3 13:55:17 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 3 Jan 2017 14:55:17 +0100
Subject: [Slackbuilds-users] BUG: Cannot build clementine after
 chromaprint upgrade
In-Reply-To: <neov9.3176f8f249.20170103104855.1ae34117@loli.sombragris.org>
References: <20170102235829.4e7f0565@loli.sombragris.org>
 <neov9.3176f8f249.20170103104855.1ae34117@loli.sombragris.org>
Message-ID: <CAPsDuS4gx6b3qxAZYGP8i100oZ39uyP1cvqiLzvgiYa-z1Me+A@mail.gmail.com>

2017-01-03 14:48 GMT+01:00 Eduardo Sanchez <sombragris at sombragris.org>:
>    Spotify support: non-GPL binary helper
[...]
> CMake Error: The following variables are used in this project, but they
> are set to NOTFOUND. Please set them or make sure they are set and
> tested correctly in the CMake files: PROTOBUF_STATIC_LIBRARY
>     linked by target "clementine-spotifyblob" in
> directory /tmp/SBo/Clementine-1.3.1/ext/clementine-spotifyblob

try removing spotify and launching the build again.

Matteo

From sombragris at sombragris.org  Tue Jan  3 14:37:28 2017
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Tue, 3 Jan 2017 11:37:28 -0300
Subject: [Slackbuilds-users] BUG: Cannot build clementine after
 chromaprint upgrade
In-Reply-To: <20170103104855.1ae34117@loli.sombragris.org>
References: <20170102235829.4e7f0565@loli.sombragris.org>
 <20170103104855.1ae34117@loli.sombragris.org>
Message-ID: <neov9.6176667a36.20170103113728.0881a9e2@loli.sombragris.org>

> try removing spotify and launching the build again.
> 
> Matteo

Hi Matteo (and Willy):

That did it. Clementine is now building OK.

I don't even know why I installed spotify, because I had no use for it.
It must be a required dependency on another audio player.

Thanks!

Eduardo

En respuesta al mensaje de Eduardo Sanchez <sombragris at sombragris.org>
el Tue, 3 Jan 2017 10:48:55 -0300

> > It's fixed in my branch already
> > https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=9c5f47526eaef77727c6ff4eb53cdeb90c4e95b4
> >   
> 
> Hi Willy, now I cannot build clementine.
> 
> CMake complains of a Protobuf static library missing.
> 
> ===
> Building Clementine version: 1.3.1
> 
> The following components will be built:
>    Box support
>    D-Bus support
>    Devices: Audio CD support
>    Devices: DeviceKit backend
>    Devices: GIO device backend
>    Devices: MTP support
>    Devices: iPod classic support
>    Dropbox support
>    Google Drive support
>    Last.fm support
>    Moodbar support
>    Pulse audio integration
>    Seafile support
>    Skydrive support
>    Spotify support: non-GPL binary helper
>    Visualisations
>    Vk.com support
>    Wiimote support
> 
> The following components WILL NOT be built:
>    Amazon Cloud Drive support (disabled in CMake config)
>    Crash reporting (disabled in CMake config)
>    Sparkle integration (missing Mac OS X, Sparkle)
> 
> CMake Error: The following variables are used in this project, but
> they are set to NOTFOUND. Please set them or make sure they are set
> and tested correctly in the CMake files: PROTOBUF_STATIC_LIBRARY
>     linked by target "clementine-spotifyblob" in
> directory /tmp/SBo/Clementine-1.3.1/ext/clementine-spotifyblob
> 
> -- Configuring incomplete, errors occurred!
> See also "/tmp/SBo/Clementine-1.3.1/build/CMakeFiles/CMakeOutput.log".
> See also "/tmp/SBo/Clementine-1.3.1/build/CMakeFiles/CMakeError.log".
> 
> ===
> 
> I don't know what happened. The previous SlackBuild used to build
> Clementine OK but I didn't see any changes on your branch which
> merited this behavior.
> 
> Thanks,
> 
> Eduardo
> 
> En respuesta al mensaje de Eduardo Sanchez <sombragris at sombragris.org>
> el Mon, 2 Jan 2017 23:58:29 -0300
> 
> > Hi there,
> > 
> > I'm using -current but this might happen as well with 14.2 so I
> > report it here.
> > 
> > After SBo's last ChangeLog and its chromaprint-1.4 update,
> > clementine cannot run anymore.
> > 
> > Trying to rebuild fails with the following errors:
> > 
> > [ 61%] Building CXX object
> > src/CMakeFiles/clementine_lib.dir/musicbrainz/acoustidclient.cpp.o
> > [ 61%] Building CXX object
> > src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:
> > In member function ?QString
> > Chromaprinter::CreateFingerprint()?: /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
> > error: invalid conversion from ?void*? to ?const int16_t* {aka const
> > short int*}? [-fpermissive] data.size() / 2); ^ In file included
> > from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:235:45:
> > note:   initializing argument 2 of ?int
> > chromaprint_feed(ChromaprintContext*, const int16_t*, int)?
> > CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const
> > int16_t *data, int size);
> > ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:152:72:
> > error: invalid conversion from ?void**? to ?uint32_t** {aka unsigned
> > int**}? [-fpermissive] int ret =
> > chromaprint_get_raw_fingerprint(chromaprint, &fprint, &size); ^ In
> > file included
> > from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:273:45:
> > note:   initializing argument 2 of ?int
> > chromaprint_get_raw_fingerprint(ChromaprintContext*, uint32_t**,
> > int*)? CHROMAPRINT_API int
> > chromaprint_get_raw_fingerprint(ChromaprintContext *ctx, uint32_t
> > **fingerprint, int *size);
> > ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
> > error: invalid conversion from ?void*? to ?const uint32_t* {aka
> > const unsigned int*}? [-fpermissive] &encoded, &encoded_size, 1); ^
> > In file included
> > from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:331:45:
> > note:   initializing argument 1 of ?int
> > chromaprint_encode_fingerprint(const uint32_t*, int, int, char**,
> > int*, int)? CHROMAPRINT_API int chromaprint_encode_fingerprint(const
> > uint32_t *fp, int size, int algorithm, char **encoded_fp, int
> > *encoded_size, int base64);
> > ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
> > error: invalid conversion from ?void**? to ?char**? [-fpermissive]
> > &encoded, &encoded_size, 1); ^ In file included
> > from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: /usr/include/chromaprint.h:331:45:
> > note:   initializing argument 4 of ?int
> > chromaprint_encode_fingerprint(const uint32_t*, int, int, char**,
> > int*, int)? CHROMAPRINT_API int chromaprint_encode_fingerprint(const
> > uint32_t *fp, int size, int algorithm, char **encoded_fp, int
> > *encoded_size, int base64); ^ At global scope: cc1plus: error:
> > unrecognized command line option
> > ?-Wno-unknown-warning-option? [-Werror] cc1plus: error: unrecognized
> > command line option ?-Wno-unused-private-field? [-Werror] cc1plus:
> > all warnings being treated as errors
> > src/CMakeFiles/clementine_lib.dir/build.make:7366: recipe for target
> > 'src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o'
> > failed make[2]: ***
> > [src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o]
> > Error 1 CMakeFiles/Makefile2:1071: recipe for target
> > 'src/CMakeFiles/clementine_lib.dir/all' failed make[1]: ***
> > [src/CMakeFiles/clementine_lib.dir/all] Error 2 Makefile:127: recipe
> > for target 'all' failed make: *** [all] Error 2
> > 
> > ===
> > 
> > btw, I'm not at all interested in "audio fingerprints". Is there a
> > way to get rid of this dependency?
> > 
> > Thanks,
> > 
> > 
> > Eduardo
> > 
> >   
> 
> 


-- 
Eduardo S?nchez Gauto, Abog., Th.M.
Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow
Tel?fono: (0991) 755-355 - Asunci?n, Paraguay
==================================================================

From andrew at omniarch.is  Wed Jan  4 01:45:07 2017
From: andrew at omniarch.is (Andrew Stevens)
Date: Wed, 4 Jan 2017 14:45:07 +1300
Subject: [Slackbuilds-users] No Longer Wish to Maintain Tarsnap
Message-ID: <9b9001c6-aa2a-3cd9-14b5-6eb6653c2134@omniarch.is>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Saluton,

Unfortunately, I have not truly updated tarnsap since I agreed to take
it on, I am sorry for that.

As I no longer use it nor wish to maintain it someone else make take
it if they wish or possibly remove it?

Best Regards & Happy New Year!

Andrew

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYbFOiAAoJEMK6/ajqI1fGj6AQAJcLvVdK1PtqzvcN8kCVqwY4
2oTck7i9+OHAsvx90bBE/BDhnc+orcO1Qv3ZqB1eXfxRfzVYMHFZn9pMhBAuWTSN
eRLLN9327PIEXl1Z2GGQ5DlKUpY620rUPWNcMgZfgYTaRhzoS1vflarBANYWmMP8
QFUZqpP+kQvAF7cwfoW3ImBp5aYwc5gCunjaTpHhAJKARCBXYs8cyP0bLohSg+vp
/tsdtza0KAZFSf9Un3AcSYbyiVT556CH2l6V1SN6YrWRBX+8IOI32PJUnQkFO4e+
8S5HFtCgpw8rLSzfG7fkc3SCpAetgbnDab8rFqmb0rbYngZBFIvh7cg2CnVDbso4
St0wzx6DcStbLg7cbvlJEjzHCAN+eHApm83oQ1X1gG6IlwSe30ALPvrKuSTM5jfo
RsHoGZSkCuGrpUrzb7eFkR0vvwphnsSpugqrwntF5veNv4T8ZmmfYWJtOz5cvowC
l7h18oY4vJWqAMQiLtfiOhZjOKCwAML7o9q4T33A78hU0t/8z1gIIeODqzHvRpmt
B8FW6QCdRPA9fyoSxeukxmzcUQ1EDfOz8Fn1pMrClcLTKc7VZUb6gRQD8LQEt/7f
h5cwbt/iLZYPyTHAQ0sa9Ehxkqd860FjRdrwFzyqH6Aaa9gHIe9/8MNzAewxgUf6
gBlU/69B1nXz5ydBw/FA
=XbOc
-----END PGP SIGNATURE-----

From willysr at slackbuilds.org  Wed Jan  4 05:22:34 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 4 Jan 2017 12:22:34 +0700
Subject: [Slackbuilds-users] No Longer Wish to Maintain Tarsnap
In-Reply-To: <9b9001c6-aa2a-3cd9-14b5-6eb6653c2134@omniarch.is>
References: <9b9001c6-aa2a-3cd9-14b5-6eb6653c2134@omniarch.is>
Message-ID: <e935e880-7050-7df6-7094-7944d2a6257f@slackbuilds.org>

> Unfortunately, I have not truly updated tarnsap since I agreed to take
> it on, I am sorry for that.
> 
> As I no longer use it nor wish to maintain it someone else make take
> it if they wish or possibly remove it?

Hi Andrew

At this moment, it's still up to date
I have just pushed a little cleanup and switch to i586 for x86.


-- 
Willy Sudiarto Raharjo

-------------- 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/20170104/99b948f5/attachment.asc>

From andrew at omniarch.is  Wed Jan  4 05:46:11 2017
From: andrew at omniarch.is (Andrew Stevens)
Date: Wed, 4 Jan 2017 18:46:11 +1300
Subject: [Slackbuilds-users] No Longer Wish to Maintain Tarsnap
In-Reply-To: <e935e880-7050-7df6-7094-7944d2a6257f@slackbuilds.org>
References: <9b9001c6-aa2a-3cd9-14b5-6eb6653c2134@omniarch.is>
 <e935e880-7050-7df6-7094-7944d2a6257f@slackbuilds.org>
Message-ID: <a8d94e4c-6b78-f371-0997-b39156767d75@omniarch.is>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/04/2017 06:22 PM, Willy Sudiarto Raharjo wrote:
> At this moment, it's still up to date I have just pushed a little
> cleanup and switch to i586 for x86.

Thanks Willy!

Regards,

Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYbIwjAAoJEMK6/ajqI1fGmXYP/1CJknHTNcQayvxGtLeBlmXR
+SsJYmIXt3DxfuqhvloCc6Y0NLsd4h8Sr2qUBihJNAaU141hZ/w/y0wESBrEoZDV
wcnuKCMFHVCbxGJW8XEvUBeY//teqxRPcpheQS4y4dYssTrhnxID9+pGprue+TVq
4dh8qZvbuyJ09b6y+ehSQf1re2eiSpI+txY90Thtq/6pdSINn72XVwA4lYPjHNCO
OoUgKIVqRpUBbGQlsnNizxu7glCYfZWi8lbKPLfeqBOSNHqnkKyV49Mhre0oSY1u
b4bOa3BgUuuWoUTiOO7V8wtwPSfJPWltWxhlBIYN7w9KB1qwjlvtAU3g3kValxsc
vy0IyCvpzF/CS8bpoE4pCEB8nkcW8YbNjzK/bpwXWAt9TUEr59Nx3sN1kk4XuwNL
9RyC6EJxNbMSBBUjy1nI8FD9i2GKrv6Cfkeo8bK3gyMRxSsfvqPvZaPp6RR8LMH/
/Yb2osf0A47NCsRzY3AJN4A/Jd3ggkuswSHjla86qIpZoieHWZpm10HrISRiGE6r
J7/2bU5dhS7VFiC7yLydzbfHV5Xt5Tz/W+G7AqCVRbUirQL9SauO6ObcDDDNO3lD
PHC2jQmGnTBS9u3XRZztFp0MVSDRVzw7fAC/7K8DT82I6+5f2MfFJlm/KyHS7DCZ
mYc13KkZvB/d/5sW+a6U
=0lXA
-----END PGP SIGNATURE-----

From thedoogster at gmail.com  Wed Jan  4 19:21:41 2017
From: thedoogster at gmail.com (Doogster)
Date: Wed, 4 Jan 2017 11:21:41 -0800
Subject: [Slackbuilds-users] "chocolate doom" search doesn't return
 chocolate doom
Message-ID: <CAE5oDab7VG-V65g43GecTfuQsLCkXALJQUE9GYwkJ7ZNhCUAPw@mail.gmail.com>

Searching SlackBuilds.org for "chocolate doom" doesn't return the
Chocolate DOOM SlackBuild. May we have that added as a keyword please?

From aclemons at runbox.no  Wed Jan  4 22:21:05 2017
From: aclemons at runbox.no (Andrew Clemons)
Date: Thu, 5 Jan 2017 11:21:05 +1300
Subject: [Slackbuilds-users] rlwrap
Message-ID: <20170104222104.GB1190@runbox.no>

I sent the rlwrap maintainer an email back in November since the
download link is currently dead. The last real update to the slackbuild
by the maintainer however was in March 2011. Unless someone else is
keen, I'd like to take over maintenance of the slackbuild.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170105/2d382d15/attachment.asc>

From willysr at slackbuilds.org  Thu Jan  5 00:14:45 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 5 Jan 2017 07:14:45 +0700
Subject: [Slackbuilds-users] rlwrap
In-Reply-To: <20170104222104.GB1190@runbox.no>
References: <20170104222104.GB1190@runbox.no>
Message-ID: <fa2b29a0-7ecc-f587-0579-f81d55f2a100@slackbuilds.org>

> I sent the rlwrap maintainer an email back in November since the
> download link is currently dead. The last real update to the slackbuild
> by the maintainer however was in March 2011. Unless someone else is
> keen, I'd like to take over maintenance of the slackbuild.

I have fixed the download link for next public update in my branch along
with other cleanups.

Feel free to take over after public update

Thanks

-- 
Willy Sudiarto Raharjo

-------------- 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/20170105/62d9333e/attachment.asc>

From willysr at slackbuilds.org  Thu Jan  5 00:17:09 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 5 Jan 2017 07:17:09 +0700
Subject: [Slackbuilds-users] "chocolate doom" search doesn't return
 chocolate doom
In-Reply-To: <CAE5oDab7VG-V65g43GecTfuQsLCkXALJQUE9GYwkJ7ZNhCUAPw@mail.gmail.com>
References: <CAE5oDab7VG-V65g43GecTfuQsLCkXALJQUE9GYwkJ7ZNhCUAPw@mail.gmail.com>
Message-ID: <eac5a59d-89a1-bc3f-54ae-9cdfe4f19f7c@slackbuilds.org>

> Searching SlackBuilds.org for "chocolate doom" doesn't return the
> Chocolate DOOM SlackBuild. May we have that added as a keyword please?

Done


-- 
Willy Sudiarto Raharjo

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

From serban.udrea at skmail.ikp.physik.tu-darmstadt.de  Thu Jan  5 13:03:17 2017
From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea)
Date: Thu, 5 Jan 2017 14:03:17 +0100
Subject: [Slackbuilds-users] atlas failed to build with recent updates
In-Reply-To: <7de976fb-649b-0577-d474-59030a624b23@skmail.ikp.physik.tu-darmstadt.de>
References: <CAJ6MA1HfDivB6KH0jtObaN=vAmpPOdtmECPvbdOudqTwmtWC5w@mail.gmail.com>
 <2901d765-8835-89eb-5373-4a230876a8bc@slackbuilds.org>
 <7de976fb-649b-0577-d474-59030a624b23@skmail.ikp.physik.tu-darmstadt.de>
Message-ID: <3d88ddfa-61c2-7120-a076-fe86f87ad184@skmail.ikp.physik.tu-darmstadt.de>

On 01/02/2017 12:30 PM, Serban Udrea wrote:
> ...
>
> Hello and Happy New Year!
>
> Last year I got two reports about errors during ATLAS compilation, one was from
> Daniil. As Willy, I too cannot reproduce the error, which seems to be platform
> dependent and related to the fact that on the affected machines ATLAS's configure
> decides at some point to use g++ for further compilation. I'll try again to find a
> solution and probably file a bug report with ATLAS's maintainer but I cannot
> promise a solution very soon.
> ...

Hello!

With Daniil's help and patience I can provide a workaround to this problem: before 
using the SlackBuild rename /usr/bin/g++-gcc-5.3.0 to something not containing 
gcc, but don't use just g++ for the new name.  Rename it back after ATLAS got 
compiled. Finally make sure /usr/bin/g++ is a proper link to /usr/bin/g++-gcc-5.3.0.

I'll file a bug report and see what ATLAS's maintainer comes up with.

Best regards,

Serban Udrea

From rshepard at appl-ecosys.com  Thu Jan  5 16:28:50 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 5 Jan 2017 08:28:50 -0800 (PST)
Subject: [Slackbuilds-users] GunCash-2.6.15 build fails
Message-ID: <alpine.LNX.2.11.1701050828340.2496@localhost>

   Yesterday I tried to build gnucash-2.6.15 after changing the version
number in the 2.6.13 script; the attempt fails:

../../src/register/ledger-core/.libs/libgncmod-ledger-core.so: undefined 
reference
to `gnc_recn_cell_set_read_only'
collect2: error: ld returned 1 exit status
make[4]: *** [gnucash] Error 1
make[4]: Leaving directory /tmp/SBo/gnucash-2.6.15/src/bin'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory /tmp/SBo/gnucash-2.6.15/src/bin'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory /tmp/SBo/gnucash-2.6.15/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory /tmp/SBo/gnucash-2.6.15'
make: *** [all] Error 2

   Please advise me how to remedy this condition so I can upgrade to the
latest version.

Regards,

Rich

From baildon.research at googlemail.com  Thu Jan  5 16:51:53 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 5 Jan 2017 16:51:53 +0000
Subject: [Slackbuilds-users] GunCash-2.6.15 build fails
In-Reply-To: <alpine.LNX.2.11.1701050828340.2496@localhost>
References: <alpine.LNX.2.11.1701050828340.2496@localhost>
Message-ID: <CAMt7G9R-+GyKDfPANcMVp5M-Gz1PgYTcfepxdi6faN0ZaRGfnw@mail.gmail.com>

> ../../src/register/ledger-core/.libs/libgncmod-ledger-core.so: undefined
> reference
> to `gnc_recn_cell_set_read_only'
> collect2: error: ld returned 1 exit status

Hey Rich, you're not the only one to have had this problem:

https://groups.google.com/forum/#!topic/muc.lists.freebsd.ports/ErCEEouw6w0

>From that conversation, you probably need to remove the old version of
gnucash before you build the new version of gnucash.  That's not an
uncommon scenario -- e.g. Patrick's slackbuild for git ;-)

Cheers
-D.

From rshepard at appl-ecosys.com  Thu Jan  5 16:55:42 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 5 Jan 2017 08:55:42 -0800 (PST)
Subject: [Slackbuilds-users] GunCash-2.6.15 build fails
In-Reply-To: <CAMt7G9R-+GyKDfPANcMVp5M-Gz1PgYTcfepxdi6faN0ZaRGfnw@mail.gmail.com>
References: <alpine.LNX.2.11.1701050828340.2496@localhost>
 <CAMt7G9R-+GyKDfPANcMVp5M-Gz1PgYTcfepxdi6faN0ZaRGfnw@mail.gmail.com>
Message-ID: <alpine.LNX.2.11.1701050853450.2496@localhost>

On Thu, 5 Jan 2017, David Spencer wrote:

> Hey Rich, you're not the only one to have had this problem:

David,

   I tried searching the web but found nothing relevant.

> From that conversation, you probably need to remove the old version of
> gnucash before you build the new version of gnucash. That's not an
> uncommon scenario -- e.g. Patrick's slackbuild for git ;-)

   Seeing this nudges a vague memory that this is written somewhere in
gnucash docs or web site. I'll remove the old version.

Thanks,

Rich

From rshepard at appl-ecosys.com  Thu Jan  5 17:14:37 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 5 Jan 2017 09:14:37 -0800 (PST)
Subject: [Slackbuilds-users] GunCash-2.6.15 build fails [FIXED]
In-Reply-To: <alpine.LNX.2.11.1701050853450.2496@localhost>
References: <alpine.LNX.2.11.1701050828340.2496@localhost>
 <CAMt7G9R-+GyKDfPANcMVp5M-Gz1PgYTcfepxdi6faN0ZaRGfnw@mail.gmail.com>
 <alpine.LNX.2.11.1701050853450.2496@localhost>
Message-ID: <alpine.LNX.2.11.1701050911200.2496@localhost>

On Thu, 5 Jan 2017, Rich Shepard wrote:

>  Seeing this nudges a vague memory that this is written somewhere in
> gnucash docs or web site. I'll remove the old version.

David,

   That did the trick. Highly unusual requirement, at least for all the
software I've used.

   What threw me off is that when I installed 2.6.13 I had forgotten that
2.6.12 was installed from some time last year (but not used then). So,
2.6.13 built and installed just fine. When I discovered I had two versions
installed I removed the 2.6.12 package. Why 2.6.13 built with an installed
earlier version, but 2.6.15 wouldn't might never be known, but is now moot.

Thanks very much,

Rich

From reedych at reedych.pw  Thu Jan  5 19:42:18 2017
From: reedych at reedych.pw (reedych)
Date: Fri, 6 Jan 2017 01:42:18 +0600
Subject: [Slackbuilds-users] i3 is not building
Message-ID: <20170106014218.6c1d7db6@slackware>

I compiled on slackware arm current with aarch64 kernel 4.8.15. That's log: http://pastebin.com/pGq11hm7

Also, this message has log too.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: i3.log
Type: text/x-log
Size: 104322 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170106/1935755e/attachment-0001.bin>

From willysr at slackbuilds.org  Thu Jan  5 19:56:22 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 6 Jan 2017 02:56:22 +0700
Subject: [Slackbuilds-users] i3 is not building
In-Reply-To: <20170106014218.6c1d7db6@slackware>
References: <20170106014218.6c1d7db6@slackware>
Message-ID: <e6cd8c14-f7d9-1e48-4e6d-a2e9f2a6a094@slackbuilds.org>

> I compiled on slackware arm current with aarch64 kernel 4.8.15. That's log: http://pastebin.com/pGq11hm7
> 
> Also, this message has log too.

Works fine in slackware64-14.2

yajl:
  MD5SUM check for lloyd-yajl-2.1.0-0-ga0ecdde.tar.gz ... OK
  Building package yajl-2.1.0-x86_64-2_SBo.tgz ... OK
  Installing package yajl-2.1.0-x86_64-2_SBo.tgz ... OK

xcb-util-xrm:
  MD5SUM check for xcb-util-xrm-1.0.tar.bz2 ... OK
  Building package xcb-util-xrm-1.0-x86_64-1_SBo.tgz ... OK
  Installing package xcb-util-xrm-1.0-x86_64-1_SBo.tgz ... OK

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

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

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

i3:
  MD5SUM check for i3-4.13.tar.bz2 ... OK
  Building package i3-4.13-x86_64-1_SBo.tgz ... OK
  Installing package i3-4.13-x86_64-1_SBo.tgz ... OK


-- 
Willy Sudiarto Raharjo

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

From baildon.research at googlemail.com  Thu Jan  5 21:35:21 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 5 Jan 2017 21:35:21 +0000
Subject: [Slackbuilds-users] i3 is not building
In-Reply-To: <20170106014218.6c1d7db6@slackware>
References: <20170106014218.6c1d7db6@slackware>
Message-ID: <CAMt7G9T_xoEF42AsP1ErhKxA9wVAO_=fo1XBdLcsAGuyV2DR7w@mail.gmail.com>

>From your pastebin:

checking for asciidoc... no
checking for xmlto... no
checking for pod2man... /usr/bin/pod2man
[...]
--------------------------------------------------------------------------------
build configured:

  i3 version:             4.13 (2016-11-08)
  is release version:     yes

  build manpages:         no
  build docs:             no

and then your error:

find: `/tmp/SBo/package-i3/usr/man': No such file or directory

Looks pretty obvious to me.  You don't have linuxdoc-tools installed
(which contains asciidoc), so i3 didn't build and install the docs and
manpages, so the SlackBuild failed.

-D.

From chytraeu at sdf.org  Fri Jan  6 00:01:57 2017
From: chytraeu at sdf.org (chytraeu)
Date: Thu, 05 Jan 2017 18:01:57 -0600
Subject: [Slackbuilds-users] wrong md5sum for lxml-3.7.1.tar.gz
Message-ID: <337054b9044200fd9c08503965e7f64c@sdf.org>


hello,
while downloading lxml-3.7.1.tar.gz I'm repeatedly getting the wrong 
md5sum.

2017-01-05 17:56:40 (243 KB/s) - ?lxml-lxml-3.7.1.tar.gz? saved 
[925193/925193]

Found lxml-lxml-3.7.1.tar.gz in /var/cache/sbopkg/distfiles.
Checking MD5SUM:
   MD5SUM check for lxml-lxml-3.7.1.tar.gz ... FAILED!
     Expected: 1fd1051aa08437f54d1e18c3b80342b
     Found:    e1fd1051aa08437f54d1e18c3b80342b


---
Regards,
Donald Cooley


From larryhaja at gmail.com  Fri Jan  6 00:39:36 2017
From: larryhaja at gmail.com (Larry Hajali)
Date: Thu, 5 Jan 2017 16:39:36 -0800
Subject: [Slackbuilds-users] wrong md5sum for lxml-3.7.1.tar.gz
In-Reply-To: <337054b9044200fd9c08503965e7f64c@sdf.org>
References: <337054b9044200fd9c08503965e7f64c@sdf.org>
Message-ID: <CAAZPBMjdprqifai73+eq7GcHLqvP0uT3gnFZ1NBA2sHY8HGgCw@mail.gmail.com>

This has been fixed in Willy's branch.  It will be available in the next
update.

https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=bfd7f4fd196469eb6b575e3c5bc961224685c699

--Larry

On Thu, Jan 5, 2017 at 4:01 PM, chytraeu <chytraeu at sdf.org> wrote:

>
> hello,
> while downloading lxml-3.7.1.tar.gz I'm repeatedly getting the wrong
> md5sum.
>
> 2017-01-05 17:56:40 (243 KB/s) - ?lxml-lxml-3.7.1.tar.gz? saved
> [925193/925193]
>
> Found lxml-lxml-3.7.1.tar.gz in /var/cache/sbopkg/distfiles.
> Checking MD5SUM:
>   MD5SUM check for lxml-lxml-3.7.1.tar.gz ... FAILED!
>     Expected: 1fd1051aa08437f54d1e18c3b80342b
>     Found:    e1fd1051aa08437f54d1e18c3b80342b
>
>
> ---
> Regards,
> Donald Cooley
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170105/8576aebe/attachment.html>

From brent at exitstatusone.com  Fri Jan  6 03:22:25 2017
From: brent at exitstatusone.com (Brenton Earl)
Date: Thu, 5 Jan 2017 20:22:25 -0700
Subject: [Slackbuilds-users] zim wiki crashes, python 2.7.13 update
Message-ID: <20170106032225.GA11754@gmail.com>

Hello,

Zim wiki seems to crash with the recent update to python 2.7.13.  There
is a work around to launch Zim:

> zim --standalone

A bug report has been filed upstream here:

https://bugs.launchpad.net/zim/+bug/1618410

I attached the error message to this email.  Reproduced in a fresh
virtual machine of Slackware x86 and x86_64 14.2.  Can anyone else
reproduce this?  Any suggestions are welcome.

Thanks,
Brenton Earl
-------------- next part --------------
This is zim 0.65
Platform: posix
Locale: en_US ISO8859-1
FS encoding: utf-8
Python: (2, 7, 13, 'final', 0)
Gtk: (2, 24, 31)
Pygtk: (2, 24, 0)
Zim revision is:
  branch: zim-trunk
  revision: 805 [protected email]-20151101144245-0g7s8a7qjt5xu1d0
  date: 2015-11-01 15:42:45 +0100

======= Traceback =======
  File "/usr/lib64/python2.7/site-packages/zim/main.py", line 446, in main
    obj.run()
  File "/usr/lib64/python2.7/site-packages/zim/main.py", line 211, in run
    zim.ipc.start_server_if_not_running()
  File "/usr/lib64/python2.7/site-packages/zim/ipc.py", line 283, in start_server_if_not_running
    raise AssertionError, 'Failed to start server (spawning)'
AssertionError: Failed to start server (spawning)

From reedych at reedych.pw  Fri Jan  6 07:19:15 2017
From: reedych at reedych.pw (reedych)
Date: Fri, 6 Jan 2017 13:19:15 +0600
Subject: [Slackbuilds-users] i3 is not building
In-Reply-To: <CAMt7G9T_xoEF42AsP1ErhKxA9wVAO_=fo1XBdLcsAGuyV2DR7w@mail.gmail.com>
References: <20170106014218.6c1d7db6@slackware>
 <CAMt7G9T_xoEF42AsP1ErhKxA9wVAO_=fo1XBdLcsAGuyV2DR7w@mail.gmail.com>
Message-ID: <20170106131915.49d96ef6@slackware>

? Thu, 5 Jan 2017 21:35:21 +0000
David Spencer <baildon.research at googlemail.com> ?????:

> From your pastebin:
> 
> checking for asciidoc... no
> checking for xmlto... no
> checking for pod2man... /usr/bin/pod2man
> [...]
> --------------------------------------------------------------------------------
> build configured:
> 
>   i3 version:             4.13 (2016-11-08)
>   is release version:     yes
> 
>   build manpages:         no
>   build docs:             no
> 
> and then your error:
> 
> find: `/tmp/SBo/package-i3/usr/man': No such file or directory
> 
> Looks pretty obvious to me.  You don't have linuxdoc-tools installed
> (which contains asciidoc), so i3 didn't build and install the docs and
> manpages, so the SlackBuild failed.
> 
> -D.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

Oh, thanks!

From willysr at slackbuilds.org  Fri Jan  6 09:34:41 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 6 Jan 2017 16:34:41 +0700
Subject: [Slackbuilds-users] zim wiki crashes, python 2.7.13 update
In-Reply-To: <20170106032225.GA11754@gmail.com>
References: <20170106032225.GA11754@gmail.com>
Message-ID: <f32338a6-50e1-83c4-afaf-c85c7c9be2b3@slackbuilds.org>

> Zim wiki seems to crash with the recent update to python 2.7.13.  There
> is a work around to launch Zim:
> 
>> zim --standalone
> 
> A bug report has been filed upstream here:
> 
> https://bugs.launchpad.net/zim/+bug/1618410
> 
> I attached the error message to this email.  Reproduced in a fresh
> virtual machine of Slackware x86 and x86_64 14.2.  Can anyone else
> reproduce this?  Any suggestions are welcome.

Works on current machine with same Python 2.7.13
probably a bug caused by the way Python was compiled? (UCS-2 vs UCS-4)



-- 
Willy Sudiarto Raharjo

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

From lists at osh.id.au  Fri Jan  6 13:31:47 2017
From: lists at osh.id.au (David O'Shaughnessy)
Date: Fri, 6 Jan 2017 23:31:47 +1000
Subject: [Slackbuilds-users] BUG: Cannot build clementine after
 chromaprint upgrade
In-Reply-To: <b365a0bd-ecb6-9ef6-ffa6-889722fd1f61@slackbuilds.org>
References: <20170102235829.4e7f0565@loli.sombragris.org>
 <neov9.3176f8f249.20170103104855.1ae34117@loli.sombragris.org>
 <b365a0bd-ecb6-9ef6-ffa6-889722fd1f61@slackbuilds.org>
Message-ID: <e02807f4-fbff-f719-242f-3ab7be597915@osh.id.au>

I also can't build Clementine after upgrading chromaprint. I don't have
Spotify installed, but building Clementine still fails with various
Chromaprint error messages;

/tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp: In member
function ?QString Chromaprinter::CreateFingerprint()?:
/tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
error: invalid conversion from ?void*? to ?const int16_t* {aka const
short int*}? [-fpermissive]
                    data.size() / 2);
                                   ^

I tried rebuilding all the dependencies (chromaprint cryptopp
libechonest pytz six python-dateutil python-gflags protobuf) but that
didn't seem to help.

--
Dave

On 01/03/2017 11:54 PM, Willy Sudiarto Raharjo wrote:
>>> It's fixed in my branch already
>>> https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=9c5f47526eaef77727c6ff4eb53cdeb90c4e95b4
>>>
>>
>> Hi Willy, now I cannot build clementine.
>>
>> CMake complains of a Protobuf static library missing.
>>
>> ===
>> Building Clementine version: 1.3.1
>>
>> The following components will be built:
>>    Box support
>>    D-Bus support
>>    Devices: Audio CD support
>>    Devices: DeviceKit backend
>>    Devices: GIO device backend
>>    Devices: MTP support
>>    Devices: iPod classic support
>>    Dropbox support
>>    Google Drive support
>>    Last.fm support
>>    Moodbar support
>>    Pulse audio integration
>>    Seafile support
>>    Skydrive support
>>    Spotify support: non-GPL binary helper
>>    Visualisations
>>    Vk.com support
>>    Wiimote support
>>
>> The following components WILL NOT be built:
>>    Amazon Cloud Drive support (disabled in CMake config)
>>    Crash reporting (disabled in CMake config)
>>    Sparkle integration (missing Mac OS X, Sparkle)
>>
>> CMake Error: The following variables are used in this project, but they
>> are set to NOTFOUND. Please set them or make sure they are set and
>> tested correctly in the CMake files: PROTOBUF_STATIC_LIBRARY
>>     linked by target "clementine-spotifyblob" in
>> directory /tmp/SBo/Clementine-1.3.1/ext/clementine-spotifyblob
>>
>> -- Configuring incomplete, errors occurred!
>> See also "/tmp/SBo/Clementine-1.3.1/build/CMakeFiles/CMakeOutput.log".
>> See also "/tmp/SBo/Clementine-1.3.1/build/CMakeFiles/CMakeError.log".
>>
>> ===
>>
>> I don't know what happened. The previous SlackBuild used to build
>> Clementine OK but I didn't see any changes on your branch which merited
>> this behavior.
> 
> protobuf hasn't been changed for a long time except for deps, which was
> in 2015. It never built static library AFAIK.
> Since you are using current, probably best to rebuilt every deps of
> Clementine just to be sure

From willysr at slackbuilds.org  Fri Jan  6 13:31:47 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 6 Jan 2017 20:31:47 +0700
Subject: [Slackbuilds-users] BUG: Cannot build clementine after
 chromaprint upgrade
In-Reply-To: <e02807f4-fbff-f719-242f-3ab7be597915@osh.id.au>
References: <20170102235829.4e7f0565@loli.sombragris.org>
 <neov9.3176f8f249.20170103104855.1ae34117@loli.sombragris.org>
 <b365a0bd-ecb6-9ef6-ffa6-889722fd1f61@slackbuilds.org>
 <e02807f4-fbff-f719-242f-3ab7be597915@osh.id.au>
Message-ID: <bf2855f7-faac-84f2-e9dd-52a826e93d40@slackbuilds.org>

> I also can't build Clementine after upgrading chromaprint. I don't have
> Spotify installed, but building Clementine still fails with various
> Chromaprint error messages;
> 
> /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp: In member
> function ?QString Chromaprinter::CreateFingerprint()?:
> /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
> error: invalid conversion from ?void*? to ?const int16_t* {aka const
> short int*}? [-fpermissive]
>                     data.size() / 2);
>                                    ^
> 
> I tried rebuilding all the dependencies (chromaprint cryptopp
> libechonest pytz six python-dateutil python-gflags protobuf) but that
> didn't seem to help.

Hi David

did you use Clementine from SlackBuild repository or the one in my
branch which is already updated with a patch?


-- 
Willy Sudiarto Raharjo

-------------- 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/20170106/67d29916/attachment.asc>

From lists at osh.id.au  Fri Jan  6 13:49:05 2017
From: lists at osh.id.au (David O'Shaughnessy)
Date: Fri, 6 Jan 2017 23:49:05 +1000
Subject: [Slackbuilds-users] BUG: Cannot build clementine after
 chromaprint upgrade
In-Reply-To: <bf2855f7-faac-84f2-e9dd-52a826e93d40@slackbuilds.org>
References: <20170102235829.4e7f0565@loli.sombragris.org>
 <neov9.3176f8f249.20170103104855.1ae34117@loli.sombragris.org>
 <b365a0bd-ecb6-9ef6-ffa6-889722fd1f61@slackbuilds.org>
 <e02807f4-fbff-f719-242f-3ab7be597915@osh.id.au>
 <bf2855f7-faac-84f2-e9dd-52a826e93d40@slackbuilds.org>
Message-ID: <56fe6824-a937-c355-d79d-861f2826b74f@osh.id.au>

Just the one from the SBo repo, I didn't realise that it was already
fixed in your branch :) Thanks!

--
Dave

On 01/06/2017 11:31 PM, Willy Sudiarto Raharjo wrote:
>> I also can't build Clementine after upgrading chromaprint. I don't have
>> Spotify installed, but building Clementine still fails with various
>> Chromaprint error messages;
>>
>> /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp: In member
>> function ?QString Chromaprinter::CreateFingerprint()?:
>> /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
>> error: invalid conversion from ?void*? to ?const int16_t* {aka const
>> short int*}? [-fpermissive]
>>                     data.size() / 2);
>>                                    ^
>>
>> I tried rebuilding all the dependencies (chromaprint cryptopp
>> libechonest pytz six python-dateutil python-gflags protobuf) but that
>> didn't seem to help.
> 
> Hi David
> 
> did you use Clementine from SlackBuild repository or the one in my
> branch which is already updated with a patch?

From kjhambrick at gmail.com  Fri Jan  6 14:43:21 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 6 Jan 2017 08:43:21 -0600
Subject: [Slackbuilds-users] xrdp patch for Slackware64 14.2 Multilib
Message-ID: <CANBHt+P50OnJDhJTXW0qVih=nyDeoEMHUOHO7bJ1pbWVzeDp0A@mail.gmail.com>

All --

xrdp fails to build on Slackware64 14.2 + Multilib because of a hard-coded
-L/usr/X11R6/lib path in two Makefile.am files.

The pttached Patch ixes the path for a 64-bit system.

Thanks for all that you're doing !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170106/f79019c3/attachment.html>
-------------- next part --------------
--- xrdp.SlackBuild.orig	2016-07-06 19:24:08.939843440 -0500
+++ xrdp.SlackBuild	2017-01-06 08:38:20.313337212 -0600
@@ -62,7 +62,16 @@
 else
     NOPAM_OPT=""
 fi
+#
+# kjh added this
+#
+if [ "$ARCH" = "x86_64" ]
+then
 
+   sed -i -e 's|-L/usr/X11R6/lib|-L/usr/X11R6/lib64|' ./genkeymap/Makefile.am
+   sed -i -e 's|-L/usr/X11R6/lib|-L/usr/X11R6/lib64|' ./sesman/chansrv/Makefile.am
+
+fi
 # patches from Mancha
 patch -p1 < $CWD/xrdp-v0.6.1_disabled.diff
 patch -p1 < $CWD/xrdp-v0.6.1_crypt.diff

From brent at exitstatusone.com  Fri Jan  6 17:28:02 2017
From: brent at exitstatusone.com (Brenton Earl)
Date: Fri, 6 Jan 2017 10:28:02 -0700
Subject: [Slackbuilds-users] zim wiki crashes, python 2.7.13 update
In-Reply-To: <f32338a6-50e1-83c4-afaf-c85c7c9be2b3@slackbuilds.org>
References: <20170106032225.GA11754@gmail.com>
 <f32338a6-50e1-83c4-afaf-c85c7c9be2b3@slackbuilds.org>
Message-ID: <20170106172802.GA1968@gmail.com>

On Fri, Jan 06, 2017 at 04:34:41PM +0700, Willy Sudiarto Raharjo wrote:
> > Zim wiki seems to crash with the recent update to python 2.7.13.  There
> > is a work around to launch Zim:
> > 
> >> zim --standalone
> > 
> > A bug report has been filed upstream here:
> > 
> > https://bugs.launchpad.net/zim/+bug/1618410
> > 
> > I attached the error message to this email.  Reproduced in a fresh
> > virtual machine of Slackware x86 and x86_64 14.2.  Can anyone else
> > reproduce this?  Any suggestions are welcome.
> 
> Works on current machine with same Python 2.7.13
> probably a bug caused by the way Python was compiled? (UCS-2 vs UCS-4)
> 

In short, rebuild python 2.7.13 and this problem will be fixed.  Remove
your $HOME/.config/zim and $HOME/.cache/zim.  Start zim as normal.

The issue lies in the python multiprocessing module.  Zim is unable to
start up because it cannot import the required module.

The following will return the import error:

> python -c "from _multiprocessing import SemLock"

This problem can be seen if you run zim in debug mode during the first
launch of the application.  See attached log.

Thanks,
Brenton Earl
-------------- next part --------------
bash-4.3$ zim -D
WARNING: Can not import 'xdg.Mime' - falling back to 'mimetypes'
WARNING: Filesystem encoding is set to ASCII or Latin1, using UTF-8 
instead
INFO: This is zim 0.65
DEBUG: Python version is sys.version_info(major=2, minor=7, micro=13, 
releaselevel='final', serial=0)
DEBUG: Platform is posix
DEBUG: Zim revision is:
  branch: zim-trunk
  revision: 805 
jaap.karssenberg at gmail.com-20151101144245-0g7s8a7qjt5xu1d0
  date: 2015-11-01 15:42:45 +0100
DEBUG: Not running from a source dir
DEBUG: Set XDG_DATA_HOME to /home/el0226/.local/share
DEBUG: Set XDG_DATA_DIRS to [<Dir: /usr/share>, <Dir: 
/usr/local/share>]
DEBUG: Set XDG_CONFIG_HOME to /home/el0226/.config
DEBUG: Set XDG_CONFIG_DIRS to [<Dir: /etc/xdg>, <Dir: /etc/kde/xdg>]
DEBUG: Set XDG_CACHE_HOME to /home/el0226/.cache
DEBUG: First time usage - prompt for notebook folder
DEBUG: Loading config from: /home/el0226/Notebooks/Notes/notebook.zim
DEBUG: Opening dialog "Add Notebook - Zim"
DEBUG: Dialog response OK
DEBUG: Closed dialog "Add Notebook"
DEBUG: Loading config from: /home/el0226/Notebooks/Notes/notebook.zim
DEBUG: Wrote /home/el0226/Notebooks/Notes/notebook.zim
DEBUG: Wrote /home/el0226/.config/zim/notebooks.list
DEBUG: Wrote /home/el0226/Notebooks/Notes/.zim/tmp
INFO: Remove file: /home/el0226/Notebooks/Notes/.zim/tmp
DEBUG: Loading config from: /home/el0226/Notebooks/Notes/notebook.zim
DEBUG: Cache dir: 
/home/el0226/.cache/zim/notebook-home_el0226_Notebooks_Notes
DEBUG: Index database file: 
/home/el0226/.cache/zim/notebook-home_el0226_Notebooks_Notes/index.db
INFO: Flushing index
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Starting server by spawning new process
INFO: Spawning: ['/usr/bin/zim', '--ipc-server-main', 
'/tmp/zim-el0226/zim-server-socket', '10'] (cwd: None)
DEBUG: Process started with PID: 4762
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
WARNING: Can not import 'xdg.Mime' - falling back to 'mimetypes'
WARNING: Filesystem encoding is set to ASCII or Latin1, using UTF-8 
instead
Traceback (most recent call last):
  File "/usr/bin/zim", line 50, in <module>
    zim.ipc.handle_argv()
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 124, in 
handle_argv
    servermain()
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 352, in 
servermain
    server = Server()
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 384, in 
__init__
    self.logqueue = multiprocessing.Queue()
  File "/usr/lib/python2.7/multiprocessing/__init__.py", line 217, in 
Queue
    from multiprocessing.queues import Queue
  File "/usr/lib/python2.7/multiprocessing/queues.py", line 48, in 
<module>
    from .synchronize import Lock, BoundedSemaphore, Semaphore, 
Condition
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 59, 
in <module>
    " function, see issue 3770.")
ImportError: This platform lacks a functioning sem_open 
implementation, therefore, the required synchronization primitives 
needed will not function, see issue 3770.
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 4758: <RemoteMethodCall: 4758: 
zim.ipc.Server(None).ping((), {})>
DEBUG: Cannot connect to server 4758:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 273, in 
start_server_if_not_running
    s.ping()
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 763, in 
call
    conn = Client(SERVER_ADDRESS, SERVER_ADDRESS_FAMILY)
  File "/usr/lib/python2.7/multiprocessing/connection.py", line 169, 
in Client
    c = SocketClient(address)
  File "/usr/lib/python2.7/multiprocessing/connection.py", line 308, 
in SocketClient
    s.connect(address)
  File "/usr/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
error: [Errno 2] No such file or directory

ERROR: Exception in main()
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/zim/main.py", line 446, in 
main
    obj.run()
  File "/usr/lib/python2.7/site-packages/zim/main.py", line 211, in 
run
    zim.ipc.start_server_if_not_running()
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 283, in 
start_server_if_not_running
    raise AssertionError, 'Failed to start server (spawning)'
AssertionError: Failed to start server (spawning)
DEBUG: Running ErrorDialog


From larryhaja at gmail.com  Fri Jan  6 19:58:57 2017
From: larryhaja at gmail.com (Larry Hajali)
Date: Fri, 6 Jan 2017 11:58:57 -0800
Subject: [Slackbuilds-users] zim wiki crashes, python 2.7.13 update
In-Reply-To: <20170106172802.GA1968@gmail.com>
References: <20170106032225.GA11754@gmail.com>
 <f32338a6-50e1-83c4-afaf-c85c7c9be2b3@slackbuilds.org>
 <20170106172802.GA1968@gmail.com>
Message-ID: <CAAZPBMhBjD2yy5pLqkU_vn9wFc9oDuWtyHk4kTvoiTMVZ-XuXQ@mail.gmail.com>

The new version of python also affects building qt5.

Updating projects from gyp files...
Traceback (most recent call last):
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/tools/buildscripts/gyp_qtwebengine",
line 178, in <module>
    sys.exit(gyp.main(args))
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py",
line 538, in main
    return gyp_main(args)
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py",
line 514, in gyp_main
    options.duplicate_basename_check)
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py",
line 130, in Load
    params['parallel'], params['root_targets'])
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/input.py",
line 2759, in Load
    check, generator_input_info)
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/input.py",
line 596, in LoadTargetBuildFilesParallel
    parallel_state.pool = multiprocessing.Pool(multiprocessing.cpu_count())
  File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 232, in Pool
    return Pool(processes, initializer, initargs, maxtasksperchild)
  File "/usr/lib64/python2.7/multiprocessing/pool.py", line 138, in __init__
    self._setup_queues()
  File "/usr/lib64/python2.7/multiprocessing/pool.py", line 233, in
_setup_queues
    from .queues import SimpleQueue
  File "/usr/lib64/python2.7/multiprocessing/queues.py", line 48, in
<module>
    from .synchronize import Lock, BoundedSemaphore, Semaphore, Condition
  File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 59, in
<module>
    " function, see issue 3770.")
ImportError: This platform lacks a functioning sem_open implementation,
therefore, the required synchronization primitives needed will not
function, see issue 3770.

--Larry

On Fri, Jan 6, 2017 at 9:28 AM, Brenton Earl <brent at exitstatusone.com>
wrote:

> On Fri, Jan 06, 2017 at 04:34:41PM +0700, Willy Sudiarto Raharjo wrote:
> > > Zim wiki seems to crash with the recent update to python 2.7.13.  There
> > > is a work around to launch Zim:
> > >
> > >> zim --standalone
> > >
> > > A bug report has been filed upstream here:
> > >
> > > https://bugs.launchpad.net/zim/+bug/1618410
> > >
> > > I attached the error message to this email.  Reproduced in a fresh
> > > virtual machine of Slackware x86 and x86_64 14.2.  Can anyone else
> > > reproduce this?  Any suggestions are welcome.
> >
> > Works on current machine with same Python 2.7.13
> > probably a bug caused by the way Python was compiled? (UCS-2 vs UCS-4)
> >
>
> In short, rebuild python 2.7.13 and this problem will be fixed.  Remove
> your $HOME/.config/zim and $HOME/.cache/zim.  Start zim as normal.
>
> The issue lies in the python multiprocessing module.  Zim is unable to
> start up because it cannot import the required module.
>
> The following will return the import error:
>
> > python -c "from _multiprocessing import SemLock"
>
> This problem can be seen if you run zim in debug mode during the first
> launch of the application.  See attached log.
>
> Thanks,
> Brenton Earl
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170106/62d1a292/attachment-0001.html>

From willysr at slackbuilds.org  Sat Jan  7 02:17:04 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 7 Jan 2017 09:17:04 +0700
Subject: [Slackbuilds-users] Updates - 20170107.1
Message-ID: <f45da3bc-a759-af08-6116-5d6f8e4433a4@slackbuilds.org>

Welcome to the first update in 2017!!

More than 270 commits in this update. A good start for new year.

Some fixes from last Python 3 update is now included in this update, but
we have some report about latest Python update in Slackware that break
some scripts in our repository. Patches are welcome for next public update.


Sat Jan  7 01:51:02 UTC 2017
academic/bibus: Change email.
academic/extrema: Change email.
academic/glpk: Change email.
academic/qhull: Change email.
academic/reduce-algrebra: Update DOWNLOAD url.
academic/veusz: Updated for version 1.25.1.
accessibility/shorturl: Added (URL Shortener).
audio/clementine: Fix build against chromaprint 1.4.
audio/flacon: Update README.
audio/jokosher: Change email.
audio/mp3check: Updated download URL, cleanup.
audio/patchage: Change email.
audio/tagtool: Change email.
audio/vamp-plugin-sdk: Change email.
desktop/anki: Updated for version 2.0.39.
desktop/avant-window-navigator: Change email.
desktop/awn-extras: Change email.
desktop/cellwriter: Change email.
desktop/dwm: Change email.
desktop/ee: Switch to i586 and update email.
desktop/enlightenment: Change email.
desktop/gmrun: Change email.
desktop/gtk-engines: Change email.
desktop/gtk-kde4: Change email.
desktop/icewm-themes: Added (Theme files for the IceWM).
desktop/kde-gtk-config: Change email.
desktop/lumina: Change email.
desktop/neutral: Change email.
desktop/paper-icon-theme: Updated for version 1.4.0.
desktop/skippy-xd: Update DOWNLOAD url.
desktop/superkey-launch: Change email.
desktop/uwm: Change email.
desktop/wbar: Change email.
desktop/x-tile: Change email.
development/Catch: Added (Unit-Test, TDD, and BDD C++ Framework).
development/alloy: Change email.
development/astyle: Change email.
development/bfg: Change email.
development/bigloo: Change email.
development/bluefish: Change email.
development/brackets: Change email.
development/colordiff: Change email.
development/ebe: Change email.
development/enki: Change email.
development/flow: Change email.
development/gauche: Change email.
development/geany-plugins: Change email.
development/geany: Change email.
development/gisto: Change email.
development/gnustep-startup: Change email.
development/google-appengine-gosdk: Change email.
development/google-appengine-pysdk: Change email.
development/groovy: Change email.
development/gtest: Update DOWNLOAD url.
development/hexedit: Change email.
development/jeex: Change email.
development/jsmin: Change email.
development/ldns: Updated for version 1.7.0
development/leiningen: Change email.
development/lighttable: Change email.
development/mcrl2: Change email.
development/medit: Change email.
development/mit-scheme: Change email.
development/mlton: Change email.
development/ninja-ide: Change email.
development/ninja: Updated for version 1.7.2.
development/nodejs: Change email.
development/pkgconf: Updated for version 1.1.0.
development/qt-creator: Updated for version 4.2.0.
development/quilt: Change email.
development/sbcl: Updated for version 1.3.13.
development/scite: Change email.
development/smalltalk: Change email.
development/spin: Change email.
development/sqlitebrowser: Change email.
development/src-vcs: Change email.
development/textadept: Change email.
development/thunderpad: Change email.
development/uemacs: Change email.
development/vscode: Added (Development tool).
development/watchman: Change email.
development/zed: Change email.
games/beetle-saturn-libretro: Added (Mednafen Saturn libretro port).
games/crispy-doom: Updated for version 3.5.
games/enigma: Change email.
games/freeciv: Change email.
games/gbrainy: Change email.
games/gottet: Change email.
games/knights: Change email.
games/lutris: Change email.
games/mame2000-libretro: Added (MAME 2000 libretro port).
games/mednafen: Change email.
games/nsudoku: Change email.
games/pioneer: Update README.
games/simsu: Change email.
games/supertuxkart: Change email.
games/xspacewarp: Change email.
gis/google-earth: Update README.
graphics/blender: Change email.
graphics/brlcad: Change email.
graphics/darktable: Updated for version 2.2.1.
graphics/evolus-pencil: Change email.
graphics/graphviz: Updated for version 2.40.1.
graphics/jpegoptim: Change email.
graphics/mirage: Change email.
graphics/mozjpeg: Change email.
graphics/pngquant: Change email.
graphics/scrot: Change email.
graphics/sxiv: Updated for version 1.3.2 + new maintainer.
graphics/uniconvertor: Update DOWNLOAD url.
libraries/RxCpp: Added (The Reactive Extensions for C++).
libraries/SDL_gfx: Change email.
libraries/allegro: Change email.
libraries/asio: Added (Asio C++ Library).
libraries/e_dbus: Change email.
libraries/ecore: Change email.
libraries/edje: Change email.
libraries/eet: Change email.
libraries/efreet: Change email.
libraries/eina: Change email.
libraries/eio: Change email.
libraries/elementary: Change email.
libraries/embryo: Change email.
libraries/emotion: Change email.
libraries/enum34: Remove python 3 support.
libraries/ethumb: Change email.
libraries/evas: Change email.
libraries/flatbuffers: Added (cross platform serialization library).
libraries/ganv: Change email.
libraries/giblib: Change email.
libraries/gloox: Change email.
libraries/gnonlin: Change email.
libraries/gtk-sharp: Updated for version 2.12.42.
libraries/gtkextra: Change email.
libraries/imlib2: Change email.
libraries/iniparser: Updated for version 4.0.
libraries/libaaio: Switch to i586 + update maintainer email.
libraries/libdesktop-agnostic: Change email.
libraries/libgcrypt15: Change email.
libraries/libmediainfo: Change email.
libraries/libminizip: Updated for version 1.2.9.
libraries/libnova: Change email.
libraries/libpng-legacy12: Updated for version 1.2.57.
libraries/libtar: Change email.
libraries/libzen: Change email.
libraries/lxqt-build-tools: Updated for version 0.3.1.
libraries/notify-sharp: Removed (maintainer request).
libraries/proxygen: Added (Facebook's C++ HTTP Libraries).
libraries/python-e_dbus: Change email.
libraries/python-elementary: Change email.
libraries/python-emotion: Change email.
libraries/python-ethumb: Change email.
libraries/python-evas: Change email.
libraries/qt3: Change email.
libraries/qt5-webkit: Switch to i586.
libraries/qutepart: Change email.
libraries/rapidjson: Added (a fast JSON parser/generator for C++)
libraries/restbed: Added (asynchronous C++11 RESTful framework).
libraries/ucl: Change email.
libraries/wxGTK: Change email.
libraries/wxsvg: Updated for version 1.5.11.
misc/asterixInspector: Change email.
misc/dmg2img: Change email.
misc/dos2unix: Change email.
misc/fbdump: Change email.
misc/gcp: Change email.
misc/gprename: Updated for version 20160905.
misc/protobuf3: Added (Google's data interchange format)
misc/recode: Change email.
misc/rlwrap: Update DOWNLOAD link, cleanups.
misc/stardict: Change email.
misc/wcd: Change email.
misc/zyGrib: Change email.
multimedia/beets: Updated for version 1.4.2.
multimedia/dvdstyler: Updated for version 3.0.3.
multimedia/exaile: Change email.
multimedia/gmtp: Change email.
multimedia/ivtv-utils: Added (Utilities for Hauppauge PVR).
multimedia/mediainfo-gui: Change email.
multimedia/mediainfo: Change email.
multimedia/musique: Change email.
multimedia/nightingale: Change email.
multimedia/pitivi: Change email.
multimedia/popcorntime: Updated for version 0.3.10.
multimedia/ripit: Change email.
multimedia/spotify: Change email.
network/Electrum: Updated for version 2.7.13.
network/LOIC: Change email.
network/barnyard2: Update scripts.
network/boxcryptor: Change email.
network/connman: Change email.
network/dwb: Change email.
network/etherape: Change email.
network/gq: Change email.
network/guacamole-client: Updated for version 0.9.9.
network/guacamole-server: Updated for version 0.9.9.
network/hipchat: Change email.
network/iojs: Change email.
network/ip2location-c: Change email.
network/ipv6calc: Change email.
network/licq: Change email.
network/lighttpd: Updated for version 1.4.44.
network/opera-developer: Updated for version 44.0.2463.0.
network/sickrage: Fix download issue.
network/skype4pidgin: Change email.
network/slack: Change email.
network/sparkleshare: Removed (maintainer request).
network/transgui: Fix download issue.
network/webkit-sharp: Removed (maintainer request).
network/wput: Change email.
network/xinetd: Change email.
network/youtube-dl: Updated for version 2017.01.02.
office/ganttproject: Change email.
office/jstock: Updated for version 1.0.7.18.
office/keepassxc: Added (personal data management application).
office/leafpad: Change email.
office/mdp: Change email.
office/openoffice.org: Change email.
office/pdfstudio11: Added (PDF editor).
office/xpad: Change email.
perl/perl-Devel-CheckLib: Added (perl module).
perl/perl-IO-CaptureOutput: Added (perl module).
perl/perl-Sidef: Updated for version 2.34.
python/Scrapy: Updated for version 1.3.0.
python/hgsubversion: Switch to i586.
python/lxml: Update MD5SUM.
python/python-distro: Add python3 support.
python/python3: Fix comment style.
python/regex: Updated for version 2016.12.27.
python/sk1libs: Update DOWNLOAD url.
python/snuggs: Updated for version 1.4.1.
python/websocket-client: Updated for version 0.40.0.
ruby/ruby-faraday: Updated for version 0.10.1.
system/Iosevka: Updated for version 1.10.2.
system/betty: Change email.
system/burp: Change email.
system/cdw: Change email.
system/cronie: Change email.
system/dateutils: Updated for version 0.4.1.
system/davfs2: Change email.
system/dieharder: Switch to i586, change option + upd maint email.
system/dina-font: Change email.
system/dosbox: Change email.
system/dump: Change email.
system/f3: Added (Fix Fake Flash).
system/file-roller: Change email.
system/google-droid-fonts: Change email.
system/guix: Fix typo.
system/ioping: Simplify README.
system/iotop: Switch to i586, cleanup.
system/isdct: Fix path.
system/komparator4: Change email.
system/linkchecker: Fix python requests version check.
system/linux-libertine-fonts: Change email.
system/multicorn: Updated for version 1.3.3.
system/musl: Updated for version 1.1.16.
system/pgbadger: Updated for version 9.0.
system/pgsanity: Switch to i586.
system/pstate-frequency: Updated for version 3.7.2.
system/slim: Change email.
system/smem: Cleanup.
system/spacefm: Change email.
system/tarsnap: Change email.
system/tarsnap: Switch to i586 + cleanup.
system/terminology: Change email.
system/tilda: Change email.
system/tinyterm: Change email.
system/tinyvm: Change email.
system/ttf-ubuntu-font-family: Change email.
system/vagrant: Updated for version 1.9.1.
system/vlock: Change email.
system/winetricks: Change email.
system/xonsh: Updated for version 0.5.1.
system/zuluCrypt: Updated for version 5.1.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From kjhambrick at gmail.com  Sat Jan  7 10:24:15 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 7 Jan 2017 04:24:15 -0600
Subject: [Slackbuilds-users] xmlsec1-1.2.23 fails to build on Slackware64
 14.2 with seamonkey-2.46-x86_64-1_slack14.2
Message-ID: <CANBHt+NDn_HpEpZna3igCeJsEHrjNOR128-h4kG10ue2D10jYw@mail.gmail.com>

Willy --

The latest xmlsec SlackBuild fails with the latest Seamonkey Package for
Slackware64 14.2.

Pat's latest seamonkey2.46 was released with an empty ~/nspr/obsolete/
directory and there are indirect references to obsolete/protypes.h in the
xmlsec source via nspr/pratom.h.

OTOH, mozilla-nspr DOES include the obsolete/*.h files and xmlsec includes
a configure option:  --with-mozilla-ver=

This config overrides the default seamonkey-nspr/ files.

There may be ( probably is ) a better way to do this ( maybe via the
Seamonkey Spec File ??? ) but attached a patch that works ( :) at least for
the time being :) )

Thanks for today's updates !

( and thanks a zillion for cleaning up and including my f3.SlackBuild -- I
wasn't aware that gnu make would override the hard-coded PREFIX =
/usr/local in the Makefile with an exported PREFIX= variable  -- VERY handy
to know )

-- kjh

This is the make error using the original xmlsec.SlackBuild:

make[3]: Entering directory '/tmp/SBo/xmlsec1-1.2.23/src/nss'
  CC       libxmlsec1_nss_la-app.lo
In file included from /usr/include/seamonkey-2.46/nspr/pratom.h:14:0,
                 from /usr/include/seamonkey-2.46/nspr/nspr.h:9,
                 from app.c:14:
/usr/include/seamonkey-2.46/nspr/prtypes.h:574:31: fatal error:
obsolete/protypes.h: No such file or directory
compilation terminated.
Makefile:612: recipe for target 'libxmlsec1_nss_la-app.lo' failed
make[3]: *** [libxmlsec1_nss_la-app.lo] Error 1
make[3]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23/src/nss'
Makefile:694: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23/src'
Makefile:725: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23'
Makefile:543: recipe for target 'all' failed
make: *** [all] Error 2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170107/7e064c9d/attachment.html>
-------------- next part --------------
--- xmlsec.SlackBuild.orig	2016-12-31 08:43:23.154400759 -0600
+++ xmlsec.SlackBuild	2017-01-07 04:03:31.950836383 -0600
@@ -69,7 +69,23 @@
   -o -perm 511 \) -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
-
+#
+# seamonkey-2.46-x86_64-1_slack14.2 was released with an empty
+# usr/include/seamonkey-2.46/nspr/obsolete/ directory and xmlsec
+# won't build without nspr/obsolete/protypes.h
+#
+# All is not lost !  
+#
+# mozilla-nss-3.23-x86_64-1 does populate usr/include/nspr/obsolete/
+# and xmlsec builds OK with that one instead.
+#
+# rather than hard-code the mozilla-version in xmlsec.SlackBuild,
+# grep it from /var/log/packages like so:
+#
+SLKMOZVER="$(basename $(ls -1 /var/log/packages/mozilla-nss-*-${ARCH}* 2>/dev/null) 2>/dev/null)"
+#
+[ "$SLKMOZVER" = "" ] && echo "could not resolve mozilla-nss version" >&2 && exit 1
+#
 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \
 ./configure \
@@ -80,6 +96,7 @@
   --mandir=/usr/man \
   --docdir=/usr/doc/$PRGNAM-$VERSION \
   --disable-static \
+  --with-mozilla-ver=$SLKMOZVER \
   --build=$ARCH-slackware-linux
 
 make

From willysr at slackbuilds.org  Sat Jan  7 12:12:15 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 7 Jan 2017 19:12:15 +0700
Subject: [Slackbuilds-users] xmlsec1-1.2.23 fails to build on
 Slackware64 14.2 with seamonkey-2.46-x86_64-1_slack14.2
In-Reply-To: <CANBHt+NDn_HpEpZna3igCeJsEHrjNOR128-h4kG10ue2D10jYw@mail.gmail.com>
References: <CANBHt+NDn_HpEpZna3igCeJsEHrjNOR128-h4kG10ue2D10jYw@mail.gmail.com>
Message-ID: <4908898d-e5ab-0753-880b-6e18a4ca6bb5@slackbuilds.org>

> The latest xmlsec SlackBuild fails with the latest Seamonkey Package for
> Slackware64 14.2.
> 
> Pat's latest seamonkey2.46 was released with an empty ~/nspr/obsolete/
> directory and there are indirect references to obsolete/protypes.h in the
> xmlsec source via nspr/pratom.h.
> 
> OTOH, mozilla-nspr DOES include the obsolete/*.h files and xmlsec includes
> a configure option:  --with-mozilla-ver=
> 
> This config overrides the default seamonkey-nspr/ files.
> 
> There may be ( probably is ) a better way to do this ( maybe via the
> Seamonkey Spec File ??? ) but attached a patch that works ( :) at least for
> the time being :) )
> 
> This is the make error using the original xmlsec.SlackBuild:
> 
> make[3]: Entering directory '/tmp/SBo/xmlsec1-1.2.23/src/nss'
>   CC       libxmlsec1_nss_la-app.lo
> In file included from /usr/include/seamonkey-2.46/nspr/pratom.h:14:0,
>                  from /usr/include/seamonkey-2.46/nspr/nspr.h:9,
>                  from app.c:14:
> /usr/include/seamonkey-2.46/nspr/prtypes.h:574:31: fatal error:
> obsolete/protypes.h: No such file or directory
> compilation terminated.
> Makefile:612: recipe for target 'libxmlsec1_nss_la-app.lo' failed
> make[3]: *** [libxmlsec1_nss_la-app.lo] Error 1
> make[3]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23/src/nss'
> Makefile:694: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23/src'
> Makefile:725: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23'
> Makefile:543: recipe for target 'all' failed
> make: *** [all] Error 2

Hi

Thanks for reporting Konrad

i send your analysis to Patrick and see if it will be patched in
Slackware's seamonkey.

If there's no update for seamonkey before next public update, i will
update xmlsec to use mozilla-nss' header files.


-- 
Willy Sudiarto Raharjo

-------------- 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/20170107/8083eec6/attachment.asc>

From kjhambrick at gmail.com  Sat Jan  7 12:41:51 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 7 Jan 2017 06:41:51 -0600
Subject: [Slackbuilds-users] xmlsec1-1.2.23 fails to build on
 Slackware64 14.2 with seamonkey-2.46-x86_64-1_slack14.2
In-Reply-To: <4908898d-e5ab-0753-880b-6e18a4ca6bb5@slackbuilds.org>
References: <CANBHt+NDn_HpEpZna3igCeJsEHrjNOR128-h4kG10ue2D10jYw@mail.gmail.com>
 <4908898d-e5ab-0753-880b-6e18a4ca6bb5@slackbuilds.org>
Message-ID: <CANBHt+Ok6kHcDB+5c41-8tSpb_FVYdMb_wCEC+U2cGn9T=1UrQ@mail.gmail.com>

Thanks for the feedback Willy.

I've been fooling with Pat's seamonkey-2.46 SlackBuild and it does throw an
error when trying to install several *.h files.

output from the SlackBuild:

# grep 'cannot stat' /tmp/seamonkey.SlackBuild-2.46-x86_64.log

cp: cannot stat 'mozilla/dist/include/nspr/*.h': No such file or directory
cp: cannot stat 'mozilla/dist/include/nspr/obsolete/*.h': No such file or
directory
cp: cannot stat 'mozilla/dist/include/nspr/private/*.h': No such file or
directory
cp: cannot stat 'mozilla/dist/include/*.tbl': No such file or directory
cp: cannot stat 'mozilla/dist/include/*.msg': No such file or directory
cp: cannot stat 'mozilla/dist/include/*.h': No such file or directory
cp: cannot stat 'mozilla/dist/sdk/include/*': No such file or directory
cp: cannot stat
'/tmp/package-seamonkey/usr/lib64/seamonkey-2.46/libfreebl3.chk': No such
file or directory
cp: cannot stat
'/tmp/package-seamonkey/usr/lib64/seamonkey-2.46/libfreebl3.so': No such
file or directory

The missing files were in the original seamonkey-2.46.source.tar.xz file
and after the SlackBuild, the files are still 'in there'.

# these are the ones wanted by xmlsec
#
# ls -la /tmp/seamonkey-2.46/mozilla/nsprpub/pr/include/obsolete

total 40
drwxr-xr-x 2 root root 4096 Dec 13 20:08 .
drwxr-xr-x 5 root root 4096 Dec 13 20:08 ..
-rw-r--r-- 1 root root  659 Dec 13 20:08 Makefile.in
-rw-r--r-- 1 root root 6945 Dec 13 20:08 pralarm.h
-rw-r--r-- 1 root root 5642 Dec 13 20:08 probslet.h
-rw-r--r-- 1 root root 4914 Dec 13 20:08 protypes.h
-rw-r--r-- 1 root root 2060 Dec 13 20:08 prsem.h

Not sure about the fix but this line in the seamonkey.SlackBuild is one I
am going to fool with and try the seamonkey.SlackBuild again:

<<snip>>
:
# Install nspr/nss headers.
for includedir in nspr nspr/obsolete nspr/private ; do
  mkdir -p $PKG/usr/include/seamonkey-${VERSION}/$includedir
  cp -aL mozilla/dist/include/${includedir}/*.h
$PKG/usr/include/seamonkey-${VERSION}/$includedir
done
:
<<snip>>

Maybe the 'fix' is as simple as changing the 'root' directory for the
'Install nspr/nss headers' for-loop ?

Thanks again All'Y'All !

-- kjh



On Sat, Jan 7, 2017 at 6:12 AM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > The latest xmlsec SlackBuild fails with the latest Seamonkey Package for
> > Slackware64 14.2.
> >
> > Pat's latest seamonkey2.46 was released with an empty ~/nspr/obsolete/
> > directory and there are indirect references to obsolete/protypes.h in the
> > xmlsec source via nspr/pratom.h.
> >
> > OTOH, mozilla-nspr DOES include the obsolete/*.h files and xmlsec
> includes
> > a configure option:  --with-mozilla-ver=
> >
> > This config overrides the default seamonkey-nspr/ files.
> >
> > There may be ( probably is ) a better way to do this ( maybe via the
> > Seamonkey Spec File ??? ) but attached a patch that works ( :) at least
> for
> > the time being :) )
> >
> > This is the make error using the original xmlsec.SlackBuild:
> >
> > make[3]: Entering directory '/tmp/SBo/xmlsec1-1.2.23/src/nss'
> >   CC       libxmlsec1_nss_la-app.lo
> > In file included from /usr/include/seamonkey-2.46/nspr/pratom.h:14:0,
> >                  from /usr/include/seamonkey-2.46/nspr/nspr.h:9,
> >                  from app.c:14:
> > /usr/include/seamonkey-2.46/nspr/prtypes.h:574:31: fatal error:
> > obsolete/protypes.h: No such file or directory
> > compilation terminated.
> > Makefile:612: recipe for target 'libxmlsec1_nss_la-app.lo' failed
> > make[3]: *** [libxmlsec1_nss_la-app.lo] Error 1
> > make[3]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23/src/nss'
> > Makefile:694: recipe for target 'all-recursive' failed
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23/src'
> > Makefile:725: recipe for target 'all-recursive' failed
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory '/tmp/SBo/xmlsec1-1.2.23'
> > Makefile:543: recipe for target 'all' failed
> > make: *** [all] Error 2
>
> Hi
>
> Thanks for reporting Konrad
>
> i send your analysis to Patrick and see if it will be patched in
> Slackware's seamonkey.
>
> If there's no update for seamonkey before next public update, i will
> update xmlsec to use mozilla-nss' header files.
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170107/4b61acd7/attachment-0001.html>

From kjhambrick at gmail.com  Sat Jan  7 13:11:40 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 7 Jan 2017 07:11:40 -0600
Subject: [Slackbuilds-users] libpng-legacy12.SlackBuild patch for MultiLib
Message-ID: <CANBHt+OLHsSXxLDVO2+ObcfLpwsPiBuNa8VtVSwqPZd7e7F2sg@mail.gmail.com>

B. Watson / Willy --

I am running Slackware64 14.2 + Multilib and in order to make TeamViewer
work, I had to install a 32-bit version of libpng-legacy12

I also went ahead and installed the 64 bit version as well and that caused
a 'dupe package' error in my `find-sbo-updates.sh` script.

As a work-around, and more-or-less in keeping with Alien Bob's convention
of appending -compat32 to the $PRGNAM for his 32-bit versions of standard
Slackware Packages, I've patched libpng-legacy12.SlackBuild to append
'-32bit' to the $PRGNAM when building an ARCH=i486 Package on a `uname -m`
= X86_64 machine.

Not sure this is in keeping with the SBo Rules but it works for me :)

Thanks for all your SBo goodies !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170107/b7fb820f/attachment.html>
-------------- next part --------------
--- libpng-legacy12.SlackBuild.orig	2017-01-07 02:03:35.740033740 -0600
+++ libpng-legacy12.SlackBuild	2017-01-07 05:59:15.056645968 -0600
@@ -31,7 +31,15 @@
  x86_64) LIBDIRSUFFIX="64" ;;
       *) echo "Warning: unrecognized ARCH '$ARCH'" ;;
 esac
-
+#
+# kjh added this for MultiLib
+#
+REALARCH="$(uname -m)"
+
+[ "$REALARCH" = "x86_64" -a "$ARCH" = "i486" ] && ATAG="-32bit" || ATAG=""
+#
+# kjh added that for MultiLib
+#
 CWD=$(pwd)
 TMP=${TMP:-/tmp/SBo}
 PKG=$TMP/package-$PRGNAM
@@ -66,4 +74,4 @@
 grep libpng12.so ./install/doinst.sh > $PKG/install/doinst.sh
 
 cd $PKG
-/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
+/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM${ATAG}-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}

From kjhambrick at gmail.com  Sat Jan  7 13:17:12 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 7 Jan 2017 07:17:12 -0600
Subject: [Slackbuilds-users] libpng-legacy12.SlackBuild patch for
 MultiLib
In-Reply-To: <CANBHt+OLHsSXxLDVO2+ObcfLpwsPiBuNa8VtVSwqPZd7e7F2sg@mail.gmail.com>
References: <CANBHt+OLHsSXxLDVO2+ObcfLpwsPiBuNa8VtVSwqPZd7e7F2sg@mail.gmail.com>
Message-ID: <CANBHt+PZktAeXXa1nDq7od6jF=gkZErWMiLVAWdUhHGD_PU7AQ@mail.gmail.com>

hmmm ... The appended patch file isn't working on gmail ...

Maybe they think I am trying to hide a .ext from a WinDOS user ...

renamed libpng-legacy12.SlackBuild.patch.txt
libpng-legacy12.SlackBuild-patch.txt

On Sat, Jan 7, 2017 at 7:11 AM, Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

> B. Watson / Willy --
>
> I am running Slackware64 14.2 + Multilib and in order to make TeamViewer
> work, I had to install a 32-bit version of libpng-legacy12
>
> I also went ahead and installed the 64 bit version as well and that caused
> a 'dupe package' error in my `find-sbo-updates.sh` script.
>
> As a work-around, and more-or-less in keeping with Alien Bob's convention
> of appending -compat32 to the $PRGNAM for his 32-bit versions of standard
> Slackware Packages, I've patched libpng-legacy12.SlackBuild to append
> '-32bit' to the $PRGNAM when building an ARCH=i486 Package on a `uname -m`
> = X86_64 machine.
>
> Not sure this is in keeping with the SBo Rules but it works for me :)
>
> Thanks for all your SBo goodies !
>
> -- kjh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170107/03200bd1/attachment.html>
-------------- next part --------------
--- libpng-legacy12.SlackBuild.orig	2017-01-07 02:03:35.740033740 -0600
+++ libpng-legacy12.SlackBuild	2017-01-07 05:59:15.056645968 -0600
@@ -31,7 +31,15 @@
  x86_64) LIBDIRSUFFIX="64" ;;
       *) echo "Warning: unrecognized ARCH '$ARCH'" ;;
 esac
-
+#
+# kjh added this for MultiLib
+#
+REALARCH="$(uname -m)"
+
+[ "$REALARCH" = "x86_64" -a "$ARCH" = "i486" ] && ATAG="-32bit" || ATAG=""
+#
+# kjh added that for MultiLib
+#
 CWD=$(pwd)
 TMP=${TMP:-/tmp/SBo}
 PKG=$TMP/package-$PRGNAM
@@ -66,4 +74,4 @@
 grep libpng12.so ./install/doinst.sh > $PKG/install/doinst.sh
 
 cd $PKG
-/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
+/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM${ATAG}-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}

From willysr at slackbuilds.org  Sat Jan  7 13:21:30 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 7 Jan 2017 20:21:30 +0700
Subject: [Slackbuilds-users] libpng-legacy12.SlackBuild patch for
 MultiLib
In-Reply-To: <CANBHt+OLHsSXxLDVO2+ObcfLpwsPiBuNa8VtVSwqPZd7e7F2sg@mail.gmail.com>
References: <CANBHt+OLHsSXxLDVO2+ObcfLpwsPiBuNa8VtVSwqPZd7e7F2sg@mail.gmail.com>
Message-ID: <9a353731-d7e6-cacb-aac6-9321e302846c@slackbuilds.org>

> I am running Slackware64 14.2 + Multilib and in order to make TeamViewer
> work, I had to install a 32-bit version of libpng-legacy12
> 
> I also went ahead and installed the 64 bit version as well and that caused
> a 'dupe package' error in my `find-sbo-updates.sh` script.
> 
> As a work-around, and more-or-less in keeping with Alien Bob's convention
> of appending -compat32 to the $PRGNAM for his 32-bit versions of standard
> Slackware Packages, I've patched libpng-legacy12.SlackBuild to append
> '-32bit' to the $PRGNAM when building an ARCH=i486 Package on a `uname -m`
> = X86_64 machine.
> 
> Not sure this is in keeping with the SBo Rules but it works for me :)

Hi Konrad

I'm afraid that's not a good idea
multilib is not officially supported in SBo, so while some patches may
be accepted by the maintainer to support multilib, but changing the
naming scheme is against SBo policy and may introduce confusion to
non-multilib users.



-- 
Willy Sudiarto Raharjo

-------------- 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/20170107/0136242c/attachment.asc>

From jebrhansen+SBo at gmail.com  Sat Jan  7 15:58:00 2017
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sat, 07 Jan 2017 15:58:00 +0000
Subject: [Slackbuilds-users] libpng-legacy12.SlackBuild patch for
 MultiLib
In-Reply-To: <9a353731-d7e6-cacb-aac6-9321e302846c@slackbuilds.org>
References: <CANBHt+OLHsSXxLDVO2+ObcfLpwsPiBuNa8VtVSwqPZd7e7F2sg@mail.gmail.com>
 <9a353731-d7e6-cacb-aac6-9321e302846c@slackbuilds.org>
Message-ID: <CANi9qSv7KPnFE-dpqv3pxomRPQM+a-7+_Roi9YgJ96WBw01M3Q@mail.gmail.com>

Konrad,

When you compile a 32bit package and intend to install it on a 64bit
system, you should be running convertpkg-compat32 against it before
installing. This will change the package name, add -32 to any binaries, and
some additional maintenance. This should minimize collisions with 64bit
packages.

Jeremy

On Sat, Jan 7, 2017, 8:21 AM Willy Sudiarto Raharjo <willysr at slackbuilds.org>
wrote:

> > I am running Slackware64 14.2 + Multilib and in order to make TeamViewer
> > work, I had to install a 32-bit version of libpng-legacy12
> >
> > I also went ahead and installed the 64 bit version as well and that
> caused
> > a 'dupe package' error in my `find-sbo-updates.sh` script.
> >
> > As a work-around, and more-or-less in keeping with Alien Bob's convention
> > of appending -compat32 to the $PRGNAM for his 32-bit versions of standard
> > Slackware Packages, I've patched libpng-legacy12.SlackBuild to append
> > '-32bit' to the $PRGNAM when building an ARCH=i486 Package on a `uname
> -m`
> > = X86_64 machine.
> >
> > Not sure this is in keeping with the SBo Rules but it works for me :)
>
> Hi Konrad
>
> I'm afraid that's not a good idea
> multilib is not officially supported in SBo, so while some patches may
> be accepted by the maintainer to support multilib, but changing the
> naming scheme is against SBo policy and may introduce confusion to
> non-multilib users.
>
>
>
> --
> Willy Sudiarto Raharjo
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170107/a8b149c5/attachment.html>

From kjhambrick at gmail.com  Sat Jan  7 20:59:02 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 7 Jan 2017 14:59:02 -0600
Subject: [Slackbuilds-users] libpng-legacy12.SlackBuild patch for
 MultiLib
In-Reply-To: <CANi9qSv7KPnFE-dpqv3pxomRPQM+a-7+_Roi9YgJ96WBw01M3Q@mail.gmail.com>
References: <CANBHt+OLHsSXxLDVO2+ObcfLpwsPiBuNa8VtVSwqPZd7e7F2sg@mail.gmail.com>
 <9a353731-d7e6-cacb-aac6-9321e302846c@slackbuilds.org>
 <CANi9qSv7KPnFE-dpqv3pxomRPQM+a-7+_Roi9YgJ96WBw01M3Q@mail.gmail.com>
Message-ID: <CANBHt+NT9M9muDrfxuf7BRUUix1CU0xGbfAfSOCbXe+oWfvdcg@mail.gmail.com>

Willy /Jeremy --

I agree with both of you.

I'll keep the patch local

The libpng-legacy.SlackBuild already properly handles the contents of the
Package for ARCH=i486.

And since it takes the Slackware 14.1 Packages instead of the Slackware
14.2 pacakges, I don't believe the convertpkg-compat32 would do what I need
without seriously messing with the scripts.

Thanks for the input !

-- kjh

On Sat, Jan 7, 2017 at 9:58 AM, Jeremy Hansen <jebrhansen+SBo at gmail.com>
wrote:

> Konrad,
>
> When you compile a 32bit package and intend to install it on a 64bit
> system, you should be running convertpkg-compat32 against it before
> installing. This will change the package name, add -32 to any binaries, and
> some additional maintenance. This should minimize collisions with 64bit
> packages.
>
> Jeremy
>
> On Sat, Jan 7, 2017, 8:21 AM Willy Sudiarto Raharjo <
> willysr at slackbuilds.org> wrote:
>
>> > I am running Slackware64 14.2 + Multilib and in order to make TeamViewer
>> > work, I had to install a 32-bit version of libpng-legacy12
>> >
>> > I also went ahead and installed the 64 bit version as well and that
>> caused
>> > a 'dupe package' error in my `find-sbo-updates.sh` script.
>> >
>> > As a work-around, and more-or-less in keeping with Alien Bob's
>> convention
>> > of appending -compat32 to the $PRGNAM for his 32-bit versions of
>> standard
>> > Slackware Packages, I've patched libpng-legacy12.SlackBuild to append
>> > '-32bit' to the $PRGNAM when building an ARCH=i486 Package on a `uname
>> -m`
>> > = X86_64 machine.
>> >
>> > Not sure this is in keeping with the SBo Rules but it works for me :)
>>
>> Hi Konrad
>>
>> I'm afraid that's not a good idea
>> multilib is not officially supported in SBo, so while some patches may
>> be accepted by the maintainer to support multilib, but changing the
>> naming scheme is against SBo policy and may introduce confusion to
>> non-multilib users.
>>
>>
>>
>> --
>> Willy Sudiarto Raharjo
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://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
> http://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/20170107/a1102f10/attachment-0001.html>

From read3valprintloop at gmail.com  Sun Jan  8 11:51:31 2017
From: read3valprintloop at gmail.com (PL RE)
Date: Sun, 8 Jan 2017 19:51:31 +0800
Subject: [Slackbuilds-users] SuperCollider(3.6.6) on Slackware 14.2 depends
 on yaml-cpp0.3
Message-ID: <CALF7xt=pV==0hf+hWhG8Z29ywakpftoC=5EcPFrbiquZ9Dh7kQ@mail.gmail.com>

To build this package successfully. I have to install yaml-cpp0.3. Note
that yaml-cpp-0.5.3 will not work. Maybe this package should be added to
the README file of the Supercollider package.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170108/d092872e/attachment.html>

From Jim.Diamond at acadiau.ca  Sun Jan  8 21:09:02 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Sun, 8 Jan 2017 17:09:02 -0400
Subject: [Slackbuilds-users] missing dependency for shutter
Message-ID: <20170108210902.GA19813@jdiamond-nb.acadiau.ca>

% shutter
Can't locate Sort/Naturally.pm in @INC (you may need to install the Sort::Naturally module) (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/bin/shutter line 93.
BEGIN failed--compilation aborted at /usr/bin/shutter line 93.


Huh.  Must be missing one of its 42,871 dependencies.  Too much work
for me to figure out, let's see if the computer can figure it out.


% sudo removepkg shutter
...

% sudo sboinstall shutter
gnome-mime-data already installed.
ORBit2 already installed.
libbonobo already installed.
gnome-vfs already installed.
libgnome already installed.
libgnomecanvas already installed.
libbonoboui already installed.
libgnomeui already installed.
perl-extutils-depends already installed.
perl-extutils-pkgconfig already installed.
perl-cairo already installed.
perl-glib already installed.
perl-pango already installed.
perl-gtk2 already installed.
perl-gnome2-canvas already installed.
perl-gnome2-vfs already installed.
perl-gnome2 already installed.
perl-IPC-Run3 already installed.
perl-Probe-Perl already installed.
perl-Test-Script already installed.
perl-File-Which already installed.
perl-PAR-Dist already installed.
perl-Module-Build already installed.
perl-IPC-System-Simple already installed.
perl-file-basedir already installed.
perl-File-Copy-Recursive already installed.
perl-gnome2-wnck already installed.
goocanvas already installed.
perl-goo-canvas already installed.
gtkimageview already installed.
perl-gtk2-imageview already installed.
libunique already installed.
perl-Gtk2-Unique already installed.
exiftool already installed.
perl-JSON already installed.
perl-common-sense already installed.
perl-JSON-XS already installed.
perl-xml-twig already installed.
perl-net-dbus already installed.
perl-Path-Class already installed.
perl-Proc-ProcessTable already installed.
perl-Proc-Simple already installed.
perl-encode-locale already installed.
perl-html-tagset already installed.
perl-html-parser already installed.
perl-http-date already installed.
perl-lwp-mediatypes already installed.
perl-IO-HTML already installed.
perl-http-message already installed.
perl-html-form already installed.
perl-file-listing already installed.
perl-http-cookies already installed.
perl-http-daemon already installed.
perl-http-negotiate already installed.
perl-net-http already installed.
perl-www-robotrules already installed.
libwww-perl already installed.
perl-http-response-encoding already installed.
perl-Test-NoWarnings already installed.
perl-Test-Deep already installed.
perl-Sub-Uplevel already installed.
perl-Slurp-Tiny already installed.
perl-tree-dagnode already installed.
perl-test-warn already installed.
perl-CGI already installed.
perl-http-server-simple already installed.
perl-www-mechanize already installed.
perl-x11-protocol already installed.

Shutter is a feature-rich screenshot program. You can take a screenshot 
of a specific area, window, your whole screen, or even of a website - 
apply different effects to it, draw on it to highlight points, and then 
upload to an image hosting site, all within one window. Shutter is free, 
open-source, and licensed under GPL v3.

Proceed with shutter? [y]: 


Huh.  Everything is allegedly there.

...

% sudo sboinstall perl-Sort-Naturally

...


And now shutter runs.

Should someone add dependency #42,872 to this program?

Cheers.

                                Jim

From chytraeu at sdf.org  Sun Jan  8 22:13:05 2017
From: chytraeu at sdf.org (Donald Cooley)
Date: Sun, 8 Jan 2017 16:13:05 -0600
Subject: [Slackbuilds-users] missing dependency for shutter
In-Reply-To: <20170108210902.GA19813@jdiamond-nb.acadiau.ca>
References: <20170108210902.GA19813@jdiamond-nb.acadiau.ca>
Message-ID: <a084a740fc5cd2f522b28c47ab6a47b3.squirrel@ma.sdf.org>


On Sun, January 8, 2017 3:09 pm, Jim Diamond wrote:
> % shutter
> Can't locate Sort/Naturally.pm in @INC (you may need to install the
> Sort::Naturally module) (@INC contains: /usr/local/lib64/perl5
> /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
> /usr/bin/shutter line 93.
> BEGIN failed--compilation aborted at /usr/bin/shutter line 93.
>
>
> Huh.  Must be missing one of its 42,871 dependencies.  Too much work
> for me to figure out, let's see if the computer can figure it out.
>
>
> % sudo removepkg shutter
> ...
>
> % sudo sboinstall shutter
> gnome-mime-data already installed.
> ORBit2 already installed.
> libbonobo already installed.
> gnome-vfs already installed.
> libgnome already installed.
> libgnomecanvas already installed.
> libbonoboui already installed.
> libgnomeui already installed.
> perl-extutils-depends already installed.
> perl-extutils-pkgconfig already installed.
> perl-cairo already installed.
> perl-glib already installed.
> perl-pango already installed.
> perl-gtk2 already installed.
> perl-gnome2-canvas already installed.
> perl-gnome2-vfs already installed.
> perl-gnome2 already installed.
> perl-IPC-Run3 already installed.
> perl-Probe-Perl already installed.
> perl-Test-Script already installed.
> perl-File-Which already installed.
> perl-PAR-Dist already installed.
> perl-Module-Build already installed.
> perl-IPC-System-Simple already installed.
> perl-file-basedir already installed.
> perl-File-Copy-Recursive already installed.
> perl-gnome2-wnck already installed.
> goocanvas already installed.
> perl-goo-canvas already installed.
> gtkimageview already installed.
> perl-gtk2-imageview already installed.
> libunique already installed.
> perl-Gtk2-Unique already installed.
> exiftool already installed.
> perl-JSON already installed.
> perl-common-sense already installed.
> perl-JSON-XS already installed.
> perl-xml-twig already installed.
> perl-net-dbus already installed.
> perl-Path-Class already installed.
> perl-Proc-ProcessTable already installed.
> perl-Proc-Simple already installed.
> perl-encode-locale already installed.
> perl-html-tagset already installed.
> perl-html-parser already installed.
> perl-http-date already installed.
> perl-lwp-mediatypes already installed.
> perl-IO-HTML already installed.
> perl-http-message already installed.
> perl-html-form already installed.
> perl-file-listing already installed.
> perl-http-cookies already installed.
> perl-http-daemon already installed.
> perl-http-negotiate already installed.
> perl-net-http already installed.
> perl-www-robotrules already installed.
> libwww-perl already installed.
> perl-http-response-encoding already installed.
> perl-Test-NoWarnings already installed.
> perl-Test-Deep already installed.
> perl-Sub-Uplevel already installed.
> perl-Slurp-Tiny already installed.
> perl-tree-dagnode already installed.
> perl-test-warn already installed.
> perl-CGI already installed.
> perl-http-server-simple already installed.
> perl-www-mechanize already installed.
> perl-x11-protocol already installed.
>
> Shutter is a feature-rich screenshot program. You can take a screenshot
> of a specific area, window, your whole screen, or even of a website -
> apply different effects to it, draw on it to highlight points, and then
> upload to an image hosting site, all within one window. Shutter is free,
> open-source, and licensed under GPL v3.
>
> Proceed with shutter? [y]:
>
>
> Huh.  Everything is allegedly there.
>
> ...
>
> % sudo sboinstall perl-Sort-Naturally
>
> ...
>
>
> And now shutter runs.
>
> Should someone add dependency #42,872 to this program?
>
> Cheers.
>
>                                 Jim
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
Ugh. I'll look into this. BTW, this is why I haven't updated to the latest
version.

-- 
Regards,
Donald Cooley


From chytraeu at sdf.org  Mon Jan  9 00:52:27 2017
From: chytraeu at sdf.org (Donald Cooley)
Date: Sun, 08 Jan 2017 18:52:27 -0600
Subject: [Slackbuilds-users] missing dependency for shutter
In-Reply-To: <a084a740fc5cd2f522b28c47ab6a47b3.squirrel@ma.sdf.org>
References: <20170108210902.GA19813@jdiamond-nb.acadiau.ca>
 <a084a740fc5cd2f522b28c47ab6a47b3.squirrel@ma.sdf.org>
Message-ID: <9b461cf9185fc84eff69478866680f8d@sdf.org>

On 2017-01-08 4:13 pm, Donald Cooley wrote:
> On Sun, January 8, 2017 3:09 pm, Jim Diamond wrote:
>> % shutter
>> Can't locate Sort/Naturally.pm in @INC (you may need to install the
>> Sort::Naturally module) (@INC contains: /usr/local/lib64/perl5
>> /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
>> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
>> /usr/bin/shutter line 93.
>> BEGIN failed--compilation aborted at /usr/bin/shutter line 93.
>> 
>> 
>> Huh.  Must be missing one of its 42,871 dependencies.  Too much work
>> for me to figure out, let's see if the computer can figure it out.
>> 
>> 
>> % sudo removepkg shutter
>> ...
>> 
>> % sudo sboinstall shutter
>> gnome-mime-data already installed.
>> ORBit2 already installed.
>> libbonobo already installed.
>> gnome-vfs already installed.
>> libgnome already installed.
>> libgnomecanvas already installed.
>> libbonoboui already installed.
>> libgnomeui already installed.
>> perl-extutils-depends already installed.
>> perl-extutils-pkgconfig already installed.
>> perl-cairo already installed.
>> perl-glib already installed.
>> perl-pango already installed.
>> perl-gtk2 already installed.
>> perl-gnome2-canvas already installed.
>> perl-gnome2-vfs already installed.
>> perl-gnome2 already installed.
>> perl-IPC-Run3 already installed.
>> perl-Probe-Perl already installed.
>> perl-Test-Script already installed.
>> perl-File-Which already installed.
>> perl-PAR-Dist already installed.
>> perl-Module-Build already installed.
>> perl-IPC-System-Simple already installed.
>> perl-file-basedir already installed.
>> perl-File-Copy-Recursive already installed.
>> perl-gnome2-wnck already installed.
>> goocanvas already installed.
>> perl-goo-canvas already installed.
>> gtkimageview already installed.
>> perl-gtk2-imageview already installed.
>> libunique already installed.
>> perl-Gtk2-Unique already installed.
>> exiftool already installed.
>> perl-JSON already installed.
>> perl-common-sense already installed.
>> perl-JSON-XS already installed.
>> perl-xml-twig already installed.
>> perl-net-dbus already installed.
>> perl-Path-Class already installed.
>> perl-Proc-ProcessTable already installed.
>> perl-Proc-Simple already installed.
>> perl-encode-locale already installed.
>> perl-html-tagset already installed.
>> perl-html-parser already installed.
>> perl-http-date already installed.
>> perl-lwp-mediatypes already installed.
>> perl-IO-HTML already installed.
>> perl-http-message already installed.
>> perl-html-form already installed.
>> perl-file-listing already installed.
>> perl-http-cookies already installed.
>> perl-http-daemon already installed.
>> perl-http-negotiate already installed.
>> perl-net-http already installed.
>> perl-www-robotrules already installed.
>> libwww-perl already installed.
>> perl-http-response-encoding already installed.
>> perl-Test-NoWarnings already installed.
>> perl-Test-Deep already installed.
>> perl-Sub-Uplevel already installed.
>> perl-Slurp-Tiny already installed.
>> perl-tree-dagnode already installed.
>> perl-test-warn already installed.
>> perl-CGI already installed.
>> perl-http-server-simple already installed.
>> perl-www-mechanize already installed.
>> perl-x11-protocol already installed.
>> 
>> Shutter is a feature-rich screenshot program. You can take a 
>> screenshot
>> of a specific area, window, your whole screen, or even of a website -
>> apply different effects to it, draw on it to highlight points, and 
>> then
>> upload to an image hosting site, all within one window. Shutter is 
>> free,
>> open-source, and licensed under GPL v3.
>> 
>> Proceed with shutter? [y]:
>> 
>> 
>> Huh.  Everything is allegedly there.
>> 
>> ...
>> 
>> % sudo sboinstall perl-Sort-Naturally
>> 
>> ...
>> 
>> 
>> And now shutter runs.
>> 
>> Should someone add dependency #42,872 to this program?
>> 
>> Cheers.
>> 
>>                                 Jim
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>> 
> Ugh. I'll look into this. BTW, this is why I haven't updated to the 
> latest
> version.

I can confirm this. Thank you for reporting this dependency issue. I 
will fix this soon.
---
Regards,
Donald Cooley


From Jim.Diamond at acadiau.ca  Mon Jan  9 00:56:05 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Sun, 8 Jan 2017 20:56:05 -0400
Subject: [Slackbuilds-users] missing dependency for shutter
In-Reply-To: <9b461cf9185fc84eff69478866680f8d@sdf.org>
References: <20170108210902.GA19813@jdiamond-nb.acadiau.ca>
 <a084a740fc5cd2f522b28c47ab6a47b3.squirrel@ma.sdf.org>
 <9b461cf9185fc84eff69478866680f8d@sdf.org>
Message-ID: <20170109005605.GB32714@jdiamond-nb.acadiau.ca>

On Sun, Jan  8, 2017 at 18:52 (-0600), Donald Cooley wrote:

> On 2017-01-08 4:13 pm, Donald Cooley wrote:
>> On Sun, January 8, 2017 3:09 pm, Jim Diamond wrote:
>>> % shutter
>>> Can't locate Sort/Naturally.pm in @INC (you may need to install the
>>> Sort::Naturally module) (@INC contains: /usr/local/lib64/perl5
>>> /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
>>> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
>>> /usr/bin/shutter line 93.
>>> BEGIN failed--compilation aborted at /usr/bin/shutter line 93.

<snip>

>>> % sudo sboinstall perl-Sort-Naturally

>>> And now shutter runs.

>>> Should someone add dependency #42,872 to this program?

>> Ugh. I'll look into this. BTW, this is why I haven't updated to the
>> latest
>> version.

> I can confirm this. Thank you for reporting this dependency issue. I will
> fix this soon.

Thanks Donald.

                                Jim

From alik at ejik.org  Mon Jan  9 02:38:08 2017
From: alik at ejik.org (Alexander Verbovetsky)
Date: Mon, 09 Jan 2017 05:38:08 +0300
Subject: [Slackbuilds-users] doinst.sh template
Message-ID: <1483929488.3172602.841340705.6FEA3980@webmail.messagingengine.com>

Hello,

I noticed that sometimes after installation of a SlackBuild with

if [ -e usr/share/icons/hicolor/icon-theme.cache ]; then
  if [ -x /usr/bin/gtk-update-icon-cache ]; then
    /usr/bin/gtk-update-icon-cache usr/share/icons/hicolor >/dev/null
    2>&1
  fi
fi

in doinst.sh the cache is not updated and therefore icons do not appear
on the desktop.  But they do appear after additional reboot.  I guess
that the reason is that in /etc/rc.d/rc.M the command
gtk-update-icon-cache has the option "-f":

--force, -f
   Overwrite an existing cache file even if it appears to be uptodate.

Wouldn't it be a good idea to add -f to doinst.sh:

/usr/bin/gtk-update-icon-cache -f usr/share/icons/hicolor >/dev/null
2>&1

Best regards,
Alexander

From rferris at posteo.net  Mon Jan  9 04:39:40 2017
From: rferris at posteo.net (Rohan Ferris)
Date: Mon, 9 Jan 2017 14:39:40 +1000
Subject: [Slackbuilds-users] foomatic-db download url needs updating
Message-ID: <274eaf18-6007-880e-3962-872af5f2941a@posteo.net>

Hi all!

I just discovered that foomatic-db SlackBuild has stopped working due to 
the file being removed from the mirror. It has been updated with a newer 
version - 20170108. The two diffs below allowed it to compile, install 
and function without any further issue...

# foomatic-db.SlackBuild

diff --git a/system/foomatic-db/foomatic-db.SlackBuild 
b/system/foomatic-db/foomatic-db.SlackBuild
index 8ecb121..d6c6dc5 100644
--- a/system/foomatic-db/foomatic-db.SlackBuild
+++ b/system/foomatic-db/foomatic-db.SlackBuild
@@ -23,7 +23,7 @@
  #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

  PRGNAM=foomatic-db
-VERSION=${VERSION:-20160724}
+VERSION=${VERSION:-20170108}
  BUILD=${BUILD:-1}
  TAG=${TAG:-_SBo}


# foomatic-db.info

diff --git a/system/foomatic-db/foomatic-db.info 
b/system/foomatic-db/foomatic-db.info 

index 79595ca..076805c 100644 

--- a/system/foomatic-db/foomatic-db.info 

+++ b/system/foomatic-db/foomatic-db.info 

@@ -1,8 +1,8 @@ 

  PRGNAM="foomatic-db" 

  VERSION="20160724" 

 
HOMEPAGE="http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/foomatic" 

-DOWNLOAD="http://www.openprinting.org/download/foomatic/foomatic-db-4.0-20160724.tar.gz" 

-MD5SUM="5ba8f4d9717c3c362f633cd17a488488" 

+DOWNLOAD="http://www.openprinting.org/download/foomatic/foomatic-db-4.0-20170108.tar.gz" 

+MD5SUM="9ba5c6f5b2962372069e2a955ffb1bcd" 

  DOWNLOAD_x86_64="" 

  MD5SUM_x86_64="" 

  REQUIRES=""


Cheers,

Rohan

From rworkman at slackbuilds.org  Mon Jan  9 04:52:09 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 8 Jan 2017 22:52:09 -0600
Subject: [Slackbuilds-users] doinst.sh template
In-Reply-To: <1483929488.3172602.841340705.6FEA3980@webmail.messagingengine.com>
References: <1483929488.3172602.841340705.6FEA3980@webmail.messagingengine.com>
Message-ID: <20170108225209.2ca85d8a@home.rlworkman.net>

On Mon, 09 Jan 2017 05:38:08 +0300
Alexander Verbovetsky <alik at ejik.org> wrote:

> I noticed that sometimes after installation of a SlackBuild with
> 
> if [ -e usr/share/icons/hicolor/icon-theme.cache ]; then
>   if [ -x /usr/bin/gtk-update-icon-cache ]; then
>     /usr/bin/gtk-update-icon-cache usr/share/icons/hicolor >/dev/null
>     2>&1  
>   fi
> fi
> 
> in doinst.sh the cache is not updated and therefore icons do not
> appear on the desktop.  But they do appear after additional reboot.
> I guess that the reason is that in /etc/rc.d/rc.M the command
> gtk-update-icon-cache has the option "-f":
> 
> --force, -f
>    Overwrite an existing cache file even if it appears to be uptodate.
> 
> Wouldn't it be a good idea to add -f to doinst.sh:
> 
> /usr/bin/gtk-update-icon-cache -f usr/share/icons/hicolor >/dev/null
> 2>&1  


Agreed:

commit 49cc824b72fbdc8c69b938e7c414b4f7a2341c81
Author: Robby Workman <rworkman at slackware.com>
Date:   Sun Jan 8 22:49:20 2017 -0600

    doinst.sh: Add "-f" to icon theme update and note other themes
    
    Thanks to Alexander Verbovetsky <alik at ejik.org> for the suggestion
    about "gtk-update-icon-cache -f" to be consistent with what's done
    in rc.M on boot:
    
    https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-January/017875.html

Thanks!

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

From rworkman at slackbuilds.org  Mon Jan  9 04:59:38 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 8 Jan 2017 22:59:38 -0600
Subject: [Slackbuilds-users] foomatic-db download url needs updating
In-Reply-To: <274eaf18-6007-880e-3962-872af5f2941a@posteo.net>
References: <274eaf18-6007-880e-3962-872af5f2941a@posteo.net>
Message-ID: <20170108225938.2f5762d0@home.rlworkman.net>

On Mon, 9 Jan 2017 14:39:40 +1000commit 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea
Author: Rohan Ferris <rferris at posteo.net>
Date:   Sun Jan 8 22:58:38 2017 -0600

    system/foomatic-db: Updated for version 20170108.
    
    Signed-off-by: Robby Workman <rworkman at slackbuilds.org>

Rohan Ferris <rferris at posteo.net> wrote:

> Hi all!
> 
> I just discovered that foomatic-db SlackBuild has stopped working due
> to the file being removed from the mirror. It has been updated with a
> newer version - 20170108. The two diffs below allowed it to compile,
> install and function without any further issue...


Done in my branch:

commit 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea
Author: Rohan Ferris <rferris at posteo.net>
Date:   Sun Jan 8 22:58:38 2017 -0600

    system/foomatic-db: Updated for version 20170108.
    
    Signed-off-by: Robby Workman <rworkman at slackbuilds.org>


Thanks!

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

From rworkman at slackbuilds.org  Mon Jan  9 05:00:48 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 8 Jan 2017 23:00:48 -0600
Subject: [Slackbuilds-users] foomatic-db download url needs updating
In-Reply-To: <20170108225938.2f5762d0@home.rlworkman.net>
References: <274eaf18-6007-880e-3962-872af5f2941a@posteo.net>
 <20170108225938.2f5762d0@home.rlworkman.net>
Message-ID: <20170108230048.61c47cb0@home.rlworkman.net>

Wow. No idea how the paste fail happened. 

-RW


On Sun, 8 Jan 2017 22:59:38 -0600
Robby Workman <rworkman at slackbuilds.org> wrote:

> On Mon, 9 Jan 2017 14:39:40 +1000commit
> 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea Author: Rohan Ferris
> <rferris at posteo.net> Date:   Sun Jan 8 22:58:38 2017 -0600
> 
>     system/foomatic-db: Updated for version 20170108.
>     
>     Signed-off-by: Robby Workman <rworkman at slackbuilds.org>
> 
> Rohan Ferris <rferris at posteo.net> wrote:
> 
> > Hi all!
> > 
> > I just discovered that foomatic-db SlackBuild has stopped working
> > due to the file being removed from the mirror. It has been updated
> > with a newer version - 20170108. The two diffs below allowed it to
> > compile, install and function without any further issue...  
> 
> 
> Done in my branch:
> 
> commit 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea
> Author: Rohan Ferris <rferris at posteo.net>
> Date:   Sun Jan 8 22:58:38 2017 -0600
> 
>     system/foomatic-db: Updated for version 20170108.
>     
>     Signed-off-by: Robby Workman <rworkman at slackbuilds.org>
> 
> 
> Thanks!
> 
> -RW 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170108/c47f07a4/attachment.asc>

From willysr at slackbuilds.org  Mon Jan  9 11:13:00 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 9 Jan 2017 18:13:00 +0700
Subject: [Slackbuilds-users] Updates in doinst.sh template
Message-ID: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>

Hi all,

just to inform you that doinst.sh in templates have been updated with a
minor update: to use -f in gtk-update-icon-cache code to force updating
the icon cache instead of updating it in the next reboot.

https://slackbuilds.org/cgit/templates/commit/?id=49cc824b72fbdc8c69b938e7c414b4f7a2341c81

We expect maintainers who have doinst.sh for their packages to update
the code accordingly.

thanks


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Mon Jan  9 13:29:08 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 9 Jan 2017 20:29:08 +0700
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
Message-ID: <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>

> just to inform you that doinst.sh in templates have been updated with a
> minor update: to use -f in gtk-update-icon-cache code to force updating
> the icon cache instead of updating it in the next reboot.
> 
> https://slackbuilds.org/cgit/templates/commit/?id=49cc824b72fbdc8c69b938e7c414b4f7a2341c81
> 
> We expect maintainers who have doinst.sh for their packages to update
> the code accordingly.

I have ran a script to update all remaining doinst.sh in my branch so
maintainer no need to change anything.

If nothing goes wrong, i will push another public update with all those
doinst.sh changes in couple hours


-- 
Willy Sudiarto Raharjo

-------------- 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/20170109/9f3e0102/attachment.asc>

From willysr at slackbuilds.org  Mon Jan  9 13:42:16 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 9 Jan 2017 20:42:16 +0700
Subject: [Slackbuilds-users] SuperCollider(3.6.6) on Slackware 14.2
 depends on yaml-cpp0.3
In-Reply-To: <CALF7xt=pV==0hf+hWhG8Z29ywakpftoC=5EcPFrbiquZ9Dh7kQ@mail.gmail.com>
References: <CALF7xt=pV==0hf+hWhG8Z29ywakpftoC=5EcPFrbiquZ9Dh7kQ@mail.gmail.com>
Message-ID: <2a2b1051-ccfc-2a9d-b8e8-16bfecd9a030@slackbuilds.org>

> To build this package successfully. I have to install yaml-cpp0.3. Note
> that yaml-cpp-0.5.3 will not work. Maybe this package should be added to
> the README file of the Supercollider package.

Is this a runtime deps?
i can build this package without having to install yaml-cpp0.3 nor
yaml-cpp-0.5.3


-- 
Willy Sudiarto Raharjo

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

From reedych at reedych.pw  Mon Jan  9 13:59:09 2017
From: reedych at reedych.pw (reedych)
Date: Mon, 9 Jan 2017 19:59:09 +0600
Subject: [Slackbuilds-users] youtube-dl doesn't work with python 3.6
Message-ID: <20170109195909.09bb50c7@slackware>

After installing python 3.6 youtube-dl has been unstartable. Log of error: https://clck.ru/AT6dr. 

From willysr at slackbuilds.org  Mon Jan  9 14:02:05 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 9 Jan 2017 21:02:05 +0700
Subject: [Slackbuilds-users] youtube-dl doesn't work with python 3.6
In-Reply-To: <20170109195909.09bb50c7@slackware>
References: <20170109195909.09bb50c7@slackware>
Message-ID: <da00593e-b49c-9254-fe66-a140f72149cf@slackbuilds.org>

> After installing python 3.6 youtube-dl has been unstartable. Log of error: https://clck.ru/AT6dr. 

Did you upgrade to youtube-dl-2017.1.2 yet?



-- 
Willy Sudiarto Raharjo

-------------- 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/20170109/10b294f7/attachment-0001.asc>

From reedych at reedych.pw  Mon Jan  9 14:05:42 2017
From: reedych at reedych.pw (reedych)
Date: Mon, 9 Jan 2017 20:05:42 +0600
Subject: [Slackbuilds-users] youtube-dl doesn't work with python 3.6
In-Reply-To: <da00593e-b49c-9254-fe66-a140f72149cf@slackbuilds.org>
References: <20170109195909.09bb50c7@slackware>
 <da00593e-b49c-9254-fe66-a140f72149cf@slackbuilds.org>
Message-ID: <20170109200524.17aa2c22@slackware>

? Mon, 9 Jan 2017 21:02:05 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> ?????:

> > After installing python 3.6 youtube-dl has been unstartable. Log of
> > error: https://clck.ru/AT6dr.   
> 
> Did you upgrade to youtube-dl-2017.1.2 yet?
> 
> 
> 

Yes.
UPD: I recompiled my package and all is ok. Thx

From kjhambrick at gmail.com  Mon Jan  9 14:07:05 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 9 Jan 2017 08:07:05 -0600
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
 <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
Message-ID: <CANBHt+PU-5fEFPW4sW_Dw+UJYzDSTnJL-KQ06StJ7e0TNBXt7Q@mail.gmail.com>

Willy --

Something I've been meaning to ask ...

Is there a git command to download a preview instead of waiting until
Friday Nite / Saturday Morning ?

Thanks !

-- kjh

On Mon, Jan 9, 2017 at 7:29 AM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > just to inform you that doinst.sh in templates have been updated with a
> > minor update: to use -f in gtk-update-icon-cache code to force updating
> > the icon cache instead of updating it in the next reboot.
> >
> > https://slackbuilds.org/cgit/templates/commit/?id=
> 49cc824b72fbdc8c69b938e7c414b4f7a2341c81
> >
> > We expect maintainers who have doinst.sh for their packages to update
> > the code accordingly.
>
> I have ran a script to update all remaining doinst.sh in my branch so
> maintainer no need to change anything.
>
> If nothing goes wrong, i will push another public update with all those
> doinst.sh changes in couple hours
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170109/c88c8a2d/attachment.html>

From willysr at slackbuilds.org  Mon Jan  9 14:09:39 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 9 Jan 2017 21:09:39 +0700
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <CANBHt+PU-5fEFPW4sW_Dw+UJYzDSTnJL-KQ06StJ7e0TNBXt7Q@mail.gmail.com>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
 <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
 <CANBHt+PU-5fEFPW4sW_Dw+UJYzDSTnJL-KQ06StJ7e0TNBXt7Q@mail.gmail.com>
Message-ID: <7c4664f9-953c-d0dc-30b4-ecdb5e865fcd@slackbuilds.org>

> Something I've been meaning to ask ...
> 
> Is there a git command to download a preview instead of waiting until
> Friday Nite / Saturday Morning ?

git clone git://slackbuilds.org/slackbuilds.git
cd slackbuilds
git checkout <branch>
you can check available branches here
https://slackbuilds.org/cgit/slackbuilds/

when you checkout certain branch, all the changes in that branch will be
your working directory. You can test all the changes there and you can
switch back to master branch if public update gets pushed.

-- 
Willy Sudiarto Raharjo

-------------- 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/20170109/28df0922/attachment.asc>

From ts at websafe.pl  Mon Jan  9 14:19:52 2017
From: ts at websafe.pl (Thomas Szteliga)
Date: Mon, 9 Jan 2017 15:19:52 +0100
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
 <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
Message-ID: <39c91810-ad95-2d8e-0a70-58d684366622@websafe.pl>

On 01/09/2017 02:29 PM, Willy Sudiarto Raharjo wrote:
> I have ran a script to update all remaining doinst.sh in my branch so
> maintainer no need to change anything.


Just an idea, maybe https://slackbuilds.org/guidelines/
should mention that maintainers should always
check their packages in git://slackbuilds.org/slackbuilds.git
before submitting upgrades of locally maintained slackbuilds?


-- 
Thomas Szteliga


From willysr at slackbuilds.org  Mon Jan  9 14:24:49 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 9 Jan 2017 21:24:49 +0700
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <39c91810-ad95-2d8e-0a70-58d684366622@websafe.pl>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
 <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
 <39c91810-ad95-2d8e-0a70-58d684366622@websafe.pl>
Message-ID: <63acc352-f23c-6be2-226f-848ef80748ed@slackbuilds.org>

> Just an idea, maybe https://slackbuilds.org/guidelines/
> should mention that maintainers should always
> check their packages in git://slackbuilds.org/slackbuilds.git
> before submitting upgrades of locally maintained slackbuilds?

IMHO, it's easier to see in https://slackbuilds.org/ready/


-- 
Willy Sudiarto Raharjo

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

From ts at websafe.pl  Mon Jan  9 14:40:46 2017
From: ts at websafe.pl (Thomas Szteliga)
Date: Mon, 9 Jan 2017 15:40:46 +0100
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <63acc352-f23c-6be2-226f-848ef80748ed@slackbuilds.org>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
 <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
 <39c91810-ad95-2d8e-0a70-58d684366622@websafe.pl>
 <63acc352-f23c-6be2-226f-848ef80748ed@slackbuilds.org>
Message-ID: <caf2a2cb-2b9a-b2ea-7d1a-ada99bcdd18d@websafe.pl>

On 01/09/2017 03:24 PM, Willy Sudiarto Raharjo wrote:
> IMHO, it's easier to see in https://slackbuilds.org/ready/


OK, but just a notice about this requirement to make sure
that maintainers are aware, that things like:

> I have ran a script to update all remaining doinst.sh in
> my branch so maintainer no need to change anything.


may occur :-)

Otherwise your work may be overwritten...


-- 
Thomas Szteliga


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3719 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170109/0041ae37/attachment.p7s>

From kjhambrick at gmail.com  Mon Jan  9 14:45:10 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 9 Jan 2017 08:45:10 -0600
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <7c4664f9-953c-d0dc-30b4-ecdb5e865fcd@slackbuilds.org>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
 <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
 <CANBHt+PU-5fEFPW4sW_Dw+UJYzDSTnJL-KQ06StJ7e0TNBXt7Q@mail.gmail.com>
 <7c4664f9-953c-d0dc-30b4-ecdb5e865fcd@slackbuilds.org>
Message-ID: <CANBHt+MT_1kdq3-WvmuvkDO5Q89wt2Gc5ma=pgokDiXzZrO5nA@mail.gmail.com>

Thank you as always, Willy !

-- kjh

On Mon, Jan 9, 2017 at 8:09 AM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > Something I've been meaning to ask ...
> >
> > Is there a git command to download a preview instead of waiting until
> > Friday Nite / Saturday Morning ?
>
> git clone git://slackbuilds.org/slackbuilds.git
> cd slackbuilds
> git checkout <branch>
> you can check available branches here
> https://slackbuilds.org/cgit/slackbuilds/
>
> when you checkout certain branch, all the changes in that branch will be
> your working directory. You can test all the changes there and you can
> switch back to master branch if public update gets pushed.
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170109/3d69723d/attachment-0001.html>

From ryanpcmcquen at member.fsf.org  Mon Jan  9 14:55:34 2017
From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen)
Date: Mon, 9 Jan 2017 06:55:34 -0800
Subject: [Slackbuilds-users] Orphaning some builds.
Message-ID: <CAAcyf-pD313ztT8hXSTVEyfwPXv3vU+MZDvUJiU2YwY3KJtBzQ@mail.gmail.com>

I am attempting to use less non-free software, so I?ll be giving up these
three builds, hopefully someone is interested in them:

multimedia/spotify
network/hipchat
network/slack

Konpai,
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170109/269f0792/attachment.html>

From atelszewski at gmail.com  Mon Jan  9 15:06:33 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 9 Jan 2017 16:06:33 +0100
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
 <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
Message-ID: <2e21e53e-3382-42e6-42a2-f9ed6124e1b7@gmail.com>

On 09/01/17 14:29, Willy Sudiarto Raharjo wrote:
> If nothing goes wrong, i will push another public update with all those
> doinst.sh changes in couple hours

I don't know if it's wrong from admins point of view, but some packages 
are listed twice in the ready queue.

For example: LibreOffice.

LibreOffice was in the ready queue for updated version, before you 
updated doinst.sh.

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Mon Jan  9 15:13:42 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 9 Jan 2017 22:13:42 +0700
Subject: [Slackbuilds-users] Updates in doinst.sh template
In-Reply-To: <2e21e53e-3382-42e6-42a2-f9ed6124e1b7@gmail.com>
References: <3aae54d6-d059-7898-90a8-e20a35b3fa78@slackbuilds.org>
 <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6@slackbuilds.org>
 <2e21e53e-3382-42e6-42a2-f9ed6124e1b7@gmail.com>
Message-ID: <09fb1ce2-fcb5-d2bd-85d5-ef32376fa7e6@slackbuilds.org>

>> If nothing goes wrong, i will push another public update with all those
>> doinst.sh changes in couple hours
> 
> I don't know if it's wrong from admins point of view, but some packages
> are listed twice in the ready queue.
> 
> For example: LibreOffice.
> 
> LibreOffice was in the ready queue for updated version, before you
> updated doinst.sh.

Yes, we noticed that, but since they changed different part of the
scripts, they will not conflict to each other

the unscheduled public update is to avoid future conflict with the rest
of the updates this week.

-- 
Willy Sudiarto Raharjo

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

From reedych at reedych.pw  Mon Jan  9 15:23:05 2017
From: reedych at reedych.pw (reedych)
Date: Mon, 9 Jan 2017 21:23:05 +0600
Subject: [Slackbuilds-users] Orphaning some builds.
In-Reply-To: <CAAcyf-pD313ztT8hXSTVEyfwPXv3vU+MZDvUJiU2YwY3KJtBzQ@mail.gmail.com>
References: <CAAcyf-pD313ztT8hXSTVEyfwPXv3vU+MZDvUJiU2YwY3KJtBzQ@mail.gmail.com>
Message-ID: <20170109212305.12df1893@slackware>

? Mon, 9 Jan 2017 06:55:34 -0800
"Ryan P.C. McQuen" <ryanpcmcquen at member.fsf.org> ?????:

> I am attempting to use less non-free software, so I?ll be giving up
> these three builds, hopefully someone is interested in them:
> 
> multimedia/spotify
> network/hipchat
> network/slack
> 
> Konpai,
> ?

>slack
wut!?

From reedych at reedych.pw  Mon Jan  9 15:56:13 2017
From: reedych at reedych.pw (reedych)
Date: Mon, 9 Jan 2017 21:56:13 +0600
Subject: [Slackbuilds-users] owncloud-client dependency missing
Message-ID: <20170109215613.69806330@slackware>

The slackbuild needs "qt5-webkit". Pls fix.

From 1.41421 at gmail.com  Mon Jan  9 16:02:50 2017
From: 1.41421 at gmail.com (JCA)
Date: Mon, 9 Jan 2017 09:02:50 -0700
Subject: [Slackbuilds-users] cracklib installation incomplete
Message-ID: <CAFy1yb2QRpAOVF3eQoG_BeF=T68Vdwy0nOo7eTMhbSKQ-EppFA@mail.gmail.com>

After successfully building and installing the package, I am getting the
following:

$ echo "SomeKey" | cracklib-check
/usr/share/cracklib/pw_dict.pwd.gz: No such file or directory
clave: error loading dictionary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170109/d653ede3/attachment.html>

From ts at websafe.pl  Mon Jan  9 16:05:24 2017
From: ts at websafe.pl (Thomas Szteliga)
Date: Mon, 9 Jan 2017 17:05:24 +0100
Subject: [Slackbuilds-users] owncloud-client dependency missing
In-Reply-To: <20170109215613.69806330@slackware>
References: <20170109215613.69806330@slackware>
Message-ID: <82b769ec-d441-a4f8-0a7f-25b6abd30f25@websafe.pl>

On 01/09/2017 04:56 PM, reedych wrote:
> The slackbuild needs "qt5-webkit". Pls fix.

BTW:
https://owncloud.org/blog/owncloud-statement-concerning-the-formation-of-nextcloud-by-frank-karlitschek/


https://nextcloud.com/install/


-- 
Thomas Szteliga


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3719 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170109/fad03bac/attachment.p7s>

From reedych at reedych.pw  Mon Jan  9 16:10:16 2017
From: reedych at reedych.pw (reedych)
Date: Mon, 9 Jan 2017 22:10:16 +0600
Subject: [Slackbuilds-users] owncloud-client dependency missing
In-Reply-To: <82b769ec-d441-a4f8-0a7f-25b6abd30f25@websafe.pl>
References: <20170109215613.69806330@slackware>
 <82b769ec-d441-a4f8-0a7f-25b6abd30f25@websafe.pl>
Message-ID: <20170109221016.7c03b231@slackware>

? Mon, 9 Jan 2017 17:05:24 +0100
Thomas Szteliga <ts at websafe.pl> ?????:

> On 01/09/2017 04:56 PM, reedych wrote:
> > The slackbuild needs "qt5-webkit". Pls fix.  
> 
> BTW:
> https://owncloud.org/blog/owncloud-statement-concerning-the-formation-of-nextcloud-by-frank-karlitschek/
> 
> 
> https://nextcloud.com/install/
> 
> 

wt*... Has slackbuilds.org a client for nextcloud?

From matteo.bernardini at gmail.com  Mon Jan  9 16:12:11 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 9 Jan 2017 17:12:11 +0100
Subject: [Slackbuilds-users] owncloud-client dependency missing
In-Reply-To: <20170109215613.69806330@slackware>
References: <20170109215613.69806330@slackware>
Message-ID: <CAPsDuS5Jf_sE7hSuZyAmiCiLUn7Upf=5RoeDQ7Y1T4D24aOstg@mail.gmail.com>

2017-01-09 16:56 GMT+01:00 reedych <reedych at reedych.pw>:
> The slackbuild needs "qt5-webkit". Pls fix.

Hi reedych,

that most probably happened to you because you built owncloud-client,
and its dependency qtkeychain first, with qt5 installed, so qtkeychain
first and owncloud-client after used qt5.

try removing qt5 and then rebuild qtkeychain first and then
owncloud-client: after having installed the two you can reinstall qt5.

Matteo

From ts at websafe.pl  Mon Jan  9 16:12:26 2017
From: ts at websafe.pl (Thomas Szteliga)
Date: Mon, 9 Jan 2017 17:12:26 +0100
Subject: [Slackbuilds-users] owncloud-client dependency missing
In-Reply-To: <20170109221016.7c03b231@slackware>
References: <20170109215613.69806330@slackware>
 <82b769ec-d441-a4f8-0a7f-25b6abd30f25@websafe.pl>
 <20170109221016.7c03b231@slackware>
Message-ID: <765eaba9-e3da-636c-54eb-0f5b9d89212d@websafe.pl>

On 01/09/2017 05:10 PM, reedych wrote:
>> https://nextcloud.com/install/
> wt*... Has slackbuilds.org a client for nextcloud?


Not yet. I'll try to prepare slackbuilds this weekend
for nextcloud client and server.


-- 
Thomas Szteliga


From matteo.bernardini at gmail.com  Mon Jan  9 16:19:01 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 9 Jan 2017 17:19:01 +0100
Subject: [Slackbuilds-users] owncloud-client dependency missing
In-Reply-To: <CAPsDuS5Jf_sE7hSuZyAmiCiLUn7Upf=5RoeDQ7Y1T4D24aOstg@mail.gmail.com>
References: <20170109215613.69806330@slackware>
 <CAPsDuS5Jf_sE7hSuZyAmiCiLUn7Upf=5RoeDQ7Y1T4D24aOstg@mail.gmail.com>
Message-ID: <CAPsDuS4-FX9nx_4v2X6Rd9nowK3q6dRHWDNVvzMGoDTk2drB3w@mail.gmail.com>

2017-01-09 17:12 GMT+01:00 Matteo Bernardini <matteo.bernardini at gmail.com>:
> 2017-01-09 16:56 GMT+01:00 reedych <reedych at reedych.pw>:
>> The slackbuild needs "qt5-webkit". Pls fix.
>
> Hi reedych,
>
> that most probably happened to you because you built owncloud-client,
> and its dependency qtkeychain first, with qt5 installed, so qtkeychain
> first and owncloud-client after used qt5.
>
> try removing qt5 and then rebuild qtkeychain first and then
> owncloud-client: after having installed the two you can reinstall qt5.

what I just wrote is also stated in owncloud-client's README

https://slackbuilds.org/repository/14.2/network/owncloud-client/

remember that you are supposed to read the READMEs of the stuff you
build from SlackBuilds.org.

Matteo

From matteo.bernardini at gmail.com  Mon Jan  9 16:28:59 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 9 Jan 2017 17:28:59 +0100
Subject: [Slackbuilds-users] cracklib installation incomplete
In-Reply-To: <CAFy1yb2QRpAOVF3eQoG_BeF=T68Vdwy0nOo7eTMhbSKQ-EppFA@mail.gmail.com>
References: <CAFy1yb2QRpAOVF3eQoG_BeF=T68Vdwy0nOo7eTMhbSKQ-EppFA@mail.gmail.com>
Message-ID: <CAPsDuS4bNQvPs=51qZ+rqboqfHAM5UVHrrO-N-qMpwWpeM3FLw@mail.gmail.com>

2017-01-09 17:02 GMT+01:00 JCA <1.41421 at gmail.com>:
> After successfully building and installing the package, I am getting the
> following:
>
> $ echo "SomeKey" | cracklib-check
> /usr/share/cracklib/pw_dict.pwd.gz: No such file or directory
> clave: error loading dictionary

Hi JCA,

have you read its README ( /usr/doc/cracklib-2.9.6/README )? I don't
use it but it states:
"CrackLib is NOT a TOOL.  It is not a complete package.  It is not
something you can utilise directly.
It is a resource, an aid, something to enhance the functionality of
other software.  You need to (either) write OR modify other software
to use it.  If you can't do this, then you shouldn't be wasting your
time with it."

Matteo

From reedych at reedych.pw  Mon Jan  9 16:30:08 2017
From: reedych at reedych.pw (reedych)
Date: Mon, 9 Jan 2017 22:30:08 +0600
Subject: [Slackbuilds-users] owncloud-client dependency missing
In-Reply-To: <CAPsDuS4-FX9nx_4v2X6Rd9nowK3q6dRHWDNVvzMGoDTk2drB3w@mail.gmail.com>
References: <20170109215613.69806330@slackware>
 <CAPsDuS5Jf_sE7hSuZyAmiCiLUn7Upf=5RoeDQ7Y1T4D24aOstg@mail.gmail.com>
 <CAPsDuS4-FX9nx_4v2X6Rd9nowK3q6dRHWDNVvzMGoDTk2drB3w@mail.gmail.com>
Message-ID: <20170109223008.54b51f0b@slackware>

? Mon, 9 Jan 2017 17:19:01 +0100
Matteo Bernardini <matteo.bernardini at gmail.com> ?????:

> 2017-01-09 17:12 GMT+01:00 Matteo Bernardini
> <matteo.bernardini at gmail.com>:
> > 2017-01-09 16:56 GMT+01:00 reedych <reedych at reedych.pw>:  
> >> The slackbuild needs "qt5-webkit". Pls fix.  
> >
> > Hi reedych,
> >
> > that most probably happened to you because you built
> > owncloud-client, and its dependency qtkeychain first, with qt5
> > installed, so qtkeychain first and owncloud-client after used qt5.
> >
> > try removing qt5 and then rebuild qtkeychain first and then
> > owncloud-client: after having installed the two you can reinstall
> > qt5.  
> 
> what I just wrote is also stated in owncloud-client's README
> 
> https://slackbuilds.org/repository/14.2/network/owncloud-client/
> 
> remember that you are supposed to read the READMEs of the stuff you
> build from SlackBuilds.org.
> 
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

oops, sorry :)

From 1.41421 at gmail.com  Mon Jan  9 16:32:40 2017
From: 1.41421 at gmail.com (JCA)
Date: Mon, 9 Jan 2017 09:32:40 -0700
Subject: [Slackbuilds-users] cracklib installation incomplete
In-Reply-To: <CAPsDuS4bNQvPs=51qZ+rqboqfHAM5UVHrrO-N-qMpwWpeM3FLw@mail.gmail.com>
References: <CAFy1yb2QRpAOVF3eQoG_BeF=T68Vdwy0nOo7eTMhbSKQ-EppFA@mail.gmail.com>
 <CAPsDuS4bNQvPs=51qZ+rqboqfHAM5UVHrrO-N-qMpwWpeM3FLw@mail.gmail.com>
Message-ID: <CAFy1yb3UHwFP10s3Lb5si_Xj1NP9uEEeMXPC04pY2o+Bbfa74A@mail.gmail.com>

OK, thanks.

On Mon, Jan 9, 2017 at 9:28 AM, Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

> 2017-01-09 17:02 GMT+01:00 JCA <1.41421 at gmail.com>:
> > After successfully building and installing the package, I am getting the
> > following:
> >
> > $ echo "SomeKey" | cracklib-check
> > /usr/share/cracklib/pw_dict.pwd.gz: No such file or directory
> > clave: error loading dictionary
>
> Hi JCA,
>
> have you read its README ( /usr/doc/cracklib-2.9.6/README )? I don't
> use it but it states:
> "CrackLib is NOT a TOOL.  It is not a complete package.  It is not
> something you can utilise directly.
> It is a resource, an aid, something to enhance the functionality of
> other software.  You need to (either) write OR modify other software
> to use it.  If you can't do this, then you shouldn't be wasting your
> time with it."
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170109/0a0d950a/attachment.html>

From matteo.bernardini at gmail.com  Mon Jan  9 16:36:28 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 9 Jan 2017 17:36:28 +0100
Subject: [Slackbuilds-users] cracklib installation incomplete
In-Reply-To: <CAFy1yb3UHwFP10s3Lb5si_Xj1NP9uEEeMXPC04pY2o+Bbfa74A@mail.gmail.com>
References: <CAFy1yb2QRpAOVF3eQoG_BeF=T68Vdwy0nOo7eTMhbSKQ-EppFA@mail.gmail.com>
 <CAPsDuS4bNQvPs=51qZ+rqboqfHAM5UVHrrO-N-qMpwWpeM3FLw@mail.gmail.com>
 <CAFy1yb3UHwFP10s3Lb5si_Xj1NP9uEEeMXPC04pY2o+Bbfa74A@mail.gmail.com>
Message-ID: <CAPsDuS6agKHFxvBfm1tP6ynwh5WOJ=EJuzoMyBtxj_sMknuwhA@mail.gmail.com>

if you're looking for a password-cracking tool you should have a look
at john the ripper

https://slackbuilds.org/repository/14.2/system/john/

Matteo

From 1.41421 at gmail.com  Mon Jan  9 16:47:19 2017
From: 1.41421 at gmail.com (JCA)
Date: Mon, 9 Jan 2017 09:47:19 -0700
Subject: [Slackbuilds-users] cracklib installation incomplete
In-Reply-To: <CAPsDuS6agKHFxvBfm1tP6ynwh5WOJ=EJuzoMyBtxj_sMknuwhA@mail.gmail.com>
References: <CAFy1yb2QRpAOVF3eQoG_BeF=T68Vdwy0nOo7eTMhbSKQ-EppFA@mail.gmail.com>
 <CAPsDuS4bNQvPs=51qZ+rqboqfHAM5UVHrrO-N-qMpwWpeM3FLw@mail.gmail.com>
 <CAFy1yb3UHwFP10s3Lb5si_Xj1NP9uEEeMXPC04pY2o+Bbfa74A@mail.gmail.com>
 <CAPsDuS6agKHFxvBfm1tP6ynwh5WOJ=EJuzoMyBtxj_sMknuwhA@mail.gmail.com>
Message-ID: <CAFy1yb1iOPvpoNsG3nL4OtLHe1UBvK7=XZ+xfOCxeNURmkaqJQ@mail.gmail.com>

No, I just wanted to use it to get an idea of the strength of different
common passwords. But, sure, I'd look into john the ripper. Thanks.

On Mon, Jan 9, 2017 at 9:36 AM, Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

> if you're looking for a password-cracking tool you should have a look
> at john the ripper
>
> https://slackbuilds.org/repository/14.2/system/john/
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170109/9c62502d/attachment-0001.html>

From info at microlinux.fr  Mon Jan  9 17:16:32 2017
From: info at microlinux.fr (Nicolas Kovacs)
Date: Mon, 9 Jan 2017 18:16:32 +0100
Subject: [Slackbuilds-users] owncloud-client dependency missing
In-Reply-To: <20170109215613.69806330@slackware>
References: <20170109215613.69806330@slackware>
Message-ID: <d54aea38-e575-dbe9-7edd-e18d427232ac@microlinux.fr>

Le 09/01/2017 ? 16:56, reedych a ?crit :
> The slackbuild needs "qt5-webkit". Pls fix.

Please *don't* introduce a qt5 dependency for owncloud-client. As far as
I know, there is none.

Cheers,

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

From willysr at slackbuilds.org  Mon Jan  9 17:22:31 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 10 Jan 2017 00:22:31 +0700
Subject: [Slackbuilds-users] cracklib installation incomplete
In-Reply-To: <CAFy1yb2QRpAOVF3eQoG_BeF=T68Vdwy0nOo7eTMhbSKQ-EppFA@mail.gmail.com>
References: <CAFy1yb2QRpAOVF3eQoG_BeF=T68Vdwy0nOo7eTMhbSKQ-EppFA@mail.gmail.com>
Message-ID: <a0fb478e-1e5e-0b52-56dd-e54c9a8f8e07@slackbuilds.org>

> After successfully building and installing the package, I am getting the
> following:
> 
> $ echo "SomeKey" | cracklib-check
> /usr/share/cracklib/pw_dict.pwd.gz: No such file or directory
> clave: error loading dictionary

perfect timing
i found that issue few hours ago when i was reading an article and
checking it through my CSB and i have pushed a fix on my branch

https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=243cda83e55aa1200127ef5f318403ff5069e625


-- 
Willy Sudiarto Raharjo

-------------- 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/20170110/899aeb1c/attachment.asc>

From markus.ka.rinne at gmail.com  Mon Jan  9 21:56:10 2017
From: markus.ka.rinne at gmail.com (Markus Rinne)
Date: Mon, 9 Jan 2017 23:56:10 +0200
Subject: [Slackbuilds-users] foomatic-db download url needs updating
In-Reply-To: <20170108225938.2f5762d0@home.rlworkman.net>
References: <274eaf18-6007-880e-3962-872af5f2941a@posteo.net>
 <20170108225938.2f5762d0@home.rlworkman.net>
Message-ID: <20170109215610.GA2298@tursas.sidaroth.foo>

On Sun, Jan 08, 2017 at 10:59:38PM -0600, Robby Workman wrote:
> Done in my branch:
> 
> commit 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea
> Author: Rohan Ferris <rferris at posteo.net>
> Date:   Sun Jan 8 22:58:38 2017 -0600
> 
>     system/foomatic-db: Updated for version 20170108.
>     
>     Signed-off-by: Robby Workman <rworkman at slackbuilds.org>

Thanks for updating this.  It seems that nowadays foomatic-db releases
new package every day, so it's not really possible to keep up to date.

    Markus

From rferris at posteo.net  Mon Jan  9 21:11:09 2017
From: rferris at posteo.net (Rohan Ferris)
Date: Tue, 10 Jan 2017 07:11:09 +1000
Subject: [Slackbuilds-users] foomatic-db download url needs updating
In-Reply-To: <20170109215610.GA2298@tursas.sidaroth.foo>
References: <274eaf18-6007-880e-3962-872af5f2941a@posteo.net>
 <20170108225938.2f5762d0@home.rlworkman.net>
 <20170109215610.GA2298@tursas.sidaroth.foo>
Message-ID: <93E43617-EB0E-4178-AE75-83D5727AE34D@posteo.net>

Totally. Nobody can be expected to keep up with that kind of pace; especially when it only really needed updating because they trashed the previous release.

> On 10 Jan 2017, at 7:56 am, Markus Rinne <markus.ka.rinne at gmail.com> wrote:
> 
>> On Sun, Jan 08, 2017 at 10:59:38PM -0600, Robby Workman wrote:
>> Done in my branch:
>> 
>> commit 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea
>> Author: Rohan Ferris <rferris at posteo.net>
>> Date:   Sun Jan 8 22:58:38 2017 -0600
>> 
>>    system/foomatic-db: Updated for version 20170108.
>> 
>>    Signed-off-by: Robby Workman <rworkman at slackbuilds.org>
> 
> Thanks for updating this.  It seems that nowadays foomatic-db releases
> new package every day, so it's not really possible to keep up to date.
> 
>    Markus


From slack.dhabyx at gmail.com  Mon Jan  9 21:57:56 2017
From: slack.dhabyx at gmail.com (Dhaby Xiloj)
Date: Mon, 9 Jan 2017 15:57:56 -0600
Subject: [Slackbuilds-users] Orphaning some builds.
In-Reply-To: <CAAcyf-pD313ztT8hXSTVEyfwPXv3vU+MZDvUJiU2YwY3KJtBzQ@mail.gmail.com>
References: <CAAcyf-pD313ztT8hXSTVEyfwPXv3vU+MZDvUJiU2YwY3KJtBzQ@mail.gmail.com>
Message-ID: <1fc2d680-ed26-4779-bd9a-7f30b4c867c9@gmail.com>

> I am attempting to use less non-free software, so I?ll be giving up
> these three builds, hopefully someone is interested in them:
>
> |multimedia/spotify|
> |network/hipchat|
> |network/slack|
>
> Konpai,
>
I take spotify

-- 
Dhaby Xiloj

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

From idlemoor at slackbuilds.org  Mon Jan  9 23:42:51 2017
From: idlemoor at slackbuilds.org (David Spencer)
Date: Mon, 9 Jan 2017 23:42:51 +0000
Subject: [Slackbuilds-users] Updates - 20170109.1
Message-ID: <7ed99694-fdf9-ca7f-b1b5-ab673e9a8aa1@slackbuilds.org>

Hey folks, here is a new Public Update for you!


As well as the usual updates, there are about 700 commits that revise
doinst.sh -- thanks to Alexander Verbovetsky for finding the problem and
finding the fix, as he reported on this mailing list yesterday.


**IMPORTANT** -- for all Maintainers

When you make a new update, *always* please start from the latest
version on SlackBuilds.org (do not use your local version) because
sometimes we need to make big changes (like this doinst.sh update) to
all the scripts.


Another **IMPORTANT** -- for nvidia users

Please do not use the nvidia-driver and nvidia-kernel updates that I
merged in this update -- they are not yet ready and I should not have
merged them yet.  Sorry everybody!  I will make a new public update in
the next couple of hours that reverts these commits.  Thanks to Matteo
for being so observant :)


Here's your ChangeLog:

Mon Jan  9 20:56:42 UTC 2017
academic/GeoGebra: Update doinst.sh.
academic/Kst: Update doinst.sh.
academic/artha: Update doinst.sh.
academic/bibus: Update doinst.sh.
academic/chemtool: Update doinst.sh.
academic/convertall: Update doinst.sh.
academic/drawtiming: Update doinst.sh.
academic/edsim51di: Update doinst.sh.
academic/fet: Update doinst.sh.
academic/flashqard: Update doinst.sh.
academic/freechartgeany: Update doinst.sh.
academic/galculator: Update doinst.sh.
academic/gcalctool: Update doinst.sh.
academic/gchemutils: Update doinst.sh.
academic/geda-gaf: Update doinst.sh.
academic/gelemental: Update doinst.sh.
academic/genius: Update doinst.sh.
academic/gerbv: Update doinst.sh.
academic/ghemical: Update doinst.sh.
academic/gnucap: Update doinst.sh.
academic/gretl: Update doinst.sh.
academic/gspiceui: Update doinst.sh.
academic/gwyddion: Update doinst.sh.
academic/kile: Update doinst.sh.
academic/klavaro: Update doinst.sh.
academic/knime: Update doinst.sh.
academic/ktikz: Update doinst.sh.
academic/kurso: Update doinst.sh.
academic/labplot2: Update doinst.sh.
academic/loggerpro: Update doinst.sh.
academic/matio: Added (MAT File I/O Library).
academic/mendeleydesktop: Update doinst.sh.
academic/octave: Update doinst.sh.
academic/pcb: Update doinst.sh.
academic/pulseview: Update doinst.sh.
academic/qtoctave: Update doinst.sh.
academic/sage: Update doinst.sh.
academic/smath-studio: Update doinst.sh.
academic/speedcrunch: Update doinst.sh.
academic/spiceopus: Update doinst.sh.
academic/tilem2: Update doinst.sh.
academic/tkgate: Update doinst.sh.
academic/tuxmath: Update doinst.sh.
academic/veusz: Update doinst.sh.
academic/wxmacmolplt: Update doinst.sh.
academic/xiphos: Update doinst.sh.
accessibility/easystroke: Update doinst.sh.
audio/HamsiManager: Update doinst.sh.
audio/alsa-tools: Update doinst.sh.
audio/ardour: Update doinst.sh.
audio/ario: Update doinst.sh.
audio/audacity: Update doinst.sh.
audio/bristol: Update doinst.sh.
audio/butt: Update doinst.sh.
audio/calf: Update doinst.sh.
audio/clementine: Update doinst.sh.
audio/creox4: Update doinst.sh.
audio/deadbeef: Update doinst.sh.
audio/easymp3gain: Update doinst.sh.
audio/easytag: Update doinst.sh.
audio/fantasia: Update doinst.sh.
audio/flacon: Update doinst.sh.
audio/fmit: Update doinst.sh.
audio/gmpc: Update doinst.sh.
audio/gogglesmm: Update doinst.sh.
audio/grip2: Update doinst.sh.
audio/guitarix: Update doinst.sh.
audio/hydrogen: Update doinst.sh.
audio/jack-keyboard: Update doinst.sh.
audio/jack_capture: Update doinst.sh.
audio/jamin: Update doinst.sh.
audio/jokosher: Update doinst.sh.
audio/jvmetro: Update doinst.sh.
audio/kid3: Update doinst.sh.
audio/lastfm: Update doinst.sh.
audio/lingot: Update doinst.sh.
audio/mhwaveedit: Update doinst.sh.
audio/muse: Update doinst.sh.
audio/ocp: Update doinst.sh.
audio/pasystray: Update doinst.sh.
audio/pithos: Update doinst.sh.
audio/pogo: Update doinst.sh.
audio/portmidi: Update doinst.sh.
audio/qastools: Update doinst.sh.
audio/qjackctl: Update doinst.sh.
audio/qmidiarp: Update doinst.sh.
audio/qmidinet: Update doinst.sh.
audio/qmmp-plugin-pack: Update doinst.sh.
audio/qmmp: Update doinst.sh.
audio/qsynth: Update doinst.sh.
audio/qtractor: Update doinst.sh.
audio/quodlibet: Update doinst.sh.
audio/rosegarden: Update doinst.sh.
audio/sayonara-player: Update doinst.sh.
audio/sooperlooper: Update doinst.sh.
audio/soundconverter: Update doinst.sh.
audio/soundkonverter: Update doinst.sh.
audio/swami: Update doinst.sh.
audio/tagtool: Update doinst.sh.
audio/transcribe: Update doinst.sh.
audio/vmpk: Update doinst.sh.
audio/vocoder: Update doinst.sh.
audio/volwheel: Update doinst.sh.
audio/waon: Update doinst.sh.
audio/wavbreaker: Update doinst.sh.
business/AssociationSubscribersManager: Update doinst.sh.
business/lemonpos: Update doinst.sh.
business/skrooge: Update doinst.sh.
desktop/ClipboardViewer: Update doinst.sh.
desktop/LX-Colors-Revival: Update doinst.sh.
desktop/LX-Colors-themes: Update doinst.sh.
desktop/alltray: Update doinst.sh.
desktop/ambiance-radiance-flat-colors-gtk-theme: Update doinst.sh.
desktop/anki: Update doinst.sh.
desktop/areao43-icon-theme: Update doinst.sh.
desktop/avant-window-navigator: Update doinst.sh.
desktop/awn-extras: Update doinst.sh.
desktop/awoken-icon-theme: Update doinst.sh.
desktop/boje-themes: Update doinst.sh.
desktop/bunsen-themes: Update doinst.sh.
desktop/cairo-compmgr: Update doinst.sh.
desktop/catfish: Update doinst.sh.
desktop/cathexis-suite-themes: Update doinst.sh.
desktop/cellwriter: Update doinst.sh.
desktop/ceti-2-theme: Update doinst.sh.
desktop/clipit: Update doinst.sh.
desktop/compiz-boxmenu: Update doinst.sh.
desktop/copyq: Update doinst.sh.
desktop/cryptkeeper: Update doinst.sh.
desktop/cwp: Update doinst.sh.
desktop/ede: Update doinst.sh.
desktop/emerald: Update doinst.sh.
desktop/faba-icon-theme: Update doinst.sh.
desktop/faba-mono-icons: Update doinst.sh.
desktop/faenza-cupertino: Update doinst.sh.
desktop/faenza-icon-theme: Update doinst.sh.
desktop/faenza-xfce: Update doinst.sh.
desktop/faience-icon-theme: Update doinst.sh.
desktop/florence: Update doinst.sh.
desktop/fusion-icon: Update doinst.sh.
desktop/glabels: Update doinst.sh.
desktop/gmusicbrowser-art: Update doinst.sh.
desktop/gnome-menus: Update doinst.sh.
desktop/gtk-theme-Albatross: Update doinst.sh.
desktop/gtk-theme-Blackbird: Update doinst.sh.
desktop/gtk-theme-Bluebird: Update doinst.sh.
desktop/gtk-theme-Greybird: Update doinst.sh.
desktop/gtk-theme-Orion: Update doinst.sh.
desktop/gtkhash: Update doinst.sh.
desktop/homerun: Update doinst.sh.
desktop/kde-gtk-config: Update doinst.sh.
desktop/kover: Update doinst.sh.
desktop/moka-icon-theme: Update doinst.sh.
desktop/moka-minimal: Update doinst.sh.
desktop/moka-themes: Update doinst.sh.
desktop/mousepad: Update doinst.sh.
desktop/neutral: Update doinst.sh.
desktop/nitrogen: Update doinst.sh.
desktop/numix-folders: Update doinst.sh.
desktop/numix-gtk-theme: Update doinst.sh.
desktop/numix-icon-theme-circle: Update doinst.sh.
desktop/numix-icon-theme-square: Update doinst.sh.
desktop/numix-icon-theme: Update doinst.sh.
desktop/numix-pack: Update doinst.sh.
desktop/obconf: Update doinst.sh.
desktop/obkey: Update doinst.sh.
desktop/obsession: Update doinst.sh.
desktop/obshutdown: Update doinst.sh.
desktop/openbox-menu: Update doinst.sh.
desktop/openbox-simple-theme: Update doinst.sh.
desktop/oranchelo-icon-theme: Update doinst.sh.
desktop/orchis-gtk-theme: Update doinst.sh.
desktop/paper-gtk-theme: Update doinst.sh.
desktop/paper-icon-theme: Update doinst.sh.
desktop/plank: Update doinst.sh.
desktop/pspshrink: Update doinst.sh.
desktop/pytyle: Update doinst.sh.
desktop/q4wine: Update doinst.sh.
desktop/qmmp-skins: Update doinst.sh.
desktop/qtwitter: Update doinst.sh.
desktop/quadkonsole4: Update doinst.sh.
desktop/razorqt: Update doinst.sh.
desktop/recoll: Update doinst.sh.
desktop/recorditnow: Update doinst.sh.
desktop/redshift: Update doinst.sh.
desktop/rodent: Update doinst.sh.
desktop/sawfish-pager: Update doinst.sh.
desktop/sawfish-session-dialog: Update doinst.sh.
desktop/sawfish: Update doinst.sh.
desktop/seafile-gui: Update doinst.sh.
desktop/searchmonkey: Update doinst.sh.
desktop/simon: Update doinst.sh.
desktop/siva-flat-themes: Update doinst.sh.
desktop/skippy-xd: Update doinst.sh.
desktop/smaragd: Update doinst.sh.
desktop/ssr: Update doinst.sh.
desktop/stoken: Update doinst.sh.
desktop/thunar-archive-plugin: Update doinst.sh.
desktop/thunar-dropbox: Update doinst.sh.
desktop/thunar-vcs-plugin: Update doinst.sh.
desktop/wally: Update doinst.sh.
desktop/wmudmount: Update doinst.sh.
desktop/x-tile: Update doinst.sh.
desktop/xed: Update doinst.sh.
desktop/xfce4-battery-plugin: Update doinst.sh.
desktop/xfce4-cpufreq-plugin: Update doinst.sh.
desktop/xfce4-cpugraph-plugin: Update doinst.sh.
desktop/xfce4-datetime-plugin: Update doinst.sh.
desktop/xfce4-dict: Update doinst.sh.
desktop/xfce4-embed-plugin: Update doinst.sh.
desktop/xfce4-eyes-plugin: Update doinst.sh.
desktop/xfce4-fsguard-plugin: Update doinst.sh.
desktop/xfce4-kbdleds-plugin: Update doinst.sh.
desktop/xfce4-mailwatch-plugin: Update doinst.sh.
desktop/xfce4-mount-plugin: Update doinst.sh.
desktop/xfce4-netload-plugin: Update doinst.sh.
desktop/xfce4-notes-plugin: Update doinst.sh.
desktop/xfce4-sensors-plugin: Update doinst.sh.
desktop/xfce4-wavelan-plugin: Update doinst.sh.
desktop/xfce4-whiskermenu-plugin: Update doinst.sh.
desktop/xfce4-windowck-plugin: Update doinst.sh.
desktop/xipper: Update doinst.sh.
desktop/yad: Update doinst.sh.
desktop/zuki-themes: Update doinst.sh.
development/KKEdit: Update doinst.sh.
development/ParadisEO: Update doinst.sh.
development/anjuta: Update doinst.sh.
development/asem51: Update doinst.sh.
development/bluefish: Update doinst.sh.
development/brackets: Update doinst.sh.
development/codeblocks: Update doinst.sh.
development/devhelp: Update doinst.sh.
development/dmd: Updated for version 2.072.2.
development/eagle: Update doinst.sh.
development/ebe: Update doinst.sh.
development/eclipse-cpp: Update doinst.sh.
development/eclipse-java: Update doinst.sh.
development/eclipse-jee: Update doinst.sh.
development/fuel: Update doinst.sh.
development/gambas3: Update doinst.sh.
development/geany-plugins: Update doinst.sh.
development/geany: Update doinst.sh.
development/gedit: Update doinst.sh.
development/glade: Update doinst.sh.
development/gnome-inform7: Update doinst.sh.
development/gpsim: Update doinst.sh.
development/icemon: Update doinst.sh.
development/kdesvn: Update doinst.sh.
development/kdiff3: Update doinst.sh.
development/kicad: Update doinst.sh.
development/kompozer: Update doinst.sh.
development/lcov: Updated for version 1.13.
development/mcu8051ide: Update doinst.sh.
development/medit: Update doinst.sh.
development/meld3: Update doinst.sh.
development/meld: Update doinst.sh.
development/monodevelop: Update doinst.sh.
development/mstch: Added (templates in C++11).
development/mysql-workbench: Update doinst.sh.
development/netbeans: Update doinst.sh.
development/nodejs: Updated for version 6.9.4.
development/omniORB: Update doinst.sh.
development/omniORBpy: Update doinst.sh.
development/p4v: Update doinst.sh.
development/poedit: Update doinst.sh.
development/qt-creator2: Update doinst.sh.
development/qt-creator: Update doinst.sh.
development/regexxer: Update doinst.sh.
development/rmlmmc: Update doinst.sh.
development/s51dude: Update doinst.sh.
development/scite: Update doinst.sh.
development/scratch: Update doinst.sh.
development/simulavr: Update doinst.sh.
development/smlnj: Update doinst.sh.
development/spyder: Update doinst.sh.
development/staruml: Update doinst.sh.
development/sublime_text: Update doinst.sh.
development/visual-studio-code: Update doinst.sh.
development/vscode: Update doinst.sh.
development/vstudio: Update doinst.sh.
development/zeal: Update doinst.sh.
development/zed: Update doinst.sh.
games/KAdventure: Update doinst.sh.
games/SLADE: Update doinst.sh.
games/abe: Update doinst.sh.
games/abuse: Update doinst.sh.
games/assaultcube-reloaded: Update doinst.sh.
games/assaultcube: Update doinst.sh.
games/atanks: Update doinst.sh.
games/barrage: Update doinst.sh.
games/cgmadness: Update doinst.sh.
games/chromium-bsu: Update doinst.sh.
games/commandergenius: Update doinst.sh.
games/connectagram: Update doinst.sh.
games/crimson: Update doinst.sh.
games/cutemaze: Update doinst.sh.
games/cuyo: Update doinst.sh.
games/dolphin-emu: Update doinst.sh.
games/doomretro: Update doinst.sh.
games/doomretro: Updated for version 2.3.8.
games/dopewars: Update doinst.sh.
games/dustrac: Update doinst.sh.
games/edgar: Update doinst.sh.
games/ember: Update doinst.sh.
games/eureka: Update doinst.sh.
games/exult: Update doinst.sh.
games/f1spirit: Update doinst.sh.
games/fgo: Update doinst.sh.
games/fifengine: Update doinst.sh.
games/flare-game: Update doinst.sh.
games/flare: Update doinst.sh.
games/foobillardplus: Update doinst.sh.
games/freeblocks: Update doinst.sh.
games/freeciv: Update doinst.sh.
games/freeminer: Update doinst.sh.
games/freeorion: Update doinst.sh.
games/frozen-bubble: Update doinst.sh.
games/fuse-emulator: Update doinst.sh.
games/galaxyv2: Update doinst.sh.
games/garden: Update doinst.sh.
games/gbrainy: Update doinst.sh.
games/gemrb: Update doinst.sh.
games/gnonograms: Update doinst.sh.
games/gnubg: Update doinst.sh.
games/golly: Update doinst.sh.
games/gottet: Update doinst.sh.
games/gzdoom: Update doinst.sh.
games/hatari: Update doinst.sh.
games/hexalate: Update doinst.sh.
games/hlsdk: Added (Half Life 1 SDK).
games/jag: Update doinst.sh.
games/kildclient: Update doinst.sh.
games/knights: Update doinst.sh.
games/m64py: Update doinst.sh.
games/mars: Update doinst.sh.
games/meandmyshadow: Update doinst.sh.
games/minetest: Update doinst.sh.
games/monkey-bubble: Update doinst.sh.
games/nSnake: Update doinst.sh.
games/neverball: Update doinst.sh.
games/nexuiz: Update doinst.sh.
games/nuvie: Update doinst.sh.
games/o2em: Update doinst.sh.
games/openclonk: Update doinst.sh.
games/opendune: Update doinst.sh.
games/openspades: Update doinst.sh.
games/openttd: Update doinst.sh.
games/ostrichriders: Update doinst.sh.
games/peg-e: Update doinst.sh.
games/pentagram: Update doinst.sh.
games/pioneer: Update doinst.sh.
games/ppsspp: Update doinst.sh.
games/pychess: Update doinst.sh.
games/pysolfc: Update doinst.sh.
games/qtsixa: Update doinst.sh.
games/redeclipse: Update doinst.sh.
games/roccat-tools: Update doinst.sh.
games/rocksndiamonds: Update doinst.sh.
games/rott: Update doinst.sh.
games/scid_vs_pc: Update doinst.sh.
games/simsu: Update doinst.sh.
games/snes9x: Update doinst.sh.
games/solarus-quest-editor: Update doinst.sh.
games/starfighter: Update doinst.sh.
games/stella: Update doinst.sh.
games/sumwars: Update doinst.sh.
games/tanglet: Update doinst.sh.
games/trackballs: Update doinst.sh.
games/trigger-rally: Update doinst.sh.
games/ufoai: Update doinst.sh.
games/unknown-horizons: Update doinst.sh.
games/vbam: Update doinst.sh.
games/vcmi: Update doinst.sh.
games/voxelands: Update doinst.sh.
games/wesnoth: Fix whitespace.
games/wordwarvi: Update doinst.sh.
games/worldofgoo: Update doinst.sh.
games/worldofpadman: Update doinst.sh.
games/xye: Update doinst.sh.
games/zelda-roth-se: Update doinst.sh.
games/zoom: Update doinst.sh.
games/zork: Update doinst.sh.
games/zsdx: Update doinst.sh.
games/zsxd: Update doinst.sh.
gis/google-earth: Update doinst.sh.
gis/merkaartor: Update doinst.sh.
gis/navit: Update doinst.sh.
gis/opencpn: Update doinst.sh.
gis/openorienteering-mapper: Update doinst.sh.
gis/qgis: Update doinst.sh.
gis/viking: Update doinst.sh.
graphics/Alchemy: Update doinst.sh.
graphics/Blender: Update doinst.sh.
graphics/blender: Update doinst.sh.
graphics/darktable: Update doinst.sh.
graphics/dia: Update doinst.sh.
graphics/digikam: Update doinst.sh.
graphics/draftsight: Update doinst.sh.
graphics/fbpic: Update doinst.sh.
graphics/flpsed: Update doinst.sh.
graphics/fontforge: Update doinst.sh.
graphics/fontmatrix: Update doinst.sh.
graphics/frescobaldi: Update doinst.sh.
graphics/gimagereader: Update doinst.sh.
graphics/gpscorrelate: Update doinst.sh.
graphics/gthumb: Update doinst.sh.
graphics/gtkam: Update doinst.sh.
graphics/hugin: Update doinst.sh.
graphics/inkscape: Update doinst.sh.
graphics/kphotoalbum: Update doinst.sh.
graphics/kuickshow: Update doinst.sh.
graphics/lcdtest: Update doinst.sh.
graphics/leocad: Update doinst.sh.
graphics/luminance-hdr: Update doinst.sh.
graphics/luxrender: Update doinst.sh.
graphics/makehuman: Update doinst.sh.
graphics/mcomix: Update doinst.sh.
graphics/mypaint: Update doinst.sh.
graphics/paraview: Update doinst.sh.
graphics/photivo: Update doinst.sh.
graphics/photoprint: Update doinst.sh.
graphics/photoqt: Update doinst.sh.
graphics/pinta: Update doinst.sh.
graphics/qcad: Update doinst.sh.
graphics/rawtherapee: Update doinst.sh.
graphics/ristretto: Update doinst.sh.
graphics/scantailor: Update doinst.sh.
graphics/shotwell: Update doinst.sh.
graphics/shutter: Update DEP.
graphics/shutter: Update doinst.sh.
graphics/simple-scan: Update doinst.sh.
graphics/teighafileconverter: Update doinst.sh.
graphics/teighaviewer: Update doinst.sh.
graphics/tuxpaint: Update doinst.sh.
graphics/viewnior: Update doinst.sh.
graphics/yagf: Update doinst.sh.
graphics/yed: Update doinst.sh.
ham/gqrx: Update doinst.sh.
libraries/Botan: Updated for version 2.0.0.
libraries/bwidget: Update doinst.sh.
libraries/capnproto: Added (Cap'n Proto serialization/RPC system).
libraries/cracklib: Fix cracklib-check.
libraries/jreen: Updated for version 1.3.0.
libraries/libffado: Update doinst.sh.
libraries/libftdi1: Update doinst.sh.
libraries/libgda: Update doinst.sh.
libraries/libinfinity: Update doinst.sh.
libraries/libinstpatch: Update doinst.sh.
libraries/libpeas: Update doinst.sh.
libraries/librep: Update doinst.sh.
libraries/qt5-webkit: Update doinst.sh.
libraries/qt5: Update doinst.sh.
libraries/rep-gtk: Update doinst.sh.
libraries/wxPython3: Update doinst.sh.
libraries/wxPython: Update doinst.sh.
libraries/xmlsec: Fix NSPR path + enable AES.
misc/KeePass: Update doinst.sh.
misc/QCMA: Update doinst.sh.
misc/ardesia: Update doinst.sh.
misc/asterixInspector: Update doinst.sh.
misc/boncuk: Update doinst.sh.
misc/brewtarget: Update doinst.sh.
misc/chemical-mime-data: Update doinst.sh.
misc/curtain: Update doinst.sh.
misc/fcitx: Update doinst.sh.
misc/glogg: Update doinst.sh.
misc/gxmessage: Update doinst.sh.
misc/ibus-skk: Update doinst.sh.
misc/ibus: Update doinst.sh.
misc/krename: Update doinst.sh.
misc/kronometer: Update doinst.sh.
misc/nfoview: Update doinst.sh.
misc/nvclock: Update doinst.sh.
misc/qtkeychain: Noted the optional dependency qt5.
misc/rlwrap: Updated for version 0.42 + new maintainer.
misc/rsibreak: Update doinst.sh.
misc/seahorse-plugins: Update doinst.sh.
misc/spotlighter: Update doinst.sh.
misc/subsurface: Update doinst.sh.
misc/yubikey-personalization-gui: Update doinst.sh.
multimedia/ExMplayer: Update doinst.sh.
multimedia/HandBrake: Update doinst.sh.
multimedia/OpenPHT: Update doinst.sh.
multimedia/SimpleSysexxer: Update doinst.sh.
multimedia/acetoneiso: Update doinst.sh.
multimedia/aegisub: Update doinst.sh.
multimedia/avidemux: Update doinst.sh.
multimedia/bombono-dvd: Update doinst.sh.
multimedia/coriander: Update doinst.sh.
multimedia/cowbell: Update doinst.sh.
multimedia/dvdrip: Update doinst.sh.
multimedia/ffmpegyag: Update doinst.sh.
multimedia/flashplayer-plugin: Update doinst.sh.
multimedia/flowblade: Update doinst.sh.
multimedia/gaupol: Update doinst.sh.
multimedia/gnash: Update doinst.sh.
multimedia/gnome-mplayer: Update doinst.sh.
multimedia/gpodder: Update doinst.sh.
multimedia/gst-plugins-bad: Added -std=c++11 to CXXFLAGS
multimedia/gtick: Update doinst.sh.
multimedia/gtkpod: Update doinst.sh.
multimedia/imagination: Update doinst.sh.
multimedia/kaffeine: Update doinst.sh.
multimedia/kdenlive: Update doinst.sh.
multimedia/kodi: Update doinst.sh.
multimedia/lightspark: Update doinst.sh.
multimedia/lives: Update doinst.sh.
multimedia/makemkv: Update doinst.sh.
multimedia/minitube: Update doinst.sh.
multimedia/miro: Update doinst.sh.
multimedia/mkclean: Update doinst.sh.
multimedia/mkvtoolnix: Update doinst.sh.
multimedia/mpv: Update doinst.sh.
multimedia/musique: Update doinst.sh.
multimedia/parole: Update doinst.sh.
multimedia/picard: Update doinst.sh.
multimedia/plex-home-theater: Update doinst.sh.
multimedia/qsampler: Update doinst.sh.
multimedia/radiotray: Update doinst.sh.
multimedia/rosa-media-player: Update doinst.sh.
multimedia/shotcut: Update doinst.sh.
multimedia/smplayer: Update doinst.sh.
multimedia/smtube: Update doinst.sh.
multimedia/subtitlecomposer: Update doinst.sh.
multimedia/subtitleeditor: Update doinst.sh.
multimedia/tomahawk: Switch to i586 + Qt5 fix.
multimedia/tomahawk: Update doinst.sh.
multimedia/totem: Update doinst.sh.
multimedia/tovid: Update doinst.sh.
multimedia/tvtime: Update doinst.sh.
multimedia/ucview: Update doinst.sh.
multimedia/umplayer: Update doinst.sh.
multimedia/videocut: Update doinst.sh.
multimedia/yarock: Update doinst.sh.
network/NetworkManager-vpnc: Update doinst.sh.
network/PaleMoon: Update doinst.sh.
network/QuiteRSS: Update doinst.sh.
network/arora: Update doinst.sh.
network/c-toxcore: Updated for version 0.1.3.
network/choqok: Update doinst.sh.
network/claws-mail: Update doinst.sh.
network/clipgrab: Update doinst.sh.
network/corebird: Update doinst.sh.
network/deluge: Update doinst.sh.
network/dianara: Update doinst.sh.
network/dropbox: Update doinst.sh.
network/ekiga: Update doinst.sh.
network/emesene: Update doinst.sh.
network/filezilla: Update doinst.sh.
network/freerapid: Update doinst.sh.
network/fwbuilder: Update doinst.sh.
network/gajim: Update doinst.sh.
network/gq: Update doinst.sh.
network/grsync: Update doinst.sh.
network/httrack: Update doinst.sh.
network/icecat: Update doinst.sh.
network/insync: Update doinst.sh.
network/ipscan: Update doinst.sh.
network/kadu: Update doinst.sh.
network/kfilebox: Update doinst.sh.
network/kmess: Update doinst.sh.
network/knemo: Update doinst.sh.
network/konversation: Update doinst.sh.
network/kvirc: Update doinst.sh.
network/leechcraft: Update doinst.sh.
network/liferea: Update doinst.sh.
network/linuxdcpp: Update doinst.sh.
network/loiq: Update doinst.sh.
network/luakit: Update doinst.sh.
network/megasync: Update doinst.sh.
network/midori: Update doinst.sh.
network/opera-developer: Update doinst.sh.
network/opera-legacy: Update doinst.sh.
network/opera: Update doinst.sh.
network/owncloud-client: Update doinst.sh.
network/psi: Update doinst.sh.
network/pyNeighborhood: Update doinst.sh.
network/pydio-sync: Update doinst.sh.
network/qTox: Update doinst.sh.
network/qTox: Updated for version 1.7.1.
network/qbittorrent: Update doinst.sh.
network/quassel: Update doinst.sh.
network/qupzilla: Update doinst.sh.
network/rekonq: Update doinst.sh.
network/remmina: Update doinst.sh.
network/roger-router: Update doinst.sh.
network/smb4k: Update doinst.sh.
network/social-engineer-toolkit: Update doinst.sh.
network/sopcast-player: Update doinst.sh.
network/synergy: Update doinst.sh.
network/transmission-remote-gtk: Update doinst.sh.
network/transmission: Update doinst.sh.
network/trojita: Update doinst.sh.
network/uTox: Update doinst.sh.
network/uget: Update doinst.sh.
network/viber: Update doinst.sh.
network/vidalia: Update doinst.sh.
network/vivaldi: Update doinst.sh.
network/vpnc: Fixed a typo in the shell script.
network/weboob: Update doinst.sh.
network/wifi-radar: Update doinst.sh.
network/wireshark: Update doinst.sh.
network/wuala: Update doinst.sh.
network/xdman: Update doinst.sh.
network/xombrero: Update doinst.sh.
office/CherryTree: Update doinst.sh.
office/JabRef: Update doinst.sh.
office/LibreOffice: Update doinst.sh.
office/LibreOffice: Updated for version 5.2.4.2
office/abiword: Update doinst.sh.
office/alot: Updated for version 0.4.
office/beaver: Update doinst.sh.
office/briss: Update doinst.sh.
office/broffice.org: Update doinst.sh.
office/calibre: Update doinst.sh.
office/diffpdf: Update doinst.sh.
office/epdfview: Update doinst.sh.
office/eqonomize: Update doinst.sh.
office/evince: Update doinst.sh.
office/flowkeeper: Update doinst.sh.
office/focuswriter: Update doinst.sh.
office/gnucash: Update doinst.sh.
office/gnumeric: Update doinst.sh.
office/grisbi: Update doinst.sh.
office/hamster: Update doinst.sh.
office/homebank: Update doinst.sh.
office/htmldoc: Update doinst.sh.
office/kbgoffice: Update doinst.sh.
office/kbibtex: Update doinst.sh.
office/keepnote: Update doinst.sh.
office/kmymoney: Update doinst.sh.
office/leafpad: Update doinst.sh.
office/libreoffice: Update doinst.sh.
office/lyx: Update doinst.sh.
office/myrulib: Update doinst.sh.
office/mytetra: Update doinst.sh.
office/notmuch: Updated for version 0.23.4.
office/openoffice.org: Update doinst.sh.
office/osmo: Update doinst.sh.
office/pdfchain: Update doinst.sh.
office/qpdfview: Update doinst.sh.
office/rednotebook: Update doinst.sh.
office/referencer: Update doinst.sh.
office/scribus: Update doinst.sh.
office/sigil: Update doinst.sh.
office/tellico: Update doinst.sh.
office/texmacs: Update doinst.sh.
office/texmaker: Update doinst.sh.
office/texstudio: Update doinst.sh.
office/treesheets: Update doinst.sh.
office/wps-office: Update doinst.sh.
office/xournal: Update doinst.sh.
office/xpad: Update doinst.sh.
python/click: Updated for version 6.7.
python/python3: Fix incorrect permissions.
python/stem: Updated for version 1.5.4.
ruby/sequel: Updated for version 4.42.0.
ruby/sqlite3: Updated for version 1.3.13.
system/barman: Updated for version 2.1.
system/brasero: Update doinst.sh.
system/cool-retro-term: Update doinst.sh.
system/cutecom: Update doinst.sh.
system/d-feet: Update doinst.sh.
system/ddrescue-gui: Update doinst.sh.
system/disk-manager: Update doinst.sh.
system/eaglemode: Updated for version 0.92.0.
system/emelfm2: Update doinst.sh.
system/evilvte: Update doinst.sh.
system/file-roller: Update doinst.sh.
system/firejail: Updated for version 0.9.44.4.
system/foomatic-db: Updated for version 20170108.
system/fpm2: Update doinst.sh.
system/fs-uae-arcade: Update doinst.sh.
system/fs-uae-launcher: Update doinst.sh.
system/fs-uae: Update doinst.sh.
system/fsviewer: Update doinst.sh.
system/gconf-editor: Update doinst.sh.
system/gencfs: Update doinst.sh.
system/gentoo: Update doinst.sh.
system/gnome-disk-utility: Update doinst.sh.
system/gnome-terminal: Update doinst.sh.
system/gsmartcontrol: Update doinst.sh.
system/hebe: Update doinst.sh.
system/jdiskreport: Update doinst.sh.
system/komparator4: Update doinst.sh.
system/krusader: Update doinst.sh.
system/kvpm: Update doinst.sh.
system/lshw: Update doinst.sh.
system/lxterminal: Update doinst.sh.
system/mbootpack: Some fixes.
system/mlterm: Updated for version 3.8.0.
system/nvidia-driver: Updated for version 375.26.
system/nvidia-kernel: Updated for version 375.26.
system/p7zip: Update doinst.sh.
system/packagekit: Update doinst.sh.
system/passwordsafe: Updated for version 1.01BETA.
system/phoronix-test-suite: Update doinst.sh.
system/roxterm: Update doinst.sh.
system/scanmem: Update doinst.sh.
system/seahorse: Update doinst.sh.
system/simpleburn: Update doinst.sh.
system/spacefm: Update doinst.sh.
system/terminator: Update doinst.sh.
system/terminix: Update doinst.sh.
system/terminology: Update doinst.sh.
system/testdisk: Update doinst.sh.
system/tracker: Update doinst.sh.
system/udiskie: Update doinst.sh.
system/unetbootin: Update doinst.sh.
system/veracrypt: Update doinst.sh.
system/vifm: Update doinst.sh.
system/virt-manager: Update doinst.sh.
system/virt-viewer: Update doinst.sh.
system/virtualbox: Update doinst.sh.
system/webmin: Updated for version 1.831.
system/xarchiver: Update doinst.sh.
system/xen: Updated for version 4.8.0.
system/xfburn: Update doinst.sh.
system/yakuake: Update doinst.sh.
system/yelp: Update doinst.sh.
system/zeroinstall-injector: Update doinst.sh.
system/zuluCrypt: Update doinst.sh.

-------------- 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/20170109/01bba52c/attachment-0001.asc>

From glenn.becker at gmail.com  Tue Jan 10 00:43:42 2017
From: glenn.becker at gmail.com (Glenn Becker)
Date: Mon, 9 Jan 2017 19:43:42 -0500
Subject: [Slackbuilds-users] giving up my builds
Message-ID: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>

Hi Folks,

I've thought about this for a while. I plan to stick with Slackware, but I
just have never been much of a build maintainer -- much as I like the
feeling of being a contributor, someone more skilled could contribute so
much more than I am able to, so I am orphaning the following. Thanks for
letting me be a part of this.

Glenn
========

desktop/wmii
desktop/ratpoison

network/surfraw

perl/perl-gnome2-vfs
perl/perl-Test-Number-Delta
perl/perl-gtk2
perl/perl-IO-HTML
perl/perl-gtk2-imageview
perl/perl-x11-protocol
perl/perl-Convert-UU
perl/perl-html-form
perl/perl-http-server-simple
perl/perl-PerlIO-Layers
perl/perl-Astro-SunTime
perl/perl-goo-canvas
perl/perl-X10
perl/perl-Inline
perl/perl-IO-All
perl/perl-Sub-Exporter-Progressive
perl/perl-extutils-pkgconfig
perl/perl-glib
perl/perl-gnome2-gconf
perl/perl-gnome2-canvas
perl/perl-MusicBrainz-DiscID
perl/perl-Sys-Mmap
perl/perl-net-dbus
perl/perl-Inline-C
perl/perl-MIME-Lite
perl/perl-File-ShareDir-Install
perl/perl-gnome2-wnck
perl/perl-YAML-LibYAML
perl/perl-http-response-encoding
perl/perl-File-Copy-Recursive
perl/perl-test-warn
perl/perl-gnome2
perl/perl-pango
perl/perl-cairo
perl/perl-Pegex
perl/perl-Device-SerialPort
perl/perl-Email-Date-Format
perl/perl-extutils-depends
perl/perl-PHP-Serialization

games/golly

development/bsdiff
development/gprolog

audio/cd-discid
audio/abcde

libraries/jbigkit

academic/calc
academic/mendeleydesktop
academic/maxima

system/splix
system/lshw
system/rxvt-unicode



Glenn Becker

<http://projecteuler.net/profile/gbecker.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170109/8f605c10/attachment.html>

From ryanpcmcquen at member.fsf.org  Tue Jan 10 00:51:21 2017
From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen)
Date: Mon, 9 Jan 2017 16:51:21 -0800
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
Message-ID: <CAAcyf-rvyB81TVUk6CdQ8Mk2GbRfqJxdMEJHT_X7qfb2SJbUgQ@mail.gmail.com>

> I've thought about this for a while. I plan to stick with Slackware, but I
> just have never been much of a build maintainer -- much as I like the
> feeling of being a contributor, someone more skilled could contribute so
> much more than I am able to, so I am orphaning the following. Thanks for
> letting me be a part of this.

Sorry to hear that. I'll take these:

desktop/wmii
desktop/ratpoison
audio/cd-discid
audio/abcde

-- 
-Ryan
[ryanpcmcquen.org]


From thedoogster at gmail.com  Tue Jan 10 00:57:43 2017
From: thedoogster at gmail.com (Doogster)
Date: Mon, 9 Jan 2017 16:57:43 -0800
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
Message-ID: <CAE5oDaYsHRr4nwVEEK=VF=mXGgKnwYF2X-x6uWMhxaAQRm0uZw@mail.gmail.com>

Glad to see you're keeping Nethack

On Mon, Jan 9, 2017 at 4:43 PM, Glenn Becker <glenn.becker at gmail.com> wrote:

> Hi Folks,
>
> I've thought about this for a while. I plan to stick with Slackware, but I
> just have never been much of a build maintainer -- much as I like the
> feeling of being a contributor, someone more skilled could contribute so
> much more than I am able to, so I am orphaning the following. Thanks for
> letting me be a part of this.
>
> Glenn
> ========
>
> desktop/wmii
> desktop/ratpoison
>
> network/surfraw
>
> perl/perl-gnome2-vfs
> perl/perl-Test-Number-Delta
> perl/perl-gtk2
> perl/perl-IO-HTML
> perl/perl-gtk2-imageview
> perl/perl-x11-protocol
> perl/perl-Convert-UU
> perl/perl-html-form
> perl/perl-http-server-simple
> perl/perl-PerlIO-Layers
> perl/perl-Astro-SunTime
> perl/perl-goo-canvas
> perl/perl-X10
> perl/perl-Inline
> perl/perl-IO-All
> perl/perl-Sub-Exporter-Progressive
> perl/perl-extutils-pkgconfig
> perl/perl-glib
> perl/perl-gnome2-gconf
> perl/perl-gnome2-canvas
> perl/perl-MusicBrainz-DiscID
> perl/perl-Sys-Mmap
> perl/perl-net-dbus
> perl/perl-Inline-C
> perl/perl-MIME-Lite
> perl/perl-File-ShareDir-Install
> perl/perl-gnome2-wnck
> perl/perl-YAML-LibYAML
> perl/perl-http-response-encoding
> perl/perl-File-Copy-Recursive
> perl/perl-test-warn
> perl/perl-gnome2
> perl/perl-pango
> perl/perl-cairo
> perl/perl-Pegex
> perl/perl-Device-SerialPort
> perl/perl-Email-Date-Format
> perl/perl-extutils-depends
> perl/perl-PHP-Serialization
>
> games/golly
>
> development/bsdiff
> development/gprolog
>
> audio/cd-discid
> audio/abcde
>
> libraries/jbigkit
>
> academic/calc
> academic/mendeleydesktop
> academic/maxima
>
> system/splix
> system/lshw
> system/rxvt-unicode
>
>
>
> Glenn Becker
>
> <http://projecteuler.net/profile/gbecker.png>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170109/9b5b9e5c/attachment.html>

From idlemoor at slackbuilds.org  Tue Jan 10 00:59:07 2017
From: idlemoor at slackbuilds.org (David Spencer)
Date: Tue, 10 Jan 2017 00:59:07 +0000
Subject: [Slackbuilds-users] Updates - 20170110.1
Message-ID: <7145aea9-99bc-53f9-6cf0-112ab1a4733a@slackbuilds.org>

Here's the nvidia cleanup I promised earlier, plus one random removal
from Andr?.

Hopefully we'll be back to the normal updates on Friday :)

Tue Jan 10 00:31:14 UTC 2017
development/visual-studio-code: Removed (replaced by vscode).
system/nvidia-driver: Revert commit 7ff6d19.
system/nvidia-kernel: Revert commit c30c401.
+--------------------------+

-------------- 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/20170110/879e86c0/attachment.asc>

From glenn.becker at gmail.com  Tue Jan 10 01:29:33 2017
From: glenn.becker at gmail.com (Glenn Becker)
Date: Mon, 9 Jan 2017 20:29:33 -0500
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CAE5oDaYsHRr4nwVEEK=VF=mXGgKnwYF2X-x6uWMhxaAQRm0uZw@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
 <CAE5oDaYsHRr4nwVEEK=VF=mXGgKnwYF2X-x6uWMhxaAQRm0uZw@mail.gmail.com>
Message-ID: <CANCo2a1qYd+JDAuEG0EJqgacYaLD8=KN1ZYrUFQXC7xPVm136Q@mail.gmail.com>

I didn't intend to keep anything. :(

<http://projecteuler.net/profile/gbecker.png>

On Mon, Jan 9, 2017 at 7:57 PM, Doogster <thedoogster at gmail.com> wrote:

> Glad to see you're keeping Nethack
>
> On Mon, Jan 9, 2017 at 4:43 PM, Glenn Becker <glenn.becker at gmail.com>
> wrote:
>
>> Hi Folks,
>>
>> I've thought about this for a while. I plan to stick with Slackware, but
>> I just have never been much of a build maintainer -- much as I like the
>> feeling of being a contributor, someone more skilled could contribute so
>> much more than I am able to, so I am orphaning the following. Thanks for
>> letting me be a part of this.
>>
>> Glenn
>> ========
>>
>> desktop/wmii
>> desktop/ratpoison
>>
>> network/surfraw
>>
>> perl/perl-gnome2-vfs
>> perl/perl-Test-Number-Delta
>> perl/perl-gtk2
>> perl/perl-IO-HTML
>> perl/perl-gtk2-imageview
>> perl/perl-x11-protocol
>> perl/perl-Convert-UU
>> perl/perl-html-form
>> perl/perl-http-server-simple
>> perl/perl-PerlIO-Layers
>> perl/perl-Astro-SunTime
>> perl/perl-goo-canvas
>> perl/perl-X10
>> perl/perl-Inline
>> perl/perl-IO-All
>> perl/perl-Sub-Exporter-Progressive
>> perl/perl-extutils-pkgconfig
>> perl/perl-glib
>> perl/perl-gnome2-gconf
>> perl/perl-gnome2-canvas
>> perl/perl-MusicBrainz-DiscID
>> perl/perl-Sys-Mmap
>> perl/perl-net-dbus
>> perl/perl-Inline-C
>> perl/perl-MIME-Lite
>> perl/perl-File-ShareDir-Install
>> perl/perl-gnome2-wnck
>> perl/perl-YAML-LibYAML
>> perl/perl-http-response-encoding
>> perl/perl-File-Copy-Recursive
>> perl/perl-test-warn
>> perl/perl-gnome2
>> perl/perl-pango
>> perl/perl-cairo
>> perl/perl-Pegex
>> perl/perl-Device-SerialPort
>> perl/perl-Email-Date-Format
>> perl/perl-extutils-depends
>> perl/perl-PHP-Serialization
>>
>> games/golly
>>
>> development/bsdiff
>> development/gprolog
>>
>> audio/cd-discid
>> audio/abcde
>>
>> libraries/jbigkit
>>
>> academic/calc
>> academic/mendeleydesktop
>> academic/maxima
>>
>> system/splix
>> system/lshw
>> system/rxvt-unicode
>>
>>
>>
>> Glenn Becker
>>
>> <http://projecteuler.net/profile/gbecker.png>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://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
> http://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/20170109/fbf4517b/attachment-0001.html>

From thedoogster at gmail.com  Tue Jan 10 01:30:55 2017
From: thedoogster at gmail.com (Doogster)
Date: Mon, 9 Jan 2017 17:30:55 -0800
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CANCo2a1qYd+JDAuEG0EJqgacYaLD8=KN1ZYrUFQXC7xPVm136Q@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
 <CAE5oDaYsHRr4nwVEEK=VF=mXGgKnwYF2X-x6uWMhxaAQRm0uZw@mail.gmail.com>
 <CANCo2a1qYd+JDAuEG0EJqgacYaLD8=KN1ZYrUFQXC7xPVm136Q@mail.gmail.com>
Message-ID: <CAE5oDaZB4jtF-sTJRfGvkpT0RLMVnvGw-QMjW8TiSEtsOZbrOw@mail.gmail.com>

I'll only take Nethack back if no-one else steps up. Anyone?

On Mon, Jan 9, 2017 at 5:29 PM, Glenn Becker <glenn.becker at gmail.com> wrote:

> I didn't intend to keep anything. :(
>
> <http://projecteuler.net/profile/gbecker.png>
>
> On Mon, Jan 9, 2017 at 7:57 PM, Doogster <thedoogster at gmail.com> wrote:
>
>> Glad to see you're keeping Nethack
>>
>> On Mon, Jan 9, 2017 at 4:43 PM, Glenn Becker <glenn.becker at gmail.com>
>> wrote:
>>
>>> Hi Folks,
>>>
>>> I've thought about this for a while. I plan to stick with Slackware, but
>>> I just have never been much of a build maintainer -- much as I like the
>>> feeling of being a contributor, someone more skilled could contribute so
>>> much more than I am able to, so I am orphaning the following. Thanks for
>>> letting me be a part of this.
>>>
>>> Glenn
>>> ========
>>>
>>> desktop/wmii
>>> desktop/ratpoison
>>>
>>> network/surfraw
>>>
>>> perl/perl-gnome2-vfs
>>> perl/perl-Test-Number-Delta
>>> perl/perl-gtk2
>>> perl/perl-IO-HTML
>>> perl/perl-gtk2-imageview
>>> perl/perl-x11-protocol
>>> perl/perl-Convert-UU
>>> perl/perl-html-form
>>> perl/perl-http-server-simple
>>> perl/perl-PerlIO-Layers
>>> perl/perl-Astro-SunTime
>>> perl/perl-goo-canvas
>>> perl/perl-X10
>>> perl/perl-Inline
>>> perl/perl-IO-All
>>> perl/perl-Sub-Exporter-Progressive
>>> perl/perl-extutils-pkgconfig
>>> perl/perl-glib
>>> perl/perl-gnome2-gconf
>>> perl/perl-gnome2-canvas
>>> perl/perl-MusicBrainz-DiscID
>>> perl/perl-Sys-Mmap
>>> perl/perl-net-dbus
>>> perl/perl-Inline-C
>>> perl/perl-MIME-Lite
>>> perl/perl-File-ShareDir-Install
>>> perl/perl-gnome2-wnck
>>> perl/perl-YAML-LibYAML
>>> perl/perl-http-response-encoding
>>> perl/perl-File-Copy-Recursive
>>> perl/perl-test-warn
>>> perl/perl-gnome2
>>> perl/perl-pango
>>> perl/perl-cairo
>>> perl/perl-Pegex
>>> perl/perl-Device-SerialPort
>>> perl/perl-Email-Date-Format
>>> perl/perl-extutils-depends
>>> perl/perl-PHP-Serialization
>>>
>>> games/golly
>>>
>>> development/bsdiff
>>> development/gprolog
>>>
>>> audio/cd-discid
>>> audio/abcde
>>>
>>> libraries/jbigkit
>>>
>>> academic/calc
>>> academic/mendeleydesktop
>>> academic/maxima
>>>
>>> system/splix
>>> system/lshw
>>> system/rxvt-unicode
>>>
>>>
>>>
>>> Glenn Becker
>>>
>>> <http://projecteuler.net/profile/gbecker.png>
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> http://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
>> http://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
> http://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/20170109/068a875a/attachment.html>

From andreas.guldstrand at gmail.com  Tue Jan 10 01:33:50 2017
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Tue, 10 Jan 2017 02:33:50 +0100
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CAE5oDaYsHRr4nwVEEK=VF=mXGgKnwYF2X-x6uWMhxaAQRm0uZw@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
 <CAE5oDaYsHRr4nwVEEK=VF=mXGgKnwYF2X-x6uWMhxaAQRm0uZw@mail.gmail.com>
Message-ID: <CAEQ5t82iVzCSUhrZPAGQm+z2U4pbgT_CrVEVNkDeBJsp-CcG1w@mail.gmail.com>

Wow, that's a lot of things that need taking up ... I'll be happy to take

perl/perl-Inline
perl/perl-Inline-C
perl/perl-File-ShareDir-Install
perl/perl-Pegex
perl/perl-IO-All
perl/perl-File-Copy-Recursive
perl/perl-YAML-LibYAML
perl/perl-test-warn

I could be persuaded to take a few more of the perl ones if nobody else
steps up.

On 10 January 2017 at 01:57, Doogster <thedoogster at gmail.com> wrote:

> Glad to see you're keeping Nethack
>
> On Mon, Jan 9, 2017 at 4:43 PM, Glenn Becker <glenn.becker at gmail.com>
> wrote:
>
>> Hi Folks,
>>
>> I've thought about this for a while. I plan to stick with Slackware, but
>> I just have never been much of a build maintainer -- much as I like the
>> feeling of being a contributor, someone more skilled could contribute so
>> much more than I am able to, so I am orphaning the following. Thanks for
>> letting me be a part of this.
>>
>> Glenn
>> ========
>>
>> desktop/wmii
>> desktop/ratpoison
>>
>> network/surfraw
>>
>> perl/perl-gnome2-vfs
>> perl/perl-Test-Number-Delta
>> perl/perl-gtk2
>> perl/perl-IO-HTML
>> perl/perl-gtk2-imageview
>> perl/perl-x11-protocol
>> perl/perl-Convert-UU
>> perl/perl-html-form
>> perl/perl-http-server-simple
>> perl/perl-PerlIO-Layers
>> perl/perl-Astro-SunTime
>> perl/perl-goo-canvas
>> perl/perl-X10
>> perl/perl-Inline
>> perl/perl-IO-All
>> perl/perl-Sub-Exporter-Progressive
>> perl/perl-extutils-pkgconfig
>> perl/perl-glib
>> perl/perl-gnome2-gconf
>> perl/perl-gnome2-canvas
>> perl/perl-MusicBrainz-DiscID
>> perl/perl-Sys-Mmap
>> perl/perl-net-dbus
>> perl/perl-Inline-C
>> perl/perl-MIME-Lite
>> perl/perl-File-ShareDir-Install
>> perl/perl-gnome2-wnck
>> perl/perl-YAML-LibYAML
>> perl/perl-http-response-encoding
>> perl/perl-File-Copy-Recursive
>> perl/perl-test-warn
>> perl/perl-gnome2
>> perl/perl-pango
>> perl/perl-cairo
>> perl/perl-Pegex
>> perl/perl-Device-SerialPort
>> perl/perl-Email-Date-Format
>> perl/perl-extutils-depends
>> perl/perl-PHP-Serialization
>>
>> games/golly
>>
>> development/bsdiff
>> development/gprolog
>>
>> audio/cd-discid
>> audio/abcde
>>
>> libraries/jbigkit
>>
>> academic/calc
>> academic/mendeleydesktop
>> academic/maxima
>>
>> system/splix
>> system/lshw
>> system/rxvt-unicode
>>
>>
>>
>> Glenn Becker
>>
>> <http://projecteuler.net/profile/gbecker.png>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://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
> http://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/20170110/9e3e29f4/attachment.html>

From atelszewski at gmail.com  Tue Jan 10 01:33:28 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 10 Jan 2017 02:33:28 +0100
Subject: [Slackbuilds-users] Possible updates to libvirt/QEMU stack
Message-ID: <1d4fc104-b99e-ad21-bf15-5cef1384eb93@gmail.com>

Hi,

There is no real reason behind, just killing the time.

I went through the virt-manager/libvirt/QEMU dependencies and updated 
those I found were not the latest versions.

After applying the updates, everything seems to work as usual (I'm using 
virt-manager/libvirt and QEMU for local virtual machines).

Most of the time, they are version bumps.
Here they go (diffs attached):

development/vala: updated for version 0.35.2.
libraries/libvirt: updated for version 2.5.0.
libraries/libvirt-glib: updated for version 1.0.0.
libraries/libvirt-python: updated for version 2.5.0.
libraries/vte3: updated for version 0.46.1, added pcre2 dependency, 
switch ARCH to i586.
network/phodav: updated for version 2.1.
python/pyparsing: updated for version 2.1.10.
python/python-requests: updated for version 2.12.4.
python/python-urllib3: updated for version 1.19.1, switch ARCH to i586.
system/qemu: updated for version 2.8.0, added BRIDGE_HELPER_SETUID option.

I'm not asking for official updates, but I won't stop you ;-)

-- 
Best regards,
Andrzej Telszewski
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vala.diff
Type: text/x-patch
Size: 1381 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0010.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python-urllib3.diff
Type: text/x-patch
Size: 1625 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0011.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python-requests.diff
Type: text/x-patch
Size: 1115 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0012.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pyparsing.diff
Type: text/x-patch
Size: 1080 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0013.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: phodav.diff
Type: text/x-patch
Size: 927 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0014.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vte3.diff
Type: text/x-patch
Size: 2451 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0015.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libvirt-python.diff
Type: text/x-patch
Size: 1077 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0016.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libvirt.diff
Type: text/x-patch
Size: 940 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0017.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libvirt-glib.diff
Type: text/x-patch
Size: 1083 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0018.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qemu.diff
Type: text/x-patch
Size: 2584 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/2758a564/attachment-0019.bin>

From jgraha8 at gmail.com  Tue Jan 10 02:19:53 2017
From: jgraha8 at gmail.com (Jason Graham)
Date: Mon, 9 Jan 2017 21:19:53 -0500
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CAEQ5t82iVzCSUhrZPAGQm+z2U4pbgT_CrVEVNkDeBJsp-CcG1w@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
 <CAE5oDaYsHRr4nwVEEK=VF=mXGgKnwYF2X-x6uWMhxaAQRm0uZw@mail.gmail.com>
 <CAEQ5t82iVzCSUhrZPAGQm+z2U4pbgT_CrVEVNkDeBJsp-CcG1w@mail.gmail.com>
Message-ID: <CALDF-3wHS31oRRk8Ub7PwhNdOi2Lc=OjayM+6eR3Axyj0Yu3Yg@mail.gmail.com>

I'm happy to pickup:

system/lshw
system/rxvt-unicode



On Mon, Jan 9, 2017 at 8:33 PM, Andreas Guldstrand <
andreas.guldstrand at gmail.com> wrote:

> Wow, that's a lot of things that need taking up ... I'll be happy to take
>
> perl/perl-Inline
> perl/perl-Inline-C
> perl/perl-File-ShareDir-Install
> perl/perl-Pegex
> perl/perl-IO-All
> perl/perl-File-Copy-Recursive
> perl/perl-YAML-LibYAML
> perl/perl-test-warn
>
> I could be persuaded to take a few more of the perl ones if nobody else
> steps up.
>
> On 10 January 2017 at 01:57, Doogster <thedoogster at gmail.com> wrote:
>
>> Glad to see you're keeping Nethack
>>
>> On Mon, Jan 9, 2017 at 4:43 PM, Glenn Becker <glenn.becker at gmail.com>
>> wrote:
>>
>>> Hi Folks,
>>>
>>> I've thought about this for a while. I plan to stick with Slackware, but
>>> I just have never been much of a build maintainer -- much as I like the
>>> feeling of being a contributor, someone more skilled could contribute so
>>> much more than I am able to, so I am orphaning the following. Thanks for
>>> letting me be a part of this.
>>>
>>> Glenn
>>> ========
>>>
>>> desktop/wmii
>>> desktop/ratpoison
>>>
>>> network/surfraw
>>>
>>> perl/perl-gnome2-vfs
>>> perl/perl-Test-Number-Delta
>>> perl/perl-gtk2
>>> perl/perl-IO-HTML
>>> perl/perl-gtk2-imageview
>>> perl/perl-x11-protocol
>>> perl/perl-Convert-UU
>>> perl/perl-html-form
>>> perl/perl-http-server-simple
>>> perl/perl-PerlIO-Layers
>>> perl/perl-Astro-SunTime
>>> perl/perl-goo-canvas
>>> perl/perl-X10
>>> perl/perl-Inline
>>> perl/perl-IO-All
>>> perl/perl-Sub-Exporter-Progressive
>>> perl/perl-extutils-pkgconfig
>>> perl/perl-glib
>>> perl/perl-gnome2-gconf
>>> perl/perl-gnome2-canvas
>>> perl/perl-MusicBrainz-DiscID
>>> perl/perl-Sys-Mmap
>>> perl/perl-net-dbus
>>> perl/perl-Inline-C
>>> perl/perl-MIME-Lite
>>> perl/perl-File-ShareDir-Install
>>> perl/perl-gnome2-wnck
>>> perl/perl-YAML-LibYAML
>>> perl/perl-http-response-encoding
>>> perl/perl-File-Copy-Recursive
>>> perl/perl-test-warn
>>> perl/perl-gnome2
>>> perl/perl-pango
>>> perl/perl-cairo
>>> perl/perl-Pegex
>>> perl/perl-Device-SerialPort
>>> perl/perl-Email-Date-Format
>>> perl/perl-extutils-depends
>>> perl/perl-PHP-Serialization
>>>
>>> games/golly
>>>
>>> development/bsdiff
>>> development/gprolog
>>>
>>> audio/cd-discid
>>> audio/abcde
>>>
>>> libraries/jbigkit
>>>
>>> academic/calc
>>> academic/mendeleydesktop
>>> academic/maxima
>>>
>>> system/splix
>>> system/lshw
>>> system/rxvt-unicode
>>>
>>>
>>>
>>> Glenn Becker
>>>
>>> <http://projecteuler.net/profile/gbecker.png>
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> http://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
>> http://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
> http://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/20170109/80bd978f/attachment.html>

From slack.dhabyx at gmail.com  Tue Jan 10 02:20:27 2017
From: slack.dhabyx at gmail.com (Dhaby Xiloj)
Date: Mon, 9 Jan 2017 20:20:27 -0600
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
Message-ID: <c1ecdeb2-844b-7ac8-3eb1-bd752dddd5ca@gmail.com>

I will take these packages:

>
> academic/calc
> academic/mendeleydesktop
> academic/maxima

-- 
Dhaby Xiloj


From read3valprintloop at gmail.com  Tue Jan 10 05:45:12 2017
From: read3valprintloop at gmail.com (PL RE)
Date: Tue, 10 Jan 2017 13:45:12 +0800
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 129, Issue 14
In-Reply-To: <mailman.1088.1483970536.1245.slackbuilds-users@slackbuilds.org>
References: <mailman.1088.1483970536.1245.slackbuilds-users@slackbuilds.org>
Message-ID: <CALF7xtkzU1zZc-uyZWb-OeAuu8KAdU1duPfKOB-kbvv5GKULcQ@mail.gmail.com>

Willy Sudiarto Raharjo,
It's indeed a runtime deps. I tried to uninstall SuperCollider,
yaml-cpp0.3, and recompile SuperCollider package. It succeeded. Sorry for
my mistake.

On Mon, Jan 9, 2017 at 10:02 PM, <slackbuilds-users-request at slackbuilds.org>
wrote:

> Send SlackBuilds-users mailing list submissions to
>         slackbuilds-users at slackbuilds.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> or, via email, send a message with subject or body 'help' to
>         slackbuilds-users-request at slackbuilds.org
>
> You can reach the person managing the list at
>         slackbuilds-users-owner at slackbuilds.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SlackBuilds-users digest..."
>
>
> Today's Topics:
>
>    1. doinst.sh template (Alexander Verbovetsky)
>    2. foomatic-db download url needs updating (Rohan Ferris)
>    3. Re: doinst.sh template (Robby Workman)
>    4. Re: foomatic-db download url needs updating (Robby Workman)
>    5. Re: foomatic-db download url needs updating (Robby Workman)
>    6. Updates in doinst.sh template (Willy Sudiarto Raharjo)
>    7. Re: Updates in doinst.sh template (Willy Sudiarto Raharjo)
>    8. Re: SuperCollider(3.6.6) on Slackware 14.2 depends on
>       yaml-cpp0.3 (Willy Sudiarto Raharjo)
>    9. youtube-dl doesn't work with python 3.6 (reedych)
>   10. Re: youtube-dl doesn't work with python 3.6
>       (Willy Sudiarto Raharjo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 09 Jan 2017 05:38:08 +0300
> From: Alexander Verbovetsky <alik at ejik.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: [Slackbuilds-users] doinst.sh template
> Message-ID:
>         <1483929488.3172602.841340705.6FEA3980 at webmail.messagingengine.com
> >
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> I noticed that sometimes after installation of a SlackBuild with
>
> if [ -e usr/share/icons/hicolor/icon-theme.cache ]; then
>   if [ -x /usr/bin/gtk-update-icon-cache ]; then
>     /usr/bin/gtk-update-icon-cache usr/share/icons/hicolor >/dev/null
>     2>&1
>   fi
> fi
>
> in doinst.sh the cache is not updated and therefore icons do not appear
> on the desktop.  But they do appear after additional reboot.  I guess
> that the reason is that in /etc/rc.d/rc.M the command
> gtk-update-icon-cache has the option "-f":
>
> --force, -f
>    Overwrite an existing cache file even if it appears to be uptodate.
>
> Wouldn't it be a good idea to add -f to doinst.sh:
>
> /usr/bin/gtk-update-icon-cache -f usr/share/icons/hicolor >/dev/null
> 2>&1
>
> Best regards,
> Alexander
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 9 Jan 2017 14:39:40 +1000
> From: Rohan Ferris <rferris at posteo.net>
> To: slackbuilds-users at slackbuilds.org
> Subject: [Slackbuilds-users] foomatic-db download url needs updating
> Message-ID: <274eaf18-6007-880e-3962-872af5f2941a at posteo.net>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi all!
>
> I just discovered that foomatic-db SlackBuild has stopped working due to
> the file being removed from the mirror. It has been updated with a newer
> version - 20170108. The two diffs below allowed it to compile, install
> and function without any further issue...
>
> # foomatic-db.SlackBuild
>
> diff --git a/system/foomatic-db/foomatic-db.SlackBuild
> b/system/foomatic-db/foomatic-db.SlackBuild
> index 8ecb121..d6c6dc5 100644
> --- a/system/foomatic-db/foomatic-db.SlackBuild
> +++ b/system/foomatic-db/foomatic-db.SlackBuild
> @@ -23,7 +23,7 @@
>   #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
>   PRGNAM=foomatic-db
> -VERSION=${VERSION:-20160724}
> +VERSION=${VERSION:-20170108}
>   BUILD=${BUILD:-1}
>   TAG=${TAG:-_SBo}
>
>
> # foomatic-db.info
>
> diff --git a/system/foomatic-db/foomatic-db.info
> b/system/foomatic-db/foomatic-db.info
>
> index 79595ca..076805c 100644
>
> --- a/system/foomatic-db/foomatic-db.info
>
> +++ b/system/foomatic-db/foomatic-db.info
>
> @@ -1,8 +1,8 @@
>
>   PRGNAM="foomatic-db"
>
>   VERSION="20160724"
>
>
> HOMEPAGE="http://www.linuxfoundation.org/collaborate/workgroups/
> openprinting/database/foomatic"
>
> -DOWNLOAD="http://www.openprinting.org/download/foomatic/foomatic-db-4.0-
> 20160724.tar.gz"
>
> -MD5SUM="5ba8f4d9717c3c362f633cd17a488488"
>
> +DOWNLOAD="http://www.openprinting.org/download/foomatic/foomatic-db-4.0-
> 20170108.tar.gz"
>
> +MD5SUM="9ba5c6f5b2962372069e2a955ffb1bcd"
>
>   DOWNLOAD_x86_64=""
>
>   MD5SUM_x86_64=""
>
>   REQUIRES=""
>
>
> Cheers,
>
> Rohan
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 8 Jan 2017 22:52:09 -0600
> From: Robby Workman <rworkman at slackbuilds.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] doinst.sh template
> Message-ID: <20170108225209.2ca85d8a at home.rlworkman.net>
> Content-Type: text/plain; charset="us-ascii"
>
> On Mon, 09 Jan 2017 05:38:08 +0300
> Alexander Verbovetsky <alik at ejik.org> wrote:
>
> > I noticed that sometimes after installation of a SlackBuild with
> >
> > if [ -e usr/share/icons/hicolor/icon-theme.cache ]; then
> >   if [ -x /usr/bin/gtk-update-icon-cache ]; then
> >     /usr/bin/gtk-update-icon-cache usr/share/icons/hicolor >/dev/null
> >     2>&1
> >   fi
> > fi
> >
> > in doinst.sh the cache is not updated and therefore icons do not
> > appear on the desktop.  But they do appear after additional reboot.
> > I guess that the reason is that in /etc/rc.d/rc.M the command
> > gtk-update-icon-cache has the option "-f":
> >
> > --force, -f
> >    Overwrite an existing cache file even if it appears to be uptodate.
> >
> > Wouldn't it be a good idea to add -f to doinst.sh:
> >
> > /usr/bin/gtk-update-icon-cache -f usr/share/icons/hicolor >/dev/null
> > 2>&1
>
>
> Agreed:
>
> commit 49cc824b72fbdc8c69b938e7c414b4f7a2341c81
> Author: Robby Workman <rworkman at slackware.com>
> Date:   Sun Jan 8 22:49:20 2017 -0600
>
>     doinst.sh: Add "-f" to icon theme update and note other themes
>
>     Thanks to Alexander Verbovetsky <alik at ejik.org> for the suggestion
>     about "gtk-update-icon-cache -f" to be consistent with what's done
>     in rc.M on boot:
>
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> 2017-January/017875.html
>
> Thanks!
>
> -RW
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 181 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> attachments/20170108/f1a96572/attachment-0001.asc>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 8 Jan 2017 22:59:38 -0600
> From: Robby Workman <rworkman at slackbuilds.org>
> To: Rohan Ferris <rferris at posteo.net>
> Cc: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] foomatic-db download url needs
>         updating
> Message-ID: <20170108225938.2f5762d0 at home.rlworkman.net>
> Content-Type: text/plain; charset="us-ascii"
>
> On Mon, 9 Jan 2017 14:39:40 +1000commit 2d4f7908b1f04e9d9330bcdc7a4272
> b79e4a87ea
> Author: Rohan Ferris <rferris at posteo.net>
> Date:   Sun Jan 8 22:58:38 2017 -0600
>
>     system/foomatic-db: Updated for version 20170108.
>
>     Signed-off-by: Robby Workman <rworkman at slackbuilds.org>
>
> Rohan Ferris <rferris at posteo.net> wrote:
>
> > Hi all!
> >
> > I just discovered that foomatic-db SlackBuild has stopped working due
> > to the file being removed from the mirror. It has been updated with a
> > newer version - 20170108. The two diffs below allowed it to compile,
> > install and function without any further issue...
>
>
> Done in my branch:
>
> commit 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea
> Author: Rohan Ferris <rferris at posteo.net>
> Date:   Sun Jan 8 22:58:38 2017 -0600
>
>     system/foomatic-db: Updated for version 20170108.
>
>     Signed-off-by: Robby Workman <rworkman at slackbuilds.org>
>
>
> Thanks!
>
> -RW
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 181 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> attachments/20170108/1e0b0e6a/attachment-0001.asc>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 8 Jan 2017 23:00:48 -0600
> From: Robby Workman <rworkman at slackbuilds.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] foomatic-db download url needs
>         updating
> Message-ID: <20170108230048.61c47cb0 at home.rlworkman.net>
> Content-Type: text/plain; charset="us-ascii"
>
> Wow. No idea how the paste fail happened.
>
> -RW
>
>
> On Sun, 8 Jan 2017 22:59:38 -0600
> Robby Workman <rworkman at slackbuilds.org> wrote:
>
> > On Mon, 9 Jan 2017 14:39:40 +1000commit
> > 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea Author: Rohan Ferris
> > <rferris at posteo.net> Date:   Sun Jan 8 22:58:38 2017 -0600
> >
> >     system/foomatic-db: Updated for version 20170108.
> >
> >     Signed-off-by: Robby Workman <rworkman at slackbuilds.org>
> >
> > Rohan Ferris <rferris at posteo.net> wrote:
> >
> > > Hi all!
> > >
> > > I just discovered that foomatic-db SlackBuild has stopped working
> > > due to the file being removed from the mirror. It has been updated
> > > with a newer version - 20170108. The two diffs below allowed it to
> > > compile, install and function without any further issue...
> >
> >
> > Done in my branch:
> >
> > commit 2d4f7908b1f04e9d9330bcdc7a4272b79e4a87ea
> > Author: Rohan Ferris <rferris at posteo.net>
> > Date:   Sun Jan 8 22:58:38 2017 -0600
> >
> >     system/foomatic-db: Updated for version 20170108.
> >
> >     Signed-off-by: Robby Workman <rworkman at slackbuilds.org>
> >
> >
> > Thanks!
> >
> > -RW
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 181 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> attachments/20170108/c47f07a4/attachment-0001.asc>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 9 Jan 2017 18:13:00 +0700
> From: Willy Sudiarto Raharjo <willysr at slackbuilds.org>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: [Slackbuilds-users] Updates in doinst.sh template
> Message-ID: <3aae54d6-d059-7898-90a8-e20a35b3fa78 at slackbuilds.org>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all,
>
> just to inform you that doinst.sh in templates have been updated with a
> minor update: to use -f in gtk-update-icon-cache code to force updating
> the icon cache instead of updating it in the next reboot.
>
> https://slackbuilds.org/cgit/templates/commit/?id=
> 49cc824b72fbdc8c69b938e7c414b4f7a2341c81
>
> We expect maintainers who have doinst.sh for their packages to update
> the code accordingly.
>
> thanks
>
>
> --
> Willy Sudiarto Raharjo
>
> -------------- 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/20170109/96337275/attachment-0001.asc>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 9 Jan 2017 20:29:08 +0700
> From: Willy Sudiarto Raharjo <willysr at slackbuilds.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] Updates in doinst.sh template
> Message-ID: <66c3219a-ed7d-d5fc-3839-99ba2fb0dab6 at slackbuilds.org>
> Content-Type: text/plain; charset="windows-1252"
>
> > just to inform you that doinst.sh in templates have been updated with a
> > minor update: to use -f in gtk-update-icon-cache code to force updating
> > the icon cache instead of updating it in the next reboot.
> >
> > https://slackbuilds.org/cgit/templates/commit/?id=
> 49cc824b72fbdc8c69b938e7c414b4f7a2341c81
> >
> > We expect maintainers who have doinst.sh for their packages to update
> > the code accordingly.
>
> I have ran a script to update all remaining doinst.sh in my branch so
> maintainer no need to change anything.
>
> If nothing goes wrong, i will push another public update with all those
> doinst.sh changes in couple hours
>
>
> --
> Willy Sudiarto Raharjo
>
> -------------- 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/20170109/9f3e0102/attachment-0001.asc>
>
> ------------------------------
>
> Message: 8
> Date: Mon, 9 Jan 2017 20:42:16 +0700
> From: Willy Sudiarto Raharjo <willysr at slackbuilds.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] SuperCollider(3.6.6) on Slackware
>         14.2 depends on yaml-cpp0.3
> Message-ID: <2a2b1051-ccfc-2a9d-b8e8-16bfecd9a030 at slackbuilds.org>
> Content-Type: text/plain; charset="windows-1252"
>
> > To build this package successfully. I have to install yaml-cpp0.3. Note
> > that yaml-cpp-0.5.3 will not work. Maybe this package should be added to
> > the README file of the Supercollider package.
>
> Is this a runtime deps?
> i can build this package without having to install yaml-cpp0.3 nor
> yaml-cpp-0.5.3
>
>
> --
> Willy Sudiarto Raharjo
>
> -------------- 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/20170109/d600d588/attachment-0001.asc>
>
> ------------------------------
>
> Message: 9
> Date: Mon, 9 Jan 2017 19:59:09 +0600
> From: reedych <reedych at reedych.pw>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: [Slackbuilds-users] youtube-dl doesn't work with python 3.6
> Message-ID: <20170109195909.09bb50c7 at slackware>
> Content-Type: text/plain; charset=US-ASCII
>
> After installing python 3.6 youtube-dl has been unstartable. Log of error:
> https://clck.ru/AT6dr.
>
>
> ------------------------------
>
> Message: 10
> Date: Mon, 9 Jan 2017 21:02:05 +0700
> From: Willy Sudiarto Raharjo <willysr at slackbuilds.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] youtube-dl doesn't work with python
>         3.6
> Message-ID: <da00593e-b49c-9254-fe66-a140f72149cf at slackbuilds.org>
> Content-Type: text/plain; charset="windows-1252"
>
> > After installing python 3.6 youtube-dl has been unstartable. Log of
> error: https://clck.ru/AT6dr.
>
> Did you upgrade to youtube-dl-2017.1.2 yet?
>
>
>
> --
> Willy Sudiarto Raharjo
>
> -------------- 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/20170109/10b294f7/attachment.asc>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>
> ------------------------------
>
> End of SlackBuilds-users Digest, Vol 129, Issue 14
> **************************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/176c48bc/attachment-0001.html>

From baildon.research at googlemail.com  Tue Jan 10 14:01:02 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Tue, 10 Jan 2017 14:01:02 +0000
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
Message-ID: <CAMt7G9R-a7T2-=cNBbzbaZzHqL-amno5q2mDAMWGovk85iXATw@mail.gmail.com>

On 10 January 2017 at 00:43, Glenn Becker <glenn.becker at gmail.com> wrote:
>
> Hi Folks,
>
> I've thought about this for a while. I plan to stick with Slackware, but I just have never been much of a build maintainer -- much as I like the feeling of being a contributor, someone more skilled could contribute so much more than I am able to, so I am orphaning the following. Thanks for letting me be a part of this.

Hey Glenn, thank *you* for being a good maintainer, and thanks for the
time and skills you have contributed. We are all volunteers, and
everybody probably feels like they could do more if they had better
skills and more time. But I guess we must be doing all right together,
because almost everything works almost all of the time ;)

Thanks again -- like everybody else on this mailing list, you're still
part of it!
-D.

From kristofru at gmail.com  Tue Jan 10 14:06:57 2017
From: kristofru at gmail.com (Chris Abela)
Date: Tue, 10 Jan 2017 15:06:57 +0100
Subject: [Slackbuilds-users] chromium
Message-ID: <CAJ2_kYr845=W4ygfXWXWyvjueYNroJXwswAc+O4WGpEd8b8UMA@mail.gmail.com>

I suspect that the python upgrade of the 28th December on Slackware 14.2
broke the chromium slackbuild:

patching file third_party/WebKit/Source/wtf/allocator/PageAllocator.cpp
Updating projects from gyp files...
Traceback (most recent call last):
  File "build/gyp_chromium", line 12, in <module>
    execfile(__file__ + '.py')
  File "build/gyp_chromium.py", line 366, in <module>
    sys.exit(main())
  File "build/gyp_chromium.py", line 353, in main
    gyp_rc = gyp.main(args)
  File "/tmp/SBo/chromium-53.0.2785.143/tools/gyp/pylib/gyp/__init__.py",
line 538, in main
    return gyp_main(args)
  File "/tmp/SBo/chromium-53.0.2785.143/tools/gyp/pylib/gyp/__init__.py",
line 514, in gyp_main
    options.duplicate_basename_check)
  File "/tmp/SBo/chromium-53.0.2785.143/tools/gyp/pylib/gyp/__init__.py",
line 130, in Load
    params['parallel'], params['root_targets'])
  File "/tmp/SBo/chromium-53.0.2785.143/tools/gyp/pylib/gyp/input.py", line
2774, in Load
    check, generator_input_info)
  File "/tmp/SBo/chromium-53.0.2785.143/tools/gyp/pylib/gyp/input.py", line
601, in LoadTargetBuildFilesParallel
    parallel_state.pool = multiprocessing.Pool(multiprocessing.cpu_count())
  File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 232, in Pool
    return Pool(processes, initializer, initargs, maxtasksperchild)
  File "/usr/lib64/python2.7/multiprocessing/pool.py", line 138, in __init__
    self._setup_queues()
  File "/usr/lib64/python2.7/multiprocessing/pool.py", line 233, in
_setup_queues
    from .queues import SimpleQueue
  File "/usr/lib64/python2.7/multiprocessing/queues.py", line 48, in
<module>
    from .synchronize import Lock, BoundedSemaphore, Semaphore, Condition
  File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 59, in
<module>
    " function, see issue 3770.")
ImportError: This platform lacks a functioning sem_open implementation,
therefore, the required synchronization primitives needed will not
function, see issue 3770.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170110/bcc8edb1/attachment.html>

From atelszewski at gmail.com  Tue Jan 10 14:25:09 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 10 Jan 2017 15:25:09 +0100
Subject: [Slackbuilds-users] qt5 fails to build
Message-ID: <91b5f4d7-63b9-c111-cd5d-685d91bc84cc@gmail.com>

Hi,

When trying to build qt5, it fails miserably ;-)

Could it be related to _Wed Dec 28 21:05:19 UTC 2016_ python-2.7.13 
update in Slackware?


using python: /usr/bin/python version: 2.7.13
Using extra options found in 
/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/core/qtwebengine_extras.gypi
Using extra options found in 
/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/core/qmake_extras.gypi
Using extra options found in 
/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/core/qtwebengine_extras.gypi
Using extra options found in 
/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/core/qmake_extras.gypi
Updating projects from gyp files...
Traceback (most recent call last):
   File 
"/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/tools/buildscripts/gyp_qtwebengine", 
line 178, in <module>
     sys.exit(gyp.main(args))
   File 
"/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py", 
line 538, in main
     return gyp_main(args)
   File 
"/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py", 
line 514, in gyp_main
     options.duplicate_basename_check)
   File 
"/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py", 
line 130, in Load
     params['parallel'], params['root_targets'])
   File 
"/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/input.py", 
line 2759, in Load
     check, generator_input_info)
   File 
"/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/input.py", 
line 596, in LoadTargetBuildFilesParallel
     parallel_state.pool = multiprocessing.Pool(multiprocessing.cpu_count())
   File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 232, in 
Pool
     return Pool(processes, initializer, initargs, maxtasksperchild)
   File "/usr/lib64/python2.7/multiprocessing/pool.py", line 138, in 
__init__
     self._setup_queues()
   File "/usr/lib64/python2.7/multiprocessing/pool.py", line 233, in 
_setup_queues
     from .queues import SimpleQueue
   File "/usr/lib64/python2.7/multiprocessing/queues.py", line 48, in 
<module>
     from .synchronize import Lock, BoundedSemaphore, Semaphore, Condition
   File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 59, 
in <module>
     " function, see issue 3770.")
ImportError: This platform lacks a functioning sem_open implementation, 
therefore, the required synchronization primitives needed will not 
function, see issue 3770.
Project ERROR: -- running gyp_qtwebengine failed --
Makefile:116: recipe for target 'sub-gyp_run-pro-make_first' failed
make[3]: *** [sub-gyp_run-pro-make_first] Error 3
make[3]: Leaving directory 
'/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/core'
Makefile:49: recipe for target 'sub-core-make_first' failed
make[2]: *** [sub-core-make_first] Error 2
make[2]: Leaving directory 
'/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine/src'
Makefile:44: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-src-make_first] Error 2
make[1]: Leaving directory 
'/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtwebengine'
Makefile:716: recipe for target 'module-qtwebengine-make_first' failed
make: *** [module-qtwebengine-make_first] Error 2
make: *** Waiting for unfinished jobs....


-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Tue Jan 10 15:49:58 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 10 Jan 2017 16:49:58 +0100
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <91b5f4d7-63b9-c111-cd5d-685d91bc84cc@gmail.com>
References: <91b5f4d7-63b9-c111-cd5d-685d91bc84cc@gmail.com>
Message-ID: <d59f4952-af9b-8aa6-a287-55872ca22a86@gmail.com>

On 10/01/17 15:25, Andrzej Telszewski wrote:
> Hi,
>
> When trying to build qt5, it fails miserably ;-)
>
> Could it be related to _Wed Dec 28 21:05:19 UTC 2016_ python-2.7.13
> update in Slackware?
>

This certainly looks like something is wrong with the Slackware's update.

Based on:
https://github.com/NixOS/nixpkgs/issues/10092

I reverted to Python 2.7.11 and:

$ python
Python 2.7.11 (default, Mar  3 2016, 13:35:30)
[GCC 5.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import multiprocessing
 >>> multiprocessing.RLock()
<RLock(None, 0)>
 >>>

Then I updated to Python 2.7.13 from _patches_ and:

$ python
Python 2.7.13 (default, Dec 28 2016, 13:46:09)
[GCC 5.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import multiprocessing
 >>> multiprocessing.RLock()
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 182, in 
RLock
     from multiprocessing.synchronize import RLock
   File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 59, 
in <module>
     " function, see issue 3770.")
ImportError: This platform lacks a functioning sem_open implementation, 
therefore, the required synchronization primitives needed will not 
function, see issue 3770.
 >>>


I then just rebuilt Python 2.7.13 from _patches_ and:

$ python
Python 2.7.13 (default, Jan 10 2017, 15:45:07)
[GCC 5.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import multiprocessing
 >>> multiprocessing.RLock()
<RLock(None, 0)>
 >>>


Somebody calls Pat?

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Tue Jan 10 15:58:36 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 10 Jan 2017 16:58:36 +0100
Subject: [Slackbuilds-users] chromium
In-Reply-To: <CAJ2_kYr845=W4ygfXWXWyvjueYNroJXwswAc+O4WGpEd8b8UMA@mail.gmail.com>
References: <CAJ2_kYr845=W4ygfXWXWyvjueYNroJXwswAc+O4WGpEd8b8UMA@mail.gmail.com>
Message-ID: <CAPsDuS6pYoWcjV2=gMVHiWA2UCpdKmAGmG6enUOeKS0kwx+KFA@mail.gmail.com>

2017-01-10 15:06 GMT+01:00 Chris Abela <kristofru at gmail.com>:
> I suspect that the python upgrade of the 28th December on Slackware 14.2
> broke the chromium slackbuild:

most probably, there are various reports

https://www.linuxquestions.org/questions/slackware-14/problem-building-qt5-4175596534/

just rebuild it from the SlackBuild in patches

http://slackware.osuosl.org/slackware-14.2/patches/source/python/

and everything should be fine.

Matteo

From atelszewski at gmail.com  Tue Jan 10 16:04:57 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 10 Jan 2017 17:04:57 +0100
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <d59f4952-af9b-8aa6-a287-55872ca22a86@gmail.com>
References: <91b5f4d7-63b9-c111-cd5d-685d91bc84cc@gmail.com>
 <d59f4952-af9b-8aa6-a287-55872ca22a86@gmail.com>
Message-ID: <a4ea3328-b7f9-4332-f8f3-1a5f370887fc@gmail.com>

On 10/01/17 16:49, Andrzej Telszewski wrote:
> On 10/01/17 15:25, Andrzej Telszewski wrote:
>> Hi,
>>
>> When trying to build qt5, it fails miserably ;-)
>>
>> Could it be related to _Wed Dec 28 21:05:19 UTC 2016_ python-2.7.13
>> update in Slackware?
>>
>
> This certainly looks like something is wrong with the Slackware's update.
>
> Based on:
> https://github.com/NixOS/nixpkgs/issues/10092
>
> I reverted to Python 2.7.11 and:
>
> $ python
> Python 2.7.11 (default, Mar  3 2016, 13:35:30)
> [GCC 5.3.0] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import multiprocessing
>>>> multiprocessing.RLock()
> <RLock(None, 0)>
>>>>
>
> Then I updated to Python 2.7.13 from _patches_ and:
>
> $ python
> Python 2.7.13 (default, Dec 28 2016, 13:46:09)
> [GCC 5.3.0] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import multiprocessing
>>>> multiprocessing.RLock()
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 182, in
> RLock
>     from multiprocessing.synchronize import RLock
>   File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 59,
> in <module>
>     " function, see issue 3770.")
> ImportError: This platform lacks a functioning sem_open implementation,
> therefore, the required synchronization primitives needed will not
> function, see issue 3770.
>>>>
>
>
> I then just rebuilt Python 2.7.13 from _patches_ and:
>
> $ python
> Python 2.7.13 (default, Jan 10 2017, 15:45:07)
> [GCC 5.3.0] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import multiprocessing
>>>> multiprocessing.RLock()
> <RLock(None, 0)>
>>>>
>
>
> Somebody calls Pat?
>

OK, it's confirmed ;-)

https://www.linuxquestions.org/questions/slackware-14/problem-building-qt5-4175596534/

-- 
Best regards,
Andrzej Telszewski

From glenn.becker at gmail.com  Tue Jan 10 16:25:55 2017
From: glenn.becker at gmail.com (Glenn Becker)
Date: Tue, 10 Jan 2017 11:25:55 -0500
Subject: [Slackbuilds-users] giving up my builds
In-Reply-To: <CAMt7G9R-a7T2-=cNBbzbaZzHqL-amno5q2mDAMWGovk85iXATw@mail.gmail.com>
References: <CANCo2a3y4Vzk6Wh9_wCUGsH3xmX--r69iGHa_bfFbhUZpA4yXw@mail.gmail.com>
 <CAMt7G9R-a7T2-=cNBbzbaZzHqL-amno5q2mDAMWGovk85iXATw@mail.gmail.com>
Message-ID: <CANCo2a1+9PoGWSkigUgQWz4yyii2jLoo40jZA6naUdWBh1ShtQ@mail.gmail.com>

Thanks, David - much appreciated.


<http://projecteuler.net/profile/gbecker.png>

On Tue, Jan 10, 2017 at 9:01 AM, David Spencer <
baildon.research at googlemail.com> wrote:

> On 10 January 2017 at 00:43, Glenn Becker <glenn.becker at gmail.com> wrote:
> >
> > Hi Folks,
> >
> > I've thought about this for a while. I plan to stick with Slackware, but
> I just have never been much of a build maintainer -- much as I like the
> feeling of being a contributor, someone more skilled could contribute so
> much more than I am able to, so I am orphaning the following. Thanks for
> letting me be a part of this.
>
> Hey Glenn, thank *you* for being a good maintainer, and thanks for the
> time and skills you have contributed. We are all volunteers, and
> everybody probably feels like they could do more if they had better
> skills and more time. But I guess we must be doing all right together,
> because almost everything works almost all of the time ;)
>
> Thanks again -- like everybody else on this mailing list, you're still
> part of it!
> -D.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170110/92b770b5/attachment.html>

From willysr at slackbuilds.org  Tue Jan 10 18:36:16 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 11 Jan 2017 01:36:16 +0700
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 129, Issue 14
In-Reply-To: <CALF7xtkzU1zZc-uyZWb-OeAuu8KAdU1duPfKOB-kbvv5GKULcQ@mail.gmail.com>
References: <mailman.1088.1483970536.1245.slackbuilds-users@slackbuilds.org>
 <CALF7xtkzU1zZc-uyZWb-OeAuu8KAdU1duPfKOB-kbvv5GKULcQ@mail.gmail.com>
Message-ID: <da08ac4e-2aa5-3887-d869-047a3aed462c@slackbuilds.org>

> It's indeed a runtime deps. I tried to uninstall SuperCollider,
> yaml-cpp0.3, and recompile SuperCollider package. It succeeded. Sorry for
> my mistake.

Thanks
Updated README and DEP in my branch


-- 
Willy Sudiarto Raharjo

-------------- 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/20170111/8acbd816/attachment.asc>

From aclemons at runbox.no  Tue Jan 10 19:18:03 2017
From: aclemons at runbox.no (Andrew Clemons)
Date: Wed, 11 Jan 2017 08:18:03 +1300
Subject: [Slackbuilds-users] eclipse-* slackbuilds
Message-ID: <20170110191802.GA31200@runbox.no>

I contacted Andr? about updates to the eclipse-* slackbuilds (there is
one major eclipse release per year, usually in June and then quarterly
updates until the next major release). He no longer wishes to maintain
them. Unless someone else is keen, I would like to take over
maintenance of these.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170111/9312f10a/attachment.asc>

From pfeifer.felix at gmail.com  Wed Jan 11 17:35:27 2017
From: pfeifer.felix at gmail.com (Felix Pfeifer)
Date: Wed, 11 Jan 2017 18:35:27 +0100
Subject: [Slackbuilds-users] SuperCollider(3.6.6) on Slackware 14.2
 depends on yaml-cpp0.3
In-Reply-To: <2a2b1051-ccfc-2a9d-b8e8-16bfecd9a030@slackbuilds.org>
References: <CALF7xt=pV==0hf+hWhG8Z29ywakpftoC=5EcPFrbiquZ9Dh7kQ@mail.gmail.com>
 <2a2b1051-ccfc-2a9d-b8e8-16bfecd9a030@slackbuilds.org>
Message-ID: <CAPANF74F5Q7_JqyLkEisx=qLnfX6T=rrOOQfbQyL78ek91zP2w@mail.gmail.com>

I think it is a runtime dep. I can build it on both
Slackware 32 Bit and 64 Bit. I am also aware
that the build does not run correctly on 32 Bit,
because of the newer compiler version. I just
had no idea how to fix this.


On 9 January 2017 at 14:42, Willy Sudiarto Raharjo
<willysr at slackbuilds.org> wrote:
>> To build this package successfully. I have to install yaml-cpp0.3. Note
>> that yaml-cpp-0.5.3 will not work. Maybe this package should be added to
>> the README file of the Supercollider package.
>
> Is this a runtime deps?
> i can build this package without having to install yaml-cpp0.3 nor
> yaml-cpp-0.5.3
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

From kristofru at gmail.com  Thu Jan 12 04:46:45 2017
From: kristofru at gmail.com (Chris Abela)
Date: Thu, 12 Jan 2017 05:46:45 +0100
Subject: [Slackbuilds-users] chromium
In-Reply-To: <CAPsDuS6pYoWcjV2=gMVHiWA2UCpdKmAGmG6enUOeKS0kwx+KFA@mail.gmail.com>
References: <CAJ2_kYr845=W4ygfXWXWyvjueYNroJXwswAc+O4WGpEd8b8UMA@mail.gmail.com>
 <CAPsDuS6pYoWcjV2=gMVHiWA2UCpdKmAGmG6enUOeKS0kwx+KFA@mail.gmail.com>
Message-ID: <CAJ2_kYpDrVeMQwLseyVwLpySPx5=xRDxBfYYQ-N2XUSHs4R7oA@mail.gmail.com>

I confirm that after building python from source, chromium builds fine.

On 10 Jan 2017 16:58, "Matteo Bernardini" <matteo.bernardini at gmail.com>
wrote:

> 2017-01-10 15:06 GMT+01:00 Chris Abela <kristofru at gmail.com>:
> > I suspect that the python upgrade of the 28th December on Slackware 14.2
> > broke the chromium slackbuild:
>
> most probably, there are various reports
>
> https://www.linuxquestions.org/questions/slackware-14/
> problem-building-qt5-4175596534/
>
> just rebuild it from the SlackBuild in patches
>
> http://slackware.osuosl.org/slackware-14.2/patches/source/python/
>
> and everything should be fine.
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170112/b3fc602a/attachment.html>

From am.marconi at gmx.com  Thu Jan 12 19:52:20 2017
From: am.marconi at gmx.com (Andrea Maria Marconi)
Date: Thu, 12 Jan 2017 20:52:20 +0100
Subject: [Slackbuilds-users] Problems building xephem (3.7.7)
Message-ID: <0ccc2fcc-cfc7-0e3f-d515-2f3aadfd16b2@gmx.com>

Hi all,

I have downloaded the xephem 3.7.7 package and it's build script,
unpacked  in the xephem dir (originally in the $HOME/andrea/Download dir
and then moved under /tmp which content is:

totale 17740
drwxr-xr-x   2 andrea users     4096 gen 12 20:40 ./
drwxrwxrwt 154 root   root     20480 gen 12 20:41 ../
-rw-r--r--   1 andrea users      353 nov 26  2013 00_trailmenu.patch
-rw-r--r--   1 andrea users      209 nov 26  2013 README
-rw-r--r--   1 andrea users       64 nov 26  2013 XEphem
-rw-r--r--   1 andrea users      518 nov 26  2013 doinst.sh
-rw-r--r--   1 andrea users      774 nov 26  2013 slack-desc
-rw-r--r--   1 andrea users 18099098 gen 12 20:16 xephem-3.7.7.tgz
-rw-r--r--   1 root   root       148 gen 12 20:40 xephem-build.log
-rwxr-xr-x   1 andrea users     2815 dic 24 01:40 xephem.SlackBuild*
-rw-r--r--   1 andrea users      227 nov 26  2013 xephem.desktop
-rw-r--r--   1 andrea users      298 dic 24 01:40 xephem.info
-rw-r--r--   1 andrea users     2642 gen 12 11:50 xephem.tar.gz

I know there are two files more than necessary: the original 
xephem.tar.gz which I always keep together with the source file and the
.log file which I created according to the instruction on SBo after
failing to obtain the desired package to install.

Actually the content of the log file is the following:

tar: Questo non sembra un archivio tar
tar: Passaggio alla prossima intestazione
tar: Uscita con stato di fallimento in base agli errori precedenti

which essentially says (for those who don't understand Italian) that it
does not recognize the tar archive as a tar file.

I'm new to the list so I'm not sure is a bug it may be that something
else but is the first time in several years I'm downloading software
from SBo that something doesn't work.

Thanks for the help.

Andrea



From matteo.bernardini at gmail.com  Thu Jan 12 20:35:19 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 12 Jan 2017 21:35:19 +0100
Subject: [Slackbuilds-users] Problems building xephem (3.7.7)
In-Reply-To: <0ccc2fcc-cfc7-0e3f-d515-2f3aadfd16b2@gmx.com>
References: <0ccc2fcc-cfc7-0e3f-d515-2f3aadfd16b2@gmx.com>
Message-ID: <CAPsDuS5=H3TZ1jnDRNz2yR39M+BzM8KsijjRXhChw1dtehwuNA@mail.gmail.com>

2017-01-12 20:52 GMT+01:00 Andrea Maria Marconi <am.marconi at gmx.com>:
> Hi all,
>
> I have downloaded the xephem 3.7.7 package and it's build script,
> unpacked  in the xephem dir (originally in the $HOME/andrea/Download dir
> and then moved under /tmp which content is:
>
> totale 17740
> drwxr-xr-x   2 andrea users     4096 gen 12 20:40 ./
> drwxrwxrwt 154 root   root     20480 gen 12 20:41 ../
> -rw-r--r--   1 andrea users      353 nov 26  2013 00_trailmenu.patch
> -rw-r--r--   1 andrea users      209 nov 26  2013 README
> -rw-r--r--   1 andrea users       64 nov 26  2013 XEphem
> -rw-r--r--   1 andrea users      518 nov 26  2013 doinst.sh
> -rw-r--r--   1 andrea users      774 nov 26  2013 slack-desc
> -rw-r--r--   1 andrea users 18099098 gen 12 20:16 xephem-3.7.7.tgz
> -rw-r--r--   1 root   root       148 gen 12 20:40 xephem-build.log
> -rwxr-xr-x   1 andrea users     2815 dic 24 01:40 xephem.SlackBuild*
> -rw-r--r--   1 andrea users      227 nov 26  2013 xephem.desktop
> -rw-r--r--   1 andrea users      298 dic 24 01:40 xephem.info
> -rw-r--r--   1 andrea users     2642 gen 12 11:50 xephem.tar.gz
>
> I know there are two files more than necessary: the original
> xephem.tar.gz which I always keep together with the source file and the
> .log file which I created according to the instruction on SBo after
> failing to obtain the desired package to install.
>
> Actually the content of the log file is the following:
>
> tar: Questo non sembra un archivio tar
> tar: Passaggio alla prossima intestazione
> tar: Uscita con stato di fallimento in base agli errori precedenti
>
> which essentially says (for those who don't understand Italian) that it
> does not recognize the tar archive as a tar file.
>
> I'm new to the list so I'm not sure is a bug it may be that something
> else but is the first time in several years I'm downloading software
> from SBo that something doesn't work.
>
> Thanks for the help.
>
> Andrea

Hi Andrea,

check the xephem-3.7.7.tgz you downloaded, because it looks different here

# ls -la xephem-3.7.7.tgz
-rw-r--r-- 1 root root 18128521 Oct 31 17:30 xephem-3.7.7.tgz
# md5sum xephem-3.7.7.tgz
27c67061a89085bf2b0d4e9deb758a79  xephem-3.7.7.tgz

try using wget to get the sources, like

wget -c http://www.clearskyinstitute.com/xephem/xephem-3.7.7.tgz

Matteo

From am.marconi at gmx.com  Thu Jan 12 20:47:00 2017
From: am.marconi at gmx.com (Andrea Maria Marconi)
Date: Thu, 12 Jan 2017 21:47:00 +0100
Subject: [Slackbuilds-users] Problems building xephem (3.7.7)
In-Reply-To: <CAPsDuS5=H3TZ1jnDRNz2yR39M+BzM8KsijjRXhChw1dtehwuNA@mail.gmail.com>
References: <0ccc2fcc-cfc7-0e3f-d515-2f3aadfd16b2@gmx.com>
 <CAPsDuS5=H3TZ1jnDRNz2yR39M+BzM8KsijjRXhChw1dtehwuNA@mail.gmail.com>
Message-ID: <4fbda302-78be-c52d-e794-7403075926f5@gmx.com>

Hi Matteo,


Great! It works now.

Thanks a lot.

Andrea


On 12/01/2017 21:35, Matteo Bernardini wrote:
> 2017-01-12 20:52 GMT+01:00 Andrea Maria Marconi <am.marconi at gmx.com>:
>> Hi all,
>>
>> I have downloaded the xephem 3.7.7 package and it's build script,
>> unpacked  in the xephem dir (originally in the $HOME/andrea/Download dir
>> and then moved under /tmp which content is:
>>
>> totale 17740
>> drwxr-xr-x   2 andrea users     4096 gen 12 20:40 ./
>> drwxrwxrwt 154 root   root     20480 gen 12 20:41 ../
>> -rw-r--r--   1 andrea users      353 nov 26  2013 00_trailmenu.patch
>> -rw-r--r--   1 andrea users      209 nov 26  2013 README
>> -rw-r--r--   1 andrea users       64 nov 26  2013 XEphem
>> -rw-r--r--   1 andrea users      518 nov 26  2013 doinst.sh
>> -rw-r--r--   1 andrea users      774 nov 26  2013 slack-desc
>> -rw-r--r--   1 andrea users 18099098 gen 12 20:16 xephem-3.7.7.tgz
>> -rw-r--r--   1 root   root       148 gen 12 20:40 xephem-build.log
>> -rwxr-xr-x   1 andrea users     2815 dic 24 01:40 xephem.SlackBuild*
>> -rw-r--r--   1 andrea users      227 nov 26  2013 xephem.desktop
>> -rw-r--r--   1 andrea users      298 dic 24 01:40 xephem.info
>> -rw-r--r--   1 andrea users     2642 gen 12 11:50 xephem.tar.gz
>>
>> I know there are two files more than necessary: the original
>> xephem.tar.gz which I always keep together with the source file and the
>> .log file which I created according to the instruction on SBo after
>> failing to obtain the desired package to install.
>>
>> Actually the content of the log file is the following:
>>
>> tar: Questo non sembra un archivio tar
>> tar: Passaggio alla prossima intestazione
>> tar: Uscita con stato di fallimento in base agli errori precedenti
>>
>> which essentially says (for those who don't understand Italian) that it
>> does not recognize the tar archive as a tar file.
>>
>> I'm new to the list so I'm not sure is a bug it may be that something
>> else but is the first time in several years I'm downloading software
>> from SBo that something doesn't work.
>>
>> Thanks for the help.
>>
>> Andrea
> Hi Andrea,
>
> check the xephem-3.7.7.tgz you downloaded, because it looks different here
>
> # ls -la xephem-3.7.7.tgz
> -rw-r--r-- 1 root root 18128521 Oct 31 17:30 xephem-3.7.7.tgz
> # md5sum xephem-3.7.7.tgz
> 27c67061a89085bf2b0d4e9deb758a79  xephem-3.7.7.tgz
>
> try using wget to get the sources, like
>
> wget -c http://www.clearskyinstitute.com/xephem/xephem-3.7.7.tgz
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


From Jim.Diamond at acadiau.ca  Thu Jan 12 23:14:36 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Thu, 12 Jan 2017 19:14:36 -0400
Subject: [Slackbuilds-users] tightvnc compile problems
Message-ID: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>

I'm trying to compile tightvnc on a S64-14.2 system.

It compiles away for a while and then

In file included from /usr/include/string.h:25:0,
                 from ../include/os.h:91,
                 from ../include/misc.h:135,
                 from ../include/gc.h:53,
                 from ../include/gcstruct.h:53,
                 from cfbply1rctG.c:33:
/usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
 # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
   ^
rm -f libcfb.a
ar clq libcfb.a cfbgc.o cfbrrop.o cfbwindow.o 	 cfbgetsp.o cfbfillrct.o 	 cfbsolidC.o cfbsolidX.o cfbsolidG.o 	 cfbtileoddC.o cfbtileoddG.o cfbtile32C.o cfbtile32G.o 	 cfbfillsp.o cfbsetsp.o cfbscrinit.o cfballpriv.o 	 cfbpntwin.o cfbmskbits.o cfbpixmap.o 	 cfbcmap.o cfbzerarcC.o cfbzerarcX.o cfbzerarcG.o 	 cfbfillarcC.o cfbfillarcG.o 	 cfbigblt8.o cfbglblt8.o cfbtegblt.o cfbbstore.o 	 cfbpolypnt.o 	 cfbbres.o cfbline.o cfbhrzvert.o cfbbresd.o cfbimage.o cfbseg.o 	 cfb8lineCO.o cfb8lineX.o cfb8lineG.o cfb8lineCP.o 	 cfb8segCS.o cfb8segX.o cfb8segG.o cfb8segC.o 	 cfbbitblt.o cfbbltC.o cfbbltX.o cfbbltO.o cfbbltG.o 	 cfbply1rctC.o cfbply1rctG.o  
ranlib libcfb.a
make[3]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver/cfb24'
rm -f libcfb.a
ar clq libcfb.a cfbgc.o cfbrrop.o cfbwindow.o 	 cfbgetsp.o cfbfillrct.o 	 cfbsolidC.o cfbsolidX.o cfbsolidG.o 	 cfbtileoddC.o cfbtileoddG.o cfbtile32C.o cfbtile32G.o 	 cfbfillsp.o cfbsetsp.o cfbscrinit.o cfballpriv.o 	 cfbpntwin.o cfbmskbits.o cfbpixmap.o 	 cfbcmap.o cfbzerarcC.o cfbzerarcX.o cfbzerarcG.o 	 cfbfillarcC.o cfbfillarcG.o 	 cfbigblt8.o cfbglblt8.o cfbtegblt.o cfbbstore.o 	 cfbpolypnt.o 	 cfbbres.o cfbline.o cfbhrzvert.o cfbbresd.o cfbimage.o cfbseg.o 	 cfb8lineCO.o cfb8lineX.o cfb8lineG.o cfb8lineCP.o 	 cfb8segCS.o cfb8segX.o cfb8segG.o cfb8segC.o 	 cfbbitblt.o cfbbltC.o cfbbltX.o cfbbltO.o cfbbltG.o 	 cfbply1rctC.o cfbply1rctG.o  
ranlib libcfb.a
make[3]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver/cfb32'
make[2]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver'
make[1]: *** [all] Error 2
Makefile:609: recipe for target 'all' failed
make[1]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs'
make: *** [all] Error 2
Makefile:592: recipe for target 'all' failed
Failures:
  tightvnc: tightvnc.SlackBuild return non-zero


While I see lots of warnings in the compiler output, I don't see the
error it is complaining against.

Anyone seeing this issue?

Thanks.


                                Jim

From willysr at slackbuilds.org  Fri Jan 13 00:32:38 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 13 Jan 2017 07:32:38 +0700
Subject: [Slackbuilds-users] tightvnc compile problems
In-Reply-To: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>
References: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>
Message-ID: <6d3c5923-679e-2771-e5e5-30420b8d0868@slackbuilds.org>

> I'm trying to compile tightvnc on a S64-14.2 system.
> 
> It compiles away for a while and then
> 
> In file included from /usr/include/string.h:25:0,
>                  from ../include/os.h:91,
>                  from ../include/misc.h:135,
>                  from ../include/gc.h:53,
>                  from ../include/gcstruct.h:53,
>                  from cfbply1rctG.c:33:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>    ^
> rm -f libcfb.a
> ar clq libcfb.a cfbgc.o cfbrrop.o cfbwindow.o 	 cfbgetsp.o cfbfillrct.o 	 cfbsolidC.o cfbsolidX.o cfbsolidG.o 	 cfbtileoddC.o cfbtileoddG.o cfbtile32C.o cfbtile32G.o 	 cfbfillsp.o cfbsetsp.o cfbscrinit.o cfballpriv.o 	 cfbpntwin.o cfbmskbits.o cfbpixmap.o 	 cfbcmap.o cfbzerarcC.o cfbzerarcX.o cfbzerarcG.o 	 cfbfillarcC.o cfbfillarcG.o 	 cfbigblt8.o cfbglblt8.o cfbtegblt.o cfbbstore.o 	 cfbpolypnt.o 	 cfbbres.o cfbline.o cfbhrzvert.o cfbbresd.o cfbimage.o cfbseg.o 	 cfb8lineCO.o cfb8lineX.o cfb8lineG.o cfb8lineCP.o 	 cfb8segCS.o cfb8segX.o cfb8segG.o cfb8segC.o 	 cfbbitblt.o cfbbltC.o cfbbltX.o cfbbltO.o cfbbltG.o 	 cfbply1rctC.o cfbply1rctG.o  
> ranlib libcfb.a
> make[3]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver/cfb24'
> rm -f libcfb.a
> ar clq libcfb.a cfbgc.o cfbrrop.o cfbwindow.o 	 cfbgetsp.o cfbfillrct.o 	 cfbsolidC.o cfbsolidX.o cfbsolidG.o 	 cfbtileoddC.o cfbtileoddG.o cfbtile32C.o cfbtile32G.o 	 cfbfillsp.o cfbsetsp.o cfbscrinit.o cfballpriv.o 	 cfbpntwin.o cfbmskbits.o cfbpixmap.o 	 cfbcmap.o cfbzerarcC.o cfbzerarcX.o cfbzerarcG.o 	 cfbfillarcC.o cfbfillarcG.o 	 cfbigblt8.o cfbglblt8.o cfbtegblt.o cfbbstore.o 	 cfbpolypnt.o 	 cfbbres.o cfbline.o cfbhrzvert.o cfbbresd.o cfbimage.o cfbseg.o 	 cfb8lineCO.o cfb8lineX.o cfb8lineG.o cfb8lineCP.o 	 cfb8segCS.o cfb8segX.o cfb8segG.o cfb8segC.o 	 cfbbitblt.o cfbbltC.o cfbbltX.o cfbbltO.o cfbbltG.o 	 cfbply1rctC.o cfbply1rctG.o  
> ranlib libcfb.a
> make[3]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver/cfb32'
> make[2]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver'
> make[1]: *** [all] Error 2
> Makefile:609: recipe for target 'all' failed
> make[1]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs'
> make: *** [all] Error 2
> Makefile:592: recipe for target 'all' failed
> Failures:
>   tightvnc: tightvnc.SlackBuild return non-zero
> 
> 
> While I see lots of warnings in the compiler output, I don't see the
> error it is complaining against.

Hi Jim

it works fine here

tightvnc:
  MD5SUM check for tightvnc-1.3.10_unixsrc.tar.bz2 ... OK
  Building package tightvnc-1.3.10-x86_64-1_SBo.tgz ... OK

perhaps you didn't install one of the xorg-* package?


-- 
Willy Sudiarto Raharjo

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

From Jim.Diamond at acadiau.ca  Fri Jan 13 01:06:04 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Thu, 12 Jan 2017 21:06:04 -0400
Subject: [Slackbuilds-users] tightvnc compile problems
In-Reply-To: <6d3c5923-679e-2771-e5e5-30420b8d0868@slackbuilds.org>
References: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>
 <6d3c5923-679e-2771-e5e5-30420b8d0868@slackbuilds.org>
Message-ID: <20170113010604.GA21253@jdiamond-nb.acadiau.ca>

On Fri, Jan 13, 2017 at 07:32 (+0700), Willy Sudiarto Raharjo wrote:

>> I'm trying to compile tightvnc on a S64-14.2 system.

>> It compiles away for a while and then

>> In file included from /usr/include/string.h:25:0,
>> from ../include/os.h:91,
>> from ../include/misc.h:135,
>> from ../include/gc.h:53,
>> from ../include/gcstruct.h:53,
>> from cfbply1rctG.c:33:
>> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>>    ^
>> rm -f libcfb.a
>> ar clq libcfb.a cfbgc.o cfbrrop.o cfbwindow.o 	 cfbgetsp.o cfbfillrct.o 	 cfbsolidC.o cfbsolidX.o cfbsolidG.o 	 cfbtileoddC.o cfbtileoddG.o cfbtile32C.o cfbtile32G.o 	 cfbfillsp.o cfbsetsp.o cfbscrinit.o cfballpriv.o 	 cfbpntwin.o cfbmskbits.o cfbpixmap.o 	 cfbcmap.o cfbzerarcC.o cfbzerarcX.o cfbzerarcG.o 	 cfbfillarcC.o cfbfillarcG.o 	 cfbigblt8.o cfbglblt8.o cfbtegblt.o cfbbstore.o 	 cfbpolypnt.o 	 cfbbres.o cfbline.o cfbhrzvert.o cfbbresd.o cfbimage.o cfbseg.o 	 cfb8lineCO.o cfb8lineX.o cfb8lineG.o cfb8lineCP.o 	 cfb8segCS.o cfb8segX.o cfb8segG.o cfb8segC.o 	 cfbbitblt.o cfbbltC.o cfbbltX.o cfbbltO.o cfbbltG.o 	 cfbply1rctC.o cfbply1rctG.o  
>> ranlib libcfb.a
>> make[3]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver/cfb24'
>> rm -f libcfb.a
>> ar clq libcfb.a cfbgc.o cfbrrop.o cfbwindow.o 	 cfbgetsp.o cfbfillrct.o 	 cfbsolidC.o cfbsolidX.o cfbsolidG.o 	 cfbtileoddC.o cfbtileoddG.o cfbtile32C.o cfbtile32G.o 	 cfbfillsp.o cfbsetsp.o cfbscrinit.o cfballpriv.o 	 cfbpntwin.o cfbmskbits.o cfbpixmap.o 	 cfbcmap.o cfbzerarcC.o cfbzerarcX.o cfbzerarcG.o 	 cfbfillarcC.o cfbfillarcG.o 	 cfbigblt8.o cfbglblt8.o cfbtegblt.o cfbbstore.o 	 cfbpolypnt.o 	 cfbbres.o cfbline.o cfbhrzvert.o cfbbresd.o cfbimage.o cfbseg.o 	 cfb8lineCO.o cfb8lineX.o cfb8lineG.o cfb8lineCP.o 	 cfb8segCS.o cfb8segX.o cfb8segG.o cfb8segC.o 	 cfbbitblt.o cfbbltC.o cfbbltX.o cfbbltO.o cfbbltG.o 	 cfbply1rctC.o cfbply1rctG.o  
>> ranlib libcfb.a
>> make[3]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver/cfb32'
>> make[2]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs/Xserver'
>> make[1]: *** [all] Error 2
>> Makefile:609: recipe for target 'all' failed
>> make[1]: Leaving directory '/tmp/SBo/vnc_unixsrc/Xvnc/programs'
>> make: *** [all] Error 2
>> Makefile:592: recipe for target 'all' failed
>> Failures:
>> tightvnc: tightvnc.SlackBuild return non-zero

>> While I see lots of warnings in the compiler output, I don't see the
>> error it is complaining against.

> Hi Jim

> it works fine here

> tightvnc:
> MD5SUM check for tightvnc-1.3.10_unixsrc.tar.bz2 ... OK
> Building package tightvnc-1.3.10-x86_64-1_SBo.tgz ... OK

> perhaps you didn't install one of the xorg-* package?


Hi Willy,

Thanks for the suggestions.

(1) The sum checks out.

(2) And I have

.../slackware64-14.2/slackware64/x/xorg-cf-files-1.0.6-x86_64-2.txz
.../slackware64-14.2/slackware64/x/xorg-docs-1.7.1-noarch-1.txz
.../slackware64-14.2/slackware64/x/xorg-server-1.18.3-x86_64-2.txz
.../slackware64-14.2/slackware64/x/xorg-server-xephyr-1.18.3-x86_64-2.txz
.../slackware64-14.2/slackware64/x/xorg-server-xnest-1.18.3-x86_64-2.txz
.../slackware64-14.2/slackware64/x/xorg-server-xvfb-1.18.3-x86_64-2.txz
.../slackware64-14.2/slackware64/x/xorg-sgml-doctools-1.11-x86_64-2.txz

in my copy of slackware, and   dir /var/log/packages/xorg-*   says

/var/log/packages/xorg-cf-files-1.0.6-x86_64-2
/var/log/packages/xorg-docs-1.7.1-noarch-1
/var/log/packages/xorg-server-1.18.3-x86_64-2
/var/log/packages/xorg-server-xephyr-1.18.3-x86_64-2
/var/log/packages/xorg-server-xnest-1.18.3-x86_64-2
/var/log/packages/xorg-server-xvfb-1.18.3-x86_64-2
/var/log/packages/xorg-sgml-doctools-1.11-x86_64-2

So that all looks OK.

Cheers.

                                Jim


From willysr at slackbuilds.org  Fri Jan 13 01:17:22 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 13 Jan 2017 08:17:22 +0700
Subject: [Slackbuilds-users] tightvnc compile problems
In-Reply-To: <20170113010604.GA21253@jdiamond-nb.acadiau.ca>
References: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>
 <6d3c5923-679e-2771-e5e5-30420b8d0868@slackbuilds.org>
 <20170113010604.GA21253@jdiamond-nb.acadiau.ca>
Message-ID: <d3d2ab43-2553-5281-0a76-31fd03aed3dd@slackbuilds.org>

> Thanks for the suggestions.
> 
> (1) The sum checks out.
> 
> (2) And I have
> 
> .../slackware64-14.2/slackware64/x/xorg-cf-files-1.0.6-x86_64-2.txz
> .../slackware64-14.2/slackware64/x/xorg-docs-1.7.1-noarch-1.txz
> .../slackware64-14.2/slackware64/x/xorg-server-1.18.3-x86_64-2.txz
> .../slackware64-14.2/slackware64/x/xorg-server-xephyr-1.18.3-x86_64-2.txz
> .../slackware64-14.2/slackware64/x/xorg-server-xnest-1.18.3-x86_64-2.txz
> .../slackware64-14.2/slackware64/x/xorg-server-xvfb-1.18.3-x86_64-2.txz
> .../slackware64-14.2/slackware64/x/xorg-sgml-doctools-1.11-x86_64-2.txz
> 
> in my copy of slackware, and   dir /var/log/packages/xorg-*   says
> 
> /var/log/packages/xorg-cf-files-1.0.6-x86_64-2
> /var/log/packages/xorg-docs-1.7.1-noarch-1
> /var/log/packages/xorg-server-1.18.3-x86_64-2
> /var/log/packages/xorg-server-xephyr-1.18.3-x86_64-2
> /var/log/packages/xorg-server-xnest-1.18.3-x86_64-2
> /var/log/packages/xorg-server-xvfb-1.18.3-x86_64-2
> /var/log/packages/xorg-sgml-doctools-1.11-x86_64-2
> 
> So that all looks OK.

It it possible to attach the complete build log?


-- 
Willy Sudiarto Raharjo

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

From Jim.Diamond at acadiau.ca  Fri Jan 13 01:31:00 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Thu, 12 Jan 2017 21:31:00 -0400
Subject: [Slackbuilds-users] tightvnc compile problems
In-Reply-To: <d3d2ab43-2553-5281-0a76-31fd03aed3dd@slackbuilds.org>
References: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>
 <6d3c5923-679e-2771-e5e5-30420b8d0868@slackbuilds.org>
 <20170113010604.GA21253@jdiamond-nb.acadiau.ca>
 <d3d2ab43-2553-5281-0a76-31fd03aed3dd@slackbuilds.org>
Message-ID: <20170113013100.GA23534@jdiamond-nb.acadiau.ca>

On Fri, Jan 13, 2017 at 08:17 (+0700), Willy Sudiarto Raharjo wrote:

>> Thanks for the suggestions.

>> (1) The sum checks out.

>> (2) And I have

>> .../slackware64-14.2/slackware64/x/xorg-cf-files-1.0.6-x86_64-2.txz
>> .../slackware64-14.2/slackware64/x/xorg-docs-1.7.1-noarch-1.txz
>> .../slackware64-14.2/slackware64/x/xorg-server-1.18.3-x86_64-2.txz
>> .../slackware64-14.2/slackware64/x/xorg-server-xephyr-1.18.3-x86_64-2.txz
>> .../slackware64-14.2/slackware64/x/xorg-server-xnest-1.18.3-x86_64-2.txz
>> .../slackware64-14.2/slackware64/x/xorg-server-xvfb-1.18.3-x86_64-2.txz
>> .../slackware64-14.2/slackware64/x/xorg-sgml-doctools-1.11-x86_64-2.txz

>> in my copy of slackware, and   dir /var/log/packages/xorg-*   says

>> /var/log/packages/xorg-cf-files-1.0.6-x86_64-2
>> /var/log/packages/xorg-docs-1.7.1-noarch-1
>> /var/log/packages/xorg-server-1.18.3-x86_64-2
>> /var/log/packages/xorg-server-xephyr-1.18.3-x86_64-2
>> /var/log/packages/xorg-server-xnest-1.18.3-x86_64-2
>> /var/log/packages/xorg-server-xvfb-1.18.3-x86_64-2
>> /var/log/packages/xorg-sgml-doctools-1.11-x86_64-2

>> So that all looks OK.

> It it possible to attach the complete build log?

It is.  And I still can, if you want (just let me know).

But it occurred to me that perhaps this is one of those packages that
won't build if you give -j <something bigger than 1> as a make option.

So I tried with -j 1
        sboconfig -j 1 ; sboinstall tightvnc
And it worked this time.

(If God didn't want me to have 8 compiles going at one time, He
wouldn't have let me have a computer with 4 hyper-threaded cores.)

So maybe I should rephrase my issue here as follows:
        Should we put a note in the README that says to use "-j 1" for
        best results?

Cheers.

                                Jim

From andreas.guldstrand at gmail.com  Fri Jan 13 02:46:17 2017
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Fri, 13 Jan 2017 03:46:17 +0100
Subject: [Slackbuilds-users] tightvnc compile problems
In-Reply-To: <20170113013100.GA23534@jdiamond-nb.acadiau.ca>
References: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>
 <6d3c5923-679e-2771-e5e5-30420b8d0868@slackbuilds.org>
 <20170113010604.GA21253@jdiamond-nb.acadiau.ca>
 <d3d2ab43-2553-5281-0a76-31fd03aed3dd@slackbuilds.org>
 <20170113013100.GA23534@jdiamond-nb.acadiau.ca>
Message-ID: <CAEQ5t80Hwi_W77kOFCKbt-vDP8PR+C7n99x9L_92dD7E4fd-7A@mail.gmail.com>

Would be better to simply change the slackbuild script's make
invocation to make it -j 1 instead ... if that's done sbotools won't
try to use its -j setting

On 13 January 2017 at 02:31, Jim Diamond <Jim.Diamond at acadiau.ca> wrote:
> On Fri, Jan 13, 2017 at 08:17 (+0700), Willy Sudiarto Raharjo wrote:
>
>>> Thanks for the suggestions.
>
>>> (1) The sum checks out.
>
>>> (2) And I have
>
>>> .../slackware64-14.2/slackware64/x/xorg-cf-files-1.0.6-x86_64-2.txz
>>> .../slackware64-14.2/slackware64/x/xorg-docs-1.7.1-noarch-1.txz
>>> .../slackware64-14.2/slackware64/x/xorg-server-1.18.3-x86_64-2.txz
>>> .../slackware64-14.2/slackware64/x/xorg-server-xephyr-1.18.3-x86_64-2.txz
>>> .../slackware64-14.2/slackware64/x/xorg-server-xnest-1.18.3-x86_64-2.txz
>>> .../slackware64-14.2/slackware64/x/xorg-server-xvfb-1.18.3-x86_64-2.txz
>>> .../slackware64-14.2/slackware64/x/xorg-sgml-doctools-1.11-x86_64-2.txz
>
>>> in my copy of slackware, and   dir /var/log/packages/xorg-*   says
>
>>> /var/log/packages/xorg-cf-files-1.0.6-x86_64-2
>>> /var/log/packages/xorg-docs-1.7.1-noarch-1
>>> /var/log/packages/xorg-server-1.18.3-x86_64-2
>>> /var/log/packages/xorg-server-xephyr-1.18.3-x86_64-2
>>> /var/log/packages/xorg-server-xnest-1.18.3-x86_64-2
>>> /var/log/packages/xorg-server-xvfb-1.18.3-x86_64-2
>>> /var/log/packages/xorg-sgml-doctools-1.11-x86_64-2
>
>>> So that all looks OK.
>
>> It it possible to attach the complete build log?
>
> It is.  And I still can, if you want (just let me know).
>
> But it occurred to me that perhaps this is one of those packages that
> won't build if you give -j <something bigger than 1> as a make option.
>
> So I tried with -j 1
>         sboconfig -j 1 ; sboinstall tightvnc
> And it worked this time.
>
> (If God didn't want me to have 8 compiles going at one time, He
> wouldn't have let me have a computer with 4 hyper-threaded cores.)
>
> So maybe I should rephrase my issue here as follows:
>         Should we put a note in the README that says to use "-j 1" for
>         best results?
>
> Cheers.
>
>                                 Jim
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From Jim.Diamond at acadiau.ca  Fri Jan 13 03:03:54 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Thu, 12 Jan 2017 23:03:54 -0400
Subject: [Slackbuilds-users] tightvnc compile problems
In-Reply-To: <CAEQ5t80Hwi_W77kOFCKbt-vDP8PR+C7n99x9L_92dD7E4fd-7A@mail.gmail.com>
References: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>
 <6d3c5923-679e-2771-e5e5-30420b8d0868@slackbuilds.org>
 <20170113010604.GA21253@jdiamond-nb.acadiau.ca>
 <d3d2ab43-2553-5281-0a76-31fd03aed3dd@slackbuilds.org>
 <20170113013100.GA23534@jdiamond-nb.acadiau.ca>
 <CAEQ5t80Hwi_W77kOFCKbt-vDP8PR+C7n99x9L_92dD7E4fd-7A@mail.gmail.com>
Message-ID: <20170113030354.GA1296@jdiamond-nb.acadiau.ca>

On Fri, Jan 13, 2017 at 03:46 (+0100), Andreas Guldstrand wrote:

> Would be better to simply change the slackbuild script's make
> invocation to make it -j 1 instead ... if that's done sbotools won't
> try to use its -j setting

Perhaps your question is to everyone, but in case you were asking me:

That might be better, depending on the POV of the Makefile author.
Who knows, perhaps there is some peculiarity of my systems which
caused the build to crash.  If it is only a rare case of the build
failing, then maybe we don't want to slow down everyone for a rare case.

Cheers.

                                Jim

From willysr at slackbuilds.org  Fri Jan 13 03:14:50 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 13 Jan 2017 10:14:50 +0700
Subject: [Slackbuilds-users] tightvnc compile problems
In-Reply-To: <20170113030354.GA1296@jdiamond-nb.acadiau.ca>
References: <20170112231436.GA29411@jdiamond-nb.acadiau.ca>
 <6d3c5923-679e-2771-e5e5-30420b8d0868@slackbuilds.org>
 <20170113010604.GA21253@jdiamond-nb.acadiau.ca>
 <d3d2ab43-2553-5281-0a76-31fd03aed3dd@slackbuilds.org>
 <20170113013100.GA23534@jdiamond-nb.acadiau.ca>
 <CAEQ5t80Hwi_W77kOFCKbt-vDP8PR+C7n99x9L_92dD7E4fd-7A@mail.gmail.com>
 <20170113030354.GA1296@jdiamond-nb.acadiau.ca>
Message-ID: <94011ef7-f7a8-0570-5c85-2ffdddce0ef1@slackbuilds.org>

>> Would be better to simply change the slackbuild script's make
>> invocation to make it -j 1 instead ... if that's done sbotools won't
>> try to use its -j setting
> 
> Perhaps your question is to everyone, but in case you were asking me:
> 
> That might be better, depending on the POV of the Makefile author.
> Who knows, perhaps there is some peculiarity of my systems which
> caused the build to crash.  If it is only a rare case of the build
> failing, then maybe we don't want to slow down everyone for a rare case.

Simply editing one line is not too much work
I think more people will buy new hardware in the future and we might
have this problem as well

-- 
Willy Sudiarto Raharjo

-------------- 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/20170113/7597433f/attachment.asc>

From slacker6896 at gmail.com  Fri Jan 13 13:40:14 2017
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Fri, 13 Jan 2017 14:40:14 +0100
Subject: [Slackbuilds-users] apache-tomcat slackbuild silently changes
 /var/tmp permissions
Message-ID: <CAA2+phFXAADiXWNPCoAfd+h1NP5HDq_11HsWtqhXpbntJsu_Ng@mail.gmail.com>

Hello,

On a clean Slackware, /var/tmp permissions are set to 1777, but once
apache-tomcat
<https://slackbuilds.org/repository/14.2/system/apache-tomcat/> is
installed, permissions are changed to 755 which can lead to issues. The
attached patch fixes this issue.


-- 
SeB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170113/553a9583/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: apache-tomcat-fix-var-tmp-permissions.patch
Type: text/x-patch
Size: 495 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170113/553a9583/attachment.bin>

From matteo.bernardini at gmail.com  Fri Jan 13 13:53:54 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 13 Jan 2017 14:53:54 +0100
Subject: [Slackbuilds-users] apache-tomcat slackbuild silently changes
 /var/tmp permissions
In-Reply-To: <CAA2+phFXAADiXWNPCoAfd+h1NP5HDq_11HsWtqhXpbntJsu_Ng@mail.gmail.com>
References: <CAA2+phFXAADiXWNPCoAfd+h1NP5HDq_11HsWtqhXpbntJsu_Ng@mail.gmail.com>
Message-ID: <CAPsDuS7dXoACuN_9+J+qFiAJET_y6h1AQen9w-Oq0-N=tXeqJg@mail.gmail.com>

2017-01-13 14:40 GMT+01:00 Sebastien BALLET <slacker6896 at gmail.com>:
> Hello,
>
> On a clean Slackware, /var/tmp permissions are set to 1777, but once
> apache-tomcat is installed, permissions are changed to 755 which can lead to
> issues. The attached patch fixes this issue.

thanks Sebastien, nice catch!

I just submitted it in my branch.

Matteo

From brent at exitstatusone.com  Fri Jan 13 14:31:18 2017
From: brent at exitstatusone.com (Brenton Earl)
Date: Fri, 13 Jan 2017 07:31:18 -0700
Subject: [Slackbuilds-users] netlib removal
Message-ID: <20170113143118.GA8099@gmail.com>

Hello,

Please remove netlib from SBo.  It has been merged into the larger code
base of "mitmproxy."

Thanks,
Brenton Earl

From willysr at slackbuilds.org  Fri Jan 13 14:34:21 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 13 Jan 2017 21:34:21 +0700
Subject: [Slackbuilds-users] netlib removal
In-Reply-To: <20170113143118.GA8099@gmail.com>
References: <20170113143118.GA8099@gmail.com>
Message-ID: <cbf46356-4ae1-1679-e07f-a0fa9c2497f3@slackbuilds.org>

> Please remove netlib from SBo.  It has been merged into the larger code
> base of "mitmproxy."

Removed in my branch

Thanks


-- 
Willy Sudiarto Raharjo

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

From atelszewski at gmail.com  Fri Jan 13 22:20:07 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 13 Jan 2017 23:20:07 +0100
Subject: [Slackbuilds-users] Package verification at SBo [was:
 apache-tomcat slackbuild silently changes /var/tmp permissions]
In-Reply-To: <CAPsDuS7dXoACuN_9+J+qFiAJET_y6h1AQen9w-Oq0-N=tXeqJg@mail.gmail.com>
References: <CAA2+phFXAADiXWNPCoAfd+h1NP5HDq_11HsWtqhXpbntJsu_Ng@mail.gmail.com>
 <CAPsDuS7dXoACuN_9+J+qFiAJET_y6h1AQen9w-Oq0-N=tXeqJg@mail.gmail.com>
Message-ID: <b3bb21c4-2b90-1584-4034-5be9e1bbd0b2@gmail.com>

On 13/01/17 14:53, Matteo Bernardini wrote:
> 2017-01-13 14:40 GMT+01:00 Sebastien BALLET <slacker6896 at gmail.com>:
>> Hello,
>>
>> On a clean Slackware, /var/tmp permissions are set to 1777, but once
>> apache-tomcat is installed, permissions are changed to 755 which can lead to
>> issues. The attached patch fixes this issue.
>
> thanks Sebastien, nice catch!
>
> I just submitted it in my branch.
>

This raises question: aren't you admins using any kind of package 
checking tool?
If not, would you be interested to have something?

If we came up with a list of requirements, I could cook something in C 
(or C++), using libarchive.

Then, the error like the one above would be easily caught.

-- 
Best regards,
Andrzej Telszewski

From brent at exitstatusone.com  Sat Jan 14 00:20:19 2017
From: brent at exitstatusone.com (Brenton Earl)
Date: Fri, 13 Jan 2017 17:20:19 -0700
Subject: [Slackbuilds-users] pianobar slackbuild 2016.06.02
Message-ID: <20170114002019.GA2601@gmail.com>

Hello,

I tried to contact the maintainer with no response for some time.
I would be happy to take over maintenance since I use pianobar all the
time.

Thanks!

----- Forwarded message from Brenton Earl <brent at exitstatusone.com> -----

Date: Tue, 3 Jan 2017 11:21:46 -0700
From: Brenton Earl <brent at exitstatusone.com>
To: pc_warner at yahoo.com
Subject: pianobar slackbuild 2016.06.02
User-Agent: Mutt/1.6.1 (2016-04-27)

Hello,

Would it be possible for you to update pianobar to version 2016.06.02?
I am running this version on Slackware64 14.2 without issues.  I did not
use the Makefile patch because it fails to patch correctly.

Thanks,

Brenton Earl

----- End forwarded message -----

From harald.achitz at gmail.com  Sat Jan 14 10:11:18 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sat, 14 Jan 2017 11:11:18 +0100
Subject: [Slackbuilds-users] Orphaning some builds.
In-Reply-To: <1fc2d680-ed26-4779-bd9a-7f30b4c867c9@gmail.com>
References: <CAAcyf-pD313ztT8hXSTVEyfwPXv3vU+MZDvUJiU2YwY3KJtBzQ@mail.gmail.com>
 <1fc2d680-ed26-4779-bd9a-7f30b4c867c9@gmail.com>
Message-ID: <CAPh+tzMbjKbxrJQQBP=pC5zLXji5ZGQYYHWeNi6CgpLcJsXEgA@mail.gmail.com>

Hi
I have an updated version of the slack build (2.3.4) and can submit that.
I can not guarantee how long I will maintain this, but maybe for a while
since c++ channel is pretty active an dalso some colleagues at work use
slack heavily.
shall I submit it?

/Harald

2017-01-09 22:57 GMT+01:00 Dhaby Xiloj <slack.dhabyx at gmail.com>:

> I am attempting to use less non-free software, so I?ll be giving up these
> three builds, hopefully someone is interested in them:
>
> multimedia/spotify
> network/hipchat
> network/slack
>
> Konpai,
>
> I take spotify
>
> --
> Dhaby Xiloj
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170114/61220c89/attachment-0001.html>

From pprkut at slackbuilds.org  Sat Jan 14 10:41:14 2017
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Sat, 14 Jan 2017 11:41:14 +0100
Subject: [Slackbuilds-users] Package verification at SBo [was:
 apache-tomcat slackbuild silently changes /var/tmp permissions]
In-Reply-To: <b3bb21c4-2b90-1584-4034-5be9e1bbd0b2@gmail.com>
References: <CAA2+phFXAADiXWNPCoAfd+h1NP5HDq_11HsWtqhXpbntJsu_Ng@mail.gmail.com>
 <CAPsDuS7dXoACuN_9+J+qFiAJET_y6h1AQen9w-Oq0-N=tXeqJg@mail.gmail.com>
 <b3bb21c4-2b90-1584-4034-5be9e1bbd0b2@gmail.com>
Message-ID: <2159136.V8VLyrkdz5@titania>

On Friday, 13 January 2017 23:20:07 CET Andrzej Telszewski wrote:
> On 13/01/17 14:53, Matteo Bernardini wrote:
> > 2017-01-13 14:40 GMT+01:00 Sebastien BALLET <slacker6896 at gmail.com>:
> >> Hello,
> >> 
> >> On a clean Slackware, /var/tmp permissions are set to 1777, but once
> >> apache-tomcat is installed, permissions are changed to 755 which can lead
> >> to issues. The attached patch fixes this issue.
> > 
> > thanks Sebastien, nice catch!
> > 
> > I just submitted it in my branch.
> 
> This raises question: aren't you admins using any kind of package
> checking tool?
> If not, would you be interested to have something?
> 
> If we came up with a list of requirements, I could cook something in C
> (or C++), using libarchive.
> 
> Then, the error like the one above would be easily caught.

I'm using lintpkg [1] to check all of my packages. It does have some 
permission checks, but not for /var/tmp, that's why it slipped through. Should 
be easy enough to add though.

Grs,
Heinz

[1] https://github.com/pprkut/lintpkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170114/35655570/attachment.asc>

From slacker6896 at gmail.com  Sat Jan 14 17:31:19 2017
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Sat, 14 Jan 2017 18:31:19 +0100
Subject: [Slackbuilds-users] apache-tomcat slackbuild silently changes
 /var/tmp permissions
In-Reply-To: <CAPsDuS7dXoACuN_9+J+qFiAJET_y6h1AQen9w-Oq0-N=tXeqJg@mail.gmail.com>
References: <CAA2+phFXAADiXWNPCoAfd+h1NP5HDq_11HsWtqhXpbntJsu_Ng@mail.gmail.com>
 <CAPsDuS7dXoACuN_9+J+qFiAJET_y6h1AQen9w-Oq0-N=tXeqJg@mail.gmail.com>
Message-ID: <CAA2+phG064yo5xG9HhJPNFMKyQC2c0n2d+w6MEyPRhH9V9Uu4w@mail.gmail.com>

Hello,

There's something else which I find troublesome in apache-tomcat.SlackBuild
at line #92-93 :

chmod -R 755 ${PKG}${TOMCAT_HOME}
chmod -R 775 ${PKG}${TOMCAT_HOME}/webapps

Note: TOMCAT_HOME=/var/lib/tomcat

I don't see any reason to set executable bit to all files in
/var/lib/tomcat, nor to set  all files in /var/lib/tomcat/webapps
read/write/executable for users in tomcat group. I think the option "-R" is
not required in both cases.

-- 
SeB

2017-01-13 14:53 GMT+01:00 Matteo Bernardini <matteo.bernardini at gmail.com>:

> 2017-01-13 14:40 GMT+01:00 Sebastien BALLET <slacker6896 at gmail.com>:
> > Hello,
> >
> > On a clean Slackware, /var/tmp permissions are set to 1777, but once
> > apache-tomcat is installed, permissions are changed to 755 which can
> lead to
> > issues. The attached patch fixes this issue.
>
> thanks Sebastien, nice catch!
>
> I just submitted it in my branch.
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170114/e19f60a7/attachment.html>

From willysr at slackbuilds.org  Sat Jan 14 23:51:28 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 15 Jan 2017 06:51:28 +0700
Subject: [Slackbuilds-users] Updates - 20170114.1
Message-ID: <bdf95a90-5828-f52b-3681-8f7765c077d8@slackbuilds.org>

Sat Jan 14 23:36:48 UTC 2017
academic/FCSalyzer: Added (Flow cytometry analyser).
academic/flann: Updated for version 1.9.1 + new maintainer.
audio/SuperCollider: Update DEP and README.
audio/cd-discid: New maintainer. i486 => i586.
audio/freac: Added (Audio converter and CD ripper).
audio/mixxx: Add upstream patch for the newer chromaprint.
audio/mpd: Updated for version 0.20.1.
audio/ncmpcpp: Updated for version 0.7.7.
desktop/glabels: Compile glib schemas in doinst.sh.
desktop/gnome-menus: Update dep.
desktop/imgur-screenshot: Updated for version 1.7.4.
desktop/numix-pack: Updated for version 0.4.6.
desktop/ratpoison: New maintainer. i486 => i586.
desktop/wmii: New maintainer. i486 => i586.
desktop/yad: Updated for version 0.38.1.
development/CImg: Updated for version 1.7.9.
development/atom: Updated for version 1.12.9.
development/eclipse-cpp: Updated for version 4.6.2.
development/eclipse-java: Updated for version 4.6.2.
development/eclipse-jee: Updated for version 4.6.2.
development/g3log: Added (Asynchronous logger with Dynamic Sinks).
development/komodo-edit: Updated for version 10.1.4.
development/komodo-ide: Updated for version 10.1.4.
development/pandas: Updated for version 0.19.2.
development/reckless: Added (logging library).
development/scite: Updated for version 3.7.2.
development/spdlog: Added (C++ logging library).
development/u-boot-tools: Updated for version 2017.01.
games/SLADE: Updated for version 3.1.1.4.
games/chessx: Update EMAIL and switch to i586.
games/chocolate-doom: Updated for version 2.3.0.
games/doomretro: Updated for version 2.3.9.
games/eureka: Updated for version 1.21.
games/lutris: Updated for version 0.4.4.
games/mame: Updated for version 0.181.
games/uligo: Added (Go games).
graphics/qcad: Updated for version 3.16.4.0
graphics/yacreader: Added (comic book reader).
libraries/Botan: Updated for version 2.0.1.
libraries/dlib: Added (machine learning and data analysis toolkit).
libraries/gperftools: Added (performance tools).
libraries/hpx: Added (C++ Standards Library).
libraries/ignition-math2: Added (math library).
libraries/ignition-transport: Added (message passing library).
libraries/libmodbus: Updated for version 3.0.6.
libraries/libosinfo: Updated for version 1.0.0.
libraries/live555: Ensure LIBDIRSUFFIX is set for non-x86
libraries/log4net: Added (log tool for mono).
libraries/lxqt-build-tools: Updated for version 0.3.2.
libraries/nini: Added (.NET configuration library).
libraries/pcl: Added (2D/3D image library).
libraries/rarfile: Updated for version 3.0.
libraries/sdformat: Added (XML format).
libraries/unarr: Added (archive library).
misc/paperkey: Added (an OpenPGP key archiver).
multimedia/flashplayer-plugin: Updated for version 24.0.0.194.
multimedia/pepperflash-plugin: Updated for version 24.0.0.194.
multimedia/pitivi: Update DOWNLOAD url.
multimedia/vlc: Adjust for arm architecture
network/PaleMoon: Add patch to support newer sed.
network/bitcoin: Updated for version 0.13.2.
network/claws-mail: Fixup typo and grammar in slack-desc
network/filezilla: Updated for version 3.24.0.
network/fqterm: Update DOWNLOAD url.
network/lighttpd: Updated for version 1.4.45.
network/retroshare: Updated for version 0.6.1 + new maintainer.
network/smuxi: Added (chat client).
network/speedtest-cli: Updated for version 1.0.1.
network/telegram: Updated for version 1.0.0.
network/tightvnc: Switch to i586 and use -j1.
network/youtube-dl: Updated for version 2017.01.08.
office/smoffice2016: Added (office suite).
office/texstudio: Updated for version 2.12.0
perl/perl-Math-BigInt-GMP: Updated for version 1.6003.
perl/perl-Math-BigInt: Updated for version 1.999808.
perl/perl-Math-MPC: Disable make test.
perl/perl-Math-MPFR: Disable make test.
perl/perl-Number-Bites-Human: Updated for version 0.11.
perl/perl-libnet: Added (perl net modules).
python/cssselect: Updated for version 1.0.1
python/egenix-mx-base: Updated for version 3.2.9.
python/hpack: Add python3 support.
python/netlib: Removed (merged into mitproxy).
python/passlib: Add python3 support.
python/pyPdf: Fix script.
python/pybluez: Updated for version 0.22.
python/pydot: Updated for version 1.2.3.
python/pyicu: Updated for version 1.9.5.
python/python-gattlib: Added (Bluetooth LE protocol library).
python/pytz: Updated for version 2016.10.
python/vobject: Updated for version 0.9.3.
ruby/ruby-build: Updated for version 20170112.
ruby/ruby-faraday: Updated for version 0.11.0.
ruby/ruby-json: Updated for version 2.0.3.
ruby/rubygem-bundler: Updated for version 1.13.7.
system/Iosevka: Updated for version 1.10.3.
system/apache-tomcat: Fix packaged /var/tmp permissions.
system/borgbackup: Updated for version 1.0.9.
system/fasd: Added (Command-line productivity booster).
system/gnome-commander: Compile glib schemas in doinst.sh.
system/iucode_tool: Updated for version 2.1.1.
system/osinfo-db-tools: Added (operating systems database tools).
system/osinfo-db: Added (operating systems database).
system/rsyslog: Updated for version 8.24.0.
system/sbotools: Updated for version 2.1.
system/vtcol: Added (Colour schemes for the Linux console).
system/worker: Updated for version 3.8.5.
+--------------------------+

-- 
Willy Sudiarto Raharjo

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

From atelszewski at gmail.com  Sun Jan 15 01:02:54 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 15 Jan 2017 02:02:54 +0100
Subject: [Slackbuilds-users] Package verification at SBo [was:
 apache-tomcat slackbuild silently changes /var/tmp permissions]
In-Reply-To: <2159136.V8VLyrkdz5@titania>
References: <CAA2+phFXAADiXWNPCoAfd+h1NP5HDq_11HsWtqhXpbntJsu_Ng@mail.gmail.com>
 <CAPsDuS7dXoACuN_9+J+qFiAJET_y6h1AQen9w-Oq0-N=tXeqJg@mail.gmail.com>
 <b3bb21c4-2b90-1584-4034-5be9e1bbd0b2@gmail.com> <2159136.V8VLyrkdz5@titania>
Message-ID: <01fcfcfd-116d-d7ae-8642-3e88b352b1f6@gmail.com>

On 14/01/17 11:41, Heinz Wiesinger wrote:
> On Friday, 13 January 2017 23:20:07 CET Andrzej Telszewski wrote:
>> On 13/01/17 14:53, Matteo Bernardini wrote:
>>> 2017-01-13 14:40 GMT+01:00 Sebastien BALLET <slacker6896 at gmail.com>:
>>>> Hello,
>>>>
>>>> On a clean Slackware, /var/tmp permissions are set to 1777, but once
>>>> apache-tomcat is installed, permissions are changed to 755 which can lead
>>>> to issues. The attached patch fixes this issue.
>>>
>>> thanks Sebastien, nice catch!
>>>
>>> I just submitted it in my branch.
>>
>> This raises question: aren't you admins using any kind of package
>> checking tool?
>> If not, would you be interested to have something?
>>
>> If we came up with a list of requirements, I could cook something in C
>> (or C++), using libarchive.
>>
>> Then, the error like the one above would be easily caught.
>
> I'm using lintpkg [1] to check all of my packages. It does have some
> permission checks, but not for /var/tmp, that's why it slipped through. Should
> be easy enough to add though.
>
> Grs,
> Heinz
>
> [1] https://github.com/pprkut/lintpkg

I had something like _lintpkg_ on my mind for some time.
It will probably happen one day that I will take the ideas from there 
and code it in C.

BTW, for you (admins) it would make sense to replace /sbin/makepkg with 
a wrapper that will first run the lint on not yet packaged directory, 
and then call the real makepkg.
This would save a bit of a time, especially on bigger stuff.
Well, maybe you're already doing this ;-)

-- 
Best regards,
Andrzej Telszewski

From reedych at reedych.pw  Sun Jan 15 06:36:16 2017
From: reedych at reedych.pw (reedych)
Date: Sun, 15 Jan 2017 12:36:16 +0600
Subject: [Slackbuilds-users] Updates - 20170114.1
In-Reply-To: <bdf95a90-5828-f52b-3681-8f7765c077d8@slackbuilds.org>
References: <bdf95a90-5828-f52b-3681-8f7765c077d8@slackbuilds.org>
Message-ID: <20170115123606.37aebd3d@slackware>

? Sun, 15 Jan 2017 06:51:28 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> ?????:

> Sat Jan 14 23:36:48 UTC 2017
> academic/FCSalyzer: Added (Flow cytometry analyser).
> academic/flann: Updated for version 1.9.1 + new maintainer.
> audio/SuperCollider: Update DEP and README.
> audio/cd-discid: New maintainer. i486 => i586.
> audio/freac: Added (Audio converter and CD ripper).
> audio/mixxx: Add upstream patch for the newer chromaprint.
> audio/mpd: Updated for version 0.20.1.
> audio/ncmpcpp: Updated for version 0.7.7.
> desktop/glabels: Compile glib schemas in doinst.sh.
> desktop/gnome-menus: Update dep.
> desktop/imgur-screenshot: Updated for version 1.7.4.
> desktop/numix-pack: Updated for version 0.4.6.
> desktop/ratpoison: New maintainer. i486 => i586.
> desktop/wmii: New maintainer. i486 => i586.
> desktop/yad: Updated for version 0.38.1.
> development/CImg: Updated for version 1.7.9.
> development/atom: Updated for version 1.12.9.
> development/eclipse-cpp: Updated for version 4.6.2.
> development/eclipse-java: Updated for version 4.6.2.
> development/eclipse-jee: Updated for version 4.6.2.
> development/g3log: Added (Asynchronous logger with Dynamic Sinks).
> development/komodo-edit: Updated for version 10.1.4.
> development/komodo-ide: Updated for version 10.1.4.
> development/pandas: Updated for version 0.19.2.
> development/reckless: Added (logging library).
> development/scite: Updated for version 3.7.2.
> development/spdlog: Added (C++ logging library).
> development/u-boot-tools: Updated for version 2017.01.
> games/SLADE: Updated for version 3.1.1.4.
> games/chessx: Update EMAIL and switch to i586.
> games/chocolate-doom: Updated for version 2.3.0.
> games/doomretro: Updated for version 2.3.9.
> games/eureka: Updated for version 1.21.
> games/lutris: Updated for version 0.4.4.
> games/mame: Updated for version 0.181.
> games/uligo: Added (Go games).
> graphics/qcad: Updated for version 3.16.4.0
> graphics/yacreader: Added (comic book reader).
> libraries/Botan: Updated for version 2.0.1.
> libraries/dlib: Added (machine learning and data analysis toolkit).
> libraries/gperftools: Added (performance tools).
> libraries/hpx: Added (C++ Standards Library).
> libraries/ignition-math2: Added (math library).
> libraries/ignition-transport: Added (message passing library).
> libraries/libmodbus: Updated for version 3.0.6.
> libraries/libosinfo: Updated for version 1.0.0.
> libraries/live555: Ensure LIBDIRSUFFIX is set for non-x86
> libraries/log4net: Added (log tool for mono).
> libraries/lxqt-build-tools: Updated for version 0.3.2.
> libraries/nini: Added (.NET configuration library).
> libraries/pcl: Added (2D/3D image library).
> libraries/rarfile: Updated for version 3.0.
> libraries/sdformat: Added (XML format).
> libraries/unarr: Added (archive library).
> misc/paperkey: Added (an OpenPGP key archiver).
> multimedia/flashplayer-plugin: Updated for version 24.0.0.194.
> multimedia/pepperflash-plugin: Updated for version 24.0.0.194.
> multimedia/pitivi: Update DOWNLOAD url.
> multimedia/vlc: Adjust for arm architecture
> network/PaleMoon: Add patch to support newer sed.
> network/bitcoin: Updated for version 0.13.2.
> network/claws-mail: Fixup typo and grammar in slack-desc
> network/filezilla: Updated for version 3.24.0.
> network/fqterm: Update DOWNLOAD url.
> network/lighttpd: Updated for version 1.4.45.
> network/retroshare: Updated for version 0.6.1 + new maintainer.
> network/smuxi: Added (chat client).
> network/speedtest-cli: Updated for version 1.0.1.
> network/telegram: Updated for version 1.0.0.
> network/tightvnc: Switch to i586 and use -j1.
> network/youtube-dl: Updated for version 2017.01.08.
> office/smoffice2016: Added (office suite).
> office/texstudio: Updated for version 2.12.0
> perl/perl-Math-BigInt-GMP: Updated for version 1.6003.
> perl/perl-Math-BigInt: Updated for version 1.999808.
> perl/perl-Math-MPC: Disable make test.
> perl/perl-Math-MPFR: Disable make test.
> perl/perl-Number-Bites-Human: Updated for version 0.11.
> perl/perl-libnet: Added (perl net modules).
> python/cssselect: Updated for version 1.0.1
> python/egenix-mx-base: Updated for version 3.2.9.
> python/hpack: Add python3 support.
> python/netlib: Removed (merged into mitproxy).
> python/passlib: Add python3 support.
> python/pyPdf: Fix script.
> python/pybluez: Updated for version 0.22.
> python/pydot: Updated for version 1.2.3.
> python/pyicu: Updated for version 1.9.5.
> python/python-gattlib: Added (Bluetooth LE protocol library).
> python/pytz: Updated for version 2016.10.
> python/vobject: Updated for version 0.9.3.
> ruby/ruby-build: Updated for version 20170112.
> ruby/ruby-faraday: Updated for version 0.11.0.
> ruby/ruby-json: Updated for version 2.0.3.
> ruby/rubygem-bundler: Updated for version 1.13.7.
> system/Iosevka: Updated for version 1.10.3.
> system/apache-tomcat: Fix packaged /var/tmp permissions.
> system/borgbackup: Updated for version 1.0.9.
> system/fasd: Added (Command-line productivity booster).
> system/gnome-commander: Compile glib schemas in doinst.sh.
> system/iucode_tool: Updated for version 2.1.1.
> system/osinfo-db-tools: Added (operating systems database tools).
> system/osinfo-db: Added (operating systems database).
> system/rsyslog: Updated for version 8.24.0.
> system/sbotools: Updated for version 2.1.
> system/vtcol: Added (Colour schemes for the Linux console).
> system/worker: Updated for version 3.8.5.
> +--------------------------+
> 

>telegram 1.0
Oh, no. Why they made a new design? The old was better!

From yalhcru at gmail.com  Sun Jan 15 10:39:57 2017
From: yalhcru at gmail.com (B Watson)
Date: Sun, 15 Jan 2017 05:39:57 -0500
Subject: [Slackbuilds-users] md5sum mismatch for games/doomretro
Message-ID: <CAN1hMuCOyXUXSejFRFPEmBQ3i9Joj65h4g+xqMkgb0muziAY-g@mail.gmail.com>

$ grep MD5SUM= *.info ; md5sum *gz
MD5SUM="20d946330c91c1b5ac26d8f9a0a86c28"
5d8d135bf4198fe075efcd3366a0c3cd  doomretro-2.3.9.tar.gz

Package seems to build & run OK.

From willysr at slackbuilds.org  Sun Jan 15 10:54:36 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 15 Jan 2017 17:54:36 +0700
Subject: [Slackbuilds-users] md5sum mismatch for games/doomretro
In-Reply-To: <CAN1hMuCOyXUXSejFRFPEmBQ3i9Joj65h4g+xqMkgb0muziAY-g@mail.gmail.com>
References: <CAN1hMuCOyXUXSejFRFPEmBQ3i9Joj65h4g+xqMkgb0muziAY-g@mail.gmail.com>
Message-ID: <e3cb259d-2707-b978-1fd8-b9083fe9023b@slackbuilds.org>

> $ grep MD5SUM= *.info ; md5sum *gz
> MD5SUM="20d946330c91c1b5ac26d8f9a0a86c28"
> 5d8d135bf4198fe075efcd3366a0c3cd  doomretro-2.3.9.tar.gz

Fixed in my branch

Thanks

-- 
Willy Sudiarto Raharjo

-------------- 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/20170115/0f4e827a/attachment.asc>

From atelszewski at gmail.com  Sun Jan 15 13:20:07 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 15 Jan 2017 14:20:07 +0100
Subject: [Slackbuilds-users] Python packages missing dependencies: should we
 report them?
Message-ID: <080e162e-5ae8-61b6-c421-f579e7621992@gmail.com>

Hi,

Some time ago I raised the problem of building Python package 
(borgbackup) in chroot environment, which has no Internet connection.
It turned out that the build fails, because Python setup procedure was 
not able to download some required dependencies.
I then added the dependency to REQUIRES and the package builds fine in 
chroot without network connection.

I now encountered this exact problem when trying to build protobuf package.
It fails to build because of missing google-apputils dependency.
If I was building in an environment with network connection, 
google-apputils would be downloaded automatically and the build (I 
guess) would succeed.

My question is:
should we consider this a bug and report missing dependency?

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Sun Jan 15 16:59:10 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 15 Jan 2017 23:59:10 +0700
Subject: [Slackbuilds-users] Python packages missing dependencies:
 should we report them?
In-Reply-To: <080e162e-5ae8-61b6-c421-f579e7621992@gmail.com>
References: <080e162e-5ae8-61b6-c421-f579e7621992@gmail.com>
Message-ID: <11f1fa79-11fd-4f7a-62c5-226be67f6ebf@slackbuilds.org>

> Some time ago I raised the problem of building Python package
> (borgbackup) in chroot environment, which has no Internet connection.
> It turned out that the build fails, because Python setup procedure was
> not able to download some required dependencies.
> I then added the dependency to REQUIRES and the package builds fine in
> chroot without network connection.
> 
> I now encountered this exact problem when trying to build protobuf package.
> It fails to build because of missing google-apputils dependency.
> If I was building in an environment with network connection,
> google-apputils would be downloaded automatically and the build (I
> guess) would succeed.
> 
> My question is:
> should we consider this a bug and report missing dependency?

perhaps most of us missed it since not everyone is looking at the build
process everytime and some might take a long time while the download
process occured in the middle of the process while we were away or it
just happened so fast that we didn't even notice.


-- 
Willy Sudiarto Raharjo

-------------- 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/20170115/082473e5/attachment.asc>

From matteo.bernardini at gmail.com  Sun Jan 15 17:44:35 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 15 Jan 2017 18:44:35 +0100
Subject: [Slackbuilds-users] Python packages missing dependencies:
 should we report them?
In-Reply-To: <080e162e-5ae8-61b6-c421-f579e7621992@gmail.com>
References: <080e162e-5ae8-61b6-c421-f579e7621992@gmail.com>
Message-ID: <CAPsDuS77LLBwQMoUWs_LRoq1gr9_6ZkG34ZQ8cYcXXNLHW5ndQ@mail.gmail.com>

2017-01-15 14:20 GMT+01:00 Andrzej Telszewski <atelszewski at gmail.com>:
> Hi,
>
> Some time ago I raised the problem of building Python package (borgbackup)
> in chroot environment, which has no Internet connection.
> It turned out that the build fails, because Python setup procedure was not
> able to download some required dependencies.
> I then added the dependency to REQUIRES and the package builds fine in
> chroot without network connection.
>
> I now encountered this exact problem when trying to build protobuf package.
> It fails to build because of missing google-apputils dependency.
> If I was building in an environment with network connection, google-apputils
> would be downloaded automatically and the build (I guess) would succeed.
>
> My question is:
> should we consider this a bug and report missing dependency?

yes, I'll put the maintainer in cc.

Matteo

From atelszewski at gmail.com  Sun Jan 15 18:27:59 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 15 Jan 2017 19:27:59 +0100
Subject: [Slackbuilds-users] Python packages missing dependencies:
 should we report them?
In-Reply-To: <11f1fa79-11fd-4f7a-62c5-226be67f6ebf@slackbuilds.org>
References: <080e162e-5ae8-61b6-c421-f579e7621992@gmail.com>
 <11f1fa79-11fd-4f7a-62c5-226be67f6ebf@slackbuilds.org>
Message-ID: <4bdab1b6-8c96-c7f3-af11-65d3d0803912@gmail.com>

On 15/01/17 17:59, Willy Sudiarto Raharjo wrote:
>> I now encountered this exact problem when trying to build protobuf package.
>> It fails to build because of missing google-apputils dependency.
>> If I was building in an environment with network connection,
>> google-apputils would be downloaded automatically and the build (I
>> guess) would succeed.
>>
>> My question is:
>> should we consider this a bug and report missing dependency?
> perhaps most of us missed it since not everyone is looking at the build
> process everytime and some might take a long time while the download
> process occured in the middle of the process while we were away or it
> just happened so fast that we didn't even notice.

My intention wasn't to point out admin-side bug ;-)
I was asking if this particular type of problem should be reported here 
on the list.

Matteo said "yes" in the next reply, so I'll take it as the answer ;-)

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Sun Jan 15 18:43:17 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 15 Jan 2017 19:43:17 +0100
Subject: [Slackbuilds-users] Python packages missing dependencies:
 should we report them?
In-Reply-To: <4bdab1b6-8c96-c7f3-af11-65d3d0803912@gmail.com>
References: <080e162e-5ae8-61b6-c421-f579e7621992@gmail.com>
 <11f1fa79-11fd-4f7a-62c5-226be67f6ebf@slackbuilds.org>
 <4bdab1b6-8c96-c7f3-af11-65d3d0803912@gmail.com>
Message-ID: <CAPsDuS6Y5sxg96LgCh=77Xp-tCUwrMe3bxAwtipLF-RjGUJhCQ@mail.gmail.com>

2017-01-15 19:27 GMT+01:00 Andrzej Telszewski <atelszewski at gmail.com>:
> On 15/01/17 17:59, Willy Sudiarto Raharjo wrote:
>>>
>>> I now encountered this exact problem when trying to build protobuf
>>> package.
>>> It fails to build because of missing google-apputils dependency.
>>> If I was building in an environment with network connection,
>>> google-apputils would be downloaded automatically and the build (I
>>> guess) would succeed.
>>>
>>> My question is:
>>> should we consider this a bug and report missing dependency?
>>
>> perhaps most of us missed it since not everyone is looking at the build
>> process everytime and some might take a long time while the download
>> process occured in the middle of the process while we were away or it
>> just happened so fast that we didn't even notice.
>
>
> My intention wasn't to point out admin-side bug ;-)

this wasn't clear: IMHO the bug is in the script, I find not important
at all to put the blame on someone specific, being him the maintainer
or the admin.
I'm not referring to you, but it seems there are people that find
satisfying to blame someone in particular, regarding that problems are
solved or not, while this last aspect is the only one that really
matters.

> I was asking if this particular type of problem should be reported here on
> the list.

you should report to the list and to the maintainer.

> Matteo said "yes" in the next reply, so I'll take it as the answer ;-)

don't do it :)

Matteo

From atelszewski at gmail.com  Sun Jan 15 19:16:28 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 15 Jan 2017 20:16:28 +0100
Subject: [Slackbuilds-users] Python packages missing dependencies:
 should we report them?
In-Reply-To: <CAPsDuS6Y5sxg96LgCh=77Xp-tCUwrMe3bxAwtipLF-RjGUJhCQ@mail.gmail.com>
References: <080e162e-5ae8-61b6-c421-f579e7621992@gmail.com>
 <11f1fa79-11fd-4f7a-62c5-226be67f6ebf@slackbuilds.org>
 <4bdab1b6-8c96-c7f3-af11-65d3d0803912@gmail.com>
 <CAPsDuS6Y5sxg96LgCh=77Xp-tCUwrMe3bxAwtipLF-RjGUJhCQ@mail.gmail.com>
Message-ID: <c1b83bac-ba1b-2f5f-acf8-05d308021d13@gmail.com>

On 15/01/17 19:43, Matteo Bernardini wrote:
> 2017-01-15 19:27 GMT+01:00 Andrzej Telszewski <atelszewski at gmail.com>:
>> My intention wasn't to point out admin-side bug ;-)
>
> this wasn't clear: IMHO the bug is in the script, I find not important
> at all to put the blame on someone specific, being him the maintainer
> or the admin.
> I'm not referring to you, but it seems there are people that find
> satisfying to blame someone in particular, regarding that problems are
> solved or not, while this last aspect is the only one that really
> matters.
>

That is annoying.
I always try to use proper wording, so people don't feel offended.
So, for the future, please treat all my messages as if they were not 
offending, even if they are.

Unless I explicitly write "how the hell you could put this fucking piece 
of shit in the script" ;-)

Cheers :-)

-- 
Best regards,
Andrzej Telszewski

From dpross1100 at msn.com  Mon Jan 16 04:47:37 2017
From: dpross1100 at msn.com (Daniel Prosser)
Date: Mon, 16 Jan 2017 04:47:37 +0000
Subject: [Slackbuilds-users] Error in ncmpcpp.SlackBuild
Message-ID: <SN1PR0701MB1870D472A76A420FD3CFD6FCCC7D0@SN1PR0701MB1870.namprd07.prod.outlook.com>

Hi,

Today I had trouble upgrading to the new version of ncmpcpp because of
what appears to be an error in the SlackBuild. ./autogen.sh and
./configure should be two separate commands, but they are joined
together into one by a "\" at the end of the line. Therefore, the
following errors result:

configure.ac:3: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.  For more info, see:
configure.ac:3: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.ac:11: installing './compile'
configure.ac:11: installing './config.guess'
configure.ac:11: installing './config.sub'
configure.ac:3: installing './install-sh'
configure.ac:3: installing './missing'

<<<<<<<<<<<<<<< snip >>>>>>>>>>>>>>>

src/Makefile.am: installing './depcomp'
  autoconf
make: *** No targets specified and no makefile found.  Stop.

A patch for the SlackBuild is attached.

Dan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ncmpcpp.SlackBuild.patch
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170116/6aaab5a7/attachment.ksh>

From willysr at slackbuilds.org  Mon Jan 16 05:11:36 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 16 Jan 2017 12:11:36 +0700
Subject: [Slackbuilds-users] Error in ncmpcpp.SlackBuild
In-Reply-To: <SN1PR0701MB1870D472A76A420FD3CFD6FCCC7D0@SN1PR0701MB1870.namprd07.prod.outlook.com>
References: <SN1PR0701MB1870D472A76A420FD3CFD6FCCC7D0@SN1PR0701MB1870.namprd07.prod.outlook.com>
Message-ID: <d77e70f3-de8e-56d7-e319-42acb1c26341@slackbuilds.org>

> Today I had trouble upgrading to the new version of ncmpcpp because of
> what appears to be an error in the SlackBuild. ./autogen.sh and
> ./configure should be two separate commands, but they are joined
> together into one by a "\" at the end of the line. Therefore, the
> following errors result:
> 
> configure.ac:3: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.  For more info, see:
> configure.ac:3: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
> configure.ac:11: installing './compile'
> configure.ac:11: installing './config.guess'
> configure.ac:11: installing './config.sub'
> configure.ac:3: installing './install-sh'
> configure.ac:3: installing './missing'
> 
> <<<<<<<<<<<<<<< snip >>>>>>>>>>>>>>>
> 
> src/Makefile.am: installing './depcomp'
>   autoconf
> make: *** No targets specified and no makefile found.  Stop.
> 
> A patch for the SlackBuild is attached.

Thanks
Fixed in my branch


-- 
Willy Sudiarto Raharjo

-------------- 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/20170116/579d18eb/attachment.asc>

From harald.achitz at gmail.com  Mon Jan 16 18:32:23 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Mon, 16 Jan 2017 19:32:23 +0100
Subject: [Slackbuilds-users] Orphaning some builds.
In-Reply-To: <CAPh+tzMbjKbxrJQQBP=pC5zLXji5ZGQYYHWeNi6CgpLcJsXEgA@mail.gmail.com>
References: <CAAcyf-pD313ztT8hXSTVEyfwPXv3vU+MZDvUJiU2YwY3KJtBzQ@mail.gmail.com>
 <1fc2d680-ed26-4779-bd9a-7f30b4c867c9@gmail.com>
 <CAPh+tzMbjKbxrJQQBP=pC5zLXji5ZGQYYHWeNi6CgpLcJsXEgA@mail.gmail.com>
Message-ID: <CAPh+tzOQiF6EnrkbZLA_WPTAyxdJZ_xOACff4WvavbqfWue89g@mail.gmail.com>

will take slack,
seems I have to use it for a while
going to sumbit the update to 2.3.4 soon.

/Harald

2017-01-14 11:11 GMT+01:00 Harald Achitz <harald.achitz at gmail.com>:

> Hi
> I have an updated version of the slack build (2.3.4) and can submit that.
> I can not guarantee how long I will maintain this, but maybe for a while
> since c++ channel is pretty active an dalso some colleagues at work use
> slack heavily.
> shall I submit it?
>
> /Harald
>
> 2017-01-09 22:57 GMT+01:00 Dhaby Xiloj <slack.dhabyx at gmail.com>:
>
>> I am attempting to use less non-free software, so I?ll be giving up these
>> three builds, hopefully someone is interested in them:
>>
>> multimedia/spotify
>> network/hipchat
>> network/slack
>>
>> Konpai,
>>
>> I take spotify
>>
>> --
>> Dhaby Xiloj
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://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/20170116/8dd81297/attachment.html>

From mr.chew.baka at gmail.com  Mon Jan 16 18:59:57 2017
From: mr.chew.baka at gmail.com (B-o-B De Mars)
Date: Mon, 16 Jan 2017 12:59:57 -0600
Subject: [Slackbuilds-users] rkhunter up for grabs
Message-ID: <654a62d8-2007-6da0-792f-7a307e89b6f2@gmail.com>

Hello, and a good day to you all.  I just wanted to let you all know 
that I no longer will be maintaining the rkhunter package.  I haven't 
actually used it for a couple years now.

If someone wants to take over maintenance of this package that would be 
great.

I will still maintain the other packages I have on SBO.

Thanks!

Bob De Mars

From gerardo.zamudio at linux.com  Mon Jan 16 21:58:55 2017
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Mon, 16 Jan 2017 15:58:55 -0600
Subject: [Slackbuilds-users] rkhunter up for grabs
In-Reply-To: <654a62d8-2007-6da0-792f-7a307e89b6f2@gmail.com>
References: <654a62d8-2007-6da0-792f-7a307e89b6f2@gmail.com>
Message-ID: <4f6f963e-1dbf-f363-a5cc-e1de1d764ca0@linux.com>

On 01/16/2017 12:59 PM, B-o-B De Mars wrote:
> that I no longer will be maintaining the rkhunter package.  
> 
> 
> If someone wants to take over maintenance of this package that would be
> great.
> 
> Bob De Mars
> 

I'll grab this. I use it very frequently at work.

-- 
Gerardo Zamudio


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

From mr.chew.baka at gmail.com  Tue Jan 17 05:27:15 2017
From: mr.chew.baka at gmail.com (B-o-B De Mars)
Date: Mon, 16 Jan 2017 23:27:15 -0600
Subject: [Slackbuilds-users] rkhunter up for grabs
In-Reply-To: <4f6f963e-1dbf-f363-a5cc-e1de1d764ca0@linux.com>
References: <654a62d8-2007-6da0-792f-7a307e89b6f2@gmail.com>
 <4f6f963e-1dbf-f363-a5cc-e1de1d764ca0@linux.com>
Message-ID: <a3a533d7-8875-3e76-a881-fd3e7d7cf03e@gmail.com>



On 1/16/2017 3:58 PM, Gerardo Zamudio wrote:
>
> I'll grab this. I use it very frequently at work.

Good Deal.  Thanks!

From rcaalves89 at gmail.com  Tue Jan 17 19:56:54 2017
From: rcaalves89 at gmail.com (Renan Cerqueira)
Date: Tue, 17 Jan 2017 19:56:54 +0000
Subject: [Slackbuilds-users] atom: cannot execute binary file
Message-ID: <CACP_GsA1zP2q=gF4hYS2LsiH9VJ=rS_wLTKq1W1C_im_PaR9Hg@mail.gmail.com>

Hi there,

I can build atom successfully, but it does not run, showing the following
error:
"/usr/share/atom/atom: cannot execute binary file"

I'm on 14.2 32 bit. Running "file /usr/share/atom/atom" I see that it is a
64 bit executable. Next I tried to force ARCH="" in the slackbuild script,
but the outcome still is 64 bit.

Any ideas on solving this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170117/fc3e6768/attachment.html>

From slack.dhabyx at gmail.com  Tue Jan 17 21:25:32 2017
From: slack.dhabyx at gmail.com (Dhaby Xiloj)
Date: Tue, 17 Jan 2017 15:25:32 -0600
Subject: [Slackbuilds-users] atom: cannot execute binary file
In-Reply-To: <CACP_GsA1zP2q=gF4hYS2LsiH9VJ=rS_wLTKq1W1C_im_PaR9Hg@mail.gmail.com>
References: <CACP_GsA1zP2q=gF4hYS2LsiH9VJ=rS_wLTKq1W1C_im_PaR9Hg@mail.gmail.com>
Message-ID: <9de22771-39ff-5e9c-d140-0b032e527e2e@gmail.com>

Hi
> I can build atom successfully, but it does not run, showing the
> following error:
> "/usr/share/atom/atom: cannot execute binary file"
>
> I'm on 14.2 32 bit. Running "file /usr/share/atom/atom" I see that it
> is a 64 bit executable. Next I tried to force ARCH="" in the
> slackbuild script, but the outcome still is 64 bit.
>
Sometimes npm does not correctly detect the architecture, ia32 or
x86_64, this bug appeared to have been fixed in previous versions.

You can try modifying the following lines to the slackbuild to see if
this solves the problems:

npm_config_arch=ia32 npm_config_target_arch=ia32 PYTHON=python2 \
  ./script/build --build-dir=$BUILD_DIR

-- 
Dhaby Xiloj

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

From porting at use.startmail.com  Wed Jan 18 15:03:00 2017
From: porting at use.startmail.com (=?iso-8859-1?Q?Rub=E9n?= Llorente)
Date: Wed, 18 Jan 2017 16:03:00 +0100
Subject: [Slackbuilds-users] [DEFECTIVE] net/retroshare
Message-ID: <20170118150300.GA75733@server.richard-falken.com>

The patch included with the build script for retroshare is
non-functional. In order for the build to work, the file 
RetroShare.pro.patch must be converted to a CRLF text file, and the
patch command must make use of the --binary switch. 

Failure to do so results in a failed patching process, because the 
target file is a CRLF text file, while the patch in the SlackBuild is LF
only. This causes an error because line terminations are not compatible.

-- 
OpenPGP Key Fingerprint:
BB5A C2A2 2CAD ACB7 D50D  C081 1DB9 6FC4 5AB7 92FA

From yalhcru at gmail.com  Wed Jan 18 16:35:29 2017
From: yalhcru at gmail.com (B Watson)
Date: Wed, 18 Jan 2017 11:35:29 -0500
Subject: [Slackbuilds-users] [DEFECTIVE] net/retroshare
In-Reply-To: <20170118150300.GA75733@server.richard-falken.com>
References: <20170118150300.GA75733@server.richard-falken.com>
Message-ID: <CAN1hMuCLmB=4nzvPuzizdU6p2e=8yPFTjzUvkMcYs4ZaLm1pxg@mail.gmail.com>

On 1/18/17, Rub?n Llorente <porting at use.startmail.com> wrote:
> The patch included with the build script for retroshare is
> non-functional. In order for the build to work, the file
> RetroShare.pro.patch must be converted to a CRLF text file

This is an ongoing issue. Probably the patch file as submitted was
correct, but SBo's git is configured to strip off LFs from any text
files checked in. Apparently this happens *after* testing and approval
is complete (otherwise whoever tested it would catch the problem).

Best solution I know for this: Maintainers, if your patches have CRLF
endings, gzip them before submitting, and have your SlackBuild do:

zcat $CWD/patchname.diff.gz | patch -p1    # or -p0 or whatever's needed

From baildon.research at googlemail.com  Wed Jan 18 16:52:14 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Wed, 18 Jan 2017 16:52:14 +0000
Subject: [Slackbuilds-users] [DEFECTIVE] net/retroshare
In-Reply-To: <CAN1hMuCLmB=4nzvPuzizdU6p2e=8yPFTjzUvkMcYs4ZaLm1pxg@mail.gmail.com>
References: <20170118150300.GA75733@server.richard-falken.com>
 <CAN1hMuCLmB=4nzvPuzizdU6p2e=8yPFTjzUvkMcYs4ZaLm1pxg@mail.gmail.com>
Message-ID: <CAMt7G9RhOHniNznxhksFowWmyMZPCgANe7QsVPxn2jEnLAXWyA@mail.gmail.com>

> This is an ongoing issue. Probably the patch file as submitted was
> correct, but SBo's git is configured to strip off LFs from any text
> files checked in. Apparently this happens *after* testing and approval
> is complete (otherwise whoever tested it would catch the problem).
>
> Best solution I know for this: Maintainers, if your patches have CRLF
> endings, gzip them before submitting, and have your SlackBuild do:
>
> zcat $CWD/patchname.diff.gz | patch -p1    # or -p0 or whatever's needed

Agreed, and good advice. Sadly git and patch handle CR LF endings in
contradictory ways. I *think* my git is setup ok, and I fixed spdlog
for the same problem three days ago, so I'll fix this one too.

Thanks everybody
-D.

From baildon.research at googlemail.com  Wed Jan 18 20:19:19 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Wed, 18 Jan 2017 20:19:19 +0000
Subject: [Slackbuilds-users] [DEFECTIVE] net/retroshare
In-Reply-To: <CAMt7G9RhOHniNznxhksFowWmyMZPCgANe7QsVPxn2jEnLAXWyA@mail.gmail.com>
References: <20170118150300.GA75733@server.richard-falken.com>
 <CAN1hMuCLmB=4nzvPuzizdU6p2e=8yPFTjzUvkMcYs4ZaLm1pxg@mail.gmail.com>
 <CAMt7G9RhOHniNznxhksFowWmyMZPCgANe7QsVPxn2jEnLAXWyA@mail.gmail.com>
Message-ID: <CAMt7G9Q=bfAe1WS+eZL9VSPVEzGd1PCsJ6u2z454UqL+WCgL4w@mail.gmail.com>

Now that I have looked (!) Alan Aversa has already contributed an
update for retroshare in Willy's branch that does not need a patch. It
will arrive for everybody in the next public update.

Thanks Alan!
-D.

From willysr at slackbuilds.org  Wed Jan 18 23:36:33 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 19 Jan 2017 06:36:33 +0700
Subject: [Slackbuilds-users] [DEFECTIVE] net/retroshare
In-Reply-To: <CAMt7G9Q=bfAe1WS+eZL9VSPVEzGd1PCsJ6u2z454UqL+WCgL4w@mail.gmail.com>
References: <20170118150300.GA75733@server.richard-falken.com>
 <CAN1hMuCLmB=4nzvPuzizdU6p2e=8yPFTjzUvkMcYs4ZaLm1pxg@mail.gmail.com>
 <CAMt7G9RhOHniNznxhksFowWmyMZPCgANe7QsVPxn2jEnLAXWyA@mail.gmail.com>
 <CAMt7G9Q=bfAe1WS+eZL9VSPVEzGd1PCsJ6u2z454UqL+WCgL4w@mail.gmail.com>
Message-ID: <ac78a88d-1af8-ba92-a6f5-d49dc5da212e@slackbuilds.org>

> Now that I have looked (!) Alan Aversa has already contributed an
> update for retroshare in Willy's branch that does not need a patch. It
> will arrive for everybody in the next public update.

I think it's already merged in last public update


-- 
Willy Sudiarto Raharjo

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

From glenn.becker at gmail.com  Thu Jan 19 17:08:54 2017
From: glenn.becker at gmail.com (Glenn Becker)
Date: Thu, 19 Jan 2017 12:08:54 -0500
Subject: [Slackbuilds-users] Fwd: Slackbuild mendeleydesktop
In-Reply-To: <1cb1b0a8-2884-fdda-3c95-b50df8ce3af0@uky.edu>
References: <1cb1b0a8-2884-fdda-3c95-b50df8ce3af0@uky.edu>
Message-ID: <CANCo2a0kq=JNszimHMHeMRAPd+KFg0kaNUGaxRq8PNQGEMS-4g@mail.gmail.com>

Hi -

I told this user I'd pass his report on.

Thanks,

Glenn

<http://projecteuler.net/profile/gbecker.png>

---------- Forwarded message ----------
From: Russell Lee Carden <russell.l.carden at uky.edu>
Date: Thu, Jan 19, 2017 at 11:50 AM
Subject: Slackbuild mendeleydesktop
To: glenn.becker at gmail.com


Hello Glenn Becker,
I was going to test out mendeley using the slackbuild that you are
maintaining.  The version that is currently on slackbuilds.org requires
qt5.  The source comes with it but the slackbuild strips it.  It would
probably be easier if mendeley  was installed in the /opt directory.
Regards,
Russell Carden
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170119/26e9167f/attachment-0001.html>

From mchagas at member.fsf.org  Thu Jan 19 17:09:23 2017
From: mchagas at member.fsf.org (Maykon Chagas)
Date: Thu, 19 Jan 2017 15:09:23 -0200
Subject: [Slackbuilds-users] Update request Docker
Message-ID: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>

Hi everyone!

Is there any possibility to update Docker version on Slackbuild?

Currently the version on Slackbuild is 1.8.2 and Docker release is 1.13.0.

Would the mantainer from Docker Slackbuild could upgrade to at least >
1.10.0?

Thanks

Kind regards.

From ryanpcmcquen at member.fsf.org  Thu Jan 19 17:12:58 2017
From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen)
Date: Thu, 19 Jan 2017 09:12:58 -0800
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
Message-ID: <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>

On Jan 19, 2017 9:11 AM, "Maykon Chagas" <mchagas at member.fsf.org> wrote:

Hi everyone!

Is there any possibility to update Docker version on Slackbuild?

Currently the version on Slackbuild is 1.8.2 and Docker release is 1.13.0.

Would the mantainer from Docker Slackbuild could upgrade to at least >
1.10.0?



Did you email the maintainer?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170119/f29b37f6/attachment.html>

From mchagas at member.fsf.org  Thu Jan 19 17:43:43 2017
From: mchagas at member.fsf.org (Maykon Chagas)
Date: Thu, 19 Jan 2017 15:43:43 -0200
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
Message-ID: <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>

Hi Ryan,

Your answers came directly to me.

Ok, I'll do this!

Thanks!

Kind regars,

Em 01/19/2017 03:22 PM, Ryan P.C. McQuen escreveu:
> On 1/19/17, Maykon Chagas <mchagas at riseup.net> wrote:
>> Hi Ryan,
>>
>> Sorry. No. That's the flow? Ask directly the mantainer?
> 
> 
> Usually it's better to ask the maintainer first, and then this list if
> there is no prompt response from the maintainer. Not all maintainers
> are subscribed to this list.
> 

From nuncestbibendum at excite.com  Thu Jan 19 17:46:46 2017
From: nuncestbibendum at excite.com (Full Name)
Date: Thu, 19 Jan 2017 12:46:46 -0500
Subject: [Slackbuilds-users] Package versions
Message-ID: <20170119124646.29147@web007.roc2.bluetie.com>

As a long time user of Slackware, I am immensely grateful to the people who have volunteered (and continue to do so) their time and effort to maintain and update third-party code, so that the rest of us Slackware users can painlessly and easily build the necessary software by using the resources in Slackbuilds (and sbopkpg.) Once again, kudos and appreciation to you.

Having said that, all too often maintainers do not update the software all that promptly. It is not uncommon to have Slackbuilds packages that are several releases behind what one can get from distributions like (shudder) Fedora or (shudder!) Ubuntu. This can be a critical issue - I have been in the position of the gentleman who enquired about docker, and I eventually had to install an Ubuntu VM in my Slackware box, for the docker version in Slackware is just too old for what I needed to do. Unfortunately, pinging maintainers does not always work. In fact, having tried that myself in connection to other packages, I never got any replies, and the relevant packages remain behind the current versions.

I understand that maintainers cannot (indeed, should not) be forced to do anything in particular. Heck, they do what they do in their spare time, with no remuneration, out of the goodness of their heart, and a sense of community. For which we are all, I am sure, very thankful. I also understand that they may happy legitimate reasons not to update their packages. However, I wonder if maintainers could be a bit more proactive and responsible about their packages? If you assume the responsibility of maintaining Slackware packages, do assume the responsibility; do a good job of it. If that is too big a burden on your time, just relinquish such responsibility, as we see some do, every so often. But, please, do not stay as the official maintainer while at the same time you silently ignore the requests that you get from people. If nothing else, that taints Slackware's reputation.

One of the ripostes that I am bound to get here is, Why don't you become a maintainer yourself? Well, that is not the point. I, for one, do not have the time, knowledge, and drive to become a maintainer. Not everybody does have what it takes. I just think that Slackware is the best Linux distribution for me, and I want to be able to use the best software that I can under Slackware. I can occasionally install, by hand, newer versions of software packages than those in Slackbuilds - but that defeats the purpose of Slackbuilds. Also, sometimes I just do not have the expertise - the docker case is one example. 

I expect that some will dismiss all this retorting "If Slackware is too difficult for you then use Ubuntu (or whatever) instead." Well, they may be right; I might have to end up doing so. However, before taking such a radical step, I'd rather appeal to the maintainers' sense of pride in what they are doing, while I will risk all the abuse and derogatory comments that such a thing might elicit from some. I love Slackware, I want to carry on using it, but I would like to have the most up-to-date Slackware packages across the board.

I hope nobody will be offended by this, for it is not my intent to offend anyone. 

From ryanpcmcquen at member.fsf.org  Thu Jan 19 18:01:15 2017
From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen)
Date: Thu, 19 Jan 2017 10:01:15 -0800
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170119124646.29147@web007.roc2.bluetie.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
Message-ID: <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>

On 1/19/17, Full Name <nuncestbibendum at excite.com> wrote:
> As a long time user of Slackware, I am immensely grateful to the people who
> have volunteered (and continue to do so) their time and effort to maintain
> and update third-party code, so that the rest of us Slackware users can
> painlessly and easily build the necessary software by using the resources in
> Slackbuilds (and sbopkpg.) Once again, kudos and appreciation to you.
>
> Having said that, all too often maintainers do not update the software all
> that promptly. It is not uncommon to have Slackbuilds packages that are
> several releases behind what one can get from distributions like (shudder)
> Fedora or (shudder!) Ubuntu. This can be a critical issue - I have been in
> the position of the gentleman who enquired about docker, and I eventually
> had to install an Ubuntu VM in my Slackware box, for the docker version in
> Slackware is just too old for what I needed to do. Unfortunately, pinging
> maintainers does not always work. In fact, having tried that myself in
> connection to other packages, I never got any replies, and the relevant
> packages remain behind the current versions.
>
> I understand that maintainers cannot (indeed, should not) be forced to do
> anything in particular. Heck, they do what they do in their spare time, with
> no remuneration, out of the goodness of their heart, and a sense of
> community. For which we are all, I am sure, very thankful. I also understand
> that they may happy legitimate reasons not to update their packages.
> However, I wonder if maintainers could be a bit more proactive and
> responsible about their packages? If you assume the responsibility of
> maintaining Slackware packages, do assume the responsibility; do a good job
> of it. If that is too big a burden on your time, just relinquish such
> responsibility, as we see some do, every so often. But, please, do not stay
> as the official maintainer while at the same time you silently ignore the
> requests that you get from people. If nothing else, that taints Slackware's
> reputation.
>
> One of the ripostes that I am bound to get here is, Why don't you become a
> maintainer yourself? Well, that is not the point. I, for one, do not have
> the time, knowledge, and drive to become a maintainer. Not everybody does
> have what it takes. I just think that Slackware is the best Linux
> distribution for me, and I want to be able to use the best software that I
> can under Slackware. I can occasionally install, by hand, newer versions of
> software packages than those in Slackbuilds - but that defeats the purpose
> of Slackbuilds. Also, sometimes I just do not have the expertise - the
> docker case is one example.
>
> I expect that some will dismiss all this retorting "If Slackware is too
> difficult for you then use Ubuntu (or whatever) instead." Well, they may be
> right; I might have to end up doing so. However, before taking such a
> radical step, I'd rather appeal to the maintainers' sense of pride in what
> they are doing, while I will risk all the abuse and derogatory comments that
> such a thing might elicit from some. I love Slackware, I want to carry on
> using it, but I would like to have the most up-to-date Slackware packages
> across the board.



Honestly if the maintainer is not responsive (I have not found this to
be the case very often), it is time for someone else to take over the
package. The list should be alerted and hopefully someone will
volunteer.

Most times editing the VERSION number and downloading a newer tarball
is enough though. So saying that you can't have the latest version
because of the maintainer is a bit of a straw man.

-- 
-Ryan
[ryanpcmcquen.org]


From slack at lodpp.net  Thu Jan 19 18:09:51 2017
From: slack at lodpp.net (slackware stuff)
Date: Thu, 19 Jan 2017 18:09:51 +0000
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>,
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
Message-ID: <51a96162e8be46bc9ee72beec2442dba@lodpp.net>

Hi Ryan, Maykon,

I've made a modified version for docker 1.12 and compiles fine ( should be okay for  1.13 though )if you are interested.

I've contacted Vincent Batts  about the need for update
He responds couple a days ago that Assaf is taking charge for the docker ( and I didn't got time to look for assaf email on the ml archive / sb site )

Best regards,

Nico



________________________________________
De : SlackBuilds-users <slackbuilds-users-bounces at slackbuilds.org> de la part de Maykon Chagas <mchagas at member.fsf.org>
Envoy? : jeudi 19 janvier 2017 18:43
? : slackbuilds-users at slackbuilds.org
Objet : Re: [Slackbuilds-users] Update request Docker

Hi Ryan,

Your answers came directly to me.

Ok, I'll do this!

Thanks!

Kind regars,

Em 01/19/2017 03:22 PM, Ryan P.C. McQuen escreveu:
> On 1/19/17, Maykon Chagas <mchagas at riseup.net> wrote:
>> Hi Ryan,
>>
>> Sorry. No. That's the flow? Ask directly the mantainer?
>
>
> Usually it's better to ask the maintainer first, and then this list if
> there is no prompt response from the maintainer. Not all maintainers
> are subscribed to this list.
>
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


From reedych at reedych.pw  Thu Jan 19 18:12:22 2017
From: reedych at reedych.pw (Reedych)
Date: Fri, 20 Jan 2017 00:12:22 +0600
Subject: [Slackbuilds-users] Package versions
Message-ID: <20170119211230.CUFidUoJ@smtp1h.mail.yandex.net>

I think that slackware is easiers from ubuntu. That's my experience. Updates? Slackware's more stable. Need additional software? Slackbuilds.org. Yes, maintainers can don't update his software, but in 95% only VERSION variable update is needed.

19 ???. 2017 ?. 23:46 ???????????? Full Name <nuncestbibendum at excite.com> ???????:
>
> As a long time user of Slackware, I am immensely grateful to the people who have volunteered (and continue to do so) their time and effort to maintain and update third-party code, so that the rest of us Slackware users can painlessly and easily build the necessary software by using the resources in Slackbuilds (and sbopkpg.) Once again, kudos and appreciation to you. 
>
> Having said that, all too often maintainers do not update the software all that promptly. It is not uncommon to have Slackbuilds packages that are several releases behind what one can get from distributions like (shudder) Fedora or (shudder!) Ubuntu. This can be a critical issue - I have been in the position of the gentleman who enquired about docker, and I eventually had to install an Ubuntu VM in my Slackware box, for the docker version in Slackware is just too old for what I needed to do. Unfortunately, pinging maintainers does not always work. In fact, having tried that myself in connection to other packages, I never got any replies, and the relevant packages remain behind the current versions. 
>
> I understand that maintainers cannot (indeed, should not) be forced to do anything in particular. Heck, they do what they do in their spare time, with no remuneration, out of the goodness of their heart, and a sense of community. For which we are all, I am sure, very thankful. I also understand that they may happy legitimate reasons not to update their packages. However, I wonder if maintainers could be a bit more proactive and responsible about their packages? If you assume the responsibility of maintaining Slackware packages, do assume the responsibility; do a good job of it. If that is too big a burden on your time, just relinquish such responsibility, as we see some do, every so often. But, please, do not stay as the official maintainer while at the same time you silently ignore the requests that you get from people. If nothing else, that taints Slackware's reputation. 
>
> One of the ripostes that I am bound to get here is, Why don't you become a maintainer yourself? Well, that is not the point. I, for one, do not have the time, knowledge, and drive to become a maintainer. Not everybody does have what it takes. I just think that Slackware is the best Linux distribution for me, and I want to be able to use the best software that I can under Slackware. I can occasionally install, by hand, newer versions of software packages than those in Slackbuilds - but that defeats the purpose of Slackbuilds. Also, sometimes I just do not have the expertise - the docker case is one example. 
>
> I expect that some will dismiss all this retorting "If Slackware is too difficult for you then use Ubuntu (or whatever) instead." Well, they may be right; I might have to end up doing so. However, before taking such a radical step, I'd rather appeal to the maintainers' sense of pride in what they are doing, while I will risk all the abuse and derogatory comments that such a thing might elicit from some. I love Slackware, I want to carry on using it, but I would like to have the most up-to-date Slackware packages across the board. 
>
> I hope nobody will be offended by this, for it is not my intent to offend anyone. 
> _______________________________________________ 
> SlackBuilds-users mailing list 
> SlackBuilds-users at slackbuilds.org 
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users 
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ 
> FAQ - https://slackbuilds.org/faq/ 
>

From am.marconi at gmx.com  Thu Jan 19 18:25:24 2017
From: am.marconi at gmx.com (Andrea Maria Marconi)
Date: Thu, 19 Jan 2017 19:25:24 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170119124646.29147@web007.roc2.bluetie.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
Message-ID: <199d800d-8791-bb55-cccc-83e9d10992e1@gmx.com>

Hi all,

I'd like to add my personal thanks to all the people contributing to the
fantastic SBo repository.

I'm not a professional user as I use Slackware (the first I installed
was 7.1 now I run the 14.2 release) for all my not-work activities but I
have never found a buggy package in SBo. It happened recently. I was not
able to build a package. I asked to the list and I got an answer in 20
minutes that solved the matter.

Please do no take this as criticism to the author of this original mail.
I do understand that every group of people who share a "common space" as
can be a player's club or a software repository, need rules and people
must comply to these rules.

I use Slackware because I do prefer an old but stable software version
instead of the last but maybe unstable (as happened to me with two
Ubuntu releases). And, BTW Slackware is the only Linux distribution in
which one can run 4 graphical session at same time on the same machine.
I was never able to do so with Suse, Ubuntu, and a lot of other older
distros (maybe I'm not very skilled but...).

Thanks to all again,
Andrea


On 19/01/2017 18:46, Full Name wrote:
> As a long time user of Slackware, I am immensely grateful to the people who have volunteered (and continue to do so) their time and effort to maintain and update third-party code, so that the rest of us Slackware users can painlessly and easily build the necessary software by using the resources in Slackbuilds (and sbopkpg.) Once again, kudos and appreciation to you.
>
> Having said that, all too often maintainers do not update the software all that promptly. It is not uncommon to have Slackbuilds packages that are several releases behind what one can get from distributions like (shudder) Fedora or (shudder!) Ubuntu. This can be a critical issue - I have been in the position of the gentleman who enquired about docker, and I eventually had to install an Ubuntu VM in my Slackware box, for the docker version in Slackware is just too old for what I needed to do. Unfortunately, pinging maintainers does not always work. In fact, having tried that myself in connection to other packages, I never got any replies, and the relevant packages remain behind the current versions.
>
> I understand that maintainers cannot (indeed, should not) be forced to do anything in particular. Heck, they do what they do in their spare time, with no remuneration, out of the goodness of their heart, and a sense of community. For which we are all, I am sure, very thankful. I also understand that they may happy legitimate reasons not to update their packages. However, I wonder if maintainers could be a bit more proactive and responsible about their packages? If you assume the responsibility of maintaining Slackware packages, do assume the responsibility; do a good job of it. If that is too big a burden on your time, just relinquish such responsibility, as we see some do, every so often. But, please, do not stay as the official maintainer while at the same time you silently ignore the requests that you get from people. If nothing else, that taints Slackware's reputation.
>
> One of the ripostes that I am bound to get here is, Why don't you become a maintainer yourself? Well, that is not the point. I, for one, do not have the time, knowledge, and drive to become a maintainer. Not everybody does have what it takes. I just think that Slackware is the best Linux distribution for me, and I want to be able to use the best software that I can under Slackware. I can occasionally install, by hand, newer versions of software packages than those in Slackbuilds - but that defeats the purpose of Slackbuilds. Also, sometimes I just do not have the expertise - the docker case is one example. 
>
> I expect that some will dismiss all this retorting "If Slackware is too difficult for you then use Ubuntu (or whatever) instead." Well, they may be right; I might have to end up doing so. However, before taking such a radical step, I'd rather appeal to the maintainers' sense of pride in what they are doing, while I will risk all the abuse and derogatory comments that such a thing might elicit from some. I love Slackware, I want to carry on using it, but I would like to have the most up-to-date Slackware packages across the board.
>
> I hope nobody will be offended by this, for it is not my intent to offend anyone. 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>



From mchagas at member.fsf.org  Thu Jan 19 18:25:11 2017
From: mchagas at member.fsf.org (Maykon Chagas)
Date: Thu, 19 Jan 2017 16:25:11 -0200
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
Message-ID: <9d71b915-3b49-ebb5-a35b-c68840ddcadd@riseup.net>

Hi Nico,

I would appreciate if you share your Slackbuild script.

I would say that! Vicent Batts a long time ago, said that will  out of
Slackware and the packages he are a manteiner, would be orphaned.

Well, just FYI Nico, the email from Assaf on Slackbuild.org
mailto:asaf at sysbind dot co dot il

Thanks for all!

Em 01/19/2017 04:09 PM, slackware stuff escreveu:
> Hi Ryan, Maykon,
> 
> I've made a modified version for docker 1.12 and compiles fine ( should be okay for  1.13 though )if you are interested.
> 
> I've contacted Vincent Batts  about the need for update
> He responds couple a days ago that Assaf is taking charge for the docker ( and I didn't got time to look for assaf email on the ml archive / sb site )
> 
> Best regards,
> 
> Nico
> 
> 
> 
> ________________________________________
> De : SlackBuilds-users <slackbuilds-users-bounces at slackbuilds.org> de la part de Maykon Chagas <mchagas at member.fsf.org>
> Envoy? : jeudi 19 janvier 2017 18:43
> ? : slackbuilds-users at slackbuilds.org
> Objet : Re: [Slackbuilds-users] Update request Docker
> 
> Hi Ryan,
> 
> Your answers came directly to me.
> 
> Ok, I'll do this!
> 
> Thanks!
> 
> Kind regars,
> 
> Em 01/19/2017 03:22 PM, Ryan P.C. McQuen escreveu:
>> On 1/19/17, Maykon Chagas <mchagas at riseup.net> wrote:
>>> Hi Ryan,
>>>
>>> Sorry. No. That's the flow? Ask directly the mantainer?
>>
>>
>> Usually it's better to ask the maintainer first, and then this list if
>> there is no prompt response from the maintainer. Not all maintainers
>> are subscribed to this list.
>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From nuncestbibendum at excite.com  Thu Jan 19 18:30:58 2017
From: nuncestbibendum at excite.com (Full Name)
Date: Thu, 19 Jan 2017 13:30:58 -0500
Subject: [Slackbuilds-users] Package versions
Message-ID: <20170119133058.25527@web005.roc2.bluetie.com>



-----Original Message-----
From: "Ryan P.C. McQuen" [ryanpcmcquen at member.fsf.org]
Date: 01/19/2017 01:01 PM
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] Package versions

On 1/19/17, Full Name <nuncestbibendum at excite.com> wrote:
> As a long time user of Slackware, I am immensely grateful to the people who
> have volunteered (and continue to do so) their time and effort to maintain
> and update third-party code, so that the rest of us Slackware users can
> painlessly and easily build the necessary software by using the resources in
> Slackbuilds (and sbopkpg.) Once again, kudos and appreciation to you.
>
> Having said that, all too often maintainers do not update the software all
> that promptly. It is not uncommon to have Slackbuilds packages that are
> several releases behind what one can get from distributions like (shudder)
> Fedora or (shudder!) Ubuntu. This can be a critical issue - I have been in
> the position of the gentleman who enquired about docker, and I eventually
> had to install an Ubuntu VM in my Slackware box, for the docker version in
> Slackware is just too old for what I needed to do. Unfortunately, pinging
> maintainers does not always work. In fact, having tried that myself in
> connection to other packages, I never got any replies, and the relevant
> packages remain behind the current versions.
>
> I understand that maintainers cannot (indeed, should not) be forced to do
> anything in particular. Heck, they do what they do in their spare time, with
> no remuneration, out of the goodness of their heart, and a sense of
> community. For which we are all, I am sure, very thankful. I also understand
> that they may happy legitimate reasons not to update their packages.
> However, I wonder if maintainers could be a bit more proactive and
> responsible about their packages? If you assume the responsibility of
> maintaining Slackware packages, do assume the responsibility; do a good job
> of it. If that is too big a burden on your time, just relinquish such
> responsibility, as we see some do, every so often. But, please, do not stay
> as the official maintainer while at the same time you silently ignore the
> requests that you get from people. If nothing else, that taints Slackware's
> reputation.
>
> One of the ripostes that I am bound to get here is, Why don't you become a
> maintainer yourself? Well, that is not the point. I, for one, do not have
> the time, knowledge, and drive to become a maintainer. Not everybody does
> have what it takes. I just think that Slackware is the best Linux
> distribution for me, and I want to be able to use the best software that I
> can under Slackware. I can occasionally install, by hand, newer versions of
> software packages than those in Slackbuilds - but that defeats the purpose
> of Slackbuilds. Also, sometimes I just do not have the expertise - the
> docker case is one example.
>
> I expect that some will dismiss all this retorting "If Slackware is too
> difficult for you then use Ubuntu (or whatever) instead." Well, they may be
> right; I might have to end up doing so. However, before taking such a
> radical step, I'd rather appeal to the maintainers' sense of pride in what
> they are doing, while I will risk all the abuse and derogatory comments that
> such a thing might elicit from some. I love Slackware, I want to carry on
> using it, but I would like to have the most up-to-date Slackware packages
> across the board.



>> Honestly if the maintainer is not responsive (I have not found this to
>> be the case very often), it is time for someone else to take over the
>> package. The list should be alerted and hopefully someone will
>> volunteer.
>>
>> Most times editing the VERSION number and downloading a newer tarball
>> is enough though. So saying that you can't have the latest version
>> because of the maintainer is a bit of a straw man.

I would agree (mostly, not entirely) with you when talking about packages with no explicit Slackbuilds dependencies. However, some packages have extensive lists of dependencies, which may in turn have their own lists of dependencies, and potentially so on. Often, the actual version numbers in those dependencies is critical. To make things more hairy, the maintainers of some of those dependencies will, in general, not be the same as that of the target one. I understand that, for these reasons, maintaining something like, say, ffmpeg, is a pain in the neck. But that is also where the real value lies; maintaining a piece of software that entails little more than doing "./configure ; make", while useful, does not come in with as much added value - even an ignoramus like me can (in general - not always) build such software.


-- 
-Ryan
[ryanpcmcquen.org]

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




From northrup at yellowapple.us  Thu Jan 19 18:28:32 2017
From: northrup at yellowapple.us (Ryan S. Northrup)
Date: Thu, 19 Jan 2017 10:28:32 -0800
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170119124646.29147@web007.roc2.bluetie.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
Message-ID: <2c4c3d63-ac50-4a7d-5da0-bc17c5d246e7@yellowapple.us>

On 01/19/2017 09:46 AM, Full Name wrote:
> It is not uncommon to have Slackbuilds packages that are several releases behind what one can get from distributions like (shudder) Fedora or (shudder!) Ubuntu.
It is not uncommon to have packages in Slackware itself that are several 
releases behind what one can get from other distributions. :)

Point being, there are distros out there that feature the 
latest-and-greatest software.  Slackware ain't one of them; it's a more 
conservative distro (not as severe as, say, Debian or Red Hat, but it's 
no Arch, either), and it's therefore unsurprising that SlackBuilds.org 
might fall into the same sort of realm.

That said, there ain't anything wrong with emailing a maintainer to let 
them know about newer software versions and ask about status (even 
better if you've tried building with the existing SlackBuild and 
verified that it still works with the new software version). Sometimes 
folks simply miss the announcements for new versions. Sometimes folks 
stop using that program and forget that they're still the maintainer.  
Sometimes there's a technical or even political reason why a certain 
version is on SBo instead of the latest and greatest.  It really depends 
on the SlackBuild.
> I expect that some will dismiss all this retorting "If Slackware is too difficult for you then use Ubuntu (or whatever) instead." Well, they may be right; I might have to end up doing so. However, before taking such a radical step, I'd rather appeal to the maintainers' sense of pride in what they are doing, while I will risk all the abuse and derogatory comments that such a thing might elicit from some. I love Slackware, I want to carry on using it, but I would like to have the most up-to-date Slackware packages across the board.
As a maintainer (albeit a rather new one), I'd by no means dismiss such 
"retorting".  I actually agree with it for the most part.

With that said, like the other Ryan mentioned, most SlackBuilds work 
fine with software versions newer than the ones for which they're 
advertised.  There are a few exceptions (like CouchDB, which totally 
switched up its build procedure, hence why I've yet to update it to the 
2.x series), but usually all it takes is to change the $VERSION variable 
in the SlackBuild to the one matching your desired software version.
>
> I hope nobody will be offended by this, for it is not my intent to offend anyone.
No offense taken :)

--
Ryan S. Northrup
northrup at yellowapple.us

From baildon.research at googlemail.com  Thu Jan 19 18:45:24 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 19 Jan 2017 18:45:24 +0000
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170119124646.29147@web007.roc2.bluetie.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
Message-ID: <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>

A few constructive thoughts --

Many years ago the advice was that we should not always update our
SlackBuilds for simple version bumps, because it's easy to use
VERSION=. But I think times have changed, git makes the whole process
easier for the admins and we are always happy to see updates.

The best time to update your SlackBuilds is maybe halfway between
Slackware releases.  So now would be a very good time for maintainers
to submit updates.  Yes, *NOW*!!  please!

We could try to show "last updated" information on more pages on the
website, however this information is already available from cgit.
Personally I don't think we want to have "flagged out-of-date" like
Arch.  But if someone wanted to start a one-off audit of the repo, it
would be a very big task but maybe helpful. There are some resources
like Anitya that might be helpful -- https://release-monitoring.org/

Maybe we should reach out to all the maintainers once a year (or so)
and ask them if they need help with particular packages, or if they
wish to continue?

As a radical idea, we could consider making some packages
auto-updating. I suspect lots of perl, python, haskell and ruby could
be completely automated. I bet everybody hates this idea :p

On the other hand, George from Salix made a very good point when he
recently wrote "SBo has a policy of constantly updating its contents
with new versions, which in my opinion is competely against
Slackware's policy (as well as our own) for stability". I do have a
lot of respect for that point of view.  I think the main reasons
against it are social not technical (too much work at one time for new
releases, need to keep maintainers involved). Having said that, for
technical reasons quite a lot of packages do need to be quite stable
between releases (haskell, ffmpeg and more -- everybody on the list
could probably name them).

There are three new messages since I started writing -- eek!!

Cheers
-D.

From myeyeismadeofglass at gmail.com  Thu Jan 19 18:47:49 2017
From: myeyeismadeofglass at gmail.com (renan)
Date: Thu, 19 Jan 2017 18:47:49 +0000
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 129, Issue 29
In-Reply-To: <mailman.1296.1484845739.1245.slackbuilds-users@slackbuilds.org>
References: <mailman.1296.1484845739.1245.slackbuilds-users@slackbuilds.org>
Message-ID: <CACP_GsBO+XM1nTO86a0Esj86uA7ctYouT0R=fbeLp3uKGOr-2g@mail.gmail.com>

> Hi
> > I can build atom successfully, but it does not run, showing the
> > following error:
> > "/usr/share/atom/atom: cannot execute binary file"
> >
> > I'm on 14.2 32 bit. Running "file /usr/share/atom/atom" I see that it
> > is a 64 bit executable. Next I tried to force ARCH="" in the
> > slackbuild script, but the outcome still is 64 bit.
> >
> Sometimes npm does not correctly detect the architecture, ia32 or
> x86_64, this bug appeared to have been fixed in previous versions.
>
> You can try modifying the following lines to the slackbuild to see if
> this solves the problems:
>
> npm_config_arch=ia32 npm_config_target_arch=ia32 PYTHON=python2 \
>   ./script/build --build-dir=$BUILD_DIR
>
> --
> Dhaby Xiloj
>
> Hello,

Thanks for your answer. Unfortunately, it did not solve the problem. Also,
the variable $BUILD_DIR is not defined in the script.

[]s
Renan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170119/14c43e9e/attachment-0001.html>

From atelszewski at gmail.com  Thu Jan 19 18:58:57 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 19 Jan 2017 19:58:57 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
Message-ID: <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>

On 19/01/17 19:45, David Spencer wrote:
> As a radical idea, we could consider making some packages
> auto-updating. I suspect lots of perl, python, haskell and ruby could
> be completely automated. I bet everybody hates this idea :p
>

You bet ;-)

> On the other hand, George from Salix made a very good point when he
> recently wrote "SBo has a policy of constantly updating its contents
> with new versions, which in my opinion is competely against
> Slackware's policy (as well as our own) for stability". I do have a
> lot of respect for that point of view.  I think the main reasons
> against it are social not technical (too much work at one time for new
> releases, need to keep maintainers involved). Having said that, for
> technical reasons quite a lot of packages do need to be quite stable
> between releases (haskell, ffmpeg and more -- everybody on the list
> could probably name them).

I don't exactly agree.
There are multiple situations where updating the package makes a lot of 
sense.
Be it security, or new features that save your time.

On the other side, how often do we see a breakage here?

As you said, there are packages that won't see an update without very 
good reason.
I think the crew is doing very well on that matter.

When it comes to Slackware, well, it's the core of everything.
The less updates it sees, the better.
I guess we are all happy for Pat's policy.

-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Thu Jan 19 19:36:11 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 19 Jan 2017 19:36:11 +0000
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <9d71b915-3b49-ebb5-a35b-c68840ddcadd@riseup.net>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
 <9d71b915-3b49-ebb5-a35b-c68840ddcadd@riseup.net>
Message-ID: <CAMt7G9QdoRO03Ve2xBRsBor=deTip31MBDT_CZR6X9JmVKv=GQ@mail.gmail.com>

> I would say that! Vicent Batts a long time ago, said that will  out of
> Slackware and the packages he are a manteiner, would be orphaned.

vbatts submitted two new SlackBuilds earlier today, and they look
*very* interesting and useful :)

-D.

From mchagas at member.fsf.org  Thu Jan 19 19:42:38 2017
From: mchagas at member.fsf.org (Maykon Chagas)
Date: Thu, 19 Jan 2017 17:42:38 -0200
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <CAMt7G9QdoRO03Ve2xBRsBor=deTip31MBDT_CZR6X9JmVKv=GQ@mail.gmail.com>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
 <9d71b915-3b49-ebb5-a35b-c68840ddcadd@riseup.net>
 <CAMt7G9QdoRO03Ve2xBRsBor=deTip31MBDT_CZR6X9JmVKv=GQ@mail.gmail.com>
Message-ID: <2ed50221-14ed-1178-9301-b6c94411481a@riseup.net>

Really? This is awesome! I apologize, I thought that he is out.
So, it's great he continue to contribute.


Em 01/19/2017 05:36 PM, David Spencer escreveu:
>> I would say that! Vicent Batts a long time ago, said that will  out of
>> Slackware and the packages he are a manteiner, would be orphaned.
> 
> vbatts submitted two new SlackBuilds earlier today, and they look
> *very* interesting and useful :)
> 
> -D.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From atelszewski at gmail.com  Thu Jan 19 19:40:59 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 19 Jan 2017 20:40:59 +0100
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <CAMt7G9QdoRO03Ve2xBRsBor=deTip31MBDT_CZR6X9JmVKv=GQ@mail.gmail.com>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
 <9d71b915-3b49-ebb5-a35b-c68840ddcadd@riseup.net>
 <CAMt7G9QdoRO03Ve2xBRsBor=deTip31MBDT_CZR6X9JmVKv=GQ@mail.gmail.com>
Message-ID: <a653e1bb-c633-1fc9-3f92-f2a414270a2c@gmail.com>

On 19/01/17 20:36, David Spencer wrote:
>> I would say that! Vicent Batts a long time ago, said that will  out of
>> Slackware and the packages he are a manteiner, would be orphaned.
>
> vbatts submitted two new SlackBuilds earlier today, and they look
> *very* interesting and useful :)
>
> -D.

I wonder if you mean MPLAB.
I hate PICs! Not that I was using them much :-^

-- 
Best regards,
Andrzej Telszewski

From eric.b.pratt at gmail.com  Thu Jan 19 19:48:57 2017
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 19 Jan 2017 11:48:57 -0800
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
 <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>
Message-ID: <CAPKhk4NMb=r4ow5e7RG1J3MxArSTysVDMmLCPKtwG5ro_y0FJg@mail.gmail.com>

I know I'm definitely guilty of letting my slackbuilds slip for long
periods of time.  I'm trying to prevent that moving forward, but it's
really mostly a matter of getting the time to do it and remembering to do
it.  So I like the auto-updating idea.  It would get many of us past the
remembering to do it part of the problem.

But it would be difficult to do.  If there were a single standard database
or even standard API on project homepages that could deliver the latest
version numbers, then this would start to look good.  But everyone has
their own method for announcing releases with their own formats.  We'd have
to parse that out of each project page.  And people change their web page
layouts and formats frequently enough for this to be an ongoing headache.
If we're not updating our packages fast enough then we're not going to put
even more effort into maintaining an auto-update feature.

However, I do like the idea.  I try to automate everything I do at some
point so this is an intriguing project.  Using ffmpeg as an example since
it was already mentioned in this thread, an example to search for the
current version number could be:

  > wget -qO - "${PROJECT_URL}" | grep -o
"${PROJECT_NAME}-[0-9][0-9A-Za-z.]*\.tar\.xz" | sort -n | tail -1
  ffmpeg-3.2.2.tar.xz
  >

Since we already know the version number as defined in the slackbuild, we
could compare the filename with the existing one to see what the latest
version is:

####################################
#!/bin/bash

PROJECT_NAME='ffmpeg'
PROJECT_URL='https://ffmpeg.org/download.html'
CURRENT_VERSION='ffmpeg-2.8.7.tar.xz'
LATEST_VERSION=$(wget -qO - "${PROJECT_URL}" | grep -o
"${PROJECT_NAME}-[0-9][0-9A-Za-z.]*\.tar\.xz" | sort -n | tail -1)

if [[ $(echo -e "${CURRENT_VERSION}\n${LATEST_VERSION}" | sort -n | tail
-1) == ${CURRENT_VERSION} ]]; then
        echo "${PROJECT_NAME} Slackbuild is up to date."
        exit 0
else
        echo "Download new version and test slackbuild."
fi
####################################

Of course, we can pull the current version from the slackbuild itself and
the part where we echo "download new version . . ." would need to be
replaced by code to download the new version and test the slackbuild with
it or at the least, send a notification of a new update available.  We
could probably put some more work into this to make something that the vast
majority of slackbuilds could use.  But no doubt there will need to be a
lot of unique update scripts.  But we already have a really nice slackbuild
tar ball that could optionally contain an auto-updater as a support
script.  So just like we have a standard template for slackbuild scripts
that get modified on a case-by-case basis, we could have a standard
template for an update script.

The update script would primarily be run by the maintainer, ideally via
cron or something similar, and could attempt to download and build a
package with the new version.  Or it can simply send an email to notify the
maintainer that a new release is available in which case it would need to
track state so it doesn't spam about the same version over and over again.
Lots of possibilities.  I'll look into doing this for my slackbuilds and
see what I can come up with.


On Thu, Jan 19, 2017 at 10:58 AM, Andrzej Telszewski <atelszewski at gmail.com>
wrote:

> On 19/01/17 19:45, David Spencer wrote:
>
>> As a radical idea, we could consider making some packages
>> auto-updating. I suspect lots of perl, python, haskell and ruby could
>> be completely automated. I bet everybody hates this idea :p
>>
>>
> You bet ;-)
>
> On the other hand, George from Salix made a very good point when he
>> recently wrote "SBo has a policy of constantly updating its contents
>> with new versions, which in my opinion is competely against
>> Slackware's policy (as well as our own) for stability". I do have a
>> lot of respect for that point of view.  I think the main reasons
>> against it are social not technical (too much work at one time for new
>> releases, need to keep maintainers involved). Having said that, for
>> technical reasons quite a lot of packages do need to be quite stable
>> between releases (haskell, ffmpeg and more -- everybody on the list
>> could probably name them).
>>
>
> I don't exactly agree.
> There are multiple situations where updating the package makes a lot of
> sense.
> Be it security, or new features that save your time.
>
> On the other side, how often do we see a breakage here?
>
> As you said, there are packages that won't see an update without very good
> reason.
> I think the crew is doing very well on that matter.
>
> When it comes to Slackware, well, it's the core of everything.
> The less updates it sees, the better.
> I guess we are all happy for Pat's policy.
>
> --
> Best regards,
> Andrzej Telszewski
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170119/a60e9f8c/attachment-0001.html>

From ryanpcmcquen at member.fsf.org  Thu Jan 19 19:54:59 2017
From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen)
Date: Thu, 19 Jan 2017 11:54:59 -0800
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPKhk4NMb=r4ow5e7RG1J3MxArSTysVDMmLCPKtwG5ro_y0FJg@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
 <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>
 <CAPKhk4NMb=r4ow5e7RG1J3MxArSTysVDMmLCPKtwG5ro_y0FJg@mail.gmail.com>
Message-ID: <CAAcyf-oDK0qungKyHqYdH3YZd8iuLaSX5PTPYQ02BjD_gRaAOQ@mail.gmail.com>

On 1/19/17, Eric Pratt <eric.b.pratt at gmail.com> wrote:
> I know I'm definitely guilty of letting my slackbuilds slip for long
> periods of time.  I'm trying to prevent that moving forward, but it's
> really mostly a matter of getting the time to do it and remembering to do
> it.  So I like the auto-updating idea.  It would get many of us past the
> remembering to do it part of the problem.
>
> But it would be difficult to do.  If there were a single standard database
> or even standard API on project homepages that could deliver the latest
> version numbers, then this would start to look good.  But everyone has
> their own method for announcing releases with their own formats.  We'd have
> to parse that out of each project page.  And people change their web page
> layouts and formats frequently enough for this to be an ongoing headache.
> If we're not updating our packages fast enough then we're not going to put
> even more effort into maintaining an auto-update feature.
>
> However, I do like the idea.  I try to automate everything I do at some
> point so this is an intriguing project.  Using ffmpeg as an example since
> it was already mentioned in this thread, an example to search for the
> current version number could be:
>
>   > wget -qO - "${PROJECT_URL}" | grep -o
> "${PROJECT_NAME}-[0-9][0-9A-Za-z.]*\.tar\.xz" | sort -n | tail -1
>   ffmpeg-3.2.2.tar.xz
>   >



I maintain a small set of builds for packages that I like to keep
up-to-date that do things like this:

https://github.com/ryanpcmcquen/ryanpc-slackbuilds/tree/master/unofficial

-- 
-Ryan
[ryanpcmcquen.org]


From baildon.research at googlemail.com  Thu Jan 19 20:06:39 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 19 Jan 2017 20:06:39 +0000
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <a653e1bb-c633-1fc9-3f92-f2a414270a2c@gmail.com>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
 <9d71b915-3b49-ebb5-a35b-c68840ddcadd@riseup.net>
 <CAMt7G9QdoRO03Ve2xBRsBor=deTip31MBDT_CZR6X9JmVKv=GQ@mail.gmail.com>
 <a653e1bb-c633-1fc9-3f92-f2a414270a2c@gmail.com>
Message-ID: <CAMt7G9SHK-CYzWyGJ8PYQ=1xDqNEiMs_tfE8=WT5Le_rDFYDHQ@mail.gmail.com>

> I wonder if you mean MPLAB.

    bubblewrap 0.1.7
    ===================

    man pages (xsltproc):                         yes
    SELinux:                                      no
    setuid mode on make install:                  none
    mysteriously satisfying to pop:               yes

lol
(and almost on-topic for an email thread about docker)
-D.

From eric.b.pratt at gmail.com  Thu Jan 19 20:31:53 2017
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 19 Jan 2017 12:31:53 -0800
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAAcyf-oDK0qungKyHqYdH3YZd8iuLaSX5PTPYQ02BjD_gRaAOQ@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
 <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>
 <CAPKhk4NMb=r4ow5e7RG1J3MxArSTysVDMmLCPKtwG5ro_y0FJg@mail.gmail.com>
 <CAAcyf-oDK0qungKyHqYdH3YZd8iuLaSX5PTPYQ02BjD_gRaAOQ@mail.gmail.com>
Message-ID: <CAPKhk4Opvn+GgtJSRpG27Q3x8bPvQyfENTgVQe7XQKXP2OGR8A@mail.gmail.com>

Nice!

On Thu, Jan 19, 2017 at 11:54 AM, Ryan P.C. McQuen <
ryanpcmcquen at member.fsf.org> wrote:

> On 1/19/17, Eric Pratt <eric.b.pratt at gmail.com> wrote:
> > I know I'm definitely guilty of letting my slackbuilds slip for long
> > periods of time.  I'm trying to prevent that moving forward, but it's
> > really mostly a matter of getting the time to do it and remembering to do
> > it.  So I like the auto-updating idea.  It would get many of us past the
> > remembering to do it part of the problem.
> >
> > But it would be difficult to do.  If there were a single standard
> database
> > or even standard API on project homepages that could deliver the latest
> > version numbers, then this would start to look good.  But everyone has
> > their own method for announcing releases with their own formats.  We'd
> have
> > to parse that out of each project page.  And people change their web page
> > layouts and formats frequently enough for this to be an ongoing headache.
> > If we're not updating our packages fast enough then we're not going to
> put
> > even more effort into maintaining an auto-update feature.
> >
> > However, I do like the idea.  I try to automate everything I do at some
> > point so this is an intriguing project.  Using ffmpeg as an example since
> > it was already mentioned in this thread, an example to search for the
> > current version number could be:
> >
> >   > wget -qO - "${PROJECT_URL}" | grep -o
> > "${PROJECT_NAME}-[0-9][0-9A-Za-z.]*\.tar\.xz" | sort -n | tail -1
> >   ffmpeg-3.2.2.tar.xz
> >   >
>
>
>
> I maintain a small set of builds for packages that I like to keep
> up-to-date that do things like this:
>
> https://github.com/ryanpcmcquen/ryanpc-slackbuilds/tree/master/unofficial
>
> --
> -Ryan
> [ryanpcmcquen.org]
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170119/fef229a6/attachment.html>

From mfilpot at gmail.com  Thu Jan 19 23:18:02 2017
From: mfilpot at gmail.com (Matthew Fillpot)
Date: Thu, 19 Jan 2017 23:18:02 +0000
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPKhk4Opvn+GgtJSRpG27Q3x8bPvQyfENTgVQe7XQKXP2OGR8A@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
 <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>
 <CAPKhk4NMb=r4ow5e7RG1J3MxArSTysVDMmLCPKtwG5ro_y0FJg@mail.gmail.com>
 <CAAcyf-oDK0qungKyHqYdH3YZd8iuLaSX5PTPYQ02BjD_gRaAOQ@mail.gmail.com>
 <CAPKhk4Opvn+GgtJSRpG27Q3x8bPvQyfENTgVQe7XQKXP2OGR8A@mail.gmail.com>
Message-ID: <CAHqrv019nu=5LbygJy9o0FR-_ppdKhG212Pop_CTQ8JA2+kCFw@mail.gmail.com>

I am currently guilty of not recently updating my builds, but will act
promptly if i receive a report.
With that being said, there are exceptions in which i will delay or skip an
update. My preference is to test each new release for at least 2 weeks for
stability and to watch bug reports before submitting an update. Quality
should be more important than having the latest and greatest.

On Thu, Jan 19, 2017, 1:32 PM Eric Pratt <eric.b.pratt at gmail.com> wrote:

> Nice!
>
> On Thu, Jan 19, 2017 at 11:54 AM, Ryan P.C. McQuen <
> ryanpcmcquen at member.fsf.org> wrote:
>
> On 1/19/17, Eric Pratt <eric.b.pratt at gmail.com> wrote:
> > I know I'm definitely guilty of letting my slackbuilds slip for long
> > periods of time.  I'm trying to prevent that moving forward, but it's
> > really mostly a matter of getting the time to do it and remembering to do
> > it.  So I like the auto-updating idea.  It would get many of us past the
> > remembering to do it part of the problem.
> >
> > But it would be difficult to do.  If there were a single standard
> database
> > or even standard API on project homepages that could deliver the latest
> > version numbers, then this would start to look good.  But everyone has
> > their own method for announcing releases with their own formats.  We'd
> have
> > to parse that out of each project page.  And people change their web page
> > layouts and formats frequently enough for this to be an ongoing headache.
> > If we're not updating our packages fast enough then we're not going to
> put
> > even more effort into maintaining an auto-update feature.
> >
> > However, I do like the idea.  I try to automate everything I do at some
> > point so this is an intriguing project.  Using ffmpeg as an example since
> > it was already mentioned in this thread, an example to search for the
> > current version number could be:
> >
> >   > wget -qO - "${PROJECT_URL}" | grep -o
> > "${PROJECT_NAME}-[0-9][0-9A-Za-z.]*\.tar\.xz" | sort -n | tail -1
> >   ffmpeg-3.2.2.tar.xz
> >   >
>
>
>
> I maintain a small set of builds for packages that I like to keep
> up-to-date that do things like this:
>
> https://github.com/ryanpcmcquen/ryanpc-slackbuilds/tree/master/unofficial
>
> --
> -Ryan
> [ryanpcmcquen.org]
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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
> http://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/20170119/0a79c5f1/attachment-0001.html>

From baildon.research at googlemail.com  Fri Jan 20 01:01:13 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Fri, 20 Jan 2017 01:01:13 +0000
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAHqrv019nu=5LbygJy9o0FR-_ppdKhG212Pop_CTQ8JA2+kCFw@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
 <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>
 <CAPKhk4NMb=r4ow5e7RG1J3MxArSTysVDMmLCPKtwG5ro_y0FJg@mail.gmail.com>
 <CAAcyf-oDK0qungKyHqYdH3YZd8iuLaSX5PTPYQ02BjD_gRaAOQ@mail.gmail.com>
 <CAPKhk4Opvn+GgtJSRpG27Q3x8bPvQyfENTgVQe7XQKXP2OGR8A@mail.gmail.com>
 <CAHqrv019nu=5LbygJy9o0FR-_ppdKhG212Pop_CTQ8JA2+kCFw@mail.gmail.com>
Message-ID: <CAMt7G9T0_qcVEirNCQLwRPqyKee897PLvyL4AK9K3SYchSADFA@mail.gmail.com>

Blimey.  This is new ... and *very* scary

http://repology.org/

I'm going to have to level up on my maintaining :(
-D.

From slack at lodpp.net  Fri Jan 20 01:02:57 2017
From: slack at lodpp.net (Nicolas Lodpp)
Date: Fri, 20 Jan 2017 01:02:57 +0000
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <6ee47b06-659f-8464-7f7b-5ca7fbdd286f@riseup.net>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
 <6ee47b06-659f-8464-7f7b-5ca7fbdd286f@riseup.net>
Message-ID: <693f68e8382d411aa81e138e63e990d6@lodpp.net>

Hi everybody,

I've checked my slackbuild and corrected it to fit the 1.13.0 docker version, it creates the package fine.
As 1.12.5 is working fine for me, I didn't test the 1.13.0 ( at least not at 1 am :) )

Please be kind, I'm new about slackbuilds and I guess my modification are not the smartest moves...

I put the slackbuild on github: https://github.com/lodpp/Slackbuilds/tree/master/docker
file modified are:
- slackbuild itself
- rc.docker
- daemon.json was needed on my setup to pass some options ( note that it could be done on the rc file to with the variable DOCKER_OPTS= )

Regards,
Nico

-----Original Message-----
From: Maykon Chagas [mailto:mchagas at riseup.net] 
Sent: Thursday, January 19, 2017 8:58 PM
To: slackware stuff <slack at lodpp.net>
Subject: Re: [Slackbuilds-users] Update request Docker

Hi Nico,

I've send an email to in responso on slackbuilds-users list.
Could you share your slackbuild script to Docker?

Thanks!

Em 01/19/2017 04:09 PM, slackware stuff escreveu:
> Hi Ryan, Maykon,
> 
> I've made a modified version for docker 1.12 and compiles fine ( should be okay for  1.13 though )if you are interested.
> 
> I've contacted Vincent Batts  about the need for update He responds 
> couple a days ago that Assaf is taking charge for the docker ( and I 
> didn't got time to look for assaf email on the ml archive / sb site )
> 
> Best regards,
> 
> Nico
> 
> 
> 
> ________________________________________
> De : SlackBuilds-users <slackbuilds-users-bounces at slackbuilds.org> de 
> la part de Maykon Chagas <mchagas at member.fsf.org> Envoy? : jeudi 19 
> janvier 2017 18:43 ? : slackbuilds-users at slackbuilds.org Objet : Re: 
> [Slackbuilds-users] Update request Docker
> 
> Hi Ryan,
> 
> Your answers came directly to me.
> 
> Ok, I'll do this!
> 
> Thanks!
> 
> Kind regars,
> 
> Em 01/19/2017 03:22 PM, Ryan P.C. McQuen escreveu:
>> On 1/19/17, Maykon Chagas <mchagas at riseup.net> wrote:
>>> Hi Ryan,
>>>
>>> Sorry. No. That's the flow? Ask directly the mantainer?
>>
>>
>> Usually it's better to ask the maintainer first, and then this list 
>> if there is no prompt response from the maintainer. Not all 
>> maintainers are subscribed to this list.
>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From gerardo.zamudio at linux.com  Fri Jan 20 01:23:54 2017
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Thu, 19 Jan 2017 19:23:54 -0600
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAMt7G9T0_qcVEirNCQLwRPqyKee897PLvyL4AK9K3SYchSADFA@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
 <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>
 <CAPKhk4NMb=r4ow5e7RG1J3MxArSTysVDMmLCPKtwG5ro_y0FJg@mail.gmail.com>
 <CAAcyf-oDK0qungKyHqYdH3YZd8iuLaSX5PTPYQ02BjD_gRaAOQ@mail.gmail.com>
 <CAPKhk4Opvn+GgtJSRpG27Q3x8bPvQyfENTgVQe7XQKXP2OGR8A@mail.gmail.com>
 <CAHqrv019nu=5LbygJy9o0FR-_ppdKhG212Pop_CTQ8JA2+kCFw@mail.gmail.com>
 <CAMt7G9T0_qcVEirNCQLwRPqyKee897PLvyL4AK9K3SYchSADFA@mail.gmail.com>
Message-ID: <34e1ed29-e1e2-0aad-a0e9-7a2641606b26@linux.com>

On 01/19/2017 07:01 PM, David Spencer wrote:
> Blimey.  This is new ... and *very* scary
> 
> http://repology.org/
> 
> I'm going to have to level up on my maintaining :(
> -D.
> 
> 

I like to think they're doing me a favor and keeping track of my
packages for me. Beats the sbo.txt I keep in ~ and check when I remember ;-)

-- 
Gerardo Zamudio


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

From ryanpcmcquen at member.fsf.org  Fri Jan 20 02:17:29 2017
From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen)
Date: Thu, 19 Jan 2017 18:17:29 -0800
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <34e1ed29-e1e2-0aad-a0e9-7a2641606b26@linux.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAMt7G9R7wxEtky4eWBBMktnAfRkof4_GmcdVPGJp3zFgkkyB_w@mail.gmail.com>
 <691a4b37-51aa-8cd0-b63e-4ffaebf50019@gmail.com>
 <CAPKhk4NMb=r4ow5e7RG1J3MxArSTysVDMmLCPKtwG5ro_y0FJg@mail.gmail.com>
 <CAAcyf-oDK0qungKyHqYdH3YZd8iuLaSX5PTPYQ02BjD_gRaAOQ@mail.gmail.com>
 <CAPKhk4Opvn+GgtJSRpG27Q3x8bPvQyfENTgVQe7XQKXP2OGR8A@mail.gmail.com>
 <CAHqrv019nu=5LbygJy9o0FR-_ppdKhG212Pop_CTQ8JA2+kCFw@mail.gmail.com>
 <CAMt7G9T0_qcVEirNCQLwRPqyKee897PLvyL4AK9K3SYchSADFA@mail.gmail.com>
 <34e1ed29-e1e2-0aad-a0e9-7a2641606b26@linux.com>
Message-ID: <CAAcyf-qr1Wcbf+RqHHOUW+h1+vw3zQ2axQiWp+zLaf5vbPgiJg@mail.gmail.com>

http://repology.org/

I?m going to have to level up on my maintaining :(

What I hate about tools like these, is for packages like nodejs, we
are shown as out-of-date, when in actuality we have the very latest
LTS version. You?d be crazy to run a non-LTS node server, but alas ?
it is helpful for a lot of packages.


From klaatu at member.fsf.org  Fri Jan 20 05:42:29 2017
From: klaatu at member.fsf.org (Klaatu)
Date: Fri, 20 Jan 2017 18:42:29 +1300
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
Message-ID: <6bec87d7-bd57-de36-e2ab-18601cb52ba7@member.fsf.org>

On 20/01/17 07:01, Ryan P.C. McQuen wrote:
> On 1/19/17, Full Name <nuncestbibendum at excite.com> wrote:
>> As a long time user of Slackware, I am immensely grateful to the people who
>> have volunteered (and continue to do so) their time and effort to maintain
>> and update third-party code, so that the rest of us Slackware users can
>> painlessly and easily build the necessary software by using the resources in
>> Slackbuilds (and sbopkpg.) Once again, kudos and appreciation to you.
>>
>> Having said that, all too often maintainers do not update the software all
>> that promptly. It is not uncommon to have Slackbuilds packages that are
>> several releases behind what one can get from distributions like (shudder)
>> Fedora or (shudder!) Ubuntu. This can be a critical issue - I have been in
>> the position of the gentleman who enquired about docker, and I eventually
>> had to install an Ubuntu VM in my Slackware box, for the docker version in
>> Slackware is just too old for what I needed to do. Unfortunately, pinging
>> maintainers does not always work. In fact, having tried that myself in
>> connection to other packages, I never got any replies, and the relevant
>> packages remain behind the current versions.
>>
>> I understand that maintainers cannot (indeed, should not) be forced to do
>> anything in particular. Heck, they do what they do in their spare time, with
>> no remuneration, out of the goodness of their heart, and a sense of
>> community. For which we are all, I am sure, very thankful. I also understand
>> that they may happy legitimate reasons not to update their packages.
>> However, I wonder if maintainers could be a bit more proactive and
>> responsible about their packages? If you assume the responsibility of
>> maintaining Slackware packages, do assume the responsibility; do a good job
>> of it. If that is too big a burden on your time, just relinquish such
>> responsibility, as we see some do, every so often. But, please, do not stay
>> as the official maintainer while at the same time you silently ignore the
>> requests that you get from people. If nothing else, that taints Slackware's
>> reputation.
>>
>> One of the ripostes that I am bound to get here is, Why don't you become a
>> maintainer yourself? Well, that is not the point. I, for one, do not have
>> the time, knowledge, and drive to become a maintainer. Not everybody does
>> have what it takes. I just think that Slackware is the best Linux
>> distribution for me, and I want to be able to use the best software that I
>> can under Slackware. I can occasionally install, by hand, newer versions of
>> software packages than those in Slackbuilds - but that defeats the purpose
>> of Slackbuilds. Also, sometimes I just do not have the expertise - the
>> docker case is one example.
>>
>> I expect that some will dismiss all this retorting "If Slackware is too
>> difficult for you then use Ubuntu (or whatever) instead." Well, they may be
>> right; I might have to end up doing so. However, before taking such a
>> radical step, I'd rather appeal to the maintainers' sense of pride in what
>> they are doing, while I will risk all the abuse and derogatory comments that
>> such a thing might elicit from some. I love Slackware, I want to carry on
>> using it, but I would like to have the most up-to-date Slackware packages
>> across the board.
> 
> 
> 
> Honestly if the maintainer is not responsive (I have not found this to
> be the case very often), it is time for someone else to take over the
> package. The list should be alerted and hopefully someone will
> volunteer.
> 
> Most times editing the VERSION number and downloading a newer tarball
> is enough though. So saying that you can't have the latest version
> because of the maintainer is a bit of a straw man.
> 

I was under the impression that SlackBuilds.org mimicked Slackware
itself in update policy: release, and then it's primarily up to the user
to adapt the build scripts if further maintenance is required. That's
why they're build scripts, no?

I use Slackware on production machines for its stability and
predictability. If I can't be reasonably sure that the system I install
today is going to be 97% the same as the one I set up 6 months ago
(after the obligatory slackpkg updates and upgrades), then I may as well
use ... anything.

I understand that SlackBuilds.org needs to update, but the update policy
should be, in part, the local user's job, not SBo's.

If SlackBuilds.org is going to follow -current, then maybe there ought
to be a separate git branch for -current? That way I can pull in new
buildscripts without updating old buildscripts out from under me.

I guess the other way for me to mitigate that is to git clone a specific
commit, but I think this is a bigger issue than that. Is SlackBuilds
mimicking -current or release?


From x80 at telus.net  Fri Jan 20 07:18:20 2017
From: x80 at telus.net (x80)
Date: Thu, 19 Jan 2017 23:18:20 -0800
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
Message-ID: <63f319be-ebbf-a1cb-c3a5-ca6922258b43@telus.net>



On 01/19/2017 09:42 PM, Klaatu wrote:
> On 20/01/17 07:01, Ryan P.C. McQuen wrote:
>> On 1/19/17, Full Name <nuncestbibendum at excite.com> wrote:
>>> As a long time user of Slackware, I am immensely grateful to the people who
>>> have volunteered (and continue to do so) their time and effort to maintain
>>> and update third-party code, so that the rest of us Slackware users can
>>> painlessly and easily build the necessary software by using the resources in
>>> Slackbuilds (and sbopkpg.) Once again, kudos and appreciation to you.
>>>
>>> Having said that, all too often maintainers do not update the software all
>>> that promptly. It is not uncommon to have Slackbuilds packages that are
>>> several releases behind what one can get from distributions like (shudder)
>>> Fedora or (shudder!) Ubuntu. This can be a critical issue - I have been in
>>> the position of the gentleman who enquired about docker, and I eventually
>>> had to install an Ubuntu VM in my Slackware box, for the docker version in
>>> Slackware is just too old for what I needed to do. Unfortunately, pinging
>>> maintainers does not always work. In fact, having tried that myself in
>>> connection to other packages, I never got any replies, and the relevant
>>> packages remain behind the current versions.
>>>
>>> I understand that maintainers cannot (indeed, should not) be forced to do
>>> anything in particular. Heck, they do what they do in their spare time, with
>>> no remuneration, out of the goodness of their heart, and a sense of
>>> community. For which we are all, I am sure, very thankful. I also understand
>>> that they may happy legitimate reasons not to update their packages.
>>> However, I wonder if maintainers could be a bit more proactive and
>>> responsible about their packages? If you assume the responsibility of
>>> maintaining Slackware packages, do assume the responsibility; do a good job
>>> of it. If that is too big a burden on your time, just relinquish such
>>> responsibility, as we see some do, every so often. But, please, do not stay
>>> as the official maintainer while at the same time you silently ignore the
>>> requests that you get from people. If nothing else, that taints Slackware's
>>> reputation.
>>>
>>> One of the ripostes that I am bound to get here is, Why don't you become a
>>> maintainer yourself? Well, that is not the point. I, for one, do not have
>>> the time, knowledge, and drive to become a maintainer. Not everybody does
>>> have what it takes. I just think that Slackware is the best Linux
>>> distribution for me, and I want to be able to use the best software that I
>>> can under Slackware. I can occasionally install, by hand, newer versions of
>>> software packages than those in Slackbuilds - but that defeats the purpose
>>> of Slackbuilds. Also, sometimes I just do not have the expertise - the
>>> docker case is one example.
>>>
>>> I expect that some will dismiss all this retorting "If Slackware is too
>>> difficult for you then use Ubuntu (or whatever) instead." Well, they may be
>>> right; I might have to end up doing so. However, before taking such a
>>> radical step, I'd rather appeal to the maintainers' sense of pride in what
>>> they are doing, while I will risk all the abuse and derogatory comments that
>>> such a thing might elicit from some. I love Slackware, I want to carry on
>>> using it, but I would like to have the most up-to-date Slackware packages
>>> across the board.
>>
>>
>> Honestly if the maintainer is not responsive (I have not found this to
>> be the case very often), it is time for someone else to take over the
>> package. The list should be alerted and hopefully someone will
>> volunteer.
>>
>> Most times editing the VERSION number and downloading a newer tarball
>> is enough though. So saying that you can't have the latest version
>> because of the maintainer is a bit of a straw man.
>>
> I was under the impression that SlackBuilds.org mimicked Slackware
> itself in update policy: release, and then it's primarily up to the user
> to adapt the build scripts if further maintenance is required. That's
> why they're build scripts, no?
>
> I use Slackware on production machines for its stability and
> predictability. If I can't be reasonably sure that the system I install
> today is going to be 97% the same as the one I set up 6 months ago
> (after the obligatory slackpkg updates and upgrades), then I may as well
> use ... anything.
>
> I understand that SlackBuilds.org needs to update, but the update policy
> should be, in part, the local user's job, not SBo's.
>
> If SlackBuilds.org is going to follow -current, then maybe there ought
> to be a separate git branch for -current? That way I can pull in new
> buildscripts without updating old buildscripts out from under me.
>
> I guess the other way for me to mitigate that is to git clone a specific
> commit, but I think this is a bigger issue than that. Is SlackBuilds
> mimicking -current or release?
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
I'll add my thoughts as amusement for the group here. As a happy user of 
Slackware64 14.1 and a Linux user for almost 25 years when I access the 
slackbuilds repo for a build script I expect it to work, period. The 
last package I downloaded was the build script for xosd. (Obviously for 
dinking with my own delusion of programming, we'll not go further into 
that...) Well, the script did not work without the modification of the 
$VERSION tag. Not unreasonably, I was able to figure my way out of this, 
but not without over 20 years of experience diddling scripts and source 
code. Friends, the build scripts are there for noobies, not guys like 
me. I appreciate the effort you people put into the site and scripts but 
really, expect the people who still have 14.0 installed to look up a 
package and try to install it just to have the script fail like xosd 
failed on 14.1 for me.

In short, build scripts are for noobs, and if they can get the software 
built and installed, then they are not noobs, and noobs don't follow 
current.

Good day, gentlemen.


From skk at shanek54.co.uk  Fri Jan 20 07:26:07 2017
From: skk at shanek54.co.uk (Shane Kelly)
Date: Fri, 20 Jan 2017 07:26:07 +0000
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <6bec87d7-bd57-de36-e2ab-18601cb52ba7@member.fsf.org>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
 <6bec87d7-bd57-de36-e2ab-18601cb52ba7@member.fsf.org>
Message-ID: <20170120072607.5953a662@iMac27>

>On 20/01/17 07:01, Ryan P.C. McQuen wrote:
>> On 1/19/17, Full Name <nuncestbibendum at excite.com> wrote:
>>> As a long time user of Slackware, I am immensely grateful to the
>>> people who have volunteered (and continue to do so) their time and
>>> effort to maintain and update third-party code, so that the rest of
>>> us Slackware users can painlessly and easily build the necessary
>>> software by using the resources in Slackbuilds (and sbopkpg.) Once
>>> again, kudos and appreciation to you.
>>>
>>> Having said that, all too often maintainers do not update the
>>> software all that promptly. It is not uncommon to have Slackbuilds
>>> packages that are several releases behind what one can get from
>>> distributions like (shudder) Fedora or (shudder!) Ubuntu. This can
>>> be a critical issue - I have been in the position of the gentleman
>>> who enquired about docker, and I eventually had to install an
>>> Ubuntu VM in my Slackware box, for the docker version in Slackware
>>> is just too old for what I needed to do. Unfortunately, pinging
>>> maintainers does not always work. In fact, having tried that myself
>>> in connection to other packages, I never got any replies, and the
>>> relevant packages remain behind the current versions.
>>>
>>> I understand that maintainers cannot (indeed, should not) be forced
>>> to do anything in particular. Heck, they do what they do in their
>>> spare time, with no remuneration, out of the goodness of their
>>> heart, and a sense of community. For which we are all, I am sure,
>>> very thankful. I also understand that they may happy legitimate
>>> reasons not to update their packages. However, I wonder if
>>> maintainers could be a bit more proactive and responsible about
>>> their packages? If you assume the responsibility of maintaining
>>> Slackware packages, do assume the responsibility; do a good job of
>>> it. If that is too big a burden on your time, just relinquish such
>>> responsibility, as we see some do, every so often. But, please, do
>>> not stay as the official maintainer while at the same time you
>>> silently ignore the requests that you get from people. If nothing
>>> else, that taints Slackware's reputation.
>>>
>>> One of the ripostes that I am bound to get here is, Why don't you
>>> become a maintainer yourself? Well, that is not the point. I, for
>>> one, do not have the time, knowledge, and drive to become a
>>> maintainer. Not everybody does have what it takes. I just think
>>> that Slackware is the best Linux distribution for me, and I want to
>>> be able to use the best software that I can under Slackware. I can
>>> occasionally install, by hand, newer versions of software packages
>>> than those in Slackbuilds - but that defeats the purpose of
>>> Slackbuilds. Also, sometimes I just do not have the expertise - the
>>> docker case is one example.
>>>
>>> I expect that some will dismiss all this retorting "If Slackware is
>>> too difficult for you then use Ubuntu (or whatever) instead." Well,
>>> they may be right; I might have to end up doing so. However, before
>>> taking such a radical step, I'd rather appeal to the maintainers'
>>> sense of pride in what they are doing, while I will risk all the
>>> abuse and derogatory comments that such a thing might elicit from
>>> some. I love Slackware, I want to carry on using it, but I would
>>> like to have the most up-to-date Slackware packages across the
>>> board.
>> 
>> 
>> 
>> Honestly if the maintainer is not responsive (I have not found this
>> to be the case very often), it is time for someone else to take over
>> the package. The list should be alerted and hopefully someone will
>> volunteer.
>> 
>> Most times editing the VERSION number and downloading a newer tarball
>> is enough though. So saying that you can't have the latest version
>> because of the maintainer is a bit of a straw man.
>> 
>
>I was under the impression that SlackBuilds.org mimicked Slackware
>itself in update policy: release, and then it's primarily up to the
>user to adapt the build scripts if further maintenance is required.
>That's why they're build scripts, no?
>
>I use Slackware on production machines for its stability and
>predictability. If I can't be reasonably sure that the system I install
>today is going to be 97% the same as the one I set up 6 months ago
>(after the obligatory slackpkg updates and upgrades), then I may as
>well use ... anything.
>
>I understand that SlackBuilds.org needs to update, but the update
>policy should be, in part, the local user's job, not SBo's.
>
>If SlackBuilds.org is going to follow -current, then maybe there ought
>to be a separate git branch for -current? That way I can pull in new
>buildscripts without updating old buildscripts out from under me.
>
>I guess the other way for me to mitigate that is to git clone a
>specific commit, but I think this is a bigger issue than that. Is
>SlackBuilds mimicking -current or release?

From the SBO how-to page:
All of our scripts are written for usage on the latest stable release
of Slackware; if you're trying them on older versions of Slackware, you
should read this page referenced in our FAQ. 

Please note the use of "latest stable release".

I take this to mean that updates for upstream packages will not
automatically be incorporated into "released" slackbuilds. 
Lately, there seems to be a trend of people asking for the updates as
if it were a right, and the proper thing to do.

Slackware is as solid as a rock because of the care taken between "
releases", and if I want to upgrade a package to the latest version I
do it myself, as befits the slackware philosophy "your system, your
way".

If we are going down the "gimmee the latest , because!", then Klaatu
has given the answer (and within that answer the probable demise of
slackbuilds ).

This is a volunteer organisation, held together by the goodwill of the
maintainers - I am very grateful for what they do, and I don't feel I
have the right to ask for more, when they so generously give of their
time to help me.

Please don't change the current policy. I want stable working systems
when I deploy a server (and on my various laptops and desktops) and
that's what I get from slackware and SBO.





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



From slackalaxy at gmail.com  Fri Jan 20 08:00:19 2017
From: slackalaxy at gmail.com (Petar Petrov)
Date: Fri, 20 Jan 2017 10:00:19 +0200
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <6bec87d7-bd57-de36-e2ab-18601cb52ba7@member.fsf.org>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
 <6bec87d7-bd57-de36-e2ab-18601cb52ba7@member.fsf.org>
Message-ID: <CAKXpWBdXz0aT=wBCwMMmPOwPFAu=0gv+tpeT+gektyeX9OwQgQ@mail.gmail.com>

> If SlackBuilds.org is going to follow -current, then maybe there ought
> to be a separate git branch for -current? That way I can pull in new
> buildscripts without updating old buildscripts out from under me.

I am _not_ following -current, nor am I going to.

-petar

From info at microlinux.fr  Fri Jan 20 08:43:09 2017
From: info at microlinux.fr (Nicolas Kovacs)
Date: Fri, 20 Jan 2017 09:43:09 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170119124646.29147@web007.roc2.bluetie.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
Message-ID: <415a08ad-f78d-fd06-1c91-fda6ff4ed318@microlinux.fr>

Le 19/01/2017 ? 18:46, Full Name a ?crit :
> Having said that, all too often maintainers do not update the
> software all that promptly. It is not uncommon to have Slackbuilds
> packages that are several releases behind what one can get from
> distributions like (shudder) Fedora or (shudder!) Ubuntu. This can be
> a critical issue - I have been in the position of the gentleman who
> enquired about docker, and I eventually had to install an Ubuntu VM
> in my Slackware box, for the docker version in Slackware is just too
> old for what I needed to do. Unfortunately, pinging maintainers does
> not always work. In fact, having tried that myself in connection to
> other packages, I never got any replies, and the relevant packages
> remain behind the current versions.

+1 on that, with a little side note.

IMHO, a distinction should be made between potentially critical packages
and those that are not. I'm maintaining a couple of more or less exotic
packages on SBo: french translations for man pages, icon themes,
wallpaper collections. If these are not the latest and greatest, it's
not a problem, as long as the provided source URL still works.

On the other hand, a period of neglect could become a problem with
mission-critical software like Postfix or Dovecot, and these two have
occasionally been behind in the past.

This being said, everyone has their own solution for this. I'm
maintaining my own package repositories at
http://www.microlinux.fr/microlinux/. A roughly estimated 80 % of these
repositories is more or less directly derived from SBo (huge pat on the
shoulder to everybody here). Still, this is a significant load of work.
On the latest count:

[kikinovak at alphamule:~] $ find ~/Public/ -name '*.txz' | wc -l
1534

Cheers,

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

From atelszewski at gmail.com  Fri Jan 20 08:56:29 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 20 Jan 2017 09:56:29 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <63f319be-ebbf-a1cb-c3a5-ca6922258b43@telus.net>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
 <63f319be-ebbf-a1cb-c3a5-ca6922258b43@telus.net>
Message-ID: <e196d315-34d3-0a27-f178-3b9cf90eb428@gmail.com>

On 20/01/17 08:18, x80 wrote:
> I'll add my thoughts as amusement for the group here. As a happy user of
> Slackware64 14.1 and a Linux user for almost 25 years when I access the
> slackbuilds repo for a build script I expect it to work, period. The
> last package I downloaded was the build script for xosd. (Obviously for
> dinking with my own delusion of programming, we'll not go further into
> that...) Well, the script did not work without the modification of the
> $VERSION tag. Not unreasonably, I was able to figure my way out of this,
> but not without over 20 years of experience diddling scripts and source
> code. Friends, the build scripts are there for noobies, not guys like
> me. I appreciate the effort you people put into the site and scripts but
> really, expect the people who still have 14.0 installed to look up a
> package and try to install it just to have the script fail like xosd
> failed on 14.1 for me.
>

Errors happen, but more often than not, they are quickly resolved here.
There is and there always will be some learning curve.

> In short, build scripts are for noobs, and if they can get the software
> built and installed, then they are not noobs, and noobs don't follow
> current.

If I understood correctly, then I don't agree.
SlackBuilds are for every level of experience.
For noobs they provide for easier entry point.
For experienced users, they are incredible time saver.

It is sad to say, but we don't have the strongest QA possible here.
People are not able to investigate the source code for possible 
regressions between versions.

So we do the best we can: we look at ChangeLog and decide if the update 
makes sense.
Almost nobody here is able to ensure that the update does not break 
something.
But in the same time, he or she is not able to ensure that the initial 
release will work as expected.
So, I wouldn't consider updates to be the corner case evil.

Still and by all means, I consider SBo an invaluable effort and part of 
my actual life.

-- 
Best regards,
Andrzej Telszewski

From mchagas at member.fsf.org  Fri Jan 20 12:20:36 2017
From: mchagas at member.fsf.org (Maykon Chagas)
Date: Fri, 20 Jan 2017 10:20:36 -0200
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <693f68e8382d411aa81e138e63e990d6@lodpp.net>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
 <6ee47b06-659f-8464-7f7b-5ca7fbdd286f@riseup.net>
 <693f68e8382d411aa81e138e63e990d6@lodpp.net>
Message-ID: <69207fb0-383f-7856-180c-6d15bf4dc6e3@riseup.net>

Hi Nico,

FYI, your package builds fine! But no with a lot of test. Here's a bit
about my journey.

1. You need to download source from this URL:
https://github.com/docker/docker/tags

2. You need to change GITHASH var with the one related to your version.

3. After a lot of try with version 1.12.5, 1.12.6 and 1.13.0 the
packages with version 1.12.6 builds and work it. I've noticed that the
binary in /usr/bin/dockerd was a symlink do /usr/bin/dockerd-${VERSION}
but this one, doesn't exist. I don't know why, and when this was created
in the Slackbuild script. You just have some mv bundles and not ln commands

4. If you tried to build a package, you need to close your terminal, or
open another tab, otherwise, you'll receive errors like these:

---> Making bundle: dynbinary (in bundles/1.12.6/dynbinary)
Building: bundles/1.12.6/dynbinary-client/docker-1.12.6
go build: when using gccgo toolchain, please pass linker flags using
-gccgoflags, not -ldflags
# github.com/docker/distribution/registry/api/errcode
vendor/src/github.com/docker/distribution/registry/api/errcode/register.go:74:24:
error: reference to undefined identifier ?http.StatusTooManyRequests?
   HTTPStatusCode: http.StatusTooManyRequests,
                        ^
# github.com/docker/docker/api/client/inspect
.gopath/src/github.com/docker/docker/api/client/inspect/inspector.go:115:26:
error: reference to undefined field or method ?Option?
  tmplMissingKey := i.tmpl.Option("missingkey=error")

Well, that's was some things that I've noticed during my tests.

runc and containerd are dependencies?

At least now I can user docker-compose, and I've already test and it works!

Thanks to everyone, and specially to Nico!

Kind regars.

Em 01/19/2017 11:02 PM, Nicolas Lodpp escreveu:
> Hi everybody,
> 
> I've checked my slackbuild and corrected it to fit the 1.13.0 docker version, it creates the package fine.
> As 1.12.5 is working fine for me, I didn't test the 1.13.0 ( at least not at 1 am :) )
> 
> Please be kind, I'm new about slackbuilds and I guess my modification are not the smartest moves...
> 
> I put the slackbuild on github: https://github.com/lodpp/Slackbuilds/tree/master/docker
> file modified are:
> - slackbuild itself
> - rc.docker
> - daemon.json was needed on my setup to pass some options ( note that it could be done on the rc file to with the variable DOCKER_OPTS= )
> 
> Regards,
> Nico
> 
> -----Original Message-----
> From: Maykon Chagas [mailto:mchagas at riseup.net] 
> Sent: Thursday, January 19, 2017 8:58 PM
> To: slackware stuff <slack at lodpp.net>
> Subject: Re: [Slackbuilds-users] Update request Docker
> 
> Hi Nico,
> 
> I've send an email to in responso on slackbuilds-users list.
> Could you share your slackbuild script to Docker?
> 
> Thanks!
> 
> Em 01/19/2017 04:09 PM, slackware stuff escreveu:
>> Hi Ryan, Maykon,
>>
>> I've made a modified version for docker 1.12 and compiles fine ( should be okay for  1.13 though )if you are interested.
>>
>> I've contacted Vincent Batts  about the need for update He responds 
>> couple a days ago that Assaf is taking charge for the docker ( and I 
>> didn't got time to look for assaf email on the ml archive / sb site )
>>
>> Best regards,
>>
>> Nico
>>
>>
>>
>> ________________________________________
>> De : SlackBuilds-users <slackbuilds-users-bounces at slackbuilds.org> de 
>> la part de Maykon Chagas <mchagas at member.fsf.org> Envoy? : jeudi 19 
>> janvier 2017 18:43 ? : slackbuilds-users at slackbuilds.org Objet : Re: 
>> [Slackbuilds-users] Update request Docker
>>
>> Hi Ryan,
>>
>> Your answers came directly to me.
>>
>> Ok, I'll do this!
>>
>> Thanks!
>>
>> Kind regars,
>>
>> Em 01/19/2017 03:22 PM, Ryan P.C. McQuen escreveu:
>>> On 1/19/17, Maykon Chagas <mchagas at riseup.net> wrote:
>>>> Hi Ryan,
>>>>
>>>> Sorry. No. That's the flow? Ask directly the mantainer?
>>>
>>>
>>> Usually it's better to ask the maintainer first, and then this list 
>>> if there is no prompt response from the maintainer. Not all 
>>> maintainers are subscribed to this list.
>>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://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
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>

From erik at slackbuilds.org  Fri Jan 20 17:12:04 2017
From: erik at slackbuilds.org (Erik Hanson)
Date: Fri, 20 Jan 2017 11:12:04 -0600
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <6bec87d7-bd57-de36-e2ab-18601cb52ba7@member.fsf.org>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
 <6bec87d7-bd57-de36-e2ab-18601cb52ba7@member.fsf.org>
Message-ID: <20170120111204.12b77b62@shaggy.doo>

On Fri, 20 Jan 2017 18:42:29 +1300
Klaatu <klaatu at member.fsf.org> wrote:

> I was under the impression that SlackBuilds.org mimicked Slackware
> itself in update policy: release, and then it's primarily up to the
> user to adapt the build scripts if further maintenance is required.
> That's why they're build scripts, no?
> 
> I understand that SlackBuilds.org needs to update, but the update
> policy should be, in part, the local user's job, not SBo's.

I'm not sure what "SlackBuilds.org needs to update" means. I guess
the website looks a little dated? At any rate, the policy has been,
and still is, that maintainers take care of their own scripts.

> If SlackBuilds.org is going to follow -current, then maybe there ought
> to be a separate git branch for -current? That way I can pull in new
> buildscripts without updating old buildscripts out from under me.

I don't know where this is coming from, admittedly I haven't read
everything in this thread, as some of it is quite lengthy, but there
are no plans to follow -current. We (SBo admins) have not talked about
doing so -at all- and it's safe to say we aren't entertaining the idea.


-- 
Erik

From harald.achitz at gmail.com  Fri Jan 20 17:12:35 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Fri, 20 Jan 2017 18:12:35 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <e196d315-34d3-0a27-f178-3b9cf90eb428@gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
 <63f319be-ebbf-a1cb-c3a5-ca6922258b43@telus.net>
 <e196d315-34d3-0a27-f178-3b9cf90eb428@gmail.com>
Message-ID: <CAPh+tzO1z_BKA=qGbJk9ht_WMg5QZcXs05h8Az8567riHmxu2g@mail.gmail.com>

Here my 2 cents

Here is a list of files changed from Qt 5.6.1 to 5.6.2
each of the files contain a list of bugs.
5.6.2 has been release in October, this is quite a while ago.
A update of Qt LTS is not about having the latest and greatest, it is about
updating a package with known bugs against a fixed version.
This is something different that updating to the latest and greatast, what
would be 5.7.1, and next wee or so 5.8.0
I contacted the maintainer of the qt build, no  reply.
This is not good.
Bugfix release have to be handled.
In times of git, such an update should just be a pull request.

/Harald









2017-01-20 9:56 GMT+01:00 Andrzej Telszewski <atelszewski at gmail.com>:

> On 20/01/17 08:18, x80 wrote:
>
>> I'll add my thoughts as amusement for the group here. As a happy user of
>> Slackware64 14.1 and a Linux user for almost 25 years when I access the
>> slackbuilds repo for a build script I expect it to work, period. The
>> last package I downloaded was the build script for xosd. (Obviously for
>> dinking with my own delusion of programming, we'll not go further into
>> that...) Well, the script did not work without the modification of the
>> $VERSION tag. Not unreasonably, I was able to figure my way out of this,
>> but not without over 20 years of experience diddling scripts and source
>> code. Friends, the build scripts are there for noobies, not guys like
>> me. I appreciate the effort you people put into the site and scripts but
>> really, expect the people who still have 14.0 installed to look up a
>> package and try to install it just to have the script fail like xosd
>> failed on 14.1 for me.
>>
>>
> Errors happen, but more often than not, they are quickly resolved here.
> There is and there always will be some learning curve.
>
> In short, build scripts are for noobs, and if they can get the software
>> built and installed, then they are not noobs, and noobs don't follow
>> current.
>>
>
> If I understood correctly, then I don't agree.
> SlackBuilds are for every level of experience.
> For noobs they provide for easier entry point.
> For experienced users, they are incredible time saver.
>
> It is sad to say, but we don't have the strongest QA possible here.
> People are not able to investigate the source code for possible
> regressions between versions.
>
> So we do the best we can: we look at ChangeLog and decide if the update
> makes sense.
> Almost nobody here is able to ensure that the update does not break
> something.
> But in the same time, he or she is not able to ensure that the initial
> release will work as expected.
> So, I wouldn't consider updates to be the corner case evil.
>
> Still and by all means, I consider SBo an invaluable effort and part of my
> actual life.
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170120/02de4168/attachment.html>

From slackbuilds at schoepfer.info  Fri Jan 20 19:12:30 2017
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 20 Jan 2017 20:12:30 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPh+tzO1z_BKA=qGbJk9ht_WMg5QZcXs05h8Az8567riHmxu2g@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
 <63f319be-ebbf-a1cb-c3a5-ca6922258b43@telus.net>
 <e196d315-34d3-0a27-f178-3b9cf90eb428@gmail.com>
 <CAPh+tzO1z_BKA=qGbJk9ht_WMg5QZcXs05h8Az8567riHmxu2g@mail.gmail.com>
Message-ID: <11bde674b5d9d6928651ffc6896af8c8@schoepfer.info>


> I contacted the maintainer of the qt build, no  reply.
> This is not good.

This picks up the initial post. The "mail the maintainer"-policy might
not be efficient enough.

Maybe a request-file per maintainer in git could help
-the maintainer to keep track what has to be done
-the (SBo)maintainers to make comments, e.g. why an update would be 
good/bad
-to have better transparency of requests. The average SBo-user doesn't 
need to search through tons of Emails in the Archive for the state of a 
specific package
-to discover orphaned packages

Basically something like a simple bucktracker.

Johannes

From slack at lodpp.net  Fri Jan 20 19:13:20 2017
From: slack at lodpp.net (Nicolas Lodpp)
Date: Fri, 20 Jan 2017 19:13:20 +0000
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <69207fb0-383f-7856-180c-6d15bf4dc6e3@riseup.net>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
 <6ee47b06-659f-8464-7f7b-5ca7fbdd286f@riseup.net>
 <693f68e8382d411aa81e138e63e990d6@lodpp.net>
 <69207fb0-383f-7856-180c-6d15bf4dc6e3@riseup.net>
Message-ID: <93277e6690af45a3a4896889298bb608@lodpp.net>

Maykon,

Thanks for feedback, appreciated :)

1 - Yeah, I should have stated that information ( get the 64bits source .tar.gz from  )

2- Didn't needed that to build and install successfully 1.12.5, I will take a look because sounds a good thing to do :)

3 - Yes, I need to take some time to review that part .
Well I guess I made some sort of bruteforce to understand how this was used ...

4 - will test, I didn't realized about those errors

5 -  runc and containerd , yes ! I didn't remember about that, I needed to install those 2 packages as well
So it should be added as dependencies

Did you need to run docker with a generic linux kernel ( not the Huge one  ) ?
Did you also need to add the daemon.json file to make it work ( or pass option in rc.docker ) ?

Thanks and Regards ,
Nico

-----Original Message-----
From: Maykon Chagas [mailto:mchagas at member.fsf.org] 
Sent: Friday, January 20, 2017 1:21 PM
To: Nicolas Lodpp <slack at lodpp.net>; slackbuilds-users (slackbuilds-users at slackbuilds.org) <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] Update request Docker

Hi Nico,

FYI, your package builds fine! But no with a lot of test. Here's a bit about my journey.

1. You need to download source from this URL:
https://github.com/docker/docker/tags

2. You need to change GITHASH var with the one related to your version.

3. After a lot of try with version 1.12.5, 1.12.6 and 1.13.0 the packages with version 1.12.6 builds and work it. I've noticed that the binary in /usr/bin/dockerd was a symlink do /usr/bin/dockerd-${VERSION} but this one, doesn't exist. I don't know why, and when this was created in the Slackbuild script. You just have some mv bundles and not ln commands

4. If you tried to build a package, you need to close your terminal, or open another tab, otherwise, you'll receive errors like these:

---> Making bundle: dynbinary (in bundles/1.12.6/dynbinary)
Building: bundles/1.12.6/dynbinary-client/docker-1.12.6
go build: when using gccgo toolchain, please pass linker flags using -gccgoflags, not -ldflags # github.com/docker/distribution/registry/api/errcode
vendor/src/github.com/docker/distribution/registry/api/errcode/register.go:74:24:
error: reference to undefined identifier 'http.StatusTooManyRequests'
   HTTPStatusCode: http.StatusTooManyRequests,
                        ^
# github.com/docker/docker/api/client/inspect
.gopath/src/github.com/docker/docker/api/client/inspect/inspector.go:115:26:
error: reference to undefined field or method 'Option'
  tmplMissingKey := i.tmpl.Option("missingkey=error")

Well, that's was some things that I've noticed during my tests.

runc and containerd are dependencies?

At least now I can user docker-compose, and I've already test and it works!

Thanks to everyone, and specially to Nico!

Kind regars.

Em 01/19/2017 11:02 PM, Nicolas Lodpp escreveu:
> Hi everybody,
> 
> I've checked my slackbuild and corrected it to fit the 1.13.0 docker version, it creates the package fine.
> As 1.12.5 is working fine for me, I didn't test the 1.13.0 ( at least 
> not at 1 am :) )
> 
> Please be kind, I'm new about slackbuilds and I guess my modification are not the smartest moves...
> 
> I put the slackbuild on github: 
> https://github.com/lodpp/Slackbuilds/tree/master/docker
> file modified are:
> - slackbuild itself
> - rc.docker
> - daemon.json was needed on my setup to pass some options ( note that 
> it could be done on the rc file to with the variable DOCKER_OPTS= )
> 
> Regards,
> Nico
> 
> -----Original Message-----
> From: Maykon Chagas [mailto:mchagas at riseup.net]
> Sent: Thursday, January 19, 2017 8:58 PM
> To: slackware stuff <slack at lodpp.net>
> Subject: Re: [Slackbuilds-users] Update request Docker
> 
> Hi Nico,
> 
> I've send an email to in responso on slackbuilds-users list.
> Could you share your slackbuild script to Docker?
> 
> Thanks!
> 
> Em 01/19/2017 04:09 PM, slackware stuff escreveu:
>> Hi Ryan, Maykon,
>>
>> I've made a modified version for docker 1.12 and compiles fine ( should be okay for  1.13 though )if you are interested.
>>
>> I've contacted Vincent Batts  about the need for update He responds 
>> couple a days ago that Assaf is taking charge for the docker ( and I 
>> didn't got time to look for assaf email on the ml archive / sb site )
>>
>> Best regards,
>>
>> Nico
>>
>>
>>
>> ________________________________________
>> De : SlackBuilds-users <slackbuilds-users-bounces at slackbuilds.org> de 
>> la part de Maykon Chagas <mchagas at member.fsf.org> Envoy? : jeudi 19 
>> janvier 2017 18:43 ? : slackbuilds-users at slackbuilds.org Objet : Re:
>> [Slackbuilds-users] Update request Docker
>>
>> Hi Ryan,
>>
>> Your answers came directly to me.
>>
>> Ok, I'll do this!
>>
>> Thanks!
>>
>> Kind regars,
>>
>> Em 01/19/2017 03:22 PM, Ryan P.C. McQuen escreveu:
>>> On 1/19/17, Maykon Chagas <mchagas at riseup.net> wrote:
>>>> Hi Ryan,
>>>>
>>>> Sorry. No. That's the flow? Ask directly the mantainer?
>>>
>>>
>>> Usually it's better to ask the maintainer first, and then this list 
>>> if there is no prompt response from the maintainer. Not all 
>>> maintainers are subscribed to this list.
>>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://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
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>

From lukenshiro at ngi.it  Fri Jan 20 23:54:21 2017
From: lukenshiro at ngi.it (LukenShiro)
Date: Sat, 21 Jan 2017 00:54:21 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170119124646.29147@web007.roc2.bluetie.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
Message-ID: <20170121005421.1a8e004d@hamalayi.mnt>

Il giorno Thu, 19 Jan 2017 12:46:46 -0500
"Full Name" <nuncestbibendum at excite.com> ha scritto:
> Having said that, all too often maintainers do not update the
> software all that promptly. It is not uncommon to have Slackbuilds
> packages that are several releases behind what one can get from
> distributions like (shudder) Fedora or (shudder!) Ubuntu. This can be
> a critical issue

I see several users now complain for lack of updates, meanwhile they
did not offer any reasonable help for the time being; I guess every
maintainer here tries to do his best but, as this is not a job for
me (and for any other maintainer here) and we use our limited free
time, no one can really expect anything.

Maybe we could do better, and BTW I will upgrade my packages ASAP..
nonetheless, as I believe such simple complaints are somehow
disrespectful for us all, if anybody is not satified he can easily step
in without hesitation and take over maintainership for all of (my)
packages.

No offence taken and I don't intend to sound too harsh, but I hope
to be deadly clear about this topic. Regards.

-- 
GNU/Linux * Slackware64 current * k4.9.4
LU #210970 SU #12583 LM #98222/#412913

From willysr at slackbuilds.org  Sat Jan 21 00:25:08 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 21 Jan 2017 07:25:08 +0700
Subject: [Slackbuilds-users] Updates - 20170121.1
Message-ID: <6ee80313-4b99-e37d-96bd-5782daa2e5fd@slackbuilds.org>

Sat Jan 21 00:05:25 UTC 2017
academic/calc: Switch to i586 + new maintainer.
academic/maxima: Updated for version 5.39.0 + new maintainer.
academic/mendeleydesktop: Updated for version 1.17.6 + new maint.
academic/pulseview: Updated for version 0.3.0.
academic/sigrok-cli: Updated for version 0.6.0.
audio/freac: Update README.
audio/mpd: Updated for version 0.20.2.
audio/ncmpcpp: Fix build.
audio/pianobar: Updated for version 2016.06.02 + new maintainer.
desktop/caffeine-ng: Added (Status bar app to stop the screensaver).
desktop/dwm: Fix compiler options. i486 => i586.
desktop/numix-blue-theme: Added (Numix GTK theme).
desktop/numix-ocean-theme: Added (modern flat theme).
desktop/numix-sx-theme: Added (Numix theme for Cinnamon/Gnome).
development/alembic: Added (database migration tool).
development/atom: Updated for version 0.10.1.
development/electron-prebuild: Added (open source library).
development/envytools: Updated for version 2017.01.11_aae0c52a.
development/gisto: Fix icon.
development/google-go-lang: Updated for version 1.7.4.
development/netbeans: Updated for version 8.2.
development/pkgconf: Updated for version 1.1.1.
development/snappy: Fix doc installation (add --docdir flag)
development/spdlog: Fixed patch.
development/sqlcl: Added (Oracle SQL Developer Command Line).
development/sqldeveloper: Updated for version 4.1.5.21.78.
games/asc: Switch to wxPython.
games/chexquest3: Added (breakfast cereal themed FPS game).
games/crispy-doom: Fixed conflicts with chocolate-doom.
games/doomretro: Update MD5SUM.
games/gzdoom: Updated for version 2.3.2.
games/hlsdk: Fixed tarball handling.
games/pioneer: Updated for version 20161129.
games/stone_soup: Updated for version 0.19.1.
games/zod-engine: Switch to wxPython.
graphics/pngquant: Updated for version 2.8.2.
libraries/FreeImage: Updated for version 3.17.0.
libraries/chromaprint: Updated for version 1.4.2.
libraries/gazebo: Added (dynamic multi-robot simulator).
libraries/gperftools: Fixed tarball handling.
libraries/ignition-transport: Fixed build.
libraries/jsoncpp: Updated for version 1.8.0
libraries/libftdi: Switch to i586.
libraries/libosinfo: Fixed version.
libraries/libp11: Added (PKCS#11 wrapper library).
libraries/librevisa: Switch to i586.
libraries/libserialport: Updated for version 0.1.1.
libraries/libsigrok: Updated for version 0.4.0.
libraries/libsigrokdecode: Updated for version 0.4.1.
libraries/pcl: Update DEP and README.
libraries/pjsip: Added (multimedia communication library).
libraries/psqlodbc: Added (PostgreSQL ODBC driver).
libraries/rapidjson: Fixed tarball handling.
libraries/rocksdb: Added (persistent key-value store).
libraries/upscaledb: Added (embedded key/value database).
libraries/wayland: Updated for version 1.12.0.
libraries/webkit2gtk: Updated for version 2.14.3.
libraries/wxSQLite3: Switch to wxPython.
misc/abgx360gui: Switch to wxPython.
misc/dcc: Updated for version 1.3.158.
misc/heimdall: Added (Flash ROM tool).
misc/protobuf: Update DEP.
misc/qtkeychain: Updated for version 0.7.0.
misc/sigrok-firmware-fx2lafw: Updated for version 0.1.4.
multimedia/Mopidy: Updated for version 2.1.0.
multimedia/devedeng: Updated for version 4.8.6.
multimedia/lightspark: Updated for version 2017.01.07_308241eb.
multimedia/obs-studio: Updated for version 17.0.1
multimedia/pepperflash-plugin: Move the manifest.json file.
multimedia/spotify: Updated for version 1.0.47 + new maintainer.
network/davmail: Updated for version 4.7.3.
network/hylafax+: Updated for version 5.5.8.
network/opera: Updated for version 42.0.2393.137.
network/qbittorrent-qt5: Added (Qt5 Bittorrent Client).
network/sabnzbd: Updated for version 1.2.0.
network/slack: Updated for version 2.3.4 + new maintainer.
network/social-engineer-toolkit: Updated for version 7.4.5.
network/telegram: Updated for version 1.0.2.
network/transgui: Fixed md5sum.
network/vivaldi: Remove suid from sandbox script.
network/wifite: Added (wireless attack tool).
office/MasterPDFEditor: Updated for version 4.0.20.
office/calibre: Updated for version 2.77.0
perl/perl-CPAN-Perl-Releases: Updated for version 3.06.
perl/perl-File-Copy-Recursive: Switch to i586 + new maintainer.
perl/perl-File-Find-Rule: New maintainer.
perl/perl-File-ShareDir-Install: Switch to i586 + new maintainer.
perl/perl-IO-All: Switch to i586 + new maintainer.
perl/perl-Inline-C: Switch to i586 + new maintainer.
perl/perl-Inline: Switch to i586 + new maintainer.
perl/perl-Number-Compare: New maintainer.
perl/perl-Pegex: Switch to i586 + new maintainer.
perl/perl-Text-Autoformat: New maintainer.
perl/perl-Text-CSV: New maintainer.
perl/perl-Text-Glob: New maintainer.
perl/perl-Text-Reform: New maintainer.
perl/perl-Text-Tabs+Wrap: Added (expand and unexpand tabs).
perl/perl-Time-Piece: New maintainer.
perl/perl-YAML-LibYAML: Switch to i586 + new maintainer.
perl/perl-common-sense: Updated for version 3.74.
perl/perl-libnet: Fixed version.
perl/perl-test-warn: Switch to i586 + new maintainer.
python/APScheduler: Updated for version 3.3.1.
python/artifacts: Updated for version 20161022.
python/colored: Updated for version 1.3.4.
python/coverage: Updated for version 4.3.4.
python/google-apputils: Added (Google Application Utilities).
python/pyPdf: Fixed tarball handling.
python/pydot: Fixed version.
python/pyewmh: Added (Extended Window Manager Hints for python).
python/python-gflags: Updated for version 3.1.0.
python/setuptools-scm: Updated for version 1.15.0.
python/tqdm: Updated for version 4.11.1.
ruby/rubygem-gosu: Updated for version 0.11.1.
system/Iosevka: Updated for version 1.10.4.
system/bubblewrap: Added (unprivileged sandboxing tool).
system/common-daemon: Update DEP.
system/firejail: Updated for version 0.9.44.8.
system/firetools: Added (GUI of Firejail).
system/fzf: Updated for version 0.16.0.
system/hashID: Added (hash-identifier).
system/hashcat: Added (advanced password recovery).
system/letsencrypt: Updated for version 0.10.1.
system/ostree: Added (tool for immutable filesystem trees).
system/rkhunter: Updated for version 1.4.2 +  new maintainer.
system/sbotools: Updated for version 2.2.
system/slackroll: Added (Package manager for Slackware Linux).
system/sleuthkit: Updated for version 4.4.0.
system/softhsm: Added (Software Hardware Security Module).
system/stm32flash: Added (flash program for the STM32 ARM).
system/terminator: Fixed deps.
system/vtcol: Updated to work in offline mode.
system/xautolock: Fix SlackBuild for -current.
+--------------------------+

-- 
Willy Sudiarto Raharjo

-------------- 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/20170121/8e88b671/attachment-0001.asc>

From Jim.Diamond at acadiau.ca  Sat Jan 21 00:34:17 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Fri, 20 Jan 2017 20:34:17 -0400
Subject: [Slackbuilds-users] Updates - 20170121.1
In-Reply-To: <6ee80313-4b99-e37d-96bd-5782daa2e5fd@slackbuilds.org>
References: <6ee80313-4b99-e37d-96bd-5782daa2e5fd@slackbuilds.org>
Message-ID: <20170121003417.GB10026@jdiamond-nb.acadiau.ca>

On Sat, Jan 21, 2017 at 07:25 (+0700), Willy Sudiarto Raharjo wrote:

> Sat Jan 21 00:05:25 UTC 2017

snip

> libraries/pjsip: Added (multimedia communication library).

$ sbocheck                                                           
Updating SlackBuilds tree...
            484   0%    0.20kB/s    0:00:02 (xfr#1, to-chk=0/50562)   
Checking for updated SlackBuilds...
A fatal script error has occurred:
error when parsing belle-sip.info file.
Exiting.

(Repeatable at least 3 times.)


Is this file
        /usr/local/poo/usr-sbo-142/repo/libraries/belle-sip/belle-sip.info
in pjsip by any chance?

Cheers.

                                Jim

From hostmaster at slackonly.com  Sat Jan 21 00:37:45 2017
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Fri, 20 Jan 2017 16:37:45 -0800
Subject: [Slackbuilds-users] slackyd
Message-ID: <39719a61-b405-8bde-d8a6-441520fbea92@slackonly.com>

Hi!,

slackyd website and source return 404...

Thanks


From willysr at slackbuilds.org  Sat Jan 21 00:38:46 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 21 Jan 2017 07:38:46 +0700
Subject: [Slackbuilds-users] Updates - 20170121.1
In-Reply-To: <20170121003417.GB10026@jdiamond-nb.acadiau.ca>
References: <6ee80313-4b99-e37d-96bd-5782daa2e5fd@slackbuilds.org>
 <20170121003417.GB10026@jdiamond-nb.acadiau.ca>
Message-ID: <5fc4152e-5507-4200-7d63-2d09720712f4@slackbuilds.org>

>> libraries/pjsip: Added (multimedia communication library).
> 
> $ sbocheck                                                           
> Updating SlackBuilds tree...
>             484   0%    0.20kB/s    0:00:02 (xfr#1, to-chk=0/50562)   
> Checking for updated SlackBuilds...
> A fatal script error has occurred:
> error when parsing belle-sip.info file.
> Exiting.
> 
> (Repeatable at least 3 times.)
> 
> 
> Is this file
>         /usr/local/poo/usr-sbo-142/repo/libraries/belle-sip/belle-sip.info
> in pjsip by any chance?

No, it's committed here
https://slackbuilds.org/cgit/slackbuilds/commit/?id=d0d2a985df2a85f7a68c1cb0294dee5299e155d8

last update to belle-sip was last year (2016-01-17)


-- 
Willy Sudiarto Raharjo

-------------- 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/20170121/067892b9/attachment.asc>

From willysr at slackbuilds.org  Sat Jan 21 00:49:39 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 21 Jan 2017 07:49:39 +0700
Subject: [Slackbuilds-users] slackyd
In-Reply-To: <39719a61-b405-8bde-d8a6-441520fbea92@slackonly.com>
References: <39719a61-b405-8bde-d8a6-441520fbea92@slackonly.com>
Message-ID: <cf7e041a-0d90-608f-0f3d-521ef063982e@slackbuilds.org>

> slackyd website and source return 404...

Fixed in my branch

commit a1124fdc886f61f5db15700841f1108b822b0633
Author: Panagiotis Nikolaou <hostmaster at slackonly.com>
Date:   Sat Jan 21 07:48:50 2017 +0700

    system/slackyd: Update DOWNLOAD and HOMEPAGE.

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


-- 
Willy Sudiarto Raharjo

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

From Jim.Diamond at acadiau.ca  Sat Jan 21 01:13:28 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Fri, 20 Jan 2017 21:13:28 -0400
Subject: [Slackbuilds-users] Updates - 20170121.1
In-Reply-To: <5fc4152e-5507-4200-7d63-2d09720712f4@slackbuilds.org>
References: <6ee80313-4b99-e37d-96bd-5782daa2e5fd@slackbuilds.org>
 <20170121003417.GB10026@jdiamond-nb.acadiau.ca>
 <5fc4152e-5507-4200-7d63-2d09720712f4@slackbuilds.org>
Message-ID: <20170121011328.GA12309@jdiamond-nb.acadiau.ca>

On Sat, Jan 21, 2017 at 07:38 (+0700), Willy Sudiarto Raharjo wrote:

>>> libraries/pjsip: Added (multimedia communication library).

>> $ sbocheck                                                           
>> Updating SlackBuilds tree...
>>             484   0%    0.20kB/s    0:00:02 (xfr#1, to-chk=0/50562)   
>> Checking for updated SlackBuilds...
>> A fatal script error has occurred:
>> error when parsing belle-sip.info file.
>> Exiting.

>> (Repeatable at least 3 times.)


>> Is this file
>>         /usr/local/poo/usr-sbo-142/repo/libraries/belle-sip/belle-sip.info
>> in pjsip by any chance?

> No, it's committed here
> https://slackbuilds.org/cgit/slackbuilds/commit/?id=d0d2a985df2a85f7a68c1cb0294dee5299e155d8

> last update to belle-sip was last year (2016-01-17)

Curious.

sbocheck is dying when it tries to parse the
        EMAIL="euan at potensol dot com" 
line.  This file has a trailing space, which I thought might be the
problem, but so do a few others (all of them with that e-mail addr).

I see that the offensive perl code /usr/share/perl5/SBO/Lib/Info.pm
was updated last week.  Coincidence?

Andreas, what do you think?

                                Jim



From willysr at slackbuilds.org  Sat Jan 21 01:18:05 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 21 Jan 2017 08:18:05 +0700
Subject: [Slackbuilds-users] Updates - 20170121.1
In-Reply-To: <20170121011328.GA12309@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>
Message-ID: <db17ccf9-fb59-dc6a-228b-414c19a433aa@slackbuilds.org>

> sbocheck is dying when it tries to parse the
>         EMAIL="euan at potensol dot com" 
> line.  This file has a trailing space, which I thought might be the
> problem, but so do a few others (all of them with that e-mail addr).
> 
> I see that the offensive perl code /usr/share/perl5/SBO/Lib/Info.pm
> was updated last week.  Coincidence?

Fixed in my branch

commit 53d2eed127b581485066b6fd4da412e888af638b
Author: Jim Diamond <jim.diamond at acadiau.ca>
Date:   Sat Jan 21 08:17:07 2017 +0700

    libraries/belle-sip: Remove trailing white space.

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


-- 
Willy Sudiarto Raharjo

-------------- 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/20170121/2edb4571/attachment.asc>

From Jim.Diamond at acadiau.ca  Sat Jan 21 01:20:15 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Fri, 20 Jan 2017 21:20:15 -0400
Subject: [Slackbuilds-users] Updates - 20170121.1
In-Reply-To: <20170121011328.GA12309@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>
Message-ID: <20170121012015.GA16469@jdiamond-nb.acadiau.ca>

On Fri, Jan 20, 2017 at 21:13 (-0400), Jim Diamond wrote:

<snip>

> sbocheck is dying when it tries to parse the
> EMAIL="euan at potensol dot com" 
> line.  This file has a trailing space, which I thought might be the
> problem, but so do a few others (all of them with that e-mail addr).

> I see that the offensive perl code /usr/share/perl5/SBO/Lib/Info.pm
> was updated last week.  Coincidence?

> Andreas, what do you think?


I forgot to add that changing
        while ($info_str =~ /\G([A-Za-z0-9_]+)="([^"]*)"\n/g) {
to
        while ($info_str =~ /\G([A-Za-z0-9_]+)="([^"]*)" *\n/g) {
solves that problem and sbocheck runs to completion.  Whether that
breaks something else remains to be seen.


                                Jim

From Jim.Diamond at acadiau.ca  Sat Jan 21 01:30:00 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Fri, 20 Jan 2017 21:30:00 -0400
Subject: [Slackbuilds-users] Updates - 20170121.1
In-Reply-To: <20170121012015.GA16469@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>
Message-ID: <20170121013000.GA17597@jdiamond-nb.acadiau.ca>

On Fri, Jan 20, 2017 at 21:20 (-0400), Jim Diamond wrote:

> On Fri, Jan 20, 2017 at 21:13 (-0400), Jim Diamond wrote:

> <snip>

>> sbocheck is dying when it tries to parse the
>> EMAIL="euan at potensol dot com" 
>> line.  This file has a trailing space, which I thought might be the
>> problem, but so do a few others (all of them with that e-mail addr).

>> I see that the offensive perl code /usr/share/perl5/SBO/Lib/Info.pm
>> was updated last week.  Coincidence?

>> Andreas, what do you think?


> I forgot to add that changing
> while ($info_str =~ /\G([A-Za-z0-9_]+)="([^"]*)"\n/g) {
> to
> while ($info_str =~ /\G([A-Za-z0-9_]+)="([^"]*)" *\n/g) {
> solves that problem and sbocheck runs to completion.  Whether that
> breaks something else remains to be seen.

And now that I got it working, it upgraded itself and fixed itself.

(Almost) nothing to see here, move along...

From andreas.guldstrand at gmail.com  Sat Jan 21 02:09:58 2017
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Sat, 21 Jan 2017 03:09:58 +0100
Subject: [Slackbuilds-users] Updates - 20170121.1
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: <CAEQ5t82vdd8Rcf84yfqiOOT1u=Hv7BA-zwpEA-ZFU7a4ueBj=Q@mail.gmail.com>

Yeah, I fixed this issue and some few others less than an hour ago ...
sorry for the inconvenience, this all should be good with sbotools-2.3
(which has already been approved and is in willysr's branch)

On 21 January 2017 at 02:30, Jim Diamond <Jim.Diamond at acadiau.ca> wrote:
> On Fri, Jan 20, 2017 at 21:20 (-0400), Jim Diamond wrote:
>
>> On Fri, Jan 20, 2017 at 21:13 (-0400), Jim Diamond wrote:
>
>> <snip>
>
>>> sbocheck is dying when it tries to parse the
>>> EMAIL="euan at potensol dot com"
>>> line.  This file has a trailing space, which I thought might be the
>>> problem, but so do a few others (all of them with that e-mail addr).
>
>>> I see that the offensive perl code /usr/share/perl5/SBO/Lib/Info.pm
>>> was updated last week.  Coincidence?
>
>>> Andreas, what do you think?
>
>
>> I forgot to add that changing
>> while ($info_str =~ /\G([A-Za-z0-9_]+)="([^"]*)"\n/g) {
>> to
>> while ($info_str =~ /\G([A-Za-z0-9_]+)="([^"]*)" *\n/g) {
>> solves that problem and sbocheck runs to completion.  Whether that
>> breaks something else remains to be seen.
>
> And now that I got it working, it upgraded itself and fixed itself.
>
> (Almost) nothing to see here, move along...

From klaatu at member.fsf.org  Sat Jan 21 05:29:20 2017
From: klaatu at member.fsf.org (Klaatu)
Date: Sat, 21 Jan 2017 18:29:20 +1300
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170120111204.12b77b62@shaggy.doo>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <CAAcyf-ok0dNNeDC=AVgvxX1GbsfMxwy8XDE-4PikiK4w8VcgOw@mail.gmail.com>
 <6bec87d7-bd57-de36-e2ab-18601cb52ba7@member.fsf.org>
 <20170120111204.12b77b62@shaggy.doo>
Message-ID: <cd81598f-4019-e9c5-6160-228a270fe556@member.fsf.org>

On 21/01/17 06:12, Erik Hanson wrote:
> On Fri, 20 Jan 2017 18:42:29 +1300
> Klaatu <klaatu at member.fsf.org> wrote:
> 
>> I was under the impression that SlackBuilds.org mimicked Slackware
>> itself in update policy: release, and then it's primarily up to the
>> user to adapt the build scripts if further maintenance is required.
>> That's why they're build scripts, no?
>>
>> I understand that SlackBuilds.org needs to update, but the update
>> policy should be, in part, the local user's job, not SBo's.
> 
> I'm not sure what "SlackBuilds.org needs to update" means. I guess
> the website looks a little dated? At any rate, the policy has been,
> and still is, that maintainers take care of their own scripts.
> 
>> If SlackBuilds.org is going to follow -current, then maybe there ought
>> to be a separate git branch for -current? That way I can pull in new
>> buildscripts without updating old buildscripts out from under me.
> 
> I don't know where this is coming from, admittedly I haven't read
> everything in this thread, as some of it is quite lengthy, but there
> are no plans to follow -current. We (SBo admins) have not talked about
> doing so -at all- and it's safe to say we aren't entertaining the idea.
> 
> 

Erik,

No, I think you're reading my statements almost exactly in the opposite
way that I meant them.

The executive summary:

I was responding to several posts that were suggesting that SBo
maintainers need to update their scripts more often.

I was arguing that this is not the case, and that build scripts are
scripts so users can update them.

I was not suggesting that the *site* needs an update, in fact far from
it. The site is functional and works well in both GUI and text browsers.
If you ask me, I'd prefer it not to change.

The sentence was written to allow for the idea that some *packages* need
updating from time to time, while primarily stating my desire for SBo
packages to mimic Slackware's stability instead of rapid updates for
update's sake.

- klaatu




From harald.achitz at gmail.com  Sat Jan 21 07:21:12 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sat, 21 Jan 2017 08:21:12 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170121005421.1a8e004d@hamalayi.mnt>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
Message-ID: <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>

Hi,
help is difficult,
the SBo rules are clear,
If you sent an updated version of a package, you need the OK of the
maintainer.
If you contact a maintainer, and there is no response, what than?

This is a barrier, unnecessary.
Git stable & testing, branch.
pull requests to testing,
when some have reviewed && tested a package in testing, it goes to stable.
all this public.
you will see, this is much more productive and delivers better results.

I try to help, e.g. I would have submitted an update for Qt, but without
maintainer permission....

The bureaucracy of SBo was long, and still is, an impediment for me.
We should be aware of that.
It is more easy for me to contribute to any opensouce project on github (I
do this) than to SBo.
Why? is this adequate for 2017?

I do not want to criticize, I want to offer help, by questioning the
project structure and suggest alternatives, I think I do this.

/Harald




2017-01-21 0:54 GMT+01:00 LukenShiro <lukenshiro at ngi.it>:

> Il giorno Thu, 19 Jan 2017 12:46:46 -0500
> "Full Name" <nuncestbibendum at excite.com> ha scritto:
> > Having said that, all too often maintainers do not update the
> > software all that promptly. It is not uncommon to have Slackbuilds
> > packages that are several releases behind what one can get from
> > distributions like (shudder) Fedora or (shudder!) Ubuntu. This can be
> > a critical issue
>
> I see several users now complain for lack of updates, meanwhile they
> did not offer any reasonable help for the time being; I guess every
> maintainer here tries to do his best but, as this is not a job for
> me (and for any other maintainer here) and we use our limited free
> time, no one can really expect anything.
>
> Maybe we could do better, and BTW I will upgrade my packages ASAP..
> nonetheless, as I believe such simple complaints are somehow
> disrespectful for us all, if anybody is not satified he can easily step
> in without hesitation and take over maintainership for all of (my)
> packages.
>
> No offence taken and I don't intend to sound too harsh, but I hope
> to be deadly clear about this topic. Regards.
>
> --
> GNU/Linux * Slackware64 current * k4.9.4
> LU #210970 SU #12583 LM #98222/#412913
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170121/f271d00f/attachment.html>

From atelszewski at gmail.com  Sat Jan 21 09:23:23 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 Jan 2017 10:23:23 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
Message-ID: <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>

On 21/01/17 08:21, Harald Achitz wrote:
> Hi,
> help is difficult,
> the SBo rules are clear,
> If you sent an updated version of a package, you need the OK of the
> maintainer.
> If you contact a maintainer, and there is no response, what than?
>
> This is a barrier, unnecessary.
> Git stable & testing, branch.
> pull requests to testing,
> when some have reviewed && tested a package in testing, it goes to stable.
> all this public.
> you will see, this is much more productive and delivers better results.
>
> I try to help, e.g. I would have submitted an update for Qt, but without
> maintainer permission....
>
> The bureaucracy of SBo was long, and still is, an impediment for me.
> We should be aware of that.
> It is more easy for me to contribute to any opensouce project on github
> (I do this) than to SBo.
> Why? is this adequate for 2017?
>
> I do not want to criticize, I want to offer help, by questioning the
> project structure and suggest alternatives, I think I do this.
>
> /Harald

I think you hugely exaggerating.
The flow isn't perfect, but I can't agree it is as bad as you describe it.

Some maintainers are more responsive, other not.
Some will complain, other not.
Like in real life.

But it doesn't mean the project as a whole is bad.

I can't see the bureaucracy you mention.
What do you mean by that?

-- 
Best regards,
Andrzej Telszewski

From harald.achitz at gmail.com  Sat Jan 21 10:23:46 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sat, 21 Jan 2017 11:23:46 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
Message-ID: <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>

I makes me tired of hearing that if you do not find something is good, the
words complain, hugely exaggerating and others come.
This are passive aggressive communication patters, please don't. Please
focus on facts and the topic, what was not reacting maintainers.
As written, even if I point to, what I see as, problems, I try to help, and
was actually helpful, maybe not for you because you might miss some basic
understanding?
difference between low and high entry barriers,
difference between sending a patch / pull request to a project that simply
apply it if it passes QA,
 difference between such workflows, and that one of SBo, where you need to
contact maintainer
mention this makes everything bad? oh come on. experience the difference,
than think, than provide feedback

/Harald


2017-01-21 10:23 GMT+01:00 Andrzej Telszewski <atelszewski at gmail.com>:

> On 21/01/17 08:21, Harald Achitz wrote:
>
>> Hi,
>> help is difficult,
>> the SBo rules are clear,
>> If you sent an updated version of a package, you need the OK of the
>> maintainer.
>> If you contact a maintainer, and there is no response, what than?
>>
>> This is a barrier, unnecessary.
>> Git stable & testing, branch.
>> pull requests to testing,
>> when some have reviewed && tested a package in testing, it goes to stable.
>> all this public.
>> you will see, this is much more productive and delivers better results.
>>
>> I try to help, e.g. I would have submitted an update for Qt, but without
>> maintainer permission....
>>
>> The bureaucracy of SBo was long, and still is, an impediment for me.
>> We should be aware of that.
>> It is more easy for me to contribute to any opensouce project on github
>> (I do this) than to SBo.
>> Why? is this adequate for 2017?
>>
>> I do not want to criticize, I want to offer help, by questioning the
>> project structure and suggest alternatives, I think I do this.
>>
>> /Harald
>>
>
> I think you hugely exaggerating.
> The flow isn't perfect, but I can't agree it is as bad as you describe it.
>
> Some maintainers are more responsive, other not.
> Some will complain, other not.
> Like in real life.
>
> But it doesn't mean the project as a whole is bad.
>
> I can't see the bureaucracy you mention.
> What do you mean by that?
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170121/a2167eed/attachment.html>

From baildon.research at googlemail.com  Sat Jan 21 10:33:18 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Sat, 21 Jan 2017 10:33:18 +0000
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
Message-ID: <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>

> difference between sending a patch / pull request to a project that simply
> apply it if it passes QA,
>  difference between such workflows, and that one of SBo, where you need to
> contact maintainer

Perhaps you can help me, because it's not clear.
Exactly who in this workflow is going to do QA?

-D.

From harald.achitz at gmail.com  Sat Jan 21 10:42:41 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sat, 21 Jan 2017 11:42:41 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
Message-ID: <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>

as mentioned in the earlier mail, for example
stable , testing, pull requests into testing, who wants can test, if no
problem reports, or some people say OK, (to be defined) it goes to stable.
the QA happens twice, once when apply the pull request,similar what is
already done today, so no more work, and than by using the testing by who
ever want.
the pull request into stable becomes a noop, but is a last additional check.

there might be other possibilities for creating work flows that include
some QA without adding additional work to 1 person, eventually even reduce
it, including using the issue tracker an gitlab or github,
but I miss the time now to make an introduction into project management at
this time
and for SBo I would see this, or something similar, as a possibility that
maybe works  together with existing tools (just use a different branch)
Important is to be able to discuss such topics without getting passive
aggressive destructive comments, because I think we all want to use the
spare time we have productive.


/Harald





2017-01-21 11:33 GMT+01:00 David Spencer <baildon.research at googlemail.com>:

> > difference between sending a patch / pull request to a project that
> simply
> > apply it if it passes QA,
> >  difference between such workflows, and that one of SBo, where you need
> to
> > contact maintainer
>
> Perhaps you can help me, because it's not clear.
> Exactly who in this workflow is going to do QA?
>
> -D.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170121/408a0697/attachment-0001.html>

From matteo.bernardini at gmail.com  Sat Jan 21 10:45:33 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 21 Jan 2017 11:45:33 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
Message-ID: <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>

2017-01-21 11:42 GMT+01:00 Harald Achitz <harald.achitz at gmail.com>:
> as mentioned in the earlier mail, for example
> stable , testing, pull requests into testing, who wants can test, if no
> problem reports, or some people say OK, (to be defined) it goes to stable.
> the QA happens twice, once when apply the pull request,similar what is
> already done today, so no more work, and than by using the testing by who
> ever want.
> the pull request into stable becomes a noop, but is a last additional check.
>
> there might be other possibilities for creating work flows that include some
> QA without adding additional work to 1 person, eventually even reduce it,
> including using the issue tracker an gitlab or github,
> but I miss the time now to make an introduction into project management at
> this time
> and for SBo I would see this, or something similar, as a possibility that
> maybe works  together with existing tools (just use a different branch)
> Important is to be able to discuss such topics without getting passive
> aggressive destructive comments, because I think we all want to use the
> spare time we have productive.

maybe it's me but I still can't understand also from this answer who's
gonna do the QA...

Matteo

From baildon.research at googlemail.com  Sat Jan 21 10:55:53 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Sat, 21 Jan 2017 10:55:53 +0000
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
Message-ID: <CAMt7G9SFU1kzGAWu5rV+8de9kBujR0c7QR5uqUFgY3e0UaW9LA@mail.gmail.com>

> maybe it's me but I still can't understand also from this answer who's
> gonna do the QA...

If it's the maintainer, why would they respond to a pull request if
they don't respond to email?

If it's anybody, how do we (the community) know they have done enough
tests, follow upstream mailing lists looking for trouble reports, have
talked with other maintainers about dependencies, ...

If it's the SBo admins, the only testing we can do is building -- we
can't learn how to *use* 6000 packages.

If it's nobody ("if no problem reports") then we can automate the
build process ;-) but even if we had 6000 sets of unit tests it
wouldn't catch as many problems as an experienced human.

-D.
"Never ask a question unless you already know the answer" ;-)

From harald.achitz at gmail.com  Sat Jan 21 10:56:11 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sat, 21 Jan 2017 11:56:11 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
Message-ID: <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>

ok, slowly, one more time
1) the one who is sending the pull request
2) the one who is applying the pull request
3) those who use the package in testing,
4) merging testing into stable at the time a package can be considered as
tested, eg due to positive feedback on a issue tracer.
more quality control, less work for a single person through more
involvement of the community.

and if you can not see why this is less work for a single person and more
quality control, than sory, I can not explain, search projects that work
like that, participate, learn, than make suggestions for improvement
/Harald




2017-01-21 11:45 GMT+01:00 Matteo Bernardini <matteo.bernardini at gmail.com>:

> 2017-01-21 11:42 GMT+01:00 Harald Achitz <harald.achitz at gmail.com>:
> > as mentioned in the earlier mail, for example
> > stable , testing, pull requests into testing, who wants can test, if no
> > problem reports, or some people say OK, (to be defined) it goes to
> stable.
> > the QA happens twice, once when apply the pull request,similar what is
> > already done today, so no more work, and than by using the testing by who
> > ever want.
> > the pull request into stable becomes a noop, but is a last additional
> check.
> >
> > there might be other possibilities for creating work flows that include
> some
> > QA without adding additional work to 1 person, eventually even reduce it,
> > including using the issue tracker an gitlab or github,
> > but I miss the time now to make an introduction into project management
> at
> > this time
> > and for SBo I would see this, or something similar, as a possibility that
> > maybe works  together with existing tools (just use a different branch)
> > Important is to be able to discuss such topics without getting passive
> > aggressive destructive comments, because I think we all want to use the
> > spare time we have productive.
>
> maybe it's me but I still can't understand also from this answer who's
> gonna do the QA...
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170121/519453fb/attachment.html>

From atelszewski at gmail.com  Sat Jan 21 10:56:28 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 Jan 2017 11:56:28 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
 <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
Message-ID: <b0d41be1-2648-9f72-9942-3e6027ec6507@gmail.com>

On 21/01/17 11:56, Harald Achitz wrote:
> ok, slowly, one more time
> 1) the one who is sending the pull request
> 2) the one who is applying the pull request
> 3) those who use the package in testing,
> 4) merging testing into stable at the time a package can be considered
> as tested, eg due to positive feedback on a issue tracer.
> more quality control, less work for a single person through more
> involvement of the community.
>
> and if you can not see why this is less work for a single person and
> more quality control, than sory, I can not explain, search projects that
> work like that, participate, learn, than make suggestions for improvement
> /Harald
>

Just a quick reminder, please don't top-post.

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Sat Jan 21 11:09:24 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 21 Jan 2017 12:09:24 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
 <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
Message-ID: <CAPsDuS4s2=N-dhdzG6k3RThaGO-0VBXvA3xCZ6+dZzm6oae+eQ@mail.gmail.com>

2017-01-21 11:56 GMT+01:00 Harald Achitz <harald.achitz at gmail.com>:
> ok, slowly, one more time
> 1) the one who is sending the pull request

this is the first problem, as most of the times there aren't any pull
request but "hey, X has been updated to W.Y.Z, update it ASAP!"

> 2) the one who is applying the pull request

David already answered to it in his last mail: we have too many
scripts and it's not reasonable that we test stuff in such a worflow.
in the qt-5.x example you made before, assuming and thoughly QA
process, that will involve testing the new build (and you know the
time it takes), rebuilding and testing everything depending on it
(also optionally) and using it for a reasonable time.
and qt-5.x is just one of the thousands SlackBuilds we have in our repository

> 3) those who use the package in testing,

we cannot have any assurance that people will use thoughly everything
we put on such a branch: people don't do that even with the /testing
stuff in Slackware (see, as an example, who adopted the new gcc in
current's /testing).

> 4) merging testing into stable at the time a package can be considered as
> tested, eg due to positive feedback on a issue tracer.
> more quality control, less work for a single person through more involvement
> of the community.

unfortunately, for the reason stated above, things don't go this way:
maybe you are speakng about stuff where there are a lot of more people
involved (admins, maintainers and users).

Matteo

From harald.achitz at gmail.com  Sat Jan 21 11:13:07 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sat, 21 Jan 2017 12:13:07 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPsDuS4s2=N-dhdzG6k3RThaGO-0VBXvA3xCZ6+dZzm6oae+eQ@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
 <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
 <CAPsDuS4s2=N-dhdzG6k3RThaGO-0VBXvA3xCZ6+dZzm6oae+eQ@mail.gmail.com>
Message-ID: <CAPh+tzP5+_bhnhbcecVd3Ge_LZQrwe_gWio4ibvGuZezN5a9RQ@mail.gmail.com>

there are no pull request because of missing chances , high entry barriers
, ask the maintainer, and similar
I am talking about projects that reduced work for 1 persons, as mentioned,
and now I quit with this,
I gave you knowledge,f feel free to ignore or discuss it to death,
have a nice weekend




2017-01-21 12:09 GMT+01:00 Matteo Bernardini <matteo.bernardini at gmail.com>:

> 2017-01-21 11:56 GMT+01:00 Harald Achitz <harald.achitz at gmail.com>:
> > ok, slowly, one more time
> > 1) the one who is sending the pull request
>
> this is the first problem, as most of the times there aren't any pull
> request but "hey, X has been updated to W.Y.Z, update it ASAP!"
>
> > 2) the one who is applying the pull request
>
> David already answered to it in his last mail: we have too many
> scripts and it's not reasonable that we test stuff in such a worflow.
> in the qt-5.x example you made before, assuming and thoughly QA
> process, that will involve testing the new build (and you know the
> time it takes), rebuilding and testing everything depending on it
> (also optionally) and using it for a reasonable time.
> and qt-5.x is just one of the thousands SlackBuilds we have in our
> repository
>
> > 3) those who use the package in testing,
>
> we cannot have any assurance that people will use thoughly everything
> we put on such a branch: people don't do that even with the /testing
> stuff in Slackware (see, as an example, who adopted the new gcc in
> current's /testing).
>
> > 4) merging testing into stable at the time a package can be considered as
> > tested, eg due to positive feedback on a issue tracer.
> > more quality control, less work for a single person through more
> involvement
> > of the community.
>
> unfortunately, for the reason stated above, things don't go this way:
> maybe you are speakng about stuff where there are a lot of more people
> involved (admins, maintainers and users).
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170121/dfe245ad/attachment-0001.html>

From atelszewski at gmail.com  Sat Jan 21 11:10:11 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 Jan 2017 12:10:11 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
 <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
Message-ID: <b88d6d5e-f4b0-9d7f-3915-f486a563e44c@gmail.com>

On 21/01/17 11:56, Harald Achitz wrote:
> ok, slowly, one more time
> 1) the one who is sending the pull request
> 2) the one who is applying the pull request
> 3) those who use the package in testing,
> 4) merging testing into stable at the time a package can be considered
> as tested, eg due to positive feedback on a issue tracer.
> more quality control, less work for a single person through more
> involvement of the community.
>
> and if you can not see why this is less work for a single person and
> more quality control, than sory, I can not explain, search projects that
> work like that, participate, learn, than make suggestions for improvement
> /Harald

Keep in mind that the particular SlackBuild is managed by the maintainer.
It is he who decides what happens with it.

You can't stop the maintainer from pushing the latest version as long as 
the core Slackware dependencies does not need an update.

As I mentioned somewhere before, there is no more QA than just testing 
if the particular version works. Nobody (almost?) looks at the code.

Surely, there are occasionally some problems.
There is room for improvement.
But I don't think they mandate the changes you think of.

-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Sat Jan 21 11:21:40 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Sat, 21 Jan 2017 11:21:40 +0000
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAPsDuS4s2=N-dhdzG6k3RThaGO-0VBXvA3xCZ6+dZzm6oae+eQ@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
 <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
 <CAPsDuS4s2=N-dhdzG6k3RThaGO-0VBXvA3xCZ6+dZzm6oae+eQ@mail.gmail.com>
Message-ID: <CAMt7G9Qs0OnAVCyjR0S_vEFEW_u5STbTPKh5zzP-tM0Q4dKCYQ@mail.gmail.com>

> this is the first problem, as most of the times there aren't any pull
> request but "hey, X has been updated to W.Y.Z, update it ASAP!"

I know you have had some bad experiences with pull requsts into your
unofficial -current repository.

But if we listen to the idea behind Harald's suggestion, maybe we
could have something on Gitlab for maintainers who opt-in, using
protected branches with multiple maintainers for particular packages?

Just an idea -- we still don't really know what to do with Gitlab ;-)
-D.

From matteo.bernardini at gmail.com  Sat Jan 21 11:32:35 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 21 Jan 2017 12:32:35 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAMt7G9Qs0OnAVCyjR0S_vEFEW_u5STbTPKh5zzP-tM0Q4dKCYQ@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
 <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
 <CAPsDuS4s2=N-dhdzG6k3RThaGO-0VBXvA3xCZ6+dZzm6oae+eQ@mail.gmail.com>
 <CAMt7G9Qs0OnAVCyjR0S_vEFEW_u5STbTPKh5zzP-tM0Q4dKCYQ@mail.gmail.com>
Message-ID: <CAPsDuS5F-nvFkMVWdepvPPmg1NVaciWeRqq=dSuqHE-pC09POA@mail.gmail.com>

2017-01-21 12:21 GMT+01:00 David Spencer <baildon.research at googlemail.com>:
>> this is the first problem, as most of the times there aren't any pull
>> request but "hey, X has been updated to W.Y.Z, update it ASAP!"
>
> I know you have had some bad experiences with pull requsts into your
> unofficial -current repository.

actually I was talking about what every maintainer (me too) finds in
its email, written by people that usually don't spend one minute to
test such updates (and then the maintainer has to do it).
properly pull request are really a few.

> But if we listen to the idea behind Harald's suggestion, maybe we
> could have something on Gitlab for maintainers who opt-in, using
> protected branches with multiple maintainers for particular packages?

to say the truth I was thinking about it somithing like that too, but
I was thinking also that wouldn't be that different from what we have
now with the user/*/updates branches on the main repository: in this
new situation we will still accept updates only by maintainers, isn't
it?
Harald was talking about accepting updates from non-maintainers and
that, IMHO, won't give any guarantee (not to say that some maintainers
won't be too happy)...

> Just an idea -- we still don't really know what to do with Gitlab ;-)

well, trying won't hurt, we can always say later "ok, we were joking!" :D

Matteo

From atelszewski at gmail.com  Sat Jan 21 11:32:39 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 Jan 2017 12:32:39 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <CAMt7G9Qs0OnAVCyjR0S_vEFEW_u5STbTPKh5zzP-tM0Q4dKCYQ@mail.gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
 <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
 <CAPsDuS4s2=N-dhdzG6k3RThaGO-0VBXvA3xCZ6+dZzm6oae+eQ@mail.gmail.com>
 <CAMt7G9Qs0OnAVCyjR0S_vEFEW_u5STbTPKh5zzP-tM0Q4dKCYQ@mail.gmail.com>
Message-ID: <5b715d2e-bd6d-8334-05d1-d4a556ba01c5@gmail.com>

On 21/01/17 12:21, David Spencer wrote:
>> this is the first problem, as most of the times there aren't any pull
>> request but "hey, X has been updated to W.Y.Z, update it ASAP!"
>
> I know you have had some bad experiences with pull requsts into your
> unofficial -current repository.
>
> But if we listen to the idea behind Harald's suggestion, maybe we
> could have something on Gitlab for maintainers who opt-in, using
> protected branches with multiple maintainers for particular packages?
>
> Just an idea -- we still don't really know what to do with Gitlab ;-)
> -D.

As with a any good design, please first define the problems you want to 
solve.

I'm really having hard times finding major problems with SBo, both as a 
maintainer and user.

As long as the maintainer is in the position of taking the final 
decision, there is not much to do. And I prefer that it stays this way, 
i.e. the maintainer decides.

There is room for improvement, maintainers responsiveness might be one 
of them. So, if that's the problem, try finding a way how to change it. 
But in that case, it might require changing of the policy.

-- 
Best regards,
Andrzej Telszewski

From info at microlinux.fr  Sat Jan 21 12:33:35 2017
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sat, 21 Jan 2017 13:33:35 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <5b715d2e-bd6d-8334-05d1-d4a556ba01c5@gmail.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
 <20170121005421.1a8e004d@hamalayi.mnt>
 <CAPh+tzNH7r7yPEoJdDbY=dCPj+jKRD9ZKk+nGH1gxVhG9UBd_Q@mail.gmail.com>
 <ac12fcf7-4e45-146a-0bc9-2a04d55a11b5@gmail.com>
 <CAPh+tzNpVOQFaQS=dz+UBiUk26th_r5df03V4YJhzcXcpTmQyg@mail.gmail.com>
 <CAMt7G9QDJWmWnok3o0YEbar9+qb=7SGP+XeELNrB6SzsCHztVQ@mail.gmail.com>
 <CAPh+tzMmSLmOhRwPz-mO4TfvQw2keM80-CurZiTY+tg+igrr-Q@mail.gmail.com>
 <CAPsDuS4EhU7QqBq0vQ_g8jjf=9XYUwU+jKWkQypcKqj50+K-nw@mail.gmail.com>
 <CAPh+tzPknqCRVD-74CK_R-46FtKAzouWmCpG2O9nmr=attep+A@mail.gmail.com>
 <CAPsDuS4s2=N-dhdzG6k3RThaGO-0VBXvA3xCZ6+dZzm6oae+eQ@mail.gmail.com>
 <CAMt7G9Qs0OnAVCyjR0S_vEFEW_u5STbTPKh5zzP-tM0Q4dKCYQ@mail.gmail.com>
 <5b715d2e-bd6d-8334-05d1-d4a556ba01c5@gmail.com>
Message-ID: <dc00d798-808c-340c-f7a1-9c16eb910185@microlinux.fr>

Le 21/01/2017 ? 12:32, Andrzej Telszewski a ?crit :
> I'm really having hard times finding major problems with SBo, both as a
> maintainer and user.

Same here. SBo obeys to the KISS principle pretty much like its
Slackware foundation.

Recently I was annoyed by VirtualBox lagging several versions behind.
The old 5.0.14 version had some problems with RHEL guests, and 5.0.30
seemed to have corrected the problem. So I emailed Heinz Wiesinger, the
maintainer, and politely asked him if he could provide an update. Which
he did a few days later.

Unfortunately, folks aren't always polite when asking for updates.

http://www.linuxquestions.org/questions/microlinux-mled-116/mled-update-packages-4175591077/

:o)

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

From ruben at rbn.im  Sat Jan 21 13:59:41 2017
From: ruben at rbn.im (Ruben Schuller)
Date: Sat, 21 Jan 2017 14:59:41 +0100
Subject: [Slackbuilds-users] Package versions
In-Reply-To: <20170119124646.29147@web007.roc2.bluetie.com>
References: <20170119124646.29147@web007.roc2.bluetie.com>
Message-ID: <20170121145941.7c38d0a6@kiwi.kuchen>

Hi!

Just my two cents: I don't think that SlackBuilds on SBo are that
outdated. Most of the time they are a rather new version. I'm guilty
myself for not updating some of my SlackBuilds that often ;)

Like some others posted here, I think that Gitlab (or something like
that) would make updating things easier, especially because the
SBo-admins _do_ review the things submitted. It would just be a nicer
"workflow" than uploading a tarball, waiting for review, getting a mail
about a problem, (forgetting about the mail... ,) fixing it locally and
resubmitting it. With the git frontends available there can be comments
directly associated with the merge request (or how the software calls
it), which makes it sometimes easier to see the problem. If well
implemented, one could also think of that the maintainers of single
SlackBuilds get merge requests, review them, and then create a request
to merge into the main repository.

I'm fine though with the current way things are handled, alas they are
sometimes a bit cumbersome. On the other hand creating a gitlab setup
for this size of project has to be well thought through, otherwise git
tends to bite ;)

The admins of SBo have my respect for managing it in their free
time, amazing job :)

Ruben

From reedych at reedych.pw  Sat Jan 21 16:42:48 2017
From: reedych at reedych.pw (reedych)
Date: Sat, 21 Jan 2017 22:42:48 +0600
Subject: [Slackbuilds-users] perl-WWW-Curl not buildable
Message-ID: <20170121224248.7c59df20@slackware>

Can anyone check it?

From hostmaster at slackonly.com  Sat Jan 21 16:49:31 2017
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Sat, 21 Jan 2017 08:49:31 -0800
Subject: [Slackbuilds-users] perl-WWW-Curl not buildable
In-Reply-To: <20170121224248.7c59df20@slackware>
References: <20170121224248.7c59df20@slackware>
Message-ID: <5336bb6b-efd7-92b3-f4e0-a99465e78b5a@slackonly.com>

On 01/21/2017 08:42 AM, reedych wrote:
> Can anyone check it?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
Working fine here (Slackware64):
perl-WWW-Curl:
   MD5SUM check for WWW-Curl-4.17.tar.gz ... OK
   Building package perl-WWW-Curl-4.17-x86_64-2_SBo.tgz ... OK

From reedych at reedych.pw  Sat Jan 21 16:59:31 2017
From: reedych at reedych.pw (reedych)
Date: Sat, 21 Jan 2017 22:59:31 +0600
Subject: [Slackbuilds-users] perl-WWW-Curl not buildable
In-Reply-To: <5336bb6b-efd7-92b3-f4e0-a99465e78b5a@slackonly.com>
References: <20170121224248.7c59df20@slackware>
 <5336bb6b-efd7-92b3-f4e0-a99465e78b5a@slackonly.com>
Message-ID: <20170121225931.736328df@slackware>

? Sat, 21 Jan 2017 08:49:31 -0800
Panagiotis Nikolaou <hostmaster at slackonly.com> ?????:

> On 01/21/2017 08:42 AM, reedych wrote:
> > Can anyone check it?
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives -
> > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -
> > https://slackbuilds.org/faq/ 
> Working fine here (Slackware64):
> perl-WWW-Curl:
>    MD5SUM check for WWW-Curl-4.17.tar.gz ... OK
>    Building package perl-WWW-Curl-4.17-x86_64-2_SBo.tgz ... OK
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

thx!

From info at microlinux.fr  Sat Jan 21 18:09:50 2017
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sat, 21 Jan 2017 19:09:50 +0100
Subject: [Slackbuilds-users] Glances 2.8
Message-ID: <e4afca58-7ac6-67c6-bdac-725a53cc2df7@microlinux.fr>

Hi everybody,

In the wake of the discussion about package updates, I thought I might
give you a little heads-up.

SBo is currently providing Glances 2.5.1. Version 2.8 has just been
released by Nicolas Hennion. I gave it a spin, and it builds fine
against the same dependencies. A simple version bump does the trick

It's worth the update, since it provides some nifty extra functionality.

Cheers,

Niki
-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

From jebrhansen+SBo at gmail.com  Sat Jan 21 22:08:31 2017
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sat, 21 Jan 2017 22:08:31 +0000
Subject: [Slackbuilds-users] Glances 2.8
In-Reply-To: <e4afca58-7ac6-67c6-bdac-725a53cc2df7@microlinux.fr>
References: <e4afca58-7ac6-67c6-bdac-725a53cc2df7@microlinux.fr>
Message-ID: <CANi9qSt6PYOFVsrdUMUXHEA2v71wCkKyYm7N1deYLmnHZDHK5A@mail.gmail.com>

Wasn't the result of that discussion that the maintainer should be notified
of possible updates since not all of them subscribe to the list? The SBo
admins aren't likely to step on the toes of maintainers unless there's a
serious reason for the update and the maintainer can't be reached.

Jeremy

On Sat, Jan 21, 2017, 1:10 PM Nicolas Kovacs <info at microlinux.fr> wrote:

> Hi everybody,
>
> In the wake of the discussion about package updates, I thought I might
> give you a little heads-up.
>
> SBo is currently providing Glances 2.5.1. Version 2.8 has just been
> released by Nicolas Hennion. I gave it a spin, and it builds fine
> against the same dependencies. A simple version bump does the trick
>
> It's worth the update, since it provides some nifty extra functionality.
>
> Cheers,
>
> Niki
> --
> Microlinux - Solutions informatiques durables
> 7, place de l'?glise - 30730 Montpezat
> Web  : http://www.microlinux.fr
> Mail : info at microlinux.fr
> T?l. : 04 66 63 10 32
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170121/35298b35/attachment.html>

From vbatts at gmail.com  Sun Jan 22 17:28:45 2017
From: vbatts at gmail.com (Vincent Batts)
Date: Sun, 22 Jan 2017 17:28:45 +0000
Subject: [Slackbuilds-users] docker updates
Message-ID: <CAN6Zp5wh9TrA0poBSLqNzpqhbHufT-v-G=uTXddOpgqG1SesjA@mail.gmail.com>

I've had a number of folks email me for updates to Docker. Only this week I
replied to
Asaf Ohayon that he can take over ownership of the build. (If he's still
interested).

There have been a few reasons I've dragged my feet on pushing out an
update. Sorry if this has been a particular inconvenience to anyone. Docker
1.8.x was a solid release. Many companies kept it as a long-term version.
Every new version has added splashy new features, while providing
fixes for prior versions and unfortunately sometimes new regressions to
tools that use/depend on docker (see kubernetes et al).

Another part of the hold back has been how Docker Inc is staging itself
more as a proprietary product (and some services), and less as an open
community. This is part of the splitting off of `runc` and more recently
`containerd`. In the few release or so, it is sounding like even having a
build of `docker` in linux distributions will be difficult without taking
the binary build straight from Docker Inc. Otherwise the distribution will
likely have to do full rebranding to not use the word "docker" (like
firefox and debian's IceWeasel). Trademark violations could be a concern.
Be that what it is, it's still a useful tool.

There are other container tools in the community and some are becoming
viable alternatives to the `docker` cli. LXC is now in slackware stock.
This is where groups like the Open Containers Initiative (OCI) (
https://github.com/opencontainers/image-spec/) is working to ensure
portability of the container images, regardless of the tool that users are
working with.
It would be great for folks to define their use-case and use what makes
sense.

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

From vbatts at gmail.com  Sun Jan 22 17:38:31 2017
From: vbatts at gmail.com (Vincent Batts)
Date: Sun, 22 Jan 2017 17:38:31 +0000
Subject: [Slackbuilds-users] Update request Docker
In-Reply-To: <CAMt7G9SHK-CYzWyGJ8PYQ=1xDqNEiMs_tfE8=WT5Le_rDFYDHQ@mail.gmail.com>
References: <04d7e5b8-8041-2d88-ace3-bf1c0e0a2ce0@riseup.net>
 <CAAcyf-rAs2osXM-UvNYf4wKWWjSF0YKX_-w9Utcy7ni7Q8JbSw@mail.gmail.com>
 <3500fdda-6050-077a-706d-d25be8c52946@riseup.net>
 <CAAcyf-pkBBbZLONTCorLtrTQ=LPxHMHaygM9Gtt2LTWxPj0g5A@mail.gmail.com>
 <8074f3ee-907d-fc92-e027-715d7f36b249@riseup.net>
 <51a96162e8be46bc9ee72beec2442dba@lodpp.net>
 <9d71b915-3b49-ebb5-a35b-c68840ddcadd@riseup.net>
 <CAMt7G9QdoRO03Ve2xBRsBor=deTip31MBDT_CZR6X9JmVKv=GQ@mail.gmail.com>
 <a653e1bb-c633-1fc9-3f92-f2a414270a2c@gmail.com>
 <CAMt7G9SHK-CYzWyGJ8PYQ=1xDqNEiMs_tfE8=WT5Le_rDFYDHQ@mail.gmail.com>
Message-ID: <CAN6Zp5xKDAyFKcLFbexOX7HdrN2mQX6Fc62m9RK_Lp2C1nDSJQ@mail.gmail.com>

On Thu, Jan 19, 2017 at 3:06 PM David Spencer <
baildon.research at googlemail.com> wrote:

> > I wonder if you mean MPLAB.
>
>     bubblewrap 0.1.7
>     ===================
>
>     man pages (xsltproc):                         yes
>     SELinux:                                      no
>     setuid mode on make install:                  none
>     mysteriously satisfying to pop:               yes
>
> lol
> (and almost on-topic for an email thread about docker)
> -D.


Yeah. Soon I'll submit the build for flatpak. It uses ostree and bubblebrap
to provide containerized desktop applications (http://flatpak.org/).

But I do like bubblewrap (`bwrap`) a lot by itself. It makes for a more
complete alternative to `fakeroot` and something that, as application
developers start to consider, will allow running very interesting
applications that need "root" or similar uid to run as a limited user
(think a LAMP stack with each piece thinking it is httpd and mysql user).

Using tools like skopeo (https://github.com/projectatomic/skopeo) you can
copy a container image from an existing docker image, and then something
like bwrap-oci (https://github.com/projectatomic/bwrap-oci) to run that
image in bwrap as a non-root user.

vb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170122/1def8a83/attachment.html>

From kjhambrick at gmail.com  Sun Jan 22 20:42:45 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 22 Jan 2017 14:42:45 -0600
Subject: [Slackbuilds-users] perl-WWW-Curl not buildable
In-Reply-To: <20170121225931.736328df@slackware>
References: <20170121224248.7c59df20@slackware>
 <5336bb6b-efd7-92b3-f4e0-a99465e78b5a@slackonly.com>
 <20170121225931.736328df@slackware>
Message-ID: <CANBHt+OEsWXfeQqFtTfPCd7c+jFXODtULOx8_SgQGnH9actvMw@mail.gmail.com>

readych --

builds fine on my Slackware64 14.2 + Multilib box.

Build Log attached.

-- kjh

On Sat, Jan 21, 2017 at 10:59 AM, reedych <reedych at reedych.pw> wrote:

> ? Sat, 21 Jan 2017 08:49:31 -0800
> Panagiotis Nikolaou <hostmaster at slackonly.com> ?????:
>
> > On 01/21/2017 08:42 AM, reedych wrote:
> > > Can anyone check it?
> > > _______________________________________________
> > > SlackBuilds-users mailing list
> > > SlackBuilds-users at slackbuilds.org
> > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > > Archives -
> > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -
> > > https://slackbuilds.org/faq/
> > Working fine here (Slackware64):
> > perl-WWW-Curl:
> >    MD5SUM check for WWW-Curl-4.17.tar.gz ... OK
> >    Building package perl-WWW-Curl-4.17-x86_64-2_SBo.tgz ... OK
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
>
> thx!
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170122/345eae5a/attachment-0001.html>
-------------- next part --------------
perl-WWW-Curl.SlackBuild startup  at Sun Jan 22 14:37:59 CST 2017
WWW-Curl-4.17/
WWW-Curl-4.17/LICENSE
WWW-Curl-4.17/META.yml
WWW-Curl-4.17/typemap
WWW-Curl-4.17/template/
WWW-Curl-4.17/template/Easy.pm.tmpl
WWW-Curl-4.17/template/Share.pm.tmpl
WWW-Curl-4.17/lib/
WWW-Curl-4.17/lib/WWW/
WWW-Curl-4.17/lib/WWW/Curl/
WWW-Curl-4.17/lib/WWW/Curl/Form.pm
WWW-Curl-4.17/lib/WWW/Curl/Multi.pm
WWW-Curl-4.17/lib/WWW/Curl/Easy.pm
WWW-Curl-4.17/lib/WWW/Curl/Share.pm
WWW-Curl-4.17/lib/WWW/Curl.pm
WWW-Curl-4.17/README.Win32
WWW-Curl-4.17/Curl.xs
WWW-Curl-4.17/Makefile.PL
WWW-Curl-4.17/MANIFEST
WWW-Curl-4.17/inc/
WWW-Curl-4.17/inc/Module/
WWW-Curl-4.17/inc/Module/Install.pm
WWW-Curl-4.17/inc/Module/Install/
WWW-Curl-4.17/inc/Module/Install/MakeMaker.pm
WWW-Curl-4.17/inc/Module/Install/Metadata.pm
WWW-Curl-4.17/inc/Module/Install/External.pm
WWW-Curl-4.17/inc/Module/Install/Base.pm
WWW-Curl-4.17/inc/Module/Install/Makefile.pm
WWW-Curl-4.17/inc/Module/Install/Can.pm
WWW-Curl-4.17/t/
WWW-Curl-4.17/t/06http-post.t
WWW-Curl-4.17/t/07ftp-upload.t
WWW-Curl-4.17/t/17slist.t
WWW-Curl-4.17/t/21write-to-scalar.t
WWW-Curl-4.17/t/symbols-in-versions
WWW-Curl-4.17/t/05progress.t
WWW-Curl-4.17/t/19multi.t
WWW-Curl-4.17/t/pod.t
WWW-Curl-4.17/t/15duphandle-callback.t
WWW-Curl-4.17/t/10errbuf.t
WWW-Curl-4.17/t/02callbacks.t
WWW-Curl-4.17/t/pod-coverage.t
WWW-Curl-4.17/t/14duphandle.t
WWW-Curl-4.17/t/18twinhandles.t
WWW-Curl-4.17/t/04abort-test.t
WWW-Curl-4.17/t/new/
WWW-Curl-4.17/t/new/07errbuf.t
WWW-Curl-4.17/t/new/08duphandle.t
WWW-Curl-4.17/t/new/06http-post.t
WWW-Curl-4.17/t/new/03body-callback.t
WWW-Curl-4.17/t/new/04abort.t
WWW-Curl-4.17/t/new/02header-callback.t
WWW-Curl-4.17/t/new/05progress.t
WWW-Curl-4.17/t/new/10multi-callback.t
WWW-Curl-4.17/t/new/09duphandle-callback.t
WWW-Curl-4.17/t/new/README
WWW-Curl-4.17/t/new/01basic.t
WWW-Curl-4.17/t/new/00constants.t
WWW-Curl-4.17/t/meta.t
WWW-Curl-4.17/t/09times.t
WWW-Curl-4.17/t/08ssl.t
WWW-Curl-4.17/t/20undefined_subs.t
WWW-Curl-4.17/t/01basic.t
WWW-Curl-4.17/t/13slowleak.t
WWW-Curl-4.17/t/16formpost.t
WWW-Curl-4.17/t/00constants.t
WWW-Curl-4.17/README
WWW-Curl-4.17/Changes
patching file Makefile.PL
Locating required external dependency bin:curl-config... found at /usr/bin/curl-config.
The version is libcurl 7.51.0
Found curl.h in /usr/include/curl/curl.h
Skipping '#define CURL_STRICTER': does not define a symbol at Makefile.PL line 127, <H> line 34.
Skipping '#define CURL_DID_MEMORY_FUNC_TYPEDEFS': does not define a symbol at Makefile.PL line 127, <H> line 399.
Building curlopt-constants.c for your libcurl version
Building Easy.pm constants for your libcurl version
Building Share.pm constants for your libcurl version
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for WWW::Curl
Writing MYMETA.yml and MYMETA.json
cp lib/WWW/Curl/Multi.pm blib/lib/WWW/Curl/Multi.pm
cp lib/WWW/Curl.pm blib/lib/WWW/Curl.pm
cp lib/WWW/Curl/Form.pm blib/lib/WWW/Curl/Form.pm
cp lib/WWW/Curl/Easy.pm blib/lib/WWW/Curl/Easy.pm
cp lib/WWW/Curl/Share.pm blib/lib/WWW/Curl/Share.pm
Running Mkbootstrap for WWW::Curl ()
chmod 644 "Curl.bs"
"/usr/bin/perl5.22.2" "-Iinc" "/usr/share/perl5/ExtUtils/xsubpp"  -typemap "/usr/share/perl5/ExtUtils/typemap" -typemap "typemap"  Curl.xs > Curl.xsc && mv Curl.xsc Curl.c
cc -c  -I/usr/include -D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -O2 -fPIC   -DVERSION=\"4.17\" -DXS_VERSION=\"4.17\" -fPIC "-I/usr/lib64/perl5/CORE"   Curl.c
In file included from Curl.xs:574:0:
curlopt-constants.c: In function 'constant':
curlopt-constants.c:2048:44: warning: overflow in implicit constant conversion [-Woverflow]
             if (strEQ(name, "ANY")) return CURLAUTH_ANY;
                                            ^
curlopt-constants.c:2049:48: warning: overflow in implicit constant conversion [-Woverflow]
             if (strEQ(name, "ANYSAFE")) return CURLAUTH_ANYSAFE;
                                                ^
rm -f blib/arch/auto/WWW/Curl/Curl.so
LD_RUN_PATH="/usr/lib64" cc  -shared -O2 -fPIC -L/usr/local/lib -fstack-protector-strong Curl.o  -o blib/arch/auto/WWW/Curl/Curl.so 	\
   -lcurl  	\
  
chmod 755 blib/arch/auto/WWW/Curl/Curl.so
"/usr/bin/perl5.22.2" "-Iinc" -MExtUtils::Command::MM -e 'cp_nonempty' -- Curl.bs blib/arch/auto/WWW/Curl/Curl.bs 644
Manifying 1 pod document
Running Mkbootstrap for WWW::Curl ()
chmod 644 "Curl.bs"
PERL_DL_NONLAZY=1 "/usr/bin/perl5.22.2" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/*.t
t/00constants.t ........... ok
t/01basic.t ............... ok
t/02callbacks.t ........... ok
t/04abort-test.t .......... ok
t/05progress.t ............ ok
t/06http-post.t ........... skipped: Not performing http POST/upload tests
t/07ftp-upload.t .......... skipped: Not performing ftp upload tests
t/08ssl.t ................. ok
t/09times.t ............... ok
t/10errbuf.t .............. ok
t/13slowleak.t ............ skipped: Not performing slow leakage regression test
t/14duphandle.t ........... ok
t/15duphandle-callback.t .. ok
t/16formpost.t ............ skipped: Not performing POST
t/17slist.t ............... skipped: Not performing printenv cgi tests
t/18twinhandles.t ......... ok
t/19multi.t ............... ok
t/20undefined_subs.t ...... ok
t/21write-to-scalar.t ..... ok
t/meta.t .................. skipped: Test::CPAN::Meta required for testing META.yml
t/pod-coverage.t .......... skipped: Test::Pod::Coverage 1.04 required for testing POD coverage
t/pod.t ................... skipped: Test::Pod 1.14 required for testing POD
All tests successful.
Files=22, Tests=816, 11 wallclock secs ( 0.09 usr  0.02 sys +  0.73 cusr  0.08 csys =  0.92 CPU)
Result: PASS
Manifying 1 pod document
Files found in blib/arch: installing files in blib/lib into architecture dependent library tree
Installing /tmp/SBo/package-perl-WWW-Curl/usr/lib64/perl5/vendor_perl/auto/WWW/Curl/Curl.so
Installing /tmp/SBo/package-perl-WWW-Curl/usr/lib64/perl5/vendor_perl/WWW/Curl.pm
Installing /tmp/SBo/package-perl-WWW-Curl/usr/lib64/perl5/vendor_perl/WWW/Curl/Easy.pm
Installing /tmp/SBo/package-perl-WWW-Curl/usr/lib64/perl5/vendor_perl/WWW/Curl/Multi.pm
Installing /tmp/SBo/package-perl-WWW-Curl/usr/lib64/perl5/vendor_perl/WWW/Curl/Share.pm
Installing /tmp/SBo/package-perl-WWW-Curl/usr/lib64/perl5/vendor_perl/WWW/Curl/Form.pm
Installing /tmp/SBo/package-perl-WWW-Curl/usr/man/man3/WWW::Curl.3
Appending installation info to /tmp/SBo/package-perl-WWW-Curl/usr/lib64/perl5/perllocal.pod

Slackware package maker, version 3.141593.

Searching for symbolic links:

No symbolic links were found, so we won't make an installation script.
You can make your own later in ./install/doinst.sh and rebuild the
package if you like.

This next step is optional - you can set the directories in your package
to some sane permissions. If any of the directories in your package have
special permissions, then DO NOT reset them here!

Would you like to reset all directory permissions to 755 (drwxr-xr-x) and
directory ownerships to root.root ([y]es, [n]o)? n

Creating Slackware package:  /tmp/perl-WWW-Curl-4.17-x86_64-2_SBo.tgz

./
usr/
usr/man/
usr/man/man3/
usr/man/man3/WWW::Curl.3.gz
usr/doc/
usr/doc/perl-WWW-Curl-4.17/
usr/doc/perl-WWW-Curl-4.17/perl-WWW-Curl.SlackBuild
usr/doc/perl-WWW-Curl-4.17/LICENSE
usr/doc/perl-WWW-Curl-4.17/README
usr/doc/perl-WWW-Curl-4.17/Changes
usr/doc/perl-WWW-Curl-4.17/MANIFEST
usr/lib64/
usr/lib64/perl5/
usr/lib64/perl5/vendor_perl/
usr/lib64/perl5/vendor_perl/auto/
usr/lib64/perl5/vendor_perl/auto/WWW/
usr/lib64/perl5/vendor_perl/auto/WWW/Curl/
usr/lib64/perl5/vendor_perl/auto/WWW/Curl/Curl.so
usr/lib64/perl5/vendor_perl/WWW/
usr/lib64/perl5/vendor_perl/WWW/Curl/
usr/lib64/perl5/vendor_perl/WWW/Curl/Easy.pm
usr/lib64/perl5/vendor_perl/WWW/Curl/Multi.pm
usr/lib64/perl5/vendor_perl/WWW/Curl/Share.pm
usr/lib64/perl5/vendor_perl/WWW/Curl/Form.pm
usr/lib64/perl5/vendor_perl/WWW/Curl.pm
install/
install/slack-desc

Slackware package /tmp/perl-WWW-Curl-4.17-x86_64-2_SBo.tgz created.

perl-WWW-Curl.SlackBuild complete at Sun Jan 22 14:38:12 CST 2017 ... RetCode = 0

From willysr at slackbuilds.org  Mon Jan 23 00:49:33 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 23 Jan 2017 07:49:33 +0700
Subject: [Slackbuilds-users] docker updates
In-Reply-To: <CAN6Zp5wh9TrA0poBSLqNzpqhbHufT-v-G=uTXddOpgqG1SesjA@mail.gmail.com>
References: <CAN6Zp5wh9TrA0poBSLqNzpqhbHufT-v-G=uTXddOpgqG1SesjA@mail.gmail.com>
Message-ID: <d99db2f0-955f-7930-a335-69c76b1eccfa@slackbuilds.org>

> I've had a number of folks email me for updates to Docker. Only this week I
> replied to
> Asaf Ohayon that he can take over ownership of the build. (If he's still
> interested).

Just FYI, Asaf's last commit was in 2013


-- 
Willy Sudiarto Raharjo

-------------- 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/20170123/5349e52c/attachment.asc>

From vbatts at gmail.com  Mon Jan 23 11:38:10 2017
From: vbatts at gmail.com (Vincent Batts)
Date: Mon, 23 Jan 2017 11:38:10 +0000
Subject: [Slackbuilds-users] docker updates
In-Reply-To: <d99db2f0-955f-7930-a335-69c76b1eccfa@slackbuilds.org>
References: <CAN6Zp5wh9TrA0poBSLqNzpqhbHufT-v-G=uTXddOpgqG1SesjA@mail.gmail.com>
 <d99db2f0-955f-7930-a335-69c76b1eccfa@slackbuilds.org>
Message-ID: <CAN6Zp5xCfzFva0KFKx1wFbGnoC5G_ywkm_bspyfULkp6DNr9gw@mail.gmail.com>

Oh interesting. I saw he had a number of builds. He had just emailed me a
month or so ago.

On Sun, Jan 22, 2017, 19:49 Willy Sudiarto Raharjo <willysr at slackbuilds.org>
wrote:

> > I've had a number of folks email me for updates to Docker. Only this
> week I
> > replied to
> > Asaf Ohayon that he can take over ownership of the build. (If he's still
> > interested).
>
> Just FYI, Asaf's last commit was in 2013
>
>
> --
> Willy Sudiarto Raharjo
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170123/56d4e452/attachment.html>

From willysr at slackbuilds.org  Mon Jan 23 11:45:27 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 23 Jan 2017 18:45:27 +0700
Subject: [Slackbuilds-users] docker updates
In-Reply-To: <CAN6Zp5xCfzFva0KFKx1wFbGnoC5G_ywkm_bspyfULkp6DNr9gw@mail.gmail.com>
References: <CAN6Zp5wh9TrA0poBSLqNzpqhbHufT-v-G=uTXddOpgqG1SesjA@mail.gmail.com>
 <d99db2f0-955f-7930-a335-69c76b1eccfa@slackbuilds.org>
 <CAN6Zp5xCfzFva0KFKx1wFbGnoC5G_ywkm_bspyfULkp6DNr9gw@mail.gmail.com>
Message-ID: <64da0147-0172-e8bc-6c0f-a47ab8a5c318@slackbuilds.org>

> Oh interesting. I saw he had a number of builds. He had just emailed me a
> month or so ago.

Well, it seems that he somehow used 2 different names
Asaf Ohaion vs Asaf Ohayon

I only checked for one of them and yes, the other one is still active :)

-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Tue Jan 24 00:59:52 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 24 Jan 2017 07:59:52 +0700
Subject: [Slackbuilds-users] Updates - 20170124.1
Message-ID: <9c3d2511-0cda-30ff-7b24-4627c1b28ddc@slackbuilds.org>

Sorry for the unscheduled public update as we have some security updates
on this release, namely jdk, opus, and phpmyadmin.

We also have a new submission for flatpack, thanks to Vincent Batts and
more than 180+ other changes in just 3 days. Andre has just submitted
changes in ipython along with other jupyter new submission and now
ipython-mathjax is removed.

Another sorry for two of my own mistakes for not reviewing well so that
i miss 2 scripts that have an empty MD5SUM values: perl-Role-Tiny and
osm2pgrouting. They have been fixed on my branch, but it will be rolled
in the regular public update this weekend.

happy updating

Tue Jan 24 00:24:36 UTC 2017
academic/FCSalyzer: Updated for version 0.9.12_alpha.
academic/mendeleydesktop: Fix problems with QT5, move to /opt.
audio/aacplusenc: Minor cleanups.
audio/minimodem: Updated for version 0.24.
audio/opus: Updated for version 1.1.4.
audio/zita-ajbridge: Updated for version 0.7.0.
audio/zita-dpl1: Updated for version 0.1.0.
desktop/awesome: Updated for version 4.0.
desktop/caffeine-ng: Fixed doinst.sh.
desktop/flatpak: Added (sandboxing desktop applications).
desktop/kwalletcli: Updated for version 3.00.
desktop/neofetch: Updated for version 3.0.
desktop/smaragd: Fix DOWNLOAD url.
desktop/trayer-srg: Updated for version 20160817.
desktop/wmweather+: Updated for version 2.16.
development/Catch: Updated for version 1.6.1.
development/byacc: Updated for version 20161202.
development/conan: Updated for version 0.18.1.
development/diffoscope: Updated for version 69.
development/gisto: Fixed icon fix.
development/git-lfs: Updated for version 1.5.5.
development/ipython-mathjax: Removed (maintainer's request).
development/jdk: Updated for version 8u121.
development/jupyter-ipykernel: Added (IPython Kernel for Jupyter).
development/jupyter-nbformat: Added (Jupyter notebook format).
development/jupyter-notebook: Added (Jupyter interactive notebook).
development/jupyter-qtconsole: Added (Jupyter Qt Console).
development/jupyter_client: Added (Jupyter protocol client APIs).
development/jupyter_core: Added (core functionality of Jupyter).
development/makedepf90: Change EMAIL address.
development/mutagen: Updated for version 1.36.1.
development/pkgconf: Updated for version 1.2.0.
development/tig: Updated for version 2.2.1.
development/unittest-cpp: Updated for version 2.0.0. Use CMake
development/vscode: Fixed building errors.
games/atari++: Updated for version 1.81.
games/commandergenius: Updated for version 1.9.8.1beta.
games/glPortal: Added (3d physics based portal puzzle game).
games/hatari: Updated for version 2.0.0.
games/libretro-vecx: Added (vecx libretro port).
games/solarus-quest-editor: Updated for version 1.5.2.
games/solarus: Updated for version 1.5.1.
games/speed-dream: Updated for version 2.2.1_r6404.
games/stella: Updated for version 4.7.3.
games/stuntrally: Added (game with Track Editor).
games/xroar: Updated for version 0.34.7.
gis/Fiona: Updated for version 1.7.1.
gis/OWSLib: Updated for version 0.14.0.
gis/geos: Updated for version 3.6.1.
gis/grass: Updated for version 7.2.0.
gis/mapnik: Updated for version 3.0.12.
gis/osm2pgrouting: Updated for version 2.2.0.
gis/pdal: Updated for version 1.4.0.
gis/pgrouting: Updated for version 2.3.2.
gis/proj: Updated for version 4.9.3.
gis/pyshp: Updated for version 1.2.10.
gis/pyspatialite: Fix build.
gis/qgis: Updated for version 2.18.3.
gis/xplanet: Updated for version 1.3.1.
graphics/converseen: Updated for version 0.9.6.
graphics/graphite2: Updated for version 1.3.9.
graphics/k3d: Updated for version 0.8.0.6.
graphics/mitsuba: Script cleanup.
graphics/openscad: Updated for version 2015.03.3.
graphics/pngcrush: Updated for version 1.8.11.
graphics/yacreader: Fixed doinst.sh.
libraries/belle-sip: Remove trailing white space.
libraries/cpprestsdk: Updated for version 2.9.1.
libraries/exiftool: Updated for version 10.40.
libraries/ffms2: Updated for version 2.23.
libraries/hinnant-date: Updated for version 2.1.0.
libraries/leptonica: Updated for version 1.74.1.
libraries/libabw: Switch to i586.
libraries/libantlr3c: Remove trailing white space.
libraries/libcdr: Updated for version 0.1.3.
libraries/libe-book: Switch to i586.
libraries/libetonyek: Updated for version 0.1.6.
libraries/libfreehand: Switch to i586.
libraries/libinput: Updated for version 1.6.0.
libraries/libixion: Updated for version 0.12.2.
libraries/liblangtag: Updated for version 0.6.2.
libraries/libmspub: Switch to i586.
libraries/libmwaw: Updated for version 0.3.9.
libraries/libopenshot: Updated for version 0.1.3
libraries/liborcus: Updated for version 0.12.1.
libraries/libpagemaker: Updated for version 0.0.3.
libraries/libpst: Updated for version 0.6.69.
libraries/libtermkey: Updated for version 0.19.
libraries/libtorrent-rasterbar: Update README.
libraries/libuv: Updated for version 1.10.2.
libraries/libvshadow: Updated for version 20161111.
libraries/libwacom: Updated for version 0.23.
libraries/libwebp: Updated for version 0.5.2.
libraries/libwps: Updated for version 0.4.5.
libraries/linphone-srtp: Remove trailing white space.
libraries/lua-lpeg: Updated for version 0.12.2.
libraries/mdds: Updated for version 1.2.2.
libraries/msgpack-c: Updated for version 2.1.0.
libraries/mysql-connector-c++: Updated for version 1.1.8.
libraries/mysql-connector-python: Updated for version 2.1.5.
libraries/pjsip: Mark opencore-amr as optional.
libraries/pugixml: Updated for version 1.8.1.
libraries/python3-PyYAML: Switch to i586.
libraries/rocksdb: Updated for version 5.0.2.
libraries/sqlpp11: Updated for version 0.44.
libraries/ucommon: Remove trailing white space.
misc/subsurface: Updated for version 4.6.0
misc/yara: Updated for version 3.5.0.
multimedia/TeamSpeak3: Updated for version 3.1.0.1.
multimedia/cantata: Updated for version 2.0.1.
multimedia/filebot: Updated for version 4.7.7.
multimedia/glyr: Updated for version 1.0.10.
multimedia/openshot: Updated for version 2.2.0
multimedia/popcorntime: Fix MD5SUM.
network/Electrum: Updated for version 2.7.17.
network/aria2: Updated for version 1.31.0.
network/bmon: Updated for version 4.0.
network/freerapid: Update README and slack-desc.
network/hylafax+: Fix path.
network/irssi_otr: Updated for version 1.0.2.
network/megatools: Updated for version 1.9.98.
network/mod_bw: Updated for version 0.92.
network/nginx: Updated for version 1.10.2
network/phpmyadmin: Updated for version 4.6.6.
network/quassel: Updated for version 0.12.4.
network/r8168: Updated for version 8.043.02.
network/sickrage: Updated for version 2017.01.19_1.
network/surf: Updated for version 0.7.
network/tornado: Updated for version 4.4.2.
network/transgui: Updated for version 5.5.1.
network/viber: Updated for version 6.5.5.1481.
network/wifite: Updated for version 20150525_edbdedd.
network/xombrero: Updated for version 1.6.4.
network/zmap: Updated for version 2.1.1.
office/keepassxc: Updated for version 2.1.0.
office/notmuch: Updated for version 0.23.5.
office/sc-im: Updated for version 0.4.0.
perl/perl-Archive-Extract: Updated for version 0.80.
perl/perl-CPAN-Perl-Releases: Updated for version 3.08.
perl/perl-CPANPLUS: Updated for version 0.9162.
perl/perl-Date-Manip: Updated for version 6.57.
perl/perl-Devel-GlobalDestruction: Updated for version 0.14.
perl/perl-ExtUtils-Helpers: Updated for version 0.026.
perl/perl-File-ShareDir-Install: Updated for version 0.11.
perl/perl-IO-Socket-SSL: Updated for version 2.043.
perl/perl-JSON-XS: Updated for version 3.03.
perl/perl-Moo: Updated for version 2.003001.
perl/perl-Path-Class: Updated for version 0.37.
perl/perl-Pegex: Updated for version 0.63.
perl/perl-Role-Tiny: Updated for version 2.000005.
perl/perl-Sub-Quote: Added (perl module).
perl/perl-Types-Serialiser: Added (data types for serialisation).
perl/perl-YAML-LibYAML: Updated for version 0.63.
perl/perl-YAML-Tiny: Updated for version 1.70.
perl/perl-test-warn: Updated for version 0.32.
python/construct: Updated for version 2.5.5.
python/dfdatetime: Updated for version 20161101.
python/dfvfs: Updated for version 20160918.
python/dfwinreg: Added (Digital Forensics Windows Registry).
python/dpkt: Updated for version 1.8.8.
python/ipython: Moved from development/, upgraded for version 5.1.0.
python/ipython_genutils: Added (vestigial IPython utilities).
python/node-semver: Added (python version of node-semver).
python/pickleshare: Added (database using Python pickles).
python/python-axolotl-curve25519: Added (python wrapper).
python/python-axolotl: Added (python port).
python/python-libsass: Updated for version 0.12.3.
python/pyzmq: Updated for version 16.0.2.
python/shutil_get_terminal_size: Added (get size of term window).
python/traitlets: Added (lightweight Traits-like module).
python/yara-python: Added (Python for yara).
system/Iosevka: Updated for version 1.10.5.
system/aha: Updated for version 0.4.10.3.
system/epson-inkjet-printer-escpr: Updated for version 1.6.11.
system/guake: Added (a drop-down terminal for GNOME).
system/heirloom-doctools: Updated for version 160308.
system/lshw: New maintainer.
system/lz4: Updated for version 1.7.5.
system/rabbitmq-server: Updated for version 3.6.6.
system/ranger: Updated for version 1.8.1.
system/rxvt-unicode: New maintainer.
system/sakura: Updated for version 3.4.0.
system/salt: Updated for version 2016.11.1.
system/sbotools: Updated for version 2.3.
system/slackyd: Update DOWNLOAD and HOMEPAGE.
system/softhsm: Fixed slack-desc.
system/the_silver_searcher: Updated for version 0.33.0.
system/volatility: Updated for version 2.6.
system/yelp: Updated for version 3.22.0.
system/zerofree: Updated for version 1.1.0.
+--------------------------+

-- 
Willy Sudiarto Raharjo

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

From lems at gmx.net  Tue Jan 24 08:59:03 2017
From: lems at gmx.net (Leonard Schmidt)
Date: Tue, 24 Jan 2017 09:59:03 +0100
Subject: [Slackbuilds-users] Some SlackBuilds don't add uname -r output to
 package name
Message-ID: <0MCL6r-1ceVWy0SuX-009795@mail.gmx.com>

Hello,

while grepping all SlackBuilds for "uname -r", I noticed that some
SlackBuilds add the uname -r output to the resulting package name, and
others don't. Those that do are, for example, the nvidia-kernel
SlackBuilds, virtualbox-kernel/-addons, and network/broadcom-sta.

The following SlackBuilds install kernel modules, but don't add the
uname -r output into the resulting package name:

network/rtl8188eu
network/xtables-addons
system/netatop
system/steamos-xpad
system/sysdig

misc/klibc uses the uname -r output in its resulting package name, but
does not turn the hyphen into an underscore. While klibc is x86_64 only,
which does not have a localversion by default, it could mess up
Slackware's package tools if one uses a custom kernel with a custom
CONFIG_LOCALVERSION that includes a hyphen.

Attached is a patch which uses a variable `PKGVER' that replaces the
VERSION variable in the makepkg command line at the end of the SlackBuild.

nvidia-kernel uses `PKGVER', virtualbox-kernel uses `PKG_VERS',
broadcom-sta does not use a variable. I don't think this matters much,
though.

I also replaced two occurrences of uname -r with $KERNEL in the
system/netatop SlackBuild (I added a variable `KERNEL').

Best regards

Leonard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kernel-version-in-pkgname.diff
Type: text/x-diff
Size: 4722 bytes
Desc: kernel-version-in-pkgname.diff
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170124/3184f6c9/attachment-0001.bin>

From chytraeu at sdf.org  Wed Jan 25 02:10:24 2017
From: chytraeu at sdf.org (Donald Cooley)
Date: Tue, 24 Jan 2017 20:10:24 -0600
Subject: [Slackbuilds-users] removal of imageshack uploader
Message-ID: <ae1fbc11-3348-53e2-6f64-cd0788197f1c@sdf.org>

imageshack-uploader seems to  be dead.

i'm the package maintainer.

Can we remove this?



From willysr at slackbuilds.org  Wed Jan 25 02:27:26 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 25 Jan 2017 09:27:26 +0700
Subject: [Slackbuilds-users] removal of imageshack uploader
In-Reply-To: <ae1fbc11-3348-53e2-6f64-cd0788197f1c@sdf.org>
References: <ae1fbc11-3348-53e2-6f64-cd0788197f1c@sdf.org>
Message-ID: <41cfaccf-125d-0b33-a844-bb4e8314fb7d@slackbuilds.org>

> imageshack-uploader seems to  be dead.
> 
> i'm the package maintainer.
> 
> Can we remove this?

Sure, it has been removed on my branch


-- 
Willy Sudiarto Raharjo

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

From reedych at reedych.pw  Wed Jan 25 05:35:38 2017
From: reedych at reedych.pw (=?UTF-8?B?0KDQuNC00LjRhw==?=)
Date: Wed, 25 Jan 2017 11:35:38 +0600
Subject: [Slackbuilds-users] Teeworlds update request
Message-ID: <916be890-72d1-a04b-68c9-3d0f694fdfcc@reedych.pw>

Hello! Can you/anyone update it? Thanks.


From atelszewski at gmail.com  Wed Jan 25 10:32:14 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 25 Jan 2017 11:32:14 +0100
Subject: [Slackbuilds-users] qt5 fails to build
Message-ID: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>

Hi,

Again ;-)

When trying to build qt5, it fails with the following:

/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc/doc/qdoc_wrapper.sh: 
line 10: /usr/lib64/qt5/bin/qdoc: No such file or directory
Makefile:749: recipe for target 'prepare_docs' failed
make[4]: *** [prepare_docs] Error 127
make[4]: Leaving directory 
'/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc/doc'
Makefile:738: recipe for target 'sub-doc-prepare_docs' failed
make[3]: *** [sub-doc-prepare_docs] Error 2
make[3]: Leaving directory 
'/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc'
Makefile:1702: recipe for target 'module-qtdoc-prepare_docs' failed
make[2]: *** [module-qtdoc-prepare_docs] Error 2
make[2]: *** Waiting for unfinished jobs....

(...)

Makefile:941: recipe for target 'html_docs' failed
make[1]: *** [html_docs] Error 2
make[1]: Leaving directory 
'/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1'
Makefile:944: recipe for target 'docs' failed
make: *** [docs] Error 2


I'm building with the following options:
DOCS=yes EXAMPLES=yes PROPRIETARY_CODECS=yes

and deps:
freetds OpenAL libwebp opus snappy


This is probably the first time this error happens to me.
Anybody experiencing something similar?

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Wed Jan 25 12:38:41 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 25 Jan 2017 19:38:41 +0700
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
Message-ID: <691a3283-d023-abbc-790f-e25e1e4161e9@slackbuilds.org>

> When trying to build qt5, it fails with the following:
> 
> /tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc/doc/qdoc_wrapper.sh:
> line 10: /usr/lib64/qt5/bin/qdoc: No such file or directory
> Makefile:749: recipe for target 'prepare_docs' failed
> make[4]: *** [prepare_docs] Error 127
> make[4]: Leaving directory
> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc/doc'
> Makefile:738: recipe for target 'sub-doc-prepare_docs' failed
> make[3]: *** [sub-doc-prepare_docs] Error 2
> make[3]: Leaving directory
> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc'
> Makefile:1702: recipe for target 'module-qtdoc-prepare_docs' failed
> make[2]: *** [module-qtdoc-prepare_docs] Error 2
> make[2]: *** Waiting for unfinished jobs....
> 
> (...)
> 
> Makefile:941: recipe for target 'html_docs' failed
> make[1]: *** [html_docs] Error 2
> make[1]: Leaving directory
> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1'
> Makefile:944: recipe for target 'docs' failed
> make: *** [docs] Error 2
> 
> 
> I'm building with the following options:
> DOCS=yes EXAMPLES=yes PROPRIETARY_CODECS=yes
> 
> and deps:
> freetds OpenAL libwebp opus snappy
> 
> 
> This is probably the first time this error happens to me.
> Anybody experiencing something similar?

probably a race condition based on the error message
can you try with lower number of processor?


-- 
Willy Sudiarto Raharjo

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

From bormant at gmail.com  Wed Jan 25 13:35:41 2017
From: bormant at gmail.com (Serg Bormant)
Date: Wed, 25 Jan 2017 16:35:41 +0300
Subject: [Slackbuilds-users] Teeworlds update request
In-Reply-To: <916be890-72d1-a04b-68c9-3d0f694fdfcc@reedych.pw>
References: <916be890-72d1-a04b-68c9-3d0f694fdfcc@reedych.pw>
Message-ID: <CAD7s_awHG5-jPjgoFUKfsvOpiwDHugj-0EBzOxNvwrmS_CQQxA@mail.gmail.com>

Hi,

is it more complex than trivial version bump?

--
wbr, sb


2017-01-25 8:35 GMT+03:00 ????? <reedych at reedych.pw>:
> Hello! Can you/anyone update it? Thanks.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From d.zlatanidis at gmail.com  Wed Jan 25 14:13:44 2017
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Wed, 25 Jan 2017 16:13:44 +0200
Subject: [Slackbuilds-users] Teeworlds update request
In-Reply-To: <CAD7s_awHG5-jPjgoFUKfsvOpiwDHugj-0EBzOxNvwrmS_CQQxA@mail.gmail.com>
References: <916be890-72d1-a04b-68c9-3d0f694fdfcc@reedych.pw>
 <CAD7s_awHG5-jPjgoFUKfsvOpiwDHugj-0EBzOxNvwrmS_CQQxA@mail.gmail.com>
Message-ID: <ce1d64a9-bef9-7e83-e72d-0040c8e63b4a@gmail.com>

It has been updated in my branch
https://www.slackbuilds.org/cgit/slackbuilds/commit/?h=user/dslackw/updates


On 01/25/2017 03:35 PM, Serg Bormant wrote:
> Hi,
>
> is it more complex than trivial version bump?
>
> --
> wbr, sb
>
>
> 2017-01-25 8:35 GMT+03:00 ????? <reedych at reedych.pw>:
>> Hello! Can you/anyone update it? Thanks.
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://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
> http://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/20170125/1f760be1/attachment.html>

From ewfalor at gmail.com  Wed Jan 25 16:32:34 2017
From: ewfalor at gmail.com (Erik Falor)
Date: Wed, 25 Jan 2017 09:32:34 -0700
Subject: [Slackbuilds-users] Teeworlds update request
In-Reply-To: <ce1d64a9-bef9-7e83-e72d-0040c8e63b4a@gmail.com>
References: <916be890-72d1-a04b-68c9-3d0f694fdfcc@reedych.pw>
 <CAD7s_awHG5-jPjgoFUKfsvOpiwDHugj-0EBzOxNvwrmS_CQQxA@mail.gmail.com>
 <ce1d64a9-bef9-7e83-e72d-0040c8e63b4a@gmail.com>
Message-ID: <20170125163234.2ptgvamppvsxvym6@viking2.falor>

On Wed, Jan 25, 2017 at 04:13:44PM +0200, Dimitris Zlatanidis wrote:
>    It has been updated in my branch
>    [1]https://www.slackbuilds.org/cgit/slackbuilds/commit/?h=user/dslackw/
>    updates
> 
>    On 01/25/2017 03:35 PM, Serg Bormant wrote:

Please, no! Teeworlds is a terrible game that nobody should play.
I almost flunked my last semester of school because of it ;)

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

From reedych at reedych.pw  Wed Jan 25 17:31:50 2017
From: reedych at reedych.pw (=?UTF-8?B?0KDQuNC00LjRhw==?=)
Date: Wed, 25 Jan 2017 23:31:50 +0600
Subject: [Slackbuilds-users] Teeworlds update request
In-Reply-To: <20170125163234.2ptgvamppvsxvym6@viking2.falor>
References: <916be890-72d1-a04b-68c9-3d0f694fdfcc@reedych.pw>
 <CAD7s_awHG5-jPjgoFUKfsvOpiwDHugj-0EBzOxNvwrmS_CQQxA@mail.gmail.com>
 <ce1d64a9-bef9-7e83-e72d-0040c8e63b4a@gmail.com>
 <20170125163234.2ptgvamppvsxvym6@viking2.falor>
Message-ID: <944f76a6-de52-772f-108a-7264f923cd16@reedych.pw>

lol :D


On 25.01.2017 22:32, Erik Falor wrote:
> On Wed, Jan 25, 2017 at 04:13:44PM +0200, Dimitris Zlatanidis wrote:
>>    It has been updated in my branch
>>    [1]https://www.slackbuilds.org/cgit/slackbuilds/commit/?h=user/dslackw/
>>    updates
>>
>>    On 01/25/2017 03:35 PM, Serg Bormant wrote:
> Please, no! Teeworlds is a terrible game that nobody should play.
> I almost flunked my last semester of school because of it ;)
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170125/4ad87b99/attachment.html>

From baildon.research at googlemail.com  Wed Jan 25 20:03:10 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Wed, 25 Jan 2017 20:03:10 +0000
Subject: [Slackbuilds-users] Some SlackBuilds don't add uname -r output
 to package name
In-Reply-To: <0MCL6r-1ceVWy0SuX-009795@mail.gmx.com>
References: <0MCL6r-1ceVWy0SuX-009795@mail.gmx.com>
Message-ID: <CAMt7G9R1NHFs2vPZGrGevq+pL7ZOt+3SomO+Fo41rqX5mh43uQ@mail.gmail.com>

> The following SlackBuilds install kernel modules, but don't add the
> uname -r output into the resulting package name:
>
> network/rtl8188eu
> network/xtables-addons
> system/netatop
> system/steamos-xpad
> system/sysdig
[...]

Interesting and useful and I think we should apply Leonard's fixes ...
does everybody agree?

Thanks Leonard!
-D.

From kingbeowulf at gmail.com  Wed Jan 25 20:10:26 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Wed, 25 Jan 2017 12:10:26 -0800
Subject: [Slackbuilds-users] Some SlackBuilds don't add uname -r output
 to package name
In-Reply-To: <CAMt7G9R1NHFs2vPZGrGevq+pL7ZOt+3SomO+Fo41rqX5mh43uQ@mail.gmail.com>
References: <0MCL6r-1ceVWy0SuX-009795@mail.gmx.com>
 <CAMt7G9R1NHFs2vPZGrGevq+pL7ZOt+3SomO+Fo41rqX5mh43uQ@mail.gmail.com>
Message-ID: <105e2649-6a13-e33d-f51d-e8791f1531ce@gmail.com>

On 01/25/2017 12:03 PM, David Spencer wrote:
>> The following SlackBuilds install kernel modules, but don't add the
>> uname -r output into the resulting package name:
>>
>> network/rtl8188eu
>> network/xtables-addons
>> system/netatop
>> system/steamos-xpad
>> system/sysdig
> [...]
> 
> Interesting and useful and I think we should apply Leonard's fixes ...
> does everybody agree?
> 
> Thanks Leonard!
> -D.
>

Sounds good to me.  Flagging packages that build kernel modules with the
running kernel version can help avoid some of those 'what the heck'
moments.

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

From lists at osh.id.au  Thu Jan 26 00:13:53 2017
From: lists at osh.id.au (David O'Shaughnessy)
Date: Thu, 26 Jan 2017 10:13:53 +1000
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
Message-ID: <8baf61f9-540c-b894-e237-3a3266dbd56d@osh.id.au>

On 01/25/2017 08:32 PM, Andrzej Telszewski wrote:
> When trying to build qt5, it fails with the following:
> 
> Makefile:941: recipe for target 'html_docs' failed
> make[1]: *** [html_docs] Error 2
> make[1]: Leaving directory
> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1'
> Makefile:944: recipe for target 'docs' failed
> make: *** [docs] Error 2
> 
> I'm building with the following options:
> DOCS=yes EXAMPLES=yes PROPRIETARY_CODECS=yes
> 
> and deps:
> freetds OpenAL libwebp opus snappy
> 

I just tried building qt5 with those options and had no problems. But I
don't have freetds, OpenAL, or snappy installed either.

--
Dave

From atelszewski at gmail.com  Thu Jan 26 00:19:26 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 26 Jan 2017 01:19:26 +0100
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <8baf61f9-540c-b894-e237-3a3266dbd56d@osh.id.au>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
 <8baf61f9-540c-b894-e237-3a3266dbd56d@osh.id.au>
Message-ID: <d5795116-cc75-b7be-d60b-03c32012b799@gmail.com>

On 26/01/17 01:13, David O'Shaughnessy wrote:
> On 01/25/2017 08:32 PM, Andrzej Telszewski wrote:
>> When trying to build qt5, it fails with the following:
>>
>> Makefile:941: recipe for target 'html_docs' failed
>> make[1]: *** [html_docs] Error 2
>> make[1]: Leaving directory
>> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1'
>> Makefile:944: recipe for target 'docs' failed
>> make: *** [docs] Error 2
>>
>> I'm building with the following options:
>> DOCS=yes EXAMPLES=yes PROPRIETARY_CODECS=yes
>>
>> and deps:
>> freetds OpenAL libwebp opus snappy
>>
>
> I just tried building qt5 with those options and had no problems. But I
> don't have freetds, OpenAL, or snappy installed either.
>

How many make jobs did you use?
Also, the deps should not matter for that particular error.

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Thu Jan 26 00:34:00 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 26 Jan 2017 01:34:00 +0100
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <691a3283-d023-abbc-790f-e25e1e4161e9@slackbuilds.org>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
 <691a3283-d023-abbc-790f-e25e1e4161e9@slackbuilds.org>
Message-ID: <dcc350c2-af84-a48f-0da2-d580cfb3c427@gmail.com>

On 25/01/17 13:38, Willy Sudiarto Raharjo wrote:
>> When trying to build qt5, it fails with the following:
>>
>> /tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc/doc/qdoc_wrapper.sh:
>> line 10: /usr/lib64/qt5/bin/qdoc: No such file or directory
>> Makefile:749: recipe for target 'prepare_docs' failed
>> make[4]: *** [prepare_docs] Error 127
>> make[4]: Leaving directory
>> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc/doc'
>> Makefile:738: recipe for target 'sub-doc-prepare_docs' failed
>> make[3]: *** [sub-doc-prepare_docs] Error 2
>> make[3]: Leaving directory
>> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1/qtdoc'
>> Makefile:1702: recipe for target 'module-qtdoc-prepare_docs' failed
>> make[2]: *** [module-qtdoc-prepare_docs] Error 2
>> make[2]: *** Waiting for unfinished jobs....
>>
>> (...)
>>
>> Makefile:941: recipe for target 'html_docs' failed
>> make[1]: *** [html_docs] Error 2
>> make[1]: Leaving directory
>> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1'
>> Makefile:944: recipe for target 'docs' failed
>> make: *** [docs] Error 2
>>
>>
>> I'm building with the following options:
>> DOCS=yes EXAMPLES=yes PROPRIETARY_CODECS=yes
>>
>> and deps:
>> freetds OpenAL libwebp opus snappy
>>
>>
>> This is probably the first time this error happens to me.
>> Anybody experiencing something similar?
>
> probably a race condition based on the error message
> can you try with lower number of processor?
>

It built correctly with 1 core.
Could the problem be that previously I used 3 cores, an odd number?
Also, I'm building in QEMU.

I wonder what was wrong, as I can't recall this type of error.
Or maybe it's a bug in build system, something like the race condition 
you mentioned?

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Thu Jan 26 01:11:18 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 26 Jan 2017 02:11:18 +0100
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <dcc350c2-af84-a48f-0da2-d580cfb3c427@gmail.com>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
 <691a3283-d023-abbc-790f-e25e1e4161e9@slackbuilds.org>
 <dcc350c2-af84-a48f-0da2-d580cfb3c427@gmail.com>
Message-ID: <d9dbc5e4-1370-77b8-3464-1a37b0cb040a@gmail.com>

On 26/01/17 01:34, Andrzej Telszewski wrote:
> It built correctly with 1 core.
> Could the problem be that previously I used 3 cores, an odd number?
> Also, I'm building in QEMU.
>
> I wonder what was wrong, as I can't recall this type of error.
> Or maybe it's a bug in build system, something like the race condition
> you mentioned?

OK, I don't know if we want to dig this further.
Maybe it had something to do with badly updated Python:

I was having problems building borgbackup, which depends on, most 
probably, Python2 for building the docs (I'm using slackrepo):
- building in verbose mode caused the build to fail,
- building in quiet mode succeeded,
- revert python2 from 2.7.13 to 2.7.11 and the build succeeds in both modes,
- upgrade again to 2.7.13 and the build succeeds in both modes.

I'm aware of the 2.7.13-1 problem that 2.7.13-2 corrected, but damn, I'm 
sure I had the correct version.

Let me bother you again when having problems building qt5 ;-)

Cheers.

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Thu Jan 26 06:13:29 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 26 Jan 2017 13:13:29 +0700
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <d9dbc5e4-1370-77b8-3464-1a37b0cb040a@gmail.com>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
 <691a3283-d023-abbc-790f-e25e1e4161e9@slackbuilds.org>
 <dcc350c2-af84-a48f-0da2-d580cfb3c427@gmail.com>
 <d9dbc5e4-1370-77b8-3464-1a37b0cb040a@gmail.com>
Message-ID: <843ecca0-bfe2-544a-3fcd-caa4c5b4e87d@slackbuilds.org>

> OK, I don't know if we want to dig this further.
> Maybe it had something to do with badly updated Python:
> 
> I was having problems building borgbackup, which depends on, most
> probably, Python2 for building the docs (I'm using slackrepo):
> - building in verbose mode caused the build to fail,
> - building in quiet mode succeeded,
> - revert python2 from 2.7.13 to 2.7.11 and the build succeeds in both
> modes,
> - upgrade again to 2.7.13 and the build succeeds in both modes.
> 
> I'm aware of the 2.7.13-1 problem that 2.7.13-2 corrected, but damn, I'm
> sure I had the correct version.
> 
> Let me bother you again when having problems building qt5 ;-)

Just FYI, Larry Haja has pushed his qt5 update to 5.7.1 in a separate
branch for testing. So far, he managed to fix couple of packages which
relies on Qt5. You can help by building Qt 5.7.1 and see if your
packages are affected with this change.

I'm able to build Qt5 5.7.1 just fine on my VM and also on my desktop
computer at home.

PS: i'm planning to merge it on this week's public update. Let me know
if you found a broken package due to this new update.



-- 
Willy Sudiarto Raharjo

-------------- 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/20170126/0d34434e/attachment.asc>

From miguel at thedeanda.com  Thu Jan 26 06:35:52 2017
From: miguel at thedeanda.com (Miguel De Anda)
Date: Wed, 25 Jan 2017 22:35:52 -0800
Subject: [Slackbuilds-users] kafka
Message-ID: <CAA62KfSOcV6aNz0sfSen78owF3Vo7y6e0L7F9KNMAiSZ7iCLRg@mail.gmail.com>

i was building kafka and i ran into this message:

  You must have a kafka user and kafka group to run this script.
  Something like this should suffice for most systems:
    # groupadd -g 323 kafka
    # useradd -u 323 -g 323 -c "Apache Kafka user" -d /var/lib/kafka
-s /bin/sh kafka

i think we usually state that on the slackbuild page so its easy to
find -- i also installed rabbitmq, couchdb, and zookeeper and those
had it. it might be useful to do the same for kafka.

thanks

From lists at osh.id.au  Thu Jan 26 09:53:57 2017
From: lists at osh.id.au (David O'Shaughnessy)
Date: Thu, 26 Jan 2017 19:53:57 +1000
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <d5795116-cc75-b7be-d60b-03c32012b799@gmail.com>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
 <8baf61f9-540c-b894-e237-3a3266dbd56d@osh.id.au>
 <d5795116-cc75-b7be-d60b-03c32012b799@gmail.com>
Message-ID: <ab32bf87-3266-86f8-d85a-8807e32cc1ef@osh.id.au>

On 01/26/2017 10:19 AM, Andrzej Telszewski wrote:
> On 26/01/17 01:13, David O'Shaughnessy wrote:
>> On 01/25/2017 08:32 PM, Andrzej Telszewski wrote:
>>> When trying to build qt5, it fails with the following:
>>>
>>> Makefile:941: recipe for target 'html_docs' failed
>>> make[1]: *** [html_docs] Error 2
>>> make[1]: Leaving directory
>>> '/tmp/slackrepo-desktop/qt-everywhere-opensource-src-5.6.1'
>>> Makefile:944: recipe for target 'docs' failed
>>> make: *** [docs] Error 2
>>>
>>> I'm building with the following options:
>>> DOCS=yes EXAMPLES=yes PROPRIETARY_CODECS=yes
>>>
>>> and deps:
>>> freetds OpenAL libwebp opus snappy
>>>
>>
>> I just tried building qt5 with those options and had no problems. But I
>> don't have freetds, OpenAL, or snappy installed either.
>>
> 
> How many make jobs did you use?
> Also, the deps should not matter for that particular error.

I have JOBS=6 in sbotools.conf.

From bmg.andre at gmail.com  Thu Jan 26 09:54:19 2017
From: bmg.andre at gmail.com (=?UTF-8?Q?Andr=C3=A9_Barboza?=)
Date: Thu, 26 Jan 2017 07:54:19 -0200
Subject: [Slackbuilds-users] kafka
In-Reply-To: <CAA62KfSOcV6aNz0sfSen78owF3Vo7y6e0L7F9KNMAiSZ7iCLRg@mail.gmail.com>
References: <CAA62KfSOcV6aNz0sfSen78owF3Vo7y6e0L7F9KNMAiSZ7iCLRg@mail.gmail.com>
Message-ID: <CAC8E-U_wtfmHfvCshV8cxz1gWfdfaG354y+N5gEcUKZUCeQV7w@mail.gmail.com>

Right. Kafka also needs to be updated.
I will work on that.

2017-01-26 4:35 GMT-02:00 Miguel De Anda <miguel at thedeanda.com>:

> i was building kafka and i ran into this message:
>
>   You must have a kafka user and kafka group to run this script.
>   Something like this should suffice for most systems:
>     # groupadd -g 323 kafka
>     # useradd -u 323 -g 323 -c "Apache Kafka user" -d /var/lib/kafka
> -s /bin/sh kafka
>
> i think we usually state that on the slackbuild page so its easy to
> find -- i also installed rabbitmq, couchdb, and zookeeper and those
> had it. it might be useful to do the same for kafka.
>
> thanks
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170126/79dafb61/attachment.html>

From andreas.guldstrand at gmail.com  Thu Jan 26 11:41:23 2017
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Thu, 26 Jan 2017 12:41:23 +0100
Subject: [Slackbuilds-users] kafka
In-Reply-To: <CAC8E-U_wtfmHfvCshV8cxz1gWfdfaG354y+N5gEcUKZUCeQV7w@mail.gmail.com>
References: <CAA62KfSOcV6aNz0sfSen78owF3Vo7y6e0L7F9KNMAiSZ7iCLRg@mail.gmail.com>
 <CAC8E-U_wtfmHfvCshV8cxz1gWfdfaG354y+N5gEcUKZUCeQV7w@mail.gmail.com>
Message-ID: <CAEQ5t81yqC4iBT3d-XoSLjYbKato_Kg0Lw8OKXzss1aYXgVL1g@mail.gmail.com>

On 26 January 2017 at 10:54, Andr? Barboza <bmg.andre at gmail.com> wrote:
> Right. Kafka also needs to be updated.
> I will work on that.
>
> 2017-01-26 4:35 GMT-02:00 Miguel De Anda <miguel at thedeanda.com>:
>>
>> i was building kafka and i ran into this message:
>>
>>   You must have a kafka user and kafka group to run this script.
>>   Something like this should suffice for most systems:
>>     # groupadd -g 323 kafka
>>     # useradd -u 323 -g 323 -c "Apache Kafka user" -d /var/lib/kafka
>> -s /bin/sh kafka
>>
>> i think we usually state that on the slackbuild page so its easy to
>> find -- i also installed rabbitmq, couchdb, and zookeeper and those
>> had it. it might be useful to do the same for kafka.
>>
>> thanks

A few other slackbuilds that have this same problem (just did a quick
grep, so don't know if this list is exhaustive):

network/dovecot
network/roger-router
network/sks-keyserver
system/apache-activemq
system/clamav
system/jenkins
system/kafka (of course)

And additionally the following ones don't have the command listed in
the README but does mention it in some other way, which will not work
with for example sbotools' automatic check for these kinds of
commands:

network/etherpad-lite
network/lighttpd
network/lighttpd2
network/openfire

From atelszewski at gmail.com  Thu Jan 26 13:15:23 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 26 Jan 2017 14:15:23 +0100
Subject: [Slackbuilds-users] qt5 fails to build
In-Reply-To: <d9dbc5e4-1370-77b8-3464-1a37b0cb040a@gmail.com>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
 <691a3283-d023-abbc-790f-e25e1e4161e9@slackbuilds.org>
 <dcc350c2-af84-a48f-0da2-d580cfb3c427@gmail.com>
 <d9dbc5e4-1370-77b8-3464-1a37b0cb040a@gmail.com>
Message-ID: <917f0bf1-fe2d-df96-d176-468bd1716b2e@gmail.com>

On 26/01/17 02:11, Andrzej Telszewski wrote:
> I was having problems building borgbackup, which depends on, most
> probably, Python2 for building the docs (I'm using slackrepo):
> - building in verbose mode caused the build to fail,
> - building in quiet mode succeeded,
> - revert python2 from 2.7.13 to 2.7.11 and the build succeeds in both
> modes,
> - upgrade again to 2.7.13 and the build succeeds in both modes.
>
> I'm aware of the 2.7.13-1 problem that 2.7.13-2 corrected, but damn, I'm
> sure I had the correct version.

It seems to be solved now.
The problem was that I didn't have UTF-8 locale set.

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Thu Jan 26 23:42:20 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 27 Jan 2017 06:42:20 +0700
Subject: [Slackbuilds-users] Some SlackBuilds don't add uname -r output
 to package name
In-Reply-To: <CAMt7G9R1NHFs2vPZGrGevq+pL7ZOt+3SomO+Fo41rqX5mh43uQ@mail.gmail.com>
References: <0MCL6r-1ceVWy0SuX-009795@mail.gmx.com>
 <CAMt7G9R1NHFs2vPZGrGevq+pL7ZOt+3SomO+Fo41rqX5mh43uQ@mail.gmail.com>
Message-ID: <4870d8b9-5765-c0ae-3206-770e27c89b4e@slackbuilds.org>

>> The following SlackBuilds install kernel modules, but don't add the
>> uname -r output into the resulting package name:
>>
>> network/rtl8188eu
>> network/xtables-addons
>> system/netatop
>> system/steamos-xpad
>> system/sysdig
> [...]
> 
> Interesting and useful and I think we should apply Leonard's fixes ...
> does everybody agree?

for me: YES :)


-- 
Willy Sudiarto Raharjo

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

From rshepard at appl-ecosys.com  Fri Jan 27 00:55:54 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 26 Jan 2017 16:55:54 -0800 (PST)
Subject: [Slackbuilds-users] Issue building scibus-1.4.6
Message-ID: <alpine.LNX.2.11.1701261651110.27406@localhost>

   Wanting to upgrade scribus from -1.4.4 to -1.4.6 I downloaded the
.SlackBuilds file and the source tarball. When I ran the script it bailed
out:

Building CXX object
scribus/desaxe/CMakeFiles/scribus_desaxe_lib.dir/saxiohelper.cpp.o
In file included from
/tmp/SBo/scribus-1.4.6/scribus/desaxe/saxiohelper.cpp:10:0:
/tmp/SBo/scribus-1.4.6/scribus/scfonts.h:19:23: fatal error: freetype.h: No
/ such file or directory
  #include FT_FREETYPE_H
                        ^
compilation terminated.
make[2]: ***
[scribus/desaxe/CMakeFiles/scribus_desaxe_lib.dir/saxiohelper.cpp.o] Error 1
make[1]: *** [scribus/desaxe/CMakeFiles/scribus_desaxe_lib.dir/all] Error 2
make: *** [all] Error 2

   freetype.h is present on the system:

$ locate freetype.h
/usr/include/freetype2/freetype.h

   I don't see a place in the build script to provide the include directory.

   Please suggest how to resolve this issue.

TIA,

Rich

From atelszewski at gmail.com  Fri Jan 27 07:27:09 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 27 Jan 2017 08:27:09 +0100
Subject: [Slackbuilds-users] qt 5.7.1 update test [was: qt5 fails to
 build]
In-Reply-To: <843ecca0-bfe2-544a-3fcd-caa4c5b4e87d@slackbuilds.org>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
 <691a3283-d023-abbc-790f-e25e1e4161e9@slackbuilds.org>
 <dcc350c2-af84-a48f-0da2-d580cfb3c427@gmail.com>
 <d9dbc5e4-1370-77b8-3464-1a37b0cb040a@gmail.com>
 <843ecca0-bfe2-544a-3fcd-caa4c5b4e87d@slackbuilds.org>
Message-ID: <7fac155a-9393-afc7-8324-3e98ddd731ed@gmail.com>

On 26/01/17 07:13, Willy Sudiarto Raharjo wrote:
> Just FYI, Larry Haja has pushed his qt5 update to 5.7.1 in a separate
> branch for testing. So far, he managed to fix couple of packages which
> relies on Qt5. You can help by building Qt 5.7.1 and see if your
> packages are affected with this change.
>
> I'm able to build Qt5 5.7.1 just fine on my VM and also on my desktop
> computer at home.
>
> PS: i'm planning to merge it on this week's public update. Let me know
> if you found a broken package due to this new update.

Qt5 5.7.1 builds fine on my side.

The following packages build fine and seem to work correctly:
- qbs-1.7.1 (commit 5db00d0f1f514317f08222b93aebc32fced7608e)
- qt-creator-4.2.1 (commit d5a61b975a8b647415ce54f5f7021310bbdab4d3)
- wireshark-2.2.4 (commit 46266ba0fb01c448aaa5b7d32028a3ad61da9905)

The following packages build fine, but running them was not tested:
- converseen-0.9.6 (commit dda7d73e9437d6a1847be4e6cbb5d031d5a3f6a8)
- PyQt5-5.7 (commit 6f637b3eeeed4b40ef8e583e0085731d66e00359)
- qt5-webkit-5.7.1 (commit 93967a67521e0f3fe12cb41ae03ac0886b6a829d)
- calibre-2.77.0 (commit 71c16c20037fdc740f5f9806c22dc6be1f4a9f08)

-- 
Best regards,
Andrzej Telszewski

From larryhaja at gmail.com  Fri Jan 27 13:59:38 2017
From: larryhaja at gmail.com (Larry Hajali)
Date: Fri, 27 Jan 2017 05:59:38 -0800
Subject: [Slackbuilds-users] qt 5.7.1 update test [was: qt5 fails to
 build]
In-Reply-To: <7fac155a-9393-afc7-8324-3e98ddd731ed@gmail.com>
References: <17426dfd-b0a5-fdc0-b055-309c62a13fab@gmail.com>
 <691a3283-d023-abbc-790f-e25e1e4161e9@slackbuilds.org>
 <dcc350c2-af84-a48f-0da2-d580cfb3c427@gmail.com>
 <d9dbc5e4-1370-77b8-3464-1a37b0cb040a@gmail.com>
 <843ecca0-bfe2-544a-3fcd-caa4c5b4e87d@slackbuilds.org>
 <7fac155a-9393-afc7-8324-3e98ddd731ed@gmail.com>
Message-ID: <CAAZPBMj07ctRBbkN6RGpZHgKCwnOvKueEfJ9foOgK2LOooeKJQ@mail.gmail.com>

>
> Qt5 5.7.1 builds fine on my side.
>
> The following packages build fine and seem to work correctly:
> - qbs-1.7.1 (commit 5db00d0f1f514317f08222b93aebc32fced7608e)
> - qt-creator-4.2.1 (commit d5a61b975a8b647415ce54f5f7021310bbdab4d3)
> - wireshark-2.2.4 (commit 46266ba0fb01c448aaa5b7d32028a3ad61da9905)
>
> The following packages build fine, but running them was not tested:
> - converseen-0.9.6 (commit dda7d73e9437d6a1847be4e6cbb5d031d5a3f6a8)
> - PyQt5-5.7 (commit 6f637b3eeeed4b40ef8e583e0085731d66e00359)
> - qt5-webkit-5.7.1 (commit 93967a67521e0f3fe12cb41ae03ac0886b6a829d)
> - calibre-2.77.0 (commit 71c16c20037fdc740f5f9806c22dc6be1f4a9f08)

I built calibre and it initially failed with this error.
https://bbs.archlinux.org/viewtopic.php?pid=1547092#p1547092
But after rebuilding PyQt5 and then calibre again it worked fine.

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

From willysr at slackbuilds.org  Sat Jan 28 01:07:23 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 28 Jan 2017 08:07:23 +0700
Subject: [Slackbuilds-users] Updates - 20170128.1
Message-ID: <ac9900d6-9785-e05f-7bb7-7e2beaadba00@slackbuilds.org>

Hi folks

this update brings a major update to Qt5. It's now bumped to 5.7.1.
Larry Haja has spent some time to build and test some packages to work
with Qt5. Since there's a lot of packages depending on qt5, we might
miss some of them.

Also Leonard's proposal to include the output of uname -r in some
scripts that build a kernel module was accepted to help people aware
when a kernel upgrade is issued and some package stopped working due to
kernel module changes.

Sat Jan 28 00:39:26 UTC 2017
academic/reduce-algebra: Updated for version 20170124svn3877.
audio/acousticbrainz-gui: fix build against Qt 5.7.1
audio/mpd: Updated for version 0.20.3.
audio/quodlibet: Updated for version 3.8.1.
audio/soundkonverter: Updated for version 2.2.2.
desktop/lumina: Updated for version 1.2.0_p1 + new maintainer.
desktop/lxappearance: Updated for version 0.6.3.
desktop/lxpanel: Updated for version 0.9.3.
desktop/neofetch: Fixed SlackBuild.
desktop/qt5ct: Updated for version 0.29.
development/atom: Updated for version 1.13.1.
development/colm: Added (Programming language).
development/composer: Updated for version 1.3.1.
development/diffoscope: Updated for version 70.
development/dmd: Updated for version 2.073.0.
development/gambas3: fix build against Qt 5.7.1
development/ioncube-loader: Updated for version 6.0.8.
development/jupyter-ipyleaflet: Added (IPython Leaflet widget).
development/jupyter-ipywidgets: Added (widgets for Jupyter N'book).
development/jupyter-nbconvert: Added (Jupyter notebook conversion).
development/jupyter-widgetsnbextension: Added (HTML f/ Jupyter).
development/kelbt: Updated for version 0.16, cleanups.
development/mutagen: Updated for version 1.36.2.
development/nedit: Install 'ncl' + new maintainer.
development/qbs: Updated for version 1.7.1.
development/qt-creator: Updated for version 4.2.1.
development/ragel: Updated for version 7.0.0.9, cleanups.
development/universal-ctags: Updated for version 15504fe.
games/hatari: Fix MD5SUM.
games/mame2010-libretro: Added (MAME 2010 libretro port).
games/mame2014-libretro: Added (MAME 2014 libretro port).
games/minetest: Updated for version 0.4.15.
games/minetest_game: Updated for version 0.4.15.
games/speed-dreams: Fixed deps.
games/teeworlds: Updated for version 0.6.4.
gis/Fiona: Updated for version 1.7.2.
gis/osm2pgrouting: Fix empty MD5SUM.
graphics/photoqt: Updated for version 1.5.1.
libraries/PyQt5: Updated for version 5.7
libraries/girara: Updated for version 0.2.7.
libraries/html5lib: Updated for version 0.9999999.
libraries/libev: Updated for version 4.24, added a license.
libraries/libixion: Fixed SlackBuild.
libraries/libtelnet: Fix build.
libraries/pjsip: Updated for version 2.6.
libraries/poppler-qt5: fix build against Qt 5.7.1
libraries/qt5-webkit: Updated for version 5.7.1
libraries/qt5: Updated for version 5.7.1
misc/klibc: Fixup kernel id in package version.
misc/subsurface: fix build against Qt 5.7.1
multimedia/cfourcc: Fix .info.
multimedia/mlt: fix build against Qt 5.7.1
network/imageshack-uploader: Removed (per maintainer's request).
network/lighttpd2: Updated for version 20170102_ca44691.
network/mdk3: Added (802.11 exploit tool).
network/opera: Updated for version 42.0.2393.351.
network/owncloud-client: Improved qt4/qt5 compatibility.
network/phodav: Updated for version 2.1.
network/rtl8188eu: Fixup kernel id in package version.
network/tixati: Updated for version 2.51_1.
network/tor: Updated for version 0.2.9.9.
network/wire: Updated for version 2.11.2685.
network/wireshark: Updated for version 2.2.4.
network/xtables-addons: Fixup kernel id in package version.
office/jstock: Updated for version 1.0.7.19.
office/juffed: Updated for version 0.10.
office/libreoffice-helppack: Updated for version 5.2.5.
office/libreoffice-langpack: Updated for version 5.2.5.
office/libreoffice: Updated for version 5.2.5.
office/mupdf: Updated for version 1.10a.
office/texstudio: Updated for version 2.12.2
office/wammu: Updated for version 0.43.
office/zathura-cb: Updated for version 0.1.6.
office/zathura-djvu: Updated for version 0.2.6.
office/zathura-pdf-mupdf: Updated for version 0.3.1.
office/zathura-ps: Updated for version 0.2.4.
office/zathura: Updated for version 0.3.7.
perl/perl-Data-Dumper: Removed (included in Perl).
perl/perl-Mojolicious: Added (next-gen web framework for Perl).
perl/perl-Moo: Fix source url.
perl/perl-Role-Tiny: Fix empty MD5SUM.
perl/perl-SOAP-Lite: Update DEP.
perl/perl-mojo: Removed (replaced by perl-Mojolicious).
python/bleach: Added (whitelist-based HTML-sanitizing tool).
python/entrypoints: Added (Discover & load entry points).
python/mistune: Added (Python markdown parser).
python/pandocfilters: Added (module for writing pandoc filters).
python/paramiko: Updated for version 2.1.1.
python/python-axolotl: Fixed slack-desc.
python/python-gammu: Added (Python bindings for gammu).
python/testpath: Added (Test utilities for files and commands).
system/fzf: Updated for version 0.16.2.
system/gammu: Updated for version 1.38.1.
system/kexec-tools: Updated for version 2.0.14.
system/lxtask: Updated for version 0.1.8.
system/lxterminal: Updated for version 20170124_a29172d.
system/mongo-tools: Updated for version 3.4.1.
system/mongodb: Updated for version 3.4.1.
system/netatop: Fixup kernel id in package version.
system/netdata: Added (real-time monitoring system).
system/pdfgrep: Updated for version 2.0.
system/qemu-guest-agent: Updated for version 2.8.0.
system/qemu: Updated for version 2.8.0.
system/slackroll: Updated for version v46.
system/steamos-xpad: Fixup kernel id in package version.
system/sysdig: Fixup kernel id in package version.
system/sysdig: Updated for version 0.14.0
system/the_silver_searcher: Updated for version 1.0.2.
system/trash-cli: Updated for version 0.17.1.14.
system/vtcol: Updated for version 0.42.2.
+--------------------------+

-- 
Willy Sudiarto Raharjo

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

From hostmaster at slackonly.com  Sat Jan 28 02:13:05 2017
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Fri, 27 Jan 2017 18:13:05 -0800
Subject: [Slackbuilds-users] snort
Message-ID: <6734d4eb-1879-5f47-768d-117ca746900a@slackonly.com>

Hi!,

Snort is unable to run in a VPS machine as it uses venet instead of eth...

We can avoid this if configure snort with --enable-non-ether-decoders

Can we add this as option to SlackBuild?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170127/60c36d65/attachment.html>

From reedych at reedych.pw  Sat Jan 28 06:22:19 2017
From: reedych at reedych.pw (=?UTF-8?B?0KDQuNC00LjRhw==?=)
Date: Sat, 28 Jan 2017 12:22:19 +0600
Subject: [Slackbuilds-users] ftp.kernel.org will shut down at this year
Message-ID: <9b7d8cf3-4b09-01ef-9545-e927db464f68@reedych.pw>

https://kernel.org/shutting-down-ftp-services.html. If anyone maintains
slackbuilds what uses it as download link, please fix it. Thanks!


From willysr at slackbuilds.org  Sat Jan 28 08:18:51 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 28 Jan 2017 15:18:51 +0700
Subject: [Slackbuilds-users] ftp.kernel.org will shut down at this year
In-Reply-To: <9b7d8cf3-4b09-01ef-9545-e927db464f68@reedych.pw>
References: <9b7d8cf3-4b09-01ef-9545-e927db464f68@reedych.pw>
Message-ID: <3e7808be-29ac-2d1f-efcb-9edbb87ad692@slackbuilds.org>

> https://kernel.org/shutting-down-ftp-services.html. If anyone maintains
> slackbuilds what uses it as download link, please fix it. Thanks!


running grep ftp.kernel.org slackbuilds/*/*/*.info returns zero results


-- 
Willy Sudiarto Raharjo

-------------- 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/20170128/9f7b8dbd/attachment.asc>

From willysr at slackbuilds.org  Sat Jan 28 08:43:55 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 28 Jan 2017 15:43:55 +0700
Subject: [Slackbuilds-users] Issue building scibus-1.4.6
In-Reply-To: <alpine.LNX.2.11.1701261651110.27406@localhost>
References: <alpine.LNX.2.11.1701261651110.27406@localhost>
Message-ID: <e59b08f2-35ed-48c0-ee56-4bf674873538@slackbuilds.org>

>   Wanting to upgrade scribus from -1.4.4 to -1.4.6 I downloaded the
> .SlackBuilds file and the source tarball. When I ran the script it bailed
> out:
> 
> Building CXX object
> scribus/desaxe/CMakeFiles/scribus_desaxe_lib.dir/saxiohelper.cpp.o
> In file included from
> /tmp/SBo/scribus-1.4.6/scribus/desaxe/saxiohelper.cpp:10:0:
> /tmp/SBo/scribus-1.4.6/scribus/scfonts.h:19:23: fatal error: freetype.h: No
> / such file or directory
>  #include FT_FREETYPE_H
>                        ^
> compilation terminated.
> make[2]: ***
> [scribus/desaxe/CMakeFiles/scribus_desaxe_lib.dir/saxiohelper.cpp.o]
> Error 1
> make[1]: *** [scribus/desaxe/CMakeFiles/scribus_desaxe_lib.dir/all] Error 2
> make: *** [all] Error 2
> 
>   freetype.h is present on the system:
> 
> $ locate freetype.h
> /usr/include/freetype2/freetype.h
> 
>   I don't see a place in the build script to provide the include directory.
> 
>   Please suggest how to resolve this issue.

I have just tested on a clean VM and it worked fine there

scribus:
  MD5SUM check for scribus-1.4.6.tar.xz ... OK
  Building package scribus-1.4.6-x86_64-1_SBo.tgz ... OK

this is tested against latest stable, not current and no multilib

-- 
Willy Sudiarto Raharjo

-------------- 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/20170128/5f4145bc/attachment-0001.asc>

From baildon.research at googlemail.com  Sat Jan 28 10:24:35 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Sat, 28 Jan 2017 10:24:35 +0000
Subject: [Slackbuilds-users] snort
In-Reply-To: <6734d4eb-1879-5f47-768d-117ca746900a@slackonly.com>
References: <6734d4eb-1879-5f47-768d-117ca746900a@slackonly.com>
Message-ID: <CAMt7G9Q6Nww2m95=R81AN-9_k-o2vyNH0dU-xY7r7RCHFaNd5A@mail.gmail.com>

> Snort is unable to run in a VPS machine as it uses venet instead of eth...
> We can avoid this if configure snort with --enable-non-ether-decoders
> Can we add this as option to SlackBuild?

Yes! Thank you!!

I've got the same kind of VPS but I don't run snort on it yet -- but I
really should, so thanks for that too :)

-D.

From reedych at reedych.pw  Sat Jan 28 14:00:15 2017
From: reedych at reedych.pw (=?UTF-8?B?0KDQuNC00LjRhw==?=)
Date: Sat, 28 Jan 2017 20:00:15 +0600
Subject: [Slackbuilds-users] ftp.kernel.org will shut down at this year
In-Reply-To: <3e7808be-29ac-2d1f-efcb-9edbb87ad692@slackbuilds.org>
References: <9b7d8cf3-4b09-01ef-9545-e927db464f68@reedych.pw>
 <3e7808be-29ac-2d1f-efcb-9edbb87ad692@slackbuilds.org>
Message-ID: <680d88d0-3cad-f9c2-c8ae-ba4e210f1cc8@reedych.pw>

ok, thanks.


On 28.01.2017 14:18, Willy Sudiarto Raharjo wrote:
>> https://kernel.org/shutting-down-ftp-services.html. If anyone maintains
>> slackbuilds what uses it as download link, please fix it. Thanks!
>
> running grep ftp.kernel.org slackbuilds/*/*/*.info returns zero results
>
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170128/d01ca559/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 803 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170128/d01ca559/attachment.asc>

From atelszewski at gmail.com  Sat Jan 28 19:55:15 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 28 Jan 2017 20:55:15 +0100
Subject: [Slackbuilds-users] hunspell-pl 20170128 update
Message-ID: <9667b423-15d0-0bef-cdfa-fd887ef69c9a@gmail.com>

Hi,

The update to hunspell-pl 
[https://slackbuilds.org/cgit/slackbuilds/commit/?id=11bc3f81e] uses the 
upstream download URL.

But the upstream delete the source as soon as they release newer version.

Just to let you know ;-)

(Bcc'd maintainer).

-- 
Best regards,
Andrzej Telszewski

From kingbeowulf at gmail.com  Sun Jan 29 03:40:03 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 28 Jan 2017 19:40:03 -0800
Subject: [Slackbuilds-users] [SlackBuilds-users] protobuf (2.6.1)
 dependencies
Message-ID: <d58eba6c-97fd-77b8-f364-eeee7ec7482b@gmail.com>

Protobuf lists the dependencies:

pytz
python-dateutil
google-apputils
python-gflags

And I have it running here on 64 and 32 bit (mumble and mumure) without
google-apputils, so is this a soft not hard dependency for other packages?

Apologies if this has been discussed before.

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

From willysr at slackbuilds.org  Sun Jan 29 05:57:19 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 29 Jan 2017 12:57:19 +0700
Subject: [Slackbuilds-users] [SlackBuilds-users] protobuf (2.6.1)
 dependencies
In-Reply-To: <d58eba6c-97fd-77b8-f364-eeee7ec7482b@gmail.com>
References: <d58eba6c-97fd-77b8-f364-eeee7ec7482b@gmail.com>
Message-ID: <03a59e2d-1a69-7994-5a79-33409e9e9482@slackbuilds.org>

> Protobuf lists the dependencies:
> 
> pytz
> python-dateutil
> google-apputils
> python-gflags
> 
> And I have it running here on 64 and 32 bit (mumble and mumure) without
> google-apputils, so is this a soft not hard dependency for other packages?
> 
> Apologies if this has been discussed before.

Yes, someone discovered that protobuf will download and build
google-apputils in the background and it shouldn't be allowed, so the
maintainer submitted google-apputils and list it as a dependency.

your package worked as it is with or without google-apputils, as it will
only have difference during build time.


-- 
Willy Sudiarto Raharjo

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

From baildon.research at googlemail.com  Sun Jan 29 14:51:36 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 29 Jan 2017 14:51:36 +0000
Subject: [Slackbuilds-users] Groups and users in README, was Re: kafka
Message-ID: <CAMt7G9QpOMwShLXx1GYZ4na1=Qq7KjO0MhFO6q5MwsM=DcaxxQ@mail.gmail.com>

Hi everybody,

I've tried to make README consistent about groupnames and usernames in
all the SlackBuilds that Andreas mentioned.  You can review the
changes here --

https://slackbuilds.org/cgit/slackbuilds/log/?h=README-review

-- and if you don't like the changes, please reply here, and I'll
change the changes ;)

The SlackBuilds affected are

> network/dovecot
> network/etherpad-lite
> network/lighttpd
> network/lighttpd2
> network/openfire
> network/roger-router
> network/sks-keyserver
> system/apache-activemq
> system/clamav
> system/jenkins
> system/kafka

Thanks to Miguel, Andr? and Andreas for their observations and suggestions.
-D.

From kingbeowulf at gmail.com  Sun Jan 29 18:59:41 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 29 Jan 2017 10:59:41 -0800
Subject: [Slackbuilds-users]  dotconf keywords missing
Message-ID: <06f5868c-6208-b707-4c2f-07033c5fcff3@gmail.com>

I just noticed that I forgot to include keywords on the original
submission.  Please add:

Keywords: configuration, parser

Thanks,
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/20170129/8445d3ce/attachment-0001.asc>

From baildon.research at googlemail.com  Sun Jan 29 20:17:48 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 29 Jan 2017 20:17:48 +0000
Subject: [Slackbuilds-users] dotconf keywords missing
In-Reply-To: <06f5868c-6208-b707-4c2f-07033c5fcff3@gmail.com>
References: <06f5868c-6208-b707-4c2f-07033c5fcff3@gmail.com>
Message-ID: <CAMt7G9S-T59CrQuw4bSa_BVFFnEUOgH56ucgVM8vXY=fb7jaMw@mail.gmail.com>

> I just noticed that I forgot to include keywords on the original
> submission.  Please add:
> Keywords: configuration, parser

done!
-D.

From atelszewski at gmail.com  Mon Jan 30 15:32:33 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 30 Jan 2017 16:32:33 +0100
Subject: [Slackbuilds-users] Renaming ltm to be libtommath
Message-ID: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>

Hi,

I'm about to submit SlackBuild for LibTomCrypt [http://www.libtom.net/].

Although the source code tarball is named "crypt", I'm going to name the 
SlackBuild and resulting package "libtomcrypt".

At that point I would like to ask if it would make sense to rename the 
"ltm" library (already maintained by B. Watson) to be "libtommath"?

It's kinda cosmetic change, but in my opinion that name would be more 
relevant.

I found only one package, convertlit, that currently depends on ltm, so 
the change should be fairly non-invasive.

Of course, libtomcrypt is going to depend on ltm/libtommath too ;-)

(Bcc-d maintainer).

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Mon Jan 30 16:26:54 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 30 Jan 2017 23:26:54 +0700
Subject: [Slackbuilds-users] Renaming ltm to be libtommath
In-Reply-To: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>
References: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>
Message-ID: <32bef272-3dc7-f428-8cb3-e5edc0f6f0ee@slackbuilds.org>

> I'm about to submit SlackBuild for LibTomCrypt [http://www.libtom.net/].
> 
> Although the source code tarball is named "crypt", I'm going to name the
> SlackBuild and resulting package "libtomcrypt".
> 
> At that point I would like to ask if it would make sense to rename the
> "ltm" library (already maintained by B. Watson) to be "libtommath"?
> 
> It's kinda cosmetic change, but in my opinion that name would be more
> relevant.
> 
> I found only one package, convertlit, that currently depends on ltm, so
> the change should be fairly non-invasive.
> 
> Of course, libtomcrypt is going to depend on ltm/libtommath too ;-)

renaming a package is not that simple as it would need to be removed
from the DB and added as a new one + changing packages that depends on it.

For that same reason i keep my letsencrypt as it is even though upstream
have renamed the project to certbot.


-- 
Willy Sudiarto Raharjo

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

From atelszewski at gmail.com  Mon Jan 30 16:36:12 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 30 Jan 2017 17:36:12 +0100
Subject: [Slackbuilds-users] Renaming ltm to be libtommath
In-Reply-To: <32bef272-3dc7-f428-8cb3-e5edc0f6f0ee@slackbuilds.org>
References: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>
 <32bef272-3dc7-f428-8cb3-e5edc0f6f0ee@slackbuilds.org>
Message-ID: <ba224e87-7786-5493-878b-7be1708b3297@gmail.com>

On 30/01/17 17:26, Willy Sudiarto Raharjo wrote:
>> I'm about to submit SlackBuild for LibTomCrypt [http://www.libtom.net/].
>>
>> Although the source code tarball is named "crypt", I'm going to name the
>> SlackBuild and resulting package "libtomcrypt".
>>
>> At that point I would like to ask if it would make sense to rename the
>> "ltm" library (already maintained by B. Watson) to be "libtommath"?
>>
>> It's kinda cosmetic change, but in my opinion that name would be more
>> relevant.
>>
>> I found only one package, convertlit, that currently depends on ltm, so
>> the change should be fairly non-invasive.
>>
>> Of course, libtomcrypt is going to depend on ltm/libtommath too ;-)
>
> renaming a package is not that simple as it would need to be removed
> from the DB and added as a new one + changing packages that depends on it.
>
> For that same reason i keep my letsencrypt as it is even though upstream
> have renamed the project to certbot.
>

When it comes to dependent packages, I see only one (convertlit).
Anyways, if it's too much work, then of course no.

-- 
Best regards,
Andrzej Telszewski

From C.J.Theunissen at differ.nl  Mon Jan 30 17:58:10 2017
From: C.J.Theunissen at differ.nl (Kees Theunissen)
Date: Mon, 30 Jan 2017 18:58:10 +0100 (CET)
Subject: [Slackbuilds-users] ftp.kernel.org will shut down at this year
In-Reply-To: <3e7808be-29ac-2d1f-efcb-9edbb87ad692@slackbuilds.org>
References: <9b7d8cf3-4b09-01ef-9545-e927db464f68@reedych.pw>
 <3e7808be-29ac-2d1f-efcb-9edbb87ad692@slackbuilds.org>
Message-ID: <alpine.LNX.2.11.1701301845100.20031@pcict9.rijnh.nl>

On Sat, 28 Jan 2017, Willy Sudiarto Raharjo wrote:

>> https://kernel.org/shutting-down-ftp-services.html. If anyone maintains
>> slackbuilds what uses it as download link, please fix it. Thanks!
>
>
>running grep ftp.kernel.org slackbuilds/*/*/*.info returns zero results
>

I think you should run:  grep -i 'ftp.*kernel\.org' ......
That will also match on "ftp://mirrors.kernel.org" and takes into
account that DNS names are case insensitive.

This still yields zero results on 14.2 but on 14.1 there are two hits.

kees at pcict9:/var/lib/sbopkg/SBo/14.1$ grep -i 'ftp.*kernel\.org' */*/*.info
graphics/plotutils/plotutils.info:DOWNLOAD="ftp://mirrors.kernel.org/gnu/plotutils/plotutils-2.6.tar.gz"
multimedia/gnash/gnash.info:DOWNLOAD="ftp://mirrors.kernel.org/gnu/gnash/0.8.10/gnash-0.8.10.tar.bz2"



Regards,

Kees Theunissen.

-- 
Kees Theunissen,  System and network manager,   Tel: +31 (0)40-3334724
Dutch Institute For Fundamental Energy Research (DIFFER)
e-mail address:   C.J.Theunissen at differ.nl
postal address:   PO Box 6336, 5600 HH, Eindhoven, the Netherlands
visitors address: De Zaale 20, 5612 AJ, Eindhoven, the Netherlands


From yalhcru at gmail.com  Mon Jan 30 18:30:33 2017
From: yalhcru at gmail.com (B Watson)
Date: Mon, 30 Jan 2017 13:30:33 -0500
Subject: [Slackbuilds-users] Renaming ltm to be libtommath
In-Reply-To: <ba224e87-7786-5493-878b-7be1708b3297@gmail.com>
References: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>
 <32bef272-3dc7-f428-8cb3-e5edc0f6f0ee@slackbuilds.org>
 <ba224e87-7786-5493-878b-7be1708b3297@gmail.com>
Message-ID: <CAN1hMuBc9euJJ49X2admcn3G5pFk9bFeLQ7bnBg-G-kq4RtbMA@mail.gmail.com>

On 1/30/17, Andrzej Telszewski <atelszewski at gmail.com> wrote:

> When it comes to dependent packages, I see only one (convertlit).
> Anyways, if it's too much work, then of course no.

I wouldn't mind resubmitting ltm as libtommath. Debian and Gentoo
both call theirs libtommath, not ltm, so there's precedent.

convertlit will need updating, but convertlit is mine too, so no problem
there.

Willy, if you think this is a terrible idea, let me know, otherwise I'll
do this Real Soon Now.

From rshepard at appl-ecosys.com  Mon Jan 30 23:38:28 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Mon, 30 Jan 2017 15:38:28 -0800 (PST)
Subject: [Slackbuilds-users] Help needed building pgadmin3
Message-ID: <alpine.LNX.2.11.1701301538040.19097@localhost>

   Installed here is pgadmin-1.22.1, but apparently built against earlier
libraries so it won't run. I downloaded new copies of the build script and
souce tarball.

   Running the SlackBuild script fails with this error:

In file included from ../pgadmin/include/pgAdmin3.h:28:0,
                  from pgAdmin3.cpp:13:
../pgadmin/include/ctl/ctlSQLBox.h:17:24: fatal error: wx/stc/stc.h: No such
file or directory
  #include <wx/stc/stc.h>
                         ^
compilation terminated.
make[3]: *** [pgAdmin3.o] Error 1
make[3]: Leaving directory /tmp/SBo/pgadmin3-1.22.1/pgadmin'
make[2]: *** [all] Error 2
make[2]: Leaving directory /tmp/SBo/pgadmin3-1.22.1/pgadmin'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory /tmp/SBo/pgadmin3-1.22.1'
make: *** [all] Error 2

   Installed here is /usr/include/wx-3.0/wx/stc/stc.h.

   How do I pass this information to the SlackBuild script?

TIA,

Rich


From willysr at slackbuilds.org  Tue Jan 31 01:07:10 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 31 Jan 2017 08:07:10 +0700
Subject: [Slackbuilds-users] Renaming ltm to be libtommath
In-Reply-To: <CAN1hMuBc9euJJ49X2admcn3G5pFk9bFeLQ7bnBg-G-kq4RtbMA@mail.gmail.com>
References: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>
 <32bef272-3dc7-f428-8cb3-e5edc0f6f0ee@slackbuilds.org>
 <ba224e87-7786-5493-878b-7be1708b3297@gmail.com>
 <CAN1hMuBc9euJJ49X2admcn3G5pFk9bFeLQ7bnBg-G-kq4RtbMA@mail.gmail.com>
Message-ID: <d12db06c-facd-333a-da76-5954d0e397f1@slackbuilds.org>

>> When it comes to dependent packages, I see only one (convertlit).
>> Anyways, if it's too much work, then of course no.
> 
> I wouldn't mind resubmitting ltm as libtommath. Debian and Gentoo
> both call theirs libtommath, not ltm, so there's precedent.
> 
> convertlit will need updating, but convertlit is mine too, so no problem
> there.
> 
> Willy, if you think this is a terrible idea, let me know, otherwise I'll
> do this Real Soon Now.

please do so if you don't have any objection :)


-- 
Willy Sudiarto Raharjo

-------------- 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/20170131/5116fce7/attachment.asc>

From kingbeowulf at gmail.com  Tue Jan 31 01:10:58 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 30 Jan 2017 17:10:58 -0800
Subject: [Slackbuilds-users] Help needed building pgadmin3
In-Reply-To: <alpine.LNX.2.11.1701301538040.19097@localhost>
References: <alpine.LNX.2.11.1701301538040.19097@localhost>
Message-ID: <6d104459-17b4-d237-4020-7922020e8d62@gmail.com>

On 01/30/2017 03:38 PM, Rich Shepard wrote:
>   Installed here is pgadmin-1.22.1, but apparently built against earlier
> libraries so it won't run. I downloaded new copies of the build script and
> souce tarball.
> 
>   Running the SlackBuild script fails with this error:
> 
> In file included from ../pgadmin/include/pgAdmin3.h:28:0,
>                  from pgAdmin3.cpp:13:
> ../pgadmin/include/ctl/ctlSQLBox.h:17:24: fatal error: wx/stc/stc.h: No
> such
> file or directory
>  #include <wx/stc/stc.h>
>                         ^
> compilation terminated.
> make[3]: *** [pgAdmin3.o] Error 1
> make[3]: Leaving directory /tmp/SBo/pgadmin3-1.22.1/pgadmin'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory /tmp/SBo/pgadmin3-1.22.1/pgadmin'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory /tmp/SBo/pgadmin3-1.22.1'
> make: *** [all] Error 2
> 
>   Installed here is /usr/include/wx-3.0/wx/stc/stc.h.
> 

Rich,
You need to install wxPython (2.8.12) not wxPython3. I suspect you
installed wxGTK3 (included in wxPython3) and is too new.

-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/20170130/962d04d9/attachment-0001.asc>

From C.J.Theunissen at differ.nl  Tue Jan 31 04:05:11 2017
From: C.J.Theunissen at differ.nl (Kees Theunissen)
Date: Tue, 31 Jan 2017 05:05:11 +0100 (CET)
Subject: [Slackbuilds-users] Renaming ltm to be libtommath
In-Reply-To: <d12db06c-facd-333a-da76-5954d0e397f1@slackbuilds.org>
References: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>
 <32bef272-3dc7-f428-8cb3-e5edc0f6f0ee@slackbuilds.org>
 <ba224e87-7786-5493-878b-7be1708b3297@gmail.com>
 <CAN1hMuBc9euJJ49X2admcn3G5pFk9bFeLQ7bnBg-G-kq4RtbMA@mail.gmail.com>
 <d12db06c-facd-333a-da76-5954d0e397f1@slackbuilds.org>
Message-ID: <alpine.LNX.2.11.1701310500510.22572@pcict9.rijnh.nl>

Sorry Willy that I relied to you instead of the list.
Here is a new attempt.


On Tue, 31 Jan 2017, Willy Sudiarto Raharjo wrote:

>>> When it comes to dependent packages, I see only one (convertlit).
>>> Anyways, if it's too much work, then of course no.
>>
>> I wouldn't mind resubmitting ltm as libtommath. Debian and Gentoo
>> both call theirs libtommath, not ltm, so there's precedent.
>>
>> convertlit will need updating, but convertlit is mine too, so no problem
>> there.
>>
>> Willy, if you think this is a terrible idea, let me know, otherwise I'll
>> do this Real Soon Now.
>
>please do so if you don't have any objection :)
>

It's cumbersome and error prone for users of the renamed package.
Although "upgradepkg" _does_ support the replacement op a package
with a differently named one this _won't_ and _can't_ be supported
by automated tools like sbopkg. The .info file simply has no fields
like "old_name" or "new_name".

All an automated tool can do is flagging that an installed package
doesn't exist in the repository anymore. I don't know if any tool
does so.

The actual replacement needs some manual intervention either by
removing the old named package and installing the new one manually
or running upgradepkg with the old and new names as an argument.

Users who miss the renaming of a package will also miss future
(securety) updates.


Regards,

Kees Theunissen.

-- 
Kees Theunissen,  System and network manager,   Tel: +31 (0)40-3334724
Dutch Institute For Fundamental Energy Research (DIFFER)
e-mail address:   C.J.Theunissen at differ.nl
postal address:   PO Box 6336, 5600 HH, Eindhoven, the Netherlands
visitors address: De Zaale 20, 5612 AJ, Eindhoven, the Netherlands


From C.J.Theunissen at differ.nl  Tue Jan 31 04:40:08 2017
From: C.J.Theunissen at differ.nl (Kees Theunissen)
Date: Tue, 31 Jan 2017 05:40:08 +0100 (CET)
Subject: [Slackbuilds-users] Renaming ltm to be libtommath
In-Reply-To: <alpine.LNX.2.11.1701310500510.22572@pcict9.rijnh.nl>
References: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>
 <32bef272-3dc7-f428-8cb3-e5edc0f6f0ee@slackbuilds.org>
 <ba224e87-7786-5493-878b-7be1708b3297@gmail.com>
 <CAN1hMuBc9euJJ49X2admcn3G5pFk9bFeLQ7bnBg-G-kq4RtbMA@mail.gmail.com>
 <d12db06c-facd-333a-da76-5954d0e397f1@slackbuilds.org>
 <alpine.LNX.2.11.1701310500510.22572@pcict9.rijnh.nl>
Message-ID: <alpine.LNX.2.11.1701310513420.22736@pcict9.rijnh.nl>

On Tue, 31 Jan 2017, Kees Theunissen wrote:

>It's cumbersome and error prone for users of the renamed package.
>Although "upgradepkg" _does_ support the replacement op a package
>with a differently named one this _won't_ and _can't_ be supported
>by automated tools like sbopkg. The .info file simply has no fields
>like "old_name" or "new_name".
>
>All an automated tool can do is flagging that an installed package
>doesn't exist in the repository anymore. I don't know if any tool
>does so.

As a work arroud it is possible to get the user's attention by
keeping the old named package in the repository with:
-- an updated version number (preferably an unlikely high value),
-- a README file that mentions the renaming of the package,
-- a .info file with fake download urls.
This will surely trigger an error in automated tools.


Regards,

Kees Theunissen.

-- 
Kees Theunissen,  System and network manager,   Tel: +31 (0)40-3334724
Dutch Institute For Fundamental Energy Research (DIFFER)
e-mail address:   C.J.Theunissen at differ.nl
postal address:   PO Box 6336, 5600 HH, Eindhoven, the Netherlands
visitors address: De Zaale 20, 5612 AJ, Eindhoven, the Netherlands



From yalhcru at gmail.com  Tue Jan 31 07:05:03 2017
From: yalhcru at gmail.com (B Watson)
Date: Tue, 31 Jan 2017 02:05:03 -0500
Subject: [Slackbuilds-users] Renaming ltm to be libtommath
In-Reply-To: <alpine.LNX.2.11.1701310500510.22572@pcict9.rijnh.nl>
References: <abb232a2-bdac-f0e0-eaf3-5631fcf030f4@gmail.com>
 <32bef272-3dc7-f428-8cb3-e5edc0f6f0ee@slackbuilds.org>
 <ba224e87-7786-5493-878b-7be1708b3297@gmail.com>
 <CAN1hMuBc9euJJ49X2admcn3G5pFk9bFeLQ7bnBg-G-kq4RtbMA@mail.gmail.com>
 <d12db06c-facd-333a-da76-5954d0e397f1@slackbuilds.org>
 <alpine.LNX.2.11.1701310500510.22572@pcict9.rijnh.nl>
Message-ID: <CAN1hMuD-EdEWYm2a05PNf=2-yE=TdqGTO8X8JmiLkez98QS-nw@mail.gmail.com>

On 1/30/17, Kees Theunissen <C.J.Theunissen at differ.nl> wrote:

> It's cumbersome and error prone for users of the renamed package.

In this case I think it won't be a big deal. Only one package depends
on ltm, and that's convertlit... and I'll be updating both of them at
the same time, renaming ltm and changing convertlit's info file so it
depends on libtommath instead of ltm... and bumping convertlit's BUILD,
so sbopkg will notice it's changed.

Anyone with ltm installed, almost certainly has it installed because it's
a dep for convertlit. So using sbopkg to look for upgradable packages will
see the new convertlit, and its info file will show the new libtommath.

I'll add a note to libtommath's README saying 'this build was previously
known as ltm; if you still have that installed, remove it before
installing libtommath'. I hate to sound like this, but... anyone who
doesn't read the README deserves whatever happens to them. That applies
whether they're using a tool like sbopkg or not.

The alternative to all this (not renaming the package) would be easier,
but I've become convinced it really does have the wrong name. If there's
no way to fix mistakes, we'll end up with an even bigger mess.

From rshepard at appl-ecosys.com  Tue Jan 31 13:51:34 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 31 Jan 2017 05:51:34 -0800 (PST)
Subject: [Slackbuilds-users] Help needed building pgadmin3
In-Reply-To: <6d104459-17b4-d237-4020-7922020e8d62@gmail.com>
References: <alpine.LNX.2.11.1701301538040.19097@localhost>
 <6d104459-17b4-d237-4020-7922020e8d62@gmail.com>
Message-ID: <alpine.LNX.2.11.1701310542350.16991@localhost>

On Mon, 30 Jan 2017, King Beowulf wrote:

> You need to install wxPython (2.8.12) not wxPython3. I suspect you
> installed wxGTK3 (included in wxPython3) and is too new.

Ed,

   I used to have both wxPython-2.8.12 and wxPython-3.0.2.0 installed.
Learning that the latter works with python2 and python3 I removed the
former.

   This leads to the question I should have asked about pgadmin4. When I try
to build it this is the result:

pgadmin4-1.1/docs/en_US/images/view_sql.png
./pgadmin4.SlackBuild: line 56: ./configure: No such file or directory

and these are lines 56-64:

CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
   --prefix=/usr \
   --libdir=/usr/lib${LIBDIRSUFFIX} \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --mandir=/usr/man \
   --build=$ARCH-slackware-linux

   I'd rather use pgadmin4 with wxPython-3.0.2.0 and python3-3.5.2 but could
not figure out why I was getting that error.

   Help getting pgadmin4 running is better than futzing with pgadmin3.

Thanks,

Rich

From kingbeowulf at gmail.com  Tue Jan 31 16:59:43 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 31 Jan 2017 08:59:43 -0800
Subject: [Slackbuilds-users] Help needed building pgadmin3
In-Reply-To: <alpine.LNX.2.11.1701310542350.16991@localhost>
References: <alpine.LNX.2.11.1701301538040.19097@localhost>
 <6d104459-17b4-d237-4020-7922020e8d62@gmail.com>
 <alpine.LNX.2.11.1701310542350.16991@localhost>
Message-ID: <f7fb2f31-a494-dc2b-463a-30f2d7d11940@gmail.com>

On 01/31/2017 05:51 AM, Rich Shepard wrote:
> On Mon, 30 Jan 2017, King Beowulf wrote:
> 
>> You need to install wxPython (2.8.12) not wxPython3. I suspect you
>> installed wxGTK3 (included in wxPython3) and is too new.
> 
> Ed,
> 
>   I used to have both wxPython-2.8.12 and wxPython-3.0.2.0 installed.
> Learning that the latter works with python2 and python3 I removed the
> former.
> 
>   This leads to the question I should have asked about pgadmin4. When I try
> to build it this is the result:
> 
> pgadmin4-1.1/docs/en_US/images/view_sql.png
> ./pgadmin4.SlackBuild: line 56: ./configure: No such file or directory
> 
---snip---

Rich,

pgadmin4 is based on QT and uses a completely different build system
based on qmake. See build instruction in:

https://www.pgadmin.org/download/source4.php

The slackbuild for pgadmin3 will not work.

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

From rshepard at appl-ecosys.com  Tue Jan 31 17:25:59 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 31 Jan 2017 09:25:59 -0800 (PST)
Subject: [Slackbuilds-users] Help needed building pgadmin3
In-Reply-To: <f7fb2f31-a494-dc2b-463a-30f2d7d11940@gmail.com>
References: <alpine.LNX.2.11.1701301538040.19097@localhost>
 <6d104459-17b4-d237-4020-7922020e8d62@gmail.com>
 <alpine.LNX.2.11.1701310542350.16991@localhost>
 <f7fb2f31-a494-dc2b-463a-30f2d7d11940@gmail.com>
Message-ID: <alpine.LNX.2.11.1701310924190.16991@localhost>

On Tue, 31 Jan 2017, King Beowulf wrote:

> pgadmin4 is based on QT and uses a completely different build system
> based on qmake. See build instruction in:
>
> https://www.pgadmin.org/download/source4.php
>
> The slackbuild for pgadmin3 will not work.

Ed,

   Oh. OK. I have Qt5 (and PyQt5) installed so I'll follow the pgadmin.org
instructions. I did not pay attention to the difference and copied/modified
the slackbuild script.

Thanks,

Rich

From 1.41421 at gmail.com  Tue Jan 31 20:34:19 2017
From: 1.41421 at gmail.com (JCA)
Date: Tue, 31 Jan 2017 13:34:19 -0700
Subject: [Slackbuilds-users] Chromium build broken in 14.1
Message-ID: <CAFy1yb2tWiS4okywgVTGSE7MuAYHQbUr9bwppUp+Af4tC44Bfg@mail.gmail.com>

I have tried building Chromium for 14.1, using the relevant Slackbuilds
scripts. Here is what  I am getting:

  cc '-DANGLE_DX11' '-D_FILE_OFFSET_BITS=64' '-DDISABLE_NACL'
'-DCHROMIUM_BUILD' '-DUSE_DEFAULT_RENDER_THEME=1' '-DUSE_LIBJPEG_TURBO=1'
'-DUSE_NSS=1' '-DUSE_X11=1' '-DENABLE_ONE_CLICK_SIGNIN'
'-DGTK_DISABLE_SINGLE_INCLUDES=1' '-DUSE_XI2_MT=2' '-DENABLE_REMOTING=1'
'-DENABLE_WEBRTC=1' '-DUSE_PROPRIETARY_CODECS' '-DENABLE_PEPPER_CDMS'
'-DENABLE_CONFIGURATION_POLICY' '-DENABLE_INPUT_SPEECH'
'-DENABLE_NOTIFICATIONS' '-DENABLE_GPU=1' '-DENABLE_EGLIMAGE=1'
'-DENABLE_TASK_MANAGER=1' '-DENABLE_EXTENSIONS=1'
'-DENABLE_PLUGIN_INSTALLATION=1' '-DENABLE_PLUGINS=1'
'-DENABLE_SESSION_SERVICE=1' '-DENABLE_THEMES=1' '-DENABLE_BACKGROUND=1'
'-DENABLE_AUTOMATION=1' '-DENABLE_GOOGLE_NOW=1' '-DCLD_VERSION=1'
'-DENABLE_FULL_PRINTING=1' '-DENABLE_PRINTING=1' '-DENABLE_SPELLCHECK=1'
'-DENABLE_CAPTIVE_PORTAL_DETECTION=1' '-DENABLE_MANAGED_USERS=1'
'-DENABLE_MDNS=1' '-DNO_PKCS11_BYPASS' '-DNSS_ENABLE_ECC'
'-DUSE_UTIL_DIRECTLY' '-DNDEBUG' '-DNVALGRIND'
'-DDYNAMIC_ANNOTATIONS_ENABLED=0' -Inet/third_party/nss/ssl/bodge
 -fstack-protector --param=ssp-buffer-size=4 -pthread -fno-exceptions
-fno-strict-aliasing -Wno-unused-parameter -Wno-missing-field-initializers
-fvisibility=hidden -pipe -fPIC -Wno-unused-local-typedefs
-I/usr/include/nss -I/usr/include/nspr -Wno-format -Wno-unused-result -m32
-mmmx -O2 -fno-ident -fdata-sections -ffunction-sections -fno-unwind-tables
-fno-asynchronous-unwind-tables -O2 -march=i486 -mtune=i686
-Wno-unused-local-typedefs  -MMD -MF
out/Release/.deps/out/Release/obj.target/libssl/net/third_party/nss/ssl/ssl3con.o.d.raw
 -c -o out/Release/obj.target/libssl/net/third_party/nss/ssl/ssl3con.o
net/third_party/nss/ssl/ssl3con.c
net/third_party/nss/ssl/ssl3con.c: In function 'ssl3_ChaCha20Poly1305':
net/third_party/nss/ssl/ssl3con.c:2079:15: error: 'CK_NSS_AEAD_PARAMS' has
no member named 'pIv'
     aeadParams.pIv = (unsigned char *) additionalData;
               ^
net/third_party/nss/ssl/ssl3con.c:2080:15: error: 'CK_NSS_AEAD_PARAMS' has
no member named 'ulIvLen'
     aeadParams.ulIvLen = 8;
               ^
make: *** [out/Release/obj.target/libssl/net/third_party/nss/ssl/ssl3con.o]
Error 1

After some googling it seems to be the case that the culprit in an
upgraded mozilla-nss package - 3.20 seems to be OK, 3.23 causes the problem
above.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170131/8508b0cf/attachment-0001.html>

From kingbeowulf at gmail.com  Tue Jan 31 20:50:49 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 31 Jan 2017 12:50:49 -0800
Subject: [Slackbuilds-users]  Stellarium update
Message-ID: <2e391137-6f11-6129-3f9b-904c36f2403a@gmail.com>

Stellarium just needs a minor version bump to 0.15.1.  Diff attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stellarium-0.15.1.diff
Type: text/x-patch
Size: 1081 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170131/136af12f/attachment.bin>
-------------- 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/20170131/136af12f/attachment.asc>

From kingbeowulf at gmail.com  Tue Jan 31 21:09:26 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 31 Jan 2017 13:09:26 -0800
Subject: [Slackbuilds-users]  Stellarium-0.15.x, qt-5.7.x and libinput
Message-ID: <e8032f44-2208-b4ae-5f9c-5cc7132eccb1@gmail.com>

All:

This error keeps popping up here when running Stellarium.
-------------
   $ stellarium
   This application failed to start because it could not find or load
   the Qt platform plugin "xcb" in "".

   Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
   offscreen, xcb.

   Reinstalling the application may fix this problem.
   Aborted
---------------
After upgrading to qt-5.7.1, then rebuilding stellarium and then
upgrading stellarium to 0.15.1, the run time error persists.  I tracked
it down to:
---------------
   $ ldd /usr/lib64/qt5/plugins/platforms/libqxcb.so | grep not
	libinput.so.10 => not found
	libinput.so.10 => not found
---------------

Installing libinput fixes the stellarium error which then runs normally.
 I recommend the following:
1. bump stellarium to 0.15.1
2. mention that libinput is required as a run time dependency.
3. on qt5 page, move libinput to "required" or "optional" as a run time
dependency for Qt5 plugin xcb (libqxcb.so)
4. on qt5 page fix libinput (not available at slackbuilds.org) since it
is available.

Thanks
-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/20170131/3430e402/attachment.asc>

From willysr at slackbuilds.org  Tue Jan 31 22:30:44 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 1 Feb 2017 05:30:44 +0700
Subject: [Slackbuilds-users] ftp.kernel.org will shut down at this year
In-Reply-To: <alpine.LNX.2.11.1701301845100.20031@pcict9.rijnh.nl>
References: <9b7d8cf3-4b09-01ef-9545-e927db464f68@reedych.pw>
 <3e7808be-29ac-2d1f-efcb-9edbb87ad692@slackbuilds.org>
 <alpine.LNX.2.11.1701301845100.20031@pcict9.rijnh.nl>
Message-ID: <05904ef7-15a7-7188-f05f-827708e14daf@slackbuilds.org>

> This still yields zero results on 14.2 but on 14.1 there are two hits.
> 
> kees at pcict9:/var/lib/sbopkg/SBo/14.1$ grep -i 'ftp.*kernel\.org' */*/*.info
> graphics/plotutils/plotutils.info:DOWNLOAD="ftp://mirrors.kernel.org/gnu/plotutils/plotutils-2.6.tar.gz"
> multimedia/gnash/gnash.info:DOWNLOAD="ftp://mirrors.kernel.org/gnu/gnash/0.8.10/gnash-0.8.10.tar.bz2"

I think one of the admin had fixed this now


-- 
Willy Sudiarto Raharjo

-------------- 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/20170201/6379ebf3/attachment.asc>

From willysr at slackbuilds.org  Tue Jan 31 22:36:11 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 1 Feb 2017 05:36:11 +0700
Subject: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput
In-Reply-To: <e8032f44-2208-b4ae-5f9c-5cc7132eccb1@gmail.com>
References: <e8032f44-2208-b4ae-5f9c-5cc7132eccb1@gmail.com>
Message-ID: <f2423b25-7224-c454-2fda-99c92a736294@slackbuilds.org>

> Installing libinput fixes the stellarium error which then runs normally.
>  I recommend the following:
> 1. bump stellarium to 0.15.1
> 2. mention that libinput is required as a run time dependency.
> 3. on qt5 page, move libinput to "required" or "optional" as a run time
> dependency for Qt5 plugin xcb (libqxcb.so)
> 4. on qt5 page fix libinput (not available at slackbuilds.org) since it
> is available.

I agree with adding libinput as a mandatory dep for qt5.



-- 
Willy Sudiarto Raharjo

-------------- 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/20170201/281bacea/attachment.asc>

From larryhaja at gmail.com  Tue Jan 31 22:37:27 2017
From: larryhaja at gmail.com (Larry Hajali)
Date: Tue, 31 Jan 2017 14:37:27 -0800
Subject: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput
In-Reply-To: <f2423b25-7224-c454-2fda-99c92a736294@slackbuilds.org>
References: <e8032f44-2208-b4ae-5f9c-5cc7132eccb1@gmail.com>
 <f2423b25-7224-c454-2fda-99c92a736294@slackbuilds.org>
Message-ID: <CAAZPBMg_JQMv8vyQT3fzQZC6gDfyCy7YeQQMqKO6R9eQskRWHA@mail.gmail.com>

On Tue, Jan 31, 2017 at 2:36 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > Installing libinput fixes the stellarium error which then runs normally.
> >  I recommend the following:
> > 1. bump stellarium to 0.15.1
> > 2. mention that libinput is required as a run time dependency.
> > 3. on qt5 page, move libinput to "required" or "optional" as a run time
> > dependency for Qt5 plugin xcb (libqxcb.so)
> > 4. on qt5 page fix libinput (not available at slackbuilds.org) since it
> > is available.
>
> I agree with adding libinput as a mandatory dep for qt5.
>
why?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170131/e7ceceab/attachment.html>

From willysr at slackbuilds.org  Tue Jan 31 22:55:11 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 1 Feb 2017 05:55:11 +0700
Subject: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput
In-Reply-To: <CAAZPBMg_JQMv8vyQT3fzQZC6gDfyCy7YeQQMqKO6R9eQskRWHA@mail.gmail.com>
References: <e8032f44-2208-b4ae-5f9c-5cc7132eccb1@gmail.com>
 <f2423b25-7224-c454-2fda-99c92a736294@slackbuilds.org>
 <CAAZPBMg_JQMv8vyQT3fzQZC6gDfyCy7YeQQMqKO6R9eQskRWHA@mail.gmail.com>
Message-ID: <8fb2fce7-0942-286d-89ed-855e2384dcb5@slackbuilds.org>

>>> Installing libinput fixes the stellarium error which then runs normally.
>>>  I recommend the following:
>>> 1. bump stellarium to 0.15.1
>>> 2. mention that libinput is required as a run time dependency.
>>> 3. on qt5 page, move libinput to "required" or "optional" as a run time
>>> dependency for Qt5 plugin xcb (libqxcb.so)
>>> 4. on qt5 page fix libinput (not available at slackbuilds.org) since it
>>> is available.
>>
>> I agree with adding libinput as a mandatory dep for qt5.
>>
> why?

Taken from
https://blog.qt.io/blog/2015/01/20/qt-weekly-23-qt-5-5-enhancements-for-linux-graphics-and-input-stacks/

Using libinput in place of the traditional evdevmouse|keyboard|touch
input handlers of Qt 5 has a number of advantages. By using it Qt
applications get the same behavior, configuration and calibration that
other clients, for example Weston use. It also simplifies bringup
scenarios since there will be no need to fight Qt?s input stack
separately in case libinput is already proven to work.

Since more packages are relying on qt5, xcb plugin will soon become an
important considerations and it does require libinput to work.

libinput is now included in -current as well, so it will be easy to
remove libinput from one place (qt5) instead of many different packages
in our repository in the next Slackware release.

if libinput stays as optional dep, we still have to fix stellarium's dep
as well. I will wait for qt5's decision about this.

ps: wayland and libinput are now available on our repository so that
will have to be fixed as well.


-- 
Willy Sudiarto Raharjo

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

From larryhaja at gmail.com  Tue Jan 31 23:39:13 2017
From: larryhaja at gmail.com (Larry Hajali)
Date: Tue, 31 Jan 2017 15:39:13 -0800
Subject: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput
In-Reply-To: <8fb2fce7-0942-286d-89ed-855e2384dcb5@slackbuilds.org>
References: <e8032f44-2208-b4ae-5f9c-5cc7132eccb1@gmail.com>
 <f2423b25-7224-c454-2fda-99c92a736294@slackbuilds.org>
 <CAAZPBMg_JQMv8vyQT3fzQZC6gDfyCy7YeQQMqKO6R9eQskRWHA@mail.gmail.com>
 <8fb2fce7-0942-286d-89ed-855e2384dcb5@slackbuilds.org>
Message-ID: <CAAZPBMhVrr_mTOrHVfjBp66hdKgR1gW8nTT1M0CDcmMkLeR7kQ@mail.gmail.com>

> >> I agree with adding libinput as a mandatory dep for qt5.
> >>
> > why?
>
> Taken from
> https://blog.qt.io/blog/2015/01/20/qt-weekly-23-qt-5-5-
> enhancements-for-linux-graphics-and-input-stacks/
>
> Using libinput in place of the traditional evdevmouse|keyboard|touch
> input handlers of Qt 5 has a number of advantages. By using it Qt
> applications get the same behavior, configuration and calibration that
> other clients, for example Weston use. It also simplifies bringup
> scenarios since there will be no need to fight Qt?s input stack
> separately in case libinput is already proven to work.
>
> Since more packages are relying on qt5, xcb plugin will soon become an
> important considerations and it does require libinput to work.
>
> libinput is now included in -current as well, so it will be easy to
> remove libinput from one place (qt5) instead of many different packages
> in our repository in the next Slackware release.
>
> if libinput stays as optional dep, we still have to fix stellarium's dep
> as well. I will wait for qt5's decision about this.
>
> ps: wayland and libinput are now available on our repository so that
> will have to be fixed as well.
>
>From your explanation I agree that adding libinput as a required dependency
for qt5 makes sense.  I only see these applications that need to be tested
with libinput as a required dep., which also have qt5 as a required dep.

desktop/compton-conf
network/qbittorrent-qt5
system/zuluCrypt

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