From slakmagik at gmail.com Mon Feb 1 00:20:02 2010 From: slakmagik at gmail.com (slakmagik) Date: Sun, 31 Jan 2010 19:20:02 -0500 Subject: [sbopkg-users] Chrome problem In-Reply-To: <20100131214131.GA3901@Junius> References: <20100131173949.GA6605@Junius> <20100131212838.GA24928@surfbox> <20100131214131.GA3901@Junius> Message-ID: <20100201002002.GA28099@surfbox> On 2010-01-31 (Sun) 21:41:31 [+0000], David Woodfall wrote: > On (16:28 31/01/10), slakmagik put forth the proposition: > >On 2010-01-31 (Sun) 17:39:50 [+0000], David Woodfall wrote: > >>I noticed that building chrome gets stuck in a loop with sbopkg. > >>Slackbuild works fine though. > >> > > Strange, it now works but I do get a checksum fail. > > > > >I can't reproduce this. Using both trunk (build) and 0.31.1 (build, > >install, uninstall), sbopkg worked fine for me (except for an md5sum > >mismatch). Can you say what version of sbopkg, version of slackware, > >arch of machine, what part exactly is looping, or any other sort of > >detail? > > Slackware 13 > sbopkg 0.31.1 > Don't recall the exact loop but it looked like it was needing some > input. > Okay, if it comes up again, try to report exactly what happens (and your arch), and I'll keep an eye out for it myself but, for now, I'm blaming it on cosmic rays. :) From chess at chessgriffin.com Mon Feb 1 02:01:39 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Sun, 31 Jan 2010 21:01:39 -0500 Subject: [sbopkg-users] Chrome problem In-Reply-To: <20100201002002.GA28099@surfbox> References: <20100131173949.GA6605@Junius> <20100131212838.GA24928@surfbox> <20100131214131.GA3901@Junius> <20100201002002.GA28099@surfbox> Message-ID: <20100201020139.GA25356@localhost> * slakmagik [2010-01-31 19:20:02]: > On 2010-01-31 (Sun) 21:41:31 [+0000], David Woodfall wrote: > > On (16:28 31/01/10), slakmagik put forth the proposition: > > >On 2010-01-31 (Sun) 17:39:50 [+0000], David Woodfall wrote: > > >>I noticed that building chrome gets stuck in a loop with sbopkg. > > >>Slackbuild works fine though. > > >> > > > > Strange, it now works but I do get a checksum fail. > > > > > > > >I can't reproduce this. Using both trunk (build) and 0.31.1 (build, > > >install, uninstall), sbopkg worked fine for me (except for an md5sum > > >mismatch). Can you say what version of sbopkg, version of slackware, > > >arch of machine, what part exactly is looping, or any other sort of > > >detail? > > > > Slackware 13 > > sbopkg 0.31.1 > > Don't recall the exact loop but it looked like it was needing some > > input. > > > > Okay, if it comes up again, try to report exactly what happens (and your > arch), and I'll keep an eye out for it myself but, for now, I'm blaming > it on cosmic rays. :) I got the same result as slakmagik - bad MD5SUM, but google-chrome and its 2 deps built and installed fine. Those cosmic rays are a bitch. :-) -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From me at alkos333.net Wed Feb 17 03:32:47 2010 From: me at alkos333.net (alkos333) Date: Tue, 16 Feb 2010 21:32:47 -0600 Subject: [sbopkg-users] Weird google-chrome Related Error During Update Message-ID: The subject pretty much speaks for itself. This is what I see on the screen: http://bit.ly/an9BfD -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From chess at chessgriffin.com Wed Feb 17 03:59:29 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 16 Feb 2010 22:59:29 -0500 Subject: [sbopkg-users] Weird google-chrome Related Error During Update In-Reply-To: References: Message-ID: <20100217035929.GA10931@localhost> * alkos333 [2010-02-16 21:32:47]: > The subject pretty much speaks for itself. This is what I see on the > screen: http://bit.ly/an9BfD > Hmm, yes, I can confirm this. The update progressbar continues on, and the list of updates is displayed correctly, but that dialog breakage looks ugly for sure. Thanks for letting us know. We'll look into it. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From me at alkos333.net Wed Feb 17 04:17:18 2010 From: me at alkos333.net (alkos333) Date: Tue, 16 Feb 2010 22:17:18 -0600 Subject: [sbopkg-users] Weird google-chrome Related Error During Update In-Reply-To: <20100217035929.GA10931@localhost> References: <20100217035929.GA10931@localhost> Message-ID: On Tue, Feb 16, 2010 at 9:59 PM, Chess Griffin wrote: > Hmm, yes, I can confirm this. Glad you were able to reproduce it. -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From agentc0re at learnix.net Wed Feb 17 09:36:42 2010 From: agentc0re at learnix.net (Jonathan Larsen) Date: Wed, 17 Feb 2010 02:36:42 -0700 Subject: [sbopkg-users] mlt and openshot queue files Message-ID: <654a19551002170136q5382d351r5a9b352e2c6dabea@mail.gmail.com> i'd like to submit these two for approval. http://learnix.net/slackbuilds/queues/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauro.giachero at gmail.com Wed Feb 17 12:57:02 2010 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Wed, 17 Feb 2010 13:57:02 +0100 Subject: [sbopkg-users] Weird google-chrome Related Error During Update In-Reply-To: References: Message-ID: On Wed, Feb 17, 2010 at 4:32 AM, alkos333 wrote: > The subject pretty much speaks for itself. This is what I see on the > screen: http://bit.ly/an9BfD > This was unexpected -- the script requires the source tarball to determine the chrome version. I can't think about any sane way to address this. The only workaround I see is to trap the error, silence the messages and fall back to trusting the .info file for the version number. Maybe log something about the event. Does that look reasonable? -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess at chessgriffin.com Wed Feb 17 14:42:08 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 17 Feb 2010 09:42:08 -0500 Subject: [sbopkg-users] Weird google-chrome Related Error During Update In-Reply-To: References: Message-ID: <20100217144208.GA16336@localhost> * Mauro Giachero [2010-02-17 13:57:02]: > On Wed, Feb 17, 2010 at 4:32 AM, alkos333 wrote: > > > The subject pretty much speaks for itself. This is what I see on the > > screen: http://bit.ly/an9BfD > > > > This was unexpected -- the script requires the source tarball to > determine the chrome version. I can't think about any sane way to > address this. The only workaround I see is to trap the error, silence > the messages and fall back to trusting the .info file for the version > number. Maybe log something about the event. Does that look > reasonable? > Yes, that VERSION line in the SlackBuild is causing the issue and some kind of workaround like you describe is probably the only solution. If I am understanding the SlackBuild script correctly, the true version of Google Chrome changes daily. So, from sbopkg's standpoint, the "version" in the repo will always be different. If we ignore this VERSION line, then the repo version will be stuck at whatever is hardcoded into the .info file, which means the user's version will likey always show up as a 'installed version is newer than repo' which we might just have to live with. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From me at alkos333.net Thu Feb 18 01:47:53 2010 From: me at alkos333.net (alkos333) Date: Wed, 17 Feb 2010 19:47:53 -0600 Subject: [sbopkg-users] 32-bit flash Message-ID: I'm running Slackware64 and since hulu doesn't work on 64-bit flash, I thought I'd install a 32-bit flash by passing ARCH=i386 option when I build, but it errors out like so: http://paste.pocoo.org/show/179539/ -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From chess at chessgriffin.com Thu Feb 18 01:58:57 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 17 Feb 2010 20:58:57 -0500 Subject: [sbopkg-users] 32-bit flash In-Reply-To: References: Message-ID: <20100218015857.GA16879@localhost> * alkos333 [2010-02-17 19:47:53]: > I'm running Slackware64 and since hulu doesn't work on 64-bit flash, I > thought I'd install a 32-bit flash by passing ARCH=i386 option when I > build, but it errors out like so: http://paste.pocoo.org/show/179539/ > Try doing from root terminal: export ARCH=i386 && sbopkg or export ARCH=i386 && sbopkg -b flash-player-plugin or add 'export ARCH=i386' to your sbopkg.conf file and then run sbopkg. Since ARCH is determined at startup, the 'options' in the sbopkg info_item menu (the package menu) does not change it. Perhaps it should. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From me at alkos333.net Thu Feb 18 02:05:50 2010 From: me at alkos333.net (alkos333) Date: Wed, 17 Feb 2010 20:05:50 -0600 Subject: [sbopkg-users] 32-bit flash In-Reply-To: <20100218015857.GA16879@localhost> References: <20100218015857.GA16879@localhost> Message-ID: On Wed, Feb 17, 2010 at 7:58 PM, Chess Griffin wrote: > Since ARCH is determined at startup, the 'options' in the sbopkg > info_item menu (the package menu) does not change it. ?Perhaps it > should. I personally thought it should, which is why I tried it in the first place. This works though. Thanks for the suggestion. -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From me at alkos333.net Thu Feb 18 02:09:05 2010 From: me at alkos333.net (alkos333) Date: Wed, 17 Feb 2010 20:09:05 -0600 Subject: [sbopkg-users] 32-bit flash In-Reply-To: References: <20100218015857.GA16879@localhost> Message-ID: On Wed, Feb 17, 2010 at 8:05 PM, alkos333 wrote: > > > I personally thought it should, which is why I tried it in the first > place. ?This works though. ?Thanks for the suggestion. However, now both YouTube and Hulu claim I have an old version of flash :/ Go figure. -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From chess at chessgriffin.com Thu Feb 18 02:13:47 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 17 Feb 2010 21:13:47 -0500 Subject: [sbopkg-users] 32-bit flash In-Reply-To: References: <20100218015857.GA16879@localhost> Message-ID: <20100218021347.GA17217@localhost> * alkos333 [2010-02-17 20:09:05]: > On Wed, Feb 17, 2010 at 8:05 PM, alkos333 wrote: > > > > > > I personally thought it should, which is why I tried it in the first > > place. ?This works though. ?Thanks for the suggestion. > > However, now both YouTube and Hulu claim I have an old version of flash :/ > > Go figure. > > Hmm, that's no good. But thanks for letting me know those other suggestions worked. You are right, we probably should allow ARCH be set in the options settings. Thanks for the report. I always hate to ask, but can you file this and the Google Chrome in the issue tracker? Thank you, Alex. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From chess at chessgriffin.com Thu Feb 18 04:18:04 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 17 Feb 2010 23:18:04 -0500 Subject: [sbopkg-users] mlt and openshot queue files In-Reply-To: <654a19551002170136q5382d351r5a9b352e2c6dabea@mail.gmail.com> References: <654a19551002170136q5382d351r5a9b352e2c6dabea@mail.gmail.com> Message-ID: <20100218041804.GA18033@localhost> * Jonathan Larsen [2010-02-17 02:36:42]: > i'd like to submit these two for approval. > http://learnix.net/slackbuilds/queues/ Sorry, I had a reply all queued up and forgot to send it! Thanks for the submission. I'll pull these into the repo. :-) -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From mauro.giachero at gmail.com Mon Feb 22 14:34:21 2010 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Mon, 22 Feb 2010 15:34:21 +0100 Subject: [sbopkg-users] [ANN] SBo/Sbopkg comprehensive queue archive Message-ID: Hello everybody. Some time ago I started building a comprehensive queue archive that would allow me to build packages without having to go through all their dependencies. Because I know we want to have control over dependencies, but sometimes populating the queue is nothing more than a hassle. I'm pleased to announce that the queue archive I built up is now available as a git repository at http://gitorious.org/sbopkg-slackware-queues It contains a queue for each of the scripts available on SlackBuilds.org for Slackware 13.0 [1], plus a tools/ directory with the simple command line tools I developed to make it easier to track updates. To try the repository, first off you have to clone it using either git clone git:// gitorious.org/sbopkg-slackware-queues/sbopkg-slackware-queues.git or git clone http://git.gitorious.org/sbopkg-slackware-queues/sbopkg-slackware-queues.git (whichever works better for you), which creates a new directory named "sbopkg-slackware-queues". Then export QUEUEDIR=/path/to/repository and start sbopkg [2]. Once this is all set up, you should be able to build and install any package by issuing something like sbopkg -R -k -i foo.sqf (where "foo" is the package name, of course). Missing dependencies should be built and installed in the correct order [3]. Updates can be fetched issuing the command git pull origin from the repository directory. Since I use only a small fraction of all those packages, there are most probably errors or badly chosen optional dependencies here and there. I'll really appreciate hints and bug reports from anybody willing to contribute. Maintainers may also want to have a look at the queues for their own packages, since some contain notes about issues found while working on this. You can also see them all with grep -i '# Note' *.sqf I'm looking forward to hear your comments and suggestions. With best regards -- Mauro Giachero [1] As you may easily guess, this work is not endorsed by neither Slackware, SlackBuilds.org or Sbopkg. [2] You can make the QUEUEDIR export permanent by editing /etc/sbopkg/sbopkg.conf. [3] "should" is a keyword here -- you're encouraged to review the list of the packages that are going to be built/installed before starting the process. This repository is not a way to turn sbopkg into apt ;-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcintosh at cotterochan.co.uk Mon Feb 22 17:25:02 2010 From: mcintosh at cotterochan.co.uk (Steven A. McIntosh) Date: Mon, 22 Feb 2010 17:25:02 +0000 Subject: [sbopkg-users] [ANN] SBo/Sbopkg comprehensive queue archive In-Reply-To: References: Message-ID: <4B82BDEE.9040408@cotterochan.co.uk> Sounds great, when is it going to be added by default sbopkg? This would allow people to select the package that they wanted and all the dependencies would be installed, but how would it handle optional dependencies? samac On 02/22/2010 02:34 PM, Mauro Giachero wrote: > Hello everybody. > > Some time ago I started building a comprehensive queue archive that would > allow me to build packages without having to go through all their > dependencies. Because I know we want to have control over dependencies, but > sometimes populating the queue is nothing more than a hassle. > > I'm pleased to announce that the queue archive I built up is now available > as a git repository at > http://gitorious.org/sbopkg-slackware-queues > It contains a queue for each of the scripts available on SlackBuilds.org for > Slackware 13.0 [1], plus a tools/ directory with the simple command line > tools I developed to make it easier to track updates. > > To try the repository, first off you have to clone it using either > git clone git:// > gitorious.org/sbopkg-slackware-queues/sbopkg-slackware-queues.git > or > git clone > http://git.gitorious.org/sbopkg-slackware-queues/sbopkg-slackware-queues.git > (whichever works better for you), which creates a new directory named > "sbopkg-slackware-queues". Then > export QUEUEDIR=/path/to/repository > and start sbopkg [2]. > > Once this is all set up, you should be able to build and install any package > by issuing something like > sbopkg -R -k -i foo.sqf > (where "foo" is the package name, of course). Missing dependencies should be > built and installed in the correct order [3]. > > Updates can be fetched issuing the command > git pull origin > from the repository directory. > > Since I use only a small fraction of all those packages, there are most > probably errors or badly chosen optional dependencies here and there. I'll > really appreciate hints and bug reports from anybody willing to contribute. > Maintainers may also want to have a look at the queues for their own > packages, since some contain notes about issues found while working on this. > You can also see them all with > grep -i '# Note' *.sqf > > I'm looking forward to hear your comments and suggestions. > > With best regards > -- > Mauro Giachero > > [1] As you may easily guess, this work is not endorsed by neither Slackware, > SlackBuilds.org or Sbopkg. > [2] You can make the QUEUEDIR export permanent by editing > /etc/sbopkg/sbopkg.conf. > [3] "should" is a keyword here -- you're encouraged to review the list of > the packages that are going to be built/installed before starting the > process. This repository is not a way to turn sbopkg into apt ;-) > > > > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users From mauro.giachero at gmail.com Mon Feb 22 17:32:47 2010 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Mon, 22 Feb 2010 18:32:47 +0100 Subject: [sbopkg-users] [ANN] SBo/Sbopkg comprehensive queue archive In-Reply-To: <4B82BDEE.9040408@cotterochan.co.uk> References: <4B82BDEE.9040408@cotterochan.co.uk> Message-ID: On Mon, Feb 22, 2010 at 6:25 PM, Steven A. McIntosh < mcintosh at cotterochan.co.uk> wrote: > Sounds great, when is it going to be added by default sbopkg? > I'm not sure it will ever be... > This would allow people to select the package that they wanted and all the > dependencies would be installed, but how would it handle optional > dependencies? > I knew somebody would have asked... Actually, there's no way to handle them -- I simply chose a set of dependencies based on my own rules (which changed daily, of course, but were generally in the direction of "support all the features by default, people will know how to disable them manually editing the queues"). Those choices can of course be changed if believed to be suboptimal. samac -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcintosh at cotterochan.co.uk Mon Feb 22 17:46:12 2010 From: mcintosh at cotterochan.co.uk (Steven A. McIntosh) Date: Mon, 22 Feb 2010 17:46:12 +0000 Subject: [sbopkg-users] [ANN] SBo/Sbopkg comprehensive queue archive In-Reply-To: References: <4B82BDEE.9040408@cotterochan.co.uk> Message-ID: <4B82C2E4.9090000@cotterochan.co.uk> Thanks. Guess I will just do it the old fashioned way! It is probably better to read the information and install the dependencies and their dependencies ad infinitum. Then at least you understand. samac On 02/22/2010 05:32 PM, Mauro Giachero wrote: > On Mon, Feb 22, 2010 at 6:25 PM, Steven A. McIntosh< > mcintosh at cotterochan.co.uk> wrote: > >> Sounds great, when is it going to be added by default sbopkg? >> > > I'm not sure it will ever be... > > >> This would allow people to select the package that they wanted and all the >> dependencies would be installed, but how would it handle optional >> dependencies? >> > > I knew somebody would have asked... > Actually, there's no way to handle them -- I simply chose a set of > dependencies based on my own rules (which changed daily, of course, but were > generally in the direction of "support all the features by default, people > will know how to disable them manually editing the queues"). Those choices > can of course be changed if believed to be suboptimal. > > samac > > > > > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users From chess at chessgriffin.com Mon Feb 22 20:58:25 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Mon, 22 Feb 2010 15:58:25 -0500 Subject: [sbopkg-users] [Slackbuilds-users] [ANN] SBo/Sbopkg comprehensive queue archive In-Reply-To: References: Message-ID: <20100222205825.GA7055@localhost> * Mauro Giachero [2010-02-22 15:34:21]: > Hello everybody. > > Some time ago I started building a comprehensive queue archive that > would allow me to build packages without having to go through all > their dependencies. Because I know we want to have control over > dependencies, but sometimes populating the queue is nothing more than > a hassle. Very nice, Mauro. This looks like a great resource and should be a big help to those folks who use sbopkg queuefiles. We already include a few queuefiles with sbopkg, and some others are available on the sbopkg.org website, but your repo really takes sbopkg queuefiles to the next level. Thanks! -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From chess at chessgriffin.com Mon Feb 22 21:01:09 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 23 Feb 2010 02:31:09 +0530 Subject: [sbopkg-users] [Slackbuilds-users] [ANN] SBo/Sbopkg comprehensive queue archive In-Reply-To: References: Message-ID: <1C62C9CFE2DE48EB9D7A35E8AA0C5BA6@angleritech.com> * Mauro Giachero [2010-02-22 15:34:21]: > Hello everybody. > > Some time ago I started building a comprehensive queue archive that > would allow me to build packages without having to go through all > their dependencies. Because I know we want to have control over > dependencies, but sometimes populating the queue is nothing more than > a hassle. Very nice, Mauro. This looks like a great resource and should be a big help to those folks who use sbopkg queuefiles. We already include a few queuefiles with sbopkg, and some others are available on the sbopkg.org website, but your repo really takes sbopkg queuefiles to the next level. Thanks! -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ 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/