Re: Setup for built-using
On Wed, Nov 27, 2019 at 06:07:50PM +0100, Ansgar wrote:
> On Wed, 2019-11-27 at 13:03 +0000, Mark Hindley wrote:
> > I am in the middle of migrating an existing archive to a new dak installation.
> >
> > I have successfully imported the existing archive using import-archive (which
> > required a few patches which I am happy to share if you are interested). But am
> > stuck with debian-installer binary packages which have Built-Using sources that
> > are not in the archive.
>
> Do you mean "import-repository"? That is still somewhat unfinished and
> not really generally usable so far. It has issues.
Sorry, my typo. Yes import-repository. That would explain why I had to patch
it. But it has worked for my usage.
> > Alternatively, I could put the Built-Using sources into another suite or
> > archive. Which of those is better. How should I link that to the main archive?
>
> They just have to be somewhere in the archive. You can import them
> into a "built-using" suite in the target suite's archive; dak will also
> copy `Built-Using` sources from other archives (with some exceptions).
> (That is what happens on Debian's security archive; see the "Built-
> Using" section in docs/debian-specific.rst)
Yes, I saw that reference and wondered if anything else needed to be done.
> You can optionally remove the packages from the "built-using" suite
> again afterwards.
>
> The extra source packages will show up in any suite having binary
> packages referencing them; an "Extra-Source-Only: yes" field gets added
> if they are only there for that reason (and not part of the suite
> otherwise).
Many thanks. Very helpful.
Mark
Reply to: