[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20170813-10-gddd508e
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official devtools repository".
The branch, master has been updated
via ddd508efc083fc9beb6f2c96e2537521b31c1e6f (commit)
via 0f3778c3d36028e5c9d4e5ec702c8f167e1cebba (commit)
from 6b55282bd702afd9a36409f85d9cb4c608ada5e5 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit ddd508efc083fc9beb6f2c96e2537521b31c1e6f
Author: Jan Alexander Steffens (heftig)
On Thu, 14 Sep 2017 17:34:11 -0400, Jan Steffens wrote:
makechrootpkg: Reopen console to assign the CTTY
nspawn does not give us a controlling terminal, hence we ignore interrupts. Apparently this was lost in systemd at some point.
Hack around this by reopening the console to make it the controlling terminal.
Does downgrading the chroot's glibc to 2.25 make this unnecessary? Or are we seeing different issues? (You'll also need to downgrade binutils, as current binutils depends on glib>=2.26 For convenience: https://archive.archlinux.org/repos/2017/09/08/core/os/x86_64/glibc-2.25-7-x... https://archive.archlinux.org/repos/2017/09/08/core/os/x86_64/binutils-2.28.... ) -- Happy hacking, ~ Luke Shumaker
On Sat, Sep 16, 2017 at 11:23 PM Luke Shumaker
On Thu, 14 Sep 2017 17:34:11 -0400, Jan Steffens wrote:
makechrootpkg: Reopen console to assign the CTTY
nspawn does not give us a controlling terminal, hence we ignore interrupts. Apparently this was lost in systemd at some point.
Hack around this by reopening the console to make it the controlling terminal.
Does downgrading the chroot's glibc to 2.25 make this unnecessary? Or are we seeing different issues?
No, this is indeed the same issue. I was mistaken when I thought this was introduced in nspawn.
On Sat, 16 Sep 2017 19:35:21 -0400, Jan Alexander Steffens wrote:
On Sat, Sep 16, 2017 at 11:23 PM Luke Shumaker
wrote: On Thu, 14 Sep 2017 17:34:11 -0400, Jan Steffens wrote:
makechrootpkg: Reopen console to assign the CTTY
nspawn does not give us a controlling terminal, hence we ignore interrupts. Apparently this was lost in systemd at some point.
Hack around this by reopening the console to make it the controlling terminal.
Does downgrading the chroot's glibc to 2.25 make this unnecessary? Or are we seeing different issues?
No, this is indeed the same issue. I was mistaken when I thought this was introduced in nspawn.
FYI, I've reported this upstream and submitted patches. Both the appropriate committer and I hope to see this fixed in glibc 2.27. https://sourceware.org/bugzilla/show_bug.cgi?id=22145 PATCH v1: https://sourceware.org/ml/libc-alpha/2017-10/msg00501.html PATCH v2: https://sourceware.org/ml/libc-alpha/2017-11/msg00060.html -- Happy hacking, ~ Luke Shumaker
participants (3)
-
heftig@archlinux.org
-
Jan Alexander Steffens
-
Luke Shumaker