From ts at websafe.pl Thu Sep 1 12:08:57 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Thu, 1 Sep 2016 14:08:57 +0200 Subject: [Slackbuilds-users] apsw for 14.1 - wrong DOWNLOAD url Message-ID: <783049df-af25-707b-939a-a7c1c561131f@websafe.pl> Hello, there is a problem with apsw.SlackBuild for Slackware 14.1 https://slackbuilds.org/repository/14.1/python/apsw/ The new correct DOWNLOAD url is: https://github.com/rogerbinns/apsw/archive/3.7.17-r1.zip apsw.SlackBuild will require a small update too, because it's looking for: unzip $CWD/$PRGNAM-${VERSION/_/-}.zip -- 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: From willysr at slackbuilds.org Thu Sep 1 12:19:00 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 1 Sep 2016 19:19:00 +0700 Subject: [Slackbuilds-users] apsw for 14.1 - wrong DOWNLOAD url In-Reply-To: <783049df-af25-707b-939a-a7c1c561131f@websafe.pl> References: <783049df-af25-707b-939a-a7c1c561131f@websafe.pl> Message-ID: > there is a problem with apsw.SlackBuild for Slackware 14.1 > https://slackbuilds.org/repository/14.1/python/apsw/ > > The new correct DOWNLOAD url is: > https://github.com/rogerbinns/apsw/archive/3.7.17-r1.zip > > > apsw.SlackBuild will require a small update too, > because it's looking for: > > unzip $CWD/$PRGNAM-${VERSION/_/-}.zip hi Thomas the new URL will produce a different MD5SUM and older releases branch will get less (if not zero) update so if possible, please use the 14.2 branch. Many of the scripts in latest branch will keep working on earlier version of Slackware. -- 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: From willysr at slackbuilds.org Thu Sep 1 12:42:40 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 1 Sep 2016 19:42:40 +0700 Subject: [Slackbuilds-users] ssmtp - Interactive doinst script? In-Reply-To: References: Message-ID: <51eee506-39d9-955f-fc5d-59fb43c4111a@slackbuilds.org> > is it allowed to have interaction in the doinst.sh script? The ssmtp > doinst.sh launches a script that asks questions about the user setup. I > don't think that is supposed to happen. I thought that the standard way > to deal with that is to have some text in the README or README.SLACKWARE > files that explains how to set things up. Hi George Thanks for reporting. I have fixed it 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: From ts at websafe.pl Thu Sep 1 21:01:52 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Thu, 1 Sep 2016 23:01:52 +0200 Subject: [Slackbuilds-users] apsw for 14.1 - wrong DOWNLOAD url In-Reply-To: References: <783049df-af25-707b-939a-a7c1c561131f@websafe.pl> Message-ID: On 01.09.2016 14:19, Willy Sudiarto Raharjo wrote: > hi Thomas > the new URL will produce a different MD5SUM and older releases branch > will get less (if not zero) update so if possible, please use the 14.2 > branch. > Many of the scripts in latest branch will keep working on earlier > version of Slackware. OK, but this will break tools like slpkg running on Slackware 14.1 because they will download the not working SlackBuild for 14.1 pointing to a non-existent source tarball. And using the 14.2 SlackBuild on a 14.1 installation will not solve the problem: # cat /etc/slackware-version Slackware 14.1 # ./apsw.SlackBuild Archive: /tmp/apsw/apsw-3.13.0-r1.zip inflating: apsw-3.13.0-r1/MANIFEST.in inflating: apsw-3.13.0-r1/checksums inflating: apsw-3.13.0-r1/mingwsetup.bat inflating: apsw-3.13.0-r1/setup.py inflating: apsw-3.13.0-r1/tests.py inflating: apsw-3.13.0-r1/PKG-INFO inflating: apsw-3.13.0-r1/src/apsw.c inflating: apsw-3.13.0-r1/src/apswbuffer.c inflating: apsw-3.13.0-r1/src/apswversion.h inflating: apsw-3.13.0-r1/src/backup.c inflating: apsw-3.13.0-r1/src/blob.c inflating: apsw-3.13.0-r1/src/connection.c inflating: apsw-3.13.0-r1/src/cursor.c inflating: apsw-3.13.0-r1/src/exceptions.c inflating: apsw-3.13.0-r1/src/pyutil.c inflating: apsw-3.13.0-r1/src/statementcache.c inflating: apsw-3.13.0-r1/src/testextension.c inflating: apsw-3.13.0-r1/src/traceback.c inflating: apsw-3.13.0-r1/src/util.c inflating: apsw-3.13.0-r1/src/vfs.c inflating: apsw-3.13.0-r1/src/vtable.c inflating: apsw-3.13.0-r1/tools/apswtrace.py inflating: apsw-3.13.0-r1/tools/shell.py inflating: apsw-3.13.0-r1/tools/speedtest.py inflating: apsw-3.13.0-r1/doc/apsw.html inflating: apsw-3.13.0-r1/doc/backup.html inflating: apsw-3.13.0-r1/doc/benchmarking.html inflating: apsw-3.13.0-r1/doc/blob.html inflating: apsw-3.13.0-r1/doc/build.html inflating: apsw-3.13.0-r1/doc/changes.html inflating: apsw-3.13.0-r1/doc/connection.html inflating: apsw-3.13.0-r1/doc/copyright.html inflating: apsw-3.13.0-r1/doc/cursor.html inflating: apsw-3.13.0-r1/doc/dbapi.html inflating: apsw-3.13.0-r1/doc/download.html inflating: apsw-3.13.0-r1/doc/example.html inflating: apsw-3.13.0-r1/doc/exceptions.html inflating: apsw-3.13.0-r1/doc/execution.html inflating: apsw-3.13.0-r1/doc/extensions.html inflating: apsw-3.13.0-r1/doc/index.html inflating: apsw-3.13.0-r1/doc/pysqlite.html inflating: apsw-3.13.0-r1/doc/shell.html inflating: apsw-3.13.0-r1/doc/tips.html inflating: apsw-3.13.0-r1/doc/types.html inflating: apsw-3.13.0-r1/doc/vfs.html inflating: apsw-3.13.0-r1/doc/vtable.html inflating: apsw-3.13.0-r1/doc/genindex.html inflating: apsw-3.13.0-r1/doc/py-modindex.html inflating: apsw-3.13.0-r1/doc/search.html inflating: apsw-3.13.0-r1/doc/.buildinfo inflating: apsw-3.13.0-r1/doc/searchindex.js inflating: apsw-3.13.0-r1/doc/objects.inv inflating: apsw-3.13.0-r1/doc/_sources/apsw.txt inflating: apsw-3.13.0-r1/doc/_sources/backup.txt inflating: apsw-3.13.0-r1/doc/_sources/benchmarking.txt inflating: apsw-3.13.0-r1/doc/_sources/blob.txt inflating: apsw-3.13.0-r1/doc/_sources/build.txt inflating: apsw-3.13.0-r1/doc/_sources/changes.txt inflating: apsw-3.13.0-r1/doc/_sources/connection.txt inflating: apsw-3.13.0-r1/doc/_sources/copyright.txt inflating: apsw-3.13.0-r1/doc/_sources/cursor.txt inflating: apsw-3.13.0-r1/doc/_sources/dbapi.txt inflating: apsw-3.13.0-r1/doc/_sources/download.txt inflating: apsw-3.13.0-r1/doc/_sources/example.txt inflating: apsw-3.13.0-r1/doc/_sources/exceptions.txt inflating: apsw-3.13.0-r1/doc/_sources/execution.txt inflating: apsw-3.13.0-r1/doc/_sources/extensions.txt inflating: apsw-3.13.0-r1/doc/_sources/index.txt inflating: apsw-3.13.0-r1/doc/_sources/pysqlite.txt inflating: apsw-3.13.0-r1/doc/_sources/shell.txt inflating: apsw-3.13.0-r1/doc/_sources/tips.txt inflating: apsw-3.13.0-r1/doc/_sources/types.txt inflating: apsw-3.13.0-r1/doc/_sources/vfs.txt inflating: apsw-3.13.0-r1/doc/_sources/vtable.txt inflating: apsw-3.13.0-r1/doc/_static/pygments.css inflating: apsw-3.13.0-r1/doc/_static/up.png inflating: apsw-3.13.0-r1/doc/_static/basic.css inflating: apsw-3.13.0-r1/doc/_static/websupport.js inflating: apsw-3.13.0-r1/doc/_static/down-pressed.png inflating: apsw-3.13.0-r1/doc/_static/file.png inflating: apsw-3.13.0-r1/doc/_static/down.png inflating: apsw-3.13.0-r1/doc/_static/plus.png inflating: apsw-3.13.0-r1/doc/_static/up-pressed.png inflating: apsw-3.13.0-r1/doc/_static/comment.png inflating: apsw-3.13.0-r1/doc/_static/minus.png inflating: apsw-3.13.0-r1/doc/_static/ajax-loader.gif inflating: apsw-3.13.0-r1/doc/_static/searchtools.js inflating: apsw-3.13.0-r1/doc/_static/comment-bright.png inflating: apsw-3.13.0-r1/doc/_static/comment-close.png inflating: apsw-3.13.0-r1/doc/_static/doctools.js inflating: apsw-3.13.0-r1/doc/_static/jquery.js inflating: apsw-3.13.0-r1/doc/_static/underscore.js inflating: apsw-3.13.0-r1/doc/_static/sidebar.js inflating: apsw-3.13.0-r1/doc/_static/classic.css inflating: apsw-3.13.0-r1/doc/_static/default.css /usr/lib64/python2.7/site-packages/setuptools/dist.py:285: UserWarning: Normaliz ing '3.13.0-r1' to '3.13.0.post1' normalized_version, running build running build_ext SQLite: Using system sqlite include/libraries ICU: Added includes, flags and libraries from icu-config building 'apsw' extension creating build creating build/temp.linux-x86_64-2.7 creating build/temp.linux-x86_64-2.7/src gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict- prototypes -fPIC -DEXPERIMENTAL=1 -DNDEBUG=1 -DAPSW_FORK_CHECKER=1 -DSQLITE_ENAB LE_FTS4=1 -DSQLITE_ENABLE_FTS3=1 -DSQLITE_ENABLE_FTS3_PARENTHESIS=1 -DSQLITE_ENA BLE_RTREE=1 -DSQLITE_ENABLE_STAT4=1 -DSQLITE_ENABLE_JSON1=1 -DSQLITE_ENABLE_FTS5 =1 -DSQLITE_ENABLE_ICU=1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -D_REENTRANT=1 -Isrc -I/ usr/include -I/usr/include/python2.7 -c src/apsw.c -o build/temp.linux-x86_64-2. 7/src/apsw.o src/apsw.c:63:2: error: #error Your SQLite version is too old. It must be at lea st 3.13 #error Your SQLite version is too old. It must be at least 3.13 ^ In file included from /usr/include/python2.7/Python.h:8:0, from src/apsw.c:74: /usr/include/python2.7/pyconfig.h:1173:0: warning: "_POSIX_C_SOURCE" redefined [ enabled by default] #define _POSIX_C_SOURCE 200112L ^ In file included from /usr/include/assert.h:36:0, from src/apsw.c:67: /usr/include/features.h:231:0: note: this is the location of the previous defini tion # define _POSIX_C_SOURCE 200809L ^ In file included from src/apsw.c:132:0: src/connection.c: In function ?Connection_createscalarfunction?: src/connection.c:2314:40: error: ?SQLITE_DETERMINISTIC? undeclared (first use in this function) SQLITE_UTF8|(deterministic?SQLITE_DETERMINISTIC:0), ^ src/util.c:54:10: note: in definition of macro ?INUSE_CALL? { x; } \ ^ src/util.c:62:42: note: in expansion of macro ?_PYSQLITE_CALL_E? #define PYSQLITE_CON_CALL(y) INUSE_CALL(_PYSQLITE_CALL_E(self->db, y)) ^ src/connection.c:2310:3: note: in expansion of macro ?PYSQLITE_CON_CALL? PYSQLITE_CON_CALL( ^ src/connection.c:2314:40: note: each undeclared identifier is reported only once for each function it appears in SQLITE_UTF8|(deterministic?SQLITE_DETERMINISTIC:0), ^ src/util.c:54:10: note: in definition of macro ?INUSE_CALL? { x; } \ ^ src/util.c:62:42: note: in expansion of macro ?_PYSQLITE_CALL_E? #define PYSQLITE_CON_CALL(y) INUSE_CALL(_PYSQLITE_CALL_E(self->db, y)) ^ src/connection.c:2310:3: note: in expansion of macro ?PYSQLITE_CON_CALL? PYSQLITE_CON_CALL( ^ src/apsw.c: In function ?config?: src/apsw.c:354:10: error: ?SQLITE_CONFIG_PCACHE_HDRSZ? undeclared (first use in this function) case SQLITE_CONFIG_PCACHE_HDRSZ: ^ src/apsw.c:370:10: error: ?SQLITE_CONFIG_PMASZ? undeclared (first use in this fu nction) case SQLITE_CONFIG_PMASZ: ^ src/apsw.c:371:10: error: ?SQLITE_CONFIG_STMTJRNL_SPILL? undeclared (first use i n this function) case SQLITE_CONFIG_STMTJRNL_SPILL: ^ src/apsw.c: In function ?status?: src/apsw.c:549:3: warning: implicit declaration of function ?sqlite3_status64? [ -Wimplicit-function-declaration] res=sqlite3_status64(op, ¤t, &highwater, reset); ^ src/apsw.c: In function ?initapsw?: src/apsw.c:1409:14: error: ?SQLITE_RECURSIVE? undeclared (first use in this func tion) ADDINT(SQLITE_RECURSIVE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1420:14: error: ?SQLITE_INDEX_CONSTRAINT_LIKE? undeclared (first use in this function) ADDINT(SQLITE_INDEX_CONSTRAINT_LIKE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1421:14: error: ?SQLITE_INDEX_CONSTRAINT_REGEXP? undeclared (first us e in this function) ADDINT(SQLITE_INDEX_CONSTRAINT_REGEXP), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1422:14: error: ?SQLITE_INDEX_CONSTRAINT_GLOB? undeclared (first use in this function) ADDINT(SQLITE_INDEX_CONSTRAINT_GLOB), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1472:14: error: ?SQLITE_BUSY_SNAPSHOT? undeclared (first use in this function) ADDINT(SQLITE_BUSY_SNAPSHOT), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1473:14: error: ?SQLITE_IOERR_GETTEMPPATH? undeclared (first use in t his function) ADDINT(SQLITE_IOERR_GETTEMPPATH), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1474:14: error: ?SQLITE_WARNING_AUTOINDEX? undeclared (first use in t his function) ADDINT(SQLITE_WARNING_AUTOINDEX), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1475:14: error: ?SQLITE_CANTOPEN_CONVPATH? undeclared (first use in t his function) ADDINT(SQLITE_CANTOPEN_CONVPATH), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1476:14: error: ?SQLITE_IOERR_CONVPATH? undeclared (first use in this function) ADDINT(SQLITE_IOERR_CONVPATH), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1477:14: error: ?SQLITE_CONSTRAINT_ROWID? undeclared (first use in th is function) ADDINT(SQLITE_CONSTRAINT_ROWID), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1478:14: error: ?SQLITE_READONLY_DBMOVED? undeclared (first use in th is function) ADDINT(SQLITE_READONLY_DBMOVED), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1479:14: error: ?SQLITE_AUTH_USER? undeclared (first use in this func tion) ADDINT(SQLITE_AUTH_USER), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1480:14: error: ?SQLITE_IOERR_VNODE? undeclared (first use in this fu nction) ADDINT(SQLITE_IOERR_VNODE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1481:14: error: ?SQLITE_IOERR_AUTH? undeclared (first use in this fun ction) ADDINT(SQLITE_IOERR_AUTH), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1557:14: error: ?SQLITE_LIMIT_WORKER_THREADS? undeclared (first use i n this function) ADDINT(SQLITE_LIMIT_WORKER_THREADS), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1583:14: error: ?SQLITE_CONFIG_WIN32_HEAPSIZE? undeclared (first use in this function) ADDINT(SQLITE_CONFIG_WIN32_HEAPSIZE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1584:14: error: ?SQLITE_CONFIG_PCACHE_HDRSZ? undeclared (first use in this function) ADDINT(SQLITE_CONFIG_PCACHE_HDRSZ), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1585:14: error: ?SQLITE_CONFIG_PMASZ? undeclared (first use in this f unction) ADDINT(SQLITE_CONFIG_PMASZ), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1586:14: error: ?SQLITE_CONFIG_STMTJRNL_SPILL? undeclared (first use in this function) ADDINT(SQLITE_CONFIG_STMTJRNL_SPILL), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1593:14: error: ?SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER? undeclared (f irst use in this function) ADDINT(SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1594:14: error: ?SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION? undeclared (f irst use in this function) ADDINT(SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1622:14: error: ?SQLITE_DBSTATUS_DEFERRED_FKS? undeclared (first use in this function) ADDINT(SQLITE_DBSTATUS_DEFERRED_FKS), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1653:14: error: ?SQLITE_IOCAP_IMMUTABLE? undeclared (first use in thi s function) ADDINT(SQLITE_IOCAP_IMMUTABLE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1666:14: error: ?SQLITE_CHECKPOINT_TRUNCATE? undeclared (first use in this function) ADDINT(SQLITE_CHECKPOINT_TRUNCATE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1684:14: error: ?SQLITE_FCNTL_TRACE? undeclared (first use in this fu nction) ADDINT(SQLITE_FCNTL_TRACE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1685:14: error: ?SQLITE_FCNTL_COMMIT_PHASETWO? undeclared (first use in this function) ADDINT(SQLITE_FCNTL_COMMIT_PHASETWO), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1686:14: error: ?SQLITE_FCNTL_HAS_MOVED? undeclared (first use in thi s function) ADDINT(SQLITE_FCNTL_HAS_MOVED), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1687:14: error: ?SQLITE_FCNTL_SYNC? undeclared (first use in this fun ction) ADDINT(SQLITE_FCNTL_SYNC), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1688:14: error: ?SQLITE_FCNTL_WIN32_SET_HANDLE? undeclared (first use in this function) ADDINT(SQLITE_FCNTL_WIN32_SET_HANDLE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1689:14: error: ?SQLITE_FCNTL_LAST_ERRNO? undeclared (first use in th is function) ADDINT(SQLITE_FCNTL_LAST_ERRNO), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1690:14: error: ?SQLITE_FCNTL_WAL_BLOCK? undeclared (first use in thi s function) ADDINT(SQLITE_FCNTL_WAL_BLOCK), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1691:14: error: ?SQLITE_FCNTL_GET_LOCKPROXYFILE? undeclared (first us e in this function) ADDINT(SQLITE_FCNTL_GET_LOCKPROXYFILE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1692:14: error: ?SQLITE_FCNTL_SET_LOCKPROXYFILE? undeclared (first us e in this function) ADDINT(SQLITE_FCNTL_SET_LOCKPROXYFILE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1693:14: error: ?SQLITE_FCNTL_RBU? undeclared (first use in this func tion) ADDINT(SQLITE_FCNTL_RBU), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1694:14: error: ?SQLITE_FCNTL_ZIPVFS? undeclared (first use in this f unction) ADDINT(SQLITE_FCNTL_ZIPVFS), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1695:14: error: ?SQLITE_FCNTL_JOURNAL_POINTER? undeclared (first use in this function) ADDINT(SQLITE_FCNTL_JOURNAL_POINTER), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1696:14: error: ?SQLITE_FCNTL_VFS_POINTER? undeclared (first use in t his function) ADDINT(SQLITE_FCNTL_VFS_POINTER), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ src/apsw.c:1719:14: error: ?SQLITE_INDEX_SCAN_UNIQUE? undeclared (first use in t his function) ADDINT(SQLITE_INDEX_SCAN_UNIQUE), ^ src/apsw.c:1365:24: note: in definition of macro ?ADDINT? #define ADDINT(n) {#n, n} ^ error: command 'gcc' failed with exit status 1 -- 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: From fernando.lopezjr at gmail.com Thu Sep 1 21:09:34 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 1 Sep 2016 15:09:34 -0600 Subject: [Slackbuilds-users] radare2 update? In-Reply-To: <3830e9a3-bd59-1023-efca-1a11c0b1f2b7@slackbuilds.org> References: <3830e9a3-bd59-1023-efca-1a11c0b1f2b7@slackbuilds.org> Message-ID: awesome. thanks =) On Tue, Aug 30, 2016 at 4:10 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Is there any way we could update radare2 to latest 0.10.5 current in repo > > is 0.9.8. > > Since it's been almost 2 weeks and no response from the maintainer, you > may step up and take over maintainership of this package > > > -- > 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ts at websafe.pl Thu Sep 1 22:35:13 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Fri, 2 Sep 2016 00:35:13 +0200 Subject: [Slackbuilds-users] apsw for 14.1 - wrong DOWNLOAD url In-Reply-To: References: <783049df-af25-707b-939a-a7c1c561131f@websafe.pl> Message-ID: Of course this is not a critical issue and I'm able to handle it, I just wanted to let you know. -- 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: From Hedgehog87 at hotmail.it Fri Sep 2 13:27:10 2016 From: Hedgehog87 at hotmail.it (Cristiano Urban) Date: Fri, 2 Sep 2016 13:27:10 +0000 Subject: [Slackbuilds-users] A few issues with qgis Message-ID: Hi, is there anyone who has tried to install qgis recently? I tried to install it and I get a runtime error similar to this one when launching qgis. It seems I solved installing python-requests (as suggested). Cristiano. ___________________________________________ Site/blog @ http://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.coldplayer at gmail.com Fri Sep 2 17:53:48 2016 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Fri, 2 Sep 2016 21:53:48 +0400 Subject: [Slackbuilds-users] A few issues with qgis In-Reply-To: References: Message-ID: Even on slackware 14.1, it gives that error, I just ignore it. On 2 September 2016 at 17:27, Cristiano Urban wrote: > Hi, > > is there anyone who has tried to install qgis recently? > > I tried to install it and I get a runtime error similar to this one > > when launching qgis. > > It seems I solved installing python-requests (as suggested). > > > Cristiano. > ___________________________________________ > Site/blog @ http://crish4cks.net/ > Registered user #488179 @ http://linuxcounter.net > Slackware, because it works! =) > > _______________________________________________ > 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: From slackbuilds at jaxartes.net Fri Sep 2 19:35:18 2016 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Fri, 2 Sep 2016 12:35:18 -0700 Subject: [Slackbuilds-users] A few issues with qgis In-Reply-To: References: Message-ID: On 02/09/16 06:27 AM, Cristiano Urban wrote: > Hi, > > is there anyone who has tried to install qgis recently? > > I tried to install it and I get a runtime error similar to this one > > when launching qgis. > > It seems I solved installing python-requests (as suggested). H? Cristiano, You can disable the Metasearch plugin so that QGIS doesn't look for requests on start up. Each Python plugin has its own dependencies, so depending on which plugins are activated, a user might need more SlackBuilds installed than what the base QGIS requires. If users think that Metasearch is important (I've never used it), I could add python-requests to the REQUIRES for the QGIS SlackBuild. Best, Ben From Hedgehog87 at hotmail.it Fri Sep 2 19:49:28 2016 From: Hedgehog87 at hotmail.it (Cristiano Urban) Date: Fri, 2 Sep 2016 19:49:28 +0000 Subject: [Slackbuilds-users] A few issues with qgis In-Reply-To: References: , Message-ID: Clear, thank you for the explanation [?] Best regards, Cristiano. ___________________________________________ Site/blog @ http://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) ________________________________ Da: SlackBuilds-users per conto di Benjamin Trigona-Harany Inviato: venerd? 2 settembre 2016 21.35.18 A: SlackBuilds.org Users List Oggetto: Re: [Slackbuilds-users] A few issues with qgis On 02/09/16 06:27 AM, Cristiano Urban wrote: > Hi, > > is there anyone who has tried to install qgis recently? > > I tried to install it and I get a runtime error similar to this one > > when launching qgis. > > It seems I solved installing python-requests (as suggested). H? Cristiano, You can disable the Metasearch plugin so that QGIS doesn't look for requests on start up. Each Python plugin has its own dependencies, so depending on which plugins are activated, a user might need more SlackBuilds installed than what the base QGIS requires. If users think that Metasearch is important (I've never used it), I could add python-requests to the REQUIRES for the QGIS SlackBuild. Best, Ben _______________________________________________ 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: From willysr at slackbuilds.org Fri Sep 2 23:26:17 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 3 Sep 2016 06:26:17 +0700 Subject: [Slackbuilds-users] apsw for 14.1 - wrong DOWNLOAD url In-Reply-To: References: <783049df-af25-707b-939a-a7c1c561131f@websafe.pl> Message-ID: > Of course this is not a critical issue and I'm able > to handle it, I just wanted to let you know. I have pushed another public update on 14.1, but this is my last public update on 14.1. It will not be updated anymore in the future. -- 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: From willysr at slackbuilds.org Sat Sep 3 01:17:52 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 3 Sep 2016 08:17:52 +0700 Subject: [Slackbuilds-users] Updates - 20160903.1 Message-ID: <3278db7c-fbd8-1705-357c-2b8ef28449fe@slackbuilds.org> Sat Sep 3 00:50:31 UTC 2016 academic/irsim: Added (A digital circuit simulator). academic/magic: Added (A VLSI layout design tool). academic/pspp: Updated for version 0.10.2. accessibility/xdotool: Fix script. audio/mpd: Updated for version 0.19.19. audio/qmmp-plugin-pack: Updated for version 0.10.1. audio/quodlibet: Updated for version 3.7.0. business/stansoft: Updated for version 7.6. desktop/ceti-2-theme: Added (GTK2|GTK3 themes). desktop/i3pystatus: Updated for version 3.35. desktop/numix-gtk-theme: Removed (per maintainer request). desktop/numix-icon-theme-bevel: Updated for version 1.0.2014102123. desktop/numix-icon-theme-circle: Updated for version 2.0.3.7. desktop/numix-icon-theme: Updated for version 0.3.824.201608071940. desktop/numix-pack: Added (Icons, Themes, Wallpapers). desktop/qmmp-skins: Added (skins for Qmmp player). desktop/tint2: Update DOWNLOAD url. desktop/zuki-themes: Added (Themes for GTK, gnome-shell and more). development/SQLAlchemy: Updated for version 1.0.15. development/atom: Updated for version 1.10.0. development/cycler: Update DOWNLOAD url. development/meld3: Updated for version 3.16.2. development/nodejs: Update DOWNLOAD. development/npm2tgz: Switch to nodejs. development/qbs: Updated for version 1.6.0. development/qt-creator: Updated for version 4.1.0. development/radare2: Updated for version 0.10.5 + new maintainer. development/sphinx_rtd_theme: Update dep. development/uz80as: Updated for version 1.02. games/SLADE: Updated for version 3.1.1.3. games/mednafen: Updated for version 0.9.39.1. games/pioneer: Updated for version 20160814. games/yabause: Updated for version 0.9.15 gis/google-earth: Updated for version 7.1.7.2600. gis/libLAS: Added (C/C++ library for the LAS LiDAR format). libraries/IMAPClient: Updated for version 0.13. libraries/SDL2_mixer: Fixed libmodplug support. libraries/botocore: Updated for version 1.4.51. libraries/matplotlib: Update DOWNLOAD url. libraries/mini18n: Updated for version 0.2.1 libraries/webkit2gtk: Updated for version 2.12.4. misc/moreutils: Updated for version 0.60. misc/nixnote: Fix build and update dep. misc/subsurface: Remove unused patch multimedia/ffmpeg2theora: Updated for version 0.30. network/PAC: Update REQUIRES. network/aggregate: Switch to i586. network/aria2: Updated for version 1.26.1. network/awscli: Updated for version 1.10.61. network/dropbox: Updated for version 8.4.21. network/etherpad-lite: Switch to nodejs. network/flexget: Updated for version 2.3.13. network/gmvault: Added (gmail backup-restore tool). network/google-cli: Updated for version 2.7. network/ike: Fixed SlackBuild. network/iojs: Update README. network/iperf3: Added (bandwidth measurement tool). network/keybase-client: Switch to nodejs. network/mailman: Updated for version 2.1.23. network/node: Removed (replaced by nodejs). network/ssmtp: Update script. network/youtube-dl: Updated for version 2016.08.28. office/MasterPDFEditor: Switch to i586. office/calibre: Updated for version 2.66.0 perl/Net-SSLeay: Updated for version 1.78. perl/perl-Capture-Tiny: Updated for version 0.44. perl/perl-Class-Method-Modifiers: Updated for version 2.12. perl/perl-Data-Random: Update script and email. perl/perl-Date-Manip: Updated for version 6.54. perl/perl-IO-Socket-SSL: Updated for version 2.037. perl/perl-Moo: Updated for version 2.002004. perl/perl-Role-Tiny: Updated for version 2.000003. python/Flask-Cors: Updated for version 3.0.1. python/Logbook: Added (A logging replacement for Python). python/buildbot: Added (automated compile/test cycle). python/lxml: Updated for version 3.6.4 python/monty: Updated for version 0.9.1. python/msgpack-python: Updated for version 0.4.8. python/pendulum: Added (Python datetimes made easy). python/ply: Updated for version 3.9. python/poster: Added (streaming HTTP uploads). python/pytest: Updated for version 3.0.1. python/python-certifi: Updated for version 2016.8.31. python/python-gflags: Updated for version 3.0.6. python/python-requests: Updated for version 2.11.1. python/python-scandir: Updated for version 1.3. python/regex: Updated for version 2016.08.27. python/s3transfer: Updated for version 0.1.3. python/sqlparse: Added (SQL parser for Python). python/waitress: Updated for version 1.0.0. system/MySQL-Sandbox: Updated for version 3.1.13. system/borgbackup: Updated for version 1.0.7. system/dymo-cups-drivers: Moved from office + update script. system/fsarchiver: Updated for version 0.8.0. system/keybase: Updated for version 1.0.17. system/nvidia-driver: Updated for version 367.44. system/nvidia-kernel: Updated for version 367.44. system/salt: Added (configuration management engine). system/ttf-zekton: Added (True Type Font). system/veracrypt: Added (free disk encryption software). system/wine-staging: Updated for version 1.9.17. system/xonsh: Updated for version 0.4.6. system/zstd: Updated for version 1.0.0. system/zuluCrypt: Updated for version 5.0.1. +--------------------------+ -- 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: From kjhambrick at gmail.com Sat Sep 3 08:06:03 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 3 Sep 2016 03:06:03 -0500 Subject: [Slackbuilds-users] cfitsio version update 3.37 -> 3.39 Message-ID: All -- The official SBo Version of libraries/cfitsio/ is 3.37. The Program was recently updated to version 3.39 ( including a critical update in 3.38 ). I've built and installed version 3.39 on Slackware64 14.2 + Multilib. Works just fine in place of the official Version 3.37 Attached are diffs on the files in the original (SBo) libraries/cfitsio/ vs (my) ~/cfitsio3390/ Note that I couldn't find an md5sum on the HOMEPAGE so made up the MD5SUM locally :) Thanks for all you do ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- diff -Naur cfitsio/cfitsio.SlackBuild cfitsio-3390/cfitsio.SlackBuild --- cfitsio/cfitsio.SlackBuild 2016-05-28 04:46:38.395637507 -0500 +++ cfitsio-3390/cfitsio.SlackBuild 2016-05-29 04:32:20.962749796 -0500 @@ -4,11 +4,11 @@ # Written by Dominik Drobek PRGNAM=cfitsio -VERSION=${VERSION:-3.37} +VERSION=${VERSION:-3.39} # kjh was here BUILD=${BUILD:-1} TAG=${TAG:-_SBo} -FVER=3370 +FVER=3390 # kjh was here if [ -z "$ARCH" ]; then case "$( uname -m )" in diff -Naur cfitsio/cfitsio.info cfitsio-3390/cfitsio.info --- cfitsio/cfitsio.info 2016-05-28 04:46:38.395637507 -0500 +++ cfitsio-3390/cfitsio.info 2016-09-03 02:48:14.425079006 -0500 @@ -1,8 +1,8 @@ PRGNAM="cfitsio" -VERSION="3.37" +VERSION="3.39" HOMEPAGE="http://heasarc.gsfc.nasa.gov/fitsio/" -DOWNLOAD="ftp://heasarc.gsfc.nasa.gov/software/fitsio/c/cfitsio3370.tar.gz" -MD5SUM="abebd2d02ba5b0503c633581e3bfa116" +DOWNLOAD="http://heasarc.gsfc.nasa.gov/FTP/software/fitsio/c/cfitsio3390.tar.gz" +MD5SUM="e92dd2a4282a1c50d46167041a29fc67" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" From kjhambrick at gmail.com Sat Sep 3 08:34:18 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 3 Sep 2016 03:34:18 -0500 Subject: [Slackbuilds-users] hdf5 v 1.8.17 is available Message-ID: All -- HDF5 Version 1.8.17 ( latest official release of HDF5 ) is available. I've built and installed hdf5-1.8.17.tar.bz2 from https://www.hdfgroup.org/ and it works fine in place of 1.8.15_patch1 on my Slackware64 14.2 + Multilib System Attached are diffs on the files in the official SBo libraries/hdf5/ directory vs files on my local hdf5-1.8.17/ Note that while hdf-1.10.0-patch1 is available, the website says: HDF5-1.8.17 is the latest official release of HDF5. This page lists the > platforms and compilers tested with HDF5-1.8.17. > Thanks for all you do ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- diff -Naur hdf5/hdf5.SlackBuild hdf5-1.8.17/hdf5.SlackBuild --- hdf5/hdf5.SlackBuild 2016-05-28 04:46:38.408637508 -0500 +++ hdf5-1.8.17/hdf5.SlackBuild 2016-05-29 05:00:23.933909398 -0500 @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=hdf5 -VERSION=${VERSION:-1.8.15_patch1} +VERSION=${VERSION:-1.8.17} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} diff -Naur hdf5/hdf5.info hdf5-1.8.17/hdf5.info --- hdf5/hdf5.info 2016-05-28 04:46:38.408637508 -0500 +++ hdf5-1.8.17/hdf5.info 2016-05-29 05:00:00.877907212 -0500 @@ -1,8 +1,8 @@ PRGNAM="hdf5" -VERSION="1.8.15_patch1" +VERSION="1.8.17" HOMEPAGE="https://www.hdfgroup.org/" -DOWNLOAD="http://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.15-patch1/src/hdf5-1.8.15-patch1.tar.bz2" -MD5SUM="3c0d7a8c38d1abc7b40fc12c1d5f2bb8" +DOWNLOAD="http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.17.tar.bz2" +MD5SUM="34bd1afa5209259201a41964100d6203" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" From kingbeowulf at gmail.com Sat Sep 3 19:41:42 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 3 Sep 2016 12:41:42 -0700 Subject: [Slackbuilds-users] Upload error Message-ID: <0d4fbdec-da5e-9ecb-e602-2a7da7852e3f@gmail.com> FYI for admins This error Notice: Undefined index: userfile in /slackbuilds/www/includes/process_submit.inc.php on line 12 No file uploaded. Please select a file to upload and try again. is a bit vague. Yes, every so often I forget to strip the source binary from the upload so maybe a message related to that issue? 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: From willysr at slackbuilds.org Sun Sep 4 01:39:08 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 4 Sep 2016 08:39:08 +0700 Subject: [Slackbuilds-users] Upload error In-Reply-To: <0d4fbdec-da5e-9ecb-e602-2a7da7852e3f@gmail.com> References: <0d4fbdec-da5e-9ecb-e602-2a7da7852e3f@gmail.com> Message-ID: > FYI for admins > > This error > > Notice: Undefined index: userfile in > /slackbuilds/www/includes/process_submit.inc.php on line 12 No file > uploaded. Please select a file to upload and try again. > > is a bit vague. Yes, every so often I forget to strip the source binary > from the upload so maybe a message related to that issue? Hi, that error was caused by an empty file or non-existent file submitted via the submission form. -- 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: From kingbeowulf at gmail.com Sun Sep 4 03:20:02 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 3 Sep 2016 20:20:02 -0700 Subject: [Slackbuilds-users] Upload error In-Reply-To: References: <0d4fbdec-da5e-9ecb-e602-2a7da7852e3f@gmail.com> Message-ID: Well, that's what I thought but it happened again. Then I noticed the file size (MB) The KB tar.gz uploaded ok. Could be a glitch with my ISP I suppose... On Saturday, September 3, 2016, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > FYI for admins > > > > This error > > > > Notice: Undefined index: userfile in > > /slackbuilds/www/includes/process_submit.inc.php on line 12 No file > > uploaded. Please select a file to upload and try again. > > > > is a bit vague. Yes, every so often I forget to strip the source binary > > from the upload so maybe a message related to that issue? > > Hi, > > that error was caused by an empty file or non-existent file submitted > via the submission form. > > -- > Willy Sudiarto Raharjo > > -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedoogster at gmail.com Mon Sep 5 20:46:58 2016 From: thedoogster at gmail.com (Doogster) Date: Mon, 5 Sep 2016 13:46:58 -0700 Subject: [Slackbuilds-users] fmodapi access upstream Message-ID: The FMOD Ex API downloads are now closed to the public. In order to even download them, you need to register on their site and then email them asking for access. I did that, and I now I have a 4.44.63 tarball that I can enjoy for personal use. I looked at the license I got with it, and it said that if I want to redistribute it, then I need to send them a second email and ask for a license to do that. Now, I could do that, but I'm not an SBo admin and I'm not the fmodapi maintainer, so it wouldn't help SBo much if I did. May I suggest that an SBo admin procures a license (I'm sure they're free) on behalf of SBo? Note: Brutal DOOM needs GZDoom to be built with FMOD support and set up to use the FMOD sound backend. Reference: http://forum.drdteam.org/viewtopic.php?t=6801 From erik at slackbuilds.org Mon Sep 5 21:21:49 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 5 Sep 2016 16:21:49 -0500 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: <20160905162149.748fc5f9@shaggy.doo> On Mon, 5 Sep 2016 13:46:58 -0700 Doogster wrote: > The FMOD Ex API downloads are now closed to the public. In order to > even download them, you need to register on their site and then email > them asking for access. I did that, and I now I have a 4.44.63 tarball > that I can enjoy for personal use. I looked at the license I got with > it, and it said that if I want to redistribute it, then I need to send > them a second email and ask for a license to do that. > > Now, I could do that, but I'm not an SBo admin and I'm not the fmodapi > maintainer, so it wouldn't help SBo much if I did. May I suggest that > an SBo admin procures a license (I'm sure they're free) on behalf of > SBo? We don't host sources at all, so I think it would be inappropriate for an admin to ask for a license on behalf of SBo. This should be done by the maintainer, maybe in conjunction with someone that runs one of the 'sbo sources' mirrors. -- Erik From yalhcru at gmail.com Mon Sep 5 22:24:22 2016 From: yalhcru at gmail.com (B Watson) Date: Mon, 5 Sep 2016 18:24:22 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: I'm not the fmodapi maintainer, but I'm the gzdoom maintainer... On 9/5/16, Doogster wrote: > The FMOD Ex API downloads are now closed to the public. In order to > even download them, you need to register on their site and then email The download URLs in the .info file are: http://ponce.cc/slackware/sources/repo/fmodapi42817linux.tar.gz http://ponce.cc/slackware/sources/repo/fmodapi42817linux64.tar.gz So we already aren't downloading them from upstream's site. Looking at fmodapi42817linux64/documentation/LICENSE.TXT... My reading of that version of the license is that it doesn't actually say anything about redistributing the source to the library. It only talks about 'products' that incorporate the library, which I take to mean binaries, but I'm DEFINITELY not a lawyer! The lower portion of it (after 'Uses Ogg Vorbis codec') is the ogg vorbis license, not the fmodapi one. Either that license allows redistributing the source, or someone's been violating it for years now with no consequence. I'd say nothing needs to be changed. > Note: Brutal DOOM needs GZDoom to be built with FMOD support and set > up to use the FMOD sound backend. Does it work with the version of fmodapi on SBo, 4.28.17? I know gzdoom itself does... ...though the latest version of gzdoom actually can be built without fmodapi (the older versions couldn't). I was considering removing fmodapi from the REQUIRES (in fact I'm pretty sure you, Doogster, were the one who pointed out that it's no longer required). If I do, I'll add a note to gzdoom's README stating "If you want to play the Brutal Doom mod, you'll have to build gzdoom with fmodapi" or such. Or I could leave it in REQUIRES, if it turns out that Brutal Doom is so popular that almost everyone using gzdoom is using it for Brutal Doom...? The 'correct' fix for this would be for the Brutal Doom authors/maintainers to fix their mod so it works without fmodapi. I have no idea how feasible that would be (maybe there are technical or political reason why they don't want to do it). From thedoogster at gmail.com Tue Sep 6 00:05:42 2016 From: thedoogster at gmail.com (Doogster) Date: Mon, 5 Sep 2016 17:05:42 -0700 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On Mon, Sep 5, 2016 at 3:24 PM, B Watson wrote: > The 'correct' fix for this would be for the Brutal Doom > authors/maintainers to fix their mod so it works without fmodapi. I > have no idea how feasible that would be (maybe there are technical or > political reason why they don't want to do it). Technical. 3D positional audio works properly with FMOD Ex but not with OpenAL. OpenAL plays all the sounds at full volume. FMOD Ex fades them based on your position as it should. What the Brutal DOOM documentation says about this is: "If you are hearing a lot of sounds from unknown sources from large distances, such as blood driping from hanged bodies and burning barrels making cracking fire noises across the map, you need to reinstall your sourceport." I suspect that the fix would actually need to be in gzdoom, not Brutal DOOM. From yalhcru at gmail.com Tue Sep 6 03:14:13 2016 From: yalhcru at gmail.com (B Watson) Date: Mon, 5 Sep 2016 23:14:13 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On 9/5/16, Doogster wrote: > > What the Brutal DOOM documentation says about this is: "If you are > hearing a lot of sounds from unknown sources from large distances, > such as blood driping from hanged bodies and burning barrels making > cracking fire noises across the map, you need to reinstall your > sourceport." Interesting... I only ever play regular Doom II (with random maps made by oblige) and I never notice this behaviour. But, I'm not using headphones, and my speakers tend to be turned down pretty low. > I suspect that the fix would actually need to be in gzdoom, not Brutal > DOOM. Well, if it's a thing that only happens in Brutal Doom, not in plain Doom/DoomII or other mods... Weird that it's using fmodapi for digital audio. I would have thought fmod would only be for background music, and that the actual game sounds would be played by the game engine (using OpenAL or just SDL audio). From thedoogster at gmail.com Tue Sep 6 04:13:14 2016 From: thedoogster at gmail.com (Doogster) Date: Mon, 5 Sep 2016 21:13:14 -0700 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: B Watson: If you don't have any issues with distributing the FMOD API source, then you might consider treating the tarball as part of gzdoom's source and just untarring the fmod tarball into gzdoom's source directory before building gzdoom. That will ensure that gzdoom is built with the latest version of FMOD that it was tested with. There's a comment about that build method here: https://github.com/coelckers/gzdoom/blob/master/src/CMakeLists.txt#L42 On Mon, Sep 5, 2016 at 8:14 PM, B Watson wrote: > On 9/5/16, Doogster wrote: >> >> What the Brutal DOOM documentation says about this is: "If you are >> hearing a lot of sounds from unknown sources from large distances, >> such as blood driping from hanged bodies and burning barrels making >> cracking fire noises across the map, you need to reinstall your >> sourceport." > > Interesting... I only ever play regular Doom II (with random maps made by > oblige) and I never notice this behaviour. But, I'm not using headphones, > and my speakers tend to be turned down pretty low. > >> I suspect that the fix would actually need to be in gzdoom, not Brutal >> DOOM. > > Well, if it's a thing that only happens in Brutal Doom, not in plain > Doom/DoomII or other mods... > > Weird that it's using fmodapi for digital audio. I would have thought > fmod would only be for background music, and that the actual game sounds > would be played by the game engine (using OpenAL or just SDL audio). > _______________________________________________ > 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 yalhcru at gmail.com Tue Sep 6 04:27:46 2016 From: yalhcru at gmail.com (B Watson) Date: Tue, 6 Sep 2016 00:27:46 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On 9/6/16, Doogster wrote: > B Watson: If you don't have any issues with distributing the FMOD API > source, then you might consider treating the tarball as part of > gzdoom's source and just untarring the fmod tarball into gzdoom's > source directory before building gzdoom. That will ensure that gzdoom > is built with the latest version of FMOD that it was tested with. You never answered my previous question... does the older fmodapi version we have on SBo actually cause problems with anything (gzdoom itself or Brutal Doom or whatever)? Problems that would be fixed by the latest version of fmodapi? Also, I might have issues with redistributing the latest fmodapi version, depending on what its LICENSE.TXT actually says. The one I was commenting on earlier is the one from the older fmodapi version we have on SBo. *That* version, I don't have issues redistributing (I believe it's OK according to the license. I still might be wrong of course) From thedoogster at gmail.com Tue Sep 6 04:34:09 2016 From: thedoogster at gmail.com (Doogster) Date: Mon, 5 Sep 2016 21:34:09 -0700 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: Aah, I missed that question. When GZDOOM 2.1.1 was built against the older FMOD Ex on SBo, it was segfaulting for me. A Google search told me that the Windows builds were having similar issues until Graf Zahl built it against a newer version of FMOD Ex. On Mon, Sep 5, 2016 at 9:27 PM, B Watson wrote: > On 9/6/16, Doogster wrote: >> B Watson: If you don't have any issues with distributing the FMOD API >> source, then you might consider treating the tarball as part of >> gzdoom's source and just untarring the fmod tarball into gzdoom's >> source directory before building gzdoom. That will ensure that gzdoom >> is built with the latest version of FMOD that it was tested with. > > You never answered my previous question... does the older fmodapi version > we have on SBo actually cause problems with anything (gzdoom itself or > Brutal Doom or whatever)? Problems that would be fixed by the latest > version of fmodapi? > > Also, I might have issues with redistributing the latest fmodapi version, > depending on what its LICENSE.TXT actually says. The one I was commenting > on earlier is the one from the older fmodapi version we have on SBo. *That* > version, I don't have issues redistributing (I believe it's OK according to > the license. I still might be wrong of course) > _______________________________________________ > 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 yalhcru at gmail.com Tue Sep 6 05:56:19 2016 From: yalhcru at gmail.com (B Watson) Date: Tue, 6 Sep 2016 01:56:19 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On 9/6/16, Doogster wrote: > Aah, I missed that question. > > When GZDOOM 2.1.1 was built against the older FMOD Ex on SBo, it was > segfaulting for me. A Google search told me that the Windows builds > were having similar issues until Graf Zahl built it against a newer > version of FMOD Ex. Oh, OK. So one way to fix the segfault is to build without fmodapi, but if you do that, brutal doom (and maybe some other mods?) won't work, is that about right? From thedoogster at gmail.com Tue Sep 6 06:50:53 2016 From: thedoogster at gmail.com (Doogster) Date: Mon, 5 Sep 2016 23:50:53 -0700 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: Yes. Well, you don' get the segfaults if you build against the older fmod and then don't use it (set the sound backend to OpenAL). Other than that: yes, exactly. On Monday, 5 September 2016, B Watson wrote: > On 9/6/16, Doogster > wrote: > > Aah, I missed that question. > > > > When GZDOOM 2.1.1 was built against the older FMOD Ex on SBo, it was > > segfaulting for me. A Google search told me that the Windows builds > > were having similar issues until Graf Zahl built it against a newer > > version of FMOD Ex. > > Oh, OK. > > So one way to fix the segfault is to build without fmodapi, but if you > do that, brutal doom (and maybe some other mods?) won't work, is that > about right? > _______________________________________________ > 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: From yalhcru at gmail.com Tue Sep 6 14:44:06 2016 From: yalhcru at gmail.com (B Watson) Date: Tue, 6 Sep 2016 10:44:06 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On 9/6/16, Doogster wrote: > Yes. > > Well, you don' get the segfaults if you build against the older fmod and > then don't use it (set the sound backend to OpenAL). Other than that: yes, > exactly. But if you set the backend to OpenAL, brutal doom stops working correctly? Does this only happen with 2.1.1? I went to some effort to make sure my slackbuild can still build the 1.8.x and 1.9.x branches of gzdoom, since upstream is developing all 3 branches in parallel (well, maybe 1.8.x is done now). See: https://slackbuilds.org/slackbuilds/14.2/games/gzdoom/README_versions.txt Particularly this bit: 1.8.09 - last version to use SDL1 (good for older/slower systems). 1.9.1 - last version to not require OpenGL 3.0 (good for nouveau). 2.2.1 - latest version of gzdoom (best choice for fast modern systems). 2.2.1 will run on my box, but it's got noticeably worse performance than either 1.8.09 or 1.9.1, so I don't actually use it (tested it by playing through the first 2 levels of Doom II, which worked). From thedoogster at gmail.com Tue Sep 6 16:13:45 2016 From: thedoogster at gmail.com (Doogster) Date: Tue, 6 Sep 2016 09:13:45 -0700 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: > But if you set the backend to OpenAL, brutal doom stops working correctly? Yes > Does this only happen with 2.1.1? I don't know. 2.1.1 is the one I use. If you want to do your own tests, load both Brutal DOOM and Back to Saturn X Episode 1. You can hear the difference in the first level. Back to Saturn X Episode 1 (including download link): https://www.doomworld.com/vb/thread/62529 From sbo-usxx.sender.grmblfjx at spamgourmet.com Tue Sep 6 20:51:41 2016 From: sbo-usxx.sender.grmblfjx at spamgourmet.com (sbo-usxx.sender.grmblfjx at spamgourmet.com) Date: Tue, 06 Sep 2016 22:51:41 +0200 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: Hi, this may be relevant: http://zdoom.org/wiki/Compile_GZDoom_on_Linux#FMOD_Links (Sorry for messing up the threading, I'm a digest reader.) From yalhcru at gmail.com Wed Sep 7 05:09:01 2016 From: yalhcru at gmail.com (B Watson) Date: Wed, 7 Sep 2016 01:09:01 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On 9/6/16, sbo-usxx.sender.grmblfjx at spamgourmet.com wrote: > Hi, this may be relevant: > http://zdoom.org/wiki/Compile_GZDoom_on_Linux#FMOD_Links Those links for fmod are actually for an even older version than the old one that's on SBo... Unless you're saying that version is the one gzdoom is actually developed/tested with? From matteo.bernardini at gmail.com Wed Sep 7 07:48:16 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 7 Sep 2016 09:48:16 +0200 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: 2016-09-07 7:09 GMT+02:00 B Watson : > On 9/6/16, sbo-usxx.sender.grmblfjx at spamgourmet.com > wrote: > >> Hi, this may be relevant: >> http://zdoom.org/wiki/Compile_GZDoom_on_Linux#FMOD_Links > > Those links for fmod are actually for an even older version than the > old one that's on SBo... > > Unless you're saying that version is the one gzdoom is actually > developed/tested with? I tried to do a version bump to the one noted in that wiki page: can you please test if you still got segfaults with this installed? http://ponce.cc/slackware/testing/fmodapi/ should be safe to host this as when they released it, AFAIK, they haven't changed their license yet. Matteo From thedoogster at gmail.com Wed Sep 7 14:19:00 2016 From: thedoogster at gmail.com (Doogster) Date: Wed, 7 Sep 2016 07:19:00 -0700 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: GZDoom's CMake file didn't detect it. The latest version of fmodapi that GZDoom's build system will detect (including in the latest development version) is 44450. To get it to build against later versions requires patching GZDoom. Specifically, you need to add the minor version here: https://github.com/coelckers/gzdoom/blob/g2.1.1/src/CMakeLists.txt#L53 FWIW, this is what I use for my personal builds: https://github.com/duganchen/my_slackbuilds/blob/master/gzdoom/gzdoom.SlackBuild I just do my own builds against 44450 and I don't get segfaults. On Wed, Sep 7, 2016 at 12:48 AM, Matteo Bernardini wrote: > 2016-09-07 7:09 GMT+02:00 B Watson : >> On 9/6/16, sbo-usxx.sender.grmblfjx at spamgourmet.com >> wrote: >> >>> Hi, this may be relevant: >>> http://zdoom.org/wiki/Compile_GZDoom_on_Linux#FMOD_Links >> >> Those links for fmod are actually for an even older version than the >> old one that's on SBo... >> >> Unless you're saying that version is the one gzdoom is actually >> developed/tested with? > > I tried to do a version bump to the one noted in that wiki page: can > you please test if you still got segfaults with this installed? > > http://ponce.cc/slackware/testing/fmodapi/ > > should be safe to host this as when they released it, AFAIK, they > haven't changed their license yet. > > 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 matteo.bernardini at gmail.com Wed Sep 7 14:38:55 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 7 Sep 2016 16:38:55 +0200 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: 2016-09-07 16:19 GMT+02:00 Doogster : > GZDoom's CMake file didn't detect it. > > The latest version of fmodapi that GZDoom's build system will detect > (including in the latest development version) is 44450. To get it to > build against later versions requires patching GZDoom. Specifically, > you need to add the minor version here: > > https://github.com/coelckers/gzdoom/blob/g2.1.1/src/CMakeLists.txt#L53 > > FWIW, this is what I use for my personal builds: > > https://github.com/duganchen/my_slackbuilds/blob/master/gzdoom/gzdoom.SlackBuild > > I just do my own builds against 44450 and I don't get segfaults. > > On Wed, Sep 7, 2016 at 12:48 AM, Matteo Bernardini > wrote: >> 2016-09-07 7:09 GMT+02:00 B Watson : >>> On 9/6/16, sbo-usxx.sender.grmblfjx at spamgourmet.com >>> wrote: >>> >>>> Hi, this may be relevant: >>>> http://zdoom.org/wiki/Compile_GZDoom_on_Linux#FMOD_Links >>> >>> Those links for fmod are actually for an even older version than the >>> old one that's on SBo... >>> >>> Unless you're saying that version is the one gzdoom is actually >>> developed/tested with? >> >> I tried to do a version bump to the one noted in that wiki page: can >> you please test if you still got segfaults with this installed? >> >> http://ponce.cc/slackware/testing/fmodapi/ >> >> should be safe to host this as when they released it, AFAIK, they >> haven't changed their license yet. the SlackBuild I modified could be used just changing $VERSION also with 4.44.50. as this is a prior version respect 4.44.61, the one noted in the gzdoom wiki page by its developers and previously avalaible on the fmod website without any registration, should be fine to redistribute as well. I'll placed it in the same place as that version http://ponce.cc/slackware/sources/repo/fmodapi44450linux.tar.gz IMHO, the maintainers of what depends on it (Ben, Pablo and Dimitris) decide which one is compatible with their stuff and they think more appropriate ;) Matteo From yalhcru at gmail.com Wed Sep 7 19:30:43 2016 From: yalhcru at gmail.com (B Watson) Date: Wed, 7 Sep 2016 15:30:43 -0400 Subject: [Slackbuilds-users] Fwd: fmodapi access upstream In-Reply-To: References: Message-ID: On 9/7/16, Matteo Bernardini wrote: > IMHO, the maintainers of what depends on it (Ben, Pablo and Dimitris) > decide which one is compatible with their stuff and they think more > appropriate ;) My name's not actually Ben, but it's a pretty good guess :) If it turns out that version of fmodapi fixes gzdoom segfaulting, but causes problems with other builds, I have no problem including that version of fmodapi as part of the gzdoom build and making sure it doesn't conflict with the fmodapi from the actual fmodapi build. Questions for Doogster: Are the segfaults in gzdoom and the badly-behaved audio in gzdoom+brutaldoom two separate issues? Is there a reliable way to trigger the segfault? Does it happen with regular Doom II or only with Brutal? From thedoogster at gmail.com Wed Sep 7 19:34:03 2016 From: thedoogster at gmail.com (Doogster) Date: Wed, 7 Sep 2016 12:34:03 -0700 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: IIRC, the segfaults happened with regular DOOM. A reliable way to trigger them was to set the sound backend to FMOD and FMOD's backend to Pulseaudio, restart the sound system (that's a menu option), then start a game. On Wednesday, 7 September 2016, B Watson wrote: > On 9/7/16, Matteo Bernardini > > wrote: > > > IMHO, the maintainers of what depends on it (Ben, Pablo and Dimitris) > > decide which one is compatible with their stuff and they think more > > appropriate ;) > > My name's not actually Ben, but it's a pretty good guess :) > > If it turns out that version of fmodapi fixes gzdoom segfaulting, > but causes problems with other builds, I have no problem including that > version of fmodapi as part of the gzdoom build and making sure it doesn't > conflict with the fmodapi from the actual fmodapi build. > > Questions for Doogster: Are the segfaults in gzdoom and the badly-behaved > audio in gzdoom+brutaldoom two separate issues? Is there a reliable way > to trigger the segfault? Does it happen with regular Doom II or only > with Brutal? > _______________________________________________ > 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: From thedoogster at gmail.com Wed Sep 7 19:35:33 2016 From: thedoogster at gmail.com (Doogster) Date: Wed, 7 Sep 2016 12:35:33 -0700 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: The segfaults and the badly behaved audio are separate issues. On Wednesday, 7 September 2016, B Watson wrote: > On 9/7/16, Matteo Bernardini > > wrote: > > > IMHO, the maintainers of what depends on it (Ben, Pablo and Dimitris) > > decide which one is compatible with their stuff and they think more > > appropriate ;) > > My name's not actually Ben, but it's a pretty good guess :) > > If it turns out that version of fmodapi fixes gzdoom segfaulting, > but causes problems with other builds, I have no problem including that > version of fmodapi as part of the gzdoom build and making sure it doesn't > conflict with the fmodapi from the actual fmodapi build. > > Questions for Doogster: Are the segfaults in gzdoom and the badly-behaved > audio in gzdoom+brutaldoom two separate issues? Is there a reliable way > to trigger the segfault? Does it happen with regular Doom II or only > with Brutal? > _______________________________________________ > 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: From yalhcru at gmail.com Wed Sep 7 20:36:54 2016 From: yalhcru at gmail.com (B Watson) Date: Wed, 7 Sep 2016 16:36:54 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On 9/7/16, Doogster wrote: > IIRC, the segfaults happened with regular DOOM. A reliable way to trigger > them was to set the sound backend to FMOD and FMOD's backend to Pulseaudio, > restart the sound system (that's a menu option), then start a game. Thanks, that'll help. Should have some time to take a look at this later on tonight. From bryanlharris at gmail.com Thu Sep 8 14:41:43 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Thu, 8 Sep 2016 10:41:43 -0400 Subject: [Slackbuilds-users] pcsc-tools Message-ID: Hi folks, It looks like the pcsc-tools source URL has become invalidated. Can this SBo get an update for the new version and new URL? To make it work all I did was to update of the version and the md5sum. Since I don't know how to tell git to make a file, so I just copy/pasted it from the git diff from putty. diff --git a/system/pcsc-tools/pcsc-tools.SlackBuild b/system/pcsc-tools/pcsc-tools.SlackBuild old mode 100644 new mode 100755 index 9d79700..0179573 --- a/system/pcsc-tools/pcsc-tools.SlackBuild +++ b/system/pcsc-tools/pcsc-tools.SlackBuild @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=pcsc-tools -VERSION=${VERSION:-1.4.25} +VERSION=${VERSION:-1.4.27} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} diff --git a/system/pcsc-tools/pcsc-tools.info b/system/pcsc-tools/ pcsc-tools.info index 90334ad..4d34af5 100644 --- a/system/pcsc-tools/pcsc-tools.info +++ b/system/pcsc-tools/pcsc-tools.info @@ -1,8 +1,8 @@ PRGNAM="pcsc-tools" VERSION="1.4.25" HOMEPAGE="http://ludovic.rousseau.free.fr/softwares/pcsc-tools/" -DOWNLOAD=" http://ludovic.rousseau.free.fr/softwares/pcsc-tools/pcsc-tools-1.4.25.tar.gz " -MD5SUM="befc40d4513daec5813ee317cb382acf" +DOWNLOAD=" http://ludovic.rousseau.free.fr/softwares/pcsc-tools/pcsc-tools-1.4.27.tar.gz " +MD5SUM="8ed881400d89f89cba13e4d70f524fb3" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="pcsc-perl perl-gtk2" V/r, Bryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Thu Sep 8 21:00:35 2016 From: dickson.tim at googlemail.com (Tim Dickson) Date: Thu, 8 Sep 2016 22:00:35 +0100 Subject: [Slackbuilds-users] what is the preferred build and test environment Message-ID: Hi everyone, I use sbopkg for building packages, but for my own slackbuilds I need to test them on both 32bit and 64bit slackware. Ideally, they would be clean installs, with just the dependencies required for the build to be tested. I would like to do this with minimum of fuss, and wondered what you guys (and gals) did ?? Up till now, I have used 2 separate test machines, or one machine with two slackware installations on different partitions, but I haven't managed a clean starting state for each slackbuild. I have somewhat limited internet data allowance, so don't want to re-download the sbo tree for every slackbuild when building dependencies. I made limited use of qemu on windows to run some slackware vm's a while ago, but prefer solely using linux for testing. any simple examples or a howto or wiki would be appreciated, and probably useful to all slackbuild creators. Thanks, Tim PS. some builds are for graphical programs that use opengl, I don't know if that affects the choice of environment or not. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Thu Sep 8 21:06:39 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 8 Sep 2016 15:06:39 -0600 Subject: [Slackbuilds-users] what is the preferred build and test environment In-Reply-To: References: Message-ID: use virtualbox there is an option to revert back any changes. On Thu, Sep 8, 2016 at 3:00 PM, Tim Dickson wrote: > Hi everyone, I use sbopkg for building packages, but for my own > slackbuilds I need to test them on both 32bit and 64bit slackware. Ideally, > they would be clean installs, with just the dependencies required for the > build to be tested. I would like to do this with minimum of fuss, and > wondered what you guys (and gals) did ?? > Up till now, I have used 2 separate test machines, or one machine with two > slackware installations on different partitions, but I haven't managed a > clean starting state for each slackbuild. I have somewhat limited internet > data allowance, so don't want to re-download the sbo tree for every > slackbuild when building dependencies. I made limited use of qemu on > windows to run some slackware vm's a while ago, but prefer solely using > linux for testing. > any simple examples or a howto or wiki would be appreciated, and probably > useful to all slackbuild creators. > Thanks, Tim > > PS. some builds are for graphical programs that use opengl, I don't know > if that affects the choice of environment or not. > > _______________________________________________ > 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dpross1100 at msn.com Thu Sep 8 23:03:37 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Thu, 8 Sep 2016 23:03:37 +0000 Subject: [Slackbuilds-users] Being upstream and maintainer Message-ID: Hi everyone, Recently I have switched to Awesome WM. I was looking for a tool to create an application menu and came across awemenugen. However, I found it didn't work so well (doesn't support icons, doesn't ignore .desktop files with NoDisplay=true, creates empty categories, not to mention that you need jdk to run it), so I wrote a similar tool in python addressing these issues: https://github.com/montagdude/awesome-appmenu I have a SlackBuild ready to go, but I wanted to ask if it's okay to be both "upstream" and maintainer. I can guess that there are some reasons this would be encouraged, but I don't want to give the appearance I am using SBo to push my own stuff. Dan Prosser From andreas.guldstrand at gmail.com Thu Sep 8 23:16:30 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Fri, 9 Sep 2016 01:16:30 +0200 Subject: [Slackbuilds-users] Being upstream and maintainer In-Reply-To: References: Message-ID: I'm both upstream and maintainer of the sbotools slackbuild, and I find it very convenient. It's not really "pushing" your own stuff to submit it to SBo, as people will only really find it if they're actually searching for it. On 9 September 2016 at 01:03, Daniel Prosser wrote: > Hi everyone, > > Recently I have switched to Awesome WM. I was looking for a tool to create an > application menu and came across awemenugen. However, I found it didn't work > so well (doesn't support icons, doesn't ignore .desktop files with > NoDisplay=true, creates empty categories, not to mention that you need jdk to > run it), so I wrote a similar tool in python addressing these issues: > > https://github.com/montagdude/awesome-appmenu > > I have a SlackBuild ready to go, but I wanted to ask if it's okay to be both > "upstream" and maintainer. I can guess that there are some reasons this would > be encouraged, but I don't want to give the appearance I am using SBo to push > my own stuff. > > Dan Prosser > _______________________________________________ > 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 kingbeowulf at gmail.com Thu Sep 8 23:37:17 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 8 Sep 2016 16:37:17 -0700 Subject: [Slackbuilds-users] what is the preferred build and test environment In-Reply-To: References: Message-ID: <0892d29f-c215-9e2c-9841-11ccec454879@gmail.com> On 09/08/2016 02:00 PM, Tim Dickson wrote: > Hi everyone, I use sbopkg for building packages, but for my own > slackbuilds I need to test them on both 32bit and 64bit slackware. > Ideally, they would be clean installs, with just the dependencies > required for the build to be tested. I would like to do this with > minimum of fuss, and wondered what you guys (and gals) did ?? > Up till now, I have used 2 separate test machines, or one machine with > two slackware installations on different partitions, but I haven't > managed a clean starting state for each slackbuild. I have somewhat > limited internet data allowance, so don't want to re-download the sbo > tree for every slackbuild when building dependencies. I made limited use > of qemu on windows to run some slackware vm's a while ago, but prefer > solely using linux for testing. > any simple examples or a howto or wiki would be appreciated, and > probably useful to all slackbuild creators. > Thanks, Tim > > PS. some builds are for graphical programs that use opengl, I don't know > if that affects the choice of environment or not. > I use qemu (since I am the maintainer!) to create clean Slackware environments. I set up a file share for both onto a SBo git clone on the host (which actually point to a NFS on a separate server..). I create a base image, then a work-in-progress copy-on-write image. I create a script with a zenity "GUI" to maintain the BASE and WIP images with all command line option. If you are interested you can look at the scripts here (item #6): http://www.linuxgalaxy.org/ Have Fun! Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From thedoogster at gmail.com Thu Sep 8 23:37:32 2016 From: thedoogster at gmail.com (Doogster) Date: Thu, 8 Sep 2016 16:37:32 -0700 Subject: [Slackbuilds-users] Being upstream and maintainer In-Reply-To: References: Message-ID: Who wouldn't be grateful that a project maintainer is supporting Slackware directly? On Thu, Sep 8, 2016 at 4:16 PM, Andreas Guldstrand wrote: > I'm both upstream and maintainer of the sbotools slackbuild, and I > find it very convenient. > > It's not really "pushing" your own stuff to submit it to SBo, as > people will only really find it if they're actually searching for it. > > On 9 September 2016 at 01:03, Daniel Prosser wrote: >> Hi everyone, >> >> Recently I have switched to Awesome WM. I was looking for a tool to create an >> application menu and came across awemenugen. However, I found it didn't work >> so well (doesn't support icons, doesn't ignore .desktop files with >> NoDisplay=true, creates empty categories, not to mention that you need jdk to >> run it), so I wrote a similar tool in python addressing these issues: >> >> https://github.com/montagdude/awesome-appmenu >> >> I have a SlackBuild ready to go, but I wanted to ask if it's okay to be both >> "upstream" and maintainer. I can guess that there are some reasons this would >> be encouraged, but I don't want to give the appearance I am using SBo to push >> my own stuff. >> >> Dan Prosser >> _______________________________________________ >> 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 chris.willing at iinet.net.au Fri Sep 9 00:30:58 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 9 Sep 2016 10:30:58 +1000 Subject: [Slackbuilds-users] what is the preferred build and test environment In-Reply-To: <0892d29f-c215-9e2c-9841-11ccec454879@gmail.com> References: <0892d29f-c215-9e2c-9841-11ccec454879@gmail.com> Message-ID: <43dec39e-0cf7-256f-99e8-009e8716e622@iinet.net.au> On 09/09/16 09:37, King Beowulf wrote: > On 09/08/2016 02:00 PM, Tim Dickson wrote: >> Hi everyone, I use sbopkg for building packages, but for my own >> slackbuilds I need to test them on both 32bit and 64bit slackware. >> Ideally, they would be clean installs, with just the dependencies >> required for the build to be tested. I would like to do this with >> minimum of fuss, and wondered what you guys (and gals) did ?? >> Up till now, I have used 2 separate test machines, or one machine with >> two slackware installations on different partitions, but I haven't >> managed a clean starting state for each slackbuild. I have somewhat >> limited internet data allowance, so don't want to re-download the sbo >> tree for every slackbuild when building dependencies. I made limited use >> of qemu on windows to run some slackware vm's a while ago, but prefer >> solely using linux for testing. >> any simple examples or a howto or wiki would be appreciated, and >> probably useful to all slackbuild creators. >> Thanks, Tim >> >> PS. some builds are for graphical programs that use opengl, I don't know >> if that affects the choice of environment or not. >> > > I use qemu (since I am the maintainer!) to create clean Slackware > environments. I set up a file share for both onto a SBo git clone on > the host (which actually point to a NFS on a separate server..). I > create a base image, then a work-in-progress copy-on-write image. > > I create a script with a zenity "GUI" to maintain the BASE and WIP > images with all command line option. If you are interested you can look > at the scripts here (item #6): > http://www.linuxgalaxy.org/ > I have an almost identical setup to Ed (just no gui) and find it to be an extremely efficient way to do builds & testing. I used Virtual Box for a while but have found it much easier (for me) to juggle BASE/WIP status with Qemu. When my script runs to do a build, it uses the hoorex tool to calculate an ordered list of any other required packages and (as well as installing in the VM) dumps resulting package(s) back into the "real" file system for installation there when/if needed. In the qemu environment, graphical programs will use mesa which is fine for general testing but, of course, won't be as fast as with hw accelerated setup. However an app built with mesa in a VM will still use whatever hw acceleration is available at run time. An example of this is NVENC support which can be included in ffmpeg by supplying the necessary API file at build time but won't be available at run time unless appropriate nvidia card and binary driver are installed i.e. works on real machine but not when testing in the VM. chris From dpross1100 at msn.com Fri Sep 9 00:56:16 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Fri, 9 Sep 2016 00:56:16 +0000 Subject: [Slackbuilds-users] Being upstream and maintainer In-Reply-To: References: Message-ID: Okay, thanks guys. I will submit it soon. On Thursday, September 08, 2016 04:37:32 PM Doogster wrote: > Who wouldn't be grateful that a project maintainer is supporting > Slackware directly? > > On Thu, Sep 8, 2016 at 4:16 PM, Andreas Guldstrand > > wrote: > > I'm both upstream and maintainer of the sbotools slackbuild, and I > > find it very convenient. > > > > It's not really "pushing" your own stuff to submit it to SBo, as > > people will only really find it if they're actually searching for it. > > > > On 9 September 2016 at 01:03, Daniel Prosser wrote: > >> Hi everyone, > >> > >> Recently I have switched to Awesome WM. I was looking for a tool to > >> create an application menu and came across awemenugen. However, I found > >> it didn't work so well (doesn't support icons, doesn't ignore .desktop > >> files with NoDisplay=true, creates empty categories, not to mention that > >> you need jdk to run it), so I wrote a similar tool in python addressing > >> these issues: > >> > >> https://github.com/montagdude/awesome-appmenu > >> > >> I have a SlackBuild ready to go, but I wanted to ask if it's okay to be > >> both "upstream" and maintainer. I can guess that there are some reasons > >> this would be encouraged, but I don't want to give the appearance I am > >> using SBo to push my own stuff. > >> > >> Dan Prosser > >> _______________________________________________ > >> 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/ From willysr at slackbuilds.org Fri Sep 9 01:10:33 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 9 Sep 2016 08:10:33 +0700 Subject: [Slackbuilds-users] pcsc-tools In-Reply-To: References: Message-ID: <6a6d7393-d19f-3465-1431-09d503f7c37c@slackbuilds.org> > It looks like the pcsc-tools source URL has become invalidated. Can this > SBo get an update for the new version and new URL? > > To make it work all I did was to update of the version and the md5sum. > Since I don't know how to tell git to make a file, so I just copy/pasted it > from the git diff from putty. Hi Bryan pcsc-tools along with pcsc-perl are now upgraded to latest update 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: From dickson.tim at googlemail.com Fri Sep 9 09:49:20 2016 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 9 Sep 2016 10:49:20 +0100 Subject: [Slackbuilds-users] what is the preferred build and test environment In-Reply-To: <0892d29f-c215-9e2c-9841-11ccec454879@gmail.com> References: <0892d29f-c215-9e2c-9841-11ccec454879@gmail.com> Message-ID: <62c42a0b-4db8-91a1-cef8-f3ff44e5969d@googlemail.com> thanks folks for the replies. I'll look at qemu. By the way King Beowulf, clicking on the "various random shell scripts and utilities" link (http://www.linuxgalaxy.org/files/utils) takes me to a html page which just says DNS lookup error

DNS lookup error

DNS lookup error so I am interested in your setup, but it's hiding! Regards, Tim On 09/09/2016 00:37, King Beowulf wrote: > On 09/08/2016 02:00 PM, Tim Dickson wrote: >> Hi everyone, I use sbopkg for building packages, but for my own >> slackbuilds I need to test them on both 32bit and 64bit slackware. >> Ideally, they would be clean installs, with just the dependencies >> required for the build to be tested. I would like to do this with >> minimum of fuss, and wondered what you guys (and gals) did ?? >> Up till now, I have used 2 separate test machines, or one machine with >> two slackware installations on different partitions, but I haven't >> managed a clean starting state for each slackbuild. I have somewhat >> limited internet data allowance, so don't want to re-download the sbo >> tree for every slackbuild when building dependencies. I made limited use >> of qemu on windows to run some slackware vm's a while ago, but prefer >> solely using linux for testing. >> any simple examples or a howto or wiki would be appreciated, and >> probably useful to all slackbuild creators. >> Thanks, Tim >> >> PS. some builds are for graphical programs that use opengl, I don't know >> if that affects the choice of environment or not. >> > I use qemu (since I am the maintainer!) to create clean Slackware > environments. I set up a file share for both onto a SBo git clone on > the host (which actually point to a NFS on a separate server..). I > create a base image, then a work-in-progress copy-on-write image. > > I create a script with a zenity "GUI" to maintain the BASE and WIP > images with all command line option. If you are interested you can look > at the scripts here (item #6): > http://www.linuxgalaxy.org/ > > Have Fun! > Ed > > > > _______________________________________________ > 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: From alik at ejik.org Fri Sep 9 09:54:24 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Fri, 09 Sep 2016 12:54:24 +0300 Subject: [Slackbuilds-users] what is the preferred build and test environment In-Reply-To: References: Message-ID: <1473414864.2258116.720527393.5C06111A@webmail.messagingengine.com> > Up till now, I have used 2 separate test machines, or one machine with > two slackware installations on different partitions, but I haven't > managed a clean starting state for each slackbuild. I have somewhat > limited internet data allowance, so don't want to re-download the sbo > tree for every slackbuild when building dependencies. I use slackrepo by David Spencer for this, it keeps the system clean, builds everything automatically, the SBo tree is updated via git. Best regards, Alexander From bryanlharris at gmail.com Fri Sep 9 12:05:57 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Fri, 9 Sep 2016 08:05:57 -0400 Subject: [Slackbuilds-users] pcsc-tools In-Reply-To: <6a6d7393-d19f-3465-1431-09d503f7c37c@slackbuilds.org> References: <6a6d7393-d19f-3465-1431-09d503f7c37c@slackbuilds.org> Message-ID: Thanks Willy, Can you tell me the URL to your repo/branch? I'm looking on this page below but it says latest commit was 6 days ago. So I think I'm in the wrong place. https://gitlab.com/SlackBuilds.org/slackbuilds/tree/master V/r, Bryan On Thu, Sep 8, 2016 at 9:10 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > It looks like the pcsc-tools source URL has become invalidated. Can this > > SBo get an update for the new version and new URL? > > > > To make it work all I did was to update of the version and the md5sum. > > Since I don't know how to tell git to make a file, so I just copy/pasted > it > > from the git diff from putty. > > Hi Bryan > > pcsc-tools along with pcsc-perl are now upgraded to latest update in my > branch > > Thanks > > > -- > 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: From willysr at slackbuilds.org Fri Sep 9 12:17:09 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 09 Sep 2016 19:17:09 +0700 Subject: [Slackbuilds-users] pcsc-tools In-Reply-To: Message-ID: An HTML attachment was scrubbed... URL: From kjhambrick at gmail.com Fri Sep 9 12:45:30 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Fri, 9 Sep 2016 07:45:30 -0500 Subject: [Slackbuilds-users] acpica updated to 20160831 Message-ID: pprkut -- Attached are Unified Diffs of the existing acpica Version 20160108 updated to Version 20160831. Beware of the MD5SUM -- I generated it locally. YMMV ( hope not :)) I've built, installed and tested 20160831 on my Slackware64 14.2 + Multilib System and it works as expected. Thanks for all your work ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- diff -Naur acpica/acpica.SlackBuild acpica-20160831/acpica.SlackBuild --- acpica/acpica.SlackBuild 2016-07-06 19:24:08.346843384 -0500 +++ acpica-20160831/acpica.SlackBuild 2016-09-09 05:34:47.173314010 -0500 @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=acpica -VERSION=${VERSION:-20160108} +VERSION=${VERSION:-20160831} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} diff -Naur acpica/acpica.info acpica-20160831/acpica.info --- acpica/acpica.info 2016-07-06 19:24:08.346843384 -0500 +++ acpica-20160831/acpica.info 2016-09-09 05:36:22.291324039 -0500 @@ -1,8 +1,8 @@ PRGNAM="acpica" -VERSION="20160108" +VERSION="20160831" HOMEPAGE="http://www.acpica.org" -DOWNLOAD="https://acpica.org/sites/acpica/files/acpica-unix2-20160108.tar.gz" -MD5SUM="59e3e9f58446cfbcf67860d09a5c5c95" +DOWNLOAD="https://acpica.org/sites/acpica/files/acpica-unix2-20160831.tar.gz" +MD5SUM="43169cad7b858a75fdb73119cb976c86" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" From atelszewski at gmail.com Fri Sep 9 13:43:09 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 9 Sep 2016 15:43:09 +0200 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool Message-ID: Hi, I have written command line submission tool for SlackBuilds.org Before going public, I would like to ask you to give it a try and report back any problems you might find. As of now, I consider the tool to be feature complete (more options will come one day), so please report back only possible errors rather than features requests. Source code together with SlackBuild for it can be found here (once tested, it will get removed): http://www.telszewski.net/software/src/sbosubmit/ For the moment, the tool does not send anything to slackbuilds.org, unless --address=sbo switch is passed. This is meant for beta testing and to prevent flooding of SBo maintainers with broken submissions. The testing addresses are: http://telszewski.net/testing/sbosubmit/submit/ http://telszewski.net/testing/sbosubmit/pending/ The address of interest is http://telszewski.net/testing/sbosubmit/pending/ , where you can see your upload exactly as it would be sent to slackbuilds.org. Please note that the uploads are overwritten if the archives with the same name are sent. Once any possible errors are resolved, the tool will default to SlackBuilds.org server. I have already tested the tool with multiple submissions to the SlackBuilds.org and haven't noticed any problems. If you want to send the archive to the real slackbuilds.org server, pass the --address=sbo switch. After passing beta tests, the address will be fixed to slackbuilds.org by default and the --address= switch will allow to specify alternative address, for example for testing purposes. The source code contains man page, please refer to it for details. Below is an excerpt from it: "sbosubmit is a tool to facilitate uploading of SlackBuilds to SlackBuilds.org. It does it by performing checks of the files to be submitted, packaging them and then uploading the resulting tarball to the SlackBuilds.org server for later approval. Using traditional methods, when you want to submit a SlackBuild, you have to perform at least the following steps: - very often you have to cleanup the SlackBuild directory from files used during development stage, - create the archive of the files to be submitted, - open web browser, - attach the archive, - fill in all the submission details, - press the submit button, - very often delete the created archive. sbosubmit allows you to perform all these steps (and a bit more) by typing a single command from within the SlackBuild directory." sbosubmit requires curl and libarchive to be already installed. Also, for HTML parsing, links or lynx is required. I hope you'll find the thing useful. -- Best regards, Andrzej Telszewski From yalhcru at gmail.com Fri Sep 9 19:16:42 2016 From: yalhcru at gmail.com (B Watson) Date: Fri, 9 Sep 2016 15:16:42 -0400 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool In-Reply-To: References: Message-ID: On 9/9/16, Andrzej Telszewski wrote: > I have written command line submission tool for SlackBuilds.org > Before going public, I would like to ask you to give it a try and report > back any problems you might find. You did just go public :) There's already a tool called sbosubmit, one of us should pick a different name to avoid confusion... http://urchlay.naptime.net/repos/sbostuff/ It's a bit of a coincidence, last night I added license/author comments to my sbosubmit at the request of someone on IRC, today there's another thing called sbosubmit. Looking at your man page, it looks like your sbosubmit does a lot more than mine (mine just uploads a tarball, yours checks the script, info file, etc and creates the tarball itself). My sbosubmit is just a quick & dirty script... I'll rename mine to 'sboupload', it will take me 30 seconds. If you were renaming yours, it would be a lot more than 30 sec worth of work for you, I think. From atelszewski at gmail.com Fri Sep 9 20:07:33 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 9 Sep 2016 22:07:33 +0200 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool In-Reply-To: References: Message-ID: <9265b405-11bb-526d-18dc-8c4159af3553@gmail.com> On 09/09/16 21:16, B Watson wrote: > There's already a tool called sbosubmit, one of us should pick a different > name to avoid confusion... > > http://urchlay.naptime.net/repos/sbostuff/ > Heh, googling for "sbosubmit" yields no meaningful results ;-) > It's a bit of a coincidence, last night I added license/author comments > to my sbosubmit at the request of someone on IRC, today there's another > thing called sbosubmit. > Mine has been in slow brewing for quite some time already, almost 1 year I think. > Looking at your man page, it looks like your sbosubmit does a lot more > than mine (mine just uploads a tarball, yours checks the script, info > file, etc and creates the tarball itself). My sbosubmit is just a quick & > dirty script... > Yep, and as time allows, more to come. There will be a lot of fun with text processing and regex in C++. The core functionality is already there, meaning you just type the command from within the SlackBuild directory and you're done ;-) What is left, is to extend the submission files verification, including for example parsing of SlackBuild and checking its values. > I'll rename mine to 'sboupload', it will take me 30 seconds. If you were > renaming yours, it would be a lot more than 30 sec worth of work for you, > I think. Yes, it certainly would. Thank you very much! -- Best regards, Andrzej Telszewski From yalhcru at gmail.com Fri Sep 9 20:23:52 2016 From: yalhcru at gmail.com (B Watson) Date: Fri, 9 Sep 2016 16:23:52 -0400 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool In-Reply-To: <9265b405-11bb-526d-18dc-8c4159af3553@gmail.com> References: <9265b405-11bb-526d-18dc-8c4159af3553@gmail.com> Message-ID: On 9/9/16, Andrzej Telszewski wrote: > > Heh, googling for "sbosubmit" yields no meaningful results ;-) Yah, because I use my own git server instead of 'social coding' sites like the cool kids. Plus, when I first started with my sbosubmit, I wasn't sure how the SBo admins were going to feel about it (usually web site owners hate scrapers), so I kept it pretty quiet, never announced it on this mailing list or mentioned it on IRC until a couple weeks ago. > There will be a lot of fun with text processing and regex in C++. Ugh, not my idea of fun at all, I'd rather use C than C++, and I'd rather use perl than either, for text processing and regex... but 'fun' is so subjective (I know otherwise-sane people who jump out of perfectly good airplanes at 10,000 feet, the plane's not even on fire or anything!) > Thank you very much! Ended up with 'sboul', since I already have a 'sbodl' script in the same repo. From atelszewski at gmail.com Fri Sep 9 21:52:43 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 9 Sep 2016 23:52:43 +0200 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool In-Reply-To: References: <9265b405-11bb-526d-18dc-8c4159af3553@gmail.com> Message-ID: <44f30256-e1e4-56a0-5c3d-34a5c340355d@gmail.com> On 09/09/16 22:23, B Watson wrote: > Plus, when I first started with my sbosubmit, I > wasn't sure how the SBo admins were going to feel about it (usually web > site owners hate scrapers), so I kept it pretty quiet, never announced > it on this mailing list or mentioned it on IRC until a couple weeks ago. I'm fearing the same. I have put quite some effort (and more to come) to ensure that admins won't get flooded with broken submissions. All in all, I believe the maintainers are rather responsible species, so there won't be any abuses. -- Best regards, Andrzej Telszewski From yalhcru at gmail.com Fri Sep 9 23:15:01 2016 From: yalhcru at gmail.com (B Watson) Date: Fri, 9 Sep 2016 19:15:01 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On 9/7/16, Doogster wrote: > IIRC, the segfaults happened with regular DOOM. A reliable way to trigger > them was to set the sound backend to FMOD and FMOD's backend to Pulseaudio, > restart the sound system (that's a menu option), then start a game. Unable to reproduce, with gzdoom 2.1.1 and fmodapi 4.28.17, playing either Doom or Doom II on Slackware64 14.2. The only thing that happens when I set the sound system to to fmod and the fmod backend to pulseaudio, then hit 'restart sound', is that gzdoom's log output says this: FMOD Sound System, copyright ?? Firelight Technologies Pty, Ltd., 1994-2009. Loaded FMOD version 4.28.17 No working sound devices found. Try a different snd_output? FMod Ex Sound init failed. Trying OpenAL. I_InitSound: Initializing OpenAL ...and in the menu, the sound system option changed itself to OpenAL. The pulseaudio daemon was running and working (I could e.g. play audio though it with mplayer or pacat). gzdoom didn't segfault. Switching gzdoom's fmod backend back to alsa and using fmod as the sound system, worked fine (gzdoom played normally, audio worked, no segfaults). Anyone else want to try this out, other than me and Doogster? From slackbuilds at schoepfer.info Sat Sep 10 19:29:48 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 10 Sep 2016 21:29:48 +0200 Subject: [Slackbuilds-users] Fwd: ffmpeg on SBo and texi2html In-Reply-To: References: Message-ID: <134ad97774b58c1a2353c01d8155b90d@schoepfer.info> Hi, as i got no reply from the ffmpeg-maintainer since two weeks, i forward to this list: -------- Original Message -------- Hi Heinz, it seems that no tetex/texlive or texi2html is needed anymore for building ffmpeg 2.8.7 on slackware 14.2, just texinfo from official slackware is needed. The check for texi2html might be an issue, see this thread http://www.linuxquestions.org/questions/slackware-14/ffmpeg-and-texi2html-4175587932/#post5595760 Would you please consider removing the check for texi2html? --- a/multimedia/ffmpeg/ffmpeg.SlackBuild +++ b/multimedia/ffmpeg/ffmpeg.SlackBuild @@ -57,15 +57,6 @@ else LIBDIRSUFFIX="" fi -# environment sanity checks -TEXI2HTML=$(which texi2html 2>/dev/null) - -if [ "$TEXI2HTML" = "" ]; then - echo "Could not find texi2html! Please make sure to have tetex or texlive installed" - echo "and that texi2html is in PATH." - exit 1 -fi - Johannes From pprkut at slackbuilds.org Sat Sep 10 21:39:34 2016 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Sat, 10 Sep 2016 23:39:34 +0200 Subject: [Slackbuilds-users] Fwd: ffmpeg on SBo and texi2html In-Reply-To: <134ad97774b58c1a2353c01d8155b90d@schoepfer.info> References: <134ad97774b58c1a2353c01d8155b90d@schoepfer.info> Message-ID: <8118737.qFOkiUNQVV@titania> On Saturday, 10 September 2016 21:29:48 CEST Franzen wrote: > Hi, > > as i got no reply from the ffmpeg-maintainer since two weeks, i forward > to this list: > > -------- Original Message -------- > Hi Heinz, > > it seems that no tetex/texlive or texi2html is needed anymore > for building ffmpeg 2.8.7 on slackware 14.2, just texinfo from official > slackware is needed. > The check for texi2html might be an issue, see this thread > http://www.linuxquestions.org/questions/slackware-14/ffmpeg-and-texi2html-41 > 75587932/#post5595760 > > Would you please consider removing the check for texi2html? Hi! Sorry I didn't get back to you earlier. Having this on the list, however, doesn't hurt either :) I was pretty much off-the-grid for the better part of the last two months and came out of it rather energy-drained. I'm just now again starting to catch up on things, but the TODO list is rather long. I can't promise a timeline, but this is on it. I'll get to it :) Grs, Heinz -------------- 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: From willysr at slackbuilds.org Sun Sep 11 02:13:25 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 11 Sep 2016 09:13:25 +0700 Subject: [Slackbuilds-users] Updates - 20160911.1 Message-ID: <03f6dac8-090c-a0dd-469e-9b269c02967e@slackbuilds.org> Sun Sep 11 01:55:42 UTC 2016 academic/libqalculate: Added (desktop caculator library). academic/qalculate-gtk: Added (GUI for libqalculate). audio/xwax: Updated for version 1.6. desktop/awesome-appmenu: Added (application menu tool for awesome). desktop/insync-thunar: Updated REQUIRES. development/codeblocks: Updated for version 16.01. development/flow: Updated for version 0.32.0. development/hub: Updated for version 2.2.6. development/komodo-edit: Updated for version 10.1.0. development/komodo-ide: Updated for version 10.1.0. development/poedit: Switch to i586. development/scite: Updated for version 3.6.7. development/tig: Updated for version 2.2. development/uz80as: Fix MD5SUM. development/vstudio: Updated for version 6.5.12. games/7kaa: Added (Seven Kingdoms, a real-time strategy game). games/GLupeN64: Added (mupen64plus + RSP-HLE + GLideN64 + libretro). games/blastem-libretro: Updated for version 2016.09.08_27b3f8e. games/bnes-libretro: Added (libretro implementation of bNES). games/chromium-bsu: Updated for version 0.9.16.1 games/firestorm: Updated for version 4.7.9.50527. gis/Shapely: Updated for version 1.5.17. gis/google-earth: Add 64 bit support. gis/pdal: Updated for version 1.3.0. graphics/converseen: Updated for version 0.9.5.1. graphics/gmic: Added (image processing framework). graphics/mapcrafter: Updated for version 2.3.1. libraries/CherryPy: Updated for version 8.0.0. libraries/Nevow: Updated for version 0.14.2. libraries/VitaMTP: Added (Vita's MTP protocol library). libraries/botocore: Updated for version 1.4.52. libraries/cffi: Updated for version 1.8.2. libraries/cfitsio: Updated for version 3.39. libraries/cryptopp: Updated for version 5.6.3. libraries/dropbox-python: Updated for version 6.8.0. libraries/enca: Updated for version 1.19 libraries/gtkspell3: Updated for version 3.0.9. libraries/jsoncpp: Updated for version 1.7.5 libraries/libgadu: Updated for version 1.12.1 + new maintainer. libraries/libvirt-python: Updated for version 2.2.0. libraries/libvirt: Updated for version 2.2.0. libraries/live555: Updated for version 2016.09.08 libraries/ntl: Updated for version 9.11.0. libraries/php-memcache: Fixed build with gnu89 flag. libraries/wxPython3: Added (Crossplatform GUI Toolkit). misc/QCMA: Added (Cross-platform content manager assistant). misc/qtspell: Updated for version 0.8.2. multimedia/aegisub: Switch to i586. multimedia/gpodder: Updated for version 3.9.1. multimedia/lives: Updated for version 2.8.0. multimedia/plexmediaserver: Updated for version 1.1.3.2700. network/Pyrit: Added (WPA precomputed cracker). network/allmydata-tahoe: Removed (replaced by tahoe-lafs). network/awscli: Updated for version 1.10.62. network/bitlbee-steam: Updated for version 1.4.2. network/boxcryptor: Updated for version 2.1.409.160. network/flexget: Updated for version 2.3.16. network/freeradius-server: Updated for version 2.2.9. network/imapproxy: i486 -> i586. network/midori: Switch to webkit2gtk. network/nghttp2: Updated for version 1.14.0. network/nzbget: Updated for version 17.1. network/postfix: Updated for version 3.1.2. network/qTox: Updated for version 20160901_76c4cf7. network/reaver: Update DOWNLOAD url. network/sipcalc: i486 -> i586. network/sphinx: Updated for version 2.2.11. network/sshguard: Updated for version 1.7.0. network/sshuttle: Updated for version 0.78.1. network/sslh: Updated for version 1.18. network/tahoe-lafs: Added (Secure File Store). network/tornado: Add backports-abc dependency. network/toxcore: Updated for version 20160727_755f084. network/vivaldi: Updated for version 1.4.589.11. network/wireshark: Updated for version 2.2.0. network/youtube-dl: Updated for version 2016.09.08. office/LibreOffice: Updated for version 5.2.1.2 office/calibre: Updated for version 2.67.0 office/gnucash: Updated for version 2.6.13. office/libreoffice-helppack: Updated for version 5.2.1. office/libreoffice-langpack: Updated for version 5.2.1. office/libreoffice: Updated for version 5.2.1. office/odt2txt: Updated for version 0.5. office/openoffice.org: Add security hotfix patch. office/pstoedit: Updated for version 3.70. python/attrs: Added (attributes without boilerplate). python/backports-abc: Added (backport of the collections.abc). python/cryptography: Updated for version 1.5. python/curtsies: Updated for version 0.2.6. python/foolscap: Updated for version 0.12.3. python/google-api-python-client: Updated for version 1.5.3. python/idna: Updated for version 2.1. python/pendulum: Updated for version 0.5.5. python/pyOpenSSL: Updated for version 0.16.1. python/pyasn1-modules: Updated for version 0.0.8. python/pyasn1: Updated for version 0.1.9. python/pytest: Updated for version 3.0.2. python/python-configargparse: Updated for version 0.11.0. python/python-django-tagging: Updated for version 0.4.3. python/python-django: Updated for version 1.10. python/python-jsonrpclib: Update HOMEPAGE. python/python-memcached: Updated for version 1.58 + new maintainer. python/python-oauth2client: Updated for version 3.0.0. python/python-oauthlib: Updated for version 2.0.0. python/python-swiftclient: Updated for version 3.1.0. python/python-twisted: Updated for version 16.4.0. python/requests-oauthlib: Updated for version 0.6.2. python/service_identity: Updated for version 16.0.0. python/sge-pygame: Updated for version 1.1.1. ruby/rubygem-sass: Added (a CSS extension). system/containerd: Added (linux containers manager). system/fakeroot: Change maintainer + new script option. system/firejail: Updated for version 0.9.42. system/parallel: Updated for version 20160822. system/pcsc-perl: Updated for version 1.4.14. system/pcsc-tools: Updated for version 1.4.27. system/phoronix-test-suite: Updated for version 6.6.0. system/qemu-guest-agent: Updated for version 2.6.1. system/qemu: Updated for version 2.6.1. system/rmw: Updated for version 2016.09.04.01a. system/runc: Added (lightweight portable containers). system/s3ql: Updated for version 2.20. system/usbredir: Updated for version 0.7.1. system/wine-staging: Updated for version 1.9.18. system/xen: Updated for version 4.7.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: From alik at ejik.org Sun Sep 11 16:36:33 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Sun, 11 Sep 2016 19:36:33 +0300 Subject: [Slackbuilds-users] Updates - 20160911.1 In-Reply-To: <03f6dac8-090c-a0dd-469e-9b269c02967e@slackbuilds.org> References: <03f6dac8-090c-a0dd-469e-9b269c02967e@slackbuilds.org> Message-ID: <1473611793.725792.722277617.12688478@webmail.messagingengine.com> On Sun, Sep 11, 2016, at 05:13, Willy Sudiarto Raharjo wrote: > python/pyOpenSSL: Updated for version 0.16.1. Building pyOpenSSL by slackrepo produced a warning: python/pyOpenSSL: Package VERSION is "16.1.0" (expected "0.16.1"). So, the Slackbuild and info contain different versions. Best regards, Alexander From willysr at slackbuilds.org Sun Sep 11 16:46:59 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 11 Sep 2016 23:46:59 +0700 Subject: [Slackbuilds-users] Updates - 20160911.1 In-Reply-To: <1473611793.725792.722277617.12688478@webmail.messagingengine.com> References: <03f6dac8-090c-a0dd-469e-9b269c02967e@slackbuilds.org> <1473611793.725792.722277617.12688478@webmail.messagingengine.com> Message-ID: <975a9cd7-df49-6e63-0078-113fb505076d@slackbuilds.org> > On Sun, Sep 11, 2016, at 05:13, Willy Sudiarto Raharjo wrote: >> python/pyOpenSSL: Updated for version 0.16.1. > > Building pyOpenSSL by slackrepo produced a warning: > python/pyOpenSSL: Package VERSION is "16.1.0" (expected "0.16.1"). > > So, the Slackbuild and info contain different versions. Sorry, my fault fixed in my branch already -- 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: From willysr at slackbuilds.org Sun Sep 11 17:04:23 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 12 Sep 2016 00:04:23 +0700 Subject: [Slackbuilds-users] Updates - 20160911.2 Message-ID: <147d85e9-5976-6989-77e0-870eb4d653ef@slackbuilds.org> Sun Sep 11 16:57:44 UTC 2016 libraries/ipaddress: Updated for version 1.0.17. python/pyOpenSSL: Fix VERSION. ruby/rubygem-bundler: Updated for version 1.13.0. system/containerd: Fix DOWNLOAD url. system/dar: Updated for version 2.5.6. system/webmin: Updated for version 1.810. +--------------------------+ -- 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: From yalhcru at gmail.com Mon Sep 12 02:31:01 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 11 Sep 2016 22:31:01 -0400 Subject: [Slackbuilds-users] fmodapi access upstream In-Reply-To: References: Message-ID: On 9/7/16, Doogster wrote: > IIRC, the segfaults happened with regular DOOM. A reliable way to trigger > them was to set the sound backend to FMOD and FMOD's backend to Pulseaudio, > restart the sound system (that's a menu option), then start a game. So what I've done is create a gzdoom.SlackBuild that will include its own private copy of fmodapi, if it finds one in $CWD. This works whether or not there's a system-wide install of fmodapi, and doesn't conflict with the regular fmodapi package if it's installed. Not pushing this to git until it's been tested more, but you can grab it from here: http://urchlay.naptime.net/~urchlay/src/gzdoom.tar.gz To use, extract that tarball, download or copy the gzdoom source to its dir as usual, then download one of ponce's fmodapi tarballs into the same dir, one of: http://ponce.cc/slackware/sources/repo/fmodapi44450linux.tar.gz http://ponce.cc/slackware/sources/repo/fmodapi44461linux.tar.gz These 2 tarballs contain both 32-bit and 64-bit shared libs. Older versions of fmodapi where there were 2 separate downloads *won't* work with this (yet?) After you build and install gzdoom, try this: $ ldd /usr/games/gzdoom | grep fmod libfmodex64.so => /usr/lib64/gzdoom/libfmodex64.so (0x00002b12ad9d4000) ...for 32-bit it'll be /usr/lib/gzdoom/libfmodex.so instead. Though I haven't actually tested it on 32-bit yet (please let me know if there are any problems!) If you still get segfaults when using the fmod ex sound engine in gzdoom using this build with both versions of fmodapi listed above, then I don't know what to tell you. Saying "it works for me" isn't very helpful, but it does work for me so I can't tell if anything I do might fix the problem for you. From fernando.lopezjr at gmail.com Mon Sep 12 19:51:41 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 12 Sep 2016 13:51:41 -0600 Subject: [Slackbuilds-users] libmp4v2 down. Message-ID: invalid url: mp4v2.googlecode . com/files/mp4v2-2.0.0.tar.bz2 -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Sep 12 19:53:58 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 13 Sep 2016 02:53:58 +0700 Subject: [Slackbuilds-users] libmp4v2 down. In-Reply-To: References: Message-ID: <83538497-4515-7e95-9030-00b3d0dbe0d7@slackbuilds.org> > invalid url: > mp4v2.googlecode . com/files/mp4v2-2.0.0.tar.bz2 It's been reported before in LQ and i have it fixed 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: From fernando.lopezjr at gmail.com Mon Sep 12 19:57:59 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 12 Sep 2016 13:57:59 -0600 Subject: [Slackbuilds-users] libmp4v2 down. In-Reply-To: <83538497-4515-7e95-9030-00b3d0dbe0d7@slackbuilds.org> References: <83538497-4515-7e95-9030-00b3d0dbe0d7@slackbuilds.org> Message-ID: lol. thanks =) On Mon, Sep 12, 2016 at 1:53 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > invalid url: > > mp4v2.googlecode . com/files/mp4v2-2.0.0.tar.bz2 > > It's been reported before in LQ and i have it fixed 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fellype at gmail.com Tue Sep 13 18:23:54 2016 From: fellype at gmail.com (Fellype do Nascimento) Date: Tue, 13 Sep 2016 15:23:54 -0300 Subject: [Slackbuilds-users] Can't build libquicktime, mlt, and kdenlive using sboinstall Message-ID: Hi all, I can't build libquicktime, mlt, and kdenlive using sboinstall. I discovered this issue trying to install kdenlive (by using sboinstall kdenlive), all other deps installed fine, but these three packages failed to install. The errors I got are listed below: ##### libquicktime ERRORS - START ##### libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../../include -DLOCALE_DIR=\"/usr/share/locale\" -O2 -march=i486 -mtune=i686 -finline-functions -Wall -Winline -Wmissing-declarations -Wdeclaration-after-statement -fvisibility=hidden -MT lqt_ffmpeg.lo -MD -MP -MF .deps/lqt_ffmpeg.Tpo -c lqt_ffmpeg.c -fPIC -DPIC -o .libs/lqt_ffmpeg.o lqt_ffmpeg.c:389:13: error: 'CODEC_ID_MPEG1VIDEO' undeclared here (not in a function) .id = CODEC_ID_MPEG1VIDEO, ^ lqt_ffmpeg.c:400:13: error: 'CODEC_ID_MPEG4' undeclared here (not in a function) .id = CODEC_ID_MPEG4, ^ lqt_ffmpeg.c:418:13: error: 'CODEC_ID_MSMPEG4V1' undeclared here (not in a function) .id = CODEC_ID_MSMPEG4V1, ^ lqt_ffmpeg.c:429:13: error: 'CODEC_ID_MSMPEG4V2' undeclared here (not in a function) .id = CODEC_ID_MSMPEG4V2, ^ lqt_ffmpeg.c:440:13: error: 'CODEC_ID_MSMPEG4V3' undeclared here (not in a function) .id = CODEC_ID_MSMPEG4V3, ^ lqt_ffmpeg.c:484:13: error: 'CODEC_ID_H263' undeclared here (not in a function) .id = CODEC_ID_H263, ^ lqt_ffmpeg.c:511:13: error: 'CODEC_ID_H264' undeclared here (not in a function) .id = CODEC_ID_H264, ^ lqt_ffmpeg.c:522:13: error: 'CODEC_ID_H263P' undeclared here (not in a function) .id = CODEC_ID_H263P, ^ lqt_ffmpeg.c:536:13: error: 'CODEC_ID_H263I' undeclared here (not in a function) .id = CODEC_ID_H263I, ^ lqt_ffmpeg.c:547:13: error: 'CODEC_ID_SVQ1' undeclared here (not in a function) .id = CODEC_ID_SVQ1, ^ lqt_ffmpeg.c:558:13: error: 'CODEC_ID_SVQ3' undeclared here (not in a function) .id = CODEC_ID_SVQ3, ^ lqt_ffmpeg.c:569:13: error: 'CODEC_ID_MJPEG' undeclared here (not in a function) .id = CODEC_ID_MJPEG, ^ lqt_ffmpeg.c:583:13: error: 'CODEC_ID_MJPEGB' undeclared here (not in a function) .id = CODEC_ID_MJPEGB, ^ lqt_ffmpeg.c:597:13: error: 'CODEC_ID_TARGA' undeclared here (not in a function) .id = CODEC_ID_TARGA, ^ lqt_ffmpeg.c:609:13: error: 'CODEC_ID_TIFF' undeclared here (not in a function) .id = CODEC_ID_TIFF, ^ lqt_ffmpeg.c:620:13: error: 'CODEC_ID_8BPS' undeclared here (not in a function) .id = CODEC_ID_8BPS, ^ lqt_ffmpeg.c:630:13: error: 'CODEC_ID_INDEO3' undeclared here (not in a function) .id = CODEC_ID_INDEO3, ^ lqt_ffmpeg.c:641:13: error: 'CODEC_ID_RPZA' undeclared here (not in a function) .id = CODEC_ID_RPZA, ^ lqt_ffmpeg.c:651:13: error: 'CODEC_ID_SMC' undeclared here (not in a function) .id = CODEC_ID_SMC, ^ lqt_ffmpeg.c:661:13: error: 'CODEC_ID_CINEPAK' undeclared here (not in a function) .id = CODEC_ID_CINEPAK, ^ lqt_ffmpeg.c:672:13: error: 'CODEC_ID_CYUV' undeclared here (not in a function) .id = CODEC_ID_CYUV, ^ lqt_ffmpeg.c:683:13: error: 'CODEC_ID_QTRLE' undeclared here (not in a function) .id = CODEC_ID_QTRLE, ^ lqt_ffmpeg.c:696:13: error: 'CODEC_ID_MSRLE' undeclared here (not in a function) .id = CODEC_ID_MSRLE, ^ lqt_ffmpeg.c:706:13: error: 'CODEC_ID_DVVIDEO' undeclared here (not in a function) .id = CODEC_ID_DVVIDEO, ^ lqt_ffmpeg.c:775:13: error: 'CODEC_ID_FFVHUFF' undeclared here (not in a function) .id = CODEC_ID_FFVHUFF, ^ lqt_ffmpeg.c:788:13: error: 'CODEC_ID_FFV1' undeclared here (not in a function) .id = CODEC_ID_FFV1, ^ lqt_ffmpeg.c:804:13: error: 'CODEC_ID_DNXHD' undeclared here (not in a function) .id = CODEC_ID_DNXHD, ^ lqt_ffmpeg.c:820:13: error: 'CODEC_ID_MPEG2VIDEO' undeclared here (not in a function) .id = CODEC_ID_MPEG2VIDEO, ^ lqt_ffmpeg.c:842:13: error: 'CODEC_ID_MP3' undeclared here (not in a function) .id = CODEC_ID_MP3, ^ lqt_ffmpeg.c:842:13: error: initializer element is not constant lqt_ffmpeg.c:842:13: note: (near initialization for 'codecidmap_a[0].id') lqt_ffmpeg.c:854:13: error: 'CODEC_ID_MP2' undeclared here (not in a function) .id = CODEC_ID_MP2, ^ lqt_ffmpeg.c:854:13: error: initializer element is not constant lqt_ffmpeg.c:854:13: note: (near initialization for 'codecidmap_a[1].id') lqt_ffmpeg.c:869:13: error: 'CODEC_ID_AC3' undeclared here (not in a function) .id = CODEC_ID_AC3, ^ lqt_ffmpeg.c:869:13: error: initializer element is not constant lqt_ffmpeg.c:869:13: note: (near initialization for 'codecidmap_a[2].id') lqt_ffmpeg.c:884:13: error: 'CODEC_ID_QDM2' undeclared here (not in a function) .id = CODEC_ID_QDM2, ^ lqt_ffmpeg.c:884:13: error: initializer element is not constant lqt_ffmpeg.c:884:13: note: (near initialization for 'codecidmap_a[3].id') lqt_ffmpeg.c:899:13: error: 'CODEC_ID_ALAC' undeclared here (not in a function) .id = CODEC_ID_ALAC, ^ lqt_ffmpeg.c:899:13: error: initializer element is not constant lqt_ffmpeg.c:899:13: note: (near initialization for 'codecidmap_a[4].id') lqt_ffmpeg.c:912:13: error: 'CODEC_ID_ADPCM_MS' undeclared here (not in a function) .id = CODEC_ID_ADPCM_MS, ^ lqt_ffmpeg.c:912:13: error: initializer element is not constant lqt_ffmpeg.c:912:13: note: (near initialization for 'codecidmap_a[5].id') lqt_ffmpeg.c:925:13: error: 'CODEC_ID_ADPCM_IMA_WAV' undeclared here (not in a function) .id = CODEC_ID_ADPCM_IMA_WAV, ^ lqt_ffmpeg.c:925:13: error: initializer element is not constant lqt_ffmpeg.c:925:13: note: (near initialization for 'codecidmap_a[6].id') make[3]: *** [lqt_ffmpeg.lo] Error 1 Makefile:407: recipe for target 'lqt_ffmpeg.lo' failed make[3]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins/ffmpeg' make[2]: *** [all-recursive] Error 1 Makefile:371: recipe for target 'all-recursive' failed make[2]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins' make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Makefile:444: recipe for target 'all-recursive' failed make[1]: Leaving directory '/tmp/SBo/libquicktime-1.2.4' Makefile:351: recipe for target 'all' failed Failure encountered while building libquicktime: libquicktime.SlackBuild return non-zero Do you want to proceed [n] ###### libquicktime ERRORS - END ##### ##### mlt ERRORS - START ##### /usr/include/libavcodec/avcodec.h:4414:6: note: declared here void av_free_packet(AVPacket *pkt); ^ make[2]: *** [producer_avformat.o] Error 1 : recipe for target 'producer_avformat.o' failed make[2]: Leaving directory '/tmp/SBo/mlt-6.0.0/src/modules/avformat' make[1]: *** [all] Error 1 Makefile:5: recipe for target 'all' failed make[1]: Leaving directory '/tmp/SBo/mlt-6.0.0/src/modules' make: *** [all] Error 1 Makefile:9: recipe for target 'all' failed Failure encountered while building mlt: mlt.SlackBuild return non-zero Do you want to proceed [n] ##### mlt ERRORS - END ##### ##### kdenlive ERRORS - START ##### CMake Error at /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message): Could NOT find MLT (missing: MLT_LIBRARIES MLTPP_LIBRARIES MLT_INCLUDE_DIR MLTPP_INCLUDE_DIR) (Required is at least version "0.9.0") Call Stack (most recent call first): /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE) cmake/modules/FindMLT.cmake:59 (find_package_handle_standard_args) CMakeLists.txt:67 (find_package) ##### kdenlive ERRORS - END ##### From andreas.guldstrand at gmail.com Tue Sep 13 20:24:00 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Tue, 13 Sep 2016 22:24:00 +0200 Subject: [Slackbuilds-users] Can't build libquicktime, mlt, and kdenlive using sboinstall In-Reply-To: References: Message-ID: I've just tried with sboinstall kdenlive here, and everything built and installed correctly. This was my install queue: Install queue: amrnb dvdauthor libavc1394 libdv libiec61883 dvgrab libmp4v2 faac faad2 gsm lame ffmpeg libquicktime mlt schroedinger x264 xvidcore kdenlive Perhaps you already had one or more of the prerequisites installed? Perhaps with an old version? Or perhaps built with non-default options? For example ffmpeg has a lot of options for its SlackBuild, and I didn't enable any of them when I tried just now. And seeing as ffmpeg is mentioned in one of the places where things fail for you, that would be my first suspect. Good luck / Andreas (current maintainer of sbotools) On 13 September 2016 at 20:23, Fellype do Nascimento wrote: > Hi all, > > I can't build libquicktime, mlt, and kdenlive using sboinstall. > > I discovered this issue trying to install kdenlive (by using sboinstall > kdenlive), all other deps installed fine, but these three packages failed to > install. > > The errors I got are listed below: > > ##### libquicktime ERRORS - START ##### > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include > -I../../include -DLOCALE_DIR=\"/usr/share/locale\" -O2 -march=i486 > -mtune=i686 -finline-functions -Wall -Winline -Wmissing-declarations > -Wdeclaration-after-statement -fvisibility=hidden -MT lqt_ffmpeg.lo -MD -MP > -MF .deps/lqt_ffmpeg.Tpo -c lqt_ffmpeg.c -fPIC -DPIC -o .libs/lqt_ffmpeg.o > lqt_ffmpeg.c:389:13: error: 'CODEC_ID_MPEG1VIDEO' undeclared here (not in a > function) > .id = CODEC_ID_MPEG1VIDEO, > ^ > lqt_ffmpeg.c:400:13: error: 'CODEC_ID_MPEG4' undeclared here (not in a > function) > .id = CODEC_ID_MPEG4, > ^ > lqt_ffmpeg.c:418:13: error: 'CODEC_ID_MSMPEG4V1' undeclared here (not in a > function) > .id = CODEC_ID_MSMPEG4V1, > ^ > lqt_ffmpeg.c:429:13: error: 'CODEC_ID_MSMPEG4V2' undeclared here (not in a > function) > .id = CODEC_ID_MSMPEG4V2, > ^ > lqt_ffmpeg.c:440:13: error: 'CODEC_ID_MSMPEG4V3' undeclared here (not in a > function) > .id = CODEC_ID_MSMPEG4V3, > ^ > lqt_ffmpeg.c:484:13: error: 'CODEC_ID_H263' undeclared here (not in a > function) > .id = CODEC_ID_H263, > ^ > lqt_ffmpeg.c:511:13: error: 'CODEC_ID_H264' undeclared here (not in a > function) > .id = CODEC_ID_H264, > ^ > lqt_ffmpeg.c:522:13: error: 'CODEC_ID_H263P' undeclared here (not in a > function) > .id = CODEC_ID_H263P, > ^ > lqt_ffmpeg.c:536:13: error: 'CODEC_ID_H263I' undeclared here (not in a > function) > .id = CODEC_ID_H263I, > ^ > lqt_ffmpeg.c:547:13: error: 'CODEC_ID_SVQ1' undeclared here (not in a > function) > .id = CODEC_ID_SVQ1, > ^ > lqt_ffmpeg.c:558:13: error: 'CODEC_ID_SVQ3' undeclared here (not in a > function) > .id = CODEC_ID_SVQ3, > ^ > lqt_ffmpeg.c:569:13: error: 'CODEC_ID_MJPEG' undeclared here (not in a > function) > .id = CODEC_ID_MJPEG, > ^ > lqt_ffmpeg.c:583:13: error: 'CODEC_ID_MJPEGB' undeclared here (not in a > function) > .id = CODEC_ID_MJPEGB, > ^ > lqt_ffmpeg.c:597:13: error: 'CODEC_ID_TARGA' undeclared here (not in a > function) > .id = CODEC_ID_TARGA, > ^ > lqt_ffmpeg.c:609:13: error: 'CODEC_ID_TIFF' undeclared here (not in a > function) > .id = CODEC_ID_TIFF, > ^ > lqt_ffmpeg.c:620:13: error: 'CODEC_ID_8BPS' undeclared here (not in a > function) > .id = CODEC_ID_8BPS, > ^ > lqt_ffmpeg.c:630:13: error: 'CODEC_ID_INDEO3' undeclared here (not in a > function) > .id = CODEC_ID_INDEO3, > ^ > lqt_ffmpeg.c:641:13: error: 'CODEC_ID_RPZA' undeclared here (not in a > function) > .id = CODEC_ID_RPZA, > ^ > lqt_ffmpeg.c:651:13: error: 'CODEC_ID_SMC' undeclared here (not in a > function) > .id = CODEC_ID_SMC, > ^ > lqt_ffmpeg.c:661:13: error: 'CODEC_ID_CINEPAK' undeclared here (not in a > function) > .id = CODEC_ID_CINEPAK, > ^ > lqt_ffmpeg.c:672:13: error: 'CODEC_ID_CYUV' undeclared here (not in a > function) > .id = CODEC_ID_CYUV, > ^ > lqt_ffmpeg.c:683:13: error: 'CODEC_ID_QTRLE' undeclared here (not in a > function) > .id = CODEC_ID_QTRLE, > ^ > lqt_ffmpeg.c:696:13: error: 'CODEC_ID_MSRLE' undeclared here (not in a > function) > .id = CODEC_ID_MSRLE, > ^ > lqt_ffmpeg.c:706:13: error: 'CODEC_ID_DVVIDEO' undeclared here (not in a > function) > .id = CODEC_ID_DVVIDEO, > ^ > lqt_ffmpeg.c:775:13: error: 'CODEC_ID_FFVHUFF' undeclared here (not in a > function) > .id = CODEC_ID_FFVHUFF, > ^ > lqt_ffmpeg.c:788:13: error: 'CODEC_ID_FFV1' undeclared here (not in a > function) > .id = CODEC_ID_FFV1, > ^ > lqt_ffmpeg.c:804:13: error: 'CODEC_ID_DNXHD' undeclared here (not in a > function) > .id = CODEC_ID_DNXHD, > ^ > lqt_ffmpeg.c:820:13: error: 'CODEC_ID_MPEG2VIDEO' undeclared here (not in a > function) > .id = CODEC_ID_MPEG2VIDEO, > ^ > lqt_ffmpeg.c:842:13: error: 'CODEC_ID_MP3' undeclared here (not in a > function) > .id = CODEC_ID_MP3, > ^ > lqt_ffmpeg.c:842:13: error: initializer element is not constant > lqt_ffmpeg.c:842:13: note: (near initialization for 'codecidmap_a[0].id') > lqt_ffmpeg.c:854:13: error: 'CODEC_ID_MP2' undeclared here (not in a > function) > .id = CODEC_ID_MP2, > ^ > lqt_ffmpeg.c:854:13: error: initializer element is not constant > lqt_ffmpeg.c:854:13: note: (near initialization for 'codecidmap_a[1].id') > lqt_ffmpeg.c:869:13: error: 'CODEC_ID_AC3' undeclared here (not in a > function) > .id = CODEC_ID_AC3, > ^ > lqt_ffmpeg.c:869:13: error: initializer element is not constant > lqt_ffmpeg.c:869:13: note: (near initialization for 'codecidmap_a[2].id') > lqt_ffmpeg.c:884:13: error: 'CODEC_ID_QDM2' undeclared here (not in a > function) > .id = CODEC_ID_QDM2, > ^ > lqt_ffmpeg.c:884:13: error: initializer element is not constant > lqt_ffmpeg.c:884:13: note: (near initialization for 'codecidmap_a[3].id') > lqt_ffmpeg.c:899:13: error: 'CODEC_ID_ALAC' undeclared here (not in a > function) > .id = CODEC_ID_ALAC, > ^ > lqt_ffmpeg.c:899:13: error: initializer element is not constant > lqt_ffmpeg.c:899:13: note: (near initialization for 'codecidmap_a[4].id') > lqt_ffmpeg.c:912:13: error: 'CODEC_ID_ADPCM_MS' undeclared here (not in a > function) > .id = CODEC_ID_ADPCM_MS, > ^ > lqt_ffmpeg.c:912:13: error: initializer element is not constant > lqt_ffmpeg.c:912:13: note: (near initialization for 'codecidmap_a[5].id') > lqt_ffmpeg.c:925:13: error: 'CODEC_ID_ADPCM_IMA_WAV' undeclared here (not in > a function) > .id = CODEC_ID_ADPCM_IMA_WAV, > ^ > lqt_ffmpeg.c:925:13: error: initializer element is not constant > lqt_ffmpeg.c:925:13: note: (near initialization for 'codecidmap_a[6].id') > make[3]: *** [lqt_ffmpeg.lo] Error 1 > Makefile:407: recipe for target 'lqt_ffmpeg.lo' failed > make[3]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins/ffmpeg' > make[2]: *** [all-recursive] Error 1 > Makefile:371: recipe for target 'all-recursive' failed > make[2]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins' > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > Makefile:444: recipe for target 'all-recursive' failed > make[1]: Leaving directory '/tmp/SBo/libquicktime-1.2.4' > Makefile:351: recipe for target 'all' failed > Failure encountered while building libquicktime: > libquicktime.SlackBuild return non-zero > > Do you want to proceed [n] > > ###### libquicktime ERRORS - END ##### > > ##### mlt ERRORS - START ##### > /usr/include/libavcodec/avcodec.h:4414:6: note: declared here > void av_free_packet(AVPacket *pkt); > ^ > make[2]: *** [producer_avformat.o] Error 1 > : recipe for target 'producer_avformat.o' failed > make[2]: Leaving directory '/tmp/SBo/mlt-6.0.0/src/modules/avformat' > make[1]: *** [all] Error 1 > Makefile:5: recipe for target 'all' failed > make[1]: Leaving directory '/tmp/SBo/mlt-6.0.0/src/modules' > make: *** [all] Error 1 > Makefile:9: recipe for target 'all' failed > Failure encountered while building mlt: > mlt.SlackBuild return non-zero > > Do you want to proceed [n] > > ##### mlt ERRORS - END ##### > > ##### kdenlive ERRORS - START ##### > CMake Error at > /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 > (message): > Could NOT find MLT (missing: MLT_LIBRARIES MLTPP_LIBRARIES MLT_INCLUDE_DIR > MLTPP_INCLUDE_DIR) (Required is at least version "0.9.0") > Call Stack (most recent call first): > /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388 > (_FPHSA_FAILURE_MESSAGE) > cmake/modules/FindMLT.cmake:59 (find_package_handle_standard_args) > CMakeLists.txt:67 (find_package) > > ##### kdenlive ERRORS - END ##### > > > _______________________________________________ > 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 fernando.lopezjr at gmail.com Tue Sep 13 22:41:29 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 13 Sep 2016 16:41:29 -0600 Subject: [Slackbuilds-users] shotcut md5 mismatch. Message-ID: Larry are you the current maintainer? Larry Hajali - Jan 7 email: "I was planning on making a shotcut slackbuild until I saw it was available on SBo. I can maintain shotcut. --Larry" this is the error i get: Found shotcut-debian7-x86_64-150810.tar.bz2 in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for shotcut-debian7-x86_64-150810.tar.bz2 ... FAILED! Expected: d0a8dcbaedca699c0a4c419527a9ff4a Found: 7550a599b195698397e1a994468b647a also, latest version is: 16.09 -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Sep 14 00:26:59 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 14 Sep 2016 07:26:59 +0700 Subject: [Slackbuilds-users] shotcut md5 mismatch. In-Reply-To: References: Message-ID: > Larry are you the current maintainer? > > Larry Hajali - Jan 7 email: > "I was planning on making a shotcut slackbuild until I saw it was available > on SBo. I can maintain shotcut. > --Larry" > > this is the error i get: > Found shotcut-debian7-x86_64-150810.tar.bz2 in /var/cache/sbopkg. > Checking MD5SUM: > MD5SUM check for shotcut-debian7-x86_64-150810.tar.bz2 ... FAILED! > Expected: d0a8dcbaedca699c0a4c419527a9ff4a > Found: 7550a599b195698397e1a994468b647a > > also, latest version is: 16.09 For now, the mismatch has been fixed on my branch Larry, please let me know if you push an update to your branch so that i can remove it from 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: From fernando.lopezjr at gmail.com Wed Sep 14 02:40:10 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 13 Sep 2016 20:40:10 -0600 Subject: [Slackbuilds-users] libquicktime Message-ID: Heinz can we modifiy the slackbuild for libquicktime? Fellype: This is how you fix libquicktime: linuxquestions . org/questions/slackware-14/unable-to-install-libquicktime-on-slackware64-14-1-a-4175534366/ -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Wed Sep 14 04:53:08 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 13 Sep 2016 22:53:08 -0600 Subject: [Slackbuilds-users] shotcut 16.09 error. Message-ID: I am getting a segmentation fault with shotcut 16.09 when running the application. Mlt seems to be causing the segmentation fault. Compiles with out problems. bash-4.3$ ./shotcut [Info ] Starting Shotcut version 16.09.13 [Info ] Linux version [Info ] number of logical cores = 8 [Info ] locale = QLocale(English, Latin, UnitedStates) [Info ] install dir = "/home/userx/Downloads/slackbuilds/shotcut/shotcut/src/shotcut/src/build/src" [Info ] device pixel ratio = 1 [Debug ] language "en_US" [Debug ] deinterlacer "onefield" [Debug ] external monitor "" [Debug ] GPU processing false [Debug ] interpolation "nearest" [Debug ] video mode "" [Debug ] realtime true [Debug ] begin [Debug ] end [Debug ] begin [Info ] OpenGL context version 4 5 [Debug ] begin Segmentation fault -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From larryhaja at gmail.com Wed Sep 14 06:43:42 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Tue, 13 Sep 2016 23:43:42 -0700 Subject: [Slackbuilds-users] shotcut md5 mismatch. In-Reply-To: References: Message-ID: On Tue, Sep 13, 2016 at 5:26 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Larry are you the current maintainer? > > > > Larry Hajali - Jan 7 email: > > "I was planning on making a shotcut slackbuild until I saw it was > available > > on SBo. I can maintain shotcut. > > --Larry" > > > I forgot. I'll take a look and test out a new shotcut version. Larry, please let me know if you push an update to your branch so that i > can remove it from my branch > > ok. I'll look at updating shotcut. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From larryhaja at gmail.com Wed Sep 14 06:51:08 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Tue, 13 Sep 2016 23:51:08 -0700 Subject: [Slackbuilds-users] shotcut 16.09 error. In-Reply-To: References: Message-ID: > > I am getting a segmentation fault with shotcut 16.09 when running the > application. Mlt seems to be causing the segmentation fault. Compiles with > out problems. > > bash-4.3$ ./shotcut > [Info ] Starting Shotcut > version 16.09.13 > [Info ] Linux version > [Info ] number of logical > cores = 8 > [Info ] locale = > QLocale(English, Latin, UnitedStates) > [Info ] install dir = > "/home/userx/Downloads/slackbuilds/shotcut/shotcut/ > src/shotcut/src/build/src" > [Info ] device pixel ratio = 1 > [Debug ] language "en_US" > [Debug ] deinterlacer "onefield" > [Debug ] external monitor "" > [Debug ] GPU processing false > [Debug ] interpolation "nearest" > [Debug ] video mode "" > [Debug ] realtime true > [Debug ] begin > [Debug ] end > [Debug ] begin > [Info ] OpenGL context version 4 > 5 > [Debug ] begin > Segmentation fault > -- > I get the same error when building a new version of shotcut. The problem is that shotcut is built with qt5 pulls in mlt plugin /usr/lib{,64}/mlt/libmltqt.so, which is built with qt. bash-4.3$ strace /usr/bin/shotcut .... open("/usr/lib64/mlt/libmltqt.so", O_RDONLY|O_CLOEXEC) = 17 read(17, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\331\0\0\0\0\0\0"..., 832) = 832 fstat(17, {st_mode=S_IFREG|0755, st_size=148664, ...}) = 0 mmap(NULL, 2243816, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 17, 0) = 0x7f1d374b5000 mprotect(0x7f1d374d7000, 2097152, PROT_NONE) = 0 mmap(0x7f1d376d7000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 17, 0x22000) = 0x7f1d376d7000 close(17) = 0 open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 17 fstat(17, {st_mode=S_IFREG|0644, st_size=240904, ...}) = 0 mmap(NULL, 240904, PROT_READ, MAP_PRIVATE, 17, 0) = 0x7f1d6009b000 close(17) = 0 open("/usr/lib64/libQtXml.so.4", O_RDONLY|O_CLOEXEC) = 17 read(17, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0p\r\1\0\0\0\0\0"..., 832) = 832 fstat(17, {st_mode=S_IFREG|0755, st_size=284360, ...}) = 0 mmap(NULL, 2379496, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 17, 0) = 0x7f1d37270000 mprotect(0x7f1d372b3000, 2097152, PROT_NONE) = 0 mmap(0x7f1d374b3000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 17, 0x43000) = 0x7f1d374b3000 close(17) = 0 open("/usr/lib64/libQtSvg.so.4", O_RDONLY|O_CLOEXEC) = 17 read(17, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0 I\1\0\0\0\0\0"..., 832) = 832 fstat(17, {st_mode=S_IFREG|0755, st_size=366000, ...}) = 0 mmap(NULL, 2461128, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 17, 0) = 0x7f1d37017000 mprotect(0x7f1d3706e000, 2093056, PROT_NONE) = 0 mmap(0x7f1d3726d000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 17, 0x56000) = 0x7f1d3726d000 close(17) = 0 open("/usr/lib64/libQtOpenGL.so.4", O_RDONLY|O_CLOEXEC) = 17 read(17, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\275\2\0\0\0\0\0"..., 832) = 832 fstat(17, {st_mode=S_IFREG|0755, st_size=1050384, ...}) = 0 mmap(NULL, 3149304, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 17, 0) = 0x7f1d36d16000 mprotect(0x7f1d36e0f000, 2093056, PROT_NONE) = 0 mmap(0x7f1d3700e000, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 17, 0xf8000) = 0x7f1d3700e000 mmap(0x7f1d37016000, 3576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f1d37016000 close(17) = 0 open("/usr/lib64/libQtGui.so.4", O_RDONLY|O_CLOEXEC) = 17 read(17, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\317\36\0\0\0\0\0"..., 832) = 832 fstat(17, {st_mode=S_IFREG|0755, st_size=11504728, ...}) = 0 mmap(NULL, 13613152, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 17, 0) = 0x7f1d3601a000 mprotect(0x7f1d36ac2000, 2093056, PROT_NONE) = 0 mmap(0x7f1d36cc1000, 335872, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 17, 0xaa7000) = 0x7f1d36cc1000 mmap(0x7f1d36d13000, 10336, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f1d36d13000 close(17) = 0 open("/usr/lib64/libQtCore.so.4", O_RDONLY|O_CLOEXEC) = 17 read(17, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0'\10\0\0\0\0\0"..., 832) = 832 fstat(17, {st_mode=S_IFREG|0755, st_size=3119528, ...}) = 0 mmap(NULL, 5217896, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 17, 0) = 0x7f1d35b20000 mprotect(0x7f1d35e0b000, 2093056, PROT_NONE) = 0 mmap(0x7f1d3600a000, 65536, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 17, 0x2ea000) = 0x7f1d3600a000 close(17) = 0 mprotect(0x7f1d376d7000, 4096, PROT_READ) = 0 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x7f1d7fd7b5c0} --- +++ killed by SIGSEGV +++ Segmentation fault bash-4.3$ ldd /usr/lib64/mlt/libmltqt.so | grep -i qt libQtXml.so.4 => /usr/lib64/libQtXml.so.4 (0x00007f136b346000) libQtSvg.so.4 => /usr/lib64/libQtSvg.so.4 (0x00007f136b0ec000) libQtOpenGL.so.4 => /usr/lib64/libQtOpenGL.so.4 (0x00007f136adeb000) libQtGui.so.4 => /usr/lib64/libQtGui.so.4 (0x00007f136a0ef000) libQtCore.so.4 => /usr/lib64/libQtCore.so.4 (0x00007f1369bf4000) Replacing --qimage-libdir=${QT4DIR}/qt/lib and --qimage-includedir=${QT4DIR}/qt/include with --qt-libdir=/usr/lib${LIBDIRSUFFIX} and --qt-includedir=/usr/include/qt5 in the mlt.slackbuild will build libmltqt.so plugin with qt5. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Sep 14 12:20:22 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 14 Sep 2016 19:20:22 +0700 Subject: [Slackbuilds-users] Updates - 20160914.1 Message-ID: <0265e391-57c3-190e-61c8-734380ff936c@slackbuilds.org> Hi guys, Sorry for unplanned schedule, but it contain an important update for flashplayer-plugins: https://helpx.adobe.com/security/products/flash-player/apsb16-29.html Wed Sep 14 12:08:01 UTC 2016 desktop/py3status: Updated for version 3.1. development/autogen: Updated for version 5.18.12. development/kicad: Updated for version 4.0.4. development/openjdk6: Updated for version 6b40. development/pycharm: Updated for version 2016.2.3. development/watchman: Updated for version 4.7.0. games/freeblocks: Added (puzzle game). games/mupen64plus-libretro: Updated for version 2016.09.12_5b86c3e. games/openmw: Updated for version 0.40.0. games/pinball: Use -j1. graphics/xmedcon: Fix VERSION. libraries/Botan: Updated for version 1.11.31. libraries/CherryPy: Updated for version 8.1.0. libraries/botocore: Updated for version 1.4.54. libraries/cryptopp: Updated for version 5.6.4. libraries/dietlibc: Switch to i586. libraries/libdsk: Updated for version 1.4.0. libraries/libhtp: Updated for version 0.5.22. libraries/libmp4v2: Update DOWNLOAD url. libraries/libofa: Update DOWNLOAD url. libraries/libowfat: Switch to i586. libraries/poco: Updated for version 1.7.5. libraries/tmdb3: Updated for version 0.7.2. multimedia/flashplayer-plugin: Updated for version 11.2.202.635. multimedia/shotcut: Update DOWNLOAD url. network/awscli: Updated for version 1.10.64. network/flexget: Updated for version 2.3.26. network/offlineimap: Updated for version 7.0.6. network/onioncat: Updated for version 0.2.2.r569. network/razor-agents: Switch to i586. network/suricata: Updated for version 3.1.2. network/telegram: Updated for version 0.10.6. network/urlwatch: Updated for version 2.5. office/hunspell-pl: Updated for version 20160907. office/jstock: Moved from misc + updated for version 1.0.7.16. office/openoffice.org: Fix build. perl/perl-Archive-Extract: Updated for version 0.78. perl/perl-CPANPLUS-Dist-Build: Updated for version 0.80. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.024. perl/perl-CPANPLUS: Updated for version 0.9160. perl/perl-DBIx-Simple: Switch to i586. perl/perl-Log-Message-Simple: Switch to i586. perl/perl-Log-Message: Switch to i586. perl/perl-Module-Pluggable: Switch to i586. perl/perl-Object-Accessor: Switch to i586. perl/perl-Package-Constants: Switch to i586. perl/perl-Term-ReadLine-Gnu: Updated for version 1.34. perl/perl-Term-UI: Switch to i586. perl/perl-WebService-MusicBrainz: Updated for version 0.94. perl/perl-cgi-minimal: Added (alternative to the CGI.pm module). python/Flask-Cors: Updated for version 3.0.2. python/Markdown: Updated for version 2.6.6. python/PyGithub: Updated for version 1.28. python/Unidecode: Updated for version 0.04.19. python/blinker: Updated for version 1.4. python/buildbot-slave: Updated for version 0.8.12. python/curtsies: Updated for version 0.2.9. python/feedgenerator: Updated for version 1.9. python/pelican: Updated for version 3.6.3. python/pendulum: Updated for version 0.6.0. python/pycryptopp: Updated for version 0.7.1. python/python-libsass: Updated for version 0.11.1. python/s3transfer: Updated for version 0.1.4. ruby/rbenv: Fix broken /etc/profile.d/rbenv.csh. ruby/ruby-build: Updated for version 20160913. ruby/rubygem-bundler: Updated for version 1.13.1. system/aespipe: Switch to i586. system/fzf: Added (A command-line fuzzy finder). system/jsawk: Added (like awk, but for JSON). system/jshon: Added (a fast JSON parser). system/mksh: Updated for version R53a. system/powerline-status: Added (ultimate statusline/prompt utility). system/ptop: Updated for version 1.0.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: From willysr at slackbuilds.org Wed Sep 14 12:46:11 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 14 Sep 2016 19:46:11 +0700 Subject: [Slackbuilds-users] Updates - 20160914.2 Message-ID: Wed Sep 14 12:35:58 UTC 2016 libraries/cryptopp: Removed cryptopp.pc. multimedia/flashplayer-plugin: Fix VERSION. +--------------------------+ -- 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: From alik at ejik.org Thu Sep 15 02:21:07 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Thu, 15 Sep 2016 05:21:07 +0300 Subject: [Slackbuilds-users] Updates - 20160914.1 Message-ID: <1473906067.13757.726205177.2E5BF0F8@webmail.messagingengine.com> > Sorry for unplanned schedule, but it contain an important update for > flashplayer-plugins: > https://helpx.adobe.com/security/products/flash-player/apsb16-29.html > multimedia/flashplayer-plugin: Updated for version 11.2.202.635. There is also 23.0.0.162 version, not affected by these bugs, http://labs.adobe.com/technologies/flashruntimes/flashplayer/ It works without problems for me. Best regards, Alexander From willysr at slackbuilds.org Thu Sep 15 03:12:46 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 15 Sep 2016 10:12:46 +0700 Subject: [Slackbuilds-users] Updates - 20160914.1 In-Reply-To: <1473906067.13757.726205177.2E5BF0F8@webmail.messagingengine.com> References: <1473906067.13757.726205177.2E5BF0F8@webmail.messagingengine.com> Message-ID: <1a1fe065-74c4-50cb-0687-6d75186c63ba@slackbuilds.org> >> multimedia/flashplayer-plugin: Updated for version 11.2.202.635. > > There is also 23.0.0.162 version, not affected by these bugs, > http://labs.adobe.com/technologies/flashruntimes/flashplayer/ Hi, Yes, it is the new BETA release of Flash Player I guess we should wait for stable releases -- 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: From fernando.lopezjr at gmail.com Thu Sep 15 17:44:35 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 15 Sep 2016 11:44:35 -0600 Subject: [Slackbuilds-users] qmc2 (0.50) broken homepage. Message-ID: slackbuilds . org/repository/14.2/games/qmc2/ -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Sep 15 22:00:37 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 16 Sep 2016 05:00:37 +0700 Subject: [Slackbuilds-users] qmc2 (0.50) broken homepage. In-Reply-To: References: Message-ID: > slackbuilds . org/repository/14.2/games/qmc2/ Fixed 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: From fernando.lopezjr at gmail.com Fri Sep 16 00:31:37 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 15 Sep 2016 18:31:37 -0600 Subject: [Slackbuilds-users] faac & twolame download times out. Message-ID: it never downloads the source code. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Sep 16 00:49:37 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 16 Sep 2016 07:49:37 +0700 Subject: [Slackbuilds-users] faac & twolame download times out. In-Reply-To: References: Message-ID: <668b9685-b031-3fc0-c146-27eae033431b@slackbuilds.org> > it never downloads the source code. Works fine here Sourceforge is using multiple mirrors probably mirror closes to you is down, so try to switch to other mirror sites -- 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: From fernando.lopezjr at gmail.com Fri Sep 16 01:57:30 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 15 Sep 2016 19:57:30 -0600 Subject: [Slackbuilds-users] faac & twolame download times out. In-Reply-To: <668b9685-b031-3fc0-c146-27eae033431b@slackbuilds.org> References: <668b9685-b031-3fc0-c146-27eae033431b@slackbuilds.org> Message-ID: oh okay.... thanks! On Thu, Sep 15, 2016 at 6:49 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > it never downloads the source code. > > Works fine here > Sourceforge is using multiple mirrors > probably mirror closes to you is down, so try to switch to other mirror > sites > > > -- > 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Fri Sep 16 16:19:44 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 16 Sep 2016 18:19:44 +0200 Subject: [Slackbuilds-users] letsencrypt.sh -> dehydrated In-Reply-To: References: Message-ID: <57DC1BA0.9050607@schoepfer.info> Hi, i maintain the package https://slackbuilds.org/repository/14.2/system/letsencrypt.sh/ which was renamed by upstream to "dehydrated" due to violation of the Let's Encrypts trademark policy. I don't know how to replace/rename the old package by the submission-form, so attached is the new package. Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: dehydrated.tar Type: application/octet-stream Size: 10240 bytes Desc: not available URL: From willysr at slackbuilds.org Fri Sep 16 16:21:01 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 16 Sep 2016 23:21:01 +0700 Subject: [Slackbuilds-users] letsencrypt.sh -> dehydrated In-Reply-To: <57DC1BA0.9050607@schoepfer.info> References: <57DC1BA0.9050607@schoepfer.info> Message-ID: <28fd25e2-a90e-68ed-856c-6eb768ca98d4@slackbuilds.org> > i maintain the package > https://slackbuilds.org/repository/14.2/system/letsencrypt.sh/ which was > renamed by upstream to "dehydrated" due to violation of the Let's > Encrypts trademark policy. > I don't know how to replace/rename the old package by the > submission-form, so attached is the new package. Hi Franzen, You will need to submit the new tarball via submission form as usual I will remove letsencrypt.sh package from our repository -- 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: From alik at ejik.org Fri Sep 16 16:56:10 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Fri, 16 Sep 2016 19:56:10 +0300 Subject: [Slackbuilds-users] letsencrypt.sh -> dehydrated In-Reply-To: <57DC1BA0.9050607@schoepfer.info> References: <57DC1BA0.9050607@schoepfer.info> Message-ID: <1474044970.538908.728013249.7B45F9BC@webmail.messagingengine.com> > so attached is the new package. Thank you! I built it without problems, but slackrepo produced a warning that there are "letsencrypt.sh" in slack-desc. Best regards, Alexander From ts at websafe.pl Fri Sep 16 18:02:46 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Fri, 16 Sep 2016 20:02:46 +0200 Subject: [Slackbuilds-users] SBo HowTo - Other Resources - SlackWiki.com down? Message-ID: <3e277701-5abf-a1fa-beba-11ea455ab894@websafe.pl> Hello, https://slackbuilds.org/howto/ refers to SlackWiki.com but the site is down? Is this a temporary problem? -- 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: From baildon.research at googlemail.com Fri Sep 16 18:41:13 2016 From: baildon.research at googlemail.com (David Spencer) Date: Fri, 16 Sep 2016 19:41:13 +0100 Subject: [Slackbuilds-users] SBo HowTo - Other Resources - SlackWiki.com down? In-Reply-To: <3e277701-5abf-a1fa-beba-11ea455ab894@websafe.pl> References: <3e277701-5abf-a1fa-beba-11ea455ab894@websafe.pl> Message-ID: > https://slackbuilds.org/howto/ refers to SlackWiki.com > but the site is down? Is this a temporary problem? ppr:kut said a few days ago (off list) that he was going to move SlackWiki.com to a new provider, so yes, it's temporary :) Thanks for checking with us :) -D. From willysr at slackbuilds.org Sat Sep 17 07:10:38 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Sep 2016 14:10:38 +0700 Subject: [Slackbuilds-users] libquicktime In-Reply-To: References: Message-ID: > Heinz can we modifiy the slackbuild for libquicktime? > > Fellype: > This is how you fix libquicktime: > linuxquestions . > org/questions/slackware-14/unable-to-install-libquicktime-on-slackware64-14-1-a-4175534366/ https://slackbuilds.org/faq/#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: From fernando.lopezjr at gmail.com Sat Sep 17 07:13:31 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 17 Sep 2016 01:13:31 -0600 Subject: [Slackbuilds-users] libquicktime In-Reply-To: References: Message-ID: I believe a note should be added to the package readme.... what do you guys think? On Sat, Sep 17, 2016 at 1:10 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Heinz can we modifiy the slackbuild for libquicktime? > > > > Fellype: > > This is how you fix libquicktime: > > linuxquestions . > > org/questions/slackware-14/unable-to-install- > libquicktime-on-slackware64-14-1-a-4175534366/ > > https://slackbuilds.org/faq/#multilib > > > -- > 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Sep 17 07:14:36 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Sep 2016 14:14:36 +0700 Subject: [Slackbuilds-users] libquicktime In-Reply-To: References: Message-ID: > I believe a note should be added to the package readme.... what do you guys > think? It's already mentioned in FAQ -- 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: From klaatu at member.fsf.org Sat Sep 17 07:33:28 2016 From: klaatu at member.fsf.org (Klaatu) Date: Sat, 17 Sep 2016 19:33:28 +1200 Subject: [Slackbuilds-users] libquicktime In-Reply-To: References: Message-ID: I've only been partly following this thread, but I have compiled libquicktime with ffmpeg 3.1.1 on my multilib system. Patch attached. Maybe it will help someone. I have no memory of where I obtained this patch...maybe borrowed from Arch. -klaatu On 17/09/16 19:10, Willy Sudiarto Raharjo wrote: >> Heinz can we modifiy the slackbuild for libquicktime? >> >> Fellype: >> This is how you fix libquicktime: >> linuxquestions . >> org/questions/slackware-14/unable-to-install-libquicktime-on-slackware64-14-1-a-4175534366/ > > https://slackbuilds.org/faq/#multilib > > > > > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: libquicktime-ffmpeg3.patch Type: text/x-patch Size: 32060 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Sep 17 07:39:28 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Sep 2016 14:39:28 +0700 Subject: [Slackbuilds-users] Updates - 20160917.1 Message-ID: <654a9f50-3fbd-42d2-da93-df0bd6982937@slackbuilds.org> Sat Sep 17 07:23:50 UTC 2016 audio/ncmpcpp: Updated for version 0.7.4. audio/puddletag: Updated for version 1.1.1 + new maintainer. desktop/gtk-theme-Greybird: Updated for version 3.20.1. development/autogen: Fix README. development/guile1.8: Disable static. games/GLupeN64: Updated for version 2016.09.15_6baff60. games/qmc2: Update HOMEPAGE. gis/qmapshack: Updated for version 1.7.1. graphics/leocad: Updated for version 0.83.1. libraries/cryptopp: Bring back required .pc file. libraries/jansson: Updated for version 2.8 libraries/libxnvctrl: Added (NVIDIA NV-CONTROL X extension). libraries/live555: Updated for version 2016.09.12 multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 52.0. network/aria2: Updated for version 1.27.0. network/flexget: Updated for version 2.3.27. network/glusterfs: Added (scalable network filesystem). network/opensmtpd: Updated for version 6.0.0p1. network/tor: Updated for version 0.2.8.7. network/vivaldi: Updated for version 1.4.589.15. network/yadifa: Added (Yet Another DNS Implementation For All). network/youtube-dl: Updated for version 2016.09.15. office/hunspell-de: Added (German hunspell dictionaries). office/task: Updated for version 2.5.1. office/taskjuggler: Updated for version 3.6.0. office/timetrap: Updated for version 1.12.0. perl/perl-Sidef: Updated for version 2.31. python/python-editor: Added (Programmatically open an editor). python/pyzmq: Updated for version 15.4.0. system/USBdev: Added (Recognition tool of USB devices). system/fzf: Fix VERSION. system/gradm: Updated for version 3.1_201608131257. system/letsencrypt.sh: Removed (letsencrypt trademark violation). system/spl-solaris: Updated for version 0.6.5.8. system/vifm: Updated for version 0.8.2. system/zfs-on-linux: Updated for version 0.6.5.8. +--------------------------+ -- 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: From slackbuilds at schoepfer.info Sat Sep 17 07:40:37 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 17 Sep 2016 09:40:37 +0200 Subject: [Slackbuilds-users] letsencrypt.sh -> dehydrated In-Reply-To: <1474044970.538908.728013249.7B45F9BC@webmail.messagingengine.com> References: <57DC1BA0.9050607@schoepfer.info> <1474044970.538908.728013249.7B45F9BC@webmail.messagingengine.com> Message-ID: > I built it without problems, but slackrepo produced a warning that > there > are "letsencrypt.sh" in slack-desc. Thanks for testing it :-) , it is fixed and submitted to SBo now. Johannes From kingbeowulf at gmail.com Sat Sep 17 20:59:13 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 17 Sep 2016 13:59:13 -0700 Subject: [Slackbuilds-users] libquicktime In-Reply-To: References: Message-ID: <922aa81c-470a-eafc-0bb1-e5d2cb1fcb0c@gmail.com> On 09/17/2016 12:33 AM, Klaatu wrote: > I've only been partly following this thread, but I have compiled > libquicktime with ffmpeg 3.1.1 on my multilib system. Patch attached. > Maybe it will help someone. > > I have no memory of where I obtained this patch...maybe borrowed from Arch. > > -klaatu > > > > > On 17/09/16 19:10, Willy Sudiarto Raharjo wrote: >>> Heinz can we modifiy the slackbuild for libquicktime? >>> >>> Fellype: >>> This is how you fix libquicktime: >>> linuxquestions . >>> org/questions/slackware-14/unable-to-install-libquicktime-on-slackware64-14-1-a-4175534366/ >> >> https://slackbuilds.org/faq/#multilib >> >> >> libquicktime's CVS repo on Sourceforge has the patch from about 9 month ago. http://libquicktime.cvs.sourceforge.net/viewvc/libquicktime/libquicktime/plugins/ffmpeg/video.c?view=log&r1=1.131&pathrev=HEAD Also Arch has both for ffmpeg2 and ffmpeg3. https://git.archlinux.org/svntogit/community.git/tree/trunk?h=packages/libquicktime So might be time to update the script on SBo (again). -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From sombragris at sombragris.org Sat Sep 17 21:39:58 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sat, 17 Sep 2016 17:39:58 -0400 Subject: [Slackbuilds-users] BUG: Bibletime 20.10.1 build fails with qt 5.7x Message-ID: <0q93i.2068104bf3.20160917173958.4378abdc@loli.sombragris.org> Hi: Bibletime 2.10.1 (the SlackBuilds.org version) building fails under qt 5.7. I know that the Qt version required by bibletime is Qt4 IIRC, but Qt5 is even in SBo and I think that 2.10.x fails to pick the correct Qt version and thus compilation fails. This is fixed upstream in 2.11x branch, which now requires Qt5. I was able to edit the SlackBuild for bibletime-2.11_rc2 and I got a successful compilation and package which runs fine on Qt5. (Just editing the version number and the name of the source file, and changing README for README.md on the /usr/doc package did the trick). Thus, I would propose any of the following: a) make sure bibletime 2.10.1 (current version) picks Qt4; or b) upgrade to 2.11x branch and include Qt5 as a requirement. Thank you! Below I paste the building output from the unmodified SlackBuild. Best regards, Eduardo [ 34%] Building CXX object CMakeFiles/bibletime.dir/src/backend/drivers/cswordmoduleinfo.cpp.o In file included from /usr/include/qt5/QtCore/qchar.h:43:0, from /usr/include/qt5/QtCore/qhash.h:44, from /usr/include/qt5/QtCore/QHash:1, from /tmp/SBo/bibletime-2.10.1/src/backend/managers/clanguagemgr.h:15, from /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.h:15, from /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:10: /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp: In constructor ?CSwordModuleInfo::CSwordModuleInfo(sword::SWModule*, CSwordBackend&, CSwordModuleInfo::ModuleType)?: /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:57:17: error: expected primary-expression before ?do? : m_module((Q_ASSERT(module), module)), ^ /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:57:17: error: expected ?)? before ?do? /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:57:41: error: expression list treated as compound expression in mem-initializer [-fpermissive] : m_module((Q_ASSERT(module), module)), ^ /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:54:1: error: uninitialized reference member in ?class2 cronicas 36:21 CSwordBackend&? [-fpermissive] CSwordModuleInfo::CSwordModuleInfo(sword::SWModule * module, ^ In file included from /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:10:0: /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.h:454:21: note: ?CSwordBackend& CSwordModuleInfo::m_backend? should be initialized CSwordBackend & m_backend; ^ /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:57:42: error: expected ?{? before ?)? token : m_module((Q_ASSERT(module), module)), ^ /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp: At global scope: /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:55:52: warning: unused parameter ?backend? [-Wunused-parameter] CSwordBackend & backend, ^ /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:56:47: warning: unused parameter ?type? [-Wunused-parameter] ModuleType type) ^ /tmp/SBo/bibletime-2.10.1/src/backend/drivers/cswordmoduleinfo.cpp:57:42: error: expected unqualified-id before ?)? token : m_module((Q_ASSERT(module), module)), ^ CMakeFiles/bibletime.dir/build.make:934: recipe for target 'CMakeFiles/bibletime.dir/src/backend/drivers/cswordmoduleinfo.cpp.o' failed make[2]: *** [CMakeFiles/bibletime.dir/src/backend/drivers/cswordmoduleinfo.cpp.o] Error 1 CMakeFiles/Makefile2:818: recipe for target 'CMakeFiles/bibletime.dir/all' failed make[1]: *** [CMakeFiles/bibletime.dir/all] Error 2 Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 -- 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 Sun Sep 18 01:00:44 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 18 Sep 2016 08:00:44 +0700 Subject: [Slackbuilds-users] BUG: Bibletime 20.10.1 build fails with qt 5.7x In-Reply-To: <0q93i.2068104bf3.20160917173958.4378abdc@loli.sombragris.org> References: <0q93i.2068104bf3.20160917173958.4378abdc@loli.sombragris.org> Message-ID: <375e7aeb-b6d1-b1c7-0925-11044d49d7f5@slackbuilds.org> > Bibletime 2.10.1 (the SlackBuilds.org version) building fails under qt > 5.7. > > I know that the Qt version required by bibletime is Qt4 IIRC, but Qt5 > is even in SBo and I think that 2.10.x fails to pick the correct Qt > version and thus compilation fails. > > This is fixed upstream in 2.11x branch, which now requires Qt5. > > I was able to edit the SlackBuild for bibletime-2.11_rc2 and I got a > successful compilation and package which runs fine on Qt5. (Just > editing the version number and the name of the source file, and > changing README for README.md on the /usr/doc package did the trick). > > Thus, I would propose any of the following: > > a) make sure bibletime 2.10.1 (current version) picks Qt4; or > > b) upgrade to 2.11x branch and include Qt5 as a requirement. > > Thank you! Thanks for the report Eduardo, For now, i have updated the README to include a note when building bibletime. As for the decision to upgrade to 2.11 or to edit the SlackBuild, i will leave that to the maintainer (Tim). -- 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: From willysr at slackbuilds.org Mon Sep 19 01:00:23 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 19 Sep 2016 08:00:23 +0700 Subject: [Slackbuilds-users] Early notification for new libwebp Message-ID: <58276536-e02b-537e-2e71-4f478655c027@slackbuilds.org> Hi all This email act as an early notification for those installing libwebp and or packages that depends on libwebp. An updated libwebp has been approved in my branch and soon it will be merged to master in the next public update. Upgrading to the new version will require you to rebuilt all packages that depends on libwep. Here are the list of the packages that have first level hard dep of libwebp: games/unvanquished graphics/openimageio graphics/vips libraries/webkit2gtk libraries/webkitgtk libraries/webkitgtk3 multimedia/vlc there are so many packages that depends on some of the libraries mentioned above, so there could be more packages affected. If you have a working packages suddenly no longer work after upgrading libwebp, rebuilding all deps will be your first options before reporting a bug in the list. 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: From larryhaja at gmail.com Mon Sep 19 01:21:25 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Sun, 18 Sep 2016 18:21:25 -0700 Subject: [Slackbuilds-users] Early notification for new libwebp In-Reply-To: <58276536-e02b-537e-2e71-4f478655c027@slackbuilds.org> References: <58276536-e02b-537e-2e71-4f478655c027@slackbuilds.org> Message-ID: qt5 is another package if built against optional libwebp dependency. --Larry On Sun, Sep 18, 2016 at 6:00 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Hi all > > This email act as an early notification for those installing libwebp and > or packages that depends on libwebp. > > An updated libwebp has been approved in my branch and soon it will be > merged to master in the next public update. > > Upgrading to the new version will require you to rebuilt all packages > that depends on libwep. Here are the list of the packages that have > first level hard dep of libwebp: > games/unvanquished > graphics/openimageio > graphics/vips > libraries/webkit2gtk > libraries/webkitgtk > libraries/webkitgtk3 > multimedia/vlc > > there are so many packages that depends on some of the libraries > mentioned above, so there could be more packages affected. > If you have a working packages suddenly no longer work after upgrading > libwebp, rebuilding all deps will be your first options before reporting > a bug in the list. > > Thanks > > -- > 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: From ryan.q at linux.com Mon Sep 19 17:20:29 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 19 Sep 2016 10:20:29 -0700 Subject: [Slackbuilds-users] Anyone interested in taking higan? Message-ID: Seems that Gabriel is no longer able to maintain it. It is currently broken because the source link has changed, and there are some new versions too! -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Mon Sep 19 20:17:17 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 19 Sep 2016 22:17:17 +0200 Subject: [Slackbuilds-users] Anyone interested in taking higan? In-Reply-To: References: Message-ID: <3354ca2953b6481a3191266a53a0fcdc@schoepfer.info> > It is currently broken because the source link has changed, and there > are some new versions too! I'll have a look at it. The newest version comes 7zip-compressed. What's better, add a requirement to p7zip just to be able to uncompress the sources, or repack/provide the sources xz-compressed by a trustworthy SBo admin? Johannes From ryan.q at linux.com Mon Sep 19 20:19:16 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 19 Sep 2016 13:19:16 -0700 Subject: [Slackbuilds-users] Anyone interested in taking higan? In-Reply-To: <3354ca2953b6481a3191266a53a0fcdc@schoepfer.info> References: <3354ca2953b6481a3191266a53a0fcdc@schoepfer.info> Message-ID: > I'll have a look at it. Thanks! > The newest version comes 7zip-compressed. What's better, add a requirement to p7zip just to be able to uncompress the sources, > or repack/provide the sources xz-compressed by a trustworthy SBo admin? What about getting the source here? https://gitlab.com/higan/higan -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Mon Sep 19 23:36:43 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 20 Sep 2016 01:36:43 +0200 Subject: [Slackbuilds-users] Anyone interested in taking higan? In-Reply-To: References: <3354ca2953b6481a3191266a53a0fcdc@schoepfer.info> Message-ID: >> The newest version comes 7zip-compressed. What's better, add a > requirement to p7zip just to be able to uncompress the sources, >> or repack/provide the sources xz-compressed by a trustworthy SBo > admin? > > What about getting the source here? > > https://gitlab.com/higan/higan I took the official tarball and made a requirement for p7zip, as the release is from august 2016 and the git-repository doesn't provide a release. Attached is the updated buildscript, but i don't want to maintain it in the future because i got headache on creating it. I will use mednafen if i want to play mario ;-) @SBo-admins: Should i submit it, even if i'm not the new maintainer? Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: higan.tar Type: application/x-tar Size: 20480 bytes Desc: not available URL: From bra_ket at zoho.com Tue Sep 20 16:16:50 2016 From: bra_ket at zoho.com (braket) Date: Tue, 20 Sep 2016 18:16:50 +0200 Subject: [Slackbuilds-users] racket slackbuild update Message-ID: <1474388210.3121.7.camel@zoho.com> Hi! The racket version used by the slackbuild [1] is outdated (6.4). Since July, the 6.6 version is available. My other problem is, that the slackbuild script byte-compiles the components written in racket during the package building. This approach has no real benefit over using the "unix source + built packages" distribution [2] provided by the racket project, but makes the compilation time longer, especially on weaker systems. [1] https://slackbuilds.org/repository/14.2/development/racket/? [2]?https://mirror.racket-lang.org/installers/6.6/racket-6.6-src-builtp kgs.tgz Therefore I propose the changes attached in the patch file. M?t? -------------- next part -------------- A non-text attachment was scrubbed... Name: racket.diff Type: text/x-patch Size: 990 bytes Desc: not available URL: From matteo.bernardini at gmail.com Tue Sep 20 16:20:36 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 20 Sep 2016 18:20:36 +0200 Subject: [Slackbuilds-users] racket slackbuild update In-Reply-To: <1474388210.3121.7.camel@zoho.com> References: <1474388210.3121.7.camel@zoho.com> Message-ID: 2016-09-20 18:16 GMT+02:00 braket : > Hi! > > The racket version used by the slackbuild [1] is outdated (6.4). Since > July, the 6.6 version is available. > > My other problem is, that the slackbuild script byte-compiles the > components written in racket during the package building. This > approach has no real benefit over using the "unix source + built > packages" distribution [2] provided by the racket project, but makes > the compilation time longer, especially on weaker systems. > > [1] https://slackbuilds.org/repository/14.2/development/racket/ > [2] https://mirror.racket-lang.org/installers/6.6/racket-6.6-src-builtp > kgs.tgz > > Therefore I propose the changes attached in the patch file. > > M?t? Hi M?t?, I'll forward this to the maintainer for his consideration: these are matters on which he only should decide the best course of action. Matteo From bra_ket at zoho.com Tue Sep 20 16:30:20 2016 From: bra_ket at zoho.com (braket) Date: Tue, 20 Sep 2016 18:30:20 +0200 Subject: [Slackbuilds-users] racket slackbuild update In-Reply-To: References: <1474388210.3121.7.camel@zoho.com> Message-ID: <1474389020.8905.3.camel@zoho.com> > Hi M?t?, > > I'll forward this to the maintainer for his consideration: these are > matters on which he only should decide the best course of action. > > Matteo >? Thanks, but i have already written an email to Markus 2 weeks ago, but he didn't responded yet. From matteo.bernardini at gmail.com Tue Sep 20 16:36:48 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 20 Sep 2016 18:36:48 +0200 Subject: [Slackbuilds-users] racket slackbuild update In-Reply-To: <1474389020.8905.3.camel@zoho.com> References: <1474388210.3121.7.camel@zoho.com> <1474389020.8905.3.camel@zoho.com> Message-ID: 2016-09-20 18:30 GMT+02:00 braket : >> Hi M?t?, >> >> I'll forward this to the maintainer for his consideration: these are >> matters on which he only should decide the best course of action. >> >> Matteo >> > Thanks, but i have already written an email to Markus 2 weeks ago, but > he didn't responded yet. let's wait a little more. Matteo From Jim.Diamond at acadiau.ca Thu Sep 22 13:29:52 2016 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Thu, 22 Sep 2016 10:29:52 -0300 Subject: [Slackbuilds-users] webkitgtk vs. webkit2gtk Message-ID: <20160922132952.GA32408@jdiamond-nb.acadiau.ca> There are slackbuilds by the names webkitgtk and webkit2gtk which seem to be more or less the same thing ("webkitgtk" with no "2"), with versions of varying degrees of age. Can anyone (*cough*, Willy and Erik, *cough*) comment on -> why there are two versions in SBo? -> do we really want both versions? -> does one version subsume the other (except for some SBos which want one and some which want the other)? -> is it possible to combine these into one all-singing, all-dancing version which makes all the dependent packages happy? Thanks. Jim From andreas.guldstrand at gmail.com Thu Sep 22 13:58:35 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Thu, 22 Sep 2016 15:58:35 +0200 Subject: [Slackbuilds-users] webkitgtk vs. webkit2gtk In-Reply-To: <20160922132952.GA32408@jdiamond-nb.acadiau.ca> References: <20160922132952.GA32408@jdiamond-nb.acadiau.ca> Message-ID: As I understand it, webkitgtk underwent major internal changes between versions 1 and 2, and because of that, any project you write for version 1 will be incompatible with version 2 and vice versa. Since SBo probably wants to be able to support software built against either version, it makes sense that both of them are around. And no, it's not useful to combine them as far as I'm aware. On 22 September 2016 at 15:29, Jim Diamond wrote: > There are slackbuilds by the names > webkitgtk > and > webkit2gtk > which seem to be more or less the same thing ("webkitgtk" with no > "2"), with versions of varying degrees of age. > > Can anyone (*cough*, Willy and Erik, *cough*) comment on > -> why there are two versions in SBo? > -> do we really want both versions? > -> does one version subsume the other (except for some SBos which > want one and some which want the other)? > -> is it possible to combine these into one all-singing, all-dancing > version which makes all the dependent packages happy? > > Thanks. > > 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 willysr at slackbuilds.org Thu Sep 22 13:59:25 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 22 Sep 2016 20:59:25 +0700 Subject: [Slackbuilds-users] webkitgtk vs. webkit2gtk In-Reply-To: <20160922132952.GA32408@jdiamond-nb.acadiau.ca> References: <20160922132952.GA32408@jdiamond-nb.acadiau.ca> Message-ID: > There are slackbuilds by the names > webkitgtk > and > webkit2gtk > which seem to be more or less the same thing ("webkitgtk" with no > "2"), with versions of varying degrees of age. > > Can anyone (*cough*, Willy and Erik, *cough*) comment on > -> why there are two versions in SBo? > -> do we really want both versions? > -> does one version subsume the other (except for some SBos which > want one and some which want the other)? webkitgtk is the legacy version, while webkit2gtk is the new version. Even though both have same 2 as major version, it has different APIs we do need both as there are apps which requires the legacy version while others have migrated to the new API. both can be installed at the same time so it's safe to do it. > -> is it possible to combine these into one all-singing, all-dancing > version which makes all the dependent packages happy? Building one package is already very time consuming. I can't imagine people will have to wait longer to get a monstrous package in which 50% of it are not used if they have a package that depends on one of them. -- 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: From bch at shroggslodge.freeserve.co.uk Thu Sep 22 14:03:31 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Thu, 22 Sep 2016 15:03:31 +0100 Subject: [Slackbuilds-users] webkitgtk vs. webkit2gtk In-Reply-To: <20160922132952.GA32408@jdiamond-nb.acadiau.ca> References: <20160922132952.GA32408@jdiamond-nb.acadiau.ca> Message-ID: Hi there I asked a similar question previously on linuxquestions. Maybe it will answer for you too. Best wishes https://www.linuxquestions.org/questions/slackware-14/what-is-the-difference-between-webkitgtk-and-webkitgtk2-and-can-they-co-exist-please-4175589659/ Habs On 22 September 2016 at 14:29, Jim Diamond wrote: > There are slackbuilds by the names > webkitgtk > and > webkit2gtk > which seem to be more or less the same thing ("webkitgtk" with no > "2"), with versions of varying degrees of age. > > Can anyone (*cough*, Willy and Erik, *cough*) comment on > -> why there are two versions in SBo? > -> do we really want both versions? > -> does one version subsume the other (except for some SBos which > want one and some which want the other)? > -> is it possible to combine these into one all-singing, all-dancing > version which makes all the dependent packages happy? > > Thanks. > > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Diamond at acadiau.ca Thu Sep 22 14:35:57 2016 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Thu, 22 Sep 2016 11:35:57 -0300 Subject: [Slackbuilds-users] webkitgtk vs. webkit2gtk In-Reply-To: References: <20160922132952.GA32408@jdiamond-nb.acadiau.ca> Message-ID: <20160922143557.GC18649@jdiamond-nb.acadiau.ca> On Thu, Sep 22, 2016 at 15:03 (+0100), bch at shroggslodge.freeserve.co.uk wrote: > Hi there > I asked a similar question previously on linuxquestions. Maybe it will > answer for you too. > Best wishes > https://www.linuxquestions.org/questions/slackware-14/what-is-the-difference-between-webkitgtk-and-webkitgtk2-and-can-they-co-exist-please-4175589659/ Habs (and others), thanks for the clarifications. Upon first scan of https://webkitgtk.org/ and then a second scan as well, I'm not sure this information is very clearly presented. However, now I know. Cheers. Jim From willysr at slackbuilds.org Sat Sep 24 00:30:25 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 24 Sep 2016 07:30:25 +0700 Subject: [Slackbuilds-users] Updates - 20160924.1 Message-ID: <1e88a69a-0ee9-8009-a354-7c3d5076500e@slackbuilds.org> Hi all, as mentioned before, this batch of update brings an update to libwebp which is used in other packages as hard and soft dependencies. If you have packages that depends on: webkitgtk{3}, webkit2gtk, qt5, qt5-webkit, openimageio, vlc, and vips, you may need to rebuilt them to pick the correct libwebp version. Also, we see a lot of maintainers are now switching to i586 for x86. Big thanks for that, but we still have around 4300+ scripts that are still using i486 for x86 architecture. For new submission, please use the new template which already use i586. Sat Sep 24 00:06:42 UTC 2016 academic/bibletime: Add NOTE about qt5. academic/labplot2: Updated for version 2.3.0. academic/reduce-algebra: Updated for version 20160913svn3783. audio/sayonara-player: Added (small, clear and fast audio player). desktop/alarm: Switch to i586. desktop/fvwm-crystal: Switch to i586. desktop/gr1d: Switch to i586. desktop/matrixgl: Switch to i586. desktop/notion: Switch to i586. desktop/ptwit: Updated for version 0.2. desktop/qtile: Switch to i586. desktop/screensaver-icon: Switch to i586. desktop/ssr: Fix build problem. desktop/sun: Switch to i586. desktop/xfce4-battery-plugin: Switch to i586. desktop/xfce4-fsguard-plugin: Switch to i586. development/Cython-Kivy: Switch to i586. development/FreeBASIC: Switch to i586. development/bpython: Switch to i586. development/extra-cmake-modules: Added (CMake extra modules). development/git-lfs: Switch to i586. development/gitstats: Switch to i586. development/ipython: Add new optional dependency. development/libretro-samples: Added (libretro API samples). development/meld: Switch to i586. development/mysql-workbench: Switch to i586. development/pandas: Switch to i586. development/poedit: Updated for version 1.8.9. development/sublime_text: Updated for version 3.1.14. games/3D-Fasteroids: Switch to i586. games/BeastieWorker-levels: Switch to i586. games/BeastieWorker: Switch to i586. games/OpenXcom: Switch to i586. games/Sokoban: Switch to i586. games/SpaceZero: Switch to i586. games/ardentryst: Switch to i586. games/arnold-cpc: Switch to i586. games/arx-libertatis: Switch to i586. games/asc: Switch to i586. games/assaultcube-reloaded: Switch to i586. games/astromenace: Switch to i586. games/berusky-data: Switch to i586. games/berusky2-data: Switch to i586. games/berusky2: Switch to i586. games/berusky: Switch to i586. games/bomberclone: Switch to i586. games/boswars: Switch to i586. games/caph: Switch to i586. games/cgames: Switch to i586. games/conquest: Switch to i586. games/crossfire-client: Switch to i586. games/curseofwar: Switch to i586. games/cyphesis: Switch to i586 and update HOMEPAGE. games/doomsday: Switch to i586. games/fifengine: Switch to i586. games/flare-game: Switch to i586. games/flare: Switch to i586. games/freedroid: Switch to i586. games/freeorion: Switch to i586. games/galaxyv2: Switch to i586. games/game_1945: Switch to i586. games/glob2: Switch to i586 and merge patches. games/goonies: Switch to i586. games/haxima-nazghul: Switch to i586. games/hexglass: Switch to i586. games/higan: Updated for version 101. games/javacpc: Switch to i586. games/libretro-mgba: Updated for version 2016.09.19_def5a46. games/mars: Switch to i586. games/mednafen: Updated for version 0.9.39.2. games/minetest: Switch to i586. games/minetest_game: Switch to i586. games/mog: Switch to i586. games/nFlood: Switch to i586. games/nSnake: Switch to i586. games/ninvaders: Switch to i586. games/nlarn: Switch to i586. games/npush: Switch to i586. games/openclonk: Switch to i586. games/openlierox: Switch to i586. games/openspades: Switch to i586. games/openttd: Updated for version 1.6.1. games/pybik: Switch to i586. games/pychess: Switch to i586. games/roadfighter: Switch to i586. games/simplesok: Switch to i586. games/smashbattle: Switch to i586. games/sokowiz: Switch to i586. games/stormbaancoureur: Added (Simulated Obstacle Course). games/sumwars: Switch to i586. games/sumwars: Switch to i586. games/teeworlds: Switch to i586. games/term2048: Switch to i586. games/tome4: Switch to i586. games/triplea: Switch to i586. games/tty-solitaire: Switch to i586. games/tuxfootball: Switch to i586. games/tworld: Switch to i586. games/unknown-horizons: Switch to i586. games/unnethack: Switch to i586. games/unvanquished: Switch to i586. games/vms-empire: Switch to i586. games/xcpc: Switch to i586. games/xpilot-ng: Switch to i586. games/yetris: Switch to i586. games/znake: Switch to i586. games/zod-engine: Switch to i586. graphics/digikam: Switch to i586. graphics/enblend-enfuse: Updated for version 4.2. graphics/jp2a: Switch to i586. libraries/Kivy: Switch to i586. libraries/SFML: Update script. libraries/botocore: Updated for version 1.4.55. libraries/cffi: Updated for version 1.8.3. libraries/gssdp: Updated for version 1.0.0. libraries/gupnp: Updated for version 1.0.0. libraries/lensfun: Switch to i586. libraries/libast: Switch to i586. libraries/libkface: Update DOWNLOAD url + switch to i586. libraries/libkgeomap4: Update DOWNLOAD url + switch to i586. libraries/libkvkontakte: Switch to i586. libraries/liblqr: Switch to i586. libraries/libpgf: Switch to i586. libraries/libwebp: Updated for version 0.5.1. libraries/live555: Updated for version 2016.09.22 libraries/plib: Switch to i586. libraries/pymediainfo: Updated for version 2.5.1. libraries/python3-dvdvideo: Added (Video DVD reader library). libraries/qt5: Switch to i586. libraries/webkit2gtk: Updated for version 2.12.5. libraries/webkitgtk3: Switch to i586. libraries/webkitgtk: Switch to i586. libraries/wxGTK3: Switch to i586. libraries/wxGTK: Switch to i586. misc/no-more-secrets: Added (Sneakers effect). multimedia/spotify: Updated for version 1.0.38.171.g5e1cd7b2. multimedia/vlsub: Switch to i586. multimedia/yarock: Switch to i586. network/BitchX: Switch to i586. network/CherryMusic: Updated for version 0.38.0. network/ClusterSSH: Updated for version 4.07. network/Electrum: Switch to i586. network/PaleMoon: Added (web browser). network/awscli: Updated for version 1.10.65. network/flexget: Updated for version 2.3.28. network/netsniff-ng: Switch to i586. network/otter: Switch to i586. network/pastebincl: Switch to i586. network/r8168: Updated for version 8.042. network/sabnzbd: Updated for version 1.1.0. network/sieve-connect: Updated for version 0.88. network/speedtest-cli: Switch to i586. network/telegram: Updated for version 0.10.7. network/tor-browser: Updated for version 6.0.5. network/vivaldi: Updated for version 1.4.589.29. network/weathercli: Switch to i586. network/youtube-dl: Updated for version 2016.09.18. network/zmap: Switch to i586. office/alot: Added (MUA based on notmuch mail). office/calibre: Updated for version 2.68.0 office/mu: Updated for version 0.9.16. office/notmuch: Updated for version 0.22.2. office/sc-im: Added (spreadsheet). perl/perl-Math-Complex_C-L: Added (interface to C's long double). perl/perl-Math-Complex_C-Q: Added (interface to C's __complex128). perl/perl-Math-Complex_C: Added (interface to C's double precision). perl/perl-Math-Decimal64: Added (interface to C's _Decimal64). perl/perl-Math-GMPf: Added (interface to GMP library's FP). perl/perl-Math-GMPq: Update README. perl/perl-Math-GMPz: Update README. perl/perl-Math-LongDouble: Added (interface to C's long double). perl/perl-Math-MPC: Update README. perl/perl-Math-MPFR: Update README. perl/perl-Module-ScanDeps: Updated for version 1.22. perl/perl-PAR: Updated for version 1.011. python/Flask: Switch to i586. python/Scrapy: Updated for version 1.1.3. python/click-default-group: Added (click extends). python/click: Switch to i586. python/colored: Updated for version 1.3.1. python/invoke: Updated for version 0.13.0. python/monty: Updated for version 0.9.4. python/numpydoc: Updated for version 0.6.0. python/pendulum: Updated for version 0.6.1. python/psutil: Updated for version 4.3.1 python/pygrametl: Updated for version 2.5.0. python/python-libnacl: Updated for version 1.5.0 python/python-libtmux: Updated for version 0.6.0. python/regex: Updated for version 2016.09.22. python/requests-oauthlib: Updated for version 0.7.0. python/xtermcolor: Switch to i586. ruby/sequel: Updated for version 4.38.0. system/Attic: Switch to i586. system/Eterm: Switch to i586. system/TLP: Updated for version 0.9. system/brasero: Switch to i586. system/caprice32: Switch to i586. system/dehydrated: Added (letsencrypt/acme client). system/em: Switch to i586. system/fakeroot: Re-adding copyright note. system/fr: Switch to i586. system/gentoo: Switch to i586. system/guix: Updated for version 0.11.0. system/intel-microcode: Updated for version 20160714. system/iucode_tool: Updated for version 2.0. system/linkchecker: Switch to i586. system/openrc: Updated for version 0.21.7. system/porg: Updated for version 0.10. system/pstate-frequency: Added (Control Intel p-state driver). system/pysed: Switch to i586. system/rmw: Updated for version 2016.09.19.01a. system/slpkg: Switch to i586. system/termenu: Switch to i586. system/thinkfan: Updated for version 0.9.3. system/tmuxp: Updated for version 1.2.1. system/ttf-paratype-pt-fonts: Added (Public Type (PT) fonts). system/ttygif: Switch to i586. system/ttyrec: Switch to i586. system/wine-staging: Updated for version 1.9.19. +--------------------------+ -- 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: From slackbuilds at schoepfer.info Sat Sep 24 07:08:02 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 24 Sep 2016 09:08:02 +0200 Subject: [Slackbuilds-users] Anyone interested in taking higan? In-Reply-To: References: <3354ca2953b6481a3191266a53a0fcdc@schoepfer.info> Message-ID: > Attached is the updated buildscript, but i don't want to maintain it > in the future because i got headache on creating it. > I will use mednafen if i want to play mario ;-) > > @SBo-admins: Should i submit it, even if i'm not the new maintainer? I submitted it, it was updated on SBo https://slackbuilds.org/repository/14.2/games/higan/ , but at least higan.SlackBuild doesn't reflect the changes from git https://slackbuilds.org/cgit/slackbuilds/commit/?id=79fc90f23 Johannes From willysr at slackbuilds.org Sat Sep 24 07:27:26 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 24 Sep 2016 14:27:26 +0700 Subject: [Slackbuilds-users] Anyone interested in taking higan? In-Reply-To: References: <3354ca2953b6481a3191266a53a0fcdc@schoepfer.info> Message-ID: <2076ac19-6765-a44e-5866-9fefccd44ac3@slackbuilds.org> > I submitted it, it was updated on SBo > https://slackbuilds.org/repository/14.2/games/higan/ , but at least > higan.SlackBuild doesn't reflect the changes from git > https://slackbuilds.org/cgit/slackbuilds/commit/?id=79fc90f23 it does reflect changes from git perhaps a cache issue? -- 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: From ryan.q at linux.com Sat Sep 24 15:45:18 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 24 Sep 2016 08:45:18 -0700 Subject: [Slackbuilds-users] Anyone interested in taking higan? In-Reply-To: <2076ac19-6765-a44e-5866-9fefccd44ac3@slackbuilds.org> References: <3354ca2953b6481a3191266a53a0fcdc@schoepfer.info> <2076ac19-6765-a44e-5866-9fefccd44ac3@slackbuilds.org> Message-ID: On Saturday, September 24, 2016, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I submitted it, it was updated on SBo > > https://slackbuilds.org/repository/14.2/games/higan/ , but at least > > higan.SlackBuild doesn't reflect the changes from git > > https://slackbuilds.org/cgit/slackbuilds/commit/?id=79fc90f23 > > it does reflect changes from git > perhaps a cache issue? > > That'd be my guess, I see the new version. -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Sep 24 23:46:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 25 Sep 2016 06:46:02 +0700 Subject: [Slackbuilds-users] New webkit2gtk for review Message-ID: <829aef04-0ddf-d3da-2d03-960d03c95869@slackbuilds.org> Hi all, webkit2gtk 2.14.0 has been released few days ago and this new version brings some new interesting features: - Threaded compositor is enabled by default in both X11 and Wayland. - Accelerated compositing is now supported in Wayland. - Clipboard works in Wayland too. - Memory pressure handler always works even when cgroups is not present or not configured. - The HTTP disk cache implements speculative revalidation of resources. - DRI3 is no longer a problem when using the modesetting intel driver. - The amount of file descriptors that are kept open has been drastically reduced. The most exciting feature is threaded compositor. Basically it moved the accelerated compositing to second thread, so it will have better throughput. You can read the detail and a comparison video here: http://blog.ryumiel.net/articles/introducing-threaded-compositor/ https://youtu.be/PJSsEiNasow While it doesn't bring new APIs, it's still better to be cautious of regression introduced by this new version. For that reason, i put the new webkit2gtk in a separate branch for review: webkit2gtk-review. There are 3 packages that have a hard dependency of webkit2gtk at this moment: graphics/shotwell network/midori system/yelp This is a good time to test them before i merge them in next week's public update. happy testing :) -- 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: From willysr at slackbuilds.org Sun Sep 25 00:21:53 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 25 Sep 2016 07:21:53 +0700 Subject: [Slackbuilds-users] Updates - 20160925.1 Message-ID: <25d75dfe-896a-562d-4354-bd4c5a4f62c4@slackbuilds.org> Sun Sep 25 00:06:32 UTC 2016 academic/galculator: Switch to i586. academic/gcompris: Switch to i586. audio/sayonara-player: Updated for version 0.9.2. desktop/homerun: Switch to i586. desktop/murrine: Switch to i586. development/anjuta: Switch to i586. development/bas55: Switch to i586. development/byacc: Switch to i586. development/gengetopt: Switch to i586. development/scratch: Switch to i586. development/squeak-vm: Switch to i586. development/wxHexEditor: Switch to i586. games/wesnoth: Switch to i586. gis/qgis: Updated for version 2.16.3. graphics/grafx2: Update DOWNLOAD url + switch to i586. graphics/pinta: Switch to i586. graphics/qcad: Updated for version 3.15.5.3 libraries/LucenePlusPlus: Switch to i586. libraries/SlowAES: Switch to i586. libraries/botocore: Updated for version 1.4.56. libraries/bullet: Switch to i586. libraries/crossguid: Updated for version 20160705 libraries/ctemplate: Switch to i586. libraries/ffms2: Switch to i586. libraries/gdata: Update download link libraries/gdl: Switch to i586. libraries/gf2x: Switch to i586. libraries/gtksourceview3: Switch to i586. libraries/hidapi: Switch to i586. libraries/imlib: Switch to i586. libraries/jansson: Updated for version 2.9 libraries/leptonica: Switch to i586. libraries/libgda: Switch to i586. libraries/libgit2-glib: Switch to i586. libraries/libgusb: Switch to i586. libraries/libmygpo-qt: Updated for version 1.0.9. libraries/libseccomp: Switch to i586. libraries/libu2f-host: Switch to i586. libraries/liburcu: Switch to i586. libraries/mysql-connector-c++: Switch to i586. libraries/mysql-connector-python: Switch to i586. libraries/nacl: Switch to i586. libraries/oath-toolkit: Updated for version 2.6.2. libraries/ocaml-bisect: Switch to i586. libraries/pugixml: Switch to i586. libraries/rest: Switch to i586. libraries/secp256k1: Switch to i586. libraries/vsqlite++: Switch to i586. libraries/xmlsec: Switch to i586. misc/fcrackzip: Switch to i586. misc/rsibreak: Switch to i586. multimedia/TeamSpeak3: Switch to i586. multimedia/gimp-gap: Switch to i586. multimedia/gtkpod: Switch to i586. multimedia/guvcview: Switch to i586. multimedia/pngnq-s9: Switch to i586. network/PaleMoon: Added alternate extract routine. network/awscli: Updated for version 1.10.66. network/bwm-ng: Switch to i586. network/darkstat: Switch to i586. network/dnstracer: Switch to i586. network/hostsblock: Switch to i586. network/mod_bw: Switch to i586. network/netcat: Switch to i586. network/putty: Switch to i586. network/sshblock: Switch to i586. network/telegram: Updated for version 0.10.8. network/you-get: Updated for version 0.4.555. network/youtube-dl: Updated for version 2016.09.24. office/Ted: Switch to i586. python/babelfish: Updated for version 0.5.5. python/ecdsa: Switch to i586. python/monty: Updated for version 0.9.5. python/pyrfc3339: Switch to i586. python/python-jsonrpclib: Switch to i586. python/python-parsedatetime: Switch to i586. python/python-pbkdf2: Switch to i586. python/python-qrcode: Switch to i586. python/python-tlslite: Updated for version 0.4.9. python/rebulk: Added (Advanced searches in strings). system/acpi: Switch to i586. system/apache-activemq: Updated for version 5.14.0. system/autocutsel: Switch to i586. system/colord: Switch to i586. system/ext4magic: Switch to i586. system/gdmap: Switch to i586. system/gimp-help: Switch to i586. system/gtk-vnc: Updated for version 0.6.0. system/md5deep: Switch to i586. system/multitail: Switch to i586. system/mysql-utilities: Switch to i586. system/netatop: Switch to i586. system/pdfgrep: Switch to i586. system/sqlite2: Switch to i586. system/suhosin: Switch to i586. system/swatch: Switch to i586. system/tomb: Switch to i586. system/unicode-character-database: Switch to i586. system/vbindiff: Switch to i586. system/yelp-tools: Switch to i586. system/yelp-xsl: Switch to i586. system/yelp: Switch to i586. +--------------------------+ -- 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: From willysr at slackbuilds.org Sun Sep 25 02:28:39 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 25 Sep 2016 09:28:39 +0700 Subject: [Slackbuilds-users] New maintainer Needed Message-ID: Hi I can't contact Diego Pantano as my message bounced back with a non-existence email account and his last contributions was 6 years ago, so i think we need a new maintainer for his scripts. He maintained several SlackBuilds related to FlightGear: games/FlightGear games/fgrun games/FlightGear-data libraries/SimGear anyone want to take over his packages? -- 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: From hostmaster at slackonly.com Sun Sep 25 05:10:57 2016 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 25 Sep 2016 08:10:57 +0300 Subject: [Slackbuilds-users] New maintainer Needed In-Reply-To: References: Message-ID: <1575fc0dae8.279b.9e181f506a95e1e04806492672ca594b@slackonly.com> I play for years this game and I like a lot! I will be happy to take it. Thanks On 25 September 2016 5:29:01 a.m. Willy Sudiarto Raharjo wrote: > Hi > > I can't contact Diego Pantano as my message bounced back with a > non-existence email account and his last contributions was 6 years ago, > so i think we need a new maintainer for his scripts. > > He maintained several SlackBuilds related to FlightGear: > games/FlightGear > games/fgrun > games/FlightGear-data > libraries/SimGear > > anyone want to take over his packages? > > > -- > 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 sombragris at sombragris.org Sun Sep 25 17:52:09 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sun, 25 Sep 2016 13:52:09 -0400 Subject: [Slackbuilds-users] BUG: sayonara-player 0.9.2 segfaults; complex, untested workaround Message-ID: <0q93i.607612f724.20160925135209.6d753e72@loli.sombragris.org> Sayonara player 0.9.2 compiles OK but segfaults upon running. I got exactly the same output as this forum thread at upstream's website: https://sayonara-player.com/forum/viewthread.php?tid=277 Apparently, this is what happens: sayonara requires gst-plugins-bad, *but now* gst-plugins-bad must be compiled with soundtouch support (which is also on SBO). Doing this would enable the software to run. However, I was unable to check this because building gst-plugins-bad fails in my system (that would be another bug report). If I manage to get sayonara 0.9.2 to run I will update. Below is the complete console output after running sayonara 0.9.2. Thanks and best regards, Eduardo [console output follows] [eduardo:~]$ sayonara Database Version 10 Warning: No need to update db **** All settings initialized **** Warning: Setting LastFM_login: Cannot convert. Use default value... Warning: Setting show_tray_icon: Not found. Use default value... Load Setting show_tray_icon: true Warning: Setting engine_pitch: Not found. Use default value... Load Setting engine_pitch: 440 Warning: Setting engine_preserve_pitch: Not found. Use default value... Load Setting engine_preserve_pitch: false Warning: Setting engine_speed: Not found. Use default value... Load Setting engine_speed: 1 Warning: Setting engine_speed_active: Not found. Use default value... Load Setting engine_speed_active: false Debug: Init application: 9ms Debug: Start player: 9ms Debug: Theme paths /home/eduardo/.icons, /usr/local/share/icons, /usr/share/icons, /usr/share/pixmaps, :/icons, Debug: Loading playlists... Error: Engine: pitch creation failed Error: Engine: lamemp3enc creation failed Error: Engine: sr_lame creation failed (sayonara:31976): GStreamer-CRITICAL **: gst_object_get_name: assertion 'GST_IS_OBJECT (object)' failed sayonara(_Z16segfault_handleri+0x12)[0x5a3732] /lib64/libpthread.so.0(+0x115b0)[0x7fcd321f95b0] /lib64/libc.so.6(+0xa075e)[0x7fcd31ec275e] /usr/lib64/libgstreamer-1.0.so.0(+0x30d87)[0x7fcd35797d87] /usr/lib64/libgstreamer-1.0.so.0(+0x60f47)[0x7fcd357c7f47] /usr/lib64/libgstreamer-1.0.so.0(gst_iterator_fold+0x7c)[0x7fcd357c89dc] /usr/lib64/libgstreamer-1.0.so.0(gst_iterator_find_custom+0x53)[0x7fcd357c8a73] /usr/lib64/libgstreamer-1.0.so.0(gst_bin_get_by_name+0xa4)[0x7fcd3579e0a4] sayonara(_ZN18ChangeablePipeline14remove_elementEP11_GstElementS1_S1_+0x35)[0x73d3b5] sayonara(_ZN16PlaybackPipeline24_sl_speed_active_changedEv+0x9d)[0x737c5d] sayonara(_ZN16PlaybackPipeline4initE8GstState+0x29f)[0x737f2f] sayonara(_ZN14PlaybackEngine4initEv+0x48)[0x735d98] sayonara(_ZN13EngineHandler10get_engineE10EngineName+0x23c)[0x7325cc] sayonara(_ZN13EngineHandler13switch_engineE10EngineName+0xe)[0x7326ae] sayonara(_ZN13EngineHandlerC2EP7QObject+0x4bb)[0x732dcb] sayonara(_ZN8PlaylistC1Ei7QString+0x368)[0x7277a8] sayonara(_ZN11StdPlaylistC1Ei7QString+0x2c)[0x73064c] sayonara(_ZN15PlaylistHandler12new_playlistEN8Playlist4TypeEi7QString+0xda)[0x728aea] sayonara(_ZN15PlaylistHandler16add_new_playlistERK7QStringbN8Playlist4TypeE+0x103)[0x728ca3] sayonara(_ZN15PlaylistHandler15create_playlistERK12MetaDataListRK7QStringbN8Playlist4TypeE+0x11a)[0x72a41a] Segmentation fault [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 sombragris at sombragris.org Sun Sep 25 18:28:13 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sun, 25 Sep 2016 14:28:13 -0400 Subject: [Slackbuilds-users] BUG: gst-plugins-bad building fails with Qt 5.7; workaround Message-ID: <0q93i.3076efc073.20160925142813.1e0915d8@loli.sombragris.org> Building gst-plugins-bad fails on libqtsink_la-gstqsgtexture.lo in my system (-current). The compiler output is actually quite large at the point, but the crux of the matter seems to be this message: # error "Qt requires C++11 support" Upon some investigation, it looks like the culprit is Qt 5.7, which requires C+11. The workaround would be to explictly enable the compiler to use C++11 during compilation. That is achieved by adding "-std=c++11" to SLKCFLAGS. After that step, gst-plugins-bad builds correctly. Below is the output of the failed build with the stock SlackBuild. Thanks Eduardo CXX libqtsink_la-gstqsgtexture.lo In file included from /usr/include/qt5/QtCore/qatomic.h:46:0, from /usr/include/qt5/QtCore/qglobal.h:1145, from /usr/include/qt5/QtQuick/qtquickglobal.h:43, from /usr/include/qt5/QtQuick/qsgtexture.h:43, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qbasicatomic.h:61:4: error: #error "Qt requires C++11 support" # error "Qt requires C++11 support" ^ In file included from /usr/include/qt5/QtCore/QObject:1:0, from /usr/include/qt5/QtQuick/qsgtexture.h:44, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qobject.h:322:9: warning: identifier 'decltype' is a keyword in C++11 [-Wc++0x-compat] typedef QtPrivate::FunctionPointer SlotType ; ^ In file included from /usr/include/qt5/QtQuick/qtquickglobal.h:43:0, from /usr/include/qt5/QtQuick/qsgtexture.h:43, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qglobal.h:1133:23: error: expected ',' or '...' before '&&' token void qAsConst(const T &&) Q_DECL_EQ_DELETE; ^ In file included from /usr/include/qt5/QtCore/qatomic.h:46:0, from /usr/include/qt5/QtCore/qglobal.h:1145, from /usr/include/qt5/QtQuick/qtquickglobal.h:43, from /usr/include/qt5/QtQuick/qsgtexture.h:43, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qbasicatomic.h:90:13: error: 'QAtomicOps' does not name a type typedef QAtomicOps Ops; ^ In file included from /usr/include/qt5/QtQuick/qtquickglobal.h:43:0, from /usr/include/qt5/QtQuick/qsgtexture.h:43, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qbasicatomic.h:93:23: error: 'QAtomicOpsSupport' was not declared in this scope Q_STATIC_ASSERT_X(QAtomicOpsSupport::IsSupported, "template parameter is an integral of a size not supported on this platform"); ^ /usr/include/qt5/QtCore/qglobal.h:756:110: note: in definition of macro 'Q_STATIC_ASSERT' enum {Q_STATIC_ASSERT_PRIVATE_JOIN(q_static_assert_result, __COUNTER__) = sizeof(QStaticAssertFailure)} ^ /usr/include/qt5/QtCore/qbasicatomic.h:93:5: note: in expansion of macro 'Q_STATIC_ASSERT_X' Q_STATIC_ASSERT_X(QAtomicOpsSupport::IsSupported, "template parameter is an integral of a size not supported on this platform"); ^ /usr/include/qt5/QtCore/qbasicatomic.h:93:51: error: '::IsSupported' has not been declared Q_STATIC_ASSERT_X(QAtomicOpsSupport::IsSupported, "template parameter is an integral of a size not supported on this platform"); ^ /usr/include/qt5/QtCore/qglobal.h:756:110: note: in definition of macro 'Q_STATIC_ASSERT' enum {Q_STATIC_ASSERT_PRIVATE_JOIN(q_static_assert_result, __COUNTER__) = sizeof(QStaticAssertFailure)} ^ /usr/include/qt5/QtCore/qbasicatomic.h:93:5: note: in expansion of macro 'Q_STATIC_ASSERT_X' Q_STATIC_ASSERT_X(QAtomicOpsSupport::IsSupported, "template parameter is an integral of a size not supported on this platform"); ^ /usr/include/qt5/QtCore/qglobal.h:756:120: error: template argument 1 is invalid enum {Q_STATIC_ASSERT_PRIVATE_JOIN(q_static_assert_result, __COUNTER__) = sizeof(QStaticAssertFailure)} ^ /usr/include/qt5/QtCore/qglobal.h:761:47: note: in expansion of macro 'Q_STATIC_ASSERT' #define Q_STATIC_ASSERT_X(Condition, Message) Q_STATIC_ASSERT(Condition) ^ /usr/include/qt5/QtCore/qbasicatomic.h:93:5: note: in expansion of macro 'Q_STATIC_ASSERT_X' Q_STATIC_ASSERT_X(QAtomicOpsSupport::IsSupported, "template parameter is an integral of a size not supported on this platform"); ^ In file included from /usr/include/qt5/QtCore/qatomic.h:46:0, from /usr/include/qt5/QtCore/qglobal.h:1145, from /usr/include/qt5/QtQuick/qtquickglobal.h:43, from /usr/include/qt5/QtQuick/qsgtexture.h:43, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qbasicatomic.h:95:14: error: 'Ops' has not been declared typename Ops::Type _q_value; ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::load() const': /usr/include/qt5/QtCore/qbasicatomic.h:99:44: error: 'Ops' has not been declared T load() const Q_DECL_NOTHROW { return Ops::load(_q_value); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'void QBasicAtomicInteger::store(T)': /usr/include/qt5/QtCore/qbasicatomic.h:100:45: error: 'Ops' has not been declared void store(T newValue) Q_DECL_NOTHROW { Ops::store(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::loadAcquire() const': /usr/include/qt5/QtCore/qbasicatomic.h:102:51: error: 'Ops' has not been declared T loadAcquire() const Q_DECL_NOTHROW { return Ops::loadAcquire(_q_value); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'void QBasicAtomicInteger::storeRelease(T)': /usr/include/qt5/QtCore/qbasicatomic.h:103:52: error: 'Ops' has not been declared void storeRelease(T newValue) Q_DECL_NOTHROW { Ops::storeRelease(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicInteger::isReferenceCountingNative()': /usr/include/qt5/QtCore/qbasicatomic.h:107:86: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isReferenceCountingNative() Q_DECL_NOTHROW { return Ops::isReferenceCountingNative(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicInteger::isReferenceCountingWaitFree()': /usr/include/qt5/QtCore/qbasicatomic.h:108:88: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isReferenceCountingWaitFree() Q_DECL_NOTHROW { return Ops::isReferenceCountingWaitFree(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::ref()': /usr/include/qt5/QtCore/qbasicatomic.h:110:40: error: 'Ops' has not been declared bool ref() Q_DECL_NOTHROW { return Ops::ref(_q_value); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::deref()': /usr/include/qt5/QtCore/qbasicatomic.h:111:42: error: 'Ops' has not been declared bool deref() Q_DECL_NOTHROW { return Ops::deref(_q_value); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicInteger::isTestAndSetNative()': /usr/include/qt5/QtCore/qbasicatomic.h:113:79: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isTestAndSetNative() Q_DECL_NOTHROW { return Ops::isTestAndSetNative(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicInteger::isTestAndSetWaitFree()': /usr/include/qt5/QtCore/qbasicatomic.h:114:81: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isTestAndSetWaitFree() Q_DECL_NOTHROW { return Ops::isTestAndSetWaitFree(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::testAndSetRelaxed(T, T)': /usr/include/qt5/QtCore/qbasicatomic.h:117:14: error: 'Ops' has not been declared { return Ops::testAndSetRelaxed(_q_value, expectedValue, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::testAndSetAcquire(T, T)': /usr/include/qt5/QtCore/qbasicatomic.h:119:14: error: 'Ops' has not been declared { return Ops::testAndSetAcquire(_q_value, expectedValue, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::testAndSetRelease(T, T)': /usr/include/qt5/QtCore/qbasicatomic.h:121:14: error: 'Ops' has not been declared { return Ops::testAndSetRelease(_q_value, expectedValue, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::testAndSetOrdered(T, T)': /usr/include/qt5/QtCore/qbasicatomic.h:123:14: error: 'Ops' has not been declared { return Ops::testAndSetOrdered(_q_value, expectedValue, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::testAndSetRelaxed(T, T, T&)': /usr/include/qt5/QtCore/qbasicatomic.h:126:14: error: 'Ops' has not been declared { return Ops::testAndSetRelaxed(_q_value, expectedValue, newValue, ¤tValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::testAndSetAcquire(T, T, T&)': /usr/include/qt5/QtCore/qbasicatomic.h:128:14: error: 'Ops' has not been declared { return Ops::testAndSetAcquire(_q_value, expectedValue, newValue, ¤tValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::testAndSetRelease(T, T, T&)': /usr/include/qt5/QtCore/qbasicatomic.h:130:14: error: 'Ops' has not been declared { return Ops::testAndSetRelease(_q_value, expectedValue, newValue, ¤tValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicInteger::testAndSetOrdered(T, T, T&)': /usr/include/qt5/QtCore/qbasicatomic.h:132:14: error: 'Ops' has not been declared { return Ops::testAndSetOrdered(_q_value, expectedValue, newValue, ¤tValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicInteger::isFetchAndStoreNative()': /usr/include/qt5/QtCore/qbasicatomic.h:134:82: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isFetchAndStoreNative() Q_DECL_NOTHROW { return Ops::isFetchAndStoreNative(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicInteger::isFetchAndStoreWaitFree()': /usr/include/qt5/QtCore/qbasicatomic.h:135:84: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isFetchAndStoreWaitFree() Q_DECL_NOTHROW { return Ops::isFetchAndStoreWaitFree(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndStoreRelaxed(T)': /usr/include/qt5/QtCore/qbasicatomic.h:138:14: error: 'Ops' has not been declared { return Ops::fetchAndStoreRelaxed(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndStoreAcquire(T)': /usr/include/qt5/QtCore/qbasicatomic.h:140:14: error: 'Ops' has not been declared { return Ops::fetchAndStoreAcquire(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndStoreRelease(T)': /usr/include/qt5/QtCore/qbasicatomic.h:142:14: error: 'Ops' has not been declared { return Ops::fetchAndStoreRelease(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndStoreOrdered(T)': /usr/include/qt5/QtCore/qbasicatomic.h:144:14: error: 'Ops' has not been declared { return Ops::fetchAndStoreOrdered(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicInteger::isFetchAndAddNative()': /usr/include/qt5/QtCore/qbasicatomic.h:146:80: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isFetchAndAddNative() Q_DECL_NOTHROW { return Ops::isFetchAndAddNative(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicInteger::isFetchAndAddWaitFree()': /usr/include/qt5/QtCore/qbasicatomic.h:147:82: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isFetchAndAddWaitFree() Q_DECL_NOTHROW { return Ops::isFetchAndAddWaitFree(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndAddRelaxed(T)': /usr/include/qt5/QtCore/qbasicatomic.h:150:14: error: 'Ops' has not been declared { return Ops::fetchAndAddRelaxed(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndAddAcquire(T)': /usr/include/qt5/QtCore/qbasicatomic.h:152:14: error: 'Ops' has not been declared { return Ops::fetchAndAddAcquire(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndAddRelease(T)': /usr/include/qt5/QtCore/qbasicatomic.h:154:14: error: 'Ops' has not been declared { return Ops::fetchAndAddRelease(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndAddOrdered(T)': /usr/include/qt5/QtCore/qbasicatomic.h:156:14: error: 'Ops' has not been declared { return Ops::fetchAndAddOrdered(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndSubRelaxed(T)': /usr/include/qt5/QtCore/qbasicatomic.h:159:14: error: 'Ops' has not been declared { return Ops::fetchAndSubRelaxed(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndSubAcquire(T)': /usr/include/qt5/QtCore/qbasicatomic.h:161:14: error: 'Ops' has not been declared { return Ops::fetchAndSubAcquire(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndSubRelease(T)': /usr/include/qt5/QtCore/qbasicatomic.h:163:14: error: 'Ops' has not been declared { return Ops::fetchAndSubRelease(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndSubOrdered(T)': /usr/include/qt5/QtCore/qbasicatomic.h:165:14: error: 'Ops' has not been declared { return Ops::fetchAndSubOrdered(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndAndRelaxed(T)': /usr/include/qt5/QtCore/qbasicatomic.h:168:14: error: 'Ops' has not been declared { return Ops::fetchAndAndRelaxed(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndAndAcquire(T)': /usr/include/qt5/QtCore/qbasicatomic.h:170:14: error: 'Ops' has not been declared { return Ops::fetchAndAndAcquire(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndAndRelease(T)': /usr/include/qt5/QtCore/qbasicatomic.h:172:14: error: 'Ops' has not been declared { return Ops::fetchAndAndRelease(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndAndOrdered(T)': /usr/include/qt5/QtCore/qbasicatomic.h:174:14: error: 'Ops' has not been declared { return Ops::fetchAndAndOrdered(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndOrRelaxed(T)': /usr/include/qt5/QtCore/qbasicatomic.h:177:14: error: 'Ops' has not been declared { return Ops::fetchAndOrRelaxed(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndOrAcquire(T)': /usr/include/qt5/QtCore/qbasicatomic.h:179:14: error: 'Ops' has not been declared { return Ops::fetchAndOrAcquire(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndOrRelease(T)': /usr/include/qt5/QtCore/qbasicatomic.h:181:14: error: 'Ops' has not been declared { return Ops::fetchAndOrRelease(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndOrOrdered(T)': /usr/include/qt5/QtCore/qbasicatomic.h:183:14: error: 'Ops' has not been declared { return Ops::fetchAndOrOrdered(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndXorRelaxed(T)': /usr/include/qt5/QtCore/qbasicatomic.h:186:14: error: 'Ops' has not been declared { return Ops::fetchAndXorRelaxed(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndXorAcquire(T)': /usr/include/qt5/QtCore/qbasicatomic.h:188:14: error: 'Ops' has not been declared { return Ops::fetchAndXorAcquire(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndXorRelease(T)': /usr/include/qt5/QtCore/qbasicatomic.h:190:14: error: 'Ops' has not been declared { return Ops::fetchAndXorRelease(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'T QBasicAtomicInteger::fetchAndXorOrdered(T)': /usr/include/qt5/QtCore/qbasicatomic.h:192:14: error: 'Ops' has not been declared { return Ops::fetchAndXorOrdered(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: At global scope: /usr/include/qt5/QtCore/qbasicatomic.h:230:13: error: 'QAtomicOps' does not name a type typedef QAtomicOps Ops; ^ /usr/include/qt5/QtCore/qbasicatomic.h:231:22: error: 'Ops' has not been declared typedef typename Ops::Type AtomicType; ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::load() const': /usr/include/qt5/QtCore/qbasicatomic.h:235:47: error: 'Ops' has not been declared Type load() const Q_DECL_NOTHROW { return Ops::load(_q_value); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'void QBasicAtomicPointer::store(QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:236:48: error: 'Ops' has not been declared void store(Type newValue) Q_DECL_NOTHROW { Ops::store(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::loadAcquire() const': /usr/include/qt5/QtCore/qbasicatomic.h:241:54: error: 'Ops' has not been declared Type loadAcquire() const Q_DECL_NOTHROW { return Ops::loadAcquire(_q_value); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'void QBasicAtomicPointer::storeRelease(QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:242:55: error: 'Ops' has not been declared void storeRelease(Type newValue) Q_DECL_NOTHROW { Ops::storeRelease(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicPointer::isTestAndSetNative()': /usr/include/qt5/QtCore/qbasicatomic.h:244:79: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isTestAndSetNative() Q_DECL_NOTHROW { return Ops::isTestAndSetNative(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicPointer::isTestAndSetWaitFree()': /usr/include/qt5/QtCore/qbasicatomic.h:245:81: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isTestAndSetWaitFree() Q_DECL_NOTHROW { return Ops::isTestAndSetWaitFree(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicPointer::testAndSetRelaxed(QBasicAtomicPointer::Type, QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:248:14: error: 'Ops' has not been declared { return Ops::testAndSetRelaxed(_q_value, expectedValue, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicPointer::testAndSetAcquire(QBasicAtomicPointer::Type, QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:250:14: error: 'Ops' has not been declared { return Ops::testAndSetAcquire(_q_value, expectedValue, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicPointer::testAndSetRelease(QBasicAtomicPointer::Type, QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:252:14: error: 'Ops' has not been declared { return Ops::testAndSetRelease(_q_value, expectedValue, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicPointer::testAndSetOrdered(QBasicAtomicPointer::Type, QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:254:14: error: 'Ops' has not been declared { return Ops::testAndSetOrdered(_q_value, expectedValue, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicPointer::testAndSetRelaxed(QBasicAtomicPointer::Type, QBasicAtomicPointer::Type, X*&)': /usr/include/qt5/QtCore/qbasicatomic.h:257:14: error: 'Ops' has not been declared { return Ops::testAndSetRelaxed(_q_value, expectedValue, newValue, ¤tValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicPointer::testAndSetAcquire(QBasicAtomicPointer::Type, QBasicAtomicPointer::Type, X*&)': /usr/include/qt5/QtCore/qbasicatomic.h:259:14: error: 'Ops' has not been declared { return Ops::testAndSetAcquire(_q_value, expectedValue, newValue, ¤tValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicPointer::testAndSetRelease(QBasicAtomicPointer::Type, QBasicAtomicPointer::Type, X*&)': /usr/include/qt5/QtCore/qbasicatomic.h:261:14: error: 'Ops' has not been declared { return Ops::testAndSetRelease(_q_value, expectedValue, newValue, ¤tValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'bool QBasicAtomicPointer::testAndSetOrdered(QBasicAtomicPointer::Type, QBasicAtomicPointer::Type, X*&)': /usr/include/qt5/QtCore/qbasicatomic.h:263:14: error: 'Ops' has not been declared { return Ops::testAndSetOrdered(_q_value, expectedValue, newValue, ¤tValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicPointer::isFetchAndStoreNative()': /usr/include/qt5/QtCore/qbasicatomic.h:265:82: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isFetchAndStoreNative() Q_DECL_NOTHROW { return Ops::isFetchAndStoreNative(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicPointer::isFetchAndStoreWaitFree()': /usr/include/qt5/QtCore/qbasicatomic.h:266:84: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isFetchAndStoreWaitFree() Q_DECL_NOTHROW { return Ops::isFetchAndStoreWaitFree(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndStoreRelaxed(QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:269:14: error: 'Ops' has not been declared { return Ops::fetchAndStoreRelaxed(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndStoreAcquire(QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:271:14: error: 'Ops' has not been declared { return Ops::fetchAndStoreAcquire(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndStoreRelease(QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:273:14: error: 'Ops' has not been declared { return Ops::fetchAndStoreRelease(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndStoreOrdered(QBasicAtomicPointer::Type)': /usr/include/qt5/QtCore/qbasicatomic.h:275:14: error: 'Ops' has not been declared { return Ops::fetchAndStoreOrdered(_q_value, newValue); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicPointer::isFetchAndAddNative()': /usr/include/qt5/QtCore/qbasicatomic.h:277:80: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isFetchAndAddNative() Q_DECL_NOTHROW { return Ops::isFetchAndAddNative(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In static member function 'static bool QBasicAtomicPointer::isFetchAndAddWaitFree()': /usr/include/qt5/QtCore/qbasicatomic.h:278:82: error: 'Ops' has not been declared static Q_DECL_CONSTEXPR bool isFetchAndAddWaitFree() Q_DECL_NOTHROW { return Ops::isFetchAndAddWaitFree(); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndAddRelaxed(qptrdiff)': /usr/include/qt5/QtCore/qbasicatomic.h:281:14: error: 'Ops' has not been declared { return Ops::fetchAndAddRelaxed(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndAddAcquire(qptrdiff)': /usr/include/qt5/QtCore/qbasicatomic.h:283:14: error: 'Ops' has not been declared { return Ops::fetchAndAddAcquire(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndAddRelease(qptrdiff)': /usr/include/qt5/QtCore/qbasicatomic.h:285:14: error: 'Ops' has not been declared { return Ops::fetchAndAddRelease(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndAddOrdered(qptrdiff)': /usr/include/qt5/QtCore/qbasicatomic.h:287:14: error: 'Ops' has not been declared { return Ops::fetchAndAddOrdered(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndSubRelaxed(qptrdiff)': /usr/include/qt5/QtCore/qbasicatomic.h:290:14: error: 'Ops' has not been declared { return Ops::fetchAndSubRelaxed(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndSubAcquire(qptrdiff)': /usr/include/qt5/QtCore/qbasicatomic.h:292:14: error: 'Ops' has not been declared { return Ops::fetchAndSubAcquire(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndSubRelease(qptrdiff)': /usr/include/qt5/QtCore/qbasicatomic.h:294:14: error: 'Ops' has not been declared { return Ops::fetchAndSubRelease(_q_value, valueToAdd); } ^ /usr/include/qt5/QtCore/qbasicatomic.h: In member function 'X* QBasicAtomicPointer::fetchAndSubOrdered(qptrdiff)': /usr/include/qt5/QtCore/qbasicatomic.h:296:14: error: 'Ops' has not been declared { return Ops::fetchAndSubOrdered(_q_value, valueToAdd); } ^ In file included from /usr/include/qt5/QtCore/QObject:1:0, from /usr/include/qt5/QtQuick/qsgtexture.h:44, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qobject.h: In static member function 'static typename QtPrivate::QEnableIf<(QtPrivate::FunctionPointer::ArgumentCount == (-1)), QMetaObject::Connection>::Type QObject::connect(const typename QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, Qt::ConnectionType)': /usr/include/qt5/QtCore/qobject.h:322:70: error: '&' cannot appear in a constant-expression typedef QtPrivate::FunctionPointer SlotType ; ^ /usr/include/qt5/QtCore/qobject.h:322:71: error: a function call cannot appear in a constant-expression typedef QtPrivate::FunctionPointer SlotType ; ^ /usr/include/qt5/QtCore/qobject.h:322:72: error: template argument 1 is invalid typedef QtPrivate::FunctionPointer SlotType ; ^ /usr/include/qt5/QtCore/qobject.h:324:26: error: 'SlotType' is not a class or namespace typedef typename SlotType::ReturnType SlotReturnType; ^ /usr/include/qt5/QtCore/qobject.h:325:39: error: 'SlotType' is not a class or namespace const int SlotArgumentCount = SlotType::ArgumentCount; ^ In file included from /usr/include/qt5/QtQuick/qtquickglobal.h:43:0, from /usr/include/qt5/QtQuick/qsgtexture.h:43, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qglobal.h:756:120: error: template argument 1 is invalid enum {Q_STATIC_ASSERT_PRIVATE_JOIN(q_static_assert_result, __COUNTER__) = sizeof(QStaticAssertFailure)} ^ /usr/include/qt5/QtCore/qglobal.h:761:47: note: in expansion of macro 'Q_STATIC_ASSERT' #define Q_STATIC_ASSERT_X(Condition, Message) Q_STATIC_ASSERT(Condition) ^ /usr/include/qt5/QtCore/qobject.h:327:9: note: in expansion of macro 'Q_STATIC_ASSERT_X' Q_STATIC_ASSERT_X(int(SignalType::ArgumentCount) >= SlotArgumentCount, ^ /usr/include/qt5/QtCore/qobject.h:329:124: error: template argument 2 is invalid Q_STATIC_ASSERT_X((QtPrivate::CheckCompatibleArguments::value), ^ /usr/include/qt5/QtCore/qglobal.h:756:110: note: in definition of macro 'Q_STATIC_ASSERT' enum {Q_STATIC_ASSERT_PRIVATE_JOIN(q_static_assert_result, __COUNTER__) = sizeof(QStaticAssertFailure)} ^ /usr/include/qt5/QtCore/qobject.h:329:9: note: in expansion of macro 'Q_STATIC_ASSERT_X' Q_STATIC_ASSERT_X((QtPrivate::CheckCompatibleArguments::value), ^ /usr/include/qt5/QtCore/qglobal.h:756:120: error: template argument 1 is invalid enum {Q_STATIC_ASSERT_PRIVATE_JOIN(q_static_assert_result, __COUNTER__) = sizeof(QStaticAssertFailure)} ^ /usr/include/qt5/QtCore/qglobal.h:761:47: note: in expansion of macro 'Q_STATIC_ASSERT' #define Q_STATIC_ASSERT_X(Condition, Message) Q_STATIC_ASSERT(Condition) ^ /usr/include/qt5/QtCore/qobject.h:329:9: note: in expansion of macro 'Q_STATIC_ASSERT_X' Q_STATIC_ASSERT_X((QtPrivate::CheckCompatibleArguments::value), ^ In file included from /usr/include/qt5/QtCore/QObject:1:0, from /usr/include/qt5/QtQuick/qsgtexture.h:44, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qobject.h:346:64: error: template argument 3 is invalid typename SignalType::ReturnType>(slot), ^ /usr/include/qt5/QtCore/qobject.h:346:65: error: expected '::' before '(' token typename SignalType::ReturnType>(slot), ^ /usr/include/qt5/QtCore/qobject.h:346:65: error: expected identifier before '(' token In file included from /usr/include/qt5/QtGui/qmatrix.h:44:0, from /usr/include/qt5/QtGui/qtransform.h:42, from /usr/include/qt5/QtGui/qimage.h:47, from /usr/include/qt5/QtGui/QImage:1, from /usr/include/qt5/QtQuick/qsgtexture.h:45, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtGui/qregion.h: At global scope: /usr/include/qt5/QtGui/qregion.h:71:21: error: expected ',' or '...' before '&&' token QRegion(QRegion &&other) Q_DECL_NOTHROW ^ /usr/include/qt5/QtGui/qregion.h:71:28: error: invalid constructor; you probably meant 'QRegion (const QRegion&)' QRegion(QRegion &&other) Q_DECL_NOTHROW ^ In file included from /usr/include/qt5/QtGui/qtransform.h:42:0, from /usr/include/qt5/QtGui/qimage.h:47, from /usr/include/qt5/QtGui/QImage:1, from /usr/include/qt5/QtQuick/qsgtexture.h:45, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtGui/qmatrix.h:66:32: error: expected ',' or '...' before '&&' token QMatrix &operator=(QMatrix &&other) Q_DECL_NOTHROW // = default ^ /usr/include/qt5/QtGui/qmatrix.h:69:21: error: expected ',' or '...' before '&&' token QMatrix(QMatrix &&other) Q_DECL_NOTHROW // = default ^ /usr/include/qt5/QtGui/qmatrix.h:69:28: error: invalid constructor; you probably meant 'QMatrix (const QMatrix&)' QMatrix(QMatrix &&other) Q_DECL_NOTHROW // = default ^ /usr/include/qt5/QtGui/qmatrix.h: In member function 'QMatrix& QMatrix::operator=(QMatrix)': /usr/include/qt5/QtGui/qmatrix.h:67:21: error: 'other' was not declared in this scope { memcpy(this, &other, sizeof(QMatrix)); return *this; } ^ In file included from /usr/include/qt5/QtGui/qimage.h:47:0, from /usr/include/qt5/QtGui/QImage:1, from /usr/include/qt5/QtQuick/qsgtexture.h:45, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/qt5/QtGui/qtransform.h: At global scope: /usr/include/qt5/QtGui/qtransform.h:79:38: error: expected ',' or '...' before '&&' token QTransform &operator=(QTransform &&other) Q_DECL_NOTHROW // = default ^ /usr/include/qt5/QtGui/qtransform.h:82:27: error: expected ',' or '...' before '&&' token QTransform(QTransform &&other) Q_DECL_NOTHROW // = default ^ /usr/include/qt5/QtGui/qtransform.h:82:34: error: invalid constructor; you probably meant 'QTransform (const QTransform&)' QTransform(QTransform &&other) Q_DECL_NOTHROW // = default ^ /usr/include/qt5/QtGui/qtransform.h: In member function 'QTransform& QTransform::operator=(QTransform)': /usr/include/qt5/QtGui/qtransform.h:80:21: error: 'other' was not declared in this scope { memcpy(this, &other, sizeof(QTransform)); return *this; } ^ In file included from /usr/include/qt5/QtGui/qopenglversionfunctions.h:58:0, from /usr/include/qt5/QtGui/qopenglcontext.h:61, from /usr/include/qt5/QtGui/qopenglfunctions.h:55, from /usr/include/qt5/QtGui/QOpenGLFunctions:1, from gstqsgtexture.h:26, from gstqsgtexture.cc:29: /usr/include/qt5/QtCore/qhash.h: In member function 'QPair::iterator, QHash::iterator> QHash::equal_range(const Key&)': /usr/include/qt5/QtCore/qhash.h:957:5: warning: 'auto' changes meaning in C++11; please remove it [-Wc++0x-compat] auto pair = qAsConst(*this).equal_range(akey); ^ /usr/include/qt5/QtCore/qhash.h:957:10: error: 'pair' does not name a type auto pair = qAsConst(*this).equal_range(akey); ^ /usr/include/qt5/QtCore/qhash.h:958:31: error: 'pair' was not declared in this scope return qMakePair(iterator(pair.first.i), iterator(pair.second.i)); ^ /usr/include/qt5/QtCore/qhash.h:958:31: note: suggested alternative: In file included from /usr/include/c++/5.4.0/utility:70:0, from /usr/include/qt5/QtCore/qcompilerdetection.h:991, from /usr/include/qt5/QtCore/qglobal.h:83, from /usr/include/qt5/QtQuick/qtquickglobal.h:43, from /usr/include/qt5/QtQuick/qsgtexture.h:43, from /usr/include/qt5/QtQuick/QSGTexture:1, from gstqsgtexture.h:25, from gstqsgtexture.cc:29: /usr/include/c++/5.4.0/bits/stl_pair.h:96:12: note: 'std::pair' struct pair ^ Makefile:940: recipe for target 'libqtsink_la-gstqsgtexture.lo' failed make[4]: *** [libqtsink_la-gstqsgtexture.lo] Error 1 make[4]: Leaving directory '/tmp/SBo/gst-plugins-bad-1.6.2/ext/qt' Makefile:830: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/tmp/SBo/gst-plugins-bad-1.6.2/ext/qt' Makefile:1361: recipe for target 'qt' failed make[2]: *** [qt] Error 2 make[2]: Leaving directory '/tmp/SBo/gst-plugins-bad-1.6.2/ext' Makefile:954: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/gst-plugins-bad-1.6.2' Makefile:883: recipe for target 'all' failed make: *** [all] Error 2 -- 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 sombragris at sombragris.org Sun Sep 25 18:34:19 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sun, 25 Sep 2016 14:34:19 -0400 Subject: [Slackbuilds-users] BUG: gst-plugins-bad building fails with Qt 5.7; workaround CONFIRMED Message-ID: <0q93i.6076cefc2c.20160925143419.275bb06b@loli.sombragris.org> Hi, Upon successful rebuild of gst-plugins-bad with soundtouch support, I can confirm that sayonara 0.9.2 now runs correctly. Thanks and best regards, 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 Sun Sep 25 21:48:40 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 26 Sep 2016 04:48:40 +0700 Subject: [Slackbuilds-users] BUG: gst-plugins-bad building fails with Qt 5.7; workaround CONFIRMED In-Reply-To: <0q93i.6076cefc2c.20160925143419.275bb06b@loli.sombragris.org> References: <0q93i.6076cefc2c.20160925143419.275bb06b@loli.sombragris.org> Message-ID: <6be15cef-298e-f5a7-7e81-ad85cbb6a309@slackbuilds.org> > Upon successful rebuild of gst-plugins-bad with soundtouch support, I > can confirm that sayonara 0.9.2 now runs correctly. Pushed the updated README 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: From johannes at schoepfer.info Sat Sep 24 19:32:49 2016 From: johannes at schoepfer.info (johannes at schoepfer.info) Date: Sat, 24 Sep 2016 21:32:49 +0200 Subject: [Slackbuilds-users] Anyone interested in taking higan? In-Reply-To: <2076ac19-6765-a44e-5866-9fefccd44ac3@slackbuilds.org> References: <3354ca2953b6481a3191266a53a0fcdc@schoepfer.info> <2076ac19-6765-a44e-5866-9fefccd44ac3@slackbuilds.org> Message-ID: <78dc8a397b964ddad0bb55ac4a81ffe2@schoepfer.info> On , Willy Sudiarto Raharjo wrote: >> I submitted it, it was updated on SBo >> https://slackbuilds.org/repository/14.2/games/higan/ , but at least >> higan.SlackBuild doesn't reflect the changes from git >> https://slackbuilds.org/cgit/slackbuilds/commit/?id=79fc90f23 > > it does reflect changes from git > perhaps a cache issue? Yes it was, sorry for the noise. Johannes From jbernts at broadpark.no Mon Sep 26 16:24:59 2016 From: jbernts at broadpark.no (Jostein Berntsen) Date: Mon, 26 Sep 2016 18:24:59 +0200 Subject: [Slackbuilds-users] mucommander link broken Message-ID: <20160926162459.GG2176@jostein> The existing mucommander download link should be corrected to: http://github.com/mucommander/mucommander/releases/download/0.9.0/mucommander-0_9_0.tar.gz Jostein From willysr at slackbuilds.org Mon Sep 26 23:00:22 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 27 Sep 2016 06:00:22 +0700 Subject: [Slackbuilds-users] mucommander link broken In-Reply-To: <20160926162459.GG2176@jostein> References: <20160926162459.GG2176@jostein> Message-ID: <34e6973f-c39e-b0b1-4978-9142b267b442@slackbuilds.org> > The existing mucommander download link should be corrected to: > > http://github.com/mucommander/mucommander/releases/download/0.9.0/mucommander-0_9_0.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: From dn2010 at gmail.com Tue Sep 27 08:06:12 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Tue, 27 Sep 2016 11:06:12 +0300 Subject: [Slackbuilds-users] pydot source and homepage Message-ID: pydot source and homepage was on googlepages, that was shut down not too far ago it seems to be moved to: https://github.com/erocarrera/pydot WBR, Daniil Bratashov. From willysr at slackbuilds.org Tue Sep 27 16:08:17 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 27 Sep 2016 23:08:17 +0700 Subject: [Slackbuilds-users] pydot source and homepage In-Reply-To: References: Message-ID: <9e6364d8-f0a8-dbbe-aef8-72b91d76b32f@slackbuilds.org> > pydot source and homepage was on googlepages, that was shut down not too far ago > > it seems to be moved to: https://github.com/erocarrera/pydot 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: From arkadiusz at drabczyk.org Tue Sep 27 20:59:31 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Tue, 27 Sep 2016 22:59:31 +0200 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool In-Reply-To: References: Message-ID: <20160927205931.GA14836@comp.a> On Fri, Sep 09, 2016 at 03:43:09PM +0200, Andrzej Telszewski wrote: > Hi, > > I have written command line submission tool for SlackBuilds.org > Before going public, I would like to ask you to give it a try and report > back any problems you might find. > As of now, I consider the tool to be feature complete (more options will > come one day), so please report back only possible errors rather than > features requests. > > Source code together with SlackBuild for it can be found here (once tested, > it will get removed): > http://www.telszewski.net/software/src/sbosubmit/ Hello Andrzej, I just used your tool and it seems to work, thank you for your work! Just one tiny remark - I accidentally had a source tarball (~2.8 MB) in a directory where I used sbosubmit and it failed with the following message: [II] creating archive... [EE] archive: Buffer exhausted It comes from libarchive and is probably caused by too large size of output archive. In current form it's quite uninformative to the user. Shouldn't it be changed to something better? IMO though it would be the best if we just sent new submissions and updates as patches directly to the mailing list as it was done during the transition from 14.1 to 14.2 instead of using the submission form. It only takes 2 commands - git-format-patch and git-send-email, much faster and comfortable. (BTW, message sent through gmane.org do not show up on the list. Does anyone else here use gmane.org?) -- Arkadiusz Drabczyk From atelszewski at gmail.com Tue Sep 27 21:29:32 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 27 Sep 2016 23:29:32 +0200 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool In-Reply-To: <20160927205931.GA14836@comp.a> References: <20160927205931.GA14836@comp.a> Message-ID: <801c2ca7-a6b9-32e2-8777-3c823355e7c5@gmail.com> On 27/09/16 22:59, Arkadiusz Drabczyk wrote: > On Fri, Sep 09, 2016 at 03:43:09PM +0200, Andrzej Telszewski wrote: >> Hi, >> >> I have written command line submission tool for SlackBuilds.org >> Before going public, I would like to ask you to give it a try and report >> back any problems you might find. >> As of now, I consider the tool to be feature complete (more options will >> come one day), so please report back only possible errors rather than >> features requests. >> >> Source code together with SlackBuild for it can be found here (once tested, >> it will get removed): >> http://www.telszewski.net/software/src/sbosubmit/ > > Hello Andrzej, > > I just used your tool and it seems to work, thank you for your work! > I'm really happy to hear that :-) I can see that you sent your SlackBuild to both the testing server and SlackBuilds.org server ;-) > Just one tiny remark - I accidentally had a source tarball (~2.8 MB) > in a directory where I used sbosubmit and it failed with the following > message: > > [II] creating archive... > [EE] archive: Buffer exhausted > > It comes from libarchive and is probably caused by too large size of > output archive. In current form it's quite uninformative to the user. > Shouldn't it be changed to something better? > The buffer size is set to 1MiB. That's actually the maximal archive size SlackBuilds.org would accept. I could probably report a differently worded message, although there is no way to tell what the archive size should be (other than it should not exceed the 1MiB). I personally do not place the source code tarball directly in the SlackBuild directory, but rather soft-link it to the source code tarball that is located under my "central" tarballs store. Using soft-linked tarball is preferred when working with sbosubmit, since soft links are skipped when creating the submission archive. This way you won't accidentally send the source code tarball within submission archive. For the record, a directory named "tmpdir" is skipped too, and it can be used as playground when developing the SlackBuild. > IMO though it would be the best if we just sent new submissions and > updates as patches directly to the mailing list as it was done during > the transition from 14.1 to 14.2 instead of using the submission form. > It only takes 2 commands - git-format-patch and git-send-email, much > faster and comfortable. > Switching to git would be a sad day for sbosubmit ;-) BTW, sbosubmit is only one command to type :-^ Once more, thanks for testing and reporting back! > (BTW, message sent through gmane.org do not show up on the list. Does > anyone else here use gmane.org?) > -- Best regards, Andrzej Telszewski From jebrhansen+SBo at gmail.com Wed Sep 28 02:39:47 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 28 Sep 2016 02:39:47 +0000 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool In-Reply-To: <801c2ca7-a6b9-32e2-8777-3c823355e7c5@gmail.com> References: <20160927205931.GA14836@comp.a> <801c2ca7-a6b9-32e2-8777-3c823355e7c5@gmail.com> Message-ID: Andrzej, Has there been any thought to add a tarball detection to the script to prevent accidental source uploading? While many tarballs are larger than 1MB and will get flagged by your side limit, not all are, and for those who keep the actual source in the slackbuild's directory may accidentally upload that to SBo. But I do like the idea of symlinking the source into the directory. I've tarred up source before (and uploaded it to git), and I need to find a better way. Jeremy On Tue, Sep 27, 2016, 5:31 PM Andrzej Telszewski wrote: > On 27/09/16 22:59, Arkadiusz Drabczyk wrote: > > On Fri, Sep 09, 2016 at 03:43:09PM +0200, Andrzej Telszewski wrote: > >> Hi, > >> > >> I have written command line submission tool for SlackBuilds.org > >> Before going public, I would like to ask you to give it a try and report > >> back any problems you might find. > >> As of now, I consider the tool to be feature complete (more options will > >> come one day), so please report back only possible errors rather than > >> features requests. > >> > >> Source code together with SlackBuild for it can be found here (once > tested, > >> it will get removed): > >> http://www.telszewski.net/software/src/sbosubmit/ > > > > Hello Andrzej, > > > > I just used your tool and it seems to work, thank you for your work! > > > > I'm really happy to hear that :-) > I can see that you sent your SlackBuild to both the testing server and > SlackBuilds.org server ;-) > > > Just one tiny remark - I accidentally had a source tarball (~2.8 MB) > > in a directory where I used sbosubmit and it failed with the following > > message: > > > > [II] creating archive... > > [EE] archive: Buffer exhausted > > > > It comes from libarchive and is probably caused by too large size of > > output archive. In current form it's quite uninformative to the user. > > Shouldn't it be changed to something better? > > > > The buffer size is set to 1MiB. That's actually the maximal archive size > SlackBuilds.org would accept. > > I could probably report a differently worded message, although there is > no way to tell what the archive size should be (other than it should not > exceed the 1MiB). > > I personally do not place the source code tarball directly in the > SlackBuild directory, but rather soft-link it to the source code tarball > that is located under my "central" tarballs store. > > Using soft-linked tarball is preferred when working with sbosubmit, > since soft links are skipped when creating the submission archive. This > way you won't accidentally send the source code tarball within > submission archive. > > For the record, a directory named "tmpdir" is skipped too, and it can be > used as playground when developing the SlackBuild. > > > IMO though it would be the best if we just sent new submissions and > > updates as patches directly to the mailing list as it was done during > > the transition from 14.1 to 14.2 instead of using the submission form. > > It only takes 2 commands - git-format-patch and git-send-email, much > > faster and comfortable. > > > > Switching to git would be a sad day for sbosubmit ;-) > BTW, sbosubmit is only one command to type :-^ > > Once more, thanks for testing and reporting back! > > > (BTW, message sent through gmane.org do not show up on the list. Does > > anyone else here use gmane.org?) > > > > > -- > 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: