util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	util-linux@vger.kernel.org
Subject: [ANNOUNCE] util-linux v2.33.2
Date: Tue, 9 Apr 2019 16:03:58 +0200	[thread overview]
Message-ID: <20190409140358.b3hssvd5bgqmbdtb@ws.net.home> (raw)

The util-linux stable release v2.33.2 is available at

  http://www.kernel.org/pub/linux/utils/util-linux/v2.33/

Feedback and bug reports, as always, are welcomed.

  Karel


util-linux 2.33.2 Release Notes
===============================

agetty:
   - Fix input of non-ASCII characters in get_logname()  [Stanislav Brabec]
   - Switch to 8-bit processing in get_logname() for UTF-8 terminals  [Stanislav Brabec]
bash-completion:
   - umount support relative path and ~ as home shorthands  [Sami Kerola]
blkid:
   - (man) cleanup return code section  [Karel Zak]
build-sys:
   - fix crypt() detection without -lcrypt  [Johannes Nixdorf]
column:
   - Address fill-order confusion in documentation  [dana]
docs:
   - update AUTHORS file  [Karel Zak]
fstrim:
   - Remove commnet about vfat not supporting fstrim  [Marcos Paulo de Souza]
include:
   - add no return function attribute  [Sami Kerola]
include/path.h:
   - remove duplicate header inclusion  [Sami Kerola]
last:
   - do not use non-standard __UT_NAMESIZE  [Patrick Steinhardt]
   - fix wtmp user name buffer overflow [asan]  [Sami Kerola]
libfdisk:
   - (dos) Use strtoul to parse the label-id  [Juerg Haefliger]
   - (gpt) add HiFive Unleashed bootloader partition UUIDs  [Icenowy Zheng]
   - sanity check, to prevent overlapping partitions from being partly reported as free  [Fabian.Kirsch@dlr.de]
libmount:
   - Recognize more fuse filesystems as pseudofs and netfs  [Stanislav Brabec]
   - don't use sscanf() for fstab parsing  [Karel Zak]
   - don't use sscanf() for mountinfo parsing  [Karel Zak]
   - don't use sscanf() for swaps parsing  [Karel Zak]
logger:
   - (man) make more obvious that --server/socket is required  [Karel Zak]
losetup:
   - use offset in warn_size() calculation  [Karel Zak]
lscpu:
   - document --hex output regression (since v2.30)  [Karel Zak]
mount:
   - Do not call mnt_pretty_path() on net file systems.  [Stanislav Brabec]
   - mount.8 clarify (no)suid behavior on file capabilities  [Peter Wu]
po:
   - merge changes  [Karel Zak]
   - update de.po (from translationproject.org)  [Mario Blättermann]
   - update fr.po (from translationproject.org)  [Frédéric Marchal]
   - update hr.po (from translationproject.org)  [Božidar Putanec]
readprofile:
   - check input file is not empty [asan]  [Sami Kerola]
setarch:
   - don't return address of automatic variable  [Andreas Schwab]
sfdisk:
   - fix logical partition resize when start specified  [Karel Zak]
su:
   - be sensitive to another SIGCHLD ssi_codes  [Karel Zak]
   - change error message  [Karel Zak]
tests:
   - add /mnt/test/foo^Mbar to mountinfo tests  [Karel Zak]
wall:
   - remove unnecessary warning  [Karel Zak]
whereis:
   - search in /(s)bin before /usr/lib  [Karel Zak]

                 reply	other threads:[~2019-04-09 14:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190409140358.b3hssvd5bgqmbdtb@ws.net.home \
    --to=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).