Github messages for voidlinux
 help / color / mirror / Atom feed
From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: re-enabling statx support on coreutils
Date: Thu, 02 Apr 2020 14:17:56 +0200	[thread overview]
Message-ID: <20200402121756.K4kSzf33VTeucvX7F77Rw1HDujDdqNGCqFZ3W6EHoAc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20556@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

New comment by ailiop-git on void-packages repository

https://github.com/void-linux/void-packages/issues/20556#issuecomment-607810623

Comment:
3.16 doesn't seem to be booting at all (getting stuck in early boot process after decompress/parsing ELF, and/or cold-rebooting). I can try to debug it later on a VM if there's still interest in having this kernel around, let me know.

3.18, 4.9 boot fine, and coreutils doesn't complain with statx enabled (glibc silently fallsback to stat).

BTW 3.18 isn't LTS upstream (@pullmoll should we consider dropping it?)


  parent reply	other threads:[~2020-04-02 12:17 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 17:19 [ISSUE] " ailiop-git
2020-04-01 17:47 ` xtraeme
2020-04-01 18:02 ` ailiop-git
2020-04-01 18:07 ` xtraeme
2020-04-01 18:53 ` ailiop-git
2020-04-01 19:06 ` xtraeme
2020-04-01 21:18 ` ailiop-git
2020-04-02  9:40 ` xtraeme
2020-04-02 11:12 ` xtraeme
2020-04-02 11:21 ` Johnnynator
2020-04-02 11:23 ` pullmoll
2020-04-02 11:26 ` ailiop-git
2020-04-02 11:29 ` pullmoll
2020-04-02 11:32 ` xtraeme
2020-04-02 12:12 ` pullmoll
2020-04-02 12:14 ` xtraeme
2020-04-02 12:17 ` ailiop-git [this message]
2020-04-02 12:19 ` xtraeme
2020-04-02 12:20 ` xtraeme
2020-04-02 12:20 ` pullmoll
2020-04-02 12:21 ` pullmoll
2020-04-02 12:22 ` xtraeme
2020-04-02 12:23 ` pullmoll
2020-04-02 12:23 ` xtraeme
2020-04-02 12:24 ` xtraeme
2020-04-02 12:26 ` xtraeme
2020-04-02 12:28 ` ailiop-git
2020-04-02 12:34 ` pullmoll
2020-04-02 12:35 ` pullmoll
2020-04-02 12:40 ` xtraeme
2020-04-02 12:40 ` xtraeme
2020-04-02 12:41 ` pullmoll
2020-04-02 12:41 ` pullmoll
2020-04-02 12:47 ` xtraeme
2020-04-02 12:59 ` xtraeme
2020-04-02 13:25 ` ailiop-git
2020-04-02 13:30 ` xtraeme
2020-04-02 13:32 ` xtraeme
2020-04-02 13:32 ` [ISSUE] [CLOSED] " xtraeme

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200402121756.K4kSzf33VTeucvX7F77Rw1HDujDdqNGCqFZ3W6EHoAc@z \
    --to=ailiop-git@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).