1. Forum
  2. Usenet
  3. LINUX.DEBIAN.PORTS.MIPS

  • Bug#867058: golang-1.8: Please enable mips64el in debian/ directory

    From John Paul Adrian Glaubitz@21:1/5 to All on Mon Jul 3 22:00:02 2017
    XPost: linux.debian.bugs.dist

    Source: golang-1.8
    Version: 1.8.3-1
    Severity: normal
    Tags: patch
    User: [email protected]
    Usertags: mips64el

    Hi!

    I just bootstrapped golang-1.8 on mips64el. In order to be able to build the package successfully on mips64el, the architecture needs to be added to the Architecture field in debian/control.in, then debian/control needs to be regenerated using "debian/rules gencontrol". For some reason, the architecture mapping for mips64el->mips64le is already present in debian/helpers/goenv.sh and doesn't need to be added.

    Thanks,
    Adrian

    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - [email protected]
    `. `' Freie Universitaet Berlin - [email protected]
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aurelien Jarno@21:1/5 to John Paul Adrian Glaubitz on Thu Jul 6 10:50:02 2017
    XPost: linux.debian.bugs.dist

    On 2017-07-03 22:53, John Paul Adrian Glaubitz wrote:
    On 07/03/2017 10:20 PM, James Cowgill wrote:
    I was under the impression that the golang maintainers want all architectures bootstrapped from gccgo? This was the reason mips64el support was not in
    stretch despite upstream support for it. If a normal bootstrap would have been acceptable, I would have done it ages ago.

    Why? What difference does it make? If a different bootstrapping compiler results in a different golang compiler after a second rebuild, there is something wrong with the compiler anyway.

    Again I have to point out that you are *not* allowed to upload binary debs to the archive before the corresponding source is uploaded. You need to re-read
    this: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#porter-guidelines

    Please can you actually discuss this with the package maintainers and mips porters _before_ you do anything like this again. You should also read the mips
    related go bugs filed against various golang packages.

    Odd. Last time I did this for fpc [1], you were actually very happy. Now you're getting upset despite the only changes actually necessary are
    two lines changed in debian/control.in and debian/helpers/goenv.sh.

    What's the difference now?


    Don't mix things. He is happy and we are happy that you work on mips
    packages and that you provide patches. He is not happy, and I am also
    not happy that you upload binaries to the archive on your own, without
    leaving a chance to other porters to have a look first. More importantly
    we are not happy at all to see binaries that do not match the sources
    in the archive.

    He told you so by IRC, I can share the logs if everybody involved allow
    me to do that.

    Aurelien

    --
    Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://www.aurel32.net

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

    iQIzBAEBCgAdFiEEd0YmQqnvlP0Pdxltupx4Bh3djJsFAlld51oACgkQupx4Bh3d jJsX7xAAigCgczToBKuWzko8DSWHIXtUMpquMLAxYpgzacitbhU1A9uA4h/aiH7s lrISxEagbVmtrycyeBfyvr9vgLMrPtg4smzoddfhpqwhNYRJf3x3K08oDFEWs8AK wttmYP3TOhRoHGsgd/QQd0/71sllba17LsyL9DCCrO0jWwPTupTBqrdQaA1LSS8d weRCdj/y1zb8cGkzy5e7Z5QaOpeE8aiWkeTlFcmKLzXEmbmWN7H4ucfpVoQ7vA+8 1eXKY6D+bsEOD1IZcqLuWnC0EzvW2bb0EqgenCNmY8Wp713kbgcDlVwpTZ1hsPYz /BqV0g2iUv1DV29hGTfrfJdAGZXoLH5K0Eobw/oC0T/WxJBBAvCI4YPXJYQsdxAw wPgjs1Xo4SZB/RnoTc/g6ybJCRXiDg+W+SpQeB5JPB4dlZUyeVX3GTHbiilbrOma o/ZPYzzp21dF0Ol+5opowFtd4qfWeOG+cMEStCocUJld7JMKzNbQzXVqK1pA7SvX wLdhB1u6cBev+NYk1pnyFHPf4wW9mVqgIYX/9C7bJ96umeJvynB3jVzg26IE4w5i DAQlReLkTxsLbh3PnE3EfNtfrJe4RTxLI7rXOdCJv60zPZIL1W97lMT3k9qN6UIV B3onYCKIr8sVEcaT+FrLvmSzz8OJ/WSLJL80BfIvt7x+G413sAI=
    =d72h
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet
  • From James Cowgill@21:1/5 to John Paul Adrian Glaubitz on Mon Jul 3 23:30:01 2017
    XPost: linux.debian.bugs.dist
    Copy: [email protected]
    Copy: [email protected]

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DuDo5N6C6mFl6UEk6nLFxqSgQOVDFWi9n
    Content-Type: text/plain; charset=utf-8
    Content-Language: en-US
    Content-Transfer-Encoding: quoted-printable

    Hi Adrian,

    On 03/07/17 19:46, John Paul Adrian Glaubitz wrote:
    Source: golang-1.8
    Version: 1.8.3-1
    Severity: normal
    Tags: patch
    User: [email protected]
    Usertags: mips64el

    Hi!

    I just bootstrapped golang-1.8 on mips64el. In order to be able to build the package successfully on mips64el, the architecture needs to be added to the Architecture field in debian/control.in, then debian/control needs to be regenerated using "debian/rules gencontrol". For some reason, the architecture
    mapping for mips64el->mips64le is already present in debian/helpers/goenv.sh and doesn't need to be added.

    I was under the impression that the golang maintainers want all
    architectures bootstrapped from gccgo? This was the reason
    mips64el support was not in stretch despite upstream support for it.
    If a normal bootstrap would have been acceptable, I would have done it
    ages ago.

    Again I have to point out that you are *not* allowed to upload binary
    debs to the archive before the corresponding source is uploaded. You
    need to re-read this: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#porter-guidelines

    Please can you actually discuss this with the package maintainers and
    mips porters _before_ you do anything like this again. You should also
    read the mips related go bugs filed against various golang packages.

    Thankfully you didn't upload golang-defaults so a mass-build of go
    packages wasn't triggered...

    [On a related note, the gccgo patches for mips64el have now been merged
    into GCC master]

    James


    --DuDo5N6C6mFl6UEk6nLFxqSgQOVDFWi9n--

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

    iQIzBAEBCgAdFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAllapxEACgkQx/Fnbeot Ae/6RBAArLNvNmYT6kV3Rv+XC6+NmxrjBp0ig/yaQ5F8HqKsqTMNgfXt3iUeb4D8 piKIokbDEgkJO2rpmSnDxjKmOTRkjqc5rOynvb+Ygw9TNxWofbJoruFJleH0MlUQ SoNSYdrlpj3yPdPLQ3YLpJalqeu9hIdfH/deYj0UGu/lIg2Js8i5Za8gRwKRsvp6 3iDuJ/XHHBf6TdxOiLt6qs1kX1+ey5prF3uL/6XTix9cdtJmBb/QkiJB8hjbv1qo 4E7wbnk6JJtQ/blZBSS2aGSq1lchhF576qUycoC9+3DdUa8ZAznDK4hppTHCV2RT v97M5Fvii1XP1U3paIlfblgNwn1idaYRU8YJifUEcpUy9zbv01kTtkW3BmGmXJWy LqqoElWT7mYxQxRs/y6tPx3b6o06hJZmcZPUROTsYTpdrd795MUUkwS+qX0GFB6M KoUIdqXV6x4gW5zsZ+gJ5zwpVgxqqxJZPz0NPXjj7eHU0ln/E3XeXdfFF83KXiWD gSw5fbyc1DbyCHtL/472Auo37FNiX2LNkiIpKSvrVixcTQl6WTzn4tziTQDZ4Ae6 n2a49OHg896tDqNqMxJ043NGBST8sYBuo4qhOUVw/oIjURERdfoAxP9FlYRY9zwH VAedrqSBazsGzfrzD1DGQn0lV4aKB1ruUbDmpJIeBeJnLFhsbYs=
    =6DP4
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to James Cowgill on Tue Jul 4 00:00:02 2017
    XPost: linux.debian.bugs.dist

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    On 07/03/2017 10:20 PM, James Cowgill wrote:
    I was under the impression that the golang maintainers want all architectures bootstrapped from gccgo? This was the reason mips64el support was not in
    stretch despite upstream support for it. If a normal bootstrap would have been acceptable, I would have done it ages ago.

    Why? What difference does it make? If a different bootstrapping compiler results in a different golang compiler after a second rebuild, there is something wrong with the compiler anyway.

    Again I have to point out that you are *not* allowed to upload binary debs to the archive before the corresponding source is uploaded. You need to re-read
    this: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#porter-guidelines

    Please can you actually discuss this with the package maintainers and mips porters _before_ you do anything like this again. You should also read the mips
    related go bugs filed against various golang packages.

    Odd. Last time I did this for fpc [1], you were actually very happy. Now
    you're getting upset despite the only changes actually necessary are
    two lines changed in debian/control.in and debian/helpers/goenv.sh.

    What's the difference now?

    Thankfully you didn't upload golang-defaults so a mass-build of go packages wasn't triggered...

    That was never the plan.

    Adrian

    [1] https://lists.debian.org/debian-mips/2017/05/msg00008.html

    - --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - [email protected]
    `. `' Freie Universitaet Berlin - [email protected]
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAllarsYACgkQdCY7N/W1 +RMfwhAAvT8glilcl1MSV5BfSATlQ9SpSto4xovQADmxnuNf1Lzmd4m9y39J28pG UWmEufxO1wHVaad6jyQcH4UDXeAEpaxYF1pIxF+xcz5I01/TaQRQ3I4JCwIPpDZp u3pSEhdZ7Hrr27EWu00UBXvo4O6HLw1IuSJ6MzwZ3LHVXz0zxCtJs+m8lN5sLptw 4sq8mykd/MhDcx+Zpt5nlCKO1Ba/v+cp8WctK/zxDuz0zcNvL7LDUyBPSjeMoPMM qB1hYniCZ8aJETwz7EjzDoJj2KwGtHSjq/m6x/r9GJz7iKSldTdZULqz4MHx3gXx Mqdoau2ar9JbJmF0yqMQPf7ECUzaYYLwDla5Otz9WSyaOyzGIiphO6GSYxnCx2zj dLZM7RsIsmbDrs+AN6UWnsWAWcGZ7sORe1AR0gvnJQXLEBTRBkPbeVaI59b1j+B5 lLAGYyeKIEYjAcReRw1zVt/Ke8KyittizcrcKIPjl9/Ir9oG2GcKXZjvnTZG2jtg WqHOYCLmP/wFRTeEn3aP9WBsaG1krErQ1NrQZ9d7b34wCmWvexCRsKMWtnZdVI0T 68JL6MyvkPI34MvV4jdbnXBjZJowCg0OdCDpr+Vj9DYax1M4wLGvh/vZ24Plokgg Skx/2fOPU/iqfz4y3OEpJfY2t1GiZXaViZngkX40nEnfLRasaHU=
    =KYla
    -----END PGP SIGNATURE-----

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