From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Bengt Richter <bokr@bokr.com>
Cc: 37233-done@debbugs.gnu.org
Subject: bug#37233: lsblk not up to date in util-linux
Date: Fri, 30 Aug 2019 16:03:12 +0200 [thread overview]
Message-ID: <87y2zapx7j.fsf@nckx> (raw)
In-Reply-To: <20190830094252.GA16694@PhantoNv4ArchGx.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
Bengt,
Sorry you had to debug that!
Bengt Richter 写道:
> …then I get the desired output above. The difference is
> apparently
> util-linux 2.32.1 vs the newer 2.34, where the newer one
> understands
> more field names for -o ...
[…]
> Hope somebody can update it.
> I think I found the updated version at
> https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.34/util-linux-2.34.tar.xz
Guix's util-linux package was already updated to 2.34 in June
(commit ac3842ef on core-updates), and it will be available when
core-updates is merged into master. That should be very soon now.
I'm closing this bug for that reason.
Updates of core Guix packages like these take a while to trickle
down to users because ‘everything’ depends on them, and when
they change ‘everything’ needs to be rebuilt, so we need to
‘batch’ these changes somehow to avoid rebuilding the world ever
two days. Search for ‘staging’ and ‘core-updates’ in the
manual. Unfortunately, core-updates in particular always takes
longer to fix up and merge than expected.
Until that happens, you can define and install your own updated
util-linux.
(define-public util-linux/latest
(package
(inherit util-linux)
(name "util-linux")
(version "2.34")
(source …))) ; updated URL
This is similar to what we already do for security updates in
Guix.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-08-30 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 9:42 bug#37233: lsblk not up to date in util-linux Bengt Richter
2019-08-30 14:03 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2zapx7j.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=37233-done@debbugs.gnu.org \
--cc=bokr@bokr.com \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).