Bug#1004348: hurd: FTBFS on hurd-i386 locally
Svante Signell, le mer. 26 janv. 2022 10:31:23 +0100, a ecrit:
> On Tue, 2022-01-25 at 23:42 +0100, Samuel Thibault wrote:
> > Svante Signell, le mar. 25 janv. 2022 23:40:17 +0100, a ecrit:
> > > On Tue, 2022-01-25 at 22:16 +0100, Samuel Thibault wrote:
> > > > >
> > > > > Thanks!
> > > > > But on a third image I get:
> > > > > mkdir: cannot create directory ‘/home’: File exists
> > > > >
> > > > > Something is fishy...
> > > >
> > > > As I already wrote, first make sure exactly *what* is producing
> > > > this
> > > > call. That way you'll see where the fish comes from.
> > >
> > > I'd really appreciate to know the difference of an old image upgraded
> > > to current and a new one??
> >
> > No idea. As I've already written, I'm just using the
> > debian-hurd-20210812.img image, upgraded to current archive.
>
> I did add set -x to mkinstalldirs:
>
> make[3]: Entering directory '/home/.../hurd-0.9.git20211230/build-
> deb/libshouldbeinlibc'
> + errstatus=0
> + echo :/home/.../hurd-0.9.git20211230/debian/tmp/lib/i386-gnu
> + sed -ne s/^:\//#/;s/^://;s/\// /g;s/^#/\//;p
> + set fnord /home srs DEBs hurd hurd-0.9.git20211230 debian tmp lib i386-gnu
Ah ok, that's what /home comes from, mkinstalldirs already splits the
path into separate components.
> + shift
> + pathcomp=
> + pathcomp=/home
> + test ! -d /home
> + echo mkdir /home
> mkdir /home
> + mkdir /home
> mkdir: cannot create directory ‘/home’: File exists
So here the problem is that
test ! -d /home
says that /home is not a directory. Is there anything special about your
/home path? Perhaps show the output of
stat /home
Samuel
Reply to: