From me at alkos333.net  Thu Jun 17 13:43:41 2010
From: me at alkos333.net (alkos333)
Date: Thu, 17 Jun 2010 08:43:41 -0500
Subject: [sbopkg-users] abiword & Update Function
Message-ID: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com>

I have abiword 2.8.4 installed and every since I updated to it, the
Update function would flag abiword, saying there is 2.8.5-noarch
available for an update, which isn't the case.  Anybody experienced
anything similar?

From pwcazenave at gmail.com  Thu Jun 17 13:57:03 2010
From: pwcazenave at gmail.com (Pierre Cazenave)
Date: Thu, 17 Jun 2010 14:57:03 +0100
Subject: [sbopkg-users] abiword & Update Function
In-Reply-To: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com>
References: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com>
Message-ID: <4C1A29AF.5050906@gmail.com>

The latest abiword version on SlackBuilds.org is indeed 2.8.5:

http://slackbuilds.org/repository/13.1/office/abiword/

Not sure what the noarch bit is about, though...

Pierre

On 17/06/2010 14:43, alkos333 wrote:
> I have abiword 2.8.4 installed and every since I updated to it, the
> Update function would flag abiword, saying there is 2.8.5-noarch
> available for an update, which isn't the case.  Anybody experienced
> anything similar? _______________________________________________
> sbopkg-users mailing list sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users


From me at alkos333.net  Thu Jun 17 14:16:27 2010
From: me at alkos333.net (alkos333)
Date: Thu, 17 Jun 2010 09:16:27 -0500
Subject: [sbopkg-users] abiword & Update Function
In-Reply-To: <4C1A29AF.5050906@gmail.com>
References: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com> 
	<4C1A29AF.5050906@gmail.com>
Message-ID: <AANLkTim-vQpwdv4FQvS7Adfn-Trrxq7Y3Zy77sow4_GR@mail.gmail.com>

On Thu, Jun 17, 2010 at 8:57 AM, Pierre Cazenave <pwcazenave at gmail.com> wrote:
> The latest abiword version on SlackBuilds.org is indeed 2.8.5:

Hmm.. odd.  last time I checked it was still 2.8.4, guess it got updated indeed.

The 'noarch' tag is, indeed, confusing.

From chess at chessgriffin.com  Thu Jun 17 14:22:07 2010
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 17 Jun 2010 10:22:07 -0400
Subject: [sbopkg-users] abiword & Update Function
In-Reply-To: <AANLkTim-vQpwdv4FQvS7Adfn-Trrxq7Y3Zy77sow4_GR@mail.gmail.com>
References: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com>
	<4C1A29AF.5050906@gmail.com>
	<AANLkTim-vQpwdv4FQvS7Adfn-Trrxq7Y3Zy77sow4_GR@mail.gmail.com>
Message-ID: <20100617142207.GA24451@localhost>

* alkos333 <me at alkos333.net> [2010-06-17 09:16:27]:

> On Thu, Jun 17, 2010 at 8:57 AM, Pierre Cazenave
> <pwcazenave at gmail.com> wrote:
> > The latest abiword version on SlackBuilds.org is indeed 2.8.5:
> 
> Hmm.. odd.  last time I checked it was still 2.8.4, guess it got
> updated indeed.
> 
> The 'noarch' tag is, indeed, confusing.

What version of sbopkg are you using?  That was a cosmetic bug on x86_64
that fixed quite awhile ago.  Updating to the latest release should fix
it.

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

From baildon.research at googlemail.com  Thu Jun 17 16:05:39 2010
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 17 Jun 2010 17:05:39 +0100
Subject: [sbopkg-users] noarch updates, was abiword & Update Function
Message-ID: <AANLkTilUyyzDIfPeN2Do_08mp-To8kP3g6HzdGh_ULUe@mail.gmail.com>

>> The 'noarch' tag is, indeed, confusing.
>
> What version of sbopkg are you using? ?That was a cosmetic bug on x86_64
> that fixed quite awhile ago. ?Updating to the latest release should fix
> it.

I'm getting it too.  Looks like the new template changes have royally
broken the grep for ^ARCH= in check_for_updates().  See, for example,
the attached set of potential updates (on an i686 box), where packages
with an explicitly invariant ARCH (GoogleEarth, apache_ant, skype) are
correct but subsequent packages tend to just pick up whatever ARCH the
previous package had.

Fixing it looks *difficult* :-(

-Dave Spencer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sbopkg_updatelist
Type: application/octet-stream
Size: 2451 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20100617/104a0d4b/attachment.obj>

From chess at chessgriffin.com  Thu Jun 17 16:20:36 2010
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 17 Jun 2010 12:20:36 -0400
Subject: [sbopkg-users] noarch updates, was abiword & Update Function
In-Reply-To: <AANLkTilUyyzDIfPeN2Do_08mp-To8kP3g6HzdGh_ULUe@mail.gmail.com>
References: <AANLkTilUyyzDIfPeN2Do_08mp-To8kP3g6HzdGh_ULUe@mail.gmail.com>
Message-ID: <20100617162036.GA6304@localhost>

* David Spencer <baildon.research at googlemail.com> [2010-06-17 17:05:39]:

> >> The 'noarch' tag is, indeed, confusing.
> >
> > What version of sbopkg are you using? ?That was a cosmetic bug on x86_64
> > that fixed quite awhile ago. ?Updating to the latest release should fix
> > it.
> 
> I'm getting it too.  Looks like the new template changes have royally
> broken the grep for ^ARCH= in check_for_updates().  See, for example,
> the attached set of potential updates (on an i686 box), where packages
> with an explicitly invariant ARCH (GoogleEarth, apache_ant, skype) are
> correct but subsequent packages tend to just pick up whatever ARCH the
> previous package had.
> 
> Fixing it looks *difficult* :-(
> 
> -Dave Spencer

Dave,

Can you open up a root terminal and edit line 707 of /usr/sbin/sbopkg
and add ARCH to the unset before BUILD, so it looks like this:

unset ARCH BUILD

Then, rerun the update and copy and paste the output into a new text
file.  You can then quit sbopkg and change line 707 back.

Thanks!

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

From marc321 at gmail.com  Thu Jun 17 17:01:10 2010
From: marc321 at gmail.com (Marc Payne)
Date: Thu, 17 Jun 2010 11:01:10 -0600
Subject: [sbopkg-users] abiword & Update Function
In-Reply-To: <20100617142207.GA24451@localhost>
References: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com>
	<4C1A29AF.5050906@gmail.com>
	<AANLkTim-vQpwdv4FQvS7Adfn-Trrxq7Y3Zy77sow4_GR@mail.gmail.com>
	<20100617142207.GA24451@localhost>
Message-ID: <AANLkTikVCZ5wDvF0RmsgojTzfnqCuVh68tzU6W5WfC3T@mail.gmail.com>

I ran some updates this morning and experienced the same issue that
alkos333 described, using sbopkg 0.33.1. Several packages were flagged
with x.y.z-noarch (graveman and yasm are a couple examples). After
building, the packages had the correct arch of i486, so it seems there
may still be a cosmetic bug lurking in the shadows.

When I have the time, I may try recreating the issue with debugging on.

root at slackbox:~# sbopkg -v
0.33.1

Marc

From me at alkos333.net  Thu Jun 17 18:02:13 2010
From: me at alkos333.net (alkos333)
Date: Thu, 17 Jun 2010 13:02:13 -0500
Subject: [sbopkg-users] abiword & Update Function
In-Reply-To: <20100617142207.GA24451@localhost>
References: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com> 
	<4C1A29AF.5050906@gmail.com>
	<AANLkTim-vQpwdv4FQvS7Adfn-Trrxq7Y3Zy77sow4_GR@mail.gmail.com> 
	<20100617142207.GA24451@localhost>
Message-ID: <AANLkTin64B9z5nJXlr_jWm-c076SfHtdMUv7FBqytqBI@mail.gmail.com>

On Thu, Jun 17, 2010 at 9:22 AM, Chess Griffin <chess at chessgriffin.com> wrote:
> What version of sbopkg are you using? ?That was a cosmetic bug on x86_64
> that fixed quite awhile ago. ?Updating to the latest release should fix

0.33.1

From chess at chessgriffin.com  Thu Jun 17 18:08:13 2010
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 17 Jun 2010 14:08:13 -0400
Subject: [sbopkg-users] abiword & Update Function
In-Reply-To: <AANLkTikVCZ5wDvF0RmsgojTzfnqCuVh68tzU6W5WfC3T@mail.gmail.com>
References: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com>
	<4C1A29AF.5050906@gmail.com>
	<AANLkTim-vQpwdv4FQvS7Adfn-Trrxq7Y3Zy77sow4_GR@mail.gmail.com>
	<20100617142207.GA24451@localhost>
	<AANLkTikVCZ5wDvF0RmsgojTzfnqCuVh68tzU6W5WfC3T@mail.gmail.com>
Message-ID: <20100617180813.GA13513@localhost>

* Marc Payne <marc321 at gmail.com> [2010-06-17 11:01:10]:

> I ran some updates this morning and experienced the same issue that
> alkos333 described, using sbopkg 0.33.1. Several packages were flagged
> with x.y.z-noarch (graveman and yasm are a couple examples). After
> building, the packages had the correct arch of i486, so it seems there
> may still be a cosmetic bug lurking in the shadows.
> 

Yes, this is a cosmetic issue -- the resulting packages will have the
ccrrect ARCH.

The line 707 fix is not the complete answer but we're working on it.
Thanks for the reports, everyone.

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

From rw at rlworkman.net  Thu Jun 17 19:00:34 2010
From: rw at rlworkman.net (Robby Workman)
Date: Thu, 17 Jun 2010 14:00:34 -0500
Subject: [sbopkg-users] abiword & Update Function
In-Reply-To: <20100617180813.GA13513@localhost>
References: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com>
	<4C1A29AF.5050906@gmail.com>
	<AANLkTim-vQpwdv4FQvS7Adfn-Trrxq7Y3Zy77sow4_GR@mail.gmail.com>
	<20100617142207.GA24451@localhost>
	<AANLkTikVCZ5wDvF0RmsgojTzfnqCuVh68tzU6W5WfC3T@mail.gmail.com>
	<20100617180813.GA13513@localhost>
Message-ID: <20100617140034.38e8fe58@liberty.rlwhome.lan>

On Thu, 17 Jun 2010 14:08:13 -0400
Chess Griffin <chess at chessgriffin.com> wrote:

> * Marc Payne <marc321 at gmail.com> [2010-06-17 11:01:10]:
> 
> > I ran some updates this morning and experienced the same issue that
> > alkos333 described, using sbopkg 0.33.1. Several packages were
> > flagged with x.y.z-noarch (graveman and yasm are a couple
> > examples). After building, the packages had the correct arch of
> > i486, so it seems there may still be a cosmetic bug lurking in the
> > shadows.
> > 
> 
> Yes, this is a cosmetic issue -- the resulting packages will have the
> ccrrect ARCH.
> 
> The line 707 fix is not the complete answer but we're working on it.
> Thanks for the reports, everyone.
> 


Maybe I'm overlooking something, but aside from having an
UNSUPPORTED value of DOWNLOAD_x86_64 or MD5SUM_x86_64 in the
.info file for the app, I don't see why you wouldn't just
return the ARCH of the running system.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20100617/2e5b135a/attachment.asc>

From chess at chessgriffin.com  Thu Jun 17 19:16:56 2010
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 17 Jun 2010 15:16:56 -0400
Subject: [sbopkg-users] abiword & Update Function
In-Reply-To: <20100617140034.38e8fe58@liberty.rlwhome.lan>
References: <AANLkTikq6yjUA9JVeMF1O9hluUNoBpMG3mwI9UjeioyZ@mail.gmail.com>
	<4C1A29AF.5050906@gmail.com>
	<AANLkTim-vQpwdv4FQvS7Adfn-Trrxq7Y3Zy77sow4_GR@mail.gmail.com>
	<20100617142207.GA24451@localhost>
	<AANLkTikVCZ5wDvF0RmsgojTzfnqCuVh68tzU6W5WfC3T@mail.gmail.com>
	<20100617180813.GA13513@localhost>
	<20100617140034.38e8fe58@liberty.rlwhome.lan>
Message-ID: <20100617191656.GA11132@localhost>

* Robby Workman <rw at rlworkman.net> [2010-06-17 14:00:34]:

> On Thu, 17 Jun 2010 14:08:13 -0400
> Chess Griffin <chess at chessgriffin.com> wrote:
> 
> > * Marc Payne <marc321 at gmail.com> [2010-06-17 11:01:10]:
> > 
> > > I ran some updates this morning and experienced the same issue that
> > > alkos333 described, using sbopkg 0.33.1. Several packages were
> > > flagged with x.y.z-noarch (graveman and yasm are a couple
> > > examples). After building, the packages had the correct arch of
> > > i486, so it seems there may still be a cosmetic bug lurking in the
> > > shadows.
> > > 
> > 
> > Yes, this is a cosmetic issue -- the resulting packages will have the
> > ccrrect ARCH.
> > 
> > The line 707 fix is not the complete answer but we're working on it.
> > Thanks for the reports, everyone.
> > 
> 
> 
> Maybe I'm overlooking something, but aside from having an
> UNSUPPORTED value of DOWNLOAD_x86_64 or MD5SUM_x86_64 in the
> .info file for the app, I don't see why you wouldn't just
> return the ARCH of the running system.
> 

Yes, we had considered that but it would provide incorrect information
in the case of SlackBuild scripts with hardcoded ARCH information, or
'noarch' and the like.  So we've tried to be fancy by eval'ing the ARCH
in the SlackBuild script to provide a more accurate output.

We might end up just using the system's ARCH, or inserting a
'placeholder' like 'ARCH', or just removing the ARCH from the string of
installed and updated packages since it really is not that relevant to
the actual determination of whether an APP is at $VERSION or $VERSION+1.

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

From chess at chessgriffin.com  Thu Jun 17 20:57:01 2010
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 17 Jun 2010 16:57:01 -0400
Subject: [sbopkg-users] noarch updates, was abiword & Update Function
In-Reply-To: <AANLkTikr0fLBJZz7GgKjNNg42PKzsIlLsEk1iXuFyl1J@mail.gmail.com>
References: <AANLkTilUyyzDIfPeN2Do_08mp-To8kP3g6HzdGh_ULUe@mail.gmail.com>
	<20100617162036.GA6304@localhost>
	<AANLkTikr0fLBJZz7GgKjNNg42PKzsIlLsEk1iXuFyl1J@mail.gmail.com>
Message-ID: <20100617205701.GA20264@localhost>

* David Spencer <baildon.research at googlemail.com> [2010-06-17 17:43:42]:

> > Can you open up a root terminal and edit line 707 of /usr/sbin/sbopkg
> > and add ARCH to the unset before BUILD, so it looks like this:
> >
> > unset ARCH BUILD
> >
> > Then, rerun the update and copy and paste the output into a new text
> > file. ?You can then quit sbopkg and change line 707 back.
> 
> An impressive instant response, Chess!  Obviously this is a cosmetic
> problem, and not urgent, but thanks for taking it seriously.
> 
> That edit has changed a few of the NEWARCHes to 'unknown' but most of
> them are 'noarch'.
> 

David, do you mind testing one more possible fix?  Change that unset
ARCH to NEWARCH, so line 707 would read:

unset BUILD NEWARCH

Thanks!

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