Tagging this bug as block-proposed-noble,
in addition to the request in comment #1.
aardvark-dns 1.6.0-1 (this upload) depends on netavark >> 1.6 [1],
which cannot be satisfied on ppc64el as netavark 1.6.0-1, that is
in noble-proposed FTBFS (build log [2]; see bug 2063447 comment 2),
and noble-release has 1.4.0-4 (lower than the requirement).
Thus, the aardvark-dns packages in noble-proposed cannot be released
until the netavark packages in noble-proposed are adjusted to fix up
the ppc64el build, and must be released together (so to satisfy deps).
Tagging this bug as block-proposed- noble,
in addition to the request in comment #1.
aardvark-dns 1.6.0-1 (this upload) depends on netavark >> 1.6 [1],
which cannot be satisfied on ppc64el as netavark 1.6.0-1, that is
in noble-proposed FTBFS (build log [2]; see bug 2063447 comment 2),
and noble-release has 1.4.0-4 (lower than the requirement).
Thus, the aardvark-dns packages in noble-proposed cannot be released
until the netavark packages in noble-proposed are adjusted to fix up
the ppc64el build, and must be released together (so to satisfy deps).
aardvark- dns_1.6. 0-1ubuntu1_ ppc64el. deb
...
Depends: ..., netavark (>> 1.6)
$ rmadison -a source,ppc64el netavark | grep noble universe | source
netavark | 1.4.0-4 | noble/universe | source, ppc64el
netavark | 1.6.0-1ubuntu1 | noble-proposed/
[1] https:/ /launchpadlibra rian.net/ 726208568/ buildlog_ ubuntu- noble-ppc64el. aardvark- dns_1.6. 0-1ubuntu1_ BUILDING. txt.gz /launchpadlibra rian.net/ 726251181/ buildlog_ ubuntu- noble-ppc64el. netavark_ 1.6.0-1ubuntu1_ BUILDING. txt.gz
[2] https:/