Mattia Rizzolo dixit: >Incidentally, I believe this is also related to: >#897662 [n| | ] [jenkins.debian.org] reproducible: is localhost unresolvable >in the build chroot? >And to that other bug I can't find right now about ensuring a resolvable >localhost in base chroots (probably in policy?)
Perhaps, yes. (Maybe resolv.conf needs a line “lookup file”, although I’ve only ever seen this used on BSD systems… or something with nsswitch.conf?) >> This patch also adds rm statements to make sure hardlinks on the >> replaced files are broken up. > >Wow, this is clever… Standard technique. With cowbuilder, hardlinks are normally broken, but only via an LD_PRELOADed library… unset that, or have your shell be statically linked, and it fails (I’ve had an in-chroot append to sources.list be persisted in the base.cow directory once, so I look for them now). >But are we sure there are no side-effects? i.e. there are no packages >that rely on for example a install-time hardlink to /etc/resolv.conf… >although I'd probably call that a bug. Nope, no such thing exists for any configuration or user file, as far as I know, not just for resolv.conf; the latter is “special” anyway as e.g. the resolvconf package replaces it with a symlink leading to tmpfs. So, yes, I’m sure ;) bye, //mirabilos -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
