From info at microlinux.fr Fri Mar 1 14:23:19 2013 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 01 Mar 2013 15:23:19 +0100 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: References: <510B86EA.4010507@slackbuilds.org> Message-ID: <5130B9D7.9050704@microlinux.fr> Le 01/02/2013 13:09, John C. Gage a ?crit : > I'll have to check out sbopkg. Frankly, 'sbopkg' has just changed my life with Slackware. Almost as easy as the Ubuntu Software Center :o) 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 chess at chessgriffin.com Fri Mar 1 14:42:52 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 1 Mar 2013 09:42:52 -0500 Subject: [Slackbuilds-users] Slackbuild Directories In-Reply-To: <5130B9D7.9050704@microlinux.fr> References: <510B86EA.4010507@slackbuilds.org> <5130B9D7.9050704@microlinux.fr> Message-ID: <20130301144251.GA19753@localhost> * Niki Kovacs [2013-03-01 15:23:19]: > Le 01/02/2013 13:09, John C. Gage a ?crit : > >I'll have to check out sbopkg. > > Frankly, 'sbopkg' has just changed my life with Slackware. Almost as > easy as the Ubuntu Software Center :o) > Glad to hear it. And you should check out the sbopkg helper script 'sqg' that we recently added to the contrib/ directory in the sbopkg subversion repository. It can zip down through the repo and create sbopkg queuefiles for you with any REQUIRES= dependencies listed in order. -- Chess Griffin From andreakarimodm at gmail.com Fri Mar 1 18:50:05 2013 From: andreakarimodm at gmail.com (Andrea Villa) Date: Fri, 1 Mar 2013 19:50:05 +0100 Subject: [Slackbuilds-users] Metasploit and Framework duplicate Message-ID: Hi everybody, I am the maintainer of the metasploit SlackBuild. As you probably may know, metasploit "changed" his name in recent releases from "framework" to just "metasploit". To follow this change, I submitted, as the new official maintainer of the package, the latest SlackBuild for the newer version of Metasploit 4.5.2 with just the name of "metasploit". However the old 'framework' 4.0.0 SlackBuild was not superseded by my SlackBuild, with the effect that searching for "framework" or "metasploit" produces two results: both framework 4.0.0 and metasploit 4.5.2. I think the framework 4.0.0 SlackBuild should be removed from the tree. Best Regards, Andrea Villa -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at gmail.com Sat Mar 2 13:13:47 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 2 Mar 2013 20:13:47 +0700 Subject: [Slackbuilds-users] Change of maintainer of MySQL-Workbench Message-ID: Hi, based on discussion with the current maintainer, i'm taking over MySQL Workbench from Andre Should i submit two updates (one with a change of maintainer and one with updated version to 5.2.47) or just one update (change of maintainer + updated version to 5.2.47) ? ---------- Forwarded message ---------- From: Andr? Geraldo Vieira Date: Sat, Mar 2, 2013 at 7:53 PM Subject: Re: mysql-workbench To: Willy Sudiarto Raharjo 2013/2/28 Willy Sudiarto Raharjo > > Hi Andre, > > Are you still maintaining MySQL Workbench on SBo? > the current version is now 5.2.47 and the one available on SBo is still 5.2.43 > I'm willing to take over the maintainership if you don't use it > anymore since i've been updating it on my SlackHacks based on your > script > > Thanks Hello Willy, I created the script to meet a need of mine, then decided to make available on the SlackBuild. For me and unfeasible create a script for each new version, because I have no way to test in a new installation without the dependencies. Ideally, the new script is tested in a "new" installation without any dependence installed to make sure the script works. And like I said I'm not able to do that with every new version. I'm updated the script when I need to update my workstation or do a fresh install. For me there is no problem in you take on this task. I appreciate your willingness. I am available to take any questions that arise I help you with something. -- Diga n?o a Exclus?o Digital!! Valorize o C?digo Aberto!! Incentive o Software Livre!! N?o Seja Pirata, Seja Livre!! Por que GNU/Linux? "Somente pelo Prazer de ser LIVRE..." |_|0|_| |_|_|0| |0|0|0| Andr? Geraldo Vieira Bras?lia - DF Usu?rio Linux N? #335012 (Linux Counter, http://counter.li.org.) -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From binhvng at gmail.com Sat Mar 2 14:41:14 2013 From: binhvng at gmail.com (Binh Nguyen) Date: Sat, 2 Mar 2013 21:41:14 +0700 Subject: [Slackbuilds-users] Change of maintainer of MySQL-Workbench In-Reply-To: References: Message-ID: On Sat, Mar 2, 2013 at 8:13 PM, Willy Sudiarto Raharjo wrote: > Hi, > > based on discussion with the current maintainer, i'm taking over MySQL > Workbench from Andre > Should i submit two updates (one with a change of maintainer and one > with updated version to 5.2.47) or just one update (change of > maintainer + updated version to 5.2.47) ? It's fine to use just one submit for all the changes. I've done that a few times in similar situations. -- Binh From rworkman at slackbuilds.org Sun Mar 3 04:55:22 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 2 Mar 2013 22:55:22 -0600 Subject: [Slackbuilds-users] Metasploit and Framework duplicate In-Reply-To: References: Message-ID: <20130302225522.09f66f1d@home.rlworkman.net> On Fri, 1 Mar 2013 19:50:05 +0100 Andrea Villa wrote: > Hi everybody, > I am the maintainer of the metasploit SlackBuild. > As you probably may know, metasploit "changed" his name in recent > releases from "framework" to just "metasploit". > To follow this change, I submitted, as the new official maintainer of > the package, the latest SlackBuild for the newer version of > Metasploit 4.5.2 with just the name of "metasploit". > However the old 'framework' 4.0.0 SlackBuild was not superseded by my > SlackBuild, with the effect that searching for "framework" or > "metasploit" produces two results: both framework 4.0.0 and > metasploit 4.5.2. I think the framework 4.0.0 SlackBuild should be > removed from the tree. Best Regards, Thanks for the note - this is done in my git branch and will be part of the next public update. -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 Mar 3 05:08:37 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 2 Mar 2013 23:08:37 -0600 Subject: [Slackbuilds-users] =?utf-8?q?=E2=98=85_Slackbuilds_Users=2C_Mark?= =?utf-8?q?_left_a_message_for_you=2E=2E=2E?= In-Reply-To: <3ZG99d3PR0z38JC@harrier.slackbuilds.org> References: <3ZG99d3PR0z38JC@harrier.slackbuilds.org> Message-ID: <20130302230837.2fdbf67e@home.rlworkman.net> On Wed, 27 Feb 2013 08:31:56 +0000 Badoo wrote: > Snipped Badoo spam... Sorry to everyone for this getting through to the list. To be honest, I still don't know how that happened, but I'll give a summary here of what I do know. There were four messages sent around the same time from the same @badoo.com address: the first one was accepted while the other three were held for moderation. The Reply-to header contained the name of a list subscriber (Iskar Enev), and while I do *not* think that user had anything to do with this, I *do* think it's possible that Mailman was "tricked" into accepting the mail because of that header. I have not looked into Mailman's code, however. Now, I know the old adage about "never attribute to malice that which can be explained by incompetence," but I'm not sure about this one. See, several months ago, this list got *many* messages sent to it from LinkedIn, as if slackbuilds-users at slackbuilds.org had signed up for a LinkedIn profile, and apparently our name was Ivan. You never saw any of those messages because they were held for moderation (and so I deleted them). I eventually got tired of deleting them, so I went to LinkedIn's site, tried to sign in as "Ivan" (using this list's address), told it I had forgotten my password (which sent a reset link to the list address, which I viewed and later deleted), and then I changed the password and deleted the profile - problem solved. Well... guess what? This "Ivan" had also created a profile at Badoo using the list address. I have no idea how that is even possible - it seems to me that the confirmation mail would never be received (after all, it's held for moderation, and besides, I never saw one sent to the list address), but somehow, that's what's happening, I guess. I don't know if this "Ivan" is that much of a dumbass or if there's some spambot that's doing it or if maybe something else is going on. Anyway, the Badoo profile has also been deleted now, so maybe "Ivan" will leave us alone. We'll see. In the meantime, I've upgraded our Mailman installation to 2.1.15, and the NEWS mentions a few security-related bugfixes: - Strengthened the validation of email addresses. - An XSS vulnerability, CVE-2011-0707, has been fixed. - The web admin interface has been hardened against CSRF attacks by adding a hidden, encrypted token with a time stamp to form submissions and not accepting authentication by cookie if the token is missing, invalid or older than the new mm_cfg.py setting FORM_LIFETIME which defaults to one hour. Posthumous thanks go to Tokio Kikuchi for this implementation which is only one of his many contributions to Mailman prior to his death from cancer on 14 January 2012. -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 Mar 3 05:19:53 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 2 Mar 2013 23:19:53 -0600 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: <20130302231953.69f5c8b2@home.rlworkman.net> On Tue, 26 Feb 2013 16:53:44 -0500 B Watson wrote: > 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). Yes, good point and all correct. The real question I have is what exactly that sed is supposed to accomplish. All it does is make /dev/rtc belong to audio group, but it doesn't change the permissions from 0644 on the node. In other words, it doesn't actually *do* anything useful at all. Therefore, I'm going to remove that part from the doinst.sh in my branch. If the maintainer thinks something else is supposed to happen there, then that fix will need to happen in an updated submission. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From yochanon at lavabit.com Sun Mar 3 06:07:10 2013 From: yochanon at lavabit.com (JB) Date: Sun, 3 Mar 2013 00:07:10 -0600 Subject: [Slackbuilds-users] =?utf-8?q?=E2=98=85_Slackbuilds_Users=2C_Mark?= =?utf-8?q?_left_a_message_for_you=2E=2E=2E?= In-Reply-To: <20130302230837.2fdbf67e@home.rlworkman.net> References: <3ZG99d3PR0z38JC@harrier.slackbuilds.org> <20130302230837.2fdbf67e@home.rlworkman.net> Message-ID: <20130303000710.6dc0690f@oogah.boogah.org> On Sat, 2 Mar 2013 23:08:37 -0600 Robby Workman wrote: > On Wed, 27 Feb 2013 08:31:56 +0000 > Badoo wrote: > > > Snipped Badoo spam... > > > Sorry to everyone for this getting through to the list. > > -RW Don't sweat it, Robby. It's not like the list was inundated or anything. IIRR, it was only one or two. You got a lot of irons in the fire and one or two little e-mails sneaking past you to the list is not something you need to worry about, heh. -- Gun control works http://www.youtube.com/watch?v=0sujnvIV4g4 From rshepard at appl-ecosys.com Sun Mar 3 14:03:08 2013 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 3 Mar 2013 06:03:08 -0800 (PST) Subject: [Slackbuilds-users] =?utf-8?q?=E2=98=85_Slackbuilds_Users=2C_Mark?= =?utf-8?q?_left_a_message_for_you=2E=2E=2E?= In-Reply-To: <20130302230837.2fdbf67e@home.rlworkman.net> References: <3ZG99d3PR0z38JC@harrier.slackbuilds.org> <20130302230837.2fdbf67e@home.rlworkman.net> Message-ID: On Sat, 2 Mar 2013, Robby Workman wrote: > Sorry to everyone for this getting through to the list. Robby, The spammers and walwere senders have very sophisticated ways of obfuscating headers and text so the message passes through filters, postfix header and body checks in my case. As I'm not a computer professional I do not understand how this is done nor have I the time to try to learn and fix the problem. Almost every day I get spam that I try to report to the originating ISP but the outgoing message is blocked by one of my postfix rules. How it is obscured when coming in I've no idea, but my MUA is alpine so it's plain text trying to get out and that's when it's caught. I've seen these messages from slackbuild, jabref, lyx, and other mail lists to which I subscribe, including a bunch supposedly from linkedin. I don't hold the list administrator accountable, just press the 'd' key and move on > Now, I know the old adage about "never attribute to malice that > which can be explained by incompetence," There's apparently a lot of malice alive and well on the 'Net, especially the WWW. Given the recent publicity about official China behind a lot of serious cracking to steal economic and political intelligence the push by server owners to put everyone's data on the 'cloud' scares me. I won't do it, but what about my banks and other businesses with whom I do business? Computers are just not completely secure, especially when admins do not keep up on installing all patches to identified vulnerabilities. You do great work that benefits all of us. Deleting spam that makes it through to the list is easy enough for each of us to do. Regards, Rich From klaatu at straightedgelinux.com Mon Mar 4 14:53:45 2013 From: klaatu at straightedgelinux.com (Klaatu) Date: Mon, 04 Mar 2013 09:53:45 -0500 Subject: [Slackbuilds-users] =?utf-8?q?=E2=98=85_Slackbuilds_Users=2C_Mark?= =?utf-8?q?_left_a_message_for_you=2E=2E=2E?= In-Reply-To: <20130302230837.2fdbf67e@home.rlworkman.net> References: <3ZG99d3PR0z38JC@harrier.slackbuilds.org> <20130302230837.2fdbf67e@home.rlworkman.net> Message-ID: <1473203.aCQQ21b8Mh@slackk> On Saturday, March 02, 2013 11:08:37 PM Robby Workman wrote: > On Wed, 27 Feb 2013 08:31:56 +0000 > > Badoo wrote: > > Snipped Badoo spam... > > Sorry to everyone for this getting through to the list. To > be honest, I still don't know how that happened, but I'll give > a summary here of what I do know. There were four messages > sent around the same time from the same @badoo.com address: > the first one was accepted while the other three were held > for moderation. The Reply-to header contained the name of a > list subscriber (Iskar Enev), and while I do *not* think that > user had anything to do with this, I *do* think it's possible > that Mailman was "tricked" into accepting the mail because of > that header. I have not looked into Mailman's code, however. > > Now, I know the old adage about "never attribute to malice that > which can be explained by incompetence," but I'm not sure about > this one. See, several months ago, this list got *many* messages > sent to it from LinkedIn, as if slackbuilds-users at slackbuilds.org > had signed up for a LinkedIn profile, and apparently our name was > Ivan. You never saw any of those messages because they were held > for moderation (and so I deleted them). I eventually got tired > of deleting them, so I went to LinkedIn's site, tried to sign in > as "Ivan" (using this list's address), told it I had forgotten > my password (which sent a reset link to the list address, which > I viewed and later deleted), and then I changed the password and > deleted the profile - problem solved. > > Well... guess what? This "Ivan" had also created a profile at > Badoo using the list address. I have no idea how that is even > possible - it seems to me that the confirmation mail would never > be received (after all, it's held for moderation, and besides, > I never saw one sent to the list address), but somehow, that's > what's happening, I guess. I don't know if this "Ivan" is that > much of a dumbass or if there's some spambot that's doing it or > if maybe something else is going on. Anyway, the Badoo profile > has also been deleted now, so maybe "Ivan" will leave us alone. > We'll see. > > In the meantime, I've upgraded our Mailman installation to 2.1.15, > and the NEWS mentions a few security-related bugfixes: > - Strengthened the validation of email addresses. > - An XSS vulnerability, CVE-2011-0707, has been fixed. > - The web admin interface has been hardened against CSRF attacks > by adding a hidden, encrypted token with a time stamp to form > submissions and not accepting authentication by cookie if the > token is missing, invalid or older than the new mm_cfg.py > setting FORM_LIFETIME which defaults to one hour. Posthumous > thanks go to Tokio Kikuchi for this implementation which is > only one of his many contributions to Mailman prior to his > death from cancer on 14 January 2012. > > -RW Thanks for the detailed report, Robby. It was both educational and informative, and - not that I had any doubt, but - it is re-assuring to know that real people with working brains actually do bother monitoring the Slackbuild infrastructure. -klaatu From xgizzmo at slackbuilds.org Mon Mar 4 23:19:49 2013 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Mon, 4 Mar 2013 18:19:49 -0500 Subject: [Slackbuilds-users] Updates - 20130304.1 Message-ID: <201303041819.50046.xgizzmo@slackbuilds.org> Mon Mar 4 22:30:59 UTC 20130301 academic/gpredict: New maintainer audio/muse: Kill badness in doinst.sh audio/volwheel: Set MAINTAINER to "nobody" (abandoned) desktop/obmenu: Set MAINTAINER to "nobody" (abandoned) desktop/openbox-themes: Set MAINTAINER to "nobody" (abandoned) desktop/stalonetray: Set MAINTAINER to "nobody" (abandoned) desktop/xmobar: Updated for version 0.16. desktop/xmonad: Updated for version 0.11. development/alex: Updated for version 3.0.4. development/darcs: Updated for version 2.8.4. development/gforth: Added (GNU Forth interpreter) development/happy: Updated for version 1.18.10. development/nose: Updated for version 1.2.1. development/setuptools-git: Updated for version 1.0b1. development/zope.interface: Updated for version 4.0.4. development/zope.testing: Updated for version 4.1.2. games/darkplaces: Updated for version 20130301. games/gtkballs: Set MAINTAINER to "nobody" (abandoned) games/lightyears: New maintainer games/tuxkart: New maintainer games/warzone2100: Updated for version 3.1.0. graphics/gallery3: Added (web-based photo album organizer) graphics/shutter: Set MAINTAINER to "nobody" (abandoned) graphics/ufraw: Updated for version 0.19. haskell/ghc: Updated for version 7.6.2. haskell/haskell-Diff: Updated for version 0.3.0. haskell/haskell-GLURaw: Updated for version 1.3.0.0. haskell/haskell-GLUT: Updated for version 2.3.1.0. haskell/haskell-HTTP: Updated for version 4000.2.8. haskell/haskell-HUnit: Updated for version 1.2.5.1. haskell/haskell-MonadCatchIO-mtl: Updated for version 0.3.0.5. haskell/haskell-OpenGL: Updated for version 2.6.0.1. haskell/haskell-OpenGLRaw: Updated for version 1.3.0.0. haskell/haskell-QuickCheck: Updated for version 2.5.1.1. haskell/haskell-X11: Updated for version 1.6.0.2. haskell/haskell-ansi-terminal: Updated for version 0.6. haskell/haskell-ansi-wl-pprint: Updated for version 0.6.6. haskell/haskell-base64-bytestring: Updated for version 1.0.0.1. haskell/haskell-blaze-html: Updated for version 0.5.1.3. haskell/haskell-blaze-markup: Updated for version 0.5.1.4. haskell/haskell-bmp: Updated for version 1.2.3.4. haskell/haskell-cgi: Updated for version 3001.1.8.3. haskell/haskell-citeproc-hs: Updated for version 0.3.7. haskell/haskell-data-default: Added (types with a default value) haskell/haskell-dataenc: Updated for version 0.14.0.5. haskell/haskell-digest: Updated for version 0.0.1.2. haskell/haskell-editline: Updated for version 0.2.1.1. haskell/haskell-extensible-exceptions: Added (Extensible exceptions) haskell/haskell-ghc-paths: Updated for version 0.1.0.9. haskell/haskell-gloss: Updated for version 1.7.8.2. haskell/haskell-hashed-storage: Updated for version 0.5.10. haskell/haskell-haskeline: Updated for version 0.7.0.3. haskell/haskell-highlighting-kate: Updated for version 0.5.3.7. haskell/haskell-hinotify: Updated for version 0.3.5. haskell/haskell-json: Updated for version 0.7. haskell/haskell-mmap: Updated for version 0.5.8. haskell/haskell-mtl: Updated for version 2.1.2. haskell/haskell-network: Updated for version 2.4.1.2. haskell/haskell-pandoc-types: Updated for version 1.10. haskell/haskell-primitive: Updated for version 0.5.0.1. haskell/haskell-regex-pcre-builtin: Updated for ver 0.94.4.5.8.31. haskell/haskell-stm: Updated for version 2.4.2. haskell/haskell-syb: Updated for version 0.3.7. haskell/haskell-tagsoup: Updated for version 0.12.8. haskell/haskell-tar: Updated for version 0.4.0.1. haskell/haskell-temporary: Updated for version 1.1.2.4. haskell/haskell-terminfo: Updated for version 0.3.2.5. haskell/haskell-test-framework-hunit: Updated for version 0.3.0. haskell/haskell-test-framework-quickcheck2: Updated for ver 0.3.0.1. haskell/haskell-test-framework: Updated for version 0.8. haskell/haskell-texmath: Updated for version 0.6.1.3. haskell/haskell-text: Updated for version 0.11.2.3. haskell/haskell-vector: Updated for version 0.10.0.1. haskell/haskell-zip-archive: Updated for version 0.1.3.3. haskell/haskell-zlib: Updated for version 0.5.4.0. haskell/hscolour: Updated for version 1.20.3. haskell/xmonad-contrib: Updated for version 0.11. libraries/FormEncode: Updated for version 1.2.6. libraries/GLee: New maintainer libraries/SQLObject: Updated for version 1.3.2. libraries/ZConfig: Updated for version 3.0.2. libraries/decorator: Updated for version 3.4.0. libraries/freealut: fixed download link libraries/geos: Updated for version 3.3.8. libraries/libpqxx: fix typo in find line libraries/libssh2: Updated for version 1.4.3. libraries/opencv: Updated for version 2.4.4. libraries/quesoglc: New maintainer libraries/xawplus: Fix to makefile patch (fixed include directories) libraries/zc.lockfile: Updated for version 1.1.0. libraries/zdaemon: Updated for version 4.0.0a1. libraries/zope.component: Updated for version 4.0.2. libraries/zope.configuration: Updated for version 4.0.2. libraries/zope.event: Updated for version 4.0.2. libraries/zope.hookable: Updated for version 4.0.1. libraries/zope.i18nmessageid: Updated for version 4.0.2. libraries/zope.location: Updated for version 4.0.1. libraries/zope.proxy: Updated for version 4.1.1. libraries/zope.schema: Updated for version 4.2.2. libraries/zope.security: Updated for version 4.0.0a4. misc/gprename: Set MAINTAINER to "nobody" (abandoned) multimedia/flash-player-plugin: Updated for version 11.2.202.273. multimedia/realplayer: Set MAINTAINER to "nobody" (abandoned) network/framework: Removed (obsolete - use metasploit) network/gtorrentviewer: Set MAINTAINER to "nobody" (abandoned) network/imageshack-uploader: Set MAINTAINER to "nobody" (abandoned) network/rssh: Updated for version 2.3.4. network/shibboleth-sp: Added (Shibboleth Service Provider) network/zabbix_agentd: Updated for version 1.8.16. network/zabbix_proxy: Updated for version 1.8.16. network/zabbix_server: Updated for version 1.8.16. office/adobe-reader: Updated for version 9.5.4. perl/perl-File-HomeDir: Updated for version 1.00. perl/perl-Sort-Naturally: Updated for version 1.03. python/lxml: Updated for version 3.1.0. python/subvertpy: Updated for version 0.9.0. system/artwiz-aleczapka: Reworked (split cursor font out) system/artwiz-cursor: Added (futuristic mouse cursor for X11) system/bochs: fix wrong --enable-sb16 parameter system/postgis: Updated for version 2.0.3. system/xen: kill obsolete udev rules +--------------------------+ From willysr at gmail.com Tue Mar 5 03:46:28 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Tue, 5 Mar 2013 10:46:28 +0700 Subject: [Slackbuilds-users] e16 version Message-ID: Hi, I think e16.info got a wrong version information http://slackbuilds.org/slackbuilds/14.0/desktop/e16/e16.info VERSION="version of application" -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From josiahb at gmail.com Tue Mar 5 16:17:09 2013 From: josiahb at gmail.com (Josiah Boothby) Date: Tue, 5 Mar 2013 08:17:09 -0800 Subject: [Slackbuilds-users] e16 version In-Reply-To: References: Message-ID: <20130305081709.7d048c92@corvus.troglophonic.org> > I think e16.info got a wrong version information > http://slackbuilds.org/slackbuilds/14.0/desktop/e16/e16.info > VERSION="version of application" Oops, sure enough. I'll send in a correction, unless there's an easier way to change it to 1.0.11. ?Josiah From openpandora at free.fr Tue Mar 5 18:40:45 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 05 Mar 2013 19:40:45 +0100 Subject: [Slackbuilds-users] 14.0 muse doinst setcap failing. In-Reply-To: <20130302231953.69f5c8b2@home.rlworkman.net> References: <1361894145.512cdb01aaf12@imp.free.fr> <1361894290.512cdb9286a88@imp.free.fr> <20130302231953.69f5c8b2@home.rlworkman.net> Message-ID: <1362508845.51363c2d929de@imp.free.fr> Seen the updated SB, you forgot to change: /usr/bin/muse into /usr/bin/muse2 in the doinst :/. LS Quoting Robby Workman : > On Tue, 26 Feb 2013 16:53:44 -0500 > B Watson wrote: > > > 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). > > > Yes, good point and all correct. The real question I have is what > exactly that sed is supposed to accomplish. All it does is make > /dev/rtc belong to audio group, but it doesn't change the permissions > from 0644 on the node. In other words, it doesn't actually *do* > anything useful at all. Therefore, I'm going to remove that part > from the doinst.sh in my branch. If the maintainer thinks something > else is supposed to happen there, then that fix will need to happen > in an updated submission. > > -RW > From rworkman at slackbuilds.org Wed Mar 6 03:26:42 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 5 Mar 2013 21:26:42 -0600 Subject: [Slackbuilds-users] e16 version In-Reply-To: <20130305081709.7d048c92@corvus.troglophonic.org> References: <20130305081709.7d048c92@corvus.troglophonic.org> Message-ID: <20130305212642.5817ee9d@home.rlworkman.net> On Tue, 5 Mar 2013 08:17:09 -0800 Josiah Boothby wrote: > > I think e16.info got a wrong version information > > http://slackbuilds.org/slackbuilds/14.0/desktop/e16/e16.info > > VERSION="version of application" > > Oops, sure enough. > > I'll send in a correction, unless there's an easier way to change it > to 1.0.11. I just fixed it in my git branch, so no need for the submission; I'll clear it from pending. Sorry about letting that slip through. -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 Wed Mar 6 03:32:28 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 5 Mar 2013 21:32:28 -0600 Subject: [Slackbuilds-users] radiotray slackbuild missing deps In-Reply-To: <1360005447.36143.YahooMailNeo@web172104.mail.ir2.yahoo.com> References: <1360005447.36143.YahooMailNeo@web172104.mail.ir2.yahoo.com> Message-ID: <20130305213228.6e60e7f2@home.rlworkman.net> On Mon, 4 Feb 2013 19:17:27 +0000 (GMT) le wrote: > 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 Sorry for the delay on this; it's now 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 Wed Mar 6 03:35:04 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 5 Mar 2013 21:35:04 -0600 Subject: [Slackbuilds-users] deluge dependency In-Reply-To: <510CAB8C.2040504@gmail.com> References: <510CAB8C.2040504@gmail.com> Message-ID: <20130305213504.1f00ae8c@home.rlworkman.net> On Sat, 02 Feb 2013 00:00:44 -0600 Zach wrote: > Deluge requires python2-chardet, which isn't listed. Marco, can you confirm 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 sid77 at slackware.it Wed Mar 6 09:16:42 2013 From: sid77 at slackware.it (Marco Bonetti) Date: Wed, 06 Mar 2013 09:16:42 +0000 Subject: [Slackbuilds-users] deluge dependency In-Reply-To: <20130305213504.1f00ae8c@home.rlworkman.net> References: <510CAB8C.2040504@gmail.com> <20130305213504.1f00ae8c@home.rlworkman.net> Message-ID: On 13.37 the dependency was called chardet, now it has probably been renamed or splitted into two packages :) I do not have a14.0 system to verify the claim, though Ciao! -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dnied at tiscali.it Wed Mar 6 10:23:37 2013 From: dnied at tiscali.it (Dario Niedermann) Date: Wed, 06 Mar 2013 11:23:37 +0100 Subject: [Slackbuilds-users] GoogleEarth not running Message-ID: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> ~> /usr/bin/googleearth /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: No such file or directory Exit 127 ~> /opt/GoogleEarth/googleearth-bin /opt/GoogleEarth/googleearth-bin: Command not found. Exit 1 ~> ls -l /opt/GoogleEarth/googleearth-bin -rwxr-xr-x 1 root root 5452 May 17 2011 /opt/GoogleEarth/googleearth-bin ~> Not sure why the silly thing doesn't know about its own existence. One thing is certain: the installer should add '/opt/GoogleEarth' to '/etc/ld.so.conf' and do `ldconfig`, otherwise the dynamic linker won't find the GoogleEarth libraries. Once done, the binary still won't run, but at least `ldd /opt/GoogleEarth/googleearth-bin` will report no missing libraries. From willysr at gmail.com Wed Mar 6 10:45:38 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Wed, 6 Mar 2013 17:45:38 +0700 Subject: [Slackbuilds-users] GoogleEarth not running In-Reply-To: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> References: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> Message-ID: > Not sure why the silly thing doesn't know about its own existence. > > One thing is certain: the installer should add '/opt/GoogleEarth' to > '/etc/ld.so.conf' and do `ldconfig`, otherwise the dynamic linker won't > find the GoogleEarth libraries. Once done, the binary still won't run, > but at least `ldd /opt/GoogleEarth/googleearth-bin` will report no > missing libraries. Are you running Slackware64 ? Google Earth will run ONLY on multilib machine for x86_64 -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From dnied at tiscali.it Wed Mar 6 10:55:05 2013 From: dnied at tiscali.it (Dario Niedermann) Date: Wed, 06 Mar 2013 11:55:05 +0100 Subject: [Slackbuilds-users] GoogleEarth not running In-Reply-To: References: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> Message-ID: <51372089./oRKw7oY28KGJEo4%dnied@tiscali.it> Willy Sudiarto Raharjo wrote: > Are you running Slackware64 ? > Google Earth will run ONLY on multilib machine for x86_64 Thanks for the reply. No, I'm on 32-bit and I just solved the issue by following point 2 of the README, which - sorry! - had completely escaped me ( `ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3` ). This should probably be done by the install script, as well as the '/etc/ld.so.conf' thing. From yalhcru at gmail.com Wed Mar 6 15:06:14 2013 From: yalhcru at gmail.com (B Watson) Date: Wed, 6 Mar 2013 10:06:14 -0500 Subject: [Slackbuilds-users] GoogleEarth not running In-Reply-To: <51372089./oRKw7oY28KGJEo4%dnied@tiscali.it> References: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> <51372089./oRKw7oY28KGJEo4%dnied@tiscali.it> Message-ID: On 3/6/13, Dario Niedermann wrote: > by following point 2 of the README, which - sorry! - had completely > escaped me ( `ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3` ). > > This should probably be done by the install script, as well as the > '/etc/ld.so.conf' thing. Better yet. The SlackBuild should modify the binary so it requires /lib/ld-2.15.so instead of /lib/ld-lsb.so.3. This can actually be done with sed, somewhere near the bottom of the .SlackBuild: sed -i 's,/lib/ld-lsb.so.3,/lib/ld-2.15.so\x00,' $PKG/opt/$PRGNAM/googleearth-bin sedding a binary is scary, but it actually does work. The replacement string has to be the same length as the original (but can be padded with null bytes), so we can't actually replace it with /lib/ld-linux.so.2 (too long). That's just a symlink to ld-2.15.so anyway... The package will break if a newer glibc is installed (e.g. one with ld-2.16.so instead). I wouldn't consider that a big deal, lots of 3rd-party packages break when upgrading libraries, especially glibc. The ld.so.conf edit shouldn't be required: the wrapper script (/opt/GoogleEarth/googleearth) contains code to export LD_LIBRARY_PATH before running googleearth-bin. The only way you'd need to edit ld.so.conf would be if you were running (or using ldd on) googleearth-bin directly. Another point mentioned in the README: upstream changes the tarball and doesn't include the version number in the filename, so the md5sum can fail. This could be fixed by hosting the file elsewhere... I could host it on urchlay.naptime.net, or someone else here could host it, maybe at http://sourceforge.net/projects/slackbuilds/ From C.J.Theunissen at differ.nl Wed Mar 6 19:04:13 2013 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Wed, 6 Mar 2013 20:04:13 +0100 (CET) Subject: [Slackbuilds-users] GoogleEarth not running In-Reply-To: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> References: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> Message-ID: On Wed, 6 Mar 2013, Dario Niedermann wrote: >One thing is certain: the installer should add '/opt/GoogleEarth' to >'/etc/ld.so.conf' and do `ldconfig`, otherwise the dynamic linker won't >find the GoogleEarth libraries. This is handled by setting and exporting LD_LIBRARY_PATH in the /opt/GoogleEarth/googleearth wrapper script. Regards, Kees. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL From lmello.009 at gmail.com Wed Mar 6 22:52:40 2013 From: lmello.009 at gmail.com (Luis Henrique Mello) Date: Wed, 06 Mar 2013 19:52:40 -0300 Subject: [Slackbuilds-users] Removal of mac In-Reply-To: References: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> Message-ID: <5137C8B8.5060708@gmail.com> Well the homepage is dead and ffmpeg can decode .ape audio files. I think it should be removed, or does anyone know where to find a copy of the source code? From rworkman at slackbuilds.org Thu Mar 7 04:10:09 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 6 Mar 2013 22:10:09 -0600 Subject: [Slackbuilds-users] deluge dependency In-Reply-To: References: <510CAB8C.2040504@gmail.com> <20130305213504.1f00ae8c@home.rlworkman.net> Message-ID: <20130306221009.7c94a86a@home.rlworkman.net> On Wed, 06 Mar 2013 09:16:42 +0000 Marco Bonetti wrote: > On 13.37 the dependency was called chardet, now it has probably been > renamed or splitted into two packages :) > > I do not have a14.0 system to verify the claim, though Okay, that sounds reasonable; I went ahead and added it in my 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 willysr at gmail.com Thu Mar 7 13:07:00 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Thu, 7 Mar 2013 20:07:00 +0700 Subject: [Slackbuilds-users] Spotify Source broken Message-ID: Spotify source has been updated, so the current source is no longer working as reported by someone in IRC The new source will be http://repository.spotify.com/pool/non-free/s/spotify/spotify-client_0.8.8.323.gd143501.250-1_i386.deb http://repository.spotify.com/pool/non-free/s/spotify/spotify-client_0.8.8.323.gd143501.250-1_amd64.deb Since this is a rolling release (they tend to remove older version), i think it's best to keep this version in harriers? At least it won't break when they released another version unless the maintainer wanted to host the source somewhere else? -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From chess at chessgriffin.com Thu Mar 7 15:25:47 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 7 Mar 2013 10:25:47 -0500 Subject: [Slackbuilds-users] Removal of mac In-Reply-To: <5137C8B8.5060708@gmail.com> References: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> <5137C8B8.5060708@gmail.com> Message-ID: <20130307152546.GA13357@localhost> * Luis Henrique Mello [2013-03-06 19:52:40]: > Well the homepage is dead and ffmpeg can decode .ape audio files. I > think it should be removed, or does anyone know where to find a copy > of the source code? Well, it looks like ponce is hosting the source himself. But if you need to find another location, I always like to check for FreeBSD and Gentoo distfile locations. I came up with: http://bsd2.cenkes.org/myports/mac-3.99-u4-b5.tar.gz http://etree.org/shnutils/shntool/support/formats/ape/unix/3.99-u4-b5/mac-3.99-u4-b5.tar.gz -- Chess Griffin From jjalmeida at gmail.com Thu Mar 7 17:13:14 2013 From: jjalmeida at gmail.com (Jorge Almeida) Date: Thu, 7 Mar 2013 17:13:14 +0000 Subject: [Slackbuilds-users] feh Message-ID: Compiling feh-2.3 on Slackware 14.0 is failing. The two libraries mentioned as prerequisites are installed. imlib2-1.4.5-i686-1_SBo giblib-1.2.4-i686-2_SBo TIA Jorge Almeida make[1]: Entering directory `/slash/var/slack/slackbuild/tmp/feh-2.3/src' sed 's/^\(.*\)$/"\1\\n"/' < help.raw > help.inc cc -MM collage.c events.c exif.c feh_png.c filelist.c getopt.c getopt1.c imlib.c index.c keyevents.c list.c main.c md5.c menu.c multiwindow.c options.c signals.c slideshow.c thumbnail.c timers.c utils.c wallpaper.c winwidget.c > deps.mk make[1]: Leaving directory `/slash/var/slack/slackbuild/tmp/feh-2.3/src' make[1]: Entering directory `/slash/var/slack/slackbuild/tmp/feh-2.3/src' cc -O2 -march=native -c -o collage.o collage.c collage.c: In function 'init_collage_mode': collage.c:68:11: error: 'PACKAGE' undeclared (first use in this function) collage.c:68:11: note: each undeclared identifier is reported only once for each function it appears in collage.c:69:6: error: expected ')' before string constant collage.c:72:6: error: too few arguments to function 'fputs' collage.c:78:6: error: expected ')' before string constant collage.c:81:6: error: too few arguments to function 'fputs' collage.c:111:7: error: expected ')' before string constant collage.c:202:28: error: expected ')' before string constant make[1]: *** [collage.o] Error 1 From kingbeowulf at gmail.com Fri Mar 8 01:59:30 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 07 Mar 2013 17:59:30 -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: <51394602.8090103@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... > > > _______________________________________________ > 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/ > Mateo, when I go to http://cgit.ponce.cc/slackbuilds/commit/?h=qemu and d/l the snapshot "slackbuilds-qemu.tar.gz" I get a copy of your entire repo tree. Somehow that does now seem to be the correct behavior? Or, if it is, then the file naming is incorrect? Thanks Ed From rworkman at slackbuilds.org Fri Mar 8 02:07:00 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 7 Mar 2013 20:07:00 -0600 Subject: [Slackbuilds-users] RFC: drop or merge qemu-kvm In-Reply-To: <51394602.8090103@gmail.com> References: <512BE79A.10602@gmail.com> <20130225211845.25e5abfa@home.rlworkman.net> <20130225213742.78db2cbf@home.rlworkman.net> <51394602.8090103@gmail.com> Message-ID: <20130307200700.428fd962@home.rlworkman.net> On Thu, 07 Mar 2013 17:59:30 -0800 King Beowulf wrote: > 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... > > > > > Mateo, > when I go to http://cgit.ponce.cc/slackbuilds/commit/?h=qemu and d/l > the snapshot "slackbuilds-qemu.tar.gz" I get a copy of your entire > repo tree. Somehow that does now seem to be the correct behavior? > Or, if it is, then the file naming is incorrect? That's the correct behavior - what you're actually getting is a snapshot of the source tree as of that commit. What you probably want to do instead is clone his git repo to a local directory, then cd into it, "git checkout qemu" and then copy ./system/qemu/ to wherever you want 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 leva at ecentrum.hu Sat Mar 9 16:24:06 2013 From: leva at ecentrum.hu (LEVAI Daniel) Date: Sat, 9 Mar 2013 17:24:06 +0100 Subject: [Slackbuilds-users] can not re-submit a port Message-ID: <20130309162405.GA7938@daniell-kurt> Hi! After removing perl-Text-Diff from pending, when trying to submit again, the page says: File exists; a submission by the name 'perl-Text-Diff' is already pending approval. I can not spot it in ^/pending, so what can I do now? Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From lmello.009 at gmail.com Sun Mar 10 22:06:14 2013 From: lmello.009 at gmail.com (Luis Henrique Mello) Date: Sun, 10 Mar 2013 19:06:14 -0300 Subject: [Slackbuilds-users] Removal of mac In-Reply-To: <20130307152546.GA13357@localhost> References: <51371929.Fasi0nKW1l8ZJ55t%dnied@tiscali.it> <5137C8B8.5060708@gmail.com> <20130307152546.GA13357@localhost> Message-ID: <513D03D6.4040909@gmail.com> Thank you Chess, just submitted mac.tar.gz with one valid download link. On 03/07/2013 12:25 PM, Chess Griffin wrote: > * Luis Henrique Mello [2013-03-06 19:52:40]: > >> Well the homepage is dead and ffmpeg can decode .ape audio files. I >> think it should be removed, or does anyone know where to find a copy >> of the source code? > > Well, it looks like ponce is hosting the source himself. But if you > need to find another location, I always like to check for FreeBSD and > Gentoo distfile locations. I came up with: > > http://bsd2.cenkes.org/myports/mac-3.99-u4-b5.tar.gz > http://etree.org/shnutils/shntool/support/formats/ape/unix/3.99-u4-b5/mac-3.99-u4-b5.tar.gz > > From xgizzmo at slackbuilds.org Mon Mar 11 23:05:56 2013 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Mon, 11 Mar 2013 19:05:56 -0400 Subject: [Slackbuilds-users] can not re-submit a port In-Reply-To: <20130309162405.GA7938@daniell-kurt> References: <20130309162405.GA7938@daniell-kurt> Message-ID: <201303111905.56719.xgizzmo@slackbuilds.org> On Saturday 09 March 2013 11:24:06 LEVAI Daniel wrote: > Hi! > > After removing perl-Text-Diff from pending, when trying to submit again, > the page says: > File exists; a submission by the name 'perl-Text-Diff' is already pending approval. > > I can not spot it in ^/pending, so what can I do now? > > > Daniel > Please email me the tarball, I am not sure why you can't submit it. From markus.hutmacher at gmail.com Wed Mar 13 08:19:01 2013 From: markus.hutmacher at gmail.com (Markus Hutmacher) Date: Wed, 13 Mar 2013 09:19:01 +0100 Subject: [Slackbuilds-users] nethogs has been upgraded from 0.7.0 to 0.8.0 Message-ID: <51403675.9070009@gmail.com> Hello together, I've built nethogs with the Slackbuildscript after changing 0.7.0 to 0.8.0 without problems, but of course the downloadlink at slackbuilds.org doesn't work any longer due to change of the version. Regards Markus -- Markus Hutmacher markus.hutmacher at gmail.com From korgie at gmail.com Wed Mar 13 22:48:58 2013 From: korgie at gmail.com (korgman) Date: Thu, 14 Mar 2013 00:48:58 +0200 Subject: [Slackbuilds-users] nethogs has been upgraded from 0.7.0 to 0.8.0 In-Reply-To: <51403675.9070009@gmail.com> References: <51403675.9070009@gmail.com> Message-ID: <5141025A.5010004@gmail.com> On 13/03/2013 10:19 ??, Markus Hutmacher wrote: > I've built nethogs with the Slackbuildscript after changing 0.7.0 to 0.8.0 without problems, but of course the downloadlink at slackbuilds.org doesn't work any longer due to change of the version. I am the maintainer. @admins, should I submit an update or the job is considered done? In case of update I need 4-5 days to submit. (the download link for version-0.7.0 works for me) From dnied at tiscali.it Fri Mar 15 12:06:59 2013 From: dnied at tiscali.it (Dario Niedermann) Date: Fri, 15 Mar 2013 13:06:59 +0100 Subject: [Slackbuilds-users] libfm requires the Vim editor! Message-ID: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> After building libfm-1.1.0, I would recommend adding the following option to its SlackBuild's `configure` line: --disable-gtk-doc-html If the above is not specified, the build will require the Vim editor to be installed, or it will fail, which I don't think is reasonable. Regards, DN From michiel at slackbuilds.org Fri Mar 15 14:07:03 2013 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Fri, 15 Mar 2013 14:07:03 +0000 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> Message-ID: <20130315140703.683f4316@hades.olympus.lan> On Fri, 15 Mar 2013 13:06:59 +0100 Dario Niedermann wrote: > the above is not specified, the build will require the Vim editor > to be installed, or it will fail, which I don't think is reasonable. I can't speak for the other admins, but I am against it. The reason: SlackBuild scripts are designed, build and tested against a full slackware install, in which case vim would be present. I think it would be a rather sliding slope to start accounting for every possibility of someone not having a full Slackware install. This basically comes down to; yes, you can do a less than full install of your Slackware system, but that pretty much come with the caveat of "You should know that some funny[1] things can turn up". [1] ie stuff not building, other undesired side effects M. -- Michiel van Wessem http://slackbuilds.org/ -------------- 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 Fri Mar 15 14:18:07 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 15 Mar 2013 09:18:07 -0500 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <20130315140703.683f4316@hades.olympus.lan> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> Message-ID: <20130315091807.2dbadd62@home.rlworkman.net> On Fri, 15 Mar 2013 14:07:03 +0000 Michiel van Wessem wrote: > On Fri, 15 Mar 2013 13:06:59 +0100 > Dario Niedermann wrote: > > > the above is not specified, the build will require the Vim editor > > to be installed, or it will fail, which I don't think is reasonable. > > I can't speak for the other admins, but I am against it. The reason: > SlackBuild scripts are designed, build and tested against a full > slackware install, in which case vim would be present. I think it > would be a rather sliding slope to start accounting for every > possibility of someone not having a full Slackware install. That would be my take as well. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From info at microlinux.fr Fri Mar 15 16:06:29 2013 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 15 Mar 2013 17:06:29 +0100 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <20130315140703.683f4316@hades.olympus.lan> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> Message-ID: <51434705.6010604@microlinux.fr> Le 15/03/2013 15:07, Michiel van Wessem a ?crit : > This basically comes down to; yes, you can do a less than full install > of your Slackware system, but that pretty much come with the caveat of > "You should know that some funny[1] things can turn up". I'd understand if it was a dependency on Emacs or some other kitchen sink. But Vim, come on! It's not as if everything besides the kernel, the C library and the shell of your choice is bloat... :o) 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 nickblizzard1776 at gmail.com Fri Mar 15 12:07:37 2013 From: nickblizzard1776 at gmail.com (Nick Blizzard) Date: Fri, 15 Mar 2013 08:07:37 -0400 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> Message-ID: As vim is part of the stock Slackware... I fail to see the problem. On Mar 15, 2013 8:06 AM, "Dario Niedermann" wrote: > After building libfm-1.1.0, I would recommend adding the following > option to its SlackBuild's `configure` line: > > --disable-gtk-doc-html > > If the above is not specified, the build will require the Vim editor > to be installed, or it will fail, which I don't think is reasonable. > > Regards, > DN > _______________________________________________ > 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 dnied at tiscali.it Fri Mar 15 18:52:15 2013 From: dnied at tiscali.it (Dario Niedermann) Date: Fri, 15 Mar 2013 19:52:15 +0100 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51434705.6010604@microlinux.fr> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> Message-ID: <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> Niki Kovacs wrote: > I'd understand if it was a dependency on Emacs or some other kitchen > sink. But Vim, come on! It's not as if everything besides the kernel, > the C library and the shell of your choice is bloat... Not only Vim is an insanely bloated program, but it's not even Slackware's default vi-like editor (that would be Elvis). I think SBo should try to be useful to real-world Slackware users, not just the arguably small fraction that will install everything and the kitchen sink as though they were Ubuntu users. Especially when it's so easy to avoid an unreasonably bloated dependency like Vim. From francois.gingras at gmail.com Fri Mar 15 18:53:58 2013 From: francois.gingras at gmail.com (Frank Gingras) Date: Fri, 15 Mar 2013 14:53:58 -0400 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> Message-ID: <51436E46.1040804@gmail.com> On 3/15/2013 2:52 PM, Dario Niedermann wrote: > Niki Kovacs wrote: > >> I'd understand if it was a dependency on Emacs or some other kitchen >> sink. But Vim, come on! It's not as if everything besides the kernel, >> the C library and the shell of your choice is bloat... > Not only Vim is an insanely bloated program, but it's not even > Slackware's default vi-like editor (that would be Elvis). > > I think SBo should try to be useful to real-world Slackware users, > not just the arguably small fraction that will install everything > and the kitchen sink as though they were Ubuntu users. Especially when > it's so easy to avoid an unreasonably bloated dependency like Vim. > _______________________________________________ > 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/ > Come on. Vim is not "bloated", by any order of comparison. And most folks install nearly every package (minus the kde / kdei packages). F. From alan at lizella.net Fri Mar 15 19:18:57 2013 From: alan at lizella.net (Alan Hicks) Date: Fri, 15 Mar 2013 15:18:57 -0400 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> Message-ID: <20130315151857.182c0f55.alan@lizella.net> On Fri, 15 Mar 2013 19:52:15 +0100 Dario Niedermann wrote: > I think SBo should try to be useful to real-world Slackware users, I believe SBo has proven itself to be extremely useful to real-world Slackware users, but if you disagree you are more than welcome to start your own damned project and do it the way you think it should be done. -- It is better to hear the rebuke of the wise, Than for a man to hear the song of fools. Ecclesiastes 7:5 From dnied at tiscali.it Fri Mar 15 19:55:08 2013 From: dnied at tiscali.it (Dario Niedermann) Date: Fri, 15 Mar 2013 20:55:08 +0100 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <20130315151857.182c0f55.alan@lizella.net> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> <20130315151857.182c0f55.alan@lizella.net> Message-ID: <51437c9c.mKyJJPnVB9Z0pSUg%dnied@tiscali.it> Alan Hicks wrote: > I believe SBo has proven itself to be extremely useful to real-world > Slackware users, but if you disagree you are more than welcome to start > your own damned project and do it the way you think it should be done. Sorry to have hurt your frail ego, man. I'll avoid sending suggestions or constructive criticism in the future, lest you suffer again. Jeez. From matteo.bernardini at gmail.com Fri Mar 15 20:22:56 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 15 Mar 2013 21:22:56 +0100 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> Message-ID: 2013/3/15 Dario Niedermann > I think SBo should try to be useful to real-world Slackware users > This doesn't look like constructive criticism to me. I thought about adding a check to disable building docs if vim isn't present, but I changed my mind. Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Fri Mar 15 22:05:16 2013 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 15 Mar 2013 23:05:16 +0100 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> Message-ID: <51439B1C.9020704@microlinux.fr> Le 15/03/2013 19:52, Dario Niedermann a ?crit : > Not only Vim is an insanely bloated program, but it's not even > Slackware's default vi-like editor (that would be Elvis). > > I think SBo should try to be useful to real-world Slackware users, > not just the arguably small fraction that will install everything > and the kitchen sink as though they were Ubuntu users. Especially when > it's so easy to avoid an unreasonably bloated dependency like Vim. Real men need nothing more than aaa_base, yeah :o) -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Fri Mar 15 22:21:39 2013 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 15 Mar 2013 23:21:39 +0100 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51437c9c.mKyJJPnVB9Z0pSUg%dnied@tiscali.it> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> <20130315151857.182c0f55.alan@lizella.net> <51437c9c.mKyJJPnVB9Z0pSUg%dnied@tiscali.it> Message-ID: <51439EF3.8010502@microlinux.fr> Le 15/03/2013 20:55, Dario Niedermann a ?crit : > Sorry to have hurt your frail ego, man. I'll avoid sending suggestions > or constructive criticism in the future, lest you suffer again. > > Jeez. I try to imagine what kind of person considers a 5 MB package like Vim as "insane bloat". Probably the same kind of person who farts into his car tyres to inflate them. Careful not to spoil that hot air. Cheez :o) -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From michiel at slackbuilds.org Fri Mar 15 23:00:39 2013 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Fri, 15 Mar 2013 23:00:39 +0000 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51439B1C.9020704@microlinux.fr> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> <51439B1C.9020704@microlinux.fr> Message-ID: <20130315230039.446f8ce9@hades.olympus.lan> On Fri, 15 Mar 2013 23:05:16 +0100 Niki Kovacs wrote: > Real men need nothing more than aaa_base, yeah :o) > and obviously bzcat > /boot/vmlinux ;) -- Michiel van Wessem http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From andrew at andrews-corner.org Fri Mar 15 22:45:19 2013 From: andrew at andrews-corner.org (andrew) Date: Sat, 16 Mar 2013 09:45:19 +1100 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51439EF3.8010502@microlinux.fr> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> <20130315151857.182c0f55.alan@lizella.net> <51437c9c.mKyJJPnVB9Z0pSUg%dnied@tiscali.it> <51439EF3.8010502@microlinux.fr> Message-ID: <20130315224519.GA5448@skamandros.andrews-corner.org> On Fri, Mar 15, 2013 at 11:21:39PM +0100, Niki Kovacs wrote: > I try to imagine what kind of person considers a 5 MB package like > Vim as "insane bloat". Probably the same kind of person who farts > into his car tyres to inflate them. Careful not to spoil that hot > air. Still trying to lose that mental image :) Andrew -- You think that's air you're breathing now? From openpandora at free.fr Fri Mar 15 23:28:57 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sat, 16 Mar 2013 00:28:57 +0100 Subject: [Slackbuilds-users] Ardour 3 is out, cwiid.pc required, more deps Message-ID: <1363390137.5143aeb907dc3@imp.free.fr> Hi ! cwiid needs to be patched to generate a .pc . I made one totally dirty myself: prefix=/usr exec_prefix=${prefix} libdir=/usr/lib64 includedir=${prefix}/include sysconfdir=/etc cwiid_config_dir=${sysconfdir}/cwiid cwiid_plugins_dir=${prefix}/lib64/cwiid/plugins Name: CWiid Description: CWiid Wiimote Interface Version: 0.6.00 Requires: bluez Libs: -L${libdir} -lcwiid Cflags: -I${includedir} New deps: serd sord sratom lilv From info at microlinux.fr Sat Mar 16 06:00:08 2013 From: info at microlinux.fr (Niki Kovacs) Date: Sat, 16 Mar 2013 07:00:08 +0100 Subject: [Slackbuilds-users] Openshot, mlt and frei0r Message-ID: <51440A68.9080205@microlinux.fr> Hi, Some time ago, I installed Openshot from SBo and couldn't manage to get it to work correctly, even though all listed dependencies were installed. After some experimentation, I found out the culprit: 'frei0r' must be installed *before* 'mlt', so it can be taken into account. Otherwise Openshot will keep complaining about "missing frei0r plugins'. Suggestion: maybe insert a short notice about the correct build order for Openshot dependencies on the corresponding page? BTW, now Openshot works nice. Thanks to Matteo Bernardini for the build! 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 matteo.bernardini at gmail.com Sat Mar 16 06:23:17 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 16 Mar 2013 07:23:17 +0100 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: <51440A68.9080205@microlinux.fr> References: <51440A68.9080205@microlinux.fr> Message-ID: I was thinking that maybe a cleaner alternative solution could be to add frei0r in the REQUIRES of mlt.info, if it's ok for the maintainer. Matteo P.S. Here I also version-bumped mlt to 0.8.8. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hba.nihilismus at gmail.com Sat Mar 16 06:42:35 2013 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sat, 16 Mar 2013 00:42:35 -0600 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: <51440A68.9080205@microlinux.fr> References: <51440A68.9080205@microlinux.fr> Message-ID: On Sat, Mar 16, 2013 at 12:00 AM, Niki Kovacs wrote: > Hi, > > Some time ago, I installed Openshot from SBo and couldn't manage to get it > to work correctly, even though all listed dependencies were installed. After > some experimentation, I found out the culprit: 'frei0r' must be installed > *before* 'mlt', so it can be taken into account. Otherwise Openshot will > keep complaining about "missing frei0r plugins'. > > Suggestion: maybe insert a short notice about the correct build order for > Openshot dependencies on the corresponding page? > > BTW, now Openshot works nice. Thanks to Matteo Bernardini for the build! > > Cheers, > > Niki > -- > Microlinux - Solutions informatiques 100% Linux et logiciels libres > 7, place de l'?glise - 30730 Montpezat > Web : http://www.microlinux.fr > Mail : info at microlinux.fr > T?l. : 04 66 63 10 32 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > The variable REQUIRES (in openshot.info) has "frei0r mlt pygoocanvas pyxdg" as value so it is indicating the correct build order ;) -- - Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster From bocke at mycity.rs Sat Mar 16 08:17:20 2013 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 16 Mar 2013 09:17:20 +0100 Subject: [Slackbuilds-users] libfm requires the Vim editor! In-Reply-To: <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> References: <51430ee3.CFe7+tZNjf8vjsQh%dnied@tiscali.it> <20130315140703.683f4316@hades.olympus.lan> <51434705.6010604@microlinux.fr> <51436ddf.lfXvU5VkdmK6XQo4%dnied@tiscali.it> Message-ID: <20130316091720.08092716@deathstar.universe.org> Yeah, real man use ed. :)) On a serious note, Vim is far from bloat in today's standards. Anyway, nothing stops you from doing a custom build with a customized runtime bundle that contains only the stuff you need. Bojan. P.S. If you call Vim bloated, what would you call emacs? :) On Fri, 15 Mar 2013 19:52:15 +0100 Dario Niedermann wrote: > Not only Vim is an insanely bloated program, but it's not even > Slackware's default vi-like editor (that would be Elvis). From c.willing at uq.edu.au Sat Mar 16 09:13:16 2013 From: c.willing at uq.edu.au (Christoph Willing) Date: Sat, 16 Mar 2013 19:13:16 +1000 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: References: <51440A68.9080205@microlinux.fr> Message-ID: On 16/03/2013, at 4:42 PM, Antonio Hern?ndez Blas wrote: [snip] > > The variable REQUIRES (in openshot.info) has "frei0r mlt pygoocanvas > pyxdg" as value so it is indicating the correct build order ;) The $PRGNAM.info specification does not stipulate that entries in the REQUIRED field should be in build order and I'm happy with that. If frei0r is already required for mlt, then the inclusion of frei0r in openshot.info is incorrect since it is not a first order requirement; it will be included in the build sequence because its already a requirement for mlt. I don't care myself - superfluous information does no particular harm - but so say the guidelines. chris From info at microlinux.fr Sat Mar 16 09:38:03 2013 From: info at microlinux.fr (Niki Kovacs) Date: Sat, 16 Mar 2013 10:38:03 +0100 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: References: <51440A68.9080205@microlinux.fr> Message-ID: <51443D7B.6020607@microlinux.fr> Le 16/03/2013 10:13, Christoph Willing a ?crit : > If frei0r is already required for mlt, then the inclusion of frei0r in openshot.info is incorrect The thing is: it's not. The 'mlt' package will build just fine without frei0r (and just note the absence of frei0r in the ./configure process). On the other hand, Openshot won't work correctly. Hence my initial post. 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 matteo.bernardini at gmail.com Sat Mar 16 09:43:31 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 16 Mar 2013 10:43:31 +0100 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: <51443D7B.6020607@microlinux.fr> References: <51440A68.9080205@microlinux.fr> <51443D7B.6020607@microlinux.fr> Message-ID: If stormstracknole prefer to keep things as they are, I can add a note like this to the README NOTE: to use frei0r plugins in openshot, it's mandatory to build mlt with frei0r already installed. But I think mlt can benefit from default frei0r support, so I still like the other solution more :) Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Sat Mar 16 10:11:06 2013 From: info at microlinux.fr (Niki Kovacs) Date: Sat, 16 Mar 2013 11:11:06 +0100 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: References: <51440A68.9080205@microlinux.fr> <51443D7B.6020607@microlinux.fr> Message-ID: <5144453A.10102@microlinux.fr> Le 16/03/2013 10:43, Matteo Bernardini a ?crit : > But I think mlt can benefit from default frei0r support, so I still like > the other solution more :) Not only does it benefit from mlt support. It also sends annoying error messages on startup that can't be disabled. -- 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 yalhcru at gmail.com Sat Mar 16 18:34:58 2013 From: yalhcru at gmail.com (B Watson) Date: Sat, 16 Mar 2013 14:34:58 -0400 Subject: [Slackbuilds-users] Ardour 3 is out, cwiid.pc required, more deps In-Reply-To: <1363390137.5143aeb907dc3@imp.free.fr> References: <1363390137.5143aeb907dc3@imp.free.fr> Message-ID: On 3/15/13, openpandora at free.fr wrote: > cwiid needs to be patched to generate a .pc . I made one totally dirty > myself: The cwiid developers haven't done a release that includes a .pc file. If Ardour3 needs cwiid.pc, then it depends on an unstable (SVN) version of cwiid. I can update the cwiid package to build the same version as Debian/Ubuntu uses, which they call "0.6.00+svn201-2+b2". Presumably it works OK with Ardour or else the Ardour folks wouldn't be using it (AFAIK their primary development platform is Ubuntu). Out of curiosity, are you actually going to use a Wiimote to control Ardour, or are you just trying to build Ardour3 with all the optional deps enabled? > New deps: > > serd > sord > sratom > lilv This is going to open a can of worms. serd/sord/lilv are the new LV2 stack, which replaces lv2core and slv2. Back when I first looked at these, I found that the old and new lv2 stacks couldn't easily coexist on the same system... and everything on SBo that uses LV2 currently depends on the old stack. So we've got 2 options: 1. Figure out a way for lv2core/slv2 to coexist with lilv/serd/sord. This could be done by using different --libdir and such (the way fltk and fltk13 do), but AFAIK it will mean that your actual LV2 plugins will have to be built twice if you want them available for apps using either stack. 2. Ditch the old stack. Every app on SBo that uses LV2 will have to be updated to use the new stack, assuming it even can use it (most can). I'd vote for this solution, but it'll require coordinated effort between many people, some of whom probably won't have the time/energy/desire to update their already-working builds. The absolute worst "solution" would be for someone to just blindly submit builds for serd/sord/lilv. We'd end up with mutually-incompatible sets of builds, and LV2 plugins that only work in certain apps, and maybe apps that crash (old-style LV2 stack, trying to load plugins built for the new). I should have some time this week to look at this. It might be that option 1 will work better than I expect, or maybe I'll find a 3rd solution that works well. What does the list think? From pprkut at liwjatan.at Sat Mar 16 19:25:57 2013 From: pprkut at liwjatan.at (Heinz Wiesinger) Date: Sat, 16 Mar 2013 20:25:57 +0100 Subject: [Slackbuilds-users] Ardour 3 is out, cwiid.pc required, more deps In-Reply-To: References: <1363390137.5143aeb907dc3@imp.free.fr> Message-ID: <6216863.4xTPsobzHc@callisto> On Saturday 16 March 2013 14:34:58 B Watson wrote: > On 3/15/13, openpandora at free.fr wrote: > > cwiid needs to be patched to generate a .pc . I made one totally dirty > > > myself: > The cwiid developers haven't done a release that includes a .pc file. If > Ardour3 needs cwiid.pc, then it depends on an unstable (SVN) version > of cwiid. > > I can update the cwiid package to build the same version as Debian/Ubuntu > uses, which they call "0.6.00+svn201-2+b2". Presumably it works OK with > Ardour or else the Ardour folks wouldn't be using it (AFAIK their primary > development platform is Ubuntu). > > Out of curiosity, are you actually going to use a Wiimote to control > Ardour, or are you just trying to build Ardour3 with all the optional > deps enabled? This is obviously a choice that's up to the cwiid maintainer, but IMHO there's no reason for us to /have to/ update the build to include the .pc file. If it doesn't work with what we currently have in the repo I would probably just drop the support for it from the ardour build. > > New deps: > > > > serd > > sord > > sratom > > lilv > > This is going to open a can of worms. serd/sord/lilv are the new LV2 > stack, which replaces lv2core and slv2. Back when I first looked at these, > I found that the old and new lv2 stacks couldn't easily coexist on the > same system... and everything on SBo that uses LV2 currently depends on > the old stack. Ardour2 already needs those and they are already on SBo. If there is a conflict between slv2 and lilv I didn't see it and it needs to be dealt with. > So we've got 2 options: > > 1. Figure out a way for lv2core/slv2 to coexist with lilv/serd/sord. This > could be done by using different --libdir and such (the way fltk and > fltk13 do), but AFAIK it will mean that your actual LV2 plugins will have > to be built twice if you want them available for apps using either stack. I don't see how that is the case. lilv still needs lv2. The plugins end up in the same place. Why would you have to build them twice? > 2. Ditch the old stack. Every app on SBo that uses LV2 will have to be > updated to use the new stack, assuming it even can use it (most can). I'd > vote for this solution, but it'll require coordinated effort between > many people, some of whom probably won't have the time/energy/desire to > update their already-working builds. calf, foo-yc20, swh-plugins-lv2, zynjacku are the only SlackBuilds in the repo depending on slv2. Nothing depends on lilv yet (Not counting optional dependencies) > The absolute worst "solution" would be for someone to just blindly submit > builds for serd/sord/lilv. We'd end up with mutually-incompatible sets > of builds, and LV2 plugins that only work in certain apps, and maybe > apps that crash (old-style LV2 stack, trying to load plugins built for > the new). Well, considering that should be the case since the 14.0 repo went live and I haven't seen a single mail about either on the ML or to me directly I doubt it's a big issue. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 230 bytes Desc: This is a digitally signed message part. URL: From openpandora at free.fr Sat Mar 16 20:47:15 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sat, 16 Mar 2013 21:47:15 +0100 Subject: [Slackbuilds-users] Ardour 3 is out, cwiid.pc required, more deps In-Reply-To: References: <1363390137.5143aeb907dc3@imp.free.fr> Message-ID: <1363466835.5144da53de300@imp.free.fr> I wasn't able to disable cwiid support. Ardour3 uses waf to build, and had no explicit option about wiimote support. Quoting B Watson : > Out of curiosity, are you actually going to use a Wiimote to control > Ardour, or are you just trying to build Ardour3 with all the optional > deps enabled? From yalhcru at gmail.com Sat Mar 16 19:46:08 2013 From: yalhcru at gmail.com (B Watson) Date: Sat, 16 Mar 2013 15:46:08 -0400 Subject: [Slackbuilds-users] Ardour 3 is out, cwiid.pc required, more deps In-Reply-To: <6216863.4xTPsobzHc@callisto> References: <1363390137.5143aeb907dc3@imp.free.fr> <6216863.4xTPsobzHc@callisto> Message-ID: On 3/16/13, Heinz Wiesinger wrote: > On Saturday 16 March 2013 14:34:58 B Watson wrote: >> I can update the cwiid package to build the same version as Debian/Ubuntu > > This is obviously a choice that's up to the cwiid maintainer, but IMHO > there's > no reason for us to /have to/ update the build to include the .pc file. I'm the cwiid maintainer... probably will update the build to include the .pc because that seems to be "the way of the future". > Ardour2 already needs those and they are already on SBo. If there is a > conflict > between slv2 and lilv I didn't see it and it needs to be dealt with. Hm. Maybe I spoke prematurely. > I don't see how that is the case. lilv still needs lv2. The plugins end up in > the same place. Why would you have to build them twice? API changes. I'm under the impression that plugins built against lilv won't be backwards-compatible with apps using lv2. But that's based on stuff I looked at last year and can't remember details of now, so I might be wrong. > Well, considering that should be the case since the 14.0 repo went live and I > haven't seen a single mail about either on the ML or to me directly I doubt > it's a big issue. Hm. Now I think maybe I'm just paranoid. Still want to do some testing, and dig up my old notes, see whether my half-remembered issue is for real or not. From hba.nihilismus at gmail.com Sat Mar 16 23:22:14 2013 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sat, 16 Mar 2013 17:22:14 -0600 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: References: <51440A68.9080205@microlinux.fr> Message-ID: On Sat, Mar 16, 2013 at 3:13 AM, Christoph Willing wrote: > The $PRGNAM.info specification does not stipulate that entries in the REQUIRED field should be in build order and I'm happy with that. Yeah, based on xgizzmo's words [1] it is left up to the maintainer... so we are left with inconsistency. [1] http://lists.slackbuilds.org/pipermail/slackbuilds-users/2012-September/009242.html -- - Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster From info at microlinux.fr Sun Mar 17 06:27:18 2013 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 17 Mar 2013 07:27:18 +0100 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: References: <51440A68.9080205@microlinux.fr> Message-ID: <51456246.6070100@microlinux.fr> Le 17/03/2013 00:22, Antonio Hern?ndez Blas a ?crit : > Yeah, based on xgizzmo's words [1] it is left up to the maintainer... > so we are left with inconsistency. I suggest to apply the KISS principle and to simply add something like this to the README: http://slackbuilds.org/repository/14.0/desktop/ccsm/ 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 hba.nihilismus at gmail.com Sun Mar 17 15:52:20 2013 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sun, 17 Mar 2013 09:52:20 -0600 Subject: [Slackbuilds-users] Openshot, mlt and frei0r In-Reply-To: <51456246.6070100@microlinux.fr> References: <51440A68.9080205@microlinux.fr> <51456246.6070100@microlinux.fr> Message-ID: On Sun, Mar 17, 2013 at 12:27 AM, Niki Kovacs wrote: > I suggest to apply the KISS principle and to simply add something like this > to the README: > > http://slackbuilds.org/repository/14.0/desktop/ccsm/ Yeah, another good one is http://slackbuilds.org/repository/14.0/desktop/enlightenment/ :) -- - Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster From openpandora at free.fr Tue Mar 19 21:00:05 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 19 Mar 2013 22:00:05 +0100 Subject: [Slackbuilds-users] Ardour 3 is out, cwiid.pc required, more deps In-Reply-To: <1363390137.5143aeb907dc3@imp.free.fr> References: <1363390137.5143aeb907dc3@imp.free.fr> Message-ID: <1363726805.5148d1d5f0ac5@imp.free.fr> Oh, also please keep ardour2 in SBo, i'm sure i'm not the only one to have A2 projects, and A3 doesn't open them properly. The two versions can live together. LS. From lipkab at zoho.com Wed Mar 20 08:26:57 2013 From: lipkab at zoho.com (lipkab) Date: Wed, 20 Mar 2013 01:26:57 -0700 Subject: [Slackbuilds-users] Some questions Message-ID: <13d86e88222.1811855674161453429.-5795131210365982897@zoho.com> Hello all, I've wrote a few SlackBuilds and would be interested to submit them to SBo. I have some questions though: One of my scripts uses third party patches. How should I include those? Where should I indicate their source and put their legal notice? Second, would the Steam client be allowed on your site? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From c at charlesmatkinson.org Thu Mar 21 10:08:52 2013 From: c at charlesmatkinson.org (Charles) Date: Thu, 21 Mar 2013 15:38:52 +0530 Subject: [Slackbuilds-users] spideroak SlackBuild is obsolete Message-ID: <514ADC34.7020801@charlesmatkinson.org> The spideroak SlackBuild (which creates a Slackware package from Spideroak's .deb) is now obsolete. According to the file names shown when downloading from https://spideroak.com/opendownload, Spideroak's "Slackware Based" packages now have the same version numbers as their "Debian Based" packages. The spideroak SlackBuild maintainer has not replied to emails about it using a superseded .deb download so I have not told them about this news. Best, Charles From xgizzmo at slackbuilds.org Fri Mar 22 11:59:32 2013 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Fri, 22 Mar 2013 07:59:32 -0400 Subject: [Slackbuilds-users] Updates - 20130322.1 Message-ID: <201303220759.32586.xgizzmo@slackbuilds.org> Fri Mar 22 11:23:26 UTC 2013 academic/ImageJ: Updated for version 1.46. academic/PhyML: Updated for version 20130219. academic/R: Updated for version 2.15.3. academic/aris: Added (sequential proof program) academic/ij-plugins-LOCI: Added (Plugins for ImageJ) academic/ij-plugins-UCSD: Added (Plugins for ImageJ) academic/primer3: Updated for version 2.3.5. academic/ucsc-blat: Added (The BLAST-Like Alignment Tool) audio/id3tool: Added (utility for manipulation ID3 tags) audio/libbs2b: Added (improve headphone listening of stereo audio) audio/mac: Homepage is dead, DL link updated. audio/mktoc: Updated for version 1.3. audio/muse: Fixed doinst.sh for real this time audio/vamp-plugin-sdk: Updated for version 2.4. desktop/crystal: Updated for version 2.1.1. desktop/e16: Fixed version string in .info file desktop/slack-wallpapers: Updated for version 0.168. desktop/xdgmenumaker: Added (generates application menus) development/astyle: Added (Artistic Style code beautifier) development/bakefile: Updated for version 0.2.9. development/geany-plugins: Updated for version 1.23. development/geany: Updated for version 1.23. development/ht: Updated for version 2.0.21. development/kdiff3: Updated for version 0.9.97. games/gemrb: Added (Infinity engine open-source implementation) games/gnugo: Added (free version of the game of Go) games/mfe: Updated for version 0.1.7. games/singularity: Added (Alternative client for SecondLife) graphics/fbida: Updated for version 2.09. libraries/SDL_gfx: Updated for version 2.0.24. libraries/compface: Added (48x48x1 image (de)compression) libraries/libaacs: Updated for version 0.6.0. libraries/libcec: Updated for version 2.1.1. libraries/libewf: Updated for version 20130303. libraries/libotr: Updated for version 4.0.0. libraries/muParser: Updated for version 2.2.3. libraries/yaz: Updated for version 4.2.51. misc/portecle: Added (Simple interface to a keystore) misc/toilet: Added (program for creating banners) multimedia/TeamSpeak3: Added (Voice Communication) multimedia/flash-player-plugin: Updated for version 11.2.202.275. multimedia/gaupol: Updated for version 0.19.2. multimedia/gtkpod: Patched to fix showing tracks on 64 bit. multimedia/radiotray: Fixed dep information network/ClusterSSH: Added (run multiple ssh clients in paralell) network/RSSOwl: Updated for version 2.1.6. network/asterisk: Updated for version 1.8.20.1. network/bitlbee: Updated for version 3.2. network/deluge: Fixed dep information network/dwb: Updated for version 2012.12.03. network/httrack: Added (offline web browser) network/mitter: Fixed download link network/pidgin-otr: Updated for version 4.0.0. network/smb4k: Updated for version 1.0.6. network/vacuum-im: Updated for version 1.2.2. network/wireshark: Updated for version 1.8.6. office/ProjectLibre: Updated for version 1.5.4. office/briss: Added (The BRIght Snippet Sire) office/calcurse: Updated for version 3.1.4. office/evince: Updated for version 3.4.0. office/gocr: Updated for version 0.50. office/texmaker: Updated for version 4.0. perl/perl-Algorithm-Diff: Added (diff between two files / lists) perl/perl-Class-Data-Inheritable: Added (Inheritable class data) perl/perl-Data-Dump: Added (Pretty printing of data structures) perl/perl-Devel-StackTrace: Added (represent a stack trace) perl/perl-Exception-Class: Added (declare real exception classes) perl/perl-HTTP-Proxy: Updated for version 0.27. perl/perl-Module-Manifest: Added (Parse distribution MANIFEST file) perl/perl-Readonly: Added (create non-modifiable variable) perl/perl-Test-Differences: Added (Test string differences) perl/perl-Test-DistManifest: Added (validates a package MANIFEST) perl/perl-Test-Trap: Added (Trap exit codes, exceptions, etc) perl/perl-Text-Diff: Added (Perform diffs on files and record sets) python/RBTools: Added (utility scripts for use with Review Board) python/euca2ools: Added (Amazon & OpenStack Command Line Tools) python/feedparser: Moved from network fixed homepage. python/simplejson: Updated for version 3.1.0. system/audit: Updated for version 2.2.2. system/clamtk: Updated for version 4.44. system/dar: Updated for version 2.4.10. system/ksh-openbsd: Updated for version 20130311. system/lzip: Updated for version 1.14. system/makeself: Added (Make self-extractable archives on Unix) system/netperf: Added (benchmarking for various types of networking) system/nickle: Added (programming language) system/rxvt-unicode: Updated for version 9.17. system/sleuthkit: Updated for version 4.0.2. system/udftools: Added (udf userspace utilites) +--------------------------+ From openpandora at free.fr Fri Mar 22 23:39:10 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sat, 23 Mar 2013 00:39:10 +0100 (CET) Subject: [Slackbuilds-users] SDL_gfx not ARM-friendly In-Reply-To: <937394871.5035460.1363995535662.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1627212564.5035653.1363995550885.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! elif [ "$ARCH" = "arm" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="" MIX=${MIX:-"dis"} is missing LS From lukenshiro at ngi.it Sat Mar 23 16:12:05 2013 From: lukenshiro at ngi.it (LukenShiro) Date: Sat, 23 Mar 2013 17:12:05 +0100 Subject: [Slackbuilds-users] netperf's and nickle's categorization Message-ID: <20130323171205.42d9797e@hamalayi.mnt> Hi all, I'd say these two scripts should be moved to a more appropriate category: 1) nickle is a programming language, so "development" directory seems more suitable; 2) netperf is a network tool, so it seems more pertinent to "network" directory. TIA. Regards. -- GNU/Linux * Slackware64 current LU #210970 SU #12583 LM #98222/#412913 From gmane at csrc.com Mon Mar 25 05:51:07 2013 From: gmane at csrc.com (joe) Date: Mon, 25 Mar 2013 05:51:07 +0000 (UTC) Subject: [Slackbuilds-users] feh References: Message-ID: Jorge Almeida writes: > > Compiling feh-2.3 on Slackware 14.0 is failing. The two libraries > mentioned as prerequisites are installed. > > imlib2-1.4.5-i686-1_SBo > giblib-1.2.4-i686-2_SBo > > TIA > > Jorge Almeida > > make[1]: Entering directory `/slash/var/slack/slackbuild/tmp/feh-2.3/src' > sed 's/^\(.*\)$/"\1\\n"/' < help.raw > help.inc > cc -MM collage.c events.c exif.c feh_png.c filelist.c getopt.c > getopt1.c imlib.c index.c keyevents.c list.c main.c md5.c menu.c > multiwindow.c options.c signals.c slideshow.c thumbnail.c timers.c > utils.c wallpaper.c winwidget.c > deps.mk > make[1]: Leaving directory `/slash/var/slack/slackbuild/tmp/feh-2.3/src' > make[1]: Entering directory `/slash/var/slack/slackbuild/tmp/feh-2.3/src' > cc -O2 -march=native -c -o collage.o collage.c > collage.c: In function 'init_collage_mode': > collage.c:68:11: error: 'PACKAGE' undeclared (first use in this function) > collage.c:68:11: note: each undeclared identifier is reported only > once for each function it appears in > collage.c:69:6: error: expected ')' before string constant > collage.c:72:6: error: too few arguments to function 'fputs' > collage.c:78:6: error: expected ')' before string constant > collage.c:81:6: error: too few arguments to function 'fputs' > collage.c:111:7: error: expected ')' before string constant > collage.c:202:28: error: expected ')' before string constant > make[1]: *** [collage.o] Error 1 > The feh build is not inheriting the slackbuild CFLAGS well. This will work around that: --- feh.SlackBuild.ori 2013-03-24 23:22:00.641550918 -0600 +++ feh.SlackBuild 2013-03-24 23:39:26.123480592 -0600 @@ -71,8 +71,8 @@ -exec chmod 644 {} \; make \ - CFLAGS="$SLKCFLAGS" \ - PREFIX=/usr + CFLAGS="-g $SLKCFLAGS -Wall -Wextra -pedantic -DPREFIX=\\\"/usr\\\" -DHAVE_LIBCURL -DHAVE_LIBXINERAMA -DPACKAGE=\\\"$PRGNAME\\\" -DVERSION=\\\"$VERSION\\\"" + make install \ DESTDIR=$PKG \ PREFIX=/usr \ From jjalmeida at gmail.com Mon Mar 25 16:55:53 2013 From: jjalmeida at gmail.com (Jorge Almeida) Date: Mon, 25 Mar 2013 16:55:53 +0000 Subject: [Slackbuilds-users] feh In-Reply-To: References: Message-ID: On Mon, Mar 25, 2013 at 5:51 AM, joe wrote: > Jorge Almeida writes: > >> > > The feh build is not inheriting the slackbuild CFLAGS well. This will work > around that: > > --- feh.SlackBuild.ori 2013-03-24 23:22:00.641550918 -0600 > +++ feh.SlackBuild 2013-03-24 23:39:26.123480592 -0600 > @@ -71,8 +71,8 @@ > -exec chmod 644 {} \; > > make \ > - CFLAGS="$SLKCFLAGS" \ > - PREFIX=/usr > + CFLAGS="-g $SLKCFLAGS -Wall -Wextra -pedantic -DPREFIX=\\\"/usr\\\" > -DHAVE_LIBCURL -DHAVE_LIBXINERAMA -DPACKAGE=\\\"$PRGNAME\\\" > -DVERSION=\\\"$VERSION\\\"" > + > make install \ > DESTDIR=$PKG \ > PREFIX=/usr \ > Thanks. Anyway, I noticed the slackbuild is for an old version. The current version of feh compiled fine, following the upstream instructions. Jorge Almeida From yalhcru at gmail.com Mon Mar 25 18:56:46 2013 From: yalhcru at gmail.com (B Watson) Date: Mon, 25 Mar 2013 14:56:46 -0400 Subject: [Slackbuilds-users] feh In-Reply-To: References: Message-ID: On 3/25/13, joe wrote: > + CFLAGS="-g $SLKCFLAGS -Wall -Wextra -pedantic -DPREFIX=\\\"/usr\\\" > -DHAVE_LIBCURL -DHAVE_LIBXINERAMA -DPACKAGE=\\\"$PRGNAME\\\" > -DVERSION=\\\"$VERSION\\\"" It probably would make more sense (and be less brittle) for things like that to use a bit of sed: sed -i "/CFLAGS=/s,-g,$SLKCFLAGS" Makefile (Untested, I haven't looked at the feh source, just an example) From Hullen at t-online.de Wed Mar 27 09:31:00 2013 From: Hullen at t-online.de (Helmut Hullen) Date: 27 Mar 2013 10:31:00 +0100 Subject: [Slackbuilds-users] clamav Message-ID: Hallo, slackbuilds-users, the clamav packet seems to have some errors: "/etc/logrotate.d/clamav" overwrites an older file, it has to be named "clamav.new" in the build script. "/etc/logrotate.d/clamav-milter" seems to have vanished, even in the "*.new" version The "doinst.sh" script must "config" the two above mentioned files too. The actual script "/etc/logrotate.d/clamav" produces some strange errors, perhaps invoked by the "su ..." line. I use an older script without the su ... create ... /bin/kill ... freshclam ... lines - it works without problems. Viele Gruesse! Helmut From matteo.bernardini at gmail.com Wed Mar 27 10:14:53 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 27 Mar 2013 11:14:53 +0100 Subject: [Slackbuilds-users] clamav In-Reply-To: References: Message-ID: 2013/3/27 Helmut Hullen > Hallo, slackbuilds-users, > > the clamav packet seems to have some errors: > > "/etc/logrotate.d/clamav" overwrites an older file, it has to be named > "clamav.new" in the build script. > I agree. > "/etc/logrotate.d/clamav-milter" seems to have vanished, even in the > "*.new" version > Looks like there never has been such file in the clamav submitted to SBo. > The "doinst.sh" script must "config" the two above mentioned files too. > Yes, obviously as a consequence of installing the logrotate stuff as .new. > The actual script "/etc/logrotate.d/clamav" produces some strange > errors, perhaps invoked by the "su ..." line. > I use an older script without the > > su ... > create ... > /bin/kill ... freshclam ... > the su option is necessary for the new logrotate: which version of slackware are you using? can you please post the related errors? Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.willing at uq.edu.au Thu Mar 28 02:36:28 2013 From: c.willing at uq.edu.au (Christoph Willing) Date: Thu, 28 Mar 2013 12:36:28 +1000 Subject: [Slackbuilds-users] qemu: New Maintainer - suggestion In-Reply-To: <512BE6B6.5050509@gmail.com> References: <512BE6B6.5050509@gmail.com> Message-ID: <1460AD2A-8DEB-4336-9834-070E85273F06@uq.edu.au> On 26/02/2013, at 8:33 AM, 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. I see there is a qemu.tar.gz in the pending queue - I guess thats the 1.4.0 version. In the meantime, I just recently used the SlackBuild from Matteo's git repo. I hoped that the latest version would fix a problem I was having with host to guest pass through for USB memory sticks. Well, the new version didn't solve the problem by itself but after a full working day of googling and trying various command line options, I finally found clear instructions (that worked) in the docs directory of the source code. For some reason it had been overlooked for inclusion with the final build, hence nothing in /usr/docs/qemu-1.4.0. Looking back now, I see docs/* were included in qemu-kvm-1.2.0 but not in qemu-1.2.0; if the new qemu-1.4.0 SlackBuild is based on the qemu-1.2.0 version then it too might not have the missing docs. Anyway my suggestion/request is that qemu's docs/* be included in the final build of the new qemu SlackBuild - those documents may save someone else a lot of troubleshooting time. chris From kerickson at lavabit.com Thu Mar 28 01:01:43 2013 From: kerickson at lavabit.com (kerickson at lavabit.com) Date: Wed, 27 Mar 2013 21:01:43 -0400 (EDT) Subject: [Slackbuilds-users] reiser4progs files need to be updated Message-ID: <6971.71.19.213.15.1364432503.squirrel@lavabit.com> reiser4progs.info needs libaal added to the REQUIRES section, the README needs to mention that reiser4progs depends upon libaal, and the slack-desc and README both need to be changed so they don't claim that reiser4progs includes libaal. These changes need to be made because the original SlackBuild I uploaded was for a package that included libaal. This was later split into two packages, but the reiser4progs files I mentioned above never got updated to reflect the split. I am the maintainer of reiser4progs and libaal. I am sending this from my new email address. Thanks. From rworkman at slackbuilds.org Thu Mar 28 05:18:24 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 28 Mar 2013 00:18:24 -0500 Subject: [Slackbuilds-users] reiser4progs files need to be updated In-Reply-To: <6971.71.19.213.15.1364432503.squirrel@lavabit.com> References: <6971.71.19.213.15.1364432503.squirrel@lavabit.com> Message-ID: <20130328001824.2719605d@home.rlworkman.net> On Wed, 27 Mar 2013 21:01:43 -0400 (EDT) kerickson at lavabit.com wrote: > reiser4progs.info needs libaal added to the REQUIRES section, the > README needs to mention that reiser4progs depends upon libaal, and > the slack-desc and README both need to be changed so they don't claim > that reiser4progs includes libaal. > > These changes need to be made because the original SlackBuild I > uploaded was for a package that included libaal. This was later split > into two packages, but the reiser4progs files I mentioned above never > got updated to reflect the split. > > I am the maintainer of reiser4progs and libaal. I am sending this > from my new email address. All fixed - thanks for the note. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From Hullen at t-online.de Thu Mar 28 08:07:00 2013 From: Hullen at t-online.de (Helmut Hullen) Date: 28 Mar 2013 09:07:00 +0100 Subject: [Slackbuilds-users] clamav In-Reply-To: Message-ID: Hallo, Matteo, Du meintest am 27.03.13: >> the clamav packet seems to have some errors: [...] >> "/etc/logrotate.d/clamav-milter" seems to have vanished, even in the >> "*.new" version >> > Looks like there never has been such file in the clamav submitted to > SBo. Yes - may be. That script has a time stamp from 2006, and these 7 years ago I didn't use the SBo clamav packet. [...] >> The actual script "/etc/logrotate.d/clamav" produces some strange >> errors, perhaps invoked by the "su ..." line. >> I use an older script without the >> >> su ... >> create ... >> /bin/kill ... freshclam ... >> > the su option is necessary for the new logrotate: which version of > slackware are you using? The error happens with 3.7.8 and 3.8.2 Slackware: self made, based on current. > can you please post the related errors? --------------------------------- [...] /etc/cron.daily/logrotate: mv: target `founderrorin/var/log/clamav/*.log,skipping.new' is not a directory error: clamav:2 unexpected log filename error: found error in /var/log/clamav/*.log , skipping --------------------------------- That error seems to happen with logrotate 3.7.8 and 3.8.2 (found on several installations). Typical: the nonexistent spaces in the "mv" line. It only happens with the "/etc/logrotate.d/clamav" script, with no other script. Viele Gruesse! Helmut From matteo.bernardini at gmail.com Thu Mar 28 08:29:24 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 28 Mar 2013 09:29:24 +0100 Subject: [Slackbuilds-users] clamav In-Reply-To: References: Message-ID: remember that SBo scripts are supported only for full installs of the latest slackware stable, in this case 14.0: any other configuration is unsupported. said that, maybe I'm missing something, but I tried on my slackware64-current to run cron.daily manually and I got no such error. Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hullen at t-online.de Thu Mar 28 09:34:00 2013 From: Hullen at t-online.de (Helmut Hullen) Date: 28 Mar 2013 10:34:00 +0100 Subject: [Slackbuilds-users] clamav In-Reply-To: Message-ID: Hallo, Matteo, Du meintest am 28.03.13: > remember that SBo scripts are supported only for full installs of the > latest slackware stable, in this case 14.0: any other configuration > is unsupported. Yes - i know. But this special error only happens with the SBo-clamav packet. > said that, maybe I'm missing something, but I tried on my > slackware64-current to run cron.daily manually and I got no such > error. That error ("mv ...") seems to happen not on all installations, it's (for me) hard to locate it. But it seems to vanish when I delete the 3 above mentioned lines in "/ etc/logrotate.d/clamav". Strange ... Viele Gruesse! Helmut From Hullen at t-online.de Thu Mar 28 12:40:00 2013 From: Hullen at t-online.de (Helmut Hullen) Date: 28 Mar 2013 13:40:00 +0100 Subject: [Slackbuilds-users] clamav In-Reply-To: Message-ID: Hallo, Matteo, Du meintest am 28.03.13: > remember that SBo scripts are supported only for full installs of the > latest slackware stable, in this case 14.0: any other configuration > is unsupported. > said that, maybe I'm missing something, but I tried on my > slackware64-current to run cron.daily manually and I got no such > error. Additional: a) "su clamav clamav" looks strange for me; I'd prefer "su - clamav" b) running "/etc/logrotate.d/clamav" without the "su clamav clamav" line shows, that "logrotate" complains the rights of the directory "/var/log/ clamav" (originally set to clamav:clamav). Setting the ownership to "clamav:root" and 750 should help. Viele Gruesse! Helmut From matteo.bernardini at gmail.com Thu Mar 28 13:05:06 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 28 Mar 2013 14:05:06 +0100 Subject: [Slackbuilds-users] clamav In-Reply-To: References: Message-ID: a) that's not shell syntax, check "man logrotate"; b) maybe it's right for your customized installation but it does not apply to the current script in our repository. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hullen at t-online.de Thu Mar 28 14:25:00 2013 From: Hullen at t-online.de (Helmut Hullen) Date: 28 Mar 2013 15:25:00 +0100 Subject: [Slackbuilds-users] clamav In-Reply-To: Message-ID: Hallo, Matteo, Du meintest am 28.03.13: > a) that's not shell syntax, check "man logrotate"; > b) maybe it's right for your customized installation but it does not > apply to the current script in our repository. Part of "clamav.SlackBuild": ----------------------- # Our rc script and logrotate entry: install -D -m 0755 $CWD/rc.clamav $PKG/etc/rc.d/rc.clamav.new install -D -m 0644 $CWD/logrotate.clamav $PKG/etc/logrotate.d/clamav ----------------------- and "logrotate.clamav" from the SBo clamav*.tgz-packet: ----------------------- /var/log/clamav/*.log { su clamav clamav weekly rotate 5 compress delaycompress notifempty missingok create 0660 clamav clamav postrotate /bin/kill -HUP `cat /var/run/clamav/clamd.pid 2>/dev/null` 2>/dev/null || true /bin/kill -HUP `cat /var/run/clamav/freshclam.pid 2>/dev/null` 2>/dev/null || true endscript } ----------------------- As mentioned: with the su ... create ... /bin/kill ... freshclam lines it seems to work without problems. User "clamav" and group "clamav" exist. Viele Gruesse! Helmut From kingbeowulf at gmail.com Thu Mar 28 18:22:52 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 28 Mar 2013 11:22:52 -0700 Subject: [Slackbuilds-users] qemu: New Maintainer - suggestion In-Reply-To: <1460AD2A-8DEB-4336-9834-070E85273F06@uq.edu.au> References: <512BE6B6.5050509@gmail.com> <1460AD2A-8DEB-4336-9834-070E85273F06@uq.edu.au> Message-ID: Chris, I'll take a gander at the script per your suggestion soon. I thought I'd included all the docs but haven't double checked. Ed On 3/27/13, Christoph Willing wrote: > > On 26/02/2013, at 8:33 AM, 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. > > I see there is a qemu.tar.gz in the pending queue - I guess thats the 1.4.0 > version. > > In the meantime, I just recently used the SlackBuild from Matteo's git repo. > I hoped that the latest version would fix a problem I was having with host > to guest pass through for USB memory sticks. > > Well, the new version didn't solve the problem by itself but after a full > working day of googling and trying various command line options, I finally > found clear instructions (that worked) in the docs directory of the source > code. For some reason it had been overlooked for inclusion with the final > build, hence nothing in /usr/docs/qemu-1.4.0. Looking back now, I see docs/* > were included in qemu-kvm-1.2.0 but not in qemu-1.2.0; if the new qemu-1.4.0 > SlackBuild is based on the qemu-1.2.0 version then it too might not have the > missing docs. > > Anyway my suggestion/request is that qemu's docs/* be included in the final > build of the new qemu SlackBuild - those documents may save someone else a > lot of troubleshooting time. > > > chris > _______________________________________________ > 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/ > > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From kingbeowulf at gmail.com Fri Mar 29 05:03:45 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 28 Mar 2013 22:03:45 -0700 Subject: [Slackbuilds-users] please pull qemu from pending Message-ID: <515520B1.9070709@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Admins, Please delete qemu from pending; I will resubmit once I clean the script up. qemu.slackbuilds "works" but there are a few glitches that need fixing. The missing .txt docs was trival, but --libdir is more important as configure recognizes but does not advertize it: https://github.com/stefanha/qemu/commit/a7b66fa7aefb8dce564f0fa665de7965d3007148 This has been merged into qemu master. Thanks. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlFVIK8ACgkQXvwMaW61dLfZpACfVByebn1bmeKRUkzEnZ4lQj6N fh8AoJ2ZJbOeegLGRKyCzt3RiSpw1WHn =Mp/i -----END PGP SIGNATURE----- From xgizzmo at slackbuilds.org Fri Mar 29 11:28:20 2013 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Fri, 29 Mar 2013 07:28:20 -0400 Subject: [Slackbuilds-users] please pull qemu from pending In-Reply-To: <515520B1.9070709@gmail.com> References: <515520B1.9070709@gmail.com> Message-ID: <201303290728.21224.xgizzmo@slackbuilds.org> On Friday 29 March 2013 01:03:45 King Beowulf wrote: > Admins, > > Please delete qemu from pending; I will resubmit once I clean the > script up. > > qemu.slackbuilds "works" but there are a few glitches that need > fixing. The missing .txt docs was trival, but --libdir is more > important as configure recognizes but does not advertize it: > > https://github.com/stefanha/qemu/commit/a7b66fa7aefb8dce564f0fa665de7965d3007148 > > This has been merged into qemu master. > > Thanks. > Done, FYI you can remove your submissions from pending at any time, the information is in the confirmation email. --dsomero From willysr at gmail.com Fri Mar 29 10:32:08 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Fri, 29 Mar 2013 17:32:08 +0700 Subject: [Slackbuilds-users] please pull qemu from pending In-Reply-To: <515520B1.9070709@gmail.com> References: <515520B1.9070709@gmail.com> Message-ID: > Please delete qemu from pending; I will resubmit once I clean the > script up. You can remove it using the link provided at your email once you submitted your SlackBuild :) -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From kingbeowulf at gmail.com Fri Mar 29 16:36:55 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 29 Mar 2013 09:36:55 -0700 Subject: [Slackbuilds-users] please pull qemu from pending In-Reply-To: References: <515520B1.9070709@gmail.com> Message-ID: <5155C327.4070508@gmail.com> On 03/29/2013 03:32 AM, Willy Sudiarto Raharjo wrote: >> Please delete qemu from pending; I will resubmit once I clean >> the script up. > > You can remove it using the link provided at your email once you > submitted your SlackBuild :) > Thanks, forgot that tid-bit. Somebody got to it before I did though: "The file qemu.tar.gz does not exist in pending." From kingbeowulf at gmail.com Fri Mar 29 19:45:56 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 29 Mar 2013 12:45:56 -0700 Subject: [Slackbuilds-users] please pull qemu from pending In-Reply-To: <5155C327.4070508@gmail.com> References: <515520B1.9070709@gmail.com> <5155C327.4070508@gmail.com> Message-ID: Oops, I should read my emails more carefully...or increase the font size ;-) On 3/29/13, King Beowulf wrote: > On 03/29/2013 03:32 AM, Willy Sudiarto Raharjo wrote: >>> Please delete qemu from pending; I will resubmit once I clean >>> the script up. >> >> You can remove it using the link provided at your email once you >> submitted your SlackBuild :) >> > Thanks, forgot that tid-bit. Somebody got to it before I did though: > "The file qemu.tar.gz does not exist in pending." > > > > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From pyllyukko at maimed.org Sat Mar 30 15:32:35 2013 From: pyllyukko at maimed.org (pyllyukko) Date: Sat, 30 Mar 2013 17:32:35 +0200 Subject: [Slackbuilds-users] clamav In-Reply-To: References: Message-ID: <20130330153234.GA2921@severi.lan> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello. On Thu, Mar 28, 2013 at 03:25:00PM +0100, Helmut Hullen wrote: > > /var/log/clamav/*.log { > su clamav clamav > weekly > rotate 5 > compress > delaycompress > notifempty > missingok > create 0660 clamav clamav > postrotate > /bin/kill -HUP `cat /var/run/clamav/clamd.pid 2>/dev/null` 2>/dev/null || true > /bin/kill -HUP `cat /var/run/clamav/freshclam.pid 2>/dev/null` 2>/dev/null || true > endscript > } Try adding "sharedscripts". I had problems without it. You can see my previous posts on this list, relating to similar problems. - -- pyllyukko email: pgp: 0xA1F32EAA www: http://maimed.org/~pyllyukko/ twitter: https://twitter.com/pyllyukko -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlFXBZIACgkQjAuVIaHzLqoQ/gCfVZDcWIrLbfXvSojmgv01XglB bQ0AoL/wY1e9cV0p/8aO4voLtWw+9Sy6 =YJ/v -----END PGP SIGNATURE----- From mherda at slackword.net Sat Mar 30 16:15:32 2013 From: mherda at slackword.net (Marcin Herda) Date: Sat, 30 Mar 2013 16:15:32 +0000 Subject: [Slackbuilds-users] Does anyone have a problem with i3status (eg. wifi display)? Message-ID: <51570FA4.5080200@slackword.net> Hi all, A user reported it to me that i3status does not display the wifi status correctly (it shows: "W: down" although it is connected). The user solved the problem by setting setuid bit on i3status. I cannot, however, reproduce the error. I have tried it on 3 different machines running S14 and -current and it works fine (ie. It does not require setuid on /usr/bin/i3status for the wifi status to be displayed as intended). Has any of you encountered a similar problem? The i3status Makefile sets: setcap cap_net_admin=ep which, according to i3 developer/author, should suffice and so far has been sufficient on my systems. Any feedback will be greatly appreciated. regards Marcin -- -- sycamorex From yalhcru at gmail.com Sat Mar 30 17:46:45 2013 From: yalhcru at gmail.com (B Watson) Date: Sat, 30 Mar 2013 13:46:45 -0400 Subject: [Slackbuilds-users] Does anyone have a problem with i3status (eg. wifi display)? In-Reply-To: <51570FA4.5080200@slackword.net> References: <51570FA4.5080200@slackword.net> Message-ID: On 3/30/13, Marcin Herda wrote: > The i3status Makefile sets: > > setcap cap_net_admin=ep > > which, according to i3 developer/author, should suffice and so far has > been sufficient on my systems. tar doesn't support capabilities, so if that bit is required, you'll have to set it in your doinst.sh. Probably should mention the capability bit in your README. It's not as much of a potential security risk as a setuid binary, but still it lets users do things users normally can't do. Also be aware that in Slackware 14 (but not 13.37 or earlier), glibc ignores LD_LIBRARY_PATH on binaries with capabilities (same it it's always done for setuid binaries). This probably doesn't affect your package, but I haven't actually looked at it... From mfilpot at gmail.com Sat Mar 30 16:33:38 2013 From: mfilpot at gmail.com (Matthew Fillpot) Date: Sat, 30 Mar 2013 12:33:38 -0400 Subject: [Slackbuilds-users] Does anyone have a problem with i3status (eg. wifi display)? In-Reply-To: <51570FA4.5080200@slackword.net> References: <51570FA4.5080200@slackword.net> Message-ID: On Mar 30, 2013 12:22 PM, "Marcin Herda" wrote: > > Hi all, > > A user reported it to me that i3status does not display the wifi status correctly (it shows: "W: down" although it is connected). The user solved the problem by setting setuid bit on i3status. I cannot, however, reproduce the error. I have tried it on 3 different machines running S14 and -current and it works fine (ie. It does not require setuid on /usr/bin/i3status for the wifi status to be displayed as intended). > > Has any of you encountered a similar problem? > > The i3status Makefile sets: > > setcap cap_net_admin=ep > > which, according to i3 developer/author, should suffice and so far has been sufficient on my systems. > > Any feedback will be greatly appreciated. > > regards > Marcin > > -- > -- sycamorex > > _______________________________________________ > 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 have it on 4 machines and have not encountered that problem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.willing at uq.edu.au Sat Mar 30 22:46:25 2013 From: c.willing at uq.edu.au (Christoph Willing) Date: Sun, 31 Mar 2013 08:46:25 +1000 Subject: [Slackbuilds-users] please pull qemu from pending In-Reply-To: <515520B1.9070709@gmail.com> References: <515520B1.9070709@gmail.com> Message-ID: <4B63D3D5-0BD7-41CF-BAB6-7C8307A95D95@uq.edu.au> On 29/03/2013, at 3:03 PM, King Beowulf wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Admins, > > Please delete qemu from pending; I will resubmit once I clean the > script up. > > qemu.slackbuilds "works" but there are a few glitches that need > fixing. The missing .txt docs was trival, There are two .cfg files there as somewhat advanced examples which would be useful to keep. Also the stuff in the docs/specs subdir is good info for hacking and is only about 60K uncompressed ... chris > but --libdir is more > important as configure recognizes but does not advertize it: > > https://github.com/stefanha/qemu/commit/a7b66fa7aefb8dce564f0fa665de7965d3007148 > > This has been merged into qemu master. > > Thanks. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iEYEARECAAYFAlFVIK8ACgkQXvwMaW61dLfZpACfVByebn1bmeKRUkzEnZ4lQj6N > fh8AoJ2ZJbOeegLGRKyCzt3RiSpw1WHn > =Mp/i > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > Christoph Willing +61 7 3365 8316 Research Computing Centre University of Queensland From kingbeowulf at gmail.com Sun Mar 31 00:32:09 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 30 Mar 2013 17:32:09 -0700 Subject: [Slackbuilds-users] please pull qemu from pending In-Reply-To: <4B63D3D5-0BD7-41CF-BAB6-7C8307A95D95@uq.edu.au> References: <515520B1.9070709@gmail.com> <4B63D3D5-0BD7-41CF-BAB6-7C8307A95D95@uq.edu.au> Message-ID: <51578409.2090307@gmail.com> On 03/30/2013 03:46 PM, Christoph Willing wrote: > > There are two .cfg files there as somewhat advanced examples which > would be useful to keep. > >> Also the stuff in the docs/specs subdir is good info for hacking >> and is only about 60K uncompressed ... > > > chris > > Done and resubmitted.