From bkirkp at gmail.com Wed May 5 19:58:22 2010 From: bkirkp at gmail.com (B Kirkpatrick) Date: Wed, 05 May 2010 14:58:22 -0500 Subject: [sbopkg-users] sbopkg slow to start using git repository Message-ID: <4BE1CDDE.2090009@gmail.com> I have recently installed -current on my laptop. The first external package I installed was sbopkg. I modified the following lines in my /etc/sbopkg/sbopkg.conf: REPO_ROOT=${REPO_ROOT:-/mnt/spock/sbopkg} QUEUEDIR=${QUEUEDIR:-/mnt/spock/sbopkg/sbopkg-slackware-queues} SRCDIR=${SRCDIR:-/mnt/spock/sbopkg/src} I added the file /etc/sbopkg/repos.d/30-SBo-git.repo with: # Repo Branch Description Tag Tool Link CheckGPG SBo-git current "Unofficial repository for -current" _SBo git git://github.com/Ponce/SBo-git.git at current "" At this point, I started sbopkg for the first time. I always use the ncurses interface. I immediately selected Utilities, then Repository, then selected the "current (SBo-git)" repository. I then went back to the main menu & chose "Sync". The repository was then populated & I was able to use it. By this time, too, the file /root/.sbopkg.conf comtained: REPO_NAME=SBo-git REPO_BRANCH=current The problem that I am having is that after sbopkg has been closed a while, then is opened, I get the following: # sbopkg Checking out files: 15% (2171/14180) It then takes several minutes to check out the 14180 files, before it presents me with the menu. If I switch to the 13.0 (SBo) repository, all works well, the menu comes up quickly. If, when using the current repository, I close the program, then open it within a few minutes, the menu comes up quicker, without the "Checking out files", but not as quickly as when using the 13.0 repository. Maybe (ir)relevant: "/mnt/spock/sbopkg" (my REPO_ROOT) is on a server, which shares the repositories via NFS with several machines. Is there some way I can speed up the loading of the program? Regards, Bill Kirkpatrick TSquaredF K5TTF From mauro.giachero at gmail.com Thu May 6 10:27:58 2010 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Thu, 6 May 2010 12:27:58 +0200 Subject: [sbopkg-users] sbopkg slow to start using git repository In-Reply-To: <4BE1CDDE.2090009@gmail.com> References: <4BE1CDDE.2090009@gmail.com> Message-ID: Sbopkg simply issues a 'git pull' command, so the slowness you experience has nothing to do with sbopkg itself. You may want to try using a local folder instead of an NFS share. Also, I vaguely remember the existence of a way to download only a single revision instead of the whole project history (can't find it right now, sorry). You could try to investigate in that direction and hack the git_command() function. -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauro.giachero at gmail.com Thu May 6 11:31:57 2010 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Thu, 6 May 2010 13:31:57 +0200 Subject: [sbopkg-users] sbopkg slow to start using git repository In-Reply-To: References: <4BE1CDDE.2090009@gmail.com> Message-ID: You may also want to try the HTTP protocol [ http://github.com/Ponce/SBo-git.git] (on some networks I had problems with the GIT protocol). -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From bkirkp at gmail.com Thu May 6 17:00:16 2010 From: bkirkp at gmail.com (Bill Kirkpatrick) Date: Thu, 6 May 2010 12:00:16 -0500 Subject: [sbopkg-users] sbopkg slow to start using git repository In-Reply-To: References: <4BE1CDDE.2090009@gmail.com> Message-ID: I've solved my problem (temporarily, I hope) by modifying /etc/sbopkg/repos.d/30-SBo-git.repo to: # Repo Branch Description Tag Tool Link CheckGPG #SBo-git current "Unofficial repository for -current" _SBo git git:// github.com/Ponce/SBo-git.git at current "" SBo-git current "Unofficial repository for -current" _SBo "" "" "" I am, of course, used to the rsync repository from SBo, so I made the mistake of thinking that the git repository would work like the rsync one, & only update when I used the sync command. My current assumption is that the git repository is updated every time sbopkg is started. My next assumption is that to update the repository, I would have to remove the "#" from line 2 above, add it to line 3 & start sbopkg. Is that correct? I really don't need it to sync every time I start the program Regards, Bill On Thu, May 6, 2010 at 5:27 AM, Mauro Giachero wrote: > Sbopkg simply issues a 'git pull' command, so the slowness you experience > has nothing to do with sbopkg itself. > > You may want to try using a local folder instead of an NFS share. Also, I > vaguely remember the existence of a way to download only a single revision > instead of the whole project history (can't find it right now, sorry). You > could try to investigate in that direction and hack the git_command() > function. > > -- > 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 at chessgriffin.com Thu May 6 17:58:50 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 6 May 2010 13:58:50 -0400 Subject: [sbopkg-users] sbopkg slow to start using git repository In-Reply-To: References: <4BE1CDDE.2090009@gmail.com> Message-ID: <20100506175850.GA2975@localhost> * Bill Kirkpatrick [2010-05-06 12:00:16]: > I've solved my problem (temporarily, I hope) by modifying > /etc/sbopkg/repos.d/30-SBo-git.repo to: > > # Repo Branch Description Tag Tool Link CheckGPG > #SBo-git current "Unofficial repository for -current" _SBo git git:// > github.com/Ponce/SBo-git.git at current "" > SBo-git current "Unofficial repository for -current" _SBo "" "" "" > > I am, of course, used to the rsync repository from SBo, so I made the > mistake of thinking that the git repository would work like the rsync > one, & only update when I used the sync command. My current assumption > is that the git repository is updated every time sbopkg is started. My > next assumption is that to update the repository, I would have to > remove the "#" from line 2 above, add it to line 3 & start sbopkg. Is > that correct? I really don't need it to sync every time I start the > program > Regards, > Bill > Hmm, using a git repo /should/ be just like the SBo rsync repo, meaning that it only syncs when you manuualy do so from the menu. It should not sync automatically every time you start sbopkg. I'll try and test this repo soon and see if I get a similar result. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From chess at chessgriffin.com Fri May 7 04:11:55 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 7 May 2010 00:11:55 -0400 Subject: [sbopkg-users] sbopkg slow to start using git repository In-Reply-To: <20100506175850.GA2975@localhost> References: <4BE1CDDE.2090009@gmail.com> <20100506175850.GA2975@localhost> Message-ID: <20100507041155.GA4859@localhost> * Chess Griffin [2010-05-06 13:58:50]: > * Bill Kirkpatrick [2010-05-06 12:00:16]: > > > I've solved my problem (temporarily, I hope) by modifying > > /etc/sbopkg/repos.d/30-SBo-git.repo to: > > > > # Repo Branch Description Tag Tool Link CheckGPG > > #SBo-git current "Unofficial repository for -current" _SBo git git:// > > github.com/Ponce/SBo-git.git at current "" > > SBo-git current "Unofficial repository for -current" _SBo "" "" "" > > > > I am, of course, used to the rsync repository from SBo, so I made the > > mistake of thinking that the git repository would work like the rsync > > one, & only update when I used the sync command. My current assumption > > is that the git repository is updated every time sbopkg is started. My > > next assumption is that to update the repository, I would have to > > remove the "#" from line 2 above, add it to line 3 & start sbopkg. Is > > that correct? I really don't need it to sync every time I start the > > program > > Regards, > > Bill > > > > Hmm, using a git repo /should/ be just like the SBo rsync repo, meaning > that it only syncs when you manuualy do so from the menu. It should not > sync automatically every time you start sbopkg. I'll try and test this > repo soon and see if I get a similar result. > Bill, I tested this out using the SBo-git repository and did not notice sbopkg syncing automatically upon start. Everything seemed to be working as it should. I am not sure why you are seeing that behavior. :/ -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From bkirkp at gmail.com Fri May 7 15:05:23 2010 From: bkirkp at gmail.com (B Kirkpatrick) Date: Fri, 07 May 2010 10:05:23 -0500 Subject: [sbopkg-users] sbopkg slow to start using git repository In-Reply-To: <20100507041155.GA4859@localhost> References: <4BE1CDDE.2090009@gmail.com> <20100506175850.GA2975@localhost> <20100507041155.GA4859@localhost> Message-ID: <4BE42C33.2030909@gmail.com> On 05/06/2010 11:11 PM, Chess Griffin wrote: > * Chess Griffin [2010-05-06 13:58:50]: > > >> * Bill Kirkpatrick [2010-05-06 12:00:16]: >> >> >>> I've solved my problem (temporarily, I hope) by modifying >>> /etc/sbopkg/repos.d/30-SBo-git.repo to: >>> >>> # Repo Branch Description Tag Tool Link CheckGPG >>> #SBo-git current "Unofficial repository for -current" _SBo git git:// >>> github.com/Ponce/SBo-git.git at current "" >>> SBo-git current "Unofficial repository for -current" _SBo "" "" "" >>> >>> I am, of course, used to the rsync repository from SBo, so I made the >>> mistake of thinking that the git repository would work like the rsync >>> one,& only update when I used the sync command. My current assumption >>> is that the git repository is updated every time sbopkg is started. My >>> next assumption is that to update the repository, I would have to >>> remove the "#" from line 2 above, add it to line 3& start sbopkg. Is >>> that correct? I really don't need it to sync every time I start the >>> program >>> Regards, >>> Bill >>> >>> >> Hmm, using a git repo /should/ be just like the SBo rsync repo, meaning >> that it only syncs when you manuualy do so from the menu. It should not >> sync automatically every time you start sbopkg. I'll try and test this >> repo soon and see if I get a similar result. >> >> > Bill, > > I tested this out using the SBo-git repository and did not notice sbopkg > syncing automatically upon start. Everything seemed to be working as it > should. I am not sure why you are seeing that behavior. :/ > > > > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > Chess, Thanks for the effort. I will do some more investigation here & let you know what I come up with. Regards, Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess at chessgriffin.com Sat May 8 03:38:57 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 07 May 2010 23:38:57 -0400 Subject: [sbopkg-users] sbopkg slow to start using git repository In-Reply-To: <4BE42C33.2030909@gmail.com> References: <4BE1CDDE.2090009@gmail.com> <20100506175850.GA2975@localhost> <20100507041155.GA4859@localhost> <4BE42C33.2030909@gmail.com> Message-ID: <1273289937.12469.1374005333@webmail.messagingengine.com> On Fri, 07 May 2010 10:05 -0500, "B Kirkpatrick" wrote: > On 05/06/2010 11:11 PM, Chess Griffin wrote: > > * Chess Griffin [2010-05-06 13:58:50]: > > > > > >> * Bill Kirkpatrick [2010-05-06 12:00:16]: > >> > >> > >>> I've solved my problem (temporarily, I hope) by modifying > >>> /etc/sbopkg/repos.d/30-SBo-git.repo to: > >>> > >>> # Repo Branch Description Tag Tool Link CheckGPG > >>> #SBo-git current "Unofficial repository for -current" _SBo git git:// > >>> github.com/Ponce/SBo-git.git at current "" > >>> SBo-git current "Unofficial repository for -current" _SBo "" "" "" > >>> > >>> I am, of course, used to the rsync repository from SBo, so I made the > >>> mistake of thinking that the git repository would work like the rsync > >>> one,& only update when I used the sync command. My current assumption > >>> is that the git repository is updated every time sbopkg is started. My > >>> next assumption is that to update the repository, I would have to > >>> remove the "#" from line 2 above, add it to line 3& start sbopkg. Is > >>> that correct? I really don't need it to sync every time I start the > >>> program > >>> Regards, > >>> Bill > >>> > >>> > >> Hmm, using a git repo /should/ be just like the SBo rsync repo, meaning > >> that it only syncs when you manuualy do so from the menu. It should not > >> sync automatically every time you start sbopkg. I'll try and test this > >> repo soon and see if I get a similar result. > >> > >> > > Bill, > > > > I tested this out using the SBo-git repository and did not notice sbopkg > > syncing automatically upon start. Everything seemed to be working as it > > should. I am not sure why you are seeing that behavior. :/ > > > > > > > > > > _______________________________________________ > > sbopkg-users mailing list > > sbopkg-users at sbopkg.org > > http://sbopkg.org/mailman/listinfo/sbopkg-users > > > Chess, > Thanks for the effort. I will do some more investigation here & let you > know what I come up with. > Regards, > Bill > > No problem at all. Please do let us know if you discover a bug or find a way to reproduce the issue. We'll definitely take a look at fixing it if we can narrow it down. -- Chess Griffin From slakmagik at gmail.com Thu May 27 04:23:20 2010 From: slakmagik at gmail.com (slakmagik) Date: Thu, 27 May 2010 00:23:20 -0400 Subject: [sbopkg-users] sbopkg and git Message-ID: <20100527042320.GA29068@devbox> (I'm cross-posting this to slackbuilds-users for wider exposure, even though this doesn't relate to people using the git repos manually.) As Robby Workman mentioned in the Status Report http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-May/005627.html SBo git repositories are publicly available while the regular 13.1 repo is not yet. For those who might be interested in using sbopkg with this repository, we recommend waiting for the usual rsync-able 13.1 repo to open. However, if you absolutely can't wait, you might be able to temporarily create an /etc/sbopkg/repos.d/70-sbogit.repo file with something like the following line SBogit 13.1 "SBo-git repository for Slackware 13.1" _SBo git git://slackbuilds.org/slackbuilds.git at 13.1 "" Make sure $REPO_ROOT/SBogit does not exist, switch your repo to SBogit/13.1 and do an initial sync. If you do this, beware that this is not supported nor really tested. And be advised that the git sync will remove anything currently in the target directory. This behavior may be familiar to slamd64 users but may be unexpected to SBo/rsync users. For more information: http://code.google.com/p/sbopkg/issues/detail?id=47 We will be releasing 0.33.1 of sbopkg as soon as safely possible after SBo 13.1 goes live, but 0.32.0 does not "know about" some of the changes in the git repo. Basically, this is all untested and unsupported, but good luck with whatever you do. :) Also, apologies to anyone who downloaded sbopkg 0.33.0. There was a twilight zone where I was testing for release and had uploaded it but hadn't made any release announcement. Due to the need to take account of some changes in the SlackBuild template, that release was pulled. Nevertheless, it appears some people downloaded it. Mea culpa. From slakmagik at gmail.com Thu May 27 19:04:26 2010 From: slakmagik at gmail.com (slakmagik) Date: Thu, 27 May 2010 15:04:26 -0400 Subject: [sbopkg-users] Sbopkg 0.33.1 Released Message-ID: <20100527190426.GA19554@devbox> sbopkg 0.33.1 is released. This release brings us into alignment with SBo and Slackware 13.1, squashes several more or less obscure bugs, and adds a couple of features, too. Here are the changes since the last official release: * Addressed an apparent bash 4.1 bug that causes the 'obsolete sources' function to break. * Addressed issue 44 where hitting ^C during the download of part of a queue and restarting the queue could result in a download failure. Thanks to slava18 for the report. * Changed the menu order of the "Build options" dialog to default to using "Saved" options rather than "None". * Fixed issue 45 where packages with '+' in the name were not properly detected in some cases. Thanks to skalkoto for the report. * Added a help item to the main menu of the dialog interface with pointers to documentation and other resources. * Added an option to print the version of sbopkg. We try not to change the meaning of flags but note that this does change what was the '-v' flag to '-V' and now uses '-v' for its customary 'version' purpose. Note that the new -V flag now accepts a '?' argument (sbopkg -V ?) which will display the list of valid repositories. * Tweak the logic re determining ARCH and modify some ARCH-related evals and conditionals in check_for_updates and info_item. * Fixed a bug which could result in some sources being missed when checking for obsolete sources. * Added a command line option '-P' to access the 'remove uninstalled packages' function which had previously only been accessible from the dialog interface. * Miscellaneous tweaks in preparation for release and to bring in line with Slackware 13.1. * Tweaked widgets in select_repository() (no or less scrolling) and load_user_queue() (better button) and modified check_gpg() to not disrupt the dialog interface with gpg output * Revised the KNOWN_ISSUES file and other documentation As always, thanks to our users who have tested sbopkg and reported bugs and given us such positive, encouraging feedback. This release can be downloaded from http://www.sbopkg.org or http://code.google.com/p/sbopkg/ Thanks also to my fellow developers, Chess Griffin and Mauro Giachero. As may be obvious from the From line and from other signs, Chess is not doing this release but, never fear, he is still actively involved in sbopkg development and was a tremendous help with this release process. I've just agreed to help with releases and other administrative duties in addition to development. Have fun!