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

JCA 1.41421 at gmail.com
Fri Apr 20 01:08:39 UTC 2018


-ki or -k -i, It does not seem to make any difference.

On Thu, Apr 19, 2018 at 6:41 PM, Donald Cooley <chytraeu at sdf.org> wrote:

> On April 19, 2018 5:53:19 PM CDT, JCA <1.41421 at gmail.com> wrote:
>>
>> As I am writing this I have the feeling I have already asked about this
>> isse. Well, I'd rather be a fool than an ignorant fool.
>>
>> I ran "sbopkg -c" in my system, and it informed me that there is a new
>> version of Wireshark available. From the /var/lib/sbopkg/queues directory,
>> as root I invoked "sbopkg -ki wireshark.sqf". This elicited the following
>> answer: "No valid packages found. Exiting". I tried again with "sbopkg -i
>> wireshark.sqf". This time I got the following:
>>
>>
>> ###########################################
>>        New queue process started on:
>>        Thu Apr 19 16:05:11 MDT 2018
>> ###########################################
>>
>> +++++++++++++++++++++++++++++++++++++++++++
>> PRE-CHECK LOG
>> Using the SBo repository for Slackware 14.2
>> Queue Process:  Download, build, and install
>>
>> GeoIP:
>>   Checking GPG for GeoIP.tar.gz ... OK
>>   Processing GeoIP 1.6.12-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> lua:
>>   Checking GPG for lua.tar.gz ... OK
>>   Processing lua 5.1.5-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> libwacom:
>>   Checking GPG for libwacom.tar.gz ... OK
>>   Processing libwacom 0.29-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> libinput:
>>   Checking GPG for libinput.tar.gz ... OK
>>   Processing libinput 1.8.3-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> libxkbcommon:
>>   Checking GPG for libxkbcommon.tar.gz ... OK
>>   Processing libxkbcommon 0.7.1-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> qt5:
>>   Checking GPG for qt5.tar.gz ... OK
>>   Processing qt5 5.7.1-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> wireshark:
>>   Checking GPG for wireshark.tar.gz ... OK
>>   Processing wireshark 2.4.6-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?:
>>
>> After typing "p", sbopkg proceeds to attempt to download, build and
>> install all those packages. Here is the thing: I already have all those
>> packages installed, and they are the right versions.
>>
>> Notice, however, that if I remove the installed version of Wireshark by
>> hand (with removepkg) on invoking "sbopkg -ki wireshark.sqf" sbopkg seems
>> to understand that all those dependencies are installed, for it only tries
>> to download and install Wireshark.
>>
>> Why is sbopkg able to do the expected (right?) thing in one case, but not
>> in the other? Is this intentional? It is not a big deal, for one can work
>> around it as described. But, naively, it would seem like it would be a good
>> idea if sbopkg could take care of the package upgrade process intelligently
>> on its own. Perhaps am I missing something here?
>>
>>
> I think you need to type sbopkg -k -i instead of sbopkg -ki.
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> _______________________________________________
> 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/20180419/3bddfd17/attachment.html>


More information about the SlackBuilds-users mailing list