From phillip.c.warner at gmail.com Wed Jul 1 05:02:58 2009 From: phillip.c.warner at gmail.com (Phillip Warner) Date: Wed, 1 Jul 2009 00:02:58 -0500 Subject: [sbopkg-users] sbopkg-0.30.0alpha1 root privileges In-Reply-To: <20090628233303.GA31866@localhost> References: <200906281508.44680.x11r6@go2.pl> <20090628233303.GA31866@localhost> Message-ID: If you don't like it you could always just use the older version of sbopkg for now. If that doesn't work in the future you have the source, so you can fix it. On Sun, Jun 28, 2009 at 6:33 PM, Chess Griffin wrote: > * x11r6 at go2.pl [2009-06-28 15:08:44]: > > > Hi! > > > > New sbopkg-0.30.0alpha1 after "sbopkg -r" as user: > > > > sbopkg: sbopkg must be run by the root user. Exiting. > > > > Is it really necessary? > > > > Cheers, -X. > > > > Based on feedback here on the ML, and based on discussions with my > co-developers and others, it was decided that, for security, code > maintenance, and other reasons, it was best to require root privileges, > just like pkgtools and slackpkg. > > -- > Chess Griffin > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rw at rlworkman.net Wed Jul 1 05:15:34 2009 From: rw at rlworkman.net (Robby Workman) Date: Wed, 1 Jul 2009 00:15:34 -0500 Subject: [sbopkg-users] sbopkg-0.30.0alpha1 root privileges In-Reply-To: <200906281508.44680.x11r6@go2.pl> References: <200906281508.44680.x11r6@go2.pl> Message-ID: <20090701001534.3f62b839@liberty.rlwhome.lan> On Sun, 28 Jun 2009 15:08:44 +0200 x11r6 at go2.pl wrote: > New sbopkg-0.30.0alpha1 after "sbopkg -r" as user: > > sbopkg: sbopkg must be run by the root user. Exiting. > > Is it really necessary? Why would you *not* want to run it as root? What do you hope to accomplish by that? Everything that sbopkg does, for the most part, requires root privileges. Therefore, you can either run it as root, or the developers can add a lot of potentially complex and otherwise unnecessary code to it enabling it to run with normal user privileges. The sky is not falling. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From x11r6 at go2.pl Wed Jul 1 11:43:43 2009 From: x11r6 at go2.pl (x11r6 at go2.pl) Date: Wed, 1 Jul 2009 13:43:43 +0200 Subject: [sbopkg-users] sbopkg-0.30.0alpha1 root privileges In-Reply-To: <20090701001534.3f62b839@liberty.rlwhome.lan> References: <200906281508.44680.x11r6@go2.pl> <20090701001534.3f62b839@liberty.rlwhome.lan> Message-ID: <200907011343.46231.x11r6@go2.pl> ?roda, 1 lipca 2009 07:15, Robby Workman : > On Sun, 28 Jun 2009 15:08:44 +0200 > > x11r6 at go2.pl wrote: > > New sbopkg-0.30.0alpha1 after "sbopkg -r" as user: > > > > sbopkg: sbopkg must be run by the root user. Exiting. > > > > Is it really necessary? > > Why would you *not* want to run it as root? > What do you hope to accomplish by that? > > Everything that sbopkg does, for the most part, requires root > privileges. Therefore, you can either run it as root, or the > developers can add a lot of potentially complex and otherwise > unnecessary code to it enabling it to run with normal user > privileges. The sky is not falling. > > -RW Right, question of your assumptions, style of engineering... Usualy I build my packages as unprivileged user because it is possible and safe. IMHO rising of permissions for is not necessary. Only some commands like "chown root:root $PKG" need root privileges to avoid random (user) permissions in the package and this is good moment to use "sudo". But why rsync? I was surprised of the new feature in the new version. That's it. -Cheers, -X. From phillip.c.warner at gmail.com Wed Jul 1 13:59:02 2009 From: phillip.c.warner at gmail.com (Phillip Warner) Date: Wed, 1 Jul 2009 08:59:02 -0500 Subject: [sbopkg-users] sbopkg-0.30.0alpha1 root privileges In-Reply-To: <200907011343.46231.x11r6@go2.pl> References: <200906281508.44680.x11r6@go2.pl> <20090701001534.3f62b839@liberty.rlwhome.lan> <200907011343.46231.x11r6@go2.pl> Message-ID: It'd be a mess to try and sudo everything, and that is assuming the user actually is configured correctly for sudo. That really is not KISS. Instead, what I would recommend is to have a completely separate script for regular user use. You could use many of the functions from sbopkg to make it, and could even place it at /usr/bin/sbopkg so that it is transparent to the user that it is a different script.. Of course, for even some mundane features such as rsync to work, the user would have to have write permissions to the destination folder. The code gets really nasty when you try to mix root and non-root. --phillip On Wed, Jul 1, 2009 at 6:43 AM, wrote: > > ?roda, 1 lipca 2009 07:15, Robby Workman : > > On Sun, 28 Jun 2009 15:08:44 +0200 > > > > x11r6 at go2.pl wrote: > > > New sbopkg-0.30.0alpha1 after "sbopkg -r" as user: > > > > > > sbopkg: sbopkg must be run by the root user. Exiting. > > > > > > Is it really necessary? > > > > Why would you *not* want to run it as root? > > What do you hope to accomplish by that? > > > > Everything that sbopkg does, for the most part, requires root > > privileges. Therefore, you can either run it as root, or the > > developers can add a lot of potentially complex and otherwise > > unnecessary code to it enabling it to run with normal user > > privileges. The sky is not falling. > > > > -RW > > Right, question of your assumptions, style of engineering... Usualy I > build my packages as unprivileged user because it is possible and safe. > IMHO rising of permissions for is not necessary. Only some commands like > "chown root:root $PKG" need root privileges to avoid random (user) > permissions in the package and this is good moment to use "sudo". > But why rsync? > I was surprised of the new feature in the new version. That's it. > > -Cheers, -X. > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess at chessgriffin.com Tue Jul 14 22:21:07 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 14 Jul 2009 18:21:07 -0400 Subject: [sbopkg-users] Sbopkg 0.30.0beta released for testing Message-ID: <20090714222105.GA15705@localhost> Thanks to everyone that has tested sbopkg0.30.0alpha1! Based on that feedback, and some further testing of our own, we are now releasing a beta of 0.30.0. In addition to various bug fixes, here are some of enhancements and improvements since the alpha release: * Add option to retry a failed build. Thanks to Zordrak for suggesting this feature. * Add CLEANUP configuration variable, which when set to YES tells sbopkg to delete the extracted sources, and all the associated "residuals" of the build, as soon as the build is finished. Thanks to Marco Bonetti and Gregory Tourte for the suggestion and the nice discussion. * Add a function to delete obsolete (not installed) packages from $OUTPUT. Thanks to alkos333 for the idea. * Reorganize the queue editing functions a bit for a better user interface; 'view queue' now only shows the queue; new 'sort' and 'remove' queue menu items now handle the editing functions; thanks to Pierre Cazenave for the suggestion. Please note that we've set Slackware 13.0 as the 'default' Slackware version even though obviously 13.0 has not been released yet. Just change the setting in sbopkg.conf back to 12.2 and you should be good to do. We're just gettin' prepared. :-) Speaking of sbopkg.conf, there is now one new variable 'CLEANUP' so you may want to check sbopkg.conf.new and migrate the change over to your own config file. As always, please feel free to post feedback on the sbopkg mailing list or in #sbopkg on irc.freenode.net. Here are direct links to a package and source tarball of sbopkg-0.30.0beta: Package: http://sbopkg.googlecode.com/files/sbopkg-0.30.0beta-noarch-1_cng.tgz Source: http://sbopkg.googlecode.com/files/sbopkg-0.30.0beta.tar.gz Thanks for testing! -- 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 mcintosh at cotterochan.co.uk Wed Jul 15 11:21:46 2009 From: mcintosh at cotterochan.co.uk (Steven A. McIntosh) Date: Wed, 15 Jul 2009 12:21:46 +0100 Subject: [sbopkg-users] sbopkg-0.30.0beta changing repository problem Message-ID: <4A5DBBCA.9010003@cotterochan.co.uk> Hi Chess et al. Thanks for the good work. I have found a problem when changing repository via the utilities menu. I changed to SB64/master from SBo/12.2, and rsynced, all worked just fine. I then quit the program to find a tarball that I had already downloaded in order to test a build under SB64/master. On trying to re-start sbopkg I got a repository error. It appears that sbopkg is trying to still load the repository in sbopkg.conf, yet it has a memory of a different repository that was used last. Should the utility menu change of repository not change the sbopkg.conf file also? Hope this is explained OK. samac From chess at chessgriffin.com Wed Jul 15 12:53:11 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 15 Jul 2009 08:53:11 -0400 Subject: [sbopkg-users] sbopkg-0.30.0beta changing repository problem In-Reply-To: <4A5DBBCA.9010003@cotterochan.co.uk> References: <4A5DBBCA.9010003@cotterochan.co.uk> Message-ID: <20090715125311.GA3408@localhost> * Steven A. McIntosh [2009-07-15 12:21:46]: > Hi Chess et al. > > Thanks for the good work. > > I have found a problem when changing repository via the utilities menu. > > I changed to SB64/master from SBo/12.2, and rsynced, all worked just > fine. I then quit the program to find a tarball that I had already > downloaded in order to test a build under SB64/master. On trying to > re-start sbopkg I got a repository error. > > It appears that sbopkg is trying to still load the repository in > sbopkg.conf, yet it has a memory of a different repository that was used > last. > > Should the utility menu change of repository not change the sbopkg.conf > file also? > After changing repositories to the Slamd64 repo, sbopkg asks if you want to save this in the /root/.sbopkg.conf file. If you select "YES" it saves REPO_BRANCH=master in /root/.sbopkg.conf (/root/.sbopkg.conf overrides settings in /etc/sbopkg/sbopkg.conf). However, it should also save REPO_NAME=SB64 in there as well, which is why it's breaking. So, could you try adding REPO_NAME=SB64 to /root/.sbopkg.conf and see if that fixes it? It appears to work here but I'd like to get confirmation. Thanks for the bug report! -- 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 mcintosh at cotterochan.co.uk Wed Jul 15 13:14:29 2009 From: mcintosh at cotterochan.co.uk (Steven A. McIntosh) Date: Wed, 15 Jul 2009 14:14:29 +0100 Subject: [sbopkg-users] sbopkg-0.30.0beta changing repository problem In-Reply-To: <20090715125311.GA3408@localhost> References: <4A5DBBCA.9010003@cotterochan.co.uk> <20090715125311.GA3408@localhost> Message-ID: <4A5DD635.8050504@cotterochan.co.uk> OK it is definitely not adding REPO_NAME=SB64 to /root/.sbopkg.conf, however making the change by hand fixes the problem. When making further changes by the utility menu, these new changes are not written to REPO_NAME either even though the line now exists. Hope this helps. samac Chess Griffin wrote: > * Steven A. McIntosh [2009-07-15 12:21:46]: > >> Hi Chess et al. >> >> Thanks for the good work. >> >> I have found a problem when changing repository via the utilities menu. >> >> I changed to SB64/master from SBo/12.2, and rsynced, all worked just >> fine. I then quit the program to find a tarball that I had already >> downloaded in order to test a build under SB64/master. On trying to >> re-start sbopkg I got a repository error. >> >> It appears that sbopkg is trying to still load the repository in >> sbopkg.conf, yet it has a memory of a different repository that was used >> last. >> >> Should the utility menu change of repository not change the sbopkg.conf >> file also? >> > > After changing repositories to the Slamd64 repo, sbopkg asks if you want > to save this in the /root/.sbopkg.conf file. If you select "YES" it > saves REPO_BRANCH=master in /root/.sbopkg.conf (/root/.sbopkg.conf > overrides settings in /etc/sbopkg/sbopkg.conf). However, it should also > save REPO_NAME=SB64 in there as well, which is why it's breaking. > > So, could you try adding REPO_NAME=SB64 to /root/.sbopkg.conf and see if > that fixes it? It appears to work here but I'd like to get > confirmation. > > Thanks for the bug report! > > > > ------------------------------------------------------------------------ > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users From chess at chessgriffin.com Wed Jul 15 13:41:31 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 15 Jul 2009 09:41:31 -0400 Subject: [sbopkg-users] sbopkg-0.30.0beta changing repository problem In-Reply-To: <4A5DD635.8050504@cotterochan.co.uk> References: <4A5DBBCA.9010003@cotterochan.co.uk> <20090715125311.GA3408@localhost> <4A5DD635.8050504@cotterochan.co.uk> Message-ID: <20090715134131.GA3584@localhost> * Steven A. McIntosh [2009-07-15 14:14:29]: > OK it is definitely not adding REPO_NAME=SB64 to /root/.sbopkg.conf, > however making the change by hand fixes the problem. > > When making further changes by the utility menu, these new changes are > not written to REPO_NAME either even though the line now exists. > > Hope this helps. > > samac > Yeah, it just needs to write REPO_NAME in addition to REPO_BRANCH. I'll make that fix now. Thanks again. -- 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 pwcazenave at gmail.com Wed Jul 22 21:56:37 2009 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Wed, 22 Jul 2009 22:56:37 +0100 Subject: [sbopkg-users] Queue naming dialogue on exit Message-ID: <4A678B15.7060408@gmail.com> Evening all, I've noticed that if you try and exit sbopkg with an unsaved queue, sbopkg prompts you to save it using a preset name (sbopkg-autosave-0). If you delete this name and then select OK, sbopkg exits. Perhaps if it offered a warning saying "Your queue will be lost" with an option to return and enter a name or continue exiting, or something along those lines, that'd be helpful. Just a thought, Pierre From jsunx1 at bellsouth.net Wed Jul 22 22:33:31 2009 From: jsunx1 at bellsouth.net (slakmagik) Date: Wed, 22 Jul 2009 18:33:31 -0400 Subject: [sbopkg-users] Queue naming dialogue on exit In-Reply-To: <4A678B15.7060408@gmail.com> References: <4A678B15.7060408@gmail.com> Message-ID: <20090722223331.GA27509@surfandslam> On 2009-07-22 (Wed) 22:56:37 [+0100], Pierre Cazenave wrote: > Evening all, > > I've noticed that if you try and exit sbopkg with an unsaved queue, > sbopkg prompts you to save it using a preset name (sbopkg-autosave-0). > If you delete this name and then select OK, sbopkg exits. > > Perhaps if it offered a warning saying "Your queue will be lost" with an > option to return and enter a name or continue exiting, or something > along those lines, that'd be helpful. > > Just a thought, > And a good one. I think it's a very simple change. If you're using the svn version, then change l.1668 from 'break' to 'continue'. I think it's l.1313 for 0.27.4. This should just cause it to present the dialog box again. If you really mean to exit then, you can hit cancel or escape or whatever. If that doesn't get the job done, we'll try something else, but I agree it shouldn't just exit. From chess at chessgriffin.com Wed Jul 22 22:56:35 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 22 Jul 2009 18:56:35 -0400 Subject: [sbopkg-users] Queue naming dialogue on exit In-Reply-To: <20090722223331.GA27509@surfandslam> References: <4A678B15.7060408@gmail.com> <20090722223331.GA27509@surfandslam> Message-ID: <20090722225635.GA3972@localhost> * slakmagik [2009-07-22 18:33:31]: > On 2009-07-22 (Wed) 22:56:37 [+0100], Pierre Cazenave wrote: > > Evening all, > > > > I've noticed that if you try and exit sbopkg with an unsaved queue, > > sbopkg prompts you to save it using a preset name (sbopkg-autosave-0). > > If you delete this name and then select OK, sbopkg exits. > > > > Perhaps if it offered a warning saying "Your queue will be lost" with an > > option to return and enter a name or continue exiting, or something > > along those lines, that'd be helpful. > > > > Just a thought, > > > > And a good one. I think it's a very simple change. If you're using the > svn version, then change l.1668 from 'break' to 'continue'. I think it's > l.1313 for 0.27.4. > > This should just cause it to present the dialog box again. If you really > mean to exit then, you can hit cancel or escape or whatever. > > If that doesn't get the job done, we'll try something else, but I agree > it shouldn't just exit. I guess I'm not understanding the problem. If there is a new queue, the dialog box prompts the user to save and fills in a preset name. If the user does not want to save, the user can tab over to 'Cancel' and sbopkg will quit. There is no need to delete the name. Or, if the user erases the name and presses 'Ok' then that is the same effect as pressing 'Cancel' -- because no name is given. Or, the user can keep the preset name or change the name and press 'Ok' in which it will save. -- 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 timp at timp.com.au Wed Jul 22 23:12:40 2009 From: timp at timp.com.au (Timothy Pollard) Date: Thu, 23 Jul 2009 09:12:40 +1000 Subject: [sbopkg-users] Queue naming dialogue on exit In-Reply-To: <20090722225635.GA3972@localhost> References: <4A678B15.7060408@gmail.com> <20090722223331.GA27509@surfandslam> <20090722225635.GA3972@localhost> Message-ID: <20090723091240.7978f8af@shammah.timp.com.au> On Wed, 22 Jul 2009 18:56:35 -0400 Chess Griffin wrote: > ... > > I guess I'm not understanding the problem. If there is a new queue, the > dialog box prompts the user to save and fills in a preset name. If the > user does not want to save, the user can tab over to 'Cancel' and sbopkg > will quit. There is no need to delete the name. Or, if the user erases > the name and presses 'Ok' then that is the same effect as pressing > 'Cancel' -- because no name is given. Or, the user can keep the preset > name or change the name and press 'Ok' in which it will save. > My understanding is that they don't think erasing the name and pressing OK should have the same result as pressing Cancel. It should assume that it was an error and ask the user to correct it. Personally I don't mind either way, though their suggestion is probably the more common way of doing it. -- TimP [http://blog.timp.com.au] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From jsunx1 at bellsouth.net Wed Jul 22 23:21:14 2009 From: jsunx1 at bellsouth.net (slakmagik) Date: Wed, 22 Jul 2009 19:21:14 -0400 Subject: [sbopkg-users] Queue naming dialogue on exit In-Reply-To: <20090722225635.GA3972@localhost> References: <4A678B15.7060408@gmail.com> <20090722223331.GA27509@surfandslam> <20090722225635.GA3972@localhost> Message-ID: <20090722232114.GA11835@surfandslam> On 2009-07-22 (Wed) 18:56:35 [-0400], Chess Griffin wrote: > * slakmagik [2009-07-22 18:33:31]: > > > On 2009-07-22 (Wed) 22:56:37 [+0100], Pierre Cazenave wrote: > > > Evening all, > > > > > > I've noticed that if you try and exit sbopkg with an unsaved queue, > > > sbopkg prompts you to save it using a preset name (sbopkg-autosave-0). > > > If you delete this name and then select OK, sbopkg exits. > > > > > > Perhaps if it offered a warning saying "Your queue will be lost" with an > > > option to return and enter a name or continue exiting, or something > > > along those lines, that'd be helpful. > > > > > > Just a thought, > > > > > > > And a good one. I think it's a very simple change. If you're using the > > svn version, then change l.1668 from 'break' to 'continue'. I think it's > > l.1313 for 0.27.4. > > > > This should just cause it to present the dialog box again. If you really > > mean to exit then, you can hit cancel or escape or whatever. > > > > If that doesn't get the job done, we'll try something else, but I agree > > it shouldn't just exit. > > I guess I'm not understanding the problem. If there is a new queue, the > dialog box prompts the user to save and fills in a preset name. If the > user does not want to save, the user can tab over to 'Cancel' and sbopkg > will quit. There is no need to delete the name. Or, if the user erases > the name and presses 'Ok' then that is the same effect as pressing > 'Cancel' -- because no name is given. Or, the user can keep the preset > name or change the name and press 'Ok' in which it will save. > I understood him to be saying that, if the user clears the name and then accidentally hits okay (or hits okay without realizing the consequences) that it will exit and the user will lose their queue. IOW, saying "Okay I want to save a queue with no filename" makes no sense but the UI allows it. And what sbopkg does now in that event is exit when that's probably not what the user wanted. It could just re-prompt for a filename or allow the user to hit "Cancel" if they mean to cancel. And that's what looping back around to the dialog on an empty string will do. From jsunx1 at bellsouth.net Wed Jul 22 23:24:29 2009 From: jsunx1 at bellsouth.net (slakmagik) Date: Wed, 22 Jul 2009 19:24:29 -0400 Subject: [sbopkg-users] Queue naming dialogue on exit In-Reply-To: <20090723091240.7978f8af@shammah.timp.com.au> References: <4A678B15.7060408@gmail.com> <20090722223331.GA27509@surfandslam> <20090722225635.GA3972@localhost> <20090723091240.7978f8af@shammah.timp.com.au> Message-ID: <20090722232429.GB11835@surfandslam> On 2009-07-23 (Thu) 09:12:40 [+1000], Timothy Pollard wrote: > On Wed, 22 Jul 2009 18:56:35 -0400 > Chess Griffin wrote: > > ... > > > > I guess I'm not understanding the problem. If there is a new queue, the > > dialog box prompts the user to save and fills in a preset name. If the > > user does not want to save, the user can tab over to 'Cancel' and sbopkg > > will quit. There is no need to delete the name. Or, if the user erases > > the name and presses 'Ok' then that is the same effect as pressing > > 'Cancel' -- because no name is given. Or, the user can keep the preset > > name or change the name and press 'Ok' in which it will save. > > > > My understanding is that they don't think erasing the name and pressing OK > should have the same result as pressing Cancel. It should assume that it was an > error and ask the user to correct it. Personally I don't mind either way, > though their suggestion is probably the more common way of doing it. > Sorry, my mail retrieval interval is slow and I didn't see your mail in time before sending my own but, yes, exactly. :) From chess at chessgriffin.com Wed Jul 22 23:54:10 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 22 Jul 2009 19:54:10 -0400 Subject: [sbopkg-users] Queue naming dialogue on exit In-Reply-To: <20090722232429.GB11835@surfandslam> References: <4A678B15.7060408@gmail.com> <20090722223331.GA27509@surfandslam> <20090722225635.GA3972@localhost> <20090723091240.7978f8af@shammah.timp.com.au> <20090722232429.GB11835@surfandslam> Message-ID: <20090722235410.GA11553@localhost> * slakmagik [2009-07-22 19:24:29]: > On 2009-07-23 (Thu) 09:12:40 [+1000], Timothy Pollard wrote: > > > My understanding is that they don't think erasing the name and > > pressing OK should have the same result as pressing Cancel. It > > should assume that it was an error and ask the user to correct it. > > Personally I don't mind either way, though their suggestion is > > probably the more common way of doing it. > > > > Sorry, my mail retrieval interval is slow and I didn't see your mail > in time before sending my own but, yes, exactly. :) Ah, okay, now I see. I really am getting old and dense. Or maybe I was always dense so I'm just getting old. :-) Anyway, it sounds like a good thing to fix. -- 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 pwcazenave at gmail.com Thu Jul 23 08:31:27 2009 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Thu, 23 Jul 2009 08:31:27 +0000 Subject: [sbopkg-users] Queue naming dialogue on exit In-Reply-To: <20090722232114.GA11835@surfandslam> References: <4A678B15.7060408@gmail.com> <20090722223331.GA27509@surfandslam> <20090722225635.GA3972@localhost> <20090722232114.GA11835@surfandslam> Message-ID: <4A681FDF.90007@gmail.com> slakmagik wrote: > On 2009-07-22 (Wed) 18:56:35 [-0400], Chess Griffin wrote: > > * slakmagik [2009-07-22 18:33:31]: > > > >> On 2009-07-22 (Wed) 22:56:37 [+0100], Pierre Cazenave wrote: > >>> Evening all, > >>> > >>> I've noticed that if you try and exit sbopkg with an unsaved > >>> queue, sbopkg prompts you to save it using a preset name > >>> (sbopkg-autosave-0). If you delete this name and then select > >>> OK, sbopkg exits. > >>> > >>> Perhaps if it offered a warning saying "Your queue will be > >>> lost" with an option to return and enter a name or continue > >>> exiting, or something along those lines, that'd be helpful. > >>> > >>> Just a thought, > >>> > >> And a good one. I think it's a very simple change. If you're > >> using the svn version, then change l.1668 from 'break' to > >> 'continue'. I think it's l.1313 for 0.27.4. > >> > >> This should just cause it to present the dialog box again. If you > >> really mean to exit then, you can hit cancel or escape or > >> whatever. > >> > >> If that doesn't get the job done, we'll try something else, but I > >> agree it shouldn't just exit. > > I guess I'm not understanding the problem. If there is a new > > queue, the dialog box prompts the user to save and fills in a > > preset name. If the user does not want to save, the user can tab > > over to 'Cancel' and sbopkg will quit. There is no need to delete > > the name. Or, if the user erases the name and presses 'Ok' then > > that is the same effect as pressing 'Cancel' -- because no name is > > given. Or, the user can keep the preset name or change the name > > and press 'Ok' in which it will save. > > > > I understood him to be saying that, if the user clears the name and > then accidentally hits okay (or hits okay without realizing the > consequences) that it will exit and the user will lose their queue. > IOW, saying "Okay I want to save a queue with no filename" makes no > sense but the UI allows it. And what sbopkg does now in that event is > exit when that's probably not what the user wanted. It could just > re-prompt for a filename or allow the user to hit "Cancel" if they > mean to cancel. And that's what looping back around to the dialog on > an empty string will do. > _______________________________________________ sbopkg-users mailing > list sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users I wrote that last night, and perhaps my English wasn't as descriptive as it could have been, but in essence, I've been understood. slakmagik summarised it well: > IOW, saying "Okay I want to save a queue with no filename" makes no > sense If it's as simple as changing break to a continue, I think that'll do it. If the user (i.e. me) clears the name and then hits enter, then it'd be nice for them to be given a second chance to save their queue, as losing a really long and complicated queue is a nuisance. This is especially the case if you're building a queue file for some application requiring many dependencies. From stormtracknole at gmail.com Thu Jul 30 00:08:35 2009 From: stormtracknole at gmail.com (stormtracknole) Date: Wed, 29 Jul 2009 19:08:35 -0500 Subject: [sbopkg-users] Search window on sbopkg beta Message-ID: List, I've noticed in the alpha and now with the beta version something that is not in the official version. By default, when you do a search, inside the search window, it comes up with two commas (,,). If you try to do a search without removing the commas, your search will not return any results. However, removing the commas, you'll get successful results. My question is, are the two commas supposed to be there by default? It's no big deal to remove them though, but being that they are kind of small, users may not realize that they are there and thus not allowing the search feature to function properly. -stn -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess at chessgriffin.com Thu Jul 30 00:49:50 2009 From: chess at chessgriffin.com (Chess Griffin) Date: Wed, 29 Jul 2009 20:49:50 -0400 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: Message-ID: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> On Wed, Jul 29, 2009 at 8:08 PM, stormtracknole wrote: > List, > > I've noticed in the alpha and now with the beta version something that is > not in the official version.? By default, when you do a search, inside the > search window, it comes up with two commas (,,).? If you try to do a search > without removing the commas, your search will not return any results. > However, removing the commas, you'll get successful results.? My question > is, are the two commas supposed to be there by default?? It's no big deal to > remove them though, but being that they are kind of small, users may not > realize that they are there and thus not allowing the search feature to > function properly. > Hmm... that is odd. I just tested it (the beta) and there are no commas in the search field. Are you by chance using sbopkg over ssh or in a screen session? Sometimes, funky things can happen with your $TERM when using ssh and/or screen that causes odd behavior like that. -- Chess Griffin From stormtracknole at gmail.com Thu Jul 30 01:06:05 2009 From: stormtracknole at gmail.com (stormtracknole) Date: Wed, 29 Jul 2009 20:06:05 -0500 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> Message-ID: You are onto something here since I'm using both an ssh and screen session. I terminated the screen session, and ran sbopkg again and I did not get the commas. I could've sworn that I had the same problem without the screen session, but now I'm not sure. I'll try it again when I get home from work later. I should have thought about screen being the culprit since this is not the first time that screen has messed up my enviroment. Thanks Chess for taking time to look into this! -stn On Wed, Jul 29, 2009 at 7:49 PM, Chess Griffin wrote: > On Wed, Jul 29, 2009 at 8:08 PM, stormtracknole > wrote: > > List, > > > > I've noticed in the alpha and now with the beta version something that is > > not in the official version. By default, when you do a search, inside > the > > search window, it comes up with two commas (,,). If you try to do a > search > > without removing the commas, your search will not return any results. > > However, removing the commas, you'll get successful results. My question > > is, are the two commas supposed to be there by default? It's no big deal > to > > remove them though, but being that they are kind of small, users may not > > realize that they are there and thus not allowing the search feature to > > function properly. > > > > Hmm... that is odd. I just tested it (the beta) and there are no > commas in the search field. Are you by chance using sbopkg over ssh > or in a screen session? Sometimes, funky things can happen with your > $TERM when using ssh and/or screen that causes odd behavior like that. > > -- > Chess Griffin > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pwcazenave at gmail.com Thu Jul 30 08:19:28 2009 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Thu, 30 Jul 2009 08:19:28 +0000 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> Message-ID: <4A715790.3080801@gmail.com> If it's any help, I get question marks in the search field when using sbopkg over ssh in a screen session. I just put it down to one of those screen things. Pierre Chess Griffin wrote: > On Wed, Jul 29, 2009 at 8:08 PM, > stormtracknole wrote: > > List, > > > > I've noticed in the alpha and now with the beta version something > > that is not in the official version. By default, when you do a > > search, inside the search window, it comes up with two commas (,,). > > If you try to do a search without removing the commas, your search > > will not return any results. However, removing the commas, you'll > > get successful results. My question is, are the two commas > > supposed to be there by default? It's no big deal to remove them > > though, but being that they are kind of small, users may not > > realize that they are there and thus not allowing the search > > feature to function properly. > > > > Hmm... that is odd. I just tested it (the beta) and there are no > commas in the search field. Are you by chance using sbopkg over ssh > or in a screen session? Sometimes, funky things can happen with your > $TERM when using ssh and/or screen that causes odd behavior like > that. > From mauro.giachero at gmail.com Thu Jul 30 11:14:42 2009 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Thu, 30 Jul 2009 13:14:42 +0200 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: <4A715790.3080801@gmail.com> References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> <4A715790.3080801@gmail.com> Message-ID: Ah, the joys of computer programming... The extra chars appear from within screen sessions. SSH isn't required. We're facing another dialog bug. Try this in a screen session inside Konsole: dialog --title "foo" --inputbox "bar" 8 20 If you resize the Konsole window, the characters appear. Now, the resize event is notified to the application with a SIGWINCH, which is exactly the signal we send in the background to dialog in screen sessions to force a repaint (to work around another dialog bug which sometimes prevented the dialogs from being drawn). I have no idea on how we can work around both problems. On the plus side (sort of), I've been unable to reproduce the issue on S12.2 in qemu. Any idea on when the problem started? -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From pwcazenave at gmail.com Thu Jul 30 11:29:49 2009 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Thu, 30 Jul 2009 11:29:49 +0000 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> <4A715790.3080801@gmail.com> Message-ID: <4A71842D.4030804@gmail.com> Mauro Giachero wrote: > Ah, the joys of computer programming... > > The extra chars appear from within screen sessions. SSH isn't > required. > > We're facing another dialog bug. Try this in a screen session inside > Konsole: dialog --title "foo" --inputbox "bar" 8 20 If you resize the > Konsole window, the characters appear. Now, the resize event is > notified to the application with a SIGWINCH, which is exactly the > signal we send in the background to dialog in screen sessions to > force a repaint (to work around another dialog bug which sometimes > prevented the dialogs from being drawn). > > I have no idea on how we can work around both problems. > > On the plus side (sort of), I've been unable to reproduce the issue > on S12.2 in qemu. Any idea on when the problem started? > > > ------------------------- > > _______________________________________________ sbopkg-users mailing > list sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users Aren't these upstream bugs? If they occur only in screen, then surely the problem is either in dialog or screen? I'd be inclined to just do: if [ $TERM == "screen" ]; then dialog --msgbox "Using sbopkg within screen causes display problems." 7 60 fi I know this doesn't help fix anything, but at least people will be prepared for the glitches! Pierre From chess.griffin at gmail.com Thu Jul 30 12:52:52 2009 From: chess.griffin at gmail.com (Chess Griffin) Date: Thu, 30 Jul 2009 08:52:52 -0400 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: <4A71842D.4030804@gmail.com> References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> <4A715790.3080801@gmail.com> <4A71842D.4030804@gmail.com> Message-ID: On Thu, Jul 30, 2009 at 7:29 AM, Pierre Cazenave wrote: > Mauro Giachero wrote: >> >> ?Ah, the joys of computer programming... >> >> ?The extra chars appear from within screen sessions. SSH isn't >> ?required. >> >> ?We're facing another dialog bug. Try this in a screen session inside >> ?Konsole: dialog --title "foo" --inputbox "bar" 8 20 If you resize the >> ?Konsole window, the characters appear. Now, the resize event is >> ?notified to the application with a SIGWINCH, which is exactly the >> ?signal we send in the background to dialog in screen sessions to >> ?force a repaint (to work around another dialog bug which sometimes >> ?prevented the dialogs from being drawn). >> >> ?I have no idea on how we can work around both problems. >> >> ?On the plus side (sort of), I've been unable to reproduce the issue >> ?on S12.2 in qemu. Any idea on when the problem started? >> >> >> ?------------------------- >> >> ?_______________________________________________ sbopkg-users mailing >> ?list sbopkg-users at sbopkg.org >> ?http://sbopkg.org/mailman/listinfo/sbopkg-users > > Aren't these upstream bugs? If they occur only in screen, then surely the > problem is either in dialog or screen? > > I'd be inclined to just do: > > if [ $TERM == "screen" ]; then > ? dialog --msgbox "Using sbopkg within screen causes display problems." 7 60 > fi > > I know this doesn't help fix anything, but at least people will be prepared > for the glitches! > > Pierre > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > Does starting sbopkg as follows prevent the problem for anyone? It seems to work here: TERM=xterm-color && sbopkg -- Chess Griffin From chess.griffin at gmail.com Thu Jul 30 12:54:46 2009 From: chess.griffin at gmail.com (Chess Griffin) Date: Thu, 30 Jul 2009 08:54:46 -0400 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> <4A715790.3080801@gmail.com> <4A71842D.4030804@gmail.com> Message-ID: On Thu, Jul 30, 2009 at 8:52 AM, Chess Griffin wrote: > Does starting sbopkg as follows prevent the problem for anyone? ?It > seems to work here: > > TERM=xterm-color && sbopkg > That is, during a GNU screen session. Start screen, and then run sbopkg with the above command seem to solve the problem here. -- Chess Griffin From mauro.giachero at gmail.com Thu Jul 30 15:02:37 2009 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Thu, 30 Jul 2009 17:02:37 +0200 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> <4A715790.3080801@gmail.com> <4A71842D.4030804@gmail.com> Message-ID: On Thu, Jul 30, 2009 at 2:54 PM, Chess Griffin wrote: > On Thu, Jul 30, 2009 at 8:52 AM, Chess Griffin > wrote: > > Does starting sbopkg as follows prevent the problem for anyone? It > > seems to work here: > > > > TERM=xterm-color && sbopkg > > > > That is, during a GNU screen session. Start screen, and then run > sbopkg with the above command seem to solve the problem here. > The problem with the signal handling remains, but since the refresh workaround doesn't trigger for TERM=xterm-color you have to explicitly resize the window. On the other hand, I've been unable to reproduce the old refresh problem on -current, and exporting TERM=xterm-color in a screen session seems to fix it on S12.2 in a screen session and in aterm (TERM=rxvt). Even though this is a very hacky way to proceed, maybe we could replace the current workaround with a simple 'export TERM=xterm-color'? -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess.griffin at gmail.com Thu Jul 30 15:15:29 2009 From: chess.griffin at gmail.com (Chess Griffin) Date: Thu, 30 Jul 2009 11:15:29 -0400 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> <4A715790.3080801@gmail.com> <4A71842D.4030804@gmail.com> Message-ID: On Thu, Jul 30, 2009 at 11:02 AM, Mauro Giachero wrote: > > The problem with the signal handling remains, but since the refresh > workaround doesn't trigger for TERM=xterm-color you have to explicitly > resize the window. > On the other hand, I've been unable to reproduce the old refresh problem on > -current, and exporting TERM=xterm-color in a screen session seems to fix it > on S12.2 in a screen session and in aterm (TERM=rxvt). > > Even though this is a very hacky way to proceed, maybe we could replace the > current workaround with a simple 'export TERM=xterm-color'? > TBH, I'm not sure we necessarily need to try to solve all of these problems in sbopkg. If the GNU Screen extra characters issue bothers someone, they could work around it by putting something like the following untested kludge in their .bashrc: case "$TERM" in screen*) alias sbopkg="TERM=xterm-color sbopkg" ;; esac However, the signal handling issue might be a different animal that cannot easily be worked around like that. I just have not looked at it yet. -- Chess Griffin From mauro.giachero at gmail.com Thu Jul 30 15:27:51 2009 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Thu, 30 Jul 2009 17:27:51 +0200 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> <4A715790.3080801@gmail.com> <4A71842D.4030804@gmail.com> Message-ID: On Thu, Jul 30, 2009 at 5:15 PM, Chess Griffin wrote: > TBH, I'm not sure we necessarily need to try to solve all of these > problems in sbopkg. If the GNU Screen extra characters issue bothers > someone, they could work around it by putting something like the > following untested kludge in their .bashrc: > > case "$TERM" in > screen*) alias sbopkg="TERM=xterm-color sbopkg" ;; > esac True. Maybe we should simply document the issue somewhere. However, the current workaround is problematic on -current, so it should be removed. While at it, if the export hack works, we can simply put it in. The next time a terminal issue arises, we scrap the whole idea of working around terminal issues and start documenting the known problems. However, the signal handling issue might be a different animal that > cannot easily be worked around like that. I just have not looked at > it yet. This is far outside the sbopkg scope, though. -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From stormtracknole at gmail.com Thu Jul 30 16:53:55 2009 From: stormtracknole at gmail.com (stormtracknole) Date: Thu, 30 Jul 2009 11:53:55 -0500 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: <8682df160907291749m7f6a5835i52de224ac7e30902@mail.gmail.com> <4A715790.3080801@gmail.com> <4A71842D.4030804@gmail.com> Message-ID: Sorry about that guys! Blame it on the long work hours and lack of sleep. The issue only shows up when using sbopkg in a screen session for me. Running it in a local session or through ssh (without using session) does not give me any problems at all. Thanks guys for looking into this. Great job to everyone that maintain and works with this project. Excellent work! :^) -stn On Thu, Jul 30, 2009 at 10:27 AM, Mauro Giachero wrote: > On Thu, Jul 30, 2009 at 5:15 PM, Chess Griffin wrote: > >> TBH, I'm not sure we necessarily need to try to solve all of these >> problems in sbopkg. If the GNU Screen extra characters issue bothers >> someone, they could work around it by putting something like the >> following untested kludge in their .bashrc: >> >> case "$TERM" in >> screen*) alias sbopkg="TERM=xterm-color sbopkg" ;; >> esac > > > True. Maybe we should simply document the issue somewhere. > However, the current workaround is problematic on -current, so it should be > removed. While at it, if the export hack works, we can simply put it in. > The next time a terminal issue arises, we scrap the whole idea of working > around terminal issues and start documenting the known problems. > > However, the signal handling issue might be a different animal that >> cannot easily be worked around like that. I just have not looked at >> it yet. > > > This is far outside the sbopkg scope, though. > > -- > Mauro Giachero > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess.griffin at gmail.com Thu Jul 30 17:04:43 2009 From: chess.griffin at gmail.com (Chess Griffin) Date: Thu, 30 Jul 2009 13:04:43 -0400 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: <4A715790.3080801@gmail.com> <4A71842D.4030804@gmail.com> Message-ID: Can you test the xterm-color workaround in Screen and see if that eliminates the issue? -- Chess Griffin Sent from my Android phone On Jul 30, 2009 12:54 PM, "stormtracknole" wrote: Sorry about that guys! Blame it on the long work hours and lack of sleep. The issue only shows up when using sbopkg in a screen session for me. Running it in a local session or through ssh (without using session) does not give me any problems at all. Thanks guys for looking into this. Great job to everyone that maintain and works with this project. Excellent work! :^) -stn On Thu, Jul 30, 2009 at 10:27 AM, Mauro Giachero wrote: > > > On Thu, Jul 30, 2009 at 5:15 PM, Chess Griffin < > chess.griffin at gmail.com> wrote: >> >> TBH, I'm n... > _______________________________________________ > > > sbopkg-users mailing list > sbopkg-users at sbopkg.org > > http://sbopkg.org/mailman/listinfo/sbopkg-u... > _______________________________________________ sbopkg-users mailing list sbopkg-users at sbopkg.org http://sbopkg.org/mailman/listinfo/sbopkg-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From stormtracknole at gmail.com Fri Jul 31 00:56:54 2009 From: stormtracknole at gmail.com (stormtracknole) Date: Thu, 30 Jul 2009 19:56:54 -0500 Subject: [sbopkg-users] Search window on sbopkg beta In-Reply-To: References: <4A71842D.4030804@gmail.com> Message-ID: Chess, Sorry for the delay! Been a little busy the last few days. Yes, I can confirm that the TERM=xterm-color works. I also found another workaround when using screen by issuing the following command: screen -T xterm-color Thanks again for looking into this. This should also fix any other problems when using screen. -stn On Thu, Jul 30, 2009 at 12:04 PM, Chess Griffin wrote: > Can you test the xterm-color workaround in Screen and see if that > eliminates the issue? > > -- > Chess Griffin > Sent from my Android phone > > On Jul 30, 2009 12:54 PM, "stormtracknole" > wrote: > > Sorry about that guys! Blame it on the long work hours and lack of sleep. > The issue only shows up when using sbopkg in a screen session for me. > Running it in a local session or through ssh (without using session) does > not give me any problems at all. Thanks guys for looking into this. Great > job to everyone that maintain and works with this project. Excellent work! > :^) > > -stn > > On Thu, Jul 30, 2009 at 10:27 AM, Mauro Giachero > wrote: > >> > > On Thu, Jul 30, 2009 at 5:15 PM, Chess Griffin < >> chess.griffin at gmail.com> wrote: >> >> TBH, I'm n... >> _______________________________________________ >> >> > sbopkg-users mailing list > sbopkg-users at sbopkg.org > >> http://sbopkg.org/mailman/listinfo/sbopkg-u... >> > > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: