abseil needs an update to go ahead with other transitions like protobuf
and grpc.  The transition was finished for Ubuntu, and with bug reports
filed for Debian.

One remaining package is sra-sdk, where no patch is available yet.  For
other packages, patches are either available or submitted in the bug
reports.

It also fixes the abseil ftbfs in unstable.

Control: block -1 by 1127767

As this transition overlaps with the qt 6 transition, let's do it after
Qt 6.10 is in testing.

Cheers

Control: tags -1 confirmed

Qt 6.10 is done, please go ahead.

Cheers

Hi Sebastian, Matthias,
[...]
 I'm wondering how to go forward. Matthias and I exchanged emails on
how to go with abseil maintenance, I may join as a co-maintainer as
I'm involved with it. Then nothing was agreed upon.
But I'm wondering if he has time to move on with this transition. It
was nine days ago when you gave it a go. If Matthis doesn't respond in
another five days (two weeks in total), would I be allowed to start
the transition, adding myself as a co-maintainer?
Matthias, if you are reading this before the five days, please step up
and start this transition.

Thanks,
Laszlo/GCS

[...]
 Matthias, another friendly ping as two weeks passed. Please step up
and start the transition. I plan to do it by adding myself as
co-maintainer tomorrow if I don't see this transition started.

Thanks,
Laszlo/GCS

From my point of view, you can do the upload to unstable following the
usual NMU rules (unless there was an agreement on co-maintenance in the
meantime).

Cheers

please don't.

If it takes the release team more than a month for even a reaction on a
transition, two more weeks for an approval, it shouldn't be a problem
for letting this alone for two weeks.

And comparing that to icu's transitions or other transitions owned by
Laszlo, which were either not done or delayed by multiple months or even
years, two weeks delay should be fine.

Matthias

This has nothing to do with the release team. From our point of view we
do not care who starts the transition. It is ACKed.

This is an issue between you and Laszlo.

Cheers

No, keeping quiet for more than a month is an issue within the release team.

Control: block -1 by 1130893 1130335

We surely appreciate additional people dealing with the workload. Are you
volunteering to help out?

Back to topic at hand: llvm-toolchain-21 is involved in the abseil
transition but depends on llvm-toolchain-22 which is currently not
migrating to testing due to open issues. Adding those bugs as blocking
bugs for the completion of this transition.

Cheers

block 1127773 by 1133861
thanks

As I can see, the abseil transition has started. Unfortunately,
telegram-desktop is currently in FTBFS state (bug #1133861) in unstable because
of a change in zlib. The fix has been prepared, though, I have to delay
uploading telegram-desktop until libtgowt, a build dependency, is built against
the new abseil on all release architectures.

Anyway, I can't upload the fix right now, because both my packages need to use
the same abseil version. If not, Telegram Desktop might fail to build or even
worse, it might crash at runtime.

I'm closing this bug because it appears that abseil 20260107.0-5 has
migrated to testing and there aren't any NBS libraries in testing or
unstable.

There is a new version of abseil in experimental but a separate
transition bug will need to be filed for that.

Thank you,
Jeremy Bícha