From rworkman at slackbuilds.org Sat Feb 1 07:16:21 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 1 Feb 2014 07:16:21 +0000 Subject: [Slackbuilds-users] Updates - 20140201.1 Message-ID: <20140201071621.GA9898@slackbuilds.org> commit f342027404df4b0ca8959208b9a987d47c6916b6 Author: Robby Workman Date: Sat Feb 1 00:43:30 2014 -0600 Public www update: Sat Feb 1 06:42:26 UTC 2014 Sat Feb 1 06:42:26 UTC 2014 academic/amd: Renamed and moved from libraries academic/arpack-ng: Added (library for solving eigenvalue problems) academic/btf: Renamed and moved from libraries. academic/camd: Renamed and moved from libraries. academic/ccolamd: Renamed and moved from libraries. academic/cholmod: Renamed and moved from libraries. academic/colamd: Renamed and moved from libraries. academic/csparse: Renamed and moved from libraries. academic/cxsparse: Renamed and moved from libraries. academic/klu: Renamed and moved from libraries. academic/ldl: Renamed and moved from libraries. academic/octave: Updated for version 3.8.0. academic/rbio: Renamed and moved from libraries. academic/spqr: Renamed and moved from libraries. academic/suitesparseconfig: Renamed and moved from libraries. academic/umfpack: Renamed and moved from libraries. audio/easymp3gain: Added patches to fix compile against new FPC. desktop/cwp: Updated for version 1.10.0. desktop/icewm: Included some patches from Fedora and Gentoo desktop/xfce4-battery-plugin: Added (battery monitor panel plugin). desktop/xfce4-embed-plugin: Added (Embed arbitrary application). desktop/xfce4-eyes-plugin: Added (Eyes that spy on you). desktop/xfce4-fsguard-plugin: Added (Checks free space). development/Editra: Updated for version 0.7.20. development/golang-googlecode-gotools: Added (golang extra tools). development/google-go-lang: Unset BASH_ENV during build development/google-go-lang: Updated for version 1.2. development/robomongo: Updated for version 0.8.4. games/yae: Added (Yet another Apple Emulator). graphics/fotoxx: Updated for version 14.01.1. graphics/pyformex: Added (program to create 3D geometry). libraries/AMD: Updated for version 2.3.1. libraries/BTF: Updated for version 1.2.0. libraries/CAMD: Updated for version 2.3.1. libraries/CCOLAMD: Updated for version 2.8.0. libraries/CHOLMOD: Updated for version 2.1.2. libraries/COLAMD: Updated for version 2.8.0. libraries/CSparse: Updated for version 3.1.2. libraries/CXSparse: Upgraded for version 3.1.2. libraries/KLU: Updated for version 1.2.1. libraries/LDL: Updated for version 2.1.0. libraries/PyYAML: Updated for version 3.10. libraries/RBio: Updated for version 2.1.1. libraries/SPQR: Updated for version 1.3.1. libraries/SuiteSparse_config: Updated for version 4.2.1. libraries/UFconfig: Removed (renamed to SuiteSparse_config) libraries/UMFPACK: Updated for version 5.6.2. libraries/pgtcl-ng: Updated for version 2.1.0. multimedia/Poor-Mans-Spotify: Updated for version 0.18.38. network/ClusterSSH: Updated for version 4.02_03. network/Flootty: Added (Floobits collaborative terminal). network/asciinema: Added (Command line recorder for asciinema.org). network/httpie: Added (command line HTTP client). network/weathercli: Updated for version 2.3.1. office/abiword: Fix a segfault when trying save to pdf office/abiword: Fixed icon installation office/calibre: Updated for version 1.22.0. office/libreoffice-helppack: Updated for version 4.2.0. office/libreoffice-langpack: Updated for version 4.2.0. office/libreoffice: Updated for version 4.2.0. python/argcomplete: Updated for version 0.6.9. python/clint: Updated for version 0.3.4. python/msgpack-python: Added (MessagePack for Python) python/pip: Updated for version 1.5.2. python/py: Updated for version 1.4.20. python/pysetuptools: Updated for version 2.1. python/tox: Updated for version 1.7.0. python/virtualenv: Updated for version 1.11.2. system/Attic: Added (Deduplicated backups) system/em: Updated for version 0.3. system/fr: Updated for version 1.19. system/gdm: Update glibc crypt patch to fix segfaults system/homerun: Added (KDE launcher widgets) system/mongodb: Updated for version 2.4.9. system/rename: Fixed homepage. system/repeat: Added (Repeat command N times every S seconds). system/termenu: Added (Interactive in-line menus). system/xosd: Note that gdk-pixbuf causes build failure +--------------------------+ From rworkman at slackbuilds.org Sat Feb 1 07:21:23 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 1 Feb 2014 07:21:23 +0000 Subject: [Slackbuilds-users] RFC: gdm users Message-ID: <20140201072123.GB9898@slackbuilds.org> While I was updating the gdm build script with the updated crypt patch, another issue was brought to my attention, and while checking on that, I noticed yet another. Here are those two issues: 1) there are still a few files in /etc/X11/gdm/ that are not installed with .new suffixes, and thus any custom edits to them get overwritten with every package upgrade. 2) /etc/X11/gdm/ should really be /etc/gdm/ * gdm is not an X11 program, at least not in the context of the other things in /etc/X11/ (go on, have a look) * kdm uses /etc/kdm/ (okay, well, it really uses /usr/share/kdm/, but you get the point) :-) I plan to fix #1 in the next update, so you should probably back up your /etc/X11/gdm/ directory somewhere if you have made any custom changes to any of the non-.new'd files in there. The RFC in the subject is related to #2. I would like to change the config directory to /etc/gdm/ -- it's just a configure flag -- but I don't want to cause too much heartache. Is there a consensus among the gdm users on the list? -RW From rworkman at slackbuilds.org Sun Feb 2 08:31:32 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 2 Feb 2014 08:31:32 +0000 Subject: [Slackbuilds-users] Updates - 20140202.1 Message-ID: <20140202083132.GA21621@slackbuilds.org> commit 7f4c6a1a29aa1515a7ff859628f798e7eaf478c8 Author: Robby Workman Date: Sun Feb 2 02:11:32 2014 -0600 Public www update: Sun Feb 2 08:10:38 UTC 2014 Sun Feb 2 08:10:38 UTC 2014 academic/cld2: Updated for version 20140131. audio/minimodem: Added (software audio FSK modem). desktop/cheser-icon-theme: Removed (No SBo Maintainer). desktop/gtkman: Removed (No SBo Maintainer). desktop/jwm: Updated for version 2.2.0. development/KKEdit: Removed (No SBo Maintainer). development/bluefish: Updated for version 2.2.5. development/scite: Updated for version 3.3.9. games/Domination: Removed (No SBo Maintainer). games/qjoypad: Removed (No SBo Maintainer). gis/Fiona: Moved from Academic category. gis/OWSLib: Moved from Academic category. gis/SFCGAL: Moved from Libraries category. gis/Shapely: Moved from Academic category. gis/geogit: Moved from Academic category. gis/geopy: Moved from Python category. gis/geos: Moved from Libraries category. gis/geoserver-control-flow: Moved from Academic category. gis/geoserver-css: Moved from Academic category. gis/geoserver-pyramid: Moved from Academic category. gis/geoserver-wps: Moved from Academic category. gis/geoserver: Moved from Academic category. gis/horao: Moved from Academic category. gis/laszip: Moved from Libraries category. gis/mapnik: Moved from Academic category. gis/osm2pgrouting: Moved from Academic category. gis/osm2pgsql: Moved from Academic category. gis/pdal: Moved from Academic category. gis/pgrouting: Moved from Academic category. gis/pointcloud: Moved from Academic category. gis/postgis: Moved from System category. gis/proj: Moved from System category. gis/pyproj: Moved from Academic category. gis/qgis: Moved from Academic category. gis/rasterio: Moved from Academic category. gis/udig: Moved from Academic category. gis/xplanet: Moved from Desktop category. graphics/dcraw: Updated for version 0.9.20. graphics/digikam: Re-Added notes about broken lensfun deps. graphics/fritzing: Updated for version 0.8.7b. libraries/dbh: Removed (No SBo Maintainer). libraries/enum34: Updated for version 0.9.20. libraries/ffms2: Added (a cross-platform wrapper library) libraries/tff: Updated for version 0.2.8. libraries/tubo: Removed (No SBo Maintainer). libraries/wxGTK3: Fixed the broken wx-config symlink multimedia/ProjectX: Removed (No SBo Maintainer). multimedia/aegisub: Added (General-purpose subtitle editor) multimedia/mtvcgui: Removed (No SBo Maintainer). network/FireWorks: Updated for version 0.66. network/Pafy: Added (Python API for YouTube content). network/QuiteRSS: Updated for version 0.14.3. network/retroshare: Updated for version 0.5.5c. office/gnucash: Updated for version 2.6.1. office/sigil: Updated for version 0.7.4. perl/perl-Archive-Extract: Updated for version 0.72. perl/perl-Module-Pluggable: Updated for version 5.1. python/pycld2: Updated for version 20140131. system/the_silver_searcher: Updated for version 0.19.2. system/trachet: Updated for version 0.3.17. system/unetbootin: Updated for version 585. +--------------------------+ From rworkman at slackbuilds.org Sun Feb 2 08:32:06 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 2 Feb 2014 08:32:06 +0000 Subject: [Slackbuilds-users] Updates - 20140202.2 Message-ID: <20140202083206.GB21621@slackbuilds.org> commit 0bf98a97dccf36a8e928f3b54c6a0effd1b7fac2 Author: Robby Workman Date: Sun Feb 2 02:24:16 2014 -0600 Public www update: Sun Feb 2 08:23:34 UTC 2014 Sun Feb 2 08:23:34 UTC 2014 desktop/rodent-icon-theme: Removed (No SBo Maintainer). network/rt5370: Removed (No SBo Maintainer). network/smb4k: Removed (No SBo Maintainer). system/rodent: Removed (No SBo Maintainer). +--------------------------+ From islandmarmot at gmail.com Sun Feb 2 18:13:38 2014 From: islandmarmot at gmail.com (Paul McCormack) Date: Sun, 02 Feb 2014 10:13:38 -0800 Subject: [Slackbuilds-users] Darktable reports that it can't find rawspeed Message-ID: <52EE8AD2.7020704@gmail.com> I'm trying to get darktable or digikam to work with Fuji's raw (RAF) files. Rawstudio shows a corrupted image when I try to open a RAF file Darktable reports:- ------------------------------------------- bash-4.2$ darktable [rawspeed] No decoder found. Sorry. [rawspeed] No decoder found. Sorry. --------------------------------------------- I find this odd because as I understand it RawStudio is included in darktable. This is just after opening a NEF file without any problem. digikam - the image editor appears and the histogram panel appears with the message "loading image" then crashes. I'm using Slackware64 -current. These are what I think are the relevant packages. GraphicsMagick-1.3.17-x86_64-1_SBo LibRaw-0.15.4-x86_64-1_SBo darktable-1.4-x86_64-1_SBo dcraw-9.20-x86_64-1_SBo digikam-4.0.0-beta2-x86_64-1_SBo ffmpeg-2.1-x86_64_custom-1_SBo flickcurl-1.25-x86_64-1_SBo lensfun-0.2.8-x86_64-3_SBo luminance-hdr-2.3.1-x86_64-2_SBo opencv-2.4.7-x86_64-1_SBo openjpeg-1.5.1-x86_64-1_SBo rawstudio-2.0-x86_64-2_SBo ufraw-0.19.1-x86_64-1_SBo Gimp and ufraw open the raf files without a problem. So getting to the point - I feel like I've broken something around the rawspeed encoders as neither digikam (RawSpeed codec support = No) or darktable can open the raf files. Please understand I'm not looking for the fix just a pointer as my internet searching is either too technical or does not fix the problem. At this point in time I'm considering reinstalling 14.1 and going from there. P. From baildon.research at googlemail.com Sun Feb 2 14:54:26 2014 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 2 Feb 2014 14:54:26 +0000 Subject: [Slackbuilds-users] Darktable reports that it can't find rawspeed In-Reply-To: <52EE8AD2.7020704@gmail.com> References: <52EE8AD2.7020704@gmail.com> Message-ID: Hi Paul, > I'm trying to get darktable or digikam to work with Fuji's raw (RAF) files. At a wild guess, are they Fuji X-Pro1 files? Due to the sensor pattern, rawspeed (and hence darktable) does not support X-Pro1 .RAF files. See, for example, this mailing list thread: http://sourceforge.net/mailarchive/forum.php?thread_name=5273CD80.9060108%40meterprosekun.de&forum_name=darktable-devel As a workround, SBo's dcraw 9.20 can convert them to tiff, and then you can process the tiffs further with darktable. This command comes from the mailing list thread referenced above: > I use > dcraw -v -w -T -4 -m 5 -o 4 > to create linear tiffs, preserving more highlight information. Later I > apply a basecurve in dt. There's not much chance of proper support, see e.g. http://www.darktable.org/2012/10/whats-involved-with-adding-support-for-new-cameras/ "Darktable does not directly share much code with dcraw, and it can't since we do everything in 32 bit float instead of 16 bit integer. And besides that there are lots of modules in Darktable that operate directly on the Bayer data, which would all have to be adapted. This is not a priority for us. Sorry." As someone commented in that thread, "Nice hardware, unfortunate sensor decision" This isn't really good news, but at least you won't have to reinstall :-/ [ .RAF files from my ancient S9500 work ok in dt-1.4, but that camera died a year ago... ] -D. From willysr at slackbuilds.org Mon Feb 3 01:32:08 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 03 Feb 2014 08:32:08 +0700 Subject: [Slackbuilds-users] call for digikam tester Message-ID: <52EEF198.80905@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There has been some reports that digikam failed to build when lensfun is installed and i can confirm that by reproducing it using a minimum dependencies installed (only ffmpeg and opencv) This morning, i tried to rebuild digikam on a clean VM using all optional dependencies installed :lensfun, eigen3, liblqr, libpgf, libdc1394, and plus LibRaw (i don't know whether this has an effect or not), but it does built perfectly here can anyone test this on their VM? you might want to not use LibRaw first Thanks PS: the side effect is that probably i might add them all as hard-dep of digikam in the future - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLu8ZgACgkQiHuDdNczM4G4FQCgpqSUsbD4gsh+FG1uaurdl5Ve 6uQAnjFdoQnYnBuckpCvZRc+y1Qsul92 =TirK -----END PGP SIGNATURE----- From willysr at slackbuilds.org Mon Feb 3 03:55:25 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 03 Feb 2014 10:55:25 +0700 Subject: [Slackbuilds-users] call for digikam tester In-Reply-To: <52EEF198.80905@slackbuilds.org> References: <52EEF198.80905@slackbuilds.org> Message-ID: <52EF132D.4030205@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon 03 Feb 2014 08:32:08 AM WIT, Willy Sudiarto Raharjo wrote: > ********* *BEGIN ENCRYPTED or SIGNED PART* ********* > > There has been some reports that digikam failed to build when lensfun > is installed and i can confirm that by reproducing it using a minimum > dependencies installed (only ffmpeg and opencv) > > This morning, i tried to rebuild digikam on a clean VM using all > optional dependencies installed :lensfun, eigen3, liblqr, libpgf, > libdc1394, and plus LibRaw (i don't know whether this has an effect or > not), but it does built perfectly here I'm able to narrow it down after some testing on VM it seems that libpgf is still optional (it built even when this is removed), but liblqr will be needed when you want to build digikam against lensfun i'm still testing with eigen3 removed and then with libdc1394 removed - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLvEy0ACgkQiHuDdNczM4FNPgCeMH+8jemziTQj33iuPDJVbuhx uIIAoKKhOUxyXhtpu6BsBws19MzmvROV =EFsK -----END PGP SIGNATURE----- From larryhaja at gmail.com Mon Feb 3 04:39:30 2014 From: larryhaja at gmail.com (Larry Hajali) Date: Sun, 2 Feb 2014 20:39:30 -0800 Subject: [Slackbuilds-users] call for digikam tester In-Reply-To: <52EF132D.4030205@slackbuilds.org> References: <52EEF198.80905@slackbuilds.org> <52EF132D.4030205@slackbuilds.org> Message-ID: Hi Willy, I'm able to reproduce the error in a VM when I only have ffmpeg, opencv and lensfun installed. You are correct in you assumption that when lensfun is installed that liblqr is also needed. In the file digikam-3.5.0/core/cmake/modules/FindLqr-1.cmake, if the variables LQR-1_LIBRARY and LQR-1_INCLUDE_DIR are defined then the GLIB2 package is searched for. If GLIB2_FOUND is set, then both of the libraries (ie. liblqr and lensfun) are linked to libdigikamcore.so library as defined in the file dikigam-3.5.0/core/digikam/CMakeLists.txt using this block of code. # For Contents Aware Resizer and Lens auto-correction tools. IF(GLIB2_FOUND) TARGET_LINK_LIBRARIES(digikamcore ${GLIB2_LIBRARIES} ${liblqr_LIBS} ${liblensfun_LIBS}) ENDIF(GLIB2_FOUND) So the way I see it, both liblqr and lensfun are required for proper linking, otherwise, you get the undefined references for lensfun. --Larry On Sun, Feb 2, 2014 at 7:55 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon 03 Feb 2014 08:32:08 AM WIT, Willy Sudiarto Raharjo wrote: > > ********* *BEGIN ENCRYPTED or SIGNED PART* ********* > > > > There has been some reports that digikam failed to build when lensfun > > is installed and i can confirm that by reproducing it using a minimum > > dependencies installed (only ffmpeg and opencv) > > > > This morning, i tried to rebuild digikam on a clean VM using all > > optional dependencies installed :lensfun, eigen3, liblqr, libpgf, > > libdc1394, and plus LibRaw (i don't know whether this has an effect or > > not), but it does built perfectly here > > I'm able to narrow it down after some testing on VM > it seems that libpgf is still optional (it built even when this is > removed), but liblqr will be needed when you want to build digikam > against lensfun > > i'm still testing with eigen3 removed and then with libdc1394 removed > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlLvEy0ACgkQiHuDdNczM4FNPgCeMH+8jemziTQj33iuPDJVbuhx > uIIAoKKhOUxyXhtpu6BsBws19MzmvROV > =EFsK > -----END PGP SIGNATURE----- > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Feb 3 07:47:01 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 03 Feb 2014 14:47:01 +0700 Subject: [Slackbuilds-users] call for digikam tester In-Reply-To: References: <52EEF198.80905@slackbuilds.org> <52EF132D.4030205@slackbuilds.org> Message-ID: <52EF4975.9020300@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I'm able to reproduce the error in a VM when I only have ffmpeg, opencv and > lensfun installed. You are correct in you assumption that when lensfun is > installed that liblqr is also needed. > > In the file digikam-3.5.0/core/cmake/modules/FindLqr-1.cmake, if the > variables LQR-1_LIBRARY and LQR-1_INCLUDE_DIR are defined then the GLIB2 > package is searched for. If GLIB2_FOUND is set, then both of the libraries > (ie. liblqr and lensfun) are linked to libdigikamcore.so library as defined > in the file dikigam-3.5.0/core/digikam/CMakeLists.txt using this block of > code. > > # For Contents Aware Resizer and Lens auto-correction tools. > IF(GLIB2_FOUND) > TARGET_LINK_LIBRARIES(digikamcore ${GLIB2_LIBRARIES} ${liblqr_LIBS} > ${liblensfun_LIBS}) > ENDIF(GLIB2_FOUND) > > So the way I see it, both liblqr and lensfun are required for proper > linking, otherwise, you get the undefined references for lensfun. Thanks for confirming about this Larry i think i will make lensfun and liblqr hard dep for digikam to anticipate future releases any objection for this idea? - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLvSXUACgkQiHuDdNczM4EDZACfZKwGrji3T6br20pqeToZjsVQ AoQAn2w3bUn3iQtxiEl/mXS0OO6GxjDz =5dMY -----END PGP SIGNATURE----- From larryhaja at gmail.com Mon Feb 3 07:59:30 2014 From: larryhaja at gmail.com (Larry Hajali) Date: Sun, 2 Feb 2014 23:59:30 -0800 Subject: [Slackbuilds-users] call for digikam tester In-Reply-To: <52EF4975.9020300@slackbuilds.org> References: <52EEF198.80905@slackbuilds.org> <52EF132D.4030205@slackbuilds.org> <52EF4975.9020300@slackbuilds.org> Message-ID: > > Thanks for confirming about this Larry > i think i will make lensfun and liblqr hard dep for digikam to > anticipate future releases > any objection for this idea? > > No objections here. -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Tue Feb 4 16:16:41 2014 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 4 Feb 2014 16:16:41 +0000 Subject: [Slackbuilds-users] Updates - 20140202.1 In-Reply-To: <20140202083132.GA21621@slackbuilds.org> References: <20140202083132.GA21621@slackbuilds.org> Message-ID: Hi Robby, The new gis folder does not contain any of the tarballs (only the expanded folders) nor any of the .asc files for each tarball. Cheers Greg On 2 February 2014 08:31, Robby Workman wrote: > commit 7f4c6a1a29aa1515a7ff859628f798e7eaf478c8 > Author: Robby Workman > Date: Sun Feb 2 02:11:32 2014 -0600 > > Public www update: Sun Feb 2 08:10:38 UTC 2014 > > Sun Feb 2 08:10:38 UTC 2014 > academic/cld2: Updated for version 20140131. > audio/minimodem: Added (software audio FSK modem). > desktop/cheser-icon-theme: Removed (No SBo Maintainer). > desktop/gtkman: Removed (No SBo Maintainer). > desktop/jwm: Updated for version 2.2.0. > development/KKEdit: Removed (No SBo Maintainer). > development/bluefish: Updated for version 2.2.5. > development/scite: Updated for version 3.3.9. > games/Domination: Removed (No SBo Maintainer). > games/qjoypad: Removed (No SBo Maintainer). > gis/Fiona: Moved from Academic category. > gis/OWSLib: Moved from Academic category. > gis/SFCGAL: Moved from Libraries category. > gis/Shapely: Moved from Academic category. > gis/geogit: Moved from Academic category. > gis/geopy: Moved from Python category. > gis/geos: Moved from Libraries category. > gis/geoserver-control-flow: Moved from Academic category. > gis/geoserver-css: Moved from Academic category. > gis/geoserver-pyramid: Moved from Academic category. > gis/geoserver-wps: Moved from Academic category. > gis/geoserver: Moved from Academic category. > gis/horao: Moved from Academic category. > gis/laszip: Moved from Libraries category. > gis/mapnik: Moved from Academic category. > gis/osm2pgrouting: Moved from Academic category. > gis/osm2pgsql: Moved from Academic category. > gis/pdal: Moved from Academic category. > gis/pgrouting: Moved from Academic category. > gis/pointcloud: Moved from Academic category. > gis/postgis: Moved from System category. > gis/proj: Moved from System category. > gis/pyproj: Moved from Academic category. > gis/qgis: Moved from Academic category. > gis/rasterio: Moved from Academic category. > gis/udig: Moved from Academic category. > gis/xplanet: Moved from Desktop category. > graphics/dcraw: Updated for version 0.9.20. > graphics/digikam: Re-Added notes about broken lensfun deps. > graphics/fritzing: Updated for version 0.8.7b. > libraries/dbh: Removed (No SBo Maintainer). > libraries/enum34: Updated for version 0.9.20. > libraries/ffms2: Added (a cross-platform wrapper library) > libraries/tff: Updated for version 0.2.8. > libraries/tubo: Removed (No SBo Maintainer). > libraries/wxGTK3: Fixed the broken wx-config symlink > multimedia/ProjectX: Removed (No SBo Maintainer). > multimedia/aegisub: Added (General-purpose subtitle editor) > multimedia/mtvcgui: Removed (No SBo Maintainer). > network/FireWorks: Updated for version 0.66. > network/Pafy: Added (Python API for YouTube content). > network/QuiteRSS: Updated for version 0.14.3. > network/retroshare: Updated for version 0.5.5c. > office/gnucash: Updated for version 2.6.1. > office/sigil: Updated for version 0.7.4. > perl/perl-Archive-Extract: Updated for version 0.72. > perl/perl-Module-Pluggable: Updated for version 5.1. > python/pycld2: Updated for version 20140131. > system/the_silver_searcher: Updated for version 0.19.2. > system/trachet: Updated for version 0.3.17. > system/unetbootin: Updated for version 585. > +--------------------------+ > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Feb 4 16:25:57 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 04 Feb 2014 23:25:57 +0700 Subject: [Slackbuilds-users] Updates - 20140202.1 In-Reply-To: References: <20140202083132.GA21621@slackbuilds.org> Message-ID: <52F11495.9070100@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The new gis folder does not contain any of the tarballs (only the expanded > folders) nor any of the .asc files for each tarball. Erik fixed it just now - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLxFJUACgkQiHuDdNczM4GH/ACfZUZPSdthvBb0wPY6aR08t9XU yhgAoJEaK+wDqN1UAR5PGBXVeo4Zqtrc =/m36 -----END PGP SIGNATURE----- From baildon.research at googlemail.com Tue Feb 4 16:45:06 2014 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 4 Feb 2014 16:45:06 +0000 Subject: [Slackbuilds-users] New GIS category Message-ID: Yeah, about that new category :-) Can I nominate some of my apps and libraries to be moved to GIS please? (if asking here is the best way of having it done -- and hoping that other maintainers might care to add more) academic/grass libraries/gdal libraries/libgeotiff misc/foxtrotgps misc/viking Thanks! -D. From willysr at slackbuilds.org Tue Feb 4 16:55:11 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 04 Feb 2014 23:55:11 +0700 Subject: [Slackbuilds-users] New GIS category In-Reply-To: References: Message-ID: <52F11B6F.30305@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Yeah, about that new category :-) > > Can I nominate some of my apps and libraries to be moved to GIS > please? (if asking here is the best way of having it done -- and > hoping that other maintainers might care to add more) > > academic/grass > libraries/gdal > libraries/libgeotiff > misc/foxtrotgps > misc/viking Done in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLxG28ACgkQiHuDdNczM4GjKACgrJoO9U0GjJrDbk7q+NPrGtyy T8MAnjz+cGlfx0pg4Ylmdo7tyo3LnqGp =C0+y -----END PGP SIGNATURE----- From slackbuilds at jaxartes.net Tue Feb 4 21:07:29 2014 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 04 Feb 2014 13:07:29 -0800 Subject: [Slackbuilds-users] New GIS category In-Reply-To: <52F11B6F.30305@slackbuilds.org> References: <52F11B6F.30305@slackbuilds.org> Message-ID: <2019165.gzavpAIMgS@jerseybastion> On February 4, 2014 23:55:11 Willy Sudiarto Raharjo wrote: > > Yeah, about that new category :-) > > > > Can I nominate some of my apps and libraries to be moved to GIS > > please? (if asking here is the best way of having it done -- and > > hoping that other maintainers might care to add more) > > > > academic/grass > > libraries/gdal > > libraries/libgeotiff > > misc/foxtrotgps > > misc/viking > > Done in my branch Here are the remaining SlackBuilds that I would recommend as candidates for the GIS category (some are debatable): academic/opengrads/ academic/spatialite-tools/ desktop/josm/ desktop/qlandkartegt/ graphics/osgEarth/ libraries/CGAL/ libraries/librasterlite/ libraries/libspatialindex/ libraries/libspatialite/ libraries/readosm/ misc/merkaartor/ misc/tangogps/ multimedia/google-earth/ network/gmapcatcher/ system/gpsd/ From baildon.research at googlemail.com Tue Feb 4 22:00:44 2014 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 4 Feb 2014 22:00:44 +0000 Subject: [Slackbuilds-users] New GIS category In-Reply-To: <2019165.gzavpAIMgS@jerseybastion> References: <52F11B6F.30305@slackbuilds.org> <2019165.gzavpAIMgS@jerseybastion> Message-ID: On 4 February 2014 21:07, Benjamin Trigona-Harany wrote: > Here are the remaining SlackBuilds that I would recommend as candidates for > the GIS category (some are debatable): > libraries/CGAL/ Hm, ok! (It's also used by openscad. CGAL is due an update, but from an abundance of caution I've been holding it back until a new version of openscad comes along, however, if pgrouting/SFCGAL would benefit, let me know and I'll push the new CGAL immediately.) > system/gpsd/ There's an update (3.10) already submitted that includes a request to move to GIS ;-) [And of course Thanks to Willy for the earlier batch] -D. From slackbuilds at jaxartes.net Tue Feb 4 23:55:40 2014 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 04 Feb 2014 15:55:40 -0800 Subject: [Slackbuilds-users] New GIS category In-Reply-To: References: <2019165.gzavpAIMgS@jerseybastion> Message-ID: <2397537.eidhZk0mVE@jerseybastion> On February 4, 2014 22:00:44 David Spencer wrote: > On 4 February 2014 21:07, Benjamin Trigona-Harany > > wrote: > > Here are the remaining SlackBuilds that I would recommend as candidates > > for > > the GIS category (some are debatable): > > > > libraries/CGAL/ > > Hm, ok! (It's also used by openscad. CGAL is due an update, but from > an abundance of caution I've been holding it back until a new version > of openscad comes along, however, if pgrouting/SFCGAL would benefit, > let me know and I'll push the new CGAL immediately.) Just a thought, doesn't have to move if it has any application beyond GIS :) I don't believe pgRouting or SFCGAL would benefit from an the latest CGAL update, so no rush there. > > system/gpsd/ > > There's an update (3.10) already submitted that includes a request to > move to GIS ;-) Nice :) From rworkman at slackbuilds.org Wed Feb 5 06:27:37 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 5 Feb 2014 00:27:37 -0600 Subject: [Slackbuilds-users] Updates - 20140202.1 In-Reply-To: <52F11495.9070100@slackbuilds.org> References: <20140202083132.GA21621@slackbuilds.org> <52F11495.9070100@slackbuilds.org> Message-ID: <20140205002737.05e203aa@home.rlworkman.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 04 Feb 2014 23:25:57 +0700 Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > The new gis folder does not contain any of the tarballs (only the > > expanded folders) nor any of the .asc files for each tarball. > > Erik fixed it just now Hrm, not sure how I missed that - I thought I moved them into place manually. Now I wonder if they got put in the old category's dir? - -RW -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlLx2d0ACgkQvGy9tf6lsvvVFgCgh61z1cSxKHuooYCPLe3OwaKL 4LMAoIlqMhr0rmtoqQkFwp/O+hfopBGG =eMct -----END PGP SIGNATURE----- From titopoquito at gmail.com Thu Feb 6 09:59:28 2014 From: titopoquito at gmail.com (titopoquito) Date: Thu, 06 Feb 2014 10:59:28 +0100 Subject: [Slackbuilds-users] opencv and stevedore missing dependency Message-ID: <52F35D00.5000600@gmail.com> Hi all, today I compiled opencv from the 14.1 repository and the build stopped, complaining about missing "orc" files. So I guess that "orc" should be listed as opencv dependency. Something similar happened when compiling stevedore: It complained about missing pysetuptools. Could one of the admins please look at this? Many thanks, Tito From baildon.research at googlemail.com Thu Feb 6 11:03:38 2014 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 6 Feb 2014 11:03:38 +0000 Subject: [Slackbuilds-users] opencv and stevedore missing dependency In-Reply-To: <52F35D00.5000600@gmail.com> References: <52F35D00.5000600@gmail.com> Message-ID: > today I compiled opencv from the 14.1 repository and the build stopped, > complaining about missing "orc" files. So I guess that "orc" should be > listed as opencv dependency. opencv-2.4.7 with no optional deps builds ok here without orc. Is it maybe a weird side effect of building opencv with ffmpeg? Does the problem go away with opencv-2.4.8? (btw I have a completely different issue building opencv for nomacs. And the 2.4.8 source has suddenly become a zip file. If I was judgmental, I'd say upstream is a bit dodgy. But let's no go there today ;-) Cheerio -D. From matteo.bernardini at gmail.com Thu Feb 6 12:07:06 2014 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 6 Feb 2014 13:07:06 +0100 Subject: [Slackbuilds-users] opencv and stevedore missing dependency In-Reply-To: References: <52F35D00.5000600@gmail.com> Message-ID: 2014-02-06 David Spencer : > (btw I have a completely different issue building opencv for nomacs. > And the 2.4.8 source has suddenly become a zip file. If I was > judgmental, I'd say upstream is a bit dodgy. But let's no go there > today ;-) I have fixed it here and asked permission to daedra to submit the mods (the pkgconfig file is borked in opencv >= 2.4.7) together with the update to 2.4.8. It will be fixed soon also in our git (in the meantime I'll attach the patch) ;) Matteo -------------- next part -------------- A non-text attachment was scrubbed... Name: opencv.patch Type: text/x-diff Size: 3273 bytes Desc: not available URL: From willysr at slackbuilds.org Thu Feb 6 12:08:09 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 06 Feb 2014 19:08:09 +0700 Subject: [Slackbuilds-users] opencv and stevedore missing dependency In-Reply-To: <52F35D00.5000600@gmail.com> References: <52F35D00.5000600@gmail.com> Message-ID: <52F37B29.8080901@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Something similar happened when compiling stevedore: It complained > about missing pysetuptools. > > Could one of the admins please look at this? Yes, you are right it does miss the pysetuptools Fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLzeykACgkQiHuDdNczM4E0fACgiFDz9PcXbLIF/h367usuD9dQ nQUAnAsxReGQzcSHn1BMfxR/H6iEOMDB =CN4P -----END PGP SIGNATURE----- From titopoquito at gmail.com Thu Feb 6 19:44:45 2014 From: titopoquito at gmail.com (titopoquito) Date: Thu, 06 Feb 2014 20:44:45 +0100 Subject: [Slackbuilds-users] opencv and stevedore missing dependency In-Reply-To: References: <52F35D00.5000600@gmail.com> Message-ID: <52F3E62D.8090208@gmail.com> On 06.02.2014 12:03, David Spencer wrote: >> today I compiled opencv from the 14.1 repository and the build stopped, >> complaining about missing "orc" files. So I guess that "orc" should be >> listed as opencv dependency. > > opencv-2.4.7 with no optional deps builds ok here without orc. Is it > maybe a weird side effect of building opencv with ffmpeg? Does the > problem go away with opencv-2.4.8? You are right of course, many thanks for the hint. Yes, I was fooled by the way the dependencies are listed - sqg and sbopkg thought ffmpeg was needed. Guess I have to be careful when %README% is listed as dependency, lesson learned. Oh, and thanks to Matteo for the 2.4.8 patch! It's missing the change from tar.gz to zip, but besides that the newer version compiled without any problem with it applied. From titopoquito at gmail.com Thu Feb 6 21:44:56 2014 From: titopoquito at gmail.com (titopoquito) Date: Thu, 06 Feb 2014 22:44:56 +0100 Subject: [Slackbuilds-users] deadbeef (audio player) maintainership Message-ID: <52F40258.3030908@gmail.com> The version of the deadbeef audio player on SBo builds ok, but is quite outdated (2010). In August (2013) I wrote an email to the maintainer of the SlackBuild (alexgav) about that, but never got an answer. Any objections against me taking over maintainership for this one? Cheers, Tito From willysr at slackbuilds.org Fri Feb 7 00:33:55 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 07 Feb 2014 07:33:55 +0700 Subject: [Slackbuilds-users] deadbeef (audio player) maintainership In-Reply-To: <52F40258.3030908@gmail.com> References: <52F40258.3030908@gmail.com> Message-ID: <52F429F3.80308@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The version of the deadbeef audio player on SBo builds ok, but is > quite outdated (2010). In August (2013) I wrote an email to the > maintainer of the SlackBuild (alexgav) about that, but never got an > answer. > Any objections against me taking over maintainership for this one? Please submit an update and don't forget to leave a comment to notify us :) - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL0KfMACgkQiHuDdNczM4HzogCgrqMW+iZ9hzU93twuOo9rZ6dw C1oAoK0DqX907bKsrqdNYMNPKWXa5R+6 =WNok -----END PGP SIGNATURE----- From panych.y at gmail.com Fri Feb 7 08:42:39 2014 From: panych.y at gmail.com (Yaroslav Panych) Date: Fri, 7 Feb 2014 10:42:39 +0200 Subject: [Slackbuilds-users] deadbeef (audio player) maintainership In-Reply-To: <52F429F3.80308@slackbuilds.org> References: <52F40258.3030908@gmail.com> <52F429F3.80308@slackbuilds.org> Message-ID: I trying to contact maintainer now using jabber and shall ask him to check that e-mail. 2014-02-07 2:33 GMT+02:00 Willy Sudiarto Raharjo : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > The version of the deadbeef audio player on SBo builds ok, but is > > quite outdated (2010). In August (2013) I wrote an email to the > > maintainer of the SlackBuild (alexgav) about that, but never got an > > answer. > > Any objections against me taking over maintainership for this one? > > Please submit an update and don't forget to leave a comment to notify > us :) > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlL0KfMACgkQiHuDdNczM4HzogCgrqMW+iZ9hzU93twuOo9rZ6dw > C1oAoK0DqX907bKsrqdNYMNPKWXa5R+6 > =WNok > -----END PGP SIGNATURE----- > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Sat Feb 8 17:21:11 2014 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 8 Feb 2014 11:21:11 -0600 Subject: [Slackbuilds-users] Updates - 20140208.1 Message-ID: <20140208112111.09985c87@shaggy.doo> Sat Feb 8 17:12:07 UTC 2014 academic/octave: Remove Qt5 detection. academic/sage: Updated for version 6.1. academic/suiteparse: Updated README. audio/jack2: Added (Jack Sound Server). desktop/dwm: Clarify use of custom patches. desktop/superkey-launch: Updated for version 0.31. desktop/wminfo: Updated for version 4.1.2. development/apache-jmeter: Updated for version 2.11. development/brackets: Updated for version 36. development/kaaedit: Updated for version 0.36.0. development/mysql-workbench: Updated for version 6.1.1. development/racket: Updated for version 5.93. development/rstudio-desktop: Added (R Statistical IDE). gis/Fiona: Updated for version 1.1.1. gis/OWSLib: Updated for version 0.8.4. gis/foxtrotgps: Moved from Misc category. gis/gdal: Moved from Libraries category. gis/geopy: Updated for version 0.97.1. gis/geoserver-python: Added (GeoServer Python scripting support). gis/gpsd: Updated for version 3.10 + Moved from System category. gis/grass: Moved from Academic category. gis/libgeotiff: Moved from Libraries category. gis/viking: Moved from Misc category. graphics/digikam: Added liblqr and lensfun to REQUIRES. graphics/enblend-enfuse: Updated for version 4.1.2. graphics/hugin: Updated for version 2013.0.0. graphics/luminance-hdr: Updated for version 2.4.0. libraries/CCfits: Added (C++ wrappers for the cfitsio library) libraries/GitPython: Added (Python Git Library). libraries/LibRaw: Updated for version 0.16.0. libraries/async: Added (Async Framework). libraries/backports-ssl-match-hostname: Added (Backported SSL). libraries/boolstuff: Added (boolean expression tree toolkit). libraries/dropbox-python: Added (Official Dropbox REST API Client). libraries/enum34: Updated for version 0.9.21. libraries/evernote-python: Added (Evernote SDK for Python). libraries/facebook-python: Added (Client library for Facebook SDK). libraries/gallerize: Added (Web image gallery generator). libraries/gitdb: Added (Git Object Database). libraries/hurry-filesize: Added (Python library). libraries/isodate: Added (date/time/duration parser and formater). libraries/leptonica: Updated for version 1.70. libraries/liblogging: Added (an easy to use logging library). libraries/libnfs: Updated for version 1.9.2. libraries/librelp: Updated for version 1.2.2. libraries/libwebp: Updated for version 0.4.0. libraries/netcdf: Updated for version 4.3.1. libraries/pyftpdlib: Added (High-level asynchronous FTP library). libraries/pysendfile: Added (Interface to sendfile syscall). libraries/python-gnupg: Added (A wrapper for the GnuPG). libraries/python-xlrd: Added (extract data from MS Excel). libraries/rarfile: Added (RAR archive reader for Python). libraries/smmap: Added (Git implementation of memory map manager). libraries/tbb: Updated for version 4.2u2. libraries/uptime: Added (Cross-platform uptime library). multimedia/aegisub: Updated for version 3.1.2. multimedia/flashplayer-plugin: Updated for version 11.2.202.336. network/CherryMusic: Added (A music streaming server). network/Pafy: Updated for version 0.3.30. network/RYMTracks: Added (Tracklist Creator for RYM Service). network/aria2: Updated for version 1.18.3, new maintainer. network/cicb: Added (ICB client). network/pms-youtube: Added (Terminal based YouTube jukebox). network/twitter: Added(An API and command-line toolset for Twitter). network/vcspull: Added (mass-update vcs). office/hunspell-en: Added (English hunspell dictionaries). office/hunspell-es: Added (Spanish hunspell dictionaries). office/pyspread: Added (Python spreadsheet). python/frosted: Updated for version 1.3.2. python/kaptan: Added (Configuration Manager). python/lxml: Updated for version 3.3.0. python/pipdeptree: Added (show dependency tree of packages). python/pytest: Updated for version 2.5.2. python/requirements-detector: Added (find requirements of Python). python/selenium: Added (Python bindings for Selenium). python/stevedore: Added pysetuptools to REQUIRES. ruby/hub: Added (github helper) system/PySixel: Updated for version 0.1.7. system/clamav: Updated for version 0.98.1. system/docker: Added (manager for applications in linux containers) system/graphterm: Added (A Graphical Terminal Interface). system/quotatool: Added (filesystem quotas from command line). system/sentimental-skk: Updated for version 0.0.139. system/thinkfan: Added (fan control program). system/tmuxp: Added (Manage tmux sessions thru JSON, YAML configs). system/ttop: Added (CUI graphical system monitor). system/udiskie: Added (Removable disk automounter for udisks). -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From stefanicivan at gmail.com Sat Feb 8 20:07:11 2014 From: stefanicivan at gmail.com (Ivan Stefanic) Date: Sat, 8 Feb 2014 21:07:11 +0100 Subject: [Slackbuilds-users] docker build failure Message-ID: <20140208210711.b44237cb30e67c4f30b9e10d@gmail.com> Hi, I'm running Slackware64 14.1 and I cannot build docker. I am running Slackware64 14.1. I also had problems building google-go-lang, same as Antonio Hern?ndez Blas in another thread, but commenting out 'set -e' made it build. I don't know if this caused problems with docker but that's how my build differs from what it should be, and google-go-lang is a build-time dependency for docker. docker.Slackbuild output: chmod: cannot operate on dangling symlink './utils/testdata/fs/a/d' chmod: cannot operate on dangling symlink './utils/testdata/fs/a/f' patching file graphdriver/btrfs/btrfs.go # WARNING! I don't seem to be running in the Docker container. # The result of this command might be an incorrect build, and will not be # officially supported. # # Try this instead: make all # ---> Making bundle: dynbinary (in bundles/0.8.0/dynbinary) Created binary: /tmp/SBo/docker-0.8.0/bundles/0.8.0/dynbinary/dockerinit-0.8.0 # github.com/dotcloud/docker/graphdriver/btrfs ../package-docker/usr/share/gocode/src/github.com/dotcloud/docker/graphdriver/btrfs/btrfs.go:8:25: fatal error: btrfs/ioctl.h: No such file or directory #include ^ compilation terminated. End output. Any ideas? -- Ivan Stefanic From willysr at slackbuilds.org Sun Feb 9 01:35:33 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 09 Feb 2014 08:35:33 +0700 Subject: [Slackbuilds-users] docker build failure In-Reply-To: <20140208210711.b44237cb30e67c4f30b9e10d@gmail.com> References: <20140208210711.b44237cb30e67c4f30b9e10d@gmail.com> Message-ID: <52F6DB65.7010407@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > ../package-docker/usr/share/gocode/src/github.com/dotcloud/docker/graphdriver/btrfs/btrfs.go:8:25: fatal error: btrfs/ioctl.h: No such file or directory > #include > ^ > compilation terminated. > > End output. > > Any ideas? Have you installed kernel-headers and kernel-source? slackpkg file-search ioctl.h DONE The list below shows the packages that contains "ioctl\.h" file. [ Status ] [ Repository ] [ Package ] installed dev86-0.16.17-i486-1 installed kernel-headers-3.10.17_smp-x86-3 installed kernel-source-3.10.17_smp-noarch-3 installed glibc-2.17-i486-7 - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL222UACgkQiHuDdNczM4HKmQCbBMxBJsBCpoIhHFP3rvjjJt6G 0/cAnj9YafQ98vN6+ljt+yvhDQOYBNR8 =NRp6 -----END PGP SIGNATURE----- From mancha1 at hush.com Sun Feb 9 03:10:21 2014 From: mancha1 at hush.com (mancha) Date: Sun, 09 Feb 2014 03:10:21 +0000 Subject: [Slackbuilds-users] docker build failure Message-ID: <20140209031022.0A93560163@smtp.hushmail.com> On Sun, 09 Feb 2014 01:35:44 +0000 "Willy Sudiarto Raharjo" wrote: >> ../package- >docker/usr/share/gocode/src/github.com/dotcloud/docker/graphdriver/ >btrfs/btrfs.go:8:25: fatal error: btrfs/ioctl.h: No such file or >directory >> #include >> ^ >> compilation terminated. >> >> End output. >> >> Any ideas? > >Have you installed kernel-headers and kernel-source? > >slackpkg file-search ioctl.h > >DONE > >The list below shows the packages that contains "ioctl\.h" file. > >[ Status ] [ Repository ] [ Package > ] > installed >dev86-0.16.17-i486-1 > installed >kernel-headers-3.10.17_smp-x86-3 > installed >kernel-source-3.10.17_smp-noarch-3 > installed glibc-2.17- >i486-7 > > > >-- >Willy Sudiarto Raharjo Actually, I believe there's a small bug in docker.SlackBuild. The attached patch should make it all good. --mancha -------------- next part -------------- A non-text attachment was scrubbed... Name: docker.SlackBuild.diff Type: application/octet-stream Size: 733 bytes Desc: not available URL: From willysr at slackbuilds.org Sun Feb 9 03:46:00 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 09 Feb 2014 10:46:00 +0700 Subject: [Slackbuilds-users] docker build failure In-Reply-To: <20140209031022.0A93560163@smtp.hushmail.com> References: <20140209031022.0A93560163@smtp.hushmail.com> Message-ID: <52F6F9F8.3030805@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Actually, I believe there's a small bug in docker.SlackBuild. > The attached patch should make it all good. i just built docker fine here using sbopkg SUMMARY LOG Using the SBo repository for Slackware 14.1 Queue Process: Download, build, and install google-go-lang: MD5SUM check for go1.2.src.tar.gz ... OK Building package google-go-lang-1.2-i486-1_SBo.tgz ... OK Installing package google-go-lang-1.2-i486-1_SBo.tgz ... OK docker: MD5SUM check for v0.8.0.tar.gz ... OK Building package docker-0.8.0-i486-1_SBo.tgz ... OK Installing package docker-0.8.0-i486-1_SBo.tgz ... OK - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL2+fgACgkQiHuDdNczM4HUTACfd01mi3LAOaQLnVNu67Mcw2nD V6EAnjZTtcAItHzyZdIKPXkqvjryHTil =52jc -----END PGP SIGNATURE----- From mancha1 at hush.com Sun Feb 9 03:51:55 2014 From: mancha1 at hush.com (mancha) Date: Sun, 09 Feb 2014 03:51:55 +0000 Subject: [Slackbuilds-users] docker build failure Message-ID: <20140209035155.DDCE160161@smtp.hushmail.com> Doesn't work on Slackware64 14.1. On Sun, 09 Feb 2014 03:46:07 +0000 "Willy Sudiarto Raharjo" wrote: >> Actually, I believe there's a small bug in docker.SlackBuild. >> The attached patch should make it all good. > >i just built docker fine here using sbopkg >SUMMARY LOG >Using the SBo repository for Slackware 14.1 >Queue Process: Download, build, and install > >google-go-lang: > MD5SUM check for go1.2.src.tar.gz ... OK > Building package google-go-lang-1.2-i486-1_SBo.tgz ... OK > Installing package google-go-lang-1.2-i486-1_SBo.tgz ... OK > >docker: > MD5SUM check for v0.8.0.tar.gz ... OK > Building package docker-0.8.0-i486-1_SBo.tgz ... OK > Installing package docker-0.8.0-i486-1_SBo.tgz ... OK > > >-- >Willy Sudiarto Raharjo From stefanicivan at gmail.com Sun Feb 9 08:15:27 2014 From: stefanicivan at gmail.com (Ivan Stefanic) Date: Sun, 9 Feb 2014 09:15:27 +0100 Subject: [Slackbuilds-users] docker build failure In-Reply-To: <20140209031022.0A93560163@smtp.hushmail.com> References: <20140209031022.0A93560163@smtp.hushmail.com> Message-ID: <20140209091527.dd1594d8619ff1861d3612ee@gmail.com> On Sun, 09 Feb 2014 03:10:21 +0000 "mancha" wrote: > Actually, I believe there's a small bug in docker.SlackBuild. > The attached patch should make it all good. > Thank you mancha. This patch makes docker build properly. -- Ivan Stefanic From mancha1 at hush.com Sun Feb 9 08:18:49 2014 From: mancha1 at hush.com (mancha) Date: Sun, 09 Feb 2014 08:18:49 +0000 Subject: [Slackbuilds-users] docker build failure Message-ID: <20140209081849.7BF0260161@smtp.hushmail.com> On Sat, 08 Feb 2014 20:07:21 +0000 "Ivan Stefanic" wrote: >I am running Slackware64 14.1. I also had problems building google- >go-lang, >same as Antonio Hern?ndez Blas in another thread, but commenting >out >'set -e' made it build. I don't know if this caused problems with >docker >but that's how my build differs from what it should be, and google- >go-lang is >a build-time dependency for docker. > >docker.Slackbuild output: > >chmod: cannot operate on dangling symlink >'./utils/testdata/fs/a/d' >chmod: cannot operate on dangling symlink >'./utils/testdata/fs/a/f' >patching file graphdriver/btrfs/btrfs.go ># WARNING! I don't seem to be running in the Docker container. ># The result of this command might be an incorrect build, and will >not be ># officially supported. ># ># Try this instead: make all ># > >---> Making bundle: dynbinary (in bundles/0.8.0/dynbinary) >Created binary: /tmp/SBo/docker- >0.8.0/bundles/0.8.0/dynbinary/dockerinit-0.8.0 ># github.com/dotcloud/docker/graphdriver/btrfs >../package- >docker/usr/share/gocode/src/github.com/dotcloud/docker/graphdriver/ >btrfs/btrfs.go:8:25: fatal error: btrfs/ioctl.h: No such file or >directory > #include > ^ >compilation terminated. > >End output. > >Any ideas? > >-- >Ivan Stefanic Hi Vincent. On x86_64 the docker build process uses btrfs.go from $PKG but that copy is made prior to applying the btrfs reversion fix - triggering Ivan's build issue above. I've re-ordered things in docker.Slackbuild so source files get copied to $PKG post-patch (I think we want that anyways, regardless of build issues, right?). After this change it builds without errors on x86_64 but I don't use docker so I can't confirm what gets built works. Willy didn't have these issues when building on 32-bit x86 so it seems there it uses btrfs.go from /tmp/SBo/docker-0.8.0. Why 32-bit and 64-bit builds differ? No clue. Ideas? --mancha From willysr at slackbuilds.org Sun Feb 9 08:21:06 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 09 Feb 2014 15:21:06 +0700 Subject: [Slackbuilds-users] docker build failure In-Reply-To: <20140209081849.7BF0260161@smtp.hushmail.com> References: <20140209081849.7BF0260161@smtp.hushmail.com> Message-ID: <52F73A72.3050700@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > On x86_64 the docker build process uses btrfs.go from $PKG > but that copy is made prior to applying the btrfs reversion > fix - triggering Ivan's build issue above. > > I've re-ordered things in docker.Slackbuild so source files > get copied to $PKG post-patch (I think we want that anyways, > regardless of build issues, right?). > > After this change it builds without errors on x86_64 but I > don't use docker so I can't confirm what gets built works. > > Willy didn't have these issues when building on 32-bit x86 > so it seems there it uses btrfs.go from /tmp/SBo/docker-0.8.0. > Why 32-bit and 64-bit builds differ? No clue. Ideas? Anyway, the patch has been applied in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL3OnIACgkQiHuDdNczM4GDiQCfb9tcQQ8rdHMLZy9qPyeadMQT hXkAn3QpNGM3gt2pCFy8JKf7fQg7fdq3 =9Nab -----END PGP SIGNATURE----- From vbatts at gmail.com Sun Feb 9 08:32:22 2014 From: vbatts at gmail.com (Vincent Batts) Date: Sun, 9 Feb 2014 03:32:22 -0500 Subject: [Slackbuilds-users] docker build failure In-Reply-To: <20140209081849.7BF0260161@smtp.hushmail.com> References: <20140209081849.7BF0260161@smtp.hushmail.com> Message-ID: On Sun, Feb 9, 2014 at 3:18 AM, mancha wrote: > On Sat, 08 Feb 2014 20:07:21 +0000 "Ivan Stefanic" wrote: > >I am running Slackware64 14.1. I also had problems building google- > >go-lang, > >same as Antonio Hern?ndez Blas in another thread, but commenting > >out > >'set -e' made it build. I don't know if this caused problems with > >docker > >but that's how my build differs from what it should be, and google- > >go-lang is > >a build-time dependency for docker. > > > >docker.Slackbuild output: > > > >chmod: cannot operate on dangling symlink > >'./utils/testdata/fs/a/d' > >chmod: cannot operate on dangling symlink > >'./utils/testdata/fs/a/f' > >patching file graphdriver/btrfs/btrfs.go > ># WARNING! I don't seem to be running in the Docker container. > ># The result of this command might be an incorrect build, and will > >not be > ># officially supported. > ># > ># Try this instead: make all > ># > > > >---> Making bundle: dynbinary (in bundles/0.8.0/dynbinary) > >Created binary: /tmp/SBo/docker- > >0.8.0/bundles/0.8.0/dynbinary/dockerinit-0.8.0 > ># github.com/dotcloud/docker/graphdriver/btrfs > >../package- > >docker/usr/share/gocode/src/github.com/dotcloud/docker/graphdriver/ > >btrfs/btrfs.go:8:25: fatal error: btrfs/ioctl.h: No such file or > >directory > > #include > > ^ > >compilation terminated. > > > >End output. > > > >Any ideas? > > > >-- > >Ivan Stefanic > > Hi Vincent. > > On x86_64 the docker build process uses btrfs.go from $PKG > but that copy is made prior to applying the btrfs reversion > fix - triggering Ivan's build issue above. > > I've re-ordered things in docker.Slackbuild so source files > get copied to $PKG post-patch (I think we want that anyways, > regardless of build issues, right?). > > After this change it builds without errors on x86_64 but I > don't use docker so I can't confirm what gets built works. > > Willy didn't have these issues when building on 32-bit x86 > so it seems there it uses btrfs.go from /tmp/SBo/docker-0.8.0. > Why 32-bit and 64-bit builds differ? No clue. Ideas? > > --mancha Ah, good catch. It built fine for me on my x86_64 machine. Regardless, it is a good change to have it reordered like you have. vb -------------- next part -------------- An HTML attachment was scrubbed... URL: From islandmarmot at gmail.com Sun Feb 9 17:04:18 2014 From: islandmarmot at gmail.com (Paul McCormack) Date: Sun, 09 Feb 2014 09:04:18 -0800 Subject: [Slackbuilds-users] Darktable reports that it can't find rawspeed Message-ID: <52F7B512.1020207@gmail.com> Hey David, It's an X-E1. :( Thanks for explaining. I did a lot of searching and reading but got lost in the timelines and various different Libs/programs etc. Thanks for your advice. This is a truly beautiful camera with astonishing output. Anyway, before Robbie "coughs" I'll just say that I'm glad this is in the mailing list so others can see it. thanks. P. Hi Paul, > I'm trying to get darktable or digikam to work with Fuji's raw (RAF) files. At a wild guess, are they Fuji X-Pro1 files? Due to the sensor pattern, rawspeed (and hence darktable) does not support X-Pro1 .RAF files. See, for example, this mailing list thread: http://sourceforge.net/mailarchive/forum.php?thread_name=5273CD80.9060108%40meterprosekun.de&forum_name=darktable-devel As a workround, SBo's dcraw 9.20 can convert them to tiff, and then you can process the tiffs further with darktable. This command comes from the mailing list thread referenced above: > I use > dcraw -v -w -T -4 -m 5 -o 4 > to create linear tiffs, preserving more highlight information. Later I > apply a basecurve in dt. There's not much chance of proper support, see e.g. http://www.darktable.org/2012/10/whats-involved-with-adding-support-for-new-cameras/ "Darktable does not directly share much code with dcraw, and it can't since we do everything in 32 bit float instead of 16 bit integer. And besides that there are lots of modules in Darktable that operate directly on the Bayer data, which would all have to be adapted. This is not a priority for us. Sorry." As someone commented in that thread, "Nice hardware, unfortunate sensor decision" This isn't really good news, but at least you won't have to reinstall :-/ [ .RAF files from my ancient S9500 work ok in dt-1.4, but that camera died a year ago... ] -D. From baildon.research at googlemail.com Sun Feb 9 15:11:44 2014 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 9 Feb 2014 15:11:44 +0000 Subject: [Slackbuilds-users] Darktable reports that it can't find rawspeed In-Reply-To: <52F7B512.1020207@gmail.com> References: <52F7B512.1020207@gmail.com> Message-ID: > It's an X-E1. :( > This is a truly beautiful camera with astonishing > output. It's your lucky week :) Coincidentally there's been a new thread about it on the dt developers' mailing list. Support *is* now being worked on for both darktable and rawspeed (yay!) although obviously will take a while to hit stable releases: http://sourceforge.net/mailarchive/forum.php?thread_name=1391620845.14483.79707781.7631C2A1%40webmail.messagingengine.com&forum_name=darktable-devel But yeah, you're right, now that we've left a trail about this issue on the mailing list, we'd better quit the chitchat :D -D. From rworkman at slackbuilds.org Sun Feb 9 16:07:13 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 9 Feb 2014 10:07:13 -0600 Subject: [Slackbuilds-users] Darktable reports that it can't find rawspeed In-Reply-To: References: <52F7B512.1020207@gmail.com> Message-ID: <20140209100713.6d30a63e@home.rlworkman.net> On Sun, 9 Feb 2014 15:11:44 +0000 David Spencer wrote: > > It's an X-E1. :( > > This is a truly beautiful camera with astonishing > > output. > > It's your lucky week :) > Coincidentally there's been a new thread about it on the dt > developers' mailing list. Support *is* now being worked on for both > darktable and rawspeed (yay!) although obviously will take a while to > hit stable releases: > > http://sourceforge.net/mailarchive/forum.php?thread_name=1391620845.14483.79707781.7631C2A1%40webmail.messagingengine.com&forum_name=darktable-devel > > But yeah, you're right, now that we've left a trail about this issue > on the mailing list, we'd better quit the chitchat :D If this is what you call off-topic, then you're much more sensitive to it than I am. No coughing for me. :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From erik at slackbuilds.org Tue Feb 11 18:23:21 2014 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 11 Feb 2014 12:23:21 -0600 Subject: [Slackbuilds-users] Updates - 20140211.1 Message-ID: <20140211122321.52984d98@shaggy.doo> Tue Feb 11 18:16:35 UTC 2014 audio/lv2file: Added (apply lv2 plugins to audio files). audio/rev-plugins: Added (LADSPA reverb plugin). desktop/dwm: Added xinitrc.dwm. development/curlpp: Added (C++ wrapper for libcURL). games/connectagram: Updated for version 1.1.2. graphics/converseen: Added (image converter and resizer). graphics/pygraphviz: Added (Python interface to Graphviz). graphics/qiv: Updated for version 2.3.1. libraries/PySoundCard: Updated for version 0.4.4. libraries/Pykka: Added (A Python implementation of the actor model). libraries/libearth: Updated for version 0.1.2. libraries/musicbrainzngs: Updated for version 0.5. libraries/pies2overrides: Updated for version 2.6.0. libraries/pies: Updated for version 2.6.0. libraries/tff: Updated for version 0.2.9. libraries/ws4py: Added (WebSocket library for Python). multimedia/OpenLP: Updated for version 2.0.4. multimedia/Poor-Mans-Spotify: Updated for version 0.18.40. multimedia/gpodder: Updated for version 3.5.2. network/Pafy: Updated for version 0.3.33. network/asciinema: Updated for version 0.9.8. network/filezilla: Updated for version 3.7.4. network/gmapcatcher: Updated for version 0.8.0.4. network/pms-youtube: Updated for version 0.01.12. network/tornado: Updated for version 3.2. network/twitter: Updated for version 1.12.1. network/vcspull: Updated for version 0.0.8.4. network/weechat: Updated for version 0.4.3. network/you-get: Added (video downloader). perl/perl-Capture-Tiny: Updated for version 0.24. perl/perl-Dist-CheckConflicts: Added dep perl-Module-Runtime. perl/perl-Import-Into: Added (import packages into other packages). perl/perl-Module-Build-Tiny: Updated for version 0.034. perl/perl-Moo: Updated for version 1.004002. perl/perl-Test-Harness: Avoid overlap with Slackware's perl package. python/frosted: Updated for version 1.3.3. python/httplib2: Added patches for ssl. python/piprot: Added (Command line utility to show requirements). python/pySmartDL: Updated for version 1.2.0. system/Attic: Fixed VERSION. system/asbt: Added (Managing SBo packages in local repository). system/barman: Updated for version 1.3.0. system/docker: Reorder build process system/hime: Added (input method). system/makepasswd: Updated for version 0.5.3. system/rsyslog: Updated for version 7.4.9. system/sentimental-skk: Updated for version 0.0.141. system/termsaver: Updated VERSION in .info. system/thermal_daemon: Updated for version 1.1. system/tmuxp: Updated for version 0.1.6. +--------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From petar.petrov at student.oulu.fi Wed Feb 12 19:51:24 2014 From: petar.petrov at student.oulu.fi (Petar Petrov) Date: Wed, 12 Feb 2014 19:51:24 +0000 Subject: [Slackbuilds-users] io_lib location In-Reply-To: <20140211122321.52984d98@shaggy.doo> References: <20140211122321.52984d98@shaggy.doo> Message-ID: guys, the website lists io_lib in Academic, but the tarball with the script is still in http://slackbuilds.org/slackbuilds/14.1/libraries/io_lib.tar.gz If you go here: http://slackbuilds.org/repository/14.1/academic/io_lib/ you cannot download io_lib.tar.gz i guess you decided to move it to the Academic category and something got messed up... -petar From willysr at slackbuilds.org Thu Feb 13 01:22:57 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 13 Feb 2014 08:22:57 +0700 Subject: [Slackbuilds-users] io_lib location In-Reply-To: References: <20140211122321.52984d98@shaggy.doo> Message-ID: <52FC1E71.4070307@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > the website lists io_lib in Academic, but the tarball with the script is still in > http://slackbuilds.org/slackbuilds/14.1/libraries/io_lib.tar.gz > > If you go here: > http://slackbuilds.org/repository/14.1/academic/io_lib/ > you cannot download io_lib.tar.gz > > i guess you decided to move it to the Academic category and something got messed up... Done it should be placed under libraries now - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL8HnEACgkQiHuDdNczM4GiIwCeOY7mtvJptqm5zWAs94d8W6Bb QOQAn23H2G18QEkF1NdqFc6TlMBRGDRU =tqGd -----END PGP SIGNATURE----- From nick at linicks.net Thu Feb 13 18:07:29 2014 From: nick at linicks.net (Nick Warne) Date: Thu, 13 Feb 2014 18:07:29 +0000 Subject: [Slackbuilds-users] Alternative builds - Qxw In-Reply-To: <52FC1E71.4070307@slackbuilds.org> References: <20140211122321.52984d98@shaggy.doo> <52FC1E71.4070307@slackbuilds.org> Message-ID: <52FD09E1.7020009@linicks.net> The excellent crossword construction program I maintain and use has been updated - but the author has stated this release is bleeding edge: http://www.quinapalus.com/qxwdownload.html Can I submit a new Slackbuild with this version along side the stable build? Thanks, Nick -- "A bug in the code is worth two in the documentation." FSF Associate Member 5508 http://linicks.net/ http://pi.linicks.net/ From willysr at slackbuilds.org Thu Feb 13 18:15:39 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Feb 2014 01:15:39 +0700 Subject: [Slackbuilds-users] Alternative builds - Qxw In-Reply-To: <52FD09E1.7020009@linicks.net> References: <20140211122321.52984d98@shaggy.doo> <52FC1E71.4070307@slackbuilds.org> <52FD09E1.7020009@linicks.net> Message-ID: <52FD0BCB.6040209@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri 14 Feb 2014 01:07:29 AM WIT, Nick Warne wrote: > The excellent crossword construction program I maintain and use has > been updated - but the author has stated this release is bleeding edge: > > http://www.quinapalus.com/qxwdownload.html > > Can I submit a new Slackbuild with this version along side the stable > build? We only accept one version per package, unless it's a special case where certain other application requires a spesific version (goffice/goffice8, guile/guile1.8) About which version you want to submit, it's up to you as the maintainer - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL9C8sACgkQiHuDdNczM4FFsQCfYSdSZqTEakFo+xw3T6MiSSSa g6cAoJUqGyvhiHBw6glT2QXFS2GNogSN =KNQ/ -----END PGP SIGNATURE----- From nick at linicks.net Thu Feb 13 18:50:26 2014 From: nick at linicks.net (Nick Warne) Date: Thu, 13 Feb 2014 18:50:26 +0000 Subject: [Slackbuilds-users] Alternative builds - Qxw In-Reply-To: <52FD0BCB.6040209@slackbuilds.org> References: <20140211122321.52984d98@shaggy.doo> <52FC1E71.4070307@slackbuilds.org> <52FD09E1.7020009@linicks.net> <52FD0BCB.6040209@slackbuilds.org> Message-ID: <52FD13F2.6010302@linicks.net> Willy Sudiarto Raharjo wrote, On 13/02/14 18:15: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri 14 Feb 2014 01:07:29 AM WIT, Nick Warne wrote: >> The excellent crossword construction program I maintain and use has >> been updated - but the author has stated this release is bleeding edge: >> >> http://www.quinapalus.com/qxwdownload.html >> >> Can I submit a new Slackbuild with this version along side the stable >> build? > > We only accept one version per package, unless it's a special case > where certain other application requires a spesific version > (goffice/goffice8, guile/guile1.8) > About which version you want to submit, it's up to you as the maintainer OK, thanks, just spoke to the author, and he happy with that until it becomes a stable release. Nick -- "A bug in the code is worth two in the documentation." FSF Associate Member 5508 http://linicks.net/ http://pi.linicks.net/ From mancha1 at hush.com Thu Feb 13 22:22:20 2014 From: mancha1 at hush.com (mancha) Date: Thu, 13 Feb 2014 22:22:20 +0000 Subject: [Slackbuilds-users] libgksu on x86_64 (Slackware64 14.1) Message-ID: <20140213222221.2AF2060160@smtp.hushmail.com> Hi Stylianos. Based on a report on LQ, I discovered an issue with SBo's libgksu when built on x86_64 (i.e. Slackware64 14.1). The SBo libgksu package places gksu-run-helper under /usr/lib64 but the library hard-codes its search path as /usr/lib. The end result is gksu fails when it tries to run the run-helper because /usr/lib/libgksu/gksu-run-helper doesn't exist. The attached patch along with the edit to the SlackBuild below will remedy things. --mancha ===== --- libgksu.SlackBuild.SBo +++ libgksu.SlackBuild @@ -79,6 +79,11 @@ patch -p0 < $CWD/patches/libgksu-2.0.12- patch -p1 < $CWD/patches/libgksu-2.0.12-notests.patch patch -p1 < $CWD/patches/libgksu-2.0.12-automake-1.11.2.patch +# Patch from mancha +if [ "$ARCH" = "x86_64" ]; then + patch -p1 < $CWD/patches/libgksu-2.0.12-x86_64-path.diff +fi + touch NEWS README libtoolize --force --copy --install autoreconf -------------- next part -------------- A non-text attachment was scrubbed... Name: libgksu-2.0.12-x86_64-path.diff Type: application/octet-stream Size: 680 bytes Desc: not available URL: From yalhcru at gmail.com Fri Feb 14 00:00:16 2014 From: yalhcru at gmail.com (B Watson) Date: Thu, 13 Feb 2014 19:00:16 -0500 Subject: [Slackbuilds-users] Alternative builds - Qxw In-Reply-To: <52FD09E1.7020009@linicks.net> References: <20140211122321.52984d98@shaggy.doo> <52FC1E71.4070307@slackbuilds.org> <52FD09E1.7020009@linicks.net> Message-ID: On 2/13/14, Nick Warne wrote: > Can I submit a new Slackbuild with this version along side the stable > build? My 2 cents worth (I'm no admin or anything): If the build process hasn't changed too much, you could submit a script that by default builds the stable version, but is smart enough to build the unstable if the user sets VERSION in the environment (and you could mention that in the README). If the build process is identical, putting something like this in the script (if you don't already have it) would be enough: VERSION=${VERSION:-1.2.3} That's a standard thing to do already, the only non-standard thing you'd be doing is putting a comment in the README. From willysr at slackbuilds.org Fri Feb 14 03:34:38 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Feb 2014 10:34:38 +0700 Subject: [Slackbuilds-users] libgksu on x86_64 (Slackware64 14.1) In-Reply-To: <20140213222221.2AF2060160@smtp.hushmail.com> References: <20140213222221.2AF2060160@smtp.hushmail.com> Message-ID: <52FD8ECE.7040401@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The end result is gksu fails when it tries to run the run-helper > because /usr/lib/libgksu/gksu-run-helper doesn't exist. > > The attached patch along with the edit to the SlackBuild below > will remedy things. > > --mancha > > ===== > > --- libgksu.SlackBuild.SBo > +++ libgksu.SlackBuild > @@ -79,6 +79,11 @@ patch -p0 < $CWD/patches/libgksu-2.0.12- > patch -p1 < $CWD/patches/libgksu-2.0.12-notests.patch > patch -p1 < $CWD/patches/libgksu-2.0.12-automake-1.11.2.patch > > +# Patch from mancha > +if [ "$ARCH" = "x86_64" ]; then > + patch -p1 < $CWD/patches/libgksu-2.0.12-x86_64-path.diff > +fi > + > touch NEWS README > libtoolize --force --copy --install > autoreconf Fixed in my branch commit 5080951eec93da7758ab664ea70628e253044e53 Author: mancha Date: Fri Feb 14 10:33:59 2014 +0700 libraries/libgksu: Fixed helper path on x86_64. Signed-off-by: Willy Sudiarto Raharjo - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL9js4ACgkQiHuDdNczM4E1eQCdHcFnngfe5VOu/CaIT/sm2rfn RhcAni5uDaXvlrhhK9J4GFug7mXv6aHv =vB9N -----END PGP SIGNATURE----- From mancha1 at hush.com Fri Feb 14 03:52:02 2014 From: mancha1 at hush.com (mancha) Date: Fri, 14 Feb 2014 03:52:02 +0000 (UTC) Subject: [Slackbuilds-users] =?utf-8?q?libgksu_on_x86=5F64_=28Slackware64_?= =?utf-8?b?MTQuMSk=?= References: <20140213222221.2AF2060160@smtp.hushmail.com> <52FD8ECE.7040401@slackbuilds.org> Message-ID: Willy Sudiarto Raharjo writes: > > > > The end result is gksu fails when it tries to run the run-helper > > because /usr/lib/libgksu/gksu-run-helper doesn't exist. > > > > The attached patch along with the edit to the SlackBuild below > > will remedy things. > > > > --mancha > > Fixed in my branch > commit 5080951eec93da7758ab664ea70628e253044e53 > Author: mancha > Date: Fri Feb 14 10:33:59 2014 +0700 > > libraries/libgksu: Fixed helper path on x86_64. > > Signed-off-by: Willy Sudiarto Raharjo > > -- > Willy Sudiarto Raharjo > Hi Willy. Small correction needed in the commit. libgksu-2.0.12-x86_64-path.diff should be in "patches". Thanks. --mancha From willysr at slackbuilds.org Fri Feb 14 04:04:17 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Feb 2014 11:04:17 +0700 Subject: [Slackbuilds-users] libgksu on x86_64 (Slackware64 14.1) In-Reply-To: References: <20140213222221.2AF2060160@smtp.hushmail.com> <52FD8ECE.7040401@slackbuilds.org> Message-ID: <52FD95C1.8090402@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Small correction needed in the commit. libgksu-2.0.12-x86_64-path.diff > should be in "patches". Thanks Fixed now http://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=9dd7ddc97975d3a4503bd56e862fd6e6667b739b - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL9lcEACgkQiHuDdNczM4H0jACeJywi4IuEWF/8EMkTohjoJMp2 3gwAoIDo8i6muBFzTZmfQB3Y82Z84Ije =DOA0 -----END PGP SIGNATURE----- From nick at linicks.net Fri Feb 14 11:26:46 2014 From: nick at linicks.net (Nick Warne) Date: Fri, 14 Feb 2014 11:26:46 +0000 Subject: [Slackbuilds-users] Alternative builds - Qxw In-Reply-To: References: <20140211122321.52984d98@shaggy.doo> <52FC1E71.4070307@slackbuilds.org> <52FD09E1.7020009@linicks.net> Message-ID: <52FDFD76.9030203@linicks.net> B Watson wrote, On 14/02/14 00:00: > On 2/13/14, Nick Warne wrote: >> Can I submit a new Slackbuild with this version along side the stable >> build? > > My 2 cents worth (I'm no admin or anything): > > If the build process hasn't changed too much, you could submit a script > that by default builds the stable version, but is smart enough to build > the unstable if the user sets VERSION in the environment (and you could > mention that in the README). > > If the build process is identical, putting something like this in the > script (if you don't already have it) would be enough: > > VERSION=${VERSION:-1.2.3} > > That's a standard thing to do already, the only non-standard thing you'd > be doing is putting a comment in the README. That's a good idea, but how would it work for the .info file with two download URLs and md5sums? Nick -- "A bug in the code is worth two in the documentation." FSF Associate Member 5508 http://linicks.net/ http://pi.linicks.net/ From willysr at slackbuilds.org Fri Feb 14 12:24:41 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Feb 2014 19:24:41 +0700 Subject: [Slackbuilds-users] Alternative builds - Qxw In-Reply-To: <52FDFD76.9030203@linicks.net> References: <20140211122321.52984d98@shaggy.doo> <52FC1E71.4070307@slackbuilds.org> <52FD09E1.7020009@linicks.net> <52FDFD76.9030203@linicks.net> Message-ID: <52FE0B09.9060001@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > That's a good idea, but how would it work for the .info file with two > download URLs and md5sums? the info file will not be used if the user download the source manually and override the VERSION variable from terminal, such as VERSION=1.2.3 sh ./qxw.SlackBuild - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL+CwkACgkQiHuDdNczM4FIrQCdFQXIuWdsfQFxjmpEuJo78tuC vBgAoI67xnxzIxVMHZFbsKzEPaytFUre =M2iT -----END PGP SIGNATURE----- From nick at linicks.net Fri Feb 14 15:18:16 2014 From: nick at linicks.net (Nick Warne) Date: Fri, 14 Feb 2014 15:18:16 +0000 Subject: [Slackbuilds-users] Fwd: Re: Alternative builds - Qxw In-Reply-To: <52FE2DF9.4070800@linicks.net> References: <52FE2DF9.4070800@linicks.net> Message-ID: <52FE33B8.3040407@linicks.net> Sorry - meant to reply to list... -------- Original Message -------- Willy Sudiarto Raharjo wrote, On 14/02/14 12:24: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >> That's a good idea, but how would it work for the .info file with two >> download URLs and md5sums? > > the info file will not be used if the user download the source manually > and override the VERSION variable from terminal, such as > VERSION=1.2.3 sh ./qxw.SlackBuild Ah, OK. So I resubmit the same build, BUT include that using the override VERSION can be used to get the updated code? Nick -- "A bug in the code is worth two in the documentation." FSF Associate Member 5508 http://linicks.net/ http://pi.linicks.net/ From yalhcru at gmail.com Fri Feb 14 20:50:59 2014 From: yalhcru at gmail.com (B Watson) Date: Fri, 14 Feb 2014 15:50:59 -0500 Subject: [Slackbuilds-users] Fwd: Re: Alternative builds - Qxw In-Reply-To: <52FE33B8.3040407@linicks.net> References: <52FE2DF9.4070800@linicks.net> <52FE33B8.3040407@linicks.net> Message-ID: On 2/14/14, Nick Warne wrote: > Ah, OK. So I resubmit the same build, BUT include that using the > override VERSION can be used to get the updated code? Yep. And in the README, you can include the URL and md5sum of the unstable code. From willysr at slackbuilds.org Fri Feb 14 22:43:29 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Feb 2014 05:43:29 +0700 Subject: [Slackbuilds-users] Fwd: Re: Alternative builds - Qxw In-Reply-To: References: <52FE2DF9.4070800@linicks.net> <52FE33B8.3040407@linicks.net> Message-ID: <85EBE4C5-3B1D-4FE6-91DC-482A1E5A8866@slackbuilds.org> > > Yep. And in the README, you can include the URL and md5sum of the > unstable code. No need to do that The README should give information to the current release only Overriding VERSION variable is just a flexibility of SlackBuild script :) -- Willy Sudiarto Raharjo From yalhcru at gmail.com Fri Feb 14 23:45:02 2014 From: yalhcru at gmail.com (B Watson) Date: Fri, 14 Feb 2014 18:45:02 -0500 Subject: [Slackbuilds-users] submit fail Message-ID: "There was a problem with your upload. Please check the file and try again. If the problem persists, contact an admin." No details on what the problem might be. Was trying to upload dungeon.tar.gz, around 23:40 GMT. My fault or the server's? From erik at slackbuilds.org Sat Feb 15 00:01:16 2014 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 14 Feb 2014 18:01:16 -0600 Subject: [Slackbuilds-users] submit fail In-Reply-To: References: Message-ID: <20140214180116.6ae2025d@shaggy.doo> On Fri, 14 Feb 2014 18:45:02 -0500 B Watson wrote: > "There was a problem with your upload. Please check the file and try > again. If the problem persists, contact an admin." > > No details on what the problem might be. Was trying to upload > dungeon.tar.gz, around 23:40 GMT. My fault or the server's? I don't see any problem on the server and without seeing the tarball in question it's impossible to know. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From klaatu at straightedgelinux.com Sat Feb 15 02:50:54 2014 From: klaatu at straightedgelinux.com (Klaatu) Date: Sat, 15 Feb 2014 15:50:54 +1300 Subject: [Slackbuilds-users] submit fail In-Reply-To: References: Message-ID: <52FED60E.2050506@straightedgelinux.com> That's the error I get when I fail to remove the .git that is bundled along with the template file from SBo, or the .backup file I have all my emacs backups save themselves to. It never tells me why, it just gives me that generic error. Which is different than the verbose errors it gives when, for instance, I forget to include a md5sum or something like that. - klaatu On 02/15/2014 12:45 PM, B Watson wrote: > "There was a problem with your upload. Please check the file and try > again. If the problem persists, contact an admin." > > No details on what the problem might be. Was trying to upload > dungeon.tar.gz, around 23:40 GMT. My fault or the server's? > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From nick at linicks.net Sat Feb 15 08:56:14 2014 From: nick at linicks.net (Nick Warne) Date: Sat, 15 Feb 2014 08:56:14 +0000 Subject: [Slackbuilds-users] Fwd: Re: Alternative builds - Qxw In-Reply-To: <85EBE4C5-3B1D-4FE6-91DC-482A1E5A8866@slackbuilds.org> References: <52FE2DF9.4070800@linicks.net> <52FE33B8.3040407@linicks.net> <85EBE4C5-3B1D-4FE6-91DC-482A1E5A8866@slackbuilds.org> Message-ID: <52FF2BAE.3040005@linicks.net> Willy Sudiarto Raharjo wrote, On 14/02/14 22:43: >> >> Yep. And in the README, you can include the URL and md5sum of the >> unstable code. > > No need to do that > > The README should give information to the current release only > > Overriding VERSION variable is just a flexibility of SlackBuild script :) I am confused now - so I don't need to do anything? How can a user know then that there is a new release (as in this case?). Nick -- "A bug in the code is worth two in the documentation." FSF Associate Member 5508 http://linicks.net/ http://pi.linicks.net/ From willysr at slackbuilds.org Sat Feb 15 09:00:04 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Feb 2014 16:00:04 +0700 Subject: [Slackbuilds-users] Fwd: Re: Alternative builds - Qxw In-Reply-To: <52FF2BAE.3040005@linicks.net> References: <52FE2DF9.4070800@linicks.net> <52FE33B8.3040407@linicks.net> <85EBE4C5-3B1D-4FE6-91DC-482A1E5A8866@slackbuilds.org> <52FF2BAE.3040005@linicks.net> Message-ID: <52FF2C94.2070400@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I am confused now - so I don't need to do anything? How can a user > know then that there is a new release (as in this case?). the user can visit the official website of the package and override the $VERSION variable or they can wait until the maintainer update the SlackBuild to work with newer version - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlL/LJQACgkQiHuDdNczM4GtOgCfU8rN8s59cPpz/uWFtBUWsVj0 VfAAoLAkaJDu9TzcmZyW6jMKuYsT1+ee =eApl -----END PGP SIGNATURE----- From yalhcru at gmail.com Sat Feb 15 22:20:05 2014 From: yalhcru at gmail.com (B Watson) Date: Sat, 15 Feb 2014 17:20:05 -0500 Subject: [Slackbuilds-users] submit fail In-Reply-To: <52FED60E.2050506@straightedgelinux.com> References: <52FED60E.2050506@straightedgelinux.com> Message-ID: On 2/14/14, Klaatu wrote: > It never tells me why, it just gives me that generic error. It turned out to be because I left a 500Kbyte .jpg file in the tarball (it's one of the source files listed in the .info, I forgot to rm it because it didn't fit my mental 'this is a source file' pattern, being a jpeg). Still not sure whether it was a simple "file too big", or if the server's smart enough to parse the .info file, look at the filenames of the downloads, and if they're in the tarball, rejects it... Either way, it would help immensely if the server would actually give a reason instead of a generic 'there was a problem' that just leaves us scratching our heads. From erik at slackbuilds.org Sat Feb 15 22:45:47 2014 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 15 Feb 2014 16:45:47 -0600 Subject: [Slackbuilds-users] submit fail In-Reply-To: References: <52FED60E.2050506@straightedgelinux.com> Message-ID: <20140215164547.57c21291@shaggy.doo> On Sat, 15 Feb 2014 17:20:05 -0500 B Watson wrote: > It turned out to be because I left a 500Kbyte .jpg file in the tarball > (it's one of the source files listed in the .info, I forgot to rm it > because it didn't fit my mental 'this is a source file' pattern, being > a jpeg). > > Still not sure whether it was a simple "file too big", or if the server's > smart enough to parse the .info file, look at the filenames of the > downloads, and if they're in the tarball, rejects it... Submissions over 1MB are rejected with a specific "File size too large" error. If I had to guess, maybe the permissions on the now-missing jpeg file had something to do with it. However, without the original tarball the true issue will forever remain a mystery. > Either way, it would help immensely if the server would actually give > a reason instead of a generic 'there was a problem' that just leaves us > scratching our heads. Believe me, I've looked into it a few times in the past and it's not worth the effort to rewrite old code to catch a few fringe cases. Maybe someday, when there's an abundance of free time. In the meantime, I did change the generic error to at least request people attach the tarball when reporting the issue, because without it we can't know what's going on. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From yalhcru at gmail.com Sat Feb 15 23:11:13 2014 From: yalhcru at gmail.com (B Watson) Date: Sat, 15 Feb 2014 18:11:13 -0500 Subject: [Slackbuilds-users] submit fail In-Reply-To: <20140215164547.57c21291@shaggy.doo> References: <52FED60E.2050506@straightedgelinux.com> <20140215164547.57c21291@shaggy.doo> Message-ID: On 2/15/14, Erik Hanson wrote: > Believe me, I've looked into it a few times in the past and it's not worth > the effort to rewrite old code to catch a few fringe cases. Maybe someday, > when there's an abundance of free time. In the meantime, I did change the > generic error to at least request people attach the tarball when reporting > the issue, because without it we can't know what's going on. Fair enough. I had already rm'ed the offending tarball, so created a new one with a different filename/PRGNAM and tried submitting that. Got the same failure with the .jpg included, and success without it. The tarball that failed is here: http://urchlay.naptime.net/~urchlay/dungeon-test-please-delete.tar.gz The tarball that succeeded is in pending/ as 'dungeon-test-please-delete.tar.gz'. I didn't delete it from the queue, in case you need to take a look at it. Thanks for looking into this. From willysr at slackbuilds.org Sun Feb 16 01:16:59 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 16 Feb 2014 08:16:59 +0700 Subject: [Slackbuilds-users] submit fail In-Reply-To: References: <52FED60E.2050506@straightedgelinux.com> Message-ID: <5300118B.8000609@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> It never tells me why, it just gives me that generic error. > > It turned out to be because I left a 500Kbyte .jpg file in the > tarball (it's one of the source files listed in the .info, I forgot > to rm it because it didn't fit my mental 'this is a source file' > pattern, being a jpeg). > > Still not sure whether it was a simple "file too big", or if the > server's smart enough to parse the .info file, look at the > filenames of the downloads, and if they're in the tarball, rejects > it... > > Either way, it would help immensely if the server would actually > give a reason instead of a generic 'there was a problem' that just > leaves us scratching our heads. Should be all good now please try again. Now the 1 MB filter is applied correctly - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMAEYsACgkQiHuDdNczM4GMIwCfUnJmqgOZL/xBNuh1Rlccq7mF 744AoJRUcFHHcc25YxJF7Omo6cT04QHg =q8Q3 -----END PGP SIGNATURE----- From yalhcru at gmail.com Sun Feb 16 02:03:37 2014 From: yalhcru at gmail.com (B Watson) Date: Sat, 15 Feb 2014 21:03:37 -0500 Subject: [Slackbuilds-users] submit fail In-Reply-To: <5300118B.8000609@slackbuilds.org> References: <52FED60E.2050506@straightedgelinux.com> <5300118B.8000609@slackbuilds.org> Message-ID: On 2/15/14, Willy Sudiarto Raharjo wrote: > Should be all good now > please try again. Now the 1 MB filter is applied correctly Yup, same tarball was accepted this time. Thanks. From rworkman at slackbuilds.org Sun Feb 16 08:15:48 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 16 Feb 2014 08:15:48 +0000 Subject: [Slackbuilds-users] Updates - 20140216.1 Message-ID: <20140216081548.GA32669@slackbuilds.org> Sun Feb 16 07:49:38 UTC 2014 audio/caps: Updated for version 0.9.20. games/dungeon: Fixed segfaults. games/hexalate: Updated for version 1.0.3. games/oblige: Fix permission and install boss fight data. games/tintin: Updated for version 2.01.0. gis/OWSLib: Updated for version 0.8.6. gis/rasterio: Updated for version 0.6. graphics/HotShots: Updated for version 2.0.1. graphics/advancecomp: Added (collection of recompression utilities). libraries/PrettyTable: Added (library to displaying tabular data). libraries/bcdoc: Added (ReST document generation tools). libraries/botocore: Added (Low-level, data-driven core of boto 3). libraries/chromaprint: Updated for version 1.1. libraries/collada-dom: Added (C++ API to the COLLADA XML schema). libraries/enum34: Updated for version 0.9.23. libraries/jansson: Added (C library). libraries/libewf: Updated for version 20140201. libraries/libgksu: Fixed helper path on x86_64 + Compress manual. libraries/miniupnpc: Updated for version 1.9. libraries/opencv: Updated for version 2.4.8. libraries/xview: Added (X11 toolkit for OPEN LOOK applications). network/FireWorks: Updated for version 0.71. network/Pafy: Updated for version 0.3.34. network/awscli: Added (Universal Command Line Environment for AWS). network/deis: Added (Command-line Client for Deis). network/filezilla: Updated for version 3.7.4.1. network/livestreamer: Updated for version 1.7.3. network/mps: Added (Search, Stream and Download MP3). network/pms-youtube: Updated for version 0.01.13. network/pubnub-curses: Added (PubNub Curses Terminal Client). network/ssvnc: Fixed script. network/turbolift: Added (OpenStack Swift Uploader). network/yoda: Added (Multiple repositories management). office/gnucash: Remove Beta label on README. python/PyColorizer: Added (Add color in your shell). python/jmespath: Added (JSON Matching Expressions). python/monty: Added (missing complement to Python). python/pipstat: Added (PyPI packages Counter). python/ply: Added (Python Lex & Yacc). python/python-swiftclient: Added (OpenStack API Library). system/asbt: Updated for version 0.8.2. system/ded: Added (directory editor). system/gdm: sysconfdir is now /etc/gdm/ instead of /etc/X11/gdm/ system/hime: Added libchewing in REQUIRES. system/sleuthkit: Updated for version 4.1.3. system/trachet: Updated for version 0.3.19. system/virt-manager: Updated for version 1.0.0. system/watch-fs: Added (monitor files changes). system/xfsudo: Updated for version 0.3. +--------------------------+ From miguel at thedeanda.com Mon Feb 17 21:50:04 2014 From: miguel at thedeanda.com (Miguel De Anda) Date: Mon, 17 Feb 2014 13:50:04 -0800 Subject: [Slackbuilds-users] google chrome Message-ID: is google chrome no longer supported? i was able to build it with only minor changes to the 13.1 script on the site (they moved the .desktop file so the 'ln -s' line is no longer needed and the path to the .desktop file modified by sed needs to change. i use chromium but there are sometimes minor differences ( html5test.comshows different scores) so i'm trying to use both browsers even though i mostly use chromium. -m -------------- next part -------------- An HTML attachment was scrubbed... URL: From joshuakwood at gmail.com Mon Feb 17 22:15:01 2014 From: joshuakwood at gmail.com (JK Wood) Date: Mon, 17 Feb 2014 16:15:01 -0600 Subject: [Slackbuilds-users] google chrome In-Reply-To: References: Message-ID: It was removed (I believe) because there's a build script for google-chrome in /extra: http://taper.alienbase.nl/mirrors/slackware/slackware-14.1/extra/google-chrome/ -- JK On Mon, Feb 17, 2014 at 3:50 PM, Miguel De Anda wrote: > is google chrome no longer supported? i was able to build it with only > minor changes to the 13.1 script on the site (they moved the .desktop file > so the 'ln -s' line is no longer needed and the path to the .desktop file > modified by sed needs to change. > > i use chromium but there are sometimes minor differences ( html5test.comshows different scores) so i'm trying to use both browsers even though i > mostly use chromium. > > -m > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Tue Feb 18 04:42:16 2014 From: miguel at thedeanda.com (Miguel De Anda) Date: Mon, 17 Feb 2014 20:42:16 -0800 Subject: [Slackbuilds-users] google chrome In-Reply-To: References: Message-ID: oh. silly me. never bothered to check extra... wow. lots of goodies there: flashplayer, tigervnc, wicd, recordmydesktop, bittorrent (isn't bit torrent illegal? j/k) etc. thanks! On Mon, Feb 17, 2014 at 2:15 PM, JK Wood wrote: > It was removed (I believe) because there's a build script for > google-chrome in /extra: > > > http://taper.alienbase.nl/mirrors/slackware/slackware-14.1/extra/google-chrome/ > > -- JK > > > On Mon, Feb 17, 2014 at 3:50 PM, Miguel De Anda wrote: > >> is google chrome no longer supported? i was able to build it with only >> minor changes to the 13.1 script on the site (they moved the .desktop file >> so the 'ln -s' line is no longer needed and the path to the .desktop file >> modified by sed needs to change. >> >> i use chromium but there are sometimes minor differences ( html5test.comshows different scores) so i'm trying to use both browsers even though i >> mostly use chromium. >> >> -m >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bocke at mycity.rs Tue Feb 18 14:30:31 2014 From: bocke at mycity.rs (Bojan Popovic) Date: Tue, 18 Feb 2014 15:30:31 +0100 Subject: [Slackbuilds-users] google chrome In-Reply-To: References: Message-ID: <20140218153031.4698a304@malac.universe.uni> Hi. Bittorent itself isn't. It's just a way of distributed file sharing. File sharing itself is not illegal if the files themselves are legal. For example, most Linux distributions (including Slack) offer bittorrent downloads as a way to decrease a load on the physical download server. Piracy is what is illegal. No matter if on bittorrent, usenet, ftp or any other medium. Cheers, Bojan. On Mon, 17 Feb 2014 20:42:16 -0800 Miguel De Anda wrote: > bittorrent (isn't bit torrent illegal? j/k) etc. From nick at linicks.net Tue Feb 18 14:50:34 2014 From: nick at linicks.net (Nick Warne) Date: Tue, 18 Feb 2014 14:50:34 +0000 Subject: [Slackbuilds-users] google chrome In-Reply-To: <20140218153031.4698a304@malac.universe.uni> References: <20140218153031.4698a304@malac.universe.uni> Message-ID: <5303733A.2000804@linicks.net> Bojan Popovic wrote, On 18/02/14 14:30: > Hi. > > > Bittorent itself isn't. It's just a way of distributed file sharing. > File sharing itself is not illegal if the files themselves are legal. > For example, most Linux distributions (including Slack) offer > bittorrent downloads as a way to decrease a load on the physical > download server. > > Piracy is what is illegal. No matter if on bittorrent, usenet, ftp or > any other medium. > > Cheers, > > Bojan. I think the j/k Miguel wrote means "joking"; as most media outlets define bittorrent as the only way illegal downloads happen - the same as they describe 'hackers' instead of 'crackers' when mentioning scans/trojans/worms etc. (us slackers are all hackers!). The press puts out wrong signals here and Joe Public (sheeple) believe it. Nick > > On Mon, 17 Feb 2014 20:42:16 -0800 > Miguel De Anda wrote: > >> bittorrent (isn't bit torrent illegal? j/k) etc. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- "A bug in the code is worth two in the documentation." FSF Associate Member 5508 http://linicks.net/ http://pi.linicks.net/ From erik at slackbuilds.org Tue Feb 18 21:11:19 2014 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 18 Feb 2014 15:11:19 -0600 Subject: [Slackbuilds-users] Updates - 20140218.1 Message-ID: <20140218151119.090faf15@shaggy.doo> Tue Feb 18 20:59:24 UTC 2014 academic/perlprimer: Fixed syntax error. audio/alsaequal: Updated for new caps Eq name. audio/ngjackspa: Added (JACK host for LADSPA plugins). desktop/qlandkartegt: Updated for version 1.7.6. development/Bottleneck: Added (Fast NumPy array functions). development/pandas: Added (Powerful data structures). development/tstoolbox: Added (manipulate time series files). games/xmoto: Update REQUIRES. gis/geopy: Updated for version 0.98. graphics/CreateCloudMap: Added (cloud map for xplanet). graphics/HotShots: Updated for version 2.1.0. libraries/ConfigParser: Added (backported configparser). libraries/DateTime: Added (DateTime data type). libraries/Kivy: Added (rapid development library). libraries/VTK: Added (The Visualization Toolkit). libraries/mxml: Updated for version 2.8. libraries/ode: Updated for version 0.13. libraries/ordereddict: Added (substitute for Py2.7's collections). libraries/pykdtree: Added (Fast kd-tree implementation). libraries/vtk: Removed (replaced by VTK). multimedia/lives: Added (Video Editing System). multimedia/x265: Added (H265/HEVC video encoder) network/CherryMusic: Updated for version 0.3.1. network/Pafy: Updated for version 0.3.35. network/RYMTracks: Updated for version 0.1.4. network/aldryn-client: Added (client for Aldryn Cloud). network/hydra: Updated for version 7.6. network/mps-youtube: Added (Terminal based YouTube jukebox). network/mps: Updated for version 0.20.02. network/speedtest-cli: Added (Testing internet bandwidth). network/spice-gtk: Updated for version 0.23. network/you-get: Updated for version 0.3.27. python/Baker: Added (Access to Python functions). python/argcomplete: Updated for version 0.7.0. python/msgpack-python: Updated for version 0.4.1. python/pipstat: Updated for version 0.2.1. python/pySmartDL: Updated for version 1.2.2. python/pygrametl: Added (ETL programming in Python). python/pyresample: Added (geospatial resampling). python/python-keyczar: Added (cryptographic toolkit). system/asbt: Updated for version 0.8.3. system/wterm: Added (VT102 Terminal Emulator). system/xfsudo: Upgraded for version 0.4. +--------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From scott_tolliver at fastmail.us Thu Feb 20 08:06:22 2014 From: scott_tolliver at fastmail.us (Scott A. Tolliver) Date: Thu, 20 Feb 2014 03:06:22 -0500 Subject: [Slackbuilds-users] Compile/make error for Octave 3.8.0 on Slackware Current (32bit) Message-ID: <1392883582.11046.85594433.4841B873@webmail.messagingengine.com> Hello. I am trying to compile Octave 3.8.0 on Slackware Current using the Slack Build script, and it fails with error(s) concerning libcore fcn? I installed blas, then lapack, then tried to compile/install octave. Any advice on where I should start to troubleshoot this? Thank you. -- Scott A. Tolliver scott_tolliver at fastmail.us From dn2010 at gmail.com Thu Feb 20 08:30:14 2014 From: dn2010 at gmail.com (Daniil Bratashov) Date: Thu, 20 Feb 2014 12:30:14 +0400 Subject: [Slackbuilds-users] Compile/make error for Octave 3.8.0 on Slackware Current (32bit) In-Reply-To: <1392883582.11046.85594433.4841B873@webmail.messagingengine.com> References: <1392883582.11046.85594433.4841B873@webmail.messagingengine.com> Message-ID: <20140220123014.18b2fabb@darkstar.example.net> On Thu, 20 Feb 2014 03:06:22 -0500 "Scott A. Tolliver" wrote: > Hello. I am trying to compile Octave 3.8.0 on Slackware Current using > the Slack Build script, and it fails with error(s) concerning libcore > fcn? I installed blas, then lapack, then tried to compile/install > octave. Any advice on where I should start to troubleshoot this? I had similar problem with x86-64 multilib -current and it seems to me it was somehow connected with failed attempt to link against 32bit libs. WBR, Daniil Bratashov. From scott_tolliver at fastmail.us Fri Feb 21 15:29:59 2014 From: scott_tolliver at fastmail.us (Scott A. Tolliver) Date: Fri, 21 Feb 2014 10:29:59 -0500 Subject: [Slackbuilds-users] Compile/make error for Octave 3.8.0 on Slackware Current (32bit) (Daniil Bratashov) Message-ID: <1392996599.5015.86171065.011B15CB@webmail.messagingengine.com> I'm using the 32bit Slackware Current, so I don't, or shouldn't have a multi-lib linking problem. >> I had similar problem with x86-64 multilib -current and it seems to me >> it was somehow connected with failed attempt to link against 32bit libs. >> WBR, Daniil Bratashov. -- Scott A. Tolliver scott_tolliver at fastmail.us From matteo.bernardini at gmail.com Fri Feb 21 16:59:08 2014 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 21 Feb 2014 17:59:08 +0100 Subject: [Slackbuilds-users] Compile/make error for Octave 3.8.0 on Slackware Current (32bit) In-Reply-To: <1392883582.11046.85594433.4841B873@webmail.messagingengine.com> References: <1392883582.11046.85594433.4841B873@webmail.messagingengine.com> Message-ID: 2014-02-20 9:06 GMT+01:00 Scott A. Tolliver : > Hello. I am trying to compile Octave 3.8.0 on Slackware Current using > the Slack Build script, and it fails with error(s) concerning libcore > fcn? I installed blas, then lapack, then tried to compile/install > octave. Any advice on where I should start to troubleshoot this? hi Scott, as you probably already know our repository supports only the stable release of Slackware, so it's possible that our scripts won't build on -current, like in this case. That said the error seems related to llvm (-current ships 3.4 while stable has 3.3) and I seem to have found a patch for it in the gentoo sources: applying that during the build makes it go fine here on a slackware-current virtual machine. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sci-mathematics/octave/files/octave-3.8.0-llvm-3.4.patch Matteo From ronayne.thomas at gmail.com Fri Feb 21 17:45:10 2014 From: ronayne.thomas at gmail.com (Thomas Ronayne) Date: Fri, 21 Feb 2014 12:45:10 -0500 Subject: [Slackbuilds-users] Install SlackBuild Package Where I Want To Message-ID: <530790A6.1040903@gmail.com> Hi, Although I really appreciate SlackBuilds and all the work that goes into them and the efforts of everyone working on SlackBuilds I have one problem that I just can't get my head around -- how do I install a SlackBuild where I want to other than in the root tree? For example, I need NetCDF for use with the Generic Mapping Tools (GMT). I have always installed both GMT and NetCDF in /opt (they're both big and I don't want 'em in the root tree). That is also true of, say, OpenOffice -- or LibreOffice -- I don't want that stuff in the root, I want it in /opt. I've tried editing the SlackBuild (changing "usr" to "opt") and have had messy failures doing that; is the some easy way to specify the installation directory? Have I just missed something really, really basic? Thanks. From didier.spaier at epsm.fr Fri Feb 21 20:06:30 2014 From: didier.spaier at epsm.fr (Didier Spaier) Date: Fri, 21 Feb 2014 21:06:30 +0100 Subject: [Slackbuilds-users] Install SlackBuild Package Where I Want To In-Reply-To: <530790A6.1040903@gmail.com> References: <530790A6.1040903@gmail.com> Message-ID: <5307B1C6.605@epsm.fr> On 21/02/2014 18:45, Thomas Ronayne wrote: > Although I really appreciate SlackBuilds and all the work that goes into them and the efforts of everyone working on SlackBuilds I have one problem that I just can't get my head around -- how do I install a SlackBuild where I want to other than in the root tree? > > For example, I need NetCDF for use with the Generic Mapping Tools (GMT). I have always installed both GMT and NetCDF in /opt (they're both big and I don't want 'em in the root tree). That is also true of, say, OpenOffice -- or LibreOffice -- I don't want that stuff in the root, I want it in /opt. > > I've tried editing the SlackBuild (changing "usr" to "opt") and have had messy failures doing that; is the some easy way to specify the installation directory? Have I just missed something really, really basic? Well, you can always change configure's options but then, you'll have to provide the needed symlinks to executables and shared libraries in the standard locations, for instance in doisnt.sh. That's what makpkg expects, see "man makepkg" and examples in /var/log/scripts. From klaatu at straightedgelinux.com Fri Feb 21 20:07:13 2014 From: klaatu at straightedgelinux.com (Klaatu) Date: Sat, 22 Feb 2014 09:07:13 +1300 Subject: [Slackbuilds-users] Install SlackBuild Package Where I Want To In-Reply-To: <530790A6.1040903@gmail.com> References: <530790A6.1040903@gmail.com> Message-ID: <5307B1F1.1070607@straightedgelinux.com> I don't know how to use NetCDF so I cannot test it thoroughly, but this worked for me: cd /path/to/SlackBuild/netcdf sed -i 's_/usr_/opt/netcdf/usr_g' netcdf.SlackBuild su -c './netcdf.SlackBuild' >From your email, it sounds like maybe you only replaced one instance of (probably the prefix) /usr with /opt but there are multiple places where things are being defined and where the absolute path /usr is being used (like when man pages are copied in, etc). So sed is probably the better choice here. Hope that helps. -klaatu On 02/22/2014 06:45 AM, Thomas Ronayne wrote: > Hi, > > Although I really appreciate SlackBuilds and all the work that goes into > them and the efforts of everyone working on SlackBuilds I have one > problem that I just can't get my head around -- how do I install a > SlackBuild where I want to other than in the root tree? > > For example, I need NetCDF for use with the Generic Mapping Tools (GMT). > I have always installed both GMT and NetCDF in /opt (they're both big > and I don't want 'em in the root tree). That is also true of, say, > OpenOffice -- or LibreOffice -- I don't want that stuff in the root, I > want it in /opt. > > I've tried editing the SlackBuild (changing "usr" to "opt") and have had > messy failures doing that; is the some easy way to specify the > installation directory? Have I just missed something really, really basic? > > Thanks. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From erik at slackbuilds.org Fri Feb 21 20:54:45 2014 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 21 Feb 2014 14:54:45 -0600 Subject: [Slackbuilds-users] Updates - 20140221.1 Message-ID: <20140221145445.1eb9643f@shaggy.doo> Fri Feb 21 20:40:16 UTC 2014 audio/alsa-tools: Validate .desktop file audio/connie: Added (organ synth for JACK). audio/sunvox: Updated for version 1.7.4b. desktop/herbstluftwm: Updated for version 0.5.3. desktop/kdeconnect: Updated for version 0.5. desktop/ptwit: Added (simple twitter client). desktop/superkey-launch: Updated for version 0.32. development/coccinelle: Added (matching and transformation engine). development/menhir: Added (OCaml parser generator). games/gnonograms: Added (Nonogram puzzle generator and solver). games/zork: Fix .desktop files so they validate. graphics/yagf: Updated for version 0.9.3. libraries/eigen3: Fixup archive extraction in some cases libraries/libhtp: Added (HTTP parser). multimedia/flashplayer-plugin: Updated for version 11.2.202.341. network/CherryMusic: Updated for version 0.31.2. network/Pafy: Updated for version 0.3.36. network/suricata: Added (Network Security Monitoring). network/udpxy: Added (UDP-to-HTTP traffic relaying). network/you-get: Updated for version 0.3.28. python/piprot: Updated for version 0.5.0. python/python-oauthlib: Added (OAuth Implementation). python/python-twitter: Updated for version 1.3.1 + New Maintainer. python/requests-oauthlib: Added (OAuthlib authentication). python/selenium: Updated for version 2.40.0. python/xtermcolor: Added (Python module for colorizing output). system/gparted: Updated for version 0.18.0. system/wterm: Added prefix. +--------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From leva at ecentrum.hu Sun Feb 23 10:07:07 2014 From: leva at ecentrum.hu (LEVAI Daniel) Date: Sun, 23 Feb 2014 11:07:07 +0100 Subject: [Slackbuilds-users] mupdf Message-ID: <20140223100707.GA3035@serenity.local> Hi! Anyone taking care of the mupdf slackbuild? Aside from the fact that there is a newer version since quite some time, in february upstream fixed a critical security bug allowing arbitrary code execution. If the maintainer won't step up, I suggest incorporating the new version and the patch for the security fix. Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F -------------- next part -------------- A non-text attachment was scrubbed... Name: mupdf.tar.gz Type: application/x-tar-gz Size: 4384 bytes Desc: not available URL: From willysr at slackbuilds.org Sun Feb 23 11:28:28 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 23 Feb 2014 18:28:28 +0700 Subject: [Slackbuilds-users] mupdf In-Reply-To: <20140223100707.GA3035@serenity.local> References: <20140223100707.GA3035@serenity.local> Message-ID: <5309DB5C.7090709@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun 23 Feb 2014 05:07:07 PM WIT, LEVAI Daniel wrote: > Hi! > > Anyone taking care of the mupdf slackbuild? Aside from the fact that > there is a newer version since quite some time, in february upstream > fixed a critical security bug allowing arbitrary code execution. > If the maintainer won't step up, I suggest incorporating the new version > and the patch for the security fix. B. Watson is the maintainer and he's quite active perhaps he only needs to be cc'ed - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMJ21wACgkQiHuDdNczM4FdhQCgg923p/nqjh/y4uy11RFHTr6+ fbUAnRWZ4gfvL1s9q/uywwnrbHsF6SMy =+vWl -----END PGP SIGNATURE----- From kingbeowulf at gmail.com Sun Feb 23 19:41:03 2014 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 23 Feb 2014 11:41:03 -0800 Subject: [Slackbuilds-users] RFC: possible BOINC submission Message-ID: <530A4ECF.8010608@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of queries to the list: 1. Is anyone interested in having BOINC https://boinc.berkeley.edu/ added to the SBo repository? Any comments, advice, are welcome. For example: desktop file, install to /opt or $HOME, rc.boinc, etc. 2. They seem to have dropped their tarball snapshot download locations, or at least I can no longer find it, and they just point everyone who wants the source to the git repository. BOINC is pushing everyone to use their precompiled install script (UBUNTU, ugh!). I could just repackage that, but their binary can act a bit odd on Slackware. Compiling from source is highly recommended and preferred. To get a source tarball for the script, I use: # git clone git://boinc.berkeley.edu/boinc-v2.git boinc_repo # cd boinc_repo # git archive --format=tar --prefix Boinc-7.2.39/ client_release/7.2/7.2.39 | bzip2 > ../Boinc-7.2.39.tar.bz2 Is there an easier way? Or does anyone know of a link to the stable snapshots? Thanks - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMKTs0ACgkQXvwMaW61dLdIGwCgjdK6IFOJPIvhIqHlNbVOvlwz +DEAmgJ8fVaSeoTO3tzVkdPQyo/HPEiT =cRjr -----END PGP SIGNATURE----- From willysr at slackbuilds.org Mon Feb 24 01:01:02 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 24 Feb 2014 08:01:02 +0700 Subject: [Slackbuilds-users] RFC: possible BOINC submission In-Reply-To: <530A4ECF.8010608@gmail.com> References: <530A4ECF.8010608@gmail.com> Message-ID: <530A99CE.7060203@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon 24 Feb 2014 02:41:03 AM WIT, King Beowulf wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > A couple of queries to the list: > > 1. Is anyone interested in having BOINC https://boinc.berkeley.edu/ > added to the SBo repository? Any comments, advice, are welcome. For > example: desktop file, install to /opt or $HOME, rc.boinc, etc. > > 2. They seem to have dropped their tarball snapshot download > locations, or at least I can no longer find it, and they just point > everyone who wants the source to the git repository. BOINC is pushing > everyone to use their precompiled install script (UBUNTU, ugh!). I > could just repackage that, but their binary can act a bit odd on > Slackware. Compiling from source is highly recommended and preferred. > To get a source tarball for the script, I use: > > # git clone git://boinc.berkeley.edu/boinc-v2.git boinc_repo > # cd boinc_repo > # git archive --format=tar --prefix Boinc-7.2.39/ > client_release/7.2/7.2.39 | bzip2 > ../Boinc-7.2.39.tar.bz2 > > Is there an easier way? Or does anyone know of a link to the stable > snapshots? I would say use tags as your base for creating the source It's all documented in https://boinc.berkeley.edu/trac/wiki/SourceCodeGit - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMKmc4ACgkQiHuDdNczM4HCmwCfYGL7I3DIQr1BMC7StUMU16f6 WmYAnicN/3hhgDf1rh5BUZ3S7xFmlBOi =0LHI -----END PGP SIGNATURE----- From yalhcru at gmail.com Mon Feb 24 03:27:55 2014 From: yalhcru at gmail.com (B Watson) Date: Sun, 23 Feb 2014 22:27:55 -0500 Subject: [Slackbuilds-users] mupdf In-Reply-To: <5309DB5C.7090709@slackbuilds.org> References: <20140223100707.GA3035@serenity.local> <5309DB5C.7090709@slackbuilds.org> Message-ID: On 2/23/14, Willy Sudiarto Raharjo wrote: > B. Watson is the maintainer and he's quite active > perhaps he only needs to be cc'ed I'm on it, thanks for the heads-up. From mhobgoodusaf at gmail.com Mon Feb 24 18:23:41 2014 From: mhobgoodusaf at gmail.com (Michael Hobgood) Date: Mon, 24 Feb 2014 12:23:41 -0600 Subject: [Slackbuilds-users] Problem with two GO language packages Message-ID: When installing two of the go language packages, I received identical errors when running the Slackbuild script. The problem isn't with the script, but with the source code. Tar complains that it isn't a tar file. I can get the source to work by unzipping it, then untarring it, then retarring and rezipping. Then the Slackbuild script can build it and I can install it. My question is whom do I contact about the source code itself. I've the email address from the SlackBuilds page for each package. The source code packages are: go.net-98.tar.gz referenced from golang-googlecode-gonet go.tools-588451.tar.gz referenced from golang-googlecode-gotools Coordially, Michael Hobgood From mancha1 at hush.com Mon Feb 24 19:12:37 2014 From: mancha1 at hush.com (mancha) Date: Mon, 24 Feb 2014 19:12:37 +0000 Subject: [Slackbuilds-users] Problem with two GO language packages Message-ID: <20140224191237.4A5A860836@smtp.hushmail.com> Hi. After a minute or two of head-scratching I was able to figure it out...they're gzipped twice! ====== $ zcat go.net-98.tar.gz > go.net-98.puzzle $ file go.net-98.puzzle go.net-98.puzzle: gzip compressed data, was... ====== When you use "tar xzf" it decompresses the outer gzip but then tar complains when it finds a gzip (inner gzip) instead of a tar archive. I'm cc'ing vbatts (who created & hosts these archives). Thanks for this Monday puzzler. --mancha On Mon, 24 Feb 2014 18:23:48 +0000 "Michael Hobgood" wrote: >When installing two of the go language packages, I received >identical >errors when running the Slackbuild script. The problem isn't with >the >script, but with the source code. Tar complains that it isn't a >tar >file. > >I can get the source to work by unzipping it, then untarring it, >then >retarring and rezipping. Then the Slackbuild script can build it >and >I can install it. > >My question is whom do I contact about the source code itself. >I've >the email address from the SlackBuilds page for each package. > >The source code packages are: >go.net-98.tar.gz referenced from golang-googlecode-gonet >go.tools-588451.tar.gz referenced from golang-googlecode-gotools > >Coordially, >Michael Hobgood >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - http://lists.slackbuilds.org/pipermail/slackbuilds- >users/ >FAQ - http://slackbuilds.org/faq/ From erik at slackbuilds.org Mon Feb 24 19:24:13 2014 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 24 Feb 2014 13:24:13 -0600 Subject: [Slackbuilds-users] Problem with two GO language packages In-Reply-To: <20140224191237.4A5A860836@smtp.hushmail.com> References: <20140224191237.4A5A860836@smtp.hushmail.com> Message-ID: <20140224132413.79f90eb0@shaggy.doo> On Mon, 24 Feb 2014 19:12:37 +0000 "mancha" wrote: > After a minute or two of head-scratching I was able to > figure it out...they're gzipped twice! > > ====== > $ zcat go.net-98.tar.gz > go.net-98.puzzle > $ file go.net-98.puzzle > go.net-98.puzzle: gzip compressed data, was... > ====== Not having this problem here, $ zcat go.net-98.tar.gz > go.net-98.test $ file go.net-98.test go.net-98.test: POSIX tar archive (GNU) same for go.tools-588451.tar.gz ... I used wget to retrieve them. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From mancha1 at hush.com Mon Feb 24 19:38:11 2014 From: mancha1 at hush.com (mancha) Date: Mon, 24 Feb 2014 19:38:11 +0000 (UTC) Subject: [Slackbuilds-users] Problem with two GO language packages References: <20140224191237.4A5A860836@smtp.hushmail.com> <20140224132413.79f90eb0@shaggy.doo> Message-ID: Erik Hanson writes: > > Not having this problem here, > > $ zcat go.net-98.tar.gz > go.net-98.test > $ file go.net-98.test > go.net-98.test: POSIX tar archive (GNU) > > same for go.tools-588451.tar.gz ... I used wget to retrieve them. > OK. Things work fine with wget for me too. Seems the outer gzip gets added when one downloads via clicking the SBo link in FF. --mancha From mhobgoodusaf at gmail.com Mon Feb 24 19:55:09 2014 From: mhobgoodusaf at gmail.com (Michael Hobgood) Date: Mon, 24 Feb 2014 13:55:09 -0600 Subject: [Slackbuilds-users] Problem with two GO language packages In-Reply-To: References: <20140224191237.4A5A860836@smtp.hushmail.com> <20140224132413.79f90eb0@shaggy.doo> Message-ID: Interesting. When I use wget to retrieve the file, it is correct. But, downloading via Firefox I also get the double gzipped one. Maybe it's just because it is Monday! Coordially, Michael Hobgood On 2/24/14, mancha wrote: > Erik Hanson writes: >> >> Not having this problem here, >> >> $ zcat go.net-98.tar.gz > go.net-98.test >> $ file go.net-98.test >> go.net-98.test: POSIX tar archive (GNU) >> >> same for go.tools-588451.tar.gz ... I used wget to retrieve them. >> > > OK. Things work fine with wget for me too. Seems the outer gzip > gets added when one downloads via clicking the SBo link in FF. > > --mancha > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From vbatts at gmail.com Mon Feb 24 20:08:04 2014 From: vbatts at gmail.com (Vincent Batts) Date: Mon, 24 Feb 2014 15:08:04 -0500 Subject: [Slackbuilds-users] Problem with two GO language packages In-Reply-To: References: Message-ID: crazy problem. Which email did you send to? I have not received anything. :-\ On Mon, Feb 24, 2014 at 1:23 PM, Michael Hobgood wrote: > When installing two of the go language packages, I received identical > errors when running the Slackbuild script. The problem isn't with the > script, but with the source code. Tar complains that it isn't a tar > file. > > I can get the source to work by unzipping it, then untarring it, then > retarring and rezipping. Then the Slackbuild script can build it and > I can install it. > > My question is whom do I contact about the source code itself. I've > the email address from the SlackBuilds page for each package. > > The source code packages are: > go.net-98.tar.gz referenced from golang-googlecode-gonet > go.tools-588451.tar.gz referenced from golang-googlecode-gotools > > Coordially, > Michael Hobgood > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mancha1 at hush.com Mon Feb 24 20:13:18 2014 From: mancha1 at hush.com (mancha) Date: Mon, 24 Feb 2014 20:13:18 +0000 Subject: [Slackbuilds-users] Problem with two GO language packages Message-ID: <20140224201319.3909960838@smtp.hushmail.com> All: The problem is server-side (vbatts, looks like your PHP-based backend might be to blame): $ wget http://www.hashbangbash.com/downloads/src/go.net-98.tar.gz $ md5sum go.net-98.tar.gz ada7722b72a1ea66a4c6a78f3e7009b2 go.net-98.tar.gz $ wget --header="accept-encoding: gzip" http://www.hashbangbash.com/downloads/src/go.net-98.tar.gz $ md5sum go.net-98.tar.gz ebcefca8bcb3c4a6926ac4122825bcf3 go.net-98.tar.gz As you can see, when the client advertises it accepts gzip encoding (which most browsers do), the server is gzipping the gzipped tarball before transmission. --mancha On Mon, 24 Feb 2014 19:55:14 +0000 "Michael Hobgood" wrote: >Interesting. When I use wget to retrieve the file, it is correct. >But, downloading via Firefox I also get the double gzipped one. >Maybe >it's just because it is Monday! > >Coordially, >Michael Hobgood > > > > >On 2/24/14, mancha wrote: >> Erik Hanson writes: >>> >>> Not having this problem here, >>> >>> $ zcat go.net-98.tar.gz > go.net-98.test >>> $ file go.net-98.test >>> go.net-98.test: POSIX tar archive (GNU) >>> >>> same for go.tools-588451.tar.gz ... I used wget to retrieve >them. >>> >> >> OK. Things work fine with wget for me too. Seems the outer gzip >> gets added when one downloads via clicking the SBo link in FF. >> >> --mancha >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds- >users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - http://lists.slackbuilds.org/pipermail/slackbuilds- >users/ >FAQ - http://slackbuilds.org/faq/ From vbatts at gmail.com Mon Feb 24 20:26:25 2014 From: vbatts at gmail.com (Vincent Batts) Date: Mon, 24 Feb 2014 15:26:25 -0500 Subject: [Slackbuilds-users] Problem with two GO language packages In-Reply-To: <20140224201319.3909960838@smtp.hushmail.com> References: <20140224201319.3909960838@smtp.hushmail.com> Message-ID: ohman! good catch. fixed now. Thanks! On Mon, Feb 24, 2014 at 3:13 PM, mancha wrote: > All: > > The problem is server-side (vbatts, looks like your PHP-based > backend might be to blame): > > $ wget http://www.hashbangbash.com/downloads/src/go.net-98.tar.gz > $ md5sum go.net-98.tar.gz > ada7722b72a1ea66a4c6a78f3e7009b2 go.net-98.tar.gz > > $ wget --header="accept-encoding: gzip" > http://www.hashbangbash.com/downloads/src/go.net-98.tar.gz > $ md5sum go.net-98.tar.gz > ebcefca8bcb3c4a6926ac4122825bcf3 go.net-98.tar.gz > > As you can see, when the client advertises it accepts gzip encoding > (which most browsers do), the server is gzipping the gzipped tarball > before transmission. > > --mancha > > On Mon, 24 Feb 2014 19:55:14 +0000 "Michael Hobgood" wrote: > >Interesting. When I use wget to retrieve the file, it is correct. > >But, downloading via Firefox I also get the double gzipped one. > >Maybe > >it's just because it is Monday! > > > >Coordially, > >Michael Hobgood > > > > > > > > > >On 2/24/14, mancha wrote: > >> Erik Hanson writes: > >>> > >>> Not having this problem here, > >>> > >>> $ zcat go.net-98.tar.gz > go.net-98.test > >>> $ file go.net-98.test > >>> go.net-98.test: POSIX tar archive (GNU) > >>> > >>> same for go.tools-588451.tar.gz ... I used wget to retrieve > >them. > >>> > >> > >> OK. Things work fine with wget for me too. Seems the outer gzip > >> gets added when one downloads via clicking the SBo link in FF. > >> > >> --mancha > >> > >> > >> _______________________________________________ > >> SlackBuilds-users mailing list > >> SlackBuilds-users at slackbuilds.org > >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds- > >users/ > >> FAQ - http://slackbuilds.org/faq/ > >> > >> > >_______________________________________________ > >SlackBuilds-users mailing list > >SlackBuilds-users at slackbuilds.org > >http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >Archives - http://lists.slackbuilds.org/pipermail/slackbuilds- > >users/ > >FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Mon Feb 24 22:51:52 2014 From: yalhcru at gmail.com (B Watson) Date: Mon, 24 Feb 2014 17:51:52 -0500 Subject: [Slackbuilds-users] mupdf In-Reply-To: <20140223100707.GA3035@serenity.local> References: <20140223100707.GA3035@serenity.local> Message-ID: On 2/23/14, LEVAI Daniel wrote: > If the maintainer won't step up, Hm, did I miss an email from you? Usually it's better to email the maintainer directly instead of the list... > I suggest incorporating the new version > and the patch for the security fix. Update now in pending/. What I did is backport the security fix to mupdf-1.2, rather than upgrade to mupdf-1.3. Reasons for that: 1. mupdf 1.3's API is incompatible with 1.2's, meaning zathura-pdf-mupdf (depends on mupdf) will have to be updated... which almost certainly means every zathura-* build needs to be updated too. 2. mupdf 1.3 needs openjpeg 2.0, we ship 1.5 for now. openjpeg 2.0's API has changed enough that any build depending on it will need attention. (could work around this by using mupdf's bundled openjpeg source, if we don't mind having it statically linked & bloating up the mupdf binary) 3. According to a mupdf developer I talked to, mupdf-1.4 is due to be released within the next month. I'll wait until then & update my build for 1.4. It's worth mentioning also: the "critical security bug" only affects XPS documents, not PDFs. XPS is still pretty rare in the wild... "critical" is probably too strong of a word. From leva at ecentrum.hu Tue Feb 25 12:52:46 2014 From: leva at ecentrum.hu (LEVAI Daniel) Date: Tue, 25 Feb 2014 13:52:46 +0100 Subject: [Slackbuilds-users] mupdf In-Reply-To: References: <20140223100707.GA3035@serenity.local> Message-ID: <20140225125246.GB16077@serenity.local> On h, febr 24, 2014 at 17:51:52 -0500, B Watson wrote: > On 2/23/14, LEVAI Daniel wrote: > > > If the maintainer won't step up, > > Hm, did I miss an email from you? Usually it's better to email the > maintainer directly instead of the list... My bad. My experience with sbo slackbuild maintainers is that most of them (read 9 out of 10) don't even bother to reply or do something with patches or new packages. I didn't intend to get around you, I just thought that a maintainer supposedly reads the mailing list, and if not (hence the phrase "won't step up"), then the package should be updated anyways. [...] > It's worth mentioning also: the "critical security bug" only affects XPS > documents, not PDFs. XPS is still pretty rare in the wild... "critical" > is probably too strong of a word. Critical means exactly that. Critical. Executing arbitrary code (as is the case with most of the stack overflows) _is_ critical. Also, your definition of "pretty rare" doesn't hold; how would you know who uses it on a day to day basis... Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From kingbeowulf at gmail.com Tue Feb 25 18:26:07 2014 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 25 Feb 2014 10:26:07 -0800 Subject: [Slackbuilds-users] mupdf In-Reply-To: <20140225125246.GB16077@serenity.local> References: <20140223100707.GA3035@serenity.local> <20140225125246.GB16077@serenity.local> Message-ID: On Tuesday, February 25, 2014, LEVAI Daniel wrote: > On h, febr 24, 2014 at 17:51:52 -0500, B Watson wrote: > > On 2/23/14, LEVAI Daniel > wrote: > > > > > If the maintainer won't step up, > > > > Hm, did I miss an email from you? Usually it's better to email the > > maintainer directly instead of the list... > > My bad. My experience with sbo slackbuild maintainers is that most of > them (read 9 out of 10) don't even bother to reply or do something with > patches or new packages. I didn't intend to get around you, I just > thought that a maintainer supposedly reads the mailing list, and if > not (hence the phrase "won't step up"), then the package should be > updated anyways. > > [...] > > It's worth mentioning also: the "critical security bug" only affects XPS > > documents, not PDFs. XPS is still pretty rare in the wild... "critical" > > is probably too strong of a word. > > Critical means exactly that. Critical. Executing arbitrary code (as is > the case with most of the stack overflows) _is_ critical. > Also, your definition of "pretty rare" doesn't hold; how would you know > who uses it on a day to day basis... > > > Just one man's opinion, but you really need to dump XPS. It was just another "not invented here" attempt by Microsoft http://www.howtogeek.com/148499/what-is-an-xps-file-and-why-does-windows-want-me-to-print-to-one/ -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Feb 25 18:32:20 2014 From: yalhcru at gmail.com (B Watson) Date: Tue, 25 Feb 2014 13:32:20 -0500 Subject: [Slackbuilds-users] mupdf In-Reply-To: <20140225125246.GB16077@serenity.local> References: <20140223100707.GA3035@serenity.local> <20140225125246.GB16077@serenity.local> Message-ID: On 2/25/14, LEVAI Daniel wrote: > thought that a maintainer supposedly reads the mailing list, and if > not (hence the phrase "won't step up"), then the package should be > updated anyways. Generally when the maintainer's not responding to direct email or the list, the admins don't update the package themselves. Either someone takes it over (usually the one reporting the issue), or the package will be dropped from the repo. > Critical means exactly that. Critical. Executing arbitrary code (as is > the case with most of the stack overflows) _is_ critical. > Also, your definition of "pretty rare" doesn't hold; how would you know > who uses it on a day to day basis... You're right. I should have thought that through better. Anyway, thanks for the heads-up. From willysr at slackbuilds.org Fri Feb 28 11:28:09 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 28 Feb 2014 18:28:09 +0700 Subject: [Slackbuilds-users] Packages Without Maintainer Message-ID: <531072C9.4080705@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Anyone interested on maintaining these packages? They have been abandoned for some time multimedia/realplayer audio/volwheel games/gtkballs libraries/libgnomecups desktop/gtk-kde4 desktop/obmenu desktop/openbox-themes development/google-appengine-pysdk development/google-appengine-gosdk development/gprolog development/polyml - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMQcskACgkQiHuDdNczM4F40wCeJb1+yXPRBZ4JU0mGeqY4gsWw 2BUAoJaT1ol0Z4qjwhC4FoyqR8/IsS1c =j9DG -----END PGP SIGNATURE----- From yalhcru at gmail.com Fri Feb 28 19:51:57 2014 From: yalhcru at gmail.com (B Watson) Date: Fri, 28 Feb 2014 14:51:57 -0500 Subject: [Slackbuilds-users] Packages Without Maintainer In-Reply-To: <531072C9.4080705@slackbuilds.org> References: <531072C9.4080705@slackbuilds.org> Message-ID: On 2/28/14, Willy Sudiarto Raharjo wrote: > games/gtkballs Taken, submission sitting in pending. > libraries/libgnomecups Looks like the only thing in the repo that uses this one is kicad, maybe its maintainer would be interested?