[Slackbuilds-users] WIP: protobuf3 25.3

[Jeremy Hansen]

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 SQLAlchemy update and another package I
maintain (sickchill) needs to have an update to work (I actually have to
remove a patch that allowed it to still work with the older version). If
you update sickchill without updating SQLAlchemy, sickchill will break,
just as if you update SQLAlchemy without updating sickchill, sickchill will
break.

If you do pick and choose which updates to make without doing everything
and something is broken, try rebuilding it to see if it fixes it.

As for the versioning, this is the version from upstream. On SBo, it hadn't
seen an update in almost two years while upstream kept chugging along.
Also, sometimes upstream will change how they version things, so you might
see big jumps at times.

The tools don't care about jumps in versions, in fact, they don't even care
what the version number is, just that the version and/or build number is
different than the current version or build number. This is why there is no
issue using commit IDs as versions or throwing dates or kernel versions
into the version.

Jeremy

On Mon, Mar 11, 2024, 5:14 AM Ruben Carlo Benante <rcb at beco.cc> wrote:

> 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 like this approach anymore. I'm trying to learn LCX, and for
> slackware it doesn't have templates ready to go, so there is that.
>
> Anyway, thanks for your reply. Good to know it works. I'm still waiting
> for the protobuf3 maintainer reply on the version numbers (previous email)
>
> Cordialmente,
>
> Ruben
>
> --
> Dr. Beco
> AI Researcher
>
>
>
>
> ---- On Sun, 10 Mar 2024 19:45:43 -0300 *Jeremy Hansen
> <jebrhansen+sbo at gmail.com <jebrhansen%2Bsbo at gmail.com>>* wrote ---
>
> Did you rebuild clementine after updating protobuf3? You should be on
> build 2 of clementine as that includes fixes for the new protobuf3 version.
>
> It works fine on my end (I'm the clementine maintainer).
>
> Jeremy
>
> On Sun, Mar 10, 2024, 1:51 PM Ruben Carlo Benante via SlackBuilds-users <
> slackbuilds-users at slackbuilds.org> wrote:
>
>
> Another thing that may or may not be related:
>
> The mp3 player Clementine has stoped working after upgrade.
>
> I've returned to grpc-1.48.4 and protobuf3-3.20.1, and after the downgrade
> Clementine works fine again.
>
> Cordialmente,
> Ruben
>
> --
> Dr. Beco
> AI Researcher
>
>
>
>
> ---- On Sun, 10 Mar 2024 13:54:41 -0300 *Ruben Carlo Benante <rcb at beco.cc
> <rcb at beco.cc>>* wrote ---
>
> Hello,
>
> Is there an error in the version number? Or is it going from 3 to 25 and
> keep growing further in the next versions?
>
> The following names are what it looked like in the past:
>
> * Packages/protobuf-2.6.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.17.3-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.18.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.3-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.4-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.20.0-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.20.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-25.3-x86_64-1_SBo.tgz
>
>
> I'm afraid slackpkg or sbotools or sbopkg will complain if the next comes
> with something like
>
>  Packages/protobuf3-3.26.0-x86_64-1_SBo.tgz or something as previous format
>
>
> Cordialmente,
> Ruben
>
> --
> Dr. Beco
> AI Researcher
>
>
>
>
> ---- On Sat, 02 Mar 2024 18:10:31 -0300 *Giancarlo Dessì <slack at giand.it
> <slack at giand.it>>* wrote ---
>
> Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto:
> > Hi
> >
> > i have just started to work on protobuf3 updates, pushing 2y of works
> > by upstream since last update.
> >
> > However, there are 26 other scripts which depends on protobuf3, listed
> > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1)
> >
> > although we do have CI engine that could help us test whether the new
> > update will break them or not, it won't help us testing the runtime
> > issues. Therefore, i would like to ask for help by those who are using
> > these 26 packages to see if by upgrading protobuf3 and rebuilding them
> > will have any runtime issues or not.
> >
> > I will keep the protobuf3 updates for future public update (like 1-2
> > weeks delay) to give others more time to test.
> >
> > The protobuf3 update can be seen here
> > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip
> >
> > Big thanks in advance
> >
> At the moment I tested new protobuf3 in -current, it works for
> protobuf-c/postgis and qgis
>
> After upgrade of protobuf3 the entire tree until qgis was broken, I had
> to rebuild protobuf-c and then postgis and finally qgis because protobuf
> is required as first level dependency also by qgis
>
> --
>
> *********************************************************
> Giancarlo Dessì
> https://www.giand.it
> https://github.com/giandex
>
> Slackware Linux... because it works!
> *********************************************************
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240311/84cf3146/attachment-0001.htm>