commit 54cba9a31bda49a0b98048d9598cc6f70bd1ee1f
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Wed Mar 31 19:16:04 2021 +0000
Remove relations that are fulfilled in at least buster
commit 9ee3197ab8d0fa23b9bb80732126eab9b1f83db5
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Wed Mar 31 19:10:26 2021 +0000
debian/control: wrap-and-sort -a
commit 03e79590157c8997e1167993a008813b0f5b7d75
Merge: cca555fb8 683b60d60
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Wed Mar 31 19:07:35 2021 +0000
Merge branch '983557-noudeb-profile' into 'master'
Allow to build without udeb packages
See merge request debian/util-linux!19
commit cca555fb8182a6a45fb6ce0a8f998902fcf20511
Merge: 0739271f0 9ce212399
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Wed Mar 31 19:07:11 2021 +0000
Merge branch '982557-bsdextrautils-not-pre-depends' into 'master'
bsdextrautils: Make shlibs:Depends regular Depends
See merge request debian/util-linux!18
commit 0739271f008241ad61be60df7d2683623fc64de2
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Wed Mar 31 19:05:16 2021 +0000
Refresh/remove patches
commit 293d1e3f91d34ae2278b0b4feb0655ae70a0f22b
Merge: 1bde4115c 4cc305d49
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Wed Mar 31 19:02:05 2021 +0000
Update upstream source from tag 'upstream/2.36.2'
Update to upstream version '2.36.2'
with Debian dir d65f595097221842223261bc2496c84e693698e9
commit 4cc305d49e05015adf9a0d1e73908edc37c41603
Merge: 88328bee2 b897734b5
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Wed Mar 31 19:01:31 2021 +0000
New upstream version 2.36.2
commit 683b60d60ab61f550f3ab3f8e8ab8aac972261d7
Author: Matthias Klose <doko@ubuntu.com>
Date: Wed Mar 31 19:35:24 2021 +0200
Allow to build without udeb packages
Tag all *-udeb packages with the !noudeb build-profile to
allow building without the udebs.
Closes: #983557
commit 9ce2123991ec104cb3cac1163a76bdc929fc7646
Author: Andreas Henriksson <andreas@fatal.se>
Date: Wed Mar 31 19:14:35 2021 +0200
bsdextrautils: Make shlibs:Depends regular Depends
As described in the bug report, bsdextrautils is a normal
package (not Essential: yes), so doesn't need to Pre-Depend
on libraries. Thanks to Sven Joachim for a keen eye to catch
this detail.
Closes: #982557
commit 1bde4115c6e8635e2ae0e08f28632a003755af3f
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Sun Feb 14 17:36:57 2021 +0000
Add upstream patches for better support of current Linux kernels
lib/loopdev: make is_loopdev() more robust
Current kernels can assign loop devices with major numbers others than
7. Makes losetup work with those.
libmount: add vboxsf, virtiofs to pseudo filesystems
For virtualisation scenarios on current kernels.
Gbp-Dch: full
commit 88328bee2482be9b7fa9093e1d9bb873c6a87728
Merge: 6e446ab36 b897734b5
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Sun Feb 14 17:25:47 2021 +0000
New upstream version 2.36.2
commit b897734b57ea06643fa916f15270f21ea2f14431
Author: Karel Zak <kzak@redhat.com>
Date: Fri Feb 12 14:59:56 2021 +0100
build-sys: release++ (v2.36.2)
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 333ae3bc84f531f995b52b98de87c44b2a91bf91
Author: Karel Zak <kzak@redhat.com>
Date: Fri Feb 12 14:58:42 2021 +0100
docs: update v2.36.2-ReleaseNotes
Signed-off-by: Karel Zak <kzak@redhat.com>
commit f34d1ebd683574bec50925532c61bf298f04fc22
Author: Karel Zak <kzak@redhat.com>
Date: Fri Feb 12 14:57:07 2021 +0100
docs: update AUTHORS file
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 282e23b206461caadc8121b926c0bc10f02f3eed
Author: Karel Zak <kzak@redhat.com>
Date: Fri Feb 12 14:55:57 2021 +0100
po: merge changes
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 88575de7919623d44a429888ab42d0e5e38094c7
Author: Мирослав Николић <miroslavnikolic@rocketmail.com>
Date: Fri Feb 12 14:47:25 2021 +0100
po: add sr.po (from translationproject.org)
commit a9770efee625820f1249211fc5ce18c076165e15
Author: Sebastian Rasmussen <sebras@gmail.com>
Date: Fri Feb 12 14:47:25 2021 +0100
po: update sv.po (from translationproject.org)
commit 5a6e531d6bda60af408f39777a9793d63d38fc12
Author: Božidar Putanec <bozidarp@yahoo.com>
Date: Fri Feb 12 14:47:25 2021 +0100
po: update hr.po (from translationproject.org)
commit 5c910da40d4dbf54a6ce6d70846fc7b1f4e60b91
Author: Karel Zak <kzak@redhat.com>
Date: Tue Feb 9 18:02:13 2021 +0100
tests: be explicit with file permissions for cramfs
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 06aafc1ea2615f9458747be069be32b96e25edaf
Author: Karel Zak <kzak@redhat.com>
Date: Thu Feb 11 12:44:44 2021 +0100
tests: don't rely on scsi_debug partitions
The disk layout as created by scsi_debug depends on kernel version.
Let's make the partition sizes hardcoded in our tests than rely on
kernel.
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 8367b07f08460b9f449c535cc540429c438980bf
Author: Karel Zak <kzak@redhat.com>
Date: Thu Feb 11 11:49:56 2021 +0100
libfdisk: (dos) fix last possible sector calculation
* rename 'last' to 'first' as we use this value as the first available free
sector rather than last used
* use '-1' when calculate last partition sector to compare with last
disk sector
* improve debug messages
Fixes: https://github.com/karelzak/util-linux/issues/1249
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 7a241ef6c7f3791e2cffd1fc26479bef334e9f4d
Author: Sami Loone <sami@loone.fi>
Date: Tue Feb 9 10:46:36 2021 +0100
agetty: tty eol defaults to REPRINT
Adapting tty eol settings from defaults misbehaves as CTRL('r') aka
REPRINT is confused with CR. Consequently --skip-login does not set
tty CR<->NL translations and thus acts against advertised CR as eol
default.
[kzak@redhat.com:
It seems this issue has been introduced by commit f566447 where we
merged sulogin and agetty terminal initialization together to the file
include/ttyutils.h.
The original agetty has really used .eol=13 (aka CR) for the default.
The problem is invisible for sulogin(1) because it always asks for a
password and .eol= is set to NL/CR, the same agetty when it asks for
username.]
Addresses: https://github.com/karelzak/util-linux/pull/1247
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 1656645e82824495b7ae814f0e961d0608f11d97
Author: Sami Kerola <kerolasa@iki.fi>
Date: Fri Oct 23 20:39:24 2020 +0100
rfkill: stop execution when rfkill device cannot be opened
Without this two error messages are printed when rfkill device
cannot be opened.
$ rfkill
rfkill: cannot open /dev/rfkill: No such file or directory
rfkill: cannot read /dev/rfkill: Bad file descriptor
Signed-off-by: Sami Kerola <kerolasa@iki.fi>
commit 65d9baa10feaaa7752601c5846bdc2de70fe8a83
Author: Thomas Deutschmann <whissi@gentoo.org>
Date: Mon Feb 8 15:30:25 2021 +0100
switch_root: check if mount point to move even exists
Signed-off-by: Thomas Deutschmann <whissi@gentoo.org>
commit fd5ed9a4f5bc371794138528c56ae8053863741c
Author: Karel Zak <kzak@redhat.com>
Date: Wed Feb 10 10:47:27 2021 +0100
libmount: (py) do not use pointer as an integer value
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 91d8a3f960bf19547630ef2a5b307244f84b21ce
Author: Karel Zak <kzak@redhat.com>
Date: Mon Dec 14 15:56:55 2020 +0100
blkdiscard: fix compiler warnings [-Wmaybe-uninitialized]
sys-utils/blkdiscard.c: In function 'main':
sys-utils/blkdiscard.c:304:33: warning: 'now.tv_usec' may be used uninitialized in this function [-Wmaybe-uninitialized]
sys-utils/blkdiscard.c:152:17: note: 'now.tv_usec' was declared here
sys-utils/blkdiscard.c:305:37: warning: 'now.tv_sec' may be used uninitialized in this function [-Wmaybe-uninitialized]
sys-utils/blkdiscard.c:152:17: note: 'now.tv_sec' was declared here
sys-utils/blkdiscard.c:304:33: warning: 'last.tv_usec' may be used uninitialized in this function [-Wmaybe-uninitialized]
sys-utils/blkdiscard.c:152:22: note: 'last.tv_usec' was declared here
sys-utils/blkdiscard.c:305:65: warning: 'last.tv_sec' may be used uninitialized in this function [-Wmaybe-uninitialized]
sys-utils/blkdiscard.c:152:22: note: 'last.tv_sec' was declared here
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 546761ecf6f56125ccb8cbefa7d32126d95c8151
Author: Karel Zak <kzak@redhat.com>
Date: Mon Dec 14 15:56:55 2020 +0100
hwclock: fix compiler warnings [-Wmaybe-uninitialized]
sys-utils/hwclock-rtc.c: In function 'synchronize_to_clock_tick_rtc':
sys-utils/hwclock.c:169:28: warning: 'now.tv_usec' may be used uninitialized in this function [-Wmaybe-uninitialized]
sys-utils/hwclock-rtc.c:215:24: note: 'now.tv_usec' was declared here
sys-utils/hwclock.c:168:28: warning: 'now.tv_sec' may be used uninitialized in this function [-Wmaybe-uninitialized]
sys-utils/hwclock-rtc.c:215:24: note: 'now.tv_sec' was declared here
sys-utils/hwclock.c:169:28: warning: 'begin.tv_usec' may be used uninitialized in this function [-Wmaybe-uninitialized]
sys-utils/hwclock-rtc.c:215:17: note: 'begin.tv_usec' was declared here
sys-utils/hwclock.c:168:28: warning: 'begin.tv_sec' may be used uninitialized in this function [-Wmaybe-uninitialized]
sys-utils/hwclock-rtc.c:215:17: note: 'begin.tv_sec' was declared here
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 2c268ffe038d955de60ca1fdd6fc0fd4b18b1749
Author: Karel Zak <kzak@redhat.com>
Date: Mon Dec 14 15:56:55 2020 +0100
scriptlive: fix compiler warnings [-Wmaybe-uninitialized]
term-utils/scriptlive.c: In function 'process_next_step':
term-utils/scriptlive.c:125:4: warning: 'now.tv_usec' may be used uninitialized in this function [-Wmaybe-uninitialized]
term-utils/scriptlive.c:122:19: note: 'now.tv_usec' was declared here
term-utils/scriptlive.c:125:4: warning: 'now.tv_sec' may be used uninitialized in this function [-Wmaybe-uninitialized]
term-utils/scriptlive.c:122:19: note: 'now.tv_sec' was declared here
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 9a768132e5ef7f15c317b55985b650df3eb7226e
Author: Karel Zak <kzak@redhat.com>
Date: Mon Dec 14 15:56:55 2020 +0100
script: fix compiler warnings [-Wmaybe-uninitialized]
term-utils/script.c: In function 'log_close.part.0.isra':
term-utils/script.c:306:3: warning: 'now.tv_usec' may be used uninitialized in this function [-Wmaybe-uninitialized]
term-utils/script.c:303:18: note: 'now.tv_usec' was declared here
term-utils/script.c:306:3: warning: 'now.tv_sec' may be used uninitialized in this function [-Wmaybe-uninitialized]
term-utils/script.c:303:18: note: 'now.tv_sec' was declared here
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 4bd4dde7242c3bf160cefea2d89f6110f4fa34bf
Author: Karel Zak <kzak@redhat.com>
Date: Wed Feb 10 10:31:23 2021 +0100
github: remove cifuzz from stable branch
It requires many changes from the master branch to make fuzzer usable.
For now it's overkill to backport it to the stable/2.36
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 0defafdd00a18f23ad4bb136e6e3d0c2d07979e5
Author: Karel Zak <kzak@redhat.com>
Date: Tue Feb 9 10:36:04 2021 +0100
libmount: fix /{etc,proc}/filesystems use
* always update context->helper
* consolidate helper and syscall status use
Signed-off-by: Karel Zak <kzak@redhat.com>
commit f40291fff8fe35ea3b8632e6a24ca17d760e1187
Author: Karel Zak <kzak@redhat.com>
Date: Wed Feb 3 14:45:15 2021 +0100
login: use full tty path for PAM_TTY
pam_set_item() man page:
PAM_TTY
The terminal name: prefixed by /dev/ if it is a device file;
for graphical, X-based, applications the value for this item
should be the $DISPLAY variable.
It seems for example pam_timestamp module is not robust enough to
differentiate between /dev/ and pty/0 and it assumes that '/' in the
path always means '/dev/' prefix ...
Fixes: https://github.com/karelzak/util-linux/issues/1242
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 9a48cbd0044cf3ef196cacb7a59592a78391f896
Author: Karel Zak <kzak@redhat.com>
Date: Wed Feb 3 14:45:15 2021 +0100
su: use full tty path for PAM_TTY
pam_set_item() man page:
PAM_TTY
The terminal name: prefixed by /dev/ if it is a device file;
for graphical, X-based, applications the value for this item
should be the $DISPLAY variable.
It seems for example pam_timestamp module is not robust enough to
differentiate between /dev/ and pty/0 and it assumes that '/' in the
path always means '/dev/' prefix ...
Fixes: https://github.com/karelzak/util-linux/issues/1242
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 25b8d1a25c0072d115bfc4e42ec6620bab6dad91
Author: ToddRK <ToddRK@example.com>
Date: Thu Jan 28 12:44:41 2021 +0100
fsck.cramfs: fix fsck.cramfs crashes on blocksizes > 4K
fsck.cramfs crashes when extracting a cramfs image with a 16KB blocksize.
The read_buffer is hardcoded for a 4KB blocksize. When using a blocksize
larger than 4KB, the program's code uses indexes that go past the end of the
allocated space for the read_buffer and this causes the crash.
The following changes fix the problem for me in the latest 2.36.1 release of
fsck.cramfs.c. However there are hardcoded values of 4096 in the code that
might cause problems under other circumstances and I have not attempted to
fix those.
[kzak@redhat.com: - some coding style changes to code]
Fixes: https://github.com/karelzak/util-linux/issues/1232
Signed-off-by: ToddRK <ToddRK@example.com>
Signed-off-by: Karel Zak <kzak@redhat.com>
commit c6ec9f8f514c93a64a2340164b1dc323616ee832
Author: Shahid Laher <govellius@gmail.com>
Date: Wed Jan 20 18:04:33 2021 +0000
libmount: add vboxsf, virtiofs to pseudo filesystems
Filesystems provided by a hypervisor for guest kernels:
* vboxsf: Linux 5.6
* virtiofs: Linux 5.4
Signed-off-by: Shahid Laher <govellius@gmail.com>
commit 686efaa4a5c9b714b03a001188d64beafab0fed5
Author: Karel Zak <kzak@redhat.com>
Date: Thu Jan 14 12:45:28 2021 +0100
libmount: do not canonicalize ZFS source dataset
Fixes: https://github.com/karelzak/util-linux/issues/1231
Addresses: https://github.com/systemd/systemd/issues/18188
Addresses: https://github.com/openzfs/zfs/pull/11295
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 547130444d893c284ab91d757b98b9435c5f3d01
Author: Karel Zak <kzak@redhat.com>
Date: Tue Jan 12 11:43:31 2021 +0100
lib/loopdev: make is_loopdev() more robust
It seems the current kernel can create a loop devices with a different
major number. For example
# losetup /dev/loop12345678 file.img
# lsblk /dev/loop12345678
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop12345678 15:811342 0 5M 0 loop
We need a way how to verify the device is loopdev also when the device is
not associated with any backing file -- in this case there is no "loop"
directory in /sys/dev/block/<maj:min>/, but we can cannonicalize this sysfs
symlink as it points to /sys/devices/virtual/block/loop<n> (see "loop" in
the path).
Note that without this change losetup is not able to list and delete
the loop device.
Addresses: https://github.com/karelzak/util-linux/issues/1202
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 5affd1f92d2dd9150f7f5210d819db61965adae3
Author: Karel Zak <kzak@redhat.com>
Date: Mon Jan 11 11:58:16 2021 +0100
libblkid: make gfs2 prober more extendible
The current GFS2 prober hard codes superblock constants, but these
constants are affected by GFS2 development.
Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=1913844
Signed-off-by: Karel Zak <kzak@redhat.com>
commit b471873c34f69a6247652aba6d2d7a232d7db3b8
Author: Gaël PORTAY <gael.portay@collabora.com>
Date: Sat Jan 9 05:03:34 2021 -0500
libfdisk: (script) ignore empty values for start and size
Signed-off-by: Gaël PORTAY <gael.portay@collabora.com>
commit a5cc6323c17f09b1e9f7888d77b57e6b7cadefb1
Author: Eric Biggers <ebiggers@google.com>
Date: Wed Dec 30 20:05:57 2020 -0800
sys-utils: mount.8: fix a typo
It should be "inode", not "i-node".
Signed-off-by: Eric Biggers <ebiggers@google.com>
commit 20f7fd6c26c2f4cdcc9fee24de89929be59cf342
Author: Heinrich Schuchardt <xypron.glpk@gmx.de>
Date: Thu Dec 31 01:32:54 2020 +0100
fstab.5: NTFS and FAT volume IDs use upper case
The man-page indicates that mount expects UUIDs to be lower case.
Mention that NTFS and FAT volume IDs are to be specified in upper case.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
commit 607c7402f8bd7788462ece8263b219bbf15e4892
Author: Vincent McIntyre <vincent.mcintyre@csiro.au>
Date: Sat Jan 2 11:02:35 2021 +1100
Show the 'r' option in the help menu
commit ec3a4a3960f05a53910d1cb956210c3fba3f3d36
Author: Ryan Finnie <ryan@finnie.org>
Date: Sun Dec 27 10:01:26 2020 -0800
libfdisk: ignore 33553920 byte optimal I/O size
A 33553920 byte optimal I/O size arises from badly-implemented USB SATA
adapters reporting 0xffff 512 byte sectors (32 MiB - 512). Commit
acb7651f8897ae73d0f45dd75bc87630001c61b9 indirectly addresses this by
ignoring the optimal I/O size if it's not a multiple of the physical
sector size. That works if the physical sector size is 4096, but
33553920 optimal is allowed for 512 physical.
This commit explicitly ignores 33553920, as there is no legitimate
situation where this number would be the real optimal I/O size.
Signed-off-by: Ryan Finnie <ryan@finnie.org>
Closes: https://github.com/karelzak/util-linux/issues/1221
commit 3cc000096b4559ded4f550dcc3eaf68337346e3c
Author: Anatoly Pugachev <matorola@gmail.com>
Date: Sat Dec 19 21:36:00 2020 +0300
tests: add checksum for cramfs/mkfs for LE:16384 (ia64)
Signed-off-by: Anatoly Pugachev <matorola@gmail.com>
commit 58492a2a73ffb3e14767ce75298792530e11691b
Author: Issam E. Maghni <issam.e.maghni@mailbox.org>
Date: Wed Dec 16 19:16:11 2020 -0500
configure: test -a|o is not POSIX
commit a9f098231167ddf52797b8b210b6cb96878827f2
Author: Karel Zak <kzak@redhat.com>
Date: Mon Dec 14 11:38:04 2020 +0100
lsblk: read SCSI_IDENT_SERIAL also from udev
Addresses: https://github.com/karelzak/util-linux/issues/1143
Signed-off-by: Karel Zak <kzak@redhat.com>
commit b826a90744ba1fa2d5fe6eec690c355483d6d447
Author: Manuel Bentele <development@manuel-bentele.de>
Date: Sat Dec 5 23:51:27 2020 +0100
losetup: fix wrong printf() format specifier for ino_t data type
Since the range of the ino_t data type is platform-specific (depending on
the wordsize), a usage of the fixed format specifier %PRIu64 is not correct
for ino_t on some 32-bit architectures, eg. ARM (Raspberry Pi 1). This issue
may lead to undefinied output and is not reported by gcc (in version 10.2.0
and 8.3.0-6+rpi1) even though -Wformat is enabled by -Wall. Therefore it is
most likely that it seems to be a false negative error in gcc's format
specifier check, so that this issue was never detected before.
This change fixes the issue by the use of a cast, since there is no
platform-independent format specifier for ino_t available. The wrong format
specifier %PRIu64 is replaced by %ju, where its corresponding variable of
type ino_t is casted to uintmax_t. The type uintmax_t represents the largest
platform-specific unsigned integer, so that all integer values are preserved
for a platform-independent printing.
Fixes: https://github.com/karelzak/util-linux/issues/1211
Signed-off-by: Manuel Bentele <development@manuel-bentele.de>
commit a47273628479324ad38d3e3e3ee9ad1f118b3869
Author: Karel Zak <kzak@redhat.com>
Date: Wed Nov 25 14:02:11 2020 +0100
lslogins: call close() for usable FD [coverity scan]
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 0e2da9740fa09ca752d9646c4aea096dfc06a6b1
Author: Pali Rohár <pali.rohar@gmail.com>
Date: Sun Nov 22 19:44:09 2020 +0100
libblkid: drbdmanage: use blkid_probe_strncpy_uuid instead of blkid_probe_set_id_label
Function blkid_probe_strncpy_uuid() is better suitable for setting UUID
than function blkid_probe_set_id_label().
Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
commit bef24ecfb990ea8ace96be0a296ec2dd32e85270
Author: Érico Rolim <erico.erc@gmail.com>
Date: Fri Nov 20 12:33:23 2020 -0300
setpriv: small clean-up.
- Add _() calls for some strings which were missing it.
- In print_caps(), use the same error checking done in
list_known_caps(); it is expected that libcap-ng will always return a
string, even if it's only "cap_%d".
commit b24fa471728bf671017588e28da63989e3eccc75
Author: Karel Zak <kzak@redhat.com>
Date: Thu Nov 19 12:04:08 2020 +0100
lib/signames: change license to public domain
The file is simple list of signal names and trivial function to search
in the list. We do not need any extra license here and as public
domain it will be more portable to other tools (GPL and BSD) in the
util-linux.
All previous contributors (Sami, Niklas and me) agree with this change.
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 0bfa747f0176af4b94a4e1f6f434ddfcd9ce5099
Author: Karel Zak <kzak@redhat.com>
Date: Thu Nov 19 11:12:06 2020 +0100
umount: ignore --no-canonicalize,-c for non-root users
It seems better to ignore this option than drop-permissions and later
exit with EPERMs. This change makes umount(8) more compatible with
fuser user umounts by systemd where -c is used to reduce overhead etc.
Addresses: https://github.com/karelzak/util-linux/issues/1192
Signed-off-by: Karel Zak <kzak@redhat.com>
commit 262ff9bf04e862dcfca8f3d0cb2c6bd2edaff327
Author: Pino Toscano <toscano.pino@tiscali.it>
Date: Tue Nov 17 11:32:45 2020 +0100
hwclock: do not assume __NR_settimeofday_time32
Check that __NR_settimeofday_time32 exists before trying to use it as
syscall number.
Signed-off-by: Pino Toscano <toscano.pino@tiscali.it>
commit 5e0dc74924354c5251e138cd8d69345aa3ab08ca
Author: Pino Toscano <toscano.pino@tiscali.it>
Date: Tue Nov 17 11:27:48 2020 +0100
build-sys: do not build plymouth-ctrl.c w/ disabled plymouth
Do not build plymouth-ctrl.c in agetty and sulogin in case the plymouth
support is disabled.
Signed-off-by: Pino Toscano <toscano.pino@tiscali.it>
commit 8bf68f78d8a3c470e5a326989aa3e78385e1e79b
Author: Érico Rolim <erico.erc@gmail.com>
Date: Wed Nov 18 11:35:26 2020 -0300
setpriv: allow using [-+]all for capabilities.
The initial change to lib/caputils that allowed this was commit
5d95818757941bc609e5aeec5e2218f7d35a6e19, which made it possible to
trust the value returned by cap_last_cap().
The error message was also somewhat misleading, since cap_last_cap()
being smaller than CAP_LAST_CAP happens when setpriv itself is built
with kernel headers older than the currently running kernel, not due to
libcap-ng.
(cherry picked from commit 93de9f687d1640fff963f26b7db474eef3746532)
commit db59b66c70fcf290196eeada26025567c9087f66
Author: Karel Zak <kzak@redhat.com>
Date: Fri Nov 20 10:38:01 2020 +0100
lib/procutils: improve proc_is_procfs(), add test
* add delay between attempts
* zeroize errno and check for EAGAIN (like in other code)
* add small test program
./test_procutils --is-procfs [<dir>]
Signed-off-by: Karel Zak <kzak@redhat.com>
(cherry picked from commit 1b54a74e8622d18b3be53ca440928d96e73bac3d)
commit 15966a2cc4cb02bded8b54cfff97987f9b29484c
Author: Érico Rolim <erico.erc@gmail.com>
Date: Sun Nov 15 01:34:41 2020 -0300
lib/caputils: add fall back for last cap using prctl.
This allows the rest of the programs using cap_last_cap to trust the
value returned by it, since it will either be obtained from procfs
(straight from kernel) or with prctl.
Also checked if the file under /proc is actually mounted in a procfs.
(cherry picked from commit 5d95818757941bc609e5aeec5e2218f7d35a6e19)
commit 9f704636d0ff547c809c0fe9cf301507359fbe44
Author: Érico Rolim <erico.erc@gmail.com>
Date: Wed Nov 18 14:07:10 2020 -0300
lib/procutils: add proc_is_procfs helper.
Also add missing include in procutils.h for the definition of pid_t.
(cherry picked from commit e411b8a63d4a44ac191b5ca032c4639b12d4b838)
commit 76bb9b30cfcf54b59591a57a3d2a747e514469b2
Author: Karel Zak <kzak@redhat.com>
Date: Thu Nov 19 09:49:16 2020 +0100
libmount: don't use "symfollow" for helpers on user mounts
Addresses: https://github.com/karelzak/util-linux/issues/1193
Signed-off-by: Karel Zak <kzak@redhat.com>
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/u/util-linux.png){kind=link}