[Pkg-owncloud-maintainers] Building ocsync

Diederik de Haas didi.debian at cknow.org
Thu Mar 14 16:35:10 UTC 2013


On Thursday 14 March 2013 11:52:57 Sandro Knauß wrote:
> The clean way (needs  git-buildpackage, creates an virtual environment
> needs  more space on harddisk; but creates a clean package, because only
> what is mentioned in control file will be installed in the virtual env):
> 
> Then you have to rune (once):
> git-pbuilder create

When it just starts I see the line:
forking: pbuilder create --buildplace /var/cache/pbuilder/base.cow --mirror 
http://ftp.debian.org/debian/ --distribution sid --no-targz --extrapackages 
cowdancer

Can I configure the parameters for that and where?
Can I also configure APT in the target environment?
I want pbuilder and the target environment to use my apt-cacher-ng proxy, so it 
won't have to download (all) the pkgs from a debian mirror again.

After mounting /proc, /run/shm and /dev/pts it wants to download/install some 
more files at which point it failed with the following error:
W: GPG error: http://ftp.debian.org sid Release: The following signatures were 
invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key 
(6.0/squeeze) <ftpmaster at debian.org>

I think this is just a temporary glitch, so it should be solvable by running it 
again. Although it failed the 2nd time as well (same error).
Is this a glitch or is this caused by bug 702102? One of the pkgs it wants to 
install (but doesn't because it cannot be authenticated) is cowdancer. Based on 
it's name it has some relation to cowbuilder, but my error is quite different 
from the one reported.

Cheers,
  Diederik



More information about the Pkg-owncloud-maintainers mailing list