From john at linux411.com Fri Feb 1 03:03:21 2013 From: john at linux411.com (John C. Gage) Date: Thu, 31 Jan 2013 22:03:21 -0500 Subject: [Slackbuilds-users] Slackbuild Directories Message-ID: Has there ever been a thought to modify the slackbuild script to configure, make and create the TXZ file in the same directory in which the SlackBuild script was run? Can the mod also automatically call installpkg and install the package all in one script? -- ------------------------------------------------------------------------------------------------------------------------------------------- Ever wonder what Linux is? I invite you to visit my site. You may find things are far better with Linux than your current operating system. Visit http://linux411.com. I look forward to help you guide your way through the wonderful world of secure and worry-free computing you may be missing. ------------------------------------------------------------------------------------------------------------------------------------------ NOTICE: This electronic mail message and any attached files are confidential. The information is exclusively for the use of the individual or entity intended as the recipient. If you are not the intended recipient, any use, copying, printing, reviewing, retention, disclosure, distribution or forwarding of the message or any attached file is not authorized and is strictly prohibited. If you have received this electronic mail message in error, please advise postmaster at linux411.com by email immediately and permanently delete the original transmission, any attachments and any copies of this message from your computer system. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alien at slackbuilds.org Fri Feb 1 09:12:10 2013 From: alien at slackbuilds.org (Eric Hameleers (SBo)) Date: Fri, 01 Feb 2013 10:12:10 +0100 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: References: Message-ID: <510B86EA.4010507@slackbuilds.org> Op 1-2-2013 4:03, John C. Gage schreef: > Has there ever been a thought to modify the slackbuild script to > configure, make and create the TXZ file in the same directory in > which the SlackBuild script was run? Can the mod also automatically > call installpkg and install the package all in one script? > > The SlackBuild script should do what it has been written for: build a Slackware package. We are not going to change that by adding feature creep. You can easily write a wrapper script which also installs the package afterwards. You can use sbopkg (http://sbopkg.org/) if you do not want to write scripts but use something which has proven its worth already. And building in the same directory as the SlackBuild? No idea why you would want that but try the following commandline to achieve this: # OUTPUT=$(pwd) TMP=$(pwd) ./some.SlackBuild Eric From john at linux411.com Fri Feb 1 12:09:25 2013 From: john at linux411.com (John C. Gage) Date: Fri, 1 Feb 2013 07:09:25 -0500 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: <510B86EA.4010507@slackbuilds.org> References: <510B86EA.4010507@slackbuilds.org> Message-ID: I'll have to check out sbopkg. Just a thought I had while installing SlackBuilds recently. Just as easy to type installpkg /tmp/*.txz but thought a single script would be more all inclusive. My though on the txz being in the same dir as SlackBuild was for ease of install. Instead of calling the built package from /tmp/. SlackBuild is awesome in itself. No doubt. Just was wondering. On Fri, Feb 1, 2013 at 4:12 AM, Eric Hameleers (SBo) wrote: > Op 1-2-2013 4:03, John C. Gage schreef: > > Has there ever been a thought to modify the slackbuild script to > > configure, make and create the TXZ file in the same directory in > > which the SlackBuild script was run? Can the mod also automatically > > call installpkg and install the package all in one script? > > > > > The SlackBuild script should do what it has been written for: build a > Slackware package. We are not going to change that by adding feature > creep. > You can easily write a wrapper script which also installs the package > afterwards. You can use sbopkg (http://sbopkg.org/) if you do not want > to write scripts but use something which has proven its worth already. > > And building in the same directory as the SlackBuild? No idea why you > would want that but try the following commandline to achieve this: > > # OUTPUT=$(pwd) TMP=$(pwd) ./some.SlackBuild > > Eric > _______________________________________________ > 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/ > > -- ------------------------------------------------------------------------------------------------------------------------------------------- Ever wonder what Linux is? I invite you to visit my site. You may find things are far better with Linux than your current operating system. Visit http://linux411.com. I look forward to help you guide your way through the wonderful world of secure and worry-free computing you may be missing. ------------------------------------------------------------------------------------------------------------------------------------------ NOTICE: This electronic mail message and any attached files are confidential. The information is exclusively for the use of the individual or entity intended as the recipient. If you are not the intended recipient, any use, copying, printing, reviewing, retention, disclosure, distribution or forwarding of the message or any attached file is not authorized and is strictly prohibited. If you have received this electronic mail message in error, please advise postmaster at linux411.com by email immediately and permanently delete the original transmission, any attachments and any copies of this message from your computer system. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bradley at NorthTech.US Fri Feb 1 18:58:31 2013 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Fri, 01 Feb 2013 10:58:31 -0800 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: References: Message-ID: <510C1057.8050900@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On 01/31/2013 07:03 PM, John C. Gage wrote: > Has there ever been a thought to modify the slackbuild script to configure, > make and create the TXZ file in the same directory in which the SlackBuild > script was run? Can the mod also automatically call installpkg and install > the package all in one script? I tend to keep my SBo's in /usr/local/slackbuilds. Then when I untar them, they reside, along with the source which I download, in /usr/local/slackbuilds/. I like to keep all of my packages in /usr/local/packages, and create a symlink there so I can get any package via HTTP. It's convenient, much less messy than /tmp, which I like to keep cleaned out, and makes for easy re-distribution, rollbacks, and use of packages later. Change the output line in .SlackBuild from /tmp to: OUTPUT=${OUTPUT:-/usr/local/packages} I also change this to be the default in sbopkg too. Of course, you'll need to: # mkdir -p /usr/local/packages I hope that helps! Kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJRDBBXAAoJEE1wgkIhr9j3NkwH/02Jtos3Hl1f7U86LRwxHG3D JDd3o1iKESm2t+MUWXn839CviHqBNvMVbimkIOM5X9oJwbzHWuRzO821gTxVUxyi 4jYuASodNVJjPSZgzwSrFGHxL7tI1klbh/AxjuMNkRweUIc7b0uvztUGTVZ+a1Qm QtMpaZdHyG6PGzX8kr8gDhk6gxd5F+yIrGeRytHIjMGlIK4DzUcr90XPflGkf984 BMyTkInzPxIv/n/uCDeMJRnNaFDe5PlQDFDMf07ZAPINjmhq9pAqmJ1E+l1w48PY RbBfBvSBKFJSyVw7TsHO/NgqZyNaPrG75howfOAs/eXp8NvcKO4slEUd3eA2NrU= =epis -----END PGP SIGNATURE----- From panych.y at gmail.com Fri Feb 1 09:57:08 2013 From: panych.y at gmail.com (Yaroslav Panych) Date: Fri, 1 Feb 2013 11:57:08 +0200 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: References: Message-ID: If I want to build into current directory I always do: OUTPUT=$(pwd)/out TMP=$(pwd)/tmp PKGTYE=txz ./*.SlackBuild But it cannot be defaulted because: a) SlackBuild can be located on Read-Only storage(DVD/CD disk, write-locked USB stoarge, or just ro mounted storage) b) SlackBuild can be located on very slow(network share), write cycles limited storage(USB sticks, some kinds of SSDs), so it is preferably to do all work in faster environments. Both problems is prevented by default now and I very happy of it. About autoinstall: No again. First of all, task of *.SlackBuild is to build package(this is not Gentoo's ebuild). Second: if it will be introduced we need mechanism to give personal additional parameters to installer(including kind of installer to run). Third: SlackBuild can do cross-compilation to different architecture, and instant installation of built package will break host system. So this function cannot be turned on by default. Regards, Yaroslav 2013/2/1 John C. Gage : > Has there ever been a thought to modify the slackbuild script to configure, > make and create the TXZ file in the same directory in which the SlackBuild > script was run? Can the mod also automatically call installpkg and install > the package all in one script? > > -- > From xgizzmo at slackbuilds.org Sat Feb 2 00:39:34 2013 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Fri, 1 Feb 2013 19:39:34 -0500 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: <510C1057.8050900@NorthTech.US> References: <510C1057.8050900@NorthTech.US> Message-ID: <201302011939.34522.xgizzmo@slackbuilds.org> On Friday 01 February 2013 13:58:31 Bradley D. Thornton wrote: > > On 01/31/2013 07:03 PM, John C. Gage wrote: > > Has there ever been a thought to modify the slackbuild script to configure, > > make and create the TXZ file in the same directory in which the SlackBuild > > script was run? Can the mod also automatically call installpkg and install > > the package all in one script? > > I tend to keep my SBo's in /usr/local/slackbuilds. Then when I untar > them, they reside, along with the source which I download, in > /usr/local/slackbuilds/. > > I like to keep all of my packages in /usr/local/packages, and create a > symlink there so I can get any package via HTTP. It's convenient, much > less messy than /tmp, which I like to keep cleaned out, and makes for > easy re-distribution, rollbacks, and use of packages later. > > Change the output line in .SlackBuild from /tmp to: > > OUTPUT=${OUTPUT:-/usr/local/packages} > > I also change this to be the default in sbopkg too. Of course, you'll > need to: > > # mkdir -p /usr/local/packages > > I hope that helps! > > Kindest regards, > > No reason to edit the Slackbuild at all add something like this to you profile: export OUTPUT="/usr/local/packages" export PKGTYPE="txz" or OUTPUT="/usr/local/packages" PKGTYPE="txz" .SlackBuild --dsomero From kingbeowulf at gmail.com Sat Feb 2 03:36:05 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 01 Feb 2013 19:36:05 -0800 Subject: [Slackbuilds-users] [Slackbuild-users] Libreoffice dead link Message-ID: <510C89A5.1070403@gmail.com> FYI: They did it again: libreoffice-3.6.5 is out so now the SBo link to libreoffice-3.6.4 is dead(moved). Enjoy Ed From zach.gardner at gmail.com Sat Feb 2 06:00:44 2013 From: zach.gardner at gmail.com (Zach) Date: Sat, 02 Feb 2013 00:00:44 -0600 Subject: [Slackbuilds-users] deluge dependency Message-ID: <510CAB8C.2040504@gmail.com> Deluge requires python2-chardet, which isn't listed. From kristofru at gmail.com Fri Feb 1 21:05:11 2013 From: kristofru at gmail.com (Chris Abela) Date: Fri, 01 Feb 2013 22:05:11 +0100 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: <510C1057.8050900@NorthTech.US> References: <510C1057.8050900@NorthTech.US> Message-ID: <510C2E07.5020008@gmail.com> I think that we would be hard pressed to find many "default" Slackware installations in the wild. My choice was to write a small /etc/profile.d/local.sh (with executable permissions of course). Then I use sbopkg most of the time. #!/bin/sh # SBo parameters export PKGTYPE=txz export OUTPUT=/home/chris/packages export QUEUEDIR=/home/chris/queues export SBo='/var/lib/sbopkg/SBo/14.0/' That's all I needed. The /usr/local/ choice is enticing as well, but I am not sure that was the original intention of the directory. Chris From pfeifer.felix at gmail.com Sat Feb 2 14:36:47 2013 From: pfeifer.felix at gmail.com (Felix Pfeifer) Date: Sat, 2 Feb 2013 15:36:47 +0100 Subject: [Slackbuilds-users] remove transset-df Message-ID: Hi, my script for transset-df is obsolete and can be removed from SBo. All the features of transset-df are now included in X.orgs original transset. greetings, Felix From slackaddict2003 at yahoo.it Mon Feb 4 19:17:27 2013 From: slackaddict2003 at yahoo.it (le) Date: Mon, 4 Feb 2013 19:17:27 +0000 (GMT) Subject: [Slackbuilds-users] radiotray slackbuild missing deps Message-ID: <1360005447.36143.YahooMailNeo@web172104.mail.ir2.yahoo.com> hi all when i tried to compile/install the package radiotray from slackbuilds i stumble on the following errors: pyxdg as a needed dep to compile/install radiotray lxml as a needed dep to actually make it works thnx to ponce who resolved my issues with it pointing me to the right missing deps here the full thread on lq > http://tinyurl.com/awpkwd7 hope helps ciao -------------- next part -------------- An HTML attachment was scrubbed... URL: From cary at sdf.org Thu Feb 7 01:17:04 2013 From: cary at sdf.org (Cary) Date: Wed, 6 Feb 2013 17:17:04 -0800 Subject: [Slackbuilds-users] building calibre-0.9.13-x86_64 fails - missing py module In-Reply-To: <96805668.iZHQdMIPYs@callisto> References: <50A38198.6030107@yahoo.com.br> <96805668.iZHQdMIPYs@callisto> Message-ID: <20130207011704.GA25944@joru2010.localhost> Hello, It looks as though a module needs to be added to REQUIRES= in the calibre.info file. Using sbopkg, my attempt to upgrade from calibre-0.8.69 to version 0.9.13 failed with the following error: * * Running gui * Traceback (most recent call last): File "setup.py", line 99, in sys.exit(main()) File "setup.py", line 85, in main command.run_all(opts) File "/tmp/SBo/calibre/setup/__init__.py", line 163, in run_all self.run_cmd(self, opts) File "/tmp/SBo/calibre/setup/__init__.py", line 156, in run_cmd self.run_cmd(scmd, opts) File "/tmp/SBo/calibre/setup/__init__.py", line 159, in run_cmd cmd.run(opts) File "/tmp/SBo/calibre/setup/gui.py", line 37, in run self.build_forms() File "/tmp/SBo/calibre/setup/gui.py", line 60, in build_forms from calibre.gui2 import build_forms File "/tmp/SBo/calibre/src/calibre/gui2/__init__.py", line 21, in from calibre.utils.date import UNDEFINED_DATE File "/tmp/SBo/calibre/src/calibre/utils/date.py", line 13, in from dateutil.tz import tzlocal, tzutc File "/usr/lib64/python2.7/site-packages/dateutil/tz.py", line 9, in from six import string_types, PY3 ImportError: No module named six ----- ---------end of error msg. ----- After building and installing module python/six the upgrade of calibre was successful. Cary From bamalabs at gmail.com Wed Feb 6 21:27:53 2013 From: bamalabs at gmail.com (bamalabs) Date: Wed, 6 Feb 2013 15:27:53 -0600 Subject: [Slackbuilds-users] osgEarth link error Message-ID: <20130206212753.GB28709@dribt> The link to the osgEarth.tar.gz SlackBuild points to the 'libraries' folder, when the file is actually in the 'graphics' folder. -- bamalabs From gabrielmagno1 at gmail.com Thu Feb 7 01:35:29 2013 From: gabrielmagno1 at gmail.com (Gabriel Magno) Date: Wed, 6 Feb 2013 23:35:29 -0200 Subject: [Slackbuilds-users] [BUG FIX] Package: lmms Message-ID: The SlackBuild script ran without error, but when I executed the program, it poped erros like this: "Could not find library /usr//usr/lib64/lmms/libtripleoscillator.so" I tried to fix this, and apparently I was able to. I changed the CMAKE options in the file "lmms.SlackBuild" from: -DCMAKE_INSTALL_PREFIX=/usr \ -DCMAKE_INSTALL_LIBDIR=/usr/lib${LIBDIRSUFFIX} \ To: -DCMAKE_INSTALL_PREFIX=/usr \ -DCMAKE_INSTALL_LIBDIR=lib${LIBDIRSUFFIX} \ I wasn't able to contact the SlackBuild maintainer, that's why I'm sending it to this mailing list. Best regards, -- Gabriel Magno -------------- next part -------------- An HTML attachment was scrubbed... URL: From sikmir at gmail.com Thu Feb 7 06:32:42 2013 From: sikmir at gmail.com (Nikolay Korotkiy) Date: Thu, 7 Feb 2013 10:32:42 +0400 Subject: [Slackbuilds-users] building calibre-0.9.13-x86_64 fails - missing py module In-Reply-To: <20130207011704.GA25944@joru2010.localhost> References: <50A38198.6030107@yahoo.com.br> <96805668.iZHQdMIPYs@callisto> <20130207011704.GA25944@joru2010.localhost> Message-ID: Everything is OK: calibre require python-dateutil, python-dateutil require six. On Thu, Feb 7, 2013 at 5:17 AM, Cary wrote: > Hello, > > It looks as though a module needs to be added to REQUIRES= in the > calibre.info file. > Using sbopkg, my attempt to upgrade from calibre-0.8.69 to version 0.9.13 > failed with the following error: > > * > * Running gui > * > > Traceback (most recent call last): > File "setup.py", line 99, in > sys.exit(main()) > File "setup.py", line 85, in main > command.run_all(opts) > File "/tmp/SBo/calibre/setup/__init__.py", line 163, in run_all > self.run_cmd(self, opts) > File "/tmp/SBo/calibre/setup/__init__.py", line 156, in run_cmd > self.run_cmd(scmd, opts) > File "/tmp/SBo/calibre/setup/__init__.py", line 159, in run_cmd > cmd.run(opts) > File "/tmp/SBo/calibre/setup/gui.py", line 37, in run > self.build_forms() > File "/tmp/SBo/calibre/setup/gui.py", line 60, in build_forms > from calibre.gui2 import build_forms > File "/tmp/SBo/calibre/src/calibre/gui2/__init__.py", line 21, in > > from calibre.utils.date import UNDEFINED_DATE > File "/tmp/SBo/calibre/src/calibre/utils/date.py", line 13, in > from dateutil.tz import tzlocal, tzutc > File "/usr/lib64/python2.7/site-packages/dateutil/tz.py", line 9, in > > from six import string_types, PY3 > ImportError: No module named six > > > ----- > ---------end of error msg. > ----- > > After building and installing module python/six the upgrade > of calibre was successful. > > Cary > _______________________________________________ > 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/ > > -- Best regards, Nikolay Korotkiy -------------- next part -------------- An HTML attachment was scrubbed... URL: From larryhaja at gmail.com Thu Feb 7 02:41:06 2013 From: larryhaja at gmail.com (Larry Hajali) Date: Wed, 6 Feb 2013 18:41:06 -0800 Subject: [Slackbuilds-users] building calibre-0.9.13-x86_64 fails - missing py module In-Reply-To: <20130207011704.GA25944@joru2010.localhost> References: <50A38198.6030107@yahoo.com.br> <96805668.iZHQdMIPYs@callisto> <20130207011704.GA25944@joru2010.localhost> Message-ID: Hi Cary, The problem that you are seeing is that python-dateutil has a new dependency on another python module called six. The python module six is in SBo and is listed as a dependency of python-dateutil. Just install six and rebuild calibre. --Larry On Wed, Feb 6, 2013 at 5:17 PM, Cary wrote: > Hello, > > It looks as though a module needs to be added to REQUIRES= in the > calibre.info file. > Using sbopkg, my attempt to upgrade from calibre-0.8.69 to version 0.9.13 > failed with the following error: > > * > * Running gui > * > > Traceback (most recent call last): > File "setup.py", line 99, in > sys.exit(main()) > File "setup.py", line 85, in main > command.run_all(opts) > File "/tmp/SBo/calibre/setup/__init__.py", line 163, in run_all > self.run_cmd(self, opts) > File "/tmp/SBo/calibre/setup/__init__.py", line 156, in run_cmd > self.run_cmd(scmd, opts) > File "/tmp/SBo/calibre/setup/__init__.py", line 159, in run_cmd > cmd.run(opts) > File "/tmp/SBo/calibre/setup/gui.py", line 37, in run > self.build_forms() > File "/tmp/SBo/calibre/setup/gui.py", line 60, in build_forms > from calibre.gui2 import build_forms > File "/tmp/SBo/calibre/src/calibre/gui2/__init__.py", line 21, in > > from calibre.utils.date import UNDEFINED_DATE > File "/tmp/SBo/calibre/src/calibre/utils/date.py", line 13, in > from dateutil.tz import tzlocal, tzutc > File "/usr/lib64/python2.7/site-packages/dateutil/tz.py", line 9, in > > from six import string_types, PY3 > ImportError: No module named six > > > ----- > ---------end of error msg. > ----- > > After building and installing module python/six the upgrade > of calibre was successful. > > Cary > _______________________________________________ > 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 burningc at SDF.ORG Thu Feb 7 16:45:20 2013 From: burningc at SDF.ORG (Glenn Becker) Date: Thu, 7 Feb 2013 16:45:20 +0000 (UTC) Subject: [Slackbuilds-users] MendeleyDesktop Message-ID: Hi -- I was unable to get the MendeleyDesktop SlackBuild to work, so wrote the maintainer. He isn't using the app any more and encouraged me to take it over if I wanted. So I am going to give it a shot. Thanks, /GB +---------------------------------------------+ Glenn Becker - burningc at sdf.org SDF Public Access UNIX System - http://sdf.org +---------------------------------------------+ From info at microlinux.fr Sun Feb 10 06:06:53 2013 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 10 Feb 2013 07:06:53 +0100 Subject: [Slackbuilds-users] Missing user 'dovenull' for Dovecot Message-ID: <511738FD.7080502@microlinux.fr> Hi, I'm currently fiddling with Postfix and Dovecot from SBo (thanks Alan Hicks!) and everything works fine so far. Out of the box, Dovecot seems to miss a 'dovenull' user besides the 'dovecot' user and group. # doveconf -n | grep Error doveconf: Error: default_login_user doesn't exist: dovenull doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: default_login_user doesn't exist: dovenull Maybe edit the Dovecot page with a suggestion to add that user. 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 andreas at andreasvoegele.com Sun Feb 10 08:26:45 2013 From: andreas at andreasvoegele.com (=?ISO-8859-1?Q?Andreas_V=F6gele?=) Date: Sun, 10 Feb 2013 09:26:45 +0100 Subject: [Slackbuilds-users] Missing user 'dovenull' for Dovecot In-Reply-To: <511738FD.7080502@microlinux.fr> References: <511738FD.7080502@microlinux.fr> Message-ID: <511759C5.6080404@andreasvoegele.com> On 10.02.2013 07:06, Niki Kovacs wrote: > Hi, > > I'm currently fiddling with Postfix and Dovecot from SBo (thanks Alan > Hicks!) and everything works fine so far. > > Out of the box, Dovecot seems to miss a 'dovenull' user besides the > 'dovecot' user and group. [...] I stumbled upon this too. The 'dovenull' user is listed in http://slackbuilds.org/uid_gid.txt but it isn't mentioned in the SlackBuild's README. From info at microlinux.fr Sun Feb 10 17:07:50 2013 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 10 Feb 2013 18:07:50 +0100 Subject: [Slackbuilds-users] makepasswd.SlackBuild Message-ID: <5117D3E6.3050909@microlinux.fr> Hi, I'm currently building 'makepasswd' from SBo. Two remarks. 1) Version 0.5.1 has been out for about a year, and builds fine as is. 2) The current scripts forgets to compress the makepasswd man page. 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 larryhaja at gmail.com Sun Feb 10 21:12:00 2013 From: larryhaja at gmail.com (Larry Hajali) Date: Sun, 10 Feb 2013 13:12:00 -0800 Subject: [Slackbuilds-users] uid and gid for vdr Message-ID: Hello, I'm looking at vdr on my own system (ie. http://linuxtv.org/vdrwiki/index.php/Main_Page) and was looking at running it as a daemon. As I was looking at possible users for this package, I took a look at reserved uid/gid at http://slackbuilds.org/uid_gid.txt. It looks like vdr is already defined by using the policyd uid/gid, which in turn is also used for policyd2. I found this in the SBo email archive. http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-June/004234.html My question is should this uid/gid be used for vdr or should it be separate from the uid/gid for policyd2? BTW...I'm just asking for clarification. I don't plan on submitting my vdr slackbuild. Thanks, --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From alan at lizella.net Sun Feb 10 21:20:25 2013 From: alan at lizella.net (Alan Hicks) Date: Sun, 10 Feb 2013 16:20:25 -0500 Subject: [Slackbuilds-users] Missing user 'dovenull' for Dovecot In-Reply-To: <511759C5.6080404@andreasvoegele.com> References: <511738FD.7080502@microlinux.fr> <511759C5.6080404@andreasvoegele.com> Message-ID: <20130210162025.7a762ab8.alan@lizella.net> On Sun, 10 Feb 2013 09:26:45 +0100 Andreas V?gele wrote: > > > On 10.02.2013 07:06, Niki Kovacs wrote: > > Hi, > > > > I'm currently fiddling with Postfix and Dovecot from SBo (thanks > > Alan Hicks!) and everything works fine so far. > > > > Out of the box, Dovecot seems to miss a 'dovenull' user besides the > > 'dovecot' user and group. [...] > > I stumbled upon this too. The 'dovenull' user is listed in > http://slackbuilds.org/uid_gid.txt but it isn't mentioned in the > SlackBuild's README. I don't remember what the dovenull user is used for. IIRC some one else pushed out an add-on for dovecot at one time that might have required a dovenull user. I don't believe dovecot itself requires one. The following is taken from my personal mail server which runs dovecot for IMAP. alan at barnowl:~$ grep dove /etc/passwd dovecot:x:202:202::/dev/null:/bin/false Since I myself don't have the dovenull user and the script itself doesn't look for that user in any fashion, I'm pretty certain that this was part of some other add-on or plugin at one time. -- It is better to hear the rebuke of the wise, Than for a man to hear the song of fools. Ecclesiastes 7:5 From rworkman at slackbuilds.org Sun Feb 10 21:27:33 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 10 Feb 2013 15:27:33 -0600 Subject: [Slackbuilds-users] Missing user 'dovenull' for Dovecot In-Reply-To: <20130210162025.7a762ab8.alan@lizella.net> References: <511738FD.7080502@microlinux.fr> <511759C5.6080404@andreasvoegele.com> <20130210162025.7a762ab8.alan@lizella.net> Message-ID: <20130210152733.01ce68f1@home.rlworkman.net> On Sun, 10 Feb 2013 16:20:25 -0500 Alan Hicks wrote: > On Sun, 10 Feb 2013 09:26:45 +0100 > Andreas V?gele wrote: > > > On 10.02.2013 07:06, Niki Kovacs wrote: > > > Hi, > > > > > > I'm currently fiddling with Postfix and Dovecot from SBo (thanks > > > Alan Hicks!) and everything works fine so far. > > > > > > Out of the box, Dovecot seems to miss a 'dovenull' user besides > > > the 'dovecot' user and group. [...] > > > > I stumbled upon this too. The 'dovenull' user is listed in > > http://slackbuilds.org/uid_gid.txt but it isn't mentioned in the > > SlackBuild's README. > > I don't remember what the dovenull user is used for. IIRC some one > else pushed out an add-on for dovecot at one time that might have > required a dovenull user. I don't believe dovecot itself requires > one. The following is taken from my personal mail server which runs > dovecot for IMAP. > > alan at barnowl:~$ grep dove /etc/passwd > dovecot:x:202:202::/dev/null:/bin/false > > Since I myself don't have the dovenull user and the script itself > doesn't look for that user in any fashion, I'm pretty certain that > this was part of some other add-on or plugin at one time. Perhaps it's just something that you're not using there, because we definitely have that on harrier: root at harrier:~# grep dovenull /etc/passwd /etc/group /etc/passwd:dovenull:x:203:203:Unpriv Dovecot User:/:/dev/null /etc/group:dovenull:x:203: -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rob0 at slackbuilds.org Sun Feb 10 22:42:20 2013 From: rob0 at slackbuilds.org (Rob McGee) Date: Sun, 10 Feb 2013 16:42:20 -0600 Subject: [Slackbuilds-users] Missing user 'dovenull' for Dovecot In-Reply-To: <20130210162025.7a762ab8.alan@lizella.net> References: <511738FD.7080502@microlinux.fr> <511759C5.6080404@andreasvoegele.com> <20130210162025.7a762ab8.alan@lizella.net> Message-ID: <20130210224220.GH3672@harrier.slackbuilds.org> On Sun, Feb 10, 2013 at 04:20:25PM -0500, Alan Hicks wrote: > On Sun, 10 Feb 2013 09:26:45 +0100 > Andreas V?gele wrote: > > On 10.02.2013 07:06, Niki Kovacs wrote: > > > I'm currently fiddling with Postfix and Dovecot from SBo > > > (thanks Alan Hicks!) and everything works fine so far. > > > > > > Out of the box, Dovecot seems to miss a 'dovenull' user besides > > > the 'dovecot' user and group. [...] > > > > I stumbled upon this too. The 'dovenull' user is listed in > > http://slackbuilds.org/uid_gid.txt but it isn't mentioned in the > > SlackBuild's README. > > I don't remember what the dovenull user is used for. IIRC some one http://wiki2.dovecot.org/UserIds > else pushed out an add-on for dovecot at one time that might have > required a dovenull user. I don't believe dovecot itself requires > one. The following is taken from my personal mail server which runs > dovecot for IMAP. > > alan at barnowl:~$ grep dove /etc/passwd > dovecot:x:202:202::/dev/null:/bin/false > > Since I myself don't have the dovenull user and the script itself > doesn't look for that user in any fashion, I'm pretty certain that > this was part of some other add-on or plugin at one time. The default_login_user setting, "dovenull", should definitely exist for a Dovecot 2.x install. Compare with: http://wiki.dovecot.org/UserIds This did not exist in 1.x. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From veljko3 at gmail.com Sun Feb 10 23:08:58 2013 From: veljko3 at gmail.com (Veljko) Date: Mon, 11 Feb 2013 00:08:58 +0100 Subject: [Slackbuilds-users] mitter Message-ID: <20130210230857.GA4979@angelina.example.org> Hi! I tried to build mitter, but run into an error: mitter: mitter not found in /var/cache/sbopkg. --2013-02-11 00:01:28-- http://mitter.googlecode.com/files/mitter-0.4.5.tar.gz Resolving mitter.googlecode.com (mitter.googlecode.com)... 173.194.70.82, 2a00:1450:4001:c02::52 Connecting to mitter.googlecode.com (mitter.googlecode.com)|173.194.70.82|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2013-02-11 00:01:29 ERROR 403: Forbidden. I can't access it's homepage on google code. Moved? Dead? Regards, Veljko From yalhcru at gmail.com Mon Feb 11 00:19:20 2013 From: yalhcru at gmail.com (B Watson) Date: Sun, 10 Feb 2013 19:19:20 -0500 Subject: [Slackbuilds-users] mitter In-Reply-To: <20130210230857.GA4979@angelina.example.org> References: <20130210230857.GA4979@angelina.example.org> Message-ID: On 2/10/13, Veljko wrote: > I can't access it's homepage on google code. Moved? Dead? There's a copy here with matching md5sum: http://pkgs.fedoraproject.org/repo/pkgs/mitter/mitter-0.4.5.tar.gz/0432f3d2d00e8d048bf0839e2d857e51/mitter-0.4.5.tar.gz Don't know if that URL is expected to be around forever, it might not be something you'd want to use for the .info file. From veljko3 at gmail.com Mon Feb 11 10:19:02 2013 From: veljko3 at gmail.com (Veljko) Date: Mon, 11 Feb 2013 11:19:02 +0100 Subject: [Slackbuilds-users] mitter In-Reply-To: References: <20130210230857.GA4979@angelina.example.org> Message-ID: <20130211101902.GA6885@angelina.example.org> On Sun, Feb 10, 2013 at 07:19:20PM -0500, B Watson wrote: > On 2/10/13, Veljko wrote: > > I can't access it's homepage on google code. Moved? Dead? > > There's a copy here with matching md5sum: > > http://pkgs.fedoraproject.org/repo/pkgs/mitter/mitter-0.4.5.tar.gz/0432f3d2d00e8d048bf0839e2d857e51/mitter-0.4.5.tar.gz > > Don't know if that URL is expected to be around forever, it might not > be something you'd want to use for the .info file. Thanks, that link works. Regards, Veljko From erik at slackbuilds.org Thu Feb 14 06:47:19 2013 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 14 Feb 2013 00:47:19 -0600 Subject: [Slackbuilds-users] Updates - 20130214.1 Message-ID: <20130214004719.1352415b@shaggy.doo> Thu Feb 14 06:30:40 UTC 2013 academic/wxmacmolplt: Updated for version 7.4.4. audio/audacity: Updated for version 2.0.3. audio/cwstation: Added (A morse code trainer) audio/faust: Added (Functional Audio Stream) audio/fmit: Added (Free Music Instrument Tuner) audio/nas: Minor fixes, added rc.* file. audio/shell-fm: Updated for version git20130207. audio/wavbreaker: Updated for version 0.11. desktop/evilwm: Added (minimalist window manager for X) desktop/rootactions_servicemenu: Updated for version 2.7.3. desktop/yawp: Updated for version 0.4.3. development/4th: Updated for version 3.62.0. development/gtest: Added (Google C++ Testing Framework) development/leveldb: Updated for version 1.9.0. development/mutagen: Updated for version 1.21. development/ne: Updated for version 2.5. development/snappy: Added (A fast compressor/decompressor) development/tiled-qt: Updated for version 0.9.0. development/trac: Updated for version 1.0.1. games/alienarena: Updated for version 7.65. games/mame: Updated for version 0.148. games/naev: Added (2d space trading game) games/nestopia: Updated for version 1.44. games/playonlinux: Updated for version 4.1.9. games/qmc2: Updated for version 0.38. games/robotfindskitten: Updated for version 2.7182818.701. games/tt: Added (Tetris for Terminals) games/vbam: Updated for version r1159. games/yamagi-quake2: Fix for missing stuff/yq2.cfg in docs. graphics/graphviz: Updated for version 2.30.0. graphics/mypaint: Note scons dependency in .info file graphics/photo: Updated for version 0.9.1. graphics/yed: Updated for version 3.10.1. libraries/gtksourceview3: Updated for version 3.7.2. libraries/harfbuzz: Updated for version 0.9.12. libraries/libee: Added (Event Expression Library inspired by CEE) libraries/libestr: Added (some essentials for string handling) libraries/lksctp-tools: Updated for version 1.0.13. misc/dvtm: Updated for version 0.8. multimedia/flash-player-plugin: Updated for version 11.2.202.270. multimedia/youtube-viewer: Added (browse YouTube videos from a terminal) network/arpwatch: Fixed slack-desc formatting network/eiskaltdcpp: Added (QT4 File Sharing) network/hydra: Updated for version 7.4.2. network/midori: Updated for version 0.4.8. network/mod_auth_kerb: Added (Kerberos Module for Apache) network/mod_dnssd: Added (dns-sd/zeroconf/avahi module for httpd) network/mpop: Updated for version 1.0.27. network/ngircd: Updated for version 20.1. network/node: Updated for version 0.8.17. network/openvswitch: Updated for version 1.4.5. network/pyNeighborhood: Updated for version bzr20130124. network/razor-agents: Added (collaborative spam detection) network/skype4pidgin: Updated for version r654. network/synergy: Added (Control sharing over the network) network/teamviewer: New maintainer. network/uwsgi: Updated for version 1.4.4. network/xtables-addons: Updated for version 1.47. network/yturl: Added (get direct URLs to YouTube videos) office/JabRef: Added (Reference Manager) office/ProjectLibre: Updated for version 1.5.3. office/flowkeeper: Added (Java-based timer for Pomodoro Technique(R)) office/myrulib: Updated for version 0.29.12. perl/perl-SNMP-Info: Added (SNMP::Info) python/Markdown: Added (Python implementation of Markdown) python/Pyro4: Updated for version 4.17. python/blinker: Added (Python module for object-to-object and broadcast signaling) python/feedgenerator: Added (Atom/RSS feed generator Python module) python/pattern: Added (a web mining module for Python) python/pep8: Updated for version 1.4.1. python/python-urllib3: Added (HTTP library) python/python3: More path fixes; use system expat and libffi python/sippy: Added (Sippy B2BUA) python/webassets: Added (Media asset management for Python) system/adobe-source-code-pro-font: Updated for version 1.017. system/bindfs: Updated for version 1.11. system/blake2: Updated for version 20130131. system/cassandra-gui: Added (Cassandra GUI Project) system/dar: Updated for version 2.4.9. system/dateutils: Updated for version 0.2.4. system/dfc: Updated for version 3.0.1. system/efibootmgr: Added (Tool to manipulate the EFI/UEFI Boot Manager) system/fsviewer: Added (NextStep-like file browser) system/grub2: Added update-grub script. system/innoextract: Added (Unpacker for Inno Setup installers) system/openct: Minor fixes and updated download link. system/opensc: Updated for version 0.13.0. system/paxctl: Added (PaX control program) system/pcsc-lite: Updated for version 1.8.8. system/percona-xtrabackup: Fixed CFLAGS and innobackupex script. system/redis: Updated for version 2.6.9. system/regionset: Updated for version 0.2. system/sbotools: Added (ports-like interface to slackbuilds.org) system/sudosh2: Added (tool for server auditing and shell reporting) system/vifm: Updated for version 0.7.4b. system/xen: Added (the Xen virtualization hypervisor) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From chess at chessgriffin.com Thu Feb 14 19:32:45 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 14 Feb 2013 14:32:45 -0500 Subject: [Slackbuilds-users] 2 Issues Message-ID: <1360870365.29281.140661191572441.0F0A0596@webmail.messagingengine.com> 1. MD5SUM for faenza-icon-theme is incorrect. The .info file has: 08a9d1567ee6e90dd5e2c271461c7390 should be: e9bd6106d13017ce06d24b586259ae9c 2. Download for epdfview fails - the home page (http://trac.emma-soft.com/epdfview/) seems to be gone so maybe a download from freebsd distfiles would work in the interim: http://ftp.freebsd.org/pub/FreeBSD/distfiles/epdfview-0.1.8.tar.bz2 -- Chess Griffin From larryhaja at gmail.com Thu Feb 14 21:14:55 2013 From: larryhaja at gmail.com (Larry Hajali) Date: Thu, 14 Feb 2013 13:14:55 -0800 Subject: [Slackbuilds-users] 2 Issues In-Reply-To: <1360870365.29281.140661191572441.0F0A0596@webmail.messagingengine.com> References: <1360870365.29281.140661191572441.0F0A0596@webmail.messagingengine.com> Message-ID: Sorry, to hijack this thread but there is one more issue. libmicrohttpd version 0.9.13 is no longer available. Minimum version available is 0.9.16. I have tested the newest one available for version 0.9.25 and it works with the current libmicrohttpd.SlackBuild with only a version bump. http://mirror.clarkson.edu/gnu/gnu/libmicrohttpd/libmicrohttpd-0.9.25.tar.gz I contacted the maintainer located in the libmicrohttpd.info file over a week ago but haven't heard anything back. --Larry On Thu, Feb 14, 2013 at 11:32 AM, Chess Griffin wrote: > 1. MD5SUM for faenza-icon-theme is incorrect. The .info file has: > > 08a9d1567ee6e90dd5e2c271461c7390 > > should be: > > e9bd6106d13017ce06d24b586259ae9c > > 2. Download for epdfview fails - the home page > (http://trac.emma-soft.com/epdfview/) seems to be gone so maybe a > download from freebsd distfiles would work in the interim: > > http://ftp.freebsd.org/pub/FreeBSD/distfiles/epdfview-0.1.8.tar.bz2 > > -- > Chess Griffin > _______________________________________________ > 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 gmail.com Fri Feb 15 01:19:19 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Fri, 15 Feb 2013 08:19:19 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) Message-ID: Hi, I'm planning to submit teamviewer 8 beta into SBo, but i will need further testing on this SlackBuild script Why: - TeamViewer 8 has been released on other platform (Windows and Mac) and currently it's still beta on Linux platform - When trying to connect to a host which has been upgraded to Teamviewer 8, the linux client version 7 will fail and demanding for upgrade I have put this SlackBuild in my SlackHacks for some time and i got several feedbacks, mostly from Ponce, but i will need more testing, mostly those who uses x86_64 architectures. I have been using it on my machine (32 bit) and so far, everything works as usual like in version 7 Thanks in advance -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com -------------- next part -------------- A non-text attachment was scrubbed... Name: teamviewer.tar.gz Type: application/x-gzip Size: 3543 bytes Desc: not available URL: From burningc at sdf.org Fri Feb 15 14:42:02 2013 From: burningc at sdf.org (Glenn Becker) Date: Fri, 15 Feb 2013 14:42:02 +0000 (UTC) Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: Hi Willy, > I'm planning to submit teamviewer 8 beta into SBo, but i will need > further testing on this SlackBuild script > > Why: > - TeamViewer 8 has been released on other platform (Windows and Mac) > and currently it's still beta on Linux platform > - When trying to connect to a host which has been upgraded to > Teamviewer 8, the linux client version 7 will fail and demanding for > upgrade > > I have put this SlackBuild in my SlackHacks for some time and i got > several feedbacks, mostly from Ponce, but i will need more testing, > mostly those who uses x86_64 architectures. I have been using it on my > machine (32 bit) and so far, everything works as usual like in version > 7 I run 2 Slack 64 boxes at home and I'd be happy to look at this over the weekend -- I have a 3-day-er coming up. /Glenn +---------------------------------------------+ Glenn Becker - burningc at sdf.org SDF Public Access UNIX System - http://sdf.org +---------------------------------------------+ From binhvng at gmail.com Fri Feb 15 13:56:25 2013 From: binhvng at gmail.com (Binh Nguyen) Date: Fri, 15 Feb 2013 20:56:25 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: Willy, > - TeamViewer 8 has been released on other platform (Windows and Mac) > and currently it's still beta on Linux platform It's out of beta as of now. > - When trying to connect to a host which has been upgraded to > Teamviewer 8, the linux client version 7 will fail and demanding for > upgrade I also encountered this in the past when using TV7 on Linux to connect to a Windows host with TV6. I didn't have a chance to test on other conditions. It's an irritating requirement since they upgrade major versions over not-so-long periods. By the way, I see that you get rid of $MAIN_VER and use the hard-coded teamviewer8. Yes, it's easier to read, but you would need to edit several places when version 9 comes out. Personally, I would use $MAIN_VER instead. Of course if they change the file structure again, it will not have much advantage since you have to edit those places anyway. -- Binh From willysr at gmail.com Fri Feb 15 19:19:58 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 16 Feb 2013 02:19:58 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: > > > It's out of beta as of now. Didn't notice that Thanks, i will check the latest version this morning and update my script By the way, I see that you get rid of $MAIN_VER and use the hard-coded > teamviewer8. Yes, it's easier to read, but you would need to edit > several places when version 9 comes out. Personally, I would use > $MAIN_VER instead. Of course if they change the file structure again, > it will not have much advantage since you have to edit those places > anyway. > > > No problem as it increases readibility of the code and it's easier to > maintenance for me A simple find and replace will do if version 9 comes out :) -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tonyoclayton at gmail.com Sat Feb 16 01:38:46 2013 From: tonyoclayton at gmail.com (Tony Clayton) Date: Fri, 15 Feb 2013 20:38:46 -0500 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: Willy Once I changed the VERSION to 8.0.17147 I was able to build and install it on my x64. Then I had to run teamviewer --daemon enable and teamviewer --daemon start then it opened fine for me thanks. On Thu, Feb 14, 2013 at 8:19 PM, Willy Sudiarto Raharjo wrote: > Hi, > > I'm planning to submit teamviewer 8 beta into SBo, but i will need > further testing on this SlackBuild script > > Why: > - TeamViewer 8 has been released on other platform (Windows and Mac) > and currently it's still beta on Linux platform > - When trying to connect to a host which has been upgraded to > Teamviewer 8, the linux client version 7 will fail and demanding for > upgrade > > I have put this SlackBuild in my SlackHacks for some time and i got > several feedbacks, mostly from Ponce, but i will need more testing, > mostly those who uses x86_64 architectures. I have been using it on my > machine (32 bit) and so far, everything works as usual like in version > 7 > > Thanks in advance > > > -- > Willy Sudiarto Raharjo > Personal Blog : http://willysr.blogspot.com > Linux Blog: http://slackblogs.blogspot.com > > _______________________________________________ > 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 gmail.com Sat Feb 16 02:22:15 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 16 Feb 2013 09:22:15 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: > Once I changed the VERSION to 8.0.17147 I was able to build and install it > on my x64. > Then I had to run teamviewer --daemon enable and teamviewer --daemon start > then it opened fine for me thanks. Why don't you use /etc/rc.d/rc.teamviewerd start ? It's already handled there :) -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From willysr at gmail.com Sat Feb 16 02:26:25 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 16 Feb 2013 09:26:25 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: >> It's out of beta as of now. Since it's now out of Beta, i have updated the script to reflect the changes I have also updated the README: The 64-bit package now works in a native environment. For 64-bit machines with multi-lib environment, please use the 32 bit package as this is a 32-bit/multi-arch package and it requires these 32-bit packages: glibc, zlib, freetype, alsa-lib, GConf. ========================================================================================= This is based on the information i got here https://www.teamviewer.com/en/help/363-How-do-I-install-TeamViewer-on-my-Linux-distribution.aspx Notes to Multiarch: On newer 64-bit DEB-systems with Multiarch-support (Debian 7) teamviewer_linux_x64.deb cannot be installed because the package ia32-libs is not available anymore on these systems. In this case you can use teamviewer_linux.deb instead. ========================================================================================= I still need to verify whether a native 64 bit does works or does it stilll need a multi-lib environment i'm planning to install Slackware64-14.0 on a virtual machine to try it, but i would be happy if someone who uses 64-bit machines (both native and multi-lib) can also test this -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com -------------- next part -------------- A non-text attachment was scrubbed... Name: teamviewer.tar.gz Type: application/x-gzip Size: 3617 bytes Desc: not available URL: From chess at chessgriffin.com Sat Feb 16 04:58:37 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 15 Feb 2013 23:58:37 -0500 Subject: [Slackbuilds-users] Odd character in JSONObject.info file Message-ID: <20130215235837.7ee5867e@slack64.localdomain> If you open up JSONObject.info in nano (not seen in vim), there is an odd character at the start of the PRGNAM= line: 1??PRGNAM=JSONObject While parsing the .info files for PRGNAM, bash appears to try and execute this line, which may be a security issue. Anyway, a simple edit of that file in the repo should take care of it. -- Chess Griffin From yalhcru at gmail.com Sat Feb 16 08:50:26 2013 From: yalhcru at gmail.com (B Watson) Date: Sat, 16 Feb 2013 03:50:26 -0500 Subject: [Slackbuilds-users] Odd character in JSONObject.info file In-Reply-To: <20130215235837.7ee5867e@slack64.localdomain> References: <20130215235837.7ee5867e@slack64.localdomain> Message-ID: On 2/15/13, Chess Griffin wrote: > If you open up JSONObject.info in nano (not seen in vim), there is an > odd character at the start of the PRGNAM= line: > > 1??PRGNAM=JSONObject It's a BOM (byte order marker). Doesn't show up in vim because vim is unicode-aware and will ignore it. See http://www.unicode.org/faq/utf_bom.html#BOM It was probably put there by the submitter's editor because his first name (M?rio) includes a non-ASCII character. > While parsing the .info files for PRGNAM, bash appears to try and > execute this line, which may be a security issue. Anyway, a simple > edit of that file in the repo should take care of it. It's not so much of security risk, but it'll break any script (such as sbopkg) that expects to parse PRGNAM out of the .info file. Try: ( set +x ; . JSONObject.info ; echo $PRGNAM ) It'd be worthwhile to add a check to the site's upload handler so it'll reject text files (.SlackBuild, .info, slack-desc) that start with a BOM, or maybe it could just remove the BOM. From vito.detullio at gmail.com Sat Feb 16 09:52:14 2013 From: vito.detullio at gmail.com (Vito De Tullio) Date: Sat, 16 Feb 2013 10:52:14 +0100 Subject: [Slackbuilds-users] Odd character in JSONObject.info file References: <20130215235837.7ee5867e@slack64.localdomain> Message-ID: Chess Griffin wrote: > If you open up JSONObject.info in nano (not seen in vim), there is an > odd character at the start of the PRGNAM= line: > > 1??PRGNAM=JSONObject > > While parsing the .info files for PRGNAM, bash appears to try and > execute this line, which may be a security issue. Anyway, a simple > edit of that file in the repo should take care of it. it's the BOM... but why is it there? shouldn't the file contains just ASCII characters?? btw: it "breaks" sbopkg: # sbopkg -o [ Checking for obsolete sources ] This may take a few moments. Press to abort. 52%[========================================================================================================== ]/var/lib/sbopkg/SBo/14.0/development/JSONObject/JSONObject.info: line 1: PRGNAM=JSONObject: command not found 100%[=============================================================================================================================================================================================================] It appears there are no obsolete sources in /var/cache/sbopkg. # -- ZeD From tonyoclayton at gmail.com Sat Feb 16 12:30:03 2013 From: tonyoclayton at gmail.com (Tony Clayton) Date: Sat, 16 Feb 2013 07:30:03 -0500 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: my system is also multi-lib On Fri, Feb 15, 2013 at 9:26 PM, Willy Sudiarto Raharjo wrote: > >> It's out of beta as of now. > > Since it's now out of Beta, i have updated the script to reflect the > changes > > I have also updated the README: > > The 64-bit package now works in a native environment. > > For 64-bit machines with multi-lib environment, please use the 32 bit > package as this is a 32-bit/multi-arch package and it requires these > 32-bit packages: glibc, zlib, freetype, alsa-lib, GConf. > > > ========================================================================================= > This is based on the information i got here > > https://www.teamviewer.com/en/help/363-How-do-I-install-TeamViewer-on-my-Linux-distribution.aspx > Notes to Multiarch: > > On newer 64-bit DEB-systems with Multiarch-support (Debian 7) > teamviewer_linux_x64.deb cannot be installed because the package > ia32-libs is not available anymore on these systems. In this case you > can use teamviewer_linux.deb instead. > > ========================================================================================= > > I still need to verify whether a native 64 bit does works or does it > stilll need a multi-lib environment > > i'm planning to install Slackware64-14.0 on a virtual machine to try > it, but i would be happy if someone who uses 64-bit machines (both > native and multi-lib) can also test this > > > -- > Willy Sudiarto Raharjo > Personal Blog : http://willysr.blogspot.com > Linux Blog: http://slackblogs.blogspot.com > > _______________________________________________ > 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 gmail.com Sat Feb 16 12:48:52 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 16 Feb 2013 19:48:52 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: > my system is also multi-lib And how was it? did you use the 32 bit multiarch deb package? Did it worked well on multi-lib environment? I'm on progress of installing Slackware64-14.0 on my VMWare and i will test the native 64-bit apps when it's done :) -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From yalhcru at gmail.com Sat Feb 16 11:32:24 2013 From: yalhcru at gmail.com (B Watson) Date: Sat, 16 Feb 2013 06:32:24 -0500 Subject: [Slackbuilds-users] Odd character in JSONObject.info file In-Reply-To: References: <20130215235837.7ee5867e@slack64.localdomain> Message-ID: On 2/16/13, Vito De Tullio wrote: > it's the BOM... Someone set up us the BOM! (sorry, couldn't resist) > but why is it there? shouldn't the file contains just ASCII > characters?? Nowhere on the slackbuilds.org site does it say that. And the submitter's got a non-ASCII character in his first name (the letter ?), so the MAINTAINER field has that character in it because that's how he spells his name. He happened to use a text editor that adds the BOM when it's writing a UTF-8 file (which I think is a bad idea, but is a pretty standard thing in some circles), and the checking code on the site didn't catch it, possibly because it's using a library that handles the BOM transparently (so the code using it, never sees the BOM). >From a quick look at the .info files, it appears that all but two of them are either ASCII-only, or Unicode UTF-8 without the BOM. ASCII is a subset of Unicode (it's just the first 128 characters), so really out of 3500+ .info files, all but two of them are Unicode text with UTF-8 encoding. So maybe UTF-8 without BOM should be the standard, and the site should say so, and kick out an error if someone drops a BOM on it... The two that are different are JSONObject.info (UTF-8 with the BOM) and development/snappy/snappy.info (it's ISO-8859, not Unicode at all). However, snappy.info doesn't break sbopkg, so it's not really a problem. From tonyoclayton at gmail.com Sat Feb 16 13:18:11 2013 From: tonyoclayton at gmail.com (Tony Clayton) Date: Sat, 16 Feb 2013 08:18:11 -0500 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: in progress On Sat, Feb 16, 2013 at 7:48 AM, Willy Sudiarto Raharjo wrote: > > my system is also multi-lib > > And how was it? > did you use the 32 bit multiarch deb package? > Did it worked well on multi-lib environment? > > I'm on progress of installing Slackware64-14.0 on my VMWare and i will > test the native 64-bit apps when it's done :) > > > -- > Willy Sudiarto Raharjo > Personal Blog : http://willysr.blogspot.com > Linux Blog: http://slackblogs.blogspot.com > _______________________________________________ > 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 tonyoclayton at gmail.com Sat Feb 16 13:17:34 2013 From: tonyoclayton at gmail.com (Tony Clayton) Date: Sat, 16 Feb 2013 08:17:34 -0500 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: still early, but I don't remember doing that for version 7. but know I now thanks. On Fri, Feb 15, 2013 at 9:22 PM, Willy Sudiarto Raharjo wrote: > > Once I changed the VERSION to 8.0.17147 I was able to build and install > it > > on my x64. > > Then I had to run teamviewer --daemon enable and teamviewer --daemon > start > > then it opened fine for me thanks. > > Why don't you use /etc/rc.d/rc.teamviewerd start ? > It's already handled there :) > > > -- > Willy Sudiarto Raharjo > Personal Blog : http://willysr.blogspot.com > Linux Blog: http://slackblogs.blogspot.com > _______________________________________________ > 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 gmail.com Sat Feb 16 13:29:59 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 16 Feb 2013 20:29:59 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: > still early, but I don't remember doing that for version 7. > but know I now thanks. Yeah, it's a new feature that only existed in Version 8 They added a new service called teamviewerd and without starting this service, TeamViewer is unusable -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From willysr at gmail.com Sat Feb 16 13:50:04 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 16 Feb 2013 20:50:04 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: > I run 2 Slack 64 boxes at home and I'd be happy to look at this over the > weekend -- I have a 3-day-er coming up. It seems that native x86_64 is still not yet supported you will need to use multilib environment for this one i have tested on native Slackware64 and i got /etc/rc.d/rc.teamviewerd start Starting TeamViewer Daemon /etc/rc.d/rc.teamviewerd: line 14: /opt/teamviewer8/tv_bin/teamviewerd: No such file or directory -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From Bradley at NorthTech.US Sat Feb 16 14:09:28 2013 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Sat, 16 Feb 2013 06:09:28 -0800 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: References: Message-ID: <511F9318.3090605@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On 02/15/2013 06:26 PM, Willy Sudiarto Raharjo wrote: >>> It's out of beta as of now. > > Since it's now out of Beta, i have updated the script to reflect the changes > > I have also updated the README: > > The 64-bit package now works in a native environment. Not happening for me over here Willy. bummer, and I'm not inclined to install multi-lib either. What might I do regarding package creation with static libs or is that likely to tank too? > > For 64-bit machines with multi-lib environment, please use the 32 bit > package as this is a 32-bit/multi-arch package and it requires these > 32-bit packages: glibc, zlib, freetype, alsa-lib, GConf. > > ========================================================================================= > This is based on the information i got here > https://www.teamviewer.com/en/help/363-How-do-I-install-TeamViewer-on-my-Linux-distribution.aspx > Notes to Multiarch: > > On newer 64-bit DEB-systems with Multiarch-support (Debian 7) > teamviewer_linux_x64.deb cannot be installed because the package > ia32-libs is not available anymore on these systems. In this case you > can use teamviewer_linux.deb instead. > ========================================================================================= > > I still need to verify whether a native 64 bit does works or does it > stilll need a multi-lib environment > > i'm planning to install Slackware64-14.0 on a virtual machine to try > it, but i would be happy if someone who uses 64-bit machines (both > native and multi-lib) can also test this > > > > > > _______________________________________________ > 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/ > - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJRH5MYAAoJEE1wgkIhr9j3ZTIIAKOW4OsR/2ZiGa7ul3ELMXlv 2BjHmHUKpEeKhiB1A4RnB55e7Frbm+05AIpZqFOnhnY+Pcw1mLyY6Ydm2V15NBL0 bJ6ySYOGoduHWcOfHNZuALWdjfW/jpLi8+TCoXSTLPTEaP/kCKYaXnaDRzR/Fpo3 wnJHzfeXu6S14XchxaOv35Lc9MhCBpAnPzyjT0RgItPIV6zF6gVWnJMxAh0t7cL1 FVjrBBdOn5oVSN8ZAd8YG7krk6mbqhvBBZIKCDCdVxIRDvZcxGNLQlFLrEBLn/Mk Raldv68Ri+slvtAkyLGSI3PBFIc60LMOtevkUi+8oNx4ySKwLrGBKaLQCcoMkRQ= =47CQ -----END PGP SIGNATURE----- From willysr at gmail.com Sat Feb 16 14:30:03 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 16 Feb 2013 21:30:03 +0700 Subject: [Slackbuilds-users] Request For Testing: Teamviewer 8 (Beta) In-Reply-To: <511F9318.3090605@NorthTech.US> References: <511F9318.3090605@NorthTech.US> Message-ID: >> The 64-bit package now works in a native environment. > > Not happening for me over here Willy. bummer, and I'm not inclined to > install multi-lib either. > > What might I do regarding package creation with static libs or is that > likely to tank too? The problem is because TeamViewer is running on top of wine and that is 32-bit spesific application, so not likely to work on Native 64-bit machines without multi-lib i'm afraid I have updated the README in my SlackHacks about the availability of 64-bit native environment and reverted it back to the old README like in SBo page -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From panych.y at gmail.com Sat Feb 16 10:37:12 2013 From: panych.y at gmail.com (Yaroslav Panych) Date: Sat, 16 Feb 2013 12:37:12 +0200 Subject: [Slackbuilds-users] Odd character in JSONObject.info file In-Reply-To: References: <20130215235837.7ee5867e@slack64.localdomain> Message-ID: Confirmed, it is BOM there(and not only in .info file). And it there more than two. weeks. But SlackBuild still buildable. 2013/2/16 Vito De Tullio : > Chess Griffin wrote: > >> If you open up JSONObject.info in nano (not seen in vim), there is an >> odd character at the start of the PRGNAM= line: >> >> 1??PRGNAM=JSONObject >> >> While parsing the .info files for PRGNAM, bash appears to try and >> execute this line, which may be a security issue. Anyway, a simple >> edit of that file in the repo should take care of it. > > it's the BOM... but why is it there? shouldn't the file contains just ASCII > characters?? > > btw: it "breaks" sbopkg: > > # sbopkg -o > [ Checking for obsolete sources ] > This may take a few moments. Press to abort. > 52%[========================================================================================================== > ]/var/lib/sbopkg/SBo/14.0/development/JSONObject/JSONObject.info: line 1: > PRGNAM=JSONObject: command not found > 100%[=============================================================================================================================================================================================================] > It appears there are no obsolete sources in /var/cache/sbopkg. > # > > > > -- > ZeD > > _______________________________________________ > 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 hba.nihilismus at gmail.com Sun Feb 17 01:26:28 2013 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sat, 16 Feb 2013 19:26:28 -0600 Subject: [Slackbuilds-users] Odd character in JSONObject.info file In-Reply-To: References: <20130215235837.7ee5867e@slack64.localdomain> Message-ID: On Sat, Feb 16, 2013 at 4:37 AM, Yaroslav Panych wrote: > Confirmed, it is BOM there(and not only in .info file). And it there > more than two. weeks. But SlackBuild still buildable. > > 2013/2/16 Vito De Tullio : >> Chess Griffin wrote: >> >>> If you open up JSONObject.info in nano (not seen in vim), there is an >>> odd character at the start of the PRGNAM= line: >>> >>> 1??PRGNAM=JSONObject >>> >>> While parsing the .info files for PRGNAM, bash appears to try and >>> execute this line, which may be a security issue. Anyway, a simple >>> edit of that file in the repo should take care of it. >> >> it's the BOM... but why is it there? shouldn't the file contains just ASCII >> characters?? >> >> btw: it "breaks" sbopkg: >> >> # sbopkg -o >> [ Checking for obsolete sources ] >> This may take a few moments. Press to abort. >> 52%[========================================================================================================== >> ]/var/lib/sbopkg/SBo/14.0/development/JSONObject/JSONObject.info: line 1: >> PRGNAM=JSONObject: command not found >> 100%[=============================================================================================================================================================================================================] >> It appears there are no obsolete sources in /var/cache/sbopkg. >> # >> >> >> >> -- >> ZeD >> >> _______________________________________________ >> 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/ > All JSONObject's files are UTF-8 with BOM: JSONObject.SlackBuild: Bourne-Again shell script, UTF-8 Unicode (with BOM) text executable JSONObject.info: UTF-8 Unicode (with BOM) text README: UTF-8 Unicode (with BOM) text slack-desc: UTF-8 Unicode (with BOM) text And BTW, JSONObject.SlackBuild has as shebang "#!/bin/bash" and, as far as i know, it should be "#!/bin/sh" -- - hba | Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. http://hba.dyndns.info | irc://irc.freenode.org/hba,isnick,needpass https://github.com/nihilismus | https://bitbucket.org/nihilismus https://twitter.com/nihilipster | http://www.last.fm/user/nihilipster From erik at slackbuilds.org Sun Feb 17 01:40:34 2013 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 16 Feb 2013 19:40:34 -0600 Subject: [Slackbuilds-users] Odd character in JSONObject.info file In-Reply-To: References: <20130215235837.7ee5867e@slack64.localdomain> Message-ID: <20130216194034.751b5e06@shaggy.doo> On Sat, 16 Feb 2013 03:50:26 -0500 B Watson wrote: > On 2/15/13, Chess Griffin wrote: > > If you open up JSONObject.info in nano (not seen in vim), there is an > > odd character at the start of the PRGNAM= line: > > > > 1??PRGNAM=JSONObject > > It's a BOM (byte order marker). Doesn't show up in vim > because vim is unicode-aware and will ignore it. See > http://www.unicode.org/faq/utf_bom.html#BOM Thanks for the report and information, fixed in my branch. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From chess at chessgriffin.com Sun Feb 17 05:19:35 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Sun, 17 Feb 2013 00:19:35 -0500 Subject: [Slackbuilds-users] Odd character in JSONObject.info file In-Reply-To: <20130216194034.751b5e06@shaggy.doo> References: <20130215235837.7ee5867e@slack64.localdomain> <20130216194034.751b5e06@shaggy.doo> Message-ID: <20130217001935.677263ce@slack64.localdomain> On Sat, 16 Feb 2013 19:40:34 -0600 Erik Hanson wrote: > On Sat, 16 Feb 2013 03:50:26 -0500 > B Watson wrote: > > > On 2/15/13, Chess Griffin wrote: > > > If you open up JSONObject.info in nano (not seen in vim), there > > > is an odd character at the start of the PRGNAM= line: > > > > > > 1??PRGNAM=JSONObject > > > > It's a BOM (byte order marker). Doesn't show up in vim > > because vim is unicode-aware and will ignore it. See > > http://www.unicode.org/faq/utf_bom.html#BOM > > Thanks for the report and information, fixed in my branch. > > Thanks for all the replies everybody (I learn something every day -- didn't know about the BOM) and thanks, Erik, for fixing it in your branch. Not a big deal, I guess, but I thought I'd mention it just in case the admins wanted to address it. -- Chess Griffin From burningc at SDF.ORG Mon Feb 18 15:43:11 2013 From: burningc at SDF.ORG (Glenn Becker) Date: Mon, 18 Feb 2013 15:43:11 +0000 (UTC) Subject: [Slackbuilds-users] MendeleyDesktop In-Reply-To: References: Message-ID: > I was unable to get the MendeleyDesktop SlackBuild to work, so wrote the > maintainer. He isn't using the app any more and encouraged me to take it > over if I wanted. > > So I am going to give it a shot. I am having second (and third) thoughts about a SlackBuild for this application. Source code seems to no longer be available ... plus one has to log in to the Mendeley site to download the application. Maybe someone will correct me if I am wrong, but it doesn't seem to make much sense to me to make a SlackBuild for this. /G +---------------------------------------------+ Glenn Becker - burningc at sdf.org SDF Public Access UNIX System - http://sdf.org +---------------------------------------------+ From rworkman at slackbuilds.org Mon Feb 18 16:34:20 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 18 Feb 2013 10:34:20 -0600 Subject: [Slackbuilds-users] 2 Issues In-Reply-To: <1360870365.29281.140661191572441.0F0A0596@webmail.messagingengine.com> References: <1360870365.29281.140661191572441.0F0A0596@webmail.messagingengine.com> Message-ID: <20130218103420.5053a8ec@home.rlworkman.net> On Thu, 14 Feb 2013 14:32:45 -0500 Chess Griffin wrote: > 1. MD5SUM for faenza-icon-theme is incorrect. The .info file has: > > 08a9d1567ee6e90dd5e2c271461c7390 > > should be: > > e9bd6106d13017ce06d24b586259ae9c > > 2. Download for epdfview fails - the home page > (http://trac.emma-soft.com/epdfview/) seems to be gone so maybe a > download from freebsd distfiles would work in the interim: > > http://ftp.freebsd.org/pub/FreeBSD/distfiles/epdfview-0.1.8.tar.bz2 Both fixed in my git branch ; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Feb 18 16:36:02 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 18 Feb 2013 10:36:02 -0600 Subject: [Slackbuilds-users] 2 Issues In-Reply-To: References: <1360870365.29281.140661191572441.0F0A0596@webmail.messagingengine.com> Message-ID: <20130218103602.64d0f1d6@home.rlworkman.net> On Thu, 14 Feb 2013 13:14:55 -0800 Larry Hajali wrote: > Sorry, to hijack this thread but there is one more issue. > > libmicrohttpd version 0.9.13 is no longer available. Minimum version > available is 0.9.16. I have tested the newest one available for > version 0.9.25 and it works with the current libmicrohttpd.SlackBuild > with only a version bump. > > http://mirror.clarkson.edu/gnu/gnu/libmicrohttpd/libmicrohttpd-0.9.25.tar.gz > > I contacted the maintainer located in the libmicrohttpd.info file > over a week ago but haven't heard anything back. I stumbled across the same thing when building xbmc recently, so I put a commit in a separate git branch which updates to 0.9.25. Let me know if you don't hear back in another week or so and we'll look into merging it. Thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From melikamp at melikamp.com Tue Feb 19 01:48:45 2013 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Mon, 18 Feb 2013 20:48:45 -0500 Subject: [Slackbuilds-users] lmms on x64 In-Reply-To: References: Message-ID: <5122D9FD.7070907@melikamp.com> I have a weird behavior with lmms-0.4.13-x86_64-1 build (via sbopkg, vanilla). On startup it says: > The plugin "tripleoscillator" wasn't found or could not be loaded! > Reason: "Cannot load library /usr//usr/lib64/lmms/tripleoscillator: > (/usr//usr/lib64/lmms/libtripleoscillator.so: > cannot open shared object file: No such file or directory)" The corresponding path setting in Preferences has no effect, as far as I can tell. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: From j at dawnrazor.net Tue Feb 19 03:32:34 2013 From: j at dawnrazor.net (J) Date: Mon, 18 Feb 2013 21:32:34 -0600 Subject: [Slackbuilds-users] lmms on x64 In-Reply-To: <5122D9FD.7070907@melikamp.com> References: <5122D9FD.7070907@melikamp.com> Message-ID: <20130218213234.Horde.p4YQjn-XL-7phES1ibwo8g1@mail.dawnrazor.net> line 63 in the SlackBuild: -DCMAKE_INSTALL_LIBDIR=/usr/lib${LIBDIRSUFFIX} \ this causes LMMS to think its libs are under something like /usr/lib/lib64 or such, even though they're not. so it acts funny, can't find its samples or presets, etc. remove that line from the slackbuild and rebuild, and you should be good to go. Quoting Ivan Zaigralin : > I have a weird behavior with lmms-0.4.13-x86_64-1 build > (via sbopkg, vanilla). On startup it says: > >> The plugin "tripleoscillator" wasn't found or could not be loaded! >> Reason: "Cannot load library /usr//usr/lib64/lmms/tripleoscillator: >> (/usr//usr/lib64/lmms/libtripleoscillator.so: >> cannot open shared object file: No such file or directory)" > > The corresponding path setting in Preferences has no effect, > as far as I can tell. From yalhcru at gmail.com Tue Feb 19 02:33:57 2013 From: yalhcru at gmail.com (B Watson) Date: Mon, 18 Feb 2013 21:33:57 -0500 Subject: [Slackbuilds-users] lmms on x64 In-Reply-To: <5122D9FD.7070907@melikamp.com> References: <5122D9FD.7070907@melikamp.com> Message-ID: On 2/18/13, Ivan Zaigralin wrote: >> The plugin "tripleoscillator" wasn't found or could not be loaded! Happens here too (Slackware64 14.0). >> Reason: "Cannot load library /usr//usr/lib64/lmms/tripleoscillator: >> (/usr//usr/lib64/lmms/libtripleoscillator.so: >> cannot open shared object file: No such file or directory)" /usr//usr/lib64 is an odd place to look for libraries. Changing the -DCMAKE_INSTALL_LIBDIR line to read: -DCMAKE_INSTALL_LIBDIR=lib${LIBDIRSUFFIX} seems to fix it (but I haven't tested it thoroughly, might break something else). The cmakelist appears to be adding the prefix to the libdir itself, so the libdir shouldn't also include the prefix... From binhvng at gmail.com Tue Feb 19 07:27:21 2013 From: binhvng at gmail.com (Binh Nguyen) Date: Tue, 19 Feb 2013 14:27:21 +0700 Subject: [Slackbuilds-users] MendeleyDesktop In-Reply-To: References: Message-ID: On Mon, Feb 18, 2013 at 10:43 PM, Glenn Becker wrote: > > ... plus one has to > log in to the Mendeley site to download the application. The current download links work fine here. I can also go to download page from the app's homepage using the link at the footer without logging-in. From burningc at SDF.ORG Tue Feb 19 12:26:26 2013 From: burningc at SDF.ORG (Glenn Becker) Date: Tue, 19 Feb 2013 12:26:26 +0000 (UTC) Subject: [Slackbuilds-users] MendeleyDesktop In-Reply-To: References: Message-ID: >> ... plus one has to >> log in to the Mendeley site to download the application. > > The current download links work fine here. I can also go to download > page from the app's homepage using the link at the footer without > logging-in. Well, the ones for the current SlackBuild are links to Amazon Web Services -- I thought perhaps the maintainer set those up (?). Thanks for pointing out the link in the Mendeley site's footer. /g +---------------------------------------------+ Glenn Becker - burningc at sdf.org SDF Public Access UNIX System - http://sdf.org +---------------------------------------------+ From belka.ew at gmail.com Wed Feb 20 10:41:03 2013 From: belka.ew at gmail.com (Eugen Wissner) Date: Wed, 20 Feb 2013 11:41:03 +0100 Subject: [Slackbuilds-users] rc.postfix Message-ID: Hi, rc.6 which is executed during shutdown/reboot sets PATH=/sbin:/etc:/bin:/usr/bin. If I want to stop postfix automatically in rc.6 or rc.local_shutdown I get an error "postfix can't be found" because postfix is in /usr/sbin. Wouldn't it be better to write the full path in rc.postfix: postfix_start() { /usr/sbin/postfix start } postfix_stop() { /usr/sbin/postfix stop } ? Best regards Eugene -------------- next part -------------- An HTML attachment was scrubbed... URL: From nishant at mnspace.net Wed Feb 20 14:00:00 2013 From: nishant at mnspace.net (Nishant Limbachia) Date: Wed, 20 Feb 2013 08:00:00 -0600 Subject: [Slackbuilds-users] rc.postfix In-Reply-To: References: Message-ID: <5124D6E0.1010108@mnspace.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/20/2013 04:41 AM, Eugen Wissner wrote: > Hi, > > rc.6 which is executed during shutdown/reboot sets > PATH=/sbin:/etc:/bin:/usr/bin. If I want to stop postfix automatically in > rc.6 or rc.local_shutdown I get an error "postfix can't be found" because > postfix is in /usr/sbin. Wouldn't it be better to write the full path in > rc.postfix: > > postfix_start() > { > /usr/sbin/postfix start > } > > postfix_stop() > { > /usr/sbin/postfix stop > } > ? > > Best regards > Eugene > > > > _______________________________________________ > 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 had the same issue and so instead of changing rc.6, I changed rc.postfix to include full path to postfix binary. Postfix also supports 'status' command from version 2.9.x, I believe. Here's the diff of rc.postfix I use on my system that is the enhanced version of the one on SBo. Thanks, - -- Nishant Limbachia nishant at mnspace.net GPG Key: 0x0FF9D6D5 GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEk1uAACgkQeG5dog/51tWJbgCfYv/2f1PSJCVr9WOCx0L2Gd09 6NwAnjBRVFYBUSChyfcJI+Ty5tpuukzU =SlMb -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- --- rc.postfix.SBo 2013-02-20 07:49:55.619007506 -0600 +++ rc.postfix 2013-02-20 07:49:12.753540045 -0600 @@ -22,12 +22,12 @@ postfix_start() { - postfix start + /usr/sbin/postfix start } postfix_stop() { - postfix stop + /usr/sbin/postfix stop } postfix_restart() @@ -38,7 +38,12 @@ postfix_reload() { - postfix reload + /usr/sbin/postfix reload +} + +postfix_status() +{ + /usr/sbin/postfix status } case $1 in @@ -54,6 +59,9 @@ 'reload') postfix_reload ;; +'status') + postfix_status + ;; *) - echo "usage $0 start|stop|restart|reload" + echo "usage $0 start|stop|restart|reload|status" esac From thedoogster at gmail.com Wed Feb 20 17:39:01 2013 From: thedoogster at gmail.com (Doogster) Date: Wed, 20 Feb 2013 09:39:01 -0800 Subject: [Slackbuilds-users] unrar should be discontinued Message-ID: The unrar SlackBuild should be discontinued. The current release of rar/unrar, the one you get from rarsoft's homepage, is 4.2.4. The current unrar SlackBuild builds 4.0.7, which is ridiculously ancient. I contacted the maintainer months ago and never got a response. We have a corresponding *rar* SlackBuild which is much more reasonably up to date (it builds 4.2.0). Its README file indicates that it can be set to build unrar, but this is not the default behavior because SBo has the unrar SlackBuild. I recommend pulling the unrar SlackBuild and setting the rar SlackBuild to build unrar. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Wed Feb 20 19:33:45 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 20 Feb 2013 11:33:45 -0800 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: References: Message-ID: Having a single script to build both makes sense. I vote yes. Ed On 2/20/13, Doogster wrote: > The unrar SlackBuild should be discontinued. > > The current release of rar/unrar, the one you get from rarsoft's homepage, > is 4.2.4. > > The current unrar SlackBuild builds 4.0.7, which is ridiculously ancient. I > contacted the maintainer months ago and never got a response. > > We have a corresponding *rar* SlackBuild which is much more reasonably up > to date (it builds 4.2.0). Its README file indicates that it can be set to > build unrar, but this is not the default behavior because SBo has the unrar > SlackBuild. > > I recommend pulling the unrar SlackBuild and setting the rar SlackBuild to > build unrar. > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From matteo.bernardini at gmail.com Wed Feb 20 20:25:41 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 20 Feb 2013 21:25:41 +0100 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: References: Message-ID: my 2 cents: - rar (with the optional unrar) is a shareware binary only release (a licence should be bought after a period of using it); - unrar/libunrar are built from the opensource unrarsrc release (latest is 4.2.4) and unifying them in a single slackbuild could be practical (and they could be in sync this way). Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From bocke at mycity.rs Wed Feb 20 20:46:55 2013 From: bocke at mycity.rs (Bojan Popovic) Date: Wed, 20 Feb 2013 21:46:55 +0100 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: References: Message-ID: <20130220214655.706d6d8a@deathstar.universe.org> @Matteo: Is libunrar built along with unrar? Or if not, does there exist an option to do so? If yes, that sounds sensible. I guess you are also suggesting to take over unrar (as you are the maintainer of libunrar)? If yes, I think that would be a good idea. Bojan. From bocke at mycity.rs Wed Feb 20 20:50:49 2013 From: bocke at mycity.rs (Bojan Popovic) Date: Wed, 20 Feb 2013 21:50:49 +0100 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: References: Message-ID: <20130220215049.7ccbe02b@deathstar.universe.org> I misread the name of the libunrar maintainer. Sorry Mario and Matteo for the confusion. Anyway, I support Matteo's idea. Bojan. From bocke at mycity.rs Wed Feb 20 20:35:24 2013 From: bocke at mycity.rs (Bojan Popovic) Date: Wed, 20 Feb 2013 21:35:24 +0100 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: References: Message-ID: <20130220213524.7abecdac@deathstar.universe.org> Hi, > The unrar SlackBuild should be discontinued. > Sorry, I don't agree. One important difference between rar and unrar is in their license terms. For example, unrar license states something like this: 3. The UnRAR utility may be freely distributed. It is allowed to distribute UnRAR inside of other software packages. while rar license states something like: 2. The software is distributed as try before you buy. This means that anyone may use the software during a test period of a maximum of 40 days at no charge. Following this test period, the user must purchase a license to continue using the software. There is a big difference in re-distributability of the resulting packages. So separate unrar is a sensible option. > The current unrar SlackBuild builds 4.0.7, which is ridiculously > ancient. I contacted the maintainer months ago and never got a > response. > I'm using a bunch of archivers/unarchivers on my machines and basically depend on any of them a lot. So it wouldn't be a problem to take over unrar if the current maintainer doesn't have time for it ATM. > I recommend pulling the unrar SlackBuild and setting the rar > SlackBuild to build unrar. The rar SlackBuild doesn't really "builds" unrar. If you change that setting it only installs the binary unrar which comes with rar distribution. Of course, this unrar is not available for non-x86 or non-x86_64 platforms like ARM for which there aren't native rar binary packages. Anyway, I'm aware of possible "conflict" between the two packages and would suggest trying to find a more sensible sollution instead of getting rid of any of the two. Bojan. From noel.butler at ausics.net Wed Feb 20 21:54:32 2013 From: noel.butler at ausics.net (Noel Butler) Date: Thu, 21 Feb 2013 07:54:32 +1000 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: <20130220213524.7abecdac@deathstar.universe.org> References: <20130220213524.7abecdac@deathstar.universe.org> Message-ID: <1361397272.3897.29.camel@tardis> On Wed, 2013-02-20 at 21:35 +0100, Bojan Popovic wrote: > > There is a big difference in re-distributability of the resulting > packages. So separate unrar is a sensible option. > Agreed. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From mario at slackverse.org Wed Feb 20 22:51:39 2013 From: mario at slackverse.org (Mario) Date: Wed, 20 Feb 2013 23:51:39 +0100 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: <20130220214655.706d6d8a@deathstar.universe.org> References: <20130220214655.706d6d8a@deathstar.universe.org> Message-ID: <5125537B.8060709@slackverse.org> On 02/20/2013 09:46 PM, Bojan Popovic wrote: > @Matteo: Is libunrar built along with unrar? Or if not, does there > exist an option to do so? If yes, that sounds sensible. > > I guess you are also suggesting to take over unrar (as you are the > maintainer of libunrar)? If yes, I think that would be a good idea. > > Bojan. > unrar libraries are requirement for my other SlackBuild, and sadly unrar maintainer did not reply to my email, so I was forced to create libunrar SlackBuild :-/ libunrar can be part of rar or unrar packages, if someone wants to make that happen let me know. -- Mario From yochanon at lavabit.com Wed Feb 20 23:10:17 2013 From: yochanon at lavabit.com (JB) Date: Wed, 20 Feb 2013 17:10:17 -0600 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: <20130220213524.7abecdac@deathstar.universe.org> References: <20130220213524.7abecdac@deathstar.universe.org> Message-ID: <20130220171017.39e2cd05@oogah.boogah.org> On Wed, 20 Feb 2013 21:35:24 +0100 Bojan Popovic wrote: > Hi, > > > The unrar SlackBuild should be discontinued. > > > > Sorry, I don't agree. > > I'm using a bunch of archivers/unarchivers on my machines and > basically depend on any of them a lot. > +1 > > I recommend pulling the unrar SlackBuild and setting the rar > > SlackBuild to build unrar. > > Anyway, I'm aware of possible "conflict" between the two packages and > would suggest trying to find a more sensible sollution instead of > getting rid of any of the two. > > Bojan. > +1 -- Man is a religious animal. He is the only religious animal. He is the only animal that has the True Religion -- several of them. -Mark Twain From larryhaja at gmail.com Wed Feb 20 23:20:16 2013 From: larryhaja at gmail.com (Larry Hajali) Date: Wed, 20 Feb 2013 15:20:16 -0800 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: <20130220171017.39e2cd05@oogah.boogah.org> References: <20130220213524.7abecdac@deathstar.universe.org> <20130220171017.39e2cd05@oogah.boogah.org> Message-ID: I don't use the rar package so I won't comment on that but I do like Mateo's idea of combining unrar/libunrar packages. --Larry On Wed, Feb 20, 2013 at 3:10 PM, JB wrote: > On Wed, 20 Feb 2013 21:35:24 +0100 > Bojan Popovic wrote: > > > Hi, > > > > > The unrar SlackBuild should be discontinued. > > > > > > > Sorry, I don't agree. > > > > > > > I'm using a bunch of archivers/unarchivers on my machines and > > basically depend on any of them a lot. > > > > +1 > > > > I recommend pulling the unrar SlackBuild and setting the rar > > > SlackBuild to build unrar. > > > > > > > Anyway, I'm aware of possible "conflict" between the two packages and > > would suggest trying to find a more sensible sollution instead of > > getting rid of any of the two. > > > > Bojan. > > > > +1 > > > -- > Man is a religious animal. He is the only religious animal. He is the only > animal that has the True Religion -- several of them. -Mark Twain > > _______________________________________________ > 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 rworkman at slackbuilds.org Thu Feb 21 01:23:05 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 20 Feb 2013 19:23:05 -0600 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: <5125537B.8060709@slackverse.org> References: <20130220214655.706d6d8a@deathstar.universe.org> <5125537B.8060709@slackverse.org> Message-ID: <20130220192305.7b91a94d@home.rlworkman.net> On Wed, 20 Feb 2013 23:51:39 +0100 Mario wrote: > On 02/20/2013 09:46 PM, Bojan Popovic wrote: > > @Matteo: Is libunrar built along with unrar? Or if not, does there > > exist an option to do so? If yes, that sounds sensible. > > > > I guess you are also suggesting to take over unrar (as you are the > > maintainer of libunrar)? If yes, I think that would be a good idea. > > > > Bojan. > > > > unrar libraries are requirement for my other SlackBuild, and sadly > unrar maintainer did not reply to my email, so I was forced to create > libunrar SlackBuild :-/ > libunrar can be part of rar or unrar packages, if someone wants to > make that happen let me know. If Nille is unresponsive (I hope he's okay and still using Slackware), and that seems to be the case based on two different people's failure to get a response from him, then it seems to me that you can have it. I think you wanted to put unrar within the libunrar build (or maybe vice versa), which would leave us with two builds: 1. rar (binary only) 2. unrar/libunrar That said, it seems to me that the right way to do it would be to keep the "unrar" name, make it install the unrar binary no matter what, and default to also installing the library. That would be consistent with how most everything in Slackware is shipped: "app" contains "libapp" and any other associated "app*" files. Support a build flag to disable installation of the library (basically, this flag installs *only* the unrar binary), and it seems like everyone should be happy. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From melikamp at melikamp.com Thu Feb 21 01:47:47 2013 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Wed, 20 Feb 2013 20:47:47 -0500 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: <20130220192305.7b91a94d@home.rlworkman.net> References: <20130220214655.706d6d8a@deathstar.universe.org> <5125537B.8060709@slackverse.org> <20130220192305.7b91a94d@home.rlworkman.net> Message-ID: <51257CC3.1040300@melikamp.com> I'd be very happy with that scenario. I prefer to have separate slackbuilds for free parts of non-free programs, as anyone conscious about security should. On 02/20/2013 08:23 PM, Robby Workman wrote: > ... it seems to me that the right way to do it would be to > keep the "unrar" name, make it install the unrar binary no matter > what, and default to also installing the library. That would be > consistent with how most everything in Slackware is shipped: > "app" contains "libapp" and any other associated "app*" files. > Support a build flag to disable installation of the library > (basically, this flag installs *only* the unrar binary), and it > seems like everyone should be happy. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: From lukenshiro at ngi.it Thu Feb 21 20:22:32 2013 From: lukenshiro at ngi.it (LukenShiro) Date: Thu, 21 Feb 2013 21:22:32 +0100 Subject: [Slackbuilds-users] alsa-tools udev rule Message-ID: <20130221212232.5d7017ec@hamalayi.mnt> Hi all, it seems "99-tascam.rules" file contains a deprecated variable in recent udev versions. I'd say BUS=="usb" should be replaced with: SUBSYSTEMS=="usb" TIA. -- GNU/Linux * Slackware64 current LU #210970 SU #12583 LM #98222/#412913 From yalhcru at gmail.com Thu Feb 21 22:08:21 2013 From: yalhcru at gmail.com (B Watson) Date: Thu, 21 Feb 2013 17:08:21 -0500 Subject: [Slackbuilds-users] alsa-tools udev rule In-Reply-To: <20130221212232.5d7017ec@hamalayi.mnt> References: <20130221212232.5d7017ec@hamalayi.mnt> Message-ID: On 2/21/13, LukenShiro wrote: > Hi all, > > it seems "99-tascam.rules" file contains a deprecated variable in recent > udev versions. > > I'd say BUS=="usb" should be replaced with: > SUBSYSTEMS=="usb" Good catch. I haven't even plugged the Tascam in since upgrading to 14.0, will try your udev rule & submit update soon. From rworkman at slackbuilds.org Sat Feb 23 05:12:46 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 22 Feb 2013 23:12:46 -0600 Subject: [Slackbuilds-users] Updates - 20130223.1 Message-ID: <20130222231246.712fb784@home.rlworkman.net> Sat Feb 23 04:30:38 UTC 2013 academic/jugglinglab: Added (create/animate juggling patterns) audio/SuperCollider: Updated for version 3.6.2. audio/alsamodularsynth: Added (realtime modular synthesizer) audio/sunvox: Added (Modular synthesizer, sampler, and sequencer/tracker) desktop/cairo-dock-plugins: Updated for version 3.1.2. desktop/cairo-dock: Updated for version 3.1.2. desktop/faenza-icon-theme: Correct MD5SUM in .info file desktop/slock: Updated for version 1.1. desktop/thunar-media-tags-plugin: Fixed taglib linkage development/JSONObject: Removed UTF-8 BOM. development/THE: Included a symlink: $bindir/nthe <-- $bindir/the development/anjuta: Fixed dep information (+itstool) development/jdk: Updated for version 7u15. dot.gitignore: Ignore .swp files games/playonlinux: Fixed dep info (imagick-->php-imagick) graphics/draftsight: Updated for version 1.2.265. graphics/screencloud: Added (Easy to use screenshot tool) graphics/teighafileconverter: Updated for version 3.8.1. graphics/teighaviewer: Updated for version 3.8.1. libraries/bullet: Added (physics library) libraries/libvdpau: Updated for version 0.6. libraries/libxkbcommon: Added (library to handle keyboard descriptions) libraries/opensaml: Added (FOSS Implementation of OASIS SAML) multimedia/devede: Updated for version 3.23.0. multimedia/gpodder3: Removed (replaced by gpodder) multimedia/gpodder: Updated for version 3.4.0. multimedia/xbmc: Updated for version 12.0. network/metasploit: Added (The Metasploit Framework) network/ndiswrapper-kernel: Updated for version 1.58. network/ndiswrapper-utils: Updated for version 1.58. network/opera: Updated for version 12.14. network/phpmyadmin: Updated for version 3.5.7. network/teamviewer: Fixup log/config dir symlinks network/teamviewer: Remove dangling symlink first network/teamviewer: Trivial rearrangement inside script network/teamviewer: Updated for version 8.0.17147. network/xombrero: Added (keyboard-centric web browser; formerly xxxterm) office/adobe-reader: Updated for version 9.5.3. office/epdfview: Use a working download link office/sigil: Updated for version 0.6.2. office/tellico: Updated for version 2.3.7. perl/perl-Geo-IP: Added (GeoIP Perl API) perl/perl-HTTP-Proxy: Updated for version 0.26. python/pyparsing: Updated for version 1.5.6. ruby/facter: Updated for version 1.6.17. system/bleachbit: Updated for version 0.9.5. system/gradm: Added (Grsecurity Administration Utility) system/nvidia-driver: Updated for version 310.32. system/nvidia-kernel: Updated for version 310.32. system/phpsysinfo: Updated for version 3.1.1. system/qtgzmanager: Added (TGZ/TXZ package management) system/qtgzmanager: Updated for version 1.0.1. system/regionset: Removed APPROVED from .info file system/swun: Added (SoftWare Update Notifier) system/tracker: Added (semantic data storage search engine) system/usbview: Updated for version 2.0. system/yakuake: Updated for version 2.9.9. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From crockabiscuit at gmail.com Sun Feb 24 00:01:31 2013 From: crockabiscuit at gmail.com (crocket) Date: Sun, 24 Feb 2013 09:01:31 +0900 Subject: [Slackbuilds-users] kipi-plugins requires cmake >= 2.8.9, but slackware 14.0 has 2.8.8 Message-ID: I couldn't build kipi-plugins because it required cmake >= 2.8.9. If I have to build cmake >= 2.8.9 myself to build a SBo package, it is a problem. How should it be dealt with? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Sun Feb 24 02:05:16 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 23 Feb 2013 20:05:16 -0600 Subject: [Slackbuilds-users] kipi-plugins requires cmake >= 2.8.9, but slackware 14.0 has 2.8.8 In-Reply-To: References: Message-ID: <20130223200516.4460ecdb@home.rlworkman.net> On Sun, 24 Feb 2013 09:01:31 +0900 crocket wrote: > I couldn't build kipi-plugins because it required cmake >= 2.8.9. > > If I have to build cmake >= 2.8.9 myself to build a SBo package, it > is a problem. > > How should it be dealt with? It's polite to follup up with a resolution, so I will - here's the log from IRC: 00:01 -!- crocket [~crocket at unaffiliated/crocket] has joined #slackbuilds 00:01 < crocket> kipi-plugins requires cmake >= 2.8.9, but slackware 14.0 has 2.8.8 00:02 < crocket> I reported this problem on SBo mailing list. 00:12 <+alienBOB> Which version crocket ? 00:12 < crocket> alienBOB, The version in SBo 14.0 00:12 < crocket> It is currently 1.9.0 00:13 <+alienBOB> Let's check that 00:13 <+rworkman> When does it fail? 00:15 <+rworkman> I just kicked off a test build locally on a 14.0 VM, and it's started fine - 3% progress now 00:16 <+alienBOB> No problems here either on a fresh 14.0 VM 00:16 <+alienBOB> crocket: are you actually running 14.0, or -current? Or installed KDE 4.10.0 on Slackware 14? 00:17 < crocket> alienBOB, I installed KDE 4.10.0 on slackware 14.0 00:17 * BP{k} listens to sound of a couple of procesors screaching to a halt ;) 00:18 <+rworkman> sheesh 00:18 <+rworkman> BP{k}: :) 00:18 <+alienBOB> KDE 4.10.0 requires a newer cmake, not kipi-plugins 00:18 <+alienBOB> Case closed 00:18 <+rworkman> alienBOB: thanks :) 00:19 < crocket> alienBOB, I think it is better if you provided a newer cmake in KDE 4.10.0 00:19 < crocket> maybe in deps 00:22 < firebird> it's slackware, if it's so important for you to have a newer cmake for $reason, it's not that hard to build it yourself. 00:26 <+alienBOB> crocket: the build script is available. I chose not to add a cmake package because that could have had unwanted side effects for people running -current and installing my packages -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From yalhcru at gmail.com Sun Feb 24 02:04:07 2013 From: yalhcru at gmail.com (B Watson) Date: Sat, 23 Feb 2013 21:04:07 -0500 Subject: [Slackbuilds-users] kipi-plugins requires cmake >= 2.8.9, but slackware 14.0 has 2.8.8 In-Reply-To: References: Message-ID: On 2/23/13, crocket wrote: > I couldn't build kipi-plugins because it required cmake >= 2.8.9. Are you trying to build a newer version than the 1.9.0 that's on the site? It's building fine here with cmake 2.8.8. From rworkman at slackbuilds.org Sun Feb 24 07:14:23 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:14:23 -0600 Subject: [Slackbuilds-users] rc.postfix In-Reply-To: <5124D6E0.1010108@mnspace.net> References: <5124D6E0.1010108@mnspace.net> Message-ID: <20130224011423.722a1bc7@home.rlworkman.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Feb 2013 08:00:00 -0600 Nishant Limbachia wrote: > I had the same issue and so instead of changing rc.6, I changed > rc.postfix to include full path to postfix binary. Postfix also > supports 'status' command from version 2.9.x, I believe. Here's the > diff of rc.postfix I use on my system that is the enhanced version of > the one on SBo. Applied in my git branch ; thanks! - -RW -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlEpvdMACgkQvGy9tf6lsvtYSwCaAhF0IZeEYDSsrWC/gDIsZtgy z3kAn1ueVRL5xT9WPC1/IgZuZ6zYE+W4 =dLcp -----END PGP SIGNATURE----- From rworkman at slackbuilds.org Sun Feb 24 07:26:04 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:26:04 -0600 Subject: [Slackbuilds-users] remove transset-df In-Reply-To: References: Message-ID: <20130224012604.134d120a@home.rlworkman.net> On Sat, 2 Feb 2013 15:36:47 +0100 Felix Pfeifer wrote: > my script for transset-df is obsolete and can be removed from > SBo. All the features of transset-df are now included in X.orgs > original transset. Done in my git branch; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 24 07:30:10 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:30:10 -0600 Subject: [Slackbuilds-users] evolus-pencil.Slackbuild results in corrupted system In-Reply-To: <50FF6F5D.10903@slaphappygeeks.com> References: <50FF6F5D.10903@slaphappygeeks.com> Message-ID: <20130224013010.08079729@home.rlworkman.net> On Tue, 22 Jan 2013 22:04:29 -0700 Slacker build user wrote: > My first hiccup with an SBo script... > > Installing the package built from evolus-pencil changes directory > permissions for /usr, /usr/lib, /usr/bin, /usr/share to 744 making it > very difficult to do anything! > > Modifying the script to set proper execute permissions after > extracting from rpm fixes it. > > I will also write the maintainer but wanted to write to the list as > well as this would be a serious issue for some. I don't think evolus did that - I just built it here, and there's no problem at all. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 24 07:36:13 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:36:13 -0600 Subject: [Slackbuilds-users] uid and gid for vdr In-Reply-To: References: Message-ID: <20130224013613.1f349252@home.rlworkman.net> On Sun, 10 Feb 2013 13:12:00 -0800 Larry Hajali wrote: > Hello, > > I'm looking at vdr on my own system (ie. > http://linuxtv.org/vdrwiki/index.php/Main_Page) and was looking at > running it as a daemon. As I was looking at possible users for this > package, I took a look at reserved uid/gid at > http://slackbuilds.org/uid_gid.txt. It looks like vdr is already > defined by using the policyd uid/gid, which in turn is also used for > policyd2. I found this in the SBo email archive. > > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-June/004234.html > > My question is should this uid/gid be used for vdr or should it be > separate from the uid/gid for policyd2? > > BTW...I'm just asking for clarification. I don't plan on submitting > my vdr slackbuild. Crap, I think what happened there is that vdr got reverted, but we didn't change the "vdr" to "policyd" above it. It's fixed now; sorry for the confusion. IOW, use a different uid/gid :) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 24 07:37:57 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:37:57 -0600 Subject: [Slackbuilds-users] osgEarth link error In-Reply-To: <20130206212753.GB28709@dribt> References: <20130206212753.GB28709@dribt> Message-ID: <20130224013757.106449d6@home.rlworkman.net> On Wed, 6 Feb 2013 15:27:53 -0600 bamalabs wrote: > The link to the osgEarth.tar.gz SlackBuild points to the 'libraries' > folder, when the file is actually in the 'graphics' folder. Sorry for the delay, but thanks - fixed now. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 24 07:40:17 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:40:17 -0600 Subject: [Slackbuilds-users] wrong version in rsnapshot's README In-Reply-To: References: Message-ID: <20130224014017.76e9c7b2@home.rlworkman.net> On Mon, 21 Jan 2013 08:33:58 +0700 Willy Sudiarto Raharjo wrote: > The version used in slackbuilds is 1.3.1, but the documentaion stated > in README is still pointing to 1.3.0 Fixed; thanks. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From slacker at slaphappygeeks.com Sun Feb 24 07:40:43 2013 From: slacker at slaphappygeeks.com (Slacker build user) Date: Sun, 24 Feb 2013 00:40:43 -0700 Subject: [Slackbuilds-users] evolus-pencil.Slackbuild results in corrupted system In-Reply-To: <20130224013010.08079729@home.rlworkman.net> References: <50FF6F5D.10903@slaphappygeeks.com> <20130224013010.08079729@home.rlworkman.net> Message-ID: <5129C3FB.109@slaphappygeeks.com> Robby Workman wrote: > On Tue, 22 Jan 2013 22:04:29 -0700 > I don't think evolus did that - I just built it here, and > there's no problem at all. > > -RW This has been resolved, and posted to the thread (I think!). I found the problem is caused by the script not enforcing directory permissions through rmp2cpio... to fix modify this line: chmod -R u+w,go+r-w,a-s . to chmod -R u+w,go+r-w,a+X-s . It seemed to be dependent on cpio version and apparently there is a history of it not preserving directory perms (but not in my own experience until now). FYI - I provided a possible new build script to the maintainer Binh Nguyen which extracts from tar.gz instead of RPM and is updated to version 2.x and does not have this problem. Thanks Robert From rworkman at slackbuilds.org Sun Feb 24 07:42:58 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:42:58 -0600 Subject: [Slackbuilds-users] jbig2dec source MIA In-Reply-To: References: Message-ID: <20130224014258.3905bb21@home.rlworkman.net> On Sat, 19 Jan 2013 15:44:26 -0500 B Watson wrote: > http://ghostscript.com/~giles/jbig2/jbig2dec/jbig2dec-0.11.tar.gz is > gone as of sometime last week. The homepage still links there, but > it's 404 now. > > There's a copy here that probably will be around for a while: > > http://distfiles.gentoo.org/distfiles/jbig2dec-0.11.tar.gz Fixed in my git branch ; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 24 07:57:27 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:57:27 -0600 Subject: [Slackbuilds-users] evolus-pencil.Slackbuild results in corrupted system In-Reply-To: <5129C3FB.109@slaphappygeeks.com> References: <50FF6F5D.10903@slaphappygeeks.com> <20130224013010.08079729@home.rlworkman.net> <5129C3FB.109@slaphappygeeks.com> Message-ID: <20130224015727.16b25c2d@home.rlworkman.net> On Sun, 24 Feb 2013 00:40:43 -0700 Slacker build user wrote: > Robby Workman wrote: > > On Tue, 22 Jan 2013 22:04:29 -0700 > > I don't think evolus did that - I just built it here, and > > there's no problem at all. > > > > This has been resolved, and posted to the thread (I think!). Hrm, maybe it was - I'm catching up on LOTS of mail, so I probably missed it. > permissions through rmp2cpio... to fix modify this line: > > chmod -R u+w,go+r-w,a-s . > to > chmod -R u+w,go+r-w,a+X-s . > > It seemed to be dependent on cpio version and apparently there is a > history of it not preserving directory perms (but not in my own > experience until now). Okay, well, in that case, I changed the chmod line in my git branch. Better safe than sorry in the case. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 24 07:58:56 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 01:58:56 -0600 Subject: [Slackbuilds-users] alsa-tools udev rule In-Reply-To: References: <20130221212232.5d7017ec@hamalayi.mnt> Message-ID: <20130224015856.6e423b35@home.rlworkman.net> On Thu, 21 Feb 2013 17:08:21 -0500 B Watson wrote: > On 2/21/13, LukenShiro wrote: > > Hi all, > > > > it seems "99-tascam.rules" file contains a deprecated variable in > > recent udev versions. > > > > I'd say BUS=="usb" should be replaced with: > > SUBSYSTEMS=="usb" > > Good catch. I haven't even plugged the Tascam in since upgrading to > 14.0, will try your udev rule & submit update soon. It's a correct change; I've got it in my git branch already. Thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 24 08:06:18 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 02:06:18 -0600 Subject: [Slackbuilds-users] pyquery broken after lxml update In-Reply-To: References: Message-ID: <20130224020618.3a3c29f5@home.rlworkman.net> On Fri, 28 Dec 2012 15:54:24 -0800 Larry Hajali wrote: > Hi, > > Between lxml version 2.x and 3.x, lxml broke out the cssselect module > into its own separate package. The version on SBo is definitely > outdated and incompatible (w/out patching) with the new lxml. > Looking at the setup.py file on the github page (ie. > https://github.com/gawel/pyquery), the new version looks to be > compatible with the new lxml with cssselect and distribute as new > dependencies. > > All that needs to be done is download the latest version of pyquery ( > http://pypi.python.org/packages/source/p/pyquery/pyquery-1.2.4.tar.gz), > install the new dependencies and change the version number in the > slackbuild to 1.2.4. I'm providing a patch with the changes I made > to get things working. Now using 'import pyquery' at the python > command prompt works. > > On a side note, there isn't a dependency listed for pysetuptools or > distribute for version 0.6.1 of pyquery. It is optional for lxml and > not listed for BeautifulSoup. Since the maintainer hasn't moved on this since then, and since you seem to have already done all of this, would you mind submitting what you've got, or at least attach some patches I can apply to what's currently in the repo? Perhaps I should just go to bed now, but I'm having a bit of trouble wrapping my head around exactly what I need to do to fix all of this... :/ -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From mario at slackverse.org Sun Feb 24 18:21:33 2013 From: mario at slackverse.org (Mario) Date: Sun, 24 Feb 2013 19:21:33 +0100 Subject: [Slackbuilds-users] unrar should be discontinued In-Reply-To: <20130220192305.7b91a94d@home.rlworkman.net> References: <20130220214655.706d6d8a@deathstar.universe.org> <5125537B.8060709@slackverse.org> <20130220192305.7b91a94d@home.rlworkman.net> Message-ID: <512A5A2D.2050800@slackverse.org> On 02/21/2013 02:23 AM, Robby Workman wrote: > On Wed, 20 Feb 2013 23:51:39 +0100 > Mario wrote: > >> On 02/20/2013 09:46 PM, Bojan Popovic wrote: >>> @Matteo: Is libunrar built along with unrar? Or if not, does there >>> exist an option to do so? If yes, that sounds sensible. >>> >>> I guess you are also suggesting to take over unrar (as you are the >>> maintainer of libunrar)? If yes, I think that would be a good idea. >>> >>> Bojan. >>> >> >> unrar libraries are requirement for my other SlackBuild, and sadly >> unrar maintainer did not reply to my email, so I was forced to create >> libunrar SlackBuild :-/ >> libunrar can be part of rar or unrar packages, if someone wants to >> make that happen let me know. > > > If Nille is unresponsive (I hope he's okay and still using Slackware), > and that seems to be the case based on two different people's failure > to get a response from him, then it seems to me that you can have it. > > I think you wanted to put unrar within the libunrar build (or maybe > vice versa), which would leave us with two builds: > 1. rar (binary only) > 2. unrar/libunrar > > That said, it seems to me that the right way to do it would be to > keep the "unrar" name, make it install the unrar binary no matter > what, and default to also installing the library. That would be > consistent with how most everything in Slackware is shipped: > "app" contains "libapp" and any other associated "app*" files. > Support a build flag to disable installation of the library > (basically, this flag installs *only* the unrar binary), and it > seems like everyone should be happy. > > -RW > Robby, sure, I can take over unrar SB and bundle libunrar, unless if Nille (CC) wants to do it himself. Personaly I do not mind handing over libunrar as long as it gets support and updates. Nille, what are your thoughts? -- Mario From larryhaja at gmail.com Sun Feb 24 17:27:29 2013 From: larryhaja at gmail.com (Larry Hajali) Date: Sun, 24 Feb 2013 09:27:29 -0800 Subject: [Slackbuilds-users] pyquery broken after lxml update In-Reply-To: <20130224020618.3a3c29f5@home.rlworkman.net> References: <20130224020618.3a3c29f5@home.rlworkman.net> Message-ID: Hi Robby, I didn't patch the 0.6.1 source. I am providing a diff of what works for me on the 1.2.4 version of pyquery. Update it as you like. Thanks, Larry On Sun, Feb 24, 2013 at 12:06 AM, Robby Workman wrote: > On Fri, 28 Dec 2012 15:54:24 -0800 > Larry Hajali wrote: > > > Hi, > > > > Between lxml version 2.x and 3.x, lxml broke out the cssselect module > > into its own separate package. The version on SBo is definitely > > outdated and incompatible (w/out patching) with the new lxml. > > Looking at the setup.py file on the github page (ie. > > https://github.com/gawel/pyquery), the new version looks to be > > compatible with the new lxml with cssselect and distribute as new > > dependencies. > > > > All that needs to be done is download the latest version of pyquery ( > > http://pypi.python.org/packages/source/p/pyquery/pyquery-1.2.4.tar.gz), > > install the new dependencies and change the version number in the > > slackbuild to 1.2.4. I'm providing a patch with the changes I made > > to get things working. Now using 'import pyquery' at the python > > command prompt works. > > > > On a side note, there isn't a dependency listed for pysetuptools or > > distribute for version 0.6.1 of pyquery. It is optional for lxml and > > not listed for BeautifulSoup. > > > Since the maintainer hasn't moved on this since then, and since > you seem to have already done all of this, would you mind > submitting what you've got, or at least attach some patches I > can apply to what's currently in the repo? Perhaps I should just > go to bed now, but I'm having a bit of trouble wrapping my head > around exactly what I need to do to fix all of this... :/ > > -RW > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pyquery.diff Type: application/octet-stream Size: 1836 bytes Desc: not available URL: From kingbeowulf at gmail.com Mon Feb 25 00:38:20 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 24 Feb 2013 16:38:20 -0800 Subject: [Slackbuilds-users] QEMU and QEMU-KVM updates Message-ID: <512AB27C.5030306@gmail.com> If I am reading the changlelogs and qemu wiki correctly http://wiki.qemu.org/KVM all of the KVM bits have been merged upstream into qemu-1.3 (current release is now 1.4). I think it would be a grand idea to merge the qemu and qemu-kvm slackbuilds into onepackage. Itappears that qemu-kvm is deprecated. I am copying the maintainers also in case they don't check this list often. Please respond to the list so that we can all talk and yell in one place. Thanks. .Ed From rworkman at slackbuilds.org Mon Feb 25 05:08:30 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 23:08:30 -0600 Subject: [Slackbuilds-users] Updates - 20130225.1 Message-ID: <20130224230830.4e162f69@home.rlworkman.net> For the first time in a while, the pending queue is clear :-) Mon Feb 25 04:55:27 UTC 2013 academic/gwyddion: Updated for version 2.31. academic/osm2pgsql: Added (convert OpenStreetMap data to PostGIS) accessibility/ruvim: Added (Russian language pack for Vim) audio/alsa-tools: Fixed udev rules (s,BUS,SUBSYSTEMS,g) audio/lmms: Pass proper libdir to cmake desktop/transset-df: Removed (obsolete) desktop/trayer-srg: Added (GTK2-based systray for UNIX desktop) development/eclipse: Updated for version 4.2.1. development/kforth: Added (A Forth programming language and environment) development/monodevelop-database: Updated for version 3.0.6. development/monodevelop-debugger-gdb: Updated for version 3.0.6. development/monodevelop: Updated for version 3.0.6. development/netbeans: Updated for version 7.3. development/qt-creator: Updated for version 2.6.2. development/scite: Updated for version 3.24. graphics/evolus-pencil: Tweak permissions setting graphics/gthumb: Remove obsolete configure flags graphics/inkscape: Updated for version 0.48.4. graphics/zbar: Added (bar code reader) libraries/jbig2dec: Fixed download link libraries/libmicrohttpd: Updated for version 0.9.25. libraries/libnova: Added (Celestial Mechanics, Astrometry, and Astrodynamics Library) libraries/libpqxx: Added (C++ client API for PostgreSQL) libraries/ltm: Added (LibTomMath library) libraries/php-pdo_dblib: Added (php pdo_dblib extension) libraries/podofo: Updated for version 0.9.2. libraries/tbb: Updated for version 4.1u2. misc/rsnapshot: Fixed version refs in README misc/zyGrib: Updated for version 6.1.2. multimedia/dirac: Pedantic fix to comment in dirac.SlackBuild multimedia/makemkv: Updated for version 1.8.0. network/bitcoin: Updated for version 0.8.0. network/dovecot: Noted dovenull user/group requirements network/etherpad-lite: Don't clobber system configs/logs on upgrade network/etherpad-lite: Updated for version 1.2.7. network/knemo: Updated for version 0.7.6. network/postfix: Use full path and add status() to init script network/skype: Updated for version 4.1.0.20. office/convertlit: Added (converts .lit files to .epub) office/texlive: Clarified README wrt building office/wyrd: Don't clobber config file on package upgrades office/wyrd: Updated for version 1.4.6. python/pyquery: Updated for version 1.2.4. system/bacula-client: Updated for version 5.2.13. system/bacula: Updated for version 5.2.13. system/cups-bjnp: Added (CUPS backend using the BJNP protocol) system/man-pages-ru: Added (Russian man pages) system/ms-sys: Added (writes Microsoft compatible boot records) system/unetbootin: Updated for version 583. system/wacomtablet: Added (KDE Wacom Tablet) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From t3slider at gmail.com Mon Feb 25 05:22:28 2013 From: t3slider at gmail.com (T3slider) Date: Mon, 25 Feb 2013 00:22:28 -0500 Subject: [Slackbuilds-users] Updates - 20130225.1 In-Reply-To: <20130224230830.4e162f69@home.rlworkman.net> References: <20130224230830.4e162f69@home.rlworkman.net> Message-ID: <20130225052228.GA3327@MyPC.phub.net.cable.rogers.com> Sorry I missed this, it was an oversight. However, there is now a typo in the SlackBuild script: mv $PKG/etc/etc/wyrdrc $PKG/etc/wyrdrc.new should be mv $PKG/etc/wyrdrc $PKG/etc/wyrdrc.new I can just submit an updated tarball if you want, unless it's easier to fix on your end. -T3slider On Sun, Feb 24, 2013 at 11:08:30PM -0600, Robby Workman wrote: > office/wyrd: Don't clobber config file on package upgrades > office/wyrd: Updated for version 1.4.6. From rworkman at slackbuilds.org Mon Feb 25 05:58:46 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Feb 2013 23:58:46 -0600 Subject: [Slackbuilds-users] Updates - 20130225.1 In-Reply-To: <20130225052228.GA3327@MyPC.phub.net.cable.rogers.com> References: <20130224230830.4e162f69@home.rlworkman.net> <20130225052228.GA3327@MyPC.phub.net.cable.rogers.com> Message-ID: <20130224235846.1428ce66@home.rlworkman.net> On Mon, 25 Feb 2013 00:22:28 -0500 T3slider wrote: > Sorry I missed this, it was an oversight. However, there is now a typo > in the SlackBuild script: > > mv $PKG/etc/etc/wyrdrc $PKG/etc/wyrdrc.new > > should be > > mv $PKG/etc/wyrdrc $PKG/etc/wyrdrc.new > > I can just submit an updated tarball if you want, unless it's easier > to fix on your end. Argh. Fixed in 7811cede60a284b5693bbf619c804908e1d8199d and pushed to both master and 14.0 branches. Thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Mon Feb 25 22:33:26 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 25 Feb 2013 14:33:26 -0800 Subject: [Slackbuilds-users] qemu: New Maintainer Message-ID: <512BE6B6.5050509@gmail.com> Admins, Heads up: I have Andrew's nod to take over qemu.SlackBuild if no one else has grabbed it yet. If it is up for grabs, I will submit a qemu-1.4 update this week. ------------ Hi Ed, I noticed that too! Unfortunately, I'm not really using slackware any longer, especially qemu - feel free to adopt if you are interested in the project. Best wishes, Andrew ------------------ From rworkman at slackbuilds.org Tue Feb 26 00:24:49 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 25 Feb 2013 18:24:49 -0600 Subject: [Slackbuilds-users] qemu: New Maintainer In-Reply-To: <512BE6B6.5050509@gmail.com> References: <512BE6B6.5050509@gmail.com> Message-ID: <20130225182449.47d7008b@home.rlworkman.net> On Mon, 25 Feb 2013 14:33:26 -0800 King Beowulf wrote: > Admins, > Heads up: I have Andrew's nod to take over qemu.SlackBuild if no one > else has grabbed it yet. If it is up for grabs, I will submit a > qemu-1.4 update this week. Sounds good - looking forward to it. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Mon Feb 25 22:37:14 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 25 Feb 2013 14:37:14 -0800 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm Message-ID: <512BE79A.10602@gmail.com> Since qemu-kvm devs have pushed the kvm bits upstream to qemu as of 1.3, should we dropqemu-kvm? It does not appear that qemu-kvm will be updated past 1.2 and qemu is now at 1.4. That might make installing both on the same system a bit tricky. Comments? From rworkman at slackbuilds.org Tue Feb 26 03:18:45 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 25 Feb 2013 21:18:45 -0600 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: <512BE79A.10602@gmail.com> References: <512BE79A.10602@gmail.com> Message-ID: <20130225211845.25e5abfa@home.rlworkman.net> On Mon, 25 Feb 2013 14:37:14 -0800 King Beowulf wrote: > Since qemu-kvm devs have pushed the kvm bits upstream to qemu as of > 1.3, should we dropqemu-kvm? It does not appear that qemu-kvm will be > updated past 1.2 and qemu is now at 1.4. That might make installing > both on the same system a bit tricky. Yes, it should be dropped - plan for that to occur unless there's serious objection. In my experience with qemu (and I use it fairly often), I think the only thing we need to ensure that it still works with some other related stuff (e.g. aqemu) is a /usr/bin/qemu-kvm symlink pointing to /usr/bin/qemu-system-$ARCH (generally x86_64) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Tue Feb 26 03:37:42 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 25 Feb 2013 21:37:42 -0600 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: <20130225211845.25e5abfa@home.rlworkman.net> References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> Message-ID: <20130225213742.78db2cbf@home.rlworkman.net> On Mon, 25 Feb 2013 21:18:45 -0600 Robby Workman wrote: > On Mon, 25 Feb 2013 14:37:14 -0800 > King Beowulf wrote: > > > Since qemu-kvm devs have pushed the kvm bits upstream to qemu as of > > 1.3, should we dropqemu-kvm? It does not appear that qemu-kvm will > > be updated past 1.2 and qemu is now at 1.4. That might make > > installing both on the same system a bit tricky. > > > Yes, it should be dropped - plan for that to occur unless there's > serious objection. > > In my experience with qemu (and I use it fairly often), I think the > only thing we need to ensure that it still works with some other > related stuff (e.g. aqemu) is a /usr/bin/qemu-kvm symlink pointing > to /usr/bin/qemu-system-$ARCH (generally x86_64) I'll do better even; here is (attached) the qemu build script I have been using. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: qemu.tar.gz Type: application/x-gzip Size: 3040 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Tue Feb 26 06:08:54 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 25 Feb 2013 22:08:54 -0800 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: <20130225213742.78db2cbf@home.rlworkman.net> References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> <20130225213742.78db2cbf@home.rlworkman.net> Message-ID: <512C5176.2070402@gmail.com> On 02/25/2013 07:37 PM, Robby Workman wrote: > On Mon, 25 Feb 2013 21:18:45 -0600 > Robby Workman wrote: > >> On Mon, 25 Feb 2013 14:37:14 -0800 >> King Beowulf wrote: >> >>> Since qemu-kvm devs have pushed the kvm bits upstream to qemu as of >>> 1.3, should we dropqemu-kvm? It does not appear that qemu-kvm will >>> be updated past 1.2 and qemu is now at 1.4. That might make >>> installing both on the same system a bit tricky. >> >> Yes, it should be dropped - plan for that to occur unless there's >> serious objection. >> >> In my experience with qemu (and I use it fairly often), I think the >> only thing we need to ensure that it still works with some other >> related stuff (e.g. aqemu) is a /usr/bin/qemu-kvm symlink pointing >> to /usr/bin/qemu-system-$ARCH (generally x86_64) > > I'll do better even; here is (attached) the qemu build script I > have been using. > > -RW Good point. I'll go over yours with mine and add appropriate updates to my TO-DO list. We'll have to search for any slackbuilds that depend on qemu-kvm to make sure they get updated. Aqemu hasn't had an update since 2011 (not necessarily a bad thing) so I wonder if its still in development? Might be worth my trying to contact the dev. I too use aqemu/qemu quite a bit, not just for playing with other OS but also for clean build environments. .Ed From matteo.bernardini at gmail.com Tue Feb 26 06:19:22 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 26 Feb 2013 07:19:22 +0100 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: <20130225213742.78db2cbf@home.rlworkman.net> References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> <20130225213742.78db2cbf@home.rlworkman.net> Message-ID: Here I'm using the new version since some time, if you want to try them I got some updates on git http://cgit.ponce.cc/slackbuilds/commit/?h=qemu http://cgit.ponce.cc/slackbuilds/commit/?h=usbredir http://cgit.ponce.cc/slackbuilds/commit/?h=spice-protocol http://cgit.ponce.cc/slackbuilds/commit/?h=spice seems it plays fine with the newer libvirt/virt-manager (all this stuff is available in the SBo-git repo), also without the qemu-kvm symlink. yes, aqemu development seems stopped so it doesn't support this new version very well... -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Tue Feb 26 06:43:36 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 26 Feb 2013 00:43:36 -0600 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: <512C5176.2070402@gmail.com> References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> <20130225213742.78db2cbf@home.rlworkman.net> <512C5176.2070402@gmail.com> Message-ID: <20130226004336.6dee8176@home.rlworkman.net> On Mon, 25 Feb 2013 22:08:54 -0800 King Beowulf wrote: > On 02/25/2013 07:37 PM, Robby Workman wrote: > > On Mon, 25 Feb 2013 21:18:45 -0600 > > Robby Workman wrote: > > > >> On Mon, 25 Feb 2013 14:37:14 -0800 > >> King Beowulf wrote: > >> > >>> Since qemu-kvm devs have pushed the kvm bits upstream to qemu as > >>> of 1.3, should we dropqemu-kvm? It does not appear that qemu-kvm > >>> will be updated past 1.2 and qemu is now at 1.4. That might make > >>> installing both on the same system a bit tricky. > >> > >> Yes, it should be dropped - plan for that to occur unless there's > >> serious objection. > >> > >> In my experience with qemu (and I use it fairly often), I think the > >> only thing we need to ensure that it still works with some other > >> related stuff (e.g. aqemu) is a /usr/bin/qemu-kvm symlink pointing > >> to /usr/bin/qemu-system-$ARCH (generally x86_64) > > > > I'll do better even; here is (attached) the qemu build script I > > have been using. > > > > > Good point. I'll go over yours with mine and add appropriate updates > to my TO-DO list. We'll have to search for any slackbuilds that > depend on qemu-kvm to make sure they get updated. Aqemu hasn't had > an update since 2011 (not necessarily a bad thing) so I wonder if its > still in development? Might be worth my trying to contact the dev. Nothing needs qemu in any fashion other than "it needs to be available at runtime," so no need to check for reverse deps. Re aqemu, I had contact with upstream (it's just one guy) back when qemu hit 1.0; he put some changes in svn/git/whatever to support it (and those patches are used in our SBo build). > I too use aqemu/qemu quite a bit, not just for playing with other OS > but also for clean build environments. Yep, it's good stuff :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Tue Feb 26 06:45:02 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 26 Feb 2013 00:45:02 -0600 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> <20130225213742.78db2cbf@home.rlworkman.net> Message-ID: <20130226004502.4a932ff7@home.rlworkman.net> On Tue, 26 Feb 2013 07:19:22 +0100 Matteo Bernardini wrote: > Here I'm using the new version since some time, if you want to try > them I got some updates on git > > http://cgit.ponce.cc/slackbuilds/commit/?h=qemu > http://cgit.ponce.cc/slackbuilds/commit/?h=usbredir > http://cgit.ponce.cc/slackbuilds/commit/?h=spice-protocol > http://cgit.ponce.cc/slackbuilds/commit/?h=spice > > seems it plays fine with the newer libvirt/virt-manager (all this > stuff is available in the SBo-git repo), also without the qemu-kvm > symlink. > > yes, aqemu development seems stopped so it doesn't support this new > version very well... Hrm, I'll admit that most of my qemu usage is via custom scripts, but best I can tell, aqemu behaves mostly fine so long as that qemu-kvm symlink is around (otherwise, it doesn't think KVM is supported at all). -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Tue Feb 26 07:37:44 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 25 Feb 2013 23:37:44 -0800 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> <20130225213742.78db2cbf@home.rlworkman.net> Message-ID: <512C6648.1070102@gmail.com> On 02/25/2013 10:19 PM, Matteo Bernardini wrote: > Here I'm using the new version since some time, if you want to try > them I got some updates on git > > http://cgit.ponce.cc/slackbuilds/commit/?h=qemu > http://cgit.ponce.cc/slackbuilds/commit/?h=usbredir > http://cgit.ponce.cc/slackbuilds/commit/?h=spice-protocol > http://cgit.ponce.cc/slackbuilds/commit/?h=spice > > seems it plays fine with the newer libvirt/virt-manager (all this > stuff is available in the SBo-git repo), also without the qemu-kvm > symlink. > > yes, aqemu development seems stopped so it doesn't support this new > version very well... > Thanks, Matteo. The more, the merrier! .Ed From matteo.bernardini at gmail.com Tue Feb 26 09:06:22 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 26 Feb 2013 10:06:22 +0100 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: <20130226004502.4a932ff7@home.rlworkman.net> References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> <20130225213742.78db2cbf@home.rlworkman.net> <20130226004502.4a932ff7@home.rlworkman.net> Message-ID: 2013/2/26 Robby Workman > > yes, aqemu development seems stopped so it doesn't support this new > > version very well... > > Hrm, I'll admit that most of my qemu usage is via custom scripts, > but best I can tell, aqemu behaves mostly fine so long as that > qemu-kvm symlink is around (otherwise, it doesn't think KVM is > supported at all). yes, my fault Robby. Just tested and can confirm this: I had tried it in the past with previous qemu versions (1.3.0, if I remember well) and had some problems, but with the latest stuff and the symlink (that doesn't disturb libvirt at all) behaves pretty ok (besides not supporting usbredir, it seems). Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From openpandora at free.fr Tue Feb 26 15:52:57 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 26 Feb 2013 16:52:57 +0100 Subject: [Slackbuilds-users] Hi everybody ! Message-ID: <1361893977.512cda59b3784@imp.free.fr> New list subscriber here. I'm the maintainer of the Open Pandora Slackware ARM port. Here's some infos there: Open Pandora: http://openpandora.org/ http://boards.openpandora.org/index.php/index/ SL4P, Slackware for Pandora: http://pandorawiki.org/Software_projects/OS/Slackware SOLEIL, Slackware on steroids: http://pandorawiki.org/Software_projects/OS/SOLEIL From openpandora at free.fr Tue Feb 26 15:55:45 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 26 Feb 2013 16:55:45 +0100 Subject: [Slackbuilds-users] 14.0 muse doinst setcap failing. Message-ID: <1361894145.512cdb01aaf12@imp.free.fr> Hi ! In the doinst: setcap cap_ipc_lock,cap_sys_nice=ep /usr/bin/muse Now the binary is /usr/bin/muse2 Also, on ARM device, the setcap fails with a "operation not supported", "Note must be a regular (non-symlink) file. LS. From openpandora at free.fr Tue Feb 26 15:58:10 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 26 Feb 2013 16:58:10 +0100 Subject: [Slackbuilds-users] 14.0 muse doinst setcap failing. In-Reply-To: <1361894145.512cdb01aaf12@imp.free.fr> References: <1361894145.512cdb01aaf12@imp.free.fr> Message-ID: <1361894290.512cdb9286a88@imp.free.fr> Oh, i've just realized maybe it's because i'm on ext2 ? Quoting openpandora at free.fr: > Hi ! > > In the doinst: > setcap cap_ipc_lock,cap_sys_nice=ep /usr/bin/muse > > Now the binary is /usr/bin/muse2 > > Also, on ARM device, the setcap fails with a "operation not supported", "Note > must be a regular (non-symlink) file. > > LS. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From kingbeowulf at gmail.com Tue Feb 26 19:49:29 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 26 Feb 2013 11:49:29 -0800 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> <20130225213742.78db2cbf@home.rlworkman.net> <20130226004502.4a932ff7@home.rlworkman.net> Message-ID: I'm not sure about usbredir, but I found any features not "supported" in aqemu, can be added as additional command line args under advanced settings. .Ed On 2/26/13, Matteo Bernardini wrote: > 2013/2/26 Robby Workman > >> > yes, aqemu development seems stopped so it doesn't support this new >> > version very well... >> >> Hrm, I'll admit that most of my qemu usage is via custom scripts, >> but best I can tell, aqemu behaves mostly fine so long as that >> qemu-kvm symlink is around (otherwise, it doesn't think KVM is >> supported at all). > > > yes, my fault Robby. > > Just tested and can confirm this: I had tried it in the past with previous > qemu versions (1.3.0, if I remember well) and had some problems, but with > the latest stuff and the symlink (that doesn't disturb libvirt at all) > behaves pretty ok (besides not supporting usbredir, it seems). > > Matteo > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From yalhcru at gmail.com Tue Feb 26 21:53:44 2013 From: yalhcru at gmail.com (B Watson) Date: Tue, 26 Feb 2013 16:53:44 -0500 Subject: [Slackbuilds-users] 14.0 muse doinst setcap failing. In-Reply-To: <1361894290.512cdb9286a88@imp.free.fr> References: <1361894145.512cdb01aaf12@imp.free.fr> <1361894290.512cdb9286a88@imp.free.fr> Message-ID: On 2/26/13, openpandora at free.fr wrote: >> Also, on ARM device, the setcap fails with a "operation not supported", > Oh, i've just realized maybe it's because i'm on ext2 ? ext2 should support filesystem capabilities, the same as ext3 and ext4 do. Maybe your ARM kernel doesn't have filesystem capabilities built in? The muse has at least one unfriendly thing it does, not related to capabilities. In the doinst.sh: if grep GROUP\=\"audio\" /lib/udev/rules.d/65-permissions.rules > /dev/null; then echo > /dev/null else sed '/^KERNEL=="rtc\|rtc0"/s!$! , GROUP="audio"!' -i /lib/udev/rules.d/65-permissions.rules fi As I understand it, packages aren't supposed to modify the contents of /lib/udev. Instead, the modified rules should get installed to /etc/udev/rules.d. Not to mention, modifying the contents of a standard rules file is something that can't be undone when the package is removed... and if the udev package gets updated after muse is installed, muse will break (because the modified 65-permissions.rules will get overwritten with one from the new udev). From openpandora at free.fr Wed Feb 27 00:36:01 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Wed, 27 Feb 2013 01:36:01 +0100 Subject: [Slackbuilds-users] 14.0 muse doinst setcap failing. In-Reply-To: References: <1361894145.512cdb01aaf12@imp.free.fr> <1361894290.512cdb9286a88@imp.free.fr> Message-ID: <1361925361.512d54f132f94@imp.free.fr> Mmm where in the config/options is located this capabilities option ? Didn't see it for now. Quoting B Watson : > On 2/26/13, openpandora at free.fr wrote: > >> Also, on ARM device, the setcap fails with a "operation not supported", > > Oh, i've just realized maybe it's because i'm on ext2 ? > > ext2 should support filesystem capabilities, the same as ext3 and ext4 do. > > Maybe your ARM kernel doesn't have filesystem capabilities built in? > > The muse has at least one unfriendly thing it does, not related to > capabilities. In the doinst.sh: > > if grep GROUP\=\"audio\" /lib/udev/rules.d/65-permissions.rules > > /dev/null; then > echo > /dev/null > else > sed '/^KERNEL=="rtc\|rtc0"/s!$! , GROUP="audio"!' -i > /lib/udev/rules.d/65-permissions.rules > fi > > As I understand it, packages aren't supposed to modify the contents > of /lib/udev. Instead, the modified rules should get installed > to /etc/udev/rules.d. Not to mention, modifying the contents of a > standard rules file is something that can't be undone when the package is > removed... and if the udev package gets updated after muse is installed, > muse will break (because the modified 65-permissions.rules will get > overwritten with one from the new udev). > _______________________________________________ > 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 mfilpot at gmail.com Wed Feb 27 00:37:36 2013 From: mfilpot at gmail.com (Matthew Fillpot) Date: Tue, 26 Feb 2013 19:37:36 -0500 Subject: [Slackbuilds-users] Notice of New Maintainer Message-ID: Admins, This is a notification that I am passing my build scripts for quesoglc, GLee, warzone2100, lightyears annd gpredict to my son David. He has been taking interest in getting more involved in Slackware and we have been working for the last few weeks on getting him to understand the scripts. Currently the contact e-mail address listed is my alternate e-mail as he is too young for a gmail account and so I can approve all actions before they are submitted to SBo. Today he submitted the update scripts for all builds listed as taking over maintenance, tuxkart which he is taking over from an orphaned state and the warzone2100 version bump update. If anyone is thinking of dropping maintenance of any games, my son would be interested in taking them over as he is picky about quality and will definitely test all builds prior to submission. -- -Thank You, -Matthew Fillpot -Slackware Documentation Project - Staff Editor - http://docs.slackware.com/wiki:user:mfillpot -Linux.com - Moderator - https://www.linux.com/forums/person/198 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply+45740624 at badoo.com Wed Feb 27 08:31:56 2013 From: noreply+45740624 at badoo.com (Badoo) Date: Wed, 27 Feb 2013 08:31:56 +0000 Subject: [Slackbuilds-users] =?utf-8?q?=E2=98=85_Slackbuilds_Users=2C_Mark?= =?utf-8?q?_left_a_message_for_you=2E=2E=2E?= Message-ID: You can instantly reply using our message exchange system. Check out your message... http://eu1.badoo.com/0291423883/in/oaoVvqKru5A/?lang_id=106&g=57&m=29&mid=512dc47a00000000006a0000013e317a03488c4a0108 Some more patiently waiting folks: If clicking the links in this message does not work, copy and paste them into the address bar of your browser. Have fun! The Badoo Team You have received this email from Badoo Trading Limited (postal address below). http://eu1.badoo.com/impersonation.phtml?lang_id=106&email=slackbuilds-users%40slackbuilds.org&block_code=b2a5a8&m=29&mid=512dc47a00000000006a0000013e317a03488c4a0108 Badoo Trading Limited is a limited company registered in England and Wales under CRN 7540255 with its registered office at Media Village, 131 - 151 Great Titchfield Street, London, W1W 5BB. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bradley at NorthTech.US Wed Feb 27 16:47:40 2013 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Wed, 27 Feb 2013 08:47:40 -0800 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: <201302011939.34522.xgizzmo@slackbuilds.org> References: <510C1057.8050900@NorthTech.US> <201302011939.34522.xgizzmo@slackbuilds.org> Message-ID: <512E38AC.2070209@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Apologies for the top-post. FYI, David, Chris, I used tips from your comments in the thread below at: http://www.linuxquestions.org/questions/showthread.php?p=4900906#post4900906 I would welcome any additional input or pointers you or anyone else has there and in part because I'm gathering data for a series of articles I'm writing on Slackware package management for a prominent Linux news site. On 02/01/2013 04:39 PM, xgizzmo at slackbuilds.org wrote: > On Friday 01 February 2013 13:58:31 Bradley D. Thornton wrote: >> >> On 01/31/2013 07:03 PM, John C. Gage wrote: >>> Has there ever been a thought to modify the slackbuild script to configure, >>> make and create the TXZ file in the same directory in which the SlackBuild >>> script was run? Can the mod also automatically call installpkg and install >>> the package all in one script? >> >> I tend to keep my SBo's in /usr/local/slackbuilds. Then when I untar >> them, they reside, along with the source which I download, in >> /usr/local/slackbuilds/. >> >> I like to keep all of my packages in /usr/local/packages, and create a >> symlink there so I can get any package via HTTP. It's convenient, much >> less messy than /tmp, which I like to keep cleaned out, and makes for >> easy re-distribution, rollbacks, and use of packages later. >> >> Change the output line in .SlackBuild from /tmp to: >> >> OUTPUT=${OUTPUT:-/usr/local/packages} >> >> I also change this to be the default in sbopkg too. Of course, you'll >> need to: >> >> # mkdir -p /usr/local/packages >> >> I hope that helps! >> >> Kindest regards, >> >> > > No reason to edit the Slackbuild at all add something like this to you profile: > > export OUTPUT="/usr/local/packages" > export PKGTYPE="txz" > > or > > OUTPUT="/usr/local/packages" PKGTYPE="txz" .SlackBuild > > --dsomero I hope neither of you mind me quoting you there. I took the liberties because the SBo list is publicly archived and I endeavored to attribute accordingly :) Thanks and kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJRLjisAAoJEE1wgkIhr9j38A4IAJ6MQqIO4zW4YVc+vzuBpoeI 2PIHZDxgwjrx9mDoOYBwZ7Xoy44e3/MDVHvh30l6Rtv3tVlY49WN0Hux3wYRNPm4 A3WsnwgGkA8c8fOqSa/B25lmxEJ0CYTUZ416OgI6Ez4UTnwx4j7AZID7KSZU5ATc KGsAyodKAHTfhFTdXcyHZdl54EkGsWoFnOnaLZZ4rw6eClQaB19/Ktkwqwz6iB8X OomfFUJ4XlABb1JbTvq0K1+hOr1K+hbqvjk8k2FiRS9Fmmr734c1JwyWnPqRnJAP 36HHt9ctbpr3bs267XZuex1mDICxSthasPRuQ6lt4nyrpEr4hp1smJWr6jGtFhY= =2RIh -----END PGP SIGNATURE----- From mjjzf at syntaktisk.dk Wed Feb 27 18:43:59 2013 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Wed, 27 Feb 2013 19:43:59 +0100 Subject: [Slackbuilds-users] Notice of New Maintainer In-Reply-To: References: Message-ID: <20130227194359.5da7bb0e@espero.syntaktisk.dk> On Tue, 26 Feb 2013 19:37:36 -0500 Matthew Fillpot wrote: > Admins, > This is a notification that I am passing my build scripts for > quesoglc, GLee, warzone2100, lightyears annd gpredict to my son > David. He has been taking interest in getting more involved in > Slackware and we have been working for the last few weeks on getting > him to understand the scripts. Currently the contact e-mail address > listed is my alternate e-mail as he is too young for a gmail account > and so I can approve all actions before they are submitted to SBo. Inheriting SlackBuilds? My deepest respect. Now I will go off and teach my kids BOTH editors. All the best, Morten __ Morten Juhl-Johansen Z?lde-Fej?r http://syntaktisk.dk * mjjzf at syntaktisk.dk From pfeifer.felix at gmail.com Wed Feb 27 17:04:59 2013 From: pfeifer.felix at gmail.com (Felix Pfeifer) Date: Wed, 27 Feb 2013 12:04:59 -0500 Subject: [Slackbuilds-users] 14.0 muse doinst setcap failing. In-Reply-To: References: <1361894145.512cdb01aaf12@imp.free.fr> <1361894290.512cdb9286a88@imp.free.fr> Message-ID: On 26 February 2013 16:53, B Watson wrote: > On 2/26/13, openpandora at free.fr wrote: >>> Also, on ARM device, the setcap fails with a "operation not supported", >> Oh, i've just realized maybe it's because i'm on ext2 ? > > ext2 should support filesystem capabilities, the same as ext3 and ext4 do. > > Maybe your ARM kernel doesn't have filesystem capabilities built in? > > The muse has at least one unfriendly thing it does, not related to > capabilities. In the doinst.sh: > > if grep GROUP\=\"audio\" /lib/udev/rules.d/65-permissions.rules > > /dev/null; then > echo > /dev/null > else > sed '/^KERNEL=="rtc\|rtc0"/s!$! , GROUP="audio"!' -i > /lib/udev/rules.d/65-permissions.rules > fi > > As I understand it, packages aren't supposed to modify the contents > of /lib/udev. Instead, the modified rules should get installed > to /etc/udev/rules.d. Not to mention, modifying the contents of a > standard rules file is something that can't be undone when the package is > removed... and if the udev package gets updated after muse is installed, > muse will break (because the modified 65-permissions.rules will get > overwritten with one from the new udev). Hi, i will try to fix the doinst.sh during the weekend. I guess the uploaded SBo script will stay a while in the pending queue though. Thank you guys for pointing this out. Felix