[sbopkg-users] sbopkg attempting to install packages already present

Thu May 9 20:49:02 UTC 2019

>> In a different 14.2 VM I went through the steps with keepassxc first,
>> then wireshark. I first did
>>
>> # sbopkg -k -i keepassxc.sqf
>>
>> This updated all the packages, as above, and then built keepassxc, as
>> expected. I then tried with wireshark. The version of wireshark that I
>> have installed in that system is 2.0.5, while the current one in
>> Slackbuilds is 3.0.1. I therefore did
>>
>> # sbopkg -k -i wireshark.sqf
>> No valid packages found. Exiting.
>>
>> I don't understand why sbopkg returns that diagnostic. I then tried
>>
>> # sbopkg -i wireshark.sqf
>>
>> This tries to update all those packages that were already updated when I
>> built keepassxc.
>>
>> Now if I remove the existing wireshark package first, and then do
>>
>> # sbopkg -k -i wireshark.sqf
>>
>> then things work as expected, in that sbopkg will not try to update all
>> those wireshark dependencies, instead just downloading and building
>> wireshark.
>>
>> Is this the way sbopkg was designed to operate?
>
> First, you don't run .sqf file. You just need to mention the package
> name, in this case it would be wireshark

   OK, thanks.

> secondly, -k implies the package you want to install as well, so if you
> already have that package installed, it won't build and install it again
> for you. Basically -k means skipped any packages installed on your
> machine, including an old one.

  Makes sense.

> If you want to build the wireshark package only, just run sbopkg -i
> wireshark and pick "P" (package) instead of queue. This way, you will
> build and install wireshark package only.

  That clarifies things. Thank you.

On Wed, May 8, 2019 at 9:22 AM JCA <1.41421 at gmail.com> wrote:

> I am quoting a response as I saw it in the archives - for some reason, it
> has yet to show up in my mailbox:
>
> Willy Sudiarto Raharjo replied:
>
> > By default, sbopkg will just read the queue and tried to install them
> > according to the build order.
>
> > If you want to skip the existing packages, you can use sbopkg -k -i
> > keepassxc. However, please note that if there's a change in one of the
> > deps, you are risking your system to link to the old version of the
> > library, so use it with care
>
> In a different 14.2 VM I went through the steps with keepassxc first, then
> wireshark. I first did
>
> # sbopkg -k -i keepassxc.sqf
>
> This updated all the packages, as above, and then built keepassxc, as
> expected. I then tried with wireshark. The version of wireshark that I have
> installed in that system is 2.0.5, while the current one in Slackbuilds is
> 3.0.1. I therefore did
>
> # sbopkg -k -i wireshark.sqf
> No valid packages found. Exiting.
>
> I don't understand why sbopkg returns that diagnostic. I then tried
>
> # sbopkg -i wireshark.sqf
>
> This tries to update all those packages that were already updated when I
> built keepassxc.
>
> Now if I remove the existing wireshark package first, and then do
>
> # sbopkg -k -i wireshark.sqf
>
> then things work as expected, in that sbopkg will not try to update all
> those wireshark dependencies, instead just downloading and building
> wireshark.
>
> Is this the way sbopkg was designed to operate?
>
>
> On Mon, May 6, 2019 at 10:06 AM JCA <1.41421 at gmail.com> wrote:
>
>> I devoted the weekend to upgrading a number of things in my 14.2 system.
>> For example, I upgraded wireshark with
>>
>> sbopkg -i wireshark.sqf
>>
>> without any problems (but it took a long time):
>>
>> +++++++++++++++++++++++++++++++++++++++++++
>> SUMMARY LOG
>> Using the SBo repository for Slackware 14.2
>> Queue Process:  Download, build, and install
>>
>> python3:
>>   MD5SUM check for Python-3.7.2.tar.xz ... OK
>>   Building package python3-3.7.2-x86_64-1_SBo.tgz ... OK
>>   Installing package python3-3.7.2-x86_64-1_SBo.tgz ... OK
>>
>> lua:
>>   MD5SUM check for lua-5.1.5.tar.gz ... OK
>>   Building package lua-5.1.5-x86_64-1_SBo.tgz ... OK
>>   Installing package lua-5.1.5-x86_64-1_SBo.tgz ... OK
>>
>> pyudev:
>>   MD5SUM check for pyudev-0.21.0.tar.gz ... OK
>>   Building package pyudev-0.21.0-x86_64-1_SBo.tgz ... OK
>>   Installing package pyudev-0.21.0-x86_64-1_SBo.tgz ... OK
>>
>> python-evdev:
>>   MD5SUM check for evdev-1.1.2.tar.gz ... OK
>>   Building package python-evdev-1.1.2-x86_64-1_SBo.tgz ... OK
>>   Installing package python-evdev-1.1.2-x86_64-1_SBo.tgz ... OK
>>
>> graphviz:
>>   MD5SUM check for graphviz.tar.gz ... OK
>>   Building package graphviz-2.40.1-x86_64-1_SBo.tgz ... OK
>>   Installing package graphviz-2.40.1-x86_64-1_SBo.tgz ... OK
>>
>> ninja:
>>   MD5SUM check for ninja-1.9.0.tar.gz ... OK
>>   Building package ninja-1.9.0-x86_64-1_SBo.tgz ... OK
>>   Installing package ninja-1.9.0-x86_64-1_SBo.tgz ... OK
>>
>> meson:
>>   MD5SUM check for meson-0.49.0.tar.gz ... OK
>>   Building package meson-0.49.0-x86_64-1_SBo.tgz ... OK
>>   Installing package meson-0.49.0-x86_64-1_SBo.tgz ... OK
>>
>> libwacom:
>>   MD5SUM check for libwacom-libwacom-0.33.tar.gz ... OK
>>   Building package libwacom-0.33-x86_64-1_SBo.tgz ... OK
>>   Installing package libwacom-0.33-x86_64-1_SBo.tgz ... OK
>>
>> libinput:
>>   MD5SUM check for libinput-1.13.1.tar.xz ... OK
>>   Building package libinput-1.13.1-x86_64-1_SBo.tgz ... OK
>>   Installing package libinput-1.13.1-x86_64-1_SBo.tgz ... OK
>>
>> libxkbcommon:
>>   MD5SUM check for libxkbcommon-0.8.4.tar.xz ... OK
>>   Building package libxkbcommon-0.8.4-x86_64-1_SBo.tgz ... OK
>>   Installing package libxkbcommon-0.8.4-x86_64-1_SBo.tgz ... OK
>>
>> qt5:
>>   MD5SUM check for qt-everywhere-opensource-src-5.9.7.tar.xz ... OK
>>   Building package qt5-5.9.7-x86_64-1_SBo.tgz ... OK
>>   Installing package qt5-5.9.7-x86_64-1_SBo.tgz ... OK
>>
>> wireshark:
>>   MD5SUM check for wireshark-3.0.1.tar.xz ... OK
>>   Building package wireshark-3.0.1-x86_64-1_SBo.tgz ... OK
>>   Installing package wireshark-3.0.1-x86_64-1_SBo.tgz ... OK
>>
>> +++++++++++++++++++++++++++++++++++++++++++
>>
>> ###########################################
>>           Queue process complete!
>> ###########################################
>>
>>
>>    Today I wanted to upgrade keepasxc, which shares a number of
>> dependencies with wireshark. When I launched
>>
>> sbopkg -i keepassxc.sqf
>>
>> I got the following:
>>
>> PRE-CHECK LOG
>> Using the SBo repository for Slackware 14.2
>> Queue Process:  Download, build, and install
>>
>> pyudev:
>>   Checking GPG for pyudev.tar.gz ... OK
>>   Processing pyudev 0.21.0-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> python-evdev:
>>   Checking GPG for python-evdev.tar.gz ... OK
>>   Processing python-evdev 1.1.2-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> graphviz:
>>   Checking GPG for graphviz.tar.gz ... OK
>>   Processing graphviz 2.40.1-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> ninja:
>>   Checking GPG for ninja.tar.gz ... OK
>>   Processing ninja 1.9.0-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> python3:
>>   Checking GPG for python3.tar.gz ... OK
>>   Processing python3 3.7.2-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> meson:
>>   Checking GPG for meson.tar.gz ... OK
>>   Processing meson 0.49.0-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> libwacom:
>>   Checking GPG for libwacom.tar.gz ... OK
>>   Processing libwacom 0.33-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> libinput:
>>   Checking GPG for libinput.tar.gz ... OK
>>   Processing libinput 1.13.1-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> libxkbcommon:
>>   Checking GPG for libxkbcommon.tar.gz ... OK
>>   Processing libxkbcommon 0.8.4-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> qt5:
>>   Checking GPG for qt5.tar.gz ... OK
>>   Processing qt5 5.9.7-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> qrencode:
>>   Checking GPG for qrencode.tar.gz ... OK
>>   Processing qrencode 4.0.2-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> libsodium:
>>   Checking GPG for libsodium.tar.gz ... OK
>>   Processing libsodium 1.0.17-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> argon2:
>>   Checking GPG for argon2.tar.gz ... OK
>>   Processing argon2 20170329_1eea010-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> keepassxc:
>>   Checking GPG for keepassxc.tar.gz ... OK
>>   Processing keepassxc 2.4.1-1
>>   Using original .info file
>>   Using original SlackBuild file
>>   No build options selected.
>>
>> What's the deal with python3, meson, ninja, etc? Why is sbopkg trying to
>> build them again? I can't believe new versions of these packages have been
>> added since yesterday. What am I misunderstanding here?
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20190509/f20c7576/attachment-0001.html>