[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: autobuilder...



On Tue, Aug 27, 2002 at 12:25:20PM +0200, Robert Jordens wrote:
> Hello!
> 
> On Die, 27 Aug 2002, Marcus Brinkmann produced 3,1K chars torturing the keyboard:
> 
> > Do you use fakeroot?  It's broken.
> 
> Intentionally broken or just short-term? Is it going to be fixed or
> should I use sudo?

It's just broken.  It never worked.  Nobody is working on it right now, so
we don't know when it is fixed, or how much effort it is.

Use sudo ;)

 
> > > 4. building dpkg:
> > >    buildd@hurd:~/chroot-unstable/build/buildd/dpkg-1.10.4$ fakeroot debian/rules binary
> > >    test -f include/dpkg.h.in
> > >    install -d /chroots/unstable/build/buildd/dpkg-1.10.4/build
> > 
> > s/chroot-unstable/chroots/ ?
> 
> No. I didn't edit that!
> 
> buildd@grafz-hurd:~$ ls -ld chroot-unstable
> lrwxr-xr-x    1 buildd   sbuild         26 Aug 27 10:57 chroot-unstable -> /usr/local/chroot/unstable
> buildd@grafz-hurd:~$ ls -ld /usr/local/chroot  
> lrwxr-xr-x    1 root     staff          17 Aug 26 18:51 /usr/local/chroot -> /mnt/work/chroots
> buildd@grafz-hurd:~$ 
> 
> Those symlinks are to satisfy wanna-build/sbuild/buildd....

I see.  This is important information, I guess.  You could try to find a
small test case (couple of shell commands) that shows the failure without
any prerequisites like buildd etc.
 
> > >    it simply kicks away the first two components of the path! The real
> > >    path should have been
> > >    /mnt/work/chroots/unstable/build/buildd/dpkg-1.10.4
> 
> > Dunno about the hang.  Maybe fakeroot bugs, too.
> 
> Are there docs about the flags (other than the source ;-)?

Not that I am aware of :)
 
> > >    shell-init: could not get current directory: getcwd: cannot access parent directories: Gratuitous error
> > 
> > Is this fakeroot, too?
> 
> No. Only chroot is involved:
> 
>               instdir defaults to  /  and
>               refers  to  the  directory where packages are to be
>               installed.  instdir is also the directory passed to
>               chroot(2)  before  running  package's  installation
>               scripts, which means that the scripts  see  instdir
>               as a root directory.  Changing root changes instdir
>               to dir and admindir to dir/var/lib/dpkg.

Ok, then we can take a closer look at it.
 
Thanks,
Marcus

-- 
`Rhubarb is no Egyptian god.' GNU      http://www.gnu.org    marcus@gnu.org
Marcus Brinkmann              The Hurd http://www.gnu.org/software/hurd/
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de/



Reply to: