From nille.kungen at gmail.com Wed Feb 1 04:37:19 2012 From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_Nille_=C5kerstr=F6m?=) Date: Wed, 01 Feb 2012 05:37:19 +0100 Subject: [Slackbuilds-users] Optional dep kipi-plugins Message-ID: <4F28C17F.5030802@gmail.com> opencv should be added as optional dependencies for kipi-plugins. opencv adds support for RemoveRedEyes. /Nille From robby at rlworkman.net Fri Feb 3 20:26:40 2012 From: robby at rlworkman.net (Robby Workman) Date: Fri, 3 Feb 2012 14:26:40 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu Message-ID: <20120203142640.036a3d30@liberty.rlwhome.lan> Hi Leo and Stu (and SBo-users): I've recently switched to using qemu-only for my virtual machines, and I have some observations / suggestions from the transition. Leo: I started out using aqemu as a front-end to simplify the initial setup, and after upgrading to qemu-1.0, I discovered that aqemu didn't understand the new version number. Find attached some a tarball with some patches from aqemu git - the patchset includes some usual bugfixes but also a commit adding support for qemu-1.0. If the result looks okay to you, please submit that and I'll get it approved and into the repo. Stu: I have two suggestions for qemu-kvm, but neither of them should be done without your approval, nor am I certain that one of them should even *be* done, so I think it's best to run both of them past you... First, how about a symlink at /usr/bin/qemu-kvm pointing to /usr/bin/qemu-system-x86_64, i.e.: ( cd $PKG/usr/bin ; ln -s qemu-system-x86_64 qemu-kvm ) This is so that e.g. aqemu can easily find it without the user having to manually tell it where the KVM-equivalent binary is located. I don't think there's any downside to this, and in fact, if it were the only change I had, I'd just make it in our repo and be done with it. However... The second suggested change is to strip the package down quite a bit. Basically, I'd like to remove everything that's also shipped with the regular qemu package so that there's no overlap. This would mean that our qemu-kvm would (optionally) depend on our qemu package. Any thoughts on this? Assuming that's acceptable, I then wonder if it wouldn't be a good idea to just rename /usr/bin/qemu-system-x86_64 to /usr/bin/qemu-kvm; after all, the former filename is still a conflict with the qemu package. My concern is simply that a reinstall/upgrade of qemu without a subsequent reinstall/upgrade of qemu-kvm would result in a /usr/bin/qemu-kvm symlink pointing to regular qemu's binary. I know that regular qemu supports the -enable-kvm switch now, and that there was a big merge of much of the qemu-kvm code into vanilla qemu, but the guys in #qemu say that qemu-kvm is still the optimal choice to use. All that said, I'm more than willing to do the legwork on this, so if it's okay with you, just say the word :) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: aqemu.tar.gz Type: application/x-gzip Size: 10627 bytes Desc: not available URL: From matteo.bernardini at gmail.com Fri Feb 3 21:16:55 2012 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 3 Feb 2012 22:16:55 +0100 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120203142640.036a3d30@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> Message-ID: hope anybody don't mind if I share some thoughts on this :D 2012/2/3 Robby Workman : > First, how about a symlink at /usr/bin/qemu-kvm pointing to > /usr/bin/qemu-system-x86_64, i.e.: > ?( cd $PKG/usr/bin ; ln -s qemu-system-x86_64 qemu-kvm ) > This is so that e.g. aqemu can easily find it without the user > having to manually tell it where the KVM-equivalent binary is > located. ?I don't think there's any downside to this, and in fact, > if it were the only change I had, I'd just make it in our repo and > be done with it. ?However... I have the qemu-system-x86_64 binary linked to just "kvm", for using it with libvirt: I know it's another example of Red Hat customizations, but I remember a discussion of not much time ago on LKML in which Pekka Enberg renamed his new in-kernel kvm emulator kvm-tool to follow this "standard"... this way is also automatically found http://ompldr.org/vY20xaA/screen.png > The second suggested change is to strip the package down quite a > bit. ?Basically, I'd like to remove everything that's also shipped > with the regular qemu package so that there's no overlap. ?This > would mean that our qemu-kvm would (optionally) depend on our qemu > package. ?Any thoughts on this? I think the present state is optimal: qemu-kvm should be used in every case kvm processor extensions are available, while qemu can be useful in the few cases of needing virtualization on old processors (it's very uncommon today to have x86 processors with no virtualization extensions); frankly, I see no cases in which the use of both can be useful... my 2 cts :) Matteo From rworkman at slackbuilds.org Fri Feb 3 21:37:13 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 3 Feb 2012 15:37:13 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: References: <20120203142640.036a3d30@liberty.rlwhome.lan> Message-ID: <20120203153713.0c1ed224@liberty.rlwhome.lan> On Fri, 3 Feb 2012 22:16:55 +0100 Matteo Bernardini wrote: > hope anybody don't mind if I share some thoughts on this :D Sure, that's fine - otherwise, I wouldn't have CC'd the list :) > 2012/2/3 Robby Workman : > > First, how about a symlink at /usr/bin/qemu-kvm pointing to > > /usr/bin/qemu-system-x86_64, i.e.: > > ?( cd $PKG/usr/bin ; ln -s qemu-system-x86_64 qemu-kvm ) > > This is so that e.g. aqemu can easily find it without the user > > having to manually tell it where the KVM-equivalent binary is > > located. ?I don't think there's any downside to this, and in fact, > > if it were the only change I had, I'd just make it in our repo and > > be done with it. ?However... > > I have the qemu-system-x86_64 binary linked to just "kvm", for using > it with libvirt: I know it's another example of Red Hat > customizations, but I remember a discussion of not much time ago on > LKML in which Pekka Enberg renamed his new in-kernel kvm emulator > kvm-tool to follow this "standard"... > > this way is also automatically found > > http://ompldr.org/vY20xaA/screen.png Yes, similar to that is what aqemu does. It looks for both "kvm" and "qemu-kvm" binaries, hence my suggestion of linking it to "qemu-kvm" in the script. Perhaps both is better... > > The second suggested change is to strip the package down quite a > > bit. ?Basically, I'd like to remove everything that's also shipped > > with the regular qemu package so that there's no overlap. ?This > > would mean that our qemu-kvm would (optionally) depend on our qemu > > package. ?Any thoughts on this? > > I think the present state is optimal: qemu-kvm should be used in every > case kvm processor extensions are available, while qemu can be useful > in the few cases of needing virtualization on old processors (it's > very uncommon today to have x86 processors with no virtualization > extensions); frankly, I see no cases in which the use of both can be > useful... Oh, I see. Good point. In other words, you don't want to have to install the regular "qemu" package to get the keymaps and such, as all you care about are x86* architectures. That's a fair point, and so I guess I should withdraw the conflict removal portion. The conflicts don't really hurt anything anyway. That being the case, here's my modified suggestion: ( cd $PKG/usr/bin mv qemu-system-x86_64 qemu-kvm ln -s qemu-kvm kvm ) This addresses the concern with overwriting qemu-system-x86_64 with the non-kvm-by-default file from regular qemu. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From matteo.bernardini at gmail.com Fri Feb 3 21:55:49 2012 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 3 Feb 2012 22:55:49 +0100 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120203153713.0c1ed224@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> Message-ID: 2012/2/3 Robby Workman : > Yes, similar to that is what aqemu does. ?It looks for both "kvm" > and "qemu-kvm" binaries, hence my suggestion of linking it to > "qemu-kvm" in the script. ?Perhaps both is better... I was missing that libvirt looks also for qemu-kvm, in this case for me qemu-kvm is ok as well :) > Oh, I see. ?Good point. ?In other words, you don't want to have to > install the regular "qemu" package to get the keymaps and such, as > all you care about are x86* architectures. Nono, I am about to use it extensively with ARM ones :) It's just that I think that usually, between qemu-kvm and qemu, only one should be needed, depending on the hardware on which you have to do virtualization. but, who knows, maybe I'm missing some use cases... Matteo From rworkman at slackbuilds.org Fri Feb 3 22:19:53 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 3 Feb 2012 16:19:53 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> Message-ID: <20120203161953.431d6b53@liberty.rlwhome.lan> On Fri, 3 Feb 2012 22:55:49 +0100 Matteo Bernardini wrote: > 2012/2/3 Robby Workman : > > Yes, similar to that is what aqemu does. ?It looks for both "kvm" > > and "qemu-kvm" binaries, hence my suggestion of linking it to > > "qemu-kvm" in the script. ?Perhaps both is better... > > I was missing that libvirt looks also for qemu-kvm, in this case for > me qemu-kvm is ok as well :) Okay, then the proposal is to only rename the binary. Stu, still following this? :) > > Oh, I see. ?Good point. ?In other words, you don't want to have to > > install the regular "qemu" package to get the keymaps and such, as > > all you care about are x86* architectures. > > Nono, I am about to use it extensively with ARM ones :) But ARM doesn't make use of KVM extensions, and that leads to... > It's just that I think that usually, between qemu-kvm and qemu, only > one should be needed, depending on the hardware on which you have to > do virtualization. > but, who knows, maybe I'm missing some use cases... Yes, so use plain qemu for ARM and other architectures. My understanding is that the qemu-kvm codebase is optimized for *only* KVM usage, and thus some more generic optimizations (e.g. for ARM and other non-KVM architectures) may not be present, while the exact opposite is true of the regular qemu codebase. Therefore, the best approach would be to have only the "qemu-kvm" package installed if you only need virtualization (i.e. x86*), or install only the regular "qemu" package if you only need to work with non-KVM-enabled architectures (e.g. ARM), or install both packages if you need to do both. I'm attaching a tarball of the result of all discussion thus far. Note that it changes KVMGROUP to "users" by default (as I suspect the most common usecase here is a single-user devel box) and no longer offers the option of building "all" targets -- regular qemu should be used for that. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: qemu-kvm.tar.gz Type: application/x-gzip Size: 3428 bytes Desc: not available URL: From niels.horn at gmail.com Fri Feb 3 23:15:22 2012 From: niels.horn at gmail.com (Niels Horn) Date: Fri, 3 Feb 2012 21:15:22 -0200 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120203161953.431d6b53@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> Message-ID: On Fri, Feb 3, 2012 at 8:19 PM, Robby Workman wrote: > Yes, so use plain qemu for ARM and other architectures. > > My understanding is that the qemu-kvm codebase is optimized for > *only* KVM usage, and thus some more generic optimizations (e.g. > for ARM and other non-KVM architectures) may not be present, > while the exact opposite is true of the regular qemu codebase. > Therefore, the best approach would be to have only the "qemu-kvm" > package installed if you only need virtualization (i.e. x86*), > or install only the regular "qemu" package if you only need to > work with non-KVM-enabled architectures (e.g. ARM), or install > both packages if you need to do both. > Hmm... I use qemu-kvm for everything - both virtualization (x86 / x86_64 running on Slackware64) and emulation (ARM). "Normal" qemu might be optimized somewhat for ARM, but I prefer to maintain only one qemu package on my system. :) I actually use a customized version of qemu-kvm to work nicely with pt-BR keyboards, but that's another story... Never used aqemu - it's somewhere on my todo-list to check out - only my own little shell scripts. -- Niels Horn From kingbeowulf at gmail.com Sat Feb 4 00:30:56 2012 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 03 Feb 2012 16:30:56 -0800 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> Message-ID: <4F2C7C40.9040106@gmail.com> On 02/03/2012 03:15 PM, Niels Horn wrote: > On Fri, Feb 3, 2012 at 8:19 PM, Robby Workman wrote: >> Yes, so use plain qemu for ARM and other architectures. >> >> My understanding is that the qemu-kvm codebase is optimized for >> *only* KVM usage, and thus some more generic optimizations (e.g. >> for ARM and other non-KVM architectures) may not be present, >> while the exact opposite is true of the regular qemu codebase. >> Therefore, the best approach would be to have only the "qemu-kvm" >> package installed if you only need virtualization (i.e. x86*), >> or install only the regular "qemu" package if you only need to >> work with non-KVM-enabled architectures (e.g. ARM), or install >> both packages if you need to do both. >> > Hmm... I use qemu-kvm for everything - both virtualization (x86 / > x86_64 running on Slackware64) and emulation (ARM). > "Normal" qemu might be optimized somewhat for ARM, but I prefer to > maintain only one qemu package on my system. :) > > I actually use a customized version of qemu-kvm to work nicely with > pt-BR keyboards, but that's another story... > > Never used aqemu - it's somewhere on my todo-list to check out - only > my own little shell scripts. > > -- > Niels Horn > _______________________________________________ > 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/ > > qemu is 1.0 ???? Man, I need to to keep up. aqemu is nice, switched to it from a myriad shell scripts when I started to forget which script did what and was writing a "generic" script to manage the VMs. aqemu was easier for me to implement and keep track of the main options. I use kvm-amd module in the stock kernel. I don't see much difference on my Athlon64 X2 system and not much difference to Virtualbox (excepting graphics acceleration). Although the current SBo readme for qemu implies kqemu is needed, it is not as that functionality is already built in as I understand from the docs. -Ed From stu at ssmbox.net Sat Feb 4 00:22:58 2012 From: stu at ssmbox.net (Stu) Date: Fri, 03 Feb 2012 17:22:58 -0700 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120203161953.431d6b53@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> Message-ID: <95f6e18a7187d1acabf4f92850c6635f@guest8> On 03.02.2012 15:19, Robby Workman wrote: > On Fri, 3 Feb 2012 22:55:49 +0100 > Matteo Bernardini wrote: > >> 2012/2/3 Robby Workman : >> >>> Yes, similar to that is what aqemu does. It looks for both "kvm" >>> and >>> "qemu-kvm" binaries, hence my suggestion of linking it to >>> "qemu-kvm" >>> in the script. Perhaps both is better... >> I was missing that libvirt looks also for qemu-kvm, in this case for >> me qemu-kvm is ok as well :) > > Okay, then the proposal is to only rename the binary. > Stu, still following this? :) Still tracking. Was looking for something fun to do tomorrow morning. We're getting hammered with snow right now in Denver, CO and I expect to be shut in for the weekend. > >>> Oh, I see. Good point. In other words, you don't want to have to >>> install the regular "qemu" package to get the keymaps and such, as >>> all you care about are x86* architectures. >> Nono, I am about to use it extensively with ARM ones :) > > But ARM doesn't make use of KVM extensions, and that leads to... From matteo.bernardini at gmail.com Sat Feb 4 09:46:26 2012 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 4 Feb 2012 10:46:26 +0100 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <4F2C7C40.9040106@gmail.com> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <4F2C7C40.9040106@gmail.com> Message-ID: a small gotcha that I seem to have noticed in the use of BUILD_ARCH and TARGETS variable (can be I haven't understood the correct syntax, in this case sorry in advance :) ): while I was playing with the build script to compile all archs support on latest current, I noticed that I wasn't able to specify, for example, BUILD_ARCH="x86_64-softmmu,x86_64-linux-user,arm-softmmu,arm-linux-user", so I removed the TARGETS variable and passed directly $BUILD_ARCH to --target-list. I added also other stuff that I use here in the attached patch, hope can be useful for someone. :) Matteo -------------- next part -------------- A non-text attachment was scrubbed... Name: qemu-kvm.patch Type: application/octet-stream Size: 15950 bytes Desc: not available URL: From netrixtardis at stealth3.com Sun Feb 5 16:38:55 2012 From: netrixtardis at stealth3.com (netrixtardis) Date: Sun, 5 Feb 2012 10:38:55 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120203142640.036a3d30@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> Message-ID: <20120205103855.43c6b7e6@conroe.localdomain.lan> On Fri, 3 Feb 2012 14:26:40 -0600 Robby Workman wrote: > Hi Leo and Stu (and SBo-users): > > I've recently switched to using qemu-only for my virtual machines, > and I have some observations / suggestions from the transition. > > Leo: > > I started out using aqemu as a front-end to simplify the initial > setup, and after upgrading to qemu-1.0, I discovered that aqemu > didn't understand the new version number. Find attached some > a tarball with some patches from aqemu git - the patchset includes > some usual bugfixes but also a commit adding support for qemu-1.0. > If the result looks okay to you, please submit that and I'll get > it approved and into the repo. > I will look into those patches today. thanks, From slackbuilds at ssmbox.net Sun Feb 5 18:36:35 2012 From: slackbuilds at ssmbox.net (Stu Miller) Date: Sun, 05 Feb 2012 11:36:35 -0700 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120203161953.431d6b53@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> Message-ID: <26444ac2169dc8c1247b2e4da39f3854@guest8> On 03.02.2012 15:19, Robby Workman wrote: > On Fri, 3 Feb 2012 22:55:49 +0100 > Matteo Bernardini wrote: > >> 2012/2/3 Robby Workman : >> >>> Yes, similar to that is what aqemu does. It looks for both "kvm" and "qemu-kvm" binaries, hence my suggestion of linking it to "qemu-kvm" in the script. Perhaps both is better... >> I was missing that libvirt looks also for qemu-kvm, in this case for me qemu-kvm is ok as well :) > > Okay, then the proposal is to only rename the binary. > Stu, still following this? :) > >>> Oh, I see. Good point. In other words, you don't want to have to install the regular "qemu" package to get the keymaps and such, as all you care about are x86* architectures. >> Nono, I am about to use it extensively with ARM ones :) > > But ARM doesn't make use of KVM extensions, and that leads to... > It's just that I think that usually, between qemu-kvm and qemu, only one should be needed, depending on the hardware on wh > >> es, so use plain qemu for ARM and other architectures. My understanding is that the qemu-kvm codebase is optimized for *only* KVM usage, and thus some more generic optimizations (e.g. for ARM and other > tectures) may not be present, while the exact opposite is true of the regular qemu codebase. Therefore, the best approach would be to have only the "qemu-kvm" package installed if you only need virtualization (i.e. x86*), or install only the regular "qemu" package if you only need to work with non-KVM-enabled architectures (e.g. ARM), or install both packages if you need to do both. I'm attaching a tarball of the result of all discussion thus far. Note that it changes KVMGROUP to "users" by default (as I suspect the most common usecase here is a single-user devel box) and no longer offers the option of building "all" targets -- regular qemu should be used for that. -RW replacement package uploaded to slackbuilds.org changes to package: default group changed from kvm to users default target changed to x86_64-softmmu target list feature (e.g. build all targets) no longer in package /usr/bin/qemu-system-x86_64 binary renamed to /usr/bin/qemu-kvm (don't forget to change your startup scripts!) README and qemu-SlackBuild reference QEMU for non-x86 CPU targets Links: ------ [1] mailto:rworkman at slackbuilds.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Mon Feb 6 04:12:06 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 5 Feb 2012 22:12:06 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <26444ac2169dc8c1247b2e4da39f3854@guest8> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> Message-ID: <20120205221206.2b566e8d@liberty.rlwhome.lan> On Sun, 05 Feb 2012 11:36:35 -0700 Stu Miller wrote: > replacement package uploaded to slackbuilds.org Got it, and I just pushed your changes (with some of those from ponce) to a git branch: http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-kvm I know these changes aren't going to make everyone happy, so I'm putting them in a separate branch for now so that we can (hopefully) reach a compromise that works for all of us... ponce: I like the idea of spice support, but since we don't have spice in our repo, I don't see the point right now. Perhaps that will change someday... ;-) Nils and ponce: Is it *really* important to continue supporting the other build targets (e.g. "all") here? If so, then I suppose we can do that, but it seems ugly :) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From hba.nihilismus at gmail.com Mon Feb 6 04:17:15 2012 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sun, 5 Feb 2012 22:17:15 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <26444ac2169dc8c1247b2e4da39f3854@guest8> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> Message-ID: On Sun, Feb 5, 2012 at 12:36 PM, Stu Miller wrote: > replacement package uploaded to slackbuilds.org > > changes to package: > > ? default group changed from kvm to users > I don't see any real need for that since you already can execute: # KVMGROUP='users' sh qemu-kvm.SlackBuild but anyway i can add "export KVMGROUP='kvm'" to /etc/profile.d/sbo.sh to keep it the same as now. > ? default target changed to x86_64-softmmu > > ? target list feature (e.g. build all targets) no longer in package > > ? /usr/bin/qemu-system-x86_64 binary renamed to /usr/bin/qemu-kvm (don't > forget to change your startup scripts!) > Can you do a symlink from /usr/bin/qemu-system-x86_64 to /usr/bin/qemu-kvm? So you don't break the normal name that one has been using ;) BTW, there's also the next binaries inside qemu-kvm package: /usr/bin/qemu-img => /usr/bin/qemu-kvm-img /usr/bin/qemu-nbd => /usr/bin/qemu-kvm-nbd /usr/bin/qemu-ga => /usr/bin/qemu-kvm-ga /usr/bin/qemu-io => /usr/bin/qemu-kvm-io Are they going to be renamed also? If so, man pages also would be renamed?. At this moment i think there's a conflict with *qemu* package, isn't there? /usr/man/man1/qemu-img.1.gz => /usr/man/man1/qemu-kvm-img.1.gz /usr/man/man1/qemu.1.gz => /usr/man/man1/qemu-kvm.1.gz /usr/man/man8/qemu-nbd.8.gz => /usr/man/man8/qemu-kvm-nbd.8.gz -- - hba | Antonio Hern?ndez Blas | Mexico, Mx. http://hba.dyndns.info | http://barrapunto.com/~hba/ | irc://irc.freenode.org/hba,isnick,needpass From rworkman at slackbuilds.org Mon Feb 6 04:30:24 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 5 Feb 2012 22:30:24 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> Message-ID: <20120205223024.3d08d2e4@liberty.rlwhome.lan> On Sun, 5 Feb 2012 22:17:15 -0600 Antonio Hern?ndez Blas wrote: > On Sun, Feb 5, 2012 at 12:36 PM, Stu Miller > wrote: > > > replacement package uploaded to slackbuilds.org > > > > changes to package: > > > > ? default group changed from kvm to users > > > > I don't see any real need for that since you already can execute: > > # KVMGROUP='users' sh qemu-kvm.SlackBuild > > but anyway i can add "export KVMGROUP='kvm'" to /etc/profile.d/sbo.sh > to keep it the same as now. The change is because "users" makes a better *default* (IMHO); there's no real reason to require a special group that's not already present, so I'd prefer the default to be this way. > > ? default target changed to x86_64-softmmu > > > > ? target list feature (e.g. build all targets) no longer in package > > > > ? /usr/bin/qemu-system-x86_64 binary renamed to /usr/bin/qemu-kvm > > (don't forget to change your startup scripts!) > > > > Can you do a symlink from /usr/bin/qemu-system-x86_64 to > /usr/bin/qemu-kvm? So you don't break the normal name that one has > been using ;) No; putting a symlink at qemu-system-x86_64 would then kill the qemu-system-x86_64 binary shipped with the regular qemu package. > BTW, there's also the next binaries inside qemu-kvm package: > > /usr/bin/qemu-img => /usr/bin/qemu-kvm-img > /usr/bin/qemu-nbd => /usr/bin/qemu-kvm-nbd > /usr/bin/qemu-ga => /usr/bin/qemu-kvm-ga > /usr/bin/qemu-io => /usr/bin/qemu-kvm-io > > Are they going to be renamed also? If so, man pages also would be > renamed?. At this moment i think there's a conflict with *qemu* > package, isn't there? Simply having a conflict is fine, so long as the contents are the same, and they are for these other conflicts, so no, there's no need to rename them. Overwriting these files is completely harmless regardless of which package is installed last. That is *not* the case for the qemu-system-x86_64 binary. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From niels.horn at gmail.com Mon Feb 6 09:05:21 2012 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 6 Feb 2012 07:05:21 -0200 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120205221206.2b566e8d@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205221206.2b566e8d@liberty.rlwhome.lan> Message-ID: On Mon, Feb 6, 2012 at 2:12 AM, Robby Workman wrote: <...> > > Nils and ponce: > > ?Is it *really* important to continue supporting the other > ?build targets (e.g. "all") here? ?If so, then I suppose we > ?can do that, but it seems ugly ?:) > > -RW > Well, I think it would be nice, so users can stick to just qemu-kvm to do everything without the need to install both qemu + qemu-kvm. OTOH, I build my own package using an adapted SlackBuild because of some extra patches I need, so don't worry too much about me :) -- Niels Horn From molbolom at gmail.com Mon Feb 6 17:35:53 2012 From: molbolom at gmail.com (Charles Kauffman) Date: Mon, 6 Feb 2012 11:35:53 -0600 Subject: [Slackbuilds-users] My echinus and vifm slackbuilds are ready. Message-ID: I have modified my slackbuilds for vifm and echinus, hopefully correctly. However, before I upload them I have a couple of questions. 1. I haven't heard back from anyone if they were working on vifm, so need to know if someone is already working on it. 2. In the echinus.SlackBuild sed -i "s;-Os;$SLKCFLAGS ;g" config.mk sed -i "s;.pixmap: ;.pixmap: \/usr\/share\/echinus\/_g" echinusrc sed -i "s/DOCPREFIX}\/echinus/DOCPREFIX}\/echinus-$VERSION/g" Makefile The source only contains Makefile and config.mk, no configure script. So I replaced the compiler flag -Os with SLKCFLAGS, as well as had the script create a doc directory that had the version number appended to it. The second sed makes modifications to the rc file since problems can occur when the program loads. So, does that look good, or should I just leave some of that alone? Thanks. Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From hba.nihilismus at gmail.com Tue Feb 7 09:40:24 2012 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Tue, 7 Feb 2012 03:40:24 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120205223024.3d08d2e4@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205223024.3d08d2e4@liberty.rlwhome.lan> Message-ID: On Sun, Feb 5, 2012 at 10:30 PM, Robby Workman wrote: > > The change is because "users" makes a better *default* (IMHO); > there's no real reason to require a special group that's not > already present, so I'd prefer the default to be this way. > Ah ok, if this change is approved and used in the future i would recommend to update system/kvm-kmod/README to delete the mention of the kvm group. BTW, there's a new version [1] ;) > > Simply having a conflict is fine, so long as the contents are the > same, and they are for these other conflicts, so no, there's no > need to rename them. ?Overwriting these files is completely harmless > regardless of which package is installed last. ?That is *not* the > case for the qemu-system-x86_64 binary. > Interesting, because ATM system/qemu (0.14.1) and system/qemu-kvm (1.0) are in different version which means they have different content and there's a conflict between them, but ATM!. So let me see, if qemu-kvm would depend on qemu then it would be needed to update them always at the same version so they can play nice or am i seeing a problem where there's no problem? :) [1] http://sourceforge.net/projects/kvm/files/kvm-kmod/3.2/ -- - hba | Antonio Hern?ndez Blas | Mexico, Mx. http://hba.dyndns.info | http://barrapunto.com/~hba/ | irc://irc.freenode.org/hba,isnick,needpass From audrius at neutrino.lt Tue Feb 7 11:24:14 2012 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Tue, 7 Feb 2012 13:24:14 +0200 Subject: [Slackbuilds-users] My echinus and vifm slackbuilds are ready. In-Reply-To: References: Message-ID: <20120207112414.GA3642@kiras> On Mon, 2012-02-06 at 11:35:53 -0600, Charles Kauffman wrote: > 2. > In the echinus.SlackBuild > sed -i "s;-Os;$SLKCFLAGS ;g" config.mk > sed -i "s;.pixmap: ;.pixmap: \/usr\/share\/echinus\/_g" echinusrc > sed -i "s/DOCPREFIX}\/echinus/DOCPREFIX}\/echinus-$VERSION/g" Makefile > > The source only contains Makefile and config.mk, no configure script. So I > replaced the compiler flag -Os with SLKCFLAGS, as well as had the script > create a doc directory that had the version number appended to it. > The second sed makes modifications to the rc file since problems can occur > when the program loads. > > So, does that look good, or should I just leave some of that alone? Looks good to me. As long as the changes don't break anything, I'd say go for it. Just not sure if global (g) substitute is needed (it looks for multiple regex matches in a single line). Also there should be a semicolon at the end of second sed-line, no (and no need to escape slashes)? -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From matteo.bernardini at gmail.com Tue Feb 7 14:40:13 2012 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 7 Feb 2012 15:40:13 +0100 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205223024.3d08d2e4@liberty.rlwhome.lan> Message-ID: sorry for the delay, but I was fiddling with the stuff :) trying to ease maintaining also for end users and to follow Robby's concerns, I've adapted the qemu slackbuild to build also qemu-kvm and make a single package (by default, but there's a switch to disable building it). it's an experiment I assembled very fast but seems to work on my machines. Matteo -------------- next part -------------- A non-text attachment was scrubbed... Name: qemu.tar.gz Type: application/x-gzip Size: 6748 bytes Desc: not available URL: From rshepard at appl-ecosys.com Wed Feb 8 23:11:49 2012 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 8 Feb 2012 15:11:49 -0800 (PST) Subject: [Slackbuilds-users] Recommended Change to postfix.SlackBuild Message-ID: I recommend a change to postfix.SlackBuild to include cyrus SASL as well as dovecot SASL. The latter works only with smtpd while the former is required for smtp and needed by anyone who has to relay outgoing mail through an ISP's mail servers. After 15 years with a static IP address the telco providing the DSL line between here and our ISP changed us all to DHCP _and_ blocked outgoing port 25. This means that we need to relay outbound mail through our ISP. After a day-and-a-half of searching the Web and speaking with experienced network admins I figured out how to fix my mail service, incoming and outgoing. I'll share that here to explain how to add cyrus to the build script, and what change I needed to make to main.cf. In the SlackBuild script I changed to # Build with dovecot sasl by default, cyrus/dovecot are supported SASL=${SASL:-cyrus} and make makefiles \ CCARGS="-DUSE_SASL_AUTH -DUSE_TLS $SASLARGS $DBARGS -DUSE_CYRUS_SASL" \ AUXLIBS="-lssl -lcrypto $SASLLIBS $DBLIBS" In /etc/postfix/main.cf I had to set smtpd_sasl_auth_enable to no and comment out all other references to smtpd_sasl, then ensure that smtp_sasl_auth_enable = yes, and the other smtp_sasl-related options were properly set. Rich From mario at slackverse.org Wed Feb 8 23:37:32 2012 From: mario at slackverse.org (Mario) Date: Thu, 09 Feb 2012 00:37:32 +0100 Subject: [Slackbuilds-users] Recommended Change to postfix.SlackBuild In-Reply-To: References: Message-ID: <4F33073C.50607@slackverse.org> On 02/09/2012 12:11 AM, Rich Shepard wrote: > I recommend a change to postfix.SlackBuild to include cyrus SASL as well > as dovecot SASL. The latter works only with smtpd while the former is > required for smtp and needed by anyone who has to relay outgoing mail > through an ISP's mail servers. > > After 15 years with a static IP address the telco providing the DSL line > between here and our ISP changed us all to DHCP _and_ blocked outgoing port > 25. This means that we need to relay outbound mail through our ISP. After a > day-and-a-half of searching the Web and speaking with experienced network > admins I figured out how to fix my mail service, incoming and outgoing. > I'll > share that here to explain how to add cyrus to the build script, and what > change I needed to make to main.cf. > > In the SlackBuild script I changed to > > # Build with dovecot sasl by default, cyrus/dovecot are supported > SASL=${SASL:-cyrus} > > and > > make makefiles \ > CCARGS="-DUSE_SASL_AUTH -DUSE_TLS $SASLARGS $DBARGS -DUSE_CYRUS_SASL" \ > AUXLIBS="-lssl -lcrypto $SASLLIBS $DBLIBS" > > In /etc/postfix/main.cf I had to set smtpd_sasl_auth_enable to no and > comment out all other references to smtpd_sasl, then ensure that > smtp_sasl_auth_enable = yes, and the other smtp_sasl-related options were > properly set. > > Rich > > _______________________________________________ > 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 fail to see the point of all this, if you need cyrus it should be enough to just do, without any modifications: SASL=cyrus ./postfix.SlackBuild Alan included my patches for cyrus into postfix slackbuild some time ago, and afaik it should work fine, I run the same on a few of my mail servers. Altho I would have also preffered if he went with cyrus as a default option, since it comes in stock slackware, he is also maintaining a dovecot slackbuild, so I guess it is just easier for him. Or do I completly fail to see what you are talking about? :-) Best, mario From rshepard at appl-ecosys.com Wed Feb 8 23:56:11 2012 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 8 Feb 2012 15:56:11 -0800 (PST) Subject: [Slackbuilds-users] Recommended Change to postfix.SlackBuild In-Reply-To: <4F33073C.50607@slackverse.org> References: <4F33073C.50607@slackverse.org> Message-ID: On Thu, 9 Feb 2012, Mario wrote: > I fail to see the point of all this, if you need cyrus it should be enough > to just do, without any modifications: > > SASL=cyrus ./postfix.SlackBuild Mario, I did not know of this syntax. I found a linuxquestions.org thread that pointed me to adding CCARGS for cyrus. > Alan included my patches for cyrus into postfix slackbuild some time ago, > and afaik it should work fine, I run the same on a few of my mail servers. > Altho I would have also preffered if he went with cyrus as a default > option, since it comes in stock slackware, he is also maintaining a > dovecot slackbuild, so I guess it is just easier for him. If I'm the only one who did not know how to include cyrus in postfix, then there's no need to make changes. I've not before needed to relay outbound mail through our ISP so it was not an issue. Rich From molbolom at gmail.com Thu Feb 9 01:00:08 2012 From: molbolom at gmail.com (Charles Kauffman) Date: Wed, 8 Feb 2012 19:00:08 -0600 Subject: [Slackbuilds-users] My echinus and vifm slackbuilds are ready. In-Reply-To: <20120207112414.GA3642@kiras> References: <20120207112414.GA3642@kiras> Message-ID: On Tue, Feb 7, 2012 at 5:24 AM, Audrius Ka?ukauskas wrote: > On Mon, 2012-02-06 at 11:35:53 -0600, Charles Kauffman wrote: > > 2. > > In the echinus.SlackBuild > > sed -i "s;-Os;$SLKCFLAGS ;g" config.mk > > sed -i "s;.pixmap: ;.pixmap: \/usr\/share\/echinus\/_g" echinusrc > > sed -i "s/DOCPREFIX}\/echinus/DOCPREFIX}\/echinus-$VERSION/g" Makefile > > > > The source only contains Makefile and config.mk, no configure script. > So I > > replaced the compiler flag -Os with SLKCFLAGS, as well as had the script > > create a doc directory that had the version number appended to it. > > The second sed makes modifications to the rc file since problems can > occur > > when the program loads. > > > > So, does that look good, or should I just leave some of that alone? > > Looks good to me. As long as the changes don't break anything, I'd say > go for it. Just not sure if global (g) substitute is needed (it looks > for multiple regex matches in a single line). Also there should be a > semicolon at the end of second sed-line, no (and no need to escape > slashes)? > Thanks for the info on (g). Had thought it would stop after the first find/replace. Anyway it worked just fine without it, so you were right that it wasn't necessary. As for the escape slashes, I had forgotten about them while testing and editing the script until after I uploaded it to Slackbuilds, but then I don't think it would fail having them in there. Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From nishant at mnspace.net Thu Feb 9 02:16:43 2012 From: nishant at mnspace.net (Nishant Limbachia) Date: Wed, 08 Feb 2012 20:16:43 -0600 Subject: [Slackbuilds-users] Recommended Change to postfix.SlackBuild In-Reply-To: References: Message-ID: <4F332C8B.8040304@mnspace.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/08/2012 05:11 PM, Rich Shepard wrote: > I recommend a change to postfix.SlackBuild to include cyrus SASL as > well as dovecot SASL. The latter works only with smtpd while the > former is required for smtp and needed by anyone who has to relay > outgoing mail through an ISP's mail servers. > > After 15 years with a static IP address the telco providing the DSL > line between here and our ISP changed us all to DHCP _and_ blocked > outgoing port 25. This means that we need to relay outbound mail > through our ISP. After a day-and-a-half of searching the Web and > speaking with experienced network admins I figured out how to fix > my mail service, incoming and outgoing. I'll > share that here to explain how to add cyrus to the build script, > and what change I needed to make to main.cf. > > In the SlackBuild script I changed to > > # Build with dovecot sasl by default, cyrus/dovecot are supported > SASL=${SASL:-cyrus} > > and > > make makefiles \ CCARGS="-DUSE_SASL_AUTH -DUSE_TLS $SASLARGS > $DBARGS -DUSE_CYRUS_SASL" \ AUXLIBS="-lssl -lcrypto $SASLLIBS > $DBLIBS" > > In /etc/postfix/main.cf I had to set smtpd_sasl_auth_enable to no > and comment out all other references to smtpd_sasl, then ensure > that smtp_sasl_auth_enable = yes, and the other smtp_sasl-related > options were properly set. > > Rich > > _______________________________________________ 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 use my own mail server and relay using my ISP provided email account. AFAIK, you need both dovecot and cyrus. Here's my own personal modification to postfix slackbuild. I've included another option "both" that will include both cyrus and dovecot support. I've used this mod to build last 3 or 4 versions of postfix and haven't had any issue. # Build with dovecot sasl by default, cyrus/dovecot are supported SASL=${SASL:-dovecot} case "$SASL" in dovecot) SASLARGS='-DDEF_SERVER_SASL_TYPE=\"dovecot\"' SASLLIBS="" ;; cyrus) SASLARGS='-DUSE_CYRUS_SASL -I/usr/include/sasl' SASLLIBS="-L/usr/lib${LIBDIRSUFFIX}/sasl2 -lsasl2" ;; both) SASLARGS='-DDEF_SERVER_SASL_TYPE=\"dovecot\" - -DUSE_CYRUS_SASL -I/$ SASLLIBS="-L/usr/lib${LIBDIRSUFFIX}/sasl2 -lsasl2" ;; *) SASLARGS='' SASLLIBS="" ;; esac Hope that helps, - -- Nishant Limbachia nishant at mnspace.net GPG Key: 0x0FF9D6D5 GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAk8zLIsACgkQeG5dog/51tW+jQCY7FuRTOSpWUoyDljjyc5nURpO HwCeNINrwKLbvDutgligtz41c0Q//mI= =4vEP -----END PGP SIGNATURE----- From rob0 at slackbuilds.org Thu Feb 9 04:20:44 2012 From: rob0 at slackbuilds.org (Rob McGee) Date: Wed, 8 Feb 2012 22:20:44 -0600 Subject: [Slackbuilds-users] Recommended Change to postfix.SlackBuild In-Reply-To: <4F332C8B.8040304@mnspace.net> References: <4F332C8B.8040304@mnspace.net> Message-ID: <20120209042044.GB14195@harrier.slackbuilds.org> On Wed, Feb 08, 2012 at 08:16:43PM -0600, Nishant Limbachia wrote: > Here's my own personal modification to postfix slackbuild. I've > included another option "both" that will include both cyrus and > dovecot support. > > I've used this mod to build last 3 or 4 versions of postfix and > haven't had any issue. Nevertheless, it's not necessary. Nothing is linked for Dovecot; when Cyrus SASL's enabled, so's Dovecot. Two for the bargain price of one. > # Build with dovecot sasl by default, cyrus/dovecot are supported > SASL=${SASL:-dovecot} > case "$SASL" in > dovecot) SASLARGS='-DDEF_SERVER_SASL_TYPE=\"dovecot\"' > SASLLIBS="" ;; > cyrus) SASLARGS='-DUSE_CYRUS_SASL -I/usr/include/sasl' > SASLLIBS="-L/usr/lib${LIBDIRSUFFIX}/sasl2 -lsasl2" ;; > both) SASLARGS='-DDEF_SERVER_SASL_TYPE=\"dovecot\" This is merely to set the default value for smtpd_sasl_type - it does not hurt to leave that at "cyrus" and set "dovecot" value in main.cf. Perhaps if anything needs patched, consider the README, specifically: " users. Thus, the outside has a sendmail-ish flavor, but the inside is completely different. This script builds postfix with support for Dovecot SASL but does not include any support for Cyrus-SASL. If you need to enable support for Cyrus see SASL_README in the source code. You can also enable support for MySQL and Postgres. This script should find support for BerkleyDB and PCRE automagically, so no special options are required. Further, this script builds postfix with TLS support and requires that openssl be installed. openssl-solibs is not enough. You can find a SlackBuild script for Dovecot at http://www.SlackBuilds.org/ but you do not need to install it to use this package without SASL. A couple things to remember about postfix: " It's not wrong. It's just a little misleading (or omissive) on how to enable Cyrus SASL. Surely anyone who would need/want Cyrus SASL needs to visit the SASL_README, and anyone who reads the postfix.SlackBuild ought to be able to figure out to pass it "SASL=cyrus". I had planned to offer a patch, but it's late in the evening here, and I *dare* not mess with Alan's beautiful, near perfect, brick text at this hour. :) But I can match it - and I can do so without resorting to cheats like doubled spaces. /dev/rob0: master of the brickroll. Thick as a brick! > - -DUSE_CYRUS_SASL -I/$ > SASLLIBS="-L/usr/lib${LIBDIRSUFFIX}/sasl2 -lsasl2" ;; > *) SASLARGS='' > SASLLIBS="" ;; > esac > > Hope that helps, -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From klaatu at straightedgelinux.com Fri Feb 10 01:47:02 2012 From: klaatu at straightedgelinux.com (Klaatu) Date: Thu, 9 Feb 2012 20:47:02 -0500 Subject: [Slackbuilds-users] fontmatrix source is M.I.A. Message-ID: <201202092047.02243.klaatu@straightedgelinux.com> Some time ago, I volunteered to take over fontmatrix from its previous maintainer, Larry Hajali. Fontmatrix is at 0.6 as it has been for about 2 years now but today I noticed that its listed homepage, fontmatrix.net is dead, and its old homepage is basically dead (Drupal install with one surviving node). So, nobody's gonna be able to actually download fontmatrix for a while if the slackbuild continues to point to its true upstream sources. Bottom line: I have the fotnmatrix source code in my own personal backups. Shall I mirror? shall I mod the slackbuild so it just steals it from a trusted mirror like a Fedora RPM dist? Thoughts? - klaatu From hba.nihilismus at gmail.com Sat Feb 11 04:21:14 2012 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Fri, 10 Feb 2012 22:21:14 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205223024.3d08d2e4@liberty.rlwhome.lan> Message-ID: On Tue, Feb 7, 2012 at 8:40 AM, Matteo Bernardini wrote: > sorry for the delay, but I was fiddling with the stuff :) > > trying to ease maintaining also for end users and to follow Robby's > concerns, I've adapted the qemu slackbuild to build also qemu-kvm and > make a single package (by default, but there's a switch to disable > building it). > > it's an experiment I assembled very fast but seems to work on my machines. > Well, the idea it seems good to me rather than having two packages with two different maintainers for the "same" thing :). What's other's opinion? -- - hba | Antonio Hern?ndez Blas | Mexico, Mx. http://hba.dyndns.info | http://barrapunto.com/~hba/ | irc://irc.freenode.org/hba,isnick,needpass From yalhcru at gmail.com Sat Feb 11 08:08:25 2012 From: yalhcru at gmail.com (B Watson) Date: Sat, 11 Feb 2012 03:08:25 -0500 Subject: [Slackbuilds-users] fontmatrix source is M.I.A. In-Reply-To: <201202092047.02243.klaatu@straightedgelinux.com> References: <201202092047.02243.klaatu@straightedgelinux.com> Message-ID: On 2/9/12, Klaatu wrote: > I have the fotnmatrix source code in my own personal backups. Shall I > mirror? > shall I mod the slackbuild so it just steals it from a trusted mirror like a > Fedora RPM dist? Either is a good choice, IMO. Just make sure that, if you use something like a fedora or debian mirror, use one whose URL isn't going to change, and which doesn't delete old versions when they upgrade their package. FreeBSD and Gentoo are pretty good in that regard. Mirroring it yourself is also good, if you have a place to keep it. From audrius at neutrino.lt Sat Feb 11 20:34:09 2012 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Sat, 11 Feb 2012 22:34:09 +0200 Subject: [Slackbuilds-users] Request to update Redis SlackBuild from slackbuilds.org In-Reply-To: <4F36CE5F.8030201@yahoo.com> References: <20120211201724.GA3554@kiras> <4F36CE5F.8030201@yahoo.com> Message-ID: <20120211203409.GA4512@kiras> On Sat, 2012-02-11 at 14:23:59 -0600, Kuroi Kenshi wrote: > Hi, > > I've moved on to another Linux distro since the time that I > published the Redis slackbuild. You're more than welcome to take > over maintance. Thanks! CC'ing to SBo mailing list. > On 02/11/2012 02:17 PM, Audrius Ka?ukauskas wrote: > >Hi, > > > >I was going to play with Redis and noticed that the version your > >SlackBuild builds is 1.02 (which is no longer available at the provided > >URL), while the current version at http://redis.io/ is 2.4.7. > > > >Could you update Redis build script for the latest version? If you're > >not interested anymore, I could take over its maintenance. -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From t3slider at gmail.com Sat Feb 11 23:16:59 2012 From: t3slider at gmail.com (T3slider) Date: Sat, 11 Feb 2012 18:16:59 -0500 Subject: [Slackbuilds-users] makemkv removal Message-ID: <20120211231658.GA3549@KeithPC.phub.net.cable.rogers.com> MakeMKV is in approved, so I cannot pull the application. There is a new version and the devs like to pull the file. Could an admin remove this version so I can submit the next? Alternatively, the DOWNLOAD links could just be changed to DOWNLOAD="http://www.makemkv.com/download/old/makemkv_v1.7.1_oss.tar.gz http://www.makemkv.com/download/old/makemkv_v1.7.1_bin.tar.gz" where the old files were moved to and I could just submit an update whenever the next SBo update goes public. -T3slider From erik at slackbuilds.org Sat Feb 11 23:38:50 2012 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 11 Feb 2012 17:38:50 -0600 Subject: [Slackbuilds-users] makemkv removal In-Reply-To: <20120211231658.GA3549@KeithPC.phub.net.cable.rogers.com> References: <20120211231658.GA3549@KeithPC.phub.net.cable.rogers.com> Message-ID: <20120211173850.05c9d2e0@shaggy.doo> On Sat, 11 Feb 2012 18:16:59 -0500 T3slider wrote: > MakeMKV is in approved, so I cannot pull the application. There is a > new version and the devs like to pull the file. Could an admin remove > this version so I can submit the next? Alternatively, the DOWNLOAD > links could just be changed to I removed it for you. -- Erik Hanson From t3slider at gmail.com Sat Feb 11 23:54:24 2012 From: t3slider at gmail.com (T3slider) Date: Sat, 11 Feb 2012 18:54:24 -0500 Subject: [Slackbuilds-users] makemkv removal In-Reply-To: <20120211173850.05c9d2e0@shaggy.doo> References: <20120211231658.GA3549@KeithPC.phub.net.cable.rogers.com> <20120211173850.05c9d2e0@shaggy.doo> Message-ID: <20120211235424.GB3549@KeithPC.phub.net.cable.rogers.com> Thanks, and resubmitted. -T3slider On Sat, Feb 11, 2012 at 05:38:50PM -0600, Erik Hanson wrote: > On Sat, 11 Feb 2012 18:16:59 -0500 > T3slider wrote: > > > MakeMKV is in approved, so I cannot pull the application. There is a > > new version and the devs like to pull the file. Could an admin remove > > this version so I can submit the next? Alternatively, the DOWNLOAD > > links could just be changed to > > I removed it for you. > > > -- > Erik Hanson > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From dominian at slackadelic.com Sun Feb 12 01:40:31 2012 From: dominian at slackadelic.com (Matt Hayes) Date: Sat, 11 Feb 2012 20:40:31 -0500 Subject: [Slackbuilds-users] fontmatrix source is M.I.A. In-Reply-To: <201202092047.02243.klaatu@straightedgelinux.com> References: <201202092047.02243.klaatu@straightedgelinux.com> Message-ID: <4F37188F.6040100@slackadelic.com> On 2/9/2012 8:47 PM, Klaatu wrote: > Some time ago, I volunteered to take over fontmatrix from its previous > maintainer, Larry Hajali. > > Fontmatrix is at 0.6 as it has been for about 2 years now but today I noticed > that its listed homepage, fontmatrix.net is dead, and its old homepage is > basically dead (Drupal install with one surviving node). > > So, nobody's gonna be able to actually download fontmatrix for a while if the > slackbuild continues to point to its true upstream sources. > > > Bottom line: > > I have the fotnmatrix source code in my own personal backups. Shall I mirror? > shall I mod the slackbuild so it just steals it from a trusted mirror like a > Fedora RPM dist? > > Thoughts? > > - klaatu I host a few source files on http://slackbuilds.slackadelic.com for sources that have 'disappeared' or change without warning. If ya need it, just let me know where the source is and what the category and name is and I'll get it setup. You can even speak with Robby about it. Done a few for slackbuilds over the years. -Matt -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4926 bytes Desc: S/MIME Cryptographic Signature URL: From rworkman at slackbuilds.org Sun Feb 12 04:46:57 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 11 Feb 2012 22:46:57 -0600 Subject: [Slackbuilds-users] Updates - 20120212.1 Message-ID: <20120211224657.30bcd00e@liberty.rlwhome.lan> Sun Feb 12 03:20:32 UTC 2012 academic/R: Updated for version 2.14.1. academic/gchemutils: Updated for version 0.12.10. academic/seaview: Updated for version 4.3.3. audio/aqualung: Build bump, added an ffmpeg patch from upstream. audio/clementine: Small change to README. audio/pianobar: Updated for version 2012.01.10. desktop/PyPanel: Added (a lightweight panel/taskbar for X11) desktop/faenza-xfce: Fixed download link; some cosmetic changes desktop/jwm: Added (Joe's Window Manager) desktop/netwmpager: Added (an enhanced version of the original) desktop/scrotwm: Updated for version 0.10.0. desktop/wally: Updated for version 2.4.4. development/acpica: Updated for version 20120111. development/devhelp: Added (an API documentation browser for GTK+ and GNOME) development/gsoap: Updated for version 2.8.6. development/processing: Fixed name of build script games/doom_shareware_data: Added (game data from the shareware Doom) games/doomseeker: Added (server browser for Doom) games/freedoom: Added (free replacement for Doom/Doom2 game data) games/gnubg: Updated for version 20120116. games/heretic_shareware_data: Added (shareware Heretic game data) games/hexen_demo_data: Added (game data from Hexen demo release) games/odamex: Added (Online Doom Multiplayer Experience) games/skulltag: Added (port iof the original Doom and Doom II) graphics/dcraw: Updated for version 9.12. libraries/cdk: Updated for version 5.0_20110517. libraries/cssutils: Updated for version 0.9.8. libraries/eigen3: Added (c++ math library) libraries/libaacs: Added (AACS specification implementation) libraries/libaal: Added (reiser4 application abstraction library) libraries/libmnl: Updated for version 1.0.2. libraries/libnetfilter_conntrack: Updated for version 1.0.0. libraries/libnetfilter_log: Updated for version 1.0.1. libraries/libnetfilter_queue: Updated for version 1.0.1. libraries/libunrar: Added (The UnRAR library) libraries/mechanize: Updated for version 0.2.5. libraries/muParser: Updated for version 2.1.0. libraries/podofo: Updated for version 0.9.1. misc/zyGrib: Build bump, added configure files in the source. network/conntrack-tools: Updated for version 1.0.1. network/fldigi: Updated for version 3.21.33. network/heimdal: Updated for version 1.5.2. network/konversation: Updated for version 1.4. network/openvswitch: Updated for version 1.3.0. network/opera: Updated for version 11.61. network/reaver: Added (brute force attack against Wifi Protected Setup) network/wireshark: Updated for version 1.6.5. network/youtube-dl: Updated for version 2012.01.08b. office/kchmviewer: Updated for version 6.0. office/libreoffice-langpack: Updated for version 3.4.5. office/libreoffice: Updated for version 3.4.5. office/scribus: Updated for version 1.4.0. office/tellico: Updated for version 2.3.5. python/cssutils: Moved from Libraries python/lxml: Updated for version 2.3.3. python/mechanize: Moved from Libraries system/acpi: Updated for version 1.6. system/grub2: Minor bug fix. system/launchpadd: Removed, deprecated since 13.37. system/memtest86: Added (comprehensive, stand-alone memory diagnostic) system/rar2fs: Added (a FUSE based file system for RAR archives) system/reiser4progs: Added (utilities for the reiser4 filesystem) system/rxvt-unicode: Updated for version 9.15. system/slack-utils: Updated for version 0.7.2. system/virtualbox-addons: Updated for version 4.1.8. system/virtualbox-kernel-addons: Updated for version 4.1.8. system/virtualbox-kernel: Updated for version 4.1.8. system/virtualbox: Updated for version 4.1.8. system/webcore-fonts: Fontconfig information added to README. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From cancellor2 at gmail.com Sun Feb 12 12:25:02 2012 From: cancellor2 at gmail.com (Fridrich von Stauffenberg) Date: Sun, 12 Feb 2012 14:25:02 +0200 Subject: [Slackbuilds-users] Hardcoded OUTPUT in eigen3.SlackBuild Message-ID: <4F37AF9E.3090807@gmail.com> libraries/eigen3.SlackBuild, line 99: > /sbin/makepkg -l y -c n /tmp/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} If there's an overridden $OUTPUT, I suppose that would be a bit confusing to have the package created elsewhere. In addition, sbopkg will fail to auto-install it. Maybe 's/\/tmp/$OUTPUT/'? From rworkman at slackbuilds.org Sun Feb 12 17:01:33 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 11:01:33 -0600 Subject: [Slackbuilds-users] Hardcoded OUTPUT in eigen3.SlackBuild In-Reply-To: <4F37AF9E.3090807@gmail.com> References: <4F37AF9E.3090807@gmail.com> Message-ID: <20120212110133.431c4614@liberty.rlwhome.lan> On Sun, 12 Feb 2012 14:25:02 +0200 Fridrich von Stauffenberg wrote: > libraries/eigen3.SlackBuild, line 99: > > > /sbin/makepkg -l y -c > > n /tmp/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} > > If there's an overridden $OUTPUT, I suppose that would be a bit > confusing to have the package created elsewhere. In addition, sbopkg > will fail to auto-install it. Maybe 's/\/tmp/$OUTPUT/'? commit 6d0f7c0782f883893aceb98da03262b73e353437 Author: Fridrich von Stauffenberg Date: Sun Feb 12 10:34:47 2012 -0600 libraries/eigen3: Fixed hardcoded package location Signed-off-by: Robby Workman diff --git a/libraries/eigen3/eigen3.SlackBuild b/libraries/eigen3/eigen3.SlackBuild index 29908a5..7e10d6b 100644 --- a/libraries/eigen3/eigen3.SlackBuild +++ b/libraries/eigen3/eigen3.SlackBuild @@ -25,7 +25,7 @@ PRGNAM=eigen3 VERSION=${VERSION:-3.0.4} -BUILD=${BUILD:-1} +BUILD=${BUILD:-2} TAG=${TAG:-_SBo} TARVERSION=eigen-13a11181fc5a @@ -96,4 +96,4 @@ mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cd $PKG -/sbin/makepkg -l y -c n /tmp/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} +/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 12 17:30:20 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 11:30:20 -0600 Subject: [Slackbuilds-users] Avidemux In-Reply-To: References: <4F107C2D.8020400@gmail.com> Message-ID: <20120212113020.540923cd@liberty.rlwhome.lan> On Sat, 14 Jan 2012 07:34:01 +0500 Ozan T?rky?lmaz wrote: > 2012/1/13 Niklas Nille ?kerstr?m : > > I updated avidemux to version 2.5.6 but i got one thing that i like > > your opinion about. > > The build makes 2 desktop files Qt and gtk? should i leave it like > > this? Or should only the Qt one be used in KDE and gtk elsewhere? > > This would be done with the options OnlyShownIn=KDE; and > > NotShowIn=KDE; in the desktop files. > > I support this as both GUIs are pretty much same expect the library > they use. Not too terribly long ago, I would have supported this, but I'm not so sure now. See, there's recently a non-KDE-but-built-on-QT DE out there called razorqt, and I think those users would prefer to use the Qt-linked avidemux. I know the desktop files can take multiple values to the OnlyShowIn and/or NotShowIn variables, but razorqt doesn't seem "registered" (whatever that means). It's probably a simple-ish fix, but my give-a-damn just hit empty. :) All that said, it's ultimately your call. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 12 17:34:17 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 11:34:17 -0600 Subject: [Slackbuilds-users] Kino In-Reply-To: <4F0AC56F.1060906@gmail.com> References: <4F0ABE8A.90100@gmail.com> <4F0AC56F.1060906@gmail.com> Message-ID: <20120212113417.4957db55@liberty.rlwhome.lan> On Mon, 09 Jan 2012 10:46:07 +0000 Pierre Cazenave wrote: > On 09/01/2012 10:41, Matteo Bernardini wrote: > > I don't use kino that much, but it seems to build here (also with > > ffmpeg-0.9) with this patch from debian/ubuntu > > > > http://cgit.ponce.cc/slackbuilds/plain/multimedia/kino/1.3.4_fix_ftbfs_libav.patch > > > > and, FYI, as I'm on -current, I use also this other patch (needed > > for kernels> 2.6.37) > > > > http://cgit.ponce.cc/slackbuilds/plain/multimedia/kino/v4l1_includes.diff > > > > Hi Matteo, > > I received an email yesterday from someone trying to build kino > saying they were unable to do so, and so I pointed them to your > repository since I imagined you would have found a fix if one > existed. However, I am writing up my thesis at the moment, and time > is tight, so I am still unable to maintain kino. To be honest, I > haven't had a lot of time for any of my SlackBuilds (even those for > programs I use daily). I've just removed this in my git branch. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 12 17:37:34 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 11:37:34 -0600 Subject: [Slackbuilds-users] Optional dep kipi-plugins In-Reply-To: <4F28C17F.5030802@gmail.com> References: <4F28C17F.5030802@gmail.com> Message-ID: <20120212113734.1821c18a@liberty.rlwhome.lan> On Wed, 01 Feb 2012 05:37:19 +0100 Niklas Nille ?kerstr?m wrote: > opencv should be added as optional dependencies for kipi-plugins. > opencv adds support for RemoveRedEyes. Committed in my git branch. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 12 17:38:40 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 11:38:40 -0600 Subject: [Slackbuilds-users] fontmatrix source is M.I.A. In-Reply-To: <201202092047.02243.klaatu@straightedgelinux.com> References: <201202092047.02243.klaatu@straightedgelinux.com> Message-ID: <20120212113840.45c5a590@liberty.rlwhome.lan> On Thu, 9 Feb 2012 20:47:02 -0500 Klaatu wrote: > Some time ago, I volunteered to take over fontmatrix from its > previous maintainer, Larry Hajali. > > Fontmatrix is at 0.6 as it has been for about 2 years now but today I > noticed that its listed homepage, fontmatrix.net is dead, and its old > homepage is basically dead (Drupal install with one surviving node). > > So, nobody's gonna be able to actually download fontmatrix for a > while if the slackbuild continues to point to its true upstream > sources. > > > Bottom line: > > I have the fotnmatrix source code in my own personal backups. Shall > I mirror? shall I mod the slackbuild so it just steals it from a > trusted mirror like a Fedora RPM dist? > > Thoughts? Any of the thoughts offered by others are valid, so you decide. :) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From nille.kungen at gmail.com Sun Feb 12 17:37:57 2012 From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_Nille_=C5kerstr=F6m?=) Date: Sun, 12 Feb 2012 18:37:57 +0100 Subject: [Slackbuilds-users] libunrar Message-ID: <4F37F8F5.1040307@gmail.com> Since libunrar uses the same source as unrar maybe the SlackBuilds should be merged. Also whats the point with "include" containing most of the source code? Most distributions only include dll.hpp Best regards Nille From kingbeowulf at gmail.com Sun Feb 12 19:33:08 2012 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 12 Feb 2012 11:33:08 -0800 Subject: [Slackbuilds-users] Kino In-Reply-To: <20120212113417.4957db55@liberty.rlwhome.lan> References: <4F0ABE8A.90100@gmail.com> <4F0AC56F.1060906@gmail.com> <20120212113417.4957db55@liberty.rlwhome.lan> Message-ID: On Sun, Feb 12, 2012 at 9:34 AM, Robby Workman wrote: > On Mon, 09 Jan 2012 10:46:07 +0000 > Pierre Cazenave wrote: > > > On 09/01/2012 10:41, Matteo Bernardini wrote: > > > I don't use kino that much, but it seems to build here (also with > > > ffmpeg-0.9) with this patch from debian/ubuntu > > > > > > > http://cgit.ponce.cc/slackbuilds/plain/multimedia/kino/1.3.4_fix_ftbfs_libav.patch > > > > > > and, FYI, as I'm on -current, I use also this other patch (needed > > > for kernels> 2.6.37) > > > > > > > http://cgit.ponce.cc/slackbuilds/plain/multimedia/kino/v4l1_includes.diff > > > > > > > Hi Matteo, > > > > I received an email yesterday from someone trying to build kino > > saying they were unable to do so, and so I pointed them to your > > repository since I imagined you would have found a fix if one > > existed. However, I am writing up my thesis at the moment, and time > > is tight, so I am still unable to maintain kino. To be honest, I > > haven't had a lot of time for any of my SlackBuilds (even those for > > programs I use daily). > > > I've just removed this in my git branch. > > -RW > > I used to be a heavy kino user but upstream development has stalled in favor of MLT/kdenlive, AFAIK; mailing list and forums are about dead. A related part, dvgrab, still works well to pull DV data off the camera, which you can then use with any number of editors. PiTiVi, Kdenlive and Openshot are better editors. Kdenlive can pull data from most firewire DV cams as well. Now, I just need to get to that 50+GB of family home video.... -Ed -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Sun Feb 12 20:15:34 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 14:15:34 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205223024.3d08d2e4@liberty.rlwhome.lan> Message-ID: <20120212141534.4e15c622@liberty.rlwhome.lan> On Tue, 7 Feb 2012 03:40:24 -0600 Antonio Hern?ndez Blas wrote: > On Sun, Feb 5, 2012 at 10:30 PM, Robby Workman > wrote: > > > > The change is because "users" makes a better *default* (IMHO); > > there's no real reason to require a special group that's not > > already present, so I'd prefer the default to be this way. > > > > Ah ok, if this change is approved and used in the future i would > recommend to update system/kvm-kmod/README to delete the mention of > the kvm group. BTW, there's a new version [1] ;) Stu has submitted it, and I made the udev rules change on this end. > > Simply having a conflict is fine, so long as the contents are the > > same, and they are for these other conflicts, so no, there's no > > need to rename them. ?Overwriting these files is completely harmless > > regardless of which package is installed last. ?That is *not* the > > case for the qemu-system-x86_64 binary. > > > > Interesting, because ATM system/qemu (0.14.1) and system/qemu-kvm > (1.0) are in different version which means they have different content > and there's a conflict between them, but ATM!. So let me see, if > qemu-kvm would depend on qemu then it would be needed to update them > always at the same version so they can play nice or am i seeing a > problem where there's no problem? :) Well, the version diffs need to be fixed for sure... Andrew, are you still interested in this, or do you want someone else to handle it? On a related note, have you seen the rest of this thread? :) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Feb 12 20:24:28 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 14:24:28 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205223024.3d08d2e4@liberty.rlwhome.lan> Message-ID: <20120212142428.4f67f5dc@liberty.rlwhome.lan> On Tue, 7 Feb 2012 15:40:13 +0100 Matteo Bernardini wrote: > sorry for the delay, but I was fiddling with the stuff :) > > trying to ease maintaining also for end users and to follow Robby's > concerns, I've adapted the qemu slackbuild to build also qemu-kvm and > make a single package (by default, but there's a switch to disable > building it). > > it's an experiment I assembled very fast but seems to work on my > machines. After a small amount of tweaking, here's the result: http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-merged (there are two commits, with fffd199a being the important one. Another approach is this one: http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-kvm (which has already been mentioned for review). Given the options, I think I like the first one (qemu-merged) better, BUT there's a very real potential to miss some files that aren't included in the qemu package (see TODO: in the build script), and who knows what kind of damned-near-impossible- to-figure-out errors that would induce in qemu runtime :/ The second approach is not as "clean" as the first, but it's less error-prone in the future probably. In both cases, the qemu and qemu-kvm versions have to be in sync, so that's an issue that we need to fix regardless... All that said, perhaps there's another approach that I'm missing, and if so, I'd like to hear it. I'm obviously not in favor of leaving things as they are, but other suggestions will certainly be entertained... -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Sun Feb 12 21:59:50 2012 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 12 Feb 2012 13:59:50 -0800 Subject: [Slackbuilds-users] Avidemux In-Reply-To: <20120212113020.540923cd@liberty.rlwhome.lan> References: <4F107C2D.8020400@gmail.com> <20120212113020.540923cd@liberty.rlwhome.lan> Message-ID: I vote for leaving the desktop files generic ie not DE dependent and add a switch to the slackbuild as to whether to install the Qt vs GTK version. That should allow compatibility with all sorts of wm and/or DE. On 2/12/12, Robby Workman wrote: > On Sat, 14 Jan 2012 07:34:01 +0500 > Ozan T?rky?lmaz wrote: > >> 2012/1/13 Niklas Nille ?kerstr?m : >> > I updated avidemux to version 2.5.6 but i got one thing that i like >> > your opinion about. >> > The build makes 2 desktop files Qt and gtk? should i leave it like >> > this? Or should only the Qt one be used in KDE and gtk elsewhere? >> > This would be done with the options OnlyShownIn=KDE; and >> > NotShowIn=KDE; in the desktop files. >> >> I support this as both GUIs are pretty much same expect the library >> they use. > > > Not too terribly long ago, I would have supported this, but I'm not > so sure now. See, there's recently a non-KDE-but-built-on-QT DE > out there called razorqt, and I think those users would prefer to > use the Qt-linked avidemux. I know the desktop files can take > multiple values to the OnlyShowIn and/or NotShowIn variables, but > razorqt doesn't seem "registered" (whatever that means). It's > probably a simple-ish fix, but my give-a-damn just hit empty. :) > > All that said, it's ultimately your call. > > -RW > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From slackbuilds at ssmbox.net Sun Feb 12 22:15:41 2012 From: slackbuilds at ssmbox.net (Stu Miller) Date: Sun, 12 Feb 2012 15:15:41 -0700 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120212142428.4f67f5dc@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205223024.3d08d2e4@liberty.rlwhome.lan> <20120212142428.4f67f5dc@liberty.rlwhome.lan> Message-ID: <98c7800de46a475e4ebd6a6ef6064c7d@guest8> On 12.02.2012 13:24, Robby Workman wrote: > On Tue, 7 Feb 2012 15:40:13 +0100 > Matteo Bernardini wrote: > >> sorry for the delay, but I was fiddling with the stuff :) trying to ease maintaining also for end users and to follow Robby's concerns, I've adapted the qemu slackbuild to build also qemu-kvm and make a single package (by default, but there's a switch to disable building it). it's an experiment I assembled very fast but seems to work on my machines. > > After a small amount of tweaking, here's the result: > http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-merged > (there are two commits, with fffd199a being the important one. > > Another approach is this one: > http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-kvm > (which has already been mentioned for review). > > Given the options, I think I like the first one (qemu-merged) > better, BUT there's a very real potential to miss some files > that aren't included in the qemu package (see TODO: in the > build script), and who knows what kind of damned-near-impossible- > to-figure-out errors that would induce in qemu runtime :/ > > The second approach is not as "clean" as the first, but it's less > error-prone in the future probably. > > In both cases, the qemu and qemu-kvm versions have to be in sync, > so that's an issue that we need to fix regardless... > > All that said, perhaps there's another approach that I'm missing, > and if so, I'd like to hear it. I'm obviously not in favor of > leaving things as they are, but other suggestions will certainly > be entertained... > > -RW IMHO our merge of the qemu-kvm SlackBuild into qemu SlackBuild is premature. It remains the intention of the KVM Team to discontinue qemu-kvm once qemu properly merges the code from kvm. The KVM Team doesn't believe they are there yet so why do we? Stephan Hajnoczi: Should I use QEMU or KVM? [1] see the section: "What is the difference between qemu.git and qemu-kvm.git?" I recommend continued support of the qemu-kvm SlackBuild with focus on the x86 Intel, x86 AMD CPUs however the PowerPC and S390 CPUs should not be forgotten. All other qemu CPU emulation should be directed to the qemu SlackBuild until such time as the KVM Team says qemu-kvm is deprecated. Processor Support - KVM [2] It's a complicated issue. I hope I'm still tracking properly. Stu Links: ------ [1] http://blog.vmsplice.net/2011/03/should-i-use-qemu-or-kvm.html [2] http://www.linux-kvm.org/page/Processor_support -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Sun Feb 12 22:48:11 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 16:48:11 -0600 Subject: [Slackbuilds-users] Avidemux In-Reply-To: References: <4F107C2D.8020400@gmail.com> <20120212113020.540923cd@liberty.rlwhome.lan> Message-ID: <20120212164811.5069a6f7@liberty.rlwhome.lan> On Sun, 12 Feb 2012 13:59:50 -0800 King Beowulf wrote: > I vote for leaving the desktop files generic ie not DE dependent and > add a switch to the slackbuild as to whether to install the Qt vs GTK > version. That should allow compatibility with all sorts of wm and/or > DE. I don't like that approach either, because I suspect there are more people than just me who tend to swap back and forth among different environments, and/or systems that have multiple users on various DEs. I don't see any harm in installing both .desktop files, so long as one doesn't clobber the other... -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From artourter at gmail.com Sun Feb 12 23:04:30 2012 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sun, 12 Feb 2012 23:04:30 +0000 Subject: [Slackbuilds-users] broadcom-sta fails to compile with -current kernel 3.2.2 + patch Message-ID: Hi, I know that -current is not supported by SBo but I thought as I had to find the solution I might as well share. There is one change in the kernel now in -current which stop broadcom-sta from compiling. You can find more info at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656600 http://www.mindwerks.net/2011/11/wireless-bcm4312-3-2-kernel/ the latter link providing a patch to compile it properly with 3.2.x. However the patch would make the source not compile with previous kernels, so I have modified it to be generic I attach the patch here if people need it or for the maintainer to include it in the SBo script. a simple patch -p1 < $CMD/bc_wl_abiupdate.patch added in the slackbuild script will do the tick. Hope this helps Cheers Greg -------------- next part -------------- A non-text attachment was scrubbed... Name: bc_wl_abiupdate.patch Type: application/octet-stream Size: 510 bytes Desc: not available URL: From kingbeowulf at gmail.com Sun Feb 12 23:23:15 2012 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 12 Feb 2012 15:23:15 -0800 Subject: [Slackbuilds-users] Avidemux In-Reply-To: <20120212164811.5069a6f7@liberty.rlwhome.lan> References: <4F107C2D.8020400@gmail.com> <20120212113020.540923cd@liberty.rlwhome.lan> <20120212164811.5069a6f7@liberty.rlwhome.lan> Message-ID: Well, I've found multiple desktop files problematic on occasion. I tend to use Xfce and Lxde mostly but leave KDE installed for a handful of apps (just too lazy to strip out the good parts). Sometimes, multiple desktop files will cause multiple menu entries and weirdness. I think if its mostly a Qt vs. Gtk lib issue, just have a switch. Since some of us switch around, and we have both Qt and GTk libs installed by default, so we should just pick one compile option - both avidemux libs are not needed. Gtk apps run ok under a Qt DE and Qt apps run ok under a Gtk DE if the appropriate qt and/or gtk libs are installed. Just my 2 cents... -ed On 2/12/12, Robby Workman wrote: > On Sun, 12 Feb 2012 13:59:50 -0800 > King Beowulf wrote: > >> I vote for leaving the desktop files generic ie not DE dependent and >> add a switch to the slackbuild as to whether to install the Qt vs GTK >> version. That should allow compatibility with all sorts of wm and/or >> DE. > > > I don't like that approach either, because I suspect there are more > people than just me who tend to swap back and forth among different > environments, and/or systems that have multiple users on various > DEs. I don't see any harm in installing both .desktop files, so long > as one doesn't clobber the other... > > -RW > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From rworkman at slackbuilds.org Mon Feb 13 03:26:55 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 12 Feb 2012 21:26:55 -0600 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <98c7800de46a475e4ebd6a6ef6064c7d@guest8> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205223024.3d08d2e4@liberty.rlwhome.lan> <20120212142428.4f67f5dc@liberty.rlwhome.lan> <98c7800de46a475e4ebd6a6ef6064c7d@guest8> Message-ID: <20120212212655.431da12a@liberty.rlwhome.lan> On Sun, 12 Feb 2012 15:15:41 -0700 Stu Miller wrote: > IMHO our merge > of the qemu-kvm SlackBuild into qemu SlackBuild is premature. It > remains the intention of the KVM Team to discontinue qemu-kvm once > qemu properly merges the code from kvm. The KVM Team doesn't believe > they are there yet so why do we? Well, in a round-a-bout way, that's why I'm wanting to do what we're doing. We're not merging the *code* - we're merging the package. Well, all we're doing now is talking and making some proposals, trying to figure out the best way to do it, assuming we do it at all... > Stephan Hajnoczi: Should I use QEMU or KVM? [1] see > the section: "What is the difference between qemu.git and > qemu-kvm.git?" > [1] http://blog.vmsplice.net/2011/03/should-i-use-qemu-or-kvm.html See, that answer supposes that I want one or the other, but I want to do both. I have some x86 (virtual) machines [1] with which I want the enhanced KVM usage (based on discussion in #qemu on freenode, qemu-kvm has better KVM support than regular qemu using -enable-kvm switch), AND I also have some ARM (virtual) machines [2] with which I want to use regular qemu (based on same discussion, regular qemu is better for non-KVM, as it gets fixes that the qemu-kvm people do not (and should not) care about). The point is that I want BOTH qemu and qemu-kvm code on my host. > I recommend continued support of the qemu-kvm SlackBuild with focus on > the x86 Intel, x86 AMD CPUs however the PowerPC and S390 CPUs should > not be forgotten. All other qemu CPU emulation should be directed to > the qemu SlackBuild until such time as the KVM Team says qemu-kvm is > deprecated. > > Processor Support - KVM [2] > [2] http://www.linux-kvm.org/page/Processor_support > > It's a complicated issue. I hope I'm still tracking properly. It *is* a bit complicated, which is why I started this thread in the first place :) The least intrusive suggestion, which would be fine with me too, is this: 1. Update qemu to version 1.0. 2. Fix (or whatever term we'd like to use) to make qemu-kvm rename the binary. 3. Fix all of (as needed) qemu, qemu-kvm, and kvm-kmod to: a. use correct CFLAGS when building b. use "users" group by default for KVM I've got aqemu updated in my git repo, and I made the udev rules change in kvm-kmod also. Perhaps the best solution for now is to do these three things and see what happens from there. Andrew, mind if I bump qemu? -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From nille.kungen at gmail.com Mon Feb 13 13:26:22 2012 From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_Nille_=C5kerstr=F6m?=) Date: Mon, 13 Feb 2012 14:26:22 +0100 Subject: [Slackbuilds-users] Avidemux In-Reply-To: References: <4F107C2D.8020400@gmail.com> <20120212113020.540923cd@liberty.rlwhome.lan> <20120212164811.5069a6f7@liberty.rlwhome.lan> Message-ID: <4F390F7E.7080905@gmail.com> On 2012-02-13 00:23, King Beowulf wrote: > Well, I've found multiple desktop files problematic on occasion. I > tend to use Xfce and Lxde mostly but leave KDE installed for a handful > of apps (just too lazy to strip out the good parts). Sometimes, > multiple desktop files will cause multiple menu entries and weirdness. > > I think if its mostly a Qt vs. Gtk lib issue, just have a switch. > Since some of us switch around, and we have both Qt and GTk libs > installed by default, so we should just pick one compile option - both > avidemux libs are not needed. Gtk apps run ok under a Qt DE and Qt > apps run ok under a Gtk DE if the appropriate qt and/or gtk libs are > installed. > > Just my 2 cents... > > -ed > > > > On 2/12/12, Robby Workman wrote: >> On Sun, 12 Feb 2012 13:59:50 -0800 >> King Beowulf wrote: >> >>> I vote for leaving the desktop files generic ie not DE dependent and >>> add a switch to the slackbuild as to whether to install the Qt vs GTK >>> version. That should allow compatibility with all sorts of wm and/or >>> DE. >> >> I don't like that approach either, because I suspect there are more >> people than just me who tend to swap back and forth among different >> environments, and/or systems that have multiple users on various >> DEs. I don't see any harm in installing both .desktop files, so long >> as one doesn't clobber the other... >> >> -RW >> I could add an switch with both as default and qt or gtk by choice, or leave it as it is today. But i need to update the built since it doesn't compile anymore. From matteo.bernardini at gmail.com Mon Feb 13 14:05:26 2012 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 13 Feb 2012 15:05:26 +0100 Subject: [Slackbuilds-users] Avidemux In-Reply-To: <20120212113020.540923cd@liberty.rlwhome.lan> References: <4F107C2D.8020400@gmail.com> <20120212113020.540923cd@liberty.rlwhome.lan> Message-ID: 2012/2/12 Robby Workman : > I know the desktop files can take > multiple values to the OnlyShowIn and/or NotShowIn variables, but > razorqt doesn't seem "registered" (whatever that means). ?It's > probably a simple-ish fix, but my give-a-damn just hit empty. :) more info on this https://bugs.freedesktop.org/show_bug.cgi?id=41112 http://bit.ly/zEX7D8 in short, should be registered soon as "Razor". :) Matteo From abrouwers at gmail.com Mon Feb 13 14:15:34 2012 From: abrouwers at gmail.com (Andrew Brouwers) Date: Mon, 13 Feb 2012 09:15:34 -0500 Subject: [Slackbuilds-users] RFC: qemu and aqemu In-Reply-To: <20120212212655.431da12a@liberty.rlwhome.lan> References: <20120203142640.036a3d30@liberty.rlwhome.lan> <20120203153713.0c1ed224@liberty.rlwhome.lan> <20120203161953.431d6b53@liberty.rlwhome.lan> <26444ac2169dc8c1247b2e4da39f3854@guest8> <20120205223024.3d08d2e4@liberty.rlwhome.lan> <20120212142428.4f67f5dc@liberty.rlwhome.lan> <98c7800de46a475e4ebd6a6ef6064c7d@guest8> <20120212212655.431da12a@liberty.rlwhome.lan> Message-ID: Hi, > The least intrusive suggestion, which would be fine with me too, is this: > > 1. Update qemu to version 1.0. Sorry for the lag, since getting new hardware, I've switched completely to qemu-kvm as well. > 2. Fix (or whatever term we'd like to use) to make qemu-kvm rename the > ? binary. > 3. Fix all of (as needed) qemu, qemu-kvm, and kvm-kmod to: > ? a. use correct CFLAGS when building > ? b. use "users" group by default for KVM > > I've got aqemu updated in my git repo, and I made the udev rules change > in kvm-kmod also. ?Perhaps the best solution for now is to do these > three things and see what happens from there. > > Andrew, mind if I bump qemu? Feel free, if you've got it prepared. Otherwise, I can come up with something this week too. Best wishes, Andrew From vbatts at hashbangbash.com Mon Feb 13 16:14:22 2012 From: vbatts at hashbangbash.com (Vincent Batts) Date: Mon, 13 Feb 2012 11:14:22 -0500 Subject: [Slackbuilds-users] gem2tgz cleanup Message-ID: a couple of points for cycojesus, the DOWNLOAD in the info does not work well in an automated fashion, since it points to a generated tarball from a git tag. When wget'ed it results in a file with the name of the tag, not the expected tarball name. I would recommend attaching an actual tarball to the github page for this project. That way it'll get properly wget'ed (see https://github.com/cycojesus/gem2tgz/downloads) for the SBo admins, the page is not rendering the contents correctly either. http://slackbuilds.org/repository/13.37/development/gem2tgz/ Take care, vb http://hashbangbash.com/ From niels.horn at gmail.com Mon Feb 13 16:33:08 2012 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 13 Feb 2012 14:33:08 -0200 Subject: [Slackbuilds-users] gem2tgz cleanup In-Reply-To: References: Message-ID: On Mon, Feb 13, 2012 at 2:14 PM, Vincent Batts wrote: <...> > > for the SBo admins, the page is not rendering the contents correctly > either. http://slackbuilds.org/repository/13.37/development/gem2tgz/ > fixed... > Take care, > vb > http://hashbangbash.com/ -- Niels Horn From klaatu at straightedgelinux.com Mon Feb 13 16:49:31 2012 From: klaatu at straightedgelinux.com (Klaatu) Date: Mon, 13 Feb 2012 11:49:31 -0500 Subject: [Slackbuilds-users] sigil updated? Message-ID: <201202131149.31997.klaatu@straightedgelinux.com> I'm curious if anyone knows who uploaded the sigil update. I thought I'd taken over sigil from Larry H. but when I went to update the slackbuild, I saw that there was an update already pending. Was I mistaken in thinking I'd taken over Sigil? Or is this what they were talking about by the magical slackbuild faeries who update packages in the wee small hours of the night? Not using Sigil myself (I'm an emacs + nxml ebook creator, me'self) I don't really care if someone has taken Sigil :-) but at the same time, I don't want to abandon it unnecessarily. - klaatu From niels.horn at gmail.com Mon Feb 13 16:56:49 2012 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 13 Feb 2012 14:56:49 -0200 Subject: [Slackbuilds-users] sigil updated? In-Reply-To: <201202131149.31997.klaatu@straightedgelinux.com> References: <201202131149.31997.klaatu@straightedgelinux.com> Message-ID: On Mon, Feb 13, 2012 at 2:49 PM, Klaatu wrote: > I'm curious if anyone knows who uploaded the sigil update. > Yes, the admins know ;) > I thought I'd taken over sigil from Larry H. but when I went to update the > slackbuild, I saw that there was an update already pending. > That was documented on this list.... > Was I mistaken in thinking I'd taken over Sigil? ?Or is this what they were > talking about by the magical slackbuild faeries who update packages in the wee > small hours of the night? > No magic involved (that would have been fun!) - it was Larry himself. > Not using Sigil myself (I'm an emacs + nxml ebook creator, me'self) I don't > really care if someone has taken Sigil :-) but at the same time, I don't want > to abandon it unnecessarily. > > > - klaatu > Larry, Any comments? -- Niels Horn From rworkman at slackbuilds.org Mon Feb 13 17:29:59 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 13 Feb 2012 11:29:59 -0600 Subject: [Slackbuilds-users] Avidemux In-Reply-To: References: <4F107C2D.8020400@gmail.com> <20120212113020.540923cd@liberty.rlwhome.lan> Message-ID: <20120213112959.6f0213d6@liberty.rlwhome.lan> On Mon, 13 Feb 2012 15:05:26 +0100 Matteo Bernardini wrote: > 2012/2/12 Robby Workman : > > I know the desktop files can take > > multiple values to the OnlyShowIn and/or NotShowIn variables, but > > razorqt doesn't seem "registered" (whatever that means). ?It's > > probably a simple-ish fix, but my give-a-damn just hit empty. :) > > more info on this > > https://bugs.freedesktop.org/show_bug.cgi?id=41112 > > http://bit.ly/zEX7D8 > > in short, should be registered soon as "Razor". :) Awesome; thanks for checking. I'll make sure that gets into the -current tree... -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From larryhaja at gmail.com Mon Feb 13 19:01:11 2012 From: larryhaja at gmail.com (Larry Hajali) Date: Mon, 13 Feb 2012 11:01:11 -0800 Subject: [Slackbuilds-users] sigil updated? In-Reply-To: References: <201202131149.31997.klaatu@straightedgelinux.com> Message-ID: Yes, I did update sigil and I do have a list of packages I no longer own. Sigil was one of them on that list. It was my mistake that I uploaded the new version. I have since taken it down and dually noted that it is no longer mine. You can go ahead and update the package. --Larry On Mon, Feb 13, 2012 at 8:56 AM, Niels Horn wrote: > On Mon, Feb 13, 2012 at 2:49 PM, Klaatu wrote: >> I'm curious if anyone knows who uploaded the sigil update. >> > > Yes, the admins know ;) > >> I thought I'd taken over sigil from Larry H. but when I went to update the >> slackbuild, I saw that there was an update already pending. >> > > That was documented on this list.... > >> Was I mistaken in thinking I'd taken over Sigil? ?Or is this what they were >> talking about by the magical slackbuild faeries who update packages in the wee >> small hours of the night? >> > > No magic involved (that would have been fun!) - it was Larry himself. > >> Not using Sigil myself (I'm an emacs + nxml ebook creator, me'self) I don't >> really care if someone has taken Sigil :-) but at the same time, I don't want >> to abandon it unnecessarily. >> >> >> - klaatu >> > > Larry, > > Any comments? > > -- > Niels Horn > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From gwenhael.le.moine at gmail.com Mon Feb 13 21:40:33 2012 From: gwenhael.le.moine at gmail.com (Gwenhael Le Moine) Date: Mon, 13 Feb 2012 22:40:33 +0100 Subject: [Slackbuilds-users] gem2tgz cleanup In-Reply-To: References: Message-ID: 2012/2/13 Vincent Batts > a couple of points > > for cycojesus, the DOWNLOAD in the info does not work well in an > automated fashion, since it points to a generated tarball from a git > tag. When wget'ed it results in a file with the name of the tag, not > the expected tarball name. I would recommend attaching an actual > tarball to the github page for this project. That way it'll get > properly wget'ed (see https://github.com/cycojesus/gem2tgz/downloads) > Thanks, I've "fixed" this and submitted an update. This problem did bothered me but somehow at the time I missed that github possibility (or it just plain wasn there yet.) Cheers. -------------- next part -------------- An HTML attachment was scrubbed... URL: From audrius at neutrino.lt Thu Feb 16 16:56:47 2012 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Thu, 16 Feb 2012 18:56:47 +0200 Subject: [Slackbuilds-users] libffi conflicts with gcc-java Message-ID: <20120216165647.GA10264@kiras> Hi, I have noticed that not too long ago libffi was added to SBo. It was included in the past and removed on Slackware 13.0 release with the following note in the changelog: libraries/libffi: Removed; conflicts with gcc-java-4.3.3. This is still true for the newest gcc-java package. There's one thing though, which gcc-java lacks (and libffi has). It's $libdir/pkgconfig/libffi.pc, which is needed by some software[0] at build time. Another difference is that libffi inside gcc-java seems to be older, judging from .so version number. My suggestion would be to add libffi to Slackware or at least include libffi.pc into gcc-java. [0] http://www.linuxquestions.org/questions/slackware-14/guile-upgrade-dependency-problems-884879/ -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From matteo.bernardini at gmail.com Thu Feb 16 18:32:46 2012 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 16 Feb 2012 19:32:46 +0100 Subject: [Slackbuilds-users] libffi conflicts with gcc-java In-Reply-To: <20120216165647.GA10264@kiras> References: <20120216165647.GA10264@kiras> Message-ID: dunno if this way I had started the armageddon but here I installed libffi-3.0.10 with this addition to the slackbuild # gcc-java in slackware already ships these headers. # maybe it's better to replace them instead of adding a second copy. # sorry for my ignorance, but I haven't found a cleaner way to extract gcc # includes path :p # fix also the pkgconfig file HEADERS_PATH=$(gcc -v 2>&1 | head -1 | cut -d\ -f4 | sed 's|specs|include|') sed -i "s|^includedir.*|includedir=${HEADERS_PATH}|" libffi.pc.in CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ --prefix=/usr \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --includedir=${HEADERS_PATH} \ installing the resulting package I'm using libffi.so.5 linked to libffi.so but updating libffi in gcc and adding a pkgconfig file IMHO should be nice :) Matteo From korgie at gmail.com Fri Feb 17 01:33:41 2012 From: korgie at gmail.com (korgman) Date: Fri, 17 Feb 2012 03:33:41 +0200 Subject: [Slackbuilds-users] Maintainer wanted for italc. Message-ID: <4F3DAE75.2000600@gmail.com> New version is out. http://italc.sourceforge.net/ http://slackbuilds.org/repository/13.37/desktop/italc/ -- Michales Michaloudes From audrius at neutrino.lt Fri Feb 17 16:20:50 2012 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Fri, 17 Feb 2012 18:20:50 +0200 Subject: [Slackbuilds-users] PyPy 1.8 packages Message-ID: <20120217162050.GA5222@kiras> Hi, Quick announcement: I have updated SlackBuild[0] for PyPy 1.8[1] and uploaded packages[2] for Slackware 13.37 (both 32 and 64-bit). If you'll notice any problems, please report them to me. Enjoy! [0] https://bitbucket.org/audriusk/slackbuilds/src/1ad0cbe60bea/python/pypy [1] http://pypy.org/ [2] https://bitbucket.org/audriusk/slackbuilds/downloads -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From niels.horn at gmail.com Sat Feb 18 11:46:20 2012 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 18 Feb 2012 09:46:20 -0200 Subject: [Slackbuilds-users] Updates - 20120218.1 Message-ID: Sat Feb 18 11:16:36 UTC 2012academic/gelemental: Miscellaneous cleanup ; change download linkaudio/qtractor: Updated for version 0.5.3.desktop/qlandkartegt: Updated for version 1.3.2.desktop/xmonad: Updated for version 0.10.development/mlton: Added (MLton Standard ML Compiler)graphics/kipi-plugins: Noted optional opencv dependencygraphics/shotwell: Updated for version 0.11.6.libraries/eigen3: Fixed hardcoded package locationlibraries/libburn: Updated for version 1.2.0.libraries/libisofs: Updated for version 1.2.0.libraries/xmonad-contrib: Updated for version 0.10.libraries/xmpppy: Added (XMPP Python Library)misc/protobuf: Include python bindings by defaultmultimedia/kino: Removed (FTBFS and lack of time)multimedia/miro: Updated for version 4.0.6.network/icecat: Updated for version 10.0.network/nagiosgraph: Added (Nagios Graphing Plugin)network/phpmyadmin: Updated for version 3.4.10.network/qbittorrent: Updated for version 2.9.3.network/shorewall6: Updated for version 4.4.27.3.network/shorewall: Updated for version 4.4.27.3.network/smb4k: Updated for version 1.0.0.network/transmission-remote-gtk: Added (Transmission remote GUI)network/weboob: Added (applications to interact with websites)office/myrulib: Updated for version 0.28.12.python/winpdb: Added (cross-platform Python debugger)system/aqemu: Add some patches from git (including qemu-1.0 support)system/cdwrite: Updated for version 3.4.system/kvm-kmod: Updated for version 3.2.system/lsyncd: Fix typo of HOMEPAGE in lsyncd.infosystem/oss: Updated for version 4.2.2006.system/smbldap-tools: Updated for version 0.9.7.system/unetbootin: Added (create bootable Live USB drives) From banderols at gmail.com Sat Feb 18 13:33:23 2012 From: banderols at gmail.com (Murat D. Kadirov) Date: Sat, 18 Feb 2012 19:33:23 +0600 Subject: [Slackbuilds-users] Updates - 20120218.1 In-Reply-To: References: Message-ID: <20120218133323.GA5776@darkstar> On Sat, Feb 18, 2012 at 09:46:20AM -0200, Niels Horn wrote: > Sat Feb 18 11:16:36 UTC 2012academic/gelemental: Miscellaneous cleanup > ; change download linkaudio/qtractor: Updated for version > 0.5.3.desktop/qlandkartegt: Updated for version 1.3.2.desktop/xmonad: > Updated for version 0.10.development/mlton: Added (MLton Standard ML > Compiler)graphics/kipi-plugins: Noted optional opencv > dependencygraphics/shotwell: Updated for version > 0.11.6.libraries/eigen3: Fixed hardcoded package > locationlibraries/libburn: Updated for version > 1.2.0.libraries/libisofs: Updated for version > 1.2.0.libraries/xmonad-contrib: Updated for version > 0.10.libraries/xmpppy: Added (XMPP Python Library)misc/protobuf: > Include python bindings by defaultmultimedia/kino: Removed (FTBFS and > lack of time)multimedia/miro: Updated for version > 4.0.6.network/icecat: Updated for version 10.0.network/nagiosgraph: > Added (Nagios Graphing Plugin)network/phpmyadmin: Updated for version > 3.4.10.network/qbittorrent: Updated for version > 2.9.3.network/shorewall6: Updated for version > 4.4.27.3.network/shorewall: Updated for version > 4.4.27.3.network/smb4k: Updated for version > 1.0.0.network/transmission-remote-gtk: Added (Transmission remote > GUI)network/weboob: Added (applications to interact with > websites)office/myrulib: Updated for version 0.28.12.python/winpdb: > Added (cross-platform Python debugger)system/aqemu: Add some patches > from git (including qemu-1.0 support)system/cdwrite: Updated for > version 3.4.system/kvm-kmod: Updated for version 3.2.system/lsyncd: > Fix typo of HOMEPAGE in lsyncd.infosystem/oss: Updated for version > 4.2.2006.system/smbldap-tools: Updated for version > 0.9.7.system/unetbootin: Added (create bootable Live USB drives) Nice formating =) > -- Murat D. Kadirov PGP fingerprint: 3081 EBFA 5CB9 BD24 4DB6 76EE 1B97 0A0E CEC0 6AA0 From niels.horn at gmail.com Sat Feb 18 13:36:47 2012 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 18 Feb 2012 11:36:47 -0200 Subject: [Slackbuilds-users] Updates - 20120218.1 In-Reply-To: <20120218133323.GA5776@darkstar> References: <20120218133323.GA5776@darkstar> Message-ID: On Sat, Feb 18, 2012 at 11:33 AM, Murat D. Kadirov wrote: > On Sat, Feb 18, 2012 at 09:46:20AM -0200, Niels Horn wrote: >> Sat Feb 18 11:16:36 UTC 2012academic/gelemental: Miscellaneous cleanup >> ; change download linkaudio/qtractor: Updated for version >> 0.5.3.desktop/qlandkartegt: Updated for version 1.3.2.desktop/xmonad: >> Updated for version 0.10.development/mlton: Added (MLton Standard ML >> Compiler)graphics/kipi-plugins: Noted optional opencv >> dependencygraphics/shotwell: Updated for version >> 0.11.6.libraries/eigen3: Fixed hardcoded package >> locationlibraries/libburn: Updated for version >> 1.2.0.libraries/libisofs: Updated for version >> 1.2.0.libraries/xmonad-contrib: Updated for version >> 0.10.libraries/xmpppy: Added (XMPP Python Library)misc/protobuf: >> Include python bindings by defaultmultimedia/kino: Removed (FTBFS and >> lack of time)multimedia/miro: Updated for version >> 4.0.6.network/icecat: Updated for version 10.0.network/nagiosgraph: >> Added (Nagios Graphing Plugin)network/phpmyadmin: Updated for version >> 3.4.10.network/qbittorrent: Updated for version >> 2.9.3.network/shorewall6: Updated for version >> 4.4.27.3.network/shorewall: Updated for version >> 4.4.27.3.network/smb4k: Updated for version >> 1.0.0.network/transmission-remote-gtk: Added (Transmission remote >> GUI)network/weboob: Added (applications to interact with >> websites)office/myrulib: Updated for version 0.28.12.python/winpdb: >> Added (cross-platform Python debugger)system/aqemu: Add some patches >> from git (including qemu-1.0 support)system/cdwrite: Updated for >> version 3.4.system/kvm-kmod: Updated for version 3.2.system/lsyncd: >> Fix typo of HOMEPAGE in lsyncd.infosystem/oss: Updated for version >> 4.2.2006.system/smbldap-tools: Updated for version >> 0.9.7.system/unetbootin: Added (create bootable Live USB drives) > > Nice formating =) >> > Bah... That was probably gmail messing up again :( Sorry for that. -- Niels Horn From niels.horn at gmail.com Sat Feb 18 13:53:26 2012 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 18 Feb 2012 11:53:26 -0200 Subject: [Slackbuilds-users] Updates - 20120218.1 In-Reply-To: References: <20120218133323.GA5776@darkstar> Message-ID: On Sat, Feb 18, 2012 at 11:36 AM, Niels Horn wrote: > On Sat, Feb 18, 2012 at 11:33 AM, Murat D. Kadirov wrote: >> On Sat, Feb 18, 2012 at 09:46:20AM -0200, Niels Horn wrote: >> >> Nice formating =) >>> >> > > Bah... That was probably gmail messing up again :( > Sorry for that. > > -- > Niels Horn Here goes the "unformatted" list (I hope): Sat Feb 18 11:16:36 UTC 2012 academic/gelemental: Miscellaneous cleanup ; change download link audio/qtractor: Updated for version 0.5.3. desktop/qlandkartegt: Updated for version 1.3.2. desktop/xmonad: Updated for version 0.10. development/mlton: Added (MLton Standard ML Compiler) graphics/kipi-plugins: Noted optional opencv dependency graphics/shotwell: Updated for version 0.11.6. libraries/eigen3: Fixed hardcoded package location libraries/libburn: Updated for version 1.2.0. libraries/libisofs: Updated for version 1.2.0. libraries/xmonad-contrib: Updated for version 0.10. libraries/xmpppy: Added (XMPP Python Library) misc/protobuf: Include python bindings by default multimedia/kino: Removed (FTBFS and lack of time) multimedia/miro: Updated for version 4.0.6. network/icecat: Updated for version 10.0. network/nagiosgraph: Added (Nagios Graphing Plugin) network/phpmyadmin: Updated for version 3.4.10. network/qbittorrent: Updated for version 2.9.3. network/shorewall6: Updated for version 4.4.27.3. network/shorewall: Updated for version 4.4.27.3. network/smb4k: Updated for version 1.0.0. network/transmission-remote-gtk: Added (Transmission remote GUI) network/weboob: Added (applications to interact with websites) office/myrulib: Updated for version 0.28.12. python/winpdb: Added (cross-platform Python debugger) system/aqemu: Add some patches from git (including qemu-1.0 support) system/cdwrite: Updated for version 3.4. system/kvm-kmod: Updated for version 3.2. system/lsyncd: Fix typo of HOMEPAGE in lsyncd.info system/oss: Updated for version 4.2.2006. system/smbldap-tools: Updated for version 0.9.7. system/unetbootin: Added (create bootable Live USB drives) From belka.ew at gmail.com Sat Feb 18 18:25:07 2012 From: belka.ew at gmail.com (Eugen Wissner) Date: Sat, 18 Feb 2012 19:25:07 +0100 Subject: [Slackbuilds-users] xmonad path Message-ID: Hi guys, there is an error on http://slackbuilds.org/repository/13.37/haskell/xmonad-contrib/ xmonad-contrib.tar.gz is library, not haskell. Best regards, Eugene Wissner -------------- next part -------------- An HTML attachment was scrubbed... URL: From niels.horn at gmail.com Sat Feb 18 18:40:59 2012 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 18 Feb 2012 16:40:59 -0200 Subject: [Slackbuilds-users] xmonad path In-Reply-To: References: Message-ID: On Sat, Feb 18, 2012 at 4:25 PM, Eugen Wissner wrote: > Hi guys, > > there is an error on > http://slackbuilds.org/repository/13.37/haskell/xmonad-contrib/ > xmonad-contrib.tar.gz is library, not haskell. > > Best regards, > Eugene Wissner > Well, it is a library written in haskell, IIRC, and the maintainer submitted the latest update in the haskell category... It got mixed up on the website though, but before fixing anything, let's see what the maintainer thinks about this. Mikko? -- Niels Horn From jens at tuxane.com Sat Feb 18 19:11:01 2012 From: jens at tuxane.com (TuxaneSoft) Date: Sat, 18 Feb 2012 20:11:01 +0100 Subject: [Slackbuilds-users] xmonad path In-Reply-To: References: Message-ID: <1329592261.8495.2.camel@slack-13-37> It even looks like it's broken on the web site: http://slackbuilds.org/repository/13.37/haskell/xmonad-contrib/ shows me : Warning: Invalid argument supplied for foreach() in /slackbuilds/www/includes/repository.inc.php on line 180 Individual Files: and no files -- Jens Am Samstag, den 18.02.2012, 16:40 -0200 schrieb Niels Horn: > On Sat, Feb 18, 2012 at 4:25 PM, Eugen Wissner wrote: > > Hi guys, > > > > there is an error on > > http://slackbuilds.org/repository/13.37/haskell/xmonad-contrib/ > > xmonad-contrib.tar.gz is library, not haskell. > > > > Best regards, > > Eugene Wissner > > > > Well, it is a library written in haskell, IIRC, and the maintainer > submitted the latest update in the haskell category... > It got mixed up on the website though, but before fixing anything, > let's see what the maintainer thinks about this. > > Mikko? > > > -- > Niels Horn > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From adis at linux.org.ba Sat Feb 18 20:10:05 2012 From: adis at linux.org.ba (Adis Nezirovic) Date: Sat, 18 Feb 2012 21:10:05 +0100 Subject: [Slackbuilds-users] Suggestion for qemu-kvm slackbuild Message-ID: Can we add the following line to udev rules (fixup_udev_rules.patch): +KERNEL=="vhost_net", GROUP="@GROUP@", MODE="0660" so that both, /dev/kvm and /dev/vhost_net devices are group-owned by kvm group (or @GROUP@) The defaults for /dev/vhost_net are root:root 600 The idea is that one can run qemu-system-x86_64 as ordinary user, and use vhost_net acceleration using netdev syntax: -netdev type=tap,ifname=tap0,id=guest0,script=no,downscript=no,vhost=on \ -device virtio-net-pci,netdev=guest0,mac=XX:YY:XX:YY:XX:YY tap0 device is precreated in rc.bridge script (tunctl -g kvm -t tap0), so nothing requires root privileges for running VM. Best regards, Adis From niels.horn at gmail.com Sat Feb 18 20:47:01 2012 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 18 Feb 2012 18:47:01 -0200 Subject: [Slackbuilds-users] xmonad path In-Reply-To: <1329592261.8495.2.camel@slack-13-37> References: <1329592261.8495.2.camel@slack-13-37> Message-ID: On Sat, Feb 18, 2012 at 5:11 PM, TuxaneSoft wrote: > It even looks like it's broken on the web site: > > http://slackbuilds.org/repository/13.37/haskell/xmonad-contrib/ shows > me : > > ? ? ? ? ? ?Warning: Invalid argument supplied for foreach() > ? ? ?in /slackbuilds/www/includes/repository.inc.php on line 180 > ? ? ? ? ? ? ? ? ? ? ? ? ? Individual Files: > > > and no files > > > -- > > Jens > That's what I meant with "It got mixed up on the website" Easy enough to fix, but I'd like to hear from the maintainer first. -- Niels Horn From lmello.009 at gmail.com Sun Feb 19 01:19:18 2012 From: lmello.009 at gmail.com (Luis Henrique F. Cardoso de Mello) Date: Sat, 18 Feb 2012 23:19:18 -0200 Subject: [Slackbuilds-users] gtk-kde4 : Forbidden Message-ID: <4F404E16.4090908@gmail.com> Hi, The 0.9.4 release of gtk-kde4 isn't available anymore. I downloaded the latest release and had to cut off a lot of the fixes and tweaks in order to build 0.9.5. I also had to rename the downloaded tarball. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gtk-kde4.SlackBuild.sbopkg URL: From rworkman at slackbuilds.org Sun Feb 19 06:45:25 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 19 Feb 2012 00:45:25 -0600 Subject: [Slackbuilds-users] qemu and qemu-kvm (again) Message-ID: <20120219004525.1bda1050@liberty.rlwhome.lan> Given that no clearly correct/optimal consensus was reached regarding qemu and qemu-kvm earlier, I opted to do the following: 1) update qemu to 1.0.1 2) rename the useful binary in qemu-kvm to "qemu-kvm" 3) disable building of non-KVM targets in qemu-kvm build 4) add optional spice support to both qemu and qemu-kvm (yes, a spice build is in pending and pretty much cleared by me already) This will allow those who only need one or the other with respect to KVM usage to be happy, but it will also allow those of us who want to parallel install both qemu and qemu-kvm to be happy too. Are there any objections with the commits here? http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-final-for-now -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From vmj at linuxbox.fi Sun Feb 19 09:46:07 2012 From: vmj at linuxbox.fi (=?ISO-8859-1?Q?Mikko_V=E4rri?=) Date: Sun, 19 Feb 2012 16:46:07 +0700 Subject: [Slackbuilds-users] xmonad path In-Reply-To: References: Message-ID: <213d9a35-65b0-47e1-b2b7-61650e4eed37@email.android.com> Niels Horn wrote: >On Sat, Feb 18, 2012 at 4:25 PM, Eugen Wissner >wrote: >> Hi guys, >> >> there is an error on >> http://slackbuilds.org/repository/13.37/haskell/xmonad-contrib/ >> xmonad-contrib.tar.gz is library, not haskell. >> >> Best regards, >> Eugene Wissner >> > >Well, it is a library written in haskell, IIRC, and the maintainer >submitted the latest update in the haskell category... >It got mixed up on the website though, but before fixing anything, >let's see what the maintainer thinks about this. > >Mikko? > > >-- >Niels Horn Yes, it is a library written in Haskell. But unlike the rest of the haskell/haskell-* stuff, it isn't named 'haskell-xmonad-contrib'. In my last update I moved xmonad-contrib from libraries category to haskell category, so that all haskell libraries would be in the same category. Maybe the database behind the website wasn't updated properly? -vmj -- Sent from my Android tablet with K-9 Mail. Please excuse my brevity. From rworkman at slackbuilds.org Sun Feb 19 10:06:17 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 19 Feb 2012 04:06:17 -0600 Subject: [Slackbuilds-users] xmonad path In-Reply-To: <213d9a35-65b0-47e1-b2b7-61650e4eed37@email.android.com> References: <213d9a35-65b0-47e1-b2b7-61650e4eed37@email.android.com> Message-ID: <20120219040617.4f81ccfa@liberty.rlwhome.lan> On Sun, 19 Feb 2012 16:46:07 +0700 Mikko V?rri wrote: > Niels Horn wrote: > > >On Sat, Feb 18, 2012 at 4:25 PM, Eugen Wissner > >wrote: > >> Hi guys, > >> > >> there is an error on > >> http://slackbuilds.org/repository/13.37/haskell/xmonad-contrib/ > >> xmonad-contrib.tar.gz is library, not haskell. > >> > >> Best regards, > >> Eugene Wissner > >> > > > >Well, it is a library written in haskell, IIRC, and the maintainer > >submitted the latest update in the haskell category... > >It got mixed up on the website though, but before fixing anything, > >let's see what the maintainer thinks about this. > > > >Mikko? > > > > Yes, it is a library written in Haskell. But unlike the rest of the > haskell/haskell-* stuff, it isn't named 'haskell-xmonad-contrib'. In > my last update I moved xmonad-contrib from libraries category to > haskell category, so that all haskell libraries would be in the same > category. > > Maybe the database behind the website wasn't updated properly? This is almost certainly my fault. Here's the git log entry: commit 468f62393275fa1f23951ba10790fe89be554a70 Author: Mikko V?rri Date: Sun Feb 12 00:43:20 2012 -0600 libraries/xmonad-contrib: Updated for version 0.10. Signed-off-by: Robby Workman I didn't even notice if/that you had changed the category when you submitted, so I just put it in the same place it already was before the update. I'll "fix" it in my git branch in just a bit. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From vmj at linuxbox.fi Sun Feb 19 10:13:43 2012 From: vmj at linuxbox.fi (=?ISO-8859-1?Q?Mikko_V=E4rri?=) Date: Sun, 19 Feb 2012 17:13:43 +0700 Subject: [Slackbuilds-users] xmonad path In-Reply-To: <20120219040617.4f81ccfa@liberty.rlwhome.lan> References: <213d9a35-65b0-47e1-b2b7-61650e4eed37@email.android.com> <20120219040617.4f81ccfa@liberty.rlwhome.lan> Message-ID: <54aa880f-a707-48ff-bf1e-2a0a77fe52ce@email.android.com> Robby Workman wrote: > >I didn't even notice if/that you had changed the category when >you submitted, so I just put it in the same place it already >was before the update. > Who reads those submit messages anyway... ;) -vmj -- Sent from my Android tablet with K-9 Mail. Please excuse my brevity. From robby at rlworkman.net Mon Feb 20 18:35:34 2012 From: robby at rlworkman.net (Robby Workman) Date: Mon, 20 Feb 2012 12:35:34 -0600 Subject: [Slackbuilds-users] Updates - 20120220.1 Message-ID: <20120220123534.21a77037@liberty.rlwhome.lan> Mon Feb 20 18:21:14 UTC 2012 academic/pcb: Updated for version 20110918. academic/staden: Several fixes/enhancements audio/amSynth: Updated for version 1.3.0. audio/celt051: Added (low delay audio codec - version 0.5.1.x) audio/qjackctl: Fix build on x86_64; new maintainer desktop/obapps: Added (a graphical tool for configuring per-application settings) desktop/obconf: Updated to git snapshot cc7a188076, new maintainer. desktop/wminfo: Updated for version 2.5.2. desktop/xfce4-screenshooter: Fix a crash bug (xfce bz #6460) development/arduino: wrapper script bugfixes wrt CPLUS_INCLUDE_PATH development/gnome-inform7: Added (fiction authoring platform) development/qt-creator: Updated for version 2.2.1. development/spice-protocol: Added (spice protocol headers) development/spyder: Updated for version 2.1.7. games/alephone: Added (open-source Marathon 2 engine) games/gargoyle: various build improvements games/mame: Updated for version 0.145. games/marathon-data: Added (game data for use with Aleph One) games/marathon-infinity-data: Added (game data for Aleph One) games/marathon2-data: Added (game data for use with Aleph One) games/playonlinux: Updated for version 4.0.14. games/quakeforge: Added (Linux port of id Software's Quake I) games/wesnoth: Updated for version 1.10. games/yamagi-quake2: Updated for version 4.02. haskell/xmonad-contrib: Moved from Libraries category libraries/io_lib: Trivial - add newlines to last line of files libraries/js185: Added (SpiderMonkey - Mozilla's JavaScript Engine) libraries/libAfterImage: New maintainer (no other changes) libraries/libcacard: Added (Virtual Smart Card Emulator library) libraries/libisoburn: Updated for version 1.2.0. libraries/libproxy: Updated for version 0.4.7. libraries/nspr: Added (Netscape Portable Runtime) multimedia/flash-player-plugin: Updated for version 11.1.102.62. multimedia/minidlna: Updated for version 1.0.24. network/cacti: Updated for version 0.8.7i_p1. network/ckermit: Added (network and serial communication software) network/freerdp: Updated for version 1.0.1. network/hiawatha: Updated for version 7.8.2. network/ndiswrapper-kernel: Added (kernel module for NDIS drivers) network/ndiswrapper-utils: Added (userspace utils for NDIS drivers) network/ndiswrapper: Removed (split in ndiswrapper-kernel & -utils) network/node: Updated for version 0.6.10. network/openvswitch: Updated for version 1.4.0. network/privoxy: Updated for version 3.0.19. network/remmina: Updated for version 1.0.0. network/spice: Added (remote computing solution) office/adobe-reader: Updated for version 9.4.7. office/libreoffice-langpack: Updated for version 3.5.0. office/libreoffice: Updated for version 3.5.0. perl/perl-BerkeleyDB: Updated for version 0.50. perl/perl-DBD-SQLite: Updated for version 1.35. perl/perl-IO-Socket-INET6: Updated for version 2.69. perl/perl-IO-Socket-SSL: Updated for version 1.54. perl/perl-Net-Pcap: Updated for version 0.16. perl/perl-NetPacket: Updated for version 1.3.1. python/babel: Added (python internationalization tools) system/nss-pam-ldapd: Added (LDAP NSS/PAM module) system/xf86-video-qxl: Added (X.org spice qxl video driver) system/zarfy: Added (gui to libxrandr) From rworkman at slackbuilds.org Mon Feb 20 19:07:22 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 20 Feb 2012 13:07:22 -0600 Subject: [Slackbuilds-users] Updates - 20120220.2 In-Reply-To: <20120220123534.21a77037@liberty.rlwhome.lan> References: <20120220123534.21a77037@liberty.rlwhome.lan> Message-ID: <20120220130722.7c901536@liberty.rlwhome.lan> Mon Feb 20 19:01:58 UTC 2012 network/remmina-plugins: Removed (included with remmina now) system/qemu-kvm: Enabled (optional) spice support. system/qemu-kvm: Rename binary to "qemu-kvm" and other changes system/qemu: Enabled (optional) spice support. system/qemu: Updated for version 1.0.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Feb 20 19:17:50 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 20 Feb 2012 13:17:50 -0600 Subject: [Slackbuilds-users] qemu and qemu-kvm (again) In-Reply-To: <20120219004525.1bda1050@liberty.rlwhome.lan> References: <20120219004525.1bda1050@liberty.rlwhome.lan> Message-ID: <20120220131750.50683fc5@liberty.rlwhome.lan> On Sun, 19 Feb 2012 00:45:25 -0600 Robby Workman wrote: > Given that no clearly correct/optimal consensus was reached regarding > qemu and qemu-kvm earlier, I opted to do the following: > > 1) update qemu to 1.0.1 > 2) rename the useful binary in qemu-kvm to "qemu-kvm" > 3) disable building of non-KVM targets in qemu-kvm build > 4) add optional spice support to both qemu and qemu-kvm > (yes, a spice build is in pending and pretty much cleared > by me already) > > This will allow those who only need one or the other with > respect to KVM usage to be happy, but it will also allow > those of us who want to parallel install both qemu and qemu-kvm > to be happy too. > > Are there any objections with the commits here? I hope not, because I just merged it into master and 13.37. If there are objections, I suspect they will be to one of two things: 1) Renaming /usr/bin/qemu-system-x86_64 to /usr/bin/qemu-kvm means that VM startup scripts have to be edited. Sorry, but go ahead and edit them. 2) Removing support for building all targets means that some users will now have to build qemu instead of using qemu-kvm for everything. Well, I won't be too terribly opposed to reverting that part and returning the ability to build all targets (though I'll insist that it default to off). Hopefully it won't be an issue though... -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From slackbuilds at ssmbox.net Wed Feb 22 00:34:35 2012 From: slackbuilds at ssmbox.net (Stu Miller) Date: Tue, 21 Feb 2012 17:34:35 -0700 Subject: [Slackbuilds-users] Suggestion for qemu-kvm slackbuild In-Reply-To: References: Message-ID: <6b5291645d5db9c39c67e9ce28ee7b55@guest8> On 18.02.2012 13:10, Adis Nezirovic wrote: > Can we add the following line to udev rules (fixup_udev_rules.patch): > > +KERNEL=="vhost_net", GROUP="@GROUP@", MODE="0660" > > so that both, /dev/kvm and /dev/vhost_net devices are group-owned by > kvm group (or @GROUP@) > The defaults for /dev/vhost_net are root:root 600 > > The idea is that one can run qemu-system-x86_64 as ordinary user, and > use vhost_net acceleration using netdev syntax: > > -netdev type=tap,ifname=tap0,id=guest0,script=no,downscript=no,vhost=on > -device virtio-net-pci,netdev=guest0,mac=XX:YY:XX:YY:XX:YY > > tap0 device is precreated in rc.bridge script (tunctl -g kvm -t tap0), > so nothing requires root privileges for running VM. > > Best regards, > Adis > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ I had some time over the weekend to check out qdev and vhost_net and I like what I've found so far. I reconfigured a non-critical, production KVM (slackware-13.37) to run vhost_net and the network latency on pings is 50% of the non-vhost_net KVMs. I'll keep the KVM running in this config and watch performance and stability. So far I support this recommendation and will add it to the next qemu-kvm SlackBuild if my KVM survives my soak test. Thanks for the suggestion! Stu -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Wed Feb 22 01:31:54 2012 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 21 Feb 2012 19:31:54 -0600 Subject: [Slackbuilds-users] Suggestion for qemu-kvm slackbuild In-Reply-To: <6b5291645d5db9c39c67e9ce28ee7b55@guest8> References: <6b5291645d5db9c39c67e9ce28ee7b55@guest8> Message-ID: <20120221193154.01eb5525@liberty.rlwhome.lan> On Tue, 21 Feb 2012 17:34:35 -0700 Stu Miller wrote: > I had some time over the weekend to > check out qdev and vhost_net and I like what I've found so far. I > reconfigured a non-critical, production KVM (slackware-13.37) to run > vhost_net and the network latency on pings is 50% of the non-vhost_net > KVMs. I'll keep the KVM running in this config and watch performance > and stability. So far I support this recommendation and will add it > to the next qemu-kvm SlackBuild if my KVM survives my soak test. I've got this in a temporary branch; I'll merge it if/when you say "go" :) http://slackbuilds.org/cgit/slackbuilds/commit/?h=qemu-kvm&id=62f46b11770e1a -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From biolizard.mail at gmail.com Wed Feb 22 07:38:54 2012 From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=) Date: Wed, 22 Feb 2012 15:38:54 +0800 Subject: [Slackbuilds-users] Dina Message-ID: <4F449B8E.6060203@gmail.com> Hello, I think the dina font source download link is broken. Regards Jos? From niels.horn at gmail.com Wed Feb 22 09:45:42 2012 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 22 Feb 2012 07:45:42 -0200 Subject: [Slackbuilds-users] Dina In-Reply-To: <4F449B8E.6060203@gmail.com> References: <4F449B8E.6060203@gmail.com> Message-ID: On Wed, Feb 22, 2012 at 5:38 AM, Jos? Lopes wrote: > Hello, > > I think the dina font source download link is broken. > > Regards > Jos? > _______________________________________________ > 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/ > Yes, ompldr.org is down, but you can use http://omploader.org/vMjIwNA/dina-pcf-2.89.tar.gz to get the file. Not sure how long that one will stay up though... -- Niels Horn From biolizard.mail at gmail.com Wed Feb 22 10:03:40 2012 From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=) Date: Wed, 22 Feb 2012 18:03:40 +0800 Subject: [Slackbuilds-users] Dina In-Reply-To: References: <4F449B8E.6060203@gmail.com> Message-ID: <4F44BD7C.8010607@gmail.com> Hello, Thanks for the link. By the way, thank you very much for your contributions to Slackbuilds. Regards, Jos? On 22-02-2012 17:45, Niels Horn wrote: > On Wed, Feb 22, 2012 at 5:38 AM, Jos? Lopes wrote: >> Hello, >> >> I think the dina font source download link is broken. >> >> Regards >> Jos? >> _______________________________________________ >> 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/ >> > Yes, ompldr.org is down, but you can use > http://omploader.org/vMjIwNA/dina-pcf-2.89.tar.gz to get the file. > Not sure how long that one will stay up though... > > -- > Niels Horn > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From Bradley at NorthTech.US Sat Feb 25 00:49:36 2012 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Fri, 24 Feb 2012 16:49:36 -0800 Subject: [Slackbuilds-users] New old version of Twin is finally up at sourceforge... Message-ID: <4F483020.1080606@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hey I've been really advocating the use of Twin for some time now. It's better, IMO, than VWM, and VWM is, IMO, better than Twin - it just depends on which feature set I want to use at the moment I guess. Anyway, for over a year now, version 0.6.2 has been available, but it was at Max's old University site and not sourceforge. I gave him a nudge after sending the SBo maintainer an email pointing to the newest version but never heard anything back. Mathhew might have had a lot on his plate at the time. That was fine until one day the original home site for Twin was taken offline and the new version wasn't up at sourceforge (0.6.1 was the latest there), so I went to task and Max just uploaded the 0.6.2 version. If anyone is so inclined, I've maintained the x86_64 version of the packages, 0.6.2 being at: gopher://gopher.northtech.us/9/software/packages/twin-0.6.2-x86_64-1_SBo.tgz but I wouldn't mind at all if Matthew wanted me to take over the SlackBuild for Twin, considering it's been such a pet project for me over the past few years anyway - hint hint :) I truly believe this is a VERY underutilized tool. Anyway, I've BCC'd him on this, seeing how he's the maintainer, and whichever way he would like to go on this would be great for the community I'm sure. Apologies for being somewhat off-topic if anyone found this post bothersome. Kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJPSDAgAAoJEE1wgkIhr9j3NPUH/RwVU4Awf09RSyk4fCzsCORH T7kKq841/z7Vrh0+so90hjhgMkhkmbGVFziiIE4p5Swk4SreCX8GBqY9xWwC6QnK DuMxGOdUyt464G3CvL2wmbKGGp6GDAHwzoyZMvFBC3wpTQ8FLMJfayAlQ2XXe+wg P64LfgpP43cNylv/tRejNIC/0eMnj2guHK5/8/tDe74qdm+nAOZQu0caBSOqvDCu 2ojQIcDSDKxOBr4LszHi1dnxRm9xdf/Z3pfXtxIe3Iz+5bzJU4mPI06//cNwqFfw jqm0m0ZflAgAfriFOnOc7qdprYV/N8CiSEjrh+Mkzy+qyZfSkxlLBxgwlNORZF4= =5zWS -----END PGP SIGNATURE----- From mfilpot at gmail.com Sat Feb 25 00:49:54 2012 From: mfilpot at gmail.com (Matthew Fillpot) Date: Fri, 24 Feb 2012 19:49:54 -0500 Subject: [Slackbuilds-users] Twin slackbuild change of ownership Message-ID: SBo Admins, I am handing over the maintenance of twin to Bradley Thonton so that the package can be maintained by an active user. -- -Thank You, -Matthew Fillpot -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgeboski at gmail.com Sat Feb 25 05:51:58 2012 From: jgeboski at gmail.com (James Geboski) Date: Sat, 25 Feb 2012 00:51:58 -0500 Subject: [Slackbuilds-users] murmur SlackBuild In-Reply-To: <20120225041727.42960@gmx.com> References: <20120225041727.42960@gmx.com> Message-ID: Hello, No worries about the delay. I personally, find it more useful to have them split into two packages. Reason being, I do not have any of the X libraries on the servers I am running murmur on. And on the client end, you really don't need murmur. If anyone has any objections to this, please inform me. Also, I'd find it "cleaner" to have /var/{lib,log,run}/mumble-server renamed to /var/{lib,log,run}/murmur. This way it matches the naming of rc.murmur and murmurd. However, people would not really be able upgrade the package if this was implemented. Would this be a forbidden to do in the SlackBuild? James On Fri, Feb 24, 2012 at 11:17 PM, wrote: > I apologize for the delay in response. I'm no longer maintaining murmur, I > was under the impression that mumble would be packaged with murmur as they > both already share the same source tarball. Anyway, I'm forwarding this to > the SBo mailing list as I am granting you permission to take over > maintenance of murmur. > > Thank you. > > > > ----- Original Message ----- > > From: James Geboski > > Sent: 02/13/12 03:46 PM > > To: adev at linuxmail.org > > Subject: murmur SlackBuild > > Hello there, > > I don't know if murmur SlackBuild has just been forgotten about or what > but, there is now version 1.2.3. > > All that really needs to be added to the SlackBuild are some config > options: no-ice, no-bonjour. I have attached a patch if you're interested > in that. > > Also, if you're not up for continuing the maintenance on this SlackBuild > anymore, I'd be willing to maintain the build script. > > James > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Sat Feb 25 06:54:16 2012 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 24 Feb 2012 22:54:16 -0800 Subject: [Slackbuilds-users] murmur SlackBuild In-Reply-To: References: <20120225041727.42960@gmx.com> Message-ID: On Fri, Feb 24, 2012 at 9:51 PM, James Geboski wrote: > Hello, > > No worries about the delay. I personally, find it more useful to have > them split into two packages. Reason being, I do not have any of the > X libraries on the servers I am running murmur on. And on the client end, > you really don't need murmur. If anyone has any objections to this, please > inform me. > > Also, I'd find it "cleaner" to have /var/{lib,log,run}/mumble-server > renamed to /var/{lib,log,run}/murmur. This way it matches the naming of > rc.murmur and murmurd. However, people would not really be able upgrade > the package if this was implemented. Would this be a forbidden to do in > the SlackBuild? > > James > > I agree on keeping the 2 as separate packages. I'm running murmur-1.2.3 on a headless box, and mumble-1.2.3 on the GUI clients. 2 packages keep it cleaner and simpler. As for '/var/{lib,log,run}/murmur' I can accept the rename. A simple warning statement about doing a clean install in the readme should be sufficient. After all, we all read the readmes, right? -Ed -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From binhnguyen at fastmail.fm Sat Feb 25 13:25:49 2012 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Sat, 25 Feb 2012 20:25:49 +0700 Subject: [Slackbuilds-users] Dina In-Reply-To: <4F44BD7C.8010607@gmail.com> References: <4F449B8E.6060203@gmail.com> <4F44BD7C.8010607@gmail.com> Message-ID: <1330176349.25690.140661041173309@webmail.messagingengine.com> On Wed, Feb 22, 2012, at 06:03 PM, Jos? Lopes wrote: > Hello, > > Thanks for the link. > By the way, thank you very much for your contributions to Slackbuilds. > > Regards, > Jos? > > On 22-02-2012 17:45, Niels Horn wrote: > > On Wed, Feb 22, 2012 at 5:38 AM, Jos? Lopes wrote: > >> Hello, > >> > >> I think the dina font source download link is broken. > >> > >> Regards > >> Jos? > >> > > Yes, ompldr.org is down, but you can use > > http://omploader.org/vMjIwNA/dina-pcf-2.89.tar.gz to get the file. > > Not sure how long that one will stay up though... > > > > -- > > Niels Horn > I've just submitted an update using this link for the font: http://distfiles.gentoo.org/distfiles/dina-pcf-2.89.tar.gz -- http://www.fastmail.fm - Faster than the air-speed velocity of an unladen european swallow From thedoogster at gmail.com Sat Feb 25 17:50:12 2012 From: thedoogster at gmail.com (Doogster) Date: Sat, 25 Feb 2012 09:50:12 -0800 Subject: [Slackbuilds-users] Why are ORBit2 and GConf available on SBo? Message-ID: Why are ORBit2 and GConf available on SBo? They're included with Slackware, in the /extra/google-chrome directory. From Bradley at NorthTech.US Sat Feb 25 18:24:51 2012 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Sat, 25 Feb 2012 10:24:51 -0800 Subject: [Slackbuilds-users] Why are ORBit2 and GConf available on SBo? In-Reply-To: References: Message-ID: <4F492773.2090600@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On 02/25/2012 09:50 AM, Doogster wrote: > Why are ORBit2 and GConf available on SBo? They're included with > Slackware, in the /extra/google-chrome directory. Oh yes. I should mention something too. Now I haven't doublechecked this, but the other day when I did a fresh install of (a two month old version of) -current, I went through my usual (initial sysadmin base install) sbopkg queue and one of the apps that I typically install through force of habit is *htop*. And then, if I recall correctly, when I ran slackpkg it wanted to update htop. I could be wrong, and I haven't taken the time to check yet, but is htop now part of the mainline repo too? Kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJPSSdyAAoJEE1wgkIhr9j3HvMH/RzeMxuuukxH1D5v/nGM33SP it/YpNu+zmoMcORrj90gzNmbEMYNVGqU60Kl6BXASJHCBOekgJTxtDWbw9aWy3PU am9+zK8XlZqH8Fz7NkJahdQvkswwJrUFbWCMN+OajGnwBxf6tn8YUudJpSI4JGwY UR7+OvLpBhA35fvIvlRxAzOelUIrSENQFf3ceLL344KRuLqgBSO+K1IR0YogFD3P Cyrf5dNZVnNIBChFJlDidOZqRO2SREDzzR6j9nAoDhsmHBLxq4X0n2TgQM3OcqO5 3Z3F8YKB0uhhqCd7GYt0nL4AMUG05x5ImsP9rvBTSWwQGvQQoxLfcIxLdt9GFJU= =sHno -----END PGP SIGNATURE----- From mpagnan at acanac.net Sat Feb 25 18:24:19 2012 From: mpagnan at acanac.net (Martin Pagnan) Date: Sat, 25 Feb 2012 13:24:19 -0500 Subject: [Slackbuilds-users] Kompozer In-Reply-To: References: Message-ID: <4F492753.8080809@acanac.net> The Kompozer SlackBuild has a strange flaw. It installs with installpkg and all messages indicate that the install was successful. However, when you run Kompozer nothing happens. Run from the command line with debug on no messages are produced. It just quits instantly. The person in Brazil listed as support for the SlackBuild does not reply to repeated emails, even though the emails do not bounce back as undeliverable. I tried Kompozer on WinDoze and was impressed. Is there an alternative install package? Has anyone else encountered the problem? Thanks. From ozan.turkyilmaz at gmail.com Sat Feb 25 18:07:56 2012 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 25 Feb 2012 23:07:56 +0500 Subject: [Slackbuilds-users] Why are ORBit2 and GConf available on SBo? In-Reply-To: References: Message-ID: 2012/2/25 Doogster : > Why are ORBit2 and GConf available on SBo? They're included with > Slackware, in the /extra/google-chrome directory. Being in extra does not make it being in stock Slackware. -- Ozan, BSc, BEng From klaatu at straightedgelinux.com Sat Feb 25 18:47:13 2012 From: klaatu at straightedgelinux.com (Klaatu) Date: Sat, 25 Feb 2012 13:47:13 -0500 Subject: [Slackbuilds-users] Why are ORBit2 and GConf available on SBo? In-Reply-To: <4F492773.2090600@NorthTech.US> References: <4F492773.2090600@NorthTech.US> Message-ID: <201202251347.13060.klaatu@straightedgelinux.com> With regards to htop, yes it does look like it is in the /ap package set in - current (according to PACKAGES.txt file in ftp://elektroni.phys.tut.fi/slackware-current/slackware) However, Slackbuilds.org's charter (at least as far as I understand) is to maintain packages for the stable release of Slackware, so htop being in Slackbuilds's 13.37 collection does make sense for those people who don't follow -current. - klaatu > On 02/25/2012 09:50 AM, Doogster wrote: > > Why are ORBit2 and GConf available on SBo? They're included with > > Slackware, in the /extra/google-chrome directory. > > Oh yes. I should mention something too. > > Now I haven't doublechecked this, but the other day when I did a fresh > install of (a two month old version of) -current, I went through my > usual (initial sysadmin base install) sbopkg queue and one of the apps > that I typically install through force of habit is *htop*. > > And then, if I recall correctly, when I ran slackpkg it wanted to update > htop. > > I could be wrong, and I haven't taken the time to check yet, but is htop > now part of the mainline repo too? > > Kindest regards, - klaatu From matteo.bernardini at gmail.com Sat Feb 25 20:03:38 2012 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 25 Feb 2012 21:03:38 +0100 Subject: [Slackbuilds-users] Kompozer In-Reply-To: <4F492753.8080809@acanac.net> References: <4F492753.8080809@acanac.net> Message-ID: I just checked and it seems to be a 32bit only application: are you trying to use it on 64bit? Then you should go multilib for that http://connie.slackware.com/~alien/multilib/ but, strictly regarding slackbuilds.org, I think running it on a 64bit is considered unsupported. Matteo From Bradley at NorthTech.US Sat Feb 25 20:22:31 2012 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Sat, 25 Feb 2012 12:22:31 -0800 Subject: [Slackbuilds-users] Why are ORBit2 and GConf available on SBo? In-Reply-To: <201202251347.13060.klaatu@straightedgelinux.com> References: <4F492773.2090600@NorthTech.US> <201202251347.13060.klaatu@straightedgelinux.com> Message-ID: <4F494307.6040204@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On 02/25/2012 10:47 AM, Klaatu wrote: > With regards to htop, yes it does look like it is in the /ap package set in - > current (according to PACKAGES.txt file in > ftp://elektroni.phys.tut.fi/slackware-current/slackware) > > However, Slackbuilds.org's charter (at least as far as I understand) is to > maintain packages for the stable release of Slackware, so htop being in > Slackbuilds's 13.37 collection does make sense for those people who don't > follow -current. > > - klaatu Thanks Klaatu :) I got so used to not checking the changelogs during the lull. It just goes to show ;) Kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJPSUMHAAoJEE1wgkIhr9j3K1MH/3l8iaLqG25NWoLGkzsgdBrW X4JaosUzlfXAY1IaNb8odRrA6y1WTotFM436WszevlOceBWwnJWvD0ETwM/i0WwY aISKoZMEiQYloJl+K4nlhYzLGDvkCE69ToUaK/wohA9HNoPpjVe04UZ5dqWlitP/ tHVBEF79gdi5Erj/Yw0ZL71+df9g8RMLsnu3cTjc5UxGe8owivC00swAAJv1O5yX KpErSQxXK/B/Ha2frl6/DWl8M9y7lenkH5/UJgKrVuJXNgh/76qLi04F1HSiMndw FrZR+o8zczDppAeFhql7AhtftTAc6Vd6pETSYM4o+3yISGXLuhkhLNWa6JYumnk= =YsCv -----END PGP SIGNATURE----- From niels.horn at gmail.com Sat Feb 25 20:28:19 2012 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 25 Feb 2012 18:28:19 -0200 Subject: [Slackbuilds-users] Kompozer In-Reply-To: References: <4F492753.8080809@acanac.net> Message-ID: On Sat, Feb 25, 2012 at 6:03 PM, Matteo Bernardini wrote: > I just checked and it seems to be a 32bit only application: are you > trying to use it on 64bit? > Then you should go multilib for that > > http://connie.slackware.com/~alien/multilib/ > > but, strictly regarding slackbuilds.org, I think running it on a 64bit > is considered unsupported. > > Matteo You could try to build kompozer from source, but that's not what the SlackBuild script does... :) -- Niels Horn From thedoogster at gmail.com Sat Feb 25 20:57:28 2012 From: thedoogster at gmail.com (Doogster) Date: Sat, 25 Feb 2012 12:57:28 -0800 Subject: [Slackbuilds-users] Why are ORBit2 and GConf available on SBo? In-Reply-To: References: Message-ID: Sure it does. That's why nothing *else* in /extra is in SBo. On Sat, Feb 25, 2012 at 10:07 AM, Ozan T?rky?lmaz wrote: > 2012/2/25 Doogster : >> Why are ORBit2 and GConf available on SBo? They're included with >> Slackware, in the /extra/google-chrome directory. > > Being in extra does not make it being in stock Slackware. > > > -- > Ozan, BSc, BEng > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From adev at linuxmail.org Sat Feb 25 04:17:27 2012 From: adev at linuxmail.org (adev at linuxmail.org) Date: Fri, 24 Feb 2012 23:17:27 -0500 Subject: [Slackbuilds-users] murmur SlackBuild Message-ID: <20120225041727.42960@gmx.com> I apologize for the delay in response. I'm no longer maintaining murmur, I was under the impression that mumble would be packaged with murmur as they both already share the same source tarball. Anyway, I'm forwarding this to the SBo mailing list as I am granting you permission to take over maintenance of murmur. Thank you. ----- Original Message ----- From: James Geboski Sent: 02/13/12 03:46 PM To: adev at linuxmail.org Subject: murmur SlackBuild Hello there, I don't know if murmur SlackBuild has just been forgotten about or what but, there is now version 1.2.3. All that really needs to be added to the SlackBuild are some config options: no-ice, no-bonjour. I have attached a patch if you're interested in that. Also, if you're not up for continuing the maintenance on this SlackBuild anymore, I'd be willing to maintain the build script. James -------------- next part -------------- An HTML attachment was scrubbed... URL: From niels.horn at gmail.com Sat Feb 25 21:17:36 2012 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 25 Feb 2012 19:17:36 -0200 Subject: [Slackbuilds-users] Why are ORBit2 and GConf available on SBo? In-Reply-To: References: Message-ID: On Sat, Feb 25, 2012 at 6:57 PM, Doogster wrote: > Sure it does. That's why nothing *else* in /extra is in SBo. > > On Sat, Feb 25, 2012 at 10:07 AM, Ozan T?rky?lmaz > wrote: >> 2012/2/25 Doogster : >>> Why are ORBit2 and GConf available on SBo? They're included with >>> Slackware, in the /extra/google-chrome directory. >> >> Being in extra does not make it being in stock Slackware. >> >> >> -- >> Ozan, BSc, BEng Some explanations: 1) A package in "extra" is not considered part of a "full instalation" - it is an optional package. 2) GConf and ORBit2 are in extra because of chrome - and that's why they live in that subdirectory 3) We keep them in SlackBuilds.org because some packages might need newer versions (and we actually have a newer version of GConf on SBo) Hope this clears it up a bit :) -- Niels Horn From mpagnan at acanac.net Sat Feb 25 21:27:36 2012 From: mpagnan at acanac.net (Martin Pagnan) Date: Sat, 25 Feb 2012 16:27:36 -0500 Subject: [Slackbuilds-users] Kompozer In-Reply-To: References: <4F492753.8080809@acanac.net> Message-ID: <4F495248.5020703@acanac.net> Thanks. I am running 64 bit and I ran it through the multilib make-compat utility with the same result. On 25/02/2012 3:03 PM, Matteo Bernardini wrote: > I just checked and it seems to be a 32bit only application: are you > trying to use it on 64bit? > Then you should go multilib for that > > http://connie.slackware.com/~alien/multilib/ > > but, strictly regarding slackbuilds.org, I think running it on a 64bit > is considered unsupported. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From mpagnan at acanac.net Sat Feb 25 21:28:54 2012 From: mpagnan at acanac.net (Martin Pagnan) Date: Sat, 25 Feb 2012 16:28:54 -0500 Subject: [Slackbuilds-users] Kompozer In-Reply-To: References: <4F492753.8080809@acanac.net> Message-ID: <4F495296.5080805@acanac.net> I was hoping to avoid that but if compiling from source is the only way, I will give it a try. On 25/02/2012 3:28 PM, Niels Horn wrote: > On Sat, Feb 25, 2012 at 6:03 PM, Matteo Bernardini > wrote: >> I just checked and it seems to be a 32bit only application: are you >> trying to use it on 64bit? >> Then you should go multilib for that >> >> http://connie.slackware.com/~alien/multilib/ >> >> but, strictly regarding slackbuilds.org, I think running it on a 64bit >> is considered unsupported. >> >> Matteo > You could try to build kompozer from source, but that's not what the > SlackBuild script does... :) > > -- > Niels Horn > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From jens at tuxane.com Sat Feb 25 22:55:24 2012 From: jens at tuxane.com (TuxaneSoft) Date: Sat, 25 Feb 2012 23:55:24 +0100 Subject: [Slackbuilds-users] Kompozer In-Reply-To: <4F495248.5020703@acanac.net> References: <4F492753.8080809@acanac.net> <4F495248.5020703@acanac.net> Message-ID: <1330210524.6390.2.camel@data.tuxane.local> Am Samstag, den 25.02.2012, 16:27 -0500 schrieb Martin Pagnan: > Thanks. I am running 64 bit and I ran it through the multilib > make-compat utility with the same result. Did you convert only the one package, or did you install *all* of the multilib layer ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dragonwisard at gmail.com Sun Feb 26 00:26:36 2012 From: dragonwisard at gmail.com (Ben Mendis) Date: Sat, 25 Feb 2012 19:26:36 -0500 Subject: [Slackbuilds-users] murmur SlackBuild In-Reply-To: References: <20120225041727.42960@gmx.com> Message-ID: I concur, FWIW. I am the same way, I use the client on a lot of systems but only run the server on a headless server. I feel like it's natural to split them into two packages even though they share the same source package. I also agree that 'murmur' makes more sense than 'mumble-server'. On Sat, Feb 25, 2012 at 1:54 AM, King Beowulf wrote: > On Fri, Feb 24, 2012 at 9:51 PM, James Geboski wrote: > >> Hello, >> >> No worries about the delay. I personally, find it more useful to have >> them split into two packages. Reason being, I do not have any of the >> X libraries on the servers I am running murmur on. And on the client end, >> you really don't need murmur. If anyone has any objections to this, please >> inform me. >> >> Also, I'd find it "cleaner" to have /var/{lib,log,run}/mumble-server >> renamed to /var/{lib,log,run}/murmur. This way it matches the naming of >> rc.murmur and murmurd. However, people would not really be able upgrade >> the package if this was implemented. Would this be a forbidden to do in >> the SlackBuild? >> >> James >> >> > I agree on keeping the 2 as separate packages. I'm running murmur-1.2.3 on > a headless box, and mumble-1.2.3 on the GUI clients. 2 packages keep it > cleaner and simpler. > > As for '/var/{lib,log,run}/murmur' I can accept the rename. A simple > warning statement about doing a clean install in the readme should be > sufficient. After all, we all read the readmes, right? > > -Ed > > -- > You! What PLANET is this! > -- McCoy, "The City on the Edge of Forever", stardate 3134.0 > > > _______________________________________________ > 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 mpagnan at acanac.net Sun Feb 26 15:48:44 2012 From: mpagnan at acanac.net (Martin Pagnan) Date: Sun, 26 Feb 2012 10:48:44 -0500 Subject: [Slackbuilds-users] Kompozer In-Reply-To: <1330210524.6390.2.camel@data.tuxane.local> References: <4F492753.8080809@acanac.net><4F495248.5020703@acanac.net> <1330210524.6390.2.camel@data.tuxane.local> Message-ID: <4F4A545C.8050406@acanac.net> Hmmm. Maybe I can learn something here. I converted just the one because the "all" had been done months before for the other 32bit packages. On 25/02/2012 5:55 PM, TuxaneSoft wrote: > > > > > > Am Samstag, den 25.02.2012, 16:27 -0500 schrieb Martin Pagnan: >> Thanks. I am running 64 bit and I ran it through the multilib >> make-compat utility with the same result. > > Did you convert only the one package, or did you install *all* of the > multilib layer ? > > > > > _______________________________________________ > 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 cancellor2 at gmail.com Mon Feb 27 12:05:00 2012 From: cancellor2 at gmail.com (Fridrich von Stauffenberg) Date: Mon, 27 Feb 2012 14:05:00 +0200 Subject: [Slackbuilds-users] Some download links should be fixed Message-ID: <4F4B716C.2020305@gmail.com> xalan-c: Source tarball has been moved from http://www.apache.org/dist/xml/xalan-c/Xalan-C_1_10_0-src.tar.gz to http://www.apache.org/dist/xml/xalan-c/source/Xalan-C_1_10_0-src.tar.gz apache-ivy: DNS lookup for mirror.cloudera.com returns NXDOMAIN, so I suggest to change http://mirror.cloudera.com/apache/ant/ivy/2.2.0/apache-ivy-2.2.0-bin.tar.gz to http://apache.cp.if.ua/ant/ivy/2.2.0/apache-ivy-2.2.0-bin.tar.gz Regards From mario at slackverse.org Wed Feb 29 08:36:10 2012 From: mario at slackverse.org (Mario) Date: Wed, 29 Feb 2012 09:36:10 +0100 Subject: [Slackbuilds-users] SlackBuilds - gtk-kde4 In-Reply-To: References: Message-ID: <4F4DE37A.1090803@slackverse.org> On 02/29/2012 04:25 AM, Gabriel Magno wrote: > Hello. > > I'm here to notify you that, by this time, your script for "gtk-kde4" is > not working > because of a 404 error of the original link for download, from > http://kde-apps.org/content/show.php?content=74689: > http://betta.houa.org/no-site/gtk-kde4(src)0.9.4.tar.gz > > I'm wondering if you could update your script for version 0.9.5, which > the link is not missing and is working: > http://kde-apps.org/CONTENT/content-files/74689-gtk-kde4(src)0.9.5.tar.gz > > Regards > > -- > Gabriel Magno I will CC SBo lists on this one, because I no longer use KDE there is no way for me to test/support this slackbuild any longer, if someone wants to take over the maintenance, feel free to do so. Best regards, mario