On Fri, 2018-05-11 at 23:45 +0100, James Clarke wrote: > On 11 May 2018, at 23:29, Svante Signell <[email protected]> > wrote: > > On Fri, 2018-05-11 at 22:11 +0100, James Clarke wrote: > > > On 11 May 2018, at 21:58, Svante Signell > > > <[email protected]> wrote: > > > > Well, if I build packages and want them installed in the chroot > > .tar.gz used for building those packages, how to do that? And how > > to give back that package to be built the normal way? The clue for > > i386 is to build mpclib3 to make gcc-7 buildable: Can you tell be > > how to create an updated /srv/chroot/sid_kfreebsd-i386.tar.gz so > > that mpclib3 builds? > > As I've said multiple times now, you don't. Packages built by buildd > always use a clean copy of the tarball for their chroot; if you want > package A to use package B in its build, you have two options:
Even if a clean copy is used every time the base system cannot be downloaded. Which packages are part of the base system: the kernel of course, and? > 1. Upload (with a DD's signature) package B to the archive And I've asked you if you (or somebody else) can sign and upload packages I've built locally without any reply so far. > 2. Build package A manually locally in a modified schroot session I've done that several times. But what's the meaning of that when those packages cannot be uploaded?
