From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15733] New: xfsprogs outdated
Date: Fri, 18 Aug 2023 14:09:14 +0000 [thread overview]
Message-ID: <bug-15733-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15733
Bug ID: 15733
Summary: xfsprogs outdated
Product: buildroot
Version: 2023.02.3
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
Assignee: unassigned@buildroot.uclibc.org
Reporter: dominique.tronche@eviden.com
CC: buildroot@uclibc.org
Target Milestone: ---
xfsprogs current version is 5.14.2, latest version available is 6.4.0
It would be interesting to switch to a newer version as xfsprogs set big
timestamps by default starting 5.15.0
(https://wiki.archlinux.org/title/XFS#Big_timestamps)
This would allow to avoid the kernel warning:
xfs filesystem being mounted at XYZ supports timestamps until 2038
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-08-18 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 14:09 bugzilla [this message]
2023-09-12 6:31 ` [Buildroot] [Bug 15733] xfsprogs outdated bugzilla
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=bug-15733-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.