Bug#1027686: transition: rakudo

2023-01-18 Thread Dominique Dumont
On Wednesday, 18 January 2023 03:03:37 CET M. Zhou wrote: > I have uploaded moarvm, nqp, and rakudo to unstable. > They turned green on release architectures. > The ppc64el buildd lags a little bit but I believe the result will be > green as well based on the previous no-change build in

Bug#1027686: transition: rakudo

2023-01-17 Thread M. Zhou
I have uploaded moarvm, nqp, and rakudo to unstable. They turned green on release architectures. The ppc64el buildd lags a little bit but I believe the result will be green as well based on the previous no-change build in experimental. On Sun, 2023-01-15 at 19:09 +0100, Sebastian Ramacher wrote:

Bug#1027686: transition: rakudo

2023-01-15 Thread Sebastian Ramacher
Control: tags -1 = confirmed On 2023-01-15 18:49:24 +0100, Dominique Dumont wrote: > On Sunday, 15 January 2023 15:21:55 CET Sebastian Ramacher wrote: > > > I've found where compiler-id is computed. I'm going patch rakudo in > > > experimental so that compiler-id depends only on source files and

Bug#1027686: transition: rakudo

2023-01-15 Thread Dominique Dumont
On Sunday, 15 January 2023 15:21:55 CET Sebastian Ramacher wrote: > > I've found where compiler-id is computed. I'm going patch rakudo in > > experimental so that compiler-id depends only on source files and nqp > > version. This patch will land in experimental. > > Okay, please let me know once

Bug#1027686: transition: rakudo

2023-01-15 Thread Sebastian Ramacher
On 2023-01-13 14:38:48 +0100, Dominique Dumont wrote: > On Wed, 11 Jan 2023 18:45:41 +0100 Dominique Dumont wrote: > > > Can the computation of the ID be patched to be independent of the > > > build path? > > > > I haven't figured out completely how this compiler-id is created. > > I've found

Bug#1027686: transition: rakudo

2023-01-13 Thread Dominique Dumont
On Wed, 11 Jan 2023 18:45:41 +0100 Dominique Dumont wrote: > > Can the computation of the ID be patched to be independent of the > > build path? > > I haven't figured out completely how this compiler-id is created. I've found where compiler-id is computed. I'm going patch rakudo in

Bug#1027686: transition: rakudo

2023-01-11 Thread Dominique Dumont
On Tuesday, 10 January 2023 11:21:32 CET Sebastian Ramacher wrote: > Control: tags -1 moreinfo > > On 2023-01-09 13:54:08 -0500, M. Zhou wrote: > > I missed the detail that the compiler ID even changes for different > > architecture.. which may not be good. > > Is it required that the build path

Bug#1027686: transition: rakudo

2023-01-11 Thread Dominique Dumont
On Monday, 9 January 2023 19:54:08 CET M. Zhou wrote: > Is it possible for us to slightly modify the postinst script to > recompile the cache locally when the compiler id mismatches? I'd rather not. Untangling pre-compilation issues is hard enough. In case of problem I dont' want to wonder

Bug#1027686: transition: rakudo

2023-01-10 Thread Sebastian Ramacher
Control: tags -1 moreinfo On 2023-01-09 13:54:08 -0500, M. Zhou wrote: > I missed the detail that the compiler ID even changes for different > architecture.. which may not be good. Is it required that the build path of the compiler influences the ID? Can the computation of the ID be patched to

Bug#1027686: transition: rakudo

2023-01-09 Thread M. Zhou
I missed the detail that the compiler ID even changes for different architecture.. which may not be good. Is it possible for us to slightly modify the postinst script to recompile the cache locally when the compiler id mismatches? The fallback script rakudo-helper.pl can at least make sure a

Bug#1027686: transition: rakudo

2023-01-07 Thread Dominique Dumont
On Saturday, 7 January 2023 11:58:29 CET you wrote: > > Unfortunately, the compiler-id also depends on the build directory. Which > > means that the compiler id changes between arches. > > This should be fixed first. Otherwise every rebuild of the compiler will > require all reverse dependencies

Bug#1027686: transition: rakudo

2023-01-07 Thread Sebastian Ramacher
Control: tags -1 moreinfo On 2023-01-02 17:02:22 +0100, Dominique Dumont wrote: > On Sunday, 1 January 2023 22:38:43 CET M. Zhou wrote: > > Specifically, the pre-compiled cache shipped in reverse dependencies > > relies on a matching compiler ID. Hence, we added the compiler ID into the > >

Bug#1027686: transition: rakudo

2023-01-02 Thread Dominique Dumont
On Sunday, 1 January 2023 22:38:43 CET M. Zhou wrote: > Specifically, the pre-compiled cache shipped in reverse dependencies > relies on a matching compiler ID. Hence, we added the compiler ID into the > virtual package to ensure cache compatibility: raku-api-2022.12+e556a5c0 > The compiler ID

Bug#1027686: transition: rakudo

2023-01-01 Thread M. Zhou
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: rak...@packages.debian.org Control: affects -1 + src:rakudo Dear release team, We would like to start the transition for rakudo, updating rakudo to the latest version in