From willysr at slackbuilds.org Sat Aug 1 01:06:54 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 1 Aug 2015 08:06:54 +0700 Subject: [Slackbuilds-users] Updates - 20150801.1 Message-ID: <55BC1BAE.7090805@slackbuilds.org> Sat Aug 1 00:54:51 UTC 2015 academic/GeoGebra: Updated for version 5.0.135.0. academic/fet: Updated for version 5.27.5. academic/gaw3: Updated for version 20150228. academic/knime: Updated for version 2.12.0. academic/sage: Updated for version 6.8. academic/sigrok-cli: Added (command-line frontend for sigrok). audio/coverlovin: Added (Cover Art Downloader). audio/sunvox: Updated for version 1.9b. desktop/bashish: Added (theme enviroment for text terminals). desktop/imgurbash: Added (bash script uploader). desktop/luna-wallpapers: Update script. development/Arduino: Small fixes and binary version coexistence. development/SQLAlchemy: Updated for version 1.0.8. development/arduino: Updated for version 1.6.5. development/cpan2tgz: Update DOWNLOAD url. development/enki: Updated for version 15.05.0. development/groovy: Updated for version 2.4.4. development/meld3: Updated for version 3.14.0. development/neovim: Fix man page installation. development/poedit: Updated for version 1.8.3. development/thunderpad: Updated for version 20150716. games/eureka: Update README. games/mednafen: Updated for version 0.9.38.5. games/spring: Updated for version 100.0. gis/grass: Updated for version 7.0.1. graphics/blender: Updated for version 2.75a. graphics/darktable: Updated for version 1.6.8. graphics/graph-easy: Added (Convert or render graphs). graphics/opencollada: Updated for version 0.20150429. libraries/discogs-client: Updated for version 2.2.0. libraries/hoedown: Updated for version 3.0.3. libraries/libepoxy: Updated for version 1.3.1. libraries/libsigrok: Added (logic analyzers access library). libraries/libtelnet: Added (TELNET protocol handling library). libraries/mpir: Updated for version 2.7.0. libraries/pugixml: Added: (XML parser for C) libraries/qutepart: Updated for version 2.2.2. misc/dos2unix: Updated for version 7.2.3. misc/wcd: Updated for version 5.2.7. multimedia/Mopidy: Updated for version 1.0.8. multimedia/dvdauthor: New maintainer. multimedia/exaile: Updated for version 3.4.5. multimedia/tovid: Updated for version 0.35.2. network/chrony: Updated for version 2.1.1. network/claws-mail: Updated for version 3.12.0. network/ddclient: Updated for version 3.8.3. network/dillo: Updated for version 3.0.5. network/dropbox: Updated for version 3.8.5. network/exim: Updated for version 4.86. network/iojs: Updated for version 2.5.0. network/keybase-client: Updated for version 0.8.14. network/movgrab: Updated for version 1.2.1. network/mumble: Updated for version 1.2.10. network/murmur: Updated for version 1.2.10. network/opensmtpd: Fix dep. network/pidgin-facebookchat: Removed (replaced by purple-facebook). network/pidgin-whatsapp: Updated for version 0.8.5. network/purple-facebook: Added (Facebook Chat for Pidgin). network/putty: Updated for version 0.65. network/qTox: Updated for version 20150722. network/toxcore: Updated for version 20150722. network/twitter: Updated for version 1.17.1. network/vivaldi: Updated for version 1.0.231.3_1. network/youtube-dl: Updated for version 2015.07.28. office/ganttproject: Updated for version 2.7.1. office/libreoffice-helppack: Updated for version 4.4.5. office/libreoffice-langpack: Updated for version 4.4.5. office/libreoffice: Updated for version 4.4.5. office/mdp: Updated for version 1.0.1. office/tellico: New maintainer. perl/perl-YAML-Tiny: Updated for version 1.69. python/astroid: Updated for version 1.3.7. python/autopep8: Updated for version 1.2. python/pydf: Added (df clone written in python). python/python-future: Updated for version 0.15.0. python/python-oauthlib: Updated for version 1.0.1. python/selenium: Updated for version 2.47.0. system/adobe-source-code-pro-font: Updated for version 1.030. system/bicon: Added (Bidirectional Console). system/cronie: Updated for version 1.5.0. system/fish: Updated for version 2.2.0 + new maintainer. system/inxi: Updated for version 2.2.26. system/nvidia-driver: Updated for version 352.30. system/nvidia-kernel: Updated for version 352.30. system/qemu: Patched for CVE-2015-5154. system/slpkg: Updated for version 2.6.8. system/sysdig: Updated for version 0.1.102. system/thermal_daemon: Updated for version 1.4.3. system/tilda: Updated for version 1.2.4. system/tomb: Added (file encryption) system/unace: New download location. system/winetricks: Updated for version 20150706. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sat Aug 1 06:39:02 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 31 Jul 2015 23:39:02 -0700 Subject: [Slackbuilds-users] libgda compile is "brittle" fix Message-ID: <55BC6985.4060806@gmail.com> I have a mish-mash of Slackware64, 32 and multilib installs, and yes, multilib is not "officially" supported, but I sometimes NEED to compile on the faster multilib box as my VMs are slow due to hardware constraints. This may help a few: When running libgda.SlackBuild on a Slackware64 multilib system, one needs to add LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" to configure otherwise the compile still looks for /usr/lib/libgobject-2.0.so The error on Slackware64 multilib without LDFLAGS: make[2]: Entering directory `/tmp/SBo/libgda-5.2.2/providers/ldap' CC gdaprov-data-model-ldap.lo CC gda-ldap-provider.lo CC gda-ldap-util.lo CC libmain.lo CCLD libgda-ldap.la /usr/lib/libgobject-2.0.so: could not read symbols: File in wrong format collect2: error: ld returned 1 exit status make[2]: *** [libgda-ldap.la] Error 1 make[2]: Leaving directory `/tmp/SBo/libgda-5.2.2/providers/ldap' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/libgda-5.2.2/providers' make: *** [all-recursive] Error 1 libgda compiled fine on pure Slackware6. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ml at mareichelt.com Sat Aug 1 09:56:35 2015 From: ml at mareichelt.com (Markus Reichelt) Date: Sat, 1 Aug 2015 11:56:35 +0200 Subject: [Slackbuilds-users] python-mock up for grabs Message-ID: <20150801095635.GA31122@pc21.mareichelt.com> Aloha! http://slackbuilds.org/repository/14.1/python/mock/ is up for grabs since v1.10.2 it's no longer a dep of allmydata-tahoe[1] but it may be useful for someone else maintaining a python project with unit tests. [1]: This release no longer requires the "mock" library (which was previously used in the unit test suite). Shortly after the Tahoe-LAFS 1.10.1 release, a new version of "mock" was released (1.1.0) that proved to be incompatible with Tahoe's fork of setuptools, preventing Tahoe-1.10.1 from building at all. ref. https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2465 From jvogel4 at stny.rr.com Sat Aug 1 12:10:48 2015 From: jvogel4 at stny.rr.com (John Vogel) Date: Sat, 1 Aug 2015 08:10:48 -0400 Subject: [Slackbuilds-users] libgda compile is "brittle" fix In-Reply-To: <55BC6985.4060806@gmail.com> References: <55BC6985.4060806@gmail.com> Message-ID: <20150801081048.1ac702ee@stygian.lan> On Fri, 31 Jul 2015 23:39:02 -0700 King Beowulf wrote: > I have a mish-mash of Slackware64, 32 and multilib installs, and yes, > multilib is not "officially" supported, but I sometimes NEED to compile > on the faster multilib box as my VMs are slow due to hardware > constraints. This may help a few: > > When running libgda.SlackBuild on a Slackware64 multilib system, one > needs to add LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" to configure otherwise > the compile still looks for /usr/lib/libgobject-2.0.so > > The error on Slackware64 multilib without LDFLAGS: > > make[2]: Entering directory `/tmp/SBo/libgda-5.2.2/providers/ldap' > CC gdaprov-data-model-ldap.lo > CC gda-ldap-provider.lo > CC gda-ldap-util.lo > CC libmain.lo > CCLD libgda-ldap.la > /usr/lib/libgobject-2.0.so: could not read symbols: File in wrong format > collect2: error: ld returned 1 exit status > make[2]: *** [libgda-ldap.la] Error 1 > make[2]: Leaving directory `/tmp/SBo/libgda-5.2.2/providers/ldap' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/tmp/SBo/libgda-5.2.2/providers' > make: *** [all-recursive] Error 1 > > libgda compiled fine on pure Slackware6. > > -Ed > > I wonder if this is a pkg-config issue. So maybe builds could add something like: PKG_CONFIG_LIBDIR="/usr/lib${LIBDIRSUFFIX}/pkgconfig" \ CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ configure \ ... so that the correct pkg-config searcg directory matches the arch for the installation. Just a thought. John From glenn.becker at gmail.com Sat Aug 1 20:57:23 2015 From: glenn.becker at gmail.com (Glenn Becker) Date: Sat, 1 Aug 2015 16:57:23 -0400 Subject: [Slackbuilds-users] python-mock up for grabs In-Reply-To: <20150801095635.GA31122@pc21.mareichelt.com> References: <20150801095635.GA31122@pc21.mareichelt.com> Message-ID: I am willing to adopt. - Glenn On Sat, Aug 1, 2015 at 5:56 AM, Markus Reichelt wrote: > Aloha! > > http://slackbuilds.org/repository/14.1/python/mock/ is up for grabs > > since v1.10.2 it's no longer a dep of allmydata-tahoe[1] but it may be > useful for someone else maintaining a python project with unit tests. > > > [1]: This release no longer requires the "mock" library (which was > previously used in the unit test suite). Shortly after the > Tahoe-LAFS 1.10.1 release, a new version of "mock" was released > (1.1.0) that proved to be incompatible with Tahoe's fork of > setuptools, preventing Tahoe-1.10.1 from building at all. ref. > https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2465 > _______________________________________________ > 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 kingbeowulf at gmail.com Sat Aug 1 22:03:01 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 1 Aug 2015 15:03:01 -0700 Subject: [Slackbuilds-users] libgda compile is "brittle" fix In-Reply-To: <20150801081048.1ac702ee@stygian.lan> References: <55BC6985.4060806@gmail.com> <20150801081048.1ac702ee@stygian.lan> Message-ID: On Saturday, August 1, 2015, John Vogel wrote: > > > I wonder if this is a pkg-config issue. So maybe builds could add > something like: > > Uncertain. compiling on pure Slack64 VM worked fine. -ed -- 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 jvogel4 at stny.rr.com Sat Aug 1 22:25:21 2015 From: jvogel4 at stny.rr.com (John Vogel) Date: Sat, 1 Aug 2015 18:25:21 -0400 Subject: [Slackbuilds-users] libgda compile is "brittle" fix In-Reply-To: References: <55BC6985.4060806@gmail.com> <20150801081048.1ac702ee@stygian.lan> Message-ID: <20150801182521.4501266a@stygian.lan> On Sat, 1 Aug 2015 15:03:01 -0700 King Beowulf wrote: > On Saturday, August 1, 2015, John Vogel wrote: > > > > > > > I wonder if this is a pkg-config issue. So maybe builds could add > > something like: > > > > > Uncertain. compiling on pure Slack64 VM worked fine. > > -ed > Yep, makes sense. If you are building from pure 64bit or pure 32bit system, then pkg-config already knows where to look (in most cases and if you aren't like me and have stuff in /opt and various non-standard places). On a multilib/multiarch system, there are different pkg-config directories for each arch's .pc files: /usr/lib64/pkgconfig and /usr/lib/pkgconfig. Manipulating pkg-config can save a lot of grief when library and header paths can be different based on compile time arch. I often have to mess with pkg-config when I'm cross compiling, so I thought I'd chime in. I'm probably just muddying the waters, and if so, my apologies in advance. John From glenn.becker at gmail.com Sun Aug 2 02:06:07 2015 From: glenn.becker at gmail.com (Glenn Becker) Date: Sat, 1 Aug 2015 22:06:07 -0400 Subject: [Slackbuilds-users] did I miss some emails? Message-ID: Hi -- I was going down my list of SlackBuilds to update ... had gotten to perl-tree-dagnode and perl-www-mechanize and it seems as though they're now maintained by Brenton Earl (?). This is fine by me but I don't recall receiving any notification. Was I just too slow? Thanks, Glenn Becker -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Sun Aug 2 02:45:22 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 1 Aug 2015 21:45:22 -0500 Subject: [Slackbuilds-users] did I miss some emails? In-Reply-To: References: Message-ID: <20150801214522.07146405@shaggy.doo> On Sat, 1 Aug 2015 22:06:07 -0400 Glenn Becker wrote: > Hi -- > > I was going down my list of SlackBuilds to update ... had gotten to > > perl-tree-dagnode > > and > > perl-www-mechanize > > and it seems as though they're now maintained by Brenton Earl (?). This is > fine by me but I don't recall receiving any notification. Was I just too > slow? According to git, both of these were maintained by Binh Nguyen before Brenton. Are there public emails discussing you taking them over? -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From glenn.becker at gmail.com Sun Aug 2 02:48:21 2015 From: glenn.becker at gmail.com (Glenn Becker) Date: Sat, 1 Aug 2015 22:48:21 -0400 Subject: [Slackbuilds-users] did I miss some emails? In-Reply-To: <20150801214522.07146405@shaggy.doo> References: <20150801214522.07146405@shaggy.doo> Message-ID: Hi Erik - I believe there were emails on the list, but it's okay ... I just exchanged emails with Brenton & he's keeping them with my blessings, for what those are worth. ;^) It's really my fault for being slower than ... well, slow. G On Sat, Aug 1, 2015 at 10:45 PM, Erik Hanson wrote: > On Sat, 1 Aug 2015 22:06:07 -0400 > Glenn Becker wrote: > > > Hi -- > > > > I was going down my list of SlackBuilds to update ... had gotten to > > > > perl-tree-dagnode > > > > and > > > > perl-www-mechanize > > > > and it seems as though they're now maintained by Brenton Earl (?). This > is > > fine by me but I don't recall receiving any notification. Was I just too > > slow? > > According to git, both of these were maintained by Binh Nguyen before > Brenton. Are there public emails discussing you taking them over? > > > -- > Erik Hanson > > _______________________________________________ > 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 mralk3 at exitstatusone.com Sun Aug 2 02:52:51 2015 From: mralk3 at exitstatusone.com (MrAlk3) Date: Sat, 01 Aug 2015 20:52:51 -0600 Subject: [Slackbuilds-users] did I miss some emails? In-Reply-To: References: <20150801214522.07146405@shaggy.doo> Message-ID: <1812394.zm4ZnLShx0@mothership> Yes, looking back in past emails, I did contact the maintainer listed in the slack build scripts and received confirmation that I could assume maintenance. I had no idea someone else asked to maintain them. I only joined the slack builds users list some time last month. Thanks, Brenton Earl On Saturday, August 01, 2015 10:48:21 PM Glenn Becker wrote: > Hi Erik - > > I believe there were emails on the list, but it's okay ... I just exchanged > emails with Brenton & he's keeping them with my blessings, for what those > are worth. ;^) > > It's really my fault for being slower than ... well, slow. > > G > > > > On Sat, Aug 1, 2015 at 10:45 PM, Erik Hanson wrote: > > On Sat, 1 Aug 2015 22:06:07 -0400 > > > > Glenn Becker wrote: > > > Hi -- > > > > > > I was going down my list of SlackBuilds to update ... had gotten to > > > > > > perl-tree-dagnode > > > > > > and > > > > > > perl-www-mechanize > > > > > > and it seems as though they're now maintained by Brenton Earl (?). This > > > > is > > > > > fine by me but I don't recall receiving any notification. Was I just too > > > slow? > > > > According to git, both of these were maintained by Binh Nguyen before > > Brenton. Are there public emails discussing you taking them over? > > > > > > -- > > Erik Hanson > > > > _______________________________________________ > > 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 willysr at slackbuilds.org Sun Aug 2 06:33:48 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 2 Aug 2015 13:33:48 +0700 Subject: [Slackbuilds-users] did I miss some emails? In-Reply-To: References: Message-ID: <55BDB9CC.6040709@slackbuilds.org> > I was going down my list of SlackBuilds to update ... had gotten to > > perl-tree-dagnode > > and > > perl-www-mechanize > > and it seems as though they're now maintained by Brenton Earl (?). This is > fine by me but I don't recall receiving any notification. Was I just too > slow? Brenton contacted me and he was looking for slackbuilds that were no longer maintained and i gave him some list from some maintainers whom i know no longer active , which includes perl-www-mechanize so he took over. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Aug 2 07:30:56 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 2 Aug 2015 00:30:56 -0700 Subject: [Slackbuilds-users] libgda compile is "brittle" fix In-Reply-To: <20150801182521.4501266a@stygian.lan> References: <55BC6985.4060806@gmail.com> <20150801081048.1ac702ee@stygian.lan> <20150801182521.4501266a@stygian.lan> Message-ID: <55BDC730.7010805@gmail.com> On 08/01/2015 03:25 PM, John Vogel wrote: > On Sat, 1 Aug 2015 15:03:01 -0700 > King Beowulf wrote: > >> On Saturday, August 1, 2015, John Vogel wrote: >> >>> >>> >>> I wonder if this is a pkg-config issue. So maybe builds could add >>> something like: >>> >>> >> Uncertain. compiling on pure Slack64 VM worked fine. >> >> -ed >> > > Yep, makes sense. If you are building from pure 64bit or pure > 32bit system, then pkg-config already knows where to look > (in most cases and if you aren't like me and have stuff in > /opt and various non-standard places). > On a multilib/multiarch system, there are different pkg-config > directories for each arch's .pc files: > > /usr/lib64/pkgconfig and /usr/lib/pkgconfig. > > Manipulating pkg-config can save a lot of grief when library and > header paths can be different based on compile time arch. > I often have to mess with pkg-config when I'm cross compiling, > so I thought I'd chime in. I'm probably just muddying the > waters, and if so, my apologies in advance. > > John I'm a bit clueless on this autotools and pkgconfig stuff. What would the benefit be to do PKG_CONFIG_LIBDIR="/usr/lib${LIBDIRSUFFIX}/pkgconfig" versus LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" To get qemu to compile with a newer libusb (the one in 14.1 is too old), I needed a static lib and a pkgconfig. But in libgda LDFLAGS appears sufficient. For this particular libdga case (and some others), I suspect a "bug" or "laziness" on the part of upstream in not making sure of [/usr/lib | /usr/lib64]. Unless they are not sticking to FHS standards (Debian)? From what I understand of the multilib set-up. PKG_CONFIG_PATH is set to assume pure x64_64: # set | grep PKG_CONFIG_PATH PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig To cross-compile x86, one needs to run /etc/profile.d/32dev.sh to reset PKG_CONFIG_PATH to PKG_CONFIG_PATH="/usr/local/lib/pkgconfig:/usr/lib/pkgconfig" before compiling 32-bit software. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From jvogel4 at stny.rr.com Sun Aug 2 15:17:15 2015 From: jvogel4 at stny.rr.com (John Vogel) Date: Sun, 2 Aug 2015 11:17:15 -0400 Subject: [Slackbuilds-users] libgda compile is "brittle" fix In-Reply-To: <55BDC730.7010805@gmail.com> References: <55BC6985.4060806@gmail.com> <20150801081048.1ac702ee@stygian.lan> <20150801182521.4501266a@stygian.lan> <55BDC730.7010805@gmail.com> Message-ID: <20150802111715.17a0b9f0@stygian.lan> On Sun, 2 Aug 2015 00:30:56 -0700 King Beowulf wrote: > On 08/01/2015 03:25 PM, John Vogel wrote: > > On Sat, 1 Aug 2015 15:03:01 -0700 > > King Beowulf wrote: > > > >> On Saturday, August 1, 2015, John Vogel wrote: > >> > >>> > >>> > >>> I wonder if this is a pkg-config issue. So maybe builds could add > >>> something like: > >>> > >>> > >> Uncertain. compiling on pure Slack64 VM worked fine. > >> > >> -ed > >> > > > > Yep, makes sense. If you are building from pure 64bit or pure > > 32bit system, then pkg-config already knows where to look > > (in most cases and if you aren't like me and have stuff in > > /opt and various non-standard places). > > On a multilib/multiarch system, there are different pkg-config > > directories for each arch's .pc files: > > > > /usr/lib64/pkgconfig and /usr/lib/pkgconfig. > > > > Manipulating pkg-config can save a lot of grief when library and > > header paths can be different based on compile time arch. > > I often have to mess with pkg-config when I'm cross compiling, > > so I thought I'd chime in. I'm probably just muddying the > > waters, and if so, my apologies in advance. > > > > John > > I'm a bit clueless on this autotools and pkgconfig stuff. What would > the benefit be to do > > PKG_CONFIG_LIBDIR="/usr/lib${LIBDIRSUFFIX}/pkgconfig" > > versus > > LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" > > To get qemu to compile with a newer libusb (the one in 14.1 is too old), > I needed a static lib and a pkgconfig. But in libgda LDFLAGS appears > sufficient. For this particular libdga case (and some others), I > suspect a "bug" or "laziness" on the part of upstream in not making sure > of [/usr/lib | /usr/lib64]. Unless they are not sticking to FHS > standards (Debian)? > > From what I understand of the multilib set-up. PKG_CONFIG_PATH is set to > assume pure x64_64: > > # set | grep PKG_CONFIG_PATH > PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig > > To cross-compile x86, one needs to run /etc/profile.d/32dev.sh to reset > PKG_CONFIG_PATH to > > PKG_CONFIG_PATH="/usr/local/lib/pkgconfig:/usr/lib/pkgconfig" > > before compiling 32-bit software. > > -Ed > I'm not saying that there is anything wrong with using LDFLAGS to adjust things for the linker. I'm not an expert on autotools stuff, either, but I try to pick stuff up as I go along. Hopefully, someone who understands this stuff better than me is willing to correct me if I get something wrong. My first reason about using the pkg-config environment variable was that it is more general. The man page for pkg-config describes the uses of both PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR. The first one gives a list, just like PATH, for pkg-config to search for .pc files; the second one replaces the default search directory. I'm not sure, and I would have to play around some more with them, which is actually more appropriate for what we're talking about here. I think the point is to get the pkg-config to only spit out appropriate libdir and includedir values in the CFLAGS, CPPFLAGS, LDFLAGS, and LDLIBS variables for the arch being built for. Overriding or bypassing a library that is installed on the host with one that is locally built is another usage. Like you are talking about with qemu and libusb; just using LDFLAGS wouldn't be enough there, you need adjustments to CPPFLAGS and CFLAGS, and possibly LDLIBS also. I'm nearly in over my head here, so if someone can correct me where or if I've strayed, please feel free to step in. John From lemelle at cbpf.br Mon Aug 3 00:29:54 2015 From: lemelle at cbpf.br (lemelle at cbpf.br) Date: Sun, 02 Aug 2015 21:29:54 -0300 Subject: [Slackbuilds-users] Make a Script in Slackbuilding -> OpenBroadcaster Message-ID: <20150802212954.Horde.UMNHJsCPne9VvrYCbaCnPDA@p0m1.cat.cbpf.br> Hello I m newbie in here, a need install OpenBroadcaster to streaming alive my video-classes in new youtube evnte alive. A think that program is better than not free programns. this the site https://obsproject.com/download#linux this Install instructions: https://github.com/jp9000/obs-studio/wiki/Install-Instructions I like to learn a make a script and help us, by i m very newbie in slackware and linux. I try make slackware for desktopers Thanks Diego From klaatu at straightedgelinux.com Mon Aug 3 00:32:45 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Mon, 3 Aug 2015 12:32:45 +1200 Subject: [Slackbuilds-users] Make a Script in Slackbuilding -> OpenBroadcaster In-Reply-To: <20150802212954.Horde.UMNHJsCPne9VvrYCbaCnPDA@p0m1.cat.cbpf.br> References: <20150802212954.Horde.UMNHJsCPne9VvrYCbaCnPDA@p0m1.cat.cbpf.br> Message-ID: <55BEB6AD.1040105@straightedgelinux.com> I have a script here: https://gitlab.com/slackermedia/slackbuilds/tree/master/Multimedia/obs-studio A quickstart is here: http://slackermedia.info/book/doku.php?id=obs Works great for me. -klaatu On 08/03/2015 12:29 PM, lemelle at cbpf.br wrote: > > Hello I m newbie in here, a need install OpenBroadcaster to streaming > alive my video-classes in new youtube evnte alive. A think that program > is better than not free programns. > > this the site https://obsproject.com/download#linux > > this Install instructions: > https://github.com/jp9000/obs-studio/wiki/Install-Instructions > > > I like to learn a make a script and help us, by i m very newbie in > slackware and linux. > > > I try make slackware for desktopers > > > Thanks > > Diego > _______________________________________________ > 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 yalhcru at gmail.com Mon Aug 3 02:29:07 2015 From: yalhcru at gmail.com (B Watson) Date: Sun, 2 Aug 2015 22:29:07 -0400 Subject: [Slackbuilds-users] GraphicsMagick maintainer? Message-ID: Trying to contact the maintainer of GraphicsMagick... MAINTAINER="Giovanne Castro" EMAIL="giovannefc at terra.com.br" Mail to that address bounces. Are you on this mailing list, by any chance? From willysr at gmail.com Mon Aug 3 05:06:34 2015 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Mon, 3 Aug 2015 12:06:34 +0700 Subject: [Slackbuilds-users] GraphicsMagick maintainer? In-Reply-To: References: Message-ID: See cgit for history If the maintainer is not active for a long time and his email is bouncing, you can consider him inactive and go ahead of taking the package Sorry for top posting :) Willy Sudiarto Raharjo -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Mon Aug 3 05:35:10 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 2 Aug 2015 22:35:10 -0700 Subject: [Slackbuilds-users] Re: Slackbuilds.org - Wrong checksum? In-Reply-To: References: Message-ID: <55BEFD8E.3070303@gmail.com> On 08/02/2015 07:15 PM, Altiris BL wrote: > Good evening, I'll get straight to the point. I believe your checksum > for the murmur package on slackbuilds.org > http://slackbuilds.org/repository/14.1/network/murmur/?search=murmur is > incorrect. When downloading via the source link, the md5sum comes out to > be 14ab2e9174b7ca87623e63aa56dd6d5b. I have also tried from the official > (I think its official) http://mumble.info/snapshot/mumble-1.2.10.tar.gz > and the checksum is the same as above. However on your slackbuild it > states it is 228fff5975a61872b83052be97e2eabf) > > Thank you for maintaining murmur, I really appreciate it! Just thought I > would give you a heads up! Hello That's very interesting. The Sourceforge and GIT repos for mumble yield different md5sums: $ md5sum *.tar.gz 228fff5975a61872b83052be97e2eabf git_mumble-1.2.10.tar.gz 228fff5975a61872b83052be97e2eabf SBo_mumble-1.2.10.tar.gz 14ab2e9174b7ca87623e63aa56dd6d5b sf_mumble-1.2.10.tar.gz The differences appear to be in the way the SF and git sources are packaged. Looks like SF stripped out a bunch of 3rd party licenses, files and code, while adding other bits. Except for some .git* specific files, I don't yet know what this fully means. When in doubt, use the git version: https://github.com/mumble-voip/mumble/releases/tag/1.2.10 FYI: do not download "snapshots" as the md5sum will often be different from the "release" and make sure you compare git to git and SF to SF for downloads. This is definitely going to cause some confusion. It will cause issues with automatic SBo tools. mumble and murmur share the same source. BTW, 1.2.10 is identical to 1.2.9. Upstream just bumped version number due to needed to recompile there windows, mac, and linux static binary releases for openssl. If you dynamically linked openSSL, you are safe to use 1.2.9. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From bocke at slackware-srbija.org Mon Aug 3 12:06:24 2015 From: bocke at slackware-srbija.org (Bojan Popovic) Date: Mon, 3 Aug 2015 14:06:24 +0200 Subject: [Slackbuilds-users] Faulty SlackBuild in the queue In-Reply-To: References: Message-ID: <20150803140624.066b1b93@artwo.universe.uni> Hi. Can someone please delete bochs.tar.gz from the queue? I'm retesting it right now and I've just found a small error in the SlackBuild I'd like to fix. Thanx in advance, Bojan. From bocke at slackware-srbija.org Mon Aug 3 12:38:09 2015 From: bocke at slackware-srbija.org (Bojan Popovic) Date: Mon, 3 Aug 2015 14:38:09 +0200 Subject: [Slackbuilds-users] Faulty SlackBuild in the queue In-Reply-To: <20150803140624.066b1b93@artwo.universe.uni> References: <20150803140624.066b1b93@artwo.universe.uni> Message-ID: <20150803143809.178c0af7@artwo.universe.uni> Solved. Willy reminded me to enter the submission info in the removal form. Thanx once again. Bojan. On Mon, 3 Aug 2015 14:06:24 +0200 Bojan Popovic wrote: > Hi. > > Can someone please delete bochs.tar.gz from the queue? I'm retesting > it right now and I've just found a small error in the SlackBuild I'd > like to fix. > > Thanx in advance, > > Bojan. > _______________________________________________ > 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 kingbeowulf at gmail.com Mon Aug 3 22:32:09 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 3 Aug 2015 15:32:09 -0700 Subject: [Slackbuilds-users] mumble/murmur .info d/l update; nvidia-kernel.Slackbuild typo Message-ID: <55BFEBE9.3080304@gmail.com> Admins: Diffs attached: 1. mumble_location_update.diff Correct links and md5 for git release instead of sourceforge 2. nvidia-driver_typo_fix.diff add missing ">" that got lost in upload Thanks Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: mumble_location_update.diff Type: text/x-patch Size: 1275 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-driver_typo_fix.diff Type: text/x-patch Size: 855 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lemelle at cbpf.br Tue Aug 4 03:04:51 2015 From: lemelle at cbpf.br (lemelle at cbpf.br) Date: Tue, 04 Aug 2015 00:04:51 -0300 Subject: [Slackbuilds-users] Try installing OBS-Studio and i receive this message Message-ID: <20150804000451.Horde.p1YPTsCPne9VwCvTmIKBMNA@p0m1.cat.cbpf.br> CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message): Could NOT find FFmpeg (missing: FFMPEG_AVCODEC_LIBRARIES FFMPEG_AVCODEC_INCLUDE_DIRS avcodec avfilter avdevice avutil swscale avformat swresample) Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_FAILURE_MESSAGE) cmake/Modules/FindFFmpeg.cmake:147 (find_package_handle_standard_args) deps/libff/CMakeLists.txt:4 (find_package) I dont know what i can do From chris.willing at iinet.net.au Tue Aug 4 03:59:56 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 4 Aug 2015 13:59:56 +1000 Subject: [Slackbuilds-users] Try installing OBS-Studio and i receive this message In-Reply-To: <20150804000451.Horde.p1YPTsCPne9VwCvTmIKBMNA@p0m1.cat.cbpf.br> References: <20150804000451.Horde.p1YPTsCPne9VwCvTmIKBMNA@p0m1.cat.cbpf.br> Message-ID: <55C038BC.5000802@iinet.net.au> On 04/08/15 13:04, lemelle at cbpf.br wrote: > > > CMake Error at > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 > (message): > Could NOT find FFmpeg (missing: FFMPEG_AVCODEC_LIBRARIES > FFMPEG_AVCODEC_INCLUDE_DIRS avcodec avfilter avdevice avutil swscale > avformat swresample) > Call Stack (most recent call first): > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 > (_FPHSA_FAILURE_MESSAGE) > cmake/Modules/FindFFmpeg.cmake:147 (find_package_handle_standard_args) > deps/libff/CMakeLists.txt:4 (find_package) > > > > > I dont know what i can do Install ffmpeg first (see https://gitlab.com/slackermedia/slackbuilds/blob/master/Multimedia/obs-studio/README). chris From klaatu at straightedgelinux.com Tue Aug 4 05:55:23 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Tue, 4 Aug 2015 17:55:23 +1200 Subject: [Slackbuilds-users] Try installing OBS-Studio and i receive this message In-Reply-To: <20150804000451.Horde.p1YPTsCPne9VwCvTmIKBMNA@p0m1.cat.cbpf.br> References: <20150804000451.Horde.p1YPTsCPne9VwCvTmIKBMNA@p0m1.cat.cbpf.br> Message-ID: <55C053CB.7060009@straightedgelinux.com> On 08/04/2015 03:04 PM, lemelle at cbpf.br wrote: > > > CMake Error at > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 > (message): > Could NOT find FFmpeg (missing: FFMPEG_AVCODEC_LIBRARIES > FFMPEG_AVCODEC_INCLUDE_DIRS avcodec avfilter avdevice avutil swscale > avformat swresample) > Call Stack (most recent call first): > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 > (_FPHSA_FAILURE_MESSAGE) > cmake/Modules/FindFFmpeg.cmake:147 (find_package_handle_standard_args) > deps/libff/CMakeLists.txt:4 (find_package) > > > > > I dont know what i can do > _______________________________________________ > 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/ > > > You should always read the README before buidling ;^) Once you have all the pre-requisites that you want installed, it should build fine. I am running it on Slackware64-14.1 myself and it performs quite nicely. -klaatu From slackalaxy at gmail.com Tue Aug 4 15:45:36 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 4 Aug 2015 18:45:36 +0300 Subject: [Slackbuilds-users] categories/tags Message-ID: Hi. I was reading the categories/tags discussion. I think people would mostly browse SBo by Category, if they just want to get an idea of what's in the repo or casually looking for something that may be useful. The problem is that the programs' names are often not related to what the software actually does. Therefore, a short description next to the name may make things clearer and give the reader a quick explanation of what the program is for. Something like this: http://www.student.oulu.fi/~ppetrov/temp/image4198.png The "Description" column lists the short description in brackets from the slack-desc file of each entry just a thought... bye Petar PS: I changed my email address. -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Tue Aug 4 16:58:34 2015 From: didier at slint.fr (Didier Spaier) Date: Tue, 4 Aug 2015 18:58:34 +0200 Subject: [Slackbuilds-users] categories/tags In-Reply-To: References: Message-ID: <55C0EF3A.7030600@slint.fr> On 04/08/2015 17:45, Petar Petrov wrote: Something like this: > http://www.student.oulu.fi/~ppetrov/temp/image4198.png > Fake link. Why? IMHO we shouldn't see that in a list.. Didier From Jim.Diamond at acadiau.ca Tue Aug 4 17:07:04 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Tue, 4 Aug 2015 14:07:04 -0300 Subject: [Slackbuilds-users] categories/tags In-Reply-To: <55C0EF3A.7030600@slint.fr> References: <55C0EF3A.7030600@slint.fr> Message-ID: <20150804170704.GA30464@jdiamond-nb2> On Tue, Aug 4, 2015 at 18:58 (+0200), Didier Spaier wrote: > On 04/08/2015 17:45, Petar Petrov wrote: > Something like this: >>http://www.student.oulu.fi/~ppetrov/temp/image4198.png >> > Fake link. Why? You don't think all the Slackware users won't be excited about some M$ stuff??? ;-) From ryan.q at linux.com Tue Aug 4 17:08:56 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Tue, 4 Aug 2015 10:08:56 -0700 Subject: [Slackbuilds-users] categories/tags In-Reply-To: <20150804170704.GA30464@jdiamond-nb2> References: <55C0EF3A.7030600@slint.fr> <20150804170704.GA30464@jdiamond-nb2> Message-ID: > > Something like this: > > >>http://www.student.oulu.fi/~ppetrov/temp/image4198.png > >>< https://outlook.office365.com/owa/redir.aspx?REF=Zhh7BjII0EPKPs6tbV5BiRA25WzipQhwwdEU84tHrUonraeY45zSCAFodHRwOi8vd3d3LnN0dWRlbnQub3VsdS5maS9-cHBldHJvdi90ZW1wL2ltYWdlNDE5OC5wbmc .> > > > Fake link. Why? > > You don't think all the Slackware users won't be excited about some M$ > stuff??? ;-) Almost makes me want to use windows again ... how much did they pay you Petar? -------------- next part -------------- An HTML attachment was scrubbed... URL: From lemelle at cbpf.br Tue Aug 4 17:19:31 2015 From: lemelle at cbpf.br (lemelle at cbpf.br) Date: Tue, 04 Aug 2015 14:19:31 -0300 Subject: [Slackbuilds-users] Try installing OBS-Studio and i receive this message > (lemelle@cbpf.br) In-Reply-To: References: Message-ID: <20150804141931.Horde.9yhrAcCPne9VwPQjMGVlBDA@p0m1.cat.cbpf.br> Sorry was ate night and after send this e-mail i can remember about installing de ffmpeg. How i can respond only to the subject in this list? I receive a resume with all send e-mail together Citando slackbuilds-users-request at slackbuilds.org: > Send SlackBuilds-users mailing list submissions to > slackbuilds-users at slackbuilds.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > or, via email, send a message with subject or body 'help' to > slackbuilds-users-request at slackbuilds.org > > You can reach the person managing the list at > slackbuilds-users-owner at slackbuilds.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of SlackBuilds-users digest..." > > > Today's Topics: > > 1. Re: Slackbuilds.org - Wrong checksum? (King Beowulf) > 2. Faulty SlackBuild in the queue (Bojan Popovic) > 3. Re: Faulty SlackBuild in the queue (Bojan Popovic) > 4. mumble/murmur .info d/l update; nvidia-kernel.Slackbuild > typo (King Beowulf) > 5. Try installing OBS-Studio and i receive this message > (lemelle at cbpf.br) > 6. Re: Try installing OBS-Studio and i receive this message > (Christoph Willing) > 7. Re: Try installing OBS-Studio and i receive this message (Klaatu) > 8. categories/tags (Petar Petrov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 2 Aug 2015 22:35:10 -0700 > From: King Beowulf > To: Altiris BL , "SlackBuilds.org Users List" > > Subject: [Slackbuilds-users] Re: Slackbuilds.org - Wrong checksum? > Message-ID: <55BEFD8E.3070303 at gmail.com> > Content-Type: text/plain; charset="utf-8" > > On 08/02/2015 07:15 PM, Altiris BL wrote: >> Good evening, I'll get straight to the point. I believe your checksum >> for the murmur package on slackbuilds.org >> http://slackbuilds.org/repository/14.1/network/murmur/?search=murmur is >> incorrect. When downloading via the source link, the md5sum comes out to >> be 14ab2e9174b7ca87623e63aa56dd6d5b. I have also tried from the official >> (I think its official) http://mumble.info/snapshot/mumble-1.2.10.tar.gz >> and the checksum is the same as above. However on your slackbuild it >> states it is 228fff5975a61872b83052be97e2eabf) >> >> Thank you for maintaining murmur, I really appreciate it! Just thought I >> would give you a heads up! > > Hello > > That's very interesting. The Sourceforge and GIT repos for mumble yield > different md5sums: > > $ md5sum *.tar.gz > 228fff5975a61872b83052be97e2eabf git_mumble-1.2.10.tar.gz > 228fff5975a61872b83052be97e2eabf SBo_mumble-1.2.10.tar.gz > 14ab2e9174b7ca87623e63aa56dd6d5b sf_mumble-1.2.10.tar.gz > > The differences appear to be in the way the SF and git sources are > packaged. Looks like SF stripped out a bunch of 3rd party licenses, > files and code, while adding other bits. Except for some .git* specific > files, I don't yet know what this fully means. When in doubt, use the > git version: > > https://github.com/mumble-voip/mumble/releases/tag/1.2.10 > > FYI: do not download "snapshots" as the md5sum will often be different > from the "release" and make sure you compare git to git and SF to SF for > downloads. This is definitely going to cause some confusion. It will > cause issues with automatic SBo tools. > > mumble and murmur share the same source. BTW, 1.2.10 is identical to > 1.2.9. Upstream just bumped version number due to needed to recompile > there windows, mac, and linux static binary releases for openssl. > > If you dynamically linked openSSL, you are safe to use 1.2.9. > > -Ed > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 181 bytes > Desc: OpenPGP digital signature > URL: > > > ------------------------------ > > Message: 2 > Date: Mon, 3 Aug 2015 14:06:24 +0200 > From: Bojan Popovic > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Faulty SlackBuild in the queue > Message-ID: <20150803140624.066b1b93 at artwo.universe.uni> > Content-Type: text/plain; charset=US-ASCII > > Hi. > > Can someone please delete bochs.tar.gz from the queue? I'm retesting it > right now and I've just found a small error in the SlackBuild I'd like > to fix. > > Thanx in advance, > > Bojan. > > > ------------------------------ > > Message: 3 > Date: Mon, 3 Aug 2015 14:38:09 +0200 > From: Bojan Popovic > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Faulty SlackBuild in the queue > Message-ID: <20150803143809.178c0af7 at artwo.universe.uni> > Content-Type: text/plain; charset=US-ASCII > > Solved. Willy reminded me to enter the submission info in the removal > form. > > Thanx once again. > > Bojan. > > On Mon, 3 Aug 2015 14:06:24 +0200 > Bojan Popovic wrote: > >> Hi. >> >> Can someone please delete bochs.tar.gz from the queue? I'm retesting >> it right now and I've just found a small error in the SlackBuild I'd >> like to fix. >> >> Thanx in advance, >> >> Bojan. >> _______________________________________________ >> 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/ >> > > > > ------------------------------ > > Message: 4 > Date: Mon, 3 Aug 2015 15:32:09 -0700 > From: King Beowulf > To: "SlackBuilds.org Users List" > Subject: [Slackbuilds-users] mumble/murmur .info d/l update; > nvidia-kernel.Slackbuild typo > Message-ID: <55BFEBE9.3080304 at gmail.com> > Content-Type: text/plain; charset="utf-8" > > Admins: > > Diffs attached: > > 1. mumble_location_update.diff > Correct links and md5 for git release instead of sourceforge > > 2. nvidia-driver_typo_fix.diff > add missing ">" that got lost in upload > > Thanks > Ed > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: mumble_location_update.diff > Type: text/x-patch > Size: 1275 bytes > Desc: not available > URL: > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: nvidia-driver_typo_fix.diff > Type: text/x-patch > Size: 855 bytes > Desc: not available > URL: > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 181 bytes > Desc: OpenPGP digital signature > URL: > > > ------------------------------ > > Message: 5 > Date: Tue, 04 Aug 2015 00:04:51 -0300 > From: lemelle at cbpf.br > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Try installing OBS-Studio and i receive > this message > Message-ID: > <20150804000451.Horde.p1YPTsCPne9VwCvTmIKBMNA at p0m1.cat.cbpf.br> > Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes > > > > CMake Error at > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 > (message): > Could NOT find FFmpeg (missing: FFMPEG_AVCODEC_LIBRARIES > FFMPEG_AVCODEC_INCLUDE_DIRS avcodec avfilter avdevice avutil swscale > avformat swresample) > Call Stack (most recent call first): > > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 > (_FPHSA_FAILURE_MESSAGE) > cmake/Modules/FindFFmpeg.cmake:147 (find_package_handle_standard_args) > deps/libff/CMakeLists.txt:4 (find_package) > > > > > I dont know what i can do > > > ------------------------------ > > Message: 6 > Date: Tue, 4 Aug 2015 13:59:56 +1000 > From: Christoph Willing > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Try installing OBS-Studio and i > receive this message > Message-ID: <55C038BC.5000802 at iinet.net.au> > Content-Type: text/plain; charset=utf-8; format=flowed > > > > On 04/08/15 13:04, lemelle at cbpf.br wrote: >> >> >> CMake Error at >> /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 >> (message): >> Could NOT find FFmpeg (missing: FFMPEG_AVCODEC_LIBRARIES >> FFMPEG_AVCODEC_INCLUDE_DIRS avcodec avfilter avdevice avutil swscale >> avformat swresample) >> Call Stack (most recent call first): >> /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 >> (_FPHSA_FAILURE_MESSAGE) >> cmake/Modules/FindFFmpeg.cmake:147 (find_package_handle_standard_args) >> deps/libff/CMakeLists.txt:4 (find_package) >> >> >> >> >> I dont know what i can do > > Install ffmpeg first (see > https://gitlab.com/slackermedia/slackbuilds/blob/master/Multimedia/obs-studio/README). > > chris > > > > ------------------------------ > > Message: 7 > Date: Tue, 4 Aug 2015 17:55:23 +1200 > From: Klaatu > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Try installing OBS-Studio and i > receive this message > Message-ID: <55C053CB.7060009 at straightedgelinux.com> > Content-Type: text/plain; charset=windows-1252 > > On 08/04/2015 03:04 PM, lemelle at cbpf.br wrote: >> >> >> CMake Error at >> /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 >> (message): >> Could NOT find FFmpeg (missing: FFMPEG_AVCODEC_LIBRARIES >> FFMPEG_AVCODEC_INCLUDE_DIRS avcodec avfilter avdevice avutil swscale >> avformat swresample) >> Call Stack (most recent call first): >> /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 >> (_FPHSA_FAILURE_MESSAGE) >> cmake/Modules/FindFFmpeg.cmake:147 (find_package_handle_standard_args) >> deps/libff/CMakeLists.txt:4 (find_package) >> >> >> >> >> I dont know what i can do >> _______________________________________________ >> 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/ >> >> >> > > You should always read the README before buidling ;^) > > Once you have all the pre-requisites that you want installed, it should > build fine. I am running it on Slackware64-14.1 myself and it performs > quite nicely. > > -klaatu > > > ------------------------------ > > Message: 8 > Date: Tue, 4 Aug 2015 18:45:36 +0300 > From: Petar Petrov > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] categories/tags > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Hi. > > I was reading the categories/tags discussion. > > I think people would mostly browse SBo by Category, if they just want to > get an idea of what's in the repo or casually looking for something that > may be useful. > > The problem is that the programs' names are often not related to what the > software actually does. Therefore, a short description next to the name may > make things clearer and give the reader a quick explanation of what the > program is for. Something like this: > > http://www.student.oulu.fi/~ppetrov/temp/image4198.png > > > The "Description" column lists the short description in brackets from the > slack-desc file of each entry > > just a thought... > > bye > > Petar > > PS: I changed my email address. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > ------------------------------ > > End of SlackBuilds-users Digest, Vol 112, Issue 4 > ************************************************* From slackalaxy at gmail.com Tue Aug 4 17:56:22 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 4 Aug 2015 20:56:22 +0300 Subject: [Slackbuilds-users] categories/tags In-Reply-To: References: <55C0EF3A.7030600@slint.fr> <20150804170704.GA30464@jdiamond-nb2> Message-ID: hi, sorry for the link... That's my University's mail, I don't know why the link was copied like that... Here's what I had in mind: http://www.student.oulu.fi/~ppetrov/temp/image4198.png and the MS mail is the reason I started using gmail for the SBo mailing list -petar 2015-08-04 20:08 GMT+03:00 Ryan P.C. McQuen : > > > > Something like this: > > > > >>http://www.student.oulu.fi/~ppetrov/temp/image4198.png > > >>< > https://outlook.office365.com/owa/redir.aspx?REF=Zhh7BjII0EPKPs6tbV5BiRA25WzipQhwwdEU84tHrUonraeY45zSCAFodHRwOi8vd3d3LnN0dWRlbnQub3VsdS5maS9-cHBldHJvdi90ZW1wL2ltYWdlNDE5OC5wbmc > .> > > > > > Fake link. Why? > > > > You don't think all the Slackware users won't be excited about some M$ > > stuff??? ;-) > > Almost makes me want to use windows again ... how much did they pay you > Petar? > > _______________________________________________ > 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 Aug 4 18:50:56 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 5 Aug 2015 01:50:56 +0700 Subject: [Slackbuilds-users] mumble/murmur .info d/l update; nvidia-kernel.Slackbuild typo In-Reply-To: <55BFEBE9.3080304@gmail.com> References: <55BFEBE9.3080304@gmail.com> Message-ID: <55C10990.8000404@slackbuilds.org> > Admins: > > Diffs attached: > > 1. mumble_location_update.diff > Correct links and md5 for git release instead of sourceforge > > 2. nvidia-driver_typo_fix.diff > add missing ">" that got lost in upload Applied in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From slacker at slaphappygeeks.com Tue Aug 4 19:59:06 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Tue, 04 Aug 2015 13:59:06 -0600 Subject: [Slackbuilds-users] categories/tags In-Reply-To: References: Message-ID: <55C1198A.6030304@slaphappygeeks.com> I personally would like to see such a browse by category option on SBo. Someone recently posted a similar link to the FreeBSD equivalent which was an excellent format. If a visitor really doesn't know what they are looking for this would provide the most useful navigational organization in my opinion. I find tag groupings can seem somewhat arbitrary, whereas with categories you can know "where you are" in a hierarchy, even if you don't know the whole landscape. This allows you to build a mental map and learn to navigate that landscape whereas tags can seem more transitory. So +1 for navigable categories with list format and short descriptions. Robert On 08/04/2015 09:45 AM, Petar Petrov wrote: > Hi. > > I was reading the categories/tags discussion. > > I think people would mostly browse SBo by Category, if they just want to > get an idea of what's in the repo or casually looking for something that > may be useful. > > The problem is that the programs' names are often not related to what the > software actually does. Therefore, a short description next to the name may > make things clearer and give the reader a quick explanation of what the > program is for. Something like this: > > http://www.student.oulu.fi/~ppetrov/temp/image4198.png > > > The "Description" column lists the short description in brackets from the > slack-desc file of each entry > > just a thought... > > bye > > Petar > > PS: I changed my email address. > > > > _______________________________________________ > 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 Tue Aug 4 20:35:17 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 4 Aug 2015 15:35:17 -0500 Subject: [Slackbuilds-users] categories/tags In-Reply-To: <55C1198A.6030304@slaphappygeeks.com> References: <55C1198A.6030304@slaphappygeeks.com> Message-ID: <20150804153517.06805408@shaggy.doo> On Tue, 04 Aug 2015 13:59:06 -0600 Slacker wrote: > I personally would like to see such a browse by category option on SBo. You mean this? https://slackbuilds.org/repository/14.1/ > On 08/04/2015 09:45 AM, Petar Petrov wrote: > > I think people would mostly browse SBo by Category, if they just want to > > get an idea of what's in the repo or casually looking for something that > > may be useful. All of the latest theory-crafting on how people search is, in my opinion, a bit pointless. In just over 9 years of the site being live with the current category/tag system, I can say we've seen exactly zero reports of people not being able to find what they were looking for. While I won't stop other admins from adding categories, I will at least vocally object to reorganization. I certainly won't be involved. It's time spent solving a problem that doesn't really exist. I will look into adding short descriptions (infact, code may already be there as I tried it many years ago) to repo browsing, but if they are not in the db (they weren't at the time) then it's unlikely to happen. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Tue Aug 4 20:41:44 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 4 Aug 2015 22:41:44 +0200 Subject: [Slackbuilds-users] categories/tags In-Reply-To: References: <55C0EF3A.7030600@slint.fr> <20150804170704.GA30464@jdiamond-nb2> Message-ID: <55C12388.1020103@microlinux.fr> Le 04/08/2015 19:56, Petar Petrov a ?crit : > That's my University's mail, I don't know why the link was copied like > that... Here's what I had in mind: > > http://www.student.oulu.fi/~ppetrov/temp/image4198.png > I think this is an excellent idea. FOSS has quite some strengths, but naming applications in an intuitive way is definitely not one of them. The world of proprietary software has Word, Toast, Winamp, iTunes. Now what does the Linux world have? K3B? Heimdal? Thunar? Exaile? Xsane? Orage? So +1 here. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From slackalaxy at gmail.com Tue Aug 4 21:08:35 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Wed, 5 Aug 2015 00:08:35 +0300 Subject: [Slackbuilds-users] categories/tags In-Reply-To: <20150804153517.06805408@shaggy.doo> References: <55C1198A.6030304@slaphappygeeks.com> <20150804153517.06805408@shaggy.doo> Message-ID: All of the latest theory-crafting on how people search is, in my opinion, > a bit pointless. In just over 9 years of the site being live with the > current category/tag system, I can say we've seen exactly zero reports of > people not being able to find what they were looking for. > you are right, I don't know about other users. I should've said that this is how I search the SBo repo sometimes. > While I won't stop other admins from adding categories, I will at least > vocally object to reorganization. I certainly won't be involved. It's time > spent solving a problem that doesn't really exist. > > I think the categories themselves are fine as they are. > I will look into adding short descriptions (infact, code may already be > there as I tried it many years ago) to repo browsing, but if they are not > in > the db (they weren't at the time) then it's unlikely to happen. > > Cool! -petar -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Tue Aug 4 21:10:42 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Tue, 4 Aug 2015 14:10:42 -0700 Subject: [Slackbuilds-users] categories/tags In-Reply-To: <55C12388.1020103@microlinux.fr> References: <55C0EF3A.7030600@slint.fr> <20150804170704.GA30464@jdiamond-nb2> <55C12388.1020103@microlinux.fr> Message-ID: i agree as well. i often use the browse feature to discover new apps but i have to click on each to find the description, then go back.. over and over. to address the search "problem" i'd recommend something along the lines of: https://www.google.com/?gws_rd=ssl#q=site:slackbuilds.org+document+viewer On Tue, Aug 4, 2015 at 1:41 PM, Nicolas Kovacs wrote: > Le 04/08/2015 19:56, Petar Petrov a ?crit : >> That's my University's mail, I don't know why the link was copied like >> that... Here's what I had in mind: >> >> http://www.student.oulu.fi/~ppetrov/temp/image4198.png >> > > I think this is an excellent idea. FOSS has quite some strengths, but > naming applications in an intuitive way is definitely not one of them. > The world of proprietary software has Word, Toast, Winamp, iTunes. Now > what does the Linux world have? K3B? Heimdal? Thunar? Exaile? Xsane? Orage? > > So +1 here. > > Niki > -- > Microlinux - Solutions informatiques durables > 7, place de l'?glise - 30730 Montpezat > Web : http://www.microlinux.fr > Mail : info at microlinux.fr > T?l. : 04 66 63 10 32 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From atelszewski at gmail.com Tue Aug 4 22:45:47 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 5 Aug 2015 00:45:47 +0200 Subject: [Slackbuilds-users] categories/tags In-Reply-To: References: <55C0EF3A.7030600@slint.fr> <20150804170704.GA30464@jdiamond-nb2> <55C12388.1020103@microlinux.fr> Message-ID: <55C1409B.8040004@gmail.com> On 04/08/15 23:10, Miguel De Anda wrote: > i agree as well. i often use the browse feature to discover new apps > but i have to click on each to find the description, then go back.. I'm in as well. The first line of slack-desc (short app description) on the front page when browsing categories or in the search results could save the "click & back" action. -- Best regards, Andrzej Telszewski From x77 at shaw.ca Tue Aug 4 23:17:36 2015 From: x77 at shaw.ca (PG Ouellette) Date: Tue, 4 Aug 2015 16:17:36 -0700 Subject: [Slackbuilds-users] categories/tags In-Reply-To: <20150804153517.06805408@shaggy.doo> References: <55C1198A.6030304@slaphappygeeks.com> <20150804153517.06805408@shaggy.doo> Message-ID: <55C14810.4070506@shaw.ca> On 08/04/2015 01:35 PM, Erik Hanson wrote: > On Tue, 04 Aug 2015 13:59:06 -0600 > Slacker wrote: > >> I personally would like to see such a browse by category option on SBo. > You mean this? https://slackbuilds.org/repository/14.1/ > > > >> On 08/04/2015 09:45 AM, Petar Petrov wrote: >>> I think people would mostly browse SBo by Category, if they just want to >>> get an idea of what's in the repo or casually looking for something that >>> may be useful. > All of the latest theory-crafting on how people search is, in my opinion, > a bit pointless. In just over 9 years of the site being live with the > current category/tag system, I can say we've seen exactly zero reports of > people not being able to find what they were looking for. > > While I won't stop other admins from adding categories, I will at least > vocally object to reorganization. I certainly won't be involved. It's time > spent solving a problem that doesn't really exist. > > I will look into adding short descriptions (infact, code may already be > there as I tried it many years ago) to repo browsing, but if they are not in > the db (they weren't at the time) then it's unlikely to happen. > > Just my two cents, a "general lumping" might be nice, like the GIS stuff. But not much more then what there is now. I tend to use google to find software for a specific purpose, like foxtrotgps, then I download the slackbuilds to find out how you pros do it. ;) From erik at slackbuilds.org Wed Aug 5 07:18:30 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 5 Aug 2015 02:18:30 -0500 Subject: [Slackbuilds-users] categories/tags In-Reply-To: <20150804153517.06805408@shaggy.doo> References: <55C1198A.6030304@slaphappygeeks.com> <20150804153517.06805408@shaggy.doo> Message-ID: <20150805021830.7886e5a0@shaggy.doo> On Tue, 4 Aug 2015 15:35:17 -0500 Erik Hanson wrote: > I will look into adding short descriptions (infact, code may already be > there as I tried it many years ago) to repo browsing, but if they are not in > the db (they weren't at the time) then it's unlikely to happen. Short descriptions are not in the db, and I have no real mysql skills, so this will only be doable if another admin has the time. Before anyone jumps in to offer a one-liner or some such, this requires more than just adding the current short descriptions to the db. The submission form and back-end approval process tools that we use during updates would also need to be hammered on. I'll consider bringing someone in to help with it, since it's a feature I've wanted for some time. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From artourter at gmail.com Wed Aug 5 10:43:19 2015 From: artourter at gmail.com (Greg' Ar Tourter) Date: Wed, 5 Aug 2015 11:43:19 +0100 Subject: [Slackbuilds-users] nvidia-driver-{info,SlackBuild} fixes Message-ID: Hi, The latest nvidia-driver package has a few errors in it. The info file has a trailing space after a new line \ in a couple of place making the file unparsable by software such as sbopkg. Additionally, if one use the compat32 option, a couple of 32bit files get written to the 64bit path overwriting their 64bit equivalent. Their is still something wrong with the package that makes it not work properly on a multilib -current platform for some reason but since neither multilib nor current are supported that will remain up to me to figure out. Cheers Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- --- nvidia-driver.SlackBuild 2015-08-01 01:57:43.000000000 +0100 +++ nvidia-driver.SlackBuild.sbopkg 2015-08-03 13:12:07.216034642 +0100 @@ -139,8 +139,8 @@ install -m 755 32/libGL.so.$VERSION $PKG/usr/lib/libGL.so.$VERSION-nvidia install -m 755 32/libGL.la $PKG/usr/lib/libGL.la-nvidia install -m 755 32/libEGL.so.$VERSION $PKG/usr/lib/libEGL.so.$VERSION-nvidia - install -m 755 32/libGLESv1_CM.so.$VERSION $PKG/usr/lib$LIBDIRSUFFIX/libGLESv1_CM.so.$VERSION - install -m 755 32/libGLESv2.so.$VERSION $PKG/usr/lib$LIBDIRSUFFIX/libGLESv2.so.$VERSION + install -m 755 32/libGLESv1_CM.so.$VERSION $PKG/usr/lib/libGLESv1_CM.so.$VERSION + install -m 755 32/libGLESv2.so.$VERSION $PKG/usr/lib/libGLESv2.so.$VERSION install -m 755 32/libnvcuvid.so.$VERSION $PKG/usr/lib/ install -m 755 32/libnvidia-compiler.so.$VERSION $PKG/usr/lib/ install -m 755 32/libnvidia-eglcore.so.$VERSION $PKG/usr/lib/ -------------- next part -------------- --- nvidia-driver.info 2015-08-01 01:57:43.000000000 +0100 +++ nvidia-driver.info.sbopkg 2015-08-03 12:37:41.143263663 +0100 @@ -11,7 +11,7 @@ c672951b0faa31089f4940d28ccd5463 \ 0e263655eaf8cf9a68697bda61e6050f \ 7975a29438550c109479b2f2bed51401 \ - e0cd59a13b5651ec2396727e7e2e54a5 \ + e0cd59a13b5651ec2396727e7e2e54a5 \ 1a6b4de9c3a91ef3680fa4f0bc80951b" DOWNLOAD_x86_64="ftp://download.nvidia.com/XFree86/Linux-x86_64/352.30/NVIDIA-Linux-x86_64-352.30.run \ ftp://download.nvidia.com/XFree86/nvidia-installer/nvidia-installer-352.30.tar.bz2 \ @@ -23,7 +23,7 @@ c672951b0faa31089f4940d28ccd5463 \ 0e263655eaf8cf9a68697bda61e6050f \ 7975a29438550c109479b2f2bed51401 \ - e0cd59a13b5651ec2396727e7e2e54a5 \ + e0cd59a13b5651ec2396727e7e2e54a5 \ 1a6b4de9c3a91ef3680fa4f0bc80951b" REQUIRES="libvdpau nvidia-kernel" MAINTAINER="Edward W. Koenig" From willysr at slackbuilds.org Wed Aug 5 11:43:46 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 5 Aug 2015 18:43:46 +0700 Subject: [Slackbuilds-users] nvidia-driver-{info,SlackBuild} fixes In-Reply-To: References: Message-ID: <55C1F6F2.7000504@slackbuilds.org> > The latest nvidia-driver package has a few errors in it. > > The info file has a trailing space after a new line \ in a couple of place > making the file unparsable by software such as sbopkg. > > Additionally, if one use the compat32 option, a couple of 32bit files get > written to the 64bit path overwriting their 64bit equivalent. Fixed on my branch Thanks cc to maintainer -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mfilpot at gmail.com Wed Aug 5 14:06:58 2015 From: mfilpot at gmail.com (Matthew Fillpot) Date: Wed, 05 Aug 2015 14:06:58 +0000 Subject: [Slackbuilds-users] categories/tags In-Reply-To: <20150805021830.7886e5a0@shaggy.doo> References: <55C1198A.6030304@slaphappygeeks.com> <20150804153517.06805408@shaggy.doo> <20150805021830.7886e5a0@shaggy.doo> Message-ID: On Wed, Aug 5, 2015, 1:18 AM Erik Hanson wrote: > On Tue, 4 Aug 2015 15:35:17 -0500 > Erik Hanson wrote: > > > I will look into adding short descriptions (infact, code may already be > > there as I tried it many years ago) to repo browsing, but if they are > not in > > the db (they weren't at the time) then it's unlikely to happen. > > Short descriptions are not in the db, and I have no real mysql skills, so > this will only be doable if another admin has the time. > > Before anyone jumps in to offer a one-liner or some such, this requires > more than just adding the current short descriptions to the db. The > submission form and back-end approval process tools that we use during > updates would also need to be hammered on. > > I'll consider bringing someone in to help with it, since it's a feature > I've wanted for some time. > > > -- > Erik Hanson > _______________________________________________ > 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/ > > I am also in agreement that this feature would help users like myself, it can also reduce server load from the current description searches. I have the database skills but am not an admin or know the other scripting requirements to implement the changes. My services are offered where they can benefit the group. Thank you, Matthew Fillpot -------------- next part -------------- An HTML attachment was scrubbed... URL: From petar.petrov at student.oulu.fi Mon Aug 3 09:23:56 2015 From: petar.petrov at student.oulu.fi (Petar Petrov) Date: Mon, 3 Aug 2015 09:23:56 +0000 Subject: [Slackbuilds-users] tags and categories In-Reply-To: <55BEFD8E.3070303@gmail.com> References: , <55BEFD8E.3070303@gmail.com> Message-ID: Hi. I was reading the categories/tags discussion. I think people would mostly browse SBo by Category, if they just want to get an idea of what's in the repo or casually looking for something that may be useful. The problem is that the programs' names are often not related to what the software actually does. Therefore, a short description next to the name may make things clearer and give the reader a quick explanation of what the program is for. Something like this: http://www.student.oulu.fi/~ppetrov/temp/image4198.png The "Description" column lists the short description in brackets from the slack-desc file of each entry just a thought... bye Petar From kingbeowulf at gmail.com Wed Aug 5 21:41:21 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 5 Aug 2015 14:41:21 -0700 Subject: [Slackbuilds-users] nvidia-driver-{info,SlackBuild} fixes In-Reply-To: <55C1F6F2.7000504@slackbuilds.org> References: <55C1F6F2.7000504@slackbuilds.org> Message-ID: <55C28301.30905@gmail.com> On 08/05/2015 04:43 AM, Willy Sudiarto Raharjo wrote: >> The latest nvidia-driver package has a few errors in it. >> >> The info file has a trailing space after a new line \ in a couple of place >> making the file unparsable by software such as sbopkg. >> >> Additionally, if one use the compat32 option, a couple of 32bit files get >> written to the 64bit path overwriting their 64bit equivalent. > > Fixed on my branch > > Thanks > > cc to maintainer > Thanks Willy and Greg. I'm getting sloppy with cut&paste in my old age. Furtunately, libGLES is not used for anything yet... -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Wed Aug 5 21:46:05 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 5 Aug 2015 14:46:05 -0700 Subject: [Slackbuilds-users] nvidia-driver-{info,SlackBuild} fixes In-Reply-To: References: Message-ID: <55C2841D.9080205@gmail.com> On 08/05/2015 03:43 AM, Greg' Ar Tourter wrote: > Their is still something wrong with the package that makes it not work > properly on a multilib -current platform for some reason but since > neither multilib nor current are supported that will remain up to me to > figure out. > Let me know what you find out. I wiped my -current multilib recently and just have the one GTX660 at this time in the main 14.1 box. I'll try to free up some HD space for another boot partition. After all, -current should be done "real soon now." -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From larryhaja at gmail.com Wed Aug 5 22:25:40 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Wed, 5 Aug 2015 15:25:40 -0700 Subject: [Slackbuilds-users] categories/tags In-Reply-To: References: <55C1198A.6030304@slaphappygeeks.com> <20150804153517.06805408@shaggy.doo> <20150805021830.7886e5a0@shaggy.doo> Message-ID: > > >> Short descriptions are not in the db, and I have no real mysql skills, so >> this will only be doable if another admin has the time. >> >> Before anyone jumps in to offer a one-liner or some such, this requires >> more than just adding the current short descriptions to the db. The >> submission form and back-end approval process tools that we use during >> updates would also need to be hammered on. >> >> I'll consider bringing someone in to help with it, since it's a feature >> I've wanted for some time. >> > I'm a mysql DBA if you need some db help. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.ka.rinne at gmail.com Thu Aug 6 18:32:51 2015 From: markus.ka.rinne at gmail.com (Markus Rinne) Date: Thu, 6 Aug 2015 21:32:51 +0300 Subject: [Slackbuilds-users] [PATCH] development/lcov: Fix typo. Message-ID: <20150806183251.GA29790@tursas> --- development/lcov/README | 2 +- development/lcov/slack-desc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/development/lcov/README b/development/lcov/README index b7dc99d..6c01ad2 100644 --- a/development/lcov/README +++ b/development/lcov/README @@ -2,4 +2,4 @@ LCOV is a graphical front-end for GCC's coverage testing tool gcov. It collects gcov data for multiple source files and creates HTML pages containing the source code annotated with coverage information. It also adds overview pages for easy navigation within the file structure. LCOV supports statement, -function and branch coverage meaurement. +function and branch coverage measurement. diff --git a/development/lcov/slack-desc b/development/lcov/slack-desc index 8f7bd66..350c265 100644 --- a/development/lcov/slack-desc +++ b/development/lcov/slack-desc @@ -13,7 +13,7 @@ lcov: It collects gcov data for multiple source files and creates HTML pages lcov: containing the source code annotated with coverage information. It lcov: also adds overview pages for easy navigation within the file lcov: structure. LCOV supports statement, function and branch coverage -lcov: meaurement. +lcov: measurement. lcov: lcov: Homepage: http://ltp.sourceforge.net/coverage/lcov.php lcov: -- 1.8.4 From rsamurti at gmail.com Fri Aug 7 02:55:35 2015 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Fri, 7 Aug 2015 08:25:35 +0530 Subject: [Slackbuilds-users] Can a link be provided to all packages maintained by a person? Message-ID: Hello, If this is done, it would help in easily locating the packages maintained by a person for upgrading the packages. Anand -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Fri Aug 7 04:30:21 2015 From: didier at slint.fr (Didier Spaier) Date: Fri, 7 Aug 2015 06:30:21 +0200 Subject: [Slackbuilds-users] Can a link be provided to all packages maintained by a person? In-Reply-To: References: Message-ID: <55C4345D.4080909@slint.fr> Hello On 07/08/2015 04:55, Ananda Murthy R S wrote: > Hello, > > If this is done, it would help in easily locating the packages > maintained by a person for upgrading the packages. Isn't that enough? http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&q=Ananda+Murthy Didier From ryan.q at linux.com Fri Aug 7 04:35:22 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 6 Aug 2015 21:35:22 -0700 Subject: [Slackbuilds-users] Can a link be provided to all packages maintained by a person? In-Reply-To: <55C4345D.4080909@slint.fr> References: <55C4345D.4080909@slint.fr> Message-ID: On Aug 6, 2015 9:30 PM, "Didier Spaier" wrote: > > Hello > > > On 07/08/2015 04:55, Ananda Murthy R S wrote: >> >> Hello, >> >> If this is done, it would help in easily locating the packages >> maintained by a person for upgrading the packages. > > > Isn't that enough? > > http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&q=Ananda+Murthy > > Didier You could also search the repo on github: https://github.com/willysr/slackbuilds/search?utf8=%E2%9C%93&q=MAINTAINER+ananda+murthy -------------- next part -------------- An HTML attachment was scrubbed... URL: From mralk3 at exitstatusone.com Fri Aug 7 10:24:09 2015 From: mralk3 at exitstatusone.com (MrAlk3) Date: Fri, 07 Aug 2015 04:24:09 -0600 Subject: [Slackbuilds-users] Can a link be provided to all packages maintained by a person? In-Reply-To: References: Message-ID: <1967897.V3sc8MqThV@mothership> On Friday, August 07, 2015 08:25:35 AM Ananda Murthy R S wrote: > Hello, > > If this is done, it would help in easily locating the packages maintained > by a person for upgrading the packages. > > Anand I have a very short python script that searches the SBo repository by local repository and then by maintainer name. I am not a great programmer and this is something I just hacked together a few weeks ago. Usage is in the comments below the gist. Please feel free to make suggestions in the comments for improvements, as I haven't tested it much. I wrote this script as a file indexer for .info files. https://gist.github.com/BrentonEarl/ea07553b404ed8a4ef81 Brenton Earl From matteo.bernardini at gmail.com Fri Aug 7 10:33:41 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 7 Aug 2015 12:33:41 +0200 Subject: [Slackbuilds-users] Can a link be provided to all packages maintained by a person? In-Reply-To: References: Message-ID: 2015-08-07 4:55 GMT+02:00 Ananda Murthy R S : > Hello, > > If this is done, it would help in easily locating the packages maintained by > a person for upgrading the packages. grep "Ananda Murthy" */*/*.info | cut -d/ -f1,2 Matteo From gwenhael.le.moine at gmail.com Fri Aug 7 10:38:36 2015 From: gwenhael.le.moine at gmail.com (Gwenhael Le Moine) Date: Fri, 7 Aug 2015 12:38:36 +0200 Subject: [Slackbuilds-users] Can a link be provided to all packages maintained by a person? In-Reply-To: References: Message-ID: 2015-08-07 12:33 GMT+02:00 Matteo Bernardini : > grep "Ananda Murthy" */*/*.info | cut -d/ -f1,2 > grep -l "Ananda Murthy" $(find /var/lib/sbopkg/SBo -name \*.info) | xargs dirname -------------- next part -------------- An HTML attachment was scrubbed... URL: From lemelle at cbpf.br Sat Aug 8 21:33:14 2015 From: lemelle at cbpf.br (lemelle at cbpf.br) Date: Sat, 08 Aug 2015 18:33:14 -0300 Subject: [Slackbuilds-users] Libopenjpeg not find Message-ID: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> please, i read the README and INSTALL. I try install OBS for slackmedia that was send me from here. but is necess?ry install ffmpeg from TRUE root... i follow all structions, them many dependencies was appearing / need install.... no problem, i search de dependency and install.... but when became in libopenjpeg not run the script of ffmpeg I run all cmake make make instal make doc in instruction of openjpeg, but dont wok here. OBS i installing ffmpeg-huge from slackmedia... i try download ffmpeg from site, but unfortunity dont work too. Sorry if i m not a genius, but i like to learn if someone explain Thanks Diego from Brazil Rio From edps.mundognu at gmail.com Sat Aug 8 21:51:37 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Sat, 08 Aug 2015 18:51:37 -0300 Subject: [Slackbuilds-users] Can a link be provided to all Message-ID: try to comprehensive list: grep -l "AUTHOR NAME" $(find /var/lib/sbopkg/SBo -name \*.info) | xargs -l1 here is a 'monster list': grep -l "Dimitris" $(find /var/lib/sbopkg/SBo -name \*.info) | xargs -l1 From didier at slint.fr Sat Aug 8 21:51:47 2015 From: didier at slint.fr (Didier Spaier) Date: Sat, 8 Aug 2015 23:51:47 +0200 Subject: [Slackbuilds-users] Libopenjpeg not find In-Reply-To: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> References: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> Message-ID: <55C679F3.4040101@slint.fr> Hi Diego, I think that there is a misunderstanding on how to use openjpeg.Slackbuilds as you wrote: > I run all cmake make make instal make doc in instruction of openjpeg, > but dont wok here. You don't have to manually run all commands in the script, but just execute the script itself as in the example in the HOWTO: http://slackbuilds.org/howto/ In the case of openjpeg, just do this: _ Download the SlackBuild: http://slackbuilds.org/slackbuilds/14.1/libraries/openjpeg.tar.gz _ unpack the archive you just downloaded: tar xf openjpeg.tar.gz _ now you should have a directory openjpeg _ download the source; http://downloads.sourceforge.net/openjpeg.mirror/openjpeg-1.5.2.tar.gz _ move openjpeg-1.5.2.tar.gz to openjpeg (alongside openjpeg.SlackBuild) _ become root: su - _ cd to the directory openjpeg _ make sure openjeg.SlackBuild be executable: chmod 755 openjpeg.SlackBuild _ execute the script to make the package. To do that, type: ./openjpeg.SlackBuild _ This will take a few minutes. After it finishes type: installpkg /tmp/openjpeg*tgz Didier From miguel at thedeanda.com Sat Aug 8 22:02:54 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Sat, 8 Aug 2015 15:02:54 -0700 Subject: [Slackbuilds-users] Libopenjpeg not find In-Reply-To: <55C679F3.4040101@slint.fr> References: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> <55C679F3.4040101@slint.fr> Message-ID: the "su -" part didier mentioned gets you to "true root" whereas just "su" gets you to... almost(?) true root. some programs don't compile properly without the -. On Sat, Aug 8, 2015 at 2:51 PM, Didier Spaier wrote: > Hi Diego, > > I think that there is a misunderstanding on how to use openjpeg.Slackbuilds > as you wrote: > >> I run all cmake make make instal make doc in instruction of openjpeg, >> but dont wok here. > > > You don't have to manually run all commands in the script, but just > execute the script itself as in the example in the HOWTO: > http://slackbuilds.org/howto/ > > In the case of openjpeg, just do this: > _ Download the SlackBuild: > http://slackbuilds.org/slackbuilds/14.1/libraries/openjpeg.tar.gz > _ unpack the archive you just downloaded: > tar xf openjpeg.tar.gz > _ now you should have a directory openjpeg > _ download the source; > http://downloads.sourceforge.net/openjpeg.mirror/openjpeg-1.5.2.tar.gz > _ move openjpeg-1.5.2.tar.gz to openjpeg (alongside openjpeg.SlackBuild) > _ become root: > su - > _ cd to the directory openjpeg > _ make sure openjeg.SlackBuild be executable: > chmod 755 openjpeg.SlackBuild > _ execute the script to make the package. To do that, type: > ./openjpeg.SlackBuild > _ This will take a few minutes. After it finishes type: > installpkg /tmp/openjpeg*tgz > > Didier > > _______________________________________________ > 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 slack.dhabyx at gmail.com Sun Aug 9 00:25:44 2015 From: slack.dhabyx at gmail.com (Dhaby Xiloj) Date: Sat, 8 Aug 2015 18:25:44 -0600 Subject: [Slackbuilds-users] Libopenjpeg not find In-Reply-To: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> References: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> Message-ID: <55C69E08.4090606@gmail.com> On 08/08/15 15:33, lemelle at cbpf.br wrote: > > please, i read the README and INSTALL. I try install OBS for > slackmedia that was send me from here. but is necess?ry install ffmpeg > from TRUE root... i follow all structions, them many dependencies was > appearing / need install.... > > no problem, i search de dependency and install.... but when became in > libopenjpeg not run the script of ffmpeg > > > I run all cmake make make instal make doc in instruction of openjpeg, > but dont wok here. > > > OBS i installing ffmpeg-huge from slackmedia... i try download ffmpeg > from site, but unfortunity dont work too. > > > Sorry if i m not a genius, but i like to learn if someone explain > > > Thanks > > > Diego from Brazil Rio > _______________________________________________ > 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/ > Hi Diego If slackmedia is based on slackware current, ffmpeg have problems using the new version of libopenjpeg, ffmpeg only be compiled with version 1.x of libopenjpeg but slackware uses version 2.1 To solve this problem you can install both librariesat the same time, but you must modify the SlackBuild of libopenjpeg and rename to libopenjpeg1. You can use the SlackBuild of libopenjpeg that I have on github[1] and then compile ffmpeg. [1] https://github.com/dhabyx/slackbuilds/tree/master/openjpeg1 -- Dhaby Xiloj From willysr at slackbuilds.org Sun Aug 9 01:31:56 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 9 Aug 2015 08:31:56 +0700 Subject: [Slackbuilds-users] [PATCH] development/lcov: Fix typo. In-Reply-To: <20150806183251.GA29790@tursas> References: <20150806183251.GA29790@tursas> Message-ID: <55C6AD8C.9080701@slackbuilds.org> > --- > development/lcov/README | 2 +- > development/lcov/slack-desc | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/development/lcov/README b/development/lcov/README > index b7dc99d..6c01ad2 100644 > --- a/development/lcov/README > +++ b/development/lcov/README > @@ -2,4 +2,4 @@ LCOV is a graphical front-end for GCC's coverage testing tool gcov. It > collects gcov data for multiple source files and creates HTML pages containing > the source code annotated with coverage information. It also adds overview > pages for easy navigation within the file structure. LCOV supports statement, > -function and branch coverage meaurement. > +function and branch coverage measurement. > diff --git a/development/lcov/slack-desc b/development/lcov/slack-desc > index 8f7bd66..350c265 100644 > --- a/development/lcov/slack-desc > +++ b/development/lcov/slack-desc > @@ -13,7 +13,7 @@ lcov: It collects gcov data for multiple source files and creates HTML pages > lcov: containing the source code annotated with coverage information. It > lcov: also adds overview pages for easy navigation within the file > lcov: structure. LCOV supports statement, function and branch coverage > -lcov: meaurement. > +lcov: measurement. > lcov: > lcov: Homepage: http://ltp.sourceforge.net/coverage/lcov.php > lcov: > Applied on my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From jvogel4 at stny.rr.com Sun Aug 9 03:15:00 2015 From: jvogel4 at stny.rr.com (John Vogel) Date: Sat, 8 Aug 2015 23:15:00 -0400 Subject: [Slackbuilds-users] dash: update maintainer Message-ID: <20150808231500.3f156a88@stygian.lan> I forgot to edit the .info file before I uploaded the dash update: -- diff -ur a/dash.info b/dash.info --- a/dash.info 2015-08-08 23:08:26.866361046 -0400 +++ b/dash.info 2015-08-08 23:09:03.459695342 -0400 @@ -6,5 +6,5 @@ DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -MAINTAINER="Vincent Batts" -EMAIL="vbatts at hashbangbash.com" +MAINTAINER="John Vogel" +EMAIL="jvogel4 at stny.rr.com" -- Sorry for the add work. John From didier at slint.fr Sun Aug 9 04:02:43 2015 From: didier at slint.fr (Didier Spaier) Date: Sun, 9 Aug 2015 06:02:43 +0200 Subject: [Slackbuilds-users] Libopenjpeg not find In-Reply-To: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> References: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> Message-ID: <55C6D0E3.4010701@slint.fr> Hi Diego, On 08/08/2015 23:33, lemelle at cbpf.br wrote: > > please, i read the README and INSTALL. I try install OBS for > slackmedia that was send me from here. but is necess?ry install ffmpeg > from TRUE root... i follow all structions, them many dependencies was > appearing / need install.... > > no problem, i search de dependency and install.... but when became in > libopenjpeg not run the script of ffmpeg > > > I run all cmake make make instal make doc in instruction of openjpeg, > but dont wok here. > > > OBS i installing ffmpeg-huge from slackmedia... i try download ffmpeg > from site, but unfortunity dont work too. > > > Sorry if i m not a genius, but i like to learn if someone explain In addition to my previous answer: I now realize that you really meant not "slackmedia" but "slackermedia": https://github.com/jp9000/obs-studio/wiki/Install-Instructions and that you got some of the needed stuff like ffmpeg-huge from here: http://slackermedia.info/slackbuilds/ Your question being about Slackermedia-specific technology, rather than about the SlackBuilds maintained @ SlackBuilds.org I suggest that you contact klaatu directly as indicated here: http://slackermedia.info/support/ and/or use the support channels provided by each provider or packager of application or dependency. Best regards, Didier From klaatu at straightedgelinux.com Sun Aug 9 05:10:52 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Sun, 9 Aug 2015 17:10:52 +1200 Subject: [Slackbuilds-users] Current or Release? In-Reply-To: <55C69E08.4090606@gmail.com> References: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> <55C69E08.4090606@gmail.com> Message-ID: <55C6E0DC.7050000@straightedgelinux.com> This has come up in emails a few times now, so I figured I'd ask the list about it: Does SlackBuilds.org guarantee compatibility with Slackware-Current or with the latest release? I had always understood it was the latest release (especially since the search function on the website filters by release number). But several times in emails, people have mentioned being based on -current. I test build and test on the latest release. Is this what other maintainers are doing or are people assuming -current? -klaatu From ryan.q at linux.com Sun Aug 9 05:33:03 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 8 Aug 2015 22:33:03 -0700 Subject: [Slackbuilds-users] Current or Release? In-Reply-To: <55C6E0DC.7050000@straightedgelinux.com> References: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> <55C69E08.4090606@gmail.com> <55C6E0DC.7050000@straightedgelinux.com> Message-ID: On Aug 8, 2015 10:10 PM, "Klaatu" wrote: > > This has come up in emails a few times now, so I figured I'd ask the > list about it: > > Does SlackBuilds.org guarantee compatibility with Slackware-Current or > with the latest release? > > I had always understood it was the latest release (especially since the > search function on the website filters by release number). But several > times in emails, people have mentioned being based on -current. > > I test build and test on the latest release. Is this what other > maintainers are doing or are people assuming -current? > > -klaatu Current is not supported. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Aug 9 05:34:06 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 9 Aug 2015 12:34:06 +0700 Subject: [Slackbuilds-users] Current or Release? In-Reply-To: <55C6E0DC.7050000@straightedgelinux.com> References: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> <55C69E08.4090606@gmail.com> <55C6E0DC.7050000@straightedgelinux.com> Message-ID: > This has come up in emails a few times now, so I figured I'd ask the > list about it: > > Does SlackBuilds.org guarantee compatibility with Slackware-Current or > with the latest release? > > I had always understood it was the latest release (especially since the > search function on the website filters by release number). But several > times in emails, people have mentioned being based on -current. > > I test build and test on the latest release. Is this what other > maintainers are doing or are people assuming -current? http://slackbuilds.org/faq/#version -- Willy Sudiarto Raharjo From yalhcru at gmail.com Sun Aug 9 06:08:50 2015 From: yalhcru at gmail.com (B Watson) Date: Sun, 9 Aug 2015 02:08:50 -0400 Subject: [Slackbuilds-users] Current or Release? In-Reply-To: <55C6E0DC.7050000@straightedgelinux.com> References: <20150808183314.Horde.9DohesCPne9VxnWaSlskccA@p0m1.cat.cbpf.br> <55C69E08.4090606@gmail.com> <55C6E0DC.7050000@straightedgelinux.com> Message-ID: On 8/9/15, Klaatu wrote: > times in emails, people have mentioned being based on -current. > > I test build and test on the latest release. Is this what other > maintainers are doing or are people assuming -current? Only stable is supported (as someone already said)... but, sooner or later, -current will become the next release, so it's nice to know in advance if a build is broken on -current... and we don't all have time to continually upgrade -current and test every build, so reporting a build that breaks for you on -current can still help us. That's my opinion only, I should mention. I'm not speaking for anyone else. From ryan.q at linux.com Sun Aug 9 15:35:25 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 9 Aug 2015 08:35:25 -0700 Subject: [Slackbuilds-users] i586 time? Message-ID: Following current, I am sure many have noticed that there are a LOT of packages changing from i486 to i586. The plot thickens even more when you take a look at Pat's note in the gcc.SlackBuild: # Some more notes, Mon Aug 3 19:49:51 UTC 2015: # # Changing to -march=i586 for 32-bit x86 as several things (Mesa being one of # them) no longer work if constrained to -march=i486. We're not going to use # -march=i686 since the only additional opcode is CMOV, which is actually less # efficient on modern CPUs running in 32-bit mode than the alternate i586 # instructions. No need to throw i586 CPUs under the bus (yet). http://slackware.osuosl.org/slackware64-current/source/d/gcc/gcc.SlackBuild It sounds like it may be time to consider switching SBo to i586 (starting with the next release). Thoughts? -Ryan From willysr at slackbuilds.org Sun Aug 9 16:27:46 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 9 Aug 2015 23:27:46 +0700 Subject: [Slackbuilds-users] Updates - 20150809.1 Message-ID: <55C77F82.4030106@slackbuilds.org> Sun Aug 9 16:13:36 UTC 2015 academic/pulseview: Added (GUI for sigrok). academic/wmcalc: Added (Calculator DockApp). accessibility/Synkron: Added (File/folder synchronization). audio/wmusic: Added (XMMS Remote Control DockApp). desktop/Window_Manager_Scripts: Added (WM Agnostic Shell Scripts). desktop/seafile-gui: Updated for version 4.3.0. desktop/sun: Updated for version 1.1.1. desktop/wmblob: Added (Fancy Moving Blobs DockApp). desktop/wmtimer: Added (Timer DockApp). desktop/wmudmount: New maintainer. desktop/wmweather+: Added (Weather Monitor DockApp). development/apache-jmeter: Updated for version 2.13. development/atom: Updated for version 1.0.5. development/brackets: Updated for version 1.4. development/chicken: Updated for version 4.10.0. development/lcov: Fix typo. development/p4: Updated for version 2015.1.1204891. development/p4v: Updated for version 2014.1.1206753. development/scons: Updated for version 2.3.6. games/atanks: Updated for version 6.3. games/chocolate_duke3D: Added (Faithful Duke Nukem 3D port). games/instead: Updated for version 2.2.4. games/mednafen: Change CXXFLAGS. games/qstat: Updated for version 2a95a5d0. games/starfighter: Updated for version 1.4. gis/mapnik: Updated for version 3.0.2. graphics/Blender: Added (3D Content Creation Suite). graphics/CairoSVG: Updated for version 1.0.16. graphics/GraphicsMagick: Updated for version 1.3.21. graphics/findimagedupes: Added (find visually similar images). graphics/openimageio: Update MD5SUM. graphics/pngcrush: Updated for version 1.7.86. libraries/CGAL: Updated for version 4.6.1. libraries/cffi: Updated for version 1.1.2. libraries/hiredis: Updated for version 0.13.1. libraries/libcpuid: Added (C library for x86 CPU detection). libraries/libmicrohttpd: Updated for version 0.9.42. libraries/libuv: Updated for version 1.7.0. libraries/live555: Updated for version 2015.08.06. libraries/wxSQLite3: Added (wxWidgets wrapper for SQLite3). misc/bdf2psf: Added (convert fonts from bdf to psf format). misc/sigrok-firmware-fx2lafw: Added (Firmware for Cypress FX2). multimedia/makemkv: Updated for version 1.9.5. multimedia/minidlna: Updated for version 20150730. network/allmydata-tahoe: Updated for version 1.10.2. network/ccnet: Updated for version 4.3.1. network/clipgrab: Updated for version 3.5.1. network/dnscrypt-wrapper: Updated for version 0.2. network/greenbone-security-assistant: Updated for version 6.0.4. network/iojs: Updated for version 3.0.0. network/mumble: Update DOWNLOAD url. network/murmur: Update DOWNLOAD url. network/openvas-cli: Updated for version 1.4.2. network/openvas-libraries: Updated for version 8.0.4. network/openvas-manager: Updated for version 5.0.4. network/openvas-scanner: Updated for version 5.0.4. network/pentadactyl: Updated for version 20150808. network/pidgin-skypeweb: Updated for version 0c354d57. network/pure-ftpd: Updated for version 1.0.42. network/purple-facebook: Updated for version 0c354d57. network/seafile-client: Updated for version 4.3.1. network/seafile-server: Updated for version 4.3.1. network/seahub: Updated for version 4.3.1. network/vivaldi: Updated for version 1.0.233.3_1. network/wmnd: Added (WindowMaker Network Devices DockApp). network/youtube-dl: Updated for version 2015.08.06.1. office/libreoffice-helppack: Updated for version 5.0.0. office/libreoffice-langpack: Updated for version 5.0.0. office/libreoffice: Updated for version 5.0.0. office/lyx: Updated for version 2.1.4. office/remind: Updated for version 03.01.15. perl/perl-Astro-SunTime: new maintainer. perl/perl-Convert-UUlib: Update DOWNLOAD url. perl/perl-DateTime: Fix broken download location. perl/perl-Device-SerialPort: new maintainer. perl/perl-Email-Date-Format: Updated for version 1.005. perl/perl-IO-HTML: Updated for version 1.001. perl/perl-Inline: Updated for version 0.80. perl/perl-MIME-Lite: New maintainer. perl/perl-MusicBrainz-DiscID: New maintainer. perl/perl-PHP-Serialization: New maintainer. perl/perl-PerlIO-Layers: Updated for version 0.011. perl/perl-Proc-Daemon: Updated for version 0.21. perl/perl-Sub-Exporter-Progressive: Update EMAIL. perl/perl-Test-Exception: Fix broken download location. perl/perl-Test-Warnings: Fix broken download location. perl/perl-x11-protocol: new maintainer. python/astroid: Updated for version 1.3.8. python/cairocffi: Updated for version 0.7.2. python/path.py: Updated for version 7.5. python/psutil: Updated for version 3.1.1. python/pyasn1-modules: Updated for version 0.0.6. python/pyasn1: Updated for version 0.1.8. python/rsa: Updated for version 3.2. python/selenium: Updated for version 2.47.1. python/stevedore: Updated for version 1.7.0. python/websocket-client: Added (WebSocket client for python). system/bochs: Updated for version 2.6.8. system/crashplan: Updated for version 4.3.0. system/dash: Updated for version 0.5.8 + new maintainer. system/eaglemode: Added (zoomable user interface). system/etckeeper: Updated for version 1.18.2. system/nvidia-driver: Fix typo. system/profile-cleaner: Updated for version 2.35. system/secure-delete: Added new doc. system/slpkg: Updated for version 2.7.1. system/wipe: Added (Secure data destruction). system/wmgtemp: Added (Graphical GPU and SYS Temp Monitor DockApp). +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ts at websafe.pl Sun Aug 9 18:32:57 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 9 Aug 2015 20:32:57 +0200 Subject: [Slackbuilds-users] Problem with building spice - celt051.SlackBuild needs an update? Message-ID: <55C79CD9.3090507@websafe.pl> Hello, I was trying to build virt-manager with dependencies, and a problem occured with `spice` : ~~~~ make[4]: Entering directory `/tmp/SBo/spice-0.12.5/server' CC agent-msg-filter.lo CC char_device.lo CC glz_encoder.lo CC glz_encoder_dictionary.lo CC inputs_channel.lo CC jpeg_encoder.lo CC main_channel.lo CC mjpeg_encoder.lo CC red_channel.lo CC dispatcher.lo CC red_dispatcher.lo CC main_dispatcher.lo CC red_memslots.lo CC red_parse_qxl.lo CC red_worker.lo CC reds.lo CC reds_stream.lo CC reds_sw_canvas.lo CC snd_worker.lo CC spicevmc.lo CC spice_timer_queue.lo CC zlib_encoder.lo CC spice_bitmap_utils.lo CC spice_image_cache.lo CCLD libspice-server.la gcc: error: /usr/lib64/libcelt051.so: No such file or directory ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ make[4]: *** [libspice-server.la] Error 1 make[4]: Leaving directory `/tmp/SBo/spice-0.12.5/server' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/SBo/spice-0.12.5/server' make[2]: *** [all] Error 2 make[2]: Leaving directory `/tmp/SBo/spice-0.12.5/server' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/spice-0.12.5' make: *** [all] Error 2 Total build time for package spice : 41.58 Sec ~~~~ `celt051` was built and installed before, but the file expected during the spice build - `/usr/lib64/libcelt051.so` - was not available: # ls -la /usr/lib64/libcelt051.so ls: cannot access /usr/lib64/libcelt051.so: No such file or directory There was a file: # ls -la /usr/lib64/libcelt051.so.0 lrwxrwxrwx 1 root root 19 Aug 9 01:57 /usr/lib64/libcelt051.so.0 -> libcelt051.so.0.0.0 What solved this issue was: ~~~~ cd /usr/lib64 && ln -s libcelt051.so.0 libcelt051.so ~~~~ So I guess `celt051.SlackBuild` needs an update? -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3712 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sun Aug 9 18:37:29 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 9 Aug 2015 20:37:29 +0200 Subject: [Slackbuilds-users] OpenDKIM download location has changed Message-ID: <55C79DE9.8030408@websafe.pl> OpenDKIM download location is no longer valid. The valid location for 2.10.1 is but there's already v. 2.10.3 available... -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3712 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sun Aug 9 18:56:55 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 9 Aug 2015 20:56:55 +0200 Subject: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64 Message-ID: <55C7A277.4080407@websafe.pl> I've compiled KeePass with mono but there was a problem and KeePass wouldn't start: ~~~~ $ keepass SendMessage (77594663, 0x112c, 0x4, 0x4) SendMessage (77594657, 0x101f, (nil), (nil)) SendMessage (0, 0x1203, (nil), 0x7fff90c590e0) SendMessage (0, 0x1204, (nil), 0x7fff90c590e0) SendMessage (0, 0x1203, 0x1, 0x7fff90c590e0) SendMessage (0, 0x1204, 0x1, 0x7fff90c590e0) SendMessage (0, 0x1203, 0x2, 0x7fff90c590e0) SendMessage (0, 0x1204, 0x2, 0x7fff90c590e0) SendMessage (0, 0x1203, 0x3, 0x7fff90c590e0) SendMessage (0, 0x1204, 0x3, 0x7fff90c590e0) SendMessage (0, 0x1203, 0x4, 0x7fff90c590e0) SendMessage (0, 0x1204, 0x4, 0x7fff90c590e0) System.TypeInitializationException: An exception was thrown by the type initializer for Mono.Unix.Native.Syscall ---> System.DllNotFoundException: /usr/lib/libMonoPosixHelper.so ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ at (wrapper managed-to-native) Mono.Unix.Native.Syscall:get_at_fdcwd () at Mono.Unix.Native.Syscall..cctor () [0x00000] in :0 --- End of inner exception stack trace --- ~~~~ Then I found this and after correcting the wrong path `/usr/lib/libMonoPosixHelper.so` to `/usr/lib64/libMonoPosixHelper.so` in `/etc/mono/config` everything worked as expected. So maybe a small update to `mono.Slackbuild` will be required? -- Best regards, Thomas Szteliga https://github.com/websafe/ -------------- next part -------------- A non-text attachment was scrubbed... Name: config.patch Type: text/x-patch Size: 685 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3712 bytes Desc: S/MIME Cryptographic Signature URL: From jvogel4 at stny.rr.com Sun Aug 9 18:51:54 2015 From: jvogel4 at stny.rr.com (John Vogel) Date: Sun, 9 Aug 2015 14:51:54 -0400 Subject: [Slackbuilds-users] Problem with building spice - celt051.SlackBuild needs an update? In-Reply-To: <55C79CD9.3090507@websafe.pl> References: <55C79CD9.3090507@websafe.pl> Message-ID: <20150809145154.509ffa20@stygian.lan> On Sun, 9 Aug 2015 20:32:57 +0200 Thomas Szteliga wrote: > gcc: error: /usr/lib64/libcelt051.so: No such file or directory > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > make[4]: *** [libspice-server.la] Error 1 > make[4]: Leaving directory `/tmp/SBo/spice-0.12.5/server' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/tmp/SBo/spice-0.12.5/server' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/tmp/SBo/spice-0.12.5/server' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/tmp/SBo/spice-0.12.5' > make: *** [all] Error 2 > Total build time for package spice : 41.58 Sec > ~~~~ > > > > `celt051` > was built and installed before, but the file expected during the spice > build - `/usr/lib64/libcelt051.so` - was not available: > > > # ls -la /usr/lib64/libcelt051.so > ls: cannot access /usr/lib64/libcelt051.so: No such file or directory > > > There was a file: > > # ls -la /usr/lib64/libcelt051.so.0 > lrwxrwxrwx 1 root root 19 Aug 9 01:57 /usr/lib64/libcelt051.so.0 -> > libcelt051.so.0.0.0 > > > What solved this issue was: > > > ~~~~ > cd /usr/lib64 && ln -s libcelt051.so.0 libcelt051.so > ~~~~ > > > So I guess `celt051.SlackBuild` needs an update? > > > -- > Thomas Szteliga > > I have celt051 installed. I have the proper links. I didn't change anything. Perhaps the link was deleted post install. John From matteo.bernardini at gmail.com Sun Aug 9 19:01:17 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 9 Aug 2015 21:01:17 +0200 Subject: [Slackbuilds-users] Problem with building spice - celt051.SlackBuild needs an update? In-Reply-To: <20150809145154.509ffa20@stygian.lan> References: <55C79CD9.3090507@websafe.pl> <20150809145154.509ffa20@stygian.lan> Message-ID: 2015-08-09 20:51 GMT+02:00 John Vogel : > On Sun, 9 Aug 2015 20:32:57 +0200 > Thomas Szteliga wrote: > > >> gcc: error: /usr/lib64/libcelt051.so: No such file or directory >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> make[4]: *** [libspice-server.la] Error 1 >> make[4]: Leaving directory `/tmp/SBo/spice-0.12.5/server' >> make[3]: *** [all-recursive] Error 1 >> make[3]: Leaving directory `/tmp/SBo/spice-0.12.5/server' >> make[2]: *** [all] Error 2 >> make[2]: Leaving directory `/tmp/SBo/spice-0.12.5/server' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/tmp/SBo/spice-0.12.5' >> make: *** [all] Error 2 >> Total build time for package spice : 41.58 Sec >> ~~~~ >> >> >> >> `celt051` >> was built and installed before, but the file expected during the spice >> build - `/usr/lib64/libcelt051.so` - was not available: >> >> >> # ls -la /usr/lib64/libcelt051.so >> ls: cannot access /usr/lib64/libcelt051.so: No such file or directory >> >> >> There was a file: >> >> # ls -la /usr/lib64/libcelt051.so.0 >> lrwxrwxrwx 1 root root 19 Aug 9 01:57 /usr/lib64/libcelt051.so.0 -> >> libcelt051.so.0.0.0 >> >> >> What solved this issue was: >> >> >> ~~~~ >> cd /usr/lib64 && ln -s libcelt051.so.0 libcelt051.so >> ~~~~ >> >> >> So I guess `celt051.SlackBuild` needs an update? >> >> >> -- >> Thomas Szteliga >> >> > > I have celt051 installed. I have the proper links. I didn't > change anything. Perhaps the link was deleted post install. you can check the link has been created for you when making the package in /var/log/scripts/celt051-0.5.1.3-* (the script run when installing the package -the doinst.sh inside of it, actually). no need to say that also in my case it has been created correctly. Matteo From ts at websafe.pl Sun Aug 9 19:24:57 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 9 Aug 2015 21:24:57 +0200 Subject: [Slackbuilds-users] Problem with building spice - celt051.SlackBuild needs an update? In-Reply-To: <20150809145154.509ffa20@stygian.lan> References: <55C79CD9.3090507@websafe.pl> <20150809145154.509ffa20@stygian.lan> Message-ID: <55C7A909.7010400@websafe.pl> On 08/09/2015 08:51 PM, John Vogel wrote: > I have celt051 installed. I have the proper links. I didn't > change anything. Perhaps the link was deleted post install. Hmm, I'm on a fresh full installation of x86_64 14.1. I did not remove anything... I'm checking now `install/doinst.sh` in the created package: ~~~~ ( cd usr/lib64 ; rm -rf libcelt051.so ) ( cd usr/lib64 ; ln -sf libcelt051.so.0.0.0 libcelt051.so ) ( cd usr/lib64 ; rm -rf libcelt051.so.0 ) ( cd usr/lib64 ; ln -sf libcelt051.so.0.0.0 libcelt051.so.0 ) ~~~~ so it should be there... I was building with slkpg (https://github.com/dslackw/slpkg) and between celt051 and spice-012.5 the following packages were built: + pyparsing-2.0.3 + spice-protocol-0.12.7 + orc-0.4.23 + gstreamer1-1.4.5 + gst1-plugins-base-1.4.5 I'll investigate this. -- Best regards, Thomas Szteliga https://github.com/websafe/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3712 bytes Desc: S/MIME Cryptographic Signature URL: From mherda at slackword.net Sun Aug 9 20:52:45 2015 From: mherda at slackword.net (Marcin Herda) Date: Sun, 9 Aug 2015 21:52:45 +0100 Subject: [Slackbuilds-users] dwb up for grabs Message-ID: <55C7BD9D.8050702@slackword.net> Hi all, I have not been using dwb (a lightweight web browser) for a long time so would like someone else to take over its maintenance. I have written a few emails to its developer asking to provide on their website a more up-to-date tarball of a stable version but have not received any response. I can see that the project's Bitbucket repository has been actively maintained. If anyone is interested, please feel free to take this one. If not, I'll just drop it, with the next Slackware release. Cheers Marcin From Jim.Diamond at acadiau.ca Sun Aug 9 21:06:36 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sun, 9 Aug 2015 18:06:36 -0300 Subject: [Slackbuilds-users] libreoffice 5.0 crash and burn Message-ID: <20150809210636.GA29362@jdiamond-nb2> # sboupgrade libreoffice ... 2015-08-09 18:04:28 (4.88 MB/s) - 'LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz' saved [239927592/239927592] Unable to download/verify source file(s) for libreoffice: md5sum failure for /usr/local/poo/usr-sbo-141/distfiles/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz. Do you want to proceed? [n] Failures: libreoffice: md5sum failure for /usr/local/poo/usr-sbo-141/distfiles/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz. 6.23s user 2.02s system 8% cpu 1:39.01 total From ts at websafe.pl Sun Aug 9 21:55:48 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 9 Aug 2015 23:55:48 +0200 Subject: [Slackbuilds-users] libreoffice 5.0 crash and burn In-Reply-To: <20150809210636.GA29362@jdiamond-nb2> References: <20150809210636.GA29362@jdiamond-nb2> Message-ID: <55C7CC64.1020909@websafe.pl> On 08/09/2015 11:06 PM, Jim Diamond wrote: > # sboupgrade libreoffice > 2015-08-09 18:04:28 (4.88 MB/s) - 'LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz' saved [239927592/239927592] > Unable to download/verify source file(s) for libreoffice: > md5sum failure for /usr/local/poo/usr-sbo-141/distfiles/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz. > Do you want to proceed? [n] > Failures: > libreoffice: md5sum failure for /usr/local/poo/usr-sbo-141/distfiles/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz. > 6.23s user 2.02s system 8% cpu 1:39.01 total I was able to download but the checksum in the info file is wrong, should be: $ md5sum LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz 6e1c97eaa221748e328c80470d296583 LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz instead of: MD5SUM_x86_64="609182c7ebbf5d5a96ffdb5418eff3f7" -- Best regards, Thomas Szteliga https://github.com/websafe/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3712 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sun Aug 9 23:06:29 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 10 Aug 2015 06:06:29 +0700 Subject: [Slackbuilds-users] libreoffice 5.0 crash and burn In-Reply-To: <55C7CC64.1020909@websafe.pl> References: <20150809210636.GA29362@jdiamond-nb2> <55C7CC64.1020909@websafe.pl> Message-ID: <55C7DCF5.5050206@slackbuilds.org> > On 08/09/2015 11:06 PM, Jim Diamond wrote: >> # sboupgrade libreoffice >> 2015-08-09 18:04:28 (4.88 MB/s) - 'LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz' saved [239927592/239927592] >> Unable to download/verify source file(s) for libreoffice: >> md5sum failure for /usr/local/poo/usr-sbo-141/distfiles/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz. >> Do you want to proceed? [n] >> Failures: >> libreoffice: md5sum failure for /usr/local/poo/usr-sbo-141/distfiles/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz. >> 6.23s user 2.02s system 8% cpu 1:39.01 total > > I was able to download > > > but the checksum in the info file is wrong, should be: > > $ md5sum LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz > 6e1c97eaa221748e328c80470d296583 LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz > > > instead of: > > MD5SUM_x86_64="609182c7ebbf5d5a96ffdb5418eff3f7" Sorry for that I have fix it already on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Aug 9 23:13:11 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 10 Aug 2015 06:13:11 +0700 Subject: [Slackbuilds-users] OpenDKIM download location has changed In-Reply-To: <55C79DE9.8030408@websafe.pl> References: <55C79DE9.8030408@websafe.pl> Message-ID: <55C7DE87.8070109@slackbuilds.org> > OpenDKIM > download location > > is no longer valid. > > The valid location for 2.10.1 is > > > but there's already v. 2.10.3 available... > Fixed on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Mon Aug 10 03:55:53 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 9 Aug 2015 20:55:53 -0700 Subject: [Slackbuilds-users] i586 time? In-Reply-To: References: Message-ID: <55C820C9.9060806@gmail.com> On 08/09/2015 08:35 AM, Ryan P.C. McQuen wrote: ... > > It sounds like it may be time to consider switching SBo to i586 > (starting with the next release). > > Thoughts? > As much as it pains me to admit it, given the fairly antique hardware I have, it may be time to move to the 21st century. Even I gave up my AMD 486DX100 CPU ages ago, and my Athlon 800 slot A motherboard bit the big one a while back. Oldest CPU I have is (from 2000): i686 Intel(R) Pentium(R) 4 CPU 2.66GHz Followed by i686 Intel(R) Atom(TM) CPU N280 @ 1.66GHz Everything else is x86_64: x86_64 Intel(R) Celeron(R) CPU 1007U @ 1.50GHz x86_64 Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ Yep, not "new" or even "newish" but definitely ok with march=i596. I say, switch...what the heck. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Mon Aug 10 04:07:49 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 10 Aug 2015 14:07:49 +1000 Subject: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64 In-Reply-To: <55C7A277.4080407@websafe.pl> References: <55C7A277.4080407@websafe.pl> Message-ID: <55C82395.5050102@iinet.net.au> On 10/08/15 04:56, Thomas Szteliga wrote: [snip] > > Then I found this > and after correcting the wrong path `/usr/lib/libMonoPosixHelper.so` to > `/usr/lib64/libMonoPosixHelper.so` in `/etc/mono/config` everything > worked as expected. > That is not an appropriate patch; it is completely 64bit-centric, just as the config in the source code is completely 32bit-centric. I forwarded a "neutral" patch to the maintainer about two months ago - he said he would review it and submit an update. In the meantime, version 4.x.x is available which includes its own fix for the problem (actually, some of the later 3.x.x versions after the SBo version also had the fix). The latest version I tried was 4.0.2.4 and it works fine without patching. chris From ryan.q at linux.com Mon Aug 10 04:10:59 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 9 Aug 2015 21:10:59 -0700 Subject: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64 In-Reply-To: <55C82395.5050102@iinet.net.au> References: <55C7A277.4080407@websafe.pl> <55C82395.5050102@iinet.net.au> Message-ID: On 8/9/15, Christoph Willing wrote: > > > On 10/08/15 04:56, Thomas Szteliga wrote: > [snip] >> >> Then I found this >> and after correcting the wrong path `/usr/lib/libMonoPosixHelper.so` to >> `/usr/lib64/libMonoPosixHelper.so` in `/etc/mono/config` everything >> worked as expected. >> > > That is not an appropriate patch; it is completely 64bit-centric, just > as the config in the source code is completely 32bit-centric. > > I forwarded a "neutral" patch to the maintainer about two months ago - > he said he would review it and submit an update. In the meantime, > version 4.x.x is available which includes its own fix for the problem > (actually, some of the later 3.x.x versions after the SBo version also > had the fix). > > The latest version I tried was 4.0.2.4 and it works fine without patching. > > chris Christoph, Is there a neutral patch for mono2? Thanks. -- --- From chris.willing at iinet.net.au Mon Aug 10 04:30:29 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 10 Aug 2015 14:30:29 +1000 Subject: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64 In-Reply-To: References: <55C7A277.4080407@websafe.pl> <55C82395.5050102@iinet.net.au> Message-ID: <55C828E5.5000206@iinet.net.au> On 10/08/15 14:10, Ryan P.C. McQuen wrote: > On 8/9/15, Christoph Willing wrote: >> >> >> On 10/08/15 04:56, Thomas Szteliga wrote: >> [snip] >>> >>> Then I found this >>> and after correcting the wrong path `/usr/lib/libMonoPosixHelper.so` to >>> `/usr/lib64/libMonoPosixHelper.so` in `/etc/mono/config` everything >>> worked as expected. >>> >> >> That is not an appropriate patch; it is completely 64bit-centric, just >> as the config in the source code is completely 32bit-centric. >> >> I forwarded a "neutral" patch to the maintainer about two months ago - >> he said he would review it and submit an update. In the meantime, >> version 4.x.x is available which includes its own fix for the problem >> (actually, some of the later 3.x.x versions after the SBo version also >> had the fix). >> >> The latest version I tried was 4.0.2.4 and it works fine without patching. >> >> chris > > Christoph, > > Is there a neutral patch for mono2? I just had a look at 2.10.9 and it seems corrected already (like the later 3.x.x versions). In data/config.in, the relevant line is: In 3.10.0, this incorrectly has an absolute path to @prefix@/lib/ in front of libMonoPosixHelper at libsuffix@. chris From ts at websafe.pl Mon Aug 10 11:14:09 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Mon, 10 Aug 2015 13:14:09 +0200 Subject: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64 In-Reply-To: <55C82395.5050102@iinet.net.au> References: <55C7A277.4080407@websafe.pl> <55C82395.5050102@iinet.net.au> Message-ID: <55C88781.2090402@websafe.pl> On 08/10/2015 06:07 AM, Christoph Willing wrote: > That is not an appropriate patch; it is completely 64bit-centric, just > as the config in the source code is completely 32bit-centric. Sorry for that, this patch wasn't meant to be a patch for the slackbuild package, just for visualisation of changes I've made that allowed me to run KeePass. Sorry for misleading. -- Best regards, Thomas Szteliga https://github.com/websafe/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3712 bytes Desc: S/MIME Cryptographic Signature URL: From larryhaja at gmail.com Mon Aug 10 18:10:50 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Mon, 10 Aug 2015 11:10:50 -0700 Subject: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64 In-Reply-To: <55C88781.2090402@websafe.pl> References: <55C7A277.4080407@websafe.pl> <55C82395.5050102@iinet.net.au> <55C88781.2090402@websafe.pl> Message-ID: This was also an issue with libgdiplus in the config file in earlier versions of mono. The issue seems to now be with MonoPosixHelper library. I'm providing a slightly updated patch to fix the /usr/lib issue. Thanks, --Larry On Mon, Aug 10, 2015 at 4:14 AM, Thomas Szteliga wrote: > On 08/10/2015 06:07 AM, Christoph Willing wrote: > > That is not an appropriate patch; it is completely 64bit-centric, just > > as the config in the source code is completely 32bit-centric. > > Sorry for that, this patch wasn't meant to be a patch for > the slackbuild package, just for visualisation of changes I've > made that allowed me to run KeePass. Sorry for misleading. > > -- > Best regards, > > Thomas Szteliga > https://github.com/websafe/ > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: config.patch Type: text/x-patch Size: 799 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mono.SlackBuild.patch Type: text/x-patch Size: 422 bytes Desc: not available URL: From 1.41421 at gmail.com Mon Aug 10 20:48:48 2015 From: 1.41421 at gmail.com (JCA) Date: Mon, 10 Aug 2015 14:48:48 -0600 Subject: [Slackbuilds-users] Building an older version of VirtualBox Message-ID: I am working in a project which assumes the presence of VirtualBox 4.3.10 - it has to be exactly that version. The current Slackbuilds repository builds 4.3.24. I tried using the virtualbox.tar.gz tarball for 4.3.24, just changing the version number before launching the compilation. However, this fails for the Slackbuilds script attempts to patch the VirtualBox source code - which it assumes to be 4.3.24, not 4.3.10. Rather than attempting to hack this code, I think that the easiest alternative is to try and get the virtualbox.tar.gz tarball that Slackbuilds used to build VritualBox 4.3.10 in its day. Anybody in this forum where I can download this tarball from? From ryan.q at linux.com Mon Aug 10 20:51:38 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 10 Aug 2015 13:51:38 -0700 Subject: [Slackbuilds-users] Building an older version of VirtualBox In-Reply-To: References: Message-ID: On 8/10/15, JCA <1.41421 at gmail.com> wrote: > I am working in a project which assumes the presence of VirtualBox > 4.3.10 - it has to be exactly that version. The current Slackbuilds > repository builds 4.3.24. I tried using the virtualbox.tar.gz tarball > for 4.3.24, just changing the version number before launching the > compilation. However, this fails for the Slackbuilds script attempts > to patch the VirtualBox source code - which it assumes to be 4.3.24, > not 4.3.10. > > Rather than attempting to hack this code, I think that the easiest > alternative is to try and get the virtualbox.tar.gz tarball that > Slackbuilds used to build VritualBox 4.3.10 in its day. Anybody in > this forum where I can download this tarball from? http://slackbuilds.org/cgit/slackbuilds/log/?qt=grep&q=virtualbox Looks like 4.3.10 is on that list. -- --- From 1.41421 at gmail.com Mon Aug 10 21:09:08 2015 From: 1.41421 at gmail.com (JCA) Date: Mon, 10 Aug 2015 15:09:08 -0600 Subject: [Slackbuilds-users] Building an older version of VirtualBox In-Reply-To: References: Message-ID: On Mon, Aug 10, 2015 at 2:51 PM, Ryan P.C. McQuen wrote: > On 8/10/15, JCA <1.41421 at gmail.com> wrote: >> I am working in a project which assumes the presence of VirtualBox >> 4.3.10 - it has to be exactly that version. The current Slackbuilds >> repository builds 4.3.24. I tried using the virtualbox.tar.gz tarball >> for 4.3.24, just changing the version number before launching the >> compilation. However, this fails for the Slackbuilds script attempts >> to patch the VirtualBox source code - which it assumes to be 4.3.24, >> not 4.3.10. >> >> Rather than attempting to hack this code, I think that the easiest >> alternative is to try and get the virtualbox.tar.gz tarball that >> Slackbuilds used to build VritualBox 4.3.10 in its day. Anybody in >> this forum where I can download this tarball from? > > http://slackbuilds.org/cgit/slackbuilds/log/?qt=grep&q=virtualbox > > Looks like 4.3.10 is on that list. > > -- > --- > > _______________________________________________ > 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/ > Much appreciated. I actually downloaded the Slackbuilds tag corresponding to 05/14/2014, which seems to be the one when the VirtualBox 4.3.10 update was picked up. I am sure there must be a more intelligent way of doing it, but this should work for me. From ryan.q at linux.com Mon Aug 10 21:11:02 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 10 Aug 2015 14:11:02 -0700 Subject: [Slackbuilds-users] Building an older version of VirtualBox In-Reply-To: References: Message-ID: > Much appreciated. I actually downloaded the Slackbuilds tag > corresponding to 05/14/2014, which seems to be the one when the > VirtualBox 4.3.10 update was picked up. I am sure there must be a more > intelligent way of doing it, but this should work for me. If you have the git repo cloned, you can use `git checkout`. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack.dhabyx at gmail.com Mon Aug 10 23:25:58 2015 From: slack.dhabyx at gmail.com (Dhaby Xiloj) Date: Mon, 10 Aug 2015 17:25:58 -0600 Subject: [Slackbuilds-users] tornado requires python-certifi Message-ID: <55C93306.8080009@gmail.com> Hi I built the mopidy packagewith all its dependencies, but when I ran I got the following message: pkg_resources.DistributionNotFound: The 'certifi' distribution was not found and is required by tornado Installing the package python-certifi mopidy works fine. Now, I guess python-certifi must be added to the list of dependencies of tornado slackBuild -- Dhaby Xiloj -------------- next part -------------- An HTML attachment was scrubbed... URL: From ts at websafe.pl Tue Aug 11 03:13:12 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Tue, 11 Aug 2015 05:13:12 +0200 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? Message-ID: <55C96848.10200@websafe.pl> SlackBuild templates (and scripts) contain this line: ~~~~ cat $CWD/$PRGNAM.SlackBuild \ > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild ~~~~ but what if a SlackBuild script requires patches applied during its execution. Shouldn't they be copied to $PKG/usr/doc/$PRGNAM-$VERSION/ as well? For example, `arj` requires a lot of patches but the SlackBuild script still contains only: ~~~~ cat $CWD/$PRGNAM.SlackBuild \ > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild ~~~~ leaving the patches out. -- Best regards, Thomas Szteliga https://github.com/websafe/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3712 bytes Desc: S/MIME Cryptographic Signature URL: From elyk03 at gmail.com Tue Aug 11 04:44:50 2015 From: elyk03 at gmail.com (Kyle Guinn) Date: Mon, 10 Aug 2015 23:44:50 -0500 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: <55C96848.10200@websafe.pl> References: <55C96848.10200@websafe.pl> Message-ID: On 8/10/15, Thomas Szteliga wrote: > SlackBuild templates (and scripts) contain this line: > > > ~~~~ > cat $CWD/$PRGNAM.SlackBuild \ > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > ~~~~ > > > but what if a SlackBuild script requires patches applied > during its execution. Shouldn't they be copied to > > > $PKG/usr/doc/$PRGNAM-$VERSION/ > > as well? > > > For example, `arj` > requires a lot of patches > but the > SlackBuild script > > still contains only: > > ~~~~ > cat $CWD/$PRGNAM.SlackBuild \ > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > ~~~~ > > > leaving the patches out. I've noticed this as well. Does anyone find it helpful that the script is installed in /usr/doc? Maybe we can omit it instead? -Kyle From ryan.q at linux.com Tue Aug 11 04:52:59 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 10 Aug 2015 21:52:59 -0700 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: References: <55C96848.10200@websafe.pl> Message-ID: > I've noticed this as well. Does anyone find it helpful that the > script is installed in /usr/doc? Maybe we can omit it instead? > > -Kyle Is anyone really that strapped for disk space that we need to be concerned? If the rare user is that concerned, surely they can write a script to clean out things like this. I like having the build script there, and wouldn't mind the patches being included also. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvogel4 at stny.rr.com Tue Aug 11 04:48:34 2015 From: jvogel4 at stny.rr.com (John Vogel) Date: Tue, 11 Aug 2015 00:48:34 -0400 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: References: <55C96848.10200@websafe.pl> Message-ID: <20150811004834.3328ff51@stygian.lan> On Mon, 10 Aug 2015 23:44:50 -0500 Kyle Guinn wrote: > On 8/10/15, Thomas Szteliga wrote: > > SlackBuild templates (and scripts) contain this line: > > > > > > ~~~~ > > cat $CWD/$PRGNAM.SlackBuild \ > > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > > ~~~~ > > > > > > but what if a SlackBuild script requires patches applied > > during its execution. Shouldn't they be copied to > > > > > > $PKG/usr/doc/$PRGNAM-$VERSION/ > > > > as well? > > > > > > For example, `arj` > > requires a lot of patches > > but the > > SlackBuild script > > > > still contains only: > > > > ~~~~ > > cat $CWD/$PRGNAM.SlackBuild \ > > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > > ~~~~ > > > > > > leaving the patches out. > > I've noticed this as well. Does anyone find it helpful that the > script is installed in /usr/doc? Maybe we can omit it instead? > > -Kyle > I like having the script installed to docdir. It's a quick reference to how the current package was built. I've utilized it's presence more than a few times. I'm not against having the patches there also. Seems innocuous and makes changes made to the source transparent. I don't feel it's actually necessary. I could see arguments against, such as unnecessary space being taken up, I guess. John From didier at slint.fr Tue Aug 11 05:19:41 2015 From: didier at slint.fr (Didier Spaier) Date: Tue, 11 Aug 2015 07:19:41 +0200 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: <55C96848.10200@websafe.pl> References: <55C96848.10200@websafe.pl> Message-ID: <55C985ED.1040308@slint.fr> Hi, On 11/08/2015 05:13, Thomas Szteliga wrote: > SlackBuild templates (and scripts) contain this line: > > > ~~~~ > cat $CWD/$PRGNAM.SlackBuild \ > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > ~~~~ > > > but what if a SlackBuild script requires patches applied > during its execution. Shouldn't they be copied to > > > $PKG/usr/doc/$PRGNAM-$VERSION/ > > as well? > > > For example, `arj` > requires a lot of patches > but the > SlackBuild script > > still contains only: > > ~~~~ > cat $CWD/$PRGNAM.SlackBuild \ > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > ~~~~ > > > leaving the patches out. > Well, it depends. In the aforementioned case, the patches comes for Debian that distributes them in a tarball found e.g. here for sid https://packages.debian.org/sid/arj In this case the Debian packaging tarball that includes the patches is: http://http.debian.net/debian/pool/main/a/arj/arj_3.10.22-14.debian.tar.xz IMHO including the patches in the SBo tarball, as done for arj, has the inconvennience that we don't know from which Debian packaging tarball (for sid, sqeeze, wheezy,stretch... ?) they come from. I didn't check but maybe the patches differ. For that reason in such a case tend to provide the link to the Debian packaging tarball as a source file unpacked by the SlackBuild, instead of including the patches in the SBo tarball. That's what I have for 'bogl', 'bidiv' or 'newt", not (yet) submitted but available here: http://slint.fr/packages/extra/bogl/build/ http://slint.fr/packages/extra/bidiv/build/ http://slint.fr/packages/extra/newt/build/ For instance: ---- for i in `cat ../debian/patches/series`; do cat ../debian/patches/$i | patch -p1 --verbose done ---- I think that makes the maintenance easier: _ We know from which Debian packaging tarball come the patches _ possibly some of them only are applied, but then we know which are left over. But there are other cases. For Bicon: http://slackbuilds.org/repository/14.1/system/bicon/ the source are on git and I cherry picked a patch from its commit and included it in the SBo tarball. In this case I agree that I could (should?) have provided it in $PKG/usr/doc/$PRGNAM-$VERSION/ possibly in a subdirectory $PKG/usr/doc/$PRGNAM-$VERSION/patches Cheers, Didier PS an attentive reader could notice that newt is already available @http://slackbuids.org. But it is built from the sources hosted @Fedora, that left over a patch allowing 'whiptail" to properly display bi-directional text. From yalhcru at gmail.com Tue Aug 11 06:02:53 2015 From: yalhcru at gmail.com (B Watson) Date: Tue, 11 Aug 2015 02:02:53 -0400 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: <55C985ED.1040308@slint.fr> References: <55C96848.10200@websafe.pl> <55C985ED.1040308@slint.fr> Message-ID: On 8/11/15, Didier Spaier wrote: > In this case the Debian packaging tarball that > includes the patches is: > http://http.debian.net/debian/pool/main/a/arj/arj_3.10.22-14.debian.tar.xz > IMHO including the patches in the SBo tarball, > as done for arj, has the inconvennience that > we don't know from which Debian packaging tarball > (for sid, sqeeze, wheezy,stretch... ?) they come > from. I didn't check but maybe the patches differ. They don't. If they did, they'd have a different patchlevel (the -14). I included the patches in the slackbuild tarball in the possible but unlikely event that debian.org disappears someday. As far as including patches in /usr/doc... if we're going to do that, we should be including everything from the slackbuild tarball. README, extra docs, .info file, etc. From willysr at slackbuilds.org Tue Aug 11 06:09:08 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 11 Aug 2015 13:09:08 +0700 Subject: [Slackbuilds-users] tornado requires python-certifi In-Reply-To: <55C93306.8080009@gmail.com> References: <55C93306.8080009@gmail.com> Message-ID: <55C99184.30903@slackbuilds.org> > I built the mopidy packagewith all its dependencies, but when I ran I > got the following message: > > pkg_resources.DistributionNotFound: The 'certifi' distribution was > not found and is required by tornado > > > Installing the package python-certifi mopidy works fine. > > Now, I guess python-certifi must be added to the list of dependencies of > tornado slackBuild Thanks fixed on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From gerardo.zamudio at linux.com Mon Aug 10 16:03:07 2015 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Mon, 10 Aug 2015 11:03:07 -0500 Subject: [Slackbuilds-users] OpenDKIM download location has changed In-Reply-To: <55C7DE87.8070109@slackbuilds.org> References: <55C79DE9.8030408@websafe.pl> <55C7DE87.8070109@slackbuilds.org> Message-ID: <55C8CB3B.2010507@linux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 08/09/2015 06:13 PM, Willy Sudiarto Raharjo wrote: >> OpenDKIM >> >> download location >> >> >> is no longer valid. >> >> The valid location for 2.10.1 is >> >> >> >> but there's already v. 2.10.3 available... >> > > Fixed on my branch > > > > > > _______________________________________________ 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/ > I've submitted an update - new version and MySQL support fix. - -- Gerardo Zamudio Linux System Administrator https://gerardozamudio.mx -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVyMs7AAoJEPbPpamee1lXemYQALB2pFms0Fxwvrl76TZ++XRI u4NCftzLzIJu7mv1GvT3dU9kbqUlY/lUXUYzl5UURtwj3KaC4eqXWarSjD9CyVPC I8mwOGn1wx9JVWTtn3DkPaNetALQm/liSbfQkp5sHIzvLvrPH6rxOdBPIoP3V0iJ rmI/nF6jMadoPjwJEZhRviq2kXyOqqOb91qo6zHXR25lzBB5RffCA1+ed4TDk6qa i6ohy3Pq/J0hsU6TeIro1tbJisQsr98YLcJ0FNy/u5PDkWV7kb3KyOSsH/8kNH98 CKvY8oBhCFZtETPbqq2IIdnJPdMuQIZWuM83uFgTsN61UCvepMlL8eDIkJRBNU08 NywJe50T8tk0684jcGYNLYimXq+lWB4IRJeYlmMLmSGZxCh8jKFrOWsCsYLLQzgM mcmGp7Lra6Ljf3vLsWlxs4AYpQcDYzGG068z5LjLIlZ7U0UgKaptMWJcowT9yN6k C1evKwb3yByAOI/MM0EqeUk3jIfl+UempHbxwxBPqpv+l6p5Vq+aR0P4fY+FM4lz HOHXEvbyyF1FiTSQa6kv3Ibrtjv7qeLw/820WQMbxtTDVZ7s/eDvSZAz+mTizTDA kBQ6jlY7GVy9v4RiymBgxZDHcRPpaRCtszSyIi6yxGkLjJ99bUzgXOPcoGfmWxtK HiZGoKKo4A/k6k0L6ymd =Nas3 -----END PGP SIGNATURE----- From erik at slackbuilds.org Tue Aug 11 14:46:57 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 11 Aug 2015 09:46:57 -0500 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: <55C96848.10200@websafe.pl> References: <55C96848.10200@websafe.pl> Message-ID: <20150811094657.30a59dd7@shaggy.doo> On Tue, 11 Aug 2015 05:13:12 +0200 Thomas Szteliga wrote: > but what if a SlackBuild script requires patches applied > during its execution. Shouldn't they be copied to > $PKG/usr/doc/$PRGNAM-$VERSION/ This is currently up to the maintainer and some scripts in the repo do copy the patches into the docs dir with the SlackBuild. So, there's nothing preventing it. I am all for making it mandatory, since a script can be completely useless without the patches. I also wouldn't mind the .info and build options (somehow) being documented in the final package. I've long held the opinion that all information required to rebuild the exact package should be included in the package itself. Thinking to a recent example that affected me, webkitgtk from ponce's repo is broken on it's own. The required libwebp package is not documented anywhere in/near the package. This is not ponce's fault, of course, since it was built with my script! :) I imagine this is difficult to solve for less experienced users, who may not know where the original script came from, or know/care to use ldd or other tools to find out what's missing. At the very least, I don't think there are any negatives to including patches and the .info file. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From erik at slackbuilds.org Tue Aug 11 14:53:20 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 11 Aug 2015 09:53:20 -0500 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: References: <55C96848.10200@websafe.pl> <55C985ED.1040308@slint.fr> Message-ID: <20150811095320.62d8fe00@shaggy.doo> On Tue, 11 Aug 2015 02:02:53 -0400 B Watson wrote: > On 8/11/15, Didier Spaier wrote: > > In this case the Debian packaging tarball that > > includes the patches is: > > http://http.debian.net/debian/pool/main/a/arj/arj_3.10.22-14.debian.tar.xz > > IMHO including the patches in the SBo tarball, > > as done for arj, has the inconvennience that > > we don't know from which Debian packaging tarball > > (for sid, sqeeze, wheezy,stretch... ?) they come > > from. I didn't check but maybe the patches differ. > > They don't. If they did, they'd have a different patchlevel (the -14). > > I included the patches in the slackbuild tarball in the possible but > unlikely event that debian.org disappears someday. I'm a bit divided on this, though I really do feel patches used (unaltered) from someplace like debian or fedora should just be linked in the .info file as a standard download. There's no real chance of them going away, but in that event the filename/md5sum from the .info file can be used to search for a mirror. There's no shortage of mirrors. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Tue Aug 11 14:58:40 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 11 Aug 2015 16:58:40 +0200 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: <20150811094657.30a59dd7@shaggy.doo> References: <55C96848.10200@websafe.pl> <20150811094657.30a59dd7@shaggy.doo> Message-ID: 2015-08-11 16:46 GMT+02:00 Erik Hanson : > Thinking to a recent example that affected me, webkitgtk from ponce's repo > is broken on it's own. The required libwebp package is not documented > anywhere in/near the package. This is not ponce's fault, of course, since it > was built with my script! :) I imagine this is difficult to solve for less > experienced users, who may not know where the original script came from, or > know/care to use ldd or other tools to find out what's missing. you mean my packages repository? but that is for my personal use only. :-) maybe you missed when it happened but I stated many times that if anybody would like to use it either they solve dependencies with the ones listed on SBo or use the repository as a whole: I don't provide dependency resolution for it. ;-) if instead you mean the script on git the webkitgtk.info file is the same as on SBo. regarding linking the tarball patches from debian it happened many times in the past that the versioned tarball linked had been removed fom their repository, breaking the download: that's the main reason why I would prefer them to be included with the script. Matteo From erik at slackbuilds.org Tue Aug 11 15:48:27 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 11 Aug 2015 10:48:27 -0500 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: References: <55C96848.10200@websafe.pl> <20150811094657.30a59dd7@shaggy.doo> Message-ID: <20150811104827.30f904cf@shaggy.doo> On Tue, 11 Aug 2015 16:58:40 +0200 Matteo Bernardini wrote: > 2015-08-11 16:46 GMT+02:00 Erik Hanson : > > Thinking to a recent example that affected me, webkitgtk from ponce's repo > > is broken on it's own. The required libwebp package is not documented > > anywhere in/near the package. , since it > > was built with my script! :) I imagine this is difficult to solve for less > > experienced users, who may not know where the original script came from, or > > know/care to use ldd or other tools to find out what's missing. > > you mean my packages repository? but that is for my personal use only. :-) > maybe you missed when it happened but I stated many times that if > anybody would like to use it either they solve dependencies with the > ones listed on SBo or use the repository as a whole: I don't provide > dependency resolution for it. ;-) > if instead you mean the script on git the webkitgtk.info file is the > same as on SBo. *sigh* > > This is not ponce's fault, of course > > This is not ponce's fault, of course > > This is not ponce's fault, of course > > This is not ponce's fault, of course > > This is not ponce's fault, of course Not sure if I could have been clearer, it wasn't an attack on you, or a call-out, or an invitation to discuss how Google returns Slackware package search results. Hint: it doesn't include or link to your disclaimers, README.txt files, emails, IRC logs, or any other places you've discussed how your repo works. In fact, it's really not about you or your repo at all: > > since it was built with my script! :) > > since it was built with my script! :) > > since it was built with my script! :) > > since it was built with my script! :) > > since it was built with my script! :) It's an example of a problem *I HAD* and is easily solvable. It happens with other well known repos. I suppose my mistake here was deciding to mention yours. Quickly needing a trustable webkitgtk package happened to me recently, was fresh on my mind, and works as an example for the discussion at hand. It applies to any other publicly/privately made repos using SBo scripts. If my script, or all SBo scripts, copied the .info file into the package, this wouldn't be an issue. The dep info would be there, in the package, irrespective of whether anyone chooses to include dep info in their repo or not. > regarding linking the tarball patches from debian it happened many > times in the past that the versioned tarball linked had been removed > fom their repository, breaking the download: that's the main reason > why I would prefer them to be included with the script. Nevermind, I guess. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Tue Aug 11 16:09:00 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 11 Aug 2015 18:09:00 +0200 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: <20150811104827.30f904cf@shaggy.doo> References: <55C96848.10200@websafe.pl> <20150811094657.30a59dd7@shaggy.doo> <20150811104827.30f904cf@shaggy.doo> Message-ID: 2015-08-11 17:48 GMT+02:00 Erik Hanson : > Not sure if I could have been clearer, it wasn't an attack on you, or a > call-out, or an invitation to discuss how Google returns Slackware package but I hadn't took it that way :D I just thought it would be another nice occasion to say that my personal repository is completely unsupported (it's never enough). > search results. Hint: it doesn't include or link to your disclaimers, > README.txt files, emails, IRC logs, or any other places you've discussed how > your repo works. In fact, it's really not about you or your repo at all: > >> > since it was built with my script! :) >> > since it was built with my script! :) >> > since it was built with my script! :) >> > since it was built with my script! :) >> > since it was built with my script! :) > > It's an example of a problem *I HAD* and is easily solvable. It happens > with other well known repos. I suppose my mistake here was deciding to > mention yours. Quickly needing a trustable webkitgtk package happened to > me recently, was fresh on my mind, and works as an example for the > discussion at hand. well, np at all, it's ok! really! :-) > It applies to any other publicly/privately made repos using SBo scripts. If > my script, or all SBo scripts, copied the .info file into the package, this > wouldn't be an issue. The dep info would be there, in the package, > irrespective of whether anyone chooses to include dep info in their repo or > not. well, one of the reason why I won't support dependency resolution at al is that I make large use of optional ones: in the example I might have built webkitgtk against geoclue, and that information wouldn't have gone in the info file (not to mention the case of ffmpeg). Matteo P.S. to clarify a little my previous statement regarding debian tarballs that include the patches and that they store in their /pool/ directories I really had to fix their download links many times in the past. taking as an example netcat-openbsd, its debian tarball now links to http://http.debian.net/debian/pool/main/n/netcat-openbsd/netcat-openbsd_1.105-7.debian.tar.gz: if we link that and they increment their version for whatever reason (from 7 to 8) the download is broken. From erik at slackbuilds.org Wed Aug 12 04:49:23 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 11 Aug 2015 23:49:23 -0500 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: References: <55C96848.10200@websafe.pl> <20150811094657.30a59dd7@shaggy.doo> <20150811104827.30f904cf@shaggy.doo> Message-ID: <20150811234923.114ec3f7@shaggy.doo> On Tue, 11 Aug 2015 18:09:00 +0200 Matteo Bernardini wrote: > well, one of the reason why I won't support dependency resolution at > al is that I make large use of optional ones: in the example I might > have built webkitgtk against geoclue, and that information wouldn't > have gone in the info file (not to mention the case of ffmpeg). This isn't dependency resolution though, I see it more as package description. I hadn't considered optional deps, but then I don't really consider the option of dumping the .info file in a complete solution. It's more a starting point, something for people to consider, discuss, expand upon. Remember, I had mentioned build options as well. > P.S. to clarify a little my previous statement regarding debian > tarballs that include the patches and that they store in their /pool/ > directories I really had to fix their download links many times in the > past. > taking as an example netcat-openbsd, its debian tarball now links to > http://http.debian.net/debian/pool/main/n/netcat-openbsd/netcat-openbsd_1.105-7.debian.tar.gz: > if we link that and they increment their version for whatever reason > (from 7 to 8) the download is broken. I wasn't aware debian did this. Seems it would be smarter to include all patches with the SlackBuild then. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Wed Aug 12 05:38:25 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 11 Aug 2015 22:38:25 -0700 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: <55C96848.10200@websafe.pl> References: <55C96848.10200@websafe.pl> Message-ID: <55CADBD1.4080303@gmail.com> On 08/10/2015 08:13 PM, Thomas Szteliga wrote: > SlackBuild templates (and scripts) contain this line: > > > ~~~~ > cat $CWD/$PRGNAM.SlackBuild \ > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > ~~~~ > > > but what if a SlackBuild script requires patches applied > during its execution. Shouldn't they be copied to > > > $PKG/usr/doc/$PRGNAM-$VERSION/ > > as well? > > > For example, `arj` > requires a lot of patches > but the > SlackBuild script > > still contains only: > > ~~~~ > cat $CWD/$PRGNAM.SlackBuild \ > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > ~~~~ > > > leaving the patches out. > > my 2 cents: The patches, and the slackbuild script itself, is only useful if you want to build the package. Neither has any compelling need to be in /usr/doc, and are perfectly useless by themselves. Any patches needed to compile the source should, nay must, be included in the $PRGNAM.tar.gz tar ball. Including the tar ball in /usr/doc is just redundant: this is easily available on SBo, SBo git and any number of mirrors. Besides, any user will ALREADY have these files downloaded. For those who say "hard drive space is cheap:" Do no assume others' financial condition or hardware availability. Also, wasting space is just inefficient and lazy. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Wed Aug 12 08:32:36 2015 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 12 Aug 2015 09:32:36 +0100 Subject: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`? In-Reply-To: <20150811234923.114ec3f7@shaggy.doo> References: <55C96848.10200@websafe.pl> <20150811094657.30a59dd7@shaggy.doo> <20150811104827.30f904cf@shaggy.doo> <20150811234923.114ec3f7@shaggy.doo> Message-ID: Erik: > Remember, I had mentioned build options as well. The build options don't tell the whole story -- lots of builds pick up optional deps automatically. For autotools builds this could be recorded by gzipping the config.log into /usr/doc. cmake? scons? waf, god help us? If anyone is thinking "queue file", @'s would need to be eliminated. King Ed: > Including the tar ball in /usr/doc is just > redundant: this is easily available on SBo, SBo git and any number of > mirrors Exactly, the only thing that needs to be recorded is the git revision, anything more (e.g. the tarball) would be for user convenience, but not every user is the same. -D. From fernando.lopezjr at gmail.com Thu Aug 13 17:16:12 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 13 Aug 2015 11:16:12 -0600 Subject: [Slackbuilds-users] shutter update available. Message-ID: current version in slackbuilds: 0.86.4 latest version is: 0.93.1 can we please update this? -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Thu Aug 13 17:27:23 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 13 Aug 2015 19:27:23 +0200 Subject: [Slackbuilds-users] shutter update available. In-Reply-To: References: Message-ID: 2015-08-13 19:16 GMT+02:00 Fernando Lopez : > current version in slackbuilds: 0.86.4 > latest version is: 0.93.1 > > can we please update this? hi Fernando, the only supported slackware version is the latest stable, 14.1, and the present shutter script is this http://slackbuilds.org/repository/14.1/graphics/shutter/ I'm telling you this because you seems to be looking at an old version. if you're interested in an update for slackware-14.1 I suggest you write to the present maintainer. Matteo From fernando.lopezjr at gmail.com Thu Aug 13 17:33:14 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 13 Aug 2015 11:33:14 -0600 Subject: [Slackbuilds-users] shutter update available. In-Reply-To: References: Message-ID: my bad. i was looking at the 13.x package... hehehe... On Thu, Aug 13, 2015 at 11:27 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2015-08-13 19:16 GMT+02:00 Fernando Lopez : > > current version in slackbuilds: 0.86.4 > > latest version is: 0.93.1 > > > > can we please update this? > > hi Fernando, > > the only supported slackware version is the latest stable, 14.1, and > the present shutter script is this > > http://slackbuilds.org/repository/14.1/graphics/shutter/ > > I'm telling you this because you seems to be looking at an old version. > > if you're interested in an update for slackware-14.1 I suggest you > write to the present maintainer. > > Matteo > _______________________________________________ > 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/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From arkadiusz at drabczyk.org Fri Aug 14 03:23:15 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Fri, 14 Aug 2015 05:23:15 +0200 Subject: [Slackbuilds-users] games/adom incorrect download link Message-ID: <20150814032315.GB7164@comp.lan> New download links for the version we currently have are:: DOWNLOAD=http://www.ancardia.com/download/old/1.2.0_pre23/adom_linux_debian_32_1.2.0_pre23.tar.gz DOWNLOAD_x86_64=http://www.ancardia.com/download/old/1.2.0_pre23/adom_linux_debian_64_1.2.0_pre23.tar.gz However, this version is quite old. It was released in May 2014. There are many newer versions available here: http://www.ancardia.com/download/. Additionally ADOM's author said that the newest version is the last that is free http://www.ancardia.com/download.html: "This is the lastest publicly available prerelease. The next prereleases (Release 60 and above) will only be available to people who pledged at least $25 in the ADOM resurrection campaign." In such situation I think it would be the best to upgrade ADOM to the newest version and leave it until it will be free again or remove it completely. -- Arkadiusz Drabczyk From didier at slint.fr Thu Aug 13 22:17:26 2015 From: didier at slint.fr (Didier Spaier) Date: Fri, 14 Aug 2015 00:17:26 +0200 Subject: [Slackbuilds-users] Please remove bicon. Message-ID: <55CD1776.6040703@slint.fr> Please remove bicon from the repository. The SlackBuild moves specific fonts in a standard location, whereas the binary looks for them elsewhere. I didn't realize that while testing, because I had an older version of bicon in /usr/local/bin that was picked up instead of the newer one, as /usr/local/bin precedes /us/bin in my $PATH. Sorry, lesson learned. I will re-submit later. Best regards, Didier From willysr at slackbuilds.org Thu Aug 13 23:47:43 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Aug 2015 06:47:43 +0700 Subject: [Slackbuilds-users] Please remove bicon. In-Reply-To: <55CD1776.6040703@slint.fr> References: <55CD1776.6040703@slint.fr> Message-ID: <55CD2C9F.2030306@slackbuilds.org> > Please remove bicon from the repository. Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Aug 13 23:58:32 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Aug 2015 06:58:32 +0700 Subject: [Slackbuilds-users] games/adom incorrect download link In-Reply-To: <20150814032315.GB7164@comp.lan> References: <20150814032315.GB7164@comp.lan> Message-ID: <55CD2F28.40009@slackbuilds.org> > New download links for the version we currently have are:: > > DOWNLOAD=http://www.ancardia.com/download/old/1.2.0_pre23/adom_linux_debian_32_1.2.0_pre23.tar.gz > DOWNLOAD_x86_64=http://www.ancardia.com/download/old/1.2.0_pre23/adom_linux_debian_64_1.2.0_pre23.tar.gz Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Fri Aug 14 00:30:52 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Aug 2015 07:30:52 +0700 Subject: [Slackbuilds-users] removal of lensfun-legacy Message-ID: <55CD36BC.9080606@slackbuilds.org> Since rawstudio is now buildable against lensfun 3.x, i'm removing lensfun-legacy from our repository in the next batch of update. AFAIK rawstudio is the last package that requires lensfun-legacy. If anyone still need lensfun-legacy on the repository, please let me know Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lramos.prof at yahoo.com.br Fri Aug 14 16:30:25 2015 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Fri, 14 Aug 2015 13:30:25 -0300 Subject: [Slackbuilds-users] geany-plugins: broken link Message-ID: <20150814163024.GA14604@giustizia> Hello, Michiel, it seems geany-plugins has a broken link in the upstream tarball URL: http://plugins.geany.org/geany-plugins/geany-plugins-1.24.tar.bz2 Probably they bumped the version up to 1.25, and erased the previous version. I tried to recover the tarball version 1.24 using git, but haven't succeed (yet). Another way to go would be to raise geany-plugins and geany itself to 1.25. It hadn't worked in the first trial, anyway: geany 1.25 fails to build with current slackbuild script. I will try something, anyway, but I currently don't have so much spare time. Thanks, Luiz Ramos S?o Paulo - Brazil lramos dot prof at yahoo dot com dot br From citizen.anon.x at gmail.com Fri Aug 14 21:30:10 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Fri, 14 Aug 2015 17:30:10 -0400 Subject: [Slackbuilds-users] murrine-themes file size mismatch Message-ID: http://slackbuilds.org/repository/14.1/desktop/murrine-themes/ The md5sum fails for the 1st file to download, which is https://www.dropbox.com/s/h0wdg2p8ohmo7pm/murrine-themes_0.98.10.tar.xz Info file reports md5sum as: badc50ec001afe363b89bed9c0e12a12 Actual md5sum is: a913247790952c2a700630c8bbba9212 http://slackbuilds.org/slackbuilds/14.1/desktop/murrine-themes/murrine-themes.SlackBuild -------------- next part -------------- An HTML attachment was scrubbed... URL: From citizen.anon.x at gmail.com Fri Aug 14 21:36:31 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Fri, 14 Aug 2015 17:36:31 -0400 Subject: [Slackbuilds-users] False report on murrine-themes size mismatch Message-ID: Apologies. Apparently the file that gets downloaded is incomplete. Is this incomplete file archive hosted on slackbuilds.org? In any case, I downloaded from the link referenced in the info file and the original md5sum was correct, so something is off. -------------- next part -------------- An HTML attachment was scrubbed... URL: From relativ at openmailbox.org Sat Aug 15 00:14:10 2015 From: relativ at openmailbox.org (Relativ) Date: Fri, 14 Aug 2015 20:14:10 -0400 Subject: [Slackbuilds-users] foobillard plus install error and solution Message-ID: <8df2ff7242949e27904275c28bdc8739@openmailbox.org> Hello SlackBuild users, http://slackbuilds.org/repository/14.1/games/foobillardplus/?search=foobillardplus I tried to install foobillardplus (3.43beta) from the slackbuild and the install errored out as seen below make[3]: Entering directory `/usr/src/slapt-src/games/foobillardplus/foobillardplus-code-170' mkdir -p /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp -p ./data/* /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data -R cp -p ./AUTHORS /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp -p ./COPYING /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp -p ./INSTALL /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp -p ./README /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp -p ./ChangeLog /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp -p ./TODO /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp -p ./OFL.txt /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp -p ./foobillardplus.desktop /usr/src/slapt-src/games/foobillardplus/package-foobillardplus/usr/games/foobillardplus/data cp: cannot stat ?./foobillardplus.desktop?: No such file or directory I was able to fix this error by simply placing a file called 'foobillardplus.desktop' into my '/usr/src/slapt-src/games/foobillardplus/foobillardplus-code-170' folder and re-running the slackbuild script. After placing that file the install finished fine. There is one other issue - the actual foobillard.desktop file that gets created doesn't work becuase the 'exec' parameter is set to 'foobillard' instead of 'foobillardplus'. Once I changed the entry, the program then runs fine from the menu shortcut that was created in my xfce menu. Thanks for all your efforts. A happy slacker, Rel From willysr at slackbuilds.org Sat Aug 15 00:20:04 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Aug 2015 07:20:04 +0700 Subject: [Slackbuilds-users] geany-plugins: broken link In-Reply-To: <20150814163024.GA14604@giustizia> References: <20150814163024.GA14604@giustizia> Message-ID: <55CE85B4.7080903@slackbuilds.org> > it seems geany-plugins has a broken link in the upstream tarball URL: > > http://plugins.geany.org/geany-plugins/geany-plugins-1.24.tar.bz2 > > Probably they bumped the version up to 1.25, and erased the previous > version. > > I tried to recover the tarball version 1.24 using git, but haven't succeed (yet). > > Another way to go would be to raise geany-plugins and geany itself to 1.25. It hadn't > worked in the first trial, anyway: geany 1.25 fails to build with > current slackbuild script. > > I will try something, anyway, but I currently don't have so much spare > time. For now, i host it on SF until the maintainer is working on new update -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Aug 15 01:15:13 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Aug 2015 08:15:13 +0700 Subject: [Slackbuilds-users] foobillard plus install error and solution In-Reply-To: <8df2ff7242949e27904275c28bdc8739@openmailbox.org> References: <8df2ff7242949e27904275c28bdc8739@openmailbox.org> Message-ID: <55CE92A1.9010701@slackbuilds.org> > Hello SlackBuild users, > > http://slackbuilds.org/repository/14.1/games/foobillardplus/?search=foobillardplus > > > I tried to install foobillardplus (3.43beta) from the slackbuild and the > install errored out as seen below > I was able to fix this error by simply placing a file called > 'foobillardplus.desktop' into my > '/usr/src/slapt-src/games/foobillardplus/foobillardplus-code-170' folder > and re-running the slackbuild script. After placing that file the > install finished fine. > > There is one other issue - the actual foobillard.desktop file that gets > created doesn't work becuase the 'exec' parameter is set to 'foobillard' > instead of 'foobillardplus'. Once I changed the entry, the program then > runs fine from the menu shortcut that was created in my xfce menu. Thanks fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Aug 15 08:25:41 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Aug 2015 15:25:41 +0700 Subject: [Slackbuilds-users] Updates - 20150815.1 Message-ID: <55CEF785.8010904@slackbuilds.org> Sat Aug 15 08:13:43 UTC 2015 academic/sword-data-kjv: Update MD5SUM. academic/xiphos: Updated for version 4.0.3. audio/pogo: Update MAN location. audio/qmmp-plugin-pack: Updated for version 0.8.5. desktop/ComixCursors: Fix DOWNLOAD and HOMEPAGE. desktop/notion: Updated for version 3_2015061300. desktop/obmenu-generator: Updated for version 0.66. desktop/sun: Updated for version 1.1.3. development/atom: Fix typo. development/codelite: Updated for version 8.1. development/ebe: Updated for version 3.0.3. development/geany-plugins: Update DOWNLOAD url. development/git-lfs: Added (Git extension). games/adom: Fix DOWNLOAD url. games/foobillardplus: Fix missing .desktop file. games/mednafen: Change CXXFLAGS & updated for 0.9.38.6. games/qzdl: Added (Qt Doom Launcher). games/scid_vs_pc: Updated for version 4.14. gis/Fiona: Updated for version 1.6.1. gis/cligj: Updated for version 0.3.0. gis/pointcloud: Updated for version 1.0.1. gis/rasterio: Updated for version 0.26.0. graphics/dia: Update HOMEPAGE. graphics/digikam: Updated for version 4.12.0. graphics/rawstudio: Patched for newer lensfun. libraries/gcab: Added (A GObject library to create cabinet files). libraries/lensfun-legacy: Removed. libraries/libsidplayfp: Updated for version 1.8.1 libraries/live555: Updated for version 2015.08.07. libraries/python3-PyQt5: Added (Python bindings for Qt). libraries/vigra: Add cmake switch. misc/KeePass: Updated for version 2.30. misc/portecle: Updated for version 1.9. multimedia/Mopidy: Update DEP. multimedia/flashplayer-plugin: Updated for version 11.2.202.508. multimedia/obs-studio: Added (Open Broadcaster Software). network/OpenDKIM: Updated for version 2.10.3. network/aggregate: Added (optimise a list of route prefixes). network/greenbone-security-assistant: Updated for version 6.0.5. network/guacamole-client: Added (Guacamole client). network/guacamole-server: Added (Guacamole server). network/imapproxy: Added (SquirrelMail's IMAP Proxy server). network/memcached-init: Added (memcached init and config). network/ocsync: Removed (included in owncloud). network/openvas-manager: Updated for version 6.0.5. network/owncloud-client: Updated for version 1.8.4. network/packETH: Added (A Linux GUI packet generator tool). network/synergy: Updated for version 1.7.4 network/tor-browser: Updated for version 5.0. network/vmware-horizon-client: Added (VMWare Horizon Client). network/vmware-view-client: Removed (renamed vmware-horizon-client). office/libreoffice: Fix MD5SUM and path. office/xtrkcad: Updated for version 4.2.1. perl/perl-BerkeleyDB: Updated for version 0.25. perl/perl-Canary-Stability: Added (Canary::Stability). perl/perl-Convert-UUlib: Updated for version 1.5. perl/perl-Module-Pluggable: Updated for version 5.2. perl/perl-Sidef: Added (A modern OOP language). perl/perl-Sub-Uplevel: Updated for version 0.25. perl/perl-Test-Exception: Updated for version 0.40. python/click-plugins: Added (extension to click). python/pbr: Updated for version 1.5.0. python/pysed: Update DOWNLOAD. python/python3-lhafile: Added (Python LHA archive extension). python/python3-sip: Added (Tool to generate Python bindings). python/snuggs: Added (s-expressions for Numpy). system/TLP: Updated for version 0.8. system/bicon: Removed (maintainer's request). system/blktrace: Added (block layer IO tracing mechanism). system/drbd-utils: Fixes for regression of drbd-8.4 pacemaker system/firmware-gobi-2000: Added (Qualcomm Gobi 2000 firmware). system/msitools: Added (Inspect and build Windows Installer). system/openrc-services: Updated for version 20150810. system/scrypt: Updated for version 1.2.0. system/slpkg: Updated for version 2.7.3. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From titopoquito at gmail.com Mon Aug 17 07:09:39 2015 From: titopoquito at gmail.com (titopoquito) Date: Mon, 17 Aug 2015 09:09:39 +0200 Subject: [Slackbuilds-users] [SlackBuild-Users] Opinions needed - hugin and incompatibilities with stock Slackware package Message-ID: <55D188B3.7080905@gmail.com> Hi all, I am the maintainer of the hugin SlackBuild, a program for creating panorama photos. A newer version has been released about a week ago. When compiling it, I succeeded first, then ran into problems trying to reproduce it. Being none of a programmer, I finally (after serious headbanging) found two workarounds that both look not optimal to me. Opinions on this one are highly appreciated. Problem overview: hugin needs enblend-enfuse, which in turn needs the vigra library. For the new hugin version, vigra needs to be build with openexr support. That's fine, openexr is bundled with Slackware 14.1. But when vigra is compiled with openexr-support then enblend-enfuse later stops during configuring claiming that libvigraimpex is not found [if someone wants more info about this, please email me]. No error is given if vigra is compiled without the openexr option, but then hugin later refuses to compile because it says vigra has to be compiled with openexr support. Duh. Workaround 1: Install vigra twice - first without openexr support, then compile enblend-enfuse, then the second vigra install WITH openexr support. With this, hugin compiles, but I cannot say if it will give errors working on real high dynamic-range photos. Workaround 2: I could trace down enblend-enfuses unwillingess to compile with the openexr-enabled vigra to to the ilmbase package bundled with Slackware. ilmbase does not pick up pthread libraries without being told so explicitely. When compiled with "-pthread" added to the SLKCFLAGS the errors disappear and all build fine - ilmbase, openexr [rebuilt just to be sure], vigra, enblend-enfuse, hugin. BINGO. But as it is shipped with Slackware and obviously noone had problems before, I hesitate asking Pat to include this pthread option, the more because it is not for security reasons. So I am considering to forget the new hugin version for now and to ask Pat to include the pthread option to ilmbase for the upcoming release. If you got here thanks for reading :D Any thoughts/suggestions? Tito From yalhcru at gmail.com Mon Aug 17 10:24:42 2015 From: yalhcru at gmail.com (B Watson) Date: Mon, 17 Aug 2015 06:24:42 -0400 Subject: [Slackbuilds-users] [SlackBuild-Users] Opinions needed - hugin and incompatibilities with stock Slackware package In-Reply-To: <55D188B3.7080905@gmail.com> References: <55D188B3.7080905@gmail.com> Message-ID: On 8/17/15, titopoquito wrote: > If you got here thanks for reading :D Any thoughts/suggestions? This may not be very helpful... but, if you can get all those libraries to compile statically, you can build the whole stack in your slackbuild (including the one that's in slackware base) and link against them. The final package shouldn't contain the static libs, just the binary you built against them. Lot of work, and maybe not worth it if Pat accepts your suggestion. From ryan.q at linux.com Mon Aug 17 10:30:43 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 17 Aug 2015 03:30:43 -0700 Subject: [Slackbuilds-users] [SlackBuild-Users] Opinions needed - hugin and incompatibilities with stock Slackware package In-Reply-To: References: <55D188B3.7080905@gmail.com> Message-ID: > Lot of work, and maybe not worth it if Pat accepts your suggestion. Pat seems to be pretty receptive to rebuilding things for a reason like this. It is definitely worth asking him. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Mon Aug 17 11:06:08 2015 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 17 Aug 2015 12:06:08 +0100 Subject: [Slackbuilds-users] [SlackBuild-Users] Opinions needed - hugin and incompatibilities with stock Slackware package In-Reply-To: References: <55D188B3.7080905@gmail.com> Message-ID: It seems to be a straightforward underlinking error in enblend-enfuse. Just add LDFLAGS="-lpthread" to the configure in enblend-enfuse, then everything works (including building hugin), there is no need to change ilmbase :-) All the best -D. From titopoquito at gmail.com Mon Aug 17 12:06:27 2015 From: titopoquito at gmail.com (titopoquito) Date: Mon, 17 Aug 2015 14:06:27 +0200 Subject: [Slackbuilds-users] [SlackBuild-Users] Opinions needed - hugin and incompatibilities with stock Slackware package In-Reply-To: References: <55D188B3.7080905@gmail.com> Message-ID: <55D1CE43.2070501@gmail.com> Hi all, many thanks so far for your input. I will try to compile and again and see if it works when I'm home again. That would indeed be the most simple solution I can think of. I'm none of a programmer, so this kind of stuff is something I can't come up with myself. Thanks for this lesson to learn :D Tito On 17.08.2015 13:06, David Spencer wrote: > It seems to be a straightforward underlinking error in enblend-enfuse. > Just add LDFLAGS="-lpthread" to the configure in enblend-enfuse, then > everything works (including building hugin), there is no need to > change ilmbase :-) > > All the best > -D. > _______________________________________________ > 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 emmanueln at gmail.com Tue Aug 18 14:17:11 2015 From: emmanueln at gmail.com (Emmanuel) Date: Tue, 18 Aug 2015 11:17:11 -0300 Subject: [Slackbuilds-users] New packages: slurm and munge Message-ID: Hi everybody, I'm preparing two new packages, munge (http://dun.github.io/munge/) and slurm (http://slurm.schedmd.com/). Both packages can run as an unprivileged user, can somebody reserve two uids/gids for theses packages? These are the first packages I'm submitting, can I send them to the mailing list for someone with experience to take a look first or just submit them? I'm also updating OpenMPI, Erik Hanson drop it and no one volunteer to update it, it this ok? Thanks -- ******************** Emmanuel Millan -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Aug 18 14:57:46 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 18 Aug 2015 21:57:46 +0700 Subject: [Slackbuilds-users] New packages: slurm and munge In-Reply-To: References: Message-ID: <55D347EA.6020207@slackbuilds.org> > I'm preparing two new packages, munge (http://dun.github.io/munge/) and > slurm (http://slurm.schedmd.com/). Both packages can run as an unprivileged > user, can somebody reserve two uids/gids for theses packages? use 310 (munge) and 311 (slurm) > These are the first packages I'm submitting, can I send them to the mailing > list for someone with experience to take a look first or just submit them? both are fine > I'm also updating OpenMPI, Erik Hanson drop it and no one volunteer to > update it, it this ok? Sure, go for it :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From emmanueln at gmail.com Tue Aug 18 17:43:33 2015 From: emmanueln at gmail.com (Emmanuel) Date: Tue, 18 Aug 2015 14:43:33 -0300 Subject: [Slackbuilds-users] New packages: slurm and munge In-Reply-To: <55D347EA.6020207@slackbuilds.org> References: <55D347EA.6020207@slackbuilds.org> Message-ID: On Tue, Aug 18, 2015 at 11:57 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I'm preparing two new packages, munge (http://dun.github.io/munge/) and > > slurm (http://slurm.schedmd.com/). Both packages can run as an > unprivileged > > user, can somebody reserve two uids/gids for theses packages? > > > use 310 (munge) and 311 (slurm) > > > These are the first packages I'm submitting, can I send them to the > mailing > > list for someone with experience to take a look first or just submit > them? > > both are fine > > > I'm also updating OpenMPI, Erik Hanson drop it and no one volunteer to > > update it, it this ok? > > Sure, go for it :) > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > 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/ > > > Great, thanks, I'm going to submit the packages directly. -- ***************** Emmanuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From citizen.anon.x at gmail.com Wed Aug 19 15:53:45 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Wed, 19 Aug 2015 11:53:45 -0400 Subject: [Slackbuilds-users] [SlackBuild-Users] Opinions needed - hugin and incompatibilities with stock Slackware package In-Reply-To: <55D188B3.7080905@gmail.com> References: <55D188B3.7080905@gmail.com> Message-ID: Hello, Maybe try adding a --library=/directory switch into the build script that points to it. On Mon, Aug 17, 2015 at 3:09 AM, titopoquito wrote: > Hi all, > > I am the maintainer of the hugin SlackBuild, a program for creating > panorama photos. A newer version has been released about a week ago. When > compiling it, I succeeded first, then ran into problems trying to reproduce > it. Being none of a programmer, I finally (after serious headbanging) found > two workarounds that both look not optimal to me. Opinions on this one are > highly appreciated. > > Problem overview: > hugin needs enblend-enfuse, which in turn needs the vigra library. For the > new hugin version, vigra needs to be build with openexr support. That's > fine, openexr is bundled with Slackware 14.1. But when vigra is compiled > with openexr-support then enblend-enfuse later stops during configuring > claiming that libvigraimpex is not found [if someone wants more info about > this, please email me]. No error is given if vigra is compiled without the > openexr option, but then hugin later refuses to compile because it says > vigra has to be compiled with openexr support. Duh. > > Workaround 1: > Install vigra twice - first without openexr support, then compile > enblend-enfuse, then the second vigra install WITH openexr support. With > this, hugin compiles, but I cannot say if it will give errors working on > real high dynamic-range photos. > > Workaround 2: > I could trace down enblend-enfuses unwillingess to compile with the > openexr-enabled vigra to to the ilmbase package bundled with Slackware. > ilmbase does not pick up pthread libraries without being told so > explicitely. When compiled with "-pthread" added to the SLKCFLAGS the > errors disappear and all build fine - ilmbase, openexr [rebuilt just to be > sure], vigra, enblend-enfuse, hugin. BINGO. > But as it is shipped with Slackware and obviously noone had problems > before, I hesitate asking Pat to include this pthread option, the more > because it is not for security reasons. > > So I am considering to forget the new hugin version for now and to ask Pat > to include the pthread option to ilmbase for the upcoming release. > > If you got here thanks for reading :D Any thoughts/suggestions? > > Tito > _______________________________________________ > 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 titopoquito at gmail.com Thu Aug 20 07:17:19 2015 From: titopoquito at gmail.com (titopoquito) Date: Thu, 20 Aug 2015 09:17:19 +0200 Subject: [Slackbuilds-users] [SlackBuild-Users] Opinions needed - hugin and incompatibilities with stock Slackware package In-Reply-To: References: <55D188B3.7080905@gmail.com> Message-ID: <55D57EFF.4010806@gmail.com> Thanks for the input. I decided to go with David's suggestion and already have submitted both SlackBuilds. I hope this will work in future versions, too, else I have some ideas for other workarounds :) On 19.08.2015 17:53, Citizen X wrote: > Hello, > Maybe try adding a --library=/directory switch into the build script that > points to it. > > On Mon, Aug 17, 2015 at 3:09 AM, titopoquito wrote: > >> Hi all, >> >> I am the maintainer of the hugin SlackBuild, a program for creating >> panorama photos. A newer version has been released about a week ago. When >> compiling it, I succeeded first, then ran into problems trying to reproduce >> it. Being none of a programmer, I finally (after serious headbanging) found >> two workarounds that both look not optimal to me. Opinions on this one are >> highly appreciated. >> >> Problem overview: >> hugin needs enblend-enfuse, which in turn needs the vigra library. For the >> new hugin version, vigra needs to be build with openexr support. That's >> fine, openexr is bundled with Slackware 14.1. But when vigra is compiled >> with openexr-support then enblend-enfuse later stops during configuring >> claiming that libvigraimpex is not found [if someone wants more info about >> this, please email me]. No error is given if vigra is compiled without the >> openexr option, but then hugin later refuses to compile because it says >> vigra has to be compiled with openexr support. Duh. >> >> Workaround 1: >> Install vigra twice - first without openexr support, then compile >> enblend-enfuse, then the second vigra install WITH openexr support. With >> this, hugin compiles, but I cannot say if it will give errors working on >> real high dynamic-range photos. >> >> Workaround 2: >> I could trace down enblend-enfuses unwillingess to compile with the >> openexr-enabled vigra to to the ilmbase package bundled with Slackware. >> ilmbase does not pick up pthread libraries without being told so >> explicitely. When compiled with "-pthread" added to the SLKCFLAGS the >> errors disappear and all build fine - ilmbase, openexr [rebuilt just to be >> sure], vigra, enblend-enfuse, hugin. BINGO. >> But as it is shipped with Slackware and obviously noone had problems >> before, I hesitate asking Pat to include this pthread option, the more >> because it is not for security reasons. >> >> So I am considering to forget the new hugin version for now and to ask Pat >> to include the pthread option to ilmbase for the upcoming release. >> >> If you got here thanks for reading :D Any thoughts/suggestions? >> >> Tito >> _______________________________________________ >> 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 ryan.q at linux.com Fri Aug 21 18:25:03 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 21 Aug 2015 11:25:03 -0700 Subject: [Slackbuilds-users] superkey-launch Message-ID: Hi all, Does anyone want to take this over? I also maintain the code here: https://github.com/ryanpcmcquen/superkey-launch If you take over the build you would have to take over the repo as well. It is only one commit away from being in sync with the upstream project 'xcape'. If not we can drop the build from SBo, because I have no plan to maintain it. Thanks, Ryan -- --- From willysr at slackbuilds.org Sat Aug 22 16:52:59 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Aug 2015 23:52:59 +0700 Subject: [Slackbuilds-users] Updates - 20150822.1 Message-ID: <55D8A8EB.4010004@slackbuilds.org> Sat Aug 22 16:43:45 UTC 2015 academic/R: Updated for version 3.2.2. academic/jpicedt: Fix VERSION. desktop/pspshrink: Added (ISO compressor for PSP games). desktop/seafile-gui: Updated for version 4.3.2. development/Cython-Kivy: Added (C bindings for Python). development/geany-plugins: Updated for version 1.25. development/geany: Updated for version 1.25 development/jdk: Updated for version 8u60. development/meld3: Downgraded to 3.12.3. development/poedit: Updated for version 1.8.4. development/pyvim: Updated for version 0.0.8. development/zeal: Added (offline documentation browser). games/triplea: Updated for version 1.8.0.7. graphics/enblend-enfuse: Added LDFLAGS. graphics/hugin: Updated for version 2015.0.0. graphics/pngquant: Updated for version 2.5.1. libraries/Kivy: Update REQUIRES. libraries/SFML: Updated for version 2.3.1. libraries/botocore: Updated for version 1.1.9. libraries/cffi: Updated for version 1.2.0. libraries/libcangjie: Added (Library for Cangjie input method). libraries/libvirt-python: Updated for version 1.2.18. libraries/libvirt: Updated for version 1.2.18. libraries/tinyxml2: Updated for version 3.0.0. misc/mosquitto: Updated for version 1.4.3. misc/xca: Updated for version 1.3.0. multimedia/Mopidy: Updated for version 1.1.0. multimedia/beets: Updated for version 1.3.14. multimedia/guvcview: Updated for version 2.0.2. multimedia/lives: Updated for version 2.4.1. multimedia/picard-plugins: Updated for version 20150819. multimedia/yarock: Updated for version 1.1.3. network/Electrum: Updated for version 2.4.1. network/awscli: Updated for version 1.7.46. network/bitlbee-stream: Updated for version 1.3.1. network/bitlbee: Updated bitlbee for version 3.4.1. network/ccnet: Updated for version 4.3.2. network/ftp-cloudfs: Added (FTP interface). network/insync: Updated for version 1.2.18.35198. network/iojs: Updated for version 3.1.0. network/munge: Added (an authentication service). network/palemoon: Added (Web browser). network/razor-agents: Added patch. network/seafile-client: Updated for version 4.3.2. network/seafile-server: Updated for version 4.3.2. network/seahub: Updated for version 4.3.2. network/slurm: Added (workload manager). network/tixati: Added (P2P client). network/vivaldi: Updated for version 1.0.249.12_1. network/weechat: Updated for version 1.3. network/you-get: Updated for version 0.3.34. network/youtube-dl: Updated for version 2015.08.16.1. office/MasterPDFEditor: Updated for version 3.3.00. office/ProjectLibre: Updated for version 1.6.1. office/mathtex: Update MD5SUM. office/mined: Added (A terminal-based text editor). office/xtrkcad: Update source. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.022. perl/perl-Capture-Tiny: Updated for version 0.30. perl/perl-Date-Manip: Updated for version 6.50. perl/perl-Devel-Symdump: Updated for version 2.15. perl/perl-ExtUtils-InstallPaths: Updated for version 0.011. perl/perl-File-Tail: Updated for version 1.3. perl/perl-Moo: Updated for version 2.000002. perl/perl-Role-Tiny: Updated for version 2.000001. perl/perl-Test-Harness: Updated for version 3.35. perl/perl-Test-Inter: Updated for version 1.06. perl/perl-strictures: Updated for version 2.000001. python/click: Updated for version 5.1. python/npyscreen: Updated for version 4.10.0. python/path.py: Updated for version 7.6. python/prompt_toolkit: Updated for version 0.46. python/ptpython: Updated for version 0.21. python/pytest-cov: Updated for version 2.0.0. python/pytest: Update script. python/python-oauthlib: Updated for version 1.0.3. ruby/ruby2: Updated for version 2.2.3. system/Iosevka: Added (Open source monospace coding font). system/apcupsd: Updated for version 3.14.13. system/atop: Updated for version 2.2. system/exfat-utils: Updated for version 1.1.1. system/fuse-exfat: Updated for version 1.1.0. system/modules: Added (modification of a user's environment). system/netatop: Updated for version 0.6. system/openmpi: Updated for version 1.8.8 + new maintainer. system/slpkg: Updated for version 2.7.4. system/tomb: Updated for version 2.1.1. system/wangfonts: Added (Free Chinese TrueType fonts). +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hostmaster at slackonly.com Sun Aug 23 09:34:15 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 23 Aug 2015 12:34:15 +0300 Subject: [Slackbuilds-users] Arduino md5sums Message-ID: <55D99397.1080606@slackonly.com> Hi! Arduino sources have some wrong md5sums: package_index.json.gz actual md5sum is: 3706a10af3b6ce2a487326ada11813dd library_index.json.gz actual md5sum is: afaa7a2203ba68d7b39b5bdaadc8dd71 package_index.json.sig actual md5sum is: cec3bd1aa9c3adaad84edf069cd283e Thanks From mario at slackware.hr Sun Aug 23 18:14:51 2015 From: mario at slackware.hr (Mario Preksavec) Date: Sun, 23 Aug 2015 20:14:51 +0200 Subject: [Slackbuilds-users] Arduino md5sums In-Reply-To: <55D99397.1080606@slackonly.com> References: <55D99397.1080606@slackonly.com> Message-ID: <55DA0D9B.5020508@slackware.hr> On 08/23/2015 11:34 AM, Panagiotis Nikolaou wrote: > Hi! > > Arduino sources have some wrong md5sums: > > package_index.json.gz actual md5sum is: 3706a10af3b6ce2a487326ada11813dd > library_index.json.gz actual md5sum is: afaa7a2203ba68d7b39b5bdaadc8dd71 > package_index.json.sig actual md5sum is: cec3bd1aa9c3adaad84edf069cd283e > > Thanks > These will match (until everything is checked for the new version): http://mirror.slackware.hr/sources/Arduino/library_index.json.gz http://mirror.slackware.hr/sources/Arduino/package_index.json.gz http://mirror.slackware.hr/sources/Arduino/package_index.json.sig -- Mario From hostmaster at slackonly.com Mon Aug 24 08:57:47 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Mon, 24 Aug 2015 11:57:47 +0300 Subject: [Slackbuilds-users] md5sums Message-ID: <55DADC8B.5090801@slackonly.com> Hi!, bellow is some correct md5sums i have find: development: 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2 b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz games: c85ae3df00c6da353306c26b02e364b9 0.43.1.zip (bastet) 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz cae8ddb55879427631d995a2e6b16e55 nsudoku.c fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2 bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz graphics: 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz libraries: fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2 3ba445324203e4e0beb2bc1cd93c547a c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz (lua-zlib) multimedia: a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz python: 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz (path.py) Thanks... From mario at slackware.hr Mon Aug 24 09:52:42 2015 From: mario at slackware.hr (Mario Preksavec) Date: Mon, 24 Aug 2015 11:52:42 +0200 Subject: [Slackbuilds-users] md5sums In-Reply-To: <55DADC8B.5090801@slackonly.com> References: <55DADC8B.5090801@slackonly.com> Message-ID: <55DAE96A.9060508@slackware.hr> On 08/24/2015 10:57 AM, Panagiotis Nikolaou wrote: > Hi!, > bellow is some correct md5sums i have find: > > development: > 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2 > b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz > > games: > c85ae3df00c6da353306c26b02e364b9 0.43.1.zip (bastet) > 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz > cae8ddb55879427631d995a2e6b16e55 nsudoku.c > fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz > f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2 > bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz > > graphics: > 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz > > libraries: > > fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz > 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2 > 3ba445324203e4e0beb2bc1cd93c547a > c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz (lua-zlib) > > multimedia: > a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz > > python: > 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz (path.py) > > Thanks... Perhaps it would make more sense to look for tested tarballs that match md5sum from the info file? -- Mario From hostmaster at slackonly.com Mon Aug 24 10:02:11 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Mon, 24 Aug 2015 13:02:11 +0300 Subject: [Slackbuilds-users] md5sums In-Reply-To: <55DAE96A.9060508@slackware.hr> References: <55DADC8B.5090801@slackonly.com> <55DAE96A.9060508@slackware.hr> Message-ID: <55DAEBA3.3060907@slackonly.com> On 08/24/2015 12:52 PM, Mario Preksavec wrote: > On 08/24/2015 10:57 AM, Panagiotis Nikolaou wrote: >> Hi!, >> bellow is some correct md5sums i have find: >> >> development: >> 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2 >> b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz >> >> games: >> c85ae3df00c6da353306c26b02e364b9 0.43.1.zip (bastet) >> 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz >> cae8ddb55879427631d995a2e6b16e55 nsudoku.c >> fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz >> f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2 >> bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz >> >> graphics: >> 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz >> >> libraries: >> >> fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz >> 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2 >> 3ba445324203e4e0beb2bc1cd93c547a >> c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz (lua-zlib) >> >> multimedia: >> a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz >> >> python: >> 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz (path.py) >> >> Thanks... > > Perhaps it would make more sense to look for tested tarballs that > match md5sum from the info file? > I use slackrepo for building packages and the wrong md5sum in .info breaks the automation of slackrepo -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario at slackware.hr Mon Aug 24 10:27:39 2015 From: mario at slackware.hr (Mario Preksavec) Date: Mon, 24 Aug 2015 12:27:39 +0200 Subject: [Slackbuilds-users] md5sums In-Reply-To: <55DAEBA3.3060907@slackonly.com> References: <55DADC8B.5090801@slackonly.com> <55DAE96A.9060508@slackware.hr> <55DAEBA3.3060907@slackonly.com> Message-ID: <55DAF19B.9050805@slackware.hr> On 08/24/2015 12:02 PM, Panagiotis Nikolaou wrote: > I use slackrepo for building > packages and the wrong md5sum in .info breaks the automation of slackrepo That's the whole point behind md5sum logic, to let you know a file might be tampered with, esp. files with version numbers. Blindly updating md5sums will probably lead to a security breach somewhere down the road, I hope we are not doing just that and hoping for the best... :-) -- Mario -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Aug 24 10:28:31 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 24 Aug 2015 17:28:31 +0700 Subject: [Slackbuilds-users] md5sums In-Reply-To: <55DADC8B.5090801@slackonly.com> References: <55DADC8B.5090801@slackonly.com> Message-ID: <55DAF1CF.8080503@slackbuilds.org> > bellow is some correct md5sums i have find: > > development: > 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2 > b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz > > games: > c85ae3df00c6da353306c26b02e364b9 0.43.1.zip (bastet) > 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz > cae8ddb55879427631d995a2e6b16e55 nsudoku.c > fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz > f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2 > bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz > > graphics: > 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz > > libraries: > > fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz > 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2 > 3ba445324203e4e0beb2bc1cd93c547a > c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz (lua-zlib) > > multimedia: > a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz > > python: > 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz (path.py) It would be easier if the package name is listed as well -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hostmaster at slackonly.com Mon Aug 24 10:39:09 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Mon, 24 Aug 2015 13:39:09 +0300 Subject: [Slackbuilds-users] md5sums In-Reply-To: <55DAF1CF.8080503@slackbuilds.org> References: <55DADC8B.5090801@slackonly.com> <55DAF1CF.8080503@slackbuilds.org> Message-ID: <55DAF44D.7030707@slackonly.com> On 08/24/2015 01:28 PM, Willy Sudiarto Raharjo wrote: > development: > > 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2 > > b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz > > > > games: > > c85ae3df00c6da353306c26b02e364b9 0.43.1.zip (bastet) > > 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz > > cae8ddb55879427631d995a2e6b16e55 nsudoku.c > > fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz > > f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2 > > bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz > > > > graphics: > > 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz > > > > libraries: > > > > fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz > > 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2 > > 3ba445324203e4e0beb2bc1cd93c547a > > c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz (lua-zlib) > > > > multimedia: > > a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz > > > > python: > > 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz (path.py) Sure sorry about that... development: avr8-burn-o-mat (actual md5sum 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2) tiled-qt (actual md5sum b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz) games: bastet (actual md5sum c85ae3df00c6da353306c26b02e364b9 0.43.1.zip) bitfighter (actual md5sum 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz) nsudoku (actual md5sum cae8ddb55879427631d995a2e6b16e55 nsudoku.c) pom1 (actual md5sum fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz) redeclipse (actual md5sum f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2) yahtzee (actual md5sum bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz) graphics: fim (actual md5sum 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz) libraries: boolstuff (actual md5sum fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz) ioncube-loader (actual md5sum 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2) lua-zlib (actual md5sum 3ba445324203e4e0beb2bc1cd93c547a c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz) multimedia: flvtool2 (actual md5sum a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz) python: path.py (actual md5sum 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz) From willysr at slackbuilds.org Mon Aug 24 10:57:20 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 24 Aug 2015 17:57:20 +0700 Subject: [Slackbuilds-users] md5sums In-Reply-To: <55DAF44D.7030707@slackonly.com> References: <55DADC8B.5090801@slackonly.com> <55DAF1CF.8080503@slackbuilds.org> <55DAF44D.7030707@slackonly.com> Message-ID: <55DAF890.90003@slackbuilds.org> > Sure sorry about that... > > development: > avr8-burn-o-mat (actual md5sum 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2) > tiled-qt (actual md5sum b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz) > > games: > bastet (actual md5sum c85ae3df00c6da353306c26b02e364b9 0.43.1.zip) > bitfighter (actual md5sum 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz) > nsudoku (actual md5sum cae8ddb55879427631d995a2e6b16e55 nsudoku.c) > pom1 (actual md5sum fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz) > redeclipse (actual md5sum f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2) > yahtzee (actual md5sum bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz) > > graphics: > fim (actual md5sum 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz) > > libraries: > boolstuff (actual md5sum fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz) > ioncube-loader (actual md5sum 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2) > lua-zlib (actual md5sum 3ba445324203e4e0beb2bc1cd93c547a > c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz) > > multimedia: > flvtool2 (actual md5sum a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz) > > python: > path.py (actual md5sum 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz) All fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From erik at slackbuilds.org Mon Aug 24 11:21:57 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 24 Aug 2015 06:21:57 -0500 Subject: [Slackbuilds-users] md5sums In-Reply-To: <55DAF890.90003@slackbuilds.org> References: <55DADC8B.5090801@slackonly.com> <55DAF1CF.8080503@slackbuilds.org> <55DAF44D.7030707@slackonly.com> <55DAF890.90003@slackbuilds.org> Message-ID: <20150824062157.3425f234@shaggy.doo> On Mon, 24 Aug 2015 17:57:20 +0700 Willy Sudiarto Raharjo wrote: > > Sure sorry about that... > > > > development: > > avr8-burn-o-mat (actual md5sum 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2) > > tiled-qt (actual md5sum b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz) > > > > games: > > bastet (actual md5sum c85ae3df00c6da353306c26b02e364b9 0.43.1.zip) > > bitfighter (actual md5sum 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz) > > nsudoku (actual md5sum cae8ddb55879427631d995a2e6b16e55 nsudoku.c) > > pom1 (actual md5sum fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz) > > redeclipse (actual md5sum f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2) > > yahtzee (actual md5sum bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz) > > > > graphics: > > fim (actual md5sum 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz) > > > > libraries: > > boolstuff (actual md5sum fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz) > > ioncube-loader (actual md5sum 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2) > > lua-zlib (actual md5sum 3ba445324203e4e0beb2bc1cd93c547a > > c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz) > > > > multimedia: > > flvtool2 (actual md5sum a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz) > > > > python: > > path.py (actual md5sum 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz) > > All fixed in my branch All of these need to be checked more carefully.. nsudoku is a version bump and for flvtool2 the given sum (a33783..) matches what is basically a 404 document. I did not check others. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hostmaster at slackonly.com Mon Aug 24 11:52:52 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Mon, 24 Aug 2015 14:52:52 +0300 Subject: [Slackbuilds-users] md5sums In-Reply-To: <20150824062157.3425f234@shaggy.doo> References: <55DADC8B.5090801@slackonly.com> <55DAF1CF.8080503@slackbuilds.org> <55DAF44D.7030707@slackonly.com> <55DAF890.90003@slackbuilds.org> <20150824062157.3425f234@shaggy.doo> Message-ID: <55DB0594.5070708@slackonly.com> On 08/24/2015 02:21 PM, Erik Hanson wrote: > On Mon, 24 Aug 2015 17:57:20 +0700 > Willy Sudiarto Raharjo wrote: > >>> Sure sorry about that... >>> >>> development: >>> avr8-burn-o-mat (actual md5sum 3ce2f3205840b855e4c2494335b0540e AVR8_Burn-O-Mat_2_1_2_src.tar.bz2) >>> tiled-qt (actual md5sum b3afda73d80b70b96351ea2de8e0959c tiled-0.12.3.tar.gz) >>> >>> games: >>> bastet (actual md5sum c85ae3df00c6da353306c26b02e364b9 0.43.1.zip) >>> bitfighter (actual md5sum 5c41e2dc23c17a82b5a06d30cd4d6f45 bitfighter-019e.tar.gz) >>> nsudoku (actual md5sum cae8ddb55879427631d995a2e6b16e55 nsudoku.c) >>> pom1 (actual md5sum fbea72f26ab9f1771e8171021406b194 pom1-1.0.0.tar.gz) >>> redeclipse (actual md5sum f12b05a32ad1f6e0cb4e83e53cc286b7 redeclipse_1.5.1_nix.tar.bz2) >>> yahtzee (actual md5sum bc4a7f2339bcb642681ad16366737e1d yahtzee-1.5.tar.gz) >>> >>> graphics: >>> fim (actual md5sum 42b0a04c328b251ea7f06e4959a06d67 fim-0.5-trunk.tar.gz) >>> >>> libraries: >>> boolstuff (actual md5sum fc8397d732f696d9f5e371bab2fb2c14 boolstuff-0.1.14.tar.gz) >>> ioncube-loader (actual md5sum 28cb8b5668880b76c0a1d6371ba78774 ioncube_loaders_lin_x86-64.tar.bz2) >>> lua-zlib (actual md5sum 3ba445324203e4e0beb2bc1cd93c547a >>> c0014bcbc4c3fd65ba3519b10965f0c184c1a059.tar.gz) >>> >>> multimedia: >>> flvtool2 (actual md5sum a337832c4c30ae557968cf09419a130a flvtool2-1.0.6.tgz) >>> >>> python: >>> path.py (actual md5sum 8467fb5b1232678e63942ff870dedc59 7.6.tar.gz) >> All fixed in my branch > All of these need to be checked more carefully.. nsudoku is a version > bump and for flvtool2 the given sum (a33783..) matches what is basically a > 404 document. I did not check others. > > > > > _______________________________________________ > 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/ > rubyforge.org seems to have problem for the time... if enyone needs flvtool2 can find here the source with the same md5sum from flvtool2.info: http://attic-distfiles.pld-linux.org/by-md5/0/8/08e5f6f10c06903447d97d7ba10cec67/flvtool2-1.0.6.tgz -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Aug 24 11:55:22 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 24 Aug 2015 18:55:22 +0700 Subject: [Slackbuilds-users] md5sums In-Reply-To: <55DB0594.5070708@slackonly.com> References: <55DADC8B.5090801@slackonly.com> <55DAF1CF.8080503@slackbuilds.org> <55DAF44D.7030707@slackonly.com> <55DAF890.90003@slackbuilds.org> <20150824062157.3425f234@shaggy.doo> <55DB0594.5070708@slackonly.com> Message-ID: <55DB062A.5010802@slackbuilds.org> > rubyforge.org seems to have problem for the time... > if enyone needs flvtool2 can find here the source with the same md5sum > from flvtool2.info: > http://attic-distfiles.pld-linux.org/by-md5/0/8/08e5f6f10c06903447d97d7ba10cec67/flvtool2-1.0.6.tgz willysr at SBo64:~/slackbuilds/multimedia/flvtool2$ wget $DOWNLOAD --2015-08-24 18:53:42-- http://attic-distfiles.pld-linux.org/by-md5/0/8/08e5f6f10c06903447d97d7ba10cec67/flvtool2-1.0.6.tgz Resolving attic-distfiles.pld-linux.org (attic-distfiles.pld-linux.org)... 193.239.45.41 Connecting to attic-distfiles.pld-linux.org (attic-distfiles.pld-linux.org)|193.239.45.41|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 26953 (26K) [application/x-tgz] Saving to: ?flvtool2-1.0.6.tgz? 100%[===================================================================================================================>] 26,953 44.2KB/s in 0.6s 2015-08-24 18:53:51 (44.2 KB/s) - ?flvtool2-1.0.6.tgz? saved [26953/26953] willysr at SBo64:~/slackbuilds/multimedia/flvtool2$ md5sum flvtool2-1.0.6.tgz 08e5f6f10c06903447d97d7ba10cec67 flvtool2-1.0.6.tgz willysr at SBo64:~/slackbuilds/multimedia/flvtool2$ cat flvtool2.info PRGNAM="flvtool2" VERSION="1.0.6" HOMEPAGE="http://rubyforge.org/projects/flvtool2/" DOWNLOAD="http://attic-distfiles.pld-linux.org/by-md5/0/8/08e5f6f10c06903447d97d7ba10cec67/flvtool2-1.0.6.tgz" MD5SUM="a337832c4c30ae557968cf09419a130a" nope, it has different value -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Aug 24 13:09:19 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 24 Aug 2015 20:09:19 +0700 Subject: [Slackbuilds-users] md5sums In-Reply-To: <20150824062157.3425f234@shaggy.doo> References: <55DADC8B.5090801@slackonly.com> <55DAF1CF.8080503@slackbuilds.org> <55DAF44D.7030707@slackonly.com> <55DAF890.90003@slackbuilds.org> <20150824062157.3425f234@shaggy.doo> Message-ID: <55DB177F.1070906@slackbuilds.org> > All of these need to be checked more carefully.. nsudoku is a version > bump and for flvtool2 the given sum (a33783..) matches what is basically a > 404 document. I did not check others. already rechecked everything and some are reverted or changed -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lemelle at cbpf.br Tue Aug 25 14:37:47 2015 From: lemelle at cbpf.br (lemelle at cbpf.br) Date: Tue, 25 Aug 2015 11:37:47 -0300 Subject: [Slackbuilds-users] Sorry, but how i can receive this list e-mail per e-mail and not resume in day Message-ID: <20150825113747.Horde.3nAUTcCPne9V3H27NPOiUjA@p0m1.cat.cbpf.br> Thanks Diego From atelszewski at gmail.com Tue Aug 25 14:55:30 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 25 Aug 2015 16:55:30 +0200 Subject: [Slackbuilds-users] Sorry, but how i can receive this list e-mail per e-mail and not resume in day In-Reply-To: <20150825113747.Horde.3nAUTcCPne9V3H27NPOiUjA@p0m1.cat.cbpf.br> References: <20150825113747.Horde.3nAUTcCPne9V3H27NPOiUjA@p0m1.cat.cbpf.br> Message-ID: <55DC81E2.8000803@gmail.com> On 25/08/15 16:37, lemelle at cbpf.br wrote: > > Thanks > > Diego > _______________________________________________ > 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/ > > Go to mailing list settings and change 'Set Digest Mode' to off. -- Best regards, Andrzej Telszewski From ts at websafe.pl Thu Aug 27 11:12:59 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Thu, 27 Aug 2015 13:12:59 +0200 Subject: [Slackbuilds-users] remmina - wrong checksum? Message-ID: <55DEF0BB.901@websafe.pl> Hello, contains: ~~~~ DOWNLOAD="https://github.com/FreeRDP/Remmina/archive/v1.2.0-rcgit.1.tar.gz \ http://pkgs.fedoraproject.org/repo/pkgs/libssh/libssh-0.6.4.tar.gz/5d092f911492e3ee4cd7b473f09a0196/libssh-0.6.4.tar.gz" MD5SUM="bd92d1beb5c0c3acb6e32ad546e30d84 \ 5d092f911492e3ee4cd7b473f09a0196" ~~~~ but: ~~~~ wget https://github.com/FreeRDP/Remmina/archive/v1.2.0-rcgit.1.tar.gz md5sum v1.2.0-rcgit.1.tar.gz 7b5df647a9fb0be206cfabd273bc91f4 v1.2.0-rcgit.1.tar.gz ~~~~ -- Best regards, Thomas Szteliga https://github.com/websafe/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3712 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Thu Aug 27 13:16:14 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 27 Aug 2015 20:16:14 +0700 Subject: [Slackbuilds-users] remmina - wrong checksum? In-Reply-To: <55DEF0BB.901@websafe.pl> References: <55DEF0BB.901@websafe.pl> Message-ID: <55DF0D9E.6060503@slackbuilds.org> > wget https://github.com/FreeRDP/Remmina/archive/v1.2.0-rcgit.1.tar.gz > > md5sum v1.2.0-rcgit.1.tar.gz > > 7b5df647a9fb0be206cfabd273bc91f4 v1.2.0-rcgit.1.tar.gz Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Thu Aug 27 16:19:14 2015 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 27 Aug 2015 17:19:14 +0100 Subject: [Slackbuilds-users] remmina - wrong checksum? In-Reply-To: <55DF0D9E.6060503@slackbuilds.org> References: <55DEF0BB.901@websafe.pl> <55DF0D9E.6060503@slackbuilds.org> Message-ID: Seeing as we mentioned remmina... the tarball extraction is broken, and there's a bashism too. (sorry for the nitpick) Cheers -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-network-remmina-Fixed-SlackBuild.patch Type: text/x-diff Size: 1229 bytes Desc: not available URL: From willysr at slackbuilds.org Thu Aug 27 16:40:26 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 27 Aug 2015 23:40:26 +0700 Subject: [Slackbuilds-users] remmina - wrong checksum? In-Reply-To: References: <55DEF0BB.901@websafe.pl> <55DF0D9E.6060503@slackbuilds.org> Message-ID: <55DF3D7A.40007@slackbuilds.org> > Seeing as we mentioned remmina... > the tarball extraction is broken, and there's a bashism too. > (sorry for the nitpick) Applied along with some more changes :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Thu Aug 27 16:45:18 2015 From: yalhcru at gmail.com (B Watson) Date: Thu, 27 Aug 2015 12:45:18 -0400 Subject: [Slackbuilds-users] bashisms? Message-ID: >From the remmina thread: On 8/27/15, David Spencer wrote: > Seeing as we mentioned remmina... > the tarball extraction is broken, and there's a bashism too. > (sorry for the nitpick) Are we supposed to be avoiding bashisms? I used to use bashisms, and put #!/bin/bash at the top of my slackbuilds. In every case, someone on the SBo team changed the shebang to #!/bin/sh but left the bashisms in place. I've been told in no uncertain terms that /bin/sh has always been bash on Slackware, and always will be... and I know that slackbuild scripts only ever have to run on installed Slackware systems (not from the busybox installer environment). Slackware itself uses bashisms in #!/bin/sh scripts: rc.S, rc.inet1, and /lib/dhcpcd/dhcpcd-run-hooks at least (though the dhcpcd one is shipped that way by upstream). So I quit worrying about it, and just use #!/bin/sh for all build scripts, but use bashisms whenever I feel like they make sense. If it's good enough for Pat, it's good enough for me. However, from time to time I see patches or git commits that "fix" scripts to get rid of bashisms. I am a bit confused. Have I been doin' it wrong all this time? From baildon.research at googlemail.com Thu Aug 27 18:07:15 2015 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 27 Aug 2015 19:07:15 +0100 Subject: [Slackbuilds-users] bashisms? In-Reply-To: References: Message-ID: > I used to use bashisms, and put #!/bin/bash at the top of my > slackbuilds. In every case, someone on the SBo team changed the shebang > to #!/bin/sh but left the bashisms in place. Me too - I used to use bashisms, and put #!/bin/bash at the top of my slackbuilds. In every case, someone on the SBo team has found a better way of doing it that didn't need bash. Since then, I've been vaguely following those examples -- I would welcome some more advice and guidance if it's offered -- but it won't keep me awake at night if we just agree that it's not very important :D -D. (I shared a short train journey with a zsh enthusiast yesterday; it was... difficult) From yalhcru at gmail.com Thu Aug 27 19:27:14 2015 From: yalhcru at gmail.com (B Watson) Date: Thu, 27 Aug 2015 15:27:14 -0400 Subject: [Slackbuilds-users] bashisms? In-Reply-To: References: Message-ID: On 8/27/15, David Spencer wrote: > In every case, someone on the SBo team has found a better > way of doing it that didn't need bash. Mine got their #!/bin/bash changed to #!/bin/sh, but their bashisms are still there. Maybe a few of them got changed (maybe even without me noticing), but I've got tons of TARVER=${VERSION/_/-} sort of constructs. > (I shared a short train journey with a zsh enthusiast yesterday; it > was... difficult) Can imagine. Though it's better than listening to other people talk about football or the weather. From didier at slint.fr Thu Aug 27 19:28:22 2015 From: didier at slint.fr (Didier Spaier) Date: Thu, 27 Aug 2015 21:28:22 +0200 Subject: [Slackbuilds-users] bashisms? In-Reply-To: References: Message-ID: <55DF64D6.7080802@slint.fr> On 27/08/2015 18:45, B Watson wrote: > Are we supposed to be avoiding bashisms? I don't know, but I tend to. We can't rule out that a folk running a SlackBuild have symlinked /bin/sh to /bin/ash, and replaced the #!/bin/sh shebang by #!/bin/bash in scripts that must run on bash (or even modified some Slackware scripts so that they run on a fully POSIX compliant shell. I seem to remember that someone have reported having done that on LQ). Else we should make very clear that /bin/sh must be a symlink to /bin/bash. Cheers, Didier From Jim.Diamond at acadiau.ca Fri Aug 28 11:25:55 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Fri, 28 Aug 2015 08:25:55 -0300 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <55DF64D6.7080802@slint.fr> References: <55DF64D6.7080802@slint.fr> Message-ID: <20150828112555.GC24396@jdiamond-nb2> On Thu, Aug 27, 2015 at 21:28 (+0200), Didier Spaier wrote: > On 27/08/2015 18:45, B Watson wrote: >> Are we supposed to be avoiding bashisms? > I don't know, but I tend to. > We can't rule out that a folk running a SlackBuild have symlinked /bin/sh > to /bin/ash, and replaced the #!/bin/sh shebang by #!/bin/bash in scripts > that must run on bash (or even modified some Slackware scripts so that > they run on a fully POSIX compliant shell. I seem to remember that > someone have reported having done that on LQ). > Else we should make very clear that /bin/sh must be a symlink to /bin/bash. I don't think that that should be a requirement. If some day Pat decides to use a faster, POSIX-complaint shell for /bin/sh, then there might be lots of breakage in SBo-land This can easily be prevented with a small bit of defensive programming (i.e., writing one's script to avoid bash-isms if that can be done "easily", and otherwise following good programming practices by explicitly declaring that the shell script must be run by bash if that is, indeed, the case). Cheers Jim From wgg2 at member.fsf.org Fri Aug 28 17:12:43 2015 From: wgg2 at member.fsf.org (William G Gardella) Date: Fri, 28 Aug 2015 17:12:43 +0000 Subject: [Slackbuilds-users] [PATCH] network/bitlbee: Correct "restart" in rc.bitlbee Message-ID: <87si738hh0.fsf@example.com> The included "restart" function of rc.bitlbee attempts to start bitlbee and then stop it, instead of stopping and then starting it. This patch corrects the problem. --- network/bitlbee/rc.bitlbee | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/network/bitlbee/rc.bitlbee b/network/bitlbee/rc.bitlbee index 5f0ef7a..ba5dbc9 100644 --- a/network/bitlbee/rc.bitlbee +++ b/network/bitlbee/rc.bitlbee @@ -59,9 +59,9 @@ case "$1" in bitlbee_stop ;; restart) - bitlbee_start - sleep 3 bitlbee_stop + sleep 3 + bitlbee_start ;; *) echo "Usage: $(basename $0) {start|stop|restart}" -- 2.5.0 From willysr at slackbuilds.org Fri Aug 28 23:33:08 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Aug 2015 06:33:08 +0700 Subject: [Slackbuilds-users] [PATCH] network/bitlbee: Correct "restart" in rc.bitlbee In-Reply-To: <87si738hh0.fsf@example.com> References: <87si738hh0.fsf@example.com> Message-ID: <55E0EFB4.8070803@slackbuilds.org> > The included "restart" function of rc.bitlbee attempts to start bitlbee > and then stop it, instead of stopping and then starting it. > This patch corrects the problem. > --- > network/bitlbee/rc.bitlbee | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/network/bitlbee/rc.bitlbee b/network/bitlbee/rc.bitlbee > index 5f0ef7a..ba5dbc9 100644 > --- a/network/bitlbee/rc.bitlbee > +++ b/network/bitlbee/rc.bitlbee > @@ -59,9 +59,9 @@ case "$1" in > bitlbee_stop > ;; > restart) > - bitlbee_start > - sleep 3 > bitlbee_stop > + sleep 3 > + bitlbee_start > ;; > *) > echo "Usage: $(basename $0) {start|stop|restart}" Fixed in my branch thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Aug 29 03:16:59 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Aug 2015 10:16:59 +0700 Subject: [Slackbuilds-users] Updates - 20150829.1 Message-ID: <55E1242B.4000409@slackbuilds.org> Sat Aug 29 03:08:16 UTC 2015 audio/minimodem: Updated for version 0.22. audio/qmmp-plugin-pack: Updated for version 0.8.6. audio/ttaenc: Added (TTA1 lossless audio encoder/decoder). audio/xmms-ctl: Added (CLI Controller for XMMS). desktop/gxkb: Updated for version 0.7.6. desktop/wmtimer: Update README. desktop/wmweather+: Update README. development/atom: Updated for version 1.0.7. development/avr8-burn-o-mat: Update MD5SUM. development/fuel: Updated for version 1.0.1. development/tiled-qt: Update MD5SUM. games/bastet: Update MD5SUM. games/bitfighter: Update DOWNLOAD url. games/chocolate_duke3D: Set permission. games/freeorion: Updated for version 0.4.5_rc1. games/pom1: Update MD5SUM. games/qstat: Updated for version 2daa7d27. games/redeclipse: Update MD5SUM. games/yahtzee: Update MD5SUM. gis/geos: Updated for version 3.5.0. graphics/fim: Update MD5SUM. graphics/gimp-plugin-bimp: Added (Batch Image Manipulation Plugin). graphics/qcad: Updated for version 3.9.8.0. libraries/SFML: Fix BUILD tag. libraries/boolstuff: Update MD5SUM. libraries/cffi: Updated for version 1.2.1. libraries/dropbox-python: Updated for version 3.14. libraries/http-parser: Updated for version 2.5.0. libraries/ioncube-loader: Update MD5SUM. libraries/jcal: Added (Jalali calender). libraries/libcec: Updated for version 3.0.1. libraries/libgit2: Updated for version 0.23.1. libraries/libuv: Updated for version 1.7.2. libraries/lua-zlib: Update MD5SUM. libraries/opensaml: Updated for version 2.5.5. libraries/platform: Added (support library). libraries/python-librtmp: Updated for version 0.3.0. libraries/xmltooling: Updated for version 1.5.6. misc/subsurface: Added patch for newer libgit2. multimedia/flvtool2: Update DOWNLOAD url. multimedia/kodi: Updated for version 15.1. multimedia/shotcut: Added (cross-platform video editor). multimedia/tvheadend: Added (PVR server). network/bitlbee: Fix restart command. network/freerapid: Fix compatibilities with new JDK. network/ftp-cloudfs: Updated for version 0.34. network/iojs: Downgraded to version 2.5.0. network/masscan: Added (Mass IP port scanner). network/palemoon: Fix symlink. network/pidgin-skypeweb: Updated for version 03ce2fa. network/purple-facebook: Updated for version 5727ffb502c7. network/remmina: Update MD5SUM. network/shibboleth-sp: Updated for version 2.5.5. network/vivaldi: Updated for version 1.0.252.3_1. network/wmnd: Update README. network/xdman: Added (download manager). network/youtube-dl: Updated for version 2015.08.23. office/libreoffice-helppack: Updated for version 5.0.1. office/libreoffice-langpack: Updated for version 5.0.1. office/libreoffice: Updated for version 5.0.1. perl/perl-Convert-BinHex: Updated for version 1.124. perl/perl-Crypt-OpenSSL-Bignum: Updated for version 0.06. perl/perl-Crypt-OpenSSL-Random: Updated for version 0.10. perl/perl-Date-Calc: Updated for version 6.4. perl/perl-IO-stringy: Updated for version 2.111. perl/perl-Image-Info: Updated for version 1.38. perl/perl-MIME-tools: Updated for version 5.506. perl/perl-Test-Pod: Updated for version 1.51. python/argcomplete: Updated for version 1.0.0. python/path.py: Update MD5SUM. python/python-augeas: Added (Python bindings for augeas). python/python-pyparted: Added (Python bindings for libparted). python/python3-augeas: Added (Python 3 bindings for augeas). python/python3-pyparted: Added (Python 3 bindings for libparted). system/Iosevka: Updated for version 0.1.7. system/augeas: Added (a configuration API). system/blocks: Added (Block Devices Conversion Tools). system/ddrescue-gui: Added (GUI for ddrescue). system/facter: Updated for version 3.0.2. system/lz4: Added (compression algorithm). system/maintboot: Added (runs commands outside of the current OS). system/parallel: Updated for version 20150822. system/pyarchey: Updated for version 0.6.2. system/slpkg: Updated for version 2.7.6. system/sysdig: Updated for version 0.1.103. system/tmuxp: Updated for version 0.9.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From andrew.david.strong at gmail.com Sat Aug 29 06:38:46 2015 From: andrew.david.strong at gmail.com (andrew) Date: Sat, 29 Aug 2015 16:38:46 +1000 Subject: [Slackbuilds-users] Updates - 20150829.1 In-Reply-To: <55E1242B.4000409@slackbuilds.org> References: <55E1242B.4000409@slackbuilds.org> Message-ID: <20150829063846.GA7524@ilium.andrews-corner.org> On Sat, Aug 29, 2015 at 10:16:59AM +0700, Willy Sudiarto Raharjo wrote: > Sat Aug 29 03:08:16 UTC 2015 [..] > audio/ttaenc: Added (TTA1 lossless audio encoder/decoder). This is more of a question for the maintainer but I am a little curious of the relationship between 'ttaenc': -------------------- TTA1 lossless audio encoder/decoder, release 3.4.1 Copyright (c) 2007 Aleksander Djuric. All rights reserved. ------------------ and 'tta' which is packaged for Slackbuilds.org: ------------------- TTA1 lossless audio encoder/decoder, version 2.3 ------------------ The version packaged for SBo has a lower version number but I believe comes from the same developer? And of course different names for the executable... Andrew -- You think that's air you're breathing now? From yalhcru at gmail.com Sat Aug 29 08:16:28 2015 From: yalhcru at gmail.com (B Watson) Date: Sat, 29 Aug 2015 04:16:28 -0400 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <20150828112555.GC24396@jdiamond-nb2> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> Message-ID: On 8/28/15, Jim Diamond wrote: > and otherwise following > good programming practices by explicitly declaring that the shell > script must be run by bash if that is, indeed, the case). I tried doing that, it got changed back to #!/bin/sh, so I just gave up. I don't use other shells normally, and haven't memorized the POSIX shell spec, so can't remember (and can't be bothered to forever be looking up) what's a bashism and what isn't. Horrible attitude maybe, but it is what it is, so I normally use #!/bin/bash to avoid confusion and breakage. I suppose if a forked or future Slackware someday has /bin/sh as non-bash, it'd be easy enough to sed the shebangs to #!/bin/bash on the entire SBo repo. Probably this whole discussion is a waste of time, I won't be offended or anything if nobody wants to reply to this. From didier at slint.fr Sat Aug 29 09:32:08 2015 From: didier at slint.fr (Didier Spaier) Date: Sat, 29 Aug 2015 11:32:08 +0200 Subject: [Slackbuilds-users] bashisms? In-Reply-To: References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> Message-ID: <55E17C18.5040003@slint.fr> On 29/08/2015 10:16, B Watson wrote: > On 8/28/15, Jim Diamond wrote: > >> and otherwise following >> good programming practices by explicitly declaring that the shell >> script must be run by bash if that is, indeed, the case). I fully agree to what Jim wrote. > > I tried doing that, it got changed back to #!/bin/sh, so I just gave up. Seeing how many SlackBuilds you contributed, I can understand your feeling. I am impressed. > I don't use other shells normally, and haven't memorized the POSIX shell > spec, so can't remember (and can't be bothered to forever be looking up) > what's a bashism and what isn't. For anyone reading, some stuff that may help. chechkbashims is provided here: http://slackbuilds.org/repository/14.1/development/checkbashisms/ See also: http://mywiki.wooledge.org/Bashism And of course bash --posix. Cheers, Didier From ozan.turkyilmaz at gmail.com Sat Aug 29 09:47:50 2015 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 29 Aug 2015 14:47:50 +0500 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <55E17C18.5040003@slint.fr> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <55E17C18.5040003@slint.fr> Message-ID: 2015-08-29 14:32 GMT+05:00 Didier Spaier : > On 29/08/2015 10:16, B Watson wrote: > For anyone reading, some stuff that may help. > > chechkbashims is provided here: > http://slackbuilds.org/repository/14.1/development/checkbashisms/ > See also: > http://mywiki.wooledge.org/Bashism > In general, I test my scripts with ash before submitting them. -- Ozan, BSc, BEng From willysr at slackbuilds.org Sat Aug 29 10:06:07 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Aug 2015 17:06:07 +0700 Subject: [Slackbuilds-users] Updates - 20150829.2 Message-ID: <55E1840F.40600@slackbuilds.org> Sat Aug 29 09:59:06 UTC 2015 network/filezilla: Revert slipped changes. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From Jim.Diamond at acadiau.ca Sat Aug 29 12:16:46 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 29 Aug 2015 09:16:46 -0300 Subject: [Slackbuilds-users] bashisms? In-Reply-To: References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> Message-ID: <20150829121646.GA12197@jdiamond-nb2> On Sat, Aug 29, 2015 at 04:16 (-0400), B Watson wrote: > On 8/28/15, Jim Diamond wrote: >> and otherwise following >> good programming practices by explicitly declaring that the shell >> script must be run by bash if that is, indeed, the case). > I tried doing that, it got changed back to #!/bin/sh, so I just gave up. I think changing that was unnecessary and ill-advised (unless the person who changed it verified there were no bash-isms at all). > I don't use other shells normally, and haven't memorized the POSIX shell > spec, Yeah, that is a job for someone with lots of time on their hands. > so can't remember (and can't be bothered to forever be looking up) > what's a bashism and what isn't. Horrible attitude maybe, but it is > what it is, so I normally use #!/bin/bash to avoid confusion and > breakage. > I suppose if a forked or future Slackware someday has /bin/sh as non-bash, > it'd be easy enough to sed the shebangs to #!/bin/bash on the entire SBo > repo. Well, this is, I believe, something which is also wrong in principle. I have this fuzzy recollection of some difference in the order of how parsing is done between bash and POSIX specs. I can't think of what it is now, but it was something along the lines of this difference between bash and zsh: bash (at least with the options I get when I run it): $ b='echo a' $ $b a zsh (at least with the options I get when I run it): $ b='echo a' $ $b zsh: command not found: echo a In other (very loosely-spoken) words, bash does word-splitting on the results of variable expansion before parsing the whole line, and zsh does not. So it is possible that changing someone's #!/bin/sh to #!/bin/bash could break the shell script. Of course, this could all be a moot point. Cheers. Jim From citizen.anon.x at gmail.com Sat Aug 29 13:11:56 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Sat, 29 Aug 2015 09:11:56 -0400 Subject: [Slackbuilds-users] gnome-media missing dependency Message-ID: While building gnome-media on Slackware 64 bit, the build failed due to missing dependency, libunique, which is not listed as a dependency. I built the dependency package and re-tried with success. http://slackbuilds.org/repository/14.1/libraries/gnome-media/?search=gnome-media -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Sat Aug 29 13:26:01 2015 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 29 Aug 2015 14:26:01 +0100 Subject: [Slackbuilds-users] gnome-media missing dependency In-Reply-To: References: Message-ID: > While building gnome-media on Slackware 64 bit, the build failed due to > missing dependency, libunique, which is not listed as a dependency. That's not true here: http://pastebin.com/6RCn3UfL -D. From yalhcru at gmail.com Sat Aug 29 15:25:48 2015 From: yalhcru at gmail.com (B Watson) Date: Sat, 29 Aug 2015 11:25:48 -0400 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <20150829121646.GA12197@jdiamond-nb2> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> Message-ID: On 8/29/15, Jim Diamond wrote: >> it'd be easy enough to sed the shebangs to #!/bin/bash > Well, this is, I believe, something which is also wrong in principle. In general, you're right. For the specific case of Slackbuilds, they're all already bash scripts (since /bin/sh is bash on Slack). If Slackware 15.0 suddenly starts using dash for /bin/sh, it's safe to change the shebang lines for SBo scripts to read #!/bin/bash. There are slight differences when bash is run as "sh" rather than "bash", but they only have to do with which startup files are read (see INVOCATION section in man page). > zsh (at least with the options I get when I run it): > $ b='echo a' > $ $b > zsh: command not found: echo a Interesting. Tried this with bash. Invoking it as sh or with the --posix flag doesn't change the way this works (it still echoes a, doesn't act like zsh). ash works like bash, for this case. So does ksh, and so does hsh (the Heirloom shell). Looks like zsh might be the odd man out here. From Jim.Diamond at acadiau.ca Sat Aug 29 16:20:37 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 29 Aug 2015 13:20:37 -0300 Subject: [Slackbuilds-users] bashisms? In-Reply-To: References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> Message-ID: <20150829162037.GA21308@jdiamond-nb2> On Sat, Aug 29, 2015 at 11:25 (-0400), B Watson wrote: > On 8/29/15, Jim Diamond wrote: >>> it'd be easy enough to sed the shebangs to #!/bin/bash >> Well, this is, I believe, something which is also wrong in principle. > In general, you're right. For the specific case of Slackbuilds, > they're all already bash scripts (since /bin/sh is bash on Slack). Well, yes and no. See below. > If Slackware 15.0 suddenly starts using dash for /bin/sh, it's safe > to change the shebang lines for SBo scripts to read #!/bin/bash. Maybe, maybe not. > There are slight differences when bash is run as "sh" rather than > "bash", but they only have to do with which startup files are read > (see INVOCATION section in man page). You are wrong on this last point (according to the bash man page). Aside from the startup files being different, there are other changes in behaviour when bash is invoked as /bin/sh. (Search the man page for all the sentences with "posix".) >> zsh (at least with the options I get when I run it): >> $ b='echo a' >> $ $b >> zsh: command not found: echo a > Interesting. Tried this with bash. Invoking it as sh or with the > --posix flag doesn't change the way this works (it still echoes a, > doesn't act like zsh). Indeed. This is annoying me, because I'm sure (99% sure?) that I fairly recently ran into something where bash's order for processing a command line is different than POSIX's order. In any case, http://www.gnu.org/software/bash/manual/bashref.html#Bash-POSIX-Mode lists 50 differences when bash is in POSIX mode. Admittedly, it is a different question whether any SBo contributors write slackbuilds which work in one mode and not the other. > ash works like bash, for this case. So does ksh, and so does hsh (the > Heirloom shell). Looks like zsh might be the odd man out here. It is (*), for better or for worse. There was an "argument" in comp.unix.shell not too long ago about this. The nice thing about this zsh behaviour is that you don't have to go around protecting variable expansion like "$var" all the time. I'd bet that it is more often the case that one does not want a variable expansion to be word split than for the expansion to be word split. (*) Well, not entirely: fish: ~> set a "echo b" ~> echo $a echo b ~> $a Variables may not be used as commands. In fish, please define a function or use 'eval a'. Cheers. Jim From hba.nihilismus at gmail.com Sat Aug 29 18:15:40 2015 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sat, 29 Aug 2015 13:15:40 -0500 Subject: [Slackbuilds-users] audio/ladspa_sdk: $DOWNLOAD returning 404 Message-ID: http://www.ladspa.org is not available so its sourcecode can not be downloaded any more. There is a copy in fedora repository [1] and its MD5 matches. - Cheers [1] http://pkgs.fedoraproject.org/repo/pkgs/ladspa/ladspa_sdk_1.13.tgz/671be3e1021d0722cadc7fb27054628e/ladspa_sdk_1.13.tgz -- Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Sat Aug 29 21:05:05 2015 From: yalhcru at gmail.com (B Watson) Date: Sat, 29 Aug 2015 17:05:05 -0400 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <20150829162037.GA21308@jdiamond-nb2> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> <20150829162037.GA21308@jdiamond-nb2> Message-ID: On 8/29/15, Jim Diamond wrote: >> There are slight differences when bash is run as "sh" rather than >> "bash", but they only have to do with which startup files are read >> (see INVOCATION section in man page). > > You are wrong on this last point (according to the bash man page). > Aside from the startup files being different, there are other changes > in behaviour when bash is invoked as /bin/sh. (Search the man page > for all the sentences with "posix".) I stand corrected, I missed the bit where it says posix mode gets enabled when run as sh. Probably the biggest thing I see there that influences SlackBuilds: | Subshells spawned to execute command substitutionsi [in posix mode] | inherit the value of the -e option from the parent shell. When not | in posix mode, bash clears the -e option in such subshells. But this shouldn't hurt working scripts. I remember a few years back when a lot of scripts that relied on subshells not inheriting -e suddenly had to be changed for a new bash version (presumably the one that introduced the -e inheritance). If they'd all had #!/bin/bash at the top, would they have needed to be changed? Sure would be nice if the bash manpage had a POSIX section that summarized all the differences between regular and posix mode. Sigh. Maybe I'll start back submitting new slackbuilds as #!/bin/bash and see if it sticks this time around. From willysr at slackbuilds.org Sun Aug 30 00:38:28 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 30 Aug 2015 07:38:28 +0700 Subject: [Slackbuilds-users] audio/ladspa_sdk: $DOWNLOAD returning 404 In-Reply-To: References: Message-ID: <55E25084.3050505@slackbuilds.org> > http://www.ladspa.org is not available so its sourcecode can not be > downloaded any more. There is a copy in fedora repository [1] and its MD5 > matches. Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Aug 30 03:40:52 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 30 Aug 2015 10:40:52 +0700 Subject: [Slackbuilds-users] Updates - 20150829.1 In-Reply-To: <20150829063846.GA7524@ilium.andrews-corner.org> References: <55E1242B.4000409@slackbuilds.org> <20150829063846.GA7524@ilium.andrews-corner.org> Message-ID: <55E27B44.9030106@slackbuilds.org> > This is more of a question for the maintainer but I am a little > curious of the relationship between 'ttaenc': > > -------------------- > TTA1 lossless audio encoder/decoder, release 3.4.1 > Copyright (c) 2007 Aleksander Djuric. All rights reserved. > ------------------ > > and 'tta' which is packaged for Slackbuilds.org: > > ------------------- > TTA1 lossless audio encoder/decoder, version 2.3 > ------------------ > > The version packaged for SBo has a lower version number but I believe > comes from the same developer? And of course different names for the > executable... Where did you get the 3.4.1 source? i checked the website and it still point to 2.3 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From andrew.david.strong at gmail.com Sun Aug 30 04:51:06 2015 From: andrew.david.strong at gmail.com (andrew) Date: Sun, 30 Aug 2015 14:51:06 +1000 Subject: [Slackbuilds-users] Updates - 20150829.1 In-Reply-To: <55E27B44.9030106@slackbuilds.org> References: <55E1242B.4000409@slackbuilds.org> <20150829063846.GA7524@ilium.andrews-corner.org> <55E27B44.9030106@slackbuilds.org> Message-ID: <20150830045106.GA28725@ilium.andrews-corner.org> On Sun, Aug 30, 2015 at 10:40:52AM +0700, Willy Sudiarto Raharjo wrote: > Where did you get the 3.4.1 source? > i checked the website and it still point to 2.3 This certainly appears to be the most modern download. The 3.4.1 source is advertised here: http://en.true-audio.com/TTA_CLI_encoder_version_3.4.1 I suspect the developer has discontinued the 3.4.1 stream and made the more modern builds a lower build number but I am only guessing. My special interest is that I have just added True Audio support to the commandline cd ripper abcde: http://git.einval.com/cgi-bin/gitweb.cgi?p=abcde.git;a=summary and I have had to juggle two cli encoders :(. Andrew -- You think that's air you're breathing now? From willysr at slackbuilds.org Sun Aug 30 05:49:23 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 30 Aug 2015 12:49:23 +0700 Subject: [Slackbuilds-users] Updates - 20150829.1 In-Reply-To: <20150830045106.GA28725@ilium.andrews-corner.org> References: <55E1242B.4000409@slackbuilds.org> <20150829063846.GA7524@ilium.andrews-corner.org> <55E27B44.9030106@slackbuilds.org> <20150830045106.GA28725@ilium.andrews-corner.org> Message-ID: <55E29963.5030904@slackbuilds.org> > This certainly appears to be the most modern download. The 3.4.1 > source is advertised here: > > http://en.true-audio.com/TTA_CLI_encoder_version_3.4.1 > > I suspect the developer has discontinued the 3.4.1 stream and made the > more modern builds a lower build number but I am only guessing. My > special interest is that I have just added True Audio support to the > commandline cd ripper abcde: Perhaps you can submit to the maintainer? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From andrew.david.strong at gmail.com Sun Aug 30 07:03:46 2015 From: andrew.david.strong at gmail.com (andrew) Date: Sun, 30 Aug 2015 17:03:46 +1000 Subject: [Slackbuilds-users] Updates - 20150829.1 In-Reply-To: <55E29963.5030904@slackbuilds.org> References: <55E1242B.4000409@slackbuilds.org> <20150829063846.GA7524@ilium.andrews-corner.org> <55E27B44.9030106@slackbuilds.org> <20150830045106.GA28725@ilium.andrews-corner.org> <55E29963.5030904@slackbuilds.org> Message-ID: <20150830070346.GA29124@ilium.andrews-corner.org> On Sun, Aug 30, 2015 at 12:49:23PM +0700, Willy Sudiarto Raharjo wrote: > Perhaps you can submit to the maintainer? Should not be needed because when I found out there was a newer version available I made the SBo version (tta) the default and the older version also available from configuration file... Andrew -- You think that's air you're breathing now? From arkadiusz at drabczyk.org Sun Aug 30 16:54:40 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sun, 30 Aug 2015 18:54:40 +0200 Subject: [Slackbuilds-users] network/chromium fails to build on x64 and binds with obsolete Python Message-ID: <20150830165440.GA2655@comp.lan> The following error occurs when building chromium on Slackware 14.1 x64: Updating projects from gyp files... gyp: Call to '../build/linux/python_arch.sh /usr/lib/libpython2.6.so.1.0' returned exit status 1. while trying to load build/all.gyp The reason for this is that `system_libdir' build variable is set to `lib' in build/common.gypi: # The system libdir used for this ABI. 'system_libdir%': 'lib', On Slackware x64 it should be set to `lib64'. But even when `system_libdir' is changed chromium still fails to build because it tries to bind with an obsolete version of Python - it's looking for Python 2.6 but it should be looking for Python 2.7. Altogether, the following change must be applied to chromium.SlackBuild in order to build chromium successfully on Slackware x64: --- /var/lib/sbopkg/SBo/14.1/network/chromium/chromium.SlackBuild 2013-11-24 20:23:52.000000000 +0100 +++ /var/lib/sbopkg/SBo/14.1/network/chromium/chromium.SlackBuild.sbopkg 2015-08-29 22:39:32.70868417 @@ -114,6 +114,8 @@ -Duse_system_yasm=1 \ -Ddisable_nacl=1 \ -Drelease_extra_cflags="$CFLAGS" \ + -Dsystem_libdir=lib64 \ + -Dpython_ver=2.7 \ -- Arkadiusz Drabczyk From oda at member.fsf.org Sun Aug 30 11:13:39 2015 From: oda at member.fsf.org (Oda) Date: Sun, 30 Aug 2015 08:13:39 -0300 Subject: [Slackbuilds-users] network/chromium fails to build on x64 and binds with obsolete Python In-Reply-To: <20150830165440.GA2655@comp.lan> References: <20150830165440.GA2655@comp.lan> Message-ID: Hi, I used to build chromium with this slackbuild, but now I'm using the Alien's package, you should give it a try: http://www.slackware.com/~alien/slackbuilds/chromium/ Abs, -- Oda ------------------------------------------------------ If you don't have time to do it right, where are you going to find the time to do it over? ------------------------------------------------------ On Sun, Aug 30, 2015 at 1:54 PM, Arkadiusz Drabczyk wrote: > The following error occurs when building chromium on Slackware 14.1 > x64: > > Updating projects from gyp files... > gyp: Call to '../build/linux/python_arch.sh /usr/lib/libpython2.6.so.1.0' returned exit status 1. while trying to load build/all.gyp > > The reason for this is that `system_libdir' build variable is set to > `lib' in build/common.gypi: > > # The system libdir used for this ABI. > 'system_libdir%': 'lib', > > On Slackware x64 it should be set to `lib64'. But even when > `system_libdir' is changed chromium still fails to build because it > tries to bind with an obsolete version of Python - it's looking for > Python 2.6 but it should be looking for Python 2.7. Altogether, the > following change must be applied to chromium.SlackBuild in order to > build chromium successfully on Slackware x64: > > --- /var/lib/sbopkg/SBo/14.1/network/chromium/chromium.SlackBuild 2013-11-24 20:23:52.000000000 +0100 > +++ /var/lib/sbopkg/SBo/14.1/network/chromium/chromium.SlackBuild.sbopkg 2015-08-29 22:39:32.70868417 > @@ -114,6 +114,8 @@ > -Duse_system_yasm=1 \ > -Ddisable_nacl=1 \ > -Drelease_extra_cflags="$CFLAGS" \ > + -Dsystem_libdir=lib64 \ > + -Dpython_ver=2.7 \ > > > -- > Arkadiusz Drabczyk > _______________________________________________ > 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 arkadiusz at drabczyk.org Sun Aug 30 13:06:09 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sun, 30 Aug 2015 15:06:09 +0200 Subject: [Slackbuilds-users] network/chromium fails to build on x64 and binds with obsolete Python In-Reply-To: References: <20150830165440.GA2655@comp.lan> Message-ID: <28E72E00-42E6-4052-9173-46C964AC5CFA@drabczyk.org> On August 30, 2015 1:13:39 PM CEST, Oda wrote: >Hi, I used to build chromium with this slackbuild, but now I'm using >the Alien's package, you should give it a try: >http://www.slackware.com/~alien/slackbuilds/chromium/ Maybe next time when I will need chromium. I think that version on slackbuilds should be fixed or removed. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From edps.mundognu at gmail.com Sun Aug 30 17:08:21 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Sun, 30 Aug 2015 14:08:21 -0300 Subject: [Slackbuilds-users] Updates - 20150829.1 Message-ID: If approved, i can submit (already tested) the SlackBuild to use: http://sourceforge.net/projects/tta/files/tta/ttaenc-src/ttaenc-3.4.1-src.tgz instead of: http://sourceforge.net/projects/tta/files/tta/libtta++/libtta-cpp-2.3.tar.gz With source of libtta-cpp-2.3, we can provide (or not) a new package called libtta, it will provide the libtta++ and encoder "tta". Using ttaenc-3.4.1-src.tgz, the present SlackBuild will provide the enconder "ttaenc", the same name of package, solving the mess. Both (tta and ttaenc) works similarly: http://hastebin.com/iyeyuritob Forgive me this little confusion, had not seen the downloadable version of ttaenc. From andrew.david.strong at gmail.com Sun Aug 30 19:38:06 2015 From: andrew.david.strong at gmail.com (andrew) Date: Mon, 31 Aug 2015 05:38:06 +1000 Subject: [Slackbuilds-users] Updates - 20150829.1 In-Reply-To: References: Message-ID: <20150830193806.GA1106@ilium.andrews-corner.org> On Sun, Aug 30, 2015 at 02:08:21PM -0300, Edinaldo wrote: > Using ttaenc-3.4.1-src.tgz, the present SlackBuild will provide the enconder > "ttaenc", the same name of package, solving the mess. > > Both (tta and ttaenc) works similarly: > > http://hastebin.com/iyeyuritob > > Forgive me this little confusion, had not seen the downloadable version of > ttaenc. Well, to tell the truth, it looks to me as if 'tta' 2.3 represents a newer version than 'ttaenc' 3.4.1 so IMHO it would be better to remain as is. Confusion definitely, but this comes from the development end rather than the SBo end. And forgive me for stirring up this confusion of versions :). Andrew -- You think that's air you're breathing now? From willysr at slackbuilds.org Mon Aug 31 04:05:23 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 31 Aug 2015 11:05:23 +0700 Subject: [Slackbuilds-users] early notice: opencv-3.0 Message-ID: <55E3D283.3060707@slackbuilds.org> The maintainer of opencv has pushed opencv 3.0 update today and since it's used by many other packages, please test this new update against your packages. AFAIK, it came with a IPP feature from Intel, but this feature can't be used in 32 bit unless we made it static libs. If we use shared libs, digikam will fail to fail to build during linking process. If we disabled IPP in opencv, digikam will loose it's face detection feature. I will probably put this under a different branch and wait for other's confirmation first before pushing it under my branch. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: