Rakudo has a transition tracker and then what ?
Hello I'm a bit lost with the transition tracker and ben. Rakudo modules used to be delivered as Rako source and pre-compiled at installation time. This was not very user friendly, and I've modified the package so that Raku modules are pre-compiled at package build time. Unfortunately, this pre-compilation process must be redone at each new rakudo release (every month or so). Hoping to automate this process, I've setup a transition tracker for Rakudo [1]. I was expecting that these tracked packages would be rebuilt automagically, but that did not happen. All package are red and nothing was rebuilt. What did I miss ? Is there some setup required elsewhere ? All the best Dod [1] https://release.debian.org/transitions/html/rakudo.html
Re: Rakudo has a transition tracker and then what ?
Hi Dod, On 03-02-2022 18:53, Dominique Dumont wrote: Hoping to automate this process, I've setup a transition tracker for Rakudo [1]. See https://lists.debian.org/debian-release/2022/02/msg00029.html and follow-up messages. Paul OpenPGP_signature Description: OpenPGP digital signature
Re: Rakudo has a transition tracker and then what ?
Quoting Paul Gevers (2022-02-03 19:08:34) > On 03-02-2022 18:53, Dominique Dumont wrote: > > Hoping to automate this process, I've setup a transition tracker for Rakudo > > [1]. > > See https://lists.debian.org/debian-release/2022/02/msg00029.html and > follow-up messages. As I understand it, librust-* packages are released as arch:any (not arch:all) for this exact reason (I seem to recall some discussion with the ftpmaster and/or release team about that - evidently leading to that praxis being tolerated, except I am totally wrong and the cause for Rust is a different one). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Rakudo has a transition tracker and then what ?
@dod: It looks that we have to change the Architecture: of raku-* packages into any (instead of "all") because there is no binnmu for Arch:all package. Then upon each time we bump the rakudo API version, we just need to file a regular transition bug to the release team and trigger the rebuild. On Thu, 2022-02-03 at 19:13 +0100, Jonas Smedegaard wrote: > Quoting Paul Gevers (2022-02-03 19:08:34) > > On 03-02-2022 18:53, Dominique Dumont wrote: > > > Hoping to automate this process, I've setup a transition tracker > > > for Rakudo > > > [1]. > > > > See > > https://lists.debian.org/debian-release/2022/02/msg00029.html and > > follow-up messages. > > As I understand it, librust-* packages are released as arch:any (not > arch:all) for this exact reason (I seem to recall some discussion > with > the ftpmaster and/or release team about that - evidently leading to > that > praxis being tolerated, except I am totally wrong and the cause for > Rust > is a different one). > > > - Jonas >
Re: Rakudo has a transition tracker and then what ?
On 2022-02-03 17:58:24, M. Zhou wrote: > @dod: It looks that we have to change the Architecture: of raku-* > packages into any (instead of "all") because there is no binnmu > for Arch:all package. Then upon each time we bump the rakudo API > version, we just need to file a regular transition bug to the > release team and trigger the rebuild. If the pre-compiled files are like pyc files for Python, is there are a reason to not follow the same approach? That is, build the pre-compiled files on install. Cheers > > On Thu, 2022-02-03 at 19:13 +0100, Jonas Smedegaard wrote: > > Quoting Paul Gevers (2022-02-03 19:08:34) > > > On 03-02-2022 18:53, Dominique Dumont wrote: > > > > Hoping to automate this process, I've setup a transition tracker > > > > for Rakudo > > > > [1]. > > > > > > See > > > https://lists.debian.org/debian-release/2022/02/msg00029.html and > > > follow-up messages. > > > > As I understand it, librust-* packages are released as arch:any (not > > arch:all) for this exact reason (I seem to recall some discussion > > with > > the ftpmaster and/or release team about that - evidently leading to > > that > > praxis being tolerated, except I am totally wrong and the cause for > > Rust > > is a different one). > > > > > > - Jonas > > > > -- Sebastian Ramacher
Re: Rakudo has a transition tracker and then what ?
Hi Sebastian, Building the files upon installation is exactly the original behavior. The problem is that compilation speed is too slow. Three raku packages could take more than 2 minutes every time when there is a raku upgrade to any version. On Fri, 2022-02-04 at 13:55 +0100, Sebastian Ramacher wrote: > On 2022-02-03 17:58:24, M. Zhou wrote: > > @dod: It looks that we have to change the Architecture: of raku-* > > packages into any (instead of "all") because there is no binnmu > > for Arch:all package. Then upon each time we bump the rakudo API > > version, we just need to file a regular transition bug to the > > release team and trigger the rebuild. > > If the pre-compiled files are like pyc files for Python, is there are > a > reason to not follow the same approach? That is, build the pre- > compiled > files on install. > > Cheers > > > > > On Thu, 2022-02-03 at 19:13 +0100, Jonas Smedegaard wrote: > > > Quoting Paul Gevers (2022-02-03 19:08:34) > > > > On 03-02-2022 18:53, Dominique Dumont wrote: > > > > > Hoping to automate this process, I've setup a transition > > > > > tracker > > > > > for Rakudo > > > > > [1]. > > > > > > > > See > > > > https://lists.debian.org/debian-release/2022/02/msg00029.html a > > > > nd > > > > follow-up messages. > > > > > > As I understand it, librust-* packages are released as arch:any > > > (not > > > arch:all) for this exact reason (I seem to recall some discussion > > > with > > > the ftpmaster and/or release team about that - evidently leading > > > to > > > that > > > praxis being tolerated, except I am totally wrong and the cause > > > for > > > Rust > > > is a different one). > > > > > > > > > - Jonas > > > > > > > >
