aboutsummaryrefslogtreecommitdiff
path: root/gnu/packages/patches/telegram-purple-adjust-test.patch
diff options
context:
space:
mode:
authorTobias Geerinckx-Rice <me@tobias.gr>2020-07-23 04:53:06 +0200
committerTobias Geerinckx-Rice <me@tobias.gr>2020-07-23 16:25:10 +0200
commit4f204533b7183adadfe5cbe7f8bcd7d11c430b44 (patch)
tree7b8bf85773c6cdd4e0ca531c3868683c6a076d48 /gnu/packages/patches/telegram-purple-adjust-test.patch
parent56d1ab2537465302b13aaaa3c07808c0b60395b5 (diff)
downloadguix-4f204533b7183adadfe5cbe7f8bcd7d11c430b44.tar.gz
guix-4f204533b7183adadfe5cbe7f8bcd7d11c430b44.zip
gnu: ansible: Update to 2.9.11.
* gnu/packages/admin.scm (ansible): Update to 2.9.11.
Diffstat (limited to 'gnu/packages/patches/telegram-purple-adjust-test.patch')
0 files changed, 0 insertions, 0 deletions
generated by cgit
7b27fb9499f8b42fa'>file-systems: Recognize “none” as a valid device spec.Nicolas Graves * gnu/build/file-systems (canonicalize-device-name): Fallback to tmpfs if spec is "none". Change-Id: Ia55c715d04c7611ba8c979f23f1ad4a8ed2e75b6 Signed-off-by: Ludovic Courtès <ludo@gnu.org> 2023-02-26file-systems: Validate 'no-diratime flag.Tobias Geerinckx-Rice This follows up on commit c0773455397746b10194bc14c7cef144f4095b65, and adds a comment to avoid this in future. * gnu/system/file-systems.scm (invalid-file-system-flags): Add 'no-diratime to the list of KNOWN-FLAGS. 2022-11-20file-systems: Always do recursive bind mounts.Ricardo Wurmus Fixes <https://issues.guix.gnu.org/59185>. * guix/build/syscalls.scm (MS_REC): New variable. * gnu/build/file-systems.scm (mount-flags->bit-mask): Set MS_REC bit when bind-mounting. 2022-11-03file-systems: Gracefully handle EMEDIUMTYPE in 'read-partitions'.Marius Bakke * gnu/build/file-systems.scm (ENOENT-safe): Catch EMEDIUMTYPE and warn. 2022-10-20file-systems: Support the 'no-diratime' mount flag.Ludovic Courtès * gnu/build/file-systems.scm (mount-flags->bit-mask): Handle 'no-diratime'. * doc/guix.texi (File Systems): Document it. 2022-09-08file-systems: Open files with O_CLOEXEC.Ludovic Courtès Since this code is run from PID 1, this ensures file descriptors to sensitive files and devices are not accidentally leaked to sub-processes. * gnu/build/file-systems.scm (call-with-input-file): New procedure. (mount-file-system): Use 'close-fdes' + 'open-fdes'. 2022-08-10gnu: system: file-systems: Add shared flag.Oleg Pykhalov * gnu/build/file-systems.scm (mount-flags->bit-mask, mount-file-system): Handle shared flag. * gnu/system/file-systems.scm (invalid-file-system-flags): Add shared to known flags. * guix/build/syscalls.scm (MS_SHARED): New variable. * doc/guix.texi (File Systems): Document shared flag. 2022-07-01file-systems: Add 'cleanly-unmounted-ext2?'.Ludovic Courtès * gnu/build/file-systems.scm (ext2-superblock-cleanly-unmounted?) (cleanly-unmounted-ext2?): New procedures. 2022-04-08file-systems: Invoke fsck tools with 'system*/tty'.Ludovic Courtès This ensures those programs, if invoked by shepherd (where standard input is /dev/null), can still interact with the user if needed. * gnu/build/file-systems.scm (check-ext2-file-system) (check-bcachefs-file-system, check-btrfs-file-system): (check-fat-file-system, check-jfs-file-system): (check-f2fs-file-system, check-ntfs-file-system): (check-xfs-file-system): Use 'system*/tty' instead of 'system*'. 2022-04-08mapped-devices: Ensure 'cryptsetup open' gets a tty.Ludovic Courtès Fixes <https://issues.guix.gnu.org/54770>. Regression introduced in 400c9ed3d779308e56038305d40cd93acb496180. Previously, for an encrypted /home (say), "cryptsetup open" would be invoked by shepherd, with /dev/null as its standard input. It would thus run in non-interactive mode and, instead of asking for a passphrase, fail with: Nothing to read on input. This change ensures it runs in interactive mode. * gnu/build/file-systems.scm (system*/console, system*/tty): New procedures. * gnu/system/mapped-devices.scm (open-luks-device): Use 'system*/tty' instead of 'system*'.