On Thu, 2016-06-02 at 01:13 +0200, Samuel Thibault wrote: > On Hurd, getting $PWD from the 700 directory fails, and find thus aborts > immediately, without emitting any output, and thus no keyring is found. > > So, to summarize, the issue is that since apt-get update runs find as a > non-root user, running it from a 700 directory breaks find. > > I guess it may make sense for apt to chdir to e.g. / before running the > find command, so that we are sure that find doesn't get any issue? > > Actually it's pure luck that the script doesn't completely fail on Linux > when find fails due to not being able to restore the cwd: since the find > command is only used as parameter of a for loop, the returned value > is ignored by sh. Had the find command output been first stored in a > variable, the script would have aborted... Thank you for the root cause. I am hitting the same problem on my Hurd box. From what you've explained, this bug should be reassigned to APT then ? -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response
Attachment:
signature.asc
Description: This is a digitally signed message part