If using current you shouldn't overwrite stock Slackware packages with those
from SBo like you did. You need to go back and reinstall the Slackware
packages.
> The whole error message: (Had to use --reinstall because in the meantime
> I got in installed, somehow.)
>
> # sboinstall --reinstall
Thanks Matteo, all very interesting. So I was probably installing
correct -current SBo's right from the beginning.
I wonder if sbotools looks at /etc/slackware-version to decide which
repo to default to.
Good advice on going to LQ for questions about -current (and sbotools
too, I guess.)
Thanks for the reply.
On 3/11/24 17:51, Erich Ritz via SlackBuilds-users wrote:
If using current you shouldn't overwrite stock Slackware packages with those
from SBo like you did. You need to go back and reinstall the Slackware
packages.
You may be right. It would be interesting to go
Hello. After updating protobuf3-25.3, building package qt6 gives an
error. The
old protobuf3 package had 17 header files, the new package has only 5, which
are located in
/usr/include/google/protobuf/stubs/
This is why the qt6 assembly complains that there are not enough headers:
ERROR
On Sun, 10 Mar 2024, J. Milgram wrote:
Hello.
Once again having problems installing with sbotools. There's evidently some
config subtlety I'm not grasping, hopefully someone can set me straight.
I have a fresh -current install and am using the default 15.0 repo. Many
slackbuilds installed
hi,
just for testing I downloaded, packaged and installed sbotools from here
https://slackbuilds.org/repository/15.0/system/sbotools/
following what's written on the documentation
https://pink-mist.github.io/sbotools/documentation/
I run "sbosnap fetch" to download the repository and I saw
Hi Jeremi,
I did not rebuild clementine after updating protobuf3 at the time.
Since this is a prod machine, I won't be able to test.
I'm still looking for some guidelines on how developers usually create virtual
machines to test. I used virtualbox when I developed for debian, but I don't
If you update just a single package without checking other programs you
have installed, you could continue to run into issues like this. We ensured
the clementine update was pushed in the same public update as protobuf3 to
make sure that the repo continued to work.
This week we're working on an
