What's the right approach to the autoremove we currently have? Plus: json-class and json-meta6 ready for review / upload

[Timo Paulssen]

Hi List, Hi Dominique,

you may have seen that a bunch of packages are going to be automatically 
removed.

The direct cause of the removal is this bug report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083145

prove6 FTBFS (fails to build from source) because raku-tap-harness (aka 
TAP) is currently packaged with a dependency on precompiled files that 
the rakudo package no longer provides.

The rakudo package has seen an upload of version 2022.12-1.1, which I 
think is what introduced the new precompiled versions of built-ins (like 
the v6c.bootstrap that's mentioned in the error message).

I think we said we don't want to cause rebuilds of all the packages 
"just" to fix their builds, but when the packages are going to be 
removed from debian if we don't get their FTBFS bugs fixed, I think it 
should be treated a little bit more urgently?

If I understand correctly, we were just waiting for a fix to the problem 
meta6 had, which was legit and not just precompilation problems. The 
upstream fixed it in the newer version, which requires a newer version 
of JSON::Class as well.

I have pushed commits to the debian/sid branch of both raku-json-class 
and raku-meta6 that should be ready-to-go for releasing packages.

I would have gone through a proper merge request workflow, but salsa is 
currently experiencing high load on its background workers, so merge 
requests hang for an extended period of time after creation.

I think once these two packages are uploaded to experimental, we should 
be in a good position to upload everything to unstable.

I hope once we do that, the unstable upload, we can soon move on towards 
testing. We can then mark all the FTBFS bugs "fixed in this version".

Actually, I'm now thinking that perhaps all the FTBFS bugs should be 
moved to become bugs of the rakudo package? The cause for it is kind of 
"ethereal" or "environmental". It will not be a new version of any one 
package that causes it to become fixed, but a new build being uploaded 
for (essentially) the same version - at least the same version of the 
source package.

Thanks
   - Timo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-rakudo-devel/attachments/20241014/525d3a4a/attachment.htm>