From chess at chessgriffin.com  Mon Mar  2 21:08:07 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 2 Mar 2009 16:08:07 -0500
Subject: [sbopkg-users] Another new member
Message-ID: <20090302210807.GB18753@localhost>

Slakmagik has made many fine contributions to sbopkg -- so I decided to
punish him by giving him commit access to the SVN repo.  :-)  I'd like
to thank slakmagik for his invaluable assistance and agreement to join
the team along with Mauro Giachero and myself.  The three of us have
been working well together on integrating improvements and fixes, and I
look forward to continuing to work with and learn from these guys while
we strive to continually improve sbopkg.

Welcome, slakmagik!

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090302/2e763890/attachment.sig>

From jsunx1 at bellsouth.net  Mon Mar  2 22:00:06 2009
From: jsunx1 at bellsouth.net (slakmagik)
Date: Mon, 2 Mar 2009 17:00:06 -0500
Subject: [sbopkg-users] Another new member
In-Reply-To: <20090302210807.GB18753@localhost>
References: <20090302210807.GB18753@localhost>
Message-ID: <20090302220006.GA26755@surfandslam>

On 2009-03-02 (Mon) 16:08:07 [-0500], Chess Griffin wrote:
> Welcome, slakmagik!
> 

Thank you, Chess. :)

Greetings to all on the list. It's been fun working with Chess and
Mauro. I appreciate their trust in me and I look forward to future
developments.

From me at alkos333.net  Mon Mar  2 22:02:42 2009
From: me at alkos333.net (alkos333)
Date: Mon, 2 Mar 2009 16:02:42 -0600
Subject: [sbopkg-users] Another new member
In-Reply-To: <20090302220006.GA26755@surfandslam>
References: <20090302210807.GB18753@localhost>
	<20090302220006.GA26755@surfandslam>
Message-ID: <a6f13f000903021402l418539fdt106e678092cf6763@mail.gmail.com>

On Mon, Mar 2, 2009 at 4:00 PM, slakmagik <jsunx1 at bellsouth.net> wrote:
> On 2009-03-02 (Mon) 16:08:07 [-0500], Chess Griffin wrote:
>> Welcome, slakmagik!
>>
>
> Thank you, Chess. :)
>
> Greetings to all on the list. It's been fun working with Chess and
> Mauro. I appreciate their trust in me and I look forward to future
> developments.
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>

Thank you all for such a wonderful tool.  It has saved me so much
time.  I really appreciate all of your efforts.

From chess at chessgriffin.com  Tue Mar  3 04:16:19 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 2 Mar 2009 23:16:19 -0500
Subject: [sbopkg-users] Sbopkg 0.27.0 released
In-Reply-To: <20090226104549.5d675767@liberty.rlwhome.lan>
References: <20090226152140.GA18127@localhost>
	<20090226104549.5d675767@liberty.rlwhome.lan>
Message-ID: <20090303041619.GA18837@localhost>

* Robby Workman <rw at rlworkman.net> [2009-02-26 10:45:49]:

> On Thu, 26 Feb 2009 10:21:40 -0500
> Chess Griffin <chess at chessgriffin.com> wrote:
> 
> >   * Include a French translation of the two sbopkg man pages.  For
> > now, these man pages will be included in the /doc directory until I
> > have time to figure out whether they can be automatically installed
> > in place of the English ones depending on a locale setting. 
> 
> 
> Install them to /usr/man/fr/man?/
> 
> See attached patch.
> 
> 
> > /var/lib/sbopkg/{repo,tmp,cache,queues} etc., but we have not spent
> > much time discussing this.  If you have any thoughts on what would be
> > a set of sensible defaults in this area, please feel free to speak up.
> 
> 
> Unless moving to a more self-contained layout simplifies things for
> you, I wouldn't do it that way.  I'd lean more toward using these:
>   /var/tmp/sbopkg
>   /var/cache/sbopkg
>   /var/lib/sbopkg/{queues,repo}
>   Other things might belong in subdirs of /var/{tmp,cache}/sbopkg as
>   appopriate, and probably other things (stuff you want to keep around
>   no matter what) will go in /var/lib/sbopkg.  Anyway, hopefully that
>   made a little bit of sense... :-)
> 
> -RW
>   

Robby,

Thank you for both of these suggestions.  I see what you are doing with
the patch and that seems pretty straightforward to implement.  As to the
directories, your suggested layout seems like it would work well.  We'll
kick this around at some point.

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: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090302/b99db9fc/attachment.sig>

From chess at chessgriffin.com  Wed Mar  4 02:20:43 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 3 Mar 2009 21:20:43 -0500
Subject: [sbopkg-users] [Slackbuilds-users] calcurse 2.5 refuses to build
In-Reply-To: <Pine.NEB.4.64.0903040124500.8530@sdf.lonestar.org>
References: <Pine.NEB.4.64.0903040051420.8530@sdf.lonestar.org>
	<20090304111003.6d4d00f8@shammah.timp.com.au>
	<Pine.NEB.4.64.0903040124500.8530@sdf.lonestar.org>
Message-ID: <20090304022043.GB19214@localhost>

* Glenn Becker <burningc at sdf.lonestar.org> [2009-03-04 01:25:24]:

>
>> The problem is with how sbopkg downloads the file, I'm not sure what would be
>> the best way to get around this though in the sbopkg. The download link is
>> http://culot.org/cgi-bin/get.cgi?calcurse-2.5.tar.gz, wget saves this as
>> get.cgi?calcurse-2.5.tar.gz while the SlackBuild is looking for
>> calcurse-2.5.tar.gz.
>
> ah okay - thanks, I wondered about that. :)

Glenn, thanks for bringing this up.  We'll take a look at fixing this in
sbopkg.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090303/6b60d606/attachment.sig>

From me at alkos333.net  Wed Mar  4 18:11:07 2009
From: me at alkos333.net (alkos333)
Date: Wed, 4 Mar 2009 12:11:07 -0600
Subject: [sbopkg-users] Obsolete Packages
Message-ID: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>

How about an "Obsolete Package" function in Utilities  menu that would
do the following:

for pkg in $OUTPUT/*.tgz
    do
            if [ ! -f /var/log/packages/${pkg%.tgz} ]; then
                    rm $pkg
            fi
    done


The it's very useful for system porting when somebody just wants to
reinstall the exact collection of packages without having to recompile
all of them on the newly ported system, using the queue.  This way,
you just eliminate obsolete packages on the model system, back them
up, and then run something like this on the new system:

installpkg $OUTPUT/*.tgz

From jsunx1 at bellsouth.net  Wed Mar  4 22:36:50 2009
From: jsunx1 at bellsouth.net (slakmagik)
Date: Wed, 4 Mar 2009 17:36:50 -0500
Subject: [sbopkg-users] Obsolete Packages
In-Reply-To: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>
References: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>
Message-ID: <20090304223650.GA8219@surfandslam>

On 2009-03-04 (Wed) 12:11:07 [-0600], alkos333 wrote:
> How about an "Obsolete Package" function in Utilities  menu that would
> do the following:
> 
> for pkg in $OUTPUT/*.tgz
>     do
>             if [ ! -f /var/log/packages/${pkg%.tgz} ]; then
>                     rm $pkg
>             fi
>     done
> 
> 
> The it's very useful for system porting when somebody just wants to
> reinstall the exact collection of packages without having to recompile
> all of them on the newly ported system, using the queue.  This way,
> you just eliminate obsolete packages on the model system, back them
> up, and then run something like this on the new system:
> 
> installpkg $OUTPUT/*.tgz

The above would need to be something like

for pkg in /home/slackbuilds/pkgs/*.tgz; do
    pkgfile=${pkg##*/}
    if [ ! -f /var/log/packages/${pkgfile%.tgz} ]; then
        rm $pkg
    fi
done

to do the path substitution as well as extension removal.

We'd been batting around ideas for something similar, but I don't think
we hit upon this particular thing. Mauro may want to jump in as he had
done some work here.

There shouldn't be any features in this release cycle but, for
version-after-next, we'll see. Thanks very much for the suggestion.

From me at alkos333.net  Wed Mar  4 22:55:04 2009
From: me at alkos333.net (alkos333)
Date: Wed, 4 Mar 2009 16:55:04 -0600
Subject: [sbopkg-users] Obsolete Packages
In-Reply-To: <20090304223650.GA8219@surfandslam>
References: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>
	<20090304223650.GA8219@surfandslam>
Message-ID: <a6f13f000903041455p23fdfd89xff4929179171396e@mail.gmail.com>

On Wed, Mar 4, 2009 at 4:36 PM, slakmagik <jsunx1 at bellsouth.net> wrote:
> On 2009-03-04 (Wed) 12:11:07 [-0600], alkos333 wrote:
>> How about an "Obsolete Package" function in Utilities ?menu that would
>> do the following:
>>
>> for pkg in $OUTPUT/*.tgz
>> ? ? do
>> ? ? ? ? ? ? if [ ! -f /var/log/packages/${pkg%.tgz} ]; then
>> ? ? ? ? ? ? ? ? ? ? rm $pkg
>> ? ? ? ? ? ? fi
>> ? ? done
>>
>>
>> The it's very useful for system porting when somebody just wants to
>> reinstall the exact collection of packages without having to recompile
>> all of them on the newly ported system, using the queue. ?This way,
>> you just eliminate obsolete packages on the model system, back them
>> up, and then run something like this on the new system:
>>
>> installpkg $OUTPUT/*.tgz
>
> The above would need to be something like
>
> for pkg in /home/slackbuilds/pkgs/*.tgz; do
> ? ?pkgfile=${pkg##*/}
> ? ?if [ ! -f /var/log/packages/${pkgfile%.tgz} ]; then
> ? ? ? ?rm $pkg
> ? ?fi
> done
>
> to do the path substitution as well as extension removal.
>
> We'd been batting around ideas for something similar, but I don't think
> we hit upon this particular thing. Mauro may want to jump in as he had
> done some work here.
>
> There shouldn't be any features in this release cycle but, for
> version-after-next, we'll see. Thanks very much for the suggestion.
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>

I don't see the point of hardcoding the search path and the defining pkgfile

-- 

Carl Sagan  - "In order to make an apple pie from scratch, you must
first create the universe."

From jsunx1 at bellsouth.net  Wed Mar  4 23:35:56 2009
From: jsunx1 at bellsouth.net (slakmagik)
Date: Wed, 4 Mar 2009 18:35:56 -0500
Subject: [sbopkg-users] Obsolete Packages
In-Reply-To: <a6f13f000903041455p23fdfd89xff4929179171396e@mail.gmail.com>
References: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>
	<20090304223650.GA8219@surfandslam>
	<a6f13f000903041455p23fdfd89xff4929179171396e@mail.gmail.com>
Message-ID: <20090304233556.GA8548@surfandslam>

On 2009-03-04 (Wed) 16:55:04 [-0600], alkos333 wrote:
> On Wed, Mar 4, 2009 at 4:36 PM, slakmagik <jsunx1 at bellsouth.net> wrote:
> >
> > The above would need to be something like
> >
> > for pkg in /home/slackbuilds/pkgs/*.tgz; do
> >      pkgfile=${pkg##*/}
> >      if [ ! -f /var/log/packages/${pkgfile%.tgz} ]; then
> >            rm $pkg
> >      fi
> > done
> >
> > to do the path substitution as well as extension removal.
> >
> 
> I don't see the point of hardcoding the search path and the defining pkgfile
> 

Crap. I just changed the search path to run it off the command line and
it should have been changed back before I mailed it, but I forgot.

But the definition of pkgfile is because your

    if [ ! -f /var/log/packages/${pkg%.tgz} ]; then

expands to

    if [ ! -f /var/log/packages//value/of/OUTPUT/pkgname ]; then

The expansion of $OUTPUT (or '/value/of/output') needs to be removed and
doing two parameter expansions is faster than 'basename $pkg .tgz'. You
could also 'cd $OUTPUT' and then do 'for pkg in *.tgz', I guess, though
I'd rather not.

From me at alkos333.net  Thu Mar  5 00:02:14 2009
From: me at alkos333.net (alkos333)
Date: Wed, 4 Mar 2009 18:02:14 -0600
Subject: [sbopkg-users] Obsolete Packages
In-Reply-To: <20090304233556.GA8548@surfandslam>
References: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>
	<20090304223650.GA8219@surfandslam>
	<a6f13f000903041455p23fdfd89xff4929179171396e@mail.gmail.com>
	<20090304233556.GA8548@surfandslam>
Message-ID: <a6f13f000903041602y412fdb81s36d06ea00fd74ec4@mail.gmail.com>

On Wed, Mar 4, 2009 at 5:35 PM, slakmagik <jsunx1 at bellsouth.net> wrote:
> On 2009-03-04 (Wed) 16:55:04 [-0600], alkos333 wrote:
>> On Wed, Mar 4, 2009 at 4:36 PM, slakmagik <jsunx1 at bellsouth.net> wrote:
>> >
>> > The above would need to be something like
>> >
>> > for pkg in /home/slackbuilds/pkgs/*.tgz; do
>> > ? ? ?pkgfile=${pkg##*/}
>> > ? ? ?if [ ! -f /var/log/packages/${pkgfile%.tgz} ]; then
>> > ? ? ? ? ? ?rm $pkg
>> > ? ? ?fi
>> > done
>> >
>> > to do the path substitution as well as extension removal.
>> >
>>
>> I don't see the point of hardcoding the search path and the defining pkgfile
>>
>
> Crap. I just changed the search path to run it off the command line and
> it should have been changed back before I mailed it, but I forgot.
>
> But the definition of pkgfile is because your
>
> ? ?if [ ! -f /var/log/packages/${pkg%.tgz} ]; then
>
> expands to
>
> ? ?if [ ! -f /var/log/packages//value/of/OUTPUT/pkgname ]; then
>
> The expansion of $OUTPUT (or '/value/of/output') needs to be removed and
> doing two parameter expansions is faster than 'basename $pkg .tgz'. You
> could also 'cd $OUTPUT' and then do 'for pkg in *.tgz', I guess, though
> I'd rather not.
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>

I see.  I just ran my snippet from the current directly ($OUTPUT), so
I didn't think of that.  Yes, the two parameter replacement is
definitely faster than a running an outside c binary.

-- 

Joe DiMaggio  - "Pair up in threes."

From mauro.giachero at gmail.com  Thu Mar  5 09:38:32 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Thu, 5 Mar 2009 10:38:32 +0100
Subject: [sbopkg-users] Obsolete Packages
In-Reply-To: <a6f13f000903041602y412fdb81s36d06ea00fd74ec4@mail.gmail.com>
References: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>
	<20090304223650.GA8219@surfandslam>
	<a6f13f000903041455p23fdfd89xff4929179171396e@mail.gmail.com>
	<20090304233556.GA8548@surfandslam>
	<a6f13f000903041602y412fdb81s36d06ea00fd74ec4@mail.gmail.com>
Message-ID: <da3e877f0903050138h4e9464d1k6177d492f3624bf5@mail.gmail.com>

This is a good idea, thanks.
Since we aren't likely to implement new features for the next release, would
you mind to open an Enhancement issue on the project repository [1]? Because
I have less memory than my cell phone...

[1] http://code.google.com/p/sbopkg/issues/entry
-- 
Mauro Giachero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090305/4ac908f9/attachment.htm>

From me at alkos333.net  Thu Mar  5 16:48:00 2009
From: me at alkos333.net (alkos333)
Date: Thu, 5 Mar 2009 10:48:00 -0600
Subject: [sbopkg-users] Obsolete Packages
In-Reply-To: <da3e877f0903050138h4e9464d1k6177d492f3624bf5@mail.gmail.com>
References: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>
	<20090304223650.GA8219@surfandslam>
	<a6f13f000903041455p23fdfd89xff4929179171396e@mail.gmail.com>
	<20090304233556.GA8548@surfandslam>
	<a6f13f000903041602y412fdb81s36d06ea00fd74ec4@mail.gmail.com>
	<da3e877f0903050138h4e9464d1k6177d492f3624bf5@mail.gmail.com>
Message-ID: <a6f13f000903050848h26e574d0g6366b785895bc3ed@mail.gmail.com>

On Thu, Mar 5, 2009 at 3:38 AM, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> This is a good idea, thanks.
> Since we aren't likely to implement new features for the next release, would
> you mind to open an Enhancement issue on the project repository [1]? Because
> I have less memory than my cell phone...
>
> [1] http://code.google.com/p/sbopkg/issues/entry
> --
> Mauro Giachero
>
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>
>

Done, only it shows up as Defect. Could you adjust that :)?
http://code.google.com/p/sbopkg/issues/detail?id=20

-- 

Joe DiMaggio  - "Pair up in threes."

From mauro.giachero at gmail.com  Thu Mar  5 17:54:04 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Thu, 5 Mar 2009 18:54:04 +0100
Subject: [sbopkg-users] Obsolete Packages
In-Reply-To: <a6f13f000903050848h26e574d0g6366b785895bc3ed@mail.gmail.com>
References: <a6f13f000903041011i9247ed2u8d93f38b4baa9bd1@mail.gmail.com>
	<20090304223650.GA8219@surfandslam>
	<a6f13f000903041455p23fdfd89xff4929179171396e@mail.gmail.com>
	<20090304233556.GA8548@surfandslam>
	<a6f13f000903041602y412fdb81s36d06ea00fd74ec4@mail.gmail.com>
	<da3e877f0903050138h4e9464d1k6177d492f3624bf5@mail.gmail.com>
	<a6f13f000903050848h26e574d0g6366b785895bc3ed@mail.gmail.com>
Message-ID: <da3e877f0903050954s28d0945cifaf923e8a83a3b9f@mail.gmail.com>

On Thu, Mar 5, 2009 at 5:48 PM, alkos333 <me at alkos333.net> wrote:

> Done, only it shows up as Defect. Could you adjust that :)?
> http://code.google.com/p/sbopkg/issues/detail?id=20


Done!

-- 
Mauro Giachero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090305/6e2bc9ce/attachment.htm>

From didier.spaier at epsm.fr  Sat Mar  7 12:34:15 2009
From: didier.spaier at epsm.fr (Didier Spaier)
Date: Sat, 7 Mar 2009 13:34:15 +0100
Subject: [sbopkg-users] Stuck in firs 'Update' - sbopkg 0.27.0
Message-ID: <200903071334.16287.didier.spaier@epsm.fr>

Hello everybody, I am a newcomer here ;)

Thanks for sbopkg, it is really useful.

I just upgraded to 0.27.0 (sbopkg.conf with changes merged is attached), launched an xterm, su, sbopkg, chose Rsync in the menu. So far, so good.

Then I chose Updates in the menu and was stuck at 0% for 10 minutes - had to kill the xterm with Ctrtl + c.

Then I tried again in command line mode:  'sbopkg -c' => OK

I tried again with the menu => OK.  

Just wonderng what can have happened during the first try ?

Cheers,

Didier

Slackware 12.2 - kernel 2.6.27.19-smp slightly customized
-------------- next part --------------
# $Id: sbopkg.conf.new 270 2008-12-29 19:40:35Z chess.griffin $
#
# Please read the sbopkg.conf(5) man page for information about this
# configuration file, including an explanation of how to set these
# variables.

# The following are variables used by sbopkg.  NOTE:  $TMP and $OUTPUT
# must be exported as both are used by the SlackBuild scripts as well.
# Any of the other variables could be exported as well, if desired.
RSYNCMIRROR=slackbuilds.org::slackbuilds
SLACKVER=${SLACKVER:-12.2}
LOCALREPO=${LOCALREPO:-/home/logiciels/sbo}
SRCDIR=${SRCDIR:-/var/cache/sbopkg}
export TMP=${TMP:-/tmp/SBo}
export OUTPUT=${OUTPUT:-/tmp}
QUEUEDIR=$TMP/queues
KEEPLOG=YES
LOGFILE=$TMP/sbopkg-build-log
DEBUG=0

# The following variables are required and can be tweaked if desired,
# although most users should leave them alone.  Note:  rsync already
# uses --archive, --delete, --no-owner, and --exclude in the main
# sbopkg script so there is no need to add those flags here.
# Similarly, wget already uses the -O options so there is no need to
# add that either.  In general, it is not recommended that users
# change these default values.
RSYNCFLAGS="--verbose --timeout=10"
WGETFLAGS="--continue --progress=bar --timeout=15 --tries=5"
DIFF=${DIFF:-diff}
DIFFOPTS=${DIFFOPTS:--u}

From chess at chessgriffin.com  Sat Mar  7 13:48:34 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Sat, 7 Mar 2009 08:48:34 -0500
Subject: [sbopkg-users] Stuck in firs 'Update' - sbopkg 0.27.0
In-Reply-To: <200903071334.16287.didier.spaier@epsm.fr>
References: <200903071334.16287.didier.spaier@epsm.fr>
Message-ID: <20090307134834.GA2933@localhost>

* Didier Spaier <didier.spaier at epsm.fr> [2009-03-07 13:34:15]:

> Hello everybody, I am a newcomer here ;)
> 
> Thanks for sbopkg, it is really useful.

Hello Didier, glad to hear that sbopkg is useful for you!  :-)

> 
> I just upgraded to 0.27.0 (sbopkg.conf with changes merged is attached), launched an xterm, su, sbopkg, chose Rsync in the menu. So far, so good.
> 
> Then I chose Updates in the menu and was stuck at 0% for 10 minutes - had to kill the xterm with Ctrtl + c.
> 
> Then I tried again in command line mode:  'sbopkg -c' => OK
> 
> I tried again with the menu => OK.  
> 
> Just wonderng what can have happened during the first try ?
> 
> Cheers,
> 
> Didier
> 

Hm, that is odd.  I have not seen that myself.  If anyone else
experiences this, please let us know.  I'll keep checking on the update
myself, just to see if I can reproduce it.

Thanks for reporting it, Didier.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090307/ca4b57cf/attachment.sig>

From phillip.c.warner at gmail.com  Sat Mar  7 16:20:26 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Sat, 7 Mar 2009 10:20:26 -0600
Subject: [sbopkg-users] Stuck in firs 'Update' - sbopkg 0.27.0
In-Reply-To: <20090307134834.GA2933@localhost>
References: <200903071334.16287.didier.spaier@epsm.fr>
	<20090307134834.GA2933@localhost>
Message-ID: <eded84250903070820q8c4b11qaa012045e0937e40@mail.gmail.com>

maybe the screen just did not refresh or something.  Next time actually
check if the update file is there and growing
  tail -f -n1 /tmp/SBo/sbopkg_updatelist

If the file is growing, but sbopkg is not responding try either resizing the
terminal or
  pkill -WINCH dialog

The refresh code in sbopkg works 99% of the time, but every "once in a
purple moon" it does not.

--phillip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090307/5687b80e/attachment.htm>

From phillip.c.warner at gmail.com  Sat Mar  7 19:04:02 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Sat, 7 Mar 2009 13:04:02 -0600
Subject: [sbopkg-users] renames bugs - sbopkg 0.27.0
Message-ID: <eded84250903071104i36b666efr4a42ed35416e8489@mail.gmail.com>

As I suspected there are still some renames bugs in sbopkg.  For instance,
if I have MPlayer installed and choose to build and install mplayer, then it
is installed alongside MPlayer.  The install/upgrade procedures in these
cases cannot do a basic upgradepkg, but instead need to specify
"oldpackagename%newpackagename".

If this is not intended to be implemented then perhaps a note about this
limitation is in order.

--phillip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090307/aedf34bf/attachment.htm>

From didier.spaier at epsm.fr  Sat Mar  7 19:27:31 2009
From: didier.spaier at epsm.fr (Didier Spaier)
Date: Sat, 7 Mar 2009 20:27:31 +0100
Subject: [sbopkg-users] Stuck in firs 'Update' - sbopkg 0.27.0
In-Reply-To: <eded84250903070820q8c4b11qaa012045e0937e40@mail.gmail.com>
References: <200903071334.16287.didier.spaier@epsm.fr>
	<20090307134834.GA2933@localhost>
	<eded84250903070820q8c4b11qaa012045e0937e40@mail.gmail.com>
Message-ID: <200903072027.31568.didier.spaier@epsm.fr>

Le Saturday 07 March 2009 17:20:26 Phillip Warner, vous avez ?crit?:
> maybe the screen just did not refresh or something.  Next time actually
> check if the update file is there and growing
>   tail -f -n1 /tmp/SBo/sbopkg_updatelist
> 
> If the file is growing, but sbopkg is not responding try either resizing the
> terminal or
>   pkill -WINCH dialog
> 
> The refresh code in sbopkg works 99% of the time, but every "once in a
> purple moon" it does not.
> 
> --phillip

Thanks for the suggestion Phillip. l'll use put it in practice  if/when the case occurs again.

From me at alkos333.net  Sat Mar  7 19:36:26 2009
From: me at alkos333.net (alkos333)
Date: Sat, 7 Mar 2009 13:36:26 -0600
Subject: [sbopkg-users] Stuck in firs 'Update' - sbopkg 0.27.0
In-Reply-To: <20090307134834.GA2933@localhost>
References: <200903071334.16287.didier.spaier@epsm.fr>
	<20090307134834.GA2933@localhost>
Message-ID: <a6f13f000903071136u45449e76sb2f5f145b344a43e@mail.gmail.com>

On Sat, Mar 7, 2009 at 7:48 AM, Chess Griffin <chess at chessgriffin.com> wrote:
> * Didier Spaier <didier.spaier at epsm.fr> [2009-03-07 13:34:15]:
>
>> Hello everybody, I am a newcomer here ;)
>>
>> Thanks for sbopkg, it is really useful.
>
> Hello Didier, glad to hear that sbopkg is useful for you! ?:-)
>
>>
>> I just upgraded to 0.27.0 (sbopkg.conf with changes merged is attached), launched an xterm, su, sbopkg, chose Rsync in the menu. So far, so good.
>>
>> Then I chose Updates in the menu and was stuck at 0% for 10 minutes - had to kill the xterm with Ctrtl + c.
>>
>> Then I tried again in command line mode: ?'sbopkg -c' => OK
>>
>> I tried again with the menu => OK.
>>
>> Just wonderng what can have happened during the first try ?
>>
>> Cheers,
>>
>> Didier
>>
>
> Hm, that is odd. ?I have not seen that myself. ?If anyone else
> experiences this, please let us know. ?I'll keep checking on the update
> myself, just to see if I can reproduce it.
>
> Thanks for reporting it, Didier.
>
> --
> Chess Griffin
>
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>
>

Yes, this has happened to me several times.

-- 

Ani DiFranco  - "Art may imitate life, but life imitates TV."

From chess at chessgriffin.com  Sun Mar  8 15:02:30 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Sun, 8 Mar 2009 11:02:30 -0400
Subject: [sbopkg-users] renames bugs - sbopkg 0.27.0
In-Reply-To: <eded84250903071104i36b666efr4a42ed35416e8489@mail.gmail.com>
References: <eded84250903071104i36b666efr4a42ed35416e8489@mail.gmail.com>
Message-ID: <20090308150230.GB3109@localhost>

* Phillip Warner <phillip.c.warner at gmail.com> [2009-03-07 13:04:02]:

> As I suspected there are still some renames bugs in sbopkg.  For instance,
> if I have MPlayer installed and choose to build and install mplayer, then it
> is installed alongside MPlayer.  The install/upgrade procedures in these
> cases cannot do a basic upgradepkg, but instead need to specify
> "oldpackagename%newpackagename".
> 
> If this is not intended to be implemented then perhaps a note about this
> limitation is in order.
> 
> --phillip

Thanks, Phillip.  We'll take a further look at this.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090308/eee2d0c0/attachment.sig>

From mauro.giachero at gmail.com  Mon Mar  9 10:46:55 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Mon, 9 Mar 2009 11:46:55 +0100
Subject: [sbopkg-users] Stuck in firs 'Update' - sbopkg 0.27.0
In-Reply-To: <a6f13f000903071136u45449e76sb2f5f145b344a43e@mail.gmail.com>
References: <200903071334.16287.didier.spaier@epsm.fr>
	<20090307134834.GA2933@localhost>
	<a6f13f000903071136u45449e76sb2f5f145b344a43e@mail.gmail.com>
Message-ID: <da3e877f0903090346o3ed51f47q67dae1784c855ce1@mail.gmail.com>

Didier, alkos333,

you may want to try commenting out/deleting the line
    [[ "$TERM" =~ "^rxvt.*" || "$TERM" =~ "^screen.*" ]] && \
around line 2900 of sbopkg. This should fix the issue if it's a refresh
problem. If you do so, please tell us about successes and failures.

Also, what's your $TERM value?

-- 
Mauro Giachero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090309/d85dafad/attachment-0001.htm>

From didier.spaier at epsm.fr  Mon Mar  9 11:27:25 2009
From: didier.spaier at epsm.fr (Didier Spaier)
Date: Mon, 9 Mar 2009 12:27:25 +0100
Subject: [sbopkg-users] Stuck in firs 'Update' - sbopkg 0.27.0
In-Reply-To: <da3e877f0903090346o3ed51f47q67dae1784c855ce1@mail.gmail.com>
References: <200903071334.16287.didier.spaier@epsm.fr>
	<a6f13f000903071136u45449e76sb2f5f145b344a43e@mail.gmail.com>
	<da3e877f0903090346o3ed51f47q67dae1784c855ce1@mail.gmail.com>
Message-ID: <200903091227.25386.didier.spaier@epsm.fr>

Le Monday 09 March 2009 11:46:55 Mauro Giachero, vous avez ?crit?:
> Didier, alkos333,
> 
> you may want to try commenting out/deleting the line
>     [[ "$TERM" =~ "^rxvt.*" || "$TERM" =~ "^screen.*" ]] && \
> around line 2900 of sbopkg. This should fix the issue if it's a refresh
> problem. 
Thanks for the info. Commented out line 3094

>If you do so, please tell us about successes and failures.
I will.

> Also, what's your $TERM value?
xterm

Cheers,

Didier

From me at alkos333.net  Mon Mar  9 12:34:36 2009
From: me at alkos333.net (alkos333)
Date: Mon, 9 Mar 2009 07:34:36 -0500
Subject: [sbopkg-users] Stuck in firs 'Update' - sbopkg 0.27.0
In-Reply-To: <200903091227.25386.didier.spaier@epsm.fr>
References: <200903071334.16287.didier.spaier@epsm.fr>
	<a6f13f000903071136u45449e76sb2f5f145b344a43e@mail.gmail.com>
	<da3e877f0903090346o3ed51f47q67dae1784c855ce1@mail.gmail.com>
	<200903091227.25386.didier.spaier@epsm.fr>
Message-ID: <a6f13f000903090534v48d7ff3bu35fc3dbbfd56e262@mail.gmail.com>

On Mon, Mar 9, 2009 at 6:27 AM, Didier Spaier <didier.spaier at epsm.fr> wrote:
> Le Monday 09 March 2009 11:46:55 Mauro Giachero, vous avez ?crit?:
>> Didier, alkos333,
>>
>> you may want to try commenting out/deleting the line
>> ? ? [[ "$TERM" =~ "^rxvt.*" || "$TERM" =~ "^screen.*" ]] && \
>> around line 2900 of sbopkg. This should fix the issue if it's a refresh
>> problem.
> Thanks for the info. Commented out line 3094
>
>>If you do so, please tell us about successes and failures.
> I will.
>
>> Also, what's your $TERM value?
> xterm
>
> Cheers,
>
> Didier
>


$ echo $TERM
xterm


-- 

Bob Hope  - "Middle age is when your age starts to show around your middle."

From mccnews at free.fr  Mon Mar  9 18:49:27 2009
From: mccnews at free.fr (mc collilieux)
Date: Mon, 09 Mar 2009 19:49:27 +0100
Subject: [sbopkg-users] strange error depending on run directory
Message-ID: <49B564B7.9090701@free.fr>

Hello, I am a new member of this list, with slackware 12.1
I have a little problem with sbopkg, in line 99
KEEPLOG=$(echo "$KEEPLOG" | tr [[:lower:]] [[:upper:]])

when I run it (as root but in my user home) i have this error message:

tr: construit [[:upper:]] et/ou [[:lower:]] mal align?
(tr: built [[:upper:]] and/or [[:lower:]] misaligned ?)

ERROR
sbopkg: Can't find a value for variable(s):
KEEPLOG

when I run it outside \home\myuser, it's OK, strange ? What can be this 
problem, I think perhaps false rights ?

-- 
Marie-Claude Collilieux
Bretagne

From jsunx1 at bellsouth.net  Mon Mar  9 20:47:45 2009
From: jsunx1 at bellsouth.net (slakmagik)
Date: Mon, 9 Mar 2009 16:47:45 -0400
Subject: [sbopkg-users] strange error depending on run directory
In-Reply-To: <49B564B7.9090701@free.fr>
References: <49B564B7.9090701@free.fr>
Message-ID: <20090309204745.GA3747@surfandslam>

On 2009-03-09 (Mon) 19:49:27 [+0100], mc collilieux wrote:
> Hello, I am a new member of this list, with slackware 12.1

Welcome. :)

> I have a little problem with sbopkg, in line 99
> KEEPLOG=$(echo "$KEEPLOG" | tr [[:lower:]] [[:upper:]])
>
> when I run it (as root but in my user home) i have this error message:
>
> tr: construit [[:upper:]] et/ou [[:lower:]] mal align?
> (tr: built [[:upper:]] and/or [[:lower:]] misaligned ?)

Je ne parle pas fran?ais (is that right?) but:

misaligned [[:upper:]] and/or [[:lower:]] construct

>
> ERROR
> sbopkg: Can't find a value for variable(s):
> KEEPLOG
>
> when I run it outside \home\myuser, it's OK, strange ? What can be this  
> problem, I think perhaps false rights ?
>

I'm not really sure what the problem is. I doubt it's a permissions
issue, though it could be. Is KEEPLOG set in the conf file(s) (root and
user may be accessing different conf files) and to what? What is the
literal pathname of /home/myuser and what odd files might be in it? Are
root and user's locale settings or other possibly related values
different?

In any case, does changing line 99 to

KEEPLOG=$(echo "$KEEPLOG" | tr "[:lower:]" "[:upper:]")

help? I hope that'll do it but, if not, for troubleshooting purposes,
does

KEEPLOG=$(echo "$KEEPLOG" | tr a-z A-Z)

work, just considering those characters?

From mccnews at free.fr  Mon Mar  9 23:37:30 2009
From: mccnews at free.fr (mc collilieux)
Date: Tue, 10 Mar 2009 00:37:30 +0100
Subject: [sbopkg-users] strange error depending on run directory
In-Reply-To: <20090309204745.GA3747@surfandslam>
References: <49B564B7.9090701@free.fr> <20090309204745.GA3747@surfandslam>
Message-ID: <49B5A83A.2000102@free.fr>

slakmagik a ?crit :
>> tr: construit [[:upper:]] et/ou [[:lower:]] mal align?
(construit should be _construction_ in french)
> 
> Je ne parle pas fran?ais (is that right?)
But it seems good :)
> but: misaligned [[:upper:]] and/or [[:lower:]] construct

to be more clear
If I have L99
KEEPLOG=$(echo "$KEEPLOG" | tr [[:lower:]] [[:upper:]])

sbopkg (with su root) run in any directory except /home/mcc, but run in
/home/mcc/test or other subdirectory

> Is KEEPLOG set in the conf file(s)
KEEPLOG=yes in /etc/sbopkg/sbopkg.conf. I have not personal conf
file, neither root.

> user may be accessing different conf files) and to what? What is the 
> literal pathname of /home/myuser and what odd files might be in it?
> Are root and user's locale settings or other possibly related values 
> different?

I have not seen any difference in locale or other env variables. I have
the same shell bash and only one version of tr.

> In any case, does changing line 99 to
> 
> KEEPLOG=$(echo "$KEEPLOG" | tr "[:lower:]" "[:upper:]")
> 
if I change L99 like
KEEPLOG=$(echo "$KEEPLOG" | tr [:lower:] [:upper:])
or
KEEPLOG=$(echo "$KEEPLOG" | tr "[:lower:]" "[:upper:]")
it's OK for root also in /home/mcc
Thanks for the idea

Finally, I can use sbopkg even if out my /home, it is not a big problem.
I wish only understand what's happening


-- 
Marie-Claude Collilieux
Bretagne

From jsunx1 at bellsouth.net  Tue Mar 10 21:49:08 2009
From: jsunx1 at bellsouth.net (slakmagik)
Date: Tue, 10 Mar 2009 17:49:08 -0400
Subject: [sbopkg-users] strange error depending on run directory
In-Reply-To: <49B5A83A.2000102@free.fr>
References: <49B564B7.9090701@free.fr> <20090309204745.GA3747@surfandslam>
	<49B5A83A.2000102@free.fr>
Message-ID: <20090310214908.GA5601@surfandslam>

On 2009-03-10 (Tue) 00:37:30 [+0100], mc collilieux wrote:
>>
> if I change L99 like
> KEEPLOG=$(echo "$KEEPLOG" | tr [:lower:] [:upper:])
> or
> KEEPLOG=$(echo "$KEEPLOG" | tr "[:lower:]" "[:upper:]")
> it's OK for root also in /home/mcc
> Thanks for the idea
>

Okay, glad that helps.

> Finally, I can use sbopkg even if out my /home, it is not a big problem.
> I wish only understand what's happening
>

I wish that, too, but I'm afraid I'm not sure what's going on. I'm not
good with I18N/L10N issues, if that's even what it is. And while the
double-brackets probably never should have been in there, the
inconsistency of the error is more puzzling. Anyway - I'll have to look
into it some more and maybe get more bug reports from others but, for
now, I guess I'll just change it to the above, since that seems to work.
Thanks for bringing this to my attention.

From mauro.giachero at gmail.com  Wed Mar 11 16:04:41 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Wed, 11 Mar 2009 17:04:41 +0100
Subject: [sbopkg-users] renames bugs - sbopkg 0.27.0
In-Reply-To: <da3e877f0903090308v721f8ad4t729218dd5ff8bc56@mail.gmail.com>
References: <eded84250903071104i36b666efr4a42ed35416e8489@mail.gmail.com>
	<20090308150230.GB3109@localhost>
	<da3e877f0903090308v721f8ad4t729218dd5ff8bc56@mail.gmail.com>
Message-ID: <da3e877f0903110904xd9109c3o36d8148e839a0d5d@mail.gmail.com>

The attached patch (on top of r498) fixes the problem here.
Unless any problems arises, I'd like to commit it this week. I'll also think
about applying a slightly less intrusive patch (not touching info_item and
the updates code, at least -- suggestions are welcome) to -stable.

-- 
Mauro Giachero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090311/f0950cac/attachment.htm>
-------------- next part --------------
From 0c90aa542dea1440593c23c364409c28d7785c01 Mon Sep 17 00:00:00 2001
From: Mauro Giachero <mauro.giachero at gmail.com>
Date: Mon, 9 Mar 2009 10:59:53 +0100
Subject: [PATCH] Refactor the renames code and fix upgrading renamed packages.

This patch refactors the renames code putting the old/new
name retrieval in two generic helpers.
Also fix the upgrading of renamed packages by providing
the old package name to upgradepkg.

Signed-off-by: Mauro Giachero <mauro.giachero at gmail.com>
---
 src/usr/sbin/sbopkg |   77 +++++++++++++++++++++++++++++++++++++++++++--------
 1 files changed, 65 insertions(+), 12 deletions(-)

diff --git a/src/usr/sbin/sbopkg b/src/usr/sbin/sbopkg
index 4e57126..9836fca 100755
--- a/src/usr/sbin/sbopkg
+++ b/src/usr/sbin/sbopkg
@@ -390,6 +390,47 @@ function progressbar_interrupted () {
     [[ "$KEY" = "$ESC" ]]
 }
 
+get_new_name () {
+    # Return the new package name, as for sbopkg-renames.
+    # If there isn't any new name, return the old name.
+    # $1 = the variable where to put the new name
+    # $2 = the old name
+    local NEWNAMEVAR="$1"
+    local OLDNAME="$2"
+    local TMP
+
+    TMP=$(grep "^$OLDNAME=" $SBOPKG_RENAMES)
+    if [[ -z "$TMP" ]]; then
+        # No rename occoured
+        TMP=$OLDNAME
+    else
+        # The package got renamed
+        TMP=$(cut -d= -f2 <<<"$TMP")
+    fi
+    eval $NEWNAMEVAR=$TMP
+}
+
+get_old_name () {
+    # Return the old package name, as for sbopkg-renames.
+    # If there isn't any old name, return the new name.
+    # $1 = the variable where to put the old name
+    # $2 = the new name
+    local OLDNAMEVAR="$1"
+    local NEWNAME="$2"
+    local TMP
+
+    # Manage package renames
+    TMP=$(grep "=$NEWNAME\$" $SBOPKG_RENAMES)
+    if [[ -z "$TMP" ]]; then
+        # No rename occoured
+        TMP=$NEWNAME
+    else
+        # The package got renamed
+        TMP=$(cut -d= -f1 <<<"$TMP")
+    fi
+    eval $OLDNAMEVAR=$TMP
+}
+
 check_for_updates () {
     # This checks for updates to installed SBo packages.  Thanks to Mauro
     # Giachero for this much-improved update code and related functions!
@@ -443,14 +484,7 @@ check_for_updates () {
         # End pkgtool code
 
             # Manage package renames
-            NAME=$(grep "^$OLDNAME=" $SBOPKG_RENAMES)
-            if [ -z $NAME ]; then
-                # No rename occoured
-                NAME=$OLDNAME
-            else
-                # The package got renamed
-                NAME=$(echo $NAME |cut -d= -f2)
-            fi
+            get_new_name NAME $OLDNAME
 
             # Find the current SlackBuild
             NEWSB=$(find $LOCALREPO/$SLACKVER -name "$NAME.SlackBuild")
@@ -727,8 +761,7 @@ info_item () {
     APP="$(cat $TMP/sbopkg_item_selection)"
 
     # We need to check and see if the APP has ever been renamed.
-    RAPP=$(grep -w $APP $SBOPKG_RENAMES | cut -d"=" -f1)
-    if [ "$RAPP" == "" ]; then RAPP=$APP ; fi
+    get_old_name RAPP $APP
 
     CATEGORY="$(cat $TMP/sbopkg_category_selection)"
     SHORTPATH=$LOCALREPO/$SLACKVER/$CATEGORY/$APP
@@ -2055,6 +2088,26 @@ add_options () {
     fi
 }
 
+do_install () {
+    # This is mostly equivalent to "upgradepkg --reinstall --install-new $@", but
+    # also checks for renames
+    local PKG PKGNAME
+    local OLDPKG
+
+    for PKG in $@; do
+        # Strip the path from $PKG
+        PKGNAME=${PKG##*/}
+        # Remove version, arch, build and tag
+        PKGNAME=$(rev <<<"$PKGNAME" | cut -d- -f4- |rev)
+
+        get_old_name OLDPKG $PKGNAME
+        if [[ -z $(ls /var/log/packages |grep -x "$OLDPKG-[^-]*-[^-]*-[^-]*") ]]; then
+            OLDPKG=$PKGNAME
+        fi
+        upgradepkg --reinstall --install-new $OLDPKG%$PKG
+    done
+}
+
 install_package () {
     # Install the package.
     INSTPKG=$1
@@ -2081,9 +2134,9 @@ install_package () {
         esac
     fi
     if [ "$INSTALLPKGS" = "1" ]; then
-        upgradepkg --reinstall --install-new $OUTPUT/*
+        do_install $OUTPUT/*
     else
-        upgradepkg --reinstall --install-new $OUTPUT/$INSTPKG
+        do_install $OUTPUT/$INSTPKG
         echo "Done upgrading/installing package."
     fi
 }
-- 
1.6.1.3

From phillip.c.warner at gmail.com  Thu Mar 12 16:00:28 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Thu, 12 Mar 2009 11:00:28 -0500
Subject: [sbopkg-users] renames bugs - sbopkg 0.27.0
In-Reply-To: <da3e877f0903110904xd9109c3o36d8148e839a0d5d@mail.gmail.com>
References: <eded84250903071104i36b666efr4a42ed35416e8489@mail.gmail.com>
	<20090308150230.GB3109@localhost>
	<da3e877f0903090308v721f8ad4t729218dd5ff8bc56@mail.gmail.com>
	<da3e877f0903110904xd9109c3o36d8148e839a0d5d@mail.gmail.com>
Message-ID: <eded84250903120900k4ec77abah4dfe8c137a5cbbd9@mail.gmail.com>

Mauro,

the latest attached patch looks fine, but I don't have time to
thoroughly test it right now.

Another issue that might come up with this renames business is
orphaned .sbopkg files.  When a SlackBuild is renamed the old one is
removed from the repo, but if you have any .sbopkg files in there they
are not migrated over to the new SlackBuild folder.  Perhaps after the
rsync a quick scan can be run to determine if there are any folders
with .sbopkg files that don't have corresponding .SlackBuild files.
If such a folder is found you could be given the option to have those
.sbopkg files moved to the renamed folder (and have the old folder
removed).  The user could then modify the .sbopkg files as needed.

A similar .sbopkg migration might be desired once a new repo
(Slackware 13) is in place.

--phillip

On 3/11/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> The attached patch (on top of r498) fixes the problem here.
> Unless any problems arises, I'd like to commit it this week. I'll also
> think
> about applying a slightly less intrusive patch (not touching info_item and
> the updates code, at least -- suggestions are welcome) to -stable.
>
> --
> Mauro Giachero
>

From mauro.giachero at gmail.com  Thu Mar 12 16:20:12 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Thu, 12 Mar 2009 17:20:12 +0100
Subject: [sbopkg-users] renames bugs - sbopkg 0.27.0
In-Reply-To: <eded84250903120900k4ec77abah4dfe8c137a5cbbd9@mail.gmail.com>
References: <eded84250903071104i36b666efr4a42ed35416e8489@mail.gmail.com>
	<20090308150230.GB3109@localhost>
	<da3e877f0903090308v721f8ad4t729218dd5ff8bc56@mail.gmail.com>
	<da3e877f0903110904xd9109c3o36d8148e839a0d5d@mail.gmail.com>
	<eded84250903120900k4ec77abah4dfe8c137a5cbbd9@mail.gmail.com>
Message-ID: <da3e877f0903120920q2f54e134q44b4a7f814ea95d5@mail.gmail.com>

On Thu, Mar 12, 2009 at 5:00 PM, Phillip Warner
<phillip.c.warner at gmail.com>wrote:

> Mauro,
>
> the latest attached patch looks fine, but I don't have time to
> thoroughly test it right now.


No problem. I'll wait a little more for a review (from anybody). After that,
I can always apply it and wait for the bug reports :-)

Another issue that might come up with this renames business is
> orphaned .sbopkg files.  When a SlackBuild is renamed the old one is
> removed from the repo, but if you have any .sbopkg files in there they
> are not migrated over to the new SlackBuild folder.  Perhaps after the
> rsync a quick scan can be run to determine if there are any folders
> with .sbopkg files that don't have corresponding .SlackBuild files.
> If such a folder is found you could be given the option to have those
> .sbopkg files moved to the renamed folder (and have the old folder
> removed).  The user could then modify the .sbopkg files as needed.


Eh, not as easy/quick as it looks.


> A similar .sbopkg migration might be desired once a new repo
> (Slackware 13) is in place.


I get your points, but I don't think these are realistic features for 0.27.x
or 0.30.0. Your best bet is to open two Enhancement tickets on the issue
tracker, so that your suggestions don't get lost.

-- 
Mauro Giachero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090312/1bb38340/attachment.htm>