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

[Timo Paulssen]

Hi Everyone,


>> I have a prototype for a "dump everything, categorized" flag for moarvm,
>> plus a corresponding patch that adds dumping of moarvm files to
>> diffoscope, and I will look into this topic more.
> ok.


I have already made one discovery related to build reproducibility, and 
a few pointers for possible optimizations, plus I've learned stuff about 
an area of MoarVM I hadn't touched much before, so it's been useful already!

>> Cool, so it's correct to have it in debian/sid like I'm already doing,
>> and we're already well on the way to reaching this goal?
> Yes. One hurdle to cleat is that I made the mistake of trying to use prove6 to
> run non-regression tests during build. This leads to circular dependencies
> when building, which is a problem.
>
> Some package were switched to use Perl's prove, like raku-tap-harness. Could
> you check that all other modules are not depending on prove6 ?


I don't know exactly what such a module usually encompasses, but it 
could be good to have dh-sequence-raku responsible for picking perl's 
prove or prove6 if it's available, and have prove6 just in the suggests?

>> If I'm not mistaken, I have nothing else to do right now for at least
>> this situation. I will wait for you to tell me what I should do next :)
> - remove prove6 dependencies from all raku modules


I committed and pushed to the debian/sid branch on a few modules. I had 
hoped I could just point you at 
https://salsa.debian.org/groups/perl6-team/modules/-/activity to find 
out what I have actually done, so I didn't write it down or anything, 
but salsa is still behind on some things, huh. So here's a summary taken 
from my shell history:

  * raku-json-name: dropped prove6
  * raku-json-optin: dropped prove6
  * raku-test-meta: forcepushed over some maybe-messed-up earlier
    attempts at packaging stuff, then dropped the prove6 dependency, and
    also created a branch version_upgrade with an upgrade from 0.0.17 to
    0.0.20
  * raku-hash-merge: dropped prove6
  * raku-uri: dropped prove6, created a branch upgrade_0.3.7;
    dh-make-raku added README.md to debian/raku-uri.docs, I'm not 100%
    sure if that's right, but probably?

And that should be everything!

> - upload modified packages (me)
> - trigger rakudo transition (me)
>
> Then we'll see the next steps.
>
> All the best


This is getting exciting :)

Kind Regards,
   - Timo