[Slackbuilds-users] Upgrading packages with sbopkg and queue files

Fri Apr 20 15:59:52 UTC 2018

Well, I remain very confused :-( I ran "sbopkg -c" in a different system,
and this is what I got:

[ Checking for potential updates ]
This may take a few moments. Press <ESC> to abort.
100%[========================================================================]
Listing installed SBo repository for Slackware 14.2 packages and flagging
potential updates...

  Note: repo version not obtainable by standard method, may be inaccurate.
haskell-cmark:
  POTENTIAL UPDATE
  Installed version:  haskell-cmark-0.5.5.1-x86_64-1_SBo
  Repo version:  haskell-cmark-0.5.6-x86_64-1_SBo
haskell-cryptonite:
  POTENTIAL UPDATE
  Installed version:  haskell-cryptonite-0.24-x86_64-1_SBo
  Repo version:  haskell-cryptonite-0.25-x86_64-1_SBo
haskell-foundation:
  POTENTIAL UPDATE
  Installed version:  haskell-foundation-0.0.13-x86_64-1_SBo
  Repo version:  haskell-foundation-0.0.20-x86_64-1_SBo
haskell-memory:
  POTENTIAL UPDATE
  Installed version:  haskell-memory-0.14.6-x86_64-1_SBo
  Repo version:  haskell-memory-0.14.16-x86_64-1_SBo

Potential update list complete.

According to info in slackbuilds, haskell-cryptonite depends on
haskell-memory, which in turn depends on haskell-foundation, itself
dependent on haskell-basement. I therefore did

# sqg -p haskell-cryptonite
# sbopkg -k -i haskell-cryptonite

This prompted me to install haskell-basement. Which I did, with the queue
file. And that was it. Nothing was done about haskell-foundation,
haskell-memory or haskell-cryptonite. In fact, if after this I try the sqg
and sbopkg commands above, here is what I am getting:

# sqg -p haskell-cryptonite
Processing haskell-cryptonite.
Done.

# sbopkg -k -i haskell-cryptonite
Both a queuefile and a package were found with the name
"haskell-cryptonite".

Use (Q)ueuefile, (P)ackage, or (A)bort?: q
No valid packages found. Exiting.

At the same time, the output from "sbopkg -c" remains exactly the same as
above. And if I do "sbopkg -i haskell-cryptonite", this is what I am
getting:

Both a queuefile and a package were found with the name
"haskell-cryptonite".

Use (Q)ueuefile, (P)ackage, or (A)bort?: q

###########################################
       New queue process started on:
       Fri Apr 20 09:53:05 MDT 2018
###########################################

+++++++++++++++++++++++++++++++++++++++++++
PRE-CHECK LOG
Using the SBo repository for Slackware 14.2
Queue Process:  Download, build, and install

ghc:
  Checking GPG for ghc.tar.gz ... OK
  Processing ghc 7.10.3-1
  Using original .info file
  Using original SlackBuild file
  No build options selected.

haskell-basement:
  Checking GPG for haskell-basement.tar.gz ... OK
  Processing haskell-basement 0.0.7-1
  Using original .info file
  Using original SlackBuild file
  No build options selected.

haskell-foundation:
  Checking GPG for haskell-foundation.tar.gz ... OK
  Processing haskell-foundation 0.0.20-1
  Using original .info file
  Using original SlackBuild file
  No build options selected.

haskell-memory:
  Checking GPG for haskell-memory.tar.gz ... OK
  Processing haskell-memory 0.14.16-1
  Using original .info file
  Using original SlackBuild file
  No build options selected.

haskell-cryptonite:
  Checking GPG for haskell-cryptonite.tar.gz ... OK
  Processing haskell-cryptonite 0.25-1
  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

Again, both ghc and haskell-basement are up-to-date - there is no reason
for them to be built anew.

What am I doing wrong?

On Fri, Apr 20, 2018 at 7:11 AM, JCA <1.41421 at gmail.com> wrote:

> OK, thanks. The only difference between what you are proposing and what I
> was doing is the "sqg -p wireshark" invocation. I'll try it the next time
> this issue comes up.
>
> On Fri, Apr 20, 2018 at 6:20 AM, Edinaldo <edps.mundognu at gmail.com> wrote:
>
>> You can processs the queue file with options -k (skip installed) and -i
>> (install), example:
>>
>> # sqg -p wireshark
>> # sbopkg -k -i wireshark
>>
>> * when asked, press Q to process the queue and next press P:
>>
>> In this case, all dependencies that are already installed will be
>> ignored, see that only qt5 and wireshark will be installed:
>>
>> http://dpaste.com/309P2A9
>>
>>
>> On the other hand, if you process the queue without the -k option, all
>> scripts will be reinstalled (NOTE: i press Q to process the queue):
>>
>> http://dpaste.com/1R28JYB
>>
>>
>> However, when a script is installed use the -k option, it will have no
>> effect:
>>
>>
>> ~ » sudo sbopkg -p | grep leafpad
>> leafpad-0.8.18.1-x86_64-2_SBo
>>
>> ~ » sudo sbopkg -k -i leafpad
>> No valid packages found. Exiting.
>>
>> ~ » sudo sbopkg -i leafpad
>>
>> ###########################################
>>        New queue process started on:
>>        Sex Abr 20 09:18:58 -03 2018
>> ###########################################
>>
>> +++++++++++++++++++++++++++++++++++++++++++
>> PRE-CHECK LOG
>> Using the SBo repository for Slackware 14.2
>> Queue Process:  Download, build, and install
>>
>> leafpad:
>>   Checking GPG for leafpad.tar.gz ... OK
>>   Processing leafpad 0.8.18.1-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?:
>>
>> Cheers,
>>
>> Edinaldo
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180420/bb6bba8d/attachment-0001.html>