1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL

  • Rakudo has a transition tracker and then what ?

    From Dominique Dumont@21:1/5 to All on Thu Feb 3 19:00:01 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Gevers@21:1/5 to All on Thu Feb 3 19:10:02 2022
    To: debian-devel@lists.debian.org (Debian Development)

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------OIpqwo3h7KronL9O29lZG04k
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGkgRG9kLA0KDQpPbiAwMy0wMi0yMDIyIDE4OjUzLCBEb21pbmlxdWUgRHVtb250IHdyb3Rl Og0KPiBIb3BpbmcgdG8gYXV0b21hdGUgdGhpcyBwcm9jZXNzLCBJJ3ZlIHNldHVwIGEgdHJh bnNpdGlvbiB0cmFja2VyIGZvciBSYWt1ZG8NCj4gWzFdLg0KDQpTZWUgaHR0cHM6Ly9saXN0 cy5kZWJpYW4ub3JnL2RlYmlhbi1yZWxlYXNlLzIwMjIvMDIvbXNnMDAwMjkuaHRtbCBhbmQg DQpmb2xsb3ctdXAgbWVzc2FnZXMuDQoNClBhdWwNCg==

    --------------OIpqwo3h7KronL9O29lZG04k--

    -----BEGIN PGP SIGNATURE-----

    wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmH8GiIFAwAAAAAACgkQnFyZ6wW9dQpP rggAmq+jCXc1XVbx073r1AO5lL7tkYlkcUimiPuAF88u7h/etSSLcOXSHcJbeBm7s/uYUijs1Y6Y HSdvZp1j/8eEXUdgMUG6EHPCoZdQniNF6e+UEzXoAruhH9Evsay1ik0msZmIVzWXI1oxdEmcMNNd B6f3ey/NVuQDB5EKYniRmSOMk6Py/hfHVt6KxAs9Wq/6DYiirrteQpH+iklXADcfSagLwbxZn1aA QZl/VoLKDs0AdXmCVUkIJCkNbWSxwigJvL778xHf9nhbScgB8KYAfd9QYjypdYo2/GTe+Ska73bv H8hgTfMvZrq1pkXL+eGOyCN0JK+jF3ySJEJVaGQtqQ==
    =tqFD
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonas Smedegaard@21:1/5 to All on Thu Feb 3 19:20:01 2022
    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 --==============q69460104918497359=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmH8G04ACgkQLHwxRsGg ASFRSg/+LRIu3mted8RExfFsyIhHvDhmZiHtDMdf/tBfAaoPhzJPSlA2lxjggyVm g7G3+j37f3l0kfJ0uolfSrZbox1Jt1l32rZFoCMLovOUXC19HXJqo85IoMp8bGvt G5jW7DUSaj5a25gA/CvQQGDZ28WR/RXLn+OxjgM6c+QtbYV1Y7elaJokRrv1oKk6 63CyywR7gUHeQoZvU0raaKYpMemeX515xuI4AeuPua4ZK6Ijxk7bUBnypDXMd5ok ORIFlVJSgKJP8bKkuCWGmuBkKEh/ueJ0JmOL8MBZc4Wjve5REyHqGcieyWCPN8/f LkPFY14tPuNw6tgIaHtfNQb5bC7MT9MPX6RRkixqGkjf3qtknvNnZMwxndb7PhyF lRE4Fg9Z/PI8pyqUiU1uYJ3AwcXHWtSHRzuulQwBZYBuSHv5AyiZyz+TQ5vK0611 HHW7Uv1iYIAqUjGr/deaPwHZo7mdAGnJazdDmoyQx1x1eeuE2yXYU21mE5LchDCu CSpK7BdWGh1u/kscT
  • From M. Zhou@21:1/5 to Jonas Smedegaard on Fri Feb 4 00:00:01 2022
    @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


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sebastian Ramacher@21:1/5 to M. Zhou on Fri Feb 4 14:00:02 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From M. Zhou@21:1/5 to Sebastian Ramacher on Fri Feb 4 17:40:01 2022
    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





    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)