• [gentoo-dev] Call for testing from toolchain team: glibc-2.34

    From Sam James@21:1/5 to All on Thu Oct 28 01:40:02 2021
    Hi,

    toolchain@ would appreciate if folks could keyword glibc-2.34 locally
    on non-production machines to help root out any bugs.

    The tracker bug is doing pretty well at this point with most remaining
    issues being in last-rited packages or being tracked upstream: https://bugs.gentoo.org/803482.

    There are no plans to keyword glibc-2.34 yet given there's
    a few large changes and we've not yet got over the libxcrypt
    hump (that's coming very shortly, stabilisation planned for
    2021-11-01!). But you can't start planning too early ;)

    I would not recommend doing this on a machine
    with Chromium or anything Electron based for now
    as I haven't had a chance to check if the sandbox stuff
    has been updated. I _think_ Firefox is fine now (at least
    in the latest versions >= 91?).

    If you're able, please therefore keyword glibc-2.34 on
    systems where you're up for a bit of experimentation,
    and ideally rebuild (-ev @world) and report any bugs.

    If you feel generous, run FEATURES=test on some/all
    stuff too.

    Please drop into #gentoo-toolchain if you have any
    questions or issues we need to debug together.

    Cheers!

    Best,
    sam

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Piotr Karbowski@21:1/5 to All on Thu Nov 11 16:50:02 2021
    Happy to report that everything works fine with sys-libs/glibc-2.34-r1,
    I have rebuilt whole @world (1300+ packages) without a single failure,
    thought I did it without FEATURES=test.

    I can sign off this glibc as good enough to go into ~arch.

    -- Piotr.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tomas Mozes@21:1/5 to sam@gentoo.org on Thu Nov 11 18:30:01 2021
    On Thu, Oct 28, 2021 at 1:39 AM Sam James <sam@gentoo.org> wrote:

    Hi,

    toolchain@ would appreciate if folks could keyword glibc-2.34 locally
    on non-production machines to help root out any bugs.

    The tracker bug is doing pretty well at this point with most remaining
    issues being in last-rited packages or being tracked upstream: https://bugs.gentoo.org/803482.

    There are no plans to keyword glibc-2.34 yet given there's
    a few large changes and we've not yet got over the libxcrypt
    hump (that's coming very shortly, stabilisation planned for
    2021-11-01!). But you can't start planning too early ;)

    I would not recommend doing this on a machine
    with Chromium or anything Electron based for now
    as I haven't had a chance to check if the sandbox stuff
    has been updated. I _think_ Firefox is fine now (at least
    in the latest versions >= 91?).

    If you're able, please therefore keyword glibc-2.34 on
    systems where you're up for a bit of experimentation,
    and ideally rebuild (-ev @world) and report any bugs.

    If you feel generous, run FEATURES=test on some/all
    stuff too.

    Please drop into #gentoo-toolchain if you have any
    questions or issues we need to debug together.

    Cheers!

    Best,
    sam


    I only had a hard time with elastic/filebeats. It crashed soon after
    starting, luckily it got fixed upstream ( https://githubmemory.com/repo/elastic/apm-server/issues/6238). It's on PR https://github.com/gentoo/gentoo/pull/22823/commits/0e8fe167b013b8cefad3c3da9d0beec9887ab15c


    Tomas

    <div dir="ltr">On Thu, Oct 28, 2021 at 1:39 AM Sam James &lt;<a href="mailto:sam@gentoo.org">sam@gentoo.org</a>&gt; wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);
    padding-left:1ex">Hi,<br>

    toolchain@ would appreciate if folks could keyword glibc-2.34 locally<br>
    on non-production machines to help root out any bugs.<br>

    The tracker bug is doing pretty well at this point with most remaining<br> issues being in last-rited packages or being tracked upstream:<br>
    <a href="https://bugs.gentoo.org/803482" rel="noreferrer" target="_blank">https://bugs.gentoo.org/803482</a>.<br>

    There are no plans to keyword glibc-2.34 yet given there&#39;s<br>
    a few large changes and we&#39;ve not yet got over the libxcrypt<br>
    hump (that&#39;s coming very shortly, stabilisation planned for<br> 2021-11-01!). But you can&#39;t start planning too early ;)<br>

    I would not recommend doing this on a machine<br>
    with Chromium or anything Electron based for now<br>
    as I haven&#39;t had a chance to check if the sandbox stuff<br>
    has been updated. I _think_ Firefox is fine now (at least<br>
    in the latest versions &gt;= 91?).<br>

    If you&#39;re able, please therefore keyword glibc-2.34 on<br>
    systems where you&#39;re up for a bit of experimentation,<br>
    and ideally rebuild (-ev @world) and report any bugs.<br>

    If you feel generous, run FEATURES=test on some/all<br>
    stuff too.<br>

    Please drop into #gentoo-toolchain if you have any<br>
    questions or issues we need to debug together.<br>

    Cheers!<br>

    Best,<br>
    sam<br>
    <br></blockquote><div><br></div><div>I only had a hard time with elastic/filebeats. It crashed soon after
    starting, luckily it got fixed upstream
    (<a href="https://githubmemory.com/repo/elastic/apm-server/issues/6238">https://githubmemory.com/repo/elastic/apm-server/issues/6238</a>). It&#39;s on PR <a href="https://github.com/gentoo/gentoo/pull/22823/commits/
    0e8fe167b013b8cefad3c3da9d0beec9887ab15c">https://github.com/gentoo/gentoo/pull/22823/commits/0e8fe167b013b8cefad3c3da9d0beec9887ab15c</a>  </div><div><br></div><div>Tomas<br></div></div></div>

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