From mickeytintincolle at yahoo.fr Tue Jul 1 14:22:57 2008 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Tue, 1 Jul 2008 16:22:57 +0200 Subject: [Slackbuilds-users] Xarchiver 0.4.6 Message-ID: <20080701162257.1b6326e6@slack.volderking.com> The Xarchiver 0.4.6 SlackBuild tarball contains the URL of the Xarchiver tarball, but it is a dl.sourceforge.net URL that works bad . I suggest replacing "dl.souceforge.net" by "prdownloads.sourceforge.net" that works better . From asamardzic at gmail.com Tue Jul 1 14:08:13 2008 From: asamardzic at gmail.com (Aleksandar Samardzic) Date: Tue, 1 Jul 2008 16:08:13 +0200 Subject: [Slackbuilds-users] Xarchiver 0.4.6 In-Reply-To: <20080701162257.1b6326e6@slack.volderking.com> References: <20080701162257.1b6326e6@slack.volderking.com> Message-ID: On Tue, Jul 1, 2008 at 4:22 PM, Antoine NONYME wrote: > The Xarchiver 0.4.6 SlackBuild tarball contains the URL of the > Xarchiver tarball, but it is a dl.sourceforge.net URL that works bad . > I suggest replacing "dl.souceforge.net" by > "prdownloads.sourceforge.net" that works better . This kind of stuff is already discussed on this list, see for example this thread: http://lists.slackbuilds.org/pipermail/slackbuilds-users/2007-October/001925.html Regards, Alex From rshepard at appl-ecosys.com Thu Jul 3 14:16:41 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 3 Jul 2008 07:16:41 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 Message-ID: I've been using Eric's script for Scribus for the past two years (since -1.3.3.2), and I used it for the latest, -1.3.3.12. However, there's apparently a bug introduced in this version that prevents the File -> New from Template menu option from appearing. My message to the scribus user's mail list brought a response that the ./configure process does not work with this version but the CMake process does. I do not have cmake installed and have no idea how to configure and use it. I certainly don't understand why the ./configure process will not include a menu item. While I don't use Scribus regularly, I do use it on occasion, and this is one of those occasions. I'd also like to restore that menu option. Is there a way to do this with the current version or should I back up one version and rebuild that one? TIA, Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From pc_warner at yahoo.com Thu Jul 3 15:18:21 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Thu, 3 Jul 2008 08:18:21 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: Message-ID: <633604.71719.qm@web57715.mail.re3.yahoo.com> I can at least say that I don't see the bug in 1.3.3.11. I have not upraded to 1.3.3.12, but as you can see newer is not always better. cmake is a slackware package, so it should be no problem to install it if you need it. I think the documentation included in the source gives you directions on cmake usage. --phil --- On Thu, 7/3/08, Rich Shepard wrote: > From: Rich Shepard > Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 > To: slackbuilds-users at slackbuilds.org > Date: Thursday, July 3, 2008, 7:16 AM > I've been using Eric's script for Scribus for the > past two years (since > -1.3.3.2), and I used it for the latest, -1.3.3.12. > However, there's > apparently a bug introduced in this version that prevents > the File -> New > from Template menu option from appearing. > > My message to the scribus user's mail list brought a > response that the > ./configure process does not work with this version but the > CMake process > does. I do not have cmake installed and have no idea how to > configure and use > it. I certainly don't understand why the ./configure > process will not > include a menu item. > > While I don't use Scribus regularly, I do use it on > occasion, and this is > one of those occasions. I'd also like to restore that > menu option. > > Is there a way to do this with the current version or > should I back up one > version and rebuild that one? > > TIA, > > Rich > > -- > Richard B. Shepard, Ph.D. | Integrity > Credibility > Applied Ecosystem Services, Inc. | > Innovation > Voice: 503-667-4517 > Fax: 503-667-8863 > _______________________________________________ > 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 rshepard at appl-ecosys.com Thu Jul 3 15:26:16 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 3 Jul 2008 08:26:16 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: <633604.71719.qm@web57715.mail.re3.yahoo.com> References: <633604.71719.qm@web57715.mail.re3.yahoo.com> Message-ID: On Thu, 3 Jul 2008, Phillip Warner wrote: > I can at least say that I don't see the bug in 1.3.3.11. Phil, I didn't, either. > I have not upraded to 1.3.3.12, but as you can see newer is not always > better. True. With office automation tools I try to use the latest release. > cmake is a slackware package, so it should be no problem to install it if > you need it. I think the documentation included in the source gives you > directions on cmake usage. I assumed it was, but hadn't looked. Rather than futzing to get .12 working, I'll back up to .11. Thanks, Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From HMWiesinger at gmx.at Thu Jul 3 17:02:54 2008 From: HMWiesinger at gmx.at (Heinz Wiesinger) Date: Thu, 3 Jul 2008 19:02:54 +0200 Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: References: <633604.71719.qm@web57715.mail.re3.yahoo.com> Message-ID: <200807031902.56912.HMWiesinger@gmx.at> Rich Shepard wrote: > On Thu, 3 Jul 2008, Phillip Warner wrote: > > I can at least say that I don't see the bug in 1.3.3.11. > > Phil, > > I didn't, either. > > > I have not upraded to 1.3.3.12, but as you can see newer is not always > > better. > > True. With office automation tools I try to use the latest release. > > > cmake is a slackware package, so it should be no problem to install it if > > you need it. I think the documentation included in the source gives you > > directions on cmake usage. > > I assumed it was, but hadn't looked. > > Rather than futzing to get .12 working, I'll back up to .11. > I have updated the script for 1.3.4, which uses cmake too. It shouldn't be that much of a problem changing the script to work with 1.3.3.12 too. Interested? Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From rshepard at appl-ecosys.com Thu Jul 3 17:12:59 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 3 Jul 2008 10:12:59 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: <200807031902.56912.HMWiesinger@gmx.at> References: <633604.71719.qm@web57715.mail.re3.yahoo.com> <200807031902.56912.HMWiesinger@gmx.at> Message-ID: On Thu, 3 Jul 2008, Heinz Wiesinger wrote: > I have updated the script for 1.3.4, which uses cmake too. It shouldn't be > that much of a problem changing the script to work with 1.3.3.12 too. > Interested? Heinz, Sure. Apparently the Scribus developers feel that the ./configure process is too much work for them and they will be using cmake from now on. Oh, well. I will happily run your script on 1.3.3.12 and provide feedback. Many thanks, Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From HMWiesinger at gmx.at Thu Jul 3 17:19:25 2008 From: HMWiesinger at gmx.at (Heinz Wiesinger) Date: Thu, 3 Jul 2008 19:19:25 +0200 Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: References: <633604.71719.qm@web57715.mail.re3.yahoo.com> <200807031902.56912.HMWiesinger@gmx.at> Message-ID: <200807031919.29638.HMWiesinger@gmx.at> Rich Shepard wrote: > On Thu, 3 Jul 2008, Heinz Wiesinger wrote: > > I have updated the script for 1.3.4, which uses cmake too. It shouldn't > > be that much of a problem changing the script to work with 1.3.3.12 too. > > Interested? > > Heinz, > > Sure. Apparently the Scribus developers feel that the ./configure > process is too much work for them and they will be using cmake from now on. > Oh, well. > > I will happily run your script on 1.3.3.12 and provide feedback. > Cool :) Here's the link: http://hw.3kisses.net/files/SlackBuilds/scribus.tar.gz Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From rshepard at appl-ecosys.com Thu Jul 3 17:44:08 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 3 Jul 2008 10:44:08 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: <200807031919.29638.HMWiesinger@gmx.at> References: <633604.71719.qm@web57715.mail.re3.yahoo.com> <200807031902.56912.HMWiesinger@gmx.at> <200807031919.29638.HMWiesinger@gmx.at> Message-ID: On Thu, 3 Jul 2008, Heinz Wiesinger wrote: > Here's the link: > http://hw.3kisses.net/files/SlackBuilds/scribus.tar.gz Heinz, Well, now I have a reason to upgrade my server/workstation to 12.0 and 12.1 from 11.0: no cmake in 11.0. Normally it's no big deal to upgrade from one version to another. But, the changes in Xfce from 4.2.3.2 to 4.4.2 are major, and took me a few hours to get my notebook back in my prefered format. Sigh. Later, Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From HMWiesinger at gmx.at Thu Jul 3 17:48:18 2008 From: HMWiesinger at gmx.at (Heinz Wiesinger) Date: Thu, 3 Jul 2008 19:48:18 +0200 Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: References: <633604.71719.qm@web57715.mail.re3.yahoo.com> <200807031919.29638.HMWiesinger@gmx.at> Message-ID: <200807031948.20890.HMWiesinger@gmx.at> Am Donnerstag, 3. Juli 2008 19:44:08 schrieb Rich Shepard: > On Thu, 3 Jul 2008, Heinz Wiesinger wrote: > > Here's the link: > > http://hw.3kisses.net/files/SlackBuilds/scribus.tar.gz > > Heinz, > > Well, now I have a reason to upgrade my server/workstation to 12.0 and > 12.1 from 11.0: no cmake in 11.0. Well, there is a cmake build script in the 11.0 section on SBo. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From rshepard at appl-ecosys.com Thu Jul 3 18:06:42 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 3 Jul 2008 11:06:42 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: <200807031948.20890.HMWiesinger@gmx.at> References: <633604.71719.qm@web57715.mail.re3.yahoo.com> <200807031919.29638.HMWiesinger@gmx.at> <200807031948.20890.HMWiesinger@gmx.at> Message-ID: On Thu, 3 Jul 2008, Heinz Wiesinger wrote: > Well, there is a cmake build script in the 11.0 section on SBo. Oh! Well, I'll do that right now, then. Many thanks, Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From rshepard at appl-ecosys.com Thu Jul 3 19:06:54 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 3 Jul 2008 12:06:54 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: <200807031948.20890.HMWiesinger@gmx.at> References: <633604.71719.qm@web57715.mail.re3.yahoo.com> <200807031919.29638.HMWiesinger@gmx.at> <200807031948.20890.HMWiesinger@gmx.at> Message-ID: On Thu, 3 Jul 2008, Heinz Wiesinger wrote: > Well, there is a cmake build script in the 11.0 section on SBo. Worked perfectly. Of course. Thanks, Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From rshepard at appl-ecosys.com Thu Jul 3 20:56:50 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 3 Jul 2008 13:56:50 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 -- SOLVED In-Reply-To: <200807031919.29638.HMWiesinger@gmx.at> References: <633604.71719.qm@web57715.mail.re3.yahoo.com> <200807031902.56912.HMWiesinger@gmx.at> <200807031919.29638.HMWiesinger@gmx.at> Message-ID: On Thu, 3 Jul 2008, Heinz Wiesinger wrote: >> I will happily run your script on 1.3.3.12 and provide feedback. >> > Cool :) To complete this thread, two changes were needed to the script to make it work with 1.3.3.12. Building with cmake rather than configure fixed the missing menu item. My thanks to Heinz. Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From pc_warner at yahoo.com Fri Jul 4 05:50:06 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Thu, 3 Jul 2008 22:50:06 -0700 (PDT) Subject: [Slackbuilds-users] Problems with Scribus-1.3.3.12 In-Reply-To: <200807031948.20890.HMWiesinger@gmx.at> Message-ID: <355993.15519.qm@web57713.mail.re3.yahoo.com> You gotta love how Pat adds some past SBo packages into Slackware. SBo users get some -current packages before they are even in -current. :) --phil --- On Thu, 7/3/08, Heinz Wiesinger wrote: > From: Heinz Wiesinger > Subject: Re: [Slackbuilds-users] Problems with Scribus-1.3.3.12 > To: "SlackBuilds.org Users List" > Date: Thursday, July 3, 2008, 10:48 AM > Am Donnerstag, 3. Juli 2008 19:44:08 schrieb Rich Shepard: > > On Thu, 3 Jul 2008, Heinz Wiesinger wrote: > > > Here's the link: > > > > http://hw.3kisses.net/files/SlackBuilds/scribus.tar.gz > > > > Heinz, > > > > Well, now I have a reason to upgrade my > server/workstation to 12.0 and > > 12.1 from 11.0: no cmake in 11.0. > > Well, there is a cmake build script in the 11.0 section on > SBo._______________________________________________ > 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 chess at chessgriffin.com Sat Jul 5 18:39:43 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Sat, 5 Jul 2008 14:39:43 -0400 Subject: [Slackbuilds-users] Fwd: bug on openbox package In-Reply-To: <518314.17099.qm@web57706.mail.re3.yahoo.com> References: <8682df160806241422i3db6569bg539789bf7abc5a46@mail.gmail.com> <518314.17099.qm@web57706.mail.re3.yahoo.com> Message-ID: <8682df160807051139h665d53f9w725cb0af9ab3c706@mail.gmail.com> On Wed, Jun 25, 2008 at 2:38 AM, Phillip Warner wrote: > Actually, after I thought about this for a second the solution is simple. > The openbox.desktop file that is in question is actually a part of the > kdebase package. It doesn't get used until there is a xinitrc file for > openbox available. The openbox slackBuild has the xinitrc's for openbox > (session), openbox-KDE, and openbox-GNOME, and the corresponding .desktop > files are in > /usr/share/xsessions/openbox*. This seemed to work fine in Slackware 12.0, > but I don't think KDM in Slackware 12.1 looks there anymore. As a result > only the stock openbox.desktop file (under > /usr/share/apps/kdm/sessions from the kdebase package) is used. > > The solution is to either move or symlink the created .desktop files under > /usr/share/xsessions/ > so that they are in > /usr/share/apps/kdm/sessions/ > > If you don't want the stock .desktop file to be overwritten (this is ideal), > you should rename the new openbox.desktop file to openbox-session.desktop > and change the "Name" field to something like Openbox-Session. The > slackBuild README should then inform the user to use Openbox-Session if they > want to use the autostart file. > > Hopefully this clears everything up. > > --phil > Ok, I think I'm pretty much back in the saddle again. :-) I've read through this thread a couple of times and I don't use KDM or have any KDE packages installed, so I might need some clarification of the issue and possible solution. The thing that jumps out at me, though, is that I'm not sure this is an issue with the openbox SlackBuild. From what I gather, it seems to be a kdebase/KDM issue. Is that correct? In other words, is the problem that the openbox.desktop file that ships with KDM should exec openbox-session and not openbox? -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com From rworkman at slackbuilds.org Sat Jul 5 19:01:31 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 05 Jul 2008 14:01:31 -0500 Subject: [Slackbuilds-users] Fwd: bug on openbox package In-Reply-To: <8682df160807051139h665d53f9w725cb0af9ab3c706@mail.gmail.com> References: <8682df160806241422i3db6569bg539789bf7abc5a46@mail.gmail.com> <518314.17099.qm@web57706.mail.re3.yahoo.com> <8682df160807051139h665d53f9w725cb0af9ab3c706@mail.gmail.com> Message-ID: <486FC50B.1080506@slackbuilds.org> Chess Griffin wrote: > On Wed, Jun 25, 2008 at 2:38 AM, Phillip Warner wrote: >> Actually, after I thought about this for a second the solution is simple. >> The openbox.desktop file that is in question is actually a part of the >> kdebase package. It doesn't get used until there is a xinitrc file for >> openbox available. The openbox slackBuild has the xinitrc's for openbox >> (session), openbox-KDE, and openbox-GNOME, and the corresponding .desktop >> files are in >> /usr/share/xsessions/openbox*. This seemed to work fine in Slackware 12.0, >> but I don't think KDM in Slackware 12.1 looks there anymore. As a result >> only the stock openbox.desktop file (under >> /usr/share/apps/kdm/sessions from the kdebase package) is used. >> >> The solution is to either move or symlink the created .desktop files under >> /usr/share/xsessions/ >> so that they are in >> /usr/share/apps/kdm/sessions/ >> >> If you don't want the stock .desktop file to be overwritten (this is ideal), >> you should rename the new openbox.desktop file to openbox-session.desktop >> and change the "Name" field to something like Openbox-Session. The >> slackBuild README should then inform the user to use Openbox-Session if they >> want to use the autostart file. >> >> Hopefully this clears everything up. >> >> > > Ok, I think I'm pretty much back in the saddle again. :-) > > I've read through this thread a couple of times and I don't use KDM or > have any KDE packages installed, so I might need some clarification of > the issue and possible solution. The thing that jumps out at me, > though, is that I'm not sure this is an issue with the openbox > SlackBuild. From what I gather, it seems to be a kdebase/KDM issue. > Is that correct? In other words, is the problem that the > openbox.desktop file that ships with KDM should exec openbox-session > and not openbox? That's how I understood it, and I think that's what Phil's solution is aiming to address. I'd wait for his assessment, though :) -RW From pc_warner at yahoo.com Sat Jul 5 21:20:20 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Sat, 5 Jul 2008 14:20:20 -0700 (PDT) Subject: [Slackbuilds-users] Fwd: bug on openbox package In-Reply-To: <8682df160807051139h665d53f9w725cb0af9ab3c706@mail.gmail.com> Message-ID: <249935.23575.qm@web57704.mail.re3.yahoo.com> Yes, the stock openbox.desktop file from the kdebase package should execute openbox-session. However, the problem is more than that. The new kdm doesn't seem to make use of the .desktop files under /usr/share/xsessions/, which is where Openbox puts them by default. Thus, in order for the Slackware 12.1 Openbox slackBuild to work properly with KDM, the openbox*.desktop files under there must either be moved or have a corresponding symlink in /usr/share/apps/kdm/sessions/ (the latter is probably better in case someone is using something other than kdm). The default location was fine in the kdm in Slackware 12.0. So, yes, you can say that it is a kdm problem and not a problem with the slackBuild per se, but it is a problem that can easily be fixed by a couple of minor changes to the slackBuild. It is a little more complicated if you want to avoid overwriting the stock openbox.desktop file from kdebase, but it is still very feasible. To preserve the stock openbox.desktop session you would want the new one to be named openbox-session.desktop with a Name value of Openbox-Session or something similar (so you would have to sed the file). The new kdm doesn't appear to list session options unless there is a corresponding xinitrc file so you would need the xinitrc file with a corresponding name (xinitrc.openbox-session). You could also have a corresponding xinitrc.openbox file (that would just execute openbox instead of openbox-session on the last line) so that the stock openbox.desktop file could be used. This would provide the most natural (ie what the openbox developers intended) setup, and it would avoid overwriting stock Slackware files. I could quickly modify the slackBuild and send it to you if you would like. It might be an easier way to see the solution I am proposing. --phil --- On Sat, 7/5/08, Chess Griffin wrote: > From: Chess Griffin > Subject: Re: [Slackbuilds-users] Fwd: bug on openbox package > To: "SlackBuilds.org Users List" > Date: Saturday, July 5, 2008, 11:39 AM > On Wed, Jun 25, 2008 at 2:38 AM, Phillip Warner > wrote: > > Actually, after I thought about this for a second the > solution is simple. > > The openbox.desktop file that is in question is > actually a part of the > > kdebase package. It doesn't get used until there > is a xinitrc file for > > openbox available. The openbox slackBuild has the > xinitrc's for openbox > > (session), openbox-KDE, and openbox-GNOME, and the > corresponding .desktop > > files are in > > /usr/share/xsessions/openbox*. This seemed to work > fine in Slackware 12.0, > > but I don't think KDM in Slackware 12.1 looks > there anymore. As a result > > only the stock openbox.desktop file (under > > /usr/share/apps/kdm/sessions from the kdebase package) > is used. > > > > The solution is to either move or symlink the created > .desktop files under > > /usr/share/xsessions/ > > so that they are in > > /usr/share/apps/kdm/sessions/ > > > > If you don't want the stock .desktop file to be > overwritten (this is ideal), > > you should rename the new openbox.desktop file to > openbox-session.desktop > > and change the "Name" field to something > like Openbox-Session. The > > slackBuild README should then inform the user to use > Openbox-Session if they > > want to use the autostart file. > > > > Hopefully this clears everything up. > > > > --phil > > > > Ok, I think I'm pretty much back in the saddle again. > :-) > > I've read through this thread a couple of times and I > don't use KDM or > have any KDE packages installed, so I might need some > clarification of > the issue and possible solution. The thing that jumps out > at me, > though, is that I'm not sure this is an issue with the > openbox > SlackBuild. From what I gather, it seems to be a > kdebase/KDM issue. > Is that correct? In other words, is the problem that the > openbox.desktop file that ships with KDM should exec > openbox-session > and not openbox? > > -- > Chess Griffin > GPG Public Key: 0x0C7558C3 > http://www.chessgriffin.com > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - > http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ From andrew.david.45 at gmail.com Sun Jul 6 01:09:17 2008 From: andrew.david.45 at gmail.com (andrew) Date: Sun, 6 Jul 2008 11:09:17 +1000 Subject: [Slackbuilds-users] Leafnode 2 script Message-ID: <20080706010917.GA21417@ilium.andrews-corner.org> Hi, There has been a small upgrade to the Leafnode 2 source code. Should I resubmit the full package myself or can the download link and script be modified at slackbuilds.org to: http://home.pages.de/~mandree/leafnode/beta/leafnode-2.0.0.alpha20080624a.tar.bz2 PRGNAM=leafnode VERSION=2.0.0.alpha20080624a The leafnode changes are quite small but I guess the improvements in logging make it a worthwhile upgrade. Andrew -- Do you think that's air you're breathing now? From chess at chessgriffin.com Sun Jul 6 03:07:27 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Sat, 5 Jul 2008 23:07:27 -0400 Subject: [Slackbuilds-users] Fwd: bug on openbox package In-Reply-To: <249935.23575.qm@web57704.mail.re3.yahoo.com> References: <8682df160807051139h665d53f9w725cb0af9ab3c706@mail.gmail.com> <249935.23575.qm@web57704.mail.re3.yahoo.com> Message-ID: <8682df160807052007y64b1e87t7feae3527580352a@mail.gmail.com> On Sat, Jul 5, 2008 at 5:20 PM, Phillip Warner wrote: > Yes, the stock openbox.desktop file from the kdebase package should execute openbox-session. However, the problem is more than that. The new kdm doesn't seem to make use of the .desktop files under /usr/share/xsessions/, which is where Openbox puts them by default. Thus, in order for the Slackware 12.1 Openbox slackBuild to work properly with KDM, the openbox*.desktop files under there must either be moved or have a corresponding symlink in /usr/share/apps/kdm/sessions/ (the latter is probably better in case someone is using something other than kdm). The default location was fine in the kdm in Slackware 12.0. > Phil, Thanks for your very helpful explanation. I do see the issue and agree with your proposed solutions. I also think we definitely do not want to overwrite any stock Slackware files and at the same time preserve the ability to use the SlackBuild for those that do not use KDE or KDM. I also like your suggestion to have both the xinitrc.openbox-session and xinitrc.openbox setup as originally intended by the Openbox developers. If I understand your solution correctly, we would need to (1) create a new xinitrc-session.desktop file and install it into the default Openbox location along with the other Openbox *desktop files (2) symlink all the Openbox *desktop files including the new xinitrc-session.desktop file to the KDM location and (3) create a new xinitrc.openbox-session file along with the current xinitrc.openbox that already comes with the SlackBuild? Since we already include a xinitrc.openbox file in the SlackBuild, I assume then the stock openbox.desktop file works ok for someone who does not want to launch an Openbox session but just straight Openbox? In any event, yes, if you have the time to send your modifications to the SlackBuild and related files that would be great. Otherwise, I'll try and work on this during the coming week. In the meantime, I'll install KDE and KDM on one of my Slack machines so I can test and get a better feel for what KDM is doing behind the scenes. I've never been a graphical login kind of person, which is why it's taken me longer than normal to get the issue here. It has nothing to do with the fact that I'm about to turn 40 or the loss of brain cells from one too many pints of Guinness in my youth. At least, that's my story and I'm sticking to it. Thanks again for your help, Phil, and to Bruno for the original bug report. -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com From lukenshiro at ngi.it Sun Jul 6 20:00:47 2008 From: lukenshiro at ngi.it (LukenShiro) Date: Sun, 6 Jul 2008 22:00:47 +0200 Subject: [Slackbuilds-users] DevIL Message-ID: <200807062200.48257.lukenshiro@ngi.it> I've noticed libraries/DevIL got lost in transfer form 12.0 to 12.1 BTW compiling 12.0 version's DevIL slackbuild I've seen an error in "include/IL/ilut.h" file while compiling (it seems to lack a capital letter "I" just before Lstring): [..] In file included from ../../src-ILUT/include/ilut_internal.h:39, from ilut_allegro.c:14: ../../include/IL/ilut.h:237: error: expected ?)? before ?FileName? make[2]: *** [ilut_allegro.lo] Error 1 make[2]: Leaving directory `/tmp/SBo/DevIL-1.6.8/src-ILUT/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/DevIL-1.6.8/src-ILUT' make: *** [all-recursive] Error 1 So I've modified it: ==================================================== --- /tmp/SBo/DevIL-1.6.8/include/IL/ilut.h 2006-07-04 16:43:23.000000000 +0200 +++ ilut.h_new 2008-07-06 21:21:13.718281714 +0200 @@ -234,7 +234,7 @@ extern "C" { #endif - ILAPI BITMAP* ILAPIENTRY ilutAllegLoadImage(Lstring FileName); + ILAPI BITMAP* ILAPIENTRY ilutAllegLoadImage(ILstring FileName); ILAPI BITMAP* ILAPIENTRY ilutConvertToAlleg(PALETTE Pal); #endif//ILUT_USE_ALLEGRO ==================================================== After editing it compiles well (maybe it hasn't been noticed before, because allegro was not installed and this chunk's use depends on allegro availability? Just a guess). -- GNU/Linux * Slackware 'current' LU #210970 LM #98222 SU #12583 "A celebrity is a person who is known for his well-knownness." From josiahb at gmail.com Sun Jul 6 20:51:04 2008 From: josiahb at gmail.com (Josiah Boothby) Date: Sun, 6 Jul 2008 13:51:04 -0700 Subject: [Slackbuilds-users] lyx_qt4 depends on libaudio? Message-ID: <6eb14ed10807061351q23c8a927o5b94cb3b5ba1cdf@mail.gmail.com> Hello, Using SBo's qt4 and lyx_qt4 on Slackware 12.1, I get the following error when trying to run lyx: lyx: error while loading shared libraries: libaudio.so.2: cannot open shared object file: No such file or directory Looking around on the internet has indicated that libaudio.so.2 would be provided by NAS (which is not distributed by Slackware, and doesn't appear to be on SBo). This does not appear to be a problem with the other qt4 programs I've tried to run (e.g., qtconfig). Is there something I'm missing? Thank you, Josiah From rworkman at slackbuilds.org Sun Jul 6 23:41:41 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 06 Jul 2008 18:41:41 -0500 Subject: [Slackbuilds-users] lyx_qt4 depends on libaudio? In-Reply-To: <6eb14ed10807061351q23c8a927o5b94cb3b5ba1cdf@mail.gmail.com> References: <6eb14ed10807061351q23c8a927o5b94cb3b5ba1cdf@mail.gmail.com> Message-ID: <48715835.2030102@slackbuilds.org> Josiah Boothby wrote: > Hello, > > Using SBo's qt4 and lyx_qt4 on Slackware 12.1, I get the following > error when trying to run lyx: > > lyx: error while loading shared libraries: libaudio.so.2: cannot open > shared object file: No such file or directory > > Looking around on the internet has indicated that libaudio.so.2 would > be provided by NAS (which is not distributed by Slackware, and doesn't > appear to be on SBo). This does not appear to be a problem with the > other qt4 programs I've tried to run (e.g., qtconfig). > > Is there something I'm missing? Yep - libaudio.so.2 ;-) On a more serious note, it looks like you either: a) used to have libaudio installed, and compiled something [1] that links it. [1] that something is apparently being linked by either qt or lyx (almost surely lyx), and then that something in turn is trying to find everything it links to. b) have a package installed from somewhere that wants libaudio, and lyx is linking to something in that package, which in turn wants libaudio. As you can see, it's essentially the same thing in either a or b. -RW From pc_warner at yahoo.com Mon Jul 7 03:42:31 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Sun, 6 Jul 2008 20:42:31 -0700 (PDT) Subject: [Slackbuilds-users] DevIL In-Reply-To: <200807062200.48257.lukenshiro@ngi.it> Message-ID: <570603.88299.qm@web57713.mail.re3.yahoo.com> DevIL did not just get lost in the transfer from 12.0 to 12.1. David Somero brought the new gcc issues to my attention back in early April and I developed a full patch to fix those issues (*much* more is needed than just the small patch you have shown- it will compile, but it will be a broken, buggy library). However, the patch I made was quite ugly and so I contacted the DevIL developers about releasing an official patch or a cvs snapshot. I have not received a response from them for over two months now. I sent a reminder to them about this last week. You are actually the first person other than David who has requested a fix for this. I actually stopped using DevIL in favor of some other image libraries, but I still have all the files from the new slackBuild I made. Since upstream support seems to be waning perhaps it is time I post what I made. What do you think, David? Also, do you want me to continue a copy of this thread in the slackbuilds-devel mailing list as it was before? --phil --- On Sun, 7/6/08, LukenShiro wrote: > From: LukenShiro > Subject: DevIL > To: slackbuilds-users at slackbuilds.org > Cc: "Phillip Warner" > Date: Sunday, July 6, 2008, 1:00 PM > I've noticed libraries/DevIL got lost in transfer form > 12.0 to 12.1 > > > > BTW compiling 12.0 version's DevIL slackbuild I've > seen an error > in "include/IL/ilut.h" file while compiling (it > seems to lack a capital > letter "I" just before Lstring): > > [..] > In file included from > ../../src-ILUT/include/ilut_internal.h:39, > from ilut_allegro.c:14: > ../../include/IL/ilut.h:237: error: expected ?)? before > ?FileName? > make[2]: *** [ilut_allegro.lo] Error 1 > make[2]: Leaving directory > `/tmp/SBo/DevIL-1.6.8/src-ILUT/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/tmp/SBo/DevIL-1.6.8/src-ILUT' > make: *** [all-recursive] Error 1 > > So I've modified it: > ==================================================== > --- /tmp/SBo/DevIL-1.6.8/include/IL/ilut.h 2006-07-04 > 16:43:23.000000000 > +0200 > +++ ilut.h_new 2008-07-06 21:21:13.718281714 +0200 > @@ -234,7 +234,7 @@ > extern "C" { > #endif > > - ILAPI BITMAP* ILAPIENTRY ilutAllegLoadImage(Lstring > FileName); > + ILAPI BITMAP* ILAPIENTRY ilutAllegLoadImage(ILstring > FileName); > ILAPI BITMAP* ILAPIENTRY ilutConvertToAlleg(PALETTE Pal); > #endif//ILUT_USE_ALLEGRO > > ==================================================== > > After editing it compiles well (maybe it hasn't been > noticed before, > because allegro was not installed and this chunk's use > depends on > allegro availability? Just a guess). > > -- > GNU/Linux * Slackware 'current' > LU #210970 LM #98222 SU #12583 > "A celebrity is a person who is known for his > well-knownness." From pc_warner at yahoo.com Mon Jul 7 04:11:58 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Sun, 6 Jul 2008 21:11:58 -0700 (PDT) Subject: [Slackbuilds-users] Fwd: bug on openbox package In-Reply-To: <8682df160807052007y64b1e87t7feae3527580352a@mail.gmail.com> Message-ID: <827426.38650.qm@web57706.mail.re3.yahoo.com> I should have time to do it in the next day or two (but not right now), and it shouldn't take me long at all. You have the right idea of what needs to be done, but you mixed up the files names a little. Here is basically what needs to be done: *) make a copy of xinitrc.openbox to xinitrc.openbox-session and change the original by removing the '-session' from the last line (make sure the second xinitrc gets installed into /etc/X11/xinit/ as well). You don't need to copy the file in the script; just having two xinitrc's in the slackBuild folder will work. *) mv /usr/share/xsessions/openbox.desktop /usr/share/xsessions/openbox-session.desktop *) sed the file to change 'Name' to Openbox-Session (to differentiate from the other kdm openbox option) *) Create symlinks under /usr/share/apps/kdm/sessions/ for the openbox*.desktop files (openbox-kde.desktop, openbox-gnome.desktop, openbox-session.desktop) under /usr/share/xsessions/ Yes, as it is currently (without the fixes), the Openbox choice in kdm will execute openbox instead of openbox-session. As the Openbox docs say, you want to use the openbox-session if you want to make use of the autostart file and session management features. If I remember correctly one place that information can be found is on http://icculus.org/openbox/index.php/Help:Getting_started. A note should probably be in the slackBuild README about this. I'll check my email tomorrow evening before updating the script. If you already have it taken care of just let me know. --phil --- On Sat, 7/5/08, Chess Griffin wrote: > From: Chess Griffin > Subject: Re: [Slackbuilds-users] Fwd: bug on openbox package > To: pc_warner at yahoo.com, "SlackBuilds.org Users List" > Date: Saturday, July 5, 2008, 8:07 PM > On Sat, Jul 5, 2008 at 5:20 PM, Phillip Warner > wrote: > > Yes, the stock openbox.desktop file from the kdebase > package should execute openbox-session. However, the > problem is more than that. The new kdm doesn't seem to > make use of the .desktop files under /usr/share/xsessions/, > which is where Openbox puts them by default. Thus, in > order for the Slackware 12.1 Openbox slackBuild to work > properly with KDM, the openbox*.desktop files under there > must either be moved or have a corresponding symlink in > /usr/share/apps/kdm/sessions/ (the latter is probably > better in case someone is using something other than kdm). > The default location was fine in the kdm in Slackware 12.0. > > > > Phil, > > Thanks for your very helpful explanation. I do see the > issue and > agree with your proposed solutions. I also think we > definitely do not > want to overwrite any stock Slackware files and at the same > time > preserve the ability to use the SlackBuild for those that > do not use > KDE or KDM. I also like your suggestion to have both the > xinitrc.openbox-session and xinitrc.openbox setup as > originally > intended by the Openbox developers. If I understand your > solution > correctly, we would need to (1) create a new > xinitrc-session.desktop > file and install it into the default Openbox location along > with the > other Openbox *desktop files (2) symlink all the Openbox > *desktop > files including the new xinitrc-session.desktop file to the > KDM > location and (3) create a new xinitrc.openbox-session file > along with > the current xinitrc.openbox that already comes with the > SlackBuild? > Since we already include a xinitrc.openbox file in the > SlackBuild, I > assume then the stock openbox.desktop file works ok for > someone who > does not want to launch an Openbox session but just > straight Openbox? > In any event, yes, if you have the time to send your > modifications to > the SlackBuild and related files that would be great. > Otherwise, I'll > try and work on this during the coming week. > > In the meantime, I'll install KDE and KDM on one of my > Slack machines > so I can test and get a better feel for what KDM is doing > behind the > scenes. I've never been a graphical login kind of > person, which is > why it's taken me longer than normal to get the issue > here. It has > nothing to do with the fact that I'm about to turn 40 > or the loss of > brain cells from one too many pints of Guinness in my > youth. At > least, that's my story and I'm sticking to it. > > Thanks again for your help, Phil, and to Bruno for the > original bug report. > > -- > Chess Griffin > GPG Public Key: 0x0C7558C3 > http://www.chessgriffin.com From josiahb at gmail.com Mon Jul 7 06:44:46 2008 From: josiahb at gmail.com (Josiah Boothby) Date: Sun, 6 Jul 2008 23:44:46 -0700 Subject: [Slackbuilds-users] lyx_qt4 depends on libaudio? In-Reply-To: <48715835.2030102@slackbuilds.org> References: <6eb14ed10807061351q23c8a927o5b94cb3b5ba1cdf@mail.gmail.com> <48715835.2030102@slackbuilds.org> Message-ID: <6eb14ed10807062344ye5e409fg1ed4aa43148cbd7d@mail.gmail.com> Chalk this up to bonehead user syndrome. I had an old install lurking around in $HOME/local, presumably compiled with NAS somewhere on the system. Thanks anyway, Josiah On Sun, Jul 6, 2008 at 4:41 PM, Robby Workman wrote: > Josiah Boothby wrote: >> >> Hello, >> >> Using SBo's qt4 and lyx_qt4 on Slackware 12.1, I get the following >> error when trying to run lyx: >> >> lyx: error while loading shared libraries: libaudio.so.2: cannot open >> shared object file: No such file or directory >> >> Looking around on the internet has indicated that libaudio.so.2 would >> be provided by NAS (which is not distributed by Slackware, and doesn't >> appear to be on SBo). This does not appear to be a problem with the >> other qt4 programs I've tried to run (e.g., qtconfig). >> >> Is there something I'm missing? > > > Yep - libaudio.so.2 ;-) > > On a more serious note, it looks like you either: > a) used to have libaudio installed, and compiled something [1] that > links it. > [1] that something is apparently being linked by either qt or > lyx (almost surely lyx), and then that something in turn > is trying to find everything it links to. > b) have a package installed from somewhere that wants libaudio, and > lyx is linking to something in that package, which in turn wants > libaudio. > > As you can see, it's essentially the same thing in either a or b. > > -RW > _______________________________________________ > 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 lukenshiro at ngi.it Mon Jul 7 09:33:36 2008 From: lukenshiro at ngi.it (LukenShiro) Date: Mon, 7 Jul 2008 11:33:36 +0200 Subject: [Slackbuilds-users] DevIL In-Reply-To: <570603.88299.qm@web57713.mail.re3.yahoo.com> References: <570603.88299.qm@web57713.mail.re3.yahoo.com> Message-ID: <200807071133.37743.lukenshiro@ngi.it> luned? 7 luglio 2008, Phillip Warner ha scritto: > You are actually the first person other than David who has requested > a fix for this. I actually stopped using DevIL in favor of some > other image libraries, but I still have all the files from the new > slackBuild I made. Since upstream support seems to be waning perhaps > it is time I post what I made. I don't really use it too. I was compiling it for the first time as a dependence for CEGUI, in order to run a game (secret maryo chronicles), _before_ finding your "smc" binary .tgz package (and reading its building documentation). But since it is not a "required" library (rather it is somehow deprecated), it doesn't serve as other slackbuilds packages' dependence, and it shows so many problematic facets ... i do not have a real need for DevIL. -- GNU/Linux * Slackware 'current' LU #210970 LM #98222 SU #12583 "A celebrity is a person who is known for his well-knownness." From pc_warner at yahoo.com Tue Jul 8 05:47:34 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Mon, 7 Jul 2008 22:47:34 -0700 (PDT) Subject: [Slackbuilds-users] Fwd: bug on openbox package In-Reply-To: <827426.38650.qm@web57706.mail.re3.yahoo.com> Message-ID: <928499.64045.qm@web57714.mail.re3.yahoo.com> Attached is the diff for the slackBuild. xinitrc.openbox-session (not shown in the diff) is the same as the old xinitrc.openbox file. I tested the new script and everything seems to work great. You can easily see the difference between running openbox and openbox-session on a default profile because with the later the autostart file causes the background to change (the other will just leave the root image the same as in the KDM screen). It also might be a good idea to add better config file support in the doinst.sh file for the files under /etc/xdg/openbox. That way upgrading openbox won't necessarily overwrite your default menu and autostart.sh file. They will create .new files instead. There are plenty of examples of this in other slackBuild scripts. --phil --- On Sun, 7/6/08, Phillip Warner wrote: > From: Phillip Warner > Subject: Re: [Slackbuilds-users] Fwd: bug on openbox package > To: "Chess Griffin" , "SlackBuilds.org Users List" > Date: Sunday, July 6, 2008, 9:11 PM > I should have time to do it in the next day or two (but not > right now), and it shouldn't take me long at all. You > have the right idea of what needs to be done, but you mixed > up the files names a little. Here is basically what needs > to be done: > > *) make a copy of xinitrc.openbox to > xinitrc.openbox-session and change the original by removing > the '-session' from the last line (make sure the > second xinitrc gets installed into /etc/X11/xinit/ as > well). You don't need to copy the file in the script; > just having two xinitrc's in the slackBuild folder will > work. > *) mv /usr/share/xsessions/openbox.desktop > /usr/share/xsessions/openbox-session.desktop > *) sed the file to change 'Name' to Openbox-Session > (to differentiate from the other kdm openbox option) > *) Create symlinks under /usr/share/apps/kdm/sessions/ for > the openbox*.desktop files (openbox-kde.desktop, > openbox-gnome.desktop, openbox-session.desktop) under > /usr/share/xsessions/ > > Yes, as it is currently (without the fixes), the Openbox > choice in kdm will execute openbox instead of > openbox-session. As the Openbox docs say, you want to use > the openbox-session if you want to make use of the > autostart file and session management features. If I > remember correctly one place that information can be found > is on > http://icculus.org/openbox/index.php/Help:Getting_started. > A note should probably be in the slackBuild README about > this. > > I'll check my email tomorrow evening before updating > the script. If you already have it taken care of just let > me know. > > --phil > > --- On Sat, 7/5/08, Chess Griffin > wrote: > > > From: Chess Griffin > > Subject: Re: [Slackbuilds-users] Fwd: bug on openbox > package > > To: pc_warner at yahoo.com, "SlackBuilds.org Users > List" > > Date: Saturday, July 5, 2008, 8:07 PM > > On Sat, Jul 5, 2008 at 5:20 PM, Phillip Warner > > wrote: > > > Yes, the stock openbox.desktop file from the > kdebase > > package should execute openbox-session. However, the > > problem is more than that. The new kdm doesn't > seem to > > make use of the .desktop files under > /usr/share/xsessions/, > > which is where Openbox puts them by default. Thus, in > > order for the Slackware 12.1 Openbox slackBuild to > work > > properly with KDM, the openbox*.desktop files under > there > > must either be moved or have a corresponding symlink > in > > /usr/share/apps/kdm/sessions/ (the latter is probably > > better in case someone is using something other than > kdm). > > The default location was fine in the kdm in Slackware > 12.0. > > > > > > > Phil, > > > > Thanks for your very helpful explanation. I do see > the > > issue and > > agree with your proposed solutions. I also think we > > definitely do not > > want to overwrite any stock Slackware files and at the > same > > time > > preserve the ability to use the SlackBuild for those > that > > do not use > > KDE or KDM. I also like your suggestion to have both > the > > xinitrc.openbox-session and xinitrc.openbox setup as > > originally > > intended by the Openbox developers. If I understand > your > > solution > > correctly, we would need to (1) create a new > > xinitrc-session.desktop > > file and install it into the default Openbox location > along > > with the > > other Openbox *desktop files (2) symlink all the > Openbox > > *desktop > > files including the new xinitrc-session.desktop file > to the > > KDM > > location and (3) create a new xinitrc.openbox-session > file > > along with > > the current xinitrc.openbox that already comes with > the > > SlackBuild? > > Since we already include a xinitrc.openbox file in the > > SlackBuild, I > > assume then the stock openbox.desktop file works ok > for > > someone who > > does not want to launch an Openbox session but just > > straight Openbox? > > In any event, yes, if you have the time to send your > > modifications to > > the SlackBuild and related files that would be great. > > Otherwise, I'll > > try and work on this during the coming week. > > > > In the meantime, I'll install KDE and KDM on one > of my > > Slack machines > > so I can test and get a better feel for what KDM is > doing > > behind the > > scenes. I've never been a graphical login kind of > > person, which is > > why it's taken me longer than normal to get the > issue > > here. It has > > nothing to do with the fact that I'm about to turn > 40 > > or the loss of > > brain cells from one too many pints of Guinness in my > > youth. At > > least, that's my story and I'm sticking to it. > > > > Thanks again for your help, Phil, and to Bruno for the > > original bug report. > > > > -- > > Chess Griffin > > GPG Public Key: 0x0C7558C3 > > http://www.chessgriffin.com > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - > http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ -------------- next part -------------- A non-text attachment was scrubbed... Name: openbox-slackBuild-2.diff Type: application/octet-stream Size: 3861 bytes Desc: not available URL: From xgizzmo at slackbuilds.org Tue Jul 8 23:42:33 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Tue, 8 Jul 2008 19:42:33 -0400 Subject: [Slackbuilds-users] Updates - 20080708 Message-ID: <200807081942.33404.xgizzmo@slackbuilds.org> Tue Jul 8 23:05:53 UTC 2008 audio/moc: Updated for version 2.4.3. Thanks to Michael Wagner. --David Somero desktop/crystal: Updated for version 1.0.6. Thanks to Michiel van Wessem. --David Somero desktop/lxpanel: Updated for version 0.3.7. Thanks to Michael Wagner. --David Somero desktop/QtCurve-Gtk2: Updated for version 0.59.4. Thanks to Michiel van Wessem. --David Somero desktop/QtCurve-KDE3: Updated for version 0.59.3. Thanks to Michiel van Wessem. --David Somero development/egenix-mx-base: Updated for version 3.1.0. Thanks to Heinz Wiesinger. --David Somero development/ipython: Added - ipython is an enhanced Python shell, library, and distributed/parallel computing system. Thanks to Carlos Corbacho. --rworkman development/kdesvn: Updated for version 0.14.4. Thanks to Michiel van Wessem. --David Somero development/libx86: Added - libx86 is a hardware-independent library for executing real-mode x86 code. Thanks to Murat D. Kadirov. --David Somero development/stgit: Updated for version 0.14.3. Thanks to Carlos Corbacho. --rworkman graphics/djvulibre: Added - djvulibre includes a standalone viewer, a browser plug-in and command line tools for DjVu files. Thanks to Murat D. Kadirov. --David Somero libraries/libfwbuilder: Updated for version 2.1.19. Thanks to David Somero. --rworkman libraries/raptor: Updated for version 1.4.18. Thanks to Heinz Wiesinger. --David Somero libraries/SDL_gfx: Updated for version 2.0.17. Thanks to Michiel van Wessem. --David Somero network/bitlbee: Updated for version 1.2.1. Thanks to Michiel van Wessem. --David Somero network/claws-mail: Updated for version 3.5.0. Thanks to Erik Hanson. --Michiel network/claws-mail-extra-plugins: Updated for version 3.5.0. Thanks to Erik Hanson. --Michiel network/fwbuilder: Updated for version 2.1.19. Thanks to David Somero. --rworkman network/haproxy: Updated for version 1.3.15.2. Thanks to Cherife Li. --David Somero network/Limewire: Updated for version 4.18.3. Thanks to Rob Workman. --Michiel network/skype: Updated for version 2.0.0.72. Thanks to Mauro Giachero. --rworkman network/squid: Updated for version 3.0.STABLE7. Thanks to David Somero. network/wifi-radar: Updated for version 1.9.9. Thanks to David Somero. --rworkman multimedia/Songbird: Updated for version 0.6.1. Thanks to Michiel van Wessem. --David Somero office/basket: Updated for version 1.0.3. Thanks to Michiel van Wessem. --David Somero office/kile: Updated for version 2.0.1. Thanks to Michiel van Wessem. --David Somero From gmartin at gmartin.org Wed Jul 9 14:43:40 2008 From: gmartin at gmartin.org (Greg Martin) Date: Wed, 09 Jul 2008 10:43:40 -0400 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x Message-ID: <4874CE9C.9090601@gmartin.org> I have been using a slackbuild script to compile nagios 2.x for a couple years. The script was written by Stefano Stabellini. Now that 3.x is available, I thought it would be a good idea to review the script and update it for 3.x. As I've only hacked through a couple of these, I seek some wise counsel before I change too much. My big question is around the directory layout. Nagios has several moving parts and I want to ensure the install locations are normalized for Slackware. Here are the pieces and the directory from the current script main nagios exe - /usr/bin cgi exes - /usr/libexec/nagios web interface root - /usr/share/nagios run file - /var/lib/nagios config dir - /etc/nagios Additionally, there is a separate package of nagios plugins plugins - /usr/libexec/nagios Looking over the guidance for writing scripts at slackwiki.org, I was considering the following layout and would like any comments you might have. main nagios exe - /usr/bin cgi exes - /usr/local/nagios/cgi web interface root - /usr/local/nagios run file - /var/nagios config dir - /etc/nagios plugins - /usr/local/nagios/plugins \\Greg From abrouwers at gmail.com Wed Jul 9 15:07:20 2008 From: abrouwers at gmail.com (Andrew Brouwers) Date: Wed, 9 Jul 2008 11:07:20 -0400 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <4874CE9C.9090601@gmartin.org> References: <4874CE9C.9090601@gmartin.org> Message-ID: <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> Hi Greg, I've never used nagios, but as a general rule, /usr/local is reserved for per-system stuff. As you'll probably notice, nothing really gets put there by default. Do you have a good reason for those components to move from /usr/share? It is usually a better place for such components. To see which packages on your installed system have used /usr/local up until now, try: grep usr/local /var/log/packages/* | grep -v aaa_base That should give you a good idea as to how many slack packages consider /usr/local to be the correct spot :> Also, I think /var/lib is the better place for application-specific processes. Check out /var and /var/lib on a slackware box, and you can see the differences. Just my opinions; good luck! Andrew On Wed, Jul 9, 2008 at 10:43 AM, Greg Martin wrote: > I have been using a slackbuild script to compile nagios 2.x for a couple > years. The script was written by Stefano Stabellini. Now that 3.x is > available, I thought it would be a good idea to review the script and update > it for 3.x. As I've only hacked through a couple of these, I seek some wise > counsel before I change too much. > > My big question is around the directory layout. Nagios has several moving > parts and I want to ensure the install locations are normalized for > Slackware. > > Here are the pieces and the directory from the current script > main nagios exe - /usr/bin > cgi exes - /usr/libexec/nagios > web interface root - /usr/share/nagios > run file - /var/lib/nagios > config dir - /etc/nagios > > Additionally, there is a separate package of nagios plugins > plugins - /usr/libexec/nagios > > Looking over the guidance for writing scripts at slackwiki.org, I was > considering the following layout and would like any comments you might have. > > main nagios exe - /usr/bin > cgi exes - /usr/local/nagios/cgi > web interface root - /usr/local/nagios > run file - /var/nagios > config dir - /etc/nagios > plugins - /usr/local/nagios/plugins > > \\Greg > _______________________________________________ > 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 cherife at dotimes.com Wed Jul 9 15:20:27 2008 From: cherife at dotimes.com (Cherife Li) Date: Wed, 09 Jul 2008 23:20:27 +0800 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <4874CE9C.9090601@gmartin.org> References: <4874CE9C.9090601@gmartin.org> Message-ID: <4874D73B.9070703@dotimes.com> On 07/09/08 22:43, Greg Martin wrote: > I have been using a slackbuild script to compile nagios 2.x for a couple > years. The script was written by Stefano Stabellini. Now that 3.x is > available, I thought it would be a good idea to review the script and > update it for 3.x. As I've only hacked through a couple of these, I > seek some wise counsel before I change too much. Good news. I intended to maintain this. But for some reason gave up. And there is an nagios-plugins package. > > My big question is around the directory layout. Yeah, +1. > > Looking over the guidance for writing scripts at slackwiki.org, I was > considering the following layout and would like any comments you might > have. > > cgi exes - /usr/local/nagios/cgi > web interface root - /usr/local/nagios IMHO, we'd better change these. Further more, how about placing cgi and web root in a same web root dir? > run file - /var/nagios > config dir - /etc/nagios > plugins - /usr/local/nagios/plugins Yeah, there are many many kinds of plugins. So, how about put them all into /var/lib/nagiosplugins? Just to mentaion, with lockfile => /var/run/nagios.pid My 2 cents. > > \\Greg -- Rgds, Cherife. From gmartin at gmartin.org Wed Jul 9 17:31:41 2008 From: gmartin at gmartin.org (Greg Martin) Date: Wed, 09 Jul 2008 13:31:41 -0400 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> References: <4874CE9C.9090601@gmartin.org> <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> Message-ID: <4874F5FD.9030205@gmartin.org> Andrew Brouwers wrote: > Hi Greg, > > I've never used nagios, but as a general rule, /usr/local is reserved > for per-system stuff. As you'll probably notice, nothing really gets > put there by default. Do you have a good reason for those components > to move from /usr/share? It is usually a better place for such > components. To see which packages on your installed system have used > /usr/local up until now, try: > > grep usr/local /var/log/packages/* | grep -v aaa_base > > That should give you a good idea as to how many slack packages > consider /usr/local to be the correct spot :> > > Also, I think /var/lib is the better place for application-specific > processes. Check out /var and /var/lib on a slackware box, and you > can see the differences. > > Just my opinions; good luck! > > Andrew > OK, good tips from you & Cherife. My ignorance is coming hrough nicely! So, here's a revision main nagios exe - /usr/bin cgi exes - /usr/share/nagios/cgi web interface root - /usr/share/nagios run file - /var/run/nagios.lock config dir - /etc/nagios plugins - /usr/share/nagios/plugins Another question I have. The --prefix in Stefano's script points to /usr/lib/nagios. What would be appropriate for that? /usr/share/nagios? \\Greg > On Wed, Jul 9, 2008 at 10:43 AM, Greg Martin wrote: > >> I have been using a slackbuild script to compile nagios 2.x for a couple >> years. The script was written by Stefano Stabellini. Now that 3.x is >> available, I thought it would be a good idea to review the script and update >> it for 3.x. As I've only hacked through a couple of these, I seek some wise >> counsel before I change too much. >> > From cherife at dotimes.com Wed Jul 9 17:55:16 2008 From: cherife at dotimes.com (Cherife Li) Date: Thu, 10 Jul 2008 01:55:16 +0800 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <4874F5FD.9030205@gmartin.org> References: <4874CE9C.9090601@gmartin.org> <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> <4874F5FD.9030205@gmartin.org> Message-ID: <4874FB84.1010009@dotimes.com> On 07/10/08 01:31, Greg Martin wrote: > Another question I have. The --prefix in Stefano's script points to > /usr/lib/nagios. What would be appropriate for that? /usr/share/nagios? You may have a look at their Makefile. The install target mess up things. This is the upstream issue. I think the nagios dev team only suppose you to prefix with /usr/local/nagios. -- Rgds, Cherife. From gmartin at gmartin.org Wed Jul 9 18:24:33 2008 From: gmartin at gmartin.org (Greg Martin) Date: Wed, 09 Jul 2008 14:24:33 -0400 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <4874FB84.1010009@dotimes.com> References: <4874CE9C.9090601@gmartin.org> <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> <4874F5FD.9030205@gmartin.org> <4874FB84.1010009@dotimes.com> Message-ID: <48750261.8080300@gmartin.org> Here's the pertinent info from 'configure --help' Installation directories: --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local/nagios] --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX [PREFIX] By default, `make install' will install all the files in `/usr/local/nagios/bin', `/usr/local/nagios/lib' etc. You can specify an installation prefix other than `/usr/local/nagios' using `--prefix', for instance `--prefix=$HOME'. For better control, use the options below. Fine tuning of the installation directories: --bindir=DIR user executables [EPREFIX/bin] --sbindir=DIR system admin executables [EPREFIX/sbin] --libexecdir=DIR program executables [EPREFIX/libexec] --datadir=DIR read-only architecture-independent data [PREFIX/share] --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIR C header files for non-gcc [/usr/include] --infodir=DIR info documentation [PREFIX/info] --mandir=DIR man documentation [PREFIX/man] Cherife Li wrote: > On 07/10/08 01:31, Greg Martin wrote: >> Another question I have. The --prefix in Stefano's script points to >> /usr/lib/nagios. What would be appropriate for that? >> /usr/share/nagios? > You may have a look at their Makefile. The install target mess up things. > This is the upstream issue. I think the nagios dev team only suppose > you to prefix with /usr/local/nagios. From rshepard at appl-ecosys.com Wed Jul 9 18:30:36 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 9 Jul 2008 11:30:36 -0700 (PDT) Subject: [Slackbuilds-users] libgphoto2 Build Error Message-ID: On my Slackware-11.0 system trying to build libgphoto2-2.4.1 using the downloaded script: libgphoto2-2.4.1/doc/api/gphoto2-sections.txt patching file packaging/generic/print-camera-list.c Hunk #1 succeeded at 235 (offset -98 lines). Hunk #2 FAILED at 348. 1 out of 2 hunks FAILED -- saving rejects to file packaging/generic/print-camera-list.c.rej Suggestions to fix hunk #2 greatly appreciated. Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From rshepard at appl-ecosys.com Wed Jul 9 21:34:07 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 9 Jul 2008 14:34:07 -0700 (PDT) Subject: [Slackbuilds-users] libgphoto2 Build Error -- UPDATE In-Reply-To: References: Message-ID: On Wed, 9 Jul 2008, Rich Shepard wrote: > On my Slackware-11.0 system trying to build libgphoto2-2.4.1 using the > downloaded script: FWIW, I was able to go the ./configure; make; make install route for the library, then use the SlackBuild script for gphoto2. It doesn't recognize my supported camera, but I was able to download the images from it. Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From gmartin at gmartin.org Thu Jul 10 19:50:15 2008 From: gmartin at gmartin.org (Greg Martin) Date: Thu, 10 Jul 2008 15:50:15 -0400 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <4874F5FD.9030205@gmartin.org> References: <4874CE9C.9090601@gmartin.org> <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> <4874F5FD.9030205@gmartin.org> Message-ID: <487667F7.8050100@gmartin.org> I think I have a lot of this worked out. I built a separate script for the nagios plugins that installs the plugins below /usr/share/nagios in a. /plugins directory. Is this a no-no? That is to have one package install below another? Seems like a good idea on one-hand to keep everything together. On the other hand, I can hear someone say "the two should be independent" and I can understand that as well. Guidance, anyone? Next issue - there is an external command directory that typically gets setup as /var/lib/nagios/rw. It needs special permissions and is something that always trips me up. Would be appropriate to add the creation and configuration of this directory into the doinst.sh? And along those lines, I've specified both packages to use the nagios.nagios user/group pair. Should I create the user & group? or is that a no-no? \\Greg Greg Martin wrote: > > > Andrew Brouwers wrote: >> Hi Greg, >> >> I've never used nagios, but as a general rule, /usr/local is reserved >> for per-system stuff. As you'll probably notice, nothing really gets >> put there by default. Do you have a good reason for those components >> to move from /usr/share? It is usually a better place for such >> components. To see which packages on your installed system have used >> /usr/local up until now, try: >> >> grep usr/local /var/log/packages/* | grep -v aaa_base >> >> That should give you a good idea as to how many slack packages >> consider /usr/local to be the correct spot :> >> >> Also, I think /var/lib is the better place for application-specific >> processes. Check out /var and /var/lib on a slackware box, and you >> can see the differences. >> >> Just my opinions; good luck! >> >> Andrew >> > > OK, good tips from you & Cherife. My ignorance is coming hrough nicely! > > So, here's a revision > > main nagios exe - /usr/bin > cgi exes - /usr/share/nagios/cgi > web interface root - /usr/share/nagios > run file - /var/run/nagios.lock > config dir - /etc/nagios > plugins - /usr/share/nagios/plugins > > > Another question I have. The --prefix in Stefano's script points to > /usr/lib/nagios. What would be appropriate for that? /usr/share/nagios? > > \\Greg > > >> On Wed, Jul 9, 2008 at 10:43 AM, Greg Martin >> wrote: >> >>> I have been using a slackbuild script to compile nagios 2.x for a >>> couple >>> years. The script was written by Stefano Stabellini. Now that 3.x is >>> available, I thought it would be a good idea to review the script >>> and update >>> it for 3.x. As I've only hacked through a couple of these, I seek >>> some wise >>> counsel before I change too much. >>> >> > _______________________________________________ > 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 chess at chessgriffin.com Thu Jul 10 21:51:48 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 10 Jul 2008 17:51:48 -0400 Subject: [Slackbuilds-users] Fwd: bug on openbox package In-Reply-To: <928499.64045.qm@web57714.mail.re3.yahoo.com> References: <928499.64045.qm@web57714.mail.re3.yahoo.com> Message-ID: <48768474.1000507@chessgriffin.com> Phillip Warner wrote: > Attached is the diff for the slackBuild. xinitrc.openbox-session > (not shown in the diff) is the same as the old xinitrc.openbox file. > > I tested the new script and everything seems to work great. You can > easily see the difference between running openbox and openbox-session > on a default profile because with the later the autostart file causes > the background to change (the other will just leave the root image > the same as in the KDM screen). > > It also might be a good idea to add better config file support in the > doinst.sh file for the files under /etc/xdg/openbox. That way > upgrading openbox won't necessarily overwrite your default menu and > autostart.sh file. They will create .new files instead. There are > plenty of examples of this in other slackBuild scripts. > > --phil > Phil, Thank you very much for doing this. I'm sorry I have not had time to test this yet and it might be another several days before I do. Things have gotten crazy for me again... the people who were supposed to buy my house bailed out and now I have to get out of an apartment lease and move my wife and kids back into the house. It's a pretty sucky situation. :/ In the meantime, if any of the admins want to test and approve I'm ok with that too. I don't want to be the one holding up a good update. Sorry for the delays on my part. Chess -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From cherife at dotimes.com Fri Jul 11 03:35:19 2008 From: cherife at dotimes.com (Cherife Li) Date: Fri, 11 Jul 2008 11:35:19 +0800 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <487667F7.8050100@gmartin.org> References: <4874CE9C.9090601@gmartin.org> <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> <4874F5FD.9030205@gmartin.org> <487667F7.8050100@gmartin.org> Message-ID: On Fri, Jul 11, 2008 at 3:50 AM, Greg Martin wrote: > I think I have a lot of this worked out. I built a separate script for the > nagios plugins that installs the plugins below /usr/share/nagios in a. > /plugins directory. Is this a no-no? That is to have one package install > below another? Never mind. You may 'mkdir -p $PKG/usr/share/nagios/plugins' within nagios-plugins.SlackBuild. > Seems like a good idea on one-hand to keep everything together. Yeah, +1. > On the other hand, I can hear someone say "the two should be independent" > and I can understand that as well. Guidance, anyone? Independent means what? IMO, nagios-plugins need nagios package. > Next issue - there is an external command directory that typically gets > setup as /var/lib/nagios/rw. It needs special permissions and is something > that always trips me up. Would be appropriate to add the creation and > configuration of this directory into the doinst.sh? Just do it within SlackBuild files. > And along those lines, I've specified both packages to use the > nagios.nagios user/group pair. Should I create the user & group? or is that > a no-no? Yeah, we need this. > > \\Greg My 2 cents. THX. -- Rgds, Cherife. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at markwalling.org Sat Jul 12 14:26:46 2008 From: mark at markwalling.org (Mark Walling) Date: Sat, 12 Jul 2008 10:26:46 -0400 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <487667F7.8050100@gmartin.org> References: <4874CE9C.9090601@gmartin.org> <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> <4874F5FD.9030205@gmartin.org> <487667F7.8050100@gmartin.org> Message-ID: <4878BF26.3010508@markwalling.org> Greg Martin wrote: > And along those lines, I've specified both packages to use the > nagios.nagios user/group pair. Should I create the user & group? or is > that a no-no? > I would suggest looking at the dovecot.SlackBuild and postfix.SlackBuilds for how to handle the group creation. -M -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Tue Jul 15 04:43:50 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Jul 2008 23:43:50 -0500 Subject: [Slackbuilds-users] Leafnode 2 script In-Reply-To: <20080706010917.GA21417@ilium.andrews-corner.org> References: <20080706010917.GA21417@ilium.andrews-corner.org> Message-ID: <487C2B06.4010705@slackbuilds.org> andrew wrote: > Hi, > > There has been a small upgrade to the Leafnode 2 source code. Should I > resubmit the full package myself or can the download link and script > be modified at slackbuilds.org to: > > http://home.pages.de/~mandree/leafnode/beta/leafnode-2.0.0.alpha20080624a.tar.bz2 > > PRGNAM=leafnode > VERSION=2.0.0.alpha20080624a > > The leafnode changes are quite small but I guess the improvements in > logging make it a worthwhile upgrade. Hi Andrew, Sorry for the delay, and it seems you already decided to do it anyway, but yeah, the best thing to do is submit the update via normal submission method. Thanks, -RW From rworkman at slackbuilds.org Tue Jul 15 04:45:21 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Jul 2008 23:45:21 -0500 Subject: [Slackbuilds-users] libgphoto2 Build Error In-Reply-To: References: Message-ID: <487C2B61.2040809@slackbuilds.org> Rich Shepard wrote: > On my Slackware-11.0 system trying to build libgphoto2-2.4.1 using the > downloaded script: > > libgphoto2-2.4.1/doc/api/gphoto2-sections.txt > patching file packaging/generic/print-camera-list.c > Hunk #1 succeeded at 235 (offset -98 lines). > Hunk #2 FAILED at 348. > 1 out of 2 hunks FAILED -- saving rejects to file > packaging/generic/print-camera-list.c.rej > > Suggestions to fix hunk #2 greatly appreciated. > > Rich > Rich, we don't apply any patches to the 2.4.1 build in our 12.1 repository, and and 2.4.1 is not in our 11.0 repository. -RW From chess at chessgriffin.com Tue Jul 15 13:48:23 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 15 Jul 2008 09:48:23 -0400 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed Message-ID: <487CAAA7.9050802@chessgriffin.com> I have added a new feature to sbopkg based on many requests -- the ability to display potential updates to installed SBo packages on the user's system -- and I would like to solicit testers. This is actually a somewhat difficult feature to implement, given the fact that there are slight variations on upstream version numbering, package names, etc. which have to be addressed in the SlackBuilds. In short, sbopkg attempts to match the $PRGNAM-$VERSION-$ARCH-$BUILD$TAG of each installed SBo package with the $PRGNAM-$VERSION-$ARCH-$BUILD$TAG of the corresponding SlackBuild. If they do not match, then there is an update. However, due to the slight upstream variations mentioned previously, parsing SlackBuilds and matching up the package name, version number, arch, and build number is not always accurate. In any event, there is a rc1 of sbopkg version 0.0.8 available for download for anyone that is interested in testing. I have already found one issue that has been fixed in svn and will be included in the next release candidate, but I could really use some more testers. If you do test, please let me know of any successes or problems by posting here, emailing me off list, or better yet, subscribing and posting to the sbopkg mailing list. The problems will likely manifest themselves in the update list -- either incorrectly marking something as a potential update, or missing an update that should be listed, or displaying packages with extraneous characters in the package name or version number (i.e. such as double quotes or something) which then results in a false positive. Anyway, enough rambling. The source tarball and package for 0.0.8rc1 are available here: http://code.google.com/p/sbopkg/downloads/list Thanks for your help. -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed Jul 16 00:00:50 2008 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 15 Jul 2008 17:00:50 -0700 (PDT) Subject: [Slackbuilds-users] libgphoto2 Build Error In-Reply-To: <487C2B61.2040809@slackbuilds.org> References: <487C2B61.2040809@slackbuilds.org> Message-ID: On Mon, 14 Jul 2008, Robby Workman wrote: > Rich, we don't apply any patches to the 2.4.1 build in our 12.1 > repository, and and 2.4.1 is not in our 11.0 repository. Thank you, Robby. I guess it will have to wait until I make the time -- probably this coming weekend -- to upgrade the distribution. The only reason I've held off this long is the major changes to Xfce that need manual intervention. Sigh. Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation Voice: 503-667-4517 Fax: 503-667-8863 From chess at chessgriffin.com Wed Jul 16 01:24:21 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 15 Jul 2008 21:24:21 -0400 Subject: [Slackbuilds-users] Fwd: bug on openbox package In-Reply-To: <928499.64045.qm@web57714.mail.re3.yahoo.com> References: <827426.38650.qm@web57706.mail.re3.yahoo.com> <928499.64045.qm@web57714.mail.re3.yahoo.com> Message-ID: <8682df160807151824x131c1ec3k8cd5f51eaea1df4f@mail.gmail.com> On Tue, Jul 8, 2008 at 1:47 AM, Phillip Warner wrote: > Attached is the diff for the slackBuild. xinitrc.openbox-session (not shown in the diff) is the same as the old xinitrc.openbox file. > > I tested the new script and everything seems to work great. You can easily see the difference between running openbox and openbox-session on a default profile because with the later the autostart file causes the background to change (the other will just leave the root image the same as in the KDM screen). > > It also might be a good idea to add better config file support in the doinst.sh file for the files under /etc/xdg/openbox. That way upgrading openbox won't necessarily overwrite your default menu and autostart.sh file. They will create .new files instead. There are plenty of examples of this in other slackBuild scripts. > Okay, I've installed a minimal KDE and KDM and tested this out and it seems to be working great. I've logged in to both openbox and openbox-session from the KDM sessions menu, and when using openbox-session the autostart.sh file is executed correctly. The links in /usr/share/apps/kdm/sessions are there and overall it's looks great. Thanks again for doing the heavy lifting, Phil. I'll package this up and submit it to SBo. Again, sorry for the delays. -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com From xgizzmo at slackbuilds.org Thu Jul 17 03:34:16 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Wed, 16 Jul 2008 23:34:16 -0400 Subject: [Slackbuilds-users] Updates - 20080717 Message-ID: <200807162334.57615.xgizzmo@slackbuilds.org> Thu Jul 17 02:07:30 UTC 2008 audio/last.fm: Small change to the last.fm script, to allow passing command-line arguments to the main executable. --Erik Hanson audio/mt-daapd: Updated for version 0.2.4.2. Thanks to Andrew Brouwers. --rworkman desktop/awesome: Updated for version 2.3.2. Thanks to Chess Griffin. --Erik Hanson development/bzr: Added - Bazaar (bzr) is a decentralized revision control system, designed to be easy for developers and end users alike. Thanks to Robby Workman. --Michiel development/scons: Updated for version 0.98.5. Thanks to Kyle Guinn. --Michiel games/freeciv: Updated for version 2.1.5. Thanks to Iskar Enev. --Erik Hanson games/openttd: Updated for version 0.6.1. Thanks to Chess Griffin. --Erik Hanson games/wesnoth: Updated for version 1.4.3. Thanks to Michiel van Wessem. --Erik Hanson graphics/dia: Updated for version 0.96.1. Thanks to Matt Hayes. --Michiel libraries/gst-ffmpeg: Added - gst-ffmpeg is a FFmpeg plugin for GStreamer. Thanks to Juan Valencia Escalante. --Michiel libraries/gst-python: Added - gst-pythons are python bindings for gstreamer. Thanks to Thiago Coutinho. --Michiel libraries/libarchive: Updated for version 2.5.5. Thanks to Heinz Wiesinger. --Erik Hanson libraries/libcap: Updated for version 2.10. Thanks to Menno Duursma. --rworkman libraries/libsamplerate: Updated for version 0.1.4. Thanks to Paul Wisehart. --rworkman libraries/rasqal: Updated for version 0.9.16. Thanks to Heinz Wiesinger. --Erik Hanson libraries/redland: Updated for version 1.0.8. Thanks to Heinz Wiesinger. --Erik Hanson libraries/xmltv_prereq: Updated to reflect a new dependency. Thanks to David Somero. --rworkman libraries/yaz: Updated for version 3.0.34. Thanks to Michiel van Wessem. --Erik Hanson misc/clawsker: Updated for version 0.5.0. Thanks to Erik Hanson. --Michiel multimedia/devede: Updated for version 3.9. Thanks to Roberto Neri. --Erik Hanson multimedia/gst-plugins-base: Updated for version 0.10.20. Thanks to Michiel van Wessem. --Erik Hanson multimedia/gst-plugins-ugly: Updated for version 0.10.8. Thanks to Michiel van Wessem. --Erik Hanson multimedia/mythtv: Updated for version 0.21. multimedia/myththemes: Updated for version 0.21. multimedia/mythplugins: Updated for version 0.21. Thanks to David Somero for the mythtv stuff. --rworkman multimedia/subtitleeditor: Added - subtitleeditor is GTK2 editor for subtitles. Thanks to Juan Valencia Escalante. --Michiel multimedia/xmltv: Updated for version 0.5.51. Thanks to David Somero. --rworkman network/bip: Updated for version 0.7.4. Thanks to Chess Griffin. --Erik Hanson network/hylafax: Updated for version 4.4.4. Thanks to David Somero. --Erik Hanson network/linuxdcpp: Updated for version 1.0.2. Thanks to Nille Kungen. --Erik Hanson network/opera: Updated for version 9.51. Thanks to Robby Workman. --Erik Hanson network/pptp: Updated for version 1.7.2. Thanks to Robby Workman. --Erik Hanson office/tellico: Updated for version 1.3.2.1. Thanks to Michiel van Wessem. --Erik Hanson system/cfengine: Updated for version 2.2.7. Thanks to Menno Duursma. --rworkman system/ktsuss: Added - ktsuss is a simple graphical su helper. Thanks to Murat D. Kadirov. --Michiel system/lirc: Updated for version 0.8.3. Thanks to David Somero. --Erik Hanson system/rxvt-unicode: Updated for version 9.05. Thanks to Thanks to Dugan Chen. --Erik Hanson system/xorg-server-xephyr: Updated for version 1.4.2 (to stay in sync with slackware-12.0/patches/). Thanks to Heinz Wiesinger. --rworkman From neobug at tornado.ktu.lt Thu Jul 17 07:34:08 2008 From: neobug at tornado.ktu.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Thu, 17 Jul 2008 10:34:08 +0300 Subject: [Slackbuilds-users] Updates - 20080717 In-Reply-To: <200807162334.57615.xgizzmo@slackbuilds.org> References: <200807162334.57615.xgizzmo@slackbuilds.org> Message-ID: <20080717073407.GB2126@kiras> On Wed, 2008-07-16 at 23:34:16 -0400, xgizzmo at slackbuilds.org wrote: > Thu Jul 17 02:07:30 UTC 2008 > network/opera: Updated for version 9.51. > Thanks to Robby Workman. --Erik Hanson In http://slackbuilds.org/repository/12.1/network/opera/ page there are files `.tar.gz.asc' and `.tar.gz', which, I think, shouldn't be there (or at least should be properly named). -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From slackbuilds at sisyphus.ch Thu Jul 17 08:09:56 2008 From: slackbuilds at sisyphus.ch (christian) Date: Thu, 17 Jul 2008 10:09:56 +0200 Subject: [Slackbuilds-users] Updates - 20080717 In-Reply-To: <200807162334.57615.xgizzmo@slackbuilds.org> References: <200807162334.57615.xgizzmo@slackbuilds.org> Message-ID: <20080717080955.GY7310@machine-18.sisyphus.loc> On Wed, Jul 16, 2008 at 11:34:16PM -0400, xgizzmo at slackbuilds.org wrote: > Thu Jul 17 02:07:30 UTC 2008 [...] rsync: opendir "12.1/development/scons" (in slackbuilds) failed: Permission denied (13) rsync: opendir "12.1/graphics/dia" (in slackbuilds) failed: Permission denied (13) rsync: opendir "12.1/libraries/gst-python" (in slackbuilds) failed: Permission denied (13) what am i doing wrong? rtfms appreciated. -- From xgizzmo at slackbuilds.org Thu Jul 17 11:47:10 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Thu, 17 Jul 2008 07:47:10 -0400 Subject: [Slackbuilds-users] Updates - 20080717 In-Reply-To: <20080717073407.GB2126@kiras> References: <200807162334.57615.xgizzmo@slackbuilds.org> <20080717073407.GB2126@kiras> Message-ID: <200807170747.10683.xgizzmo@slackbuilds.org> On Thursday 17 July 2008 03:34:08 Audrius Ka?ukauskas wrote: > In http://slackbuilds.org/repository/12.1/network/opera/ page there are > files `.tar.gz.asc' and `.tar.gz', which, I think, shouldn't be there > (or at least should be properly named). Should all be fixed now thanks for the report. David Somero From xgizzmo at slackbuilds.org Thu Jul 17 12:01:51 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Thu, 17 Jul 2008 08:01:51 -0400 Subject: [Slackbuilds-users] Updates - 20080717 In-Reply-To: <20080717080955.GY7310@machine-18.sisyphus.loc> References: <200807162334.57615.xgizzmo@slackbuilds.org> <20080717080955.GY7310@machine-18.sisyphus.loc> Message-ID: <200807170801.51574.xgizzmo@slackbuilds.org> On Thursday 17 July 2008 04:09:56 christian wrote: > what am i doing wrong? Nothing, I screwed up. :) Sorry about that, it should be fixed now. David Somero From HMWiesinger at gmx.at Thu Jul 17 12:44:14 2008 From: HMWiesinger at gmx.at (Heinz Wiesinger) Date: Thu, 17 Jul 2008 14:44:14 +0200 Subject: [Slackbuilds-users] Updates - 20080717 In-Reply-To: <200807162334.57615.xgizzmo@slackbuilds.org> References: <200807162334.57615.xgizzmo@slackbuilds.org> Message-ID: <200807171444.17519.HMWiesinger@gmx.at> Am Donnerstag, 17. Juli 2008 05:34:16 schrieb xgizzmo at slackbuilds.org: > Thu Jul 17 02:07:30 UTC 2008 > [...] > system/xorg-server-xephyr: Updated for version 1.4.2 (to stay in sync with > slackware-12.0/patches/). Thanks to Heinz Wiesinger. --rworkman Somehow the files were not updated. The information and the link on the website was updated for 1.4.2, but the files are still from 1.4.0.90. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From rworkman at slackbuilds.org Thu Jul 17 16:45:26 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 17 Jul 2008 11:45:26 -0500 Subject: [Slackbuilds-users] Updates - 20080717 In-Reply-To: <200807171444.17519.HMWiesinger@gmx.at> References: <200807162334.57615.xgizzmo@slackbuilds.org> <200807171444.17519.HMWiesinger@gmx.at> Message-ID: <487F7726.4040706@slackbuilds.org> Heinz Wiesinger wrote: > Am Donnerstag, 17. Juli 2008 05:34:16 schrieb xgizzmo at slackbuilds.org: >> Thu Jul 17 02:07:30 UTC 2008 >> [...] >> system/xorg-server-xephyr: Updated for version 1.4.2 (to stay in sync with >> slackware-12.0/patches/). Thanks to Heinz Wiesinger. --rworkman > > Somehow the files were not updated. The information and the link on the > website was updated for 1.4.2, but the files are still from 1.4.0.90. Mea culpa. I have no friggin' clue how that happened. Can you resend that tarball to me? Even my local DONE/ directory has the wrong version. Maybe I was drinking or something... :/ -RW From mickeytintincolle at yahoo.fr Thu Jul 17 19:31:59 2008 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Thu, 17 Jul 2008 21:31:59 +0200 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <487CAAA7.9050802@chessgriffin.com> References: <487CAAA7.9050802@chessgriffin.com> Message-ID: <20080717213159.45a35bbd@slack.volderking.com> Le Tue, 15 Jul 2008 09:48:23 -0400, Chess Griffin a ?crit : > I have added a new feature to sbopkg based on many requests -- the > ability to display potential updates to installed SBo packages on the > user's system -- and I would like to solicit testers. This is > actually a somewhat difficult feature to implement, given the fact > that there are slight variations on upstream version numbering, > package names, etc. which have to be addressed in the SlackBuilds. > In short, sbopkg attempts to match the > $PRGNAM-$VERSION-$ARCH-$BUILD$TAG of each installed SBo package with > the $PRGNAM-$VERSION-$ARCH-$BUILD$TAG of the corresponding > SlackBuild. If they do not match, then there is an update. However, > due to the slight upstream variations mentioned previously, parsing > SlackBuilds and matching up the package name, version number, arch, > and build number is not always accurate. > > In any event, there is a rc1 of sbopkg version 0.0.8 available for > download for anyone that is interested in testing. I have already > found one issue that has been fixed in svn and will be included in > the next release candidate, but I could really use some more > testers. If you do test, please let me know of any successes or > problems by posting here, emailing me off list, or better yet, > subscribing and posting to the sbopkg mailing list. The problems > will likely manifest themselves in the update list -- either > incorrectly marking something as a potential update, or missing an > update that should be listed, or displaying packages with extraneous > characters in the package name or version number (i.e. such as double > quotes or something) which then results in a false positive. > > Anyway, enough rambling. The source tarball and package for 0.0.8rc1 > are available here: > > http://code.google.com/p/sbopkg/downloads/list > > Thanks for your help. > First, thanks for sbopkg, it is far better that my 17-lines slackmerge script ;) . I tested SBopkg 0.0.8rc2 and the package doesn't create /home/sbo . It is a bug or a feature ? From mickeytintincolle at yahoo.fr Thu Jul 17 19:43:46 2008 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Thu, 17 Jul 2008 21:43:46 +0200 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <20080717213159.45a35bbd@slack.volderking.com> References: <487CAAA7.9050802@chessgriffin.com> <20080717213159.45a35bbd@slack.volderking.com> Message-ID: <20080717214346.6bba5af5@slack.volderking.com> Le Thu, 17 Jul 2008 21:31:59 +0200, Antoine NONYME a ?crit : > Le Tue, 15 Jul 2008 09:48:23 -0400, > Chess Griffin a ?crit : > > > I have added a new feature to sbopkg based on many requests -- the > > ability to display potential updates to installed SBo packages on > > the user's system -- and I would like to solicit testers. This is > > actually a somewhat difficult feature to implement, given the fact > > that there are slight variations on upstream version numbering, > > package names, etc. which have to be addressed in the SlackBuilds. > > In short, sbopkg attempts to match the > > $PRGNAM-$VERSION-$ARCH-$BUILD$TAG of each installed SBo package with > > the $PRGNAM-$VERSION-$ARCH-$BUILD$TAG of the corresponding > > SlackBuild. If they do not match, then there is an update. > > However, due to the slight upstream variations mentioned > > previously, parsing SlackBuilds and matching up the package name, > > version number, arch, and build number is not always accurate. > > > > In any event, there is a rc1 of sbopkg version 0.0.8 available for > > download for anyone that is interested in testing. I have already > > found one issue that has been fixed in svn and will be included in > > the next release candidate, but I could really use some more > > testers. If you do test, please let me know of any successes or > > problems by posting here, emailing me off list, or better yet, > > subscribing and posting to the sbopkg mailing list. The problems > > will likely manifest themselves in the update list -- either > > incorrectly marking something as a potential update, or missing an > > update that should be listed, or displaying packages with extraneous > > characters in the package name or version number (i.e. such as > > double quotes or something) which then results in a false positive. > > > > Anyway, enough rambling. The source tarball and package for > > 0.0.8rc1 are available here: > > > > http://code.google.com/p/sbopkg/downloads/list > > > > Thanks for your help. > > > > First, thanks for sbopkg, it is far better that my 17-lines > slackmerge script ;) . > I tested SBopkg 0.0.8rc2 and the package doesn't > create /home/sbo . > It is a bug or a feature ? > > _______________________________________________ > 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/ > Excuse me, slackmerge doesn't do which sbopkg does . Here is slackmerge, if you want to integrate it in sbopkg . -------------- next part -------------- A non-text attachment was scrubbed... Name: slackmerge-12.1 Type: application/octet-stream Size: 333 bytes Desc: not available URL: From chess at chessgriffin.com Thu Jul 17 17:50:41 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 17 Jul 2008 13:50:41 -0400 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <20080717213159.45a35bbd@slack.volderking.com> References: <487CAAA7.9050802@chessgriffin.com> <20080717213159.45a35bbd@slack.volderking.com> Message-ID: <487F8671.1000806@chessgriffin.com> Antoine NONYME wrote: > First, thanks for sbopkg, it is far better that my 17-lines > slackmerge script ;) . > I tested SBopkg 0.0.8rc2 and the package doesn't > create /home/sbo . > It is a bug or a feature ? > It's a feature. :-) I didn't want the script to create the local rsync root directory, but it will create the necessary subdirectories, i.e. /home/sbo/12.1. If you create /home/sbo then it will proceed normally. There are a few bug fixes in SVN that are not in rc2, so I'll try and roll out an rc3 soon. Thanks for testing! -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From mickeytintincolle at yahoo.fr Thu Jul 17 20:20:07 2008 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Thu, 17 Jul 2008 22:20:07 +0200 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <487F8671.1000806@chessgriffin.com> References: <487CAAA7.9050802@chessgriffin.com> <20080717213159.45a35bbd@slack.volderking.com> <487F8671.1000806@chessgriffin.com> Message-ID: <20080717222007.026da627@slack.volderking.com> Le Thu, 17 Jul 2008 13:50:41 -0400, Chess Griffin a ?crit : > Antoine NONYME wrote: > > > First, thanks for sbopkg, it is far better that my 17-lines > > slackmerge script ;) . > > I tested SBopkg 0.0.8rc2 and the package doesn't > > create /home/sbo . > > It is a bug or a feature ? > > > > It's a feature. :-) I didn't want the script to create the local > rsync root directory, but it will create the necessary > subdirectories, i.e. /home/sbo/12.1. If you create /home/sbo then it > will proceed normally. > > There are a few bug fixes in SVN that are not in rc2, so I'll try and > roll out an rc3 soon. > > Thanks for testing! > I've found another bug in sbopkg : when I try to list the potential updates (marked as experimental) I've the following error messages : "cut: Octet ou champ de liste invalide. Pour en savoir davantage, faites: ? cut --help ?. cut: Liste des champs manquante. Pour en savoir davantage, faites: ? cut --help ?." Translated in English, that makes : "cut: Bad byte or list field. For further information, type: "cut --help" cut: Missing fields list. For further information, type: "cut --help"" From chess at chessgriffin.com Thu Jul 17 18:29:06 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 17 Jul 2008 14:29:06 -0400 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <20080717222007.026da627@slack.volderking.com> References: <487CAAA7.9050802@chessgriffin.com> <20080717213159.45a35bbd@slack.volderking.com> <487F8671.1000806@chessgriffin.com> <20080717222007.026da627@slack.volderking.com> Message-ID: <487F8F72.8050000@chessgriffin.com> Antoine NONYME wrote: > I've found another bug in sbopkg : when I try to list the potential > updates (marked as experimental) I've the following error messages : > "cut: Octet ou champ de liste invalide. > Pour en savoir davantage, faites: ? cut --help ?. > cut: Liste des champs manquante. > Pour en savoir davantage, faites: ? cut --help ?." > Translated in English, that makes : > "cut: Bad byte or list field. > For further information, type: "cut --help" > cut: Missing fields list. > For further information, type: "cut --help"" > After this occurs, can you exit sbopkg and email me the file $TMP/sbopkg-debug-updatelist? Can you tell if it is a particular package that is causing this problem? I have not seen that type of error yet during testing. Thanks! -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From mickeytintincolle at yahoo.fr Thu Jul 17 20:41:05 2008 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Thu, 17 Jul 2008 22:41:05 +0200 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <487F8F72.8050000@chessgriffin.com> References: <487CAAA7.9050802@chessgriffin.com> <20080717213159.45a35bbd@slack.volderking.com> <487F8671.1000806@chessgriffin.com> <20080717222007.026da627@slack.volderking.com> <487F8F72.8050000@chessgriffin.com> Message-ID: <20080717224105.2844249c@slack.volderking.com> Le Thu, 17 Jul 2008 14:29:06 -0400, Chess Griffin a ?crit : > Antoine NONYME wrote: > > > I've found another bug in sbopkg : when I try to list the potential > > updates (marked as experimental) I've the following error messages : > > "cut: Octet ou champ de liste invalide. > > Pour en savoir davantage, faites: ? cut --help ?. > > cut: Liste des champs manquante. > > Pour en savoir davantage, faites: ? cut --help ?." > > Translated in English, that makes : > > "cut: Bad byte or list field. > > For further information, type: "cut --help" > > cut: Missing fields list. > > For further information, type: "cut --help"" > > > > After this occurs, can you exit sbopkg and email me the file > $TMP/sbopkg-debug-updatelist? Can you tell if it is a particular > package that is causing this problem? I have not seen that type of > error yet during testing. > > Thanks! > Of course :) But I have some shit in my installed packages : -I took the SlackBuild example script and turned it to a script that badly compiles arbitrary tarballs (for example I commented out the set -e) and didn't replace the _SBo tag by something like _experimental_build, so there are fake SBo packages not in the repository . -I have double-version SlackBuilded packages, for example I have both Enlightenment .042 and .043 packages -I have frozen-bubble-2.1.0 and frozen-bubble-menu-0.2.0, there is nothing better to confuse slackpkg and sbopkg ;) -Some of SlackBuilded packages are from the 12.0 repository, some others from the 12.1 one, and I have Slackware 12.0 (where most of the 12.1 SlackBuilds work) . So it's a good challenge to test sbopkg in my (dirty) Slackware installation . -------------- next part -------------- A non-text attachment was scrubbed... Name: sbopkg-debug-updatelist Type: application/octet-stream Size: 2946 bytes Desc: not available URL: From chess at chessgriffin.com Thu Jul 17 19:02:51 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 17 Jul 2008 15:02:51 -0400 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <20080717214346.6bba5af5@slack.volderking.com> References: <487CAAA7.9050802@chessgriffin.com> <20080717213159.45a35bbd@slack.volderking.com> <20080717214346.6bba5af5@slack.volderking.com> Message-ID: <487F975B.5070507@chessgriffin.com> Antoine NONYME wrote: > Excuse me, slackmerge doesn't do which sbopkg does . > Here is slackmerge, if you want to integrate it in sbopkg . > Thanks for sending this, Antoine. Yes, sbopkg builds packages but does not install them. And, as it stands today, I don't plan to add the installation feature, although it would be quite easy to do so -- just call installpkg as your script does. The problem is, the next logical step would be to add a feature to call upgradepkg if there's a newer version, or call removepkg to remove a SBo package. Installing or upgrading or removing a package would make sbopkg more like a package manager, which it's not. From a philosophical standpoint, I view sbopkg as an interface to SlackBuilds.org -- I call it a package browser -- not a replacement for any of the default *pkg tools. It's a subtle distinction, and perhaps a distinction without a difference. And maybe my view is wrong, so it's good for me to revisit this issue from time to time. Believe me, you are not the first to ask -- I've had many emails asking for the same thing. :-) So, who knows, maybe one day I'll change my mind and add in these features, but for now, I don't have any plans to do that. I really appreciate the feedback, though. -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From chess at chessgriffin.com Thu Jul 17 19:08:26 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 17 Jul 2008 15:08:26 -0400 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <20080717224105.2844249c@slack.volderking.com> References: <487CAAA7.9050802@chessgriffin.com> <20080717213159.45a35bbd@slack.volderking.com> <487F8671.1000806@chessgriffin.com> <20080717222007.026da627@slack.volderking.com> <487F8F72.8050000@chessgriffin.com> <20080717224105.2844249c@slack.volderking.com> Message-ID: <487F98AA.60300@chessgriffin.com> Antoine NONYME wrote: > > So it's a good challenge to test sbopkg in my (dirty) Slackware > installation . > Wow! Thank you very much for sending this along. I'll look through this and test a few things. A few of the errors I see have been corrected in SVN but there's still more work to do. When exactly do you get the error message you mentioned previously? Does the update list actually appear in the ncurses interface after selecting "YES" to the 'experimental' warning or does sbopkg die and exit? I'm just trying to envision what happens after you select "UPDATES" in the main menu. Thanks again for testing, Antoine! It's really appreciated. -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From mickeytintincolle at yahoo.fr Thu Jul 17 21:30:52 2008 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Thu, 17 Jul 2008 23:30:52 +0200 Subject: [Slackbuilds-users] sbopkg 0.0.8rc1 testers needed In-Reply-To: <487F98AA.60300@chessgriffin.com> References: <487CAAA7.9050802@chessgriffin.com> <20080717213159.45a35bbd@slack.volderking.com> <487F8671.1000806@chessgriffin.com> <20080717222007.026da627@slack.volderking.com> <487F8F72.8050000@chessgriffin.com> <20080717224105.2844249c@slack.volderking.com> <487F98AA.60300@chessgriffin.com> Message-ID: <20080717233052.6f3f05ca@slack.volderking.com> Le Thu, 17 Jul 2008 15:08:26 -0400, Chess Griffin a ?crit : > Antoine NONYME wrote: > > > > So it's a good challenge to test sbopkg in my (dirty) Slackware > > installation . > > > > Wow! Thank you very much for sending this along. I'll look through > this and test a few things. A few of the errors I see have been > corrected in SVN but there's still more work to do. > > When exactly do you get the error message you mentioned previously? > Does the update list actually appear in the ncurses interface after > selecting "YES" to the 'experimental' warning or does sbopkg die and > exit? I'm just trying to envision what happens after you select > "UPDATES" in the main menu. > > Thanks again for testing, Antoine! It's really appreciated. > I first get the error messages, then I get the update list and I can quit sbopkg without problem . sbopkg doesn't die . From lukenshiro at ngi.it Sun Jul 20 14:06:55 2008 From: lukenshiro at ngi.it (LukenShiro) Date: Sun, 20 Jul 2008 16:06:55 +0200 Subject: [Slackbuilds-users] tiny error in djvulibre Message-ID: <200807201606.55750.lukenshiro@ngi.it> I've noticed a tiny error in djvulibre's doinst.sh doinst.sh contains these lines: """ if [ -x /usr/share/djvu/osi/desktop/register-djvu-mime ]; then /usr/share/djvu/osi/desktop/register-djvu-mime install fi( cd usr/lib ; rm -rf libdjvulibre.so.15 ) ... etc .... """ In the 3rd line it needs a linefeed just after "fi" , in order to avoid a syntax error (depending on automatic symbolic links' management that is consecutively added in doinst.sh). Regards. -- GNU/Linux * Slackware 'current' LU #210970 LM #98222 SU #12583 "Everything depends. Nothing is always. Everything is sometimes.." From rworkman at slackbuilds.org Sun Jul 20 23:23:04 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 20 Jul 2008 18:23:04 -0500 Subject: [Slackbuilds-users] tiny error in djvulibre In-Reply-To: <200807201606.55750.lukenshiro@ngi.it> References: <200807201606.55750.lukenshiro@ngi.it> Message-ID: <4883C8D8.2070405@slackbuilds.org> LukenShiro wrote: > I've noticed a tiny error in djvulibre's doinst.sh > > doinst.sh contains these lines: > """ > if [ -x /usr/share/djvu/osi/desktop/register-djvu-mime ]; then > /usr/share/djvu/osi/desktop/register-djvu-mime install > fi( cd usr/lib ; rm -rf libdjvulibre.so.15 ) > ... etc .... > """ > > In the 3rd line it needs a linefeed just after "fi" , in order to avoid > a syntax error (depending on automatic symbolic links' management that > is consecutively added in doinst.sh). Fixed; thanks. -RW From rworkman at slackbuilds.org Mon Jul 21 16:33:00 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 21 Jul 2008 16:33:00 +0000 Subject: [Slackbuilds-users] Updates - 20080721 Message-ID: <20080721163300.GA539@slackbuilds.org> Mon Jul 21 16:27:39 UTC 2008 audio/gmpc-plugins: Added - gmpc-plugins are extra plugins for GMPC. Thanks to Erik Hanson. --David Somero audio/gmpc: Added - GMPC is a frontend for the mpd. Thanks to Erik Hanson. --David Somero audio/lv2core: Added - LV2 is a successor to LADSPA, Thanks to Heinz Wiesinger. --David Somero development/help2man: Added - a tool for automatically generating simple manual pages from program output. Thanks to Chess Griffin. --David Somero games/openarena: Updated for version 0.7.7. Thanks to Chess Griffin. --David Somero libraries/ftgl: Added - FTGL is a font rendering library for OpenGL applications. Thanks to Niklas "Nille" ? kerstr??m. --David Somero libraries/gstreamer: Upated for version 0.10.20. This is necessary for building the gst-plugins currently in the repository. Sorry for letting that slip. Thanks to Michiel van Wessem. --Erik Hanson multimedia/dvgrab: Added - dvgrab receives audio and video data from a digital camcorder via an IEEE1394 Thanks to Murat D. Kadirov. --David Somero multimedia/gpodder: Updated for version 0.11.3. Thanks to Chess Griffin. --David Somero multimedia/smplayer: Added support for the optional icon themes available. Thanks to Erik Hanson. --David Somero network/elinks: Updated for version 0.11.4. Thanks to Brian Muramatsu. --David Somero network/leafnode: Updated for version 2.0.0.alpha20080624a. Thanks to Andrew Strong. --David Somero network/murmur: Added - Murmur is the VoIP server component for Mumble. Thanks to "adev". --David Somero network/nginx: Updated for version 0.7.5. Thanks to Cherife Li. --David Somero network/wireshark: Updated for version 1.0.2. Thanks to Michiel van Wessem. --David Somero network/wol: Added - wol implements Wake On LAN functionality in a small program. Thankd to Brian Muramatsu. --David Somero office/freemind: Added - freemind helps keeping track of projects, including subtasks, state of subtasks and time recording. Thanks to Dhaby Xiloj. --David Somero system/fpm2: Added - Figaro's Password Manager 2 is a program that allows you to securely store passwords using a GTK2 interface. Thanks to Erik Hanson. --David Somero system/nvidia-driver: Updated for version 173.14.09. system/nvidia-kernel: Updated for version 173.14.09. system/nvidia-legacy-driver: Added - nvidia legacy version 96.43.05. system/nvidia-legacy-kernel: Added - nvidia legacy version 96.43.05. Thanks to Heinz Wiesinger. --David Somero system/qstardict: Added - qstardict is a StarDict clone written with using Qt4. Thanks to grissiom. --David Somero system/sakura: Updated for version 2.2.0. New Maintainer. Thanks to Kristaps Esterlinsh. --David Somero system/stardict: Updated for version 3.0.1. Thanks to Murat D. Kadirov. --David Somero system/suspend: Added - suspend is a set of userland tools for suspend and resume on laptops; it supports some features not included in the kernel's suspend/resume framework. Thanks to Murat D. Kadirov. --rworkman From pc_warner at yahoo.com Sun Jul 27 00:36:48 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Sat, 26 Jul 2008 17:36:48 -0700 (PDT) Subject: [Slackbuilds-users] wicd problems -wicd users read this! Message-ID: <973890.72847.qm@web57707.mail.re3.yahoo.com> This email is more of a heads up for those using wicd as the problems listed here seem to be from upstream. The biggest problem I see with wicd is the configuration and log files it saves under /opt/wicd. In particular there is a log file at /opt/wicd/data/wicd.log that is world readable and writable. A malicious user could potentially use this to fill up your hdd partition that /opt resides on. Worse yet, I found out that the file sometimes will display your network keys in clear text. Perhaps touching the file in the slackBuild and setting better initial permissions would help. If wicd really needs the file world writable then something upstream is amiss. Also, the current version of wicd does not work with dbus-python 0.83.0. This shouldn't be a problem for anyone using the official Slackware dbus-python package for Slackware 12.1, however. FWIW, I had problems using wicd on a WEP network (using patched and non-patched versions with the Slackware default networking enabled and disabled). Using passphrase instead of the key or using quotes did not help. From rw at rlworkman.net Sun Jul 27 05:14:25 2008 From: rw at rlworkman.net (Robby Workman) Date: Sun, 27 Jul 2008 00:14:25 -0500 Subject: [Slackbuilds-users] wicd problems -wicd users read this! In-Reply-To: <973890.72847.qm@web57707.mail.re3.yahoo.com> References: <973890.72847.qm@web57707.mail.re3.yahoo.com> Message-ID: <488C0431.4050803@rlworkman.net> Phillip Warner wrote: > This email is more of a heads up for those using wicd as the problems listed here seem to be from upstream. > > The biggest problem I see with wicd is the configuration and log files it saves under /opt/wicd. In particular there is a log file at > /opt/wicd/data/wicd.log that is world readable and writable. A malicious user could potentially use this to fill up your hdd partition that /opt resides on. Worse yet, I found out that the file sometimes will display your network keys in clear text. Perhaps touching the file in the slackBuild and setting better initial permissions would help. If wicd really needs the file world writable then something upstream is amiss. > > Also, the current version of wicd does not work with dbus-python 0.83.0. This shouldn't be a problem for anyone using the official Slackware dbus-python package for Slackware 12.1, however. > > FWIW, I had problems using wicd on a WEP network (using patched and non-patched versions with the Slackware default networking enabled and disabled). Using passphrase instead of the key or using quotes did not help. I *strongly* urge all Wicd users to upgrade to the wicd package in my personal repository. It's from the testing-1.5.0 branch, which is really close to release of 1.5.0 now, and all of the above problems are addressed. More importantly, it works better :) -RW From adis at linux.org.ba Sun Jul 27 08:45:37 2008 From: adis at linux.org.ba (Adis Nezirovic) Date: Sun, 27 Jul 2008 10:45:37 +0200 Subject: [Slackbuilds-users] New package manager for Slackware Message-ID: <20080727084537.GC4744@hiigarah.localhost.ba> For quite some time I'm working on this pet project of mine, a package manager for Slackware, written in Python: http://localhost.ba/Slackware/Slapkg Nothing too fancy, just a *reimplementation* of pkgtool functionality in high level language, with less lines of code and better performance. Additionally, I also implemented slackpkg like functionality (remote package upgrades). I really like slackpkg, but it is unbelievably slow when creating "package upgrade lists" (we're at least 10x faster) My goal with this project is either of the following: a) To rule the (Slackware) world (just kidding, of course) b) To see some speed improvements in pkgtool and slackpkg i.e. beat them with (code) stick to do it faster. Anyway, I would really appreciate some additional exposure. I'm already using slapkg on my machines daily, many of them even survived upgrade from Slackware 12.1 to Slackware-current, and I don't expect any catastrophic bugs. P.S. Sorry for spamming slackbuilds.org mailing list, but I could not think of any other more appropriate place ;-) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From pc_warner at yahoo.com Mon Jul 28 04:33:35 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Sun, 27 Jul 2008 21:33:35 -0700 (PDT) Subject: [Slackbuilds-users] wicd problems -wicd users read this! In-Reply-To: <488C0431.4050803@rlworkman.net> Message-ID: <354314.81559.qm@web57705.mail.re3.yahoo.com> Thanks for the info, Robby :) --phil --- On Sat, 7/26/08, Robby Workman wrote: > From: Robby Workman > Subject: Re: wicd problems -wicd users read this! > To: pc_warner at yahoo.com > Cc: slackbuilds-users at slackbuilds.org > Date: Saturday, July 26, 2008, 10:14 PM > Phillip Warner wrote: > > This email is more of a heads up for those using wicd > as the problems listed here seem to be from upstream. > > > > The biggest problem I see with wicd is the > configuration and log files it saves under /opt/wicd. In > particular there is a log file at > > /opt/wicd/data/wicd.log that is world readable and > writable. A malicious user could potentially use this to > fill up your hdd partition that /opt resides on. Worse > yet, I found out that the file sometimes will display your > network keys in clear text. Perhaps touching the file in > the slackBuild and setting better initial permissions would > help. If wicd really needs the file world writable then > something upstream is amiss. > > > > Also, the current version of wicd does not work with > dbus-python 0.83.0. This shouldn't be a problem for > anyone using the official Slackware dbus-python package for > Slackware 12.1, however. > > > > FWIW, I had problems using wicd on a WEP network > (using patched and non-patched versions with the Slackware > default networking enabled and disabled). Using passphrase > instead of the key or using quotes did not help. > > > I *strongly* urge all Wicd users to upgrade to the wicd > package in my > personal repository. It's from the testing-1.5.0 > branch, which is > really close to release of 1.5.0 now, and all of the above > problems > are addressed. More importantly, it works better :) > > -RW From adis at linux.org.ba Sat Jul 26 21:01:05 2008 From: adis at linux.org.ba (Adis Nezirovic) Date: Sat, 26 Jul 2008 23:01:05 +0200 Subject: [Slackbuilds-users] New package manager for Slackware Message-ID: <20080726210105.GA4744@hiigarah.localhost.ba> For quite some time I'm working on this pet project of mine, a package manager for Slackware, written in Python: http://localhost.ba/Slackware/Slapkg Nothing too fancy, just a *reimplementation* of pkgtool functionality in high level language, with less lines of code and better performance. Additionally, I also implemented slackpkg like functionality (remote package upgrades). I really like slackpkg, but it is unbelievably slow when creating "package upgrade lists" (we're at least 10x faster) My goal with this project is either of the following: a) To rule the (Slackware) world (just kidding, of course) b) To see some speed improvements in pkgtool and slackpkg i.e. beat them with (code) stick to do it faster. Anyway, I would really appreciate some additional exposure. I'm already using slapkg on my machines daily, many of them even survived upgrade from Slackware 12.1 to Slackware-current, and I don't expect any catastrophic bugs. P.S. Sorry for spamming slackbuilds.org mailing list, but I could not think of any more appropriate place ;-) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From gmartin at gmartin.org Thu Jul 31 22:55:13 2008 From: gmartin at gmartin.org (Greg Martin) Date: Thu, 31 Jul 2008 18:55:13 -0400 Subject: [Slackbuilds-users] Slackbuild for nagios 3.x In-Reply-To: <4878BF26.3010508@markwalling.org> References: <4874CE9C.9090601@gmartin.org> <196c22970807090807l38d4ce8dred16a44f9c04ec2d@mail.gmail.com> <4874F5FD.9030205@gmartin.org> <487667F7.8050100@gmartin.org> <4878BF26.3010508@markwalling.org> Message-ID: <489242D1.10801@gmartin.org> Mark, I finally got around to checking out how dovecot & postfix manage the user account issue. I notice that both specify specific GID & UID for the respective groups & users. Do I need to specify these? How do I know the GID/UID I select will be available on the build system? Thanks \\Greg Mark Walling wrote: > Greg Martin wrote: > > >> And along those lines, I've specified both packages to use the >> nagios.nagios user/group pair. Should I create the user & group? or is >> that a no-no? >> >> > > I would suggest looking at the dovecot.SlackBuild and > postfix.SlackBuilds for how to handle the group creation. > > -M > >