From willysr at slackbuilds.org Sat Oct 1 00:54:14 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 1 Oct 2016 07:54:14 +0700 Subject: [Slackbuilds-users] Updates - 20161001.1 Message-ID: <45f7a45a-6cb2-270a-7ff9-9868a2cec6ae@slackbuilds.org> Sat Oct 1 00:30:20 UTC 2016 academic/bibletime: Updated for version 2.11_rc2. academic/sword-data-kjv: Updated for version 1.7.5. academic/sword: Updated for version 1.7.5a1. audio/quodlibet: Updated for version 3.7.1. audio/sayonara-player: Update HOMEPAGE and README. desktop/Ater-MPlayer-skin: Switch to i586 + update HOMEPAGE & DOWNLOAD. desktop/faenza-cupertino: Added (gnome icon theme). desktop/moka-icon-theme: Updated for version 5.3.3. desktop/numix-icon-theme-circle: Updated for version 2.0.3.9. desktop/paper-icon-theme: Updated for version 1.3.3. desktop/perwindowlayoutd: Switch to i586. development/Bottleneck: Switch to i586. development/Naked: Switch to i586. development/PythonToolkit: Switch to i586. development/coccinelle: Switch to i586. development/dreampie: Switch to i586. development/global: Updated for version 6.5.5. development/love: Updated for version B.02.18. development/menhir: Switch to i586. development/squeak-vm: Update README. development/sublime_text: Updated for version 3.1.26. development/tstoolbox: Updated for version 1.12.12.9. development/wheel: Switch to i586. development/xsp: Added (Mono's ASP.NET hosting server). games/FlightGear-data: Updated for version 2016.3.1, new maintainer. games/FlightGear: Updated for version 2016.3.1, new maintainer. games/doomretro: Updated for version 2.3. games/gzdoom: Updated for version 2.2.0. games/mame: Updated for version 0.178, add bgfx support. games/snes9x: Fix crash in "open recent" menu. gis/postgis: Updated for version 2.3.0. graphics/grafx2: Added alternate source. graphics/oyranos: Switch to i586. graphics/phatch: Switch to i586. graphics/pygraphviz: Switch to i586. graphics/shotwell: Updated for version 0.24.0. libraries/Atlas-C++: Switch to i586. libraries/CherryPy: Updated for version 8.1.1. libraries/ConfigParser: Switch to i586. libraries/PrettyTable: Switch to i586. libraries/PyODE: Switch to i586. libraries/SimGear: Updated for version 2016.3.1 + new maintainer. libraries/async: Switch to i586. libraries/audioread: Switch to i586. libraries/avbin: Switch to i586. libraries/bcdoc: Switch to i586. libraries/botocore: Updated for version 1.4.58. libraries/cchardet: Switch to i586. libraries/curses_ex: Switch to i586. libraries/discogs-client: Switch to i586. libraries/dropbox-python: Updated for version 6.9.0. libraries/enum34: Switch to i586. libraries/evernote-python: Switch to i586. libraries/gallerize: Updated for version 0.3.2. libraries/guppy: Switch to i586. libraries/hurry-filesize: Switch to i586. libraries/jsoncpp: Updated for version 1.7.6 libraries/kaadbg: Switch to i586. libraries/libclaw: Switch to i586. libraries/libedit: Updated for version 20160903_3.1. libraries/libfilezilla: Updated for version 0.7.0. libraries/libunibreak: Updated for version 3.0. libraries/libwfut: Switch to i586. libraries/plumbum: Switch to i586. libraries/pykdtree: Updated for version 1.2.1. libraries/pysendfile: Switch to i586. libraries/rarfile: Switch to i586. libraries/rpyc: Switch to i586. libraries/setproctitle: Switch to i586. libraries/smmap: Switch to i586. libraries/toro: Switch to i586. libraries/urdfdom: Updated for version 0.4.1. libraries/urdfdom_headers: Updated for version 0.4.1. libraries/varconf: Switch to i586. libraries/web.py: Switch to i586. libraries/webkit2gtk: Updated for version 2.14.0. libraries/wxGTK3: Update README. libraries/wxPython3: Add webkitgtk detection. multimedia/Poor-Mans-Spotify: Removed (Project name renamed). multimedia/ffmpegyag: Switch to i586. network/Flootty: Switch to i586. network/PaleMoon: Updated for version 26.5.0. network/awscli: Updated for version 1.11.0. network/etherpoke: Switch to i586. network/flexget: Updated for version 2.3.33. network/krb5: Avoid overwriting Slackware's package. network/light-firefox: Added (A light browser based on Mozilla). network/livestreamer-curses: Switch to i586. network/livestreamer: Switch to i586. network/offlineimap: Updated for version 7.0.7. network/pms-youtube: Switch to i586. network/qTox: Updated for version 20160927_427176a. network/r2e: Updated for version 2.71 + new maintainer. network/rubygem-showterm: Switch to i586. network/tixati: Updated for version 2.45_1. network/toxcore: Updated for version 20160921_161ab46. network/turbolift: Switch to i586. network/vacuum-im: Updated for version 1.2.5. network/wakeonlan: Switch to i586. network/yoda: Switch to i586. network/youtube-dl: Updated for version 2016.09.27. office/LibreOffice: Updated for version 5.2.2.2 office/TaskCoach: Switch to i586. office/etm: Removed (replaced with etmtk). office/etmtk: Added (event and task manager for console and GUI). office/libreoffice-helppack: Updated for version 5.2.2. office/libreoffice-langpack: Updated for version 5.2.2. office/libreoffice: Updated for version 5.2.2. office/marave: Switch to i586. office/minidjvu: Switch to i586. office/pyspread: Switch to i586. office/tudu: Added (todo list program). perl/perl-CPAN-Perl-Releases: Added (Mapping Perl releases). perl/perl-Devel-PatchPerl: Added (Patch perl source). perl/perl-File-pushd: Added (change directory temporarily). perl/perl-Package-DeprecationManager: Update DOWNLOAD url. perl/perl-Readonly: Updated for version 2.05. perl/perl-Scalar-List-Utils: Removed (included in perl 5.22). perl/perl-Test-Output: Added (Utilities to test STDOUT and STDERR). perl/perl-Test-Simple: Updated for version 1.302056. perl/perl-Test-Spec: Added (Write tests). perl/perl-local-lib: Added (create and use a local lib/). python/PyDispatcher: Switch to i586. python/PySDL2: Switch to i586. python/argcomplete: Switch to i586. python/argh: Switch to i586. python/args: Switch to i586. python/blessings: Switch to i586. python/chump: Switch to i586. python/cov-core: Switch to i586. python/drawille: Switch to i586. python/functools32: Switch to i586. python/guess-language: Switch to i586. python/guessit: Updated for version 2.0.4. python/i3-py: Switch to i586. python/jedi: Switch to i586. python/jsonschema: Switch to i586. python/kaptan: Switch to i586. python/lxml: Fix download url python/minidb: Switch to i586. python/ndg_httpsclient: Switch to i586. python/pendulum: Updated for version 0.6.2. python/pilkit: Switch to i586. python/pluggy: Switch to i586. python/purl: Switch to i586. python/py: Switch to i586. python/pydot: Update DOWNLOAD url + switch to i586. python/pyglet: Switch to i586. python/pymongo: Switch to i586. python/pytest: Updated for version 3.0.3. python/python-certifi: Updated for version 2016.9.26. python/python-keyutils: Switch to i586. python/python-libtmux: Switch to i586. python/python-notify2: Switch to i586. python/python-unicodecsv: Switch to i586. python/python-wrapt: Switch to i586. python/python-xcffib: Switch to i586. python/pywebkitgtk: Update download url python/queuelib: Switch to i586. python/s3transfer: Updated for version 0.1.5. python/singledispatch: Switch to i586. python/soundcloud: Switch to i586. python/sql: Switch to i586. python/termcolor: Switch to i586. python/trollius: Switch to i586. python/tzlocal: Switch to i586. python/wsgiref: Switch to i586. ruby/rubygem-bundler: Updated for version 1.13.2. ruby/rubygem-coderay: Switch to i586. ruby/rubygem-method_source: Switch to i586. ruby/rubygem-pry: Switch to i586. ruby/rubygem-slop3: Switch to i586. system/TermRecord: Switch to i586. system/autoarchive: Switch to i586. system/barman: Updated for version 2.0. system/findcmd: Switch to i586. system/flashcards: Switch to i586. system/graphterm: Switch to i586 + update HOMEPAGE. system/iucode_tool: Switch to i586 + new maintainer. system/lshw: Updated for version B.02.18. system/mdocml: Updated for version 1.13.4. system/mongo-tools: Updated for version 3.2.9. system/mongodb: Updated for version 3.2.9. system/mucommander: Update DOWNLOAD url. system/patool: Switch to i586. system/phoronix-test-suite: Updated for version 6.6.1. system/pstate-frequency: Updated for version 3.5.1. system/qdirstat: Added (disk space information). system/rar2fs: Updated for version 1.23.1. system/rar: Updated for version 5.4.0. system/redis-py: Switch to i586. system/rename: Switch to i586. system/repeat: Switch to i586. system/syslog-ng: Updated for version 3.8.1. system/termsaver: Switch to i586. system/udiskie: Switch to i586. system/unrar: Updated for version 5.4.5. system/zstd: Updated for version 1.1.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Oct 1 23:31:49 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 2 Oct 2016 06:31:49 +0700 Subject: [Slackbuilds-users] Updates - 20161001.2 Message-ID: <5686e886-cca0-836b-8e83-14c553f76a99@slackbuilds.org> Sat Oct 1 23:25:41 UTC 2016 development/composer: Updated for version 1.2.1. development/dwarf: Updated for version 20160929. development/hhvm: Updated for version 3.15.1. development/meld3: Updated for version 3.16.3. development/nodejs: Updated for version 4.6.0. development/textadept: Updated for version 9.0. development/universal-ctags: Updated for version 29ae3cc. graphics/converseen: Updated for version 0.9.5.2. libraries/CherryPy: Updated for version 8.1.2. network/filezilla: Updated for version 3.22.0. network/pentadactyl: Updated for version 20160924. office/calibre: Updated for version 2.69.0 perl/perl-Test-Simple: Updated for version 1.302059. perl/perlbrew: Added (Manage perl installations). system/progress: Added (Linux tool to show progress). +--------------------------+ -- 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 Sun Oct 2 15:31:42 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 2 Oct 2016 08:31:42 -0700 Subject: [Slackbuilds-users] Early notification for new libwebp In-Reply-To: References: <58276536-e02b-537e-2e71-4f478655c027@slackbuilds.org> Message-ID: On Sunday, September 18, 2016, Larry Hajali wrote: > qt5 is another package if built against optional libwebp dependency. > Another optional one that broke stuff for me: ffmpeg Had to recompile that and Audacity and all is well again. ;^) -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From anddt at ukr.net Sun Oct 2 15:34:57 2016 From: anddt at ukr.net (Andrew) Date: Sun, 2 Oct 2016 18:34:57 +0300 Subject: [Slackbuilds-users] Early notification for new libwebp In-Reply-To: References: <58276536-e02b-537e-2e71-4f478655c027@slackbuilds.org> Message-ID: <20161002183457.7c8df5e51ce5fe5ecdf540ee@ukr.net> On Sun, 2 Oct 2016 08:31:42 -0700 "Ryan P.C. McQuen" wrote: > Another optional one that broke stuff for me: ffmpeg And GraphicsMagick for me -- Andrew From edps.mundognu at gmail.com Sun Oct 2 22:34:01 2016 From: edps.mundognu at gmail.com (Edinaldo) Date: Sun, 02 Oct 2016 19:34:01 -0300 Subject: [Slackbuilds-users] download link for gtk-qt-engine Message-ID: new source link for SBo gtk-qt-engine: http://pkgs.fedoraproject.org/repo/pkgs/gtk-qt-engine/gtk-qt-engine-1.1.tar.bz2/de8048baef7dfe6c97cd97c463d66152/gtk-qt-engine-1.1.tar.bz2 From willysr at slackbuilds.org Sun Oct 2 23:04:57 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 3 Oct 2016 06:04:57 +0700 Subject: [Slackbuilds-users] download link for gtk-qt-engine In-Reply-To: References: Message-ID: > new source link for SBo gtk-qt-engine: > > http://pkgs.fedoraproject.org/repo/pkgs/gtk-qt-engine/gtk-qt-engine-1.1.tar.bz2/de8048baef7dfe6c97cd97c463d66152/gtk-qt-engine-1.1.tar.bz2 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 kjhambrick at gmail.com Tue Oct 4 20:01:23 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Tue, 4 Oct 2016 15:01:23 -0500 Subject: [Slackbuilds-users] Postgresql 9.5.4 ( minor ) and Postgresql 9.6.0 ( major ) Message-ID: Adis -- Postgresql version 9.5.4 is available and builds fine with the existing postgresql.SlackBuild I've been running it for a couple weeks with no issues. In addition Postgresql version 9.6.0 was released Sep'29. It also builds just fine with the existing postgresql.SlackBuild. I am still evaluating 9.6.0 but so far I've had no issues. Thanks ! -- kjh https://www.postgresql.org/ftp/source/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From titopoquito at gmail.com Tue Oct 4 20:48:49 2016 From: titopoquito at gmail.com (titopoquito) Date: Tue, 4 Oct 2016 22:48:49 +0200 Subject: [Slackbuilds-users] rdiff-backup needing patch for python >= 2.6? Message-ID: <3911e246-d0c9-27d7-cb22-e02794155bc8@gmail.com> Hi, I tried to send a mail to Paul Wisehart, who is listed as maintainer for the rdiff-backup SlackBuild, but unfortunately the email address is dead. Today I stumbled upon rdiff-backup and doing some further research I found a post* on the rdiff-backup mailing-list that indicates that a patch for python versions newer than 2.4 might be needed for it**. Is anyone actually using rdiff-backup and does it still work as expected for you? Best regards, Tito * http://lists.nongnu.org/archive/html/rdiff-backup-users/2016-08/msg00008.html ** http://pkgs.fedoraproject.org/cgit/rpms/rdiff-backup.git/tree/ - the one named rdiff-backup--popen2.patch From ricardo at palmtx.com.ar Tue Oct 4 21:23:01 2016 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Tue, 4 Oct 2016 18:23:01 -0300 Subject: [Slackbuilds-users] rdiff-backup needing patch for python >= 2.6? In-Reply-To: <3911e246-d0c9-27d7-cb22-e02794155bc8@gmail.com> References: <3911e246-d0c9-27d7-cb22-e02794155bc8@gmail.com> Message-ID: <201610041823.01588.ricardo@palmtx.com.ar> El Martes 04/10/2016, titopoquito escribi?: > Hi, > > I tried to send a mail to Paul Wisehart, who is listed as maintainer for > the rdiff-backup SlackBuild, but unfortunately the email address is dead. > > Today I stumbled upon rdiff-backup and doing some further research I > found a post* on the rdiff-backup mailing-list that indicates that a > patch for python versions newer than 2.4 might be needed for it**. > > Is anyone actually using rdiff-backup and does it still work as expected > for you? > > Best regards, > > Tito I've been using it for ages, previously on Kubuntu (up to 12.04), then Slackware (14.1 and now 14.2) with no issues at all. Actually, the website says: "Note: rdiff-backup-statistics requires Python v2.4 or later" So my guess is that mailing list post has old information. Cheers, -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From info at microlinux.fr Wed Oct 5 06:38:31 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 5 Oct 2016 08:38:31 +0200 Subject: [Slackbuilds-users] faenza-icon-theme: broken download link Message-ID: <9e9655cf-e5a4-892d-ae3c-ebb4b02c5358@microlinux.fr> Hi, The Faenza icon theme has a broken download link. Cheers, Niki PS: thanks to Robbie Workman for subscribing me here, after some technical troubles. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Wed Oct 5 06:43:25 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 5 Oct 2016 08:43:25 +0200 Subject: [Slackbuilds-users] luna-wallpapers: broken download link Message-ID: Hi, The luna-wallpapers package builds with two separate source archives. The download link for the second one (elementary-wallpapers) is broken, and I'd say it's wrong anyway. I'd recommend either hosting it on SBo's own server (if possible), or use the source archive(s) on my own server: http://www.microlinux.fr/microlinux/desktop-14.2-source/xfce/luna-wallpapers/ What I *think* happened was that the download link pointed to my site's mirror, but the URL is not exactly correct. Here's the correct one: http://slackware.uk/microlinux/desktop-14.2-source/xfce/luna-wallpapers/ Upon reflectino, maybe it's better to point to that one, since it seems to have way more bandwidth than my own server. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Wed Oct 5 07:40:49 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 5 Oct 2016 14:40:49 +0700 Subject: [Slackbuilds-users] faenza-icon-theme: broken download link In-Reply-To: <9e9655cf-e5a4-892d-ae3c-ebb4b02c5358@microlinux.fr> References: <9e9655cf-e5a4-892d-ae3c-ebb4b02c5358@microlinux.fr> Message-ID: <852196d1-15d7-4a58-91ed-717110637a56@slackbuilds.org> > The Faenza icon theme has a broken download link. Fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From didier at slint.fr Wed Oct 5 08:08:45 2016 From: didier at slint.fr (Didier Spaier) Date: Wed, 5 Oct 2016 10:08:45 +0200 Subject: [Slackbuilds-users] luna-wallpapers: broken download link In-Reply-To: References: Message-ID: Hi, Le 05/10/2016 ? 08:43, Nicolas Kovacs a ?crit : > The luna-wallpapers package builds with two separate source archives. > The download link for the second one (elementary-wallpapers) is broken, > and I'd say it's wrong anyway. I'd recommend either hosting it on SBo's > own server (if possible), or use the source archive(s) on my own server: > > http://www.microlinux.fr/microlinux/desktop-14.2-source/xfce/luna-wallpapers/ > > What I *think* happened was that the download link pointed to my site's > mirror, but the URL is not exactly correct. Here's the correct one: > > http://slackware.uk/microlinux/desktop-14.2-source/xfce/luna-wallpapers/ > > Upon reflectino, maybe it's better to point to that one, since it seems > to have way more bandwidth than my own server. This leads to a question: is the archive the same as in sbosrcarch? http://slackware.uk/sbosrcarch/by-name/desktop/luna-wallpapers/ I ask because this one is also hosted by Darren, PS It seems to be the case: http://slackware.uk/sbosrcarch/by-md5/1/5/153357336d6c727669127c27d64cf5a1/ Cheers, Didier From klaatu at member.fsf.org Wed Oct 5 08:24:09 2016 From: klaatu at member.fsf.org (Klaatu) Date: Wed, 5 Oct 2016 21:24:09 +1300 Subject: [Slackbuilds-users] rdiff-backup needing patch for python >= 2.6? In-Reply-To: <201610041823.01588.ricardo@palmtx.com.ar> References: <3911e246-d0c9-27d7-cb22-e02794155bc8@gmail.com> <201610041823.01588.ricardo@palmtx.com.ar> Message-ID: <91dd4410-a013-26ee-57ee-f7a808350047@member.fsf.org> I use rdiff-backup and have for quite some time. There's no patch required. Just install and use. If you want to use librsync 2.0, then there's a patch for that, but otherwise it just works on Slackware 14.2 -klaatu On 05/10/16 10:23, Ricardo J. Barberis wrote: > El Martes 04/10/2016, titopoquito escribi?: >> Hi, >> >> I tried to send a mail to Paul Wisehart, who is listed as maintainer for >> the rdiff-backup SlackBuild, but unfortunately the email address is dead. >> >> Today I stumbled upon rdiff-backup and doing some further research I >> found a post* on the rdiff-backup mailing-list that indicates that a >> patch for python versions newer than 2.4 might be needed for it**. >> >> Is anyone actually using rdiff-backup and does it still work as expected >> for you? >> >> Best regards, >> >> Tito > > I've been using it for ages, previously on Kubuntu (up to 12.04), then > Slackware (14.1 and now 14.2) with no issues at all. > > Actually, the website says: > > "Note: rdiff-backup-statistics requires Python v2.4 or later" > > So my guess is that mailing list post has old information. > > Cheers, > From info at microlinux.fr Wed Oct 5 09:15:49 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 5 Oct 2016 11:15:49 +0200 Subject: [Slackbuilds-users] luna-wallpapers: broken download link In-Reply-To: References: Message-ID: <00c22b4c-53a0-38c8-3df1-f8e60183fe5e@microlinux.fr> Le 05/10/2016 ? 10:08, Didier Spaier a ?crit : > This leads to a question: is the archive the same as in sbosrcarch? > http://slackware.uk/sbosrcarch/by-name/desktop/luna-wallpapers/ > > I ask because this one is also hosted by Darren, > > PS It seems to be the case: > http://slackware.uk/sbosrcarch/by-md5/1/5/153357336d6c727669127c27d64cf5a1/ I hope it is. Darren from slackware.uk is kindly mirroring my stuff. :o) Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Wed Oct 5 10:13:20 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 5 Oct 2016 17:13:20 +0700 Subject: [Slackbuilds-users] Another Maintainer Needed Message-ID: Hi all, vvoody is no longer using Slackware, so his packages are free for grabs python/virtualenvwrapper python/virtualenv-clone network/opera network/fqterm network/mew anyone want to take over this package? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From d.zlatanidis at gmail.com Wed Oct 5 10:36:56 2016 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Wed, 5 Oct 2016 13:36:56 +0300 Subject: [Slackbuilds-users] Another Maintainer Needed In-Reply-To: References: Message-ID: <4b5176ed-76da-16b0-450a-71917dacd5af@gmail.com> I'll take both python packages: python/virtualenvwrapper python/virtualenv-clone On 10/05/2016 01:13 PM, Willy Sudiarto Raharjo wrote: > Hi all, > > vvoody is no longer using Slackware, so his packages are free for grabs > > python/virtualenvwrapper > python/virtualenv-clone > network/opera > network/fqterm > network/mew > > anyone want to take over this package? > > > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From titopoquito at gmail.com Wed Oct 5 13:50:26 2016 From: titopoquito at gmail.com (titopoquito) Date: Wed, 5 Oct 2016 15:50:26 +0200 Subject: [Slackbuilds-users] rdiff-backup needing patch for python >= 2.6? In-Reply-To: <201610041823.01588.ricardo@palmtx.com.ar> References: <3911e246-d0c9-27d7-cb22-e02794155bc8@gmail.com> <201610041823.01588.ricardo@palmtx.com.ar> Message-ID: <0a343103-e1b8-c985-a9a9-9c51599cca38@gmail.com> Thanks Ricardo and klaatu, that answers my question :) Am 04.10.2016 um 23:23 schrieb Ricardo J. Barberis: > El Martes 04/10/2016, titopoquito escribi?: >> Hi, >> >> I tried to send a mail to Paul Wisehart, who is listed as maintainer for >> the rdiff-backup SlackBuild, but unfortunately the email address is dead. >> >> Today I stumbled upon rdiff-backup and doing some further research I >> found a post* on the rdiff-backup mailing-list that indicates that a >> patch for python versions newer than 2.4 might be needed for it**. >> >> Is anyone actually using rdiff-backup and does it still work as expected >> for you? >> >> Best regards, >> >> Tito > > I've been using it for ages, previously on Kubuntu (up to 12.04), then > Slackware (14.1 and now 14.2) with no issues at all. > > Actually, the website says: > > "Note: rdiff-backup-statistics requires Python v2.4 or later" > > So my guess is that mailing list post has old information. > > Cheers, > From edps.mundognu at gmail.com Wed Oct 5 22:24:15 2016 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 05 Oct 2016 19:24:15 -0300 Subject: [Slackbuilds-users] Another Maintainer Needed Message-ID: I'll take: network/opera Thanks, Edinaldo. From glenn.becker at gmail.com Wed Oct 5 23:59:19 2016 From: glenn.becker at gmail.com (Glenn Becker) Date: Wed, 5 Oct 2016 19:59:19 -0400 Subject: [Slackbuilds-users] Another Maintainer Needed In-Reply-To: References: Message-ID: I'll take mew and fqterm. Glenn On Wed, Oct 5, 2016 at 6:13 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Hi all, > > vvoody is no longer using Slackware, so his packages are free for grabs > > python/virtualenvwrapper > python/virtualenv-clone > network/opera > network/fqterm > network/mew > > anyone want to take over 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/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fellype at gmail.com Thu Oct 6 20:04:16 2016 From: fellype at gmail.com (Fellype do Nascimento) Date: Thu, 6 Oct 2016 17:04:16 -0300 Subject: [Slackbuilds-users] BUG: sayonara-player 0.9.2 segfaults; complex, untested workaround In-Reply-To: <0q93i.607612f724.20160925135209.6d753e72@loli.sombragris.org> References: <0q93i.607612f724.20160925135209.6d753e72@loli.sombragris.org> Message-ID: <222aa51a-d737-ed0f-9cf0-ca3552ec97e4@gmail.com> > 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. > It is right. gst-plugins-bad must be compiled with soundtouch support in order to enable sayonara-player to run properly. I've recompiled gst-plugins-bad after install soundtouch and sayonara-player runs fine now. But soundtouch is currently assigned as an optional dependency for gst-plugins-bad. Is it possible to assign soundtouch as a required dep of gst-plugins-bad? Regards, Fellype From willysr at slackbuilds.org Thu Oct 6 23:46:49 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 7 Oct 2016 06:46:49 +0700 Subject: [Slackbuilds-users] BUG: sayonara-player 0.9.2 segfaults; complex, untested workaround In-Reply-To: <222aa51a-d737-ed0f-9cf0-ca3552ec97e4@gmail.com> References: <0q93i.607612f724.20160925135209.6d753e72@loli.sombragris.org> <222aa51a-d737-ed0f-9cf0-ca3552ec97e4@gmail.com> Message-ID: > It is right. gst-plugins-bad must be compiled with soundtouch support in > order to enable sayonara-player to run properly. I've recompiled > gst-plugins-bad after install soundtouch and sayonara-player runs fine now. > But soundtouch is currently assigned as an optional dependency for > gst-plugins-bad. > Is it possible to assign soundtouch as a required dep of gst-plugins-bad? I have added a NOTE on sayonara-player about soundtouch is needed before installing gst-plugins-bad. Instead of adding soundtouch as hard dep for gst-plugins-* to fix a single package, i propose to add soundtouch as hard dep of sayonara-player with a note that it should be installed before installing gst-plugins-bad. -- 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 Fri Oct 7 02:38:53 2016 From: yalhcru at gmail.com (B Watson) Date: Thu, 6 Oct 2016 22:38:53 -0400 Subject: [Slackbuilds-users] BUG: sayonara-player 0.9.2 segfaults; complex, untested workaround In-Reply-To: References: <0q93i.607612f724.20160925135209.6d753e72@loli.sombragris.org> <222aa51a-d737-ed0f-9cf0-ca3552ec97e4@gmail.com> Message-ID: On 10/6/16, Willy Sudiarto Raharjo wrote: > Instead of adding soundtouch as hard dep for gst-plugins-* to fix a > single package, i propose to add soundtouch as hard dep of > sayonara-player with a note that it should be installed before > installing gst-plugins-bad. List soundtouch first in REQUIRES. It'll help out the most common case, someone using sbopkg to install all the deps (assuming gst-plugins-bad wasn't already installed without soundtouch support). At least, most people will install all the deps in order. From atelszewski at gmail.com Fri Oct 7 11:07:27 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 7 Oct 2016 13:07:27 +0200 Subject: [Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool In-Reply-To: References: <20160927205931.GA14836@comp.a> <801c2ca7-a6b9-32e2-8777-3c823355e7c5@gmail.com> Message-ID: <5eb1810e-cd60-7526-be00-b11905bf312e@gmail.com> On 28/09/16 04:39, Jeremy Hansen wrote: > 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. I've been thinking about that, primarily for the purpose of ensuring correct MD5 sums in the info file. Then, if I had the tarball name, it would be easy to skip adding it to the submission archive. Unfortunately, determining the source code tarball name does not look like an obvious task. Still, I might try to do it one day. Anyways, I know it's not the solution you asked for, but sbosubmit list the submission archive contents before the actual submission happens. So you can visually inspect the submission archive for the presence of any unwanted files. I used to do it before I created sbosubmit, that is I was looking inside the tarred SlackBuild directory, to see if there aren't any problematic files. -- Best regards, Andrzej Telszewski From fellype at gmail.com Fri Oct 7 13:17:47 2016 From: fellype at gmail.com (Fellype do Nascimento) Date: Fri, 7 Oct 2016 10:17:47 -0300 Subject: [Slackbuilds-users] BUG: sayonara-player 0.9.2 segfaults; complex, untested workaround In-Reply-To: References: <0q93i.607612f724.20160925135209.6d753e72@loli.sombragris.org> <222aa51a-d737-ed0f-9cf0-ca3552ec97e4@gmail.com> Message-ID: <8e1fc51d-7ccd-6d67-2b5e-6027e2433bb5@gmail.com> On 10/06/2016 11:38 PM, B Watson wrote: > On 10/6/16, Willy Sudiarto Raharjo wrote: > >> Instead of adding soundtouch as hard dep for gst-plugins-* to fix a >> single package, i propose to add soundtouch as hard dep of >> sayonara-player with a note that it should be installed before >> installing gst-plugins-bad. > List soundtouch first in REQUIRES. It'll help out the most common case, > someone using sbopkg to install all the deps (assuming gst-plugins-bad > wasn't already installed without soundtouch support). At least, most > people will install all the deps in order. To list soundtouch as a dep of sayonara-player will solve the problem *if* gst-plugins-bad wasn't already installed without soundtouch support. But if gst-plugins-bad is already installed, it will be necessary to recompile it after install soundtouch. I think that the note must contain this information. Fellype From willysr at slackbuilds.org Sat Oct 8 01:24:50 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 8 Oct 2016 08:24:50 +0700 Subject: [Slackbuilds-users] Updates - 20161008.1 Message-ID: Sat Oct 8 01:09:57 UTC 2016 academic/biblesync: Switch to i586. academic/cblas: Updated for version 3.6.1. academic/stellarium: Updated for version 0.15.0. academic/xiphos: Switch to i586. audio/flacon: Updated for version 2.1.0. audio/qmmp-plugin-pack: Updated for version 0.10.2. audio/snd: Updated for version 16.8. audio/sunvox: Updated for version 1.9.1. desktop/faenza-icon-theme: Fix DOWNLOAD url. desktop/gxkb: Updated for version 0.7.8. desktop/i3minator: Switch to i586. desktop/luna-wallpapers: Fix DOWNLOAD url. desktop/moka-icon-theme: Updated for version 5.3.5. desktop/neofetch: Updated for version 1.8.1. desktop/numix-gtk-theme: Added (modern flat theme). desktop/paper-icon-theme: Updated for version 1.3.4. desktop/pyful: Switch to i586. desktop/xfce4-eyes-plugin: Switch to i586. development/SQLAlchemy: Updated for version 1.1.0. development/hub: Updated for version 2.2.9. development/mono: Updated for version 4.6.1.3. development/monodevelop: Updated for version 6.1.1.15. development/pandas: Updated for version 0.19.0. development/rarian: Switch to i586. games/doomretro: Updated for version 2.3.1. games/ember: Switch to i586. games/fuse-emulator: Updated for version 1.3.0. games/mgba: Updated for version 0.5.1. games/miscom: Added (textmode Missile Command clone). games/trackballs: Install icons correctly. graphics/Blender: Updated for version 2.78 graphics/CairoSVG: Switch to i586. graphics/PyMOL: Switch to i586. graphics/fim: Switch to i586. graphics/pngcrush: Updated for version 1.8.7. graphics/ristretto: Updated for version 0.8.1. libraries/HawkNL: Switch to i586. libraries/blas: Updated for version 3.6.1. libraries/futures: Switch to i586. libraries/gtk-qt-engine: Update DOWNLOAD url. libraries/imageloader: Switch to i586. libraries/lapack: Updated for version 3.6.1. libraries/libspectrum: Updated for version 1.3.0. libraries/ordereddict: Switch to i586. libraries/python-librtmp: Switch to i586. multimedia/beets: Switch to i586. multimedia/devedeng: Updated for version 4.8.2. multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 53.0. multimedia/x265: Updated for version 2.1. network/DarTui: Switch to i586. network/Electrum: Updated for version 2.7.2. network/Free-Cinema: Switch to i586. network/aldryn-client: Switch to i586. network/aria2: Updated for version 1.27.1. network/asciinema: Updated for version 1.3.0. network/flexget: Updated for version 2.3.41. network/google-cli: Updated for version 2.8. network/krb5: Updated for version 1.14.4. network/mps-youtube: Switch to i586. network/mps: Switch to i586. network/mrtg: Switch to i586. network/opensmtpd: Updated for version 6.0.1p1. network/opera-developer: Added (Fast and secure web browser). network/opera-next: Removed (replaced with opera-developer). network/opera: New maintainer. network/r2e: Update README. network/telegram: Updated for version 0.10.11. network/vivaldi: Updated for version 1.4.589.38. network/wireshark: Updated for version 2.2.1. network/youtube-dl: Updated for version 2016.10.02. office/sigil: Update download link office/teapot: Added (ncurses based spreadsheet). office/tpp: Added (text based presentation tool for the CLI). python/PyColorizer: Switch to i586. python/PyGithub: Updated for version 1.29. python/Scrapy: Updated for version 1.2.0. python/asciimatics: Added (APIs to create ASCII art animations). python/cairocffi: Switch to i586. python/colorama: Switch to i586. python/coverage: Updated for version 4.2. python/cryptography: Restore DEPS. python/dnspython: Updated for version 1.15.0 python/docopt: Switch to i586. python/fudge: Updated for version 1.1.0. python/monty: Updated for version 0.9.6. python/npyscreen: Switch to i586. python/path.py: Switch to i586. python/progressive: Switch to i586. python/ptpython: Switch to i586. python/pySmartDL: Switch to i586. python/python-distro: Added (Linux OS platform information API). python/python-future: Switch to i586. python/python-keyring: Switch to i586. python/python-tvrage: Switch to i586. python/python3-future: Switch to i586. python/selenium: Switch to i586. python/tox: Switch to i586. python/virtualenv-clone: Updated for version 0.2.6 + new maintainer. python/virtualenvwrapper: Updated for version 4.7.2, new maintainer. ruby/ncurses-ruby: Added (Ruby module for accessing the ncurses). ruby/ruby-sass: Added (Sass is an extension of CSS). system/Iosevka: Updated for version 1.9.4. system/conky: Updated for version 1.10.5. system/ddg: Switch to i586. system/eaglemode: Switch to i586. system/forkstat: Updated for version 0.01.15. system/genext2fs: Added (generate ext2 filesystem as a normal user). system/guix: Remove patch. system/letsencrypt: Updated for version 0.9.1. system/openrc: Updated for version 0.22.2. system/sentimental-skk: Switch to i586. system/tmuxp: Updated for version 1.2.2. system/webmin: Updated for version 1.820. system/wine-staging: Updated for version 1.9.20. system/xonsh: Updated for version 0.4.7. +--------------------------+ -- 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 adis at linux.org.ba Sat Oct 8 03:21:53 2016 From: adis at linux.org.ba (Adis Nezirovic) Date: Sat, 8 Oct 2016 05:21:53 +0200 Subject: [Slackbuilds-users] Postgresql 9.5.4 ( minor ) and Postgresql 9.6.0 ( major ) In-Reply-To: References: Message-ID: Hello, Great to hear that, I was planning to submit updated script this weekend :-) Best regards, Adis From sombragris at sombragris.org Sat Oct 8 12:54:25 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sat, 8 Oct 2016 09:54:25 -0300 Subject: [Slackbuilds-users] BUG: ncurses-ruby fails MD5 Message-ID: <0q93i.4089a6ca3c.20161008095425.2032ad58@loli.sombragris.org> Hi there: I just want to notify that we have a MD5 mismatch in ncurses-ruby: > ncurses-ruby: > MD5SUM check for ncurses-ruby-1.2.4.gem ... FAILED! > Expected: > b140259492780978d6537f08427d28d1a1759111c030edba833f8e90ff09bd2f > Found: b140259492780978d6537f08427d28d1 Downloading again. 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 Sat Oct 8 14:43:57 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 8 Oct 2016 21:43:57 +0700 Subject: [Slackbuilds-users] BUG: ncurses-ruby fails MD5 In-Reply-To: <0q93i.4089a6ca3c.20161008095425.2032ad58@loli.sombragris.org> References: <0q93i.4089a6ca3c.20161008095425.2032ad58@loli.sombragris.org> Message-ID: > I just want to notify that we have a MD5 mismatch in ncurses-ruby: > >> ncurses-ruby: >> MD5SUM check for ncurses-ruby-1.2.4.gem ... FAILED! >> Expected: >> b140259492780978d6537f08427d28d1a1759111c030edba833f8e90ff09bd2f >> Found: b140259492780978d6537f08427d28d1 Downloading again. Thanks, it's fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hostmaster at slackonly.com Sun Oct 9 13:20:59 2016 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 9 Oct 2016 06:20:59 -0700 Subject: [Slackbuilds-users] monkey-studio Message-ID: Hi! The source for monkey-studio is dead... New source: http://slackware.uk/sbosrcarch/by-md5/1/b/1b76fdaf9293ab160ca90ff919440598/mks_1.9.0.4-src.tar.gz Thanks From slack at lodpp.net Sun Oct 9 14:51:06 2016 From: slack at lodpp.net (Nico) Date: Sun, 9 Oct 2016 16:51:06 +0200 Subject: [Slackbuilds-users] Postgresql 9.5.4 ( minor ) and Postgresql 9.6.0 ( major ) In-Reply-To: References: Message-ID: <04fa9212-7592-d31f-77c2-e929477c7f4e@lodpp.net> Hi Adis, Jumpin` on the thread. Is there any reason to avoid building pgsql without all extensions (contrib stuff )? I needed some other extension than the default you put: # adminpack - helper extension for pgAdmin # pgcrypto - extension for some business applications # ltree, xml2 - useful extensions for developers # postgres_fdw - foreign-data wrapper for access to external PostgreSQL servers # file_fdw - foreign-data wrapper for access to data files on filesystem I've added hstore + citext, both where need to use NIPAP (ipam) Thanks Nico On 10/08/2016 05:21 AM, Adis Nezirovic wrote: > Hello, > > Great to hear that, I was planning to submit updated script this weekend :-) > > Best regards, > Adis > _______________________________________________ > 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 emmanueln at gmail.com Sun Oct 9 19:38:22 2016 From: emmanueln at gmail.com (Emmanuel) Date: Sun, 9 Oct 2016 16:38:22 -0300 Subject: [Slackbuilds-users] Ganglia and OpenMPI updates Message-ID: Hi All, I'm about to send an update package for OpenMPI (update to version 1.10.4 and with some modifications suggested by Kyle Guinn) and I'm preparing a SBo package for Ganglia and Ganglia-web. Ganglia was present in Slackbuilds up to 12.2, the maintainer was Cherife Li, does anyone knows if he is still active in the mailing list? Can I take over as the maintainer of the Ganglia package? Thanks -- ***************** Emmanuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From adis at linux.org.ba Sun Oct 9 19:53:09 2016 From: adis at linux.org.ba (Adis Nezirovic) Date: Sun, 9 Oct 2016 21:53:09 +0200 Subject: [Slackbuilds-users] Postgresql 9.5.4 ( minor ) and Postgresql 9.6.0 ( major ) In-Reply-To: <04fa9212-7592-d31f-77c2-e929477c7f4e@lodpp.net> References: <04fa9212-7592-d31f-77c2-e929477c7f4e@lodpp.net> Message-ID: Hey Nico, Actually, we try to keep it simple by not building it all, usually an extension gets enabled if someone complains, so I guess it's time to expand the list (if nobody objects). Best regards, Adis On Sun, Oct 9, 2016 at 4:51 PM, Nico wrote: > Hi Adis, > > > Jumpin` on the thread. > > Is there any reason to avoid building pgsql without all extensions (contrib > stuff )? > > I needed some other extension than the default you put: > > # adminpack - helper extension for pgAdmin > # pgcrypto - extension for some business applications > # ltree, xml2 - useful extensions for developers > # postgres_fdw - foreign-data wrapper for access to external PostgreSQL > servers > # file_fdw - foreign-data wrapper for access to data files on filesystem > > I've added hstore + citext, both where need to use NIPAP (ipam) > > > Thanks > > Nico > > > > On 10/08/2016 05:21 AM, Adis Nezirovic wrote: >> >> Hello, >> >> Great to hear that, I was planning to submit updated script this weekend >> :-) >> >> Best regards, >> Adis >> _______________________________________________ >> 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 fernando.lopezjr at gmail.com Mon Oct 10 06:55:35 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 10 Oct 2016 00:55:35 -0600 Subject: [Slackbuilds-users] keepassx update? Message-ID: Which one is the latest stable version available? 2.0.3 or 0.4.4? I dont see any indication that 0.4.4 is beta I believe they are not compatible and it is based on Qt 5. Is there any way you could update to latest stable version? thank you. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From navigium at grindcore.ch Mon Oct 10 07:12:46 2016 From: navigium at grindcore.ch (Beni) Date: Mon, 10 Oct 2016 09:12:46 +0200 Subject: [Slackbuilds-users] keepassx update? In-Reply-To: References: Message-ID: I'm using keepassx 2.0.2 from Slackbuilds https://slackbuilds.org/repository/14.2/office/keepassx/ It works quite well. Are you still on 14.1? This Slackbuild wasn't updated https://slackbuilds.org/repository/14.1/office/keepassx Regards Beni On 10/10/2016 08:55 AM, Fernando Lopez wrote: > Which one is the latest stable version available? 2.0.3 or 0.4.4? I dont > see any indication that 0.4.4 is beta I believe they are not compatible > and it is based on Qt 5. > > Is there any way you could update to latest stable version? > > thank you. > > -- > > ------------ > Regards, > Fernando Lopez Jr. > > > _______________________________________________ > 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 navigium at grindcore.ch Mon Oct 10 07:12:56 2016 From: navigium at grindcore.ch (Beni) Date: Mon, 10 Oct 2016 09:12:56 +0200 Subject: [Slackbuilds-users] keepassx update? In-Reply-To: References: Message-ID: <615d1a01-d219-f042-ffc4-b3c690b7546a@grindcore.ch> I'm using keepassx 2.0.2 from Slackbuilds https://slackbuilds.org/repository/14.2/office/keepassx/ It works quite well. Are you still on 14.1? This Slackbuild wasn't updated https://slackbuilds.org/repository/14.1/office/keepassx Regards Beni On 10/10/2016 08:55 AM, Fernando Lopez wrote: > Which one is the latest stable version available? 2.0.3 or 0.4.4? I dont > see any indication that 0.4.4 is beta I believe they are not compatible > and it is based on Qt 5. > > Is there any way you could update to latest stable version? > > thank you. > > -- > > ------------ > Regards, > Fernando Lopez Jr. > > > _______________________________________________ > 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 Mon Oct 10 07:17:02 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 10 Oct 2016 01:17:02 -0600 Subject: [Slackbuilds-users] keepassx update? In-Reply-To: <615d1a01-d219-f042-ffc4-b3c690b7546a@grindcore.ch> References: <615d1a01-d219-f042-ffc4-b3c690b7546a@grindcore.ch> Message-ID: i believe latest is 2.0.3 isn't? is it based on Qt5? On Mon, Oct 10, 2016 at 1:12 AM, Beni wrote: > I'm using keepassx 2.0.2 from Slackbuilds > > https://slackbuilds.org/repository/14.2/office/keepassx/ > > It works quite well. Are you still on 14.1? This Slackbuild wasn't updated > > https://slackbuilds.org/repository/14.1/office/keepassx > > Regards > > Beni > > On 10/10/2016 08:55 AM, Fernando Lopez wrote: > > Which one is the latest stable version available? 2.0.3 or 0.4.4? I dont > > see any indication that 0.4.4 is beta I believe they are not compatible > > and it is based on Qt 5. > > > > Is there any way you could update to latest stable version? > > > > thank you. > > > > -- > > > > ------------ > > Regards, > > Fernando Lopez Jr. > > > > > > _______________________________________________ > > 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/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Mon Oct 10 07:21:55 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 10 Oct 2016 09:21:55 +0200 Subject: [Slackbuilds-users] keepassx update? In-Reply-To: References: Message-ID: 2016-10-10 8:55 GMT+02:00 Fernando Lopez : > Which one is the latest stable version available? 2.0.3 or 0.4.4? I dont see > any indication that 0.4.4 is beta I believe they are not compatible and it > is based on Qt 5. > > Is there any way you could update to latest stable version? > > thank you. Hi Fernando, as you can see on their site, 2.0.3 is the last version, released just two days ago, with the previous one being 2.0.2 (what we have on SBo). https://www.keepassx.org/releases/?C=M;O=A https://www.keepassx.org/news still on their site you can read that they moved to the stable version version 2.0.x, that ATM uses qt4, after many years. https://www.keepassx.org/news/2015/12/533 (it's available also in the news page linked above) note that 2.0.x versions, use version 2 of the database to store credentials: be aware that converting a database that you were using with version 0.4.4 is a one-way operation (you can't convert it back). FYI, I tested here a simple version bump in the SlackBuild to 2.0.3 and it seems all is well. Matteo From arkadiusz at drabczyk.org Mon Oct 10 07:31:17 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Mon, 10 Oct 2016 02:31:17 -0500 Subject: [Slackbuilds-users] Ganglia and OpenMPI updates In-Reply-To: References: Message-ID: <291cdde572200c3e7c41fc3e5daefa60@drabczyk.org> On 2016-10-09 14:38, Emmanuel wrote: > Hi All, > > I'm about to send an update package for OpenMPI (update to version > 1.10.4 and with some modifications suggested by Kyle Guinn) and I'm > preparing a SBo package for Ganglia and Ganglia-web. > > Ganglia was present in Slackbuilds up to 12.2, the maintainer was > Cherife Li, does anyone knows if he is still active in the mailing > list? Can I take over as the maintainer of the Ganglia package? It would be good if you first tried to contact Cherife Li directly outside of the mailing list and only when he confirms he doesn't maintain the package anymore or does not reply within a reasonable time frame you could step in as a new maintainer. I did a couple of times and people always replied. Some of them don't use Slackware and don't read this mailing list anymore. -- Arkadiusz Drabczyk From matteo.bernardini at gmail.com Mon Oct 10 07:41:42 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 10 Oct 2016 09:41:42 +0200 Subject: [Slackbuilds-users] Ganglia and OpenMPI updates In-Reply-To: <291cdde572200c3e7c41fc3e5daefa60@drabczyk.org> References: <291cdde572200c3e7c41fc3e5daefa60@drabczyk.org> Message-ID: 2016-10-10 9:31 GMT+02:00 Arkadiusz Drabczyk : > On 2016-10-09 14:38, Emmanuel wrote: >> >> Hi All, >> >> I'm about to send an update package for OpenMPI (update to version >> 1.10.4 and with some modifications suggested by Kyle Guinn) and I'm >> preparing a SBo package for Ganglia and Ganglia-web. >> >> Ganglia was present in Slackbuilds up to 12.2, the maintainer was >> Cherife Li, does anyone knows if he is still active in the mailing >> list? Can I take over as the maintainer of the Ganglia package? > > > It would be good if you first tried to contact Cherife Li directly > outside of the mailing list and only when he confirms he doesn't > maintain the package anymore or does not reply within a reasonable > time frame you could step in as a new maintainer. I did a couple of > times and people always replied. Some of them don't use Slackware and > don't read this mailing list anymore. yes, this is, IMHO, the best path to follow to step in as a maintainer. but in this specific case, although a mail won't hurt, I think it's safe to say that Cherife is completely inactive from at least six years and an half https://slackbuilds.org/cgit/slackbuilds/log/?qt=author&q=cherife also other stuff that he was maintaining has already been inherited by other people so I'll say it's fine if you go with it. Matteo From info at microlinux.fr Mon Oct 10 09:59:32 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Mon, 10 Oct 2016 11:59:32 +0200 Subject: [Slackbuilds-users] Problem with VLC: Inconsistency detected Message-ID: Hi, I have VLC 2.2.4 installed on Slackware64 14.2. It stopped working after a recent upgrade. When I launch it from the command line, here's what I get: --8<----------------------------- Inconsistency detected by ld.so: dl-tls.c: 74: _dl_next_tls_modid: Assertion `result <= GL(dl_tls_max_dtv_idx) + 1' failed! --8<----------------------------- Any idea what's wrong here? Cheers, Niki PS: also posted on LQ. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From chris.willing at iinet.net.au Mon Oct 10 12:26:39 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 10 Oct 2016 22:26:39 +1000 Subject: [Slackbuilds-users] Problem with VLC: Inconsistency detected In-Reply-To: References: Message-ID: <41792259-d516-6dd3-6c5a-19a16a51e3fb@iinet.net.au> On 10/10/16 19:59, Nicolas Kovacs wrote: > Hi, > > I have VLC 2.2.4 installed on Slackware64 14.2. It stopped working after > a recent upgrade. When I launch it from the command line, here's what I get: > > --8<----------------------------- > Inconsistency detected by ld.so: dl-tls.c: 74: _dl_next_tls_modid: > Assertion `result <= GL(dl_tls_max_dtv_idx) + 1' failed! > --8<----------------------------- > > Any idea what's wrong here? > > Cheers, > > Niki > > PS: also posted on LQ. > I saw the post at LQ first and responded there. In short, no idea why you're seeing that problem but since some vlc dependencies have had updates recently, a simple rebuild of vlc may fix it. chris From emmanueln at gmail.com Mon Oct 10 12:45:43 2016 From: emmanueln at gmail.com (Emmanuel) Date: Mon, 10 Oct 2016 09:45:43 -0300 Subject: [Slackbuilds-users] Ganglia and OpenMPI updates In-Reply-To: References: <291cdde572200c3e7c41fc3e5daefa60@drabczyk.org> Message-ID: On Mon, Oct 10, 2016 at 4:41 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2016-10-10 9:31 GMT+02:00 Arkadiusz Drabczyk : > > On 2016-10-09 14:38, Emmanuel wrote: > >> > >> Hi All, > >> > >> I'm about to send an update package for OpenMPI (update to version > >> 1.10.4 and with some modifications suggested by Kyle Guinn) and I'm > >> preparing a SBo package for Ganglia and Ganglia-web. > >> > >> Ganglia was present in Slackbuilds up to 12.2, the maintainer was > >> Cherife Li, does anyone knows if he is still active in the mailing > >> list? Can I take over as the maintainer of the Ganglia package? > > > > > > It would be good if you first tried to contact Cherife Li directly > > outside of the mailing list and only when he confirms he doesn't > > maintain the package anymore or does not reply within a reasonable > > time frame you could step in as a new maintainer. I did a couple of > > times and people always replied. Some of them don't use Slackware and > > don't read this mailing list anymore. > > yes, this is, IMHO, the best path to follow to step in as a maintainer. > > but in this specific case, although a mail won't hurt, I think it's > safe to say that Cherife is completely inactive from at least six > years and an half > > https://slackbuilds.org/cgit/slackbuilds/log/?qt=author&q=cherife > > also other stuff that he was maintaining has already been inherited by > other people so I'll say it's fine if you go with it. > > Thanks for the reply, I will send an email to Cherife first and wait a couple of days. Regards > 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/ > > -- ***************** Emmanuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at lodpp.net Mon Oct 10 18:40:21 2016 From: slack at lodpp.net (Nico) Date: Mon, 10 Oct 2016 20:40:21 +0200 Subject: [Slackbuilds-users] Postgresql 9.5.4 ( minor ) and Postgresql 9.6.0 ( major ) In-Reply-To: References: <04fa9212-7592-d31f-77c2-e929477c7f4e@lodpp.net> Message-ID: <89fbf98d-8ee4-5400-80b2-6d3e8db5f32a@lodpp.net> Adis, Thanks for the feedback, that makes sense, light is right :) Maybe another solution could be to add all the extension in the slackbuild, but comment them. With a note on the README page stating that you can uncomment what you need ( or pass extra args to the Slakbuild ) That way we don't change the philosophy of compiling only what is needed . Best regards, Nico On 10/09/2016 09:53 PM, Adis Nezirovic wrote: > Hey Nico, > > Actually, we try to keep it simple by not building it all, usually an > extension gets enabled if someone complains, so I guess it's time to > expand the list (if nobody objects). > > Best regards, > Adis > > On Sun, Oct 9, 2016 at 4:51 PM, Nico wrote: >> Hi Adis, >> >> >> Jumpin` on the thread. >> >> Is there any reason to avoid building pgsql without all extensions (contrib >> stuff )? >> >> I needed some other extension than the default you put: >> >> # adminpack - helper extension for pgAdmin >> # pgcrypto - extension for some business applications >> # ltree, xml2 - useful extensions for developers >> # postgres_fdw - foreign-data wrapper for access to external PostgreSQL >> servers >> # file_fdw - foreign-data wrapper for access to data files on filesystem >> >> I've added hstore + citext, both where need to use NIPAP (ipam) >> >> >> Thanks >> >> Nico >> >> >> >> On 10/08/2016 05:21 AM, Adis Nezirovic wrote: >>> Hello, >>> >>> Great to hear that, I was planning to submit updated script this weekend >>> :-) >>> >>> Best regards, >>> Adis >>> _______________________________________________ >>> 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 kjhambrick at gmail.com Mon Oct 10 20:42:49 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Mon, 10 Oct 2016 15:42:49 -0500 Subject: [Slackbuilds-users] Postgresql 9.5.4 ( minor ) and Postgresql 9.6.0 ( major ) In-Reply-To: <89fbf98d-8ee4-5400-80b2-6d3e8db5f32a@lodpp.net> References: <04fa9212-7592-d31f-77c2-e929477c7f4e@lodpp.net> <89fbf98d-8ee4-5400-80b2-6d3e8db5f32a@lodpp.net> Message-ID: Adis -- I do like Nico's suggestion :) Especially with the additional info in the README. I always write a local do-package.SlackBuild script wrapper when I enable one-or-more optional features. This would be right in line with my old habits. Thanks again. All of you SBo maintainers are much appreciated ! -- kjh On Mon, Oct 10, 2016 at 1:40 PM, Nico wrote: > Adis, > > > Thanks for the feedback, that makes sense, light is right :) > > > Maybe another solution could be to add all the extension in the > slackbuild, but comment them. > > With a note on the README page stating that you can uncomment what you > need ( or pass extra args to the Slakbuild ) > > That way we don't change the philosophy of compiling only what is needed . > > > Best regards, > > Nico > > > > On 10/09/2016 09:53 PM, Adis Nezirovic wrote: > >> Hey Nico, >> >> Actually, we try to keep it simple by not building it all, usually an >> extension gets enabled if someone complains, so I guess it's time to >> expand the list (if nobody objects). >> >> Best regards, >> Adis >> >> On Sun, Oct 9, 2016 at 4:51 PM, Nico wrote: >> >>> Hi Adis, >>> >>> >>> Jumpin` on the thread. >>> >>> Is there any reason to avoid building pgsql without all extensions >>> (contrib >>> stuff )? >>> >>> I needed some other extension than the default you put: >>> >>> # adminpack - helper extension for pgAdmin >>> # pgcrypto - extension for some business applications >>> # ltree, xml2 - useful extensions for developers >>> # postgres_fdw - foreign-data wrapper for access to external PostgreSQL >>> servers >>> # file_fdw - foreign-data wrapper for access to data files on filesystem >>> >>> I've added hstore + citext, both where need to use NIPAP (ipam) >>> >>> >>> Thanks >>> >>> Nico >>> >>> >>> >>> On 10/08/2016 05:21 AM, Adis Nezirovic wrote: >>> >>>> Hello, >>>> >>>> Great to hear that, I was planning to submit updated script this weekend >>>> :-) >>>> >>>> Best regards, >>>> Adis >>>> _______________________________________________ >>>> 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/ >> >> > _______________________________________________ > 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 slack at lodpp.net Tue Oct 11 06:23:57 2016 From: slack at lodpp.net (Nico) Date: Tue, 11 Oct 2016 08:23:57 +0200 Subject: [Slackbuilds-users] Postgresql 9.5.4 ( minor ) and Postgresql 9.6.0 ( major ) In-Reply-To: References: <04fa9212-7592-d31f-77c2-e929477c7f4e@lodpp.net> <89fbf98d-8ee4-5400-80b2-6d3e8db5f32a@lodpp.net> Message-ID: <7cba085e-a74b-de37-a70d-b53daa7e0ea6@lodpp.net> Adis, Konrad, Just looked at the README.SBo and actually, there is the note about extension: [...] This script builds postgresql with some useful extension modules from the contrib directory, see PG_EXTENSIONS in SlackBuild file. To build PostgreSQL with all extensions, use the following command: # PG_EXTENSIONS=ALL ./postgresql.SlackBuild Please note that in order to actually use extension, you must execute 'CREATE EXTENSION [ IF NOT EXISTS ] extension_name' for each extension. [...] So my pbm was just that I didn't RTFM :( Either choice is fine to install ALL or adding them in the Slackbuild, but I guess that it should be in the README, as it's the first thing people see from the slackbuild.org site Regards, Nico On 10/10/2016 10:42 PM, Konrad J Hambrick wrote: > Adis -- > > I do like Nico's suggestion :) > > Especially with the additional info in the README. > > I always write a local do-package.SlackBuild script wrapper when I > enable one-or-more optional features. > > This would be right in line with my old habits. > > Thanks again. > > All of you SBo maintainers are much appreciated ! > > -- kjh > > On Mon, Oct 10, 2016 at 1:40 PM, Nico > wrote: > > Adis, > > > Thanks for the feedback, that makes sense, light is right :) > > > Maybe another solution could be to add all the extension in the > slackbuild, but comment them. > > With a note on the README page stating that you can uncomment what > you need ( or pass extra args to the Slakbuild ) > > That way we don't change the philosophy of compiling only what is > needed . > > > Best regards, > > Nico > > > > On 10/09/2016 09:53 PM, Adis Nezirovic wrote: > > Hey Nico, > > Actually, we try to keep it simple by not building it all, > usually an > extension gets enabled if someone complains, so I guess it's > time to > expand the list (if nobody objects). > > Best regards, > Adis > > On Sun, Oct 9, 2016 at 4:51 PM, Nico > wrote: > > Hi Adis, > > > Jumpin` on the thread. > > Is there any reason to avoid building pgsql without all > extensions (contrib > stuff )? > > I needed some other extension than the default you put: > > # adminpack - helper extension for pgAdmin > # pgcrypto - extension for some business applications > # ltree, xml2 - useful extensions for developers > # postgres_fdw - foreign-data wrapper for access to > external PostgreSQL > servers > # file_fdw - foreign-data wrapper for access to data files > on filesystem > > I've added hstore + citext, both where need to use NIPAP > (ipam) > > > Thanks > > Nico > > > > On 10/08/2016 05:21 AM, Adis Nezirovic wrote: > > Hello, > > Great to hear that, I was planning to submit updated > script this weekend > :-) > > Best regards, > Adis > _______________________________________________ > 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/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbernts at broadpark.no Tue Oct 11 13:47:14 2016 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 11 Oct 2016 15:47:14 +0200 Subject: [Slackbuilds-users] sbbdep Message-ID: <20161011134714.GA2243@jostein> The sbbdep slackbuild gets an download error for bbuseruploads.s3.amazonaws.com Jostein From matteo.bernardini at gmail.com Tue Oct 11 13:55:21 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 11 Oct 2016 15:55:21 +0200 Subject: [Slackbuilds-users] sbbdep In-Reply-To: <20161011134714.GA2243@jostein> References: <20161011134714.GA2243@jostein> Message-ID: 2016-10-11 15:47 GMT+02:00 Jostein Berntsen : > > The sbbdep slackbuild gets an download error for > bbuseruploads.s3.amazonaws.com Hi Jostein, it seems to work fine here... $ wget https://bitbucket.org/a4z/sbbdep/downloads/sbbdep-0.2.6.tar.gz --2016-10-11 15:54:46-- https://bitbucket.org/a4z/sbbdep/downloads/sbbdep-0.2.6.tar.gz Resolving bitbucket.org (bitbucket.org)... 2401:1d80:1010::151, 104.192.143.1, 104.192.143.3, ... Connecting to bitbucket.org (bitbucket.org)|2401:1d80:1010::151|:443... connected. HTTP request sent, awaiting response... 302 FOUND Location: https://bbuseruploads.s3.amazonaws.com/c538bd46-caf1-429a-a9c1-7f511874725c/downloads/716bfb69-2ea7-417d-ba9d-f47083f20234/sbbdep-0.2.6.tar.gz?Signature=ghS1PV9zTi%2BgTQfTblOvmmBmNek%3D&Expires=1476195209&AWSAccessKeyId=AKIAIVFPT2YJYYZY3H4A&versionId=egoF6Z9Q8mNsqd3ULdfx4P22TBAUBZQ7&response-content-disposition=attachment%3B%20filename%3D%22sbbdep-0.2.6.tar.gz%22 [following] --2016-10-11 15:54:47-- https://bbuseruploads.s3.amazonaws.com/c538bd46-caf1-429a-a9c1-7f511874725c/downloads/716bfb69-2ea7-417d-ba9d-f47083f20234/sbbdep-0.2.6.tar.gz?Signature=ghS1PV9zTi%2BgTQfTblOvmmBmNek%3D&Expires=1476195209&AWSAccessKeyId=AKIAIVFPT2YJYYZY3H4A&versionId=egoF6Z9Q8mNsqd3ULdfx4P22TBAUBZQ7&response-content-disposition=attachment%3B%20filename%3D%22sbbdep-0.2.6.tar.gz%22 Resolving bbuseruploads.s3.amazonaws.com (bbuseruploads.s3.amazonaws.com)... 52.216.225.80 Connecting to bbuseruploads.s3.amazonaws.com (bbuseruploads.s3.amazonaws.com)|52.216.225.80|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 2059560 (2,0M) [application/x-tar] Saving to: ?sbbdep-0.2.6.tar.gz? sbbdep-0.2.6.tar.gz 100%[=======================================================================================================>] 1,96M 481KB/s in 4,4s 2016-10-11 15:54:52 (453 KB/s) - ?sbbdep-0.2.6.tar.gz? saved [2059560/2059560] From jbernts at broadpark.no Tue Oct 11 14:12:19 2016 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 11 Oct 2016 16:12:19 +0200 Subject: [Slackbuilds-users] sbbdep In-Reply-To: References: <20161011134714.GA2243@jostein> Message-ID: <20161011141219.GB2243@jostein> On 11.10.16,15:55, Matteo Bernardini wrote: >2016-10-11 15:47 GMT+02:00 Jostein Berntsen : >> >> The sbbdep slackbuild gets an download error for >> bbuseruploads.s3.amazonaws.com > >Hi Jostein, > >it seems to work fine here... > >$ wget https://bitbucket.org/a4z/sbbdep/downloads/sbbdep-0.2.6.tar.gz >--2016-10-11 15:54:46-- This seems to have been a hiccup. It works fine now. Thanks. Jostein From lists at osh.id.au Tue Oct 11 15:06:19 2016 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 12 Oct 2016 01:06:19 +1000 Subject: [Slackbuilds-users] Is chromium updated? Message-ID: I notice that chromium in the SBo repo is currently at version 48.0.2564.97. I'm not very up to date with chromium development, but that version number seems like it could be so out of date that it's a security risk. If that's the case, maybe it would be better to just drop it from SBo? If there's someone actually keeping an eye on it and all is well then I guess this can be ignored :) Btw, the entry also strangely has the tags "arcade,shooter,space,bsu,chromium B.S.U." which are obviously not for the chromium browser. -- Dave From 1.41421 at gmail.com Tue Oct 11 15:08:03 2016 From: 1.41421 at gmail.com (JCA) Date: Tue, 11 Oct 2016 09:08:03 -0600 Subject: [Slackbuilds-users] Is chromium updated? In-Reply-To: References: Message-ID: Slackbuild always seems to lag way behind the latest when it comes to Chromium. AlienBob always has up-to-date builds. On Tue, Oct 11, 2016 at 9:06 AM, David O'Shaughnessy wrote: > I notice that chromium in the SBo repo is currently at version > 48.0.2564.97. I'm not very up to date with chromium development, but > that version number seems like it could be so out of date that it's a > security risk. If that's the case, maybe it would be better to just drop > it from SBo? If there's someone actually keeping an eye on it and all is > well then I guess this can be ignored :) > > Btw, the entry also strangely has the tags > "arcade,shooter,space,bsu,chromium B.S.U." which are obviously not for > the chromium browser. > > -- > Dave > _______________________________________________ > 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 ryan.q at linux.com Wed Oct 12 13:23:34 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 12 Oct 2016 06:23:34 -0700 Subject: [Slackbuilds-users] Nodejs bump to v6 Message-ID: Hello friends! Nodejs v6 is going to reach long term support status on October 18. I?d like to switch over our nodejs package on SBo, but wanted to make sure no one is relying on the older v4. It also seems that Atom v1.11.x is going to require the newer npm from nodejs v6 anyway, so this is an opportune time to switch. Thoughts? Objections? ? -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Wed Oct 12 13:31:05 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 12 Oct 2016 15:31:05 +0200 Subject: [Slackbuilds-users] Nodejs bump to v6 In-Reply-To: References: Message-ID: 2016-10-12 15:23 GMT+02:00 Ryan P.C. McQuen : > Hello friends! > > Nodejs v6 is going to reach long term support status on October 18. I?d like > to switch over our nodejs package on SBo, but wanted to make sure no one is > relying on the older v4. It also seems that Atom v1.11.x is going to require > the newer npm from nodejs v6 anyway, so this is an opportune time to switch. > > Thoughts? Objections? > > > > -- > -Ryan > [ryanpcmcquen.org] > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From matteo.bernardini at gmail.com Wed Oct 12 13:35:28 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 12 Oct 2016 15:35:28 +0200 Subject: [Slackbuilds-users] Nodejs bump to v6 In-Reply-To: References: Message-ID: 2016-10-12 15:23 GMT+02:00 Ryan P.C. McQuen : > Hello friends! > > Nodejs v6 is going to reach long term support status on October 18. I?d like > to switch over our nodejs package on SBo, but wanted to make sure no one is > relying on the older v4. It also seems that Atom v1.11.x is going to require > the newer npm from nodejs v6 anyway, so this is an opportune time to switch. > > Thoughts? Objections? (sorry for the previous empty reply) I'll put in cc the people maintaining packages depending on nodejs, so they can reply even if they don't follow the mailing list Matteo From matteo.bernardini at gmail.com Wed Oct 12 13:41:09 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 12 Oct 2016 15:41:09 +0200 Subject: [Slackbuilds-users] Fwd: Nodejs bump to v6 In-Reply-To: References: Message-ID: from sending this mail it seems that Luke Williams (xocel at iquidus.org) it's MIA... ---------- Forwarded message ---------- From: Matteo Bernardini Date: 2016-10-12 15:35 GMT+02:00 Subject: Re: [Slackbuilds-users] Nodejs bump to v6 To: "SlackBuilds.org Users List" Cc: slack.dhabyx at gmail.com, gwenhael.le.moine at gmail.com, xocel at iquidus.org, beni.nospam at sdf.org 2016-10-12 15:23 GMT+02:00 Ryan P.C. McQuen : > Hello friends! > > Nodejs v6 is going to reach long term support status on October 18. I?d like > to switch over our nodejs package on SBo, but wanted to make sure no one is > relying on the older v4. It also seems that Atom v1.11.x is going to require > the newer npm from nodejs v6 anyway, so this is an opportune time to switch. > > Thoughts? Objections? (sorry for the previous empty reply) I'll put in cc the people maintaining packages depending on nodejs, so they can reply even if they don't follow the mailing list Matteo From ryan.q at linux.com Wed Oct 12 13:53:13 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 12 Oct 2016 06:53:13 -0700 Subject: [Slackbuilds-users] Nodejs bump to v6 In-Reply-To: References: Message-ID: > > > 2016-10-12 15:23 GMT+02:00 Ryan P.C. McQuen >: > > Hello friends! > > > > Nodejs v6 is going to reach long term support status on October 18. I?d > like > > to switch over our nodejs package on SBo, but wanted to make sure no one > is > > relying on the older v4. It also seems that Atom v1.11.x is going to > require > > the newer npm from nodejs v6 anyway, so this is an opportune time to > switch. > > > > Thoughts? Objections? > > (sorry for the previous empty reply) > > I'll put in cc the people maintaining packages depending on nodejs, so > they can reply even if they don't follow the mailing list > > Thanks Matteo, I also added DhabyX. -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack.dhabyx at gmail.com Wed Oct 12 15:53:22 2016 From: slack.dhabyx at gmail.com (Dhaby Xiloj) Date: Wed, 12 Oct 2016 09:53:22 -0600 Subject: [Slackbuilds-users] Nodejs bump to v6 In-Reply-To: References: Message-ID: <5019847d-11d6-d203-3dbc-d019adca41c8@gmail.com> El 12/10/16 a las 07:23, Ryan P.C. McQuen escribi?: > > Hello friends! > > Nodejs v6 is going to reach long term support status on October 18. > I?d like to switch over our |nodejs| package on SBo, but wanted to > make sure no one is relying on the older v4. It also seems that Atom > v1.11.x is going to require the newer |npm| from nodejs v6 anyway, so > this is an opportune time to switch. > > Thoughts? Objections? > > ? > > > -- > -Ryan > [ryanpcmcquen.org ] > tps://slackbuilds.org/faq/ Hi Ryan No problem, the new slackbuild for Atom 1.11 is comming -- Dhaby Xiloj -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Wed Oct 12 18:19:43 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 12 Oct 2016 20:19:43 +0200 Subject: [Slackbuilds-users] Qt 5.6.2 Released Message-ID: Hi, FYI, Qt 5.6.2 has been released. http://blog.qt.io/blog/2016/10/12/qt-5-6-2-released/ -- Best regards, Andrzej Telszewski From arkadiusz at drabczyk.org Wed Oct 12 19:31:15 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Wed, 12 Oct 2016 21:31:15 +0200 Subject: [Slackbuilds-users] development/magit should probably be removed Message-ID: <20161012193115.GA13448@comp.a> magit is a git mode for Emacs. We have development/magit in the repo but it got last update in 2011. I contacted its maintainer and he said he doesn't maintain it any more. Providing that magit and other Emacs modes can now be installed from inside Emacs using package-install mechanism I think that development/magit should be completely removed as it doesn't make sense to maintain it any more. What do you think about it? -- Arkadiusz Drabczyk From klaatu at member.fsf.org Thu Oct 13 05:47:19 2016 From: klaatu at member.fsf.org (Klaatu) Date: Thu, 13 Oct 2016 18:47:19 +1300 Subject: [Slackbuilds-users] development/magit should probably be removed In-Reply-To: <20161012193115.GA13448@comp.a> References: <20161012193115.GA13448@comp.a> Message-ID: <8ffb6a30-7f4d-9b8a-f25b-f55f4ebbfd9c@member.fsf.org> As a user liver and breather of emacs and git, I agree. I haven't touched magit since emacs made its internal packaging system official. On 13/10/16 08:31, Arkadiusz Drabczyk wrote: > magit is a git mode for Emacs. We have development/magit in the repo > but it got last update in 2011. I contacted its maintainer and he > said he doesn't maintain it any more. Providing that magit and other > Emacs modes can now be installed from inside Emacs using > package-install mechanism I think that development/magit should be > completely removed as it doesn't make sense to maintain it any more. > What do you think about it? > From miguel at thedeanda.com Thu Oct 13 05:56:03 2016 From: miguel at thedeanda.com (Miguel De Anda) Date: Wed, 12 Oct 2016 22:56:03 -0700 Subject: [Slackbuilds-users] x2goserver issues Message-ID: has anybody tried running the x2go server lately? i've never managed to get it to work but while trying right now from client on ubuntu, and server on slackware i got stuck when trying to start the session. it appears that the ssh connection works but the scripts are having issues. after some debugging (not trivial to do so far) i discovered the following output: Connection failed. /usr/bin/x2gostartagent: line 25: /usr/lib/x2go/x2gosyslog: No such file or directory /usr/bin/x2gostartagent: line 82: /usr/lib/x2go/x2gosyslog: No such file or directory /usr/bin/x2gostartagent: line 188: /usr/lib/x2go/x2gogetdisplays: No such file or directory /usr/bin/x2gostartagent: line 196: /usr/lib/x2go/x2gogetports: No such file or directory /usr/bin/x2gostartagent: line 214: /usr/lib/x2go/x2goinsertsession: No such file or directory /usr/bin/x2gostartagent: line 188: /usr/lib/x2go/x2gogetdisplays: No such file or directory /usr/bin/x2gostartagent: line 196: /usr/lib/x2go/................. that appears to be the output of the remote script running from x2gostartagent. while looking for /usr/lib/x2go i discovered its not really there and that the script in /usr/bin/x2gopath has incorrect values for libexec (but maybe more). it seems that most files are in /usr/lib64/x2go/* but there is 1 in /var/lib/x2go (x2go_sessions) i'm guessing that the slackbuild script has issues but since i've never used x2go before, i can't say for sure. i didn't want to post on linuxpackages (yet) since this seems to be a slackbuild issue. thanks, miguel From willysr at slackbuilds.org Thu Oct 13 06:23:37 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 13 Oct 2016 13:23:37 +0700 Subject: [Slackbuilds-users] monkey-studio In-Reply-To: References: Message-ID: > The source for monkey-studio is dead... > > New source: > > http://slackware.uk/sbosrcarch/by-md5/1/b/1b76fdaf9293ab160ca90ff919440598/mks_1.9.0.4-src.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 khronosschoty at utmail.net Thu Oct 13 23:08:57 2016 From: khronosschoty at utmail.net (Vasily Sora) Date: Thu, 13 Oct 2016 16:08:57 -0700 Subject: [Slackbuilds-users] znc at SlackBuilds.org Message-ID: <829df70d-42c0-134a-cd0e-926c7cd281a8@utmail.net> Hi, I just noticed that the info file for znc is out of date. The download link http://znc.in/releases/znc-1.6.1.tar.gz is invalid. From willysr at slackbuilds.org Thu Oct 13 23:55:26 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Oct 2016 06:55:26 +0700 Subject: [Slackbuilds-users] znc at SlackBuilds.org In-Reply-To: <829df70d-42c0-134a-cd0e-926c7cd281a8@utmail.net> References: <829df70d-42c0-134a-cd0e-926c7cd281a8@utmail.net> Message-ID: > I just noticed that the info file for znc is out of date. The download > link http://znc.in/releases/znc-1.6.1.tar.gz is invalid. 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 willysr at slackbuilds.org Thu Oct 13 23:58:17 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Oct 2016 06:58:17 +0700 Subject: [Slackbuilds-users] development/magit should probably be removed In-Reply-To: <20161012193115.GA13448@comp.a> References: <20161012193115.GA13448@comp.a> Message-ID: <935e63d5-5c83-a6e6-7d61-3c6d447fd3ef@slackbuilds.org> > magit is a git mode for Emacs. We have development/magit in the repo > but it got last update in 2011. I contacted its maintainer and he > said he doesn't maintain it any more. Providing that magit and other > Emacs modes can now be installed from inside Emacs using > package-install mechanism I think that development/magit should be > completely removed as it doesn't make sense to maintain it any more. > What do you think about it? it's removed on my branch if someone wanted to take over maintenance, please let us know before next public update -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kjhambrick at gmail.com Fri Oct 14 02:26:50 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Thu, 13 Oct 2016 21:26:50 -0500 Subject: [Slackbuilds-users] x2goserver issues In-Reply-To: References: Message-ID: Miguel -- I tried several months ago but never got it to work on Slackware64-14.2 + Multilib Gave up without much debugging. There several threads on LQ about it. The x2goserver seems to not like Slackware ... -- kjh On Thu, Oct 13, 2016 at 12:56 AM, Miguel De Anda wrote: > has anybody tried running the x2go server lately? i've never managed > to get it to work but while trying right now from client on ubuntu, > and server on slackware i got stuck when trying to start the session. > it appears that the ssh connection works but the scripts are having > issues. > > after some debugging (not trivial to do so far) i discovered the > following output: > > Connection failed. /usr/bin/x2gostartagent: line 25: > /usr/lib/x2go/x2gosyslog: No such file or directory > /usr/bin/x2gostartagent: line 82: /usr/lib/x2go/x2gosyslog: No such > file or directory /usr/bin/x2gostartagent: line 188: > /usr/lib/x2go/x2gogetdisplays: No such file or directory > /usr/bin/x2gostartagent: line 196: /usr/lib/x2go/x2gogetports: No such > file or directory /usr/bin/x2gostartagent: line 214: > /usr/lib/x2go/x2goinsertsession: No such file or directory > /usr/bin/x2gostartagent: line 188: /usr/lib/x2go/x2gogetdisplays: No > such file or directory /usr/bin/x2gostartagent: line 196: > /usr/lib/x2go/................. > > that appears to be the output of the remote script running from > x2gostartagent. while looking for /usr/lib/x2go i discovered its not > really there and that the script in /usr/bin/x2gopath has incorrect > values for libexec (but maybe more). > > it seems that most files are in /usr/lib64/x2go/* but there is 1 in > /var/lib/x2go (x2go_sessions) > > i'm guessing that the slackbuild script has issues but since i've > never used x2go before, i can't say for sure. > > i didn't want to post on linuxpackages (yet) since this seems to be a > slackbuild issue. > > thanks, > miguel > _______________________________________________ > 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 Sat Oct 15 00:22:39 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Oct 2016 07:22:39 +0700 Subject: [Slackbuilds-users] Updates - 20161015.1 Message-ID: Sat Oct 15 00:10:43 UTC 2016 academic/fet: Updated for version 5.30.4. academic/gwyddion: Updated for version 2.46. academic/lapacke: Added (C interface to LAPACK). academic/wmcalc: Updated for version 0.6. accessibility/svkbd: Fix HOMEPAGE, add missing man page src. accessibility/unclutter-xfixes: Added (X11 tool). accessibility/xdotool: Updated for version 3.20160805.1. audio/sayonara-player: Updated for version 0.9.2-git6-20161010. desktop/xed: Added (small and lightweight text editor). desktop/xkblayout-state: Added (get/set the keyboard layout). development/SQLAlchemy: Updated for version 1.1.1. development/bpython: Updated for version 0.16. development/cppcheck: Updated for version 1.76. development/flow: Updated for version 0.33.0. development/fsharp: Updated for version 4.0.1.13. development/komodo-edit: Updated for version 10.1.1. development/komodo-ide: Updated for version 10.1.1. development/magit: Removed (No longer maintained). development/monkey-studio: Fix DOWNLOAD url. development/p4: Updated for version 2016.1.1443785. development/p4d: Added (Perforce Helix VCS server). development/sbcl: Updated for version 1.3.10. development/sqlitebrowser: Updated for version 3.9.1. games/GLupeN64: Updated for version 2016.10.12_4378f48. games/connectagram: Updated for version 1.2.3. games/cutemaze: Updated for version 1.1.1. games/doomretro: Fixed README and icon installation. games/etlegacy: Updated for version 2.75. games/hexalate: Updated for version 1.1.0. games/peg-e: Updated for version 1.2.2 games/tanglet: Updated for version 1.4.0. gis/basemap: Switch to i586. graphics/PyMOL: Updated for version 1.8.4.0. graphics/openimageio: Updated for version 1.7.7 libraries/GeoIP-Python: updated for version 1.3.2. libraries/Ipopt: Added (Interior Point OPTimizer). libraries/SDL2_image: Fix JPEG support. libraries/botocore: Updated for version 1.4.60. libraries/fifechan: Switch to i586. libraries/jsoncpp: Updated for version 1.7.7 libraries/libmseed: Updated for version 2.18. libraries/libuchardet: Updated for version 0.0.6. libraries/pyechonest: Switch to i586. libraries/pyftpdlib: Switch to i586. libraries/uptime: Switch to i586. libraries/webkit2gtk: Updated for version 2.14.1. multimedia/flashplayer-plugin: Updated for version 11.2.202.637. multimedia/opera-developer-ffmpeg-codecs: Added (Extra codec). network/EarthReader-Web: Switch to i586. network/Electrum: Updated for version 2.7.8. network/awscli: Updated for version 1.11.2. network/cacti-spine: Updated for version 0.8.8h. network/cacti: Updated for version 0.8.8h. network/chromium: Updated for version 53.0.2785.143. network/cowpatty: Switch to i586. network/deis: Switch to i586. network/flexget: Updated for version 2.3.43. network/opensmtpd: Updated for version 6.0.2p1. network/opera-developer: Updated for version 42.0.2372.0. network/pidgin-extprefs: Switch to i586. network/privoxy: Updated for version 3.0.26. network/tixati: Updated for version 2.47_1. network/youtube-dl: Updated for version 2016.10.07. network/znc: Update DOWNLOAD url. office/texstudio: Updated for version 2.11.2 perl/libpurple-kwallet-plugin: Fix DOWNLOAD url. perl/perl-DateTime-Format-Strptime: Update DOWNLOAD url. perl/perl-DateTime-Locale: Fix DOWNLOAD url. perl/perl-IO-Socket-INET6: Update DOWNLOAD url. perl/perl-Log-Dispatch: Update DOWNLOAD url. perl/perl-Sidef: Updated for version 2.32. perl/perl-Text-Iconv: Switch to i586. perl/perl-WWW-Curl: Fix Build. python/argcomplete: Updated for version 1.5.1. python/curtsies: Updated for version 0.2.10. python/ipaddr-py: Update DOWNLOAD url. python/piprot: Updated for version 0.9.7. python/s3transfer: Updated for version 0.1.7. python/tox: Updated for version 2.4.0. python/wcwidth: Switch to i586. ruby/ncurses-ruby: Update MD5SUM. ruby/ruby-gist: Added (A single function that uploads a gist). ruby/rubygem-bundler: Updated for version 1.13.3. system/PySixel: Switch to i586. system/letsencrypt: Updated for version 0.9.3. system/logkeys: Switch to i586. system/lsyncd: Updated for version 2.1.6. system/openmpi: Updated for version 1.10.4. system/ossec-agent: Added (Open Source Host-based IDS). system/ossec-local: Added (Open Source Host-based IDS). system/ossec-server: Added (Open Source Host-based IDS). system/postgresql: Updated for version 9.6.0. system/slpkg: Updated for version 3.1.8. system/watch-fs: Switch to i586. system/xen: Added XSA-190 security advisory patch. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lists at osh.id.au Sat Oct 15 19:36:01 2016 From: lists at osh.id.au (David O'Shaughnessy) Date: Sun, 16 Oct 2016 05:36:01 +1000 Subject: [Slackbuilds-users] development/magit should probably be removed In-Reply-To: <935e63d5-5c83-a6e6-7d61-3c6d447fd3ef@slackbuilds.org> References: <20161012193115.GA13448@comp.a> <935e63d5-5c83-a6e6-7d61-3c6d447fd3ef@slackbuilds.org> Message-ID: <271a876d-915a-8736-a5bc-3700916b001d@osh.id.au> On 10/14/2016 09:58 AM, Willy Sudiarto Raharjo wrote: >> magit is a git mode for Emacs. We have development/magit in the repo >> but it got last update in 2011. I contacted its maintainer and he >> said he doesn't maintain it any more. Providing that magit and other >> Emacs modes can now be installed from inside Emacs using >> package-install mechanism I think that development/magit should be >> completely removed as it doesn't make sense to maintain it any more. >> What do you think about it? > > > it's removed on my branch > > if someone wanted to take over maintenance, please let us know before > next public update I think that's the way to go. The Emacs internal packaging system is very good, so there's no need to maintain it separately for SBo. -- Dave From yalhcru at gmail.com Sat Oct 15 20:42:59 2016 From: yalhcru at gmail.com (B Watson) Date: Sat, 15 Oct 2016 16:42:59 -0400 Subject: [Slackbuilds-users] active inform6 developers? Message-ID: Does anyone actually use games/inform to develop interactive fiction games? The reason I ask is, there's a newer version of inform 6 (6.33), but it's not as nicely packaged as the 6.32.1 we have on SBo (it's missing the manual, for one thing). For my own use, 6.32.1 is just fine. But, is there anyone here that's using inform and just dying to upgrade to 6.33? I don't want to force anyone to stick with an old version if they really want the new one. The build system has changed enough between 6.32.1 and 6.33 that it'll be a pain in the butt to keep the SlackBuild script compatible with both. But depending on the response I get to this message, I may end up doing that anyway. This query is specifically about the standalone inform 6. If you code in inform 7, you've already got inform 6.33, but not its documentation/manpages/etc. I'm wanting to hear from people who code in inform 6, not inform 7 (for those who don't know, it's a completely different language). From kingbeowulf at gmail.com Sun Oct 16 03:57:15 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 15 Oct 2016 20:57:15 -0700 Subject: [Slackbuilds-users] Nvidia-legacy304-driver vdpau missing video and opengl/glx as user crash Message-ID: <647264fc-525f-5ee6-8760-e430089725d9@gmail.com> willy flagged an issue on the new nvidia-304.132 drivers. I decided to build a box with an older card (GTX6800) to test on bare metal before I update (only so much one can do in qemu). After fixing a few items, I have these issues. The "root" issue nags my memory but I can't seem to recall why. Clean Slackware64-14.2 updated install, no other files. AMD Athlon X2 3200+ 1. logged in as regular user glxgears and nvidia-settings crashes: ---------------- $ glxgears X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 30 Current serial number in output stream: 31 When accessing nvidia-settings OpenGL/GLX information: $ nvidia-settings The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 584 error_code 2 request_code 154 minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ---------------- mplayer will play via -vo xv but no other driver (Big Buck Bunny 1920x1080 30fps). 2. logged in as root everything works except mplayer -vo {vdpau | xvidix}. Nvidia-settings and glxgears work as expected. So there is a vdpau issue, but nothing in logs re: user vs. root running GLX. as far as I know, 'ldd' reports ok. Any assistance appreciated. Files for testing are on http:/www.koenigcomputers.com/ (follow biblio links...) -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 Oct 16 04:14:44 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 16 Oct 2016 11:14:44 +0700 Subject: [Slackbuilds-users] Nvidia-legacy304-driver vdpau missing video and opengl/glx as user crash In-Reply-To: <647264fc-525f-5ee6-8760-e430089725d9@gmail.com> References: <647264fc-525f-5ee6-8760-e430089725d9@gmail.com> Message-ID: <1e3aa9d1-7b6e-a875-8672-7059c2ce0a21@slackbuilds.org> > willy flagged an issue on the new nvidia-304.132 drivers. I decided to > build a box with an older card (GTX6800) to test on bare metal before I > update (only so much one can do in qemu). After fixing a few items, I > have these issues. The "root" issue nags my memory but I can't seem to > recall why. > > Clean Slackware64-14.2 updated install, no other files. AMD Athlon X2 3200+ > > 1. logged in as regular user > glxgears and nvidia-settings crashes: > > ---------------- > $ glxgears > X Error of failed request: BadValue (integer parameter out of range for > operation) > Major opcode of failed request: 154 (GLX) > Minor opcode of failed request: 3 (X_GLXCreateContext) > Value in failed request: 0x0 > Serial number of failed request: 30 > Current serial number in output stream: 31 > > When accessing nvidia-settings OpenGL/GLX information: > > $ nvidia-settings > The program 'nvidia-settings' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadValue (integer parameter out of range for operation)'. > (Details: serial 584 error_code 2 request_code 154 minor_code 3) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() function.) > ---------------- > > mplayer will play via -vo xv but no other driver (Big Buck Bunny > 1920x1080 30fps). > > 2. logged in as root > everything works except mplayer -vo {vdpau | xvidix}. Nvidia-settings > and glxgears work as expected. > > So there is a vdpau issue, but nothing in logs re: user vs. root running > GLX. as far as I know, 'ldd' reports ok. > > Any assistance appreciated. Files for testing are on > http:/www.koenigcomputers.com/ (follow biblio links...) > -Ed Hi Ed, thanks for the confirmation of the bug in 304.132 driver it seems that other users in other distribution are also having this problem https://devtalk.nvidia.com/default/topic/968892/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/ https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=nvidia-legacy-304xx-driver;dist=unstable however one person posted an image about a working 304.142 in Fedora 24 with Linux Kernel 4.7 http://media.if-not-true-then-false.com/2015/08/nvidia-304.132-on-fedora-24-lxde.png here's what listed as the release highlight of 304.132 Added /var/log/dmesg to the list of paths which are searched by nvidia-bug-report.sh for kernel messages. Fixed a bug that caused kernel panics when using the NVIDIA driver on v4.5 and newer Linux kernels built with CONFIG_DEBUG_VM_PGFLAGS. Updated nvidia-installer to support ncurses version 6.x. I'm suspecting that it *might* require newer kernel so for now, i will stick to the 304.131 which still works fine as it is. 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 dnied at tiscali.it Sun Oct 16 10:47:12 2016 From: dnied at tiscali.it (Dario Niedermann) Date: Sun, 16 Oct 2016 12:47:12 +0200 Subject: [Slackbuilds-users] Nvi unstable with --enable-threads Message-ID: <58035ab0.xYWC8nSKupuTTYT4%dnied@tiscali.it> Nvi-1.81.6 is giving error messages when quitting an unmodified file: "DB_THREAD mandates memory allocation flag on key DBT", and one other message about not being able to append to line 0. Something is clearly wrong... Both messages went away when I removed the '--enable-threads' option from the SlackBuild's configure step. Unless that option is important for some reason, I'd recommend removing it altogether: using nvi built without threads, I haven't found any downsides yet. Best regards, DN From sbolokanov at abv.bg Sun Oct 16 10:54:30 2016 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGKINCR0L7Qu9C+0LrQsNC90L7QstGK?=) Date: Sun, 16 Oct 2016 13:54:30 +0300 (EEST) Subject: [Slackbuilds-users] version bumps for cdemu-client and deps Message-ID: <2132355031.1444090.1476615270215.JavaMail.apache@nm52.abv.bg> Hello, versions of vhba-module, libmirage, cdemu-daemon and cdemu-client are quite old. Here are version bumps, if it is okay. https://github.com/sbolokanov/sbo-push/commits/master Regards, -- ?????? ?????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Oct 16 12:14:43 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 16 Oct 2016 19:14:43 +0700 Subject: [Slackbuilds-users] version bumps for cdemu-client and deps In-Reply-To: <2132355031.1444090.1476615270215.JavaMail.apache@nm52.abv.bg> References: <2132355031.1444090.1476615270215.JavaMail.apache@nm52.abv.bg> Message-ID: <3da50985-e256-7364-e1ac-f3d49dbd9442@slackbuilds.org> > versions of vhba-module, libmirage, cdemu-daemon and cdemu-client are quite old. > Here are version bumps, if it is okay. > > https://github.com/sbolokanov/sbo-push/commits/master Hi It would be better if the commit message use this format: "/: Updated for version ." i can merge those changes after all the commit messages are 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 willysr at slackbuilds.org Sun Oct 16 15:08:55 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 16 Oct 2016 22:08:55 +0700 Subject: [Slackbuilds-users] Nvi unstable with --enable-threads In-Reply-To: <58035ab0.xYWC8nSKupuTTYT4%dnied@tiscali.it> References: <58035ab0.xYWC8nSKupuTTYT4%dnied@tiscali.it> Message-ID: <416a03a2-dd6a-79bc-632e-05fbd5ff9df6@slackbuilds.org> > Nvi-1.81.6 is giving error messages when quitting an unmodified file: > "DB_THREAD mandates memory allocation flag on key DBT", and one > other message about not being able to append to line 0. > > Something is clearly wrong... > > Both messages went away when I removed the '--enable-threads' option > from the SlackBuild's configure step. Unless that option is important > for some reason, I'd recommend removing it altogether: using nvi built > without threads, I haven't found any downsides yet. Thanks it has been pushed 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 ryan.q at linux.com Sun Oct 16 16:38:27 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 16 Oct 2016 09:38:27 -0700 Subject: [Slackbuilds-users] Nodejs bump to v6 In-Reply-To: <5019847d-11d6-d203-3dbc-d019adca41c8@gmail.com> References: <5019847d-11d6-d203-3dbc-d019adca41c8@gmail.com> Message-ID: No problem, the new slackbuild for Atom 1.11 is comming > Since there?s been no objection, I?ve pushed nodejs 6.8.1 to my branch, should go out in the next public update. This will make updating atom to 1.11.x really easy. Konpai! ? -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Sun Oct 16 18:54:41 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 16 Oct 2016 11:54:41 -0700 Subject: [Slackbuilds-users] Nvidia-legacy304-driver vdpau missing video and opengl/glx as user crash In-Reply-To: <1e3aa9d1-7b6e-a875-8672-7059c2ce0a21@slackbuilds.org> References: <647264fc-525f-5ee6-8760-e430089725d9@gmail.com> <1e3aa9d1-7b6e-a875-8672-7059c2ce0a21@slackbuilds.org> Message-ID: <66e6ef98-06b9-ee27-78c8-3c96d21ef2cb@gmail.com> On 10/15/2016 09:14 PM, Willy Sudiarto Raharjo wrote: >> willy flagged an issue on the new nvidia-304.132 drivers. I decided to >> build a box with an older card (GTX6800) to test on bare metal before I >> update (only so much one can do in qemu). After fixing a few items, I >> have these issues. The "root" issue nags my memory but I can't seem to >> recall why. >> >> Clean Slackware64-14.2 updated install, no other files. AMD Athlon X2 3200+ >> >> 1. logged in as regular user >> glxgears and nvidia-settings crashes: >> --snip-- > > Hi Ed, > > thanks for the confirmation of the bug in 304.132 driver > it seems that other users in other distribution are also having this problem > > https://devtalk.nvidia.com/default/topic/968892/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/ > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=nvidia-legacy-304xx-driver;dist=unstable > > however one person posted an image about a working 304.142 in Fedora 24 > with Linux Kernel 4.7 > http://media.if-not-true-then-false.com/2015/08/nvidia-304.132-on-fedora-24-lxde.png > > here's what listed as the release highlight of 304.132 > > Added /var/log/dmesg to the list of paths which are searched by > nvidia-bug-report.sh for kernel messages. > Fixed a bug that caused kernel panics when using the NVIDIA driver on > v4.5 and newer Linux kernels built with CONFIG_DEBUG_VM_PGFLAGS. > Updated nvidia-installer to support ncurses version 6.x. > > I'm suspecting that it *might* require newer kernel so for now, i will > stick to the 304.131 which still works fine as it is. > > Thanks > > Thanks for the links. I overlooked the Nvidia devtalk for some reason. Looks like SBo will have to stick with 304.131 for now. The are 2 minor bugs in the slackbuild and nvdia-switch that I will correct an post today. As for the image of 304.132 on Fedora: Bah. I was able to get that far. The desktop runs fine (2D), but try any 3D opengl/glx function, or even just clicking on OpenGL/GLX Information, and the bug occurs. -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 arnaud.garcia-fernandez at laposte.net Mon Oct 17 09:28:14 2016 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Mon, 17 Oct 2016 11:28:14 +0200 Subject: [Slackbuilds-users] findpkg version mismatch in .info Message-ID: <20161017112814.da79974142e7b0be6af5ed17@laposte.net> Hi everybody ! findpkg is on version 20160817 both on the file to download in findpkg.info and on the SlackBuild script, but the VERSION in the findpkg.info file is still 20160710. It could confuse some auto-build scripts... Best regards, Arnaud. From info at microlinux.fr Mon Oct 17 11:13:40 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Mon, 17 Oct 2016 13:13:40 +0200 Subject: [Slackbuilds-users] Recoll dependencies Message-ID: <646f64b8-ea3f-6f25-b1b9-d36136707118@microlinux.fr> Hi, The Recoll application currently lists three optional dependencies: * antiword * unrtf * exiftool I would suggest to mark these as requirements, since the application keeps nagging the user if the tools are not installed on the system. This nagging can not be turned off in the preferences. Furthermore, there's a fourth dependency that's been introduced recently: untex. I just submitted a SlackBuild for untex on SBo. I would suggest to also add it as a requirement. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From fellype at gmail.com Mon Oct 17 14:06:10 2016 From: fellype at gmail.com (Fellype do Nascimento) Date: Mon, 17 Oct 2016 12:06:10 -0200 Subject: [Slackbuilds-users] gwyddion 2.46 requires libminizip Message-ID: Hi all, libminizip is currently assigned as an optional dependence of gwyddion. But when upgrading gwyddion 2.45 -> 2.46 I got the following error(s): **** jpkscan.c: In function 'match_segment_filename': jpkscan.c:804:11: error: implicit declaration of function 'atoi' [-Werror=implicit-function-declaration] *id = atoi(s); ^ cc1: some warnings being treated as errors make[3]: *** [jpkscan_la-jpkscan.lo] Error 1 Makefile:1972: recipe for target 'jpkscan_la-jpkscan.lo' failed make[3]: Leaving directory '/tmp/SBo/gwyddion-2.46/modules/file' make[2]: *** [all-recursive] Error 1 Makefile:642: recipe for target 'all-recursive' failed make[2]: Leaving directory '/tmp/SBo/gwyddion-2.46/modules' make[1]: *** [all-recursive] Error 1 Makefile:612: recipe for target 'all-recursive' failed make[1]: Leaving directory '/tmp/SBo/gwyddion-2.46' make: *** [all] Error 2 Makefile:521: recipe for target 'all' failed Failures: gwyddion: gwyddion.SlackBuild return non-zero **** gwyddion 2.46 compiled fine after installing libminizip. Regards, -- Dr. Fellype do Nascimento - fellype (at) gmail.com Center for Semiconductor Components and Nanotechnologies / Laborat?rio de Plasmas State University of Campinas, C.P. 6101, Rua Jo?o Pandia Calogeras, No.90, Cidade Universit?ria Zeferino Vaz, Campinas, SP, 13083-870, Brazil Fone/Phone: +55 19 35217321 From dn2010 at gmail.com Mon Oct 17 14:12:36 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Mon, 17 Oct 2016 17:12:36 +0300 Subject: [Slackbuilds-users] gwyddion 2.46 requires libminizip In-Reply-To: References: Message-ID: It should fall back to libzip if libminizip is not installed, however I've not tried it without libminizip recently. WBR, Daniil Bratashov. On Mon, Oct 17, 2016 at 5:06 PM, Fellype do Nascimento wrote: > Hi all, > > libminizip is currently assigned as an optional dependence of gwyddion. But > when upgrading gwyddion 2.45 -> 2.46 I got the following error(s): > > **** > jpkscan.c: In function 'match_segment_filename': > jpkscan.c:804:11: error: implicit declaration of function 'atoi' > [-Werror=implicit-function-declaration] > *id = atoi(s); > ^ > cc1: some warnings being treated as errors > make[3]: *** [jpkscan_la-jpkscan.lo] Error 1 > Makefile:1972: recipe for target 'jpkscan_la-jpkscan.lo' failed > make[3]: Leaving directory '/tmp/SBo/gwyddion-2.46/modules/file' > make[2]: *** [all-recursive] Error 1 > Makefile:642: recipe for target 'all-recursive' failed > make[2]: Leaving directory '/tmp/SBo/gwyddion-2.46/modules' > make[1]: *** [all-recursive] Error 1 > Makefile:612: recipe for target 'all-recursive' failed > make[1]: Leaving directory '/tmp/SBo/gwyddion-2.46' > make: *** [all] Error 2 > Makefile:521: recipe for target 'all' failed > Failures: > gwyddion: gwyddion.SlackBuild return non-zero > > **** > gwyddion 2.46 compiled fine after installing libminizip. > > Regards, > > > -- > > Dr. Fellype do Nascimento - fellype (at) gmail.com > Center for Semiconductor Components and Nanotechnologies / Laborat?rio de > Plasmas > State University of Campinas, C.P. 6101, > Rua Jo?o Pandia Calogeras, No.90, > Cidade Universit?ria Zeferino Vaz, > Campinas, SP, 13083-870, Brazil > Fone/Phone: +55 19 35217321 > > _______________________________________________ > 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 dn2010 at gmail.com Mon Oct 17 14:30:53 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Mon, 17 Oct 2016 17:30:53 +0300 Subject: [Slackbuilds-users] gwyddion 2.46 requires libminizip In-Reply-To: References: Message-ID: Yes, there is a problem with recent gwyddion builds, I'll try to fix it and upload modified slackbuild. On Mon, Oct 17, 2016 at 5:12 PM, Daniil Bratashov wrote: > It should fall back to libzip if libminizip is not installed, however > I've not tried it without libminizip recently. > > WBR, Daniil Bratashov. > > On Mon, Oct 17, 2016 at 5:06 PM, Fellype do Nascimento > wrote: >> Hi all, >> >> libminizip is currently assigned as an optional dependence of gwyddion. But >> when upgrading gwyddion 2.45 -> 2.46 I got the following error(s): >> >> **** >> jpkscan.c: In function 'match_segment_filename': >> jpkscan.c:804:11: error: implicit declaration of function 'atoi' >> [-Werror=implicit-function-declaration] >> *id = atoi(s); >> ^ >> cc1: some warnings being treated as errors >> make[3]: *** [jpkscan_la-jpkscan.lo] Error 1 >> Makefile:1972: recipe for target 'jpkscan_la-jpkscan.lo' failed >> make[3]: Leaving directory '/tmp/SBo/gwyddion-2.46/modules/file' >> make[2]: *** [all-recursive] Error 1 >> Makefile:642: recipe for target 'all-recursive' failed >> make[2]: Leaving directory '/tmp/SBo/gwyddion-2.46/modules' >> make[1]: *** [all-recursive] Error 1 >> Makefile:612: recipe for target 'all-recursive' failed >> make[1]: Leaving directory '/tmp/SBo/gwyddion-2.46' >> make: *** [all] Error 2 >> Makefile:521: recipe for target 'all' failed >> Failures: >> gwyddion: gwyddion.SlackBuild return non-zero >> >> **** >> gwyddion 2.46 compiled fine after installing libminizip. >> >> Regards, >> >> >> -- >> >> Dr. Fellype do Nascimento - fellype (at) gmail.com >> Center for Semiconductor Components and Nanotechnologies / Laborat?rio de >> Plasmas >> State University of Campinas, C.P. 6101, >> Rua Jo?o Pandia Calogeras, No.90, >> Cidade Universit?ria Zeferino Vaz, >> Campinas, SP, 13083-870, Brazil >> Fone/Phone: +55 19 35217321 >> >> _______________________________________________ >> 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 titopoquito at gmail.com Mon Oct 17 21:09:23 2016 From: titopoquito at gmail.com (Tito) Date: Mon, 17 Oct 2016 23:09:23 +0200 Subject: [Slackbuilds-users] Recoll dependencies In-Reply-To: <646f64b8-ea3f-6f25-b1b9-d36136707118@microlinux.fr> References: <646f64b8-ea3f-6f25-b1b9-d36136707118@microlinux.fr> Message-ID: Hi Niki and all, I would be fine with that. Could you please send me your submission tarball for untex, it still is in pending and so it is not accessible via git. I would like to test it before I submit a recoll upgrade. After all without these helper tools recoll is not much help anyway. Any objections to mark these runtime dependencies as "required"? Cheers, Tito > Am 17.10.2016 um 13:13 schrieb Nicolas Kovacs : > > Hi, > > The Recoll application currently lists three optional dependencies: > > * antiword > * unrtf > * exiftool > > I would suggest to mark these as requirements, since the application > keeps nagging the user if the tools are not installed on the system. > This nagging can not be turned off in the preferences. > > Furthermore, there's a fourth dependency that's been introduced > recently: untex. > > I just submitted a SlackBuild for untex on SBo. I would suggest to also > add it as a requirement. > > Cheers, > > Niki > -- > Microlinux - Solutions informatiques durables > 7, place de l'?glise - 30730 Montpezat > Web : http://www.microlinux.fr > Mail : info at microlinux.fr > T?l. : 04 66 63 10 32 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From info at microlinux.fr Mon Oct 17 21:11:46 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Mon, 17 Oct 2016 23:11:46 +0200 Subject: [Slackbuilds-users] Recoll dependencies In-Reply-To: References: <646f64b8-ea3f-6f25-b1b9-d36136707118@microlinux.fr> Message-ID: <8f8f2f5d-e52e-e6de-6469-88e1f75eaa87@microlinux.fr> Le 17/10/2016 ? 23:09, Tito a ?crit : > Hi Niki and all, > > I would be fine with that. Could you please send me your submission > tarball for untex, it still is in pending and so it is not accessible > via git. I would like to test it before I submit a recoll upgrade. > After all without these helper tools recoll is not much help anyway. > Any objections to mark these runtime dependencies as "required"? Hi Tito, Thanks for your fast response. Here's the untex.tar.gz tarball you asked for. It's the same I submitted earlier. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 -------------- next part -------------- A non-text attachment was scrubbed... Name: untex.tar.gz Type: application/x-gzip Size: 1921 bytes Desc: not available URL: From ts at websafe.pl Mon Oct 17 23:14:34 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Tue, 18 Oct 2016 01:14:34 +0200 Subject: [Slackbuilds-users] Fixed and updated KeePass Message-ID: Hello, + Upgraded to 2.34 + Fixed icons source path + Fixed installation prefix to /usr/lib/KeePass (removed version) as discussed here: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-August/016930.html + Fixed SlackBuild to match new template (586) + Fixed final location of License.txt and KeePass.chm to /usr/doc/KeePass-2.34 Details: https://github.com/websafe/slackbuilds/commits/master/KeePass -- 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 titopoquito at gmail.com Tue Oct 18 08:48:54 2016 From: titopoquito at gmail.com (titopoquito) Date: Tue, 18 Oct 2016 10:48:54 +0200 Subject: [Slackbuilds-users] Recoll dependencies In-Reply-To: <8f8f2f5d-e52e-e6de-6469-88e1f75eaa87@microlinux.fr> References: <646f64b8-ea3f-6f25-b1b9-d36136707118@microlinux.fr> <8f8f2f5d-e52e-e6de-6469-88e1f75eaa87@microlinux.fr> Message-ID: <8fcb587b-dc5a-5be7-7155-89b0484f8700@gmail.com> Am 17.10.2016 um 23:11 schrieb Nicolas Kovacs: > Hi Tito, > > Thanks for your fast response. Here's the untex.tar.gz tarball you asked > for. It's the same I submitted earlier. > > Cheers, > > Niki > Thanks Niki, I will compile it later today, test recoll indexing and submit an update. BTW there will be an unrtf upgrade, too. It's already in the pending queue. Tito From jm.inform at gesaku.es Tue Oct 18 08:51:03 2016 From: jm.inform at gesaku.es (=?UTF-8?Q?Jos=c3=a9_Manuel_Garc=c3=ada-Patos?=) Date: Tue, 18 Oct 2016 10:51:03 +0200 Subject: [Slackbuilds-users] active inform6 developers? In-Reply-To: References: Message-ID: <86049a37-88f5-0951-7d9e-f5b84294c2ad@gesaku.es> > For my own use, 6.32.1 is just fine. But, is there anyone here that's > using inform and just dying to upgrade to 6.33? I don't want to force > anyone to stick with an old version if they really want the new one. I use inform 6.33 (a beta version, actually), but I created my own SlackBuild for it. I follow its development on git, so if there's any upgrade-worthy change, I will upgrade from there. Same with the library. So, as far as I'm concerned, it's your call. But if you need help, let me know. -- Jos? Manuel Garc?a-Patos Madrid From akasoft.cmf at gmail.com Tue Oct 18 17:07:46 2016 From: akasoft.cmf at gmail.com (Andrzej Kobylski) Date: Tue, 18 Oct 2016 19:07:46 +0200 Subject: [Slackbuilds-users] A library libdvdcss-1.4.0 doesn't work with Slackware 14.2 Message-ID: Hi, Mentioned library doesn't work with Slackware 14.2. There are technical details: https://mailman.videolan.org/pipermail/libdvdcss-devel/2016-April/001641.html The last issue of libdvdcss which works correctly with Slackware 14.2 is 1.3.0. Would you like to consider a relevant correction in the SlackBuild repository? Thanks for your work Andrew Kobylski -------------- next part -------------- An HTML attachment was scrubbed... URL: From dn2010 at gmail.com Tue Oct 18 21:18:00 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Wed, 19 Oct 2016 00:18:00 +0300 Subject: [Slackbuilds-users] gwyddion 2.46 requires libminizip In-Reply-To: References: Message-ID: <20161019001800.6cca110f@darkstar.example.net> On Mon, 17 Oct 2016 12:06:10 -0200 Fellype do Nascimento wrote: > libminizip is currently assigned as an optional dependence of > gwyddion. But when upgrading gwyddion 2.45 -> 2.46 I got the > following error(s): I've uploaded new version with patch for this case. WBR, Daniil Bratashov. From s.arcus at open-t.co.uk Wed Oct 19 09:42:58 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 19 Oct 2016 10:42:58 +0100 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware Message-ID: The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of Cron used on Slackware. It uses the extra field for the username (clamav) which seems to break things on Slackware. I've just noticed this on several clamav installs which were months out of date, as the cron file never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line is needed - as it works fine for me without it. Could this be fixed please - unless I'm doing something silly and it should actually work? From slackbuilds at schoepfer.info Wed Oct 19 09:59:06 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 19 Oct 2016 11:59:06 +0200 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: References: Message-ID: <580743EA.8030201@schoepfer.info> On 19.10.2016 11:42, Sebastian Arcus wrote: > The clamav-unofficial-sigs.cron crond crontab file included with > clamav-unofficial-sigs seems to be incompatible with the version of Cron > used on Slackware. It uses the extra field for the username (clamav) > which seems to break things on Slackware. I've just noticed this on > several clamav installs which were months out of date, as the cron file > never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line > is needed - as it works fine for me without it. /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i suggest to don't use the cron-script from upstream, but put the following in /var/spool/cron/crontabs/clamav: 12 * * * * /usr/bin/clamav-unofficial-sigs.sh Johannes From s.arcus at open-t.co.uk Wed Oct 19 10:17:38 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 19 Oct 2016 11:17:38 +0100 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: <580743EA.8030201@schoepfer.info> References: <580743EA.8030201@schoepfer.info> Message-ID: <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> On 19/10/16 10:59, Franzen wrote: > On 19.10.2016 11:42, Sebastian Arcus wrote: >> The clamav-unofficial-sigs.cron crond crontab file included with >> clamav-unofficial-sigs seems to be incompatible with the version of Cron >> used on Slackware. It uses the extra field for the username (clamav) >> which seems to break things on Slackware. I've just noticed this on >> several clamav installs which were months out of date, as the cron file >> never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line >> is needed - as it works fine for me without it. > > /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i > suggest to don't use the cron-script from upstream, but put the > following in /var/spool/cron/crontabs/clamav: > 12 * * * * /usr/bin/clamav-unofficial-sigs.sh I can't really make sense of what is going on here - because the clamav-unofficial-sigs.cron file is included in the clamav-unofficial-sigs.tar.gz - but looking at its contents, it should be part of the sources, as it comes from upstream. Same with the logrotate and the man files. Why are they included in the SBo scripts archive? From slackbuilds at schoepfer.info Wed Oct 19 13:41:38 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 19 Oct 2016 15:41:38 +0200 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> References: <580743EA.8030201@schoepfer.info> <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> Message-ID: <58077812.701@schoepfer.info> On 19.10.2016 12:17, Sebastian Arcus wrote: > On 19/10/16 10:59, Franzen wrote: >> On 19.10.2016 11:42, Sebastian Arcus wrote: >>> The clamav-unofficial-sigs.cron crond crontab file included with >>> clamav-unofficial-sigs seems to be incompatible with the version of Cron >>> used on Slackware. It uses the extra field for the username (clamav) >>> which seems to break things on Slackware. I've just noticed this on >>> several clamav installs which were months out of date, as the cron file >>> never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line >>> is needed - as it works fine for me without it. >> >> /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i >> suggest to don't use the cron-script from upstream, but put the >> following in /var/spool/cron/crontabs/clamav: >> 12 * * * * /usr/bin/clamav-unofficial-sigs.sh > > I can't really make sense of what is going on here - because the > clamav-unofficial-sigs.cron file is included in the > clamav-unofficial-sigs.tar.gz - but looking at its contents, it should > be part of the sources, as it comes from upstream. Same with the > logrotate and the man files. Why are they included in the SBo scripts > archive? The cron-file and logrotate-file come from upstream, they are generated by https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh, by the --install-all option. I assume the packager exracted the files because he didn't wan't to use the --install-all option for the package. As this package depends on clamav, which has also logrotate-script starting with /var/log/clamav/*.log { ,logrotate will complain about double configuration, so you don't need this logrotate at all. The best the you can do, is to fix the SlackBuild and propose it to the maintainer. Johannes From nishant at mnspace.net Wed Oct 19 20:26:32 2016 From: nishant at mnspace.net (Nishant Limbachia) Date: Wed, 19 Oct 2016 15:26:32 -0500 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: <58077812.701@schoepfer.info> References: <580743EA.8030201@schoepfer.info> <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> <58077812.701@schoepfer.info> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/19/2016 08:41 AM, Franzen wrote: > On 19.10.2016 12:17, Sebastian Arcus wrote: >> On 19/10/16 10:59, Franzen wrote: >>> On 19.10.2016 11:42, Sebastian Arcus wrote: >>>> The clamav-unofficial-sigs.cron crond crontab file included with >>>> clamav-unofficial-sigs seems to be incompatible with the version of Cron >>>> used on Slackware. It uses the extra field for the username (clamav) >>>> which seems to break things on Slackware. I've just noticed this on >>>> several clamav installs which were months out of date, as the cron file >>>> never worked. Also, I'm not sure the "/bin/bash" bit on the crontab line >>>> is needed - as it works fine for me without it. >>> >>> /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i >>> suggest to don't use the cron-script from upstream, but put the >>> following in /var/spool/cron/crontabs/clamav: >>> 12 * * * * /usr/bin/clamav-unofficial-sigs.sh >> >> I can't really make sense of what is going on here - because the >> clamav-unofficial-sigs.cron file is included in the >> clamav-unofficial-sigs.tar.gz - but looking at its contents, it should >> be part of the sources, as it comes from upstream. Same with the >> logrotate and the man files. Why are they included in the SBo scripts >> archive? > > The cron-file and logrotate-file come from upstream, they are generated by > https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh, by the --install-all option. I assume the packager exracted the files because he didn't wan't to use the --install-all option for the package. > As this package depends on clamav, which has also logrotate-script starting with > /var/log/clamav/*.log { > ,logrotate will complain about double configuration, so you don't need this logrotate at all. > The best the you can do, is to fix the SlackBuild and propose it to the maintainer. > > Johannes > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > I'm the maintainer for clamav-unofficial-sigs. logrotate and cron script are provided within the clamav-unofficial-sigs.sh script and upstream expects each user to use --install-all to generate those two. With SlackBuild, we shouldn't expect the user to do one additional step after install to actually use the package. So with every new version, I extract logrotate and cron script first and provide them as part of SlackBuild. As far as using upstream cron script is concerned, my intent was to provide a script in DOCS so builders will take it as an example and not simply copy and use the script in cron. You can roll your own or modify upstream script as you see fit. Here's my crontab (root) # Run clamav-unofficial-sigs script 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null I can provide my script as an example which would again go in DOCS and not anywhere else. Thanks, - -- Nishant Limbachia nishant at mnspace.net ### Please note the new pgp keys Old GPG Key: 0x0FF9D6D5 (expiring soon) Old GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5 New GPG Key: 0x3D46A2D1 New GPG Fingerprint: 44D1 27CE D07F 2ED1 B4AD 2BEE A828 D6D6 3D46 A2D1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYB9b4AAoJEKgo1tY9RqLRqRcQAITANT0yP19yMd8sWBgZemHN sTOOcqrkx7z76bYd/zekAWX7VUNKne6ts8Va5Q8u0Xm0ZynF9yBJALI8CXw/SFBn e5U1bhfmpM6Ja/XDVNUodvf6w+a89IisViVmtjp9Ex2PCJS0wID0REdilcF6+Jnz FUjFKMWnbJRPod/G/e5rakUpgZhTkc2C9FYYc3/nE1iaiS5l89Z/i6x3lxsuH6Mz WTQdIkExE1129XUCLpEvaL+hKNIGLTOz3jxIY4tChXtukDDzxiEFXumoo405EwaA yO9KN5izddiMZMBxySNUm+dj5aahEaGnFKVHyBDWh3OHuN8WzKISLnkYDklq4UYX CaAcZAMXNAaFiNybz+CLX29RfwBy0TB5qao5DkdyU9/15aE4nv+23uV++dN1QB1t kQNkUMMicBO1zO8mWVQX19W+V6IFQMx25ow62enCahTKqGA9oMJKYwTUYoA13Yxy CdukwpAUXnPi4kFJEEaNQtcMS+c+QeEB9+hSz79CVna5scrmNhQ1OWqTVS3dXy7x 5hnsnbvL9YJl67g4oiBJV6sNLrWyv85cDLGMLWUf8U+hE3lOYwBDcbiVWMBOtwkf /kKmgaK+dC16I0DHWGS2KY6IozJTk2kfReYE8DpVuv3xr5y+kNG5sTTpTiv7fLbU wUgJhjpu2PDCgoJ70eZN =8DGU -----END PGP SIGNATURE----- From ts at websafe.pl Wed Oct 19 22:26:32 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Thu, 20 Oct 2016 00:26:32 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir Message-ID: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> Hello, shouldn't usbredir be listed in REQUIRES of QEMU and spice-gtk? Because when QEMU is compiled without usbredir present (autodetected during compilation) virt-install usage will be problematic or even impossible. This won't work without usbredir: ~~~~ # virt-install \ --connect qemu:///system \ --name guest1 \ --cdrom /srv/storage/iso/CentOS-7-x86_64-Minimal-1511.iso \ --memory 1024 \ --disk none ERROR unsupported configuration: USB redirection is not supported by this version of QEMU Domain installation does not appear to have been successful. ~~~~ and will work when QEMU was compiled with usbredir present: ~~~~ # virt-install \ --connect qemu:///system \ --name guest1 \ --cdrom /srv/storage/iso/CentOS-7-x86_64-Minimal-1511.iso \ --memory 1024 \ --disk none Starting install... Creating domain... ~~~~ Same goes for spice-gtk. When spice-gtk is compiled without usbredir present then View Manager in virt-manager won't be able to connect to a VM's screen. -- 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 s.arcus at open-t.co.uk Wed Oct 19 23:22:20 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 20 Oct 2016 00:22:20 +0100 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: References: <580743EA.8030201@schoepfer.info> <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> <58077812.701@schoepfer.info> Message-ID: <504b88f0-8da2-5a33-ffca-84e3240ed6ac@open-t.co.uk> On 19/10/16 21:26, Nishant Limbachia wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 10/19/2016 08:41 AM, Franzen wrote: >> On 19.10.2016 12:17, Sebastian Arcus wrote: >>> On 19/10/16 10:59, Franzen wrote: >>>> On 19.10.2016 11:42, Sebastian Arcus wrote: >>>>> The clamav-unofficial-sigs.cron crond crontab file included with >>>>> clamav-unofficial-sigs seems to be incompatible with the version of > Cron >>>>> used on Slackware. It uses the extra field for the username (clamav) >>>>> which seems to break things on Slackware. I've just noticed this on >>>>> several clamav installs which were months out of date, as the cron file >>>>> never worked. Also, I'm not sure the "/bin/bash" bit on the crontab > line >>>>> is needed - as it works fine for me without it. >>>> >>>> /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i >>>> suggest to don't use the cron-script from upstream, but put the >>>> following in /var/spool/cron/crontabs/clamav: >>>> 12 * * * * /usr/bin/clamav-unofficial-sigs.sh >>> >>> I can't really make sense of what is going on here - because the >>> clamav-unofficial-sigs.cron file is included in the >>> clamav-unofficial-sigs.tar.gz - but looking at its contents, it should >>> be part of the sources, as it comes from upstream. Same with the >>> logrotate and the man files. Why are they included in the SBo scripts >>> archive? >> >> The cron-file and logrotate-file come from upstream, they are generated by >> > https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh, > by the --install-all option. I assume the packager exracted the files > because he didn't wan't to use the --install-all option for the package. >> As this package depends on clamav, which has also logrotate-script > starting with >> /var/log/clamav/*.log { >> ,logrotate will complain about double configuration, so you don't need > this logrotate at all. >> The best the you can do, is to fix the SlackBuild and propose it to > the maintainer. >> >> Johannes >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > I'm the maintainer for clamav-unofficial-sigs. logrotate and cron script > are provided within the clamav-unofficial-sigs.sh script and upstream > expects each user to use --install-all to generate those two. With > SlackBuild, we shouldn't expect the user to do one additional step after > install to actually use the package. So with every new version, I > extract logrotate and cron script first and provide them as part of > SlackBuild. > > As far as using upstream cron script is concerned, my intent was to > provide a script in DOCS so builders will take it as an example and not > simply copy and use the script in cron. You can roll your own or modify > upstream script as you see fit. > > Here's my crontab (root) > > # Run clamav-unofficial-sigs script > 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null > > I can provide my script as an example which would again go in DOCS and > not anywhere else. > I'm still not sure I'm following this: why is the cron file provided with the Slackbuilds at all, if it is incompatible with Slackware? It's worse than nothing - as the user would copy it in place and assume it works - as it comes from Slackbuilds and it is presumed to be tested to work with Slackware. Wouldn't it be better to provide either nothing or provide a suitable cron file that works or at least a patch? From kingbeowulf at gmail.com Wed Oct 19 23:23:10 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 19 Oct 2016 16:23:10 -0700 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> Message-ID: <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> On 10/19/2016 03:26 PM, Thomas Szteliga wrote: > Hello, > > shouldn't usbredir be listed in REQUIRES of QEMU and spice-gtk? > > Because when QEMU is compiled without usbredir present > (autodetected during compilation) virt-install usage will > be problematic or even impossible. > > --- Usbredir is not a "hard" dependency that prevents qemu from compiling. Rather, it is an optional dependency to add functionality. This is mentioned in the README. -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 ts at websafe.pl Wed Oct 19 23:46:34 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Thu, 20 Oct 2016 01:46:34 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> Message-ID: <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> On 10/20/2016 01:23 AM, King Beowulf wrote: > Usbredir is not a "hard" dependency that prevents qemu from compiling. > Rather, it is an optional dependency to add functionality. This is > mentioned in the README. I'm aware, but without usbredir virt-manager becomes kind of unusable. I remember on 14.1 usbredir was optional because the official libusb was too old, but since 14.2 that's not the case anymore... And in the current state the same slackbuild script will create two different binaries depending on the installed packages. And we're not able to build QEMU without usbredir support on a system with usbredir installed (no slackbuild switches / automatically enabled if found)... Maybe the *.nfo files should be extended by listing optional dependencies, so we could handle these an automated way? Another subject are dependencies required only during build-time vss dependencies required at runtime. I'm just thinking out loud ;-) -- 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 nishant at mnspace.net Thu Oct 20 02:00:51 2016 From: nishant at mnspace.net (Nishant Limbachia) Date: Wed, 19 Oct 2016 21:00:51 -0500 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: <504b88f0-8da2-5a33-ffca-84e3240ed6ac@open-t.co.uk> References: <580743EA.8030201@schoepfer.info> <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> <58077812.701@schoepfer.info> <504b88f0-8da2-5a33-ffca-84e3240ed6ac@open-t.co.uk> Message-ID: <1bdd104f-825e-af1a-e9ba-0fb99b3687e8@mnspace.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/19/2016 06:22 PM, Sebastian Arcus wrote: > On 19/10/16 21:26, Nishant Limbachia wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> On 10/19/2016 08:41 AM, Franzen wrote: >>> On 19.10.2016 12:17, Sebastian Arcus wrote: >>>> On 19/10/16 10:59, Franzen wrote: >>>>> On 19.10.2016 11:42, Sebastian Arcus wrote: >>>>>> The clamav-unofficial-sigs.cron crond crontab file included with >>>>>> clamav-unofficial-sigs seems to be incompatible with the version of >> Cron >>>>>> used on Slackware. It uses the extra field for the username (clamav) >>>>>> which seems to break things on Slackware. I've just noticed this on >>>>>> several clamav installs which were months out of date, as the cron file >>>>>> never worked. Also, I'm not sure the "/bin/bash" bit on the crontab >> line >>>>>> is needed - as it works fine for me without it. >>>>> >>>>> /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, i >>>>> suggest to don't use the cron-script from upstream, but put the >>>>> following in /var/spool/cron/crontabs/clamav: >>>>> 12 * * * * /usr/bin/clamav-unofficial-sigs.sh >>>> >>>> I can't really make sense of what is going on here - because the >>>> clamav-unofficial-sigs.cron file is included in the >>>> clamav-unofficial-sigs.tar.gz - but looking at its contents, it should >>>> be part of the sources, as it comes from upstream. Same with the >>>> logrotate and the man files. Why are they included in the SBo scripts >>>> archive? >>> >>> The cron-file and logrotate-file come from upstream, they are generated by >>> >> https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh, >> by the --install-all option. I assume the packager exracted the files >> because he didn't wan't to use the --install-all option for the package. >>> As this package depends on clamav, which has also logrotate-script >> starting with >>> /var/log/clamav/*.log { >>> ,logrotate will complain about double configuration, so you don't need >> this logrotate at all. >>> The best the you can do, is to fix the SlackBuild and propose it to >> the maintainer. >>> >>> Johannes >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >> >> I'm the maintainer for clamav-unofficial-sigs. logrotate and cron script >> are provided within the clamav-unofficial-sigs.sh script and upstream >> expects each user to use --install-all to generate those two. With >> SlackBuild, we shouldn't expect the user to do one additional step after >> install to actually use the package. So with every new version, I >> extract logrotate and cron script first and provide them as part of >> SlackBuild. >> >> As far as using upstream cron script is concerned, my intent was to >> provide a script in DOCS so builders will take it as an example and not >> simply copy and use the script in cron. You can roll your own or modify >> upstream script as you see fit. >> >> Here's my crontab (root) >> >> # Run clamav-unofficial-sigs script >> 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null >> >> I can provide my script as an example which would again go in DOCS and >> not anywhere else. >> > > I'm still not sure I'm following this: why is the cron file provided with the Slackbuilds at all, if it is incompatible with Slackware? It's worse than nothing - as the user would copy it in place and assume it works - as it comes from Slackbuilds and it is presumed to be tested to work with Slackware. Wouldn't it be better to provide either nothing or provide a suitable cron file that works or at least a patch? > _______________________________________________ > 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/ > It is provided because it is part of the script. You can generate one anytime by running /usr/bin/clamav-unofficial-sigs.sh --install-cron. Since it is part of script, I've packaged it in DOCS. - -- Nishant Limbachia nishant at mnspace.net ### Please note the new pgp keys Old GPG Key: 0x0FF9D6D5 (expiring soon) Old GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5 New GPG Key: 0x3D46A2D1 New GPG Fingerprint: 44D1 27CE D07F 2ED1 B4AD 2BEE A828 D6D6 3D46 A2D1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYCCVTAAoJEKgo1tY9RqLRmNsQAJC8tgYVb1piWLab+ic8Ekfz BXtyqhoT8OFtKKdETuc9eiowclbCiA4oBbyN8s6iwnRUkGaaayW9K1zJ3GtsEQYE MBaemwTkvryQmswM46Av4oIs31yAMTyaVQGwqH7jnW5aN6f1nFI7ZiIOvYBse2Bg hoBN1ltA7sMWi8rWZfGNiWySkadhwrZZeP0J0iKzQHLMQPbclrg5JV90s8JL07DV Uwx3iT4EFpt+Qb0HzZUsQFFLYLmUfIysp1zHXEyxVJVYbliLNMd2teIuYS2eyEZZ UPDrIZf8Cml9o4XJg643Wewaqcxch306PtH5QZ4thq9UcHf52Hb3GwjSNCJZiPc5 yhNJ/5UNUBBSg0NmmExhMQUHIXrFOQm6e/EpzczxLe/7hphhMC4V1BAWzepXKV+w ld4rPFYt2HZk+CJojsIXRcy4zcrs0VJq5PiIlS8XlBqSpJYqAkn/6//SwsbJMHUL VXF7s0YICEueyUU/hUbrdpO8J3JEOToQUZanbOWbR+7shUb+xKH0l4WQfxZ53UrE qc0MVNxH9pFb2M7jpwRTvRcPuOt2ojm7MLAdp2rk+iGD+ZEQAcR+CG86ZhMEshWR tJ6kY/rUs6vHVcipgJFuNHUCRm2sHaftzIhfHqvZsD2SCWpD87ObWGQz/m2qXnjj sHlzwkFdkInX8tBc2eno =QY+H -----END PGP SIGNATURE----- From willysr at slackbuilds.org Thu Oct 20 06:43:19 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 20 Oct 2016 13:43:19 +0700 Subject: [Slackbuilds-users] findpkg version mismatch in .info In-Reply-To: <20161017112814.da79974142e7b0be6af5ed17@laposte.net> References: <20161017112814.da79974142e7b0be6af5ed17@laposte.net> Message-ID: > Hi everybody ! > > findpkg is on version 20160817 both on the file to download in > findpkg.info and on the SlackBuild script, but the VERSION in the findpkg.info > file is still 20160710. > > It could confuse some auto-build scripts... 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 willysr at slackbuilds.org Thu Oct 20 06:50:36 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 20 Oct 2016 13:50:36 +0700 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> Message-ID: <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> > Maybe the *.nfo files should be extended by listing optional > dependencies, so we could handle these an automated way? NO REQUIRES in .info should only be used for mandatory dependencies, not optional dependencies. > Another subject are dependencies required only during build-time > vss dependencies required at runtime. This can be written in the README -- 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 s.arcus at open-t.co.uk Thu Oct 20 09:07:14 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 20 Oct 2016 10:07:14 +0100 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: <1bdd104f-825e-af1a-e9ba-0fb99b3687e8@mnspace.net> References: <580743EA.8030201@schoepfer.info> <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> <58077812.701@schoepfer.info> <504b88f0-8da2-5a33-ffca-84e3240ed6ac@open-t.co.uk> <1bdd104f-825e-af1a-e9ba-0fb99b3687e8@mnspace.net> Message-ID: <3fa2ccd1-d192-e00d-692a-91f47d1afa32@open-t.co.uk> >> >> I'm still not sure I'm following this: why is the cron file provided > with the Slackbuilds at all, if it is incompatible with Slackware? It's > worse than nothing - as the user would copy it in place and assume it > works - as it comes from Slackbuilds and it is presumed to be tested to > work with Slackware. Wouldn't it be better to provide either nothing or > provide a suitable cron file that works or at least a patch? >> _______________________________________________ >> 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/ >> > It is provided because it is part of the script. You can generate one > anytime by running /usr/bin/clamav-unofficial-sigs.sh --install-cron. > Since it is part of script, I've packaged it in DOCS.# Thanks for the explanation Nishant. Would it be maybe a good idea to add a little note in the README file at the end where it mentions the cron script - something like "note the enclosed cron script needs modifying to work with Slackware" - or something like that? From yalhcru at gmail.com Thu Oct 20 09:25:16 2016 From: yalhcru at gmail.com (B Watson) Date: Thu, 20 Oct 2016 05:25:16 -0400 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: References: <580743EA.8030201@schoepfer.info> <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> <58077812.701@schoepfer.info> Message-ID: On 10/19/16, Nishant Limbachia wrote: > Here's my crontab (root) > > # Run clamav-unofficial-sigs script > 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null Why is this incompatible with slackware? /usr/bin/ is a weird place to look for bash, but my 14.2 box does have a symlink there. Or is the script itself (clamav-unofficial-sigs.sh) non-functional? In that case you should fix it & include a patch with the SlackBuild. From slackbuilds at schoepfer.info Thu Oct 20 09:47:22 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 20 Oct 2016 11:47:22 +0200 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: References: <580743EA.8030201@schoepfer.info> <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> <58077812.701@schoepfer.info> Message-ID: <580892AA.5080902@schoepfer.info> On 20.10.2016 11:25, B Watson wrote: > On 10/19/16, Nishant Limbachia wrote: >> Here's my crontab (root) >> >> # Run clamav-unofficial-sigs script >> 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null > > Why is this incompatible with slackware? That's the cron-script from Nishant. The incompatible cron-script from upstream says: 6 * * * * clamav /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null My suggestion is: cat << EOF > /var/spool/cron/crontabs/clamav 6 * * * * /usr/bin/clamav-unofficial-sigs.sh > /dev/null EOF > Or is the script itself (clamav-unofficial-sigs.sh) non-functional? It is functional if executed as user clamav, as it has to work in conjunction with package "clamav", which takes care about the existence of the user clamav. Johannes From kristofru at gmail.com Thu Oct 20 13:28:53 2016 From: kristofru at gmail.com (Chris Abela) Date: Thu, 20 Oct 2016 15:28:53 +0200 Subject: [Slackbuilds-users] wireshark does not require qt5 Message-ID: I successfully built wireshark without qt5. Perhaps we consider removing it from the REQUIRED list. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristofru at gmail.com Thu Oct 20 13:55:04 2016 From: kristofru at gmail.com (Chris Abela) Date: Thu, 20 Oct 2016 15:55:04 +0200 Subject: [Slackbuilds-users] qt5.Slackbuild segmenation error Message-ID: I have new and default x86_64 Slackware 14.2 installation. qt5 does not build. The last 50 lines of my build logs may be found here: http://pastebin.com/Y4EGGMYB I do not need qt5 but I thought that you would want to know. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Oct 20 14:44:26 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 20 Oct 2016 21:44:26 +0700 Subject: [Slackbuilds-users] wireshark does not require qt5 In-Reply-To: References: Message-ID: <205d4cd7-8f27-ff05-cc6c-e1bc493223d3@slackbuilds.org> > I successfully built wireshark without qt5. Perhaps we consider removing it > from the REQUIRED list. No, it's still required for the new user interface https://blog.wireshark.org/2015/11/let-me-tell-you-about-wireshark-2-0/ without qt5, wireshark (default to use Qt) will be broken, but not wireshark-gtk (still use GTK) -- 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 kristofru at gmail.com Thu Oct 20 15:56:35 2016 From: kristofru at gmail.com (Chris Abela) Date: Thu, 20 Oct 2016 17:56:35 +0200 Subject: [Slackbuilds-users] wireshark does not require qt5 In-Reply-To: <205d4cd7-8f27-ff05-cc6c-e1bc493223d3@slackbuilds.org> References: <205d4cd7-8f27-ff05-cc6c-e1bc493223d3@slackbuilds.org> Message-ID: Mine probably built against the stock qt4. It works fine. On 20 Oct 2016 16:44, "Willy Sudiarto Raharjo" wrote: > > I successfully built wireshark without qt5. Perhaps we consider removing > it > > from the REQUIRED list. > > No, it's still required for the new user interface > https://blog.wireshark.org/2015/11/let-me-tell-you-about-wireshark-2-0/ > > without qt5, wireshark (default to use Qt) will be broken, but not > wireshark-gtk (still use GTK) > > -- > 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 miguel at thedeanda.com Thu Oct 20 17:47:41 2016 From: miguel at thedeanda.com (Miguel De Anda) Date: Thu, 20 Oct 2016 10:47:41 -0700 Subject: [Slackbuilds-users] jdk8 Message-ID: in the past, i feel like java has been installed such that a symlink /usr/lib64/java -> /usr/lib64/jdk-$VERSION but now it seems to be the opposite... i was hoping to keep both jdk8 and jdk7 installed so i can more easily switch between them: https://slackbuilds.org/slackbuilds/14.2/development/jdk/jdk.SlackBuild ( cd $PKG/usr/lib${LIBDIRSUFFIX} mv ${PRGNAM}${DVER} java ln -sf java ${PRGNAM}${DVER} ) is this the preferred method now or was this a mistake? for now i'm forced to uninstall jdk8 and use an untarred jdk8 on my home directory. thanks. From larryhaja at gmail.com Fri Oct 21 19:31:30 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Fri, 21 Oct 2016 12:31:30 -0700 Subject: [Slackbuilds-users] qt5.Slackbuild segmenation error In-Reply-To: References: Message-ID: I'm not familiar with that error. It works for me with Slackware64 full install. Trying to google the error message didn't pull up much information. --Larry On Thu, Oct 20, 2016 at 6:55 AM, Chris Abela wrote: > I have new and default x86_64 Slackware 14.2 installation. qt5 does not > build. The last 50 lines of my build logs may be found here: > > http://pastebin.com/Y4EGGMYB > > I do not need qt5 but I thought that you would want to know. > > Chris > > _______________________________________________ > 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 Sat Oct 22 02:06:48 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Oct 2016 09:06:48 +0700 Subject: [Slackbuilds-users] Updates - 20161022.1 Message-ID: <4ebd1e40-02c8-a7ea-d3a2-996008fdc2d6@slackbuilds.org> Sat Oct 22 01:50:45 UTC 2016 academic/gwyddion: Allow build without libminizip. accessibility/speech-dispatcher: Updated for version 0.8.5. audio/guitarix: Updated for version 0.35.2. audio/jalv: Updated for version 1.4.6. audio/sayonara-player: Updated source. audio/transcribe: Updated for version 8.65. desktop/Pulse-Glass: Switch to i586. desktop/fbmenugen: Updated for version 0.77. desktop/menutray: Updated for version 0.46. desktop/numix-icon-theme: Updated for version 0.3.871.201610060518. desktop/obmenu-generator: Updated for version 0.68. desktop/recoll: Updated for version 1.22.3. desktop/xdgmenumaker: Update README. desktop/xdgmenumaker: Updated for version 1.1. desktop/xfce4-volumed-pulse: Added (XFCE Volume Daemon). development/SDL2_gfx: Switch to i586. development/SQLAlchemy: Updated for version 1.1.2. development/atasm: Updated for version 1.07d, fix man page. development/dwarf: Updated for version 20161001. development/google-go-lang: Updated for version 1.7.3. development/gradle: Updated for version 3.1. development/gtest: Switch to i586. development/hhvm: Updated for version 3.15.2. development/julia: Updated for version 0.4.7. development/leveldb: Update DOWNLOAD and HOMEPAGE url. development/nodejs: Updated for version 6.8.1. development/nvi: Remove --enable-threads parameter. development/pkgconf: Added (compiler and linker metadata toolkit). development/pyvim: Updated for version 0.0.20. development/scite: Updated for version 3.7.0. games/blobwars: Updated for version 2.00. games/colem: Updated for version 3.8. games/connectagram: Updated for version 1.2.4. games/empire: Added (strategy game). games/fizmo: Updated for version 0.8.2, docs, /usr/games. games/fortune-dune: New HOMEPAGE. games/freeorion: Updated for version 0.4.6. games/jfsw_demo_data: Fix HOMEPAGE. games/jzintv: New HOMEPAGE. games/megamario: New HOMEPAGE. games/mrrescue: Updated for version 1.02e. games/oblige: Updated for version 7.50. games/openmw: Add patch against bullet 2.85.1. games/ostrichriders: Updated for version 0.6.4. games/snes9x: Updated for version 1.54.1. games/starfighter: Updated for version 2.0.2. games/supermariowar: Updated for version 2.0beta1. games/xarchon: Remove non-functional Adept game. games/xcowsay: Updated for version 1.4. games/xroar: Updated for version 0.34.5. gis/google-earth: Updated for version 7.1.7.2606. graphics/GraphicsMagick: Updated for version 1.3.25. graphics/fbida: Updated for version 2.12. graphics/gnofract4d: Switch to i586. graphics/pngcrush: Updated for version 1.8.8. graphics/pyformex: Switch to i586. graphics/tintii: Switch to i586. graphics/yesplz: Updated for version 22102016. libraries/CEGUI0.7: Switch to i586. libraries/GitPython: Updated for version 2.0.9. libraries/QDarkStyle: Switch to i586. libraries/SDL2: Updated for version 2.0.5. libraries/SlowAES: Update HOMEPAGE and DOWNLOAD url. libraries/alure: Switch to i586. libraries/assimp: Updated for version 3.3.1. libraries/botocore: Updated for version 1.4.62. libraries/bullet: Updated for version 2.85.1. libraries/facebook-python: Switch to i586. libraries/flatzebra: New HOMEPAGE. libraries/gitdb2: Added (IO of git-style object databases). libraries/gssdp: Updated for version 1.0.1. libraries/gupnp: Updated for version 1.0.1. libraries/libearth: Switch to i586. libraries/libmirage: Updated for version 3.0.5 libraries/libpst: Updated for version 0.6.68. libraries/libu2f-host: Updated for version 1.1.3. libraries/log4cplus: Added (A C++ logger). libraries/lunatic-python: Switch to i586. libraries/lvtk: Fix HOMEPAGE. libraries/ntl: Updated for version 10.1.0. libraries/pyte: Switch to i586. libraries/secp256k1: Updated for version 7d15cd78. libraries/smmap2: Added (A sliding memory map manager). libraries/yaml-cpp0.3: Switch to i586. libraries/yaml-cpp: Switch to i586. misc/KeePass: Updated for version 2.34. misc/deb2tgz: Added (convert Debian packages). misc/sbo-templates: Switch to i586. multimedia/freshplayerplugin: Updated for version 0.3.6. multimedia/mlt: Updated for version 6.2.0. multimedia/mp3fm: Switch to i586. multimedia/pepperflash-plugin: Added (flash PPAPI plugin). multimedia/pngnq-s9: Updated for version 2.0.2. multimedia/youtube-viewer: Updated for version 3.2.4. network/Electrum: Updated for version 2.7.9. network/aldryn-client: Updated for version 2.3.3. network/awscli: Updated for version 1.11.5. network/flexget: Updated for version 2.3.45. network/ganglia-web: Added (distributed monitoring web interface). network/ganglia: Added (distributed monitoring system). network/glusterfs: Updated for version 3.8.5. network/jdownloader: Removed (no longer working). network/pysub-dl: Switch to i586. network/python-onedrive: Switch to i586. network/r8168: Updated for version 8.043.01. network/teamviewer: Updated for version 11.0.67687. network/telegram: Updated for version 0.10.16. network/translate: Switch to i586. network/twine: Added (Utilities for interacting with PyPI). network/vcspull: Switch to i586. network/weetwit: Switch to i586. network/youtube-dl: Updated for version 2016.10.16. office/calibre: Updated for version 2.70.0 office/qute: Switch to i586. perl/perl-Date-Manip: Updated for version 6.56. perl/perl-IO-Socket-SSL: Updated for version 2.038. perl/perl-linux-desktop-files: Updated for version 0.12. python/PySDL2: Updated for version 0.9.5. python/Scrapy: Updated for version 1.2.1. python/aniso8601: Updated for version 1.2.0. python/argcomplete: Updated for version 1.6.0. python/chump: Updated for version 1.5.2. python/clint: Updated for version 0.5.1. python/gmpy: Fix HOMEPAGE. python/helpy: Switch to i586. python/jmespath: Switch to i586. python/pendulum: Updated for version 0.6.3. python/pkginfo: Added (API for querying the distutils metadata). python/prompt_toolkit: Updated for version 1.0.8. python/ptpython: Updated for version 0.36. python/pyresample: Updated for version 1.2.6. python/python-keybinder: New HOMEPAGE. python/python-keyring: Updated for version 10.0.2. python/python-mccabe: Switch to i586. python/python-tabulate: Switch to i586. python/regex: Updated for version 2016.10.22. python/requests-toolbelt: Added (utilities for python-requests). python/s3transfer: Updated for version 0.1.8. python/selenium: Updated for version 3.0.1. python/sge-pygame: Updated for version 1.2. python/stevedore: Updated for version 1.18.0. python/terminaltables: Updated for version 3.1.0. python/threadpool: Updated for version 1.3.2. python/tox: Updated for version 2.4.1. python/tqdm: Added (progress bar for Python). python/tzlocal: Updated for version 1.3. python/w3lib: Switch to i586. ruby/rubygem-bundler: Updated for version 1.13.5. system/aha: Updated for version 0.4.10. system/avfs: Updated for version 1.0.4. system/cdemu-client: Updated for version 3.0.4 system/cdemu-daemon: Updated for version 3.0.5 system/findpkg: Fix VERSION in .info. system/info2man: New HOMEPAGE. system/linuxconsoletools: Updated for version 1.6.0. system/man-db: Fix VERSION in .info file. system/man-pages-ja: Updated for version 20161015. system/nvidia-legacy304-driver: Added nvidia-installer. system/pymux: Updated for version 0.13. system/qemu-guest-agent: Updated for version 2.7.0. system/qemu: Updated for version 2.7.0. system/sdl-jstest: Updated for version 20160824git. system/slpkg: Updated for version 3.2.0. system/trachet: Switch to i586. system/unrtf: Updated for version 0.21.9. system/untex: Added (strip LaTeX commands from source file). system/veracrypt: Updated for version 1.19. system/vhba-module: Updated for version 20161009 system/vinterm: Fix HOMEPAGE. system/wine-staging: Updated for version 1.9.21. system/worker: Updated for version 3.8.4. system/xarchiver: Updated for version 0.5.4.7. +--------------------------+ -- 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 Sat Oct 22 07:39:38 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 22 Oct 2016 00:39:38 -0700 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> Message-ID: <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> On 10/19/2016 11:50 PM, Willy Sudiarto Raharjo wrote: >> Maybe the *.nfo files should be extended by listing optional >> dependencies, so we could handle these an automated way? > > NO > REQUIRES in .info should only be used for mandatory dependencies, not > optional dependencies. > >> Another subject are dependencies required only during build-time >> vss dependencies required at runtime. > > This can be written in the README > qemu README already mentions spice and usbredir as optional dependencies. spice-gtk README also mentions usbredir as an optional dependency. Perhaps a more precise wording can ovoid confusion. I suggest that the OP should assume that an optional dependency is expected to be present at COMPILE-TIME unless otherwise specified. Or the OP can just read the qemu/virt documentation. -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 bch at shroggslodge.freeserve.co.uk Sat Oct 22 08:07:25 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Sat, 22 Oct 2016 09:07:25 +0100 Subject: [Slackbuilds-users] Openshot Message-ID: Good morning everyone Is it likely that we will see a move towards the latest release of Openshot please? I am asking because I wondered, not withstanding and respecting maintainers' time constraints etc, if one of the issues would be that there has been some fundamental changes to the latest regarding dependencies and so forth. I am probably showing my ignorance, but I had read somewhere that it now requires QT (not GTK). Has anyone built the new release yet on Slackware and does it work fine ? Thanks for any insight etc. Peace and best wishes. Habs -------------- next part -------------- An HTML attachment was scrubbed... URL: From ts at websafe.pl Sat Oct 22 12:33:25 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 22 Oct 2016 14:33:25 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> Message-ID: <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> On 10/22/2016 09:39 AM, King Beowulf wrote: > qemu README already mentions spice and usbredir as optional > dependencies. spice-gtk README also mentions usbredir as an optional > dependency. Perhaps a more precise wording can ovoid confusion. > I suggest that the OP should assume that an optional dependency is > expected to be present at COMPILE-TIME unless otherwise specified. > Or the OP can just read the qemu/virt documentation. I'm aware. I can read, really ;-) But automated build tools won't know. And this causes, that the build order matters. We're no longer able to build qemu without usbredir when usbredir is somehow already present, because there's no way to pass --disable-usbredir to the qemu.Slackbuild. And what I'm really trying to say here is, that qemu without usbredir is missing an important feature and qemu without usbredir will make the virt-manager viewer unusable. So maybe usbredir should be considered as REQUIRED or at least there should be a switch for qemu.Slackbuild available, which would stop the build if usbredir is missing, so we have more control, or a switch allowing us to pass --disable-usbredir if we're building on a system, where usbredir is already installed. Before 14.1 usbredir was optional, because the official libusb was too old, that's not the case anymore. -- 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 414N at slacky.it Sat Oct 22 16:03:57 2016 From: 414N at slacky.it (414N) Date: Sat, 22 Oct 2016 18:03:57 +0200 Subject: [Slackbuilds-users] Openshot In-Reply-To: References: Message-ID: <8d88faf5-1c28-94b8-f385-90031d2204f0@slacky.it> Hi Habs, it seems that they're distributing the latest versions as AppImages, so there's no strict need to build a dedicated Slackware package if all you want is to test a new release. Compiling from source seems to now requires an additional effort, as dependencies are now split in several openshot-related packages (openshot-audio, libopenshot etc.). Alan Alberghini SBo clone: GitHub On 22/10/2016 10:07, bch at shroggslodge.freeserve.co.uk wrote: > Good morning everyone > > Is it likely that we will see a move towards the latest release of > Openshot please? > > I am asking because I wondered, not withstanding and respecting > maintainers' time constraints etc, if one of the issues would be that > there has been some fundamental changes to the latest regarding > dependencies and so forth. I am probably showing my ignorance, but I > had read somewhere that it now requires QT (not GTK). > > Has anyone built the new release yet on Slackware and does it work fine ? > > Thanks for any insight etc. Peace and best wishes. > Habs > > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Sat Oct 22 16:16:00 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 22 Oct 2016 18:16:00 +0200 Subject: [Slackbuilds-users] Openshot In-Reply-To: References: Message-ID: <57cce60e-e732-f80c-b718-c0c6e398a2ab@microlinux.fr> Le 22/10/2016 ? 10:07, bch at shroggslodge.freeserve.co.uk a ?crit : > Is it likely that we will see a move towards the latest release of > Openshot please? I had the same question recently. Openshot is a nifty little application, but unfortunately it's not exactly a stable one and indeed very crash-prone. I've found no information as to how to build more recent sources. This added to a general disappointment, so I looked for a replacement... and found the Flowblade video editor. A lesser-known app, though really great, and a perfect replacement for Openshot. You'll find the app and all its dependencies on SBo. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From atelszewski at gmail.com Sat Oct 22 17:28:43 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 22 Oct 2016 19:28:43 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> Message-ID: On 22/10/16 14:33, Thomas Szteliga wrote: > On 10/22/2016 09:39 AM, King Beowulf wrote: >> qemu README already mentions spice and usbredir as optional >> dependencies. spice-gtk README also mentions usbredir as an optional >> dependency. Perhaps a more precise wording can ovoid confusion. >> I suggest that the OP should assume that an optional dependency is >> expected to be present at COMPILE-TIME unless otherwise specified. >> Or the OP can just read the qemu/virt documentation. > > > I'm aware. I can read, really ;-) > But automated build tools won't know. > > And this causes, that the build order matters. > > We're no longer able to build qemu without usbredir when usbredir > is somehow already present, because there's no way to pass > --disable-usbredir to the qemu.Slackbuild. > > And what I'm really trying to say here is, that qemu without > usbredir is missing an important feature and qemu without > usbredir will make the virt-manager viewer unusable. > That depends on your use case. Not everybody requires that feature. And not everybody uses virt-manager. > So maybe usbredir should be considered as REQUIRED > or at least there should be a switch for qemu.Slackbuild > available, which would stop the build if usbredir is missing, > so we have more control, or a switch allowing us to pass > --disable-usbredir if we're building on a system, where > usbredir is already installed. > Something that is not required, shouldn't be flagged as required as long as it makes sense. But your proposal to forcibly disable building against usbredir is viable. If it solves your problem, then ask the maintainer to add it. You can never have too few options ;-) > Before 14.1 usbredir was optional, because the official libusb > was too old, that's not the case anymore. > No, it was optional, because it was optional ;-) The SlackBuild build shipped with newer version of libusb linked statically (?) to allow you to use usbredir. All that being said, I'm using QEMU with usbredir support compiled-in, everything under libvirt ;-) > > > > _______________________________________________ > 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/ > -- Best regards, Andrzej Telszewski From yalhcru at gmail.com Sat Oct 22 17:40:00 2016 From: yalhcru at gmail.com (B Watson) Date: Sat, 22 Oct 2016 13:40:00 -0400 Subject: [Slackbuilds-users] qt5.Slackbuild segmenation error In-Reply-To: References: Message-ID: On 10/20/16, Chris Abela wrote: > I have new and default x86_64 Slackware 14.2 installation. qt5 does not > build. The last 50 lines of my build logs may be found here: > internal compiler error: Illegal instruction Is that repeatable? Does it always fail in the same place with the same error message? If not, it's probably heat-related. Clean vents, make sure fan's running, check CPU temperature while the compile's going. Try running 'watch sensors' in another terminal while qt5 is building. qt5 is a beast. Trying to compile massive projects like qt5 can expose cooling problems that might not be noticeable in normal use... ...if it turns out to be repeatable, always fails with 'illegal instruction' trying to build .obj/moc_qquicktexthandle.o, then it's likely an issue with gcc itself, but possibly one that can be worked around by messing with the SLKCFLAGS or patching the source a little. googling for the exact error message might result in some useful info (if it happened to you, odds are it's happened to someone else). From fernando.lopezjr at gmail.com Sat Oct 22 22:22:30 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 22 Oct 2016 16:22:30 -0600 Subject: [Slackbuilds-users] Openshot In-Reply-To: <57cce60e-e732-f80c-b718-c0c6e398a2ab@microlinux.fr> References: <57cce60e-e732-f80c-b718-c0c6e398a2ab@microlinux.fr> Message-ID: what about cinelerra? On Sat, Oct 22, 2016 at 10:16 AM, Nicolas Kovacs wrote: > Le 22/10/2016 ? 10:07, bch at shroggslodge.freeserve.co.uk a ?crit : > > Is it likely that we will see a move towards the latest release of > > Openshot please? > > I had the same question recently. Openshot is a nifty little > application, but unfortunately it's not exactly a stable one and indeed > very crash-prone. > > I've found no information as to how to build more recent sources. This > added to a general disappointment, so I looked for a replacement... and > found the Flowblade video editor. A lesser-known app, though really > great, and a perfect replacement for Openshot. You'll find the app and > all its dependencies on SBo. > > Cheers, > > Niki > > -- > Microlinux - Solutions informatiques durables > 7, place de l'?glise - 30730 Montpezat > Web : http://www.microlinux.fr > Mail : info at microlinux.fr > T?l. : 04 66 63 10 32 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sat Oct 22 22:34:30 2016 From: 1.41421 at gmail.com (JCA) Date: Sat, 22 Oct 2016 16:34:30 -0600 Subject: [Slackbuilds-users] Openshot In-Reply-To: References: <57cce60e-e732-f80c-b718-c0c6e398a2ab@microlinux.fr> Message-ID: On this subject, it would be nice to have a free video editor with frame-accurate capabilities when dealing with H.264 (or HVAC) videos. Such things seem to exist for Windows (at least for H.264) and probably Mac, but not for Linux, AFAIK. On Oct 22, 2016 4:22 PM, "Fernando Lopez" wrote: > what about cinelerra? > > On Sat, Oct 22, 2016 at 10:16 AM, Nicolas Kovacs > wrote: > >> Le 22/10/2016 ? 10:07, bch at shroggslodge.freeserve.co.uk a ?crit : >> > Is it likely that we will see a move towards the latest release of >> > Openshot please? >> >> I had the same question recently. Openshot is a nifty little >> application, but unfortunately it's not exactly a stable one and indeed >> very crash-prone. >> >> I've found no information as to how to build more recent sources. This >> added to a general disappointment, so I looked for a replacement... and >> found the Flowblade video editor. A lesser-known app, though really >> great, and a perfect replacement for Openshot. You'll find the app and >> all its dependencies on SBo. >> >> Cheers, >> >> Niki >> >> -- >> Microlinux - Solutions informatiques durables >> 7, place de l'?glise - 30730 Montpezat >> Web : http://www.microlinux.fr >> Mail : info at microlinux.fr >> T?l. : 04 66 63 10 32 >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > > > -- > > ------------ > Regards, > Fernando Lopez Jr. > > _______________________________________________ > 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 ts at websafe.pl Sat Oct 22 23:26:43 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 23 Oct 2016 01:26:43 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> Message-ID: On 10/22/2016 07:28 PM, Andrzej Telszewski wrote: > Something that is not required, shouldn't be flagged as required as long > as it makes sense. > But your proposal to forcibly disable building against usbredir is viable. > If it solves your problem, then ask the maintainer to add it. > You can never have too few options ;-) OK, before I ask I wanted to discuss this. And yes, You're right: "Something that is not required, shouldn't be flagged as required" so maybe it's time to rethink the way OPTIONAL dependencies are announced? The README is OK, but it requires with every new release to re-read all READMEs and check, if any optional deps were added. It would be much easier to have an "OPTIONAL" tag in addition to "REQUIRES" in the *.nfo files. Don't you think? >> Before 14.1 usbredir was optional, because the official libusb >> was too old, that's not the case anymore. > No, it was optional, because it was optional ;-) ;-) -- 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 chris.willing at iinet.net.au Sat Oct 22 23:56:08 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 23 Oct 2016 09:56:08 +1000 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> Message-ID: On 23/10/16 09:26, Thomas Szteliga wrote: > On 10/22/2016 07:28 PM, Andrzej Telszewski wrote: >> Something that is not required, shouldn't be flagged as required as long >> as it makes sense. >> But your proposal to forcibly disable building against usbredir is viable. >> If it solves your problem, then ask the maintainer to add it. >> You can never have too few options ;-) > > > OK, before I ask I wanted to discuss this. And yes, You're right: > > "Something that is not required, shouldn't be flagged as required" The trouble is that some peoples' REQUIRED is/are other peoples' OPTIONAL. > so maybe it's time to rethink the way OPTIONAL dependencies are > announced? The README is OK, but it requires with every new release > to re-read all READMEs and check, if any optional deps were added. > It would be much easier to have an "OPTIONAL" tag in addition > to "REQUIRES" in the *.nfo files. Don't you think? > Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) non obvious cases? Presumably the maintainer. If a maintainer's balance of REQUIRED/OPTIONAL deps doesn't suit someone else's particular needs/wants, then the builder will have to change their personal .info files anyway (or complain to the maintainer). chris From ts at websafe.pl Sun Oct 23 00:04:17 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 23 Oct 2016 02:04:17 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> Message-ID: <672245d2-af8c-6c4a-7d01-45abc0e808fe@websafe.pl> On 10/23/2016 01:56 AM, Christoph Willing wrote: > Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) non > obvious cases? Presumably the maintainer. If a maintainer's balance of > REQUIRED/OPTIONAL deps doesn't suit someone else's particular > needs/wants, then the builder will have to change their personal .info > files anyway (or complain to the maintainer). Hmm, I guess the source developer decides what is really required and what is optional, and the slackbuild maintainer decides which optional (for the developer) dependencies should be treated as REQUIRED by the distribution... -- 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 ts at websafe.pl Sun Oct 23 00:17:29 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 23 Oct 2016 02:17:29 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> Message-ID: <0be08a0b-ff73-28c2-94c7-68d765efb2bd@websafe.pl> Just a short review: http://www.rpm.org/wiki/PackagerDocs/BooleanDependencies "Requires, Recommends, Suggests, Supplements, Enhances, Conflicts" ~~~~ Weak dependencies In addition to the strong dependencies created by Requires, there are 4 dependencies that are completely ignored by rpm itself. Their purpose is to be used by dependency solvers to make choices about what packages to install. They come in two levels of strength: + Weak: By default the dependency solver shall attempt to process the dependency as though it were strong. If this is results in an error then they should be ignored and not trigger an error or warning. + Very weak: By default the dependency solver shall ignore them. But they may be used to show the matching packages as option to the user. The depsolver may offer to treat the weak like very weak relations or the other way round. In addition to normal, forward relations that behave the same way as Requires: there are also two weak dependencies that work backward. Instead of adding packages that match the relations of to-be-installed packages these Relations add packages that contain relations matching to-be-installed packages. ~~~~ More here: http://www.rpm.org/wiki/PackagerDocs/Dependencies -- 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 kingbeowulf at gmail.com Sun Oct 23 00:44:18 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 22 Oct 2016 17:44:18 -0700 Subject: [Slackbuilds-users] qt5.Slackbuild segmenation error In-Reply-To: References: Message-ID: <1900b67b-f74e-f29d-307c-3239f19b13b9@gmail.com> On 10/20/2016 06:55 AM, Chris Abela wrote: > I have new and default x86_64 Slackware 14.2 installation. qt5 does not > build. The last 50 lines of my build logs may be found here: > > http://pastebin.com/Y4EGGMYB > > I do not need qt5 but I thought that you would want to know. > > Chris > > Just built it here in a qemy VM (full Slack64 14.2). No issues. I would reinstall the compiles packages, and make sure something didn't get scrambled if you are using multilib. And as others had said: possible hardware issues (heat, bad HD). -------------- 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 Oct 23 00:51:56 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 22 Oct 2016 17:51:56 -0700 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <0be08a0b-ff73-28c2-94c7-68d765efb2bd@websafe.pl> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <0be08a0b-ff73-28c2-94c7-68d765efb2bd@websafe.pl> Message-ID: On 10/22/2016 05:17 PM, Thomas Szteliga wrote: > Just a short review: > > http://www.rpm.org/wiki/PackagerDocs/BooleanDependencies > > "Requires, Recommends, Suggests, Supplements, Enhances, Conflicts" > > > ~~~~ > Weak dependencies > > In addition to the strong dependencies created by Requires, there are 4 > dependencies that are completely ignored by rpm itself. Their purpose is > to be used by dependency solvers to make choices about what packages to > install. They come in two levels of strength: > > + Weak: By default the dependency solver shall attempt to process > the dependency > > as though it were strong. If this is results in an error then they > should be ignored and not trigger an error or warning. > > + Very weak: By default the dependency solver shall ignore them. > But they may be used to show the matching packages as option > to the user. > > The depsolver may offer to treat the weak like very weak relations or > the other way round. > > In addition to normal, forward relations that behave the same way as > Requires: there are also two weak dependencies that work backward. > Instead of adding packages that match the relations of to-be-installed > packages these Relations add packages that contain relations matching > to-be-installed packages. > ~~~~ > > > More here: http://www.rpm.org/wiki/PackagerDocs/Dependencies > > That's just nuts. Lets not try to force Slackware and SBo into a Debian/Fedora/Gentoo etc mold. Sure, it takes a bit more work for the end user to sift through what he needs for his special use case and that is how it should be. -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 kingbeowulf at gmail.com Sun Oct 23 01:08:56 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 22 Oct 2016 18:08:56 -0700 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> Message-ID: <8e55a9a3-3d15-3e56-8418-b2cf33f894e2@gmail.com> On 10/22/2016 04:56 PM, Christoph Willing wrote: > On 23/10/16 09:26, Thomas Szteliga wrote: >> On 10/22/2016 07:28 PM, Andrzej Telszewski wrote: >>> Something that is not required, shouldn't be flagged as required as long >>> as it makes sense. >>> But your proposal to forcibly disable building against usbredir is >>> viable. >>> If it solves your problem, then ask the maintainer to add it. >>> You can never have too few options ;-) >> >> >> OK, before I ask I wanted to discuss this. And yes, You're right: >> >> "Something that is not required, shouldn't be flagged as required" > > The trouble is that some peoples' REQUIRED is/are other peoples' OPTIONAL. > > >> so maybe it's time to rethink the way OPTIONAL dependencies are >> announced? The README is OK, but it requires with every new release >> to re-read all READMEs and check, if any optional deps were added. >> It would be much easier to have an "OPTIONAL" tag in addition >> to "REQUIRES" in the *.nfo files. Don't you think? >> > Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) non > obvious cases? Presumably the maintainer. If a maintainer's balance of > REQUIRED/OPTIONAL deps doesn't suit someone else's particular > needs/wants, then the builder will have to change their personal .info > files anyway (or complain to the maintainer). > > chris > Chris, thank you for your explanation. To all others: there are just too many use cases to make everyone happy. Some of you will just have to do some real work on your own. For example, MOST of the slackbuilds I pull from SBo for my use are customized. Perhaps I need a non-default function, or to drop a function/dependency I can live without. I'm not going force the maintainers toward my use case. My LQ HOW-TO for Boinc-7.6.33 is a good example of this. Does anyone REALLY want wxGTK3 to have a hard requirement for webkitgtk? -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 ts at websafe.pl Sun Oct 23 01:30:05 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 23 Oct 2016 03:30:05 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: <8e55a9a3-3d15-3e56-8418-b2cf33f894e2@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <8e55a9a3-3d15-3e56-8418-b2cf33f894e2@gmail.com> Message-ID: On 10/23/2016 03:08 AM, King Beowulf wrote: > Some of you will just have to do some real work on your own. > For example, MOST of the slackbuilds I pull from SBo for my use are > customized. Perhaps I need a non-default function, or to drop a > function/dependency I can live without. I'm not going force the > maintainers toward my use case. > My LQ HOW-TO for Boinc-7.6.33 is a good example of this. Does anyone > REALLY want wxGTK3 to have a hard requirement for webkitgtk? I just wanted to talk about an ~OPTIONAL tag in *.nfo for better organized optional dependencies than checking each time the README. I'm not trying to force anyone, just wanted to discuss this. Something like CONFLICTS in *.nfo could be a good thing too, or not? https://slackbuilds.org/repository/14.2/network/postfix/ https://slackbuilds.org/repository/14.2/network/exim/ https://slackbuilds.org/repository/14.2/network/opensmtpd/ CONFLICTS: sendmail 8-) -- 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 Sun Oct 23 01:38:03 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 23 Oct 2016 08:38:03 +0700 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <8e55a9a3-3d15-3e56-8418-b2cf33f894e2@gmail.com> Message-ID: > I just wanted to talk about an ~OPTIONAL tag in *.nfo > for better organized optional dependencies than checking > each time the README. I'm not trying to force anyone, > just wanted to discuss this. > > Something like CONFLICTS in *.nfo could be a good thing > too, or not? > > https://slackbuilds.org/repository/14.2/network/postfix/ > https://slackbuilds.org/repository/14.2/network/exim/ > https://slackbuilds.org/repository/14.2/network/opensmtpd/ > > CONFLICTS: sendmail That's the purpose of README (it should be read) While some package may have small number of optional deps, others may have more than a dozen and the maintainer may or may not be able to detect all of it. automatic tools are there to help us building the job automatically, but if it requires special attention, it's up to us (users) to do the job done :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kristofru at gmail.com Sun Oct 23 06:04:30 2016 From: kristofru at gmail.com (Chris Abela) Date: Sun, 23 Oct 2016 06:04:30 +0000 Subject: [Slackbuilds-users] qt5.Slackbuild segmenation error In-Reply-To: <1900b67b-f74e-f29d-307c-3239f19b13b9@gmail.com> References: <1900b67b-f74e-f29d-307c-3239f19b13b9@gmail.com> Message-ID: I confirm that it built fine on a newer machine. I also agree that it looks like a localised hardware issue. I will take it from here. Thank You Chris On Sun, 23 Oct 2016 02:44 King Beowulf, wrote: > On 10/20/2016 06:55 AM, Chris Abela wrote: > > I have new and default x86_64 Slackware 14.2 installation. qt5 does not > > build. The last 50 lines of my build logs may be found here: > > > > http://pastebin.com/Y4EGGMYB > > > > I do not need qt5 but I thought that you would want to know. > > > > Chris > > > > > > Just built it here in a qemy VM (full Slack64 14.2). No issues. > > I would reinstall the compiles packages, and make sure something didn't > get scrambled if you are using multilib. > > And as others had said: possible hardware issues (heat, bad HD). > > > _______________________________________________ > 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 matteo.bernardini at gmail.com Sun Oct 23 06:39:33 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 23 Oct 2016 08:39:33 +0200 Subject: [Slackbuilds-users] Openshot In-Reply-To: References: Message-ID: 2016-10-22 10:07 GMT+02:00 : > Good morning everyone > > Is it likely that we will see a move towards the latest release of Openshot > please? > > I am asking because I wondered, not withstanding and respecting maintainers' > time constraints etc, if one of the issues would be that there has been some > fundamental changes to the latest regarding dependencies and so forth. I am > probably showing my ignorance, but I had read somewhere that it now requires > QT (not GTK). > > Has anyone built the new release yet on Slackware and does it work fine ? > > Thanks for any insight etc. Peace and best wishes. > Habs > > > _______________________________________________ > 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 Sun Oct 23 06:44:30 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 23 Oct 2016 08:44:30 +0200 Subject: [Slackbuilds-users] Openshot In-Reply-To: References: Message-ID: 2016-10-22 10:07 GMT+02:00 : > Good morning everyone > > Is it likely that we will see a move towards the latest release of Openshot > please? > > I am asking because I wondered, not withstanding and respecting maintainers' > time constraints etc, if one of the issues would be that there has been some > fundamental changes to the latest regarding dependencies and so forth. I am > probably showing my ignorance, but I had read somewhere that it now requires > QT (not GTK). > > Has anyone built the new release yet on Slackware and does it work fine ? > > Thanks for any insight etc. Peace and best wishes. > Habs (sorry for the previous empty reply, finger slipped!) Hi Habs, I'have not upgraded to openshot 2.x yet as it has been a beta version until this august... but the main reason why I haven't upgraded yet is that the new version is based on python3 and ATM I'm trying to avoid python3 stuff on my installations: for this reason I'm also inclined to drop completely openshot and its two dependencies goocanvas and pygoocanvas. if someone is interested in maintaining these scripts, please step in. Matteo From dn2010 at gmail.com Sun Oct 23 06:46:43 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Sun, 23 Oct 2016 09:46:43 +0300 Subject: [Slackbuilds-users] cholmod build failure Message-ID: <20161023094643.6988da82@darkstar.example.net> cholmod build failed on my system. It's fully updated slackware64 14.2 with atlas and lapack-atlas providing blas and lapack respectivelly. It also failed with similar -current, but it has other problems, like atlas cannot be build on x86_64 due to newer gcc and other build tools. make cholmod_demo cholmod_l_demo cholmod_simple make[2]: ???? ? ??????? ?/tmp/SBo/SuiteSparse/CHOLMOD/Demo? gcc -DHAVE_CONFIG_H -I. -I.. -I../Include -I../Include -O2 -fPIC -fexceptions -D_FILE_OFFSET_BITS=64 -c -o cholmod_demo.o cholmod_demo.c /bin/sh ../libtool --tag=CC --mode=link gcc -O2 -fPIC -fexceptions -D_FILE_OFFSET_BITS=64 -o cholmod_demo cholmod_demo.o ../libcholmod.la -lsuitesparseconfig libtool: link: gcc -O2 -fPIC -fexceptions -D_FILE_OFFSET_BITS=64 -o .libs/cholmod_demo cholmod_demo.o ../.libs/libcholmod.so -lcolamd -lamd -lmetis -lccolamd -lcamd -lm -llapack -lcblas -lf77blas -latlas -lsuitesparseconfig ../.libs/libcholmod.so: undefined reference to `_gfortran_transfer_character_write' ../.libs/libcholmod.so: undefined reference to `_gfortran_transfer_integer_write' ../.libs/libcholmod.so: undefined reference to `_gfortran_st_write_done' ../.libs/libcholmod.so: undefined reference to `_gfortran_st_write' ../.libs/libcholmod.so: undefined reference to `_gfortran_stop_string' collect2: error: ld returned 1 exit status Makefile:437: ?????? ?????????? ??????? ??? ???? ?cholmod_demo? make[2]: *** [cholmod_demo] ?????? 1 make[2]: ????? ?? ???????? ?/tmp/SBo/SuiteSparse/CHOLMOD/Demo? Makefile:592: ?????? ?????????? ??????? ??? ???? ?check-am? make[1]: *** [check-am] ?????? 2 make[1]: ????? ?? ???????? ?/tmp/SBo/SuiteSparse/CHOLMOD/Demo? Makefile:570: ?????? ?????????? ??????? ??? ???? ?check-recursive? make: *** [check-recursive] ?????? 1 Russian text at the end is: failed to build target XXX leaving directory YYY WBR, Daniil Bratashov. From matteo.bernardini at gmail.com Sun Oct 23 08:50:14 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 23 Oct 2016 10:50:14 +0200 Subject: [Slackbuilds-users] cholmod build failure In-Reply-To: <20161023094643.6988da82@darkstar.example.net> References: <20161023094643.6988da82@darkstar.example.net> Message-ID: 2016-10-23 8:46 GMT+02:00 Daniil Bratashov : > cholmod build failed on my system. It's fully updated slackware64 14.2 > with atlas and lapack-atlas providing blas and lapack respectivelly. ... > make cholmod_demo cholmod_l_demo cholmod_simple > make[2]: ???? ? ??????? ?/tmp/SBo/SuiteSparse/CHOLMOD/Demo? > gcc -DHAVE_CONFIG_H -I. -I.. -I../Include -I../Include -O2 -fPIC > -fexceptions -D_FILE_OFFSET_BITS=64 -c -o cholmod_demo.o > cholmod_demo.c /bin/sh ../libtool --tag=CC --mode=link gcc -O2 > -fPIC -fexceptions -D_FILE_OFFSET_BITS=64 -o cholmod_demo > cholmod_demo.o ../libcholmod.la -lsuitesparseconfig libtool: link: gcc > -O2 -fPIC -fexceptions -D_FILE_OFFSET_BITS=64 -o .libs/cholmod_demo > cholmod_demo.o ../.libs/libcholmod.so -lcolamd -lamd -lmetis -lccolamd > -lcamd -lm -llapack -lcblas -lf77blas -latlas > -lsuitesparseconfig ../.libs/libcholmod.so: undefined reference to > `_gfortran_transfer_character_write' ../.libs/libcholmod.so: undefined > reference to `_gfortran_transfer_integer_write' ../.libs/libcholmod.so: > undefined reference to > `_gfortran_st_write_done' ../.libs/libcholmod.so: undefined reference > to `_gfortran_st_write' ../.libs/libcholmod.so: undefined reference to > `_gfortran_stop_string' collect2: error: ld returned 1 exit status > Makefile:437: ?????? ?????????? ??????? ??? ???? ?cholmod_demo? > make[2]: *** [cholmod_demo] ?????? 1 make[2]: ????? ?? ???????? > ?/tmp/SBo/SuiteSparse/CHOLMOD/Demo? Makefile:592: ?????? ?????????? > ??????? ??? ???? ?check-am? make[1]: *** [check-am] ?????? 2 make[1]: > ????? ?? ???????? ?/tmp/SBo/SuiteSparse/CHOLMOD/Demo? Makefile:570: > ?????? ?????????? ??????? ??? ???? ?check-recursive? make: *** > [check-recursive] ?????? 1 > > Russian text at the end is: > failed to build target XXX > leaving directory YYY > > WBR, Daniil Bratashov. Hi Daniil, I think it's a matter of underlinking: try substituting the autotoolize.diff patch in the cholmod.SlackBuild directory with the one attached where I force linking against the gfortran libraries in the cholmod demo autotools file. Matteo -------------- next part -------------- diff --git a/Check/Makefile.am b/Check/Makefile.am new file mode 100644 --- /dev/null +++ b/Check/Makefile.am @@ -0,0 +1,26 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(SUITESPARSECONFIG_CFLAGS) + +EXTRA_DIST = \ + License.txt \ + lesser.txt + +CHECKSRC = \ + cholmod_check.c \ + cholmod_read.c \ + cholmod_write.c + +noinst_LTLIBRARIES = \ + libchecki.la \ + libcheckl.la \ + libcheck.la + +libchecki_la_SOURCES = $(CHECKSRC) +libchecki_la_LIBADD = $(SUITESPARSECONFIG_LIBS) +libchecki_la_CPPFLAGS= $(AM_CPPFLAGS) + +libcheckl_la_SOURCES = $(CHECKSRC) +libcheckl_la_LIBADD = $(SUITESPARSECONFIG_LIBS) +libcheckl_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +libcheck_la_SOURCES = +libcheck_la_LIBADD = libchecki.la libcheckl.la diff --git a/Cholesky/Makefile.am b/Cholesky/Makefile.am new file mode 100644 --- /dev/null +++ b/Cholesky/Makefile.am @@ -0,0 +1,41 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(COLAMD_CFLAGS) $(AMD_CFLAGS) $(SUITESPARSECONFIG_CFLAGS) + +EXTRA_DIST = \ + License.txt \ + lesser.txt + +CHOLESKYSRC = \ + cholmod_amd.c \ + cholmod_analyze.c \ + cholmod_colamd.c \ + cholmod_etree.c \ + cholmod_factorize.c \ + cholmod_postorder.c \ + cholmod_rcond.c \ + cholmod_resymbol.c \ + cholmod_rowcolcounts.c \ + cholmod_rowfac.c \ + cholmod_solve.c \ + cholmod_spsolve.c + +noinst_HEADERS = \ + t_cholmod_lsolve.c \ + t_cholmod_ltsolve.c \ + t_cholmod_rowfac.c \ + t_cholmod_solve.c + +noinst_LTLIBRARIES = \ + libcholeskyi.la \ + libcholeskyl.la \ + libcholesky.la + +libcholeskyi_la_SOURCES = $(CHOLESKYSRC) +libcholeskyi_la_LIBADD = $(COLAMD_LIBS) $(AMD_LIBS) $(SUITESPARSECONFIG_LIBS) -lm +libcholeskyi_la_CPPFLAGS = $(AM_CPPFLAGS) + +libcholeskyl_la_SOURCES = $(CHOLESKYSRC) +libcholeskyl_la_LIBADD = $(COLAMD_LIBS) $(AMD_LIBS) $(SUITESPARSECONFIG_LIBS) -lm +libcholeskyl_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +libcholesky_la_SOURCES = +libcholesky_la_LIBADD = libcholeskyi.la libcholeskyl.la diff --git a/Core/Makefile.am b/Core/Makefile.am new file mode 100644 --- /dev/null +++ b/Core/Makefile.am @@ -0,0 +1,44 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(SUITESPARSECONFIG_CFLAGS) + +EXTRA_DIST = \ + License.txt \ + lesser.txt + +CORESRC = \ + cholmod_aat.c \ + cholmod_add.c \ + cholmod_band.c \ + cholmod_change_factor.c \ + cholmod_common.c \ + cholmod_complex.c \ + cholmod_copy.c \ + cholmod_dense.c \ + cholmod_error.c \ + cholmod_factor.c \ + cholmod_memory.c \ + cholmod_sparse.c \ + cholmod_transpose.c \ + cholmod_triplet.c \ + cholmod_version.c + +noinst_HEADERS = \ + t_cholmod_change_factor.c \ + t_cholmod_dense.c \ + t_cholmod_transpose.c \ + t_cholmod_triplet.c + +noinst_LTLIBRARIES = \ + libcorei.la \ + libcorel.la \ + libcore.la + +libcorei_la_SOURCES = $(CORESRC) +libcorei_la_LIBADD = $(SUITESPARSECONFIG_LIBS) -lm +libcorei_la_CPPFLAGS = $(AM_CPPFLAGS) + +libcorel_la_SOURCES = $(CORESRC) +libcorel_la_LIBADD = $(SUITESPARSECONFIG_LIBS) -lm +libcorel_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +libcore_la_SOURCES = +libcore_la_LIBADD = libcorei.la libcorel.la diff --git a/Demo/Makefile.am b/Demo/Makefile.am new file mode 100644 --- /dev/null +++ b/Demo/Makefile.am @@ -0,0 +1,60 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(SUITESPARSECONFIG_CFLAGS) + +EXTRA_DIST = \ + License.txt \ + gpl.txt + +dist_noinst_HEADERS = \ + cholmod_demo.h + +dist_noinst_DATA = \ + Matrix/bcsstk01.tri \ + Matrix/lp_afiro.tri \ + Matrix/can___24.mtx \ + Matrix/c.tri + +noinst_PROGRAMS = \ + reade \ + readhb \ + readhb2 + +reade_SOURCES = reade.f +readhb_SOURCES = readhb.f +readhb2_SOURCES = readhb2.f + +if MOD_CHOLESKY +if MOD_CHECK +if MOD_MATRIXOPS + +check_PROGRAMS = \ + cholmod_demo \ + cholmod_l_demo \ + cholmod_simple + +cholmod_demo_SOURCES = cholmod_demo.c +cholmod_demo_LDADD = $(top_builddir)/libcholmod.la $(SUITESPARSECONFIG_LIBS) -lgfortran + +cholmod_l_demo_SOURCES = cholmod_l_demo.c +cholmod_l_demo_LDADD = $(top_builddir)/libcholmod.la $(SUITESPARSECONFIG_LIBS) -lgfortran + +cholmod_simple_SOURCES = cholmod_simple.c +cholmod_simple_LDADD = $(top_builddir)/libcholmod.la -lgfortran + +check-local: $(check_PROGRAMS) $(dist_noinst_DATA) + ./cholmod_demo < $(srcdir)/Matrix/bcsstk01.tri + ./cholmod_l_demo < $(srcdir)/Matrix/bcsstk01.tri + ./cholmod_demo < $(srcdir)/Matrix/lp_afiro.tri + ./cholmod_l_demo < $(srcdir)/Matrix/lp_afiro.tri + ./cholmod_demo < $(srcdir)/Matrix/can___24.mtx + ./cholmod_l_demo < $(srcdir)/Matrix/can___24.mtx + ./cholmod_demo < $(srcdir)/Matrix/c.tri + ./cholmod_l_demo < $(srcdir)/Matrix/c.tri + ./cholmod_simple < $(srcdir)/Matrix/c.tri + ./cholmod_simple < $(srcdir)/Matrix/can___24.mtx + ./cholmod_simple < $(srcdir)/Matrix/bcsstk01.tri + +endif +endif +endif + +CLEANFILES = timelog.m diff --git a/Doc/Makefile.am b/Doc/Makefile.am new file mode 100644 --- /dev/null +++ b/Doc/Makefile.am @@ -0,0 +1,437 @@ +EXTRA_DIST = \ + ChangeLog + +dist_noinst_DATA = \ + UserGuide.bib \ + UserGuide.tex \ + header.tex \ + footer.tex \ + mheader.tex \ + mfooter.tex \ + mfile.awk \ + rule.awk + +dist_pdf_DATA = \ + UserGuide.pdf + +dist_noinst_SCRIPTS = \ + getmproto \ + getproto + +# ./getmproto file.m > _file_m.tex +define getmproto = +( \ +cat $(srcdir)/mheader.tex; \ +expand -8 $< | awk -f $(srcdir)/mfile.awk; \ +cat $(srcdir)/mfooter.tex; \ +) > $@ +endef + +# ./getproto 'proto' header.h > _file.tex +define getproto = +( \ +echo -n $(PATTERN); \ +cat $(srcdir)/rule.awk; \ +) > $(basename $@).awk +( \ +cat $(srcdir)/header.tex; \ +expand -8 $< | awk -f $(basename $@).awk; \ +cat $(srcdir)/footer.tex; \ +) > $@ +$(RM) $(basename $@).awk +endef + +PROTO_M = \ + _analyze_m.tex \ + _bisect_m.tex \ + _chol2_m.tex \ + _cholmod2_m.tex \ + _cholmod_demo_m.tex \ + _cholmod_make_m.tex \ + _etree2_m.tex \ + _graph_demo_m.tex \ + _lchol_m.tex \ + _ldl_normest_m.tex \ + _ldlchol_m.tex \ + _ldlsolve_m.tex \ + _ldlsplit_m.tex \ + _ldlupdate_m.tex \ + _ldlrowmod_m.tex \ + _metis_m.tex \ + _mread_m.tex \ + _mwrite_m.tex \ + _nesdis_m.tex \ + _resymbol_m.tex \ + _sdmult_m.tex \ + _sparse2_m.tex \ + _spsym_m.tex \ + _symbfact2_m.tex + +$(PROTO_M): mheader.tex mfile.awk mfooter.tex +_%_m.tex: $(top_srcdir)/MATLAB/%.m + $(getmproto) + +PROTO_SIMPLE = \ + _simple.tex + +_simple.tex: PATTERN = '/include/, /^}/' + +$(PROTO_SIMPLE): $(top_srcdir)/Demo/cholmod_simple.c header.tex rule.awk footer.tex + $(getproto) + +PROTO_CORE = \ + _common.tex \ + _start.tex \ + _finish.tex \ + _defaults.tex \ + _maxrank.tex \ + _allocate_work.tex \ + _free_work.tex \ + _clear_flag.tex \ + _error.tex \ + _dbound.tex \ + _hypot.tex \ + _divcomplex.tex \ + _sparse.tex \ + _allocate_sparse.tex \ + _free_sparse.tex \ + _reallocate_sparse.tex \ + _nnz.tex \ + _speye.tex \ + _spzeros.tex \ + _transpose.tex \ + _transpose_unsym.tex \ + _transpose_sym.tex \ + _ptranspose.tex \ + _sort.tex \ + _band.tex \ + _band_inplace.tex \ + _aat.tex \ + _copy_sparse.tex \ + _copy.tex \ + _add.tex \ + _sparse_xtype.tex \ + _factor.tex \ + _allocate_factor.tex \ + _free_factor.tex \ + _reallocate_factor.tex \ + _change_factor.tex \ + _pack_factor.tex \ + _reallocate_column.tex \ + _factor_to_sparse.tex \ + _copy_factor.tex \ + _factor_xtype.tex \ + _dense.tex \ + _allocate_dense.tex \ + _ensure_dense.tex \ + _zeros.tex \ + _ones.tex \ + _eye.tex \ + _free_dense.tex \ + _sparse_to_dense.tex \ + _dense_to_sparse.tex \ + _copy_dense.tex \ + _copy_dense2.tex \ + _dense_xtype.tex \ + _triplet.tex \ + _allocate_triplet.tex \ + _free_triplet.tex \ + _reallocate_triplet.tex \ + _sparse_to_triplet.tex \ + _triplet_to_sparse.tex \ + _copy_triplet.tex \ + _triplet_xtype.tex \ + _malloc.tex \ + _calloc.tex \ + _free.tex \ + _realloc.tex \ + _realloc_multiple.tex \ + _version.tex \ + _defn.tex + +_common.tex: PATTERN = '/typedef struct cholmod_common/, /^}/' +_start.tex: PATTERN = '/int cholmod_start/, /\*\) ;/' +_finish.tex: PATTERN = '/int cholmod_finish/, /\*\) ;/' +_defaults.tex: PATTERN = '/int cholmod_defaults/, /\*\) ;/' +_maxrank.tex: PATTERN = '/size_t cholmod_maxrank/, /\*\) ;/' +_allocate_work.tex: PATTERN = '/int cholmod_allocate_work/, /\*\) ;/' +_free_work.tex: PATTERN = '/int cholmod_free_work/, /\*\) ;/' +_clear_flag.tex: PATTERN = '/long cholmod_clear_flag/, /\*\) ;/' +_error.tex: PATTERN = '/int cholmod_error/, /\*\) ;/' +_dbound.tex: PATTERN = '/double cholmod_dbound/, /\*\) ;/' +_hypot.tex: PATTERN = '/double cholmod_hypot/, /double\) ;/' +_divcomplex.tex: PATTERN = '/int cholmod_divcomplex/, /\*\) ;/' +_sparse.tex: PATTERN = '/typedef struct cholmod_sparse/, /^}/' +_allocate_sparse.tex: PATTERN = '/cholmod_sparse \*cholmod_allocate_sparse/, /\*\) ;/' +_free_sparse.tex: PATTERN = '/int cholmod_free_sparse/, /\*\) ;/' +_reallocate_sparse.tex: PATTERN = '/int cholmod_reallocate_sparse/, /\*\) ;/' +_nnz.tex: PATTERN = '/long cholmod_nnz/, /\*\) ;/' +_speye.tex: PATTERN = '/cholmod_sparse \*cholmod_speye/, /\*\) ;/' +_spzeros.tex: PATTERN = '/cholmod_sparse \*cholmod_spzeros/, /\*\) ;/' +_transpose.tex: PATTERN = '/cholmod_sparse \*cholmod_transpose/, /\*\) ;/' +_transpose_unsym.tex: PATTERN = '/int cholmod_transpose_unsym/, /\*\) ;/' +_transpose_sym.tex: PATTERN = '/int cholmod_transpose_sym/, /\*\) ;/' +_ptranspose.tex: PATTERN = '/cholmod_sparse \*cholmod_ptranspose/, /\*\) ;/' +_sort.tex: PATTERN = '/int cholmod_sort/, /\*\) ;/' +_band.tex: PATTERN = '/cholmod_sparse \*cholmod_band/, /\*\) ;/' +_band_inplace.tex: PATTERN = '/int cholmod_band_inplace/, /\*\) ;/' +_aat.tex: PATTERN = '/cholmod_sparse \*cholmod_aat/, /\*\) ;/' +_copy_sparse.tex: PATTERN = '/cholmod_sparse \*cholmod_copy_sparse/, /\*\) ;/' +_copy.tex: PATTERN = '/cholmod_sparse \*cholmod_copy /, /\*\) ;/' +_add.tex: PATTERN = '/cholmod_sparse \*cholmod_add/, /\*\) ;/' +_sparse_xtype.tex: PATTERN = '/int cholmod_sparse_xtype/, /\*\) ;/' +_factor.tex: PATTERN = '/typedef struct cholmod_factor/, /^}/' +_allocate_factor.tex: PATTERN = '/cholmod_factor \*cholmod_allocate_factor/, /\*\) ;/' +_free_factor.tex: PATTERN = '/int cholmod_free_factor/, /\*\) ;/' +_reallocate_factor.tex: PATTERN = '/int cholmod_reallocate_factor/, /\*\) ;/' +_change_factor.tex: PATTERN = '/int cholmod_change_factor/, /\*\) ;/' +_pack_factor.tex: PATTERN = '/int cholmod_pack_factor/, /\*\) ;/' +_reallocate_column.tex: PATTERN = '/int cholmod_reallocate_column/, /\*\) ;/' +_factor_to_sparse.tex: PATTERN = '/cholmod_sparse \*cholmod_factor_to_sparse/, /\*\) ;/' +_copy_factor.tex: PATTERN = '/cholmod_factor \*cholmod_copy_factor/, /\*\) ;/' +_factor_xtype.tex: PATTERN = '/int cholmod_factor_xtype/, /\*\) ;/' +_dense.tex: PATTERN = '/typedef struct cholmod_dense/, /^}/' +_allocate_dense.tex: PATTERN = '/cholmod_dense \*cholmod_allocate_dense/, /\*\) ;/' +_ensure_dense.tex: PATTERN = '/cholmod_dense \*cholmod_ensure_dense/, /\*\) ;/' +_zeros.tex: PATTERN = '/cholmod_dense \*cholmod_zeros/, /\*\) ;/' +_ones.tex: PATTERN = '/cholmod_dense \*cholmod_ones/, /\*\) ;/' +_eye.tex: PATTERN = '/cholmod_dense \*cholmod_eye/, /\*\) ;/' +_free_dense.tex: PATTERN = '/int cholmod_free_dense/, /\*\) ;/' +_sparse_to_dense.tex: PATTERN = '/cholmod_dense \*cholmod_sparse_to_dense/, /\*\) ;/' +_dense_to_sparse.tex: PATTERN = '/cholmod_sparse \*cholmod_dense_to_sparse/, /\*\) ;/' +_copy_dense.tex: PATTERN = '/cholmod_dense \*cholmod_copy_dense/, /\*\) ;/' +_copy_dense2.tex: PATTERN = '/int cholmod_copy_dense2/, /\*\) ;/' +_dense_xtype.tex: PATTERN = '/int cholmod_dense_xtype/, /\*\) ;/' +_triplet.tex: PATTERN = '/typedef struct cholmod_triplet/, /^}/' +_allocate_triplet.tex: PATTERN = '/cholmod_triplet \*cholmod_allocate_triplet/, /\*\) ;/' +_free_triplet.tex: PATTERN = '/int cholmod_free_triplet/, /\*\) ;/' +_reallocate_triplet.tex: PATTERN = '/int cholmod_reallocate_triplet/, /\*\) ;/' +_sparse_to_triplet.tex: PATTERN = '/cholmod_triplet \*cholmod_sparse_to_triplet/, /\*\) ;/' +_triplet_to_sparse.tex: PATTERN = '/cholmod_sparse \*cholmod_triplet_to_sparse/, /\*\) ;/' +_copy_triplet.tex: PATTERN = '/cholmod_triplet \*cholmod_copy_triplet/, /\*\) ;/' +_triplet_xtype.tex: PATTERN = '/int cholmod_triplet_xtype/, /\*\) ;/' +_malloc.tex: PATTERN = '/void \*cholmod_malloc/, /\*\) ;/' +_calloc.tex: PATTERN = '/void \*cholmod_calloc/, /\*\) ;/' +_free.tex: PATTERN = '/void \*cholmod_free/, /\*\) ;/' +_realloc.tex: PATTERN = '/void \*cholmod_realloc/, /\*\) ;/' +_realloc_multiple.tex: PATTERN = '/int cholmod_realloc_multiple/, /\*\) ;/' +_version.tex: PATTERN = '/int cholmod_version/, /l_version/' +_defn.tex: PATTERN = '/itype defines the/, /define CHOLMOD_SUPERNODAL/' + +$(PROTO_CORE): $(top_srcdir)/Include/cholmod_core.h header.tex rule.awk footer.tex + $(getproto) + +PROTO_CHECK = \ + _check_common.tex \ + _print_common.tex \ + _check_sparse.tex \ + _print_sparse.tex \ + _check_dense.tex \ + _print_dense.tex \ + _check_factor.tex \ + _print_factor.tex \ + _check_triplet.tex \ + _print_triplet.tex \ + _check_subset.tex \ + _print_subset.tex \ + _check_perm.tex \ + _print_perm.tex \ + _check_parent.tex \ + _print_parent.tex \ + _read_triplet.tex \ + _read_sparse.tex \ + _read_dense.tex \ + _read_matrix.tex \ + _write_sparse.tex \ + _write_dense.tex + +_check_common.tex: PATTERN = '/int cholmod_check_common/, /\*\) ;/' +_print_common.tex: PATTERN = '/int cholmod_print_common/, /\*\) ;/' +_check_sparse.tex: PATTERN = '/int cholmod_check_sparse/, /\*\) ;/' +_print_sparse.tex: PATTERN = '/int cholmod_print_sparse/, /\*\) ;/' +_check_dense.tex: PATTERN = '/int cholmod_check_dense/, /\*\) ;/' +_print_dense.tex: PATTERN = '/int cholmod_print_dense/, /\*\) ;/' +_check_factor.tex: PATTERN = '/int cholmod_check_factor/, /\*\) ;/' +_print_factor.tex: PATTERN = '/int cholmod_print_factor/, /\*\) ;/' +_check_triplet.tex: PATTERN = '/int cholmod_check_triplet/, /\*\) ;/' +_print_triplet.tex: PATTERN = '/int cholmod_print_triplet/, /\*\) ;/' +_check_subset.tex: PATTERN = '/int cholmod_check_subset/, /\*\) ;/' +_print_subset.tex: PATTERN = '/int cholmod_print_subset/, /\*\) ;/' +_check_perm.tex: PATTERN = '/int cholmod_check_perm/, /\*\) ;/' +_print_perm.tex: PATTERN = '/int cholmod_print_perm/, /\*\) ;/' +_check_parent.tex: PATTERN = '/int cholmod_check_parent/, /\*\) ;/' +_print_parent.tex: PATTERN = '/int cholmod_print_parent/, /\*\) ;/' +_read_triplet.tex: PATTERN = '/cholmod_triplet \*cholmod_read_triplet/, /\*\) ;/' +_read_sparse.tex: PATTERN = '/cholmod_sparse \*cholmod_read_sparse/, /\*\) ;/' +_read_dense.tex: PATTERN = '/cholmod_dense \*cholmod_read_dense/, /\*\) ;/' +_read_matrix.tex: PATTERN = '/void \*cholmod_read_matrix/, /\*\) ;/' +_write_sparse.tex: PATTERN = '/int cholmod_write_sparse/, /\*\) ;/' +_write_dense.tex: PATTERN = '/int cholmod_write_dense/, /\*\) ;/' + +$(PROTO_CHECK): $(top_srcdir)/Include/cholmod_check.h header.tex rule.awk footer.tex + $(getproto) + +PROTO_CHOLESKY = \ + _analyze.tex \ + _analyze_p.tex \ + _factorize.tex \ + _factorize_p.tex \ + _solve.tex \ + _solve2.tex \ + _spsolve.tex \ + _etree.tex \ + _rowcolcounts.tex \ + _analyze_ordering.tex \ + _amd.tex \ + _colamd.tex \ + _rowfac.tex \ + _rowfac_mask.tex \ + _row_subtree.tex \ + _row_lsubtree.tex \ + _lsolve_pattern.tex \ + _resymbol.tex \ + _resymbol_noperm.tex \ + _rcond.tex \ + _postorder.tex + +_analyze.tex: PATTERN = '/cholmod_factor \*cholmod_analyze /, /\*\) ;/' +_analyze_p.tex: PATTERN = '/cholmod_factor \*cholmod_analyze_p/, /\*\) ;/' +_factorize.tex: PATTERN = '/int cholmod_factorize /, /\*\) ;/' +_factorize_p.tex: PATTERN = '/int cholmod_factorize_p/, /\*\) ;/' +_solve.tex: PATTERN = '/cholmod_dense \*cholmod_solve/, /\*\) ;/' +_solve2.tex: PATTERN = '/int cholmod_solve2/, /\*\) ;/' +_spsolve.tex: PATTERN = '/cholmod_sparse \*cholmod_spsolve/, /\*\) ;/' +_etree.tex: PATTERN = '/int cholmod_etree/, /\*\) ;/' +_rowcolcounts.tex: PATTERN = '/int cholmod_rowcolcounts/, /\*\) ;/' +_analyze_ordering.tex: PATTERN = '/int cholmod_analyze_ordering/, /\*\) ;/' +_amd.tex: PATTERN = '/int cholmod_amd/, /\*\) ;/' +_colamd.tex: PATTERN = '/int cholmod_colamd/, /\*\) ;/' +_rowfac.tex: PATTERN = '/int cholmod_rowfac/, /\*\) ;/' +_rowfac_mask.tex: PATTERN = '/int cholmod_rowfac_mask/, /\*\) ;/' +_row_subtree.tex: PATTERN = '/int cholmod_row_subtree/, /\*\) ;/' +_row_lsubtree.tex: PATTERN = '/int cholmod_row_lsubtree/, /\*\) ;/' +_lsolve_pattern.tex: PATTERN = '/int cholmod_lsolve_pattern/, /\*\) ;/' +_resymbol.tex: PATTERN = '/int cholmod_resymbol /, /\*\) ;/' +_resymbol_noperm.tex: PATTERN = '/int cholmod_resymbol_noperm/, /\*\) ;/' +_rcond.tex: PATTERN = '/double cholmod_rcond/, /\*\) ;/' +_postorder.tex: PATTERN = '/long cholmod_postorder/, /\*\) ;/' + +$(PROTO_CHOLESKY): $(top_srcdir)/Include/cholmod_cholesky.h header.tex rule.awk footer.tex + $(getproto) + +PROTO_MODIFY = \ + _updown.tex \ + _updown_solve.tex \ + _updown_mark.tex \ + _updown_mask.tex \ + _rowadd.tex \ + _rowadd_solve.tex \ + _rowadd_mark.tex \ + _rowdel.tex \ + _rowdel_solve.tex \ + _rowdel_mark.tex + +_updown.tex: PATTERN = '/int cholmod_updown /, /\*\) ;/' +_updown_solve.tex: PATTERN = '/int cholmod_updown_solve/, /\*\) ;/' +_updown_mark.tex: PATTERN = '/int cholmod_updown_mark/, /\*\) ;/' +_updown_mask.tex: PATTERN = '/int cholmod_updown_mask/, /\*\) ;/' +_rowadd.tex: PATTERN = '/int cholmod_rowadd /, /\*\) ;/' +_rowadd_solve.tex: PATTERN = '/int cholmod_rowadd_solve/, /\*\) ;/' +_rowadd_mark.tex: PATTERN = '/int cholmod_rowadd_mark/, /\*\) ;/' +_rowdel.tex: PATTERN = '/int cholmod_rowdel /, /\*\) ;/' +_rowdel_solve.tex: PATTERN = '/int cholmod_rowdel_solve/, /\*\) ;/' +_rowdel_mark.tex: PATTERN = '/int cholmod_rowdel_mark/, /\*\) ;/' + +$(PROTO_MODIFY): $(top_srcdir)/Include/cholmod_modify.h header.tex rule.awk footer.tex + $(getproto) + +PROTO_MATRIXOPS = \ + _drop.tex \ + _norm_dense.tex \ + _norm_sparse.tex \ + _horzcat.tex \ + _scale.tex \ + _sdmult.tex \ + _ssmult.tex \ + _submatrix.tex \ + _vertcat.tex \ + _symmetry.tex + +_drop.tex: PATTERN = '/int cholmod_drop/, /\*\) ;/' +_norm_dense.tex: PATTERN = '/double cholmod_norm_dense/, /\*\) ;/' +_norm_sparse.tex: PATTERN = '/double cholmod_norm_sparse/, /\*\) ;/' +_horzcat.tex: PATTERN = '/cholmod_sparse \*cholmod_horzcat/, /\*\) ;/' +_scale.tex: PATTERN = '/define CHOLMOD_SCALAR/, /\*\) ;/' +_sdmult.tex: PATTERN = '/int cholmod_sdmult/, /\*\) ;/' +_ssmult.tex: PATTERN = '/cholmod_sparse \*cholmod_ssmult/, /\*\) ;/' +_submatrix.tex: PATTERN = '/cholmod_sparse \*cholmod_submatrix/, /\*\) ;/' +_vertcat.tex: PATTERN = '/cholmod_sparse \*cholmod_vertcat/, /\*\) ;/' +_symmetry.tex: PATTERN = '/int cholmod_symmetry/, /\*\) ;/' + +$(PROTO_MATRIXOPS): $(top_srcdir)/Include/cholmod_matrixops.h header.tex rule.awk footer.tex + $(getproto) + +PROTO_SUPERNODAL = \ + _super_symbolic.tex \ + _super_numeric.tex \ + _super_lsolve.tex \ + _super_ltsolve.tex + +_super_symbolic.tex: PATTERN = '/int cholmod_super_symbolic/, /\*\) ;/' +_super_numeric.tex: PATTERN = '/int cholmod_super_numeric/, /\*\) ;/' +_super_lsolve.tex: PATTERN = '/int cholmod_super_lsolve/, /\*\) ;/' +_super_ltsolve.tex: PATTERN = '/int cholmod_super_ltsolve/, /\*\) ;/' + +$(PROTO_SUPERNODAL): $(top_srcdir)/Include/cholmod_supernodal.h header.tex rule.awk footer.tex + $(getproto) + +PROTO_PARTITION = \ + _nested_dissection.tex \ + _metis.tex \ + _ccolamd.tex \ + _camd.tex \ + _csymamd.tex \ + _bisect.tex \ + _metis_bisector.tex \ + _collapse_septree.tex + +_nested_dissection.tex: PATTERN = '/long cholmod_nested_dissection/, /\*\) ;/' +_metis.tex: PATTERN = '/int cholmod_metis/, /\*\) ;/' +_ccolamd.tex: PATTERN = '/int cholmod_ccolamd/, /\*\) ;/' +_camd.tex: PATTERN = '/int cholmod_camd/, /\*\) ;/' +_csymamd.tex: PATTERN = '/int cholmod_csymamd/, /\*\) ;/' +_bisect.tex: PATTERN = '/long cholmod_bisect/, /\*\) ;/' +_metis_bisector.tex: PATTERN = '/long cholmod_metis_bisector/, /\*\) ;/' +_collapse_septree.tex: PATTERN = '/long cholmod_collapse_septree/, /\*\) ;/' + +$(PROTO_PARTITION): $(top_srcdir)/Include/cholmod_partition.h header.tex rule.awk footer.tex + $(getproto) + +PROTO = \ + $(PROTO_M) \ + $(PROTO_SIMPLE) \ + $(PROTO_CORE) \ + $(PROTO_CHECK) \ + $(PROTO_CHOLESKY) \ + $(PROTO_MODIFY) \ + $(PROTO_MATRIXOPS) \ + $(PROTO_SUPERNODAL) \ + $(PROTO_PARTITION) + +UserGuide.pdf UserGuide.aux: $(PROTO) +.INTERMEDIATE: UserGuide.aux $(PROTO) + +TEX = TEXINPUTS="$(srcdir):" pdflatex -interaction nonstopmode -file-line-error +BIB = BIBINPUTS="$(srcdir):" bibtex +%.pdf: %.tex %.bbl + $(TEX) $* + while grep -q "Rerun to get cross-references right" $*.log; do \ + $(TEX) $*; \ + done +%.bbl: %.aux %.bib + $(BIB) $* +%.aux: %.tex + $(TEX) $* + +CLEANFILES = _*.awk _*.tex *.dvi *.aux *.log *.lof *.lot *.toc *.bak *.bbl *.blg +MAINTAINERCLEANFILES = $(dist_pdf_DATA) diff --git a/GPU/Makefile.am b/GPU/Makefile.am new file mode 100644 --- /dev/null +++ b/GPU/Makefile.am @@ -0,0 +1,25 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(SUITESPARSECONFIG_CFLAGS) + +GPUSRC = \ + cholmod_gpu.c + +EXTRA_DIST = \ + cholmod_gpu_kernels.c \ + cholmod_gpu_kernels.cu + +noinst_HEADERS = \ + t_cholmod_gpu.c + +noinst_LTLIBRARIES = \ + libgpui.la \ + libgpul.la \ + libgpu.la + +libgpui_la_SOURCES = $(GPUSRC) +libgpui_la_CPPFLAGS = $(AM_CPPFLAGS) + +libgpul_la_SOURCES = $(GPUSRC) +libgpul_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +libgpu_la_SOURCES = +libgpu_la_LIBADD = libgpui.la libgpul.la diff --git a/Include/Makefile.am b/Include/Makefile.am new file mode 100644 --- /dev/null +++ b/Include/Makefile.am @@ -0,0 +1,45 @@ +EXTRA_DIST = \ + License.txt \ + README.txt + +# Automatically generated headers +nodist_pkginclude_HEADERS = \ + cholmod_config.h + +pkginclude_HEADERS = \ + cholmod.h \ + cholmod_blas.h \ + cholmod_core.h \ + cholmod_function.h \ + cholmod_gpu.h \ + cholmod_io64.h + +noinst_HEADERS = \ + cholmod_complexity.h \ + cholmod_gpu_kernels.h \ + cholmod_internal.h \ + cholmod_template.h + +if MOD_CHECK +pkginclude_HEADERS += cholmod_check.h +endif + +if MOD_CHOLESKY +pkginclude_HEADERS += cholmod_cholesky.h +endif + +if MOD_PARTITION +pkginclude_HEADERS += cholmod_camd.h cholmod_partition.h +endif + +if MOD_MATRIXOPS +pkginclude_HEADERS += cholmod_matrixops.h +endif + +if MOD_MODIFY +pkginclude_HEADERS += cholmod_modify.h +endif + +if MOD_SUPERNODAL +pkginclude_HEADERS += cholmod_supernodal.h +endif diff --git a/Include/cholmod_config.h b/Include/cholmod_config.h.in rename from Include/cholmod_config.h rename to Include/cholmod_config.h.in --- a/Include/cholmod_config.h +++ b/Include/cholmod_config.h.in @@ -54,17 +54,31 @@ /* Use the compiler flag, or uncomment the definition(s), if you want to use * one or more non-default installation options: */ -/* -#define NCHECK -#define NCHOLESKY -#define NCAMD -#define NPARTITION +/* Define to disable the Check module */ +#undef NCHECK -#define NGPL -#define NMATRIXOPS -#define NMODIFY -#define NSUPERNODAL +/* Define to disable the Cholesky module */ +#undef NCHOLESKY + +/* Define to disable the Partition module */ +#undef NCAMD + +/* Define to disable metis support in the Partition module */ +#undef NPARTITION +/* Define to disable GPL-licensed modules */ +#undef NGPL + +/* Define to disable the MatrixOps module */ +#undef NMATRIXOPS + +/* Define to disable the Modify module */ +#undef NMODIFY + +/* Define to disable the Supernodal module */ +#undef NSUPERNODAL + +/* #define NPRINT #define LONGBLAS long diff --git a/MATLAB/Makefile.am b/MATLAB/Makefile.am new file mode 100644 --- /dev/null +++ b/MATLAB/Makefile.am @@ -0,0 +1,26 @@ +# Needed by Doc/Makefile.am +EXTRA_DIST = \ + analyze.m \ + bisect.m \ + chol2.m \ + cholmod2.m \ + cholmod_demo.m \ + cholmod_make.m \ + etree2.m \ + graph_demo.m \ + lchol.m \ + ldl_normest.m \ + ldlchol.m \ + ldlsolve.m \ + ldlsplit.m \ + ldlupdate.m \ + ldlrowmod.m \ + metis.m \ + mread.m \ + mwrite.m \ + nesdis.m \ + resymbol.m \ + sdmult.m \ + sparse2.m \ + spsym.m \ + symbfact2.m diff --git a/Makefile.am b/Makefile.am new file mode 100644 --- /dev/null +++ b/Makefile.am @@ -0,0 +1,46 @@ +SUBDIRS = Include Core +EXTRA_DIST = README.txt + +pkgconfigdir = $(libdir)/pkgconfig +pkgconfig_DATA = cholmod.pc + +lib_LTLIBRARIES = libcholmod.la + +libcholmod_la_SOURCES = +libcholmod_la_LIBADD = $(top_builddir)/Core/libcore.la +libcholmod_la_LDFLAGS = -no-undefined -release $(PACKAGE_VERSION) + +if MOD_CHECK +SUBDIRS += Check +libcholmod_la_LIBADD += $(top_builddir)/Check/libcheck.la +endif + +if MOD_CHOLESKY +SUBDIRS += Cholesky +libcholmod_la_LIBADD += $(top_builddir)/Cholesky/libcholesky.la +endif + +if MOD_PARTITION +SUBDIRS += Partition +libcholmod_la_LIBADD += $(top_builddir)/Partition/libpartition.la +endif + +if MOD_MATRIXOPS +SUBDIRS += MatrixOps +libcholmod_la_LIBADD += $(top_builddir)/MatrixOps/libmatrixops.la +endif + +if MOD_MODIFY +SUBDIRS += Modify +libcholmod_la_LIBADD += $(top_builddir)/Modify/libmodify.la +endif + +if MOD_SUPERNODAL +SUBDIRS += Supernodal +libcholmod_la_LIBADD += $(top_builddir)/Supernodal/libsupernodal.la +endif + +#SUBDIRS += GPU +#libcholmod_la_LIBADD += $(top_builddir)/GPU/libgpu.la + +SUBDIRS += MATLAB Demo Doc diff --git a/MatrixOps/Makefile.am b/MatrixOps/Makefile.am new file mode 100644 --- /dev/null +++ b/MatrixOps/Makefile.am @@ -0,0 +1,35 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(SUITESPARSECONFIG_CFLAGS) + +EXTRA_DIST = \ + License.txt \ + gpl.txt + +MATRIXOPSSRC = \ + cholmod_drop.c \ + cholmod_horzcat.c \ + cholmod_norm.c \ + cholmod_scale.c \ + cholmod_sdmult.c \ + cholmod_ssmult.c \ + cholmod_submatrix.c \ + cholmod_symmetry.c \ + cholmod_vertcat.c + +noinst_HEADERS = \ + t_cholmod_sdmult.c + +noinst_LTLIBRARIES = \ + libmatrixopsi.la \ + libmatrixopsl.la \ + libmatrixops.la + +libmatrixopsi_la_SOURCES = $(MATRIXOPSSRC) +libmatrixopsi_la_LIBADD = $(SUITESPARSECONFIG_LIBS) -lm +libmatrixopsi_la_CPPFLAGS = $(AM_CPPFLAGS) + +libmatrixopsl_la_SOURCES = $(MATRIXOPSSRC) +libmatrixopsl_la_LIBADD = $(SUITESPARSECONFIG_LIBS) -lm +libmatrixopsl_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +libmatrixops_la_SOURCES = +libmatrixops_la_LIBADD = libmatrixopsi.la libmatrixopsl.la diff --git a/Modify/Makefile.am b/Modify/Makefile.am new file mode 100644 --- /dev/null +++ b/Modify/Makefile.am @@ -0,0 +1,30 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(SUITESPARSECONFIG_CFLAGS) + +EXTRA_DIST = \ + License.txt \ + gpl.txt + +MODIFYSRC = \ + cholmod_rowadd.c \ + cholmod_rowdel.c \ + cholmod_updown.c + +noinst_HEADERS = \ + t_cholmod_updown.c \ + t_cholmod_updown_numkr.c + +noinst_LTLIBRARIES = \ + libmodifyi.la \ + libmodifyl.la \ + libmodify.la + +libmodifyi_la_SOURCES = $(MODIFYSRC) +libmodifyi_la_LIBADD = $(SUITESPARSECONFIG_LIBS) -lm +libmodifyi_la_CPPFLAGS = $(AM_CPPFLAGS) + +libmodifyl_la_SOURCES = $(MODIFYSRC) +libmodifyl_la_LIBADD = $(SUITESPARSECONFIG_LIBS) -lm +libmodifyl_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +libmodify_la_SOURCES = +libmodify_la_LIBADD = libmodifyi.la libmodifyl.la diff --git a/Partition/Makefile.am b/Partition/Makefile.am new file mode 100644 --- /dev/null +++ b/Partition/Makefile.am @@ -0,0 +1,28 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(METIS_CFLAGS) $(CCOLAMD_CFLAGS) $(CAMD_CFLAGS) $(SUITESPARSECONFIG_CFLAGS) + +EXTRA_DIST = \ + License.txt \ + lesser.txt + +PARTITIONSRC = \ + cholmod_camd.c \ + cholmod_ccolamd.c \ + cholmod_csymamd.c \ + cholmod_metis.c \ + cholmod_nesdis.c + +noinst_LTLIBRARIES = \ + libpartitioni.la \ + libpartitionl.la \ + libpartition.la + +libpartitioni_la_SOURCES = $(PARTITIONSRC) +libpartitioni_la_LIBADD = $(METIS_LIBS) $(CCOLAMD_LIBS) $(CAMD_LIBS) $(SUITESPARSECONFIG_LIBS) -lm +libpartitioni_la_CPPFLAGS = $(AM_CPPFLAGS) + +libpartitionl_la_SOURCES = $(PARTITIONSRC) +libpartitionl_la_LIBADD = $(METIS_LIBS) $(CCOLAMD_LIBS) $(CAMD_LIBS) $(SUITESPARSECONFIG_LIBS) -lm +libpartitionl_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +libpartition_la_SOURCES = +libpartition_la_LIBADD = libpartitioni.la libpartitionl.la diff --git a/Partition/cholmod_camd.c b/Partition/cholmod_camd.c --- a/Partition/cholmod_camd.c +++ b/Partition/cholmod_camd.c @@ -32,6 +32,7 @@ * Supports any xtype (pattern, real, complex, or zomplex) */ +#include "cholmod_config.h" #ifndef NCAMD #include "cholmod_internal.h" diff --git a/Partition/cholmod_ccolamd.c b/Partition/cholmod_ccolamd.c --- a/Partition/cholmod_ccolamd.c +++ b/Partition/cholmod_ccolamd.c @@ -22,6 +22,7 @@ * Supports any xtype (pattern, real, complex, or zomplex). */ +#include "cholmod_config.h" #ifndef NCAMD #include "cholmod_internal.h" diff --git a/Partition/cholmod_csymamd.c b/Partition/cholmod_csymamd.c --- a/Partition/cholmod_csymamd.c +++ b/Partition/cholmod_csymamd.c @@ -21,6 +21,7 @@ * Supports any xtype (pattern, real, complex, or zomplex). */ +#include "cholmod_config.h" #ifndef NCAMD #include "cholmod_internal.h" diff --git a/Partition/cholmod_metis.c b/Partition/cholmod_metis.c --- a/Partition/cholmod_metis.c +++ b/Partition/cholmod_metis.c @@ -43,6 +43,7 @@ * Supports any xtype (pattern, real, complex, or zomplex). */ +#include "cholmod_config.h" #ifndef NPARTITION #include "cholmod_internal.h" diff --git a/Partition/cholmod_nesdis.c b/Partition/cholmod_nesdis.c --- a/Partition/cholmod_nesdis.c +++ b/Partition/cholmod_nesdis.c @@ -38,6 +38,7 @@ * Supports any xtype (pattern, real, complex, or zomplex). */ +#include "cholmod_config.h" #ifndef NPARTITION #include "cholmod_internal.h" diff --git a/Supernodal/Makefile.am b/Supernodal/Makefile.am new file mode 100644 --- /dev/null +++ b/Supernodal/Makefile.am @@ -0,0 +1,35 @@ +AM_CPPFLAGS = -I$(top_srcdir)/Include $(SUITESPARSECONFIG_CFLAGS) + +EXTRA_DIST = \ + License.txt \ + gpl.txt + +SUPERNODALSRC = \ + cholmod_super_numeric.c \ + cholmod_super_solve.c \ + cholmod_super_symbolic.c + +noinst_HEADERS = \ + t_cholmod_super_numeric.c \ + t_cholmod_super_solve.c + +noinst_LTLIBRARIES = \ + libsupernodali.la \ + libsupernodall.la \ + libsupernodal.la + +libsupernodali_la_SOURCES = $(SUPERNODALSRC) +libsupernodali_la_LIBADD = $(LAPACK_LIBS) $(BLAS_LIBS) $(SUITESPARSECONFIG_LIBS) +libsupernodali_la_CPPFLAGS = $(AM_CPPFLAGS) + +libsupernodall_la_SOURCES = $(SUPERNODALSRC) +libsupernodall_la_LIBADD = $(LAPACK_LIBS) $(BLAS_LIBS) $(SUITESPARSECONFIG_LIBS) +libsupernodall_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +if !TIMING +libsupernodali_la_CPPFLAGS += -DNTIMER +libsupernodall_la_CPPFLAGS += -DNTIMER +endif + +libsupernodal_la_SOURCES = +libsupernodal_la_LIBADD = libsupernodali.la libsupernodall.la diff --git a/ax_blas.m4 b/ax_blas.m4 new file mode 100644 --- /dev/null +++ b/ax_blas.m4 @@ -0,0 +1,238 @@ +# =========================================================================== +# http://www.gnu.org/software/autoconf-archive/ax_blas.html +# =========================================================================== +# +# SYNOPSIS +# +# AX_BLAS([ACTION-IF-FOUND[, ACTION-IF-NOT-FOUND]]) +# +# DESCRIPTION +# +# This macro looks for a library that implements the BLAS linear-algebra +# interface (see http://www.netlib.org/blas/). On success, it sets the +# BLAS_LIBS output variable to hold the requisite library linkages. +# +# To link with BLAS, you should link with: +# +# $BLAS_LIBS $LIBS $FLIBS +# +# in that order. FLIBS is the output variable of the +# AC_F77_LIBRARY_LDFLAGS macro (called if necessary by AX_BLAS), and is +# sometimes necessary in order to link with F77 libraries. Users will also +# need to use AC_F77_DUMMY_MAIN (see the autoconf manual), for the same +# reason. +# +# Many libraries are searched for, from ATLAS to CXML to ESSL. The user +# may also use --with-blas= in order to use some specific BLAS +# library . In order to link successfully, however, be aware that you +# will probably need to use the same Fortran compiler (which can be set +# via the F77 env. var.) as was used to compile the BLAS library. +# +# ACTION-IF-FOUND is a list of shell commands to run if a BLAS library is +# found, and ACTION-IF-NOT-FOUND is a list of commands to run it if it is +# not found. If ACTION-IF-FOUND is not specified, the default action will +# define HAVE_BLAS. +# +# LICENSE +# +# Copyright (c) 2008 Steven G. Johnson +# +# This program is free software: you can redistribute it and/or modify it +# under the terms of the GNU General Public License as published by the +# Free Software Foundation, either version 3 of the License, or (at your +# option) any later version. +# +# This program is distributed in the hope that it will be useful, but +# WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General +# Public License for more details. +# +# You should have received a copy of the GNU General Public License along +# with this program. If not, see . +# +# As a special exception, the respective Autoconf Macro's copyright owner +# gives unlimited permission to copy, distribute and modify the configure +# scripts that are the output of Autoconf when processing the Macro. You +# need not follow the terms of the GNU General Public License when using +# or distributing such scripts, even though portions of the text of the +# Macro appear in them. The GNU General Public License (GPL) does govern +# all other use of the material that constitutes the Autoconf Macro. +# +# This special exception to the GPL applies to versions of the Autoconf +# Macro released by the Autoconf Archive. When you make and distribute a +# modified version of the Autoconf Macro, you may extend this special +# exception to the GPL to apply to your modified version as well. + +#serial 14 + +AU_ALIAS([ACX_BLAS], [AX_BLAS]) +AC_DEFUN([AX_BLAS], [ +AC_PREREQ(2.50) +AC_REQUIRE([AC_F77_LIBRARY_LDFLAGS]) +AC_REQUIRE([AC_CANONICAL_HOST]) +ax_blas_ok=no + +AC_ARG_WITH(blas, + [AS_HELP_STRING([--with-blas=], [use BLAS library ])]) +case $with_blas in + yes | "") ;; + no) ax_blas_ok=disable ;; + -* | */* | *.a | *.so | *.so.* | *.o) BLAS_LIBS="$with_blas" ;; + *) BLAS_LIBS="-l$with_blas" ;; +esac + +# Get fortran linker names of BLAS functions to check for. +AC_F77_FUNC(sgemm) +AC_F77_FUNC(dgemm) + +ax_blas_save_LIBS="$LIBS" +LIBS="$LIBS $FLIBS" + +# First, check BLAS_LIBS environment variable +if test $ax_blas_ok = no; then +if test "x$BLAS_LIBS" != x; then + save_LIBS="$LIBS"; LIBS="$BLAS_LIBS $LIBS" + AC_MSG_CHECKING([for $sgemm in $BLAS_LIBS]) + AC_TRY_LINK_FUNC($sgemm, [ax_blas_ok=yes], [BLAS_LIBS=""]) + AC_MSG_RESULT($ax_blas_ok) + LIBS="$save_LIBS" +fi +fi + +# BLAS linked to by default? (happens on some supercomputers) +if test $ax_blas_ok = no; then + save_LIBS="$LIBS"; LIBS="$LIBS" + AC_MSG_CHECKING([if $sgemm is being linked in already]) + AC_TRY_LINK_FUNC($sgemm, [ax_blas_ok=yes]) + AC_MSG_RESULT($ax_blas_ok) + LIBS="$save_LIBS" +fi + +# BLAS in OpenBLAS library? (http://xianyi.github.com/OpenBLAS/) +if test $ax_blas_ok = no; then + AC_CHECK_LIB(openblas, $sgemm, [ax_blas_ok=yes + BLAS_LIBS="-lopenblas"]) +fi + +# BLAS in ATLAS library? (http://math-atlas.sourceforge.net/) +if test $ax_blas_ok = no; then + AC_CHECK_LIB(atlas, ATL_xerbla, + [AC_CHECK_LIB(f77blas, $sgemm, + [AC_CHECK_LIB(cblas, cblas_dgemm, + [ax_blas_ok=yes + BLAS_LIBS="-lcblas -lf77blas -latlas"], + [], [-lf77blas -latlas])], + [], [-latlas])]) +fi + +# BLAS in PhiPACK libraries? (requires generic BLAS lib, too) +if test $ax_blas_ok = no; then + AC_CHECK_LIB(blas, $sgemm, + [AC_CHECK_LIB(dgemm, $dgemm, + [AC_CHECK_LIB(sgemm, $sgemm, + [ax_blas_ok=yes; BLAS_LIBS="-lsgemm -ldgemm -lblas"], + [], [-lblas])], + [], [-lblas])]) +fi + +# BLAS in Intel MKL library? +if test $ax_blas_ok = no; then + # MKL for gfortran + if test x"$ac_cv_fc_compiler_gnu" = xyes; then + # 64 bit + if test $host_cpu = x86_64; then + AC_CHECK_LIB(mkl_gf_lp64, $sgemm, + [ax_blas_ok=yes;BLAS_LIBS="-lmkl_gf_lp64 -lmkl_sequential -lmkl_core -lpthread"],, + [-lmkl_gf_lp64 -lmkl_sequential -lmkl_core -lpthread]) + # 32 bit + elif test $host_cpu = i686; then + AC_CHECK_LIB(mkl_gf, $sgemm, + [ax_blas_ok=yes;BLAS_LIBS="-lmkl_gf -lmkl_sequential -lmkl_core -lpthread"],, + [-lmkl_gf -lmkl_sequential -lmkl_core -lpthread]) + fi + # MKL for other compilers (Intel, PGI, ...?) + else + # 64-bit + if test $host_cpu = x86_64; then + AC_CHECK_LIB(mkl_intel_lp64, $sgemm, + [ax_blas_ok=yes;BLAS_LIBS="-lmkl_intel_lp64 -lmkl_sequential -lmkl_core -lpthread"],, + [-lmkl_intel_lp64 -lmkl_sequential -lmkl_core -lpthread]) + # 32-bit + elif test $host_cpu = i686; then + AC_CHECK_LIB(mkl_intel, $sgemm, + [ax_blas_ok=yes;BLAS_LIBS="-lmkl_intel -lmkl_sequential -lmkl_core -lpthread"],, + [-lmkl_intel -lmkl_sequential -lmkl_core -lpthread]) + fi + fi +fi +# Old versions of MKL +if test $ax_blas_ok = no; then + AC_CHECK_LIB(mkl, $sgemm, [ax_blas_ok=yes;BLAS_LIBS="-lmkl -lguide -lpthread"],,[-lguide -lpthread]) +fi + +# BLAS in Apple vecLib library? +if test $ax_blas_ok = no; then + save_LIBS="$LIBS"; LIBS="-framework vecLib $LIBS" + AC_MSG_CHECKING([for $sgemm in -framework vecLib]) + AC_TRY_LINK_FUNC($sgemm, [ax_blas_ok=yes;BLAS_LIBS="-framework vecLib"]) + AC_MSG_RESULT($ax_blas_ok) + LIBS="$save_LIBS" +fi + +# BLAS in Alpha CXML library? +if test $ax_blas_ok = no; then + AC_CHECK_LIB(cxml, $sgemm, [ax_blas_ok=yes;BLAS_LIBS="-lcxml"]) +fi + +# BLAS in Alpha DXML library? (now called CXML, see above) +if test $ax_blas_ok = no; then + AC_CHECK_LIB(dxml, $sgemm, [ax_blas_ok=yes;BLAS_LIBS="-ldxml"]) +fi + +# BLAS in Sun Performance library? +if test $ax_blas_ok = no; then + if test "x$GCC" != xyes; then # only works with Sun CC + AC_CHECK_LIB(sunmath, acosp, + [AC_CHECK_LIB(sunperf, $sgemm, + [BLAS_LIBS="-xlic_lib=sunperf -lsunmath" + ax_blas_ok=yes],[],[-lsunmath])]) + fi +fi + +# BLAS in SCSL library? (SGI/Cray Scientific Library) +if test $ax_blas_ok = no; then + AC_CHECK_LIB(scs, $sgemm, [ax_blas_ok=yes; BLAS_LIBS="-lscs"]) +fi + +# BLAS in SGIMATH library? +if test $ax_blas_ok = no; then + AC_CHECK_LIB(complib.sgimath, $sgemm, + [ax_blas_ok=yes; BLAS_LIBS="-lcomplib.sgimath"]) +fi + +# BLAS in IBM ESSL library? (requires generic BLAS lib, too) +if test $ax_blas_ok = no; then + AC_CHECK_LIB(blas, $sgemm, + [AC_CHECK_LIB(essl, $sgemm, + [ax_blas_ok=yes; BLAS_LIBS="-lessl -lblas"], + [], [-lblas $FLIBS])]) +fi + +# Generic BLAS library? +if test $ax_blas_ok = no; then + AC_CHECK_LIB(blas, $sgemm, [ax_blas_ok=yes; BLAS_LIBS="-lblas"]) +fi + +AC_SUBST(BLAS_LIBS) + +LIBS="$ax_blas_save_LIBS" + +# Finally, execute ACTION-IF-FOUND/ACTION-IF-NOT-FOUND: +if test x"$ax_blas_ok" = xyes; then + ifelse([$1],,AC_DEFINE(HAVE_BLAS,1,[Define if you have a BLAS library.]),[$1]) + : +else + ax_blas_ok=no + $2 +fi +])dnl AX_BLAS diff --git a/ax_lapack.m4 b/ax_lapack.m4 new file mode 100644 --- /dev/null +++ b/ax_lapack.m4 @@ -0,0 +1,131 @@ +# =========================================================================== +# http://www.gnu.org/software/autoconf-archive/ax_lapack.html +# =========================================================================== +# +# SYNOPSIS +# +# AX_LAPACK([ACTION-IF-FOUND[, ACTION-IF-NOT-FOUND]]) +# +# DESCRIPTION +# +# This macro looks for a library that implements the LAPACK linear-algebra +# interface (see http://www.netlib.org/lapack/). On success, it sets the +# LAPACK_LIBS output variable to hold the requisite library linkages. +# +# To link with LAPACK, you should link with: +# +# $LAPACK_LIBS $BLAS_LIBS $LIBS $FLIBS +# +# in that order. BLAS_LIBS is the output variable of the AX_BLAS macro, +# called automatically. FLIBS is the output variable of the +# AC_F77_LIBRARY_LDFLAGS macro (called if necessary by AX_BLAS), and is +# sometimes necessary in order to link with F77 libraries. Users will also +# need to use AC_F77_DUMMY_MAIN (see the autoconf manual), for the same +# reason. +# +# The user may also use --with-lapack= in order to use some specific +# LAPACK library . In order to link successfully, however, be aware +# that you will probably need to use the same Fortran compiler (which can +# be set via the F77 env. var.) as was used to compile the LAPACK and BLAS +# libraries. +# +# ACTION-IF-FOUND is a list of shell commands to run if a LAPACK library +# is found, and ACTION-IF-NOT-FOUND is a list of commands to run it if it +# is not found. If ACTION-IF-FOUND is not specified, the default action +# will define HAVE_LAPACK. +# +# LICENSE +# +# Copyright (c) 2009 Steven G. Johnson +# +# This program is free software: you can redistribute it and/or modify it +# under the terms of the GNU General Public License as published by the +# Free Software Foundation, either version 3 of the License, or (at your +# option) any later version. +# +# This program is distributed in the hope that it will be useful, but +# WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General +# Public License for more details. +# +# You should have received a copy of the GNU General Public License along +# with this program. If not, see . +# +# As a special exception, the respective Autoconf Macro's copyright owner +# gives unlimited permission to copy, distribute and modify the configure +# scripts that are the output of Autoconf when processing the Macro. You +# need not follow the terms of the GNU General Public License when using +# or distributing such scripts, even though portions of the text of the +# Macro appear in them. The GNU General Public License (GPL) does govern +# all other use of the material that constitutes the Autoconf Macro. +# +# This special exception to the GPL applies to versions of the Autoconf +# Macro released by the Autoconf Archive. When you make and distribute a +# modified version of the Autoconf Macro, you may extend this special +# exception to the GPL to apply to your modified version as well. + +#serial 7 + +AU_ALIAS([ACX_LAPACK], [AX_LAPACK]) +AC_DEFUN([AX_LAPACK], [ +AC_REQUIRE([AX_BLAS]) +ax_lapack_ok=no + +AC_ARG_WITH(lapack, + [AS_HELP_STRING([--with-lapack=], [use LAPACK library ])]) +case $with_lapack in + yes | "") ;; + no) ax_lapack_ok=disable ;; + -* | */* | *.a | *.so | *.so.* | *.o) LAPACK_LIBS="$with_lapack" ;; + *) LAPACK_LIBS="-l$with_lapack" ;; +esac + +# Get fortran linker name of LAPACK function to check for. +AC_F77_FUNC(cheev) + +# We cannot use LAPACK if BLAS is not found +if test "x$ax_blas_ok" != xyes; then + ax_lapack_ok=noblas + LAPACK_LIBS="" +fi + +# First, check LAPACK_LIBS environment variable +if test "x$LAPACK_LIBS" != x; then + save_LIBS="$LIBS"; LIBS="$LAPACK_LIBS $BLAS_LIBS $LIBS $FLIBS" + AC_MSG_CHECKING([for $cheev in $LAPACK_LIBS]) + AC_TRY_LINK_FUNC($cheev, [ax_lapack_ok=yes], [LAPACK_LIBS=""]) + AC_MSG_RESULT($ax_lapack_ok) + LIBS="$save_LIBS" + if test $ax_lapack_ok = no; then + LAPACK_LIBS="" + fi +fi + +# LAPACK linked to by default? (is sometimes included in BLAS lib) +if test $ax_lapack_ok = no; then + save_LIBS="$LIBS"; LIBS="$LIBS $BLAS_LIBS $FLIBS" + AC_CHECK_FUNC($cheev, [ax_lapack_ok=yes]) + LIBS="$save_LIBS" +fi + +# Generic LAPACK library? +for lapack in lapack lapack_rs6k; do + if test $ax_lapack_ok = no; then + save_LIBS="$LIBS"; LIBS="$BLAS_LIBS $LIBS" + AC_CHECK_LIB($lapack, $cheev, + [ax_lapack_ok=yes; LAPACK_LIBS="-l$lapack"], [], [$FLIBS]) + LIBS="$save_LIBS" + fi +done + +AC_SUBST(LAPACK_LIBS) + +# Finally, execute ACTION-IF-FOUND/ACTION-IF-NOT-FOUND: +if test x"$ax_lapack_ok" = xyes; then + ifelse([$1],,AC_DEFINE(HAVE_LAPACK,1,[Define if you have LAPACK library.]),[$1]) + : +else + ax_lapack_ok=no + $2 +fi +])dnl AX_LAPACK diff --git a/cholmod.pc.in b/cholmod.pc.in new file mode 100644 --- /dev/null +++ b/cholmod.pc.in @@ -0,0 +1,13 @@ +prefix=@prefix@ +exec_prefix=@exec_prefix@ +libdir=@libdir@ +includedir=@includedir@ + +Name: @PACKAGE_NAME@ +Description: Sparse Cholesky factorization +Version: @PACKAGE_VERSION@ +URL: @PACKAGE_URL@ +Requires.private: @CHOLMOD_REQUIRES@ +Libs: -L${libdir} -lcholmod +Libs.private: @LAPACK_LIBS@ @BLAS_LIBS@ -lm +Cflags: -I${includedir}/cholmod diff --git a/configure.ac b/configure.ac new file mode 100644 --- /dev/null +++ b/configure.ac @@ -0,0 +1,216 @@ +# -*- Autoconf -*- +# Process this file with autoconf to produce a configure script. + +AC_PREREQ([2.69]) +AC_INIT([CHOLMOD],[3.0.6],[DrTimothyAldenDavis at gmail.com],[cholmod],[http://www.suitesparse.com/]) +AC_CONFIG_SRCDIR([Core/cholmod_common.c]) +AC_CONFIG_HEADERS([config.h Include/cholmod_config.h]) +AM_INIT_AUTOMAKE([foreign]) +LT_INIT + +# Checks for programs. +AC_PROG_INSTALL +AC_PROG_CC +AC_PROG_F77 +AC_PROG_AWK + +AC_MSG_CHECKING([whether to build GPL-licensed modules]) +AC_ARG_ENABLE([gpl-modules], + [AS_HELP_STRING( + [--disable-gpl-modules], + [do not build GPL-licensed modules])], + [mod_gpl=$enableval], + [mod_gpl="yes"]) +AC_MSG_RESULT([$mod_gpl]) + +AC_MSG_CHECKING([whether to build mod-check]) +AC_ARG_ENABLE([mod-check], + [AS_HELP_STRING( + [--disable-mod-check], + [do not build the Check module])], + [mod_check=$enableval], + [mod_check="yes"]) +AC_MSG_RESULT([$mod_check]) + +AC_MSG_CHECKING([whether to build mod-cholesky]) +AC_ARG_ENABLE([mod-cholesky], + [AS_HELP_STRING( + [--disable-mod-cholesky], + [do not build the Cholesky module])], + [mod_cholesky=$enableval], + [mod_cholesky="yes"]) +AC_MSG_RESULT([$mod_cholesky]) + +AC_MSG_CHECKING([whether to build mod-partition]) +AC_ARG_ENABLE([mod-partition], + [AS_HELP_STRING( + [--disable-mod-partition], + [do not build the Partition module])], + [mod_partition=$enableval], + [mod_partition="yes"]) +AC_MSG_RESULT([$mod_partition]) + +AC_MSG_CHECKING([whether to build mod-matrixops]) +AC_ARG_ENABLE([mod-matrixops], + [AS_HELP_STRING( + [--disable-mod-matrixops], + [do not build the MatrixOps module])], + [mod_matrixops=$enableval], + [mod_matrixops=$mod_gpl]) +AC_MSG_RESULT([$mod_matrixops]) + +AC_MSG_CHECKING([whether to build mod-modify]) +AC_ARG_ENABLE([mod-modify], + [AS_HELP_STRING( + [--disable-mod-modify], + [do not build the Modify module])], + [mod_modify=$enableval], + [mod_modify=$mod_gpl]) +AC_MSG_RESULT([$mod_modify]) + +AC_MSG_CHECKING([whether to build mod-supernodal]) +AC_ARG_ENABLE([mod-supernodal], + [AS_HELP_STRING( + [--disable-mod-supernodal], + [do not build the Supernodal module])], + [mod_supernodal=$enableval], + [mod_supernodal=$mod_gpl]) +AC_MSG_RESULT([$mod_supernodal]) + +AC_MSG_CHECKING([whether to use timing routines]) +AC_ARG_ENABLE([timing], + [AS_HELP_STRING( + [--disable-timing], + [do not use timing routines])], + [timing=$enableval], + [timing="yes"]) +AC_MSG_RESULT([$timing]) + +LIBS_SAVED=$LIBS + +# Checks for libraries. +AC_CHECK_LIB([m], [sqrt]) + +PKG_PROG_PKG_CONFIG +PKG_CHECK_MODULES([SUITESPARSECONFIG],[suitesparseconfig], + [], + [AC_MSG_ERROR([cannot find suitesparseconfig])]) +CHOLMOD_REQUIRES="suitesparseconfig" + +if test "x$mod_cholesky" = "xyes"; then + PKG_CHECK_MODULES([AMD],[amd], + [], + [AC_MSG_ERROR([cannot find amd (required by mod-cholesky)])]) + CHOLMOD_REQUIRES="$CHOLMOD_REQUIRES amd" + + PKG_CHECK_MODULES([COLAMD],[colamd], + [], + [AC_MSG_ERROR([cannot find colamd (required by mod-cholesky)])]) + CHOLMOD_REQUIRES="$CHOLMOD_REQUIRES colamd" +fi + +if test "x$mod_partition" = "xyes"; then + PKG_CHECK_MODULES([CAMD],[camd], + [], + [AC_MSG_ERROR([cannot find camd (required by mod-partition)])]) + CHOLMOD_REQUIRES="$CHOLMOD_REQUIRES camd" + + PKG_CHECK_MODULES([CCOLAMD],[ccolamd], + [], + [AC_MSG_ERROR([cannot find ccolamd (required by mod-partition)])]) + CHOLMOD_REQUIRES="$CHOLMOD_REQUIRES ccolamd" + + PKG_CHECK_MODULES([METIS],[metis], + [metis="yes"], + [metis="no"]) + if test "x$metis" = "xyes"; then + CHOLMOD_REQUIRES="$CHOLMOD_REQUIRES metis" + else + AC_MSG_WARN([cannot find metis (used by mod-partition), disabling some functionality]) + fi +fi + +if test "x$mod_supernodal" = "xyes"; then + sinclude([ax_blas.m4]) + AX_BLAS + if test "x$ax_blas_ok" != "xyes"; then + AC_MSG_ERROR([cannot find blas (required by mod-supernodal)]) + fi + + sinclude([ax_lapack.m4]) + AX_LAPACK + if test "x$ax_lapack_ok" != "xyes"; then + AC_MSG_ERROR([cannot find lapack (required by mod-supernodal)]) + fi +fi + +# Checks for header files. +AC_CHECK_HEADERS([float.h limits.h stddef.h stdlib.h string.h]) + +# Checks for typedefs, structures, and compiler characteristics. +AC_TYPE_SIZE_T + +# Checks for library functions. +AC_FUNC_MALLOC +AC_CHECK_FUNCS([sqrt]) + +LIBS=$LIBS_SAVED + +if test "x$mod_check" != "xyes"; then + AC_DEFINE([NCHECK], [], [Define to disable the Check module]) +fi + +if test "x$mod_cholesky" != "xyes"; then + AC_DEFINE([NCHOLESKY], [], [Define to disable the Cholesky module]) +fi + +if test "x$mod_partition" != "xyes"; then + AC_DEFINE([NCAMD], [], [Define to disable the Partition module]) +fi + +if test "x$metis" != "xyes"; then + AC_DEFINE([NPARTITION], [], [Define to disable metis support in the Partition module]) +fi + +if test "x$mod_gpl" != "xyes"; then + AC_DEFINE([NGPL], [], [Define to disable GPL-licensed modules]) +fi + +if test "x$mod_matrixops" != "xyes"; then + AC_DEFINE([NMATRIXOPS], [], [Define to disable the MatrixOps module]) +fi + +if test "x$mod_modify" != "xyes"; then + AC_DEFINE([NMODIFY], [], [Define to disable the Modify module]) +fi + +if test "x$mod_supernodal" != "xyes"; then + AC_DEFINE([NSUPERNODAL], [], [Define to disable the Supernodal module]) +fi + +AM_CONDITIONAL([MOD_CHECK], [test "x$mod_check" = "xyes"]) +AM_CONDITIONAL([MOD_CHOLESKY], [test "x$mod_cholesky" = "xyes"]) +AM_CONDITIONAL([MOD_PARTITION], [test "x$mod_partition" = "xyes"]) +AM_CONDITIONAL([MOD_MATRIXOPS], [test "x$mod_matrixops" = "xyes"]) +AM_CONDITIONAL([MOD_MODIFY], [test "x$mod_modify" = "xyes"]) +AM_CONDITIONAL([MOD_SUPERNODAL], [test "x$mod_supernodal" = "xyes"]) +AM_CONDITIONAL([TIMING], [test "x$timing" = "xyes"]) + +AC_SUBST([CHOLMOD_REQUIRES]) + +AC_CONFIG_FILES([ + cholmod.pc + Makefile + Check/Makefile + Cholesky/Makefile + Core/Makefile + Demo/Makefile + Doc/Makefile + GPU/Makefile + Include/Makefile + MATLAB/Makefile + MatrixOps/Makefile + Modify/Makefile + Partition/Makefile + Supernodal/Makefile]) +AC_OUTPUT From bch at shroggslodge.freeserve.co.uk Sun Oct 23 08:56:56 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Sun, 23 Oct 2016 09:56:56 +0100 Subject: [Slackbuilds-users] Openshot Message-ID: Good morning everyone Thanks for the responses. Flowblade looks interesting.....it's got a new release out at 1.8; 1.6 on SBo and I wonder if dependencies have changed for that update too - will have a more detailed look. On SBo it makes reference to requiring gnome* dependencies (gnome-python then requiring libgnome etc... and some Corba stuff), yet when I tried a quick build and then ran it - all seemed to work fine other than a lot of MLT service ladspa.nnnn errors. I didn't install gnome-python dependency, but it seems to work ok so I wonder what all that is for. *I don't specifically have KDE or Gnome environment on my machine so wary about deps... on gnome stuff especially. Dont know why! Can any one enlighten as to why the gnome deps are required ... are they really necessary ? re: Cinelerra - i've not looked at that one previously as Openshot (and previously Kdenline before I stopped using kde) has been my goto. @Matteo - yes I can understand why you dont want to go to the trouble with having to update everything....even I can appreciate what a task can unfold :-) Shame though as Openshot (though was buggy at times) was easy to use. Thanks again everyone. Habs On 23 October 2016 at 07:44, Matteo Bernardini wrote: > 2016-10-22 10:07 GMT+02:00 : > > Good morning everyone > > > > Is it likely that we will see a move towards the latest release of > Openshot > > please? > > > > I am asking because I wondered, not withstanding and respecting > maintainers' > > time constraints etc, if one of the issues would be that there has been > some > > fundamental changes to the latest regarding dependencies and so forth. I > am > > probably showing my ignorance, but I had read somewhere that it now > requires > > QT (not GTK). > > > > Has anyone built the new release yet on Slackware and does it work fine ? > > > > Thanks for any insight etc. Peace and best wishes. > > Habs > > (sorry for the previous empty reply, finger slipped!) > > Hi Habs, > > I'have not upgraded to openshot 2.x yet as it has been a beta version > until this august... > but the main reason why I haven't upgraded yet is that the new version > is based on python3 and ATM I'm trying to avoid python3 stuff on my > installations: for this reason I'm also inclined to drop completely > openshot and its two dependencies goocanvas and pygoocanvas. > if someone is interested in maintaining these scripts, please step in. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dn2010 at gmail.com Sun Oct 23 09:15:33 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Sun, 23 Oct 2016 12:15:33 +0300 Subject: [Slackbuilds-users] cholmod build failure In-Reply-To: References: <20161023094643.6988da82@darkstar.example.net> Message-ID: <20161023121533.63c7ff65@darkstar.example.net> On Sun, 23 Oct 2016 10:50:14 +0200 Matteo Bernardini wrote: > I think it's a matter of underlinking: try substituting the > autotoolize.diff patch in the cholmod.SlackBuild directory with the > one attached where I force linking against the gfortran libraries in > the cholmod demo autotools file. It builds fine with the patch, thanks a lot. WBR, Daniil Bratashov. From matteo.bernardini at gmail.com Sun Oct 23 09:24:02 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 23 Oct 2016 11:24:02 +0200 Subject: [Slackbuilds-users] Openshot In-Reply-To: References: Message-ID: 2016-10-23 10:56 GMT+02:00 : > @Matteo - yes I can understand why you dont want to go to the trouble with > having to update everything....even I can appreciate what a task can unfold > :-) Shame though as Openshot (though was buggy at times) was easy to > use. sorry, maybe I hasn't been clear enough: for me, it's not an issue updating all the stuff needed for openshot to run, the problem is that it now it has an hard dependency on python3 and, long story short, ATM I don't want to have it on my installations. Matteo From dn2010 at gmail.com Sun Oct 23 09:32:58 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Sun, 23 Oct 2016 12:32:58 +0300 Subject: [Slackbuilds-users] biber checksum error it texlive Message-ID: <20161023123258.516283be@darkstar.example.net> Seems that there is some sort of checksum error with biber binary tarball in texlive if it's build on x86_64 architecture. Biber, downloaded from CTAN has different checksum. WBR, Daniil Bratashov. From matteo.bernardini at gmail.com Sun Oct 23 09:54:14 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 23 Oct 2016 11:54:14 +0200 Subject: [Slackbuilds-users] biber checksum error it texlive In-Reply-To: <20161023123258.516283be@darkstar.example.net> References: <20161023123258.516283be@darkstar.example.net> Message-ID: 2016-10-23 11:32 GMT+02:00 Daniil Bratashov : > Seems that there is some sort of checksum error with biber binary > tarball in texlive if it's build on x86_64 architecture. Biber, > downloaded from CTAN has different checksum. thanks for reporting this too, it's now fixed in my branch. Matteo From atelszewski at gmail.com Sun Oct 23 10:36:08 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 23 Oct 2016 12:36:08 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> Message-ID: On 23/10/16 01:56, Christoph Willing wrote: > Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) non > obvious cases? Presumably the maintainer. If a maintainer's balance of > REQUIRED/OPTIONAL deps doesn't suit someone else's particular > needs/wants, then the builder will have to change their personal .info > files anyway (or complain to the maintainer). I think the problem of REQUIRED vs OPTIONAL has been solved long time ago. It's the maintainer that decides what is placed in REQUIRED and most probably 99% of us just installs what is there. And most probably 99% of the time what is placed in the REQUIRED is what is ABSOLUTELY necessary to compile the software or to run it (run time dependency). Everything else, i.e. things that could be added later on or are detected during compilation, are OPTIONAL. I'm the supporter of the OPTIONAL field and I actually proposed it sometime ago, but it was rejected too. I think there is too big resistance here for this addition, because naturally it would involve work. And as with everything in the world, there are people for whom OPTIONAL would be a nice addition and those for whom it's just pointless work. -- Best regards, Andrzej Telszewski From slackbuilds at schoepfer.info Sun Oct 23 10:54:05 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 23 Oct 2016 12:54:05 +0200 Subject: [Slackbuilds-users] biber checksum error it texlive In-Reply-To: References: <20161023123258.516283be@darkstar.example.net> Message-ID: <1b08d79c04cf9d46e6740b1f06e366b7@schoepfer.info> On 2016-10-23 11:54, Matteo Bernardini wrote: > 2016-10-23 11:32 GMT+02:00 Daniil Bratashov : >> Seems that there is some sort of checksum error with biber binary >> tarball in texlive if it's build on x86_64 architecture. Biber, >> downloaded from CTAN has different checksum. > > thanks for reporting this too, it's now fixed in my branch. Thanks Matteo. The texlive-netarchive is a moving target, it seems biber was updated there about a month ago. Please let me know if some biber-related things don't work anymore, as the texmf-sourcetarball contains biber-related stuff. Biber is the only binary-package(which is a desaster to build,see explanation here http://www.linuxfromscratch.org/blfs/view/svn/pst/biber.html) to handle for texlive, i'm thinking about including both 32bit&64bit biber-binarie packages in the texmf-sourcetarball to be more safe from texlive-netarchives updates. Johannes From willysr at slackbuilds.org Sun Oct 23 14:23:50 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 23 Oct 2016 21:23:50 +0700 Subject: [Slackbuilds-users] MySQL Workbench 6.3.8 Message-ID: <0f47280e-1c20-3dbb-618e-8c4b431645c7@slackbuilds.org> Hi all, MySQL Workbench 6.3.8 has been released with some changes that needs attention and further testing. According to mysql-connector-c++ 1.1.7 release notes [1], it requires JSON data type, which is now added into mysql-connector-c++-1.1.7, but since MariaDB 10.0.x used in 14.2 doesn't have JSON support yet (it will be included in 10.2.x), i patched the mysql-connector-c++ to disable JSON support and it allows mysql-workbench to built normally. Also since MySQL and MariaDB diverges from time to time, there are features added in MySQL and may not yet available in MariaDB. mysql-workbench has a check for this in the source code, so i had to remove the check manually. So far, i have been able to build the new mysql-workbench in current and in stable (14.2) and found no issue, but since MySQL Workbench has so many features, i may not notice any side effects due to above changes. I have pushed all the changes in mysql-workbench-review branch for testing before it will be merged into master branch in the next public update. [1]: https://dev.mysql.com/doc/relnotes/connector-cpp/en/news-1-1-7.html [2]: https://dev.mysql.com/doc/refman/5.7/en/mysql-real-escape-string-quote.html -- 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 matteo.bernardini at gmail.com Sun Oct 23 15:04:02 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 23 Oct 2016 17:04:02 +0200 Subject: [Slackbuilds-users] biber checksum error it texlive In-Reply-To: <1b08d79c04cf9d46e6740b1f06e366b7@schoepfer.info> References: <20161023123258.516283be@darkstar.example.net> <1b08d79c04cf9d46e6740b1f06e366b7@schoepfer.info> Message-ID: 2016-10-23 12:54 GMT+02:00 Franzen : > Thanks Matteo. The texlive-netarchive is a moving target, it seems biber was > updated there about a month ago. Please let me know if some biber-related > things don't work anymore, as the texmf-sourcetarball contains biber-related > stuff. > Biber is the only binary-package(which is a desaster to build,see > explanation here > http://www.linuxfromscratch.org/blfs/view/svn/pst/biber.html) to handle for > texlive, i'm thinking about including both 32bit&64bit biber-binarie > packages in the texmf-sourcetarball to > be more safe from texlive-netarchives updates. in the meantime I just self-hosted today's biber versions (to avoid breakage). Matteo From fernando.lopezjr at gmail.com Sun Oct 23 16:47:49 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 23 Oct 2016 10:47:49 -0600 Subject: [Slackbuilds-users] blender: needs python to build? Message-ID: Do I really need python to build? I would like to disable python. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From belka at caraus.de Sun Oct 23 20:13:50 2016 From: belka at caraus.de (Eugen Wissner) Date: Sun, 23 Oct 2016 22:13:50 +0200 Subject: [Slackbuilds-users] biber checksum error it texlive In-Reply-To: <1b08d79c04cf9d46e6740b1f06e366b7@schoepfer.info> References: <20161023123258.516283be@darkstar.example.net> <1b08d79c04cf9d46e6740b1f06e366b7@schoepfer.info> Message-ID: <1477253630.1364.1.camel@caraus.de> Just for info. I installed texlive a few days ago and biber didn't work because of biber/biblatex version mismatch. Something like (similar, I don't have the exact error now): Error: Found biblatex control file version 3.4, expected version 3.5. ????????This means that your biber (2.6) and biblatex () versions are incompatible. ????????See compat matrix in biblatex or biber PDF documentation. I had to download biber from http://slackware.schoepfer.info/slackbuild s/texlive/2016/texlive/ So mirror.ctan.org's tarball was updated and the currently available build from slackbuilds.org is broken because of it. Eugene Am Sonntag, den 23.10.2016, 12:54 +0200 schrieb Franzen: > On 2016-10-23 11:54, Matteo Bernardini wrote: > > 2016-10-23 11:32 GMT+02:00 Daniil Bratashov : > > > Seems that there is some sort of checksum error with biber binary > > > tarball in texlive if it's build on x86_64 architecture. Biber, > > > downloaded from CTAN has different checksum. > > > > thanks for reporting this too, it's now fixed in my branch. > > Thanks Matteo. The texlive-netarchive is a moving target, it seems > biber? > was updated there about a month ago. Please let me know if some? > biber-related things don't work anymore, as the texmf-sourcetarball? > contains biber-related stuff. > Biber is the only binary-package(which is a desaster to build,see? > explanation here? > http://www.linuxfromscratch.org/blfs/view/svn/pst/biber.html) to > handle? > for texlive, i'm thinking about including both 32bit&64bit biber- > binarie? > packages in the texmf-sourcetarball to > be more safe from texlive-netarchives updates. > > Johannes > > _______________________________________________ > 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 Sun Oct 23 21:55:19 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 24 Oct 2016 07:55:19 +1000 Subject: [Slackbuilds-users] blender: needs python to build? In-Reply-To: References: Message-ID: <36e76420-1102-e2ff-680c-44ef5b556a13@iinet.net.au> On 24/10/16 02:47, Fernando Lopez wrote: > Do I really need python to build? I would like to disable python. > I guess you mean Blender (not blender). If it is possible, you'll probably lose much functionality. My built package has 2407 file entries (from tar tvf Blender-2.78-... |wc -l) and 989 of these contain "python" (tar tvf Blender-2.78-... |grep python|wc -l). chris From fernando.lopezjr at gmail.com Sun Oct 23 22:33:25 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 23 Oct 2016 16:33:25 -0600 Subject: [Slackbuilds-users] blender: needs python to build? In-Reply-To: <36e76420-1102-e2ff-680c-44ef5b556a13@iinet.net.au> References: <36e76420-1102-e2ff-680c-44ef5b556a13@iinet.net.au> Message-ID: Yes. I meant Blender. that sucks. =( On Sun, Oct 23, 2016 at 3:55 PM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 24/10/16 02:47, Fernando Lopez wrote: > >> Do I really need python to build? I would like to disable python. >> >> I guess you mean Blender (not blender). If it is possible, you'll > probably lose much functionality. My built package has 2407 file entries > (from tar tvf Blender-2.78-... |wc -l) and 989 of these contain "python" > (tar tvf Blender-2.78-... |grep python|wc -l). > > chris > > _______________________________________________ > 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 ryan.q at linux.com Sun Oct 23 22:37:54 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 23 Oct 2016 15:37:54 -0700 Subject: [Slackbuilds-users] blender: needs python to build? In-Reply-To: References: <36e76420-1102-e2ff-680c-44ef5b556a13@iinet.net.au> Message-ID: On Oct 23, 2016 3:33 PM, "Fernando Lopez" wrote: > > Yes. I meant Blender. that sucks. =( You're going to have a severely limited system without Python. -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sun Oct 23 22:37:59 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 24 Oct 2016 00:37:59 +0200 Subject: [Slackbuilds-users] cgit source code tarball download link change Message-ID: <7c0d7dd8-b208-06f2-482c-9357110c124b@gmail.com> Hi, This is me just randomly wasting time. I noticed that cgit SlackBuild points to Ponce's hosted source code tarball: http://ponce.cc/slackware/sources/repo/cgit-1.0.tar.xz but it seems to be possible to download from the upstream: https://git.zx2c4.com/cgit/snapshot/cgit-1.0.tar.xz I checked the MD5 sums and they agree on both places. Cheers. -- Best regards, Andrzej Telszewski From slackbuilds at schoepfer.info Sun Oct 23 23:32:59 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 24 Oct 2016 01:32:59 +0200 Subject: [Slackbuilds-users] biber checksum error it texlive In-Reply-To: <1477253630.1364.1.camel@caraus.de> References: <20161023123258.516283be@darkstar.example.net> <1b08d79c04cf9d46e6740b1f06e366b7@schoepfer.info> <1477253630.1364.1.camel@caraus.de> Message-ID: > So mirror.ctan.org's tarball was updated and the currently available > build from slackbuilds.org is broken because of it. I'll create new texmf-tarballs with biber included and submit a new texlive buildscript tomorrow. Johannes From chris.willing at iinet.net.au Mon Oct 24 07:43:36 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 24 Oct 2016 17:43:36 +1000 Subject: [Slackbuilds-users] Openshot In-Reply-To: References: Message-ID: <834213a5-1010-5b5b-4898-e9f3efa7922b@iinet.net.au> On 23/10/16 16:44, Matteo Bernardini wrote: > 2016-10-22 10:07 GMT+02:00 : >> Good morning everyone >> >> Is it likely that we will see a move towards the latest release of Openshot >> please? >> >> I am asking because I wondered, not withstanding and respecting maintainers' >> time constraints etc, if one of the issues would be that there has been some >> fundamental changes to the latest regarding dependencies and so forth. I am >> probably showing my ignorance, but I had read somewhere that it now requires >> QT (not GTK). >> That's correct. In fact, the final executable is named openshot-qt >> Has anyone built the new release yet on Slackware and does it work fine ? >> Yes I've just built it and it seems to work OK (although just minimal testing so far). > Hi Habs, > > I'have not upgraded to openshot 2.x yet as it has been a beta version > until this august... > but the main reason why I haven't upgraded yet is that the new version > is based on python3 and ATM I'm trying to avoid python3 stuff on my > installations: for this reason I'm also inclined to drop completely > openshot and its two dependencies goocanvas and pygoocanvas. > if someone is interested in maintaining these scripts, please step in. > Hi Matteo, I can take openshot. However goocanvas and pygoocanvas are not used in the new version (which needs several other new SlackBuilds instead) so someone else should take those two. Having built the new openshot, I'm now working through the new SlackBuilds required to build and run it. They should all be available in a day or two (ready for next SlackBuilds repo update). chris From leva at ecentrum.hu Mon Oct 24 09:09:11 2016 From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=) Date: Mon, 24 Oct 2016 11:09:11 +0200 Subject: [Slackbuilds-users] slackbuilds.org submission removal doesn't work Message-ID: <20161024090911.GN6565@serenity.localdomain> Hi! I've removed perl-Test-PerlTidy from the pending list, but the submit interface says that it's there and cannot upload it. Daniel From matteo.bernardini at gmail.com Mon Oct 24 09:18:49 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 24 Oct 2016 11:18:49 +0200 Subject: [Slackbuilds-users] Openshot In-Reply-To: <834213a5-1010-5b5b-4898-e9f3efa7922b@iinet.net.au> References: <834213a5-1010-5b5b-4898-e9f3efa7922b@iinet.net.au> Message-ID: 2016-10-24 9:43 GMT+02:00 Christoph Willing : > I can take openshot. thanks Chris, I'm sure it will be in good hands! > However goocanvas and pygoocanvas are not used in the new version (which > needs several other new SlackBuilds instead) so someone else should take > those two. ok, in the meantime I'll leave them there. Matteo From willysr at slackbuilds.org Mon Oct 24 09:43:45 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 24 Oct 2016 16:43:45 +0700 Subject: [Slackbuilds-users] slackbuilds.org submission removal doesn't work In-Reply-To: <20161024090911.GN6565@serenity.localdomain> References: <20161024090911.GN6565@serenity.localdomain> Message-ID: > I've removed perl-Test-PerlTidy from the pending list, but the submit > interface says that it's there and cannot upload it. It's because it's a dep for ClusterSSH i have removed ClusterSSH as well and now you can resubmit both 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 leva at ecentrum.hu Mon Oct 24 09:46:25 2016 From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=) Date: Mon, 24 Oct 2016 11:46:25 +0200 Subject: [Slackbuilds-users] slackbuilds.org submission removal doesn't work In-Reply-To: References: <20161024090911.GN6565@serenity.localdomain> Message-ID: <20161024094625.GO6565@serenity.localdomain> Willy Sudiarto Raharjo @ 2016-10-24T11:43:45 +0200: > > I've removed perl-Test-PerlTidy from the pending list, but the submit > > interface says that it's there and cannot upload it. > > It's because it's a dep for ClusterSSH > i have removed ClusterSSH as well and now you can resubmit both packages Perhaps it would be a good idea then if the removal site didn't let me remove it in the first place :) Daniel From dn2010 at gmail.com Mon Oct 24 12:46:14 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Mon, 24 Oct 2016 15:46:14 +0300 Subject: [Slackbuilds-users] cholmod build failure In-Reply-To: <20161023121533.63c7ff65@darkstar.example.net> References: <20161023094643.6988da82@darkstar.example.net> <20161023121533.63c7ff65@darkstar.example.net> Message-ID: Seems to be still underlinked, it now breaks the build of umfpack with ld error. WBR, Daniil Bratashov. On Sun, Oct 23, 2016 at 12:15 PM, Daniil Bratashov wrote: > On Sun, 23 Oct 2016 10:50:14 +0200 > Matteo Bernardini wrote: > >> I think it's a matter of underlinking: try substituting the >> autotoolize.diff patch in the cholmod.SlackBuild directory with the >> one attached where I force linking against the gfortran libraries in >> the cholmod demo autotools file. > > It builds fine with the patch, thanks a lot. > > WBR, Daniil Bratashov. From matteo.bernardini at gmail.com Mon Oct 24 13:55:48 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 24 Oct 2016 15:55:48 +0200 Subject: [Slackbuilds-users] cholmod build failure In-Reply-To: References: <20161023094643.6988da82@darkstar.example.net> <20161023121533.63c7ff65@darkstar.example.net> Message-ID: 2016-10-24 14:46 GMT+02:00 Daniil Bratashov : > Seems to be still underlinked, it now breaks the build of umfpack with ld error. I'm not sure is cholmod's fault (I've tried also adding -lgfortran to its pkconfig file). BTW, try changing umfpack's autotoolize.diff like below --- ./autotoolize.diff.orig 2016-10-24 15:08:33.875628932 +0200 +++ ./autotoolize.diff 2016-10-24 15:44:08.417918280 +0200 @@ -463,8 +463,8 @@ +libumf_l_la_CPPFLAGS = $(AM_CPPFLAGS) -DDLONG + +if CHOLMOD -+libumf_i_la_LIBADD = $(CHOLMOD_LIBS) -+libumf_l_la_LIBADD = $(CHOLMOD_LIBS) ++libumf_i_la_LIBADD = $(CHOLMOD_LIBS) -lgfortran ++libumf_l_la_LIBADD = $(CHOLMOD_LIBS) -lgfortran +else +libumf_i_la_CPPFLAGS += -DNCHOLMOD +libumf_l_la_CPPFLAGS += -DNCHOLMOD Matteo P.S. thanks for reporting this too and feel free to report anything else still broken! From slackbuilds at schoepfer.info Mon Oct 24 15:37:40 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 24 Oct 2016 17:37:40 +0200 Subject: [Slackbuilds-users] qemu/spice-gtk and usbredir In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> Message-ID: <580E2AC4.8050508@schoepfer.info> On 23.10.2016 12:36, Andrzej Telszewski wrote: > On 23/10/16 01:56, Christoph Willing wrote: >> Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) non >> obvious cases? Presumably the maintainer. If a maintainer's balance of >> REQUIRED/OPTIONAL deps doesn't suit someone else's particular >> needs/wants, then the builder will have to change their personal .info >> files anyway (or complain to the maintainer). > > I think the problem of REQUIRED vs OPTIONAL has been solved long time ago. > It's the maintainer that decides what is placed in REQUIRED and most > probably 99% of us just installs what is there. > And most probably 99% of the time what is placed in the REQUIRED is what > is ABSOLUTELY necessary to compile the software or to run it (run time > dependency). > > Everything else, i.e. things that could be added later on or are > detected during compilation, are OPTIONAL. > > I'm the supporter of the OPTIONAL field and I actually proposed it > sometime ago, but it was rejected too. > > I think there is too big resistance here for this addition, because > naturally it would involve work. I think maintaining Options in README is about the same work as providing an Options field in the Info-file. Looking at https://slackbuilds.org/repository/14.2/multimedia/ffmpeg/ , it felt much better to see this list in in an OPTIONAL field in, which would also be parsable by tools like sbotools. Without further bothering the qemu-maintainer, whatever package requires qemu compiled with usbredir, then could have something like REQUIRED="qemu:usbredir" in the Info-file. Johannes From dn2010 at gmail.com Mon Oct 24 19:40:57 2016 From: dn2010 at gmail.com (Daniil Bratashov) Date: Mon, 24 Oct 2016 22:40:57 +0300 Subject: [Slackbuilds-users] cholmod build failure In-Reply-To: References: <20161023094643.6988da82@darkstar.example.net> <20161023121533.63c7ff65@darkstar.example.net> Message-ID: <20161024224057.50a039a0@darkstar.example.net> On Mon, 24 Oct 2016 15:55:48 +0200 Matteo Bernardini wrote: > BTW, try changing umfpack's autotoolize.diff like below Seems to fix the problem, thanks. WBR, Daniil Bratashov. From jbernts at broadpark.no Mon Oct 24 20:10:30 2016 From: jbernts at broadpark.no (Jostein Berntsen) Date: Mon, 24 Oct 2016 22:10:30 +0200 Subject: [Slackbuilds-users] fzf fails to build Message-ID: <20161024201030.GA2354@jostein> Building fzf after processing the package with sqg gives this error: # _/tmp/SBo/fzf-0.13.5/src/fzf /tmp/go-build733267827/_/tmp/SBo/fzf-0.13.5/src/fzf/_obj/_go_.o: In function `main.AN36_github_com_junegunn_fzf_src$sizeSpec4e$hash': /tmp/SBo/fzf-0.13.5/src/fzf/main.go:5: undefined reference to `github_com_junegunn_fzf_src.sizeSpec$hash' collect2: error: ld returned 1 exit status Makefile:69: recipe for target 'fzf/fzf-linux_amd64' failed make: *** [fzf/fzf-linux_amd64] Error 2 fzf: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. Jostein From matteo.bernardini at gmail.com Mon Oct 24 20:51:31 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 24 Oct 2016 22:51:31 +0200 Subject: [Slackbuilds-users] fzf fails to build In-Reply-To: <20161024201030.GA2354@jostein> References: <20161024201030.GA2354@jostein> Message-ID: 2016-10-24 22:10 GMT+02:00 Jostein Berntsen : > Building fzf after processing the package with sqg gives this error: > > # _/tmp/SBo/fzf-0.13.5/src/fzf > /tmp/go-build733267827/_/tmp/SBo/fzf-0.13.5/src/fzf/_obj/_go_.o: In function > `main.AN36_github_com_junegunn_fzf_src$sizeSpec4e$hash': > /tmp/SBo/fzf-0.13.5/src/fzf/main.go:5: undefined reference to > `github_com_junegunn_fzf_src.sizeSpec$hash' > collect2: error: ld returned 1 exit status > Makefile:69: recipe for target 'fzf/fzf-linux_amd64' failed > make: *** [fzf/fzf-linux_amd64] Error 2 > > fzf: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. Hi Jostein, google-go-lang installs file in /etc/profile.d that are loaded in your shell at login, so you have to logout and login again after having installed the package to use the correct go interpreter to build stuff (as fzf). Matteo From chris.willing at iinet.net.au Mon Oct 24 21:57:14 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 25 Oct 2016 07:57:14 +1000 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <580E2AC4.8050508@schoepfer.info> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> Message-ID: <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> On 25/10/16 01:37, Franzen wrote: > On 23.10.2016 12:36, Andrzej Telszewski wrote: >> On 23/10/16 01:56, Christoph Willing wrote: >>> Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) non >>> obvious cases? Presumably the maintainer. If a maintainer's balance of >>> REQUIRED/OPTIONAL deps doesn't suit someone else's particular >>> needs/wants, then the builder will have to change their personal .info >>> files anyway (or complain to the maintainer). >> >> I think the problem of REQUIRED vs OPTIONAL has been solved long time >> ago. >> It's the maintainer that decides what is placed in REQUIRED and most >> probably 99% of us just installs what is there. >> And most probably 99% of the time what is placed in the REQUIRED is what >> is ABSOLUTELY necessary to compile the software or to run it (run time >> dependency). >> >> Everything else, i.e. things that could be added later on or are >> detected during compilation, are OPTIONAL. >> >> I'm the supporter of the OPTIONAL field and I actually proposed it >> sometime ago, but it was rejected too. >> >> I think there is too big resistance here for this addition, because >> naturally it would involve work. > > I think maintaining Options in README is about the same work as > providing an Options field in the Info-file. > > Looking at https://slackbuilds.org/repository/14.2/multimedia/ffmpeg/ , > it felt much better to see this list in in an OPTIONAL field in, which > would also be parsable by tools like sbotools. > Because ffmpeg has so many options, it is a good example of the problem to decide which to include. Some people want a mean & lean ffmpeg with minimal options, while others want the lot. Even with a new OPTIONAL field, which options would be included in it that would please everyone? Each builder will probably modify to suit themselves. Of course everyone already has that option - to modify the .info file with any additional fields they want. For ffmpeg I add: ENVOPTS="LAME=yes X264=yes CELT=yes ..." My build tool finds ENVOPTS and exports each of the variables found, triggering the desired options already supplied in the ffmpeg.SlackBuild file. However the maintainer can't know what options I want. They could put all the possible options in a new OPTIONAL field but perhaps I don't want _all_ of them; just some of them. Then I, the builder, would still have to make the changes to suit my own needs/desires, so what has been gained? Anyway, whatever the mechanism is used, its up to the various build tools to actually support it. Maybe one of the public build tools will introduce something of their own just to see if it catches on. chris From atelszewski at gmail.com Mon Oct 24 22:46:52 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 25 Oct 2016 00:46:52 +0200 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> Message-ID: <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> On 24/10/16 23:57, Christoph Willing wrote: > On 25/10/16 01:37, Franzen wrote: >> On 23.10.2016 12:36, Andrzej Telszewski wrote: >>> On 23/10/16 01:56, Christoph Willing wrote: >>>> Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) >>>> non >>>> obvious cases? Presumably the maintainer. If a maintainer's balance of >>>> REQUIRED/OPTIONAL deps doesn't suit someone else's particular >>>> needs/wants, then the builder will have to change their personal .info >>>> files anyway (or complain to the maintainer). >>> >>> I think the problem of REQUIRED vs OPTIONAL has been solved long time >>> ago. >>> It's the maintainer that decides what is placed in REQUIRED and most >>> probably 99% of us just installs what is there. >>> And most probably 99% of the time what is placed in the REQUIRED is what >>> is ABSOLUTELY necessary to compile the software or to run it (run time >>> dependency). >>> >>> Everything else, i.e. things that could be added later on or are >>> detected during compilation, are OPTIONAL. >>> >>> I'm the supporter of the OPTIONAL field and I actually proposed it >>> sometime ago, but it was rejected too. >>> >>> I think there is too big resistance here for this addition, because >>> naturally it would involve work. >> >> I think maintaining Options in README is about the same work as >> providing an Options field in the Info-file. >> >> Looking at https://slackbuilds.org/repository/14.2/multimedia/ffmpeg/ , >> it felt much better to see this list in in an OPTIONAL field in, which >> would also be parsable by tools like sbotools. >> > Because ffmpeg has so many options, it is a good example of the problem > to decide which to include. Some people want a mean & lean ffmpeg with > minimal options, while others want the lot. Even with a new OPTIONAL > field, which options would be included in it that would please everyone? > Each builder will probably modify to suit themselves. > The point is OPTIONAL wouldn't force you to do anything special. It won't change the way you work, if you don't want to. > Of course everyone already has that option - to modify the .info file > with any additional fields they want. For ffmpeg I add: > ENVOPTS="LAME=yes X264=yes CELT=yes ..." > My build tool finds ENVOPTS and exports each of the variables found, > triggering the desired options already supplied in the ffmpeg.SlackBuild > file. > > However the maintainer can't know what options I want. They could put > all the possible options in a new OPTIONAL field but perhaps I don't > want _all_ of them; just some of them. Then I, the builder, would still > have to make the changes to suit my own needs/desires, so what has been > gained? > Most probably what the supporters of OPTIONAL think of, is that this field would contain all the possible software that might be added to broaden the capabilities of the package, but is not absolutely necessary to compile/run the package. Basically, it's all about moving/duplicating the information about optional packages from README to .info. The OPTIONAL filed already exists, it's just in a format that is not possible to parse by machines. I.e. they cannot understand README ;-) > Anyway, whatever the mechanism is used, its up to the various build > tools to actually support it. Maybe one of the public build tools will > introduce something of their own just to see if it catches on. > Exactly, it's for the build tools. They can store externally what optional packages have been chosen and work according to that. > chris > > _______________________________________________ > 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/ > > -- Best regards, Andrzej Telszewski From chris.willing at iinet.net.au Tue Oct 25 01:12:04 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 25 Oct 2016 11:12:04 +1000 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> Message-ID: <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> On 25/10/16 08:46, Andrzej Telszewski wrote: > > Most probably what the supporters of OPTIONAL think of, is that this > field would contain all the possible software that might be added to > broaden the capabilities of the package, but is not absolutely necessary > to compile/run the package. > > Basically, it's all about moving/duplicating the information about > optional packages from README to .info. > > The OPTIONAL filed already exists, it's just in a format that is not > possible to parse by machines. I.e. they cannot understand README ;-) > >> Anyway, whatever the mechanism is used, its up to the various build >> tools to actually support it. Maybe one of the public build tools will >> introduce something of their own just to see if it catches on. >> > > Exactly, it's for the build tools. They can store externally what > optional packages have been chosen and work according to that. > Could you give a small example of how you see that working? It seems like there would be yet another layer of configuration needed (albeit as part of the build tool setup, I guess) to distinguish between all the possible optional packages and those that a user may want to actually use. I'm not trying to be contrary (I mentioned previously that I already use additional .info fields myself); just interested. chris From atelszewski at gmail.com Tue Oct 25 08:41:33 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 25 Oct 2016 10:41:33 +0200 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> Message-ID: <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> On 25/10/16 03:12, Christoph Willing wrote: >> Exactly, it's for the build tools. They can store externally what >> optional packages have been chosen and work according to that. >> > Could you give a small example of how you see that working? It seems > like there would be yet another layer of configuration needed (albeit as > part of the build tool setup, I guess) to distinguish between all the > possible optional packages and those that a user may want to actually use. > > I'm not trying to be contrary (I mentioned previously that I already use > additional .info fields myself); just interested. > > chris It would require a deeper thought, because there are potentially more interesting things to take into account. But my first idea is that, the automated tool would offer you / ask you what optional packages do you want. It would then remember your choice, and could also track any possible changes to the upstream OPTIONAL field, and if there was a change, ask you again. Of course you could just edit some config file to contain all the optional packages, but what we're talking about here is to let the machine assist you in doing so, and tracking for possible misconfiguration (e.g. the tool can detect that you have a package flagged as optional, but upstream has changed .info and removed that package from OPTIONAL field). -- Best regards, Andrzej Telszewski From arnaud.garcia-fernandez at laposte.net Tue Oct 25 08:59:33 2016 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Tue, 25 Oct 2016 10:59:33 +0200 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> Message-ID: <20161025105933.fcf5b7845c42613274f50674@laposte.net> > On 25/10/16 03:12, Christoph Willing wrote: > >> Exactly, it's for the build tools. They can store externally what > >> optional packages have been chosen and work according to that. > >> > > Could you give a small example of how you see that working? It seems > > like there would be yet another layer of configuration needed (albeit as > > part of the build tool setup, I guess) to distinguish between all the > > possible optional packages and those that a user may want to actually use. > > > > I'm not trying to be contrary (I mentioned previously that I already use > > additional .info fields myself); just interested. > > > > chris > > It would require a deeper thought, because there are potentially more > interesting things to take into account. > > But my first idea is that, the automated tool would offer you / ask you > what optional packages do you want. It would then remember your choice, > and could also track any possible changes to the upstream OPTIONAL > field, and if there was a change, ask you again. > > Of course you could just edit some config file to contain all the > optional packages, but what we're talking about here is to let the > machine assist you in doing so, and tracking for possible > misconfiguration (e.g. the tool can detect that you have a package > flagged as optional, but upstream has changed .info and removed that > package from OPTIONAL field). It could also, more basically, just pop that there are optional dependencies, and ask you to take steps manually. I don't re-read every README each time I rebuild a package, and I don't keep track of which packages have optional dependencies. Sometimes there is a %README% listed as a REQUIRE (like in ffmpeg.info), but not always (openbox, nothing in REQUIRE, but imlib2 is optional). It is actually hard to keep track of wether I built a package with an optional dependency. Having a list of optional package would help, as I could look at which ones are installed already, which ones are out of date, and take care of all that before rebuilding a given package. I have actually a special script to handle ffmpeg, which reports installed dependencies, check their up-to-date status, and build ffmpeg with my options. Because it's too big a mess otherwise ^^ - Arnaud. From jgraha8 at gmail.com Wed Oct 26 06:04:10 2016 From: jgraha8 at gmail.com (Jason Graham) Date: Wed, 26 Oct 2016 02:04:10 -0400 Subject: [Slackbuilds-users] engauge: broken link, project moved, new versions Message-ID: Hi, The engauge download link is broken due the project having been moved to http://markummitchell.github.io/engauge-digitizer/ The SBo version is at 5.2 which the new site doesn't host (only version 6 or later). I found a 5.2 package hosted by the fedora project http://pkgs.fedoraproject.org/lookaside/pkgs/engauge-digitizer/engauge_5.2.tgz/2fbd9c81fa9e910f871560767bbb52bc/engauge_5.2.tgz However, it may be a good time to update things since the latest version is at 9.5. I haven't tried building the latest package, but plan to do so shortly. Regards, Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Oct 26 06:23:08 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 26 Oct 2016 13:23:08 +0700 Subject: [Slackbuilds-users] engauge: broken link, project moved, new versions In-Reply-To: References: Message-ID: > The engauge download link is broken due the project having been moved to > > http://markummitchell.github.io/engauge-digitizer/ > > The SBo version is at 5.2 which the new site doesn't host (only version 6 > or later). I found a 5.2 package hosted by the fedora project > > > http://pkgs.fedoraproject.org/lookaside/pkgs/engauge-digitizer/engauge_5.2.tgz/2fbd9c81fa9e910f871560767bbb52bc/engauge_5.2.tgz Hi, Thanks for reporting It's been fixed in my branch > However, it may be a good time to update things since the latest version is > at 9.5. I haven't tried building the latest package, but plan to do so > shortly. You will have to contact the maintainer for that. If he/she doesn't respond, you can step up to take over this package -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Wed Oct 26 09:53:31 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 26 Oct 2016 10:53:31 +0100 Subject: [Slackbuilds-users] Restarting monit still kills it Message-ID: <5188cf36-5f2a-51dd-dd96-0d3a66de8b82@open-t.co.uk> I know this has been brought up on this list before - but has it ever been solved? Using the stock install from SBo, and doing: #/etc/rc.d/rc.monit restart kills Monit. It's the same on all my other machines. Could this be fixed with a 2-3 second delay between stop and start in the rc.monit script - or some other way? From bryanlharris at gmail.com Wed Oct 26 12:46:25 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Wed, 26 Oct 2016 08:46:25 -0400 Subject: [Slackbuilds-users] Restarting monit still kills it In-Reply-To: <5188cf36-5f2a-51dd-dd96-0d3a66de8b82@open-t.co.uk> References: <5188cf36-5f2a-51dd-dd96-0d3a66de8b82@open-t.co.uk> Message-ID: Looking at the last thread, it looks like I never continued with the fix. I will add a delay and submit to them for update. Sorry about that. V/r, Bryan On Wed, Oct 26, 2016 at 5:53 AM, Sebastian Arcus wrote: > I know this has been brought up on this list before - but has it ever been > solved? Using the stock install from SBo, and doing: > > #/etc/rc.d/rc.monit restart > > kills Monit. It's the same on all my other machines. Could this be fixed > with a 2-3 second delay between stop and start in the rc.monit script - or > some other way? > _______________________________________________ > 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 s.arcus at open-t.co.uk Wed Oct 26 12:55:40 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 26 Oct 2016 13:55:40 +0100 Subject: [Slackbuilds-users] Restarting monit still kills it In-Reply-To: References: <5188cf36-5f2a-51dd-dd96-0d3a66de8b82@open-t.co.uk> Message-ID: <3f69074f-6e34-dffe-6bdc-67c4b53145d9@open-t.co.uk> On 26/10/16 13:46, Bryan Harris wrote: > Looking at the last thread, it looks like I never continued with the > fix. I will add a delay and submit to them for update. > > Sorry about that. Thank you! > > V/r, > Bryan > > On Wed, Oct 26, 2016 at 5:53 AM, Sebastian Arcus wrote: >> I know this has been brought up on this list before - but has it ever been >> solved? Using the stock install from SBo, and doing: >> >> #/etc/rc.d/rc.monit restart >> >> kills Monit. It's the same on all my other machines. Could this be fixed >> with a 2-3 second delay between stop and start in the rc.monit script - or >> some other way? >> _______________________________________________ >> 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 johannes at schoepfer.info Wed Oct 19 22:03:20 2016 From: johannes at schoepfer.info (johannes at schoepfer.info) Date: Thu, 20 Oct 2016 00:03:20 +0200 Subject: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware In-Reply-To: References: <580743EA.8030201@schoepfer.info> <9ac11e6c-538d-02d5-877c-5d4c4213f4c5@open-t.co.uk> <58077812.701@schoepfer.info> Message-ID: <25f015765c35b6a918a1fa6f5c342ee3@schoepfer.info> > On 10/19/2016 08:41 AM, Franzen wrote: >> On 19.10.2016 12:17, Sebastian Arcus wrote: >>> On 19/10/16 10:59, Franzen wrote: >>>> On 19.10.2016 11:42, Sebastian Arcus wrote: >>>>> The clamav-unofficial-sigs.cron crond crontab file included with >>>>> clamav-unofficial-sigs seems to be incompatible with the version of > Cron >>>>> used on Slackware. It uses the extra field for the username >>>>> (clamav) >>>>> which seems to break things on Slackware. I've just noticed this on >>>>> several clamav installs which were months out of date, as the cron >>>>> file >>>>> never worked. Also, I'm not sure the "/bin/bash" bit on the crontab > line >>>>> is needed - as it works fine for me without it. >>>> >>>> /usr/bin/clamav-unofficial-sigs.sh has to be excuted as user clamav, >>>> i >>>> suggest to don't use the cron-script from upstream, but put the >>>> following in /var/spool/cron/crontabs/clamav: >>>> 12 * * * * /usr/bin/clamav-unofficial-sigs.sh >>> >>> I can't really make sense of what is going on here - because the >>> clamav-unofficial-sigs.cron file is included in the >>> clamav-unofficial-sigs.tar.gz - but looking at its contents, it >>> should >>> be part of the sources, as it comes from upstream. Same with the >>> logrotate and the man files. Why are they included in the SBo scripts >>> archive? >> >> The cron-file and logrotate-file come from upstream, they are >> generated by >> > https://raw.githubusercontent.com/extremeshok/clamav-unofficial-sigs/master/clamav-unofficial-sigs.sh, > by the --install-all option. I assume the packager exracted the files > because he didn't wan't to use the --install-all option for the > package. >> As this package depends on clamav, which has also logrotate-script > starting with >> /var/log/clamav/*.log { >> ,logrotate will complain about double configuration, so you don't need > this logrotate at all. >> The best the you can do, is to fix the SlackBuild and propose it to > the maintainer. > I'm the maintainer for clamav-unofficial-sigs. logrotate and cron > script > are provided within the clamav-unofficial-sigs.sh script and upstream > expects each user to use --install-all to generate those two. With > SlackBuild, we shouldn't expect the user to do one additional step > after > install to actually use the package. > So with every new version, I > extract logrotate and cron script first and provide them as part of > SlackBuild. > > As far as using upstream cron script is concerned, my intent was to > provide a script in DOCS so builders will take it as an example and not > simply copy and use the script in cron. You can roll your own or > modify > upstream script as you see fit. > > Here's my crontab (root) > > # Run clamav-unofficial-sigs script > 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null > > I can provide my script as an example which would again go in DOCS and > not anywhere else. That would make more sense, as the upstream-cron-script isn't a good example as it does not work with dillon's cron. In that case, a note that it has to be run as clamav user would also be helpfull. Logrotate will still complain about double configured logfiles(see clamav logrotate-script) with the current Buildscript. Johannes From pedro at gepasi.org Wed Oct 26 14:33:38 2016 From: pedro at gepasi.org (Pedro Mendes) Date: Wed, 26 Oct 2016 10:33:38 -0400 Subject: [Slackbuilds-users] engauge: broken link, project moved, new versions In-Reply-To: References: Message-ID: Hi Jason I've got a slackbuild for version 8.3 ready which I am going to upload. However since this now requires lib4cpp and that itself is not yet on slackbuilds, I had to package a slackbuild for that and upload it to SBo. I can only upload the new engauge slackbuild after lib4cpp is available, because this is a requirement... I wish the author had moved to log4cplus, which is in SBo, as some users requested , but he has not done so. I am also trying to get version 9.5 done. I will upload that one as soon as possible (if it turns out to be easy, then I may submit that one straight away). Regards Pedro On Wed, Oct 26, 2016 at 2:04 AM, Jason Graham wrote: > Hi, > > The engauge download link is broken due the project having been moved to > > http://markummitchell.github.io/engauge-digitizer/ > > The SBo version is at 5.2 which the new site doesn't host (only version 6 > or later). I found a 5.2 package hosted by the fedora project > > http://pkgs.fedoraproject.org/lookaside/pkgs/engauge- > digitizer/engauge_5.2.tgz/2fbd9c81fa9e910f871560767bbb52bc/engauge_5.2.tgz > > However, it may be a good time to update things since the latest version > is at 9.5. I haven't tried building the latest package, but plan to do so > shortly. > > Regards, > Jason > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryanlharris at gmail.com Wed Oct 26 16:51:02 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Wed, 26 Oct 2016 12:51:02 -0400 Subject: [Slackbuilds-users] Restarting monit still kills it In-Reply-To: <3f69074f-6e34-dffe-6bdc-67c4b53145d9@open-t.co.uk> References: <5188cf36-5f2a-51dd-dd96-0d3a66de8b82@open-t.co.uk> <3f69074f-6e34-dffe-6bdc-67c4b53145d9@open-t.co.uk> Message-ID: Okay it is in the queue with a new sleep 2 statement between stop and start. I also went ahead and updated to monit v5.20.0. https://slackbuilds.org/pending/ V/r, Bryan On Wed, Oct 26, 2016 at 8:55 AM, Sebastian Arcus wrote: > > On 26/10/16 13:46, Bryan Harris wrote: >> >> Looking at the last thread, it looks like I never continued with the >> fix. I will add a delay and submit to them for update. >> >> Sorry about that. > > > Thank you! > > > > >> >> V/r, >> Bryan >> >> On Wed, Oct 26, 2016 at 5:53 AM, Sebastian Arcus >> wrote: >>> >>> I know this has been brought up on this list before - but has it ever >>> been >>> solved? Using the stock install from SBo, and doing: >>> >>> #/etc/rc.d/rc.monit restart >>> >>> kills Monit. It's the same on all my other machines. Could this be fixed >>> with a 2-3 second delay between stop and start in the rc.monit script - >>> or >>> some other way? >>> _______________________________________________ >>> 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 yalhcru at gmail.com Wed Oct 26 18:08:50 2016 From: yalhcru at gmail.com (B Watson) Date: Wed, 26 Oct 2016 14:08:50 -0400 Subject: [Slackbuilds-users] engauge: broken link, project moved, new versions In-Reply-To: References: Message-ID: On 10/26/16, Pedro Mendes wrote: > I had to package a slackbuild for that and upload it to SBo. I > can only upload the new engauge slackbuild after lib4cpp is available, > because this is a requirement... You could have uploaded them together, if they were both ready. From willysr at slackbuilds.org Sat Oct 29 00:15:23 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Oct 2016 07:15:23 +0700 Subject: [Slackbuilds-users] Updates - 20161029.1 Message-ID: Sat Oct 29 00:00:06 UTC 2016 academic/cholmod: Fix underlinking against gfortran libraries. academic/engauge: Updated for version 5.20.0. academic/reduce-algebra: Updated for version 20161022svn3821. academic/umfpack: Fix underlinking against gfortran libraries. academic/units: Updated for version 2.13. audio/clyrics: Updated for version 0.05. desktop/fbmenugen: Updated for version 0.78. desktop/i3situation: Switch to i586. desktop/lumina: Updated for version 1.1.0-p1. desktop/menutray: Updated for version 0.47. desktop/quickswitch-i3: Switch to i586. development/Cython-Kivy: Update DOWNLOAD url. development/SQLAlchemy: Updated for version 1.1.3. development/apache-ant: Update README. development/atom: Updated for version 1.11.2. development/dao: Switch to i586 + update HOMEPAGE. development/dmd: Added (Digital Mars D Compiler Package). development/eagle: Updated for version 7.7.0 + new maintainer. development/gambas3: Add Qt5 detection. development/hhvm: Update script. development/ioncube-loader: Updated for version 6.0.5. development/jdk: Updated for version 8u112. development/mysql-workbench: Updated for version 6.3.8. development/nodejs: Updated for version 6.9.1. development/p4: Updated for version 2016.1.1454320. development/p4d: Updated for version 2016.1.1454320. development/pkgconf: Updated for version 1.0.2. development/unittest-cpp: Added (unit testing framework). development/universal-ctags: Updated for version 7859817. games/bitfighter: Switch to i586 + remove dead link. games/domination: Added (clone of the board game Risk). games/doomretro: Updated for version 2.3.2. games/ppsspp: Updated for version 2016.10.26_cc37528. games/solarus-quest-editor: Updated for version 1.5.0. games/solarus: Updated for version 1.5.0. games/tome4: Updated for version 1.4.9. games/zelda-roth-se: Updated for version 1.1.0. games/zsdx: Updated for version 1.11.0. games/zsxd: Added (Parodic Zelda fangame). gis/GMT: Updated for version 5.3.1. gis/opencpn: Added (A Chartplotter and GPS Navigation Software). graphics/Shellpic: Switch to i586. graphics/pngcrush: Updated for version 1.8.9. graphics/pygraphviz: Add python3 support. libraries/BeautifulSoup4: Add python3 support. libraries/GitPython: Updated for version 2.1.0. libraries/alure: Fix build when fluidsynth is present. libraries/backports-ssl-match-hostname: Switch to i586. libraries/botocore: Updated for version 1.4.65. libraries/dropbox-python: Updated for version 7.1.0. libraries/eris: Switch to i586. libraries/fuzzylite: Switch to i586. libraries/libcpuid: Switch to i586. libraries/libdvdcss: Included some patches from upstream git repo libraries/libewf: Fix DOWNLOAD url. libraries/libopenshot-audio: Added (OpenShot Audio library). libraries/libopenshot: Added (OpenShot Library). libraries/live555: Updated for 2016.10.21 libraries/log4cpp: Added (library of C++ classes for logging). libraries/munkres: Switch to i586. libraries/mysql-connector-c++: Updated for version 1.1.7. libraries/pyjf3: Switch to i586. libraries/rtorrent-python: Switch to i586. libraries/skstream: Switch to i586. libraries/sparsehash: Updated for version 2.0.3. libraries/tff: Switch to i586. multimedia/MP3Diags: Added (mp3 file diagnosis and repair tool). multimedia/flashplayer-plugin: Updated for version 11.2.202.643. multimedia/get_iplayer: Updated for version 2.97. multimedia/mkclean: Added (Matroska Optimizer). multimedia/mlt: added optional qt5 support, various fixes. multimedia/openshot: Updated for version 2.1.0. New maintainer network/ClusterSSH: Updated for version 4.08. network/Electrum: Updated for version 2.7.11. network/aldryn-client: Updated for version 2.3.5. network/awscli: Updated for version 1.11.8. network/dropbox: Updated for version 13.4.21. network/flexget: Updated for version 2.5.1. network/mosaic-ck: Added (Cameron Kaiser's fork of NCSA Mosaic). network/offlineimap: Updated for version 7.0.8. network/opendkim: Update script. network/opera-developer: Updated for version 42.0.2392.0. network/opera-legacy: Added (Web browser and Internet suite). network/opera: Removed (per maintainer request). network/packETH: Switch to i586. network/retroshare: Updated for version 0.6.0RC2. network/shorewall-core: Updated for version 5.0.13.4. network/shorewall6: Updated for version 5.0.13.4. network/shorewall: Updated for version 5.0.13.4. network/syncthing: Updated for version 0.14.9. network/telegram: Updated for version 0.10.19. network/vivaldi: Update README. network/wire: Added (Wire for Desktop). network/youtube-dl-gui: Switch to i586. network/youtube-dl: Updated for version 2016.10.25. office/CherryTree: Updated for version 0.37.5. office/asymptote: Added (The Vector Graphics Language) office/pdfjam: Added (pdf toolkit). office/texlive-docs: Updated for version 20161025. office/texlive-extra: Updated for version 20161023. office/texlive-fonts: Updated for version 20161023. office/texlive: Updated texmf to 20161023; removed asymptote office/unoconv: Switch to i586. perl/mod_perl: Updated for version 2.0.10. perl/perl-Cache-FastMmap: Updated for version 1.44. perl/perl-File-Finder: Added (nice wrapper for File::Find). perl/perl-Image-Info: Updated for version 1.39. perl/perl-Module-Install: Updated for version 1.17. perl/perl-Test-PerlTidy: Added (check that all your files are tidy). perl/perl-Test-Simple: Updated for version 1.302062. perl/perl-X11-Protocol-Other: Added (perl modules). python/Flask-Login: Updated for version 0.4.0. python/Flask-SQLAlchemy: Switch to i586. python/Paver: Switch to i586. python/PyInstaller: Updated for version 3.2. python/autopep8: Switch to i586. python/curtsies: Updated for version 0.2.11. python/frosted: Switch to i586. python/mando: Updated for version 0.4. python/pendulum: Updated for version 0.6.4. python/pipdeptree: Updated for version 0.8.0. python/pipstat: Switch to i586. python/pyfiglet: Switch to i586. python/pymongo: Updated for version 3.3.1. python/pytest-cov: Updated for version 2.4.0. python/python-future: Updated for version 0.16.0. python/python-libsass: Updated for version 0.11.2. python/python-twitter: Updated for version 3.1. python/python3-Cython: Added (C-Extensions for Python3). python/python3-pythondialog: Added (dialog utility). python/python3-pyzmq: Added (Python3 bindings for 0MQ). python/requests-futures: Switch to i586. python/s3transfer: Updated for version 0.1.9. python/scikit-learn: Added (machine learning and data mining). python/shutilwhich: Added (shutil.which backport from Python 3.3). python/smmap2: Updated for version 2.0.1. python/waitress: Updated for version 1.0.1. ruby/rubygem-bundler: Updated for version 1.13.6. system/Iosevka: Updated for version 1.9.5. system/ansible: Updated for version 2.1.2.0 + new maintainer. system/argyllcms: Updated for version 3.6.0. system/backasa: Switch to i586. system/disksearch: Switch to i586. system/firejail: Updated for version 0.9.44. system/lnav: Added (The Log File Navigator). system/monit: Updated for version 5.20.0. system/mysql-utilities: Updated for version 1.6.4. system/partimage: Added (backup system). system/pstate-frequency: Updated for version 3.6.0. system/slpkg: Updated for version 3.2.2. system/st: Updated for version 0.7. system/ttop: Switch to i586. system/xautolock: Added (monitors console activity). +--------------------------+ -- 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 Oct 29 06:00:11 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 29 Oct 2016 00:00:11 -0600 Subject: [Slackbuilds-users] wbar broken source code url. Message-ID: wbar broken source code url. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Sat Oct 29 06:30:52 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 29 Oct 2016 08:30:52 +0200 Subject: [Slackbuilds-users] wbar broken source code url. In-Reply-To: References: Message-ID: <9246825c26f6ec06a0bd32ce78df539e@schoepfer.info> On 2016-10-29 08:00, Fernando Lopez wrote: > wbar broken source code url. Fernando, let me google that for you: https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/wbar/wbar-2.3.4.tgz The more efficient way would have been to send a working link to the maintainer. Johannes From bch at shroggslodge.freeserve.co.uk Sat Oct 29 08:50:43 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Sat, 29 Oct 2016 09:50:43 +0100 Subject: [Slackbuilds-users] libwebp source not accessible Message-ID: Good morning everyone I have been trying to download libwebp and the source server is not accessible..at least to me; "storage.googleapis.com" full link: https://storage.googleapis.com/downloads.webmproject.org/releases/webp/libwebp-0.5.1.tar.gz Has anyone else got trouble with the same please ? Apologies if this has already been reported. Thank you Habs -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Oct 29 08:52:43 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Oct 2016 15:52:43 +0700 Subject: [Slackbuilds-users] libwebp source not accessible In-Reply-To: References: Message-ID: > I have been trying to download libwebp and the source server is not > accessible..at least to me; "storage.googleapis.com" > > full link: > https://storage.googleapis.com/downloads.webmproject.org/releases/webp/libwebp-0.5.1.tar.gz > > Has anyone else got trouble with the same please ? > > Apologies if this has already been reported. Hi It works fine here -- 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 Sat Oct 29 09:29:14 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Sat, 29 Oct 2016 10:29:14 +0100 Subject: [Slackbuilds-users] libwebp source not accessible In-Reply-To: References: Message-ID: Thank you for that. I have sorted it. Following your confirmation I checked my settings and that domain is blocked in my hosts file...the hosts file compilation has not been updated for many a moon and is taken from hosts-file.net. Is this a [fairly] new location for libwebp source please ? Regards On 29 October 2016 at 09:52, Willy Sudiarto Raharjo wrote: > > I have been trying to download libwebp and the source server is not > > accessible..at least to me; "storage.googleapis.com" > > > > full link: > > https://storage.googleapis.com/downloads.webmproject.org/ > releases/webp/libwebp-0.5.1.tar.gz > > > > Has anyone else got trouble with the same please ? > > > > Apologies if this has already been reported. > > Hi > > It works fine here > > > > -- > 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 Sat Oct 29 09:33:25 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Oct 2016 16:33:25 +0700 Subject: [Slackbuilds-users] libwebp source not accessible In-Reply-To: References: Message-ID: <37d374db-25b7-7271-265d-2ade6ca76c17@slackbuilds.org> > Thank you for that. I have sorted it. Following your confirmation I checked > my settings and that domain is blocked in my hosts file...the hosts file > compilation has not been updated for many a moon and is taken from > hosts-file.net. > > Is this a [fairly] new location for libwebp source please ? it's been there for a month or so -- 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 cristiano at telenet.be Sat Oct 29 14:16:14 2016 From: cristiano at telenet.be (Cristiano Di Buduo) Date: Sat, 29 Oct 2016 16:16:14 +0200 Subject: [Slackbuilds-users] Updates - 20161029.1 In-Reply-To: References: Message-ID: <7a987ac6-beac-b1f8-1a63-6e7a4b7a0e22@telenet.be> How to unsubscribe please? I've sent a message with subject "unsubscribe" weeks ago already. From nishant at mnspace.net Sat Oct 29 17:00:21 2016 From: nishant at mnspace.net (Nishant Limbachia) Date: Sat, 29 Oct 2016 12:00:21 -0500 Subject: [Slackbuilds-users] Updates - 20161029.1 In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/28/2016 07:15 PM, Willy Sudiarto Raharjo wrote: > system/argyllcms: Updated for version 3.6.0. Looks like a typo somewhere. Argyllcms version in the SlackBuild is 1.9.2 Thanks, - -- Nishant Limbachia nishant at mnspace.net ### Please note the new pgp keys Old GPG Key: 0x0FF9D6D5 (expiring soon) Old GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5 New GPG Key: 0x3D46A2D1 New GPG Fingerprint: 44D1 27CE D07F 2ED1 B4AD 2BEE A828 D6D6 3D46 A2D1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYFNWlAAoJEKgo1tY9RqLRZVcP/2jYNT9Ewp24Rn/90N9U6OTC G8s/y0rhM4Vgn3wVEARV3EpzylJbIYk59yTPq/vZ0swVSLGLWFr5KNXof3xQXH1M nRdjuExnPNp9VAjdAhQb5pReccnWQzYd6YJFwkSekdUfbvjz/sffLlxhw0Y2WVVq aS0Xc/rnLfouGdiy45A5xeMPQlV3h6QFmDfGvXznvZiK/7irV0tHmYwrZX3Yvngo yNmKddFGH4XsbEi5v852n2bjop4Y8juweHhNCPyvDAiATtO+p61SBraKVI9OSG05 Krjnnhm7EioRZ3argI5TqKJHQp6DRP1MM5yIeAR31WZ3b1CfOTYfh7FkABOzpFKN CCXvhPfkIRvyVQ9LPSNfZjE4Qol5B7iR5A28vfrZe97EGGXrthV+rtIIKZW4iuCh 5BVdFOlra+pRdw8ZU7TTunoXZug2C3XZ7vrbv/TKt7pozhpjWTAf6rTquBxJZf1m ERsCVN28yU/sZg0RAOwzkpbWZL+zT7pb5QMQvonVANONnnuaXsS9XwEU21hOQmR0 F8HJp8qnS7a7xHsFkk8JT1r4W5OvhoWtiD1VzFm9ZCe8pziDQQxVkmBvesrEhdcG 3dxwh3vgTXOdJDB5r1TJa3ufNzjmdlGL+w5MCEBBZoYpJ5ItX2VceSPXhJqlTBIz raY8TOfgYk96XD2CLs23 =i/iL -----END PGP SIGNATURE----- From sombragris at sombragris.org Sat Oct 29 17:32:42 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sat, 29 Oct 2016 14:32:42 -0300 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org Message-ID: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> For the following SlackBuild: https://slackbuilds.org/repository/14.2/office/texlive/ When trying to download the following file: ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz a) At first try, download location capped download bandwitdh to 15 kb/s. So, downloading a 44MB source file was a S-L-O-W process. b) At second try, download location rejected anonymous login attempts so redownload was impossible. I'd suggest seeking a reliable, fast mirror for such file, if possible. Thanks, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== From slackbuilds at schoepfer.info Sat Oct 29 18:16:53 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 29 Oct 2016 20:16:53 +0200 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> Message-ID: <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> On 2016-10-29 19:32, Eduardo Sanchez wrote: > For the following SlackBuild: > > https://slackbuilds.org/repository/14.2/office/texlive/ > > When trying to download the following file: > > ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz > > a) At first try, download location capped download bandwitdh to 15 > kb/s. So, downloading a 44MB source file was a S-L-O-W process. I never had issues with that download, maybe a temporay issue? No one reported thta before. I don't believe that my server is more reliable than tug.org, but if you have no issues downloading texlive-base-20161023.tar.xz, you can also grab the sources from that place: http://slackware.schoepfer.info/slackbuilds/texlive/2016/texlive/texlive-20160523b-source.tar.xz > I'd suggest seeking a reliable, fast mirror for such file, if possible. If more people have issues with that download, i'll look for another solution. Johannes From ts at websafe.pl Sat Oct 29 18:27:50 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 29 Oct 2016 20:27:50 +0200 Subject: [Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch? Message-ID: <899534ea-7526-65f9-a50c-92acc83030ec@websafe.pl> Hello, lately I posted an update for KeePass https://slackbuilds.org/repository/14.2/misc/KeePass/ and now I'm creating a SlackBuild for KeePassHttp, which is a plugin for KeePass and this plugin is a pure plgx file, (no compilation needed) so the Slackbuild will contain ARCH=noarch. Now I'm thinking that KeePass itself should be noarch too... Am I right? It's a pure mono application (binary). https://slackbuilds.org/slackbuilds/14.2/misc/KeePass/KeePass.SlackBuild Just let me know and I'll post an updated Slackbuild. -- 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 yalhcru at gmail.com Sat Oct 29 18:30:59 2016 From: yalhcru at gmail.com (B Watson) Date: Sat, 29 Oct 2016 14:30:59 -0400 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> Message-ID: On 10/29/16, Franzen wrote: > If more people have issues with that download, i'll look for another > solution. Tried from two different systems on different networks, both times: wget ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz --2016-10-29 14:20:21-- ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz => 'texlive-20160523b-source.tar.xz' Resolving tug.org (tug.org)... 130.225.2.178 Connecting to tug.org (tug.org)|130.225.2.178|:21... connected. Logging in as anonymous ... Login incorrect. There's a copy here: http://slackware.uk/sbosrcarch/by-md5/1/e/1e75db3412b3e2945fa94b0a423a29c7/texlive-20160523b-source.tar.xz ...but it'd be better not to use that as the download URL in the .info file. A better bet would be to use the OSU mirror: http://ftp.osuosl.org/pub/blfs/conglomeration/texlive/texlive-20160523b-source.tar.xz From yalhcru at gmail.com Sat Oct 29 18:37:25 2016 From: yalhcru at gmail.com (B Watson) Date: Sat, 29 Oct 2016 14:37:25 -0400 Subject: [Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch? In-Reply-To: <899534ea-7526-65f9-a50c-92acc83030ec@websafe.pl> References: <899534ea-7526-65f9-a50c-92acc83030ec@websafe.pl> Message-ID: On 10/29/16, Thomas Szteliga wrote: > Now I'm thinking that KeePass itself should be noarch too... > Am I right? It's a pure mono application (binary). If there are no native (ELF) binaries, the only other thing to watch out for is LIBDIRSUFFIX. If it installs stuff in /usr/lib on 32-bit and /usr/lib64 on 64-bit, you'll want to get rid of that (/usr/share/$PRGNAM is probably better). The test is whether the same binary package runs correctly on either 32-bit or 64-bit. Example: a lot of Perl packages install only perl code, nothing native, but the install path is different (lib vs. lib64) so they can't use noarch. ...and, you have just made me realize that the 'domination' build I just submitted should be noarch also (it's pure Java). From ts at websafe.pl Sat Oct 29 19:11:16 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 29 Oct 2016 21:11:16 +0200 Subject: [Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch? In-Reply-To: References: <899534ea-7526-65f9-a50c-92acc83030ec@websafe.pl> Message-ID: <06777a0a-3c6b-6203-7c5a-a8f5c2b8934b@websafe.pl> On 10/29/2016 08:37 PM, B Watson wrote: > On 10/29/16, Thomas Szteliga wrote: >> Now I'm thinking that KeePass itself should be noarch too... >> Am I right? It's a pure mono application (binary). > If there are no native (ELF) binaries, the only other thing to watch > out for is LIBDIRSUFFIX. If it installs stuff in /usr/lib on 32-bit and > /usr/lib64 on 64-bit, you'll want to get rid of that (/usr/share/$PRGNAM > is probably better). I think this /usr/share/$PRGNAM in this case is much better than /usr/lib/$PRGNAM. I've seen this on Arch Linux. Fedora ships KeePass with defined ARCH and in /usr/lib (also the x86_64 pkg) but I see there's another thing, the Slackware pkg is coming with KeePassLibC32.dll and KeePassLibC64.dll and ShInstUtil.exe, which are probably not needed (not found in fedora's rpm). I'll check this before posting a noarch Slackbuild. > The test is whether the same binary package runs correctly on either > 32-bit or 64-bit. > Example: a lot of Perl packages install only perl code, nothing native, > but the install path is different (lib vs. lib64) so they can't use > noarch. All KeePass files (except icons) land in /usr/lib/KeePass/ on both - x86 and x86_64. > ...and, you have just made me realize that the 'domination' build I just > submitted should be noarch also (it's pure Java). :-) -- 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 belka at caraus.de Sat Oct 29 21:39:25 2016 From: belka at caraus.de (Eugen Wissner) Date: Sat, 29 Oct 2016 23:39:25 +0200 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> Message-ID: <1477777165.24030.0.camel@caraus.de> I personally haven't had any problems with tug.org ever. Am Samstag, den 29.10.2016, 20:16 +0200 schrieb Franzen: > On 2016-10-29 19:32, Eduardo Sanchez wrote: > > For the following SlackBuild: > > > > https://slackbuilds.org/repository/14.2/office/texlive/ > > > > When trying to download the following file: > > > > ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-sourc > > e.tar.xz > > > > a) At first try, download location capped download bandwitdh to 15 > > kb/s. So, downloading a 44MB source file was a S-L-O-W process. > > I never had issues with that download, maybe a temporay issue? No > one? > reported thta before. > I don't believe that my server is more reliable than tug.org, but > if you have no issues downloading texlive-base-20161023.tar.xz, you > can? > also grab the sources from that place: > http://slackware.schoepfer.info/slackbuilds/texlive/2016/texlive/texl > ive-20160523b-source.tar.xz > > > I'd suggest seeking a reliable, fast mirror for such file, if > > possible. > > If more people have issues with that download, i'll look for another? > solution. > > Johannes > _______________________________________________ > 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 Sat Oct 29 22:08:31 2016 From: yalhcru at gmail.com (B Watson) Date: Sat, 29 Oct 2016 18:08:31 -0400 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: <1477777165.24030.0.camel@caraus.de> References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> <1477777165.24030.0.camel@caraus.de> Message-ID: On 10/29/16, Eugen Wissner wrote: > I personally haven't had any problems with tug.org ever. It seems to be intermittent. I just tried it again and it downloaded just fine. From slackbuilds at schoepfer.info Sat Oct 29 23:33:03 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 30 Oct 2016 01:33:03 +0200 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> Message-ID: >> If more people have issues with that download, i'll look for another >> solution. > > Tried from two different systems on different networks, both times: > > wget > ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz > --2016-10-29 14:20:21-- > ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz > => 'texlive-20160523b-source.tar.xz' > Resolving tug.org (tug.org)... 130.225.2.178 > Connecting to tug.org (tug.org)|130.225.2.178|:21... connected. > Logging in as anonymous ... > Login incorrect. That's what i got from the texlive-mailinglist: > Connecting to tug.org (tug.org)|130.225.2.178|:21... connected. > Logging in as anonymous ... > > It is common for all the anon ftp slots on tug to get used up by > stupid robots or whatever. Despite my limiting by IP address, etc. > > > beside that there's also the rsync-able svn, > > In addition to the svn, the whole historic/ directory is available by > rsync ... tug.org::historic/systems/texlive/2016/ > > On ctan there is > http://mirrors.ctan.org/systems/texlive/Source/texlive-20160520- > source.tar.xz, > which is not same release tarball. > > Oops. I updated the directories on tug. I'm not sure if CTAN mirrors > that directory continuously or only when I ask them to update. We'll > see > what happens in the next 24 hours or so ... --thanks, karl. So, there may be an alternative Download location soon on CTAN. If i use a CTAN download-link in the .info-file, the link will likely be broken as soon as texlive2017 is released, tug.org keeps the archive. Johannes From jebrhansen+SBo at gmail.com Sun Oct 30 00:06:49 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 29 Oct 2016 20:06:49 -0400 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> Message-ID: On Sat, Oct 29, 2016 at 2:30 PM, B Watson wrote: > > There's a copy here: > > http://slackware.uk/sbosrcarch/by-md5/1/e/1e75db3412b3e2945fa94b0a423a29 > c7/texlive-20160523b-source.tar.xz > > ...but it'd be better not to use that as the download URL in the .info > file. > That is just if you want to use the directory structure based on MD5 hashes. They also have it sorted into the same directories as SBo. http://slackware.uk/sbosrcarch/by-name/office/texlive/texlive-20160523b-source.tar.xz -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Oct 30 00:41:06 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 30 Oct 2016 07:41:06 +0700 Subject: [Slackbuilds-users] Updates - 20161029.1 In-Reply-To: References: Message-ID: <47adfd5d-0bfd-b628-c993-1d1d2a46c986@slackbuilds.org> >> system/argyllcms: Updated for version 3.6.0. > Looks like a typo somewhere. Argyllcms version in the SlackBuild is 1.9.2 Yes, i think i made a mistake by not sourcing the .info file when doing git commit to argyllcms so it took the wrong version number, but the SlackBuild and .info file are correct. -- 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 rsamurti at gmail.com Sun Oct 30 07:07:46 2016 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Sun, 30 Oct 2016 12:37:46 +0530 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> Message-ID: Hello, When I try to download ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz it is asking me to enter user name and password. Anand On Sun, Oct 30, 2016 at 5:36 AM, Jeremy Hansen wrote: > > > On Sat, Oct 29, 2016 at 2:30 PM, B Watson wrote: > >> >> There's a copy here: >> >> http://slackware.uk/sbosrcarch/by-md5/1/e/1e75db3412b3e2945f >> a94b0a423a29c7/texlive-20160523b-source.tar.xz >> >> ...but it'd be better not to use that as the download URL in the .info >> file. >> > > That is just if you want to use the directory structure based on MD5 > hashes. They also have it sorted into the same directories as SBo. > > http://slackware.uk/sbosrcarch/by-name/office/texlive/texlive-20160523b- > source.tar.xz > > > _______________________________________________ > 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/ > > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Sun Oct 30 10:07:19 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 30 Oct 2016 20:07:19 +1000 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> Message-ID: <2791f073-781f-3084-0851-8ad0a64a32e5@iinet.net.au> On 30/10/16 17:07, Ananda Murthy R S wrote: > Hello, > > When I try to download > ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz > it is asking me to enter user name and password. > Either: log in as 'anonymous' with your email (or anything else you like) as the password or: use wget to download it (wget will log in as anonymous for you) chris From atelszewski at gmail.com Sun Oct 30 10:08:35 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 30 Oct 2016 11:08:35 +0100 Subject: [Slackbuilds-users] Is building packages using fakeroot safe? Message-ID: Hi, I would like to ask you, if building packages within fakeroot is safe? What I mean is, have you ever encountered any problem, e.g. a package with wrong permissions or something like that? I've been testing fakeroot for a while and so far haven't observed any obvious problems. I know that Buildroot (https://buildroot.org/) is using fakeroot to generate the whole root file system and this project has a lot of eyes looking into it, so I assume it's working fine. Based on that, I assume it works fine for building Slackware packages too. Thanks! -- Best regards, Andrzej Telszewski From slackbuilds at schoepfer.info Sun Oct 30 11:02:30 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 30 Oct 2016 12:02:30 +0100 Subject: [Slackbuilds-users] Is building packages using fakeroot safe? In-Reply-To: References: Message-ID: On 2016-10-30 11:08, Andrzej Telszewski wrote: > Hi, > > I would like to ask you, if building packages within fakeroot is safe? I did build with fakeroot a few years long, and had some minor issues, maybe this thread(and links in that thread) is a little bit helpful. Currently i build my personal packages as unprivileged user, with a patched makepkg. This does not work without also patching buildscripts from SBo, as there is almost always a "chown root ..." Johannes From atelszewski at gmail.com Sun Oct 30 13:26:20 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 30 Oct 2016 14:26:20 +0100 Subject: [Slackbuilds-users] Is building packages using fakeroot safe? In-Reply-To: References: Message-ID: <75f886b6-3df2-56d3-d8b6-834f6778f0df@gmail.com> On 30/10/16 12:02, Franzen wrote: > On 2016-10-30 11:08, Andrzej Telszewski wrote: >> Hi, >> >> I would like to ask you, if building packages within fakeroot is safe? > > I did build with fakeroot a few years long, and had some minor issues, > maybe this thread(and links in that thread) is a little bit helpful. Links missing? > Currently i build my personal packages as unprivileged user, with a > patched makepkg. > This does not work without also patching buildscripts from SBo, as there > is almost always a "chown root ..." > Changing build scripts is a no-go for me, in my opinion it's too much hassle. I am just playing with software and fakeroot just happened to be interesting to play with. But after a bit of thought, I think it won't be that useful. I'm already using VM to build packages, so I'm on the safe side. What I'm really aiming for is to ensure that the build process does not write outside of the build directories. And it's not possible to spot that happening with fakeroot, because the build process can easily write to /tmp or user directory. And I actually came across Makefile that would write into system directory if building as root or into home directory when building as user. In that cases the build wouldn't stop because of 'permission denied'. I think my best bet is to use overlay filesystem, alternatively there is another piece of software (can't really remember the name now) that can record the changes made to filesystem by particular process. But overlay filesystem is my favorite now, need to give it a go. -- Best regards, Andrzej Telszewski From kristofru at gmail.com Sun Oct 30 13:41:21 2016 From: kristofru at gmail.com (Chris Abela) Date: Sun, 30 Oct 2016 13:41:21 +0000 Subject: [Slackbuilds-users] Is building packages using fakeroot safe? In-Reply-To: <75f886b6-3df2-56d3-d8b6-834f6778f0df@gmail.com> References: <75f886b6-3df2-56d3-d8b6-834f6778f0df@gmail.com> Message-ID: I use fakeroot extensively when building my slackbuilds manually. As far as I remember only qemu refused to build once. On Sun, 30 Oct 2016 14:28 Andrzej Telszewski, wrote: > On 30/10/16 12:02, Franzen wrote: > > On 2016-10-30 11:08, Andrzej Telszewski wrote: > >> Hi, > >> > >> I would like to ask you, if building packages within fakeroot is safe? > > > > I did build with fakeroot a few years long, and had some minor issues, > > maybe this thread(and links in that thread) is a little bit helpful. > > Links missing? > > > Currently i build my personal packages as unprivileged user, with a > > patched makepkg. > > This does not work without also patching buildscripts from SBo, as there > > is almost always a "chown root ..." > > > > Changing build scripts is a no-go for me, in my opinion it's too much > hassle. > > I am just playing with software and fakeroot just happened to be > interesting to play with. > But after a bit of thought, I think it won't be that useful. > I'm already using VM to build packages, so I'm on the safe side. > > What I'm really aiming for is to ensure that the build process does not > write outside of the build directories. > And it's not possible to spot that happening with fakeroot, because the > build process can easily write to /tmp or user directory. > And I actually came across Makefile that would write into system > directory if building as root or into home directory when building as user. > In that cases the build wouldn't stop because of 'permission denied'. > > I think my best bet is to use overlay filesystem, alternatively there is > another piece of software (can't really remember the name now) that can > record the changes made to filesystem by particular process. > > But overlay filesystem is my favorite now, need to give it a go. > > -- > 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: From jebrhansen+SBo at gmail.com Sun Oct 30 14:52:13 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 30 Oct 2016 14:52:13 +0000 Subject: [Slackbuilds-users] Is building packages using fakeroot safe? In-Reply-To: <75f886b6-3df2-56d3-d8b6-834f6778f0df@gmail.com> References: <75f886b6-3df2-56d3-d8b6-834f6778f0df@gmail.com> Message-ID: David Spencer's (55020) slackrepo will automate building using overlay, ultimately keeping the build server completely clean (it starts with a clean install for every build project since it uses overlays and doesn't install the packages to the machine itself -- they're just installed to the overlay, so as soon as it's removed, you're back to a clean system) and setting up a slackpkg+ compatible repo. http://idlemoor.github.io/slackrepo/ It might be something you'd be interested in. On Sun, Oct 30, 2016, 9:28 AM Andrzej Telszewski wrote: > On 30/10/16 12:02, Franzen wrote: > > On 2016-10-30 11:08, Andrzej Telszewski wrote: > >> Hi, > >> > >> I would like to ask you, if building packages within fakeroot is safe? > > > > I did build with fakeroot a few years long, and had some minor issues, > > maybe this thread(and links in that thread) is a little bit helpful. > > Links missing? > > > Currently i build my personal packages as unprivileged user, with a > > patched makepkg. > > This does not work without also patching buildscripts from SBo, as there > > is almost always a "chown root ..." > > > > Changing build scripts is a no-go for me, in my opinion it's too much > hassle. > > I am just playing with software and fakeroot just happened to be > interesting to play with. > But after a bit of thought, I think it won't be that useful. > I'm already using VM to build packages, so I'm on the safe side. > > What I'm really aiming for is to ensure that the build process does not > write outside of the build directories. > And it's not possible to spot that happening with fakeroot, because the > build process can easily write to /tmp or user directory. > And I actually came across Makefile that would write into system > directory if building as root or into home directory when building as user. > In that cases the build wouldn't stop because of 'permission denied'. > > I think my best bet is to use overlay filesystem, alternatively there is > another piece of software (can't really remember the name now) that can > record the changes made to filesystem by particular process. > > But overlay filesystem is my favorite now, need to give it a go. > > -- > 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: From jbernts at broadpark.no Sun Oct 30 18:43:28 2016 From: jbernts at broadpark.no (Jostein Berntsen) Date: Sun, 30 Oct 2016 19:43:28 +0100 Subject: [Slackbuilds-users] fzf fails to build In-Reply-To: References: <20161024201030.GA2354@jostein> Message-ID: <20161030184328.GA3910@jostein> On 24.10.16,22:51, Matteo Bernardini wrote: >2016-10-24 22:10 GMT+02:00 Jostein Berntsen : >> Building fzf after processing the package with sqg gives this error: >> >> # _/tmp/SBo/fzf-0.13.5/src/fzf >> /tmp/go-build733267827/_/tmp/SBo/fzf-0.13.5/src/fzf/_obj/_go_.o: In function >> `main.AN36_github_com_junegunn_fzf_src$sizeSpec4e$hash': >> /tmp/SBo/fzf-0.13.5/src/fzf/main.go:5: undefined reference to >> `github_com_junegunn_fzf_src.sizeSpec$hash' >> collect2: error: ld returned 1 exit status >> Makefile:69: recipe for target 'fzf/fzf-linux_amd64' failed >> make: *** [fzf/fzf-linux_amd64] Error 2 >> >> fzf: >> Would you like to continue processing the rest of the >> queue or would you like to abort? If this failed >> package is a dependency of another package in the queue >> then it may not make sense to continue. > >Hi Jostein, > >google-go-lang installs file in /etc/profile.d that are loaded in your >shell at login, so you have to logout and login again after having >installed the package to use the correct go interpreter to build stuff >(as fzf). > >Matteo Hi, I rebooted and tried again, but still gets the same error. Jostein From atelszewski at gmail.com Sun Oct 30 21:43:32 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 30 Oct 2016 22:43:32 +0100 Subject: [Slackbuilds-users] Is building packages using fakeroot safe? In-Reply-To: References: <75f886b6-3df2-56d3-d8b6-834f6778f0df@gmail.com> Message-ID: <6da9822b-d48b-149b-7bc0-07d4c99cb573@gmail.com> On 30/10/16 15:52, Jeremy Hansen wrote: > David Spencer's (55020) slackrepo will automate building using overlay, > ultimately keeping the build server completely clean (it starts with a > clean install for every build project since it uses overlays and doesn't > install the packages to the machine itself -- they're just installed to > the overlay, so as soon as it's removed, you're back to a clean system) > and setting up a slackpkg+ compatible repo. > > http://idlemoor.github.io/slackrepo/ > > It might be something you'd be interested in. It definitely is. Thanks! -- Best regards, Andrzej Telszewski From slackbuilds at schoepfer.info Mon Oct 31 07:52:33 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 31 Oct 2016 08:52:33 +0100 Subject: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org In-Reply-To: References: <0q93i.71108e5a9f.20161029143242.55ee0060@loli.sombragris.org> <62dd8be0ab93d15990b1db868bc8ee42@schoepfer.info> Message-ID: <8ea385e8fe56a01f938829c8306d83f0@schoepfer.info> On 2016-10-30 01:33, Franzen wrote: >>> If more people have issues with that download, i'll look for another >>> solution. >> >> Tried from two different systems on different networks, both times: >> >> wget >> ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz >> --2016-10-29 14:20:21-- >> ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz >> => 'texlive-20160523b-source.tar.xz' >> Resolving tug.org (tug.org)... 130.225.2.178 >> Connecting to tug.org (tug.org)|130.225.2.178|:21... connected. >> Logging in as anonymous ... >> Login incorrect. > > That's what i got from the texlive-mailinglist: > >> Connecting to tug.org (tug.org)|130.225.2.178|:21... connected. >> Logging in as anonymous ... >> >> It is common for all the anon ftp slots on tug to get used up by >> stupid robots or whatever. Despite my limiting by IP address, etc. >> >> >> beside that there's also the rsync-able svn, >> >> In addition to the svn, the whole historic/ directory is available by >> rsync ... tug.org::historic/systems/texlive/2016/ >> >> On ctan there is >> http://mirrors.ctan.org/systems/texlive/Source/texlive-20160520- >> source.tar.xz, >> which is not same release tarball. >> >> Oops. I updated the directories on tug. I'm not sure if CTAN mirrors >> that directory continuously or only when I ask them to update. We'll >> see >> what happens in the next 24 hours or so ... --thanks, karl. > > So, there may be an alternative Download location soon on CTAN. It's now on CTAN :-) http://mirrors.ctan.org/systems/texlive/Source/texlive-20160523b-source.tar.xz I'll put this source in the .info-file on the next update. Johannes From sombragris at sombragris.org Mon Oct 31 17:59:25 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Mon, 31 Oct 2016 14:59:25 -0300 Subject: [Slackbuilds-users] Perl modules orphaned between 14.1 and 14.2 Message-ID: <0q93i.01120072d8.20161031145925.2593563d@loli.sombragris.org> Hi there, While hunting an odd bug in texinfo I caught the following: I have some perl modules installed from the 14.1 era: perl-CPAN-Meta-2.150005-x86_64-1_SBo perl-CPAN-Meta-YAML-0.018-x86_64-1_SBo perl-Parse-CPAN-Meta-1.4417-x86_64-1_SBo perl-TermReadKey-2.33-x86_64-0_SBo Now, these modules are *not* in the 14.2 repository, nor there is any notice I can find of their removal. Since I don't know anything about coding and even less about perl, I had to install these as dependencies from another package. Can you see if these are no longer needed and could be removed, or, should any package need those, republish for 14.2? Thanks, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== From yalhcru at gmail.com Mon Oct 31 18:35:18 2016 From: yalhcru at gmail.com (B Watson) Date: Mon, 31 Oct 2016 14:35:18 -0400 Subject: [Slackbuilds-users] Perl modules orphaned between 14.1 and 14.2 In-Reply-To: <0q93i.01120072d8.20161031145925.2593563d@loli.sombragris.org> References: <0q93i.01120072d8.20161031145925.2593563d@loli.sombragris.org> Message-ID: On 10/31/16, Eduardo Sanchez wrote: > Now, these modules are *not* in the 14.2 repository, nor there is any > notice I can find of their removal. The git log has the reason. For all 4 modules: Removed (Included in Slackware's Perl). From sombragris at sombragris.org Mon Oct 31 18:55:34 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Mon, 31 Oct 2016 15:55:34 -0300 Subject: [Slackbuilds-users] Perl modules orphaned between 14.1 and 14.2 Message-ID: <0q93i.3112146fa9.20161031155534.0b23ed34@loli.sombragris.org> About this message: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-October/017333.html > The git log has the reason. For all 4 modules: > > Removed (Included in Slackware's Perl). The issue is that there's no mention at all in the ChangeLog: https://slackbuilds.org/ChangeLog.txt There is no metion of any git log on any part of the SlackBuild website. Any user looking to maintain its system would be at a loss. The question is: where should I follow the SlackBuilds.org changes: at the ChangeLog which is published and advertised at the website, or at some git log whose mention is nowhere on the SlackBuilds.org page? Thanks, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== From atelszewski at gmail.com Mon Oct 31 21:30:25 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 31 Oct 2016 22:30:25 +0100 Subject: [Slackbuilds-users] Is building packages using fakeroot safe? In-Reply-To: References: <75f886b6-3df2-56d3-d8b6-834f6778f0df@gmail.com> Message-ID: On 30/10/16 15:52, Jeremy Hansen wrote: > David Spencer's (55020) slackrepo will automate building using overlay, > ultimately keeping the build server completely clean (it starts with a > clean install for every build project since it uses overlays and doesn't > install the packages to the machine itself -- they're just installed to > the overlay, so as soon as it's removed, you're back to a clean system) > and setting up a slackpkg+ compatible repo. > > http://idlemoor.github.io/slackrepo/ > > It might be something you'd be interested in. Exactly what I was thinking of and maybe something of interest to SBo team: Built ok: wxPython-2.8.12.1-x86_64-2_sbo.txz 22:23:46 WARNING: libraries/wxPython: Files/directories were modified in the chroot /usr/lib64/python2.7/site-packages /usr/lib64/python2.7/site-packages/libxml2.pyc Built ok: youtube-dl-gui-0.3.8-x86_64-1_sbo.txz 22:24:12 WARNING: network/youtube-dl-gui: Files/directories were modified in the chroot /root/.config -- Best regards, Andrzej Telszewski From yalhcru at gmail.com Mon Oct 31 23:01:51 2016 From: yalhcru at gmail.com (B Watson) Date: Mon, 31 Oct 2016 19:01:51 -0400 Subject: [Slackbuilds-users] Perl modules orphaned between 14.1 and 14.2 In-Reply-To: <0q93i.3112146fa9.20161031155534.0b23ed34@loli.sombragris.org> References: <0q93i.3112146fa9.20161031155534.0b23ed34@loli.sombragris.org> Message-ID: On 10/31/16, Eduardo Sanchez wrote: > The issue is that there's no mention at all in the ChangeLog: > > https://slackbuilds.org/ChangeLog.txt You make a good point. That ChangeLog only goes back to July 2, 2016, which is when Slack 14.2 was released. The removed packages were removed before that (mid-January 2016). > There is no metion of any git log on any part of the SlackBuild website. > > Any user looking to maintain its system would be at a loss. Also good points. In theory, every user reads every line of Slackware's ChangeLog, so they'd know that package XYZ got added to Slackware & therefore won't be on SBo any more. But that's like saying every user has the time/energy/skill to read the source code of all open source software they use (just plain not true). Also for these particular packages, they aren't mentioned in the Slack ChangeLog (they became part of the perl package, but none of the perl-* entries mention the modules by name). > The question is: where should I follow the SlackBuilds.org changes: at > the ChangeLog which is published and advertised at the website, or at > some git log whose mention is nowhere on the SlackBuilds.org page? I can't answer that (I speak only for myself, not the SBo team). However... The git log is actually there on the site, just not obvious. At https://slackbuilds.org/repository/14.2/ there are links at the bottom: Access to the repository is available via: ftp git cgit http rsync The git log can be found in your browser by clicking on the cgit link... or by using git to clone the URL in the git link. But the site documentation (FAQ and HOWTO) don't mention this. And, if a user's not familiar with git and/or cgit, he might have a hard time finding what he's looking for. For your missing packages, you could enter the package name in the search box on the main cgit page... if that helps any in the future. It'd be nice to add this info to the FAQ.