control: tag -1 + fixed-upstream
On 2024-04-23 16:22, David Edmondson wrote:
> tag 1041415 - upstream
> thanks
>
> Ultimately this fails because /proc is not available in the chroot.
>
> The version of libc in use *emulates* fchmodat() using /proc/self/fd
> rather than using the fchmodat system
Processing control commands:
> tag -1 + fixed-upstream
Bug #1041415 [libc6] libc6: fchmodat emulation fails in the absence of /proc
Added tag(s) fixed-upstream.
--
1041415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
tag 1041415 - upstream
thanks
Ultimately this fails because /proc is not available in the chroot.
The version of libc in use *emulates* fchmodat() using /proc/self/fd
rather than using the fchmodat system call.
When /proc is provided in the chroot, the fchmodat emulation works
successfully and
tag 1041415 + upstream
thanks
The error message:
>>Error occurred processing /usr/share/emacs/site-lisp/debian-startup.el: File
>>error (("Doing chmod" "Operation not supported"
>>"/usr/share/emacs/site-lisp/debian-startup.elcFx8oFi"))
comes from the emacs byte compiler. Tracing through the
Ah, by specifically using a chroot rather than a systemd-nspawn
container, I *am* able to reproduce the failure.
Off to debug...
--
I'm not living in the real world, no more, no more.
I was not able to reproduce this failure.
Is there anything interesting about the filesystem underlying the chroot
used during the install?
Is root able to write files with impunity in the relevant directories?
Are you able to reproduce the failure?
--
Time is waiting to explain, why refuse?
6 matches
Mail list logo
