From diniz.bortolotto at gmail.com  Sat Feb 27 02:02:53 2021
From: diniz.bortolotto at gmail.com (Diniz Bortolotto)
Date: Fri, 26 Feb 2021 23:02:53 -0300
Subject: [sbopkg-users] Fwd: sqg not respects sbopkg.conf REPOs (warning:
 very long e-mail)
In-Reply-To: <CAEbqFbUiBjKbwNbkEMhqMLV8guBZmETR+W7EBLkNbpHDzAMjzQ@mail.gmail.com>
References: <CAEbqFbUiBjKbwNbkEMhqMLV8guBZmETR+W7EBLkNbpHDzAMjzQ@mail.gmail.com>
Message-ID: <CAEbqFbU2U1OrTmoPSSG8dtd6frC6SxGFmzSKOVcOZ0yxMJgscg@mail.gmail.com>

Resending because size constraingt
Removed PNG trying jpg attachment

Best Regards,

Diniz Bortolotto



---------- Forwarded message ---------
De: Diniz Bortolotto <diniz.bortolotto at gmail.com>
Date: sex., 26 de fev. de 2021 ?s 22:43
Subject: sqg not respects sbopkg.conf REPOs (warning: very long e-mail)
To: <sbopkg-users at sbopkg.org>


Hi buddies!

My name is Diniz Bortolotto and I'm a Slackware64-current user.
Some days ago I changed my SBo default repository on sbopkg to Ponce's
repository to get current compliant packages.

After that, I noticed that some *SBo Queues* should be updated to keep
track of correct dependencies of the new repository.
I started a full update and after that noticed that it didn't work.
Studying the *sqg* script and BASH rules maybe I identified a
misunderstanding of source command and substitutions.

I think that error occurs because when we use a command substitution (like
*${...}* construct), we are creating a subshell that could inherit
variables from their parent shells, but this only works in one way and the
subshell cannot modify the environment of its parent shell (*sqg* in this
case).

I've made some changes to *sqg script* to test cases and after those tests
my suggestion is to *REMOVE REPOs variables* of sqg. (patch attached) I
also created two sbopkg.confs to test and added an option to show what I
wanna explain. (patch of test if someone want also try it)

Below I tried to make a graphical explanation of what I got on tests. :-)
Note that the third case is the default sqg and it should use REPOs in
sbopkg.conf not the sqg's defined.
*Sent a JPG attached.*

Below some test cases output:

First I created some test dirs to pass ok on sanity checks

root at darkstar:/usr/sbin# tree -fi /var/lib/sbopkg/sbo*

/var/lib/sbopkg/sbo_root_str

/var/lib/sbopkg/sbo_root_str/queue_str

/var/lib/sbopkg/sbo_root_str/repo_str

/var/lib/sbopkg/sbo_root_str/repo_str/branch_str

/var/lib/sbopkg/sbo_root_var

/var/lib/sbopkg/sbo_root_var/queue_var

/var/lib/sbopkg/sbo_root_var/repo_var

/var/lib/sbopkg/sbo_root_var/repo_var/branch_var


Test Cases:
1 - SBOPKG_CONF "BLANK" (commented out with '#') and REPOs also commented
on sqg: *(fail)*

root at darkstar:~# sqg -s
>
> SQG's vars before sanity checks:
>      SQG's SBOPKG_CONF..:
>      SQG's REPO_ROOT....:
>      SQG's REPO_NAME....:
>      SQG's REPO_BRANCH..:
>
> Doing sanity checks ...
> not found.
> Check the configurable variables at the top of the script.

2 - SBOPKG_CONF "BLANK" (commented out with '#') and REPOs defined on sqg:
*(fail)*

root at darkstar:~# sqg -s
>
> SQG's vars before sanity checks:
>      SQG's SBOPKG_CONF..:
>      SQG's REPO_ROOT....: /var/lib/sbopkg
>      SQG's REPO_NAME....: SBo
>      SQG's REPO_BRANCH..: 14.2
>
> Doing sanity checks ...
> not found.
> Check the configurable variables at the top of the script.
>
*3 - SBOPKG_CONF defined on sqg using substitution variables and REPOs
defined on sqg (default)*
*>>>> this is the behaviour that I first detected:  (wrong)*

root at darkstar:~# sqg -s
>
> SQG's vars before sanity checks:
>      SQG's SBOPKG_CONF..: /etc/sbopkg/sbopkg.conf_var
>      SQG's REPO_ROOT....: /var/lib/sbopkg
>      SQG's REPO_NAME....: SBo
>      SQG's REPO_BRANCH..: 14.2
>
> Doing sanity checks ...
>
> SQG's vars after sanity checks':
> (that includes a 'source /etc/sbopkg/sbopkg.conf_var')
>      SQG's REPO_ROOT....: /var/lib/sbopkg
>      SQG's REPO_NAME....: SBo
>      SQG's REPO_BRANCH..: 14.2
>
> SBo's vars (using grep to /etc/sbopkg/sbopkg.conf_var):
> getting all that came after '=' sign
>
>      SBo's REPO_ROOT....: ${REPO_ROOT:-/var/lib/sbopkg/sbo_root_var}
>      SBo's REPO_NAME....: ${REPO_NAME:-repo_var}
>      SBo's REPO_BRANCH..: ${REPO_BRANCH:-branch_var}
> Done.
>
4 - SBOPKG_CONF defined on sqg using substitution variables and REPOs
commented on sqg: (OK)

root at darkstar:~# sqg -s
>
> SQG's vars before sanity checks:
>      SQG's SBOPKG_CONF..: /etc/sbopkg/sbopkg.conf_var
>      SQG's REPO_ROOT....:
>      SQG's REPO_NAME....:
>      SQG's REPO_BRANCH..:
>
> Doing sanity checks ...
>
> SQG's vars after sanity checks':
> (that includes a 'source /etc/sbopkg/sbopkg.conf_var')
>      SQG's REPO_ROOT....: /var/lib/sbopkg/sbo_root_var
>      SQG's REPO_NAME....: repo_var
>      SQG's REPO_BRANCH..: branch_var
>
> SBo's vars (using grep to /etc/sbopkg/sbopkg.conf_var):
> getting all that came after '=' sign
>
>      SBo's REPO_ROOT....: ${REPO_ROOT:-/var/lib/sbopkg/sbo_root_var}
>      SBo's REPO_NAME....: ${REPO_NAME:-repo_var}
>      SBo's REPO_BRANCH..: ${REPO_BRANCH:-branch_var}
> Done.
>
5 - SBOPKG_CONF defined on sqg with fixed variables and REPOs commented on
sqg: (OK)

root at darkstar:~# sqg -s
>
> SQG's vars before sanity checks:
>      SQG's SBOPKG_CONF..: /etc/sbopkg/sbopkg.conf_str
>      SQG's REPO_ROOT....:
>      SQG's REPO_NAME....:
>      SQG's REPO_BRANCH..:
>
> Doing sanity checks ...
>
> SQG's vars after sanity checks':
> (that includes a 'source /etc/sbopkg/sbopkg.conf_str')
>      SQG's REPO_ROOT....: /var/lib/sbopkg/sbo_root_str
>      SQG's REPO_NAME....: repo_str
>      SQG's REPO_BRANCH..: branch_str
>
> SBo's vars (using grep to /etc/sbopkg/sbopkg.conf_str):
> getting all that came after '=' sign
>
>      SBo's REPO_ROOT....: /var/lib/sbopkg/sbo_root_str
>      SBo's REPO_NAME....: repo_str
>      SBo's REPO_BRANCH..: branch_str
> Done.
>
6 - SBOPKG_CONF defined on sqg with fixed variables and REPOs defined on
sqg: (OK)

root at darkstar:~# sqg -s
>
> SQG's vars before sanity checks:
>      SQG's SBOPKG_CONF..: /etc/sbopkg/sbopkg.conf_str
>      SQG's REPO_ROOT....: /var/lib/sbopkg
>      SQG's REPO_NAME....: SBo
>      SQG's REPO_BRANCH..: 14.2
>
> Doing sanity checks ...
>
> SQG's vars after sanity checks':
> (that includes a 'source /etc/sbopkg/sbopkg.conf_str')
>      SQG's REPO_ROOT....: /var/lib/sbopkg/sbo_root_str
>      SQG's REPO_NAME....: repo_str
>      SQG's REPO_BRANCH..: branch_str
>
> SBo's vars (using grep to /etc/sbopkg/sbopkg.conf_str):
> getting all that came after '=' sign
>
>      SBo's REPO_ROOT....: /var/lib/sbopkg/sbo_root_str
>      SBo's REPO_NAME....: repo_str
>      SBo's REPO_BRANCH..: branch_str
> Done.
>

Best Regards,
Diniz Bortolotto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20210226/69d054d1/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sqg.patch
Type: application/x-patch
Size: 882 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20210226/69d054d1/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sqg.test.patch
Type: application/x-patch
Size: 1853 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20210226/69d054d1/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sqg parms graph.jpg
Type: image/jpeg
Size: 82111 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20210226/69d054d1/attachment-0001.jpg>

From willysr at slackbuilds.org  Sat Feb 27 02:23:31 2021
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 27 Feb 2021 09:23:31 +0700
Subject: [sbopkg-users] Fwd: sqg not respects sbopkg.conf REPOs
 (warning: very long e-mail)
In-Reply-To: <CAEbqFbU2U1OrTmoPSSG8dtd6frC6SxGFmzSKOVcOZ0yxMJgscg@mail.gmail.com>
References: <CAEbqFbUiBjKbwNbkEMhqMLV8guBZmETR+W7EBLkNbpHDzAMjzQ@mail.gmail.com>
 <CAEbqFbU2U1OrTmoPSSG8dtd6frC6SxGFmzSKOVcOZ0yxMJgscg@mail.gmail.com>
Message-ID: <776eb61f-4207-fccb-1b45-00c52ae8e8a3@slackbuilds.org>

> My name is Diniz Bortolotto and I'm a Slackware64-current user.
> Some days ago I changed my SBo default repository on sbopkg to Ponce's
> repository to get current compliant packages.
> 
> After that, I noticed that some *SBo Queues* should be updated to keep
> track of correct dependencies of the new repository.
> I started a full update and after that noticed that it didn't work.
> Studying the *sqg* script and BASH rules maybe I identified a
> misunderstanding of source command and substitutions.
> 
> I think that error occurs because when we use a command substitution (like
> *${...}* construct), we are creating a subshell that could inherit
> variables from their parent shells, but this only works in one way and the
> subshell cannot modify the environment of its parent shell (*sqg* in this
> case).
> 
> I've made some changes to *sqg script* to test cases and after those tests
> my suggestion is to *REMOVE REPOs variables* of sqg. (patch attached) I
> also created two sbopkg.confs to test and added an option to show what I
> wanna explain. (patch of test if someone want also try it)
> 
> Below I tried to make a graphical explanation of what I got on tests. :-)
> Note that the third case is the default sqg and it should use REPOs in
> sbopkg.conf not the sqg's defined.

Hi Diniz

You should try this version instead :)
https://sbopkg.org/test/sbopkg-0.38.2-noarch-1_wsr.tgz

make sure to change the REPO version to 14.2 first since 15.0 isn't
available yet.


-- 
Willy Sudiarto Raharjo

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

From diniz.bortolotto at gmail.com  Sat Feb 27 02:46:08 2021
From: diniz.bortolotto at gmail.com (Diniz Bortolotto)
Date: Fri, 26 Feb 2021 23:46:08 -0300
Subject: [sbopkg-users] Fwd: sqg not respects sbopkg.conf REPOs
 (warning: very long e-mail)
In-Reply-To: <776eb61f-4207-fccb-1b45-00c52ae8e8a3@slackbuilds.org>
References: <CAEbqFbUiBjKbwNbkEMhqMLV8guBZmETR+W7EBLkNbpHDzAMjzQ@mail.gmail.com>
 <CAEbqFbU2U1OrTmoPSSG8dtd6frC6SxGFmzSKOVcOZ0yxMJgscg@mail.gmail.com>
 <776eb61f-4207-fccb-1b45-00c52ae8e8a3@slackbuilds.org>
Message-ID: <CAEbqFbW-C58Dp000oKJH4VYNWbtEDRcbp5MvyqSYEi-48yDkVQ@mail.gmail.com>

Hi Willy!

Thanks a lot for your prompt answer. I will try this test version for shure.
Sorry for that long e-mail. I just wanted to make myself clear.

Best Regards,

Diniz Bortolotto



Em sex., 26 de fev. de 2021 ?s 23:23, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> escreveu:

> > My name is Diniz Bortolotto and I'm a Slackware64-current user.
> > Some days ago I changed my SBo default repository on sbopkg to Ponce's
> > repository to get current compliant packages.
> >
> > After that, I noticed that some *SBo Queues* should be updated to keep
> > track of correct dependencies of the new repository.
> > I started a full update and after that noticed that it didn't work.
> > Studying the *sqg* script and BASH rules maybe I identified a
> > misunderstanding of source command and substitutions.
> >
> > I think that error occurs because when we use a command substitution
> (like
> > *${...}* construct), we are creating a subshell that could inherit
> > variables from their parent shells, but this only works in one way and
> the
> > subshell cannot modify the environment of its parent shell (*sqg* in this
> > case).
> >
> > I've made some changes to *sqg script* to test cases and after those
> tests
> > my suggestion is to *REMOVE REPOs variables* of sqg. (patch attached) I
> > also created two sbopkg.confs to test and added an option to show what I
> > wanna explain. (patch of test if someone want also try it)
> >
> > Below I tried to make a graphical explanation of what I got on tests. :-)
> > Note that the third case is the default sqg and it should use REPOs in
> > sbopkg.conf not the sqg's defined.
>
> Hi Diniz
>
> You should try this version instead :)
> https://sbopkg.org/test/sbopkg-0.38.2-noarch-1_wsr.tgz
>
> make sure to change the REPO version to 14.2 first since 15.0 isn't
> available yet.
>
>
> --
> Willy Sudiarto Raharjo
>
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> https://sbopkg.org/mailman/listinfo/sbopkg-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20210226/8190a033/attachment.htm>

From diniz.bortolotto at gmail.com  Sun Feb 28 19:41:15 2021
From: diniz.bortolotto at gmail.com (Diniz Bortolotto)
Date: Sun, 28 Feb 2021 16:41:15 -0300
Subject: [sbopkg-users] sbopkg 0.38.2 + SBo-git not considering *.sbopkg
 files
Message-ID: <CAEbqFbVqXWAWcXFhm5PrKp+aovONd3ZN+GRoemmhgQ0peyTHJw@mail.gmail.com>

Hi buddies!
It's me again! :-)

Today I'm testing sbopkg 0.38.2 (with Ponce's SBo-git repo) and noticed
that when trying to use a "Local" pkg.info.sbopkg it was ignored/deleted
and I couldn't figure out how to correct it.
I also tried  to do the same using sbopkg 0.38.1 and also didn't work. So,
I could assume that it's something related to the git portion of the sbopkg
code.
Could someone explain that? :)

If someone wants to try/check, here is the spotify.info.sbopkg content:

root at darkstar:~# cat
> /var/lib/sbopkg/SBo/14.2/multimedia/spotify/spotify.info.sbopkg
> PRGNAM="spotify"
> VERSION="1.1.42"
> HOMEPAGE="https://www.spotify.com"
> DOWNLOAD="
> http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.72.117.g6bd7c
> c73-35_i386.deb"
> MD5SUM="c8e54d60452bda40f6de23f11c909b2d"
> DOWNLOAD_x86_64="
> http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622
> .gbd112320-37_amd64.deb"
> MD5SUM_x86_64="9c9cbd30bac795b8ca71643de9d2d719"
> REQUIRES=""
> MAINTAINER="DhabyX"
> EMAIL="slack.dhabyx at gmail.com"
>

Below a small example of what happened:

Here we could see the original content of directory:

root at darkstar:~/sbolibs/multimedia/spotify# ls -1
> README

doinst.sh

slack-desc

spotify.SlackBuild

spotify.info
>

So, I created *.sbopkg files with new version to build:

root at darkstar:~/sbolibs/multimedia/spotify# ls -1
> README
> doinst.sh
> slack-desc
> spotify.SlackBuild
> spotify.SlackBuild.sbopkg
> spotify.info
> spotify.info.sbopkg


Now a diff to show that I'm trying to create a new version of this package
(1.1.42):

root at darkstar:~/sbolibs/multimedia/spotify# diff spotify.SlackBuild
> spotify.SlackBuild.sbopkg
> 31c31
> < VERSION32=${VERSION32:-1.0.72}
> ---
> > VERSION32=${VERSION32:-1.1.42}



Here I just call "sbopkg -i" as usual and notice that there was no warn
about Local vs Original and old version was chosen (and I Quit):

root at darkstar:~/sbolibs/multimedia/spotify# sbopkg -i spotify
>
> ###########################################
>        New queue process started on:
>        Sun Feb 28 03:38:14 -03 2021
> ###########################################
>
> +++++++++++++++++++++++++++++++++++++++++++
> PRE-CHECK LOG
> Using the UNSUPPORTED SBo git repository for -current
> Queue Process:  Download, build, and install
>
> spotify:
>   GPG checks not supported for the SBo-git repository.
>   Processing spotify 1.1.10-2
>   Using original .info file
>   Using original SlackBuild file
>   No build options selected.
>
> +++++++++++++++++++++++++++++++++++++++++++
>
> Pre-check complete.
>
> Do you wish to proceed based on the search results above? Packages not
> found will be skipped during the process.
>
> (P)roceed or (Q)uit?: Q
>

Listing files again and my *.sbopkg files has gone:

root at darkstar:~/sbolibs/multimedia/spotify# ls -1
> README
> doinst.sh
> slack-desc
> spotify.SlackBuild
> spotify.info




Best Regards,
Diniz Bortolotto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20210228/217f717e/attachment.htm>

From diniz.bortolotto at gmail.com  Sun Feb 28 20:32:28 2021
From: diniz.bortolotto at gmail.com (Diniz Bortolotto)
Date: Sun, 28 Feb 2021 17:32:28 -0300
Subject: [sbopkg-users] sbopkg 0.38.2 + SBo-git not considering *.sbopkg
 files
In-Reply-To: <CAEbqFbVqXWAWcXFhm5PrKp+aovONd3ZN+GRoemmhgQ0peyTHJw@mail.gmail.com>
References: <CAEbqFbVqXWAWcXFhm5PrKp+aovONd3ZN+GRoemmhgQ0peyTHJw@mail.gmail.com>
Message-ID: <CAEbqFbXGVCHs1oh8JCrdqV+BNyweydJPLXUDV+5abpaMh6kdrQ@mail.gmail.com>

A small correction.
The line changed in SlackBuild is VERSION, not VERSION32.
I corrected that but made a wrong copy/paste of diff. :)
But the error remains the same.

root at darkstar:~/sbolibs/multimedia/spotify# diff spotify.SlackBuild
> spotify.SlackBuild.sbopkg
> 30c30
> < VERSION=${VERSION:-1.1.10}
> ---
> > VERSION=${VERSION:-1.1.42}


Best Regards,
Diniz Bortolotto




Em dom., 28 de fev. de 2021 ?s 16:41, Diniz Bortolotto <
diniz.bortolotto at gmail.com> escreveu:

> Hi buddies!
> It's me again! :-)
>
> Today I'm testing sbopkg 0.38.2 (with Ponce's SBo-git repo) and noticed
> that when trying to use a "Local" pkg.info.sbopkg it was ignored/deleted
> and I couldn't figure out how to correct it.
> I also tried  to do the same using sbopkg 0.38.1 and also didn't work. So,
> I could assume that it's something related to the git portion of the sbopkg
> code.
> Could someone explain that? :)
>
> If someone wants to try/check, here is the spotify.info.sbopkg content:
>
> root at darkstar:~# cat
>> /var/lib/sbopkg/SBo/14.2/multimedia/spotify/spotify.info.sbopkg
>> PRGNAM="spotify"
>> VERSION="1.1.42"
>> HOMEPAGE="https://www.spotify.com"
>> DOWNLOAD="
>> http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.72.117.g6bd7c
>> c73-35_i386.deb"
>> MD5SUM="c8e54d60452bda40f6de23f11c909b2d"
>> DOWNLOAD_x86_64="
>> http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622
>> .gbd112320-37_amd64.deb"
>> MD5SUM_x86_64="9c9cbd30bac795b8ca71643de9d2d719"
>> REQUIRES=""
>> MAINTAINER="DhabyX"
>> EMAIL="slack.dhabyx at gmail.com"
>>
>
> Below a small example of what happened:
>
> Here we could see the original content of directory:
>
> root at darkstar:~/sbolibs/multimedia/spotify# ls -1
>> README
>
> doinst.sh
>
> slack-desc
>
> spotify.SlackBuild
>
> spotify.info
>>
>
> So, I created *.sbopkg files with new version to build:
>
> root at darkstar:~/sbolibs/multimedia/spotify# ls -1
>> README
>> doinst.sh
>> slack-desc
>> spotify.SlackBuild
>> spotify.SlackBuild.sbopkg
>> spotify.info
>> spotify.info.sbopkg
>
>
> Now a diff to show that I'm trying to create a new version of this package
> (1.1.42):
>
> root at darkstar:~/sbolibs/multimedia/spotify# diff spotify.SlackBuild
>> spotify.SlackBuild.sbopkg
>> 31c31
>> < VERSION32=${VERSION32:-1.0.72}
>> ---
>> > VERSION32=${VERSION32:-1.1.42}
>
>
>
> Here I just call "sbopkg -i" as usual and notice that there was no warn
> about Local vs Original and old version was chosen (and I Quit):
>
> root at darkstar:~/sbolibs/multimedia/spotify# sbopkg -i spotify
>>
>> ###########################################
>>        New queue process started on:
>>        Sun Feb 28 03:38:14 -03 2021
>> ###########################################
>>
>> +++++++++++++++++++++++++++++++++++++++++++
>> PRE-CHECK LOG
>> Using the UNSUPPORTED SBo git repository for -current
>> Queue Process:  Download, build, and install
>>
>> spotify:
>>   GPG checks not supported for the SBo-git repository.
>>   Processing spotify 1.1.10-2
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> +++++++++++++++++++++++++++++++++++++++++++
>>
>> Pre-check complete.
>>
>> Do you wish to proceed based on the search results above? Packages not
>> found will be skipped during the process.
>>
>> (P)roceed or (Q)uit?: Q
>>
>
> Listing files again and my *.sbopkg files has gone:
>
> root at darkstar:~/sbolibs/multimedia/spotify# ls -1
>> README
>> doinst.sh
>> slack-desc
>> spotify.SlackBuild
>> spotify.info
>
>
>
>
> Best Regards,
> Diniz Bortolotto
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20210228/a5249771/attachment-0001.htm>