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

  • Re: No mips64el porterbox?

    From Sebastiaan Couwenberg@21:1/5 to Julien Puydt on Tue Mar 1 10:40:01 2022
    On 3/1/22 10:28, Julien Puydt wrote:
    Is there really no mips64el porterbox, or is it only a transitory
    situation?

    eller.debian.org has mips64el chroots.

    Kind Regards,

    Bas

    --
    GPG Key ID: 4096R/6750F10AE88D4AF1
    Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Julien Puydt@21:1/5 to All on Tue Mar 1 10:30:01 2022
    Hi,

    one of my package has a failure on mips64el and upstream is ready to
    help me find the cause and debug the issue.

    Unfortunately, on https://db.debian.org/machines.cgi I only see five
    developer machines on this architecture -- all buildd!

    Is there really no mips64el porterbox, or is it only a transitory
    situation?

    Cheers,

    J.Puydt

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YunQiang Su@21:1/5 to All on Tue Mar 1 10:40:01 2022
    mips64el uses the same porterbox with mipsel, since mips32 and mips64 are compatiable; and all of our machines are in fact 64bit.

    Julien Puydt <[email protected]> 于 2022年3月1日周二 下午5:28写道：

    Hi,

    one of my package has a failure on mips64el and upstream is ready to
    help me find the cause and debug the issue.

    Unfortunately, on https://db.debian.org/machines.cgi I only see five developer machines on this architecture -- all buildd!

    Is there really no mips64el porterbox, or is it only a transitory
    situation?

    Cheers,

    J.Puydt



    <div dir="auto"><div>mips64el uses the same porterbox with mipsel, since mips32 and mips64 are compatiable; and all of our machines are in fact 64bit.<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Julien Puydt &lt;<a href="mailto:
    [email protected]">[email protected]</a>&gt; 于 2022年3月1日周二 下午5:28写道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>

    one of my package has a failure on mips64el and upstream is ready to<br>
    help me find the cause and debug the issue.<br>

    Unfortunately, on <a href="https://db.debian.org/machines.cgi" rel="noreferrer noreferrer" target="_blank">https://db.debian.org/machines.cgi</a> I only see five<br>
    developer machines on this architecture -- all buildd!<br><br>
    Is there really no mips64el porterbox, or is it only a transitory<br> situation?<br><br>
    Cheers,<br>

    J.Puydt<br>

    </blockquote></div></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Gard Spreemann@21:1/5 to Julien Puydt on Tue Mar 1 10:40:01 2022
    Julien Puydt <[email protected]> writes:

    Hi,

    one of my package has a failure on mips64el and upstream is ready to
    help me find the cause and debug the issue.

    Unfortunately, on https://db.debian.org/machines.cgi I only see five developer machines on this architecture -- all buildd!

    Is there really no mips64el porterbox, or is it only a transitory
    situation?

    Hi,

    How about eller.debian.org?

    $ uname -a
    Linux eller 4.19.0-18-octeon #1 SMP Debian 4.19.208-1 (2021-09-29) mips64 GNU/Linux
    $ lscpu
    Architecture: mips64
    Byte Order: Little Endian


    -- Gard

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

    iQJGBAEBCgAwFiEEz8XvhRCFHnNVtV6AnRFYKv1UjPoFAmId6LQSHGdzcHJAbm9u ZW1wdHkub3JnAAoJEJ0RWCr9VIz68UUP/0X3qENSiZOz0/mIl3j9MhLZ/l44lKrN uce+IWL2h8XEw0SEaGQmHpIIh8MP/WrIps/IwLjgsPrzi40aIQIc/0hroQwipO3d BHsuShG0JRSxYd9DD8pZbdh8V3vNaA0OBTu5MCmSEloJEoba54MKCB0Oh6v1XTdd KI9pihLj2FKBX36PvWKRU9uEqVxxycNGrpUg2TFwapVxQ44P9PjFkJH9eUoSt0a4 FpaH7FOGoDzvjsWq016rIqRAZGXbmtRwYSJ5dyrg0ujxH1ISe5DSl4vYgFCgzJAn YuTJ9u/qbdOuhVTZfsmjmWyqOSeAj2y2IwCzNVnoe1VvY9xgTH8TXf7kci0AQ9wH ycWl00nqDuuywbinaQEzZEXAqLaykk+z06YTsfGOYYZkeP5dvI97F9+NCsKahjze ZbuTPB0FNoGGxbN3zUF+NA32A2BeKopB0wjAf3PHdzt0zz65Jiue0N4Yf+x+1ERW Mvt7gdij5jrrPx9JtXQxytarG/XiM3I58wY6+j+SnN1WeykZaSfpSiK/otMIbWt6 1odtuzId0V/RUsjzYH+9irlXJyzEvyh11HTEHGdggr1Mc0yjWyLbNJ30RoQuwxxl Fs47O5hDmNeTo/9sOju+OAe0GlHBZ6aDBmzh5BOH+e0tsyLkdgejFV0rTVkS2bbd
    zRhtArowAHfW
    =CUVm
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Julien Puydt@21:1/5 to All on Tue Mar 1 11:00:01 2022
    Le mardi 01 mars 2022 à 10:34 +0100, Sebastiaan Couwenberg a écrit :
    On 3/1/22 10:28, Julien Puydt wrote:
    Is there really no mips64el porterbox, or is it only a transitory situation?

    eller.debian.org has mips64el chroots.


    How do I use one of those and not a mipsel one? I'm using https://dsa.debian.org/doc/schroot/ as usual, and it looks like I'm
    getting a mipsel and not mips64el...

    Thanks,

    J.Puydt

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?B?SsOpcsOpbXkgTGFs?=@21:1/5 to [email protected] on Tue Mar 1 11:00:01 2022
    On Tue, Mar 1, 2022 at 10:28 AM Julien Puydt <[email protected]> wrote:

    Hi,

    one of my package has a failure on mips64el and upstream is ready to
    help me find the cause and debug the issue.

    Unfortunately, on https://db.debian.org/machines.cgi I only see five developer machines on this architecture -- all buildd!


    The "architecture" column filter is not the one to use to find a porter box
    for a given architecture,
    that's why you did not find it.

    Jérémy

    <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 1, 2022 at 10:28 AM Julien Puydt &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote
    class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>

    one of my package has a failure on mips64el and upstream is ready to<br>
    help me find the cause and debug the issue.<br>

    Unfortunately, on <a href="https://db.debian.org/machines.cgi" rel="noreferrer" target="_blank">https://db.debian.org/machines.cgi</a> I only see five<br>
    developer machines on this architecture -- all buildd!<br></blockquote><div><br></div><div>The &quot;architecture&quot; column filter is not the one to use to find a porter box for a given architecture,</div><div>that&#39;s why you did not find it.</div><
    <br></div><div>Jérémy</div></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sebastiaan Couwenberg@21:1/5 to Julien Puydt on Tue Mar 1 11:10:01 2022
    On 3/1/22 10:54, Julien Puydt wrote:
    Le mardi 01 mars 2022 à 10:34 +0100, Sebastiaan Couwenberg a écrit :
    On 3/1/22 10:28, Julien Puydt wrote:
    Is there really no mips64el porterbox, or is it only a transitory
    situation?

    eller.debian.org has mips64el chroots.


    How do I use one of those and not a mipsel one? I'm using https://dsa.debian.org/doc/schroot/ as usual, and it looks like I'm
    getting a mipsel and not mips64el...

    Specify the mips64el chroot when creating it:

    schroot -b -c sid_mips64el-dchroot -n $sessionid

    Kind Regards,

    Bas

    --
    GPG Key ID: 4096R/6750F10AE88D4AF1
    Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?B?SsOpcsOpbXkgTGFs?=@21:1/5 to [email protected] on Sat Mar 19 17:00:01 2022
    On Sat, Mar 19, 2022 at 4:40 PM Nilesh Patra <[email protected]> wrote:

    Quoting Julien Pudyt
    Le mardi 01 mars 2022 à 10:34 +0100, Sebastiaan Couwenberg a écrit :
    On 3/1/22 10:28, Julien Puydt wrote:
    Is there really no mips64el porterbox, or is it only a transitory
    situation?

    eller.debian.org has mips64el chroots.


    How do I use one of those and not a mipsel one? I'm using https://dsa.debian.org/doc/schroot/ as usual, and it looks like I'm
    getting a mipsel and not mips64el...

    Just in case this helps, I use this very helpful script from Enrico Zini,
    you can find it here[1]

    So for mips64el, just do

    $ debug-on-porterbox mips64el --host eller.debian.org


    Already documented here (since 2021-01), with a link to Enrico's blog post: https://wiki.debian.org/PorterBoxHowToUse

    <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 19, 2022 at 4:40 PM Nilesh Patra &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote class="gmail_
    quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Quoting Julien Pudyt<br>
    &gt; Le mardi 01 mars 2022 à 10:34 +0100, Sebastiaan Couwenberg a écrit :<br> &gt;&gt; On 3/1/22 10:28, Julien Puydt wrote:<br>
    &gt;&gt; &gt; Is there really no mips64el porterbox, or is it only a transitory<br>
    &gt;&gt; &gt; situation?<br>
    &gt;&gt; <br>
    &gt;&gt; <a href="http://eller.debian.org" rel="noreferrer" target="_blank">eller.debian.org</a> has mips64el chroots.<br>
    &gt;&gt; <br>

    &gt; How do I use one of those and not a mipsel one? I&#39;m using<br>
    &gt; <a href="https://dsa.debian.org/doc/schroot/" rel="noreferrer" target="_blank">https://dsa.debian.org/doc/schroot/</a> as usual, and it looks like I&#39;m<br>
    &gt; getting a mipsel and not mips64el...<br>

    Just in case this helps, I use this very helpful script from Enrico Zini,<br> you can find it here[1]<br>

    So for mips64el, just do<br>

            $ debug-on-porterbox mips64el --host <a href="http://eller.debian.org" rel="noreferrer" target="_blank">eller.debian.org</a></blockquote><div><br></div><div>Already documented here (since 2021-01), with a link to Enrico&#39;s blog post:<br></
    <div><a href="https://wiki.debian.org/PorterBoxHowToUse">https://wiki.debian.org/PorterBoxHowToUse</a></div><div><br></div></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nilesh Patra@21:1/5 to All on Sat Mar 19 16:50:01 2022
    Quoting Julien Pudyt
    Le mardi 01 mars 2022 � 10:34 +0100, Sebastiaan Couwenberg a �crit :
    On 3/1/22 10:28, Julien Puydt wrote:
    Is there really no mips64el porterbox, or is it only a transitory
    situation?

    eller.debian.org has mips64el chroots.


    How do I use one of those and not a mipsel one? I'm using https://dsa.debian.org/doc/schroot/ as usual, and it looks like I'm
    getting a mipsel and not mips64el...

    Just in case this helps, I use this very helpful script from Enrico Zini,
    you can find it here[1]

    So for mips64el, just do

    $ debug-on-porterbox mips64el --host eller.debian.org

    And voila ...

    [1]: https://salsa.debian.org/enrico/debug-on-porterbox

    Regards,
    Nilesh

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

    iQIzBAABCgAdFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmI1+T8ACgkQALrnSzQz afH0+g/+MtzNZOgb9L+nQH0LtaRDR4E7/hHlzVrA0rGOsVlNWoWE9zhn/8VGAOTM Wxl7a9CXydzWKzoSkDoAWgCZxxoSn3Owek4kLMgGoScjMttkcoGfy7AsqKOVGnQc zePEz7SvfRCsyG3Hw7OU0Bc/aUfLcZKudwg5dRJg/wFWdKft1nuK+W7d7QLf4AVn p4flFI6x2akT9RYl1BX7pRay5sCRfDMOPYL/0Mc3wWD4R2v58yLNp59dIFUUm+V4 fLMPNXAHuRAT8+ciii9nJkSuOd/0vMUYf/TPl6qYW1O+OdA59ZR9VH5uWZbZIxDE t1pomp2FR7eNt374N2Ar4u2NslZ3svxllNor+aYm2MxuXDgWUdYRiHeQR25dRQkK McC2kj6f0ZSMoD0BPLVX3nrd1FjAZUqXLUzXk/pb1HgkiNz094y1ctALkbj3vAg5 cdc2HfS+r4pdJLvr/0GnB1mIb7qWCNOfcfCVtMtj0GCkRF5L8P63QSbJNIuzgwri OsJc42/iXAuVaTFGZRjYFpyLVdylIzXs0vt5MyjMk8O46eBaN9WrkCrOdzvtj6Od cSY2WTaHLCHSqXhe5Nk28z0rTf6fwJINw7VubehiD/C0Ty/iXXvUuLNZp8MpqJUl yErHCQfvvRjaw+CAPU6W85SLHMiongteGki62SWv/SkpYxojDMg=
    =dsbX
    -----END PGP SIGNATURE-----

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