Fwd: Incoming Debian freeze

[Dominique Dumont]

On Monday 13 January 2025 15:25:55 CET Timo Paulssen wrote:
> I think that's only in the mail I forwarded to you. I can see my mail on
> the mailing list archive.

Hmm, the mail from the list may have been deleted by free's email server. No 
matter, I got the message directly.

> I have good news! I have a patch that uses memory fencing when writing,
> and atomic loads when reading, and I've run it for around 16 hours
> without triggering the issue. The issue makes sense when interpreted
> from a "you didn't make sure the changes arrive on other cores in the
> right order" standpoint, and the solution should be correct, too.

Excellent !

> Is it better to apply it to 2024.09 and concentrate on getting that all
> through, or would it be wiser to try packaging 2024.12? 

I'd rather to the former.

> Right now I'm at
> the start of a little respiratory viral infection (apparently not the
> big one) so I have to assume this week, maybe next week, I won't be able
> to do anything that requires much concentration. In that case, 2024.09
> with a little patch may be better.

Indeed. One step at a time.

> I do see a couple of packages blocked by the FTBFS bug, so I think I
> need to go through these bugs and send a mail to mark them as resolved.
> I am not exactly sure how, though. Can I mark them as "fixed by the
> transition we did"? Does it require a "fixed in version XYZ"? Because
> there's not really "a version that is broken" vs "a version where it's
> fixed" for these packages.

Let's first fix rakudo and clear its bugs. Then we'll see what needs to be done 
for raku modules.

> Glad to say I believe the build hang issue is resolvable through just a
> patch to moarvm, 

ok, then we'll need to re-assign 1086555 to moarvm an indicated that it 
"affects" rakudo.

> it shouldn't even require an upgrade to nqp and rakudo,
> except if it's required to increase the dependency in nqp to require the
> new moarvm, and the dependency in rakudo to require that new nqp.

Let's update moarvm and wait for it to go to testing. Then we clear the 
1086555 bug. Then all rebuilds will be done with the new moarvm.

> I am not sure what the options are for "only new versions on some
> arches", or if it doesn't matter and we just submit a new source package
> with a patch applied and the rest happens by itself?

Doesn't matter. Let's rebuild moarvm on all arches

All the best