From rshepard at appl-ecosys.com  Wed May 20 17:43:34 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 20 May 2020 10:43:34 -0700 (PDT)
Subject: [sbopkg-users] sbopkg issues
Message-ID: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>

I want to learn why when sbopkg builds a file of upgrades it keep listing
python3-PyQt5 when the installed version is the current one which to it
wants to upgrade. And today, it did the same thing with gnucash-3.10 which
I've had installed and running.

TIA,

Rich

From willysr at sbopkg.org  Wed May 20 17:45:02 2020
From: willysr at sbopkg.org (Willy Sudiarto Raharjo)
Date: Thu, 21 May 2020 00:45:02 +0700
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
Message-ID: <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>

> I want to learn why when sbopkg builds a file of upgrades it keep listing
> python3-PyQt5 when the installed version is the current one which to it
> wants to upgrade. And today, it did the same thing with gnucash-3.10 which
> I've had installed and running.

Please check your queue file for that package
perhaps it was an old queue file that hasn't been updated after some
changes in the repository
you can simply regenerate the queue file using sqg -p <packagename>


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20200521/e4174917/attachment.asc>

From rshepard at appl-ecosys.com  Wed May 20 18:02:07 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 20 May 2020 11:02:07 -0700 (PDT)
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
Message-ID: <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>

On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote:

> Please check your queue file for that package
> perhaps it was an old queue file that hasn't been updated after some
> changes in the repository
> you can simply regenerate the queue file using sqg -p <packagename>

Willy,

Queue file is empty. I also took the opportunity to clean out obsolete
sources using the Utility menu of the GUI.

Thanks,

Rich

From willysr at slackbuilds.org  Wed May 20 18:04:53 2020
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 21 May 2020 01:04:53 +0700
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
Message-ID: <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>

>> Please check your queue file for that package
>> perhaps it was an old queue file that hasn't been updated after some
>> changes in the repository
>> you can simply regenerate the queue file using sqg -p <packagename>
> 
> Willy,
> 
> Queue file is empty. I also took the opportunity to clean out obsolete
> sources using the Utility menu of the GUI.

try to regenerate the queue files again first using sqg


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20200521/fe11b2ee/attachment.asc>

From rshepard at appl-ecosys.com  Wed May 20 18:18:33 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 20 May 2020 11:18:33 -0700 (PDT)
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
 <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.2005201118130.17042@salmo.appl-ecosys.com>

On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote:

> try to regenerate the queue files again first using sqg

In progress using sqg -a

Rich

From rshepard at appl-ecosys.com  Wed May 20 20:04:50 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 20 May 2020 13:04:50 -0700 (PDT)
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
 <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>

On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote:

> try to regenerate the queue files again first using sqg

I ran 'sqg -a', went grocery shopping, and eventually it finished all 3726
package. When I open the sbopkg display and select View for the queue it
tells me the queue is empty.

Should I add all installed packages to the queue? I thought that the
queue represents installed packages for which updates are available. And I
should now be up to date.

Regards,

Rich


From krt at 3space.xyz  Wed May 20 20:26:42 2020
From: krt at 3space.xyz (KRT)
Date: Wed, 20 May 2020 14:26:42 -0600
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
 <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
 <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>
Message-ID: <20200520202642.26ee5ed7@Balboa.SkyyNyet>

Howdy,

   I joined the list to chime in, I hope you don't mind my $0.02.

   sqg -a populates the queue directory so that now each package with hard dependencies has a queue file listing these, that's all I use it for.

   Regarding the gnucash situation, it was recently patched without a change in version number, and I think sbopkg picked this up, and is what you noticed.

   
SlackBuilds.org changes for Sat, 16 May 2020 01:45:30 GMT
[...]
office/gnucash: Patched.


   I believe that python3-PyQt5 is a similar situation, those Qt5-related scripts were refactored a few times recently to account for some anomalies.  Yet again, just a build version bump, not a package version bump.  I think that is all you are seeing.

SlackBuilds.org changes for Sun, 03 May 2020 01:49:27 GMT
[...]
libraries/python3-PyQt5: Change python3 include path.

  I could be wrong, but I noticed the same thing when packages get rebuilt for various reasons.

- KRT

On Wed, 20 May 2020 13:04:50 -0700 (PDT)
Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote:
> 
> > try to regenerate the queue files again first using sqg  
> 
> I ran 'sqg -a', went grocery shopping, and eventually it finished all 3726
> package. When I open the sbopkg display and select View for the queue it
> tells me the queue is empty.
> 
> Should I add all installed packages to the queue? I thought that the
> queue represents installed packages for which updates are available. And I
> should now be up to date.
> 
> Regards,
> 
> Rich
> 
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> https://sbopkg.org/mailman/listinfo/sbopkg-users

From rshepard at appl-ecosys.com  Wed May 20 20:41:37 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 20 May 2020 13:41:37 -0700 (PDT)
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <20200520202642.26ee5ed7@Balboa.SkyyNyet>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
 <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
 <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>
 <20200520202642.26ee5ed7@Balboa.SkyyNyet>
Message-ID: <alpine.LNX.2.20.2005201337530.17042@salmo.appl-ecosys.com>

On Wed, 20 May 2020, KRT wrote:

>   I joined the list to chime in, I hope you don't mind my $0.02.

KRT,

Nah, all contributions are welcome.

>   sqg -a populates the queue directory so that now each package with hard
> dependencies has a queue file listing these, that's all I use it for.

Thanks for clarifying.

>   Regarding the gnucash situation, it was recently patched without a
> change in version number, and I think sbopkg picked this up, and is what
> you noticed.

>   I believe that python3-PyQt5 is a similar situation, those Qt5-related
> scripts were refactored a few times recently to account for some
> anomalies. Yet again, just a build version bump, not a package version
> bump. I think that is all you are seeing.

>  I could be wrong, but I noticed the same thing when packages get rebuilt
> for various reasons.

When the weekly update lists arrive in my inbox I quickly scan them, but let
sbopkg find the one's installed here needing updates so I don't see the
reason for the package's placement on the list.

>From now on, when I see a package on the queue process list that is the same
version as is installed here I'll check the e-mail and de-select it for
processing.

Thanks for the chimes,

Rich

From willysr at slackbuilds.org  Thu May 21 01:49:55 2020
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 21 May 2020 08:49:55 +0700
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
 <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
 <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>
Message-ID: <3d1fb592-2aea-d7b5-dd9d-3d075de920e5@slackbuilds.org>

> I ran 'sqg -a', went grocery shopping, and eventually it finished all 3726
> package. When I open the sbopkg display and select View for the queue it
> tells me the queue is empty.
> 
> Should I add all installed packages to the queue? I thought that the
> queue represents installed packages for which updates are available. And I
> should now be up to date.

Oh, i misunderstand your questions Rich
i thought it was dealing with queue files (generated by sqg), but
instead you mean as build queue (which is standard operation by sbopkg).
Sorry for that.

Yes, as KRT mentioned, if sbopkg find a different VERSION OR BUILD, it
will add it to the queue to build. You can simply check it on
https://git.slackbuilds.org/slackbuilds/ to see whether you need to
rebuild or not. In this case, for gnucash, it's here:
https://git.slackbuilds.org/slackbuilds/commit/?id=9c270f89fd886c80e031ff3930f3c923a9f6abb4

As you can see, the maintainer decided to bump the BUILD number to 2, so
sbopkg will detect this and add it to list of updates.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20200521/0684443d/attachment.asc>

From rshepard at appl-ecosys.com  Thu May 21 12:41:48 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 21 May 2020 05:41:48 -0700 (PDT)
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <3d1fb592-2aea-d7b5-dd9d-3d075de920e5@slackbuilds.org>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
 <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
 <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>
 <3d1fb592-2aea-d7b5-dd9d-3d075de920e5@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.2005210538280.2661@salmo.appl-ecosys.com>

On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote:

> Oh, i misunderstand your questions Rich i thought it was dealing with
> queue files (generated by sqg), but instead you mean as build queue (which
> is standard operation by sbopkg). Sorry for that.

Willy,

E-mail communications are easier to mis-read than are face-to-face oral
communications. Apology not necessary.

> Yes, as KRT mentioned, if sbopkg find a different VERSION OR BUILD, it
> will add it to the queue to build. You can simply check it on
> https://git.slackbuilds.org/slackbuilds/ to see whether you need to
> rebuild or not. In this case, for gnucash, it's here:
> https://git.slackbuilds.org/slackbuilds/commit/?id=9c270f89fd886c80e031ff3930f3c923a9f6abb4
>
> As you can see, the maintainer decided to bump the BUILD number to 2, so
> sbopkg will detect this and add it to list of updates.

Thank you. This confirms that when I see a package on the list of updates
with the same version number as the installed package I'll just unselect it.
A build number change for the same application version is not important to
me.

Stay well,

Rich

From yalhcru at gmail.com  Thu May 21 18:22:51 2020
From: yalhcru at gmail.com (B Watson)
Date: Thu, 21 May 2020 14:22:51 -0400
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <alpine.LNX.2.20.2005210538280.2661@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
 <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
 <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>
 <3d1fb592-2aea-d7b5-dd9d-3d075de920e5@slackbuilds.org>
 <alpine.LNX.2.20.2005210538280.2661@salmo.appl-ecosys.com>
Message-ID: <CAN1hMuCQif-0bJ=gBOiu4oC2z=vT40hWsRP2HWpOZ77x9OcKjw@mail.gmail.com>

On 5/21/20, Rich Shepard <rshepard at appl-ecosys.com> wrote:

> A build number change for the same application version is not important to
> me.

It depends on why the build number changed.

If the script maintainer applied a patch that fixes a security
vulnerability, for instance. Or just a bugfix for a bug that you don't
happen to have bitten by yet.

If it's a library package, maybe the new build fixes a build issue with
some application that uses the library, that you might someday want
to install.

The person who changed that build number thought it was important enough
to go to the trouble of changing it... probably worth at least reading
the commit message to see what the change was for.

From rshepard at appl-ecosys.com  Thu May 21 18:57:13 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 21 May 2020 11:57:13 -0700 (PDT)
Subject: [sbopkg-users] sbopkg issues
In-Reply-To: <CAN1hMuCQif-0bJ=gBOiu4oC2z=vT40hWsRP2HWpOZ77x9OcKjw@mail.gmail.com>
References: <alpine.LNX.2.20.2005201042200.17042@salmo.appl-ecosys.com>
 <ef249d08-c32b-5117-f2f8-258424ae1be6@sbopkg.org>
 <alpine.LNX.2.20.2005201100480.17042@salmo.appl-ecosys.com>
 <e988fd7b-1b07-8407-506a-695bf305cd04@slackbuilds.org>
 <alpine.LNX.2.20.2005201258080.17042@salmo.appl-ecosys.com>
 <3d1fb592-2aea-d7b5-dd9d-3d075de920e5@slackbuilds.org>
 <alpine.LNX.2.20.2005210538280.2661@salmo.appl-ecosys.com>
 <CAN1hMuCQif-0bJ=gBOiu4oC2z=vT40hWsRP2HWpOZ77x9OcKjw@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.2005211153470.2661@salmo.appl-ecosys.com>

On Thu, 21 May 2020, B Watson wrote:

> If the script maintainer applied a patch that fixes a security
> vulnerability, for instance. Or just a bugfix for a bug that you don't
> happen to have bitten by yet.

B.

This makes sense. My experiences have been that such adjustments by the
application developer results in a sub-minor version change. GnuCash did
this recently when some bug fixes broke the Windows version (they added a
fourth digit to the verson number), then fixed all the issues and released a
new minor version, dropping the last digit.

> The person who changed that build number thought it was important enough
> to go to the trouble of changing it... probably worth at least reading the
> commit message to see what the change was for.

Good advice.

Thanks,

Rich