On December 23, 2018 12:51:41 PM EST, Johannes Schauer <jo...@debian.org> wrote: >Hi, > >On Tue, 04 Dec 2018 21:15:35 +0100 Johannes 'josch' Schauer ><jo...@debian.org> wrote: >> recently (2018-11-29), glibc 2.28 was accepted in unstable. It adds a >wrapper >> for the renameat2 syscall. That wrapper is necessary for fakechroot >because >> fakechroot cannot intercept system calls but uses a preloaded library >to >> intercept library calls. >> >> Up to coreutils 8.30, mv(1) uses the renameat2 syscall which makes >mv(1) >> fail under fakechroot. See #909612. >> >> Now that glibc 2.28 offers the renameat2 library function as a >wrapper >> to the syscall, coreutils added support for choosing the library >> function instead of the syscall if the former is available: >> >> >https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=c50cf67bd7ff70525f3cb4074f0d9cc1f5c6cf9c >> >> I don't know if another coreutils release is likely to happen before >the >> freeze but if it isn't please consider the attached patch which >> backports the commit from the gnulib git to coreutils 8.30. >> >> Without this patch, fakechroot is currently not very useful because >the >> mv(1) tool is unusable inside fakechroot. Most prominently, apt uses >> mv(1) inside its postinst script, so its impossible to install apt >inside >> fakechroot and thus one cannot setup a sensible system. > >what is the status of this bug? Without this patch, the functionality >of >fakechroot and mmdebstrap in the next stable release will be hampered. >If you >don't have time, I could also NMU coreutils with the attached patch. > >What do you think? > >Thanks! > >cheers, josch
Please just wait -- Michael Stone (From phone, please excuse typos)
