Bug#1141561: transition: c-blosc2

Antonio Valentino <[email protected]>
Newsgroups gmane.linux.debian.devel.release
Message-ID <045f2c0f-9150-43c0-b9a2-ec7a8d68e90f__47115.3940235794$1783918408$gmane$org@tiscali.it>
Dear Emilio,

On Mon, 6 Jul 2026 19:54:28 +0200 Emilio Pozuelo Monfort 
<[email protected]> wrote:
> Control: tags -1 moreinfo
> 
> On 06/07/2026 10:49, Antonio Valentino wrote:
> > Package: release.debian.org
> > Severity: normal
> > X-Debbugs-Cc: [email protected], [email protected]
> > Control: affects -1 + src:c-blosc2
> > User: [email protected]
> > Usertags: transition
> > 
> > Dear release team,
> > 
> > the upgrade from c-blosc2 v2.23.1 to v3.1.5 requires a change in the
> > SONAME and hence a transition. The new version is already in experimental.
> > The following source packages need to be rebuilt:
> > 
> > * adios2
> > * groonga
> > * pytables
> > * zmat
> > 
> > I have tested the above packages with the new version of c-blosc2.
> > Only for pytables it was necessary a small patch that has been already
> > uploaded.
> > 
> > pytables 3.11.1-2 is now in unstable and it should migrate to testing in
> > 5 days.
> > 
> > Apart for that all the packages build successfully with the new c-blosc2
> > version that is currently in experimental.
> 
> There's a few build failures in experimental:
> 
> https://buildd.debian.org/status/package.php?p=c-blosc2&suite=experimental
> 
> Please fix those in experimental first.

Thanks for the quick reply.
According to [1] 32bit architectures are no longer supported in c-blosc2 
v3.x.

My plan would be just to request the removal of c-blosc2 package for 
i386 and armhf from sid.
According to my understanding this should unblock the migration of the 
new new c-blosc2 package to testing in a normal situation.
I'm not sure if this is fine for a transition (like in this case).
Do you have comments or any advice?



[1] https://github.com/Blosc/c-blosc2/issues/790



kind regards
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.