<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">I am quoting a response as I saw it in the archives - for some reason, it has yet to show up in my mailbox:<div><br></div><div>Willy Sudiarto Raharjo replied:<br></div><div><br></div><div><div>> By default, sbopkg will just read the queue and tried to install them</div><div>> according to the build order.</div><div><br></div><div>> If you want to skip the existing packages, you can use sbopkg -k -i</div><div>> keepassxc. However, please note that if there's a change in one of the</div><div>> deps, you are risking your system to link to the old version of the</div><div>> library, so use it with care</div></div><div><br></div><div>In a different 14.2 VM I went through the steps with keepassxc first, then wireshark. I first did</div><div><br></div><div># sbopkg -k -i keepassxc.sqf</div><div><br></div><div>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</div><div><br></div><div><div># sbopkg -k -i wireshark.sqf </div><div>No valid packages found. Exiting.</div></div><div><br></div><div>I don't understand why sbopkg returns that diagnostic. I then tried </div><div><br></div><div># sbopkg -i wireshark.sqf</div><div><br></div><div>This tries to update all those packages that were already updated when I built keepassxc.</div><div><br></div><div>Now if I remove the existing wireshark package first, and then do</div><div><br></div><div># sbopkg -k -i wireshark.sqf</div><div><br></div><div>then things work as expected, in that sbopkg will not try to update all those wireshark dependencies, instead just downloading and building wireshark.</div><div><br></div><div>Is this the way sbopkg was designed to operate?</div><div><br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 6, 2019 at 10:06 AM JCA <<a href="mailto:1.41421@gmail.com">1.41421@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr">I devoted the weekend to upgrading a number of things in my 14.2 system. For example, I upgraded wireshark with<div><br></div><div>sbopkg -i wireshark.sqf</div><div><br></div><div>without any problems (but it took a long time):</div><div><br></div><div><div>+++++++++++++++++++++++++++++++++++++++++++</div><div>SUMMARY LOG</div><div>Using the SBo repository for Slackware 14.2</div><div>Queue Process: Download, build, and install</div><div><br></div><div>python3:</div><div> MD5SUM check for Python-3.7.2.tar.xz ... OK</div><div> Building package python3-3.7.2-x86_64-1_SBo.tgz ... OK</div><div> Installing package python3-3.7.2-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>lua:</div><div> MD5SUM check for lua-5.1.5.tar.gz ... OK</div><div> Building package lua-5.1.5-x86_64-1_SBo.tgz ... OK</div><div> Installing package lua-5.1.5-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>pyudev:</div><div> MD5SUM check for pyudev-0.21.0.tar.gz ... OK</div><div> Building package pyudev-0.21.0-x86_64-1_SBo.tgz ... OK</div><div> Installing package pyudev-0.21.0-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>python-evdev:</div><div> MD5SUM check for evdev-1.1.2.tar.gz ... OK</div><div> Building package python-evdev-1.1.2-x86_64-1_SBo.tgz ... OK</div><div> Installing package python-evdev-1.1.2-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>graphviz:</div><div> MD5SUM check for graphviz.tar.gz ... OK</div><div> Building package graphviz-2.40.1-x86_64-1_SBo.tgz ... OK</div><div> Installing package graphviz-2.40.1-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>ninja:</div><div> MD5SUM check for ninja-1.9.0.tar.gz ... OK</div><div> Building package ninja-1.9.0-x86_64-1_SBo.tgz ... OK</div><div> Installing package ninja-1.9.0-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>meson:</div><div> MD5SUM check for meson-0.49.0.tar.gz ... OK</div><div> Building package meson-0.49.0-x86_64-1_SBo.tgz ... OK</div><div> Installing package meson-0.49.0-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>libwacom:</div><div> MD5SUM check for libwacom-libwacom-0.33.tar.gz ... OK</div><div> Building package libwacom-0.33-x86_64-1_SBo.tgz ... OK</div><div> Installing package libwacom-0.33-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>libinput:</div><div> MD5SUM check for libinput-1.13.1.tar.xz ... OK</div><div> Building package libinput-1.13.1-x86_64-1_SBo.tgz ... OK</div><div> Installing package libinput-1.13.1-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>libxkbcommon:</div><div> MD5SUM check for libxkbcommon-0.8.4.tar.xz ... OK</div><div> Building package libxkbcommon-0.8.4-x86_64-1_SBo.tgz ... OK</div><div> Installing package libxkbcommon-0.8.4-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>qt5:</div><div> MD5SUM check for qt-everywhere-opensource-src-5.9.7.tar.xz ... OK</div><div> Building package qt5-5.9.7-x86_64-1_SBo.tgz ... OK</div><div> Installing package qt5-5.9.7-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>wireshark:</div><div> MD5SUM check for wireshark-3.0.1.tar.xz ... OK</div><div> Building package wireshark-3.0.1-x86_64-1_SBo.tgz ... OK</div><div> Installing package wireshark-3.0.1-x86_64-1_SBo.tgz ... OK</div><div><br></div><div>+++++++++++++++++++++++++++++++++++++++++++</div><div><br></div><div>###########################################</div><div> Queue process complete!</div><div>###########################################</div></div><div><br></div><div><br></div><div> Today I wanted to upgrade keepasxc, which shares a number of dependencies with wireshark. When I launched</div><div><br></div><div>sbopkg -i keepassxc.sqf</div><div><br></div><div>I got the following:</div><div><br></div><div><div>PRE-CHECK LOG</div><div>Using the SBo repository for Slackware 14.2</div><div>Queue Process: Download, build, and install</div><div><br></div><div>pyudev:</div><div> Checking GPG for pyudev.tar.gz ... OK</div><div> Processing pyudev 0.21.0-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>python-evdev:</div><div> Checking GPG for python-evdev.tar.gz ... OK</div><div> Processing python-evdev 1.1.2-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>graphviz:</div><div> Checking GPG for graphviz.tar.gz ... OK</div><div> Processing graphviz 2.40.1-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>ninja:</div><div> Checking GPG for ninja.tar.gz ... OK</div><div> Processing ninja 1.9.0-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>python3:</div><div> Checking GPG for python3.tar.gz ... OK</div><div> Processing python3 3.7.2-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>meson:</div><div> Checking GPG for meson.tar.gz ... OK</div><div> Processing meson 0.49.0-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>libwacom:</div><div> Checking GPG for libwacom.tar.gz ... OK</div><div> Processing libwacom 0.33-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>libinput:</div><div> Checking GPG for libinput.tar.gz ... OK</div><div> Processing libinput 1.13.1-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>libxkbcommon:</div><div> Checking GPG for libxkbcommon.tar.gz ... OK</div><div> Processing libxkbcommon 0.8.4-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>qt5:</div><div> Checking GPG for qt5.tar.gz ... OK</div><div> Processing qt5 5.9.7-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>qrencode:</div><div> Checking GPG for qrencode.tar.gz ... OK</div><div> Processing qrencode 4.0.2-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>libsodium:</div><div> Checking GPG for libsodium.tar.gz ... OK</div><div> Processing libsodium 1.0.17-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>argon2:</div><div> Checking GPG for argon2.tar.gz ... OK</div><div> Processing argon2 20170329_1eea010-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div><div>keepassxc:</div><div> Checking GPG for keepassxc.tar.gz ... OK</div><div> Processing keepassxc 2.4.1-1</div><div> Using original .info file</div><div> Using original SlackBuild file</div><div> No build options selected.</div><div><br></div></div><div>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?</div><div><br></div></div></div></div>
</blockquote></div>