From genghiskhan at gmx.ca Mon Dec 1 13:02:39 2014 From: genghiskhan at gmx.ca (Genghis Khan) Date: Mon, 1 Dec 2014 14:02:39 +0100 Subject: [Slackbuilds-users] Error while installing package culmus Message-ID: I am using slapt-src with spkg under Salix OS. Slackware package /usr/src/slapt-src/system/culmus/culmus-0.130-noarch-1_SBo.txz created. Installing package culmus-0.130-noarch-1_SBo... | culmus (Hebrew scalable fonts) | | The Culmus project aims at providing the Hebrew-speaking | GNU/Linux and Unix community with a basic collection of | Hebrew fonts for X Windows. | | | for more info: http://culmus.sourceforge.net | | | | | ERROR: Package contains symlink with unsafe path. (/etc/fonts/conf.d/61-culmus.conf) ERROR: Installation script processing failed. ERROR: Package installation failed! /sbin/spkg -u --reinstall --install-new culmus-0.130-noarch-1_SBo.txz Failed From yalhcru at gmail.com Mon Dec 1 19:15:39 2014 From: yalhcru at gmail.com (B Watson) Date: Mon, 1 Dec 2014 14:15:39 -0500 Subject: [Slackbuilds-users] Error while installing package culmus In-Reply-To: References: Message-ID: On 12/1/14, Genghis Khan wrote: > I am using slapt-src with spkg under Salix OS. Salix, spkg, and slapt-src are all off-topic for this list. If you ask on a Salix mailing list, you'll probably get a much better answer. However, I'll give it a shot: > ERROR: Package contains symlink with unsafe path. > (/etc/fonts/conf.d/61-culmus.conf) > ERROR: Installation script processing failed. > ERROR: Package installation failed! > /sbin/spkg -u --reinstall --install-new culmus-0.130-noarch-1_SBo.txz > Failed The package's doinst.sh contains this as the last line: ( cd /etc/fonts/conf.d ; ln -sf ../conf.avail/61-culmus.conf 61-culmus.conf ) ...which is a perfectly normal thing for a font package to do. spkg seems to have some extra code to check for "dangerous" symlinks, and this symlink is triggering it. Possible solutions: 1. See if spkg has an option to disable the check (if it has a man page, that should tell you). 2. If Salix has Slackware's installpkg, use that instead of spkg. 3. Edit the doinst.sh script in the SlackBuild directory, get rid of the offending line. After package installation, manually create the symlink. From vlahavas at gmail.com Mon Dec 1 22:34:31 2014 From: vlahavas at gmail.com (George Vlahavas) Date: Tue, 2 Dec 2014 00:34:31 +0200 (EET) Subject: [Slackbuilds-users] Error while installing package culmus In-Reply-To: References: Message-ID: On Mon, 1 Dec 2014, B Watson wrote: > Salix, spkg, and slapt-src are all off-topic for this list. If you ask on > a Salix mailing list, you'll probably get a much better answer. > > However, I'll give it a shot: > >> ERROR: Package contains symlink with unsafe path. >> (/etc/fonts/conf.d/61-culmus.conf) >> ERROR: Installation script processing failed. >> ERROR: Package installation failed! >> /sbin/spkg -u --reinstall --install-new culmus-0.130-noarch-1_SBo.txz >> Failed > > The package's doinst.sh contains this as the last line: > > ( cd /etc/fonts/conf.d ; ln -sf ../conf.avail/61-culmus.conf 61-culmus.conf ) > > ...which is a perfectly normal thing for a font package to do. Actually, no. This is wrong and it will also fail to work with installpkg if it is used with the --root option. It needs to be changed to: ( cd etc/fonts/conf.d ; ln -sf ../conf.avail/61-culmus.conf 61-culmus.conf ) From yalhcru at gmail.com Mon Dec 1 22:46:01 2014 From: yalhcru at gmail.com (B Watson) Date: Mon, 1 Dec 2014 17:46:01 -0500 Subject: [Slackbuilds-users] Error while installing package culmus In-Reply-To: References: Message-ID: On 12/1/14, George Vlahavas wrote: > Actually, no. This is wrong and it will also fail to work with installpkg > if it is used with the --root option. It needs to be changed to: > > ( cd etc/fonts/conf.d ; ln -sf ../conf.avail/61-culmus.conf 61-culmus.conf > ) Good catch. I didn't even notice the leading slash in front of etc. Actually the whole doinst.sh is like that, it runs /usr/bin/mkfontdir instead of usr/bin/mkfontdir, etc etc. From vlahavas at gmail.com Mon Dec 1 22:59:27 2014 From: vlahavas at gmail.com (George Vlahavas) Date: Tue, 2 Dec 2014 00:59:27 +0200 (EET) Subject: [Slackbuilds-users] Error while installing package culmus In-Reply-To: References: Message-ID: On Mon, 1 Dec 2014, B Watson wrote: > On 12/1/14, George Vlahavas wrote: >> Actually, no. This is wrong and it will also fail to work with installpkg >> if it is used with the --root option. It needs to be changed to: >> >> ( cd etc/fonts/conf.d ; ln -sf ../conf.avail/61-culmus.conf 61-culmus.conf >> ) > > Good catch. I didn't even notice the leading slash in front of etc. > > Actually the whole doinst.sh is like that, it runs /usr/bin/mkfontdir > instead of usr/bin/mkfontdir, etc etc. I didn't see the doinst.sh at all, I only read the email. Moreover, if the symlink is only created in the doinst.sh, then it's also wrong. Symlinks should better be created in the SlackBuild itself and they will then be picked up automatically by makepkg. This way, when you removepkg the package, the symlink will be removed as well. As it is now (at least how I think it is), the symlink will not be removed and will be left dangling. Unless there is another reason to keep it like that which I'm not aware of of course. From gilcio.amaral at gmail.com Tue Dec 2 14:16:55 2014 From: gilcio.amaral at gmail.com (Gilcio Amaral-Martins) Date: Tue, 2 Dec 2014 12:16:55 -0200 Subject: [Slackbuilds-users] MasterPDFEditor Message-ID: When I open a PDF document I could not see any text, only frames. What's wrong? -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Dec 2 16:38:06 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 02 Dec 2014 23:38:06 +0700 Subject: [Slackbuilds-users] MasterPDFEditor In-Reply-To: References: Message-ID: <547DEAEE.60205@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > When I open a PDF document I could not see any text, only frames. > What's wrong? works fine here - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlR96u4ACgkQiHuDdNczM4FPUwCgnJU3pbXALvTpIUCUu/OkBCUl xOAAniygl4flWzpZ/R+aM3zbD6KCVbE3 =syiz -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: pdfeditor.png Type: image/png Size: 503324 bytes Desc: not available URL: From sbolokanov at abv.bg Tue Dec 2 16:48:53 2014 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Tue, 2 Dec 2014 18:48:53 +0200 (EET) Subject: [Slackbuilds-users] How to send updates for SlackBuilds? Message-ID: <1772504808.43599.1417538933208.JavaMail.apache@nm42.abv.bg> Hello, I have made some updates to 0ad and 0ad-data scripts. How should I send them? -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Dec 2 16:50:16 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 02 Dec 2014 23:50:16 +0700 Subject: [Slackbuilds-users] How to send updates for SlackBuilds? In-Reply-To: <1772504808.43599.1417538933208.JavaMail.apache@nm42.abv.bg> References: <1772504808.43599.1417538933208.JavaMail.apache@nm42.abv.bg> Message-ID: <547DEDC8.30303@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I have made some updates to 0ad and 0ad-data scripts. How should I > send them? 0ad and 0ad-data are maintained by Erik Hanson You should send your updates to him - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlR97cgACgkQiHuDdNczM4FhTwCff7p+Om/5w7+Yjr+RqZmbloF/ dbQAn18bTozFUtYQBId25DnquOXPcREh =mUYl -----END PGP SIGNATURE----- From chris at chrisn.me.uk Wed Dec 3 00:15:28 2014 From: chris at chrisn.me.uk (Chris Novakovic) Date: Wed, 03 Dec 2014 00:15:28 +0000 Subject: [Slackbuilds-users] Bugs in perl-template.SlackBuild Message-ID: <547E5620.3070201@chrisn.me.uk> Dear all, There are a few bugs in perl-template.SlackBuild that prevent some module distributions installing correctly, or at all. "Build method #1" uses makefiles generated by ExtUtils::MakeMaker [1] to drive the build process: perl Makefile.PL \ PREFIX=/usr \ INSTALLDIRS=vendor \ INSTALLVENDORMAN3DIR=/usr/man/man3 make make test make install DESTDIR=$PKG Module distributions that install system-wide scripts to /usr/bin have the man pages for those scripts installed to /usr/share/man/man1 because INSTALLVENDORMAN1DIR isn't set. The solution is to set INSTALLVENDORMAN1DIR=/usr/man/man1 after setting INSTALLDIRS. "Build method #2" uses Module::Build [2] to build and install the module distribution: perl Build.PL \ prefix=/usr \ installdirs=vendor \ destdir=$PKG ./Build ./Build test ./Build install \ --install_path bindoc=/usr/man/man1 \ --install_path libdoc=/usr/man/man3 There are two bugs here: - Options and values passed to Build.PL aren't meant to be delimited with = symbols, which leads to them being ignored; the default behaviour is to install to /usr/local (and in the main perl directory, not in the site or vendor subdirectories) and then to install directly to /usr/local when running `./Build install`, thus bypassing $PKG entirely. The solution is to replace the = symbols with spaces in the arguments to `perl Build.PL`. - The Module::Build cookbook [3] says that destdir should be passed to `./Build install` rather than `perl Build.PL`. destdir=$PKG should therefore move to `./Build install` and become --destdir $PKG. With all three of these changes, I've yet to see a Perl module that doesn't build and install correctly. Cheers, Chris [1] http://search.cpan.org/~bingos/ExtUtils-MakeMaker-7.04/lib/ExtUtils/MakeMaker.pm [2] http://search.cpan.org/~leont/Module-Build-0.4210/lib/Module/Build.pm [3] http://search.cpan.org/~leont/Module-Build-0.4210/lib/Module/Build/Cookbook.pm From lukenshiro at ngi.it Thu Dec 4 11:33:27 2014 From: lukenshiro at ngi.it (LukenShiro) Date: Thu, 4 Dec 2014 12:33:27 +0100 Subject: [Slackbuilds-users] autogen Message-ID: <20141204123327.20c19802@hamalayi.mnt> I've noticed autogen does not build if guile1.8 is installed, maybe it is advisable to mention it in README. Best regards. -- GNU/Linux * Slackware64 current * k3.17.4 LU #210970 SU #12583 LM #98222/#412913 From willysr at slackbuilds.org Thu Dec 4 11:39:30 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 04 Dec 2014 18:39:30 +0700 Subject: [Slackbuilds-users] autogen In-Reply-To: <20141204123327.20c19802@hamalayi.mnt> References: <20141204123327.20c19802@hamalayi.mnt> Message-ID: <548047F2.6070402@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I've noticed autogen does not build if guile1.8 is installed, maybe > it is advisable to mention it in README. done - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSAR/IACgkQiHuDdNczM4EThACfVOtW/66wOjZWuf0Nv+UtChk4 mIsAoKJdys6N9kuaWqUsZ712q45NGH4j =aJNP -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Dec 6 01:03:35 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 06 Dec 2014 08:03:35 +0700 Subject: [Slackbuilds-users] Updates - 20141206.1 Message-ID: <548255E7.5060805@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Dec 6 00:54:24 UTC 2014 academic/veusz: Added (Scientific Plotting). audio/hydrogen: Updated for version 0.9.5.1. audio/icecast: Updated for version 2.4.1 + new maintainer. audio/spandsp: Updated for version 0.0.6. desktop/9menu: Update email. desktop/lxappearance: Updated for version 0.6.1. desktop/mcwm: Update email. desktop/wmSun: Updated for version 1.11. desktop/wmSunMoon: Updated for version 1.11. development/autogen: Update README. development/google-webdesigner: Updated for version 1.1.3.1119. development/javacc: Updated for version 6.0. development/meld3: Updated for version 3.12.2. development/poedit: Updated for version 1.6.11. development/scite: Updated for version 3.52. development/smartgit: Updated for version 6.5.1. development/vala: Updated for version 0.26.0. games/fgo: Updated for version 1.5.5. games/scid_vs_pc: Updated for version 4.13. games/triplea: Updated for version 1.8.0.4. gis/Shapely: Updated for version 1.5.1. gis/postgis: Updated for version 2.1.4. gis/qgis: Updated for version 2.6.1. graphics/PyMOL: Updated for version 1.7.4.0. graphics/SweetHome3D: Updated for version 4.5. graphics/gifsicle: Updated for version 1.86. libraries/botocore: Updated for version 0.77.0. libraries/libg15: Update HOMEPAGE. libraries/libg15render: Update HOMEPAGE. libraries/libsidplayfp: Updated for version 1.6.1. libraries/liburcu: Updated for version 0.8.6. libraries/live555: Updated for version 2014.11.28. libraries/ogre: Fix output extension (tgz). libraries/yajl: Fix script. misc/g15composer: Update HOMEPAGE. misc/g15daemon: Update HOMEPAGE. misc/g15stats: Update HOMEPAGE. misc/ykpers: Updated for version 1.16.2. misc/yubikey-personalization-gui: Updated for version 3.1.18. multimedia/mpv: Updated for version 0.7.1. multimedia/plex-home-theater: Updated for version 1.3.0. network/Pafy: Update REQUIRES. network/awscli: Updated for version 1.6.6. network/dclib: Added (Neomodus DC library). network/dnscrypt-wrapper: Updated for version 0.1.14. network/flexget: Updated for version 1.2.230. network/geoipupdate: Added (GeoIP Updater). network/libmaxminddb: Added (C Library). network/pidgin-whatsapp: Updated for version 29112014. network/sipcalc: Added (IP Subnet Calculator). network/sphinx: Updated for version 2.2.6. network/synergy: Updated for version 1.6.2. network/teamviewer: Updated for version 10.0.36281. network/telegram: Added (messaging app). network/tnftp: Updated for version 20141104. network/tor-browser: Updated for version 4.0.2. network/valknut: Added (Neomodus DC library). network/vmware-view-client: Added (VMWare View Client). office/MasterPDFEditor: Updated for version 2.1.90. office/sofastats: Updated for version 1.4.3. perl/perl-Algorithm-Diff: Updated for version 1.1903. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.018. perl/perl-Geo-IP: Updated for version 1.45 + new maintainer. perl/perl-IO-Socket-IP: Added (Perl Module). perl/perl-MailTools: Updated for version 2.14. perl/perl-Test-Exception: Updated for version 0.35. python/bencode: Added (bittorrent module). python/binplist: Added (list parser module). python/construct: Added (python library). python/dpkt: Updated for version 1.8 + new maintainer. ruby/hub: Updated for version 1.12.3. system/ack: Updated for version 2.14, set ARCH=noarch. system/davfs2: Updated for version 1.5.2 + new maintainer. system/glances: Updated for version 2.1.2. system/intel-microcode: Added (Processor Microcode Data File). system/lxterminal: Updated for version 0.2.0. system/lzip: Updated for version 1.16. system/mlterm: Updated for version 3.4.1. system/netatop: Updated for version 0.4. system/slpkg: Updated for version 2.1.2. system/xarchiver: Updated for version 0.5.4. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSCVecACgkQiHuDdNczM4G4rACgrhRGHVBi9prOQg2YLXZLBkmG Me0AnjCSWJ8trXnTqVeLwhpI/w2Axuui =ZvxN -----END PGP SIGNATURE----- From andrew.david.strong at gmail.com Sun Dec 7 04:20:08 2014 From: andrew.david.strong at gmail.com (andrew) Date: Sun, 7 Dec 2014 15:20:08 +1100 Subject: [Slackbuilds-users] Orphaned: Leafnode 2 In-Reply-To: <20141129073726.GA1639@ilium.andrews-corner.org> References: <20141129073726.GA1639@ilium.andrews-corner.org> Message-ID: <20141207042008.GA8744@ilium.andrews-corner.org> On Sat, Nov 29, 2014 at 06:37:26PM +1100, andrew wrote: > I no longer use Leafnode 2 having finally settled in with slrnpull. > Is somebody interested in taking over care of this script? D'oh! I knew I was the only one using it :). Perhaps it should be quietly retired for 14.2... Andrew -- You think that's air you're breathing now? From rworkman at slackbuilds.org Sun Dec 7 06:38:35 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 7 Dec 2014 00:38:35 -0600 Subject: [Slackbuilds-users] Gajim Slackbuild In-Reply-To: <545224D3.4060704@slackbuilds.org> References: <20141029150710.4d4b93e2@kiwi> <5451ADFA.9020405@slackbuilds.org> <20141030113510.34bac8cf@kiwi> <545224D3.4060704@slackbuilds.org> Message-ID: <20141207003835.6f41a202@home.rlworkman.net> On Thu, 30 Oct 2014 18:45:23 +0700 Willy Sudiarto Raharjo wrote: > > But there's one more problem: gajim.SlackBuild misses a licence.. > > So, law-technically i can't simply insert the standard licence, and > > can't even change something in there (at least in germany). I can > > mail the original author about that, but any ideas how to handle > > that if he doesn't answer? Maybe i should just start fresh from a > > template. > > I don't think it will be a problem since it doesn't have any license > attached since the beginning. > What's problematic is if the author has put a strict license and > abandoned the script without any chance for other people to modify the > scripts. > > I'm not a lawyer, so i can be wrong. > > Robby? Eric? any thoughts? I've generally just made a new script based on the template in those cases - there were a few that went into Slackware proper on that same basis. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Dec 7 07:14:12 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 7 Dec 2014 01:14:12 -0600 Subject: [Slackbuilds-users] Error while installing package culmus In-Reply-To: References: Message-ID: <20141207011412.4a8d5a6e@home.rlworkman.net> On Mon, 1 Dec 2014 14:02:39 +0100 "Genghis Khan" wrote: > I am using slapt-src with spkg under Salix OS. > > > Slackware > package /usr/src/slapt-src/system/culmus/culmus-0.130-noarch-1_SBo.txz > created. > > Installing package culmus-0.130-noarch-1_SBo... > | culmus (Hebrew scalable fonts) > | > | The Culmus project aims at providing the Hebrew-speaking > | GNU/Linux and Unix community with a basic collection of > | Hebrew fonts for X Windows. > | > | > | for more info: http://culmus.sourceforge.net > | > | > | > | > | > ERROR: Package contains symlink with unsafe path. > (/etc/fonts/conf.d/61-culmus.conf) ERROR: Installation script > processing failed. ERROR: Package installation failed! > /sbin/spkg -u --reinstall --install-new culmus-0.130-noarch-1_SBo.txz > Failed _______________________________________________ Good catch. Fixed in this commit, slated for next public update: commit d8b2310bae83a1a18748335de00e49fd8eb9ae03 Author: Robby Workman Date: Sun Dec 7 01:12:02 2014 -0600 system/culmus: Fix font installation and doinst.sh paths Signed-off-by: Robby Workman -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Dec 7 07:15:15 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 7 Dec 2014 01:15:15 -0600 Subject: [Slackbuilds-users] Orphaned: Leafnode 2 In-Reply-To: <20141207042008.GA8744@ilium.andrews-corner.org> References: <20141129073726.GA1639@ilium.andrews-corner.org> <20141207042008.GA8744@ilium.andrews-corner.org> Message-ID: <20141207011515.398ebef9@home.rlworkman.net> On Sun, 7 Dec 2014 15:20:08 +1100 andrew wrote: > On Sat, Nov 29, 2014 at 06:37:26PM +1100, andrew wrote: > > > I no longer use Leafnode 2 having finally settled in with slrnpull. > > Is somebody interested in taking over care of this script? > > D'oh! I knew I was the only one using it :). Perhaps it should be > quietly retired for 14.2... Actually, we use it on harrier, as it's perfect for what we want. If nobody picks it up, I will for 14.2. :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Dec 7 07:16:28 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 7 Dec 2014 01:16:28 -0600 Subject: [Slackbuilds-users] Bugs in perl-template.SlackBuild In-Reply-To: <547E5620.3070201@chrisn.me.uk> References: <547E5620.3070201@chrisn.me.uk> Message-ID: <20141207011628.3c459345@home.rlworkman.net> On Wed, 03 Dec 2014 00:15:28 +0000 Chris Novakovic wrote: > Dear all, > > There are a few bugs in perl-template.SlackBuild that prevent some > module distributions installing correctly, or at all. > > "Build method #1" uses makefiles generated by ExtUtils::MakeMaker [1] > to drive the build process: > > perl Makefile.PL \ > PREFIX=/usr \ > INSTALLDIRS=vendor \ > INSTALLVENDORMAN3DIR=/usr/man/man3 > make > make test > make install DESTDIR=$PKG > > Module distributions that install system-wide scripts to /usr/bin have > the man pages for those scripts installed to /usr/share/man/man1 > because INSTALLVENDORMAN1DIR isn't set. The solution is to set > INSTALLVENDORMAN1DIR=/usr/man/man1 after setting INSTALLDIRS. > > "Build method #2" uses Module::Build [2] to build and install the > module distribution: > > perl Build.PL \ > prefix=/usr \ > installdirs=vendor \ > destdir=$PKG > ./Build > ./Build test > ./Build install \ > --install_path bindoc=/usr/man/man1 \ > --install_path libdoc=/usr/man/man3 > > There are two bugs here: > > - Options and values passed to Build.PL aren't meant to be delimited > with = symbols, which leads to them being ignored; the default > behaviour is to install to /usr/local (and in the main perl > directory, not in the site or vendor subdirectories) and then to > install directly to /usr/local when running `./Build install`, thus > bypassing $PKG entirely. The solution is to replace the = symbols > with spaces in the arguments to `perl Build.PL`. > > - The Module::Build cookbook [3] says that destdir should be passed to > `./Build install` rather than `perl Build.PL`. destdir=$PKG should > therefore move to `./Build install` and become --destdir $PKG. > > With all three of these changes, I've yet to see a Perl module that > doesn't build and install correctly. > > Cheers, > Chris > > [1] > http://search.cpan.org/~bingos/ExtUtils-MakeMaker-7.04/lib/ExtUtils/MakeMaker.pm > [2] > http://search.cpan.org/~leont/Module-Build-0.4210/lib/Module/Build.pm > [3] > http://search.cpan.org/~leont/Module-Build-0.4210/lib/Module/Build/Cookbook.pm If you will send me a patch against the current template, we'll get it merged. Thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From andrew.david.strong at gmail.com Sun Dec 7 07:24:29 2014 From: andrew.david.strong at gmail.com (andrew) Date: Sun, 7 Dec 2014 18:24:29 +1100 Subject: [Slackbuilds-users] Orphaned: Leafnode 2 In-Reply-To: <20141207011515.398ebef9@home.rlworkman.net> References: <20141129073726.GA1639@ilium.andrews-corner.org> <20141207042008.GA8744@ilium.andrews-corner.org> <20141207011515.398ebef9@home.rlworkman.net> Message-ID: <20141207072429.GA9545@ilium.andrews-corner.org> On Sun, Dec 07, 2014 at 01:15:15AM -0600, Robby Workman wrote: > Actually, we use it on harrier, as it's perfect for what we want. > If nobody picks it up, I will for 14.2. :-) Great news :) Andrew -- You think that's air you're breathing now? From bocke at mycity.rs Sun Dec 7 14:03:28 2014 From: bocke at mycity.rs (Bojan Popovic) Date: Sun, 7 Dec 2014 15:03:28 +0100 Subject: [Slackbuilds-users] Baires and trayer_srg up for adoption In-Reply-To: <548255E7.5060805@slackbuilds.org> References: <548255E7.5060805@slackbuilds.org> Message-ID: <20141207150328.508d53b0@artwo.universe.uni> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, I have a little plea for admins. I would like to orphan two packages: baires and trayer_srg. I'm not using them or following their development anymore. If anyone is, they are free to adopt them. Just a note: Baires homepage is down, but if anyone uses it and have a backup source tarball, they can still maintain it if they wish. Cheers, Bojan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUhF4wAAoJEBOUH7bZ9xhe2xAP/0IxVyMPNOMiSHRO7plnipDL OhvChrwi0iHINiMeXWIpMOdzwPEykM2+ebX8xOdv7ye3XOSfhYMW90KHVDuSUxqs 5ua7mHdgbh+yB/lyAkLLFI0HQwMiVfRKqhKnlmWzrqcluJDjQVa8UkCgidEdmnxq LDu7oeLj91njKZx0imv5YEs4UqP/1GwOAese6WIUogM5btUI8DkeRYcpEzefaP3t nW5/JWyyGmZZ1boRN7gaI/0fKt0TUmYjikzKwfGS4oY8mYT3cIYk3A+X0F9MbNGw s7a8be0BN8eBGc+0KTcgIGiwUr+2fOkciy8UAZ7Kyxo/zjp175T7SdiYv7nenYMA 4xEuxLFJoolTXlmnDqasMKteGmNESPr9WUOjScNsDXomJcBGOdQh5+guTUqYeSNQ VzbklJZngl1lk7PA+YDZn3Q7yRtFOisXvy4lASR4Kmkg3ZainMwyBhdY2KcCxqYD yNuaKby0hO1FCwHImHhUK3vhO2zk1SBKqTIbifuQrpWf6j+vjgsnIrQIL2PDm0Uz /9qyH4bKy4dwXK21rpSnmBrj7HSm14N4oqG419yC4usrSgu/fA7p35JuEnEPY9Ox UTgyXmnvZfvjD6CLA6SpmHsweRXy7oFzrepdBSIqP7ZhlzJgSIXH/7+HiRzB96L2 gDMpQvG84BExzp5RqR07 =Xwn3 -----END PGP SIGNATURE----- From enigma77 at gmx.net Sun Dec 7 17:11:03 2014 From: enigma77 at gmx.net (enigma) Date: Sun, 07 Dec 2014 18:11:03 +0100 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) Message-ID: <4597111.3qqFLkqWIH@slackware> I try to install fontforge (20141014) manually from the console, but also via sbopkg. In both cases I got the error message: make[2]: Leaving directory `/tmp/SBo/fontforge-20141014/Unicode' Making install in gutils make[2]: Entering directory `/tmp/SBo/fontforge-20141014/gutils' make[3]: Entering directory `/tmp/SBo/fontforge-20141014/gutils' /bin/mkdir -p '/tmp/SBo/package-fontforge/usr/lib64' /bin/sh ../libtool --mode=install /bin/ginstall -c libgutils.la libgioftp.la '/tmp/SBo/package-fontforge/usr/lib64' libtool: install: warning: relinking `libgutils.la' libtool: install: (cd /tmp/SBo/fontforge-20141014/gutils; /bin/sh /tmp/SBo/fontforge-20141014/libtool --silent --tag CC --mode=relink gcc -std=gnu99 -std=gnu99 -O2 -fPIC -Wl,--no-undefined -I/tmp/SBo/freetype-2.4.10/src/truetype -I/tmp/SBo/freetype-2.4.10/include -I/tmp/SBo/freetype-2.4.10/include/freetype -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -pthread -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/libdrm -I/usr/include/freetype2 -I/usr/include/libxml2 -I/usr/include/python2.7 -pthread -version-info 2:0:0 -no-undefined -o libgutils.la -rpath /usr/lib64 libgutils_la-divisors.lo libgutils_la-dlist.lo libgutils_la-fsys.lo libgutils_la-g_giomime.lo libgutils_la-gcol.lo libgutils_la-gimage.lo libgutils_la-gimageread.lo libgutils_la-gimagereadbmp.lo libgutils_la-gimagereadgif.lo libgutils_la-gimagereadjpeg.lo libgutils_la-gimagereadpng.lo libgutils_la-gimagereadras.lo libgutils_la-gimagereadrgb.lo libgutils_la-gimagereadtiff.lo libgutils_la-gimagereadxbm.lo libgutils_la-gimagereadxpm.lo libgutils_la-gimagewritebmp.lo libgutils_la-gimagewritegimage.lo libgutils_la-gimagewritejpeg.lo libgutils_la-gimagewritepng.lo libgutils_la-gimagewritexbm.lo libgutils_la-gimagewritexpm.lo libgutils_la-gio.lo libgutils_la-giofile.lo libgutils_la-giohosts.lo libgutils_la-giothread.lo libgutils_la-giotrans.lo libgutils_la-gnetwork.lo libgutils_la-gutils.lo libgutils_la-gwwintl.lo libgutils_la-prefs.lo libgutils_la-unicodelibinfo.lo -lpython2.7 -lgif -ljpeg -lpng -ltiff -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lglib-2.0 -lpangoxft-1.0 -lpangoft2-1.0 -lXft -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lSM -lICE -lreadline -ltermcap -lpython2.7 -lfreetype -lz -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lxml2 ../Unicode/libgunicode.la ../lib/libgnu.la -lX11 -lm -lltdl -ldl -inst-prefix-dir /tmp/SBo/package-fontforge) .libs/libgutils_la-gimage.o: In function `GImageCreate': gimage.c:(.text+0x131): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimage.o: In function `_GImage_Create': gimage.c:(.text+0x251): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimage.o: In function `GImageCreateAnimation': gimage.c:(.text+0x41c): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimage.o: In function `GImageAddImageBefore': gimage.c:(.text+0x6a6): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimagereadbmp.o: In function `GImageRead_Bmp': gimagereadbmp.c:(.text+0x915): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimagereadbmp.o:gimagereadbmp.c:(.text+0x1553): more undefined references to `NoMoreMemMessage' follow collect2: error: ld returned 1 exit status libtool: install: error: relink `libgutils.la' with the above command before installing it make[3]: *** [install-libLTLIBRARIES] Fehler 1 make[3]: Leaving directory `/tmp/SBo/fontforge-20141014/gutils' make[2]: *** [install-am] Fehler 2 make[2]: Leaving directory `/tmp/SBo/fontforge-20141014/gutils' make[1]: *** [install-recursive] Fehler 1 make[1]: Leaving directory `/tmp/SBo/fontforge-20141014' make: *** [install] Fehler 2 fontforge: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: My OS: Slackware64 14.1 (multilib-installation). Kernel vmlinuz changed from Huge to Generic ; but System.map and config both linked on huge (dont know why, maybe i should it also linked to generic(?) Window-Manager: Openbox Type of Installation: FULL (Over 7,? GB on Harddisk) Current fontforge: fontforge-20120731_b-x86_64-1_SBo (install and run without problems) Would be nice if someone knows a solution for my problem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvogel4 at stny.rr.com Mon Dec 8 05:41:49 2014 From: jvogel4 at stny.rr.com (John Vogel) Date: Mon, 8 Dec 2014 00:41:49 -0500 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <4597111.3qqFLkqWIH@slackware> References: <4597111.3qqFLkqWIH@slackware> Message-ID: <20141208004149.53487a0d@stygian.lan> On Sun, 07 Dec 2014 18:11:03 +0100 enigma wrote: > > > I try to install fontforge (20141014) manually from the console, but also via sbopkg. > In both cases I got the error message: > > make[2]: Leaving directory `/tmp/SBo/fontforge-20141014/Unicode' > Making install in gutils > make[2]: Entering directory `/tmp/SBo/fontforge-20141014/gutils' > make[3]: Entering directory `/tmp/SBo/fontforge-20141014/gutils' > /bin/mkdir -p '/tmp/SBo/package-fontforge/usr/lib64' > /bin/sh ../libtool --mode=install /bin/ginstall -c libgutils.la > libgioftp.la '/tmp/SBo/package-fontforge/usr/lib64' > libtool: install: warning: relinking `libgutils.la' > libtool: install: (cd /tmp/SBo/fontforge-20141014/gutils; /bin/sh > /tmp/SBo/fontforge-20141014/libtool --silent --tag CC --mode=relink gcc > -std=gnu99 -std=gnu99 -O2 -fPIC -Wl,--no-undefined > -I/tmp/SBo/freetype-2.4.10/src/truetype -I/tmp/SBo/freetype-2.4.10/include > -I/tmp/SBo/freetype-2.4.10/include/freetype -pthread -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/harfbuzz > -I/usr/include/freetype2 -pthread -I/usr/include/pango-1.0 > -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 > -I/usr/include/libdrm -I/usr/include/freetype2 -I/usr/include/libxml2 > -I/usr/include/python2.7 -pthread -version-info 2:0:0 -no-undefined -o > libgutils.la -rpath /usr/lib64 libgutils_la-divisors.lo libgutils_la-dlist.lo > libgutils_la-fsys.lo libgutils_la-g_giomime.lo libgutils_la-gcol.lo > libgutils_la-gimage.lo libgutils_la-gimageread.lo > libgutils_la-gimagereadbmp.lo libgutils_la-gimagereadgif.lo > libgutils_la-gimagereadjpeg.lo libgutils_la-gimagereadpng.lo > libgutils_la-gimagereadras.lo libgutils_la-gimagereadrgb.lo > libgutils_la-gimagereadtiff.lo libgutils_la-gimagereadxbm.lo > libgutils_la-gimagereadxpm.lo libgutils_la-gimagewritebmp.lo > libgutils_la-gimagewritegimage.lo libgutils_la-gimagewritejpeg.lo > libgutils_la-gimagewritepng.lo libgutils_la-gimagewritexbm.lo > libgutils_la-gimagewritexpm.lo libgutils_la-gio.lo libgutils_la-giofile.lo > libgutils_la-giohosts.lo libgutils_la-giothread.lo libgutils_la-giotrans.lo > libgutils_la-gnetwork.lo libgutils_la-gutils.lo libgutils_la-gwwintl.lo > libgutils_la-prefs.lo libgutils_la-unicodelibinfo.lo -lpython2.7 -lgif -ljpeg > -lpng -ltiff -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lglib-2.0 > -lpangoxft-1.0 -lpangoft2-1.0 -lXft -lpango-1.0 -lfreetype -lfontconfig > -lgobject-2.0 -lglib-2.0 -lSM -lICE -lreadline -ltermcap -lpython2.7 > -lfreetype -lz -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lxml2 > ../Unicode/libgunicode.la ../lib/libgnu.la -lX11 -lm -lltdl -ldl > -inst-prefix-dir /tmp/SBo/package-fontforge) > .libs/libgutils_la-gimage.o: In function `GImageCreate': > gimage.c:(.text+0x131): undefined reference to `NoMoreMemMessage' > .libs/libgutils_la-gimage.o: In function `_GImage_Create': > gimage.c:(.text+0x251): undefined reference to `NoMoreMemMessage' > .libs/libgutils_la-gimage.o: In function `GImageCreateAnimation': > gimage.c:(.text+0x41c): undefined reference to `NoMoreMemMessage' > .libs/libgutils_la-gimage.o: In function `GImageAddImageBefore': > gimage.c:(.text+0x6a6): undefined reference to `NoMoreMemMessage' > .libs/libgutils_la-gimagereadbmp.o: In function `GImageRead_Bmp': > gimagereadbmp.c:(.text+0x915): undefined reference to `NoMoreMemMessage' > .libs/libgutils_la-gimagereadbmp.o:gimagereadbmp.c:(.text+0x1553): more > undefined references to `NoMoreMemMessage' follow > collect2: error: ld returned 1 exit status > libtool: install: error: relink `libgutils.la' with the above command before > installing it > make[3]: *** [install-libLTLIBRARIES] Fehler 1 > make[3]: Leaving directory `/tmp/SBo/fontforge-20141014/gutils' > make[2]: *** [install-am] Fehler 2 > make[2]: Leaving directory `/tmp/SBo/fontforge-20141014/gutils' > make[1]: *** [install-recursive] Fehler 1 > make[1]: Leaving directory `/tmp/SBo/fontforge-20141014' > make: *** [install] Fehler 2 > > fontforge: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: > > > My OS: Slackware64 14.1 (multilib-installation). > Kernel vmlinuz changed from Huge to Generic ; but System.map and config both linked on huge (dont know why, maybe i should it also linked to generic(?) > Window-Manager: Openbox > Type of Installation: FULL (Over 7,? GB on Harddisk) > Current fontforge: fontforge-20120731_b-x86_64-1_SBo (install and run without problems) > > > > Would be nice if someone knows a solution for my problem. > Looks the same as this issue: https://github.com/fontforge/fontforge/issues/352 From enigma77 at gmx.net Mon Dec 8 09:15:35 2014 From: enigma77 at gmx.net (enigma) Date: Mon, 08 Dec 2014 10:15:35 +0100 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <20141208004149.53487a0d@stygian.lan> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> Message-ID: <15415336.FJRy4CrBc9@slackware> > Looks the same as this issue: https://github.com/fontforge/fontforge/issues/352 > > _______________________________________________ > 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 make following changes: $ tar -xvzf fontforge-20141014.tar.gz $ vim fontforge-20141014/libfontforge.pc [...] Version: 2.0.20140101 Requires: Requires.private: python-2.7 cairo pango zlib Libs: -L${exec_prefix}/lib -lfontforge ### ---------> changed to: Libs: -L${exec_prefix}/lib -lfontforge -lgunicode Libs.private: -lgioftp -lgutils -lgunicode -lgif -ljpeg -lpng -ltiff -lspiro -luninameslist -lreadline -lSM -lICE -lltdl -lX11 -lm -lltdl -ldl Cflags: -I${includedir}/fontforge $ vim fontforge-20141014/m4/fontforge_create_pkg_config_files.m4 [...] __pkg_deps="${__pkg_deps} zlib" __private_deps="" __private_deps="${__private_deps} -lgioftp" __private_deps="${__private_deps} -lgutils" __private_deps="${__private_deps} -lgunicode" ### This line was removed test x"${i_do_have_giflib}" = xyes && test x"${with_giflib}" != xno && __private_deps="${__private_deps} ${GIFLIB_LIBS}" [...] AC_SUBST([LIBFONTFORGEEXE_PKGCONFIG_VERSION],["${__cleaned_version}"]) AC_SUBST([LIBFONTFORGEEXE_PKGCONFIG_REQUIRES],[]) AC_SUBST([LIBFONTFORGEEXE_PKGCONFIG_REQUIRES_PRIVATE],["libfontforge ${__pkg_deps}"]) AC_SUBST([LIBFONTFORGEEXE_PKGCONFIG_LIBS],["-L${libdir} -lfontforgeexe"]) ### changed to: AC_SUBST([LIBFONTFORGEEXE_PKGCONFIG_LIBS],["-L${libdir} -lfontforgeexe -lgunicode"]) AC_SUBST([LIBFONTFORGEEXE_PKGCONFIG_LIBS_PRIVATE],["-L${libdir} ${__private_exe_deps} ${__private_deps}"]) AC_CONFIG_FILES([libfontforge.pc]) AC_CONFIG_FILES([libfontforgeexe.pc]) ]) $ tar -cvzf fontforge-20141014.tar.gz fontforge20141014 And then try to Build and install with this package, but i still get errors: make[2]: Leaving directory `/tmp/SBo/fontforge-20141014/Unicode' Making install in gutils make[2]: Entering directory `/tmp/SBo/fontforge-20141014/gutils' make[3]: Entering directory `/tmp/SBo/fontforge-20141014/gutils' /bin/mkdir -p '/tmp/SBo/package-fontforge/usr/lib64' /bin/sh ../libtool --mode=install /bin/ginstall -c libgutils.la libgioftp.la '/tmp/SBo/package-fontforge/usr/lib64' libtool: install: warning: relinking `libgutils.la' libtool: install: (cd /tmp/SBo/fontforge-20141014/gutils; /bin/sh /tmp/SBo/fontforge-20141014/libtool --silent --tag CC --mode=relink gcc -std=gnu99 -std=gnu99 -O2 -fPIC -Wl,--no-undefined -I/tmp/SBo/freetype-2.4.10/src/truetype -I/tmp/SBo/freetype-2.4.10/include -I/tmp/SBo/freetype-2.4.10/include/freetype - pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -pthread -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 - I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/libdrm -I/usr/include/freetype2 -I/usr/include/libxml2 -I/usr/include/python2.7 -pthread -version-info 2:0:0 -no-undefined -o libgutils.la -rpath /usr/lib64 libgutils_la-divisors.lo libgutils_la-dlist.lo libgutils_la-fsys.lo libgutils_la-g_giomime.lo libgutils_la-gcol.lo libgutils_la-gimage.lo libgutils_la-gimageread.lo libgutils_la-gimagereadbmp.lo libgutils_la-gimagereadgif.lo libgutils_la-gimagereadjpeg.lo libgutils_la-gimagereadpng.lo libgutils_la-gimagereadras.lo libgutils_la-gimagereadrgb.lo libgutils_la-gimagereadtiff.lo libgutils_la-gimagereadxbm.lo libgutils_la- gimagereadxpm.lo libgutils_la-gimagewritebmp.lo libgutils_la-gimagewritegimage.lo libgutils_la-gimagewritejpeg.lo libgutils_la-gimagewritepng.lo libgutils_la-gimagewritexbm.lo libgutils_la-gimagewritexpm.lo libgutils_la-gio.lo libgutils_la-giofile.lo libgutils_la-giohosts.lo libgutils_la-giothread.lo libgutils_la-giotrans.lo libgutils_la-gnetwork.lo libgutils_la-gutils.lo libgutils_la-gwwintl.lo libgutils_la-prefs.lo libgutils_la-unicodelibinfo.lo -lpython2.7 -lgif -ljpeg -lpng -ltiff -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lglib-2.0 -lpangoxft-1.0 -lpangoft2-1.0 -lXft -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lSM -lICE -lreadline - ltermcap -lpython2.7 -lfreetype -lz -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lxml2 ../Unicode/libgunicode.la ../lib/libgnu.la -lX11 -lm -lltdl -ldl -inst-prefix-dir /tmp/SBo/package-fontforge) .libs/libgutils_la-gimage.o: In function `GImageCreate': gimage.c:(.text+0x131): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimage.o: In function `_GImage_Create': gimage.c:(.text+0x251): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimage.o: In function `GImageCreateAnimation': gimage.c:(.text+0x41c): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimage.o: In function `GImageAddImageBefore': gimage.c:(.text+0x6a6): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimagereadbmp.o: In function `GImageRead_Bmp': gimagereadbmp.c:(.text+0x915): undefined reference to `NoMoreMemMessage' .libs/libgutils_la-gimagereadbmp.o:gimagereadbmp.c:(.text+0x1553): more undefined references to `NoMoreMemMessage' follow collect2: error: ld returned 1 exit status libtool: install: error: relink `libgutils.la' with the above command before installing it make[3]: *** [install-libLTLIBRARIES] Fehler 1 make[3]: Leaving directory `/tmp/SBo/fontforge-20141014/gutils' make[2]: *** [install-am] Fehler 2 make[2]: Leaving directory `/tmp/SBo/fontforge-20141014/gutils' make[1]: *** [install-recursive] Fehler 1 make[1]: Leaving directory `/tmp/SBo/fontforge-20141014' make: *** [install] Fehler 2 I hope the presentation in other email clients will not be distorted by the line-breaks. Does anyone have a solution? -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Mon Dec 8 19:11:07 2014 From: yalhcru at gmail.com (B Watson) Date: Mon, 8 Dec 2014 14:11:07 -0500 Subject: [Slackbuilds-users] Baires and trayer_srg up for adoption In-Reply-To: <20141207150328.508d53b0@artwo.universe.uni> References: <548255E7.5060805@slackbuilds.org> <20141207150328.508d53b0@artwo.universe.uni> Message-ID: On 12/7/14, Bojan Popovic wrote: > I have a little plea for admins. I would like to orphan two packages: > baires and trayer_srg. I'm not using them or following their > development anymore. If anyone is, they are free to adopt them. I'll take them, unless someone else wants them badly. baires looks like something I might use someday (if I ever own a camera again), and trayer-srg is similar to peksystray, which I'm maintainer of already. > Just a note: Baires homepage is down, but if anyone uses it and have a > backup source tarball, they can still maintain it if they wish. archive.org to the rescue! From jvogel4 at stny.rr.com Mon Dec 8 21:32:11 2014 From: jvogel4 at stny.rr.com (John Vogel) Date: Mon, 8 Dec 2014 16:32:11 -0500 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <15415336.FJRy4CrBc9@slackware> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> Message-ID: <20141208163211.042960e9@stygian.lan> > > I hope the presentation in other email clients will not be distorted by the line-breaks. > Does anyone have a solution? I just successfully built fontforge package here. Can't reproduce same issue on my system. I used freetype from 14.0 for one build and freetype from 14.1 for another... both built fine. After I send this, I will fire up a pristine vm of slackware-14.1 and try to reproduce on that. I'm just grasping at straws here, but I wonder if your system is multilib? John From jvogel4 at stny.rr.com Mon Dec 8 22:07:01 2014 From: jvogel4 at stny.rr.com (John Vogel) Date: Mon, 8 Dec 2014 17:07:01 -0500 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <15415336.FJRy4CrBc9@slackware> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> Message-ID: <20141208170701.7487dc9a@stygian.lan> On Mon, 08 Dec 2014 10:15:35 +0100 enigma wrote: > Does anyone have a solution? On pristine virtual machine of slackware64-14.1, fontforge builds fine. I would need more information in order to help further: what arch, stock packages changed or removed, more complete log of build, things like that.. I corrupted my master image of my slackware-14.1 (32bit) vm, so I could setup a new one and test on that if you are on 32 bit arch, but I would only have time for that if you confirm that you have 32 bit arch. John From chris.willing at iinet.net.au Mon Dec 8 22:20:40 2014 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 09 Dec 2014 08:20:40 +1000 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <20141208170701.7487dc9a@stygian.lan> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> <20141208170701.7487dc9a@stygian.lan> Message-ID: <54862438.7020909@iinet.net.au> On 12/09/2014 08:07 AM, John Vogel wrote: > On Mon, 08 Dec 2014 10:15:35 +0100 > enigma wrote: > >> Does anyone have a solution? > > On pristine virtual machine of slackware64-14.1, fontforge builds fine. I would > need more information in order to help further: what arch, stock packages > changed or removed, more complete log of build, things like that.. I corrupted > my master image of my slackware-14.1 (32bit) vm, so I could setup a new one > and test on that if you are on 32 bit arch, but I would only have time for that > if you confirm that you have 32 bit arch. From OP's original email: My OS: Slackware64 14.1 (multilib-installation). From jvogel4 at stny.rr.com Tue Dec 9 00:52:50 2014 From: jvogel4 at stny.rr.com (John Vogel) Date: Mon, 8 Dec 2014 19:52:50 -0500 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <54862438.7020909@iinet.net.au> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> <20141208170701.7487dc9a@stygian.lan> <54862438.7020909@iinet.net.au> Message-ID: <20141208195250.1bd5c1d1@stygian.lan> On Tue, 09 Dec 2014 08:20:40 +1000 Christoph Willing wrote: > > From OP's original email: > My OS: Slackware64 14.1 (multilib-installation). Thanks for setting me straight. Apologies all around for wasting everyones time. From chris.willing at iinet.net.au Tue Dec 9 01:43:38 2014 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 09 Dec 2014 11:43:38 +1000 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <20141208195250.1bd5c1d1@stygian.lan> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> <20141208170701.7487dc9a@stygian.lan> <54862438.7020909@iinet.net.au> <20141208195250.1bd5c1d1@stygian.lan> Message-ID: <548653CA.20501@iinet.net.au> On 12/09/2014 10:52 AM, John Vogel wrote: > On Tue, 09 Dec 2014 08:20:40 +1000 > Christoph Willing wrote: >> >> From OP's original email: >> My OS: Slackware64 14.1 (multilib-installation). > > Thanks for setting me straight. Apologies all around for wasting everyones > time. Well, I just successfully built with latest fontforge.SlackBuild on a 14.1-multilib partition that I have for testing. Thats not particularly helpful in diagnosing/fixing the OP's problem apart from pointing to some deeper problem - something beyond being on a multilib system. chris From elyk03 at gmail.com Tue Dec 9 07:22:08 2014 From: elyk03 at gmail.com (Kyle Guinn) Date: Tue, 9 Dec 2014 01:22:08 -0600 Subject: [Slackbuilds-users] Call for testing: BLAS/LAPACK Message-ID: Hi all, I have updated the blas and lapack Slackbuilds to version 3.5.0 in my user/elyk/lapack branch. I know these are dependencies of several other packages and I would appreciate any feedback if you maintain any packages that don't actually work with it. I've built octave and it seems to be OK. http://slackbuilds.org/cgit/slackbuilds/log/?h=user/elyk/lapack Two important changes: 1. Upstream has added cmake as a build system. This makes it easier to build a shared library, and I'd like confirmation that this library still works for everyone. Note that they set the SONAME to lib(blas|lapack).so, not lib(blas|lapack).so.3 as we manually did in the script previously. 2. lapack should auto-detect between blas and atlas, preferring atlas if it's installed. I believe this removes the need for a separate lapack-atlas Slackbuild, but I'll leave that for Serban to decide. It does not detect OpenBLAS; that package provides its own LAPACK implementation. Thanks in advance! -Kyle From enigma77 at gmx.net Tue Dec 9 09:35:08 2014 From: enigma77 at gmx.net (enigma) Date: Tue, 09 Dec 2014 10:35:08 +0100 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <548653CA.20501@iinet.net.au> References: <4597111.3qqFLkqWIH@slackware> <20141208195250.1bd5c1d1@stygian.lan> <548653CA.20501@iinet.net.au> Message-ID: <2035381.Evyg14pB9l@slackware> > Am Dienstag, 9. Dezember 2014, 11:43:38 schrieb Christoph Willing: > > Well, I just successfully built with latest fontforge.SlackBuild on a > 14.1-multilib partition that I have for testing. Thats not particularly > helpful in diagnosing/fixing the OP's problem apart from pointing to > some deeper problem - something beyond being on a multilib system. > > chris The same error-message appears on the PC of my wife (also slackware64 14.1 multilb-installation). But in two virtualbox-machines slackware64 14.1 (without multilib) installations, it has been done correctly. > Am Montag, 8. Dezember 2014, 11:23:04 schrieb Panagiotis Nikolaou: > Hi! > If you interesting only for the package and not for a solution > you can download the latest version here: > https://slackonly.com/pub/packages/14.1-x86_64/graphics/fontforge/ Thank you, this would solve my problem for now. However, I am curious about the cause of my problem. Now more than ever, because it worked in the virtualbox. Here more Information about my multilib-installation: $ ll /var/log/packages/gcc* -rw-r--r-- 1 root root 25K Dez 6 21:31 /var/log/packages/gcc-4.8.2_multilib-x86_64-1alien -rw-r--r-- 1 root root 40K Dez 6 21:31 /var/log/packages/gcc-g++-4.8.2_multilib-x86_64-1alien -rw-r--r-- 1 root root 2,3K Dez 6 21:31 /var/log/packages/gcc-gfortran-4.8.2_multilib-x86_64-1alien -rw-r--r-- 1 root root 245K Dez 6 21:31 /var/log/packages/gcc-gnat-4.8.2_multilib-x86_64-1alien -rw-r--r-- 1 root root 20K Dez 6 21:31 /var/log/packages/gcc-go-4.8.2_multilib-x86_64-1alien -rw-r--r-- 1 root root 231K Dez 6 21:31 /var/log/packages/gcc-java-4.8.2_multilib-x86_64-1alien -rw-r--r-- 1 root root 2,2K Dez 6 21:31 /var/log/packages/gcc-objc-4.8.2_multilib-x86_64-1alien -rw-r--r-- 1 root root 661 Jan 6 2014 /var/log/packages/gccmakedep-1.0.2-noarch-2 $ ll /var/log/packages/glib* -rw-r--r-- 1 root root 1,5K Jan 6 2014 /var/log/packages/glib-1.2.10-x86_64-3 -rw-r--r-- 1 root root 7,8K Jan 6 2014 /var/log/packages/glib-networking-2.36.2-x86_64-1 -rw-r--r-- 1 root root 44K Jan 6 2014 /var/log/packages/glib2-2.36.4-x86_64-1 -rw-r--r-- 1 root root 1,9K Jan 26 2014 /var/log/packages/glib2-compat32-2.36.4-x86_64-1compat32 -rw-r--r-- 1 root root 559K Dez 6 21:32 /var/log/packages/glibc-2.17_multilib-x86_64-9alien -rw-r--r-- 1 root root 463K Dez 6 21:32 /var/log/packages/glibc-i18n-2.17_multilib-x86_64-9alien -rw-r--r-- 1 root root 1,3K Dez 6 21:32 /var/log/packages/glibc-profile-2.17_multilib-x86_64-9alien -rw-r--r-- 1 root root 16K Dez 6 21:32 /var/log/packages/glibc-solibs-2.17_multilib-x86_64-9alien -rw-r--r-- 1 root root 69K Dez 6 21:32 /var/log/packages/glibc-zoneinfo-2014i_multilib-noarch-9alien $ ll /var/log/packages/compat32-tools* -rw-r--r-- 1 root root 984 Dez 6 21:30 /var/log/packages/compat32-tools-3.4-noarch-1alien And although the slackbuild already give a downloadable freetype-Link, there is already installed another one on my System: # slackpkg search freetype [ installed ] - freetype-2.5.0.1-x86_64-1 $ ll /var/log/packages/freetype-compyat* -rw-r--r-- 1 root root 1,2K Jan 26 2014 /var/log/packages/freetype-compat32-2.5.0.1-x86_64-1compat32 maybe there are conflicts between these versions?? (i think not, but i must ask) At the Moment i dont know, which configuration files/informations could be important. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Diamond at acadiau.ca Tue Dec 9 12:35:27 2014 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Tue, 9 Dec 2014 08:35:27 -0400 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <548653CA.20501@iinet.net.au> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> <20141208170701.7487dc9a@stygian.lan> <54862438.7020909@iinet.net.au> <20141208195250.1bd5c1d1@stygian.lan> <548653CA.20501@iinet.net.au> Message-ID: <20141209123527.GA24676@jdiamond-nb> On Tue, Dec 9, 2014 at 11:43 (+1000), Christoph Willing wrote: > On 12/09/2014 10:52 AM, John Vogel wrote: >>On Tue, 09 Dec 2014 08:20:40 +1000 >>Christoph Willing wrote: >>> From OP's original email: >>> My OS: Slackware64 14.1 (multilib-installation). >>Thanks for setting me straight. Apologies all around for wasting everyones >>time. > Well, I just successfully built with latest fontforge.SlackBuild on a > 14.1-multilib partition that I have for testing. Thats not particularly > helpful in diagnosing/fixing the OP's problem apart from pointing to some > deeper problem - something beyond being on a multilib system. FWIW, I am able to build it in a 64-bit only version of 14.1, but on a multilib system it crashes and burns with the same issue as in the original posting. Does your multilib system have a lot of SBo packages? Perhaps there is some interaction between some package(s) that the OP and I have installed. If anyone is keen to do some binary search looking to see when fontforge stops compiling, I'd be happy to supply the list of packages I have on my system. (But I can't do that myself any time in the near future.) Cheers. Jim From bocke at mycity.rs Tue Dec 9 19:15:43 2014 From: bocke at mycity.rs (Bojan Popovic) Date: Tue, 9 Dec 2014 20:15:43 +0100 Subject: [Slackbuilds-users] Baires and trayer_srg up for adoption In-Reply-To: References: <548255E7.5060805@slackbuilds.org> <20141207150328.508d53b0@artwo.universe.uni> Message-ID: <20141209201543.70ef3290@artwo.universe.uni> Hi, On Mon, 8 Dec 2014 14:11:07 -0500 B Watson wrote: > I'll take them, unless someone else wants them badly. Thanx Brian. :) Cheers, Bojan. From vmj at linuxbox.fi Tue Dec 9 19:48:07 2014 From: vmj at linuxbox.fi (Mikko Varri) Date: Tue, 9 Dec 2014 21:48:07 +0200 Subject: [Slackbuilds-users] perl/perl-AnyEvent(-Handle)? In-Reply-To: <20141102170548.GJ2202@linuxbox.fi> References: <20141102170548.GJ2202@linuxbox.fi> Message-ID: <20141209194807.GA31842@linuxbox.fi> On Sun, Nov 02, 2014 at 07:05:48PM +0200, Mikko Varri wrote: > > I was about to add a perl-AnyEvent.SlackBuild, but by chance noticed > that perl-AnyEvent-Handle.SlackBuild already installs the whole > AnyEvent distibution. AnyEvent::Handle is just one module of that > distribution. > > So, I'd suggest renaming the SlackBuild. If you agree, you can review > (and pull) the commits from > > https://github.com/vmj/slackbuilds/compare/perl-AnyEvent > > It's been over a month now with no reply (I sent a reminder to maintainer a week ago). I think it is safe to adopt the SlackBuild? -vmj From chris.willing at iinet.net.au Tue Dec 9 23:28:27 2014 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 10 Dec 2014 09:28:27 +1000 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <20141209123527.GA24676@jdiamond-nb> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> <20141208170701.7487dc9a@stygian.lan> <54862438.7020909@iinet.net.au> <20141208195250.1bd5c1d1@stygian.lan> <548653CA.20501@iinet.net.au> <20141209123527.GA24676@jdiamond-nb> Message-ID: <5487859B.4000900@iinet.net.au> On 12/09/2014 10:35 PM, Jim Diamond wrote: > On Tue, Dec 9, 2014 at 11:43 (+1000), Christoph Willing wrote: > > > >> On 12/09/2014 10:52 AM, John Vogel wrote: >>> On Tue, 09 Dec 2014 08:20:40 +1000 >>> Christoph Willing wrote: > >>>> From OP's original email: >>>> My OS: Slackware64 14.1 (multilib-installation). > >>> Thanks for setting me straight. Apologies all around for wasting everyones >>> time. > >> Well, I just successfully built with latest fontforge.SlackBuild on a >> 14.1-multilib partition that I have for testing. Thats not particularly >> helpful in diagnosing/fixing the OP's problem apart from pointing to some >> deeper problem - something beyond being on a multilib system. > > FWIW, I am able to build it in a 64-bit only version of 14.1, but on a > multilib system it crashes and burns with the same issue as in the > original posting. > > Does your multilib system have a lot of SBo packages? Perhaps there > is some interaction between some package(s) that the OP and I have > installed. If anyone is keen to do some binary search looking to see > when fontforge stops compiling, I'd be happy to supply the list of > packages I have on my system. (But I can't do that myself any time in > the near future.) Yes, the multilib that I built fontforge on had quite a few extra packages - it had been my regular system until I started tracking -current - so had become a little crufty. However I did also find another more recent multilib partition that I'd made to test something special - it had far fewer extra packages. The fontforge build was OK on that system too. Using the date fields from 'ls -l /var/log/packages', I removed all packages installed after the initial installation of base multilib packages i.e. the system now has been returned to a base multilib system. Again the build of fontforge completed OK. Maybe multilib can be implicated in the fontforge build failures but I think there's some other factor involved too. chris From willysr at slackbuilds.org Wed Dec 10 00:10:47 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 10 Dec 2014 07:10:47 +0700 Subject: [Slackbuilds-users] perl/perl-AnyEvent(-Handle)? In-Reply-To: <20141209194807.GA31842@linuxbox.fi> References: <20141102170548.GJ2202@linuxbox.fi> <20141209194807.GA31842@linuxbox.fi> Message-ID: <54878F87.3090508@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > It's been over a month now with no reply (I sent a reminder to > maintainer a week ago). > > I think it is safe to adopt the SlackBuild? Yes, go ahead - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSHj4cACgkQiHuDdNczM4HSDwCfa5BSkOJR2oLCYi7qy2i1o0Rm De0An2Gzykv7fUlbAM3hIiA159qM2ioy =zzhK -----END PGP SIGNATURE----- From elyk03 at gmail.com Wed Dec 10 05:17:18 2014 From: elyk03 at gmail.com (Kyle Guinn) Date: Tue, 9 Dec 2014 23:17:18 -0600 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <5487859B.4000900@iinet.net.au> References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> <20141208170701.7487dc9a@stygian.lan> <54862438.7020909@iinet.net.au> <20141208195250.1bd5c1d1@stygian.lan> <548653CA.20501@iinet.net.au> <20141209123527.GA24676@jdiamond-nb> <5487859B.4000900@iinet.net.au> Message-ID: On 12/9/14, Christoph Willing wrote: > Maybe multilib can be implicated in the fontforge build failures but I > think there's some other factor involved too. I tried building it about a week ago or so, got what I believe is the same error. It's on a 64-bit machine, but that machine is not and has never been multilib. Must be a conflict with some other package. I haven't had time to narrow it down yet. Just a hunch, maybe it's conflicting with an older version of fontforge? -Kyle From klaatu at straightedgelinux.com Wed Dec 10 06:48:36 2014 From: klaatu at straightedgelinux.com (Klaatu) Date: Wed, 10 Dec 2014 19:48:36 +1300 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> <20141208170701.7487dc9a@stygian.lan> <54862438.7020909@iinet.net.au> <20141208195250.1bd5c1d1@stygian.lan> <548653CA.20501@iinet.net.au> <20141209123527.GA24676@jdiamond-nb> <5487859B.4000900@iinet.net.au> Message-ID: <5487ECC4.1060908@straightedgelinux.com> On 12/10/2014 06:17 PM, Kyle Guinn wrote: > On 12/9/14, Christoph Willing wrote: >> Maybe multilib can be implicated in the fontforge build failures but I >> think there's some other factor involved too. > > I tried building it about a week ago or so, got what I believe is the > same error. It's on a 64-bit machine, but that machine is not and has > never been multilib. Must be a conflict with some other package. I > haven't had time to narrow it down yet. > > Just a hunch, maybe it's conflicting with an older version of fontforge? > > -Kyle > _______________________________________________ > 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/ > > > Fontforge compiled ok on both my 64bit and multilib systems, for what that's worth. Just tried tonight. -klaatu From enigma77 at gmx.net Wed Dec 10 10:08:50 2014 From: enigma77 at gmx.net (enigma) Date: Wed, 10 Dec 2014 11:08:50 +0100 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: References: <4597111.3qqFLkqWIH@slackware> <5487859B.4000900@iinet.net.au> Message-ID: <8834504.Og3xX7HinG@slackware> Am Dienstag, 9. Dezember 2014, 23:17:18 schrieb Kyle Guinn: > On 12/9/14, Christoph Willing wrote: > > Maybe multilib can be implicated in the fontforge build failures but I > > think there's some other factor involved too. > > I tried building it about a week ago or so, got what I believe is the > same error. It's on a 64-bit machine, but that machine is not and has > never been multilib. Must be a conflict with some other package. I > haven't had time to narrow it down yet. > > Just a hunch, maybe it's conflicting with an older version of fontforge? > > -Kyle > _______________________________________________ > 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/ > Is it possible that it has something to do with the way we upgrade our multilib libraries? I do it manually (no slackpkg+ or something similar). Therefor I download the Repo in a separate directory (not /tmp/multilib/) and diff the files with them in /tmp/multilib. Here my Way to upgrade the multilib: # SLACKVER=14.1 # mkdir /home/foo/downloads/and.not.tmp.multilib # cd and.not.tmp.multilib/ # lftp -c "open http://taper.alienbase.nl/mirrors/people/alien/multilib/ ; mirror -c -e ${SLACKVER}" # diff -r and.not.tmp.multilib/ /tmp/multilib # cp different.files /tm/multilib/ # rm /tmp/multilib/old.version.of.different.files # cd /tmp/multilib/14.1/ # upgradepkg --reinstall --install-new *.t?z # upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z Now I have some questions: 1.) Is it possible, that my Way to upgrade the multilib-files, confused my system? For example, I do not first upgrade the original 64-bit files (e.g. glibc), but simply overwrite the old multilib-files with the new multilib-files, as described above. 2.) Should i next time first upgrade the original 64bit packages (so that the multilib-packets are replaced by the original), before i again upgrade these with the multilib-packages from alienbobs repo? Or is it irrelevant? 3.) Whats the best Way to upgrade the multilib-files? 4.) In the case that my multilib-system actually has errors, what is the best way to synchronize my system with the current alien slackware64 14.1 Repository? After i synchronize my system and if the Build process still failed with an error, i can at least assume that it's not the multilib system and so i can turn my attention to other causes. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mherda at gmail.com Wed Dec 10 18:10:02 2014 From: mherda at gmail.com (Marcin Herda) Date: Wed, 10 Dec 2014 18:10:02 +0000 Subject: [Slackbuilds-users] perl/perl-AnyEvent(-Handle)? In-Reply-To: <20141209194807.GA31842@linuxbox.fi> References: <20141102170548.GJ2202@linuxbox.fi> <20141209194807.GA31842@linuxbox.fi> Message-ID: <54888C7A.6070402@gmail.com> Hi all, Massive apologies for not responding. I must have missed the original email. Sorry about that. I'll review it over the weekend. regards Marcin On 09/12/14 19:48, Mikko Varri wrote: > On Sun, Nov 02, 2014 at 07:05:48PM +0200, Mikko Varri wrote: >> I was about to add a perl-AnyEvent.SlackBuild, but by chance noticed >> that perl-AnyEvent-Handle.SlackBuild already installs the whole >> AnyEvent distibution. AnyEvent::Handle is just one module of that >> distribution. >> >> So, I'd suggest renaming the SlackBuild. If you agree, you can review >> (and pull) the commits from >> >> https://github.com/vmj/slackbuilds/compare/perl-AnyEvent >> >> > It's been over a month now with no reply (I sent a reminder to > maintainer a week ago). > > I think it is safe to adopt the SlackBuild? > > -vmj > > _______________________________________________ > 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 vmj at linuxbox.fi Wed Dec 10 19:53:43 2014 From: vmj at linuxbox.fi (Mikko Varri) Date: Wed, 10 Dec 2014 21:53:43 +0200 Subject: [Slackbuilds-users] perl/perl-AnyEvent(-Handle)? In-Reply-To: <54888C7A.6070402@gmail.com> References: <20141102170548.GJ2202@linuxbox.fi> <20141209194807.GA31842@linuxbox.fi> <54888C7A.6070402@gmail.com> Message-ID: <20141210195342.GA21171@linuxbox.fi> On Wed, Dec 10, 2014 at 06:10:02PM +0000, Marcin Herda wrote: > > I'll review it over the weekend. > Ok, cool! -vmj From timp at timp.com.au Wed Dec 10 22:29:46 2014 From: timp at timp.com.au (Timothy Pollard) Date: Thu, 11 Dec 2014 08:29:46 +1000 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: References: <4597111.3qqFLkqWIH@slackware> <20141208004149.53487a0d@stygian.lan> <15415336.FJRy4CrBc9@slackware> <20141208170701.7487dc9a@stygian.lan> <54862438.7020909@iinet.net.au> <20141208195250.1bd5c1d1@stygian.lan> <548653CA.20501@iinet.net.au> <20141209123527.GA24676@jdiamond-nb> <5487859B.4000900@iinet.net.au> Message-ID: <20141211082946.709c31a4@helez.timp.com.au> On Tue, 9 Dec 2014 23:17:18 -0600 Kyle Guinn wrote: > > Just a hunch, maybe it's conflicting with an older version of fontforge? > > -Kyle I think Kyle is correct on this front. I originally had this problem (on 14.1 Multilib, while building with sbopkg), so I tried a couple of experiments Today: Building the older version (20120731) by running the SlackBuild directly -- Successful Building the latest (20141014) with sbopkg after removing the 20120731 package -- Successful Building 20141014 with sbopkg after reinstalling the 20120731 package -- Failed Building 20141014 with sbopkg after re-upgrading to the 20141014 package -- Successful Seems to be the older version not playing nice with the build process; possibly only specific older version/s, and possibly only on Multilib Slackware. -- TimP [http://hub.timp.com.au] [http://blog.timp.com.au] -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Thu Dec 11 00:12:09 2014 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 11 Dec 2014 10:12:09 +1000 Subject: [Slackbuilds-users] Additional live555 update Message-ID: <5488E159.6040108@iinet.net.au> Since the SlackBuild for the 2014.12.08 version of live555 was approved, upstream has released a new 2014.12.09 update. Since I can't (I presume) recall a SlackBuild from the approved queue, could someone replace it with the 2014.12.09 version directly from my github repo please? Its at: https://github.com/cwilling/slackbuilds/tree/update-live555/libraries/live555 Thanks, chris From willysr at slackbuilds.org Thu Dec 11 05:29:27 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 11 Dec 2014 12:29:27 +0700 Subject: [Slackbuilds-users] Additional live555 update In-Reply-To: <5488E159.6040108@iinet.net.au> References: <5488E159.6040108@iinet.net.au> Message-ID: <54892BB7.1020502@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Since the SlackBuild for the 2014.12.08 version of live555 was > approved, upstream has released a new 2014.12.09 update. Since I > can't (I presume) recall a SlackBuild from the approved queue, > could someone replace it with the 2014.12.09 version directly from > my github repo please? Its at: > https://github.com/cwilling/slackbuilds/tree/update-live555/libraries/live555 done - -- > Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSJK7cACgkQiHuDdNczM4GzBACff+c+rbndqb30WPuF7v/zuaY1 SgQAn2XSLe4PxPLMp8i9t7nhcP05MH1/ =LL21 -----END PGP SIGNATURE----- From genghiskhan at gmx.ca Thu Dec 11 13:32:31 2014 From: genghiskhan at gmx.ca (Genghis Khan) Date: Thu, 11 Dec 2014 14:32:31 +0100 Subject: [Slackbuilds-users] Using BitTorrent to download SlackBuilds and Source Code Message-ID: Hallo, What do you think of a new pilot mechanism that would download and upload SlackBuilds and Source Code archives using software like aria2 or rTorrent? Torrent files of SlackBuild should not include Source Code and vice-versa, for these reasons: 1. So peer users of other distros (e.g. Archlinux, Gentoo and Salix) would also be usable for SBo users. 2. So SBo peer users that did not made an update of an SBo package, which has an update in its SlackBuild only, would not be not connected with users who would install (not update) that package after an update. If some would still like to have one Torrent file, then I suggest to make such Torrent file to contain two torrent files (a Torrent file of an SlackBuild, and another of a Source Code). Note: I do not know whether aria2 is able to upload files. From enigma77 at gmx.net Thu Dec 11 16:48:05 2014 From: enigma77 at gmx.net (enigma) Date: Thu, 11 Dec 2014 17:48:05 +0100 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <20141211082946.709c31a4@helez.timp.com.au> References: <4597111.3qqFLkqWIH@slackware> <20141211082946.709c31a4@helez.timp.com.au> Message-ID: <9716143.eYo27KddTF@slackware> Am Donnerstag, 11. Dezember 2014, 08:29:46 schrieb Timothy Pollard: > On Tue, 9 Dec 2014 23:17:18 -0600 > Kyle Guinn wrote: > > > > Just a hunch, maybe it's conflicting with an older version of fontforge? > > > > -Kyle > > I think Kyle is correct on this front. > > I originally had this problem (on 14.1 Multilib, while building with sbopkg), > so I tried a couple of experiments Today: > > Building the older version (20120731) by running the SlackBuild directly > -- Successful > Building the latest (20141014) with sbopkg after removing the 20120731 package > -- Successful > Building 20141014 with sbopkg after reinstalling the 20120731 package > -- Failed > Building 20141014 with sbopkg after re-upgrading to the 20141014 package > -- Successful > > Seems to be the older version not playing nice with the build process; possibly > only specific older version/s, and possibly only on Multilib Slackware. > > -- > TimP > [http://hub.timp.com.au] > [http://blog.timp.com.au] SOLVED After I remove the old fontforge-Version, the new Version build and install without error. It also worked on the manual way, without sbopkg. I would like to thank everyone who has helped me to solved my problem. THANK YOU. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Thu Dec 11 20:06:13 2014 From: yalhcru at gmail.com (B Watson) Date: Thu, 11 Dec 2014 15:06:13 -0500 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: <9716143.eYo27KddTF@slackware> References: <4597111.3qqFLkqWIH@slackware> <20141211082946.709c31a4@helez.timp.com.au> <9716143.eYo27KddTF@slackware> Message-ID: On 12/11/14, enigma wrote: > After I remove the old fontforge-Version, the new Version build and install > without error. > It also worked on the manual way, without sbopkg. Maybe ask the maintainer to mention this in his README? From willysr at slackbuilds.org Thu Dec 11 20:17:04 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 12 Dec 2014 03:17:04 +0700 Subject: [Slackbuilds-users] Error while installing package fontforge (20141014) In-Reply-To: References: <4597111.3qqFLkqWIH@slackware> <20141211082946.709c31a4@helez.timp.com.au> <9716143.eYo27KddTF@slackware> Message-ID: <5489FBC0.4070100@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> After I remove the old fontforge-Version, the new Version build >> and install without error. It also worked on the manual way, >> without sbopkg. > > Maybe ask the maintainer to mention this in his README? Added on my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSJ+78ACgkQiHuDdNczM4EeuACgh9GvXd4Oq49OvgY5a3R8Ti5s yYsAn2SF9n0UvRKvfu7eXxvHrE1cXnnh =3OOq -----END PGP SIGNATURE----- From chris at chrisn.me.uk Thu Dec 11 20:27:38 2014 From: chris at chrisn.me.uk (Chris Novakovic) Date: Thu, 11 Dec 2014 20:27:38 +0000 Subject: [Slackbuilds-users] Bugs in perl-template.SlackBuild In-Reply-To: <20141207011628.3c459345@home.rlworkman.net> References: <547E5620.3070201@chrisn.me.uk> <20141207011628.3c459345@home.rlworkman.net> Message-ID: <5489FE3A.2000900@chrisn.me.uk> On 07/12/2014 07:16, Robby Workman wrote: > On Wed, 03 Dec 2014 00:15:28 +0000 > Chris Novakovic wrote: > >> Dear all, >> >> There are a few bugs in perl-template.SlackBuild that prevent some >> module distributions installing correctly, or at all. >> >> "Build method #1" uses makefiles generated by ExtUtils::MakeMaker [1] >> to drive the build process: >> >> perl Makefile.PL \ >> PREFIX=/usr \ >> INSTALLDIRS=vendor \ >> INSTALLVENDORMAN3DIR=/usr/man/man3 >> make >> make test >> make install DESTDIR=$PKG >> >> Module distributions that install system-wide scripts to /usr/bin have >> the man pages for those scripts installed to /usr/share/man/man1 >> because INSTALLVENDORMAN1DIR isn't set. The solution is to set >> INSTALLVENDORMAN1DIR=/usr/man/man1 after setting INSTALLDIRS. >> >> "Build method #2" uses Module::Build [2] to build and install the >> module distribution: >> >> perl Build.PL \ >> prefix=/usr \ >> installdirs=vendor \ >> destdir=$PKG >> ./Build >> ./Build test >> ./Build install \ >> --install_path bindoc=/usr/man/man1 \ >> --install_path libdoc=/usr/man/man3 >> >> There are two bugs here: >> >> - Options and values passed to Build.PL aren't meant to be delimited >> with = symbols, which leads to them being ignored; the default >> behaviour is to install to /usr/local (and in the main perl >> directory, not in the site or vendor subdirectories) and then to >> install directly to /usr/local when running `./Build install`, thus >> bypassing $PKG entirely. The solution is to replace the = symbols >> with spaces in the arguments to `perl Build.PL`. >> >> - The Module::Build cookbook [3] says that destdir should be passed to >> `./Build install` rather than `perl Build.PL`. destdir=$PKG should >> therefore move to `./Build install` and become --destdir $PKG. >> >> With all three of these changes, I've yet to see a Perl module that >> doesn't build and install correctly. >> >> Cheers, >> Chris >> >> [1] >> http://search.cpan.org/~bingos/ExtUtils-MakeMaker-7.04/lib/ExtUtils/MakeMaker.pm >> [2] >> http://search.cpan.org/~leont/Module-Build-0.4210/lib/Module/Build.pm >> [3] >> http://search.cpan.org/~leont/Module-Build-0.4210/lib/Module/Build/Cookbook.pm > > > If you will send me a patch against the current template, we'll get > it merged. > > Thanks! Apologies for the delay -- I've attached a patch against the HEAD of templates.git. Cheers, Chris -------------- next part -------------- commit 1bf543364072d3a676bb887856cd56b9f66c59cd Author: Chris Novakovic Date: Thu Dec 11 20:20:08 2014 +0000 Several fixes for perl-template.SlackBuild: - INSTALLVENDORMAN1DIR=/usr/man/man1 is now set during build method #1, so man pages in section 1 are installed in a location supported by Slackware - The options "prefix" and "installdirs" that are passed to Build.PL in build method #2 are now correctly recognised - "destdir" is now passed to `./Build install` instead of Build.PL in build method #2, as recommended by the Module::Build::Cookbook documentation diff --git a/perl-template.SlackBuild b/perl-template.SlackBuild index 53adb0d..6787cda 100644 --- a/perl-template.SlackBuild +++ b/perl-template.SlackBuild @@ -106,6 +106,7 @@ find -L . \ perl Makefile.PL \ PREFIX=/usr \ INSTALLDIRS=vendor \ + INSTALLVENDORMAN1DIR=/usr/man/man1 \ INSTALLVENDORMAN3DIR=/usr/man/man3 make make test @@ -113,12 +114,12 @@ make install DESTDIR=$PKG # Build method #2 perl Build.PL \ - prefix=/usr \ - installdirs=vendor \ - destdir=$PKG + prefix /usr \ + installdirs vendor ./Build ./Build test ./Build install \ + --destdir $PKG \ --install_path bindoc=/usr/man/man1 \ --install_path libdoc=/usr/man/man3 From chris.willing at iinet.net.au Thu Dec 11 22:14:01 2014 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 12 Dec 2014 08:14:01 +1000 Subject: [Slackbuilds-users] ANOTHER Additional live555 update In-Reply-To: <54892BB7.1020502@slackbuilds.org> References: <5488E159.6040108@iinet.net.au> <54892BB7.1020502@slackbuilds.org> Message-ID: <548A1729.2070903@iinet.net.au> On 12/11/2014 03:29 PM, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> Since the SlackBuild for the 2014.12.08 version of live555 was >> approved, upstream has released a new 2014.12.09 update. Since I >> can't (I presume) recall a SlackBuild from the approved queue, >> could someone replace it with the 2014.12.09 version directly from >> my github repo please? Its at: >> https://github.com/cwilling/slackbuilds/tree/update-live555/libraries/live555 > > done Thanks Willy. However there was yet another update overnight to version 2014.12.11, fixing some buffer overflows. Could you update again from same location please? chris From zarniwhoop at ntlworld.com Thu Dec 11 22:09:27 2014 From: zarniwhoop at ntlworld.com (Ken Moffat) Date: Thu, 11 Dec 2014 22:09:27 +0000 Subject: [Slackbuilds-users] texlive slackbuild produces a broken xindy.(14.1, 20140525) Message-ID: <20141211220927.GA11736@milliways> Hi, Introductory history to explain why I'm reporting this - I've ended up taking (some) responsibility for texlive at another place [1] and some while ago we got notified that _our_ build (starting from the binary install-tl-unx) was not buildng xindy (an indexing tool, used by 'makeglossaries'). At that time, I could not find out how to _use_ it, so I delayed adding it. Eventually I found an example, which I adapted and got working (well, it works on our x86_64, but not on i686 - that part is *my* problem). Because I wanted to be able to run tests to check that things still worked after an upgrade, I started preparing some test scripts. And then I decided to try to make them more generally useful, and also to ensure that I could look for texlive OTF/TTF fonts wherever they had been installed. For that, I've been using qemu. And now, the problem: On the (64-bit) slackbuild, xindy gets built but it is broken. I've now found an easier test (which works for me on both i686 and x86_64 and does not need modern fonts, and does actually error if it fails: tug.ctan.org/macros/latex/contrib/glossaries/samples/samplexdy.tex (I assume wget will be able to download thet, I used firefox). This creates three somewhat sparse pages, followed by two pages of glossary. The commands to run it to create a PDF are: $latex samplexdy $makeglossaries samplexdy $pdflatex samplexdy but on your 64-bit it initially fails with ***Call to xindy failed*** Check 'samplexdy.glg' for details which said among other things xindy: Cannot locate /usr/lib64/xindy.mem at /usr/bin/xindy line 519. Well, xindy.mem is in /usr/bin so I made a symlink and tried again. But makeglossaries still fails: xindy -L general -I xindy -M "samplexdy" -t "samplexdy.glg" -o "samplexdy.gls! "samplexdy.glo" Cannot locate xindy module for language general. ***Call to xindy failed*** Check 'samplexdy.glg' for details - that now contains: *** Unable to execute: '"xindy" -L english -C utf8 -I xindy -M "samplexdy" -t "samplexdy.glg" -o "samplexdy.gls" "samplexdy.glo"' *** Failed with error code 1. Status report: Cannot locate xindy module for language english in codepage utf8. At that point, I gave up. No idea why it said 'language general' when it is actually trying to use english. I wonder if, perhaps, a UTF-8 locale is needed to build xindy. I'm not subscribed, but if you need to contact me, the address I'm sending from should work. This is a somewhat niche part of tex, I can understand if you do not care about it. If somebdy wants to look at it, it might be easiest to start with the separate xindy-2.5.0 tarball at http://www.ctan.org/tex-archive/indexing/xindy/base to save having to build all of texlive. ?en [1.] beyond.linuxfromscratch.org -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. From willysr at slackbuilds.org Fri Dec 12 00:49:54 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 12 Dec 2014 07:49:54 +0700 Subject: [Slackbuilds-users] ANOTHER Additional live555 update In-Reply-To: <548A1729.2070903@iinet.net.au> References: <5488E159.6040108@iinet.net.au> <54892BB7.1020502@slackbuilds.org> <548A1729.2070903@iinet.net.au> Message-ID: <548A3BB2.60008@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > However there was yet another update overnight to version > 2014.12.11, fixing some buffer overflows. Could you update again > from same location please? done - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSKO7IACgkQiHuDdNczM4EAOACfZjuSzlFkd5rQEQlpJT0j/6mD 0EEAnjA+18oP49e769V1H4tr6P7rpbKs =hvVe -----END PGP SIGNATURE----- From rworkman at slackbuilds.org Fri Dec 12 05:13:59 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 11 Dec 2014 23:13:59 -0600 Subject: [Slackbuilds-users] texlive slackbuild produces a broken xindy.(14.1, 20140525) In-Reply-To: <20141211220927.GA11736@milliways> References: <20141211220927.GA11736@milliways> Message-ID: <20141211231359.7f6f1b70@home.rlworkman.net> On Thu, 11 Dec 2014 22:09:27 +0000 Ken Moffat wrote: > Hi, > > Introductory history to explain why I'm reporting this - > > I've ended up taking (some) responsibility for texlive at another > place [1] and some while ago we got notified that _our_ build > (starting from the binary install-tl-unx) was not buildng xindy (an > indexing tool, used by 'makeglossaries'). > > At that time, I could not find out how to _use_ it, so I delayed > adding it. Eventually I found an example, which I adapted and got > working (well, it works on our x86_64, but not on i686 - that part > is *my* problem). > > Because I wanted to be able to run tests to check that things still > worked after an upgrade, I started preparing some test scripts. And > then I decided to try to make them more generally useful, and also > to ensure that I could look for texlive OTF/TTF fonts wherever they > had been installed. For that, I've been using qemu. > > And now, the problem: > > On the (64-bit) slackbuild, xindy gets built but it is broken. I've > now found an easier test (which works for me on both i686 and x86_64 > and does not need modern fonts, and does actually error if it fails: > tug.ctan.org/macros/latex/contrib/glossaries/samples/samplexdy.tex > (I assume wget will be able to download thet, I used firefox). > > This creates three somewhat sparse pages, followed by two pages of > glossary. The commands to run it to create a PDF are: > $latex samplexdy > $makeglossaries samplexdy > $pdflatex samplexdy > > but on your 64-bit it initially fails with > > ***Call to xindy failed*** > > Check 'samplexdy.glg' for details > > which said among other things > xindy: Cannot locate /usr/lib64/xindy.mem at /usr/bin/xindy line > 519. > > Well, xindy.mem is in /usr/bin so I made a symlink and tried again. > But makeglossaries still fails: > > xindy -L general -I xindy -M "samplexdy" -t "samplexdy.glg" -o > "samplexdy.gls! "samplexdy.glo" > Cannot locate xindy module for language general. > > ***Call to xindy failed*** > > Check 'samplexdy.glg' for details > > - that now contains: > > *** Unable to execute: '"xindy" -L english -C utf8 -I xindy -M > "samplexdy" -t "samplexdy.glg" -o "samplexdy.gls" "samplexdy.glo"' > *** > > Failed with error code 1. > > Status report: > > Cannot locate xindy module for language english in codepage utf8. > > At that point, I gave up. No idea why it said 'language general' > when it is actually trying to use english. I wonder if, perhaps, > a UTF-8 locale is needed to build xindy. > > I'm not subscribed, but if you need to contact me, the address I'm > sending from should work. > > This is a somewhat niche part of tex, I can understand if you do > not care about it. If somebdy wants to look at it, it might be > easiest to start with the separate xindy-2.5.0 tarball at > http://www.ctan.org/tex-archive/indexing/xindy/base to save having > to build all of texlive. > > ?en > > [1.] beyond.linuxfromscratch.org Hi Ken, I've recently gotten another report that Xindy is broken, so you're not the only one. It's on my TODO list, but I'm a bit stretched thin right now, so if anyone has some spare cycles and can figure it out and send us a patch, I'd be quite grateful. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From rworkman at slackbuilds.org Fri Dec 12 06:12:39 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 12 Dec 2014 00:12:39 -0600 Subject: [Slackbuilds-users] Bugs in perl-template.SlackBuild In-Reply-To: <5489FE3A.2000900@chrisn.me.uk> References: <547E5620.3070201@chrisn.me.uk> <20141207011628.3c459345@home.rlworkman.net> <5489FE3A.2000900@chrisn.me.uk> Message-ID: <20141212001239.2c62578e@home.rlworkman.net> On Thu, 11 Dec 2014 20:27:38 +0000 Chris Novakovic wrote: > Apologies for the delay -- I've attached a patch against the HEAD of > templates.git. Applied to both master and 14.1: commit e9e7c963c00d9902561075332e17392f47c1cda2 Author: Chris Novakovic Date: Fri Dec 12 00:09:22 2014 -0600 perl-template.SlackBuild: Several fixes - INSTALLVENDORMAN1DIR=/usr/man/man1 is now set during build method #1, so man pages in section 1 are installed in a location supported by Slackware - The options "prefix" and "installdirs" that are passed to Build.PL in build method #2 are now correctly recognised - "destdir" is now passed to `./Build install` instead of Build.PL in build method #2, as recommended by the Module::Build::Cookbook documentation Signed-off-by: Robby Workman Thanks again! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From carl.kreider at comcast.net Fri Dec 12 16:27:49 2014 From: carl.kreider at comcast.net (Carl Kreider) Date: Fri, 12 Dec 2014 11:27:49 -0500 Subject: [Slackbuilds-users] building virtualbox Message-ID: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> I have waded through a few years of archived messages but didn't find an answer to this: Regarding virtualbox, what does "NOTE:This will not build on a stock x86_64 system" mean? It will not build at all? It needs a non-stock system to build? If so, what is a non-stock system? TIA Carl From sbolokanov at abv.bg Fri Dec 12 16:46:12 2014 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Fri, 12 Dec 2014 18:46:12 +0200 (EET) Subject: [Slackbuilds-users] building virtualbox Message-ID: <1137108179.35671.1418402772541.JavaMail.apache@nm41.abv.bg> >From: Carl Kreider carl.kreider at comcast.net >I have waded through a few years of archived messages but didn't find an answer to this: Regarding virtualbox, what does "NOTE:This will not >build on a stock x86_64 system" mean? It will not build at all? It needs a non-stock system to build? If so, what is a non-stock system? It means that you need to have multilib installed. var m3_u = (location.protocol=='https:'?'https://a.abv.bg/www/delivery/ajs.php':'http://a.abv.bg/www/delivery/ajs.php'); var m3_r = Math.floor(Math.random()*99999999999); if (!document.MAX_used) document.MAX_used = ','; document.write (" "); -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Fri Dec 12 16:53:27 2014 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 12 Dec 2014 08:53:27 -0800 Subject: [Slackbuilds-users] building virtualbox In-Reply-To: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> References: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> Message-ID: you can just grab the .run for other distributions from vbox's website works great on x64 --- On Dec 12, 2014 8:27 AM, "Carl Kreider" wrote: > > I have waded through a few years of archived messages but didn't find an > answer to this: Regarding virtualbox, what does "NOTE:This will not build > on a stock x86_64 system" mean? It will not build at all? It needs a > non-stock system to build? If so, what is a non-stock system? > > TIA > > Carl > _______________________________________________ > 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 k.venken at online.be Fri Dec 12 17:24:08 2014 From: k.venken at online.be (Karel Venken) Date: Fri, 12 Dec 2014 18:24:08 +0100 Subject: [Slackbuilds-users] building virtualbox In-Reply-To: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> References: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> Message-ID: <548B24B8.6040007@online.be> Carl Kreider wrote: > I have waded through a few years of archived messages but didn't find an answer to this: Regarding virtualbox, what does "NOTE:This will not build on a stock x86_64 system" mean? It will not build at all? It needs a non-stock system to build? If so, what is a non-stock system? I built it a few months ago (64bit) and use it currently. Seems to work fine, so I guess it is OK. Just try it? K. > TIA > > Carl > _______________________________________________ > 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 northrupthebandgeek at gmail.com Fri Dec 12 17:51:07 2014 From: northrupthebandgeek at gmail.com (Ryan Northrup) Date: Fri, 12 Dec 2014 09:51:07 -0800 Subject: [Slackbuilds-users] building virtualbox In-Reply-To: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> References: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> Message-ID: On Dec 12, 2014 8:27 AM, "Carl Kreider" wrote: > > > I have waded through a few years of archived messages but didn't find an answer to this: Regarding virtualbox, what does "NOTE:This will not build on a stock x86_64 system" mean? It will not build at all? It needs a non-stock system to build? If so, what is a non-stock system? > > TIA > > Carl Virtualbox needs 32-bit libraries at compilation-time, which aren't available by default on a 64-bit install. You'll need to install 32-bit libraries via multilib. At runtime, however, 32-bit dependencies are not needed (IIRC), so once it's compiled, you shouldn't need the 32-bit libs. This is why the precompiled versions from Oracle reportedly work on stock 64-bit Slack. -- Ryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From k.venken at online.be Fri Dec 12 18:27:05 2014 From: k.venken at online.be (Karel Venken) Date: Fri, 12 Dec 2014 19:27:05 +0100 Subject: [Slackbuilds-users] building virtualbox In-Reply-To: References: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> Message-ID: <548B3379.5030700@online.be> Ryan Northrup wrote: > > On Dec 12, 2014 8:27 AM, "Carl Kreider" > wrote: > > > > > > I have waded through a few years of archived messages but didn't > find an answer to this: Regarding virtualbox, what does "NOTE:This > will not build on a stock x86_64 system" mean? It will not build at > all? It needs a non-stock system to build? If so, what is a non-stock > system? > > > > TIA > > > > Carl > > Virtualbox needs 32-bit libraries at compilation-time, which aren't > available by default on a 64-bit install. You'll need to install > 32-bit libraries via multilib. > > At runtime, however, 32-bit dependencies are not needed (IIRC), so > once it's compiled, you shouldn't need the 32-bit libs. This is why > the precompiled versions from Oracle reportedly work on stock 64-bit > Slack. > Intresting, Would this have been solved by installing multilib? If so, is there a way to check it if I have installed it. I guess wine has then same requirement? Because I use it as well and it is also indicated not to be for 64bit? K. From carl.kreider at comcast.net Fri Dec 12 18:30:47 2014 From: carl.kreider at comcast.net (Carl Kreider) Date: Fri, 12 Dec 2014 13:30:47 -0500 Subject: [Slackbuilds-users] building virtualbox In-Reply-To: References: <19675659-C4BF-46AE-BCDF-6D185E8328A6@comcast.net> Message-ID: Wow! Such response! Thank you all very much! Carl On Dec 12, 2014, at 12:51 PM, Ryan Northrup wrote: > On Dec 12, 2014 8:27 AM, "Carl Kreider" wrote: > > > > > > I have waded through a few years of archived messages but didn't find an answer to this: Regarding virtualbox, what does "NOTE:This will not build on a stock x86_64 system" mean? It will not build at all? It needs a non-stock system to build? If so, what is a non-stock system? > > > > TIA > > > > Carl > > Virtualbox needs 32-bit libraries at compilation-time, which aren't available by default on a 64-bit install. You'll need to install 32-bit libraries via multilib. > > At runtime, however, 32-bit dependencies are not needed (IIRC), so once it's compiled, you shouldn't need the 32-bit libs. This is why the precompiled versions from Oracle reportedly work on stock 64-bit Slack. > > -- Ryan > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Fri Dec 12 20:50:26 2014 From: miguel at thedeanda.com (Miguel De Anda) Date: Fri, 12 Dec 2014 12:50:26 -0800 Subject: [Slackbuilds-users] chromium update Message-ID: has there been a chromium update lately? i just ask b/c i've been seeing the "this version of chrome no longer supported..." on gmail for at least a few months now. i tried finding a new source archive but i couldn't figure out how to find the link to the source. -m -------------- next part -------------- An HTML attachment was scrubbed... URL: From hostmaster at slackonly.com Fri Dec 12 20:55:52 2014 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Fri, 12 Dec 2014 22:55:52 +0200 Subject: [Slackbuilds-users] chromium update In-Reply-To: References: Message-ID: <548B5658.1010907@slackonly.com> On 12/12/2014 10:50 PM, Miguel De Anda wrote: > has there been a chromium update lately? i just ask b/c i've been > seeing the "this version of chrome no longer supported..." on gmail > for at least a few months now. i tried finding a new source archive > but i couldn't figure out how to find the link to the source. > > -m > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > Hi! Look here: http://www.slackware.com/~alien/slackbuilds/chromium/ and here: http://alien.slackbook.org/blog/ Eric has everything you want... -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Fri Dec 12 21:04:27 2014 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 12 Dec 2014 13:04:27 -0800 Subject: [Slackbuilds-users] chromium update In-Reply-To: References: Message-ID: >has there been a chromium update lately? you should try manually updating the script version or grab eric hameleer's chromium latest is v39.* --- On Dec 12, 2014 12:50 PM, "Miguel De Anda" wrote: > has there been a chromium update lately? i just ask b/c i've been seeing > the "this version of chrome no longer supported..." on gmail for at least a > few months now. i tried finding a new source archive but i couldn't figure > out how to find the link to the source. > > -m > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Fri Dec 12 21:13:21 2014 From: miguel at thedeanda.com (Miguel De Anda) Date: Fri, 12 Dec 2014 13:13:21 -0800 Subject: [Slackbuilds-users] chromium update In-Reply-To: References: Message-ID: ah alien! somehow i feel like i've looked here before for something. so is the chromium slackbuild on sbo unmaintained? on another note, i made a small change to the google-chrome script included in /extras b/c i got tired of the broken icon.... i'm not sure if the maintainer of that script subscripts to this but i didn't find an easy way to report it to main slackware devs (sorry for it not being a patch): # Install a .desktop launcher: sed -i -e "s/Icon=google-chrome/Icon=\/opt\/google\/chrome\/product_logo_256.png/" \ $PKG/usr/share/applications/google-chrome.desktop #mkdir -p $PKG/usr/share/applications #ln -s /opt/google/chrome/google-chrome.desktop \ # $PKG/usr/share/applications/google-chrome.desktop thanks for the link, downloading and installing now. On Fri, Dec 12, 2014 at 1:04 PM, Ryan P.C. McQuen wrote: > > >has there been a chromium update lately? > > you should try manually updating the script version or grab eric > hameleer's chromium > > latest is v39.* > > --- > > On Dec 12, 2014 12:50 PM, "Miguel De Anda" wrote: > >> has there been a chromium update lately? i just ask b/c i've been seeing >> the "this version of chrome no longer supported..." on gmail for at least a >> few months now. i tried finding a new source archive but i couldn't figure >> out how to find the link to the source. >> >> -m >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Dec 13 03:51:53 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 13 Dec 2014 10:51:53 +0700 Subject: [Slackbuilds-users] Updates - 20141213.1 Message-ID: <548BB7D9.8080104@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Dec 13 03:37:50 UTC 2014 academic/Kst: Added (KDE4 Plotting Tool). academic/fet: Updated for version 5.23.4. academic/labplot2: Added (graph and scientific data analaysis). academic/octave: Add workarounds for documentation browser bugs. audio/pithos: Include pithosctl remote control script desktop/enlightenment: Updated for version 0.17.6 + new maintainer. desktop/lxpanel: Updated for version 0.8.0. desktop/screenfetch: Updated for version 3.6.5. desktop/trayer-srg: New maintainer. development/THE: Fix HTML documentation. development/acpica: Updated for version 20141107. development/android-studio: Updated for version 1.0.0_135_1629389. development/gsoap: Updated for version 2.8.21. development/le: Updated for version 1.15.1. development/netbeans: Updated for version 8.0.2. development/numpy: Updated for version 1.9.1. development/qt-creator3: Updated for version 3.3.0. development/src-vcs: Added (Simple Revision Control). development/sublime_text: Updated for version 3.0.65. games/freeciv: Updated for version 2.4.4. games/lutris: Added (Open Gaming Platform). games/mednafen: Updated for version 0.9.36.5. gis/Shapely: Prevent creation of unnecessary .pxi file in package. gis/geopy: Updated for version 1.5.0. gis/osm2pgsql: Updated for version 0.87.0. gis/postgis: Add option for pgAdmin plugin. graphics/Shellpic: Updated for version 1.6.1. graphics/baires: New maintainer. graphics/darktable: Updated for version 1.6.0. graphics/fontforge: Update README. graphics/lilypond: Fix building against fontforge-20141014. libraries/botocore: Updated for version 0.79.0. libraries/e_dbus: Updated for version 1.7.10 + new maintainer. libraries/ecore: Updated for version 1.7.10 + new maintainer. libraries/edje: Updated for version 1.7.10 + new maintainer. libraries/eet: Updated for version 1.7.10 + new maintainer. libraries/efreet: Updated for version 1.7.10 + new maintainer. libraries/eina: Updated for version 1.7.10 + new maintainer. libraries/eio: Updated for version 1.7.10 + new maintainer. libraries/elementary: Updated for version 1.7.10 + new maintainer. libraries/embryo: Updated for version 1.7.10 + new maintainer. libraries/emotion: Updated for version 1.7.10 + new maintainer. libraries/ethumb: Updated for version 1.7.10 + new maintainer. libraries/evas: Updated for version 1.7.10 + new maintainer. libraries/libbde: Added (libYAL BitLocker library). libraries/libdesktop-agnostic: Fix tarball naming discrepancy. libraries/libesedb: Added (libYAL library for ESE databases). libraries/libevt: Added (libYAL EVT library). libraries/libevtx: Added (libYAL EVTX library). libraries/libfm: Updated for version 1.2.3. libraries/libsidplayfp: Updated for version 1.6.2. libraries/live555: Updated for version 2014.12.11. libraries/logilab-common: Updated for version 0.63.2. libraries/matplotlib: Updated for version 1.4.2. libraries/menu-cache: Updated for version 1.0.0. libraries/mysql-connector-c++: Updated for version 1.1.5. libraries/pexpect: Updated for version 3.2 + new maintainer. libraries/poco: Updated for version 1.4.7p1. multimedia/flashplayer-plugin: Updated for version 11.2.202.425. multimedia/mkvtoolnix: Updated for version 7.3.0. multimedia/plexmediaserver: Updated for version 0.9.11.4.739. network/awscli: Updated for version 1.6.9. network/deis: Updated for version 1.1.0. network/flexget: Updated for version 1.2.234. network/hydra: Updated for version 8.1. network/openconnect: Fix vpnc-script's test for /sbin/netconfig network/owncloud-server: Updated for version 7.0.4. network/pentadactyl: Added (Vim keybindings for Firefox). network/phpmyadmin: Updated for version 4.3.11. network/valknut: Added patch. network/viber: Fix desktop file. network/you-get: Updated for version 0.3.32. perl/perl-DBD-SQLiteL: Updated for version 1.46. python/argcomplete: Updated for version 0.8.4. python/statsmodels: Added (statistical computation). system/culmus: Fix font installation and doinst.sh paths system/heirloom-doctools: Updated for version 141029. system/lxsession: Updated for version 0.5.2. system/pcmanfm: Updated for version 1.2.3. system/phoronix-test-suite: Updated for version 5.4.0. system/refind: Added (An EFI boot manager utility). system/slpkg: Updated for version 2.1.3. system/terminology: Updated for version 0.7.0 + new maintainer. system/vagrant: Updated for version 1.7.0. system/virtualbox-addons: Updated for version 4.3.20. system/virtualbox-extension-pack: Updated for version 4.3.20. system/virtualbox-kernel-addons: Updated for version 4.3.20. system/virtualbox-kernel: Updated for version 4.3.20. system/virtualbox: Updated for version 4.3.20. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSLt9kACgkQiHuDdNczM4GI9gCgpntb8XOKiI77qmJVSdPCKRuq KGgAn09hXraJ/t9UJ7dKEXUaEQuNUp7W =2BYK -----END PGP SIGNATURE----- From mdhalstead at truvista.net Sat Dec 13 14:25:05 2014 From: mdhalstead at truvista.net (Mark Halstead) Date: Sat, 13 Dec 2014 09:25:05 -0500 Subject: [Slackbuilds-users] mkvtoolnix update breaks qt gui Message-ID: <548C4C41.4060000@truvista.net> The latest slackbuild for mkvtoolnix requires qt5 to build the qt gui. I don't think this got mentioned in the README. From Jim.Diamond at acadiau.ca Sat Dec 13 21:30:25 2014 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 13 Dec 2014 17:30:25 -0400 Subject: [Slackbuilds-users] matplotlib does not build on 1 of 3 systems Message-ID: <20141213213025.GA9794@jdiamond-nb> Hi, I'm trying to compile matplotlib on some Slackware64 14.1 systems, all with multilib. On 2 of the 3, it compiles fine using sboinstall and/or sboupgrade. On the third, my attempts are rewarded with the following: ... BUILDING MATPLOTLIB matplotlib: yes [1.4.2] python: yes [2.7.5 (default, May 29 2013, 02:28:51) [GCC 4.8.0]] platform: yes [linux2] REQUIRED DEPENDENCIES AND EXTENSIONS numpy: yes [version 1.9.1] six: yes [using six version 1.8.0] dateutil: yes [using dateutil version 2.2] pytz: yes [using pytz version 2013.8] tornado: yes [using tornado version 4.0.2] pyparsing: yes [using pyparsing version 2.0.1] pycxx: yes [Couldn't import. Using local copy.] libagg: yes [pkg-config information for 'libagg' could not be found. Using local copy.] freetype: yes [version 2.5.0] png: yes [version 1.4.12] qhull: yes [pkg-config information for 'qhull' could not be found. Using local copy.] OPTIONAL SUBPACKAGES sample_data: yes [installing] toolkits: yes [installing] tests: no [skipping due to configuration] toolkits_tests: no [skipping due to configuration] OPTIONAL BACKEND EXTENSIONS macosx: no [Mac OS-X only] qt5agg: no [PyQt5 not found] Traceback (most recent call last): File "setup.py", line 155, in result = package.check() File "/tmp/SBo/matplotlib-1.4.2/setupext.py", line 504, in check additional_info = self.check_requirements() File "/tmp/SBo/matplotlib-1.4.2/setupext.py", line 1989, in check_requirements msg = p.map(self.callback, [self])[0] File "/usr/lib64/python2.7/multiprocessing/pool.py", line 250, in map return self.map_async(func, iterable, chunksize).get() File "/usr/lib64/python2.7/multiprocessing/pool.py", line 554, in get raise self._value RuntimeError: the sip module implements API v7.0 to v7.1 but the PyQt4.QtCore module requires API v9.1 ... On the good systems, I see ... OPTIONAL BACKEND EXTENSIONS macosx: no [Mac OS-X only] qt5agg: no [PyQt5 not found] qt4agg: yes [installing, Qt: 4.8.4, PyQt: 4.8.4] pyside: no [PySide not found] gtk3agg: no [Requires pygobject to be installed.] gtk3cairo: no [Requires pygobject to be installed.] gtkagg: yes [installing, Gtk: 2.24.20 pygtk: 2.24.0] tkagg: yes [installing, version 81008] wxagg: yes [installing, version 2.8.12.1] gtk: yes [installing, Gtk: 2.24.20 pygtk: 2.24.0] agg: yes [installing] cairo: yes [installing, pycairo version 1.8.10] windowing: no [Microsoft Windows only] OPTIONAL LATEX DEPENDENCIES dvipng: yes [version 1.14] ghostscript: yes [version 9.07] latex: yes [version 3.14159265] pdftops: yes [version 0.24.3] running install ... I've compared the packages installed (and their versions) on all three systems, and while there are a few differences, I didn't see any difference which looked like it should affect any of Python, PyQt or Qt. (Admittedly, I may have missed some significant difference.) Does anyone have any insight as to what I might be looking for? Obviously I can copy over the package from one of the successful systems and install it (whether it would work correctly is another issue), but I'd rather have some idea about what the real problem is. Thanks. Jim From larryhaja at gmail.com Sat Dec 13 21:56:50 2014 From: larryhaja at gmail.com (Larry Hajali) Date: Sat, 13 Dec 2014 13:56:50 -0800 Subject: [Slackbuilds-users] matplotlib does not build on 1 of 3 systems In-Reply-To: <20141213213025.GA9794@jdiamond-nb> References: <20141213213025.GA9794@jdiamond-nb> Message-ID: Looks like your PyQt package is not compatible with the installed sip package. I get similar errors on calibre 1.x versions because I upgraded sip to a newer version for building PyQt5. You might want to reinstall PyQt and sip on the system that is giving you problems. --Larry On Sat, Dec 13, 2014 at 1:30 PM, Jim Diamond wrote: > > Hi, > > I'm trying to compile matplotlib on some Slackware64 14.1 systems, all > with multilib. > > On 2 of the 3, it compiles fine using sboinstall and/or sboupgrade. > > On the third, my attempts are rewarded with the following: > > ... > BUILDING MATPLOTLIB > matplotlib: yes [1.4.2] > python: yes [2.7.5 (default, May 29 2013, 02:28:51) [GCC > 4.8.0]] > platform: yes [linux2] > > REQUIRED DEPENDENCIES AND EXTENSIONS > numpy: yes [version 1.9.1] > six: yes [using six version 1.8.0] > dateutil: yes [using dateutil version 2.2] > pytz: yes [using pytz version 2013.8] > tornado: yes [using tornado version 4.0.2] > pyparsing: yes [using pyparsing version 2.0.1] > pycxx: yes [Couldn't import. Using local copy.] > libagg: yes [pkg-config information for 'libagg' could not > be found. Using local copy.] > freetype: yes [version 2.5.0] > png: yes [version 1.4.12] > qhull: yes [pkg-config information for 'qhull' could not > be > found. Using local copy.] > > OPTIONAL SUBPACKAGES > sample_data: yes [installing] > toolkits: yes [installing] > tests: no [skipping due to configuration] > toolkits_tests: no [skipping due to configuration] > > OPTIONAL BACKEND EXTENSIONS > macosx: no [Mac OS-X only] > qt5agg: no [PyQt5 not found] > Traceback (most recent call last): > File "setup.py", line 155, in > result = package.check() > File "/tmp/SBo/matplotlib-1.4.2/setupext.py", line 504, in check > additional_info = self.check_requirements() > File "/tmp/SBo/matplotlib-1.4.2/setupext.py", line 1989, in > check_requirements > msg = p.map(self.callback, [self])[0] > File "/usr/lib64/python2.7/multiprocessing/pool.py", line 250, in map > return self.map_async(func, iterable, chunksize).get() > File "/usr/lib64/python2.7/multiprocessing/pool.py", line 554, in get > raise self._value > RuntimeError: the sip module implements API v7.0 to v7.1 but the > PyQt4.QtCore module requires API v9.1 > ... > > > On the good systems, I see > > ... > OPTIONAL BACKEND EXTENSIONS > macosx: no [Mac OS-X only] > qt5agg: no [PyQt5 not found] > qt4agg: yes [installing, Qt: 4.8.4, PyQt: 4.8.4] > pyside: no [PySide not found] > gtk3agg: no [Requires pygobject to be installed.] > gtk3cairo: no [Requires pygobject to be installed.] > gtkagg: yes [installing, Gtk: 2.24.20 pygtk: 2.24.0] > tkagg: yes [installing, version 81008] > wxagg: yes [installing, version 2.8.12.1] > gtk: yes [installing, Gtk: 2.24.20 pygtk: 2.24.0] > agg: yes [installing] > cairo: yes [installing, pycairo version 1.8.10] > windowing: no [Microsoft Windows only] > > OPTIONAL LATEX DEPENDENCIES > dvipng: yes [version 1.14] > ghostscript: yes [version 9.07] > latex: yes [version 3.14159265] > pdftops: yes [version 0.24.3] > > running install > ... > > > I've compared the packages installed (and their versions) on all three > systems, and while there are a few differences, I didn't see any > difference which looked like it should affect any of Python, PyQt or > Qt. (Admittedly, I may have missed some significant difference.) > > > Does anyone have any insight as to what I might be looking for? > Obviously I can copy over the package from one of the successful > systems and install it (whether it would work correctly is another > issue), but I'd rather have some idea about what the real problem is. > > Thanks. > > Jim > _______________________________________________ > 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 Jim.Diamond at acadiau.ca Sun Dec 14 01:45:15 2014 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 13 Dec 2014 21:45:15 -0400 Subject: [Slackbuilds-users] matplotlib does not build on 1 of 3 systems In-Reply-To: References: <20141213213025.GA9794@jdiamond-nb> Message-ID: <20141214014515.GA15455@jdiamond-nb> On Sat, Dec 13, 2014 at 13:56 (-0800), Larry Hajali wrote: > Looks like your PyQt package is not compatible with the installed sip > package. I get similar errors on calibre 1.x versions because I upgraded > sip to a newer version for building PyQt5. You might want to reinstall > PyQt and sip on the system that is giving you problems. Larry, Thanks for that. I have to admit I was skeptical of your advice, since I was just using the distributed PyQt and sip packages. (I haven't needed to upgrade, downgrade or overgrade either of those things.) However, it turned out that it was the sip package; when I reinstalled that, things got better. Now I wish I had saved the old files before reinstalling to see which one was mysteriously changed along the way, and when. Cheers. Jim From willysr at slackbuilds.org Sun Dec 14 08:54:46 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 Dec 2014 15:54:46 +0700 Subject: [Slackbuilds-users] mkvtoolnix update breaks qt gui In-Reply-To: <548C4C41.4060000@truvista.net> References: <548C4C41.4060000@truvista.net> Message-ID: <548D5056.5050003@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The latest slackbuild for mkvtoolnix requires qt5 to build the qt > gui. I don't think this got mentioned in the README. Done on my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSNUFYACgkQiHuDdNczM4Fb4wCePibQiXZtq5WwTjIZ6cKT/yhH EjQAoJxoB7BMjttlLtD3hDD7wse7CeC7 =AiyZ -----END PGP SIGNATURE----- From thomas at beingboiled.info Sun Dec 14 23:16:07 2014 From: thomas at beingboiled.info (Thomas Morper) Date: Mon, 15 Dec 2014 00:16:07 +0100 (CET) Subject: [Slackbuilds-users] qemu annotations In-Reply-To: References: Message-ID: On Sat, 15 Nov 2014, Antonio Hern?ndez Blas wrote: > would it be possible to have an static version of libusb for qemu? See here: https://beingboiled.info/slackware/14.1/build/twm/qemu/ Simply place the libusb 1.0.19 archive next to the other files and the modified SlackBuild will build qemu including a static libusb so you'll get USB passthrough. The libusb addition to the build script is neither very sophisticated nor very well tested, so use it carefully. Also be aware of the different defaults for TARGETS, AUDIODRIVERS and VERSION :-) -- From janusz.kusnierek at akron.net.pl Tue Dec 16 12:26:38 2014 From: janusz.kusnierek at akron.net.pl (janusz.kusnierek at akron.net.pl) Date: Tue, 16 Dec 2014 13:26:38 +0100 (CET) Subject: [Slackbuilds-users] Slackbuilds.org - Virtualbox Package - /dev/vboxdrvu, /dev/vboxnetctl permissions fix Message-ID: Hello, I'm using Your scripts for Virtualbox on Slack64_14.1 (multilib) and everything is ok when I'm running Headless VM environment as user root. But I tried to migrate to regular user. I've found one problem during starting VMs. You can see it in ~/.config/VirtualBox/VBoxSVC.log --------------- 00:00:00.106446 nspr-2 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE 00:01:01.636762 nspr-3 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE 00:01:01.648883 nspr-2 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE 00:01:01.824179 nspr-3 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE 00:01:28.767725 nspr-3 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE 00:01:28.778548 nspr-3 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE 00:02:11.466239 nspr-2 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE ----------------- When we load modules using "/etc/rc.d/rc.vboxdrv start" it automatically creates additional devices (not only /dev/vboxdrv) with permissions like below using /lib/udev/rules.d/10-virtualbox.rules: ######## ls -l /dev crw-rw---- 1 root vboxusers 10, 56 Dec 16 09:55 vboxdrv crw------- 1 root root 10, 55 Dec 16 09:55 vboxdrvu crw------- 1 root root 10, 54 Dec 16 09:55 vboxnetctl ######## Permissions of the /dev/vboxdrvu and /dev/vboxnetctl are too restrictive for regular user, so I've added another rule file called 20-virtualbox2.rules with: ------ KERNEL=="vboxdrvu", NAME="vboxdrvu", OWNER="root", GROUP="vboxusers", MODE="0660" KERNEL=="vboxnetctl", NAME="vboxnetctl", OWNER="root",GROUP="vboxusers", MODE="0660" ------ And after restarting computer or /etc/rc.d/rc.vboxdrv, permissions are set correctly and there are no more errors in users's log ######## ls -l /dev crw-rw---- 1 root vboxusers 10, 55 Dec 16 12:20 vboxdrvu crw-rw---- 1 root vboxusers 10, 54 Dec 16 13:23 vboxnetctl ######## Could You apply this fix (or similar) in Your scripts? Thank You :) -- Best regards Janusz Kusnierek From mathieu.bouillaguet at gmail.com Tue Dec 16 21:23:23 2014 From: mathieu.bouillaguet at gmail.com (Mathieu Bouillaguet) Date: Tue, 16 Dec 2014 22:23:23 +0100 Subject: [Slackbuilds-users] libvirt SlackBuild running domains detection Message-ID: Hi, The libvirtd startup script included in the current SlackBuild doesn't reliably detetct running domains and consequently doesn't stop them when stopping the libvirt daemon. Currently it executes a grep on the keyword 'running'. This doesn't work on system with localized variables since the word 'running' will be translated. A reliable way would be to use the command "virsh list --name --state-running" which outputs the name of the currently running domains. On another subject it may be good to use the configure option --qemu-user to run the qemu virtual machines with another user than root. It is stronlgy recommended by upstream : "It is possible to change this default by using the --with-qemu-user=$USERNAME and --with-qemu-group=$GROUPNAME arguments to 'configure' during build. It is strongly recommended that vendors build with both of these arguments set to 'qemu'." http://libvirt.org/drvqemu.html#securitydac Currently all qemu virtual machnie are executed with root user and priviledges unless it is built with optional dependency libcapng. See http://libvirt.org/drvqemu.html#securitycap Cordially Mathieu Bouillaguet -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Tue Dec 16 22:35:52 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 16 Dec 2014 16:35:52 -0600 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: References: Message-ID: <20141216163552.5bece862@home.rlworkman.net> On Mon, 15 Dec 2014 00:16:07 +0100 (CET) Thomas Morper wrote: > On Sat, 15 Nov 2014, Antonio Hern?ndez Blas wrote: > > > would it be possible to have an static version of libusb for qemu? > > See here: https://beingboiled.info/slackware/14.1/build/twm/qemu/ > > Simply place the libusb 1.0.19 archive next to the other files and > the modified SlackBuild will build qemu including a static libusb so > you'll get USB passthrough. > > The libusb addition to the build script is neither very sophisticated > nor very well tested, so use it carefully. Also be aware of the > different defaults for TARGETS, AUDIODRIVERS and VERSION :-) If I can find some time to do so, I'd like to do this with the stock qemu build here, as the libusb update isn't going to go into 14.1's /patches, and as it stands, the lack of updated libusb (and the consequent lack of usb passthrough support in qemu) is a big drawback. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From C.J.Theunissen at differ.nl Wed Dec 17 02:10:37 2014 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Wed, 17 Dec 2014 03:10:37 +0100 (CET) Subject: [Slackbuilds-users] perl-Geo-IP (1.45): download link changed. Message-ID: Hi, The download link mentioned in the .info file for perl-Geo-IP 1.45 (http://search.cpan.org/CPAN/authors/id/B/BO/BORISZ/Geo-IP-1.45.tar.gz) doesn't function anymore. The file can currently be found on CPAN at this URL: http://search.cpan.org/CPAN/authors/id/M/MA/MAXMIND/Geo-IP-1.45.tar.gz The md5sum didn't change. Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL From willysr at slackbuilds.org Wed Dec 17 02:23:28 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 17 Dec 2014 09:23:28 +0700 Subject: [Slackbuilds-users] perl-Geo-IP (1.45): download link changed. In-Reply-To: References: Message-ID: <5490E920.80805@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The download link mentioned in the .info file for perl-Geo-IP 1.45 > (http://search.cpan.org/CPAN/authors/id/B/BO/BORISZ/Geo-IP-1.45.tar.gz) > > doesn't function anymore. The file can currently be found on CPAN > at this URL: > > http://search.cpan.org/CPAN/authors/id/M/MA/MAXMIND/Geo-IP-1.45.tar.gz > > The md5sum didn't change. Thanks for reporting Fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSQ6SAACgkQiHuDdNczM4GabQCdERGcnn1Q3/aOk5aBaOzIFqHP Gh4AnA3sNK89+422uZxldmWetWYTRFXC =MlF+ -----END PGP SIGNATURE----- From C.J.Theunissen at differ.nl Wed Dec 17 02:41:24 2014 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Wed, 17 Dec 2014 03:41:24 +0100 (CET) Subject: [Slackbuilds-users] spamassassin (3.4.0): obsolete dependency. Message-ID: The .info file for spamassassing 3.4.0 mentions perl-IP-Country as a requirement, but this package seems to be obsolete. >From /usr/doc/spamassassin-3.4.0/INSTALL: Optional Modules ---------------- [...] - Geo::IP (from CPAN) Used by the RelayCountry plugin (not enabled by default) to determine the domain country codes of each relay in the path of an email. IP::Country::Fast is used as alternative if Geo::IP is not installed. This is not recommended as it's obsolete. A SlackBuild for the Geo::IP module is available on SlackBuilds.org as perl-Geo-IP (version 1.45). (The download link of that package is currently broken. See my previous mail to the slackbuilds mailing list.) Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL From kingbeowulf at gmail.com Wed Dec 17 03:18:54 2014 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 16 Dec 2014 19:18:54 -0800 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <20141216163552.5bece862@home.rlworkman.net> References: <20141216163552.5bece862@home.rlworkman.net> Message-ID: On Tuesday, December 16, 2014, Robby Workman wrote: > On Mon, 15 Dec 2014 00:16:07 +0100 (CET) > Thomas Morper > wrote: > > > On Sat, 15 Nov 2014, Antonio Hern?ndez Blas wrote: > > > > > would it be possible to have an static version of libusb for qemu? > > > > See here: https://beingboiled.info/slackware/14.1/build/twm/qemu/ > > > > Simply place the libusb 1.0.19 archive next to the other files and > > the modified SlackBuild will build qemu including a static libusb so > > you'll get USB passthrough. > > > > The libusb addition to the build script is neither very sophisticated > > nor very well tested, so use it carefully. Also be aware of the > > different defaults for TARGETS, AUDIODRIVERS and VERSION :-) > > > If I can find some time to do so, I'd like to do this with the > stock qemu build here, as the libusb update isn't going to go > into 14.1's /patches, and as it stands, the lack of updated > libusb (and the consequent lack of usb passthrough support in > qemu) is a big drawback. > > -RW > Let me take a crack at it since I need to submit an update anyway. Now that the new kitchen windows are in, I just need to finish the trim. (For some reason I always end up fixing the house when on "vacation") -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 chris.willing at iinet.net.au Wed Dec 17 21:14:31 2014 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 18 Dec 2014 07:14:31 +1000 Subject: [Slackbuilds-users] live555 update Message-ID: <5491F237.1080901@iinet.net.au> Its happened again - there's an update to 2014.12.13 in the approved queue but upstream has released 2014.12.17 overnight (actually there had also been a 2014.12.16 but I ignored it since it related only to Windows). Could someone replace the existing approved version with the update at my github repo please. Its at: https://github.com/cwilling/slackbuilds/tree/update-live555/libraries/live555 Thanks, chris From willysr at slackbuilds.org Wed Dec 17 21:19:07 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 18 Dec 2014 04:19:07 +0700 Subject: [Slackbuilds-users] live555 update In-Reply-To: <5491F237.1080901@iinet.net.au> References: <5491F237.1080901@iinet.net.au> Message-ID: <5491F34B.6030302@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Its happened again - there's an update to 2014.12.13 in the > approved queue but upstream has released 2014.12.17 overnight > (actually there had also been a 2014.12.16 but I ignored it since > it related only to Windows). > > Could someone replace the existing approved version with the update > at my github repo please. Its at: > > https://github.com/cwilling/slackbuilds/tree/update-live555/libraries/live555 if > it isn't a critical update, we can leave it as it is and you can submit an update after the public update Let me know if it's a critical update (security-related) and i will update it on my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSR80sACgkQiHuDdNczM4H1xACeIA/ftVhOWiR0qIv9EbGL0bt+ yHQAn30Add41+nJLqJh83tLmetZHoTHA =FEdd -----END PGP SIGNATURE----- From chris.willing at iinet.net.au Wed Dec 17 21:30:55 2014 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 18 Dec 2014 07:30:55 +1000 Subject: [Slackbuilds-users] live555 update In-Reply-To: <5491F34B.6030302@slackbuilds.org> References: <5491F237.1080901@iinet.net.au> <5491F34B.6030302@slackbuilds.org> Message-ID: <5491F60F.2010305@iinet.net.au> On 12/18/2014 07:19 AM, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> Its happened again - there's an update to 2014.12.13 in the >> approved queue but upstream has released 2014.12.17 overnight >> (actually there had also been a 2014.12.16 but I ignored it since >> it related only to Windows). >> >> Could someone replace the existing approved version with the update >> at my github repo please. Its at: >> >> https://github.com/cwilling/slackbuilds/tree/update-live555/libraries/live555 > > if >> > it isn't a critical update, we can leave it as it is and you can > submit an update after the public update > > Let me know if it's a critical update (security-related) and i will > update it on my branch Its not overtly security related; from the changelog.txt: - Updated "RTSPServerSupportingHTTPStreaming" to make sure that the data stream source gets closed when it's no longer needed. so could probably wait. chris From ryan.q at linux.com Thu Dec 18 00:34:21 2014 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 17 Dec 2014 16:34:21 -0800 Subject: [Slackbuilds-users] COMPAT32 question Message-ID: I maintain apulse, which has a COMPAT32=yes switch. I'm wondering how everyone feels about putting a check for compat32 into the SlackBuild, and the best way to do that. I was thinking something like this: if [ ! -z '$( find /var/log/packages/ -name "*compat32*" -print )' ]; then export COMPAT32=yes; fi The reason I would like to do this, is that even though I always pass the flag the first time I build it, like so: COMPAT32=yes sbopkg -i apulse I will probably forget at some point when I am updating through sbopkg's ncurses interface. Now I know we don't technically support multilib, or sbopkg, but does anyone see a downside to having this kind of checking in the build? Furthermore, does someone know a better way to perform this check. Maybe I should be relying on checking glibc or gcc ... Thanks, Ryan - -- --- From yalhcru at gmail.com Thu Dec 18 00:53:34 2014 From: yalhcru at gmail.com (B Watson) Date: Wed, 17 Dec 2014 19:53:34 -0500 Subject: [Slackbuilds-users] COMPAT32 question In-Reply-To: References: Message-ID: On 12/17/14, Ryan P.C. McQuen wrote: > Furthermore, does someone know a better way to perform this check. > Maybe I should be relying on checking glibc or gcc ... That's what I'd do. In the section that checks ARCH: ... elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" [ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}" else ... Doing it that way will autodetect, but still allow the user to override with COMPAT32=no in the environment. It also avoids the use of find, which is kinda slow and heavy. As to whether it's a good idea... I don't see why not. The existing apulse.SlackBuild already has multilib-specific code, this just automates enabling it (instead of user having to manually COMPAT32=yes). From info at microlinux.fr Thu Dec 18 15:09:39 2014 From: info at microlinux.fr (Niki Kovacs) Date: Thu, 18 Dec 2014 16:09:39 +0100 Subject: [Slackbuilds-users] Small mistake in recode.SlackBuild Message-ID: <5492EE33.4040002@microlinux.fr> Hi, There's a small mistake in recode.SlackBuild. Before unpacking the source code archive, there's a line to clear an eventual previous source code directory tree: rm -rf $PRGNAM-$VERSION In the script, this should read: rm -rf $SRCNAM-$SRCVER Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 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 ryan.q at linux.com Thu Dec 18 15:22:36 2014 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 18 Dec 2014 07:22:36 -0800 Subject: [Slackbuilds-users] Small mistake in recode.SlackBuild In-Reply-To: <5492EE33.4040002@microlinux.fr> References: <5492EE33.4040002@microlinux.fr> Message-ID: Ok I can push that out (thanks for catching it), should I bump the build number? - -- --- On Thu, Dec 18, 2014 at 7:09 AM, Niki Kovacs wrote: > Hi, > > There's a small mistake in recode.SlackBuild. > > Before unpacking the source code archive, there's a line to clear an > eventual previous source code directory tree: > > rm -rf $PRGNAM-$VERSION > > In the script, this should read: > > rm -rf $SRCNAM-$SRCVER > > Cheers, > > Niki > -- > Microlinux - Solutions informatiques 100% Linux et logiciels libres > 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 info at microlinux.fr Fri Dec 19 06:25:45 2014 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 19 Dec 2014 07:25:45 +0100 Subject: [Slackbuilds-users] Small mistake in recode.SlackBuild In-Reply-To: References: <5492EE33.4040002@microlinux.fr> Message-ID: <5493C4E9.6000707@microlinux.fr> Le 18/12/2014 16:22, Ryan P.C. McQuen a ?crit : > Ok I can push that out (thanks for catching it), should I bump the build number? I think this is not really necessary. I only spotted it while perusing it for my own (MLED) purposes. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Fri Dec 19 06:26:44 2014 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 19 Dec 2014 07:26:44 +0100 Subject: [Slackbuilds-users] Problem with libaacs download link Message-ID: <5493C524.6040409@microlinux.fr> Hi, The download link for libaacs works *sometimes*. More often than not, ftp.videolan.org will ask (randomly) for a password. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Fri Dec 19 06:37:20 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 19 Dec 2014 13:37:20 +0700 Subject: [Slackbuilds-users] Problem with libaacs download link In-Reply-To: <5493C524.6040409@microlinux.fr> References: <5493C524.6040409@microlinux.fr> Message-ID: <5493C7A0.7080209@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The download link for libaacs works *sometimes*. More often than > not, ftp.videolan.org will ask (randomly) for a password. Larry, is it ok to change it to this site? http://ftp.vim.org/ftp/mediaplayer/vlc/libaacs/0.7.1/libaacs-0.7.1.tar.bz2 it doesn't ask for password checksum is a match - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSTx6AACgkQiHuDdNczM4GrtgCfdwhMlQKZCsr/tjfPIlHd4ZJ2 LBcAn2/dBeglVzhwACDFopuIVbijHr4/ =FzqK -----END PGP SIGNATURE----- From klaatu at straightedgelinux.com Fri Dec 19 19:47:48 2014 From: klaatu at straightedgelinux.com (Klaatu) Date: Sat, 20 Dec 2014 08:47:48 +1300 Subject: [Slackbuilds-users] rejoystick patch In-Reply-To: <5493C7A0.7080209@slackbuilds.org> References: <5493C524.6040409@microlinux.fr> <5493C7A0.7080209@slackbuilds.org> Message-ID: <549480E4.4010301@straightedgelinux.com> I tried to email this to the email listed in the rejoystick.info file but got a delivery error ("This user doesn't have an account"), so I'm emailing the list instead, So, I was getting an error "Error occured: Failed to init sdl with joystick. Exiting..." Found an 8 line (or so) patch online, used it, and it fixed my problem. I'm attaching that here. It is not my patch; it is by Winter Knight. It works for me. Not sure if other people were getting the error when attempting to use rejoystick, but this did fix the issue for me. Cheers, Klaatu -------------- next part -------------- A non-text attachment was scrubbed... Name: rejoystick.patch Type: text/x-patch Size: 424 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Dec 20 00:04:51 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 20 Dec 2014 07:04:51 +0700 Subject: [Slackbuilds-users] rejoystick patch In-Reply-To: <549480E4.4010301@straightedgelinux.com> References: <5493C524.6040409@microlinux.fr> <5493C7A0.7080209@slackbuilds.org> <549480E4.4010301@straightedgelinux.com> Message-ID: <5494BD23.7080408@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I tried to email this to the email listed in the rejoystick.info > file but got a delivery error ("This user doesn't have an > account"), so I'm emailing the list instead, > > So, I was getting an error "Error occured: Failed to init sdl with > joystick. Exiting..." > > Found an 8 line (or so) patch online, used it, and it fixed my > problem. I'm attaching that here. > > It is not my patch; it is by Winter Knight. It works for me. > > Not sure if other people were getting the error when attempting to > use rejoystick, but this did fix the issue for me. Added the patch on my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSUvSMACgkQiHuDdNczM4HhQACgjLgGfl61hau50BWG3TNIS5Kw EzMAmwZLpBgbMF+Y/dntYR+7VQdrd9lc =Am0q -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Dec 20 00:39:40 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 20 Dec 2014 07:39:40 +0700 Subject: [Slackbuilds-users] Updates - 20141220.1 Message-ID: <5494C54C.3070809@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Dec 20 00:18:44 UTC 2014 academic/calc: Updated for 2.12.5.0. academic/maxima: Updated for 5.35.1. academic/mendeleydesktop: Updated for version 1.12.4. audio/abcde: Updated for version 2.6. audio/apulse: Updated for version 0.1.5 & detect multilib. audio/hydrogen: Updated for version 0.9.6.1. audio/podget: Updated for version 0.7.5. desktop/e16: Updated for version 1.0.15. desktop/i3: Update README. desktop/spectrwm: Updated for version 2.6.1. development/brackets: Updated for version 1.1. development/casperjs: Updated for version 1.1beta3. development/dbeaver: Updated for version 3.1.0. development/gradle: Updated for version 2.2.1. development/julia: Added (Dynamic Programming Language). development/mono-addins: Update DOWNLOAD url. development/phantomjs: Updated for version 1.9.8. development/poedit: Updated for version 1.7.1. development/src-vcs: Updated for version 0.15. development/ucblogo: Added (programming language). games/galaxyv2: Updated for version 1.84. games/kardsgt: Added (card games). games/moon-buggy: Updated for version 1.0.51. games/rejoystick: Patched for init SDL. gis/OWSLib: Updated for version 0.8.11. gis/geopy: Updated for version 1.6.1. gis/postgis: Updated for version 2.1.5. gis/rasterio: Updated for version 0.16. graphics/dcraw: Updated for version 9.22. graphics/digikam: Updated for version 4.6.0. graphics/pdf2png: Updated for version 0.5. graphics/qelectrotech: Updated for version 0.4rc1. graphics/ufraw: Updated for version 0.20. ham/fldigi: Updated for version 3.22.02. libraries/SFML: Updated for version 2.2. libraries/aqbanking: Update DOWNLOAD url. libraries/blas: Updated for version 3.5.0 + new maintainer. libraries/daq: Update DOWNLOAD url. libraries/gwenhywfar: Update DOWNLOAD url. libraries/jemalloc: Updated for version 3.6.0. libraries/lapack: Updated for version 3.5.0 + new maintainer. libraries/libaacs: Update DOWNLOAD url. libraries/libechonest: Updated for version 2.3.0. libraries/libevtx: Updated slack-desc. libraries/libewf: Updated for version 20140608. libraries/libfm-extra: Added (pcmanfm library) libraries/libfm: Splitted libfm-extra. libraries/libfwsi: Added (libYAL Windows Shell Item Library). libraries/libgit2: Updated for version 0.21.3. libraries/libhtp: Updated for version 0.5.16. libraries/libilbc: Updated for 2.0.2. libraries/liblnk: Added (libYAL LNK library). libraries/libolecf: Added (libYAL OLE 2 Library). libraries/libpff: Added (libYAL PFF Library). libraries/libqcow: Added (libYAL QEMU QCOW Image Library). libraries/libregf: Added (libYAL WinNT Registry Library). libraries/libsmdev: Added (libYAL Storage Media Library). libraries/libsmraw: Added (libYAL RAW Image Library). libraries/libvhdi: Added (libYAL VHD Library). libraries/libvirt-python: Updated for version 1.2.11. libraries/libvirt: Updated for version 1.2.11. libraries/libvmdk: Added (libYAL VMDK Library). libraries/libvshadow: Added (libYAL Volume Shadow Library). libraries/live555: Updated for version 2014.12.13. libraries/menu-cache: Noted the new dependency libfm-extra. misc/recode: Fix typo. misc/rsibreak: Update DOWNLOAD url. misc/subsurface: Updated for version 4.3. multimedia/mkvtoolnix: Update README about qt5. network/CherryMusic: Updated for version 0.34.1. network/Flootty: Updated for version 3.1.1. network/livestreamer: Updated for version 1.11.1. network/phpmyadmin: Updated for version 4.3.2. network/privoxy: Updated for version 3.0.22. network/snort: Update DOWNLOAD url. network/suricata: Updated for version 2.0.5. network/twitter: Updated for version 1.15.0. network/wireshark: Updated for version 1.12.2 office/libreoffice-helppack: Updated for version 4.3.5. office/libreoffice-langpack: Updated for version 4.3.5. office/libreoffice: Updated for version 4.3.5. office/scribus: Updated for version 1.4.4. office/texmaker: Updated for version 4.4.1. perl/perl-AnyEvent-Handle: Removed (Replaced by perl-AnyEvent). perl/perl-AnyEvent-I3: Update DEPS. perl/perl-AnyEvent: Added (the DBI of event loop programming). perl/perl-Geo-IP: Update DOWNLOAD url. perl/perl-cairo: Updated for version 1.105. python/autopep8: Updated for version 1.1. python/nxt-python: Added (Python module to control Lego NXT). python/python-mccabe: Updated for version 0.3. ruby/heroku-client: Added (Heroku CLI). system/Attic: Updated for version 0.14. system/asbt: Updated for version 1.0. system/butterfly: Updated for version 1.5.10. system/docker: Add note about requirement. system/elasticsearch: Updated for version 1.4.2. system/heirloom-doctools: Updated for version 141217. system/inxi: Updated for version 2.2.16. system/nilfs-utils: Updated for version 2.2.2. system/percona-toolkit: Updated for version 2.2.12. system/profile-sync-daemon: Updated for version 5.54. system/slpkg: Updated for version 2.1.4. system/tinyterm: Updated for version 0.3. system/vagrant: Updated for version 1.7.1. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSUxUwACgkQiHuDdNczM4HYYgCfa6TLJONe2De1cEXm6FCnSm7S 2N4AoITn2BWBCZwagWWuJWyc0YXjcJ3Y =u9yG -----END PGP SIGNATURE----- From rsamurti at gmail.com Sat Dec 20 02:20:33 2014 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Sat, 20 Dec 2014 07:50:33 +0530 Subject: [Slackbuilds-users] Is it possible to add Recent Updates link in the web page? Message-ID: Hello, If it is possible to add a link like Recent Updates in the web page of SlackBuilds it would be nice. Any comments? Anand -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Dec 20 02:23:23 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 20 Dec 2014 09:23:23 +0700 Subject: [Slackbuilds-users] Is it possible to add Recent Updates link in the web page? In-Reply-To: References: Message-ID: <5494DD9B.10602@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > If it is possible to add a link like Recent Updates in the web page > of SlackBuilds it would be nice. > > Any comments? I think that's what ChangeLog is used for http://slackbuilds.org/ChangeLog.php - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSU3ZoACgkQiHuDdNczM4HhvwCeOLBxik76pOSp38V66fxgOIQs 9CAAn0IFy/mNTEpsT72t/YC2oi2y6gXD =hw2e -----END PGP SIGNATURE----- From rsamurti at gmail.com Sat Dec 20 02:27:09 2014 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Sat, 20 Dec 2014 07:57:09 +0530 Subject: [Slackbuilds-users] Is it possible to add Recent Updates link in the web page? In-Reply-To: <5494DD9B.10602@slackbuilds.org> References: <5494DD9B.10602@slackbuilds.org> Message-ID: Hello, Thanks for showing this. I had not seen this!! Anand On Sat, Dec 20, 2014 at 7:53 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > If it is possible to add a link like Recent Updates in the web page > > of SlackBuilds it would be nice. > > > > Any comments? > > I think that's what ChangeLog is used for > http://slackbuilds.org/ChangeLog.php > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSU3ZoACgkQiHuDdNczM4HhvwCeOLBxik76pOSp38V66fxgOIQs > 9CAAn0IFy/mNTEpsT72t/YC2oi2y6gXD > =hw2e > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From genghiskhan at gmx.ca Sat Dec 20 03:15:16 2014 From: genghiskhan at gmx.ca (Genghis Khan) Date: Sat, 20 Dec 2014 04:15:16 +0100 Subject: [Slackbuilds-users] Segregate Speed Dreams tarballs to several SlackBuilds Message-ID: Hello, First of all, thank you for providing Speed Dreams at SBo. I don't want to download and install all of the following extras at one. speed-dreams-src-hq-cars-and-tracks-2.1.0-r5799.tar.xz speed-dreams-src-more-hq-cars-and-tracks-2.1.0-r5799.tar.xz speed-dreams-src-wip-cars-and-tracks-2.1.0-r5799.tar.xz I prefer to have several SlackBuilds for each tarball so in case I change my mind, I would not have to rebuild Speed Dreams, from source, once again. Please divide the above tarballs into 3 SlackBuilds. Regards, --GK From rsamurti at gmail.com Sat Dec 20 03:57:40 2014 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Sat, 20 Dec 2014 09:27:40 +0530 Subject: [Slackbuilds-users] blas-3.5.0 and lapack-3.5.0 problems w.r.t. octave. Message-ID: Hello, GNU Octave fails to run after installing the latest blas-3.5.0 and lapack-3.5.0. I think blas and lapack should should be corrected to include the following: libblas.so.3 link to libblas.so liblapack.so.3 link to liblapack.so After creating these links GNU Octave works properly. Anand -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Dec 20 04:27:28 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 20 Dec 2014 11:27:28 +0700 Subject: [Slackbuilds-users] blas-3.5.0 and lapack-3.5.0 problems w.r.t. octave. In-Reply-To: References: Message-ID: <5494FAB0.4010101@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > GNU Octave fails to run after installing the latest blas-3.5.0 and > lapack-3.5.0. > > I think blas and lapack should should be corrected to include the > following: > > libblas.so.3 link to libblas.so liblapack.so.3 link to > liblapack.so > > After creating these links GNU Octave works properly. you may need to rebuild octave since there has been a soname bump by upstream developers - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSU+q8ACgkQiHuDdNczM4HhBACdFnQLBgQF8FtDmqIB8VPSyICs GoUAnjMkFsCZ5/ayIpdpkRKa9YBAWTL0 =bq6J -----END PGP SIGNATURE----- From rsamurti at gmail.com Sat Dec 20 04:45:12 2014 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Sat, 20 Dec 2014 10:15:12 +0530 Subject: [Slackbuilds-users] blas-3.5.0 and lapack-3.5.0 problems w.r.t. octave. In-Reply-To: <5494FAB0.4010101@slackbuilds.org> References: <5494FAB0.4010101@slackbuilds.org> Message-ID: Hello, Even after rebuilding I faced this problem. Anand On Sat, Dec 20, 2014 at 9:57 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > GNU Octave fails to run after installing the latest blas-3.5.0 and > > lapack-3.5.0. > > > > I think blas and lapack should should be corrected to include the > > following: > > > > libblas.so.3 link to libblas.so liblapack.so.3 link to > > liblapack.so > > > > After creating these links GNU Octave works properly. > > you may need to rebuild octave since there has been a soname bump by > upstream developers > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSU+q8ACgkQiHuDdNczM4HhBACdFnQLBgQF8FtDmqIB8VPSyICs > GoUAnjMkFsCZ5/ayIpdpkRKa9YBAWTL0 > =bq6J > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Sat Dec 20 05:50:37 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 19 Dec 2014 23:50:37 -0600 Subject: [Slackbuilds-users] libvirt SlackBuild running domains detection In-Reply-To: References: Message-ID: <20141219235037.3178ea48@home.rlworkman.net> On Tue, 16 Dec 2014 22:23:23 +0100 Mathieu Bouillaguet wrote: > The libvirtd startup script included in the current SlackBuild doesn't > reliably detetct running domains and consequently doesn't stop them > when stopping the libvirt daemon. > > Currently it executes a grep on the keyword 'running'. This doesn't > work on system with localized variables since the word 'running' will > be translated. > > A reliable way would be to use the command "virsh list --name > --state-running" which outputs the name of the currently running > domains. > > On another subject it may be good to use the configure option > --qemu-user to run the qemu virtual machines with another user than > root. > > It is stronlgy recommended by upstream : > "It is possible to change this default by using the > --with-qemu-user=$USERNAME and --with-qemu-group=$GROUPNAME arguments > to 'configure' during build. It is strongly recommended that vendors > build with both of these arguments set to 'qemu'." > http://libvirt.org/drvqemu.html#securitydac > > Currently all qemu virtual machnie are executed with root user and > priviledges unless it is built with optional dependency libcapng. See > http://libvirt.org/drvqemu.html#securitycap commit bb44a8de7f7927a431c49c13416d49e2f670d8e6 Author: Robby Workman Date: Fri Dec 19 23:46:35 2014 -0600 libraries/libvirt: Make rc.libvirt more robust Detecting running domains by grepping for "running" isn't very effective for non-english strings, so let's fix that. Since I was already there, I cleaned up a few more nits. Thanks to Mathieu Bouillaguet for the report and solution. TODO: use --with-qemu-user=qemu and --with-qemu-group=qemu per upstream recommendation; this will have to be in sync with the qemu build here (with respect to what actual user and group names are used) Signed-off-by: Robby Workman -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From hba.nihilismus at gmail.com Sat Dec 20 10:44:39 2014 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sat, 20 Dec 2014 04:44:39 -0600 Subject: [Slackbuilds-users] vlc-2.1.5 source code URL is returning 404 Message-ID: The current value for download vlc's source code is returning 404: http://download.videolan.org/pub/videolan/vlc/2.1.5/vlc-2.1.5.tar.xz The working URL is: http://download.videolan.org/vlc/2.1.5/vlc-2.1.5.tar.xz MD5 matches. - Cheers -- 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 hba.nihilismus at gmail.com Sat Dec 20 11:26:28 2014 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sat, 20 Dec 2014 05:26:28 -0600 Subject: [Slackbuilds-users] Updates - 20141220.1 In-Reply-To: <5494C54C.3070809@slackbuilds.org> References: <5494C54C.3070809@slackbuilds.org> Message-ID: On Fri, Dec 19, 2014 at 6:39 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > libraries/libilbc: Updated for 2.0.2. > This update has broken the execution of ffmpeg in my system: # ldd /usr/bin/ffmpeg | grep not libilbc.so.1 => not found So as a fix: # cd /usr/lib64 # ln -s libilbc.so.2.0.2 libilbc.so.1 Am i the only one experiencing this issue? BTW, this is the content of install/doinst.sh for this update. ( cd usr/lib64 ; rm -rf libilbc.so.2 ) ( cd usr/lib64 ; ln -sf libilbc.so.2.0.2 libilbc.so.2 ) ( cd usr/lib64 ; rm -rf libilbc.so ) ( cd usr/lib64 ; ln -sf libilbc.so.2 libilbc.so ) - Cheers -- 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 matteo.bernardini at gmail.com Sat Dec 20 11:50:35 2014 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 20 Dec 2014 12:50:35 +0100 Subject: [Slackbuilds-users] Updates - 20141220.1 In-Reply-To: References: <5494C54C.3070809@slackbuilds.org> Message-ID: 2014-12-20 12:26 GMT+01:00 Antonio Hern?ndez Blas : > On Fri, Dec 19, 2014 at 6:39 PM, Willy Sudiarto Raharjo > wrote: >> >> libraries/libilbc: Updated for 2.0.2. > > > This update has broken the execution of ffmpeg in my system: > > # ldd /usr/bin/ffmpeg | grep not > libilbc.so.1 => not found it's normal if you built it against the old version: you should try rebuilding it against the new one (personally I haven't as I don't use libilbc). this usually happens whenever a library on which something else depends on gets a major version bump and you have to rebuild that something else so that it links to the new version of the library... Matteo From hba.nihilismus at gmail.com Sat Dec 20 12:17:44 2014 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sat, 20 Dec 2014 06:17:44 -0600 Subject: [Slackbuilds-users] Updates - 20141220.1 In-Reply-To: References: <5494C54C.3070809@slackbuilds.org> Message-ID: On Sat, Dec 20, 2014 at 5:50 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > it's normal if you built it against the old version: you should try > rebuilding it against the new one > Rebuilding ffmpeg and now i'm getting: --- CC libavcodec/libilbc.o libavcodec/libilbc.c: In function ?ilbc_decode_frame?: libavcodec/libilbc.c:99:31: error: ?WebRtc_Word16? undeclared (first use in this function) WebRtcIlbcfix_DecodeImpl((WebRtc_Word16*) frame->data[0], ^ libavcodec/libilbc.c:99:31: note: each undeclared identifier is reported only once for each function it appears in libavcodec/libilbc.c:99:45: error: expected expression before ?)? token WebRtcIlbcfix_DecodeImpl((WebRtc_Word16*) frame->data[0], ^ libavcodec/libilbc.c:100:30: error: too few arguments to function ?WebRtcIlbcfix_DecodeImpl? (const WebRtc_UWord16*) buf, &s->decoder, 1); ^ In file included from libavcodec/libilbc.c:22:0: /usr/include/ilbc.h:413:8: note: declared here void WebRtcIlbcfix_DecodeImpl(int16_t *decblock, ^ libavcodec/libilbc.c:83:20: warning: unused variable ?buf? [-Wunused-variable] const uint8_t *buf = avpkt->data; ^ libavcodec/libilbc.c: In function ?ilbc_encode_frame?: libavcodec/libilbc.c:173:31: error: ?WebRtc_UWord16? undeclared (first use in this function) WebRtcIlbcfix_EncodeImpl((WebRtc_UWord16*) avpkt->data, (const WebRtc_Word16*) frame->data[0], &s->encoder); ^ libavcodec/libilbc.c:173:46: error: expected expression before ?)? token WebRtcIlbcfix_EncodeImpl((WebRtc_UWord16*) avpkt->data, (const WebRtc_Word16*) frame->data[0], &s->encoder); ^ libavcodec/libilbc.c:173:46: error: too few arguments to function ?WebRtcIlbcfix_EncodeImpl? In file included from libavcodec/libilbc.c:22:0: /usr/include/ilbc.h:417:8: note: declared here void WebRtcIlbcfix_EncodeImpl(uint16_t *bytes, ^ make: *** [libavcodec/libilbc.o] Error 1 --- Time to remove it from dependencies :-) Thanks. -- 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 sbolokanov at abv.bg Sat Dec 20 13:09:28 2014 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Sat, 20 Dec 2014 15:09:28 +0200 (EET) Subject: [Slackbuilds-users] vlc-2.1.5 source code URL is returning 404 Message-ID: <606119379.50735.1419080968115.JavaMail.apache@nm42.abv.bg> Same with libbluray. Working link: http://download.videolan.org/libbluray/0.6.2/libbluray-0.6.2.tar.bz2 -------- ?????????? ????? -------- ??: Antonio Hern?ndez Blas hba.nihilismus at gmail.com ???????: [Slackbuilds-users] vlc-2.1.5 source code URL is returning 404 ??: "SlackBuilds.org Users List" ????????? ??: ??????, 2014, ???????? 20 12:44:39 EET The current value for download vlc's source code is returning 404: http://download.videolan.org/pub/videolan/vlc/2.1.5/vlc-2.1.5.tar.xz The working URL is: http://download.videolan.org/vlc/2.1.5/vlc-2.1.5.tar.xz MD5 matches. - Cheers -- Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster var m3_u = (location.protocol=='https:'?'https://a.abv.bg/www/delivery/ajs.php':'http://a.abv.bg/www/delivery/ajs.php'); var m3_r = Math.floor(Math.random()*99999999999); if (!document.MAX_used) document.MAX_used = ','; document.write (" "); -------------- next part -------------- An HTML attachment was scrubbed... URL: From lems at gmx.net Sat Dec 20 15:50:35 2014 From: lems at gmx.net (Leonard Schmidt) Date: Sat, 20 Dec 2014 16:50:35 +0100 Subject: [Slackbuilds-users] x264 download/distfile missing Message-ID: <0Lat5o-1Xe32i1ovQ-00kKxn@mail.gmx.com> Hello, just a quick note that the address http://download.videolan.org/x264/snapshots/ only has "last_stable_x264.tar.bz2" and "last_x264.tar.bz2". I found the tarball "x264-snapshot-20131101-2245-stable.tar.bz2" via Google: http://mirror.yandex.ru/mirrors/ftp.videolan.org/x264/snapshots/ It seems that there are no versioned tarballs anymore. Regards Leonard From richard.lapointe at gmail.com Sat Dec 20 12:13:07 2014 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Sat, 20 Dec 2014 07:13:07 -0500 Subject: [Slackbuilds-users] Errot in robomongo Slackbuiid Script Message-ID: <549567D3.5040503@laprjns.com> Running the robomongo.Slackbuild script results in the following error: tar: /usr/src/slapt-src/development/robomongo/robomongo-0.8.4-.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now fakeroot -- sh robomongo.SlackBuild Failed Line 38 of the Slackbuild has an error in the file name path. It is: tar xvf $CWD/$PRGNAM-$VERSION-$ANAME.tar.gz It should be: tar xvf $CWD/$PRGNAM-$VERSION-$ARCH.tar.gz Regards Richard Lapointe From miguel at thedeanda.com Sat Dec 20 16:10:28 2014 From: miguel at thedeanda.com (Miguel De Anda) Date: Sat, 20 Dec 2014 08:10:28 -0800 Subject: [Slackbuilds-users] Errot in robomongo Slackbuiid Script In-Reply-To: <549567D3.5040503@laprjns.com> References: <549567D3.5040503@laprjns.com> Message-ID: Thanks I'll take a look and update. Did you have issues for x86 or 64? M On Dec 20, 2014 8:01 AM, "Richard Lapointe" wrote: > Running the robomongo.Slackbuild script results in the following error: > > tar: /usr/src/slapt-src/development/robomongo/robomongo-0.8.4-.tar.gz: > Cannot open: No such file or directory > tar: Error is not recoverable: exiting now > fakeroot -- sh robomongo.SlackBuild Failed > > > Line 38 of the Slackbuild has an error in the file name path. It is: > > tar xvf $CWD/$PRGNAM-$VERSION-$ANAME.tar.gz > > It should be: > > tar xvf $CWD/$PRGNAM-$VERSION-$ARCH.tar.gz > > Regards > > Richard Lapointe > _______________________________________________ > 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 sbolokanov at abv.bg Sat Dec 20 16:32:56 2014 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Sat, 20 Dec 2014 18:32:56 +0200 (EET) Subject: [Slackbuilds-users] 0ad and 0ad-data updates Message-ID: <290976228.54972.1419093176567.JavaMail.apache@nm41.abv.bg> I have made some changes for 0ad and 0ad-data. Erik said that he is busy, so I wonder if somebody else can take a look. 0ad: https://github.com/sbolokanov/slackbuilds-official/tree/master/0ad 0ad-data: https://github.com/sbolokanov/slackbuilds-official/tree/master/0ad-data Enet >= 1.3 is now required for 0ad. -- ????? ????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Dec 20 16:42:51 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 20 Dec 2014 23:42:51 +0700 Subject: [Slackbuilds-users] vlc-2.1.5 source code URL is returning 404 In-Reply-To: <606119379.50735.1419080968115.JavaMail.apache@nm42.abv.bg> References: <606119379.50735.1419080968115.JavaMail.apache@nm42.abv.bg> Message-ID: <5495A70B.30207@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Same with libbluray. > > Working link: > http://download.videolan.org/libbluray/0.6.2/libbluray-0.6.2.tar.bz2 > > The current value for download vlc's source code is returning 404: > http://download.videolan.org/pub/videolan/vlc/2.1.5/vlc-2.1.5.tar.xz > The working URL is: > http://download.videolan.org/vlc/2.1.5/vlc-2.1.5.tar.xz Fixed both on my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSVpwsACgkQiHuDdNczM4FWfwCfdfJsEESRqLUW0ds4hoAZdcUQ DYwAoI9NgRQYRIN5hvolDpXmskHxnRGX =B0k8 -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Dec 20 16:46:25 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 20 Dec 2014 23:46:25 +0700 Subject: [Slackbuilds-users] x264 download/distfile missing In-Reply-To: <0Lat5o-1Xe32i1ovQ-00kKxn@mail.gmx.com> References: <0Lat5o-1Xe32i1ovQ-00kKxn@mail.gmx.com> Message-ID: <5495A7E1.9050109@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > just a quick note that the address > http://download.videolan.org/x264/snapshots/ only has > "last_stable_x264.tar.bz2" and "last_x264.tar.bz2". > > I found the tarball "x264-snapshot-20131101-2245-stable.tar.bz2" > via Google: > http://mirror.yandex.ru/mirrors/ftp.videolan.org/x264/snapshots/ > > It seems that there are no versioned tarballs anymore. Fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSVp+EACgkQiHuDdNczM4GPMgCgjNNbO6VP4TdAhlYzLmnQY/Qx BvAAnR+KXvlN7bECxs83WVdAXi8RzYnQ =x7JE -----END PGP SIGNATURE----- From thomasrling at gmail.com Sat Dec 20 17:05:54 2014 From: thomasrling at gmail.com (Thomas) Date: Sat, 20 Dec 2014 12:05:54 -0500 Subject: [Slackbuilds-users] Requesting update: gnome-inform7 to version 6L38 Message-ID: I'd like to request that the gnome-inform7 SlackBuild be updated to version 6L38. http://inform7.com/download/ Thank you much for your time. From andrew.david.strong at gmail.com Sat Dec 20 19:26:48 2014 From: andrew.david.strong at gmail.com (andrew) Date: Sun, 21 Dec 2014 06:26:48 +1100 Subject: [Slackbuilds-users] Updates - 20141220.1 In-Reply-To: References: <5494C54C.3070809@slackbuilds.org> Message-ID: <20141220192648.GA18846@ilium.andrews-corner.org> On Sat, Dec 20, 2014 at 06:17:44AM -0600, Antonio Hern?ndez Blas wrote: > Time to remove it from dependencies :-) Certainly works with current git FFmpeg and as well with the latest FFmpeg release 2.5.1. I realise it sounds a little like the 'tail wagging the dog' but perhaps it is time to update FFmpeg? Slackbuilds.org is holding FFmpeg 2.1.5 which is now unmaintained by the FFmpeg developers, a little rough since it only came out 5 months ago and was only updated to 2.1.6 in November but that is the way with FFmpeg... Andrew -- You think that's air you're breathing now? From thedoogster at gmail.com Sat Dec 20 23:21:41 2014 From: thedoogster at gmail.com (Doogster) Date: Sat, 20 Dec 2014 15:21:41 -0800 Subject: [Slackbuilds-users] Requesting update: gnome-inform7 to version 6L38 In-Reply-To: References: Message-ID: Thanks for the heads up. I won't be getting it done overnight, but it's on my todo list now. On Sat, Dec 20, 2014 at 9:05 AM, Thomas wrote: > I'd like to request that the gnome-inform7 SlackBuild be updated to > version 6L38. http://inform7.com/download/ > > Thank you much for your time. > _______________________________________________ > 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 Dec 21 01:17:42 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 Dec 2014 08:17:42 +0700 Subject: [Slackbuilds-users] Updates - 20141220.1 In-Reply-To: <20141220192648.GA18846@ilium.andrews-corner.org> References: <5494C54C.3070809@slackbuilds.org> <20141220192648.GA18846@ilium.andrews-corner.org> Message-ID: <54961FB6.50000@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Certainly works with current git FFmpeg and as well with the latest > FFmpeg release 2.5.1. I realise it sounds a little like the 'tail > wagging the dog' but perhaps it is time to update FFmpeg? > > Slackbuilds.org is holding FFmpeg 2.1.5 which is now unmaintained > by the FFmpeg developers, a little rough since it only came out 5 > months ago and was only updated to 2.1.6 in November but that is > the way with FFmpeg... just FYI, ffmpeg is used by many other packages here's a list of packages that depends (only 1st level) on ffmpeg they must be tested against newer ffmpeg before we can have ffmpeg released or else they will be broken audio/kradio audio/lastfm audio/pithos audio/quodlibet audio/soundconverter desktop/ffmpegthumbnailer desktop/recorditnow desktop/ssr games/alephone games/openmw games/vcmi games/wargus graphics/digikam libraries/ffms2 libraries/wxsvg multimedia/bombono-dvd multimedia/cantata multimedia/cinelerra multimedia/devede multimedia/dvd-slideshow multimedia/ffmpeg2theora multimedia/flowblade multimedia/get_iplayer multimedia/guvcview multimedia/imagination multimedia/kino multimedia/lives multimedia/makemkv multimedia/minidlna multimedia/miro multimedia/mlt multimedia/mpv multimedia/oggconvert multimedia/parole multimedia/picard multimedia/radiotray multimedia/ripit multimedia/rosa-media-player multimedia/sinthgunt multimedia/transcode multimedia/winff multimedia/xjadeo multimedia/xvst network/Pafy network/freerdp network/imageshack-uploader network/linphone SlackBuilds/digikam SlackBuilds/ffms2 SlackBuilds/guvcview - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSWH7YACgkQiHuDdNczM4G8JACfczYXOHd+aqls1HPHl4FwB9SF MRQAmwe7YJv51jm2k3Y4fVwGdW9JMHp1 =yh+7 -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sun Dec 21 02:33:06 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 Dec 2014 09:33:06 +0700 Subject: [Slackbuilds-users] 0ad and 0ad-data updates In-Reply-To: <290976228.54972.1419093176567.JavaMail.apache@nm41.abv.bg> References: <290976228.54972.1419093176567.JavaMail.apache@nm41.abv.bg> Message-ID: <54963162.2010809@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I have made some changes for 0ad and 0ad-data. Erik said that he is > busy, so I wonder if somebody else can take a look. > > 0ad: > https://github.com/sbolokanov/slackbuilds-official/tree/master/0ad > > 0ad-data: > https://github.com/sbolokanov/slackbuilds-official/tree/master/0ad-data > > Enet >= 1.3 is now required for 0ad. Hi it would be easier to check against SBo's script if you clone SBo's GIT repo and then make some changes and push a commit in your github account Here's SBo's GIT Repo address: git://slackbuilds.org/slackbuilds.git - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSWMWIACgkQiHuDdNczM4G6JACggTqxeN0fjSeiO4HRAxjCBZ+K RwYAn0srjmsVBljLYKU6iC02gl8k9i6T =aC93 -----END PGP SIGNATURE----- From info at microlinux.fr Sun Dec 21 08:08:52 2014 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 21 Dec 2014 09:08:52 +0100 Subject: [Slackbuilds-users] dirac source unavailable Message-ID: <54968014.8050109@microlinux.fr> Hi, The dirac-1.0.2.tar.gz source tarball is unavailable. The site returns a 503 error. I suggest to change the download URL for a SourceForge mirror. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Sun Dec 21 08:10:14 2014 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 21 Dec 2014 09:10:14 +0100 Subject: [Slackbuilds-users] ffmpeg can't find libilbc Message-ID: <54968066.9030104@microlinux.fr> Hi, I'm currently trying to compile ffmpeg-2.1.5 from SBo. I have all the prerequisites installed. Everything works fine, except for one little detail. FFmpeg can't seem to find libilbc, even though it is installed. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Sun Dec 21 08:12:32 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 Dec 2014 15:12:32 +0700 Subject: [Slackbuilds-users] dirac source unavailable In-Reply-To: <54968014.8050109@microlinux.fr> References: <54968014.8050109@microlinux.fr> Message-ID: <549680F0.1000304@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The dirac-1.0.2.tar.gz source tarball is unavailable. The site > returns a 503 error. I suggest to change the download URL for a > SourceForge mirror. Thanks fixed in my branch already - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSWgPAACgkQiHuDdNczM4F+6ACePNQBnHPQ+RO68YHqltVkulNn K98AoI8mzqUTnlQLf4j+HwudMNLoolQB =ki5L -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sun Dec 21 08:13:55 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 Dec 2014 15:13:55 +0700 Subject: [Slackbuilds-users] ffmpeg can't find libilbc In-Reply-To: <54968066.9030104@microlinux.fr> References: <54968066.9030104@microlinux.fr> Message-ID: <54968143.4000208@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I'm currently trying to compile ffmpeg-2.1.5 from SBo. I have all > the prerequisites installed. Everything works fine, except for one > little detail. FFmpeg can't seem to find libilbc, even though it is > installed. yes, it's probably a result of the latest libilbc that was upgraded in yesterday's public update It seems newer ffmpeg is required to detect newer libilbc, something which is not yet available in our repo for now - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSWgUMACgkQiHuDdNczM4HyGACgisQ7E8TFsK4yZ6q/ioMDj5D7 PYoAoKT5y1G1dZND9hcGG+fOQstAN4vq =RI8t -----END PGP SIGNATURE----- From info at microlinux.fr Sun Dec 21 08:17:56 2014 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 21 Dec 2014 09:17:56 +0100 Subject: [Slackbuilds-users] Problem with download.videolan.org Message-ID: <54968234.2080002@microlinux.fr> Hi, I suggest not to use any download.videolan.org links, and there are quite a few. They admins there can't seem to get their act together. cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Sun Dec 21 08:20:00 2014 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 21 Dec 2014 09:20:00 +0100 Subject: [Slackbuilds-users] Problem with download.videolan.org In-Reply-To: <54968234.2080002@microlinux.fr> References: <54968234.2080002@microlinux.fr> Message-ID: <549682B0.3000001@microlinux.fr> Le 21/12/2014 09:17, Niki Kovacs a ?crit : > Hi, > > I suggest not to use any download.videolan.org links, and there are > quite a few. They admins there can't seem to get their act together. > > cheers, > > Niki One possibility is to use the mirror : http://mirror.ircam.fr/pub/videolan/ -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 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 sbolokanov at abv.bg Sun Dec 21 11:54:06 2014 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Sun, 21 Dec 2014 13:54:06 +0200 (EET) Subject: [Slackbuilds-users] 0ad and 0ad-data updates Message-ID: <1681534527.67867.1419162846807.JavaMail.apache@nm41.abv.bg> It should be better now. Link to commit: https://github.com/sbolokanov/slackbuilds-clone/commit/9a2a76268eec999ba03825d317fc3b8d8fe41e77 -------- ?????????? ????? -------- ??: Willy Sudiarto Raharjo willysr at slackbuilds.org ???????: Re: [Slackbuilds-users] 0ad and 0ad-data updates ??: slackbuilds-users at slackbuilds.org ????????? ??: ??????, 2014, ???????? 21 04:33:06 EET -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I have made some changes for 0ad and 0ad-data. Erik said that he is > busy, so I wonder if somebody else can take a look. > > 0ad: > https://github.com/sbolokanov/slackbuilds-official/tree/master/0ad > > 0ad-data: > https://github.com/sbolokanov/slackbuilds-official/tree/master/0ad-data > > Enet >= 1.3 is now required for 0ad. Hi it would be easier to check against SBo's script if you clone SBo's GIT repo and then make some changes and push a commit in your github account Here's SBo's GIT Repo address: git://slackbuilds.org/slackbuilds.git - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSWMWIACgkQiHuDdNczM4G6JACggTqxeN0fjSeiO4HRAxjCBZ+K RwYAn0srjmsVBljLYKU6iC02gl8k9i6T =aC93 -----END PGP SIGNATURE----- _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ var m3_u = (location.protocol=='https:'?'https://a.abv.bg/www/delivery/ajs.php':'http://a.abv.bg/www/delivery/ajs.php'); var m3_r = Math.floor(Math.random()*99999999999); if (!document.MAX_used) document.MAX_used = ','; document.write (" "); -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Dec 21 13:16:19 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 Dec 2014 20:16:19 +0700 Subject: [Slackbuilds-users] 0ad and 0ad-data updates In-Reply-To: <1681534527.67867.1419162846807.JavaMail.apache@nm41.abv.bg> References: <1681534527.67867.1419162846807.JavaMail.apache@nm41.abv.bg> Message-ID: <14257EAF-7DC7-4928-ABC8-DB25BB13B3A2@slackbuilds.org> > It should be better now. > > Link to commit: > https://github.com/sbolokanov/slackbuilds-clone/commit/9a2a76268eec999ba03825d317fc3b8d8fe41e77 Hi Here's my remark: Please make one commit per app In 0ad's README, no need to spesify mandatory dep, as it will be generated during public update You can spesify optional deps though -- Willy Sudiarto Raharjo -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbolokanov at abv.bg Sun Dec 21 14:24:37 2014 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Sun, 21 Dec 2014 16:24:37 +0200 (EET) Subject: [Slackbuilds-users] 0ad and 0ad-data updates Message-ID: <960776040.70637.1419171877553.JavaMail.apache@nm41.abv.bg> >Hi > >Here's my remark: >Please make one commit per app >In 0ad's README, no need to spesify mandatory dep, as it will be generated during public update >You can spesify optional deps though > >Willy Sudiarto Raharjo It should be better now. (v2) Link to commits: https://github.com/sbolokanov/slackbuilds-clone/commits/master 0ad deps as follow: required at build time: OpenAL gloox enet >= 1.3 optional dep: SDL2 runtime dep: 0ad-data -- ????? ????????? var m3_u = (location.protocol=='https:'?'https://a.abv.bg/www/delivery/ajs.php':'http://a.abv.bg/www/delivery/ajs.php'); var m3_r = Math.floor(Math.random()*99999999999); if (!document.MAX_used) document.MAX_used = ','; document.write (" "); -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Sun Dec 21 14:51:09 2014 From: miguel at thedeanda.com (Miguel De Anda) Date: Sun, 21 Dec 2014 06:51:09 -0800 Subject: [Slackbuilds-users] ffmpeg can't find libilbc In-Reply-To: <54968066.9030104@microlinux.fr> References: <54968066.9030104@microlinux.fr> Message-ID: Not sure if it will help in this case but some slackbuilds require 'su -' instead of just 'su' before running the script. On Dec 21, 2014 12:10 AM, "Niki Kovacs" wrote: > Hi, > > I'm currently trying to compile ffmpeg-2.1.5 from SBo. I have all the > prerequisites installed. Everything works fine, except for one little > detail. FFmpeg can't seem to find libilbc, even though it is installed. > > Cheers, > > Niki > -- > Microlinux - Solutions informatiques 100% Linux et logiciels libres > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Sun Dec 21 14:51:10 2014 From: miguel at thedeanda.com (Miguel De Anda) Date: Sun, 21 Dec 2014 06:51:10 -0800 Subject: [Slackbuilds-users] ffmpeg can't find libilbc In-Reply-To: <54968066.9030104@microlinux.fr> References: <54968066.9030104@microlinux.fr> Message-ID: Not sure if it will help in this case but some slackbuilds require 'su -' instead of just 'su' before running the script. On Dec 21, 2014 12:10 AM, "Niki Kovacs" wrote: > Hi, > > I'm currently trying to compile ffmpeg-2.1.5 from SBo. I have all the > prerequisites installed. Everything works fine, except for one little > detail. FFmpeg can't seem to find libilbc, even though it is installed. > > Cheers, > > Niki > -- > Microlinux - Solutions informatiques 100% Linux et logiciels libres > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hba.nihilismus at gmail.com Sun Dec 21 18:52:03 2014 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sun, 21 Dec 2014 12:52:03 -0600 Subject: [Slackbuilds-users] ffmpeg can't find libilbc In-Reply-To: <54968066.9030104@microlinux.fr> References: <54968066.9030104@microlinux.fr> Message-ID: On Sun, Dec 21, 2014 at 2:10 AM, Niki Kovacs wrote: > Hi, > > I'm currently trying to compile ffmpeg-2.1.5 from SBo. I have all the > prerequisites installed. Everything works fine, except for one little > detail. FFmpeg can't seem to find libilbc, even though it is installed. Topic related (read its answers): http://lists.slackbuilds.org/pipermail/slackbuilds-users/2014-December/013288.html -- 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 pprkut at slackbuilds.org Sun Dec 21 20:14:24 2014 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Sun, 21 Dec 2014 21:14:24 +0100 Subject: [Slackbuilds-users] ffmpeg can't find libilbc In-Reply-To: References: <54968066.9030104@microlinux.fr> Message-ID: <1442610.KtepAC6HoB@titania> On Sunday 21 December 2014 12:52:03 Antonio Hern?ndez Blas wrote: > On Sun, Dec 21, 2014 at 2:10 AM, Niki Kovacs wrote: > > Hi, > > > > I'm currently trying to compile ffmpeg-2.1.5 from SBo. I have all the > > prerequisites installed. Everything works fine, except for one little > > detail. FFmpeg can't seem to find libilbc, even though it is installed. > > Topic related (read its answers): > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2014-December/01328 > 8.html I just pushed a fix for this to my updates branch. Thanks for reporting :) Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: This is a digitally signed message part. URL: From pprkut at slackbuilds.org Sun Dec 21 20:17:42 2014 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Sun, 21 Dec 2014 21:17:42 +0100 Subject: [Slackbuilds-users] Slackbuilds.org - Virtualbox Package - /dev/vboxdrvu, /dev/vboxnetctl permissions fix In-Reply-To: References: Message-ID: <12236228.rEpEQYhE81@titania> On Tuesday 16 December 2014 13:26:38 janusz.kusnierek at akron.net.pl wrote: > Hello, > > [..] > > Permissions of the /dev/vboxdrvu and /dev/vboxnetctl are too restrictive > for regular user, so I've added another rule file called > 20-virtualbox2.rules with: > > ------ > KERNEL=="vboxdrvu", NAME="vboxdrvu", OWNER="root", GROUP="vboxusers", > MODE="0660" > KERNEL=="vboxnetctl", NAME="vboxnetctl", OWNER="root",GROUP="vboxusers", > MODE="0660" > ------ > > Could You apply this fix (or similar) in Your scripts? > Thank You :) Thank you for the heads-up! I completely missed this. I pushed a fix for this to my updates branch, but it's slightly different to match what the binary installer is doing :) Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: This is a digitally signed message part. URL: From info at microlinux.fr Mon Dec 22 04:52:10 2014 From: info at microlinux.fr (Niki Kovacs) Date: Mon, 22 Dec 2014 05:52:10 +0100 Subject: [Slackbuilds-users] ffmpeg can't find libilbc In-Reply-To: References: <54968066.9030104@microlinux.fr> Message-ID: <5497A37A.9040508@microlinux.fr> Le 21/12/2014 15:51, Miguel De Anda a ?crit : > Not sure if it will help in this case but some slackbuilds require 'su > -' instead of just 'su' before running the script. I'd even say all of them :o) -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 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 hostmaster at slackonly.com Mon Dec 22 15:51:38 2014 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Mon, 22 Dec 2014 17:51:38 +0200 Subject: [Slackbuilds-users] awstats Message-ID: <54983E0A.1000703@slackonly.com> Hi, In awstats httpd-awstats.conf the settings is for apache 2.2 as a result all images request returning error 403, and the images are not displayed on the awstats page... This settings is also in the awstats docs page: http://www.awstats.org/docs/awstats_setup.html in apache 2.4must be: # This is to permit URL access to scripts/files in AWStats directory. # # Allowing access only via local machine may be too restrictive so you can # set Require ip directive below to allow access to AWStats # via your local LAN. Options FollowSymLinks ExecCGI AllowOverride None - Order allow,deny - Allow from all + Require all granted https://httpd.apache.org/docs/2.4/upgrading.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruben at orgizm.net Mon Dec 22 18:55:13 2014 From: ruben at orgizm.net (Ruben Schuller) Date: Mon, 22 Dec 2014 19:55:13 +0100 Subject: [Slackbuilds-users] MD5 hashes Message-ID: <20141222195513.388f15ac@kiwi> Hi! Are there any plans to change the hashing algorithm from MD5 to a hash algorithm for which collisions are not (so easy) to generate? Maybe just introduce an additional field for SHA256/512 to the info file? Maybe this would break some of the helper tools, but those errors should be not hard to fix, I guess. Greetings, Ruben From ml at mareichelt.com Mon Dec 22 20:21:17 2014 From: ml at mareichelt.com (Markus Reichelt) Date: Mon, 22 Dec 2014 21:21:17 +0100 Subject: [Slackbuilds-users] pysetuptools 8 implements PEP 440 Message-ID: <20141222202117.GA24591@pc21.mareichelt.com> Hi, just a heads-up wrt pysetuptools 8+ #tahoe-lafs on freenode: setuptools 8 implements PEP 440 PEP 440 makes the meaning of , change from "a bunch of arbitrary confusing crap that PJE invented in the past" to "AND" related: https://gist.github.com/kylemanna/a22e7c37e5ff1f9286c2 tl;dr: if you can, keep pysetuptools <8 M. From sbolokanov at abv.bg Mon Dec 22 21:25:18 2014 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Mon, 22 Dec 2014 23:25:18 +0200 (EET) Subject: [Slackbuilds-users] meld3 patch Message-ID: <1946446945.42127.1419283518783.JavaMail.apache@nm41.abv.bg> Hello, just want to report that there is a meld3 patch. It is fixing a problem with meld, when saving patches with bulgarian letters (cyrillic). See attachment. -- ????? ????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: utf8.patch Type: application/octet-stream Size: 357 bytes Desc: not available URL: From jvogel4 at stny.rr.com Mon Dec 22 21:40:05 2014 From: jvogel4 at stny.rr.com (John Vogel) Date: Mon, 22 Dec 2014 16:40:05 -0500 Subject: [Slackbuilds-users] Updates - 20141220.1 In-Reply-To: <54961FB6.50000@slackbuilds.org> References: <5494C54C.3070809@slackbuilds.org> <20141220192648.GA18846@ilium.andrews-corner.org> <54961FB6.50000@slackbuilds.org> Message-ID: <20141222164005.2a8fb560@stygian.lan> On Sun, 21 Dec 2014 08:17:42 +0700 Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Certainly works with current git FFmpeg and as well with the latest > > FFmpeg release 2.5.1. I realise it sounds a little like the 'tail > > wagging the dog' but perhaps it is time to update FFmpeg? > > > > Slackbuilds.org is holding FFmpeg 2.1.5 which is now unmaintained > > by the FFmpeg developers, a little rough since it only came out 5 > > months ago and was only updated to 2.1.6 in November but that is > > the way with FFmpeg... > > just FYI, ffmpeg is used by many other packages > here's a list of packages that depends (only 1st level) on ffmpeg > they must be tested against newer ffmpeg before we can have ffmpeg > released or else they will be broken > > audio/kradio > audio/lastfm > audio/pithos > audio/quodlibet > audio/soundconverter > desktop/ffmpegthumbnailer > desktop/recorditnow > desktop/ssr > games/alephone > games/openmw > games/vcmi > games/wargus > graphics/digikam > libraries/ffms2 > libraries/wxsvg > multimedia/bombono-dvd > multimedia/cantata > multimedia/cinelerra > multimedia/devede > multimedia/dvd-slideshow > multimedia/ffmpeg2theora > multimedia/flowblade > multimedia/get_iplayer > multimedia/guvcview > multimedia/imagination > multimedia/kino > multimedia/lives > multimedia/makemkv > multimedia/minidlna > multimedia/miro > multimedia/mlt > multimedia/mpv > multimedia/oggconvert > multimedia/parole > multimedia/picard > multimedia/radiotray > multimedia/ripit > multimedia/rosa-media-player > multimedia/sinthgunt > multimedia/transcode > multimedia/winff > multimedia/xjadeo > multimedia/xvst > network/Pafy > network/freerdp > network/imageshack-uploader > network/linphone > SlackBuilds/digikam > SlackBuilds/ffms2 > SlackBuilds/guvcview > > > - -- I'm not clear what version of ffmpeg we should be testing against. There are several to choose from: 2.1.6, 2.2.11, 2.3.5, 2.4.5, 2.5.1 I willing to start testing, but it would be nice to know in advance if there is a preferred target. From willysr at slackbuilds.org Tue Dec 23 00:50:33 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 23 Dec 2014 07:50:33 +0700 Subject: [Slackbuilds-users] meld3 patch In-Reply-To: <1946446945.42127.1419283518783.JavaMail.apache@nm41.abv.bg> References: <1946446945.42127.1419283518783.JavaMail.apache@nm41.abv.bg> Message-ID: <5498BC59.4030208@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > just want to report that there is a meld3 patch. It is fixing a > problem with meld, when saving patches with bulgarian letters > (cyrillic). Thanks pushed to my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSYvFgACgkQiHuDdNczM4ECsACgilnWK4Dur4XQhOFTzNWrMTpd 5u8AoJcRhAGgqlJAqnOp6/1ZlZRlPWH4 =Y2BL -----END PGP SIGNATURE----- From willysr at slackbuilds.org Tue Dec 23 02:15:13 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 23 Dec 2014 09:15:13 +0700 Subject: [Slackbuilds-users] Errot in robomongo Slackbuiid Script In-Reply-To: References: <549567D3.5040503@laprjns.com> Message-ID: <5498D031.9090206@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Thanks I'll take a look and update. Did you have issues for x86 or > 64? >> Running the robomongo.Slackbuild script results in the following >> error: >> >> tar: >> /usr/src/slapt-src/development/robomongo/robomongo-0.8.4-.tar.gz: >> >> Cannot open: No such file or directory >> tar: Error is not recoverable: exiting now fakeroot -- sh >> robomongo.SlackBuild Failed >> >> >> Line 38 of the Slackbuild has an error in the file name path. It >> is: >> >> tar xvf $CWD/$PRGNAM-$VERSION-$ANAME.tar.gz >> >> It should be: >> >> tar xvf $CWD/$PRGNAM-$VERSION-$ARCH.tar.gz Fixed this on my branch http://slackbuilds.org/cgit/slackbuilds/log/?h=willysr - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSY0DEACgkQiHuDdNczM4FcKQCfQoygwLi71Ui4ZbPWgTCh/jYi fTQAnRYaZ6cCyMjhMRLeF8A9P1HJtYdm =SiDg -----END PGP SIGNATURE----- From info at microlinux.fr Tue Dec 23 13:38:52 2014 From: info at microlinux.fr (Niki Kovacs) Date: Tue, 23 Dec 2014 14:38:52 +0100 Subject: [Slackbuilds-users] dirac source unavailable In-Reply-To: <549680F0.1000304@slackbuilds.org> References: <54968014.8050109@microlinux.fr> <549680F0.1000304@slackbuilds.org> Message-ID: <5499706C.5030906@microlinux.fr> Le 21/12/2014 09:12, Willy Sudiarto Raharjo a ?crit : > Thanks > fixed in my branch already What URL do you use ? -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Thu Dec 25 00:46:10 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 25 Dec 2014 07:46:10 +0700 Subject: [Slackbuilds-users] Updates - 20141220.1 In-Reply-To: <20141222164005.2a8fb560@stygian.lan> References: <5494C54C.3070809@slackbuilds.org> <20141220192648.GA18846@ilium.andrews-corner.org> <54961FB6.50000@slackbuilds.org> <20141222164005.2a8fb560@stygian.lan> Message-ID: <549B5E52.70504@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I'm not clear what version of ffmpeg we should be testing against. > There are several to choose from: 2.1.6, 2.2.11, 2.3.5, 2.4.5, > 2.5.1 I willing to start testing, but it would be nice to know in > advance if there is a preferred target. That's up to pprkut as the maintainer of ffmpeg of which version should be used for the next cycle - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSbXlIACgkQiHuDdNczM4FMZgCfQn7NEu2D8TMQkV0wnLLtUD12 hUMAnjzeb6md03ZTCiGs0+tYz2h90QbU =90em -----END PGP SIGNATURE----- From rworkman at slackbuilds.org Thu Dec 25 01:59:29 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 24 Dec 2014 19:59:29 -0600 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: References: <20141216163552.5bece862@home.rlworkman.net> Message-ID: <20141224195929.759f8db4@home.rlworkman.net> On Tue, 16 Dec 2014 19:18:54 -0800 King Beowulf wrote: > Let me take a crack at it since I need to submit an update anyway. > Now that the new kitchen windows are in, I just need to finish the > trim. (For some reason I always end up fixing the house when on > "vacation") Since Thomas already had something working and since I had a bit of time to play here, I went ahead and did this along with an update to 2.2.0. How's this look? http://slackbuilds.org/cgit/slackbuilds/commit/?h=qemu -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Dec 25 02:15:40 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 25 Dec 2014 09:15:40 +0700 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <20141224195929.759f8db4@home.rlworkman.net> References: <20141216163552.5bece862@home.rlworkman.net> <20141224195929.759f8db4@home.rlworkman.net> Message-ID: <549B734C.9070502@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Since Thomas already had something working and since I had a bit of > time to play here, I went ahead and did this along with an update > to 2.2.0. How's this look? > > http://slackbuilds.org/cgit/slackbuilds/commit/?h=qemu since -current is a moving target, i propose to self-host the libusb source in harrier - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSbc0wACgkQiHuDdNczM4Ei7gCfSYuuHn9DUxAMang2LHyyxIez F54AnigSZTRMNLF+137JxfYEv9XHCC9q =qAOc -----END PGP SIGNATURE----- From rworkman at slackbuilds.org Thu Dec 25 03:16:38 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 24 Dec 2014 21:16:38 -0600 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <549B734C.9070502@slackbuilds.org> References: <20141216163552.5bece862@home.rlworkman.net> <20141224195929.759f8db4@home.rlworkman.net> <549B734C.9070502@slackbuilds.org> Message-ID: <20141224211638.5f5be00a@home.rlworkman.net> On Thu, 25 Dec 2014 09:15:40 +0700 Willy Sudiarto Raharjo wrote: > > Since Thomas already had something working and since I had a bit of > > time to play here, I went ahead and did this along with an update > > to 2.2.0. How's this look? > > > > http://slackbuilds.org/cgit/slackbuilds/commit/?h=qemu > > since -current is a moving target, i propose to self-host the libusb > source in harrier Fair enough ; done. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Thu Dec 25 08:28:40 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Dec 2014 02:28:40 -0600 Subject: [Slackbuilds-users] Updates - 20141225.1 Message-ID: <20141225022840.63b0a1c8@home.rlworkman.net> Thu Dec 25 08:14:50 UTC 2014 academic/omlibraries: Updated for version svn20141218. academic/openmodelica: Remove fakeroot. audio/apulse: Fix build. audio/google-musicmanager: Updated for version 1.0.129.6633. desktop/XDecorations: Added (eye candy). desktop/conky-manager: Added (Conky front-end). desktop/ffmpegthumbnailer: Updated for version 2.0.9. development/android-tools: Added (adb and fastboot tools) development/cudatoolkit: Updated for version 6.5.14. development/ltrace: Added (library call trace utility). development/meld3: Added patch to work with UTF-8. development/nexus: Updated for version 2.11.1_01. development/robomongo: Fix script. development/xdebug: Updated for version 2.2.6. games/0ad-data: Updated for version 0.0.17. games/0ad: Updated for version 0.0.17. libraries/chromaprint: Updated for version 1.2. libraries/jsoncpp: Added (JSON C++ library) libraries/libaacs: Update DOWNLOAD url. libraries/libbdplus: Update DOWNLOAD url. libraries/libbluray: Update DOWNLOAD url. libraries/libcec: Updated for version 2.2.0. libraries/libcli: Updated for version 1.9.7. libraries/libdvbcsa: Added (DVB Common Scrambling Algorithm). libraries/libmms: Updated for version 0.6.4. libraries/libmsiecf: Added (libYAL MSIE Cache library) libraries/libnfs: Updated for version 1.9.6. libraries/libnice: Updated for version 0.1.8. libraries/libvirt: Make rc.libvirt more robust libraries/libvirt: add comments re VIRTUSERS group wrt qemu libraries/openjpeg: Updated for version 1.5.2. libraries/php-imagick: Fix headers not installing to DESTDIR. libraries/php-pgsql: Updated for version 5.4.34. libraries/tbb: Updated for version 4.3u2. misc/protobuf: Updated for version 2.6.1. misc/samdump2: Added (Windows password dumper). multimedia/dirac: Update DOWNLOAD url. multimedia/ffmpeg: Fix building with new libilbc. multimedia/gpac: Updated for version svn_r5564. multimedia/vlc: Update DOWNLOAD url. multimedia/w_scan: Updated for version 20141122. multimedia/x264: Update DOWNLOAD url. multimedia/xvidcore: Updated for version 1.3.3. network/ClusterSSH: Updated for version 4.03_04. network/enet: Updated for version 1.3.12. network/keybase-client: Added (keybase client). network/phpmyadmin: Updated for version 4.3.3. network/tribler: Added (video streaming and bittorrent client). network/wildfly: Updated for version 8.2.0. perl/perl-File-Tail: Updated for version 1.0. perl/perl-Term-ReadLine-Gnu: Updated for version 1.25. perl/perl-Test-Simple: Updated for version 1.001012. perl/perl-Test-Trap: Updated for version 0.3.0. perl/perl-cairo: Update MD5SUM. perl/perl-extutils-depends: Updated for version 0.402. perl/perl-glib: Updated for version 1.306. perl/perl-gnome2-vfs: New maintainer. perl/perl-gnome2-wnck: New maintainer. perl/perl-goo-canvas: New maintainer. perl/perl-gtk2-imageview: New maintainer. perl/perl-gtk2: Updated for version 1.2493 + new maintainer. perl/perl-html-form: New maintainer. perl/perl-http-response-encoding: New maintainer. perl/perl-http-server-simple: New maintainer. perl/perl-net-dbus: New maintainer. perl/perl-pango: Updated for version 1.226 + new maintainer. python/dfvfs: Added (Digital Forensics Virtual File System) python/gmpy: Added (multi-precision arithmetic). python/python-MonthDelta: Added (Pythonic Module). python/pytsk: Added (Python binding for the SleuthKit) python/stem: Updated for version 1.3.0. ruby/heroku-client: Updated for version 3.21.3. system/adobe-source-han-sans-fonts: Updated for version 1.001R. system/ksh-openbsd: Updated for version 20141220. system/phoronix-test-suite: Updated for version 5.4.1. system/profile-sync-daemon: Updated for version 5.55. system/sleuthkit: Fix external type errors with EWF system/virtualbox: Sync udev rules with binary release. -------------- 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 Thu Dec 25 19:50:21 2014 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 25 Dec 2014 11:50:21 -0800 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <20141224211638.5f5be00a@home.rlworkman.net> References: <20141216163552.5bece862@home.rlworkman.net> <20141224195929.759f8db4@home.rlworkman.net> <549B734C.9070502@slackbuilds.org> <20141224211638.5f5be00a@home.rlworkman.net> Message-ID: <549C6A7D.4070508@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/24/2014 07:16 PM, Robby Workman wrote: > On Thu, 25 Dec 2014 09:15:40 +0700 Willy Sudiarto Raharjo > wrote: > >>> Since Thomas already had something working and since I had a >>> bit of time to play here, I went ahead and did this along with >>> an update to 2.2.0. How's this look? >>> >>> http://slackbuilds.org/cgit/slackbuilds/commit/?h=qemu >> >> since -current is a moving target, i propose to self-host the >> libusb source in harrier > > > Fair enough ; done. > > -RW > Spiffy. How about we add a libusb present sanity check in case in case someone what's to skip USB pasthrough and not build a new libusb? For example, https://gitorious.org/kingbeowulf/sbo-slackbuilds/commit/70a11441a757682ae647b29fa8cd25c8de269513 I might not have that quite right, so advise as needed. - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlScansACgkQXvwMaW61dLcgegCfRvcXsc0UavEMf7ndWT52aVbe vroAnRnpzHQjOpICB4NDDITrXO4hGbCs =u/pL -----END PGP SIGNATURE----- From genghiskhan at gmx.ca Fri Dec 26 09:00:35 2014 From: genghiskhan at gmx.ca (Genghis Khan) Date: Fri, 26 Dec 2014 10:00:35 +0100 Subject: [Slackbuilds-users] Fontconfig warning with package culmus (was: Error while installing package culmus) Message-ID: File /etc/fonts/conf.d/61-culmus.conf appears to be mis-configured. # spkg -i /tmp/culmus-0.130-noarch-2_SBo.tgz Installing package culmus-0.130-noarch-2_SBo... | culmus (Hebrew scalable fonts) | | The Culmus project aims at providing the Hebrew-speaking | GNU/Linux and Unix community with a basic collection of | Hebrew fonts for X Windows. | | | for more info: http://culmus.sourceforge.net | | | | | Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 21: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 43: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 53: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 64: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 75: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 86: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 98: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 110: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", line 120: Having multiple values in isn't supported and may not work as expected install/doinst.sh: line 18: syntax error: unexpected end of file WARNING: Post-installation script failed. (256) On Sun, 7 Dec 2014 01:14:12 -0600 Robby Workman wrote: > On Mon, 1 Dec 2014 14:02:39 +0100 > "Genghis Khan" wrote: > > > I am using slapt-src with spkg under Salix OS. > > > > > > Slackware > > package /usr/src/slapt-src/system/culmus/culmus-0.130-noarch-1_SBo.txz > > created. > > > > Installing package culmus-0.130-noarch-1_SBo... > > | culmus (Hebrew scalable fonts) > > | > > | The Culmus project aims at providing the Hebrew-speaking > > | GNU/Linux and Unix community with a basic collection of > > | Hebrew fonts for X Windows. > > | > > | > > | for more info: http://culmus.sourceforge.net > > | > > | > > | > > | > > | > > ERROR: Package contains symlink with unsafe path. > > (/etc/fonts/conf.d/61-culmus.conf) ERROR: Installation script > > processing failed. ERROR: Package installation failed! > > /sbin/spkg -u --reinstall --install-new > > culmus-0.130-noarch-1_SBo.txz Failed > > _______________________________________________ > > > Good catch. > > Fixed in this commit, slated for next public update: > > commit d8b2310bae83a1a18748335de00e49fd8eb9ae03 > Author: Robby Workman > Date: Sun Dec 7 01:12:02 2014 -0600 > > system/culmus: Fix font installation and doinst.sh paths > > Signed-off-by: Robby Workman > From willysr at slackbuilds.org Fri Dec 26 17:06:04 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 Dec 2014 00:06:04 +0700 Subject: [Slackbuilds-users] Fontconfig warning with package culmus (was: Error while installing package culmus) In-Reply-To: References: Message-ID: <549D957C.1040103@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > File /etc/fonts/conf.d/61-culmus.conf appears to be > mis-configured. > > # spkg -i /tmp/culmus-0.130-noarch-2_SBo.tgz Installing package > culmus-0.130-noarch-2_SBo... | culmus (Hebrew scalable fonts) | | > The Culmus project aims at providing the Hebrew-speaking | > GNU/Linux and Unix community with a basic collection of | Hebrew > fonts for X Windows. | | | for more info: > http://culmus.sourceforge.net | | | | | Fontconfig warning: > "/etc/fonts/conf.d/61-culmus.conf", line 21: Having multiple values > in isn't supported and may not work as expected Fontconfig > warning: "/etc/fonts/conf.d/61-culmus.conf", line 43: Having > multiple values in isn't supported and may not work as > expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", > line 53: Having multiple values in isn't supported and may > not work as expected Fontconfig warning: > "/etc/fonts/conf.d/61-culmus.conf", line 64: Having multiple values > in isn't supported and may not work as expected Fontconfig > warning: "/etc/fonts/conf.d/61-culmus.conf", line 75: Having > multiple values in isn't supported and may not work as > expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", > line 86: Having multiple values in isn't supported and may > not work as expected Fontconfig warning: > "/etc/fonts/conf.d/61-culmus.conf", line 98: Having multiple values > in isn't supported and may not work as expected Fontconfig > warning: "/etc/fonts/conf.d/61-culmus.conf", line 110: Having > multiple values in isn't supported and may not work as > expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", > line 120: Having multiple values in isn't supported and may > not work as expected install/doinst.sh: line 18: syntax error: > unexpected end of file WARNING: Post-installation script failed. > (256) Fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSdlXwACgkQiHuDdNczM4EnrQCaAkPvY1YDzX+ONdBTBJPCAzb6 DIIAoKjI+YsPs156JNfqhW0geGDV/O+t =KE5Y -----END PGP SIGNATURE----- From willysr at slackbuilds.org Fri Dec 26 18:20:19 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 Dec 2014 01:20:19 +0700 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <549C6A7D.4070508@gmail.com> References: <20141216163552.5bece862@home.rlworkman.net> <20141224195929.759f8db4@home.rlworkman.net> <549B734C.9070502@slackbuilds.org> <20141224211638.5f5be00a@home.rlworkman.net> <549C6A7D.4070508@gmail.com> Message-ID: <549DA6E3.9020200@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Spiffy. How about we add a libusb present sanity check in case in > case someone what's to skip USB pasthrough and not build a new > libusb? For example, > > https://gitorious.org/kingbeowulf/sbo-slackbuilds/commit/70a11441a757682ae647b29fa8cd25c8de269513 > > I might not have that quite right, so advise as needed. if the check is based on source existence, then all users using (semi) automated tools, such as sbopkg will surely build USB passthrough as it will download all source mentioned in DOWNLOAD or DOWNLOAD_x86_64 - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSdpuMACgkQiHuDdNczM4FyCQCfYHwUD4xAMmsm9HTXqdwctCIV 0G4AnRv1ycMYsav/pvHyoc3vGzX0uqZy =lQxn -----END PGP SIGNATURE----- From kingbeowulf at gmail.com Sat Dec 27 00:47:31 2014 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 26 Dec 2014 16:47:31 -0800 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <549DA6E3.9020200@slackbuilds.org> References: <20141216163552.5bece862@home.rlworkman.net> <20141224195929.759f8db4@home.rlworkman.net> <549B734C.9070502@slackbuilds.org> <20141224211638.5f5be00a@home.rlworkman.net> <549C6A7D.4070508@gmail.com> <549DA6E3.9020200@slackbuilds.org> Message-ID: <549E01A3.9080904@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/26/2014 10:20 AM, Willy Sudiarto Raharjo wrote: >> Spiffy. How about we add a libusb present sanity check in case >> in case someone what's to skip USB pasthrough and not build a >> new libusb? For example, > >> https://gitorious.org/kingbeowulf/sbo-slackbuilds/commit/70a11441a757682ae647b29fa8cd25c8de269513 > >> I might not have that quite right, so advise as needed. > > if the check is based on source existence, then all users using > (semi) automated tools, such as sbopkg will surely build USB > passthrough as it will download all source mentioned in DOWNLOAD or > DOWNLOAD_x86_64 > > > -- Willy Sudiarto Raharjo I wasn't really worrying about the "automagical tools" folks, just a check for those, like me, that build stuff manually, only to have the script fail due to a missing tarball. I've added a note in the README to provide a reminder, but who reads those? So the question is, (1) do we want to enforce the use of the newer static libusb and thus have the script fail if libusb source is missing or should the script continue on the assumption that libusb is not needed? (2) have users upgrade the libusb in 14.1, i.e, libusb-1.0.19-sbo as a qemu dependency? Are there 14.1 packages dependent on libusb that upgrading could break? In the long run, #2 might be better...depending on when -current goes - -stable. Leaving the SBo script as vanilla as possible will make the SBo transition easier when we all upgrade. - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSeAaEACgkQXvwMaW61dLdg1ACeOLhM1q7kZp8XWQ1EW5BAKtqu J0kAoKrsmgSwd8uxHS9vj5ab2xbIPHBF =TlJF -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Dec 27 00:56:20 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 Dec 2014 07:56:20 +0700 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <549E01A3.9080904@gmail.com> References: <20141216163552.5bece862@home.rlworkman.net> <20141224195929.759f8db4@home.rlworkman.net> <549B734C.9070502@slackbuilds.org> <20141224211638.5f5be00a@home.rlworkman.net> <549C6A7D.4070508@gmail.com> <549DA6E3.9020200@slackbuilds.org> <549E01A3.9080904@gmail.com> Message-ID: <549E03B4.1000405@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I wasn't really worrying about the "automagical tools" folks, just > a check for those, like me, that build stuff manually, only to have > the script fail due to a missing tarball. I've added a note in the > README to provide a reminder, but who reads those? > > So the question is, > > (1) do we want to enforce the use of the newer static libusb and > thus have the script fail if libusb source is missing or should the > script continue on the assumption that libusb is not needed? > > (2) have users upgrade the libusb in 14.1, i.e, libusb-1.0.19-sbo > as a qemu dependency? Are there 14.1 packages dependent on libusb > that upgrading could break? > > In the long run, #2 might be better...depending on when -current > goes -stable. Leaving the SBo script as vanilla as possible will > make the SBo transition easier when we all upgrade. what if we provide a variable check, such as LIBUSB=yes sh ./qemu.SlackBuild will build libusb-0.19 statically, otherwise, it will not be built - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSeA7QACgkQiHuDdNczM4FXzgCeOsgcII+9jd7gqjiVqdWmwWng g4wAn1ddRa1FhinOkvD3NtyRIzfgAiCi =gi/U -----END PGP SIGNATURE----- From jvogel4 at stny.rr.com Sat Dec 27 09:43:42 2014 From: jvogel4 at stny.rr.com (John Vogel) Date: Sat, 27 Dec 2014 04:43:42 -0500 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <549E03B4.1000405@slackbuilds.org> References: <20141216163552.5bece862@home.rlworkman.net> <20141224195929.759f8db4@home.rlworkman.net> <549B734C.9070502@slackbuilds.org> <20141224211638.5f5be00a@home.rlworkman.net> <549C6A7D.4070508@gmail.com> <549DA6E3.9020200@slackbuilds.org> <549E01A3.9080904@gmail.com> <549E03B4.1000405@slackbuilds.org> Message-ID: <20141227044342.18d35bf3@stygian.lan> On Sat, 27 Dec 2014 07:56:20 +0700 Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I wasn't really worrying about the "automagical tools" folks, just > > a check for those, like me, that build stuff manually, only to have > > the script fail due to a missing tarball. I've added a note in the > > README to provide a reminder, but who reads those? > > > > So the question is, > > > > (1) do we want to enforce the use of the newer static libusb and > > thus have the script fail if libusb source is missing or should the > > script continue on the assumption that libusb is not needed? > > > > (2) have users upgrade the libusb in 14.1, i.e, libusb-1.0.19-sbo > > as a qemu dependency? Are there 14.1 packages dependent on libusb > > that upgrading could break? > > > > In the long run, #2 might be better...depending on when -current > > goes -stable. Leaving the SBo script as vanilla as possible will > > make the SBo transition easier when we all upgrade. > > what if we provide a variable check, such as LIBUSB=yes sh > ./qemu.SlackBuild will build libusb-0.19 statically, otherwise, it > will not be built +1 From rworkman at slackbuilds.org Sat Dec 27 18:51:07 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 27 Dec 2014 12:51:07 -0600 Subject: [Slackbuilds-users] Fontconfig warning with package culmus (was: Error while installing package culmus) In-Reply-To: <549D957C.1040103@slackbuilds.org> References: <549D957C.1040103@slackbuilds.org> Message-ID: <20141227125107.2c2672aa@home.rlworkman.net> On Sat, 27 Dec 2014 00:06:04 +0700 Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > File /etc/fonts/conf.d/61-culmus.conf appears to be > > mis-configured. > > > > # spkg -i /tmp/culmus-0.130-noarch-2_SBo.tgz Installing package > > culmus-0.130-noarch-2_SBo... | culmus (Hebrew scalable fonts) | | > > The Culmus project aims at providing the Hebrew-speaking | > > GNU/Linux and Unix community with a basic collection of | Hebrew > > fonts for X Windows. | | | for more info: > > http://culmus.sourceforge.net | | | | | Fontconfig warning: > > "/etc/fonts/conf.d/61-culmus.conf", line 21: Having multiple values > > in isn't supported and may not work as expected Fontconfig > > warning: "/etc/fonts/conf.d/61-culmus.conf", line 43: Having > > multiple values in isn't supported and may not work as > > expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", > > line 53: Having multiple values in isn't supported and may > > not work as expected Fontconfig warning: > > "/etc/fonts/conf.d/61-culmus.conf", line 64: Having multiple values > > in isn't supported and may not work as expected Fontconfig > > warning: "/etc/fonts/conf.d/61-culmus.conf", line 75: Having > > multiple values in isn't supported and may not work as > > expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", > > line 86: Having multiple values in isn't supported and may > > not work as expected Fontconfig warning: > > "/etc/fonts/conf.d/61-culmus.conf", line 98: Having multiple values > > in isn't supported and may not work as expected Fontconfig > > warning: "/etc/fonts/conf.d/61-culmus.conf", line 110: Having > > multiple values in isn't supported and may not work as > > expected Fontconfig warning: "/etc/fonts/conf.d/61-culmus.conf", > > line 120: Having multiple values in isn't supported and may > > not work as expected install/doinst.sh: line 18: syntax error: > > unexpected end of file WARNING: Post-installation script failed. > > (256) > > Fixed in my branch The fontconfig warnings are fixed in my branch: commit 9c1851b5b958d70c2cb2001b7885dec151488a54 Author: Robby Workman Date: Sat Dec 27 12:47:09 2014 -0600 system/culums: Fixup fontconfig warnings Thanks to Ghengis Khan. Signed-off-by: Robby Workman -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Dec 27 18:55:16 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 28 Dec 2014 01:55:16 +0700 Subject: [Slackbuilds-users] Fontconfig warning with package culmus In-Reply-To: <20141227125107.2c2672aa@home.rlworkman.net> References: <549D957C.1040103@slackbuilds.org> <20141227125107.2c2672aa@home.rlworkman.net> Message-ID: <549F0094.4010508@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The fontconfig warnings are fixed in my branch: > > commit 9c1851b5b958d70c2cb2001b7885dec151488a54 Author: Robby > Workman Date: Sat Dec 27 12:47:09 > 2014 -0600 > > system/culums: Fixup fontconfig warnings > > Thanks to Ghengis Khan. > > Signed-off-by: Robby Workman you need to take care of doinst.sh as well there's a missing "fi" in the second if then block Should i remove my commit? - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSfAJMACgkQiHuDdNczM4Gp4QCfc8M2z/Xc4RvMdJWXUCRG+08b aS0AmgKJqeVbuCu1z0dd17tACxmVS/er =wYB/ -----END PGP SIGNATURE----- From rworkman at slackbuilds.org Sat Dec 27 19:17:23 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 27 Dec 2014 13:17:23 -0600 Subject: [Slackbuilds-users] qemu annotations In-Reply-To: <549E03B4.1000405@slackbuilds.org> References: <20141216163552.5bece862@home.rlworkman.net> <20141224195929.759f8db4@home.rlworkman.net> <549B734C.9070502@slackbuilds.org> <20141224211638.5f5be00a@home.rlworkman.net> <549C6A7D.4070508@gmail.com> <549DA6E3.9020200@slackbuilds.org> <549E01A3.9080904@gmail.com> <549E03B4.1000405@slackbuilds.org> Message-ID: <20141227131723.2442ef7e@home.rlworkman.net> On Sat, 27 Dec 2014 07:56:20 +0700 Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I wasn't really worrying about the "automagical tools" folks, just > > a check for those, like me, that build stuff manually, only to have > > the script fail due to a missing tarball. I've added a note in the > > README to provide a reminder, but who reads those? > > > > So the question is, > > > > (1) do we want to enforce the use of the newer static libusb and > > thus have the script fail if libusb source is missing or should the > > script continue on the assumption that libusb is not needed? > > > > (2) have users upgrade the libusb in 14.1, i.e, libusb-1.0.19-sbo > > as a qemu dependency? Are there 14.1 packages dependent on libusb > > that upgrading could break? > > > > In the long run, #2 might be better...depending on when -current > > goes -stable. Leaving the SBo script as vanilla as possible will > > make the SBo transition easier when we all upgrade. > > what if we provide a variable check, such as LIBUSB=yes sh > ./qemu.SlackBuild will build libusb-0.19 statically, otherwise, it > will not be built It's untested, but I just pushed something like that - those of you affected, please test and make sure it works :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Sat Dec 27 22:18:53 2014 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 27 Dec 2014 22:18:53 +0000 Subject: [Slackbuilds-users] Fontconfig warning with package culmus (was: Error while installing package culmus) In-Reply-To: <20141227125107.2c2672aa@home.rlworkman.net> References: <549D957C.1040103@slackbuilds.org> <20141227125107.2c2672aa@home.rlworkman.net> Message-ID: > Thanks to Ghengis Khan. Best. Commit. Message. Ever. -D. From rworkman at slackbuilds.org Sat Dec 27 22:32:07 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 27 Dec 2014 16:32:07 -0600 Subject: [Slackbuilds-users] Fontconfig warning with package culmus (was: Error while installing package culmus) In-Reply-To: References: <549D957C.1040103@slackbuilds.org> <20141227125107.2c2672aa@home.rlworkman.net> Message-ID: <20141227163207.679cbaf1@home.rlworkman.net> On Sat, 27 Dec 2014 22:18:53 +0000 David Spencer wrote: > > Thanks to Ghengis Khan. > > Best. Commit. Message. Ever. Heh. :-) For the sake of clarity, there were two errors here. One was a missing "fi" that I introduced in my earlier fix ( git id 80587f16a16eb ); this is what willysr fixed in his commit. The second is what I just fixed, and it is really a fix to upstream to account for changes in fontconfig's handling of blocks. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Sun Dec 28 05:28:55 2014 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 27 Dec 2014 23:28:55 -0600 Subject: [Slackbuilds-users] Updates - 20141228.1 Message-ID: <20141227232855.66a219ee@home.rlworkman.net> Sun Dec 28 05:17:52 UTC 2014 academic/openmodelica: Updated for version svn23908. audio/apulse: Add speex as recommended dependency. audio/volumeicon: Add option to built against GTK+2. development/android-tools: Fixed source. gis/foxtrotgps: Fix doinst.sh. gis/mobac: Added (Mobile Atlas Creator). graphics/darktable: Updated for version 1.6.1. graphics/meshlab: Fix build on i486. libraries/CGAL: Updated for version 4.5.1. libraries/Nevow: Updated for version 0.11.1. libraries/mpir: Added (Multiple Precision Integers and Rationals). libraries/qt5: Updated for version 5.4.0. multimedia/musique: Updated for version 1.4. network/connman: Updated for version 1.27. network/hipchat: Updated for version 2.2.1309. office/texstudio: Updated for version 2.8.8. python/characteristic: Added (Python Package). python/pyasn1-modules: Added (ASN.1-based protocols modules). python/service_identity: Added (Service Identity Verification). system/asbt: Updated for version 1.1. system/culmus: Fix doinst.sh. system/culmus: Fixup fontconfig warnings system/glances: Updated for version 2.2.1. system/profile-sync-daemon: Updated for version 5.60. system/slpkg: Updated for version 2.1.5. system/the_silver_searcher: Updated for version 0.28.0. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ts at websafe.pl Sun Dec 28 16:13:06 2014 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 28 Dec 2014 17:13:06 +0100 Subject: [Slackbuilds-users] [BUG] slack-desc for perl-IO-HTML has only 10 lines (one missing) Message-ID: <54A02C12.8030808@websafe.pl> The section below "handy-ruler" in slack-desc for perl-IO-HTML has only 10 lines instead of expected 11 lines. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sun Dec 28 16:17:49 2014 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 28 Dec 2014 17:17:49 +0100 Subject: [Slackbuilds-users] [BUG] slack-desc for perl-TermReadKey has only 8 lines (three missing) Message-ID: <54A02D2D.90201@websafe.pl> The section below "handy-ruler" in slack-desc for perl-TermReadKey has only 8 lines instead of expected 11 lines. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sun Dec 28 16:22:09 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 28 Dec 2014 23:22:09 +0700 Subject: [Slackbuilds-users] [BUG] slack-desc for perl-IO-HTML has only 10 lines (one missing) In-Reply-To: <54A02C12.8030808@websafe.pl> References: <54A02C12.8030808@websafe.pl> Message-ID: <54A02E31.9040007@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The section below "handy-ruler" in slack-desc for perl-IO-HTML > > > > has only 10 lines instead of expected 11 lines. > The section below "handy-ruler" in slack-desc for perl-TermReadKey > /slack-desc> > has only 8 lines instead of expected 11 lines. Both fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSgLjEACgkQiHuDdNczM4E5AQCgkK0vrLn4UU1TEO2SWJzKckx4 vEcAn3sC0f0WzHTIfgg+W0lSrAV0eDrW =GLsX -----END PGP SIGNATURE----- From burningc at SDF.ORG Sun Dec 28 18:49:03 2014 From: burningc at SDF.ORG (Glenn Becker) Date: Sun, 28 Dec 2014 18:49:03 +0000 (UTC) Subject: [Slackbuilds-users] [BUG] slack-desc for perl-IO-HTML has only 10 lines (one missing) In-Reply-To: <54A02E31.9040007@slackbuilds.org> References: <54A02C12.8030808@websafe.pl> <54A02E31.9040007@slackbuilds.org> Message-ID: Thanks, both -- sorry about that. /Glenn On Sun, 28 Dec 2014, Willy Sudiarto Raharjo wrote: > Date: Sun, 28 Dec 2014 23:22:09 +0700 > From: Willy Sudiarto Raharjo > Reply-To: SlackBuilds.org Users List > To: SlackBuilds.org Users List > Subject: Re: [Slackbuilds-users] [BUG] slack-desc for perl-IO-HTML has only 10 > lines (one missing) > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> The section below "handy-ruler" in slack-desc for perl-IO-HTML >> >> >> >> has only 10 lines instead of expected 11 lines. > >> The section below "handy-ruler" in slack-desc for perl-TermReadKey > >> > /slack-desc> > >> has only 8 lines instead of expected 11 lines. > > Both fixed in my branch > Thanks > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSgLjEACgkQiHuDdNczM4E5AQCgkK0vrLn4UU1TEO2SWJzKckx4 > vEcAn3sC0f0WzHTIfgg+W0lSrAV0eDrW > =GLsX > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > +---------------------------------------------+ Glenn Becker - burningc at sdf.org SDF Public Access UNIX System - http://sdf.org +---------------------------------------------+ From hba.nihilismus at gmail.com Mon Dec 29 05:48:13 2014 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sun, 28 Dec 2014 23:48:13 -0600 Subject: [Slackbuilds-users] network/jetty download returns 404 Message-ID: A working DOWNLOAD value: http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/9.2.3.v20140905/jetty-distribution-9.2.3.v20140905.tar.gz MD5 sums matches! I would say that is better to use maven's repository for future jetty's updates: http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/ - Cheers -- 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 willysr at slackbuilds.org Mon Dec 29 08:48:48 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 29 Dec 2014 15:48:48 +0700 Subject: [Slackbuilds-users] network/jetty download returns 404 In-Reply-To: References: Message-ID: <54A11570.8090004@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > A working DOWNLOAD value: > http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/9.2.3.v20140905/jetty-distribution-9.2.3.v20140905.tar.gz > > MD5 sums matches! Fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlShFXAACgkQiHuDdNczM4HyPACeNZz5GQFwioC6An/V2MpBMuED wqgAn249YcmoFDUo8OYxDh3igVIwjWGX =UIwM -----END PGP SIGNATURE----- From philip at vd-hoeven.nl Mon Dec 29 09:04:37 2014 From: philip at vd-hoeven.nl (Philip van der Hoeven) Date: Mon, 29 Dec 2014 10:04:37 +0100 Subject: [Slackbuilds-users] uid request Message-ID: Hi, I have a sabnzbd slackbuild which needs some cleanup so I can submit it. I would need a sabnzbd user and group, can somebody please reserve one for me ? Regards, Philip -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Mon Dec 29 16:06:44 2014 From: miguel at thedeanda.com (Miguel De Anda) Date: Mon, 29 Dec 2014 08:06:44 -0800 Subject: [Slackbuilds-users] network/jetty download returns 404 In-Reply-To: References: Message-ID: I agree. Their download link seems to go 404 after every minor release. On Dec 28, 2014 9:48 PM, "Antonio Hern?ndez Blas" wrote: > A working DOWNLOAD value: > http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/9.2.3.v20140905/jetty-distribution-9.2.3.v20140905.tar.gz > > MD5 sums matches! > > I would say that is better to use maven's repository for future jetty's > updates: > http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/ > > - Cheers > > -- > Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. > https://github.com/nihilismus | https://bitbucket.org/nihilismus | > https://twitter.com/nihilipster > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Dec 29 16:36:28 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 29 Dec 2014 23:36:28 +0700 Subject: [Slackbuilds-users] uid request In-Reply-To: References: Message-ID: <54A1830C.6050007@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I have a sabnzbd slackbuild which needs some cleanup so I can > submit it. I would need a sabnzbd user and group, can somebody > please reserve one for me ? 296 - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlShgwwACgkQiHuDdNczM4FEsACgmPcH9gR80Mp3pDZO/rgD2rBx y7QAn2tUS18YD1YmrkPyIDuPtD6AM6g5 =Lr+/ -----END PGP SIGNATURE----- From thorsten.johannvorderbrueggen at t-online.de Mon Dec 29 19:40:33 2014 From: thorsten.johannvorderbrueggen at t-online.de (thorsten.johannvorderbrueggen at t-online.de) Date: Mon, 29 Dec 2014 20:40:33 +0100 Subject: [Slackbuilds-users] update available for libftdi Message-ID: <20141229204033.0eed088e674a361d2ba7f471@t-online.de> Hi at Ananda, there's a new version of libftdi available -> 1.2 ... Cheers Thorsten -- thorsten.johannvorderbrueggen at t-online.de From mariolpantunes at gmail.com Tue Dec 30 00:42:57 2014 From: mariolpantunes at gmail.com (=?UTF-8?B?TcOhcmlvIEFudHVuZXM=?=) Date: Tue, 30 Dec 2014 00:42:57 +0000 Subject: [Slackbuilds-users] network/jetty download returns 404 In-Reply-To: References: Message-ID: <54A1F511.40106@gmail.com> Thanks for the report, I will change the download link in the future releases. On 12/29/2014 04:06 PM, Miguel De Anda wrote: > > I agree. Their download link seems to go 404 after every minor release. > > On Dec 28, 2014 9:48 PM, "Antonio Hern?ndez Blas" > > wrote: > > A working DOWNLOAD value: > http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/9.2.3.v20140905/jetty-distribution-9.2.3.v20140905.tar.gz > > MD5 sums matches! > > I would say that is better to use maven's repository for future > jetty's updates: > http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/ > > - Cheers > > -- > Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. > https://github.com/nihilismus | https://bitbucket.org/nihilismus | > https://twitter.com/nihilipster > > _______________________________________________ > 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 Wed Dec 31 12:43:30 2014 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 31 Dec 2014 19:43:30 +0700 Subject: [Slackbuilds-users] Updates - 20141231.1 Message-ID: <54A3EF72.30505@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wed Dec 31 12:25:45 UTC 2014 academic/gcompris: Updated for version 14.12. academic/stellarium: Updated for version 0.13.1. audio/clementine: Updated for version 1.2.3. audio/hydrogen: Update README. desktop/q4wine: Updated for version 1.1_r2. development/android-studio: Updated for version 1.0.1_135_1641136. development/chibi-scheme: Updated for version 0.7.1. development/cppunit: Updated for version 1.13.2 + new maintainer. development/jdk: Updated for version 8u25. development/mcrl2: Updated for version 201409.1. development/mm-common: Updated for version 0.9.7. development/src-vcs: Updated for version 0.18. games/mednafen: Updated for version 0.9.37.1. gis/osm2pgsql: Updated for version 0.87.1. graphics/hugin: Fix VERSION. libraries/cryptopp: Update DOWNLOAD url. libraries/libftdi1: Updated for version 1.2. libraries/libvirt-glib: Updated for version 0.2.0. libraries/live555: Updated for version 2014.12.17. libraries/webkitgtk3: Updated for version 2.4.7. libraries/webkitgtk: Updated for version 2.4.7. misc/protobuf: Update DEPS. misc/recode: Fix README typo. multimedia/aegisub: Updated for version 3.2.2. multimedia/mpv: Updated for version 0.7.2. multimedia/mythplugins: Updated for version 0.27.4 multimedia/mythtv: Updated for version 0.27.4 multimedia/picard: Updated for version 1.3.1 + new maintainer. multimedia/xmltv: Updated for version 0.5.66. network/btsync: Added (sync files). network/hylafax: Updated for version 6.0.6. network/jetty: Update DOWNLOAD url. network/megasync: Added (Mega Sync Client). network/netstat-nat: Updated for version 1.4.10. network/nzbget: Updated for version 14.1. network/sabnzbd: Added (Binary newsreader). network/squid: Updated for version 3.4.10. network/teamviewer: Mark x86_64 as UNSUPPORTED. office/mdp: Updated for version 0.93.0. office/qpdfview: Updated for version 0.4.13. perl/perl-Archive-Zip: Updated for version 1.39. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.020. perl/perl-Capture-Tiny: Updated for version 0.27. perl/perl-Class-Load: Updated vor version 0.21. perl/perl-Class-MethodMaker: Updated for version 2.21. perl/perl-Class-Singleton: Updated for version 1.5. perl/perl-Data-Dumper: Updated for version 2.154. perl/perl-Data-OptList: Updated for version 0.109. perl/perl-Date-Manip: Updated for version 6.48. perl/perl-DateTime-Format-Strptime: Updated for version 1.56. perl/perl-DateTime-TimeZone: Updated for version 1.70. perl/perl-DateTime: Updated for version 1.10. perl/perl-Devel-Symdump: Updated for version 2.14. perl/perl-Dist-CheckConflicts: Updated for version 0.11. perl/perl-Exporter-Tiny: Added (Exporter::Tiny perl module) perl/perl-IO-HTML: Fixed slack-desc. perl/perl-IO-SessionData: Added (supporting module for SOAP::Lite) perl/perl-JSON: Updated for version 2.90. perl/perl-Lingua-EN-Numbers-Ordinate: Updated for version 1.03. perl/perl-List-MoreUtils: Updated for version 0.402. perl/perl-Module-Runtime: Updated for version 0.014. perl/perl-Package-Stash: Updated for version 0.37. perl/perl-Params-Validate: Updated for version 1.13. perl/perl-SOAP-Lite: Updated for version 1.12. perl/perl-Sub-Install: Updated for version 0.928. perl/perl-Term-ProgressBar: Updated for version 2.16. perl/perl-TermReadKey: Fixed slack-desc. perl/perl-Test-Fatal: Updated for version 0.014. perl/perl-Test-Harness: Updated for version 3.34. perl/perl-Test-Requires: Updated for version 0.08. perl/perl-Test-Warnings: Added (Test::Warnings perl module) perl/perl-Try-Tiny: Updated for version 0.22. perl/perl-XML-LibXSLT: Updated for version 1.92. perl/perl-XML-Writer: Updated for version 0.625. perl/perl-YAML-Syck: Updated for version 1.29. python/pyusb: Updated for version 0.4.3. ruby/hub: Updated for version 1.12.4. system/ifuse: Updated for version 1.1.3. system/mksh: Updated for version R50d. system/monit: Updated for version 5.11. system/phpsysinfo: Updated for version 3.1.17. system/sakura: Updated for version 3.2.0. system/usermin: Updated for version 1.630. system/webmin: Updated for version 1.720. +--------------------------+ This will probably be the last update in 2014, so i would like to say Happy New Year for everyone. It's only few hours to go in my current local time :) See you in 2015!! - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSj73IACgkQiHuDdNczM4HiUACgo/2LrmUcwFqG8Z0yFBkGT4QY yxgAn3G40m2S7NpGOTefP/k8vQMii/zN =px+T -----END PGP SIGNATURE-----