Re: Setup for built-using
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.
> How should I handle this?
Import the relevant source packages.
> Is this something that could/should be overridden? If
> so how?
No; dak is very agressive in enforcing that all sources are present.
Maybe more than people sometimes want.
In particular it should not rely on references to external archives
which might no longer provide source or binary packages that your
distribution's overlay still references.
> 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)
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).
Ansgar
Reply to: