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

Re: Automatic building of (parts of) the archive



Op di, 08-03-2005 te 23:01 +0100, schreef Frank Küster:
> Hi,
> 
> I am still struggling with the setup of a local buildd for testing
> purposes.  I was able to manually build a package, using the command
> 
> buildd@bombadil:~$ sbuild -d unstable -v hello_2.1.1-4
> 
> However, after I put a package into build/REDO:
> 
> buildd@bombadil:~$ cat build/REDO 
> acl2_2.9.1-1 unstable
> 
> and start buildd, I get:
> 
> buildd@bombadil:~$ cat daemon.log 
> Mar  8 23:44:22 buildd: Daemon started. (pid=8002)
> Mar  8 23:44:31 buildd: Updated source-dependencies
> Mar  8 23:48:48 buildd: Updated apt sources for unstable
> Mar  8 23:48:49 buildd: Autocleaned apt cache directory for unstable
> Mar  8 23:48:49 buildd: Starting build (dist=unstable) of:
> Mar  8 23:48:49 buildd: acl2_2.9.1-1
> Bad distribution
> Mar  8 23:48:49 buildd: sbuild failed with status 2/0
> Mar  8 23:48:49 buildd: Assuming all packages unbuilt and adding to REDO:
> Mar  8 23:48:49 buildd: acl2_2.9.1-1
> Mar  8 23:48:49 buildd: Build finished.
> 
> This is repeated 3 times, then I get
> 
> Mar  8 23:49:06 buildd: sbuild now failed 3 times in a row; going to sleep
> Mar  8 23:49:06 buildd: sendmail failed (exit status 1/0)
> 
> (I guess I can find out the sendmail problem myself, didn't look at it
> yet).  Why does it say "bad distribution"?  I have chroots at 
> 
> $ ls -l ~buildd/chroot*
> lrwxrwxrwx  1 buildd buildd   12 Mar  8 22:57 /home/buildd/chroot-sid -> chroots/sid/
> lrwxrwxrwx  1 buildd buildd   12 Mar  8 23:03 /home/buildd/chroot-unstable -> chroots/sid/

These should be in ~buildd/build. Sbuild will find them if they're a
subdirectory of the current working directory, and buildd changes that
to that directory.

I'm not sure whether this is actually the cause of your problem, though.
If not, I'm sure I'll hear about it ;-)

> /home/buildd/chroots:
> total 4
> drwxr-xr-x  21 root root 4096 Mar  5 22:03 sid
> 
> The buildd is running as user buildd, not as root, but that is how it
> should be, isn't it?

Yes, but it needs passwordless sudo access.

-- 
         EARTH
     smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
         WATER
 -- with thanks to fortune



Reply to: