From: Randy Dunlap <rdunlap@infradead.org>
To: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: kernel bugzilla entries for util-linux
Date: Tue, 10 Apr 2018 10:11:39 -0700 [thread overview]
Message-ID: <fb5b024f-575b-cbf2-4170-b7c7239946d3@infradead.org> (raw)
Hi,
There are a number of util-linux related bug entries at https://bugzilla.kernel.org/,
mostly in the Tools/Other category.
Can I do anything with these?
E.g., I could add a comment in each one of them to report the bug/request to
the util-linux mailing list.
Or I could forward each one individually to the util-linux mailing list.
Or I could ignore them. :)
If any of these have already been fixed, I can also mark them closed/fixed,
although it would be better to have a commit ID or release version info for
the fix.
thanks,
--
~Randy
summary:
Bug 199079 - blkid reports that a disk that once was a zfs pool, but is not anymore, is still a zfs pool
Bug 198565 - [util-linux] gid lookups with getgrnam_r() should handle an ERANGE error, by retrying with a larger buffer.
Bug 198039 - [util-linux] look parameter for giving back line numbers.
Bug 198011 - [util-linux] look is ignoring locale.
Bug 197471 - fdisk does not display c/h/s values correctly
Bug 194857 - building util-linux-2.29.2 doesn't seem to be including libs from <proj>/lib @ link
Bug 117261 - util-linux's cal gives wrong leap years before 1800
Bug 108521 - [util-linux] column -s X -t fails when there are colour escapes before X
Bug 100021 - [util-linux] v2.24 ... v2.26.2: bug in regression test script for partx
Bug 93981 - [util-linux] login, shells, file paths, and the /usr/bin/ merge
Bug 101111 - [util-linux] scriptreplay replays typescript created by "script -q" wrongly
next reply other threads:[~2018-04-10 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 17:11 Randy Dunlap [this message]
2018-04-12 17:15 ` kernel bugzilla entries for util-linux Ruediger Meier
2018-04-12 22:19 ` Randy Dunlap
2018-04-13 8:36 ` Karel Zak
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=fb5b024f-575b-cbf2-4170-b7c7239946d3@infradead.org \
--to=rdunlap@infradead.org \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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).