Hi Brian, On Mon, Dec 19, 2022 at 08:25:52AM +1100, Brian May wrote: > Helmut Grohne <hel...@subdivi.de> writes: > > >> When I tried to build this with my build system I get: > >> > >> $ apt-get-build-depends --yes > >> Reading package lists... Done > >> Building dependency tree... Done > >> Reading state information... Done > >> E: Unable to locate package heimdal-multidev-bin > >> E: Unable to locate package <cross> > >> > >> Is "heimdal-multidev-bin <cross>," correct syntax? If so, maybe > >> apt-get-build-depends doesn't support it. > > > > The problem is not with the syntax, but with the package. Look closely > > which package provides it. It comes from heimdal itself and is added by > > my patch. So you first need to perform a native build and then once that > > native build is accessible, you can perform a cross build. > > Hmmm. Not entirely convinced here. If you look at the messages, it is > clearly trying to locate a package called "<cross>" in addition to the > correct package name.
I fear that you nailed it. I didn't look closely enough on you previous mail, sorry. apt-get-build-depends comes from haskell-debian-utils, which is built from haskell-debian, which is listed as unsupported in https://wiki.debian.org/BuildProfileSpec. I'm quite surprised that it misparses the dependency rather than failing. Do you require this tool for your heimdal workflow or otherwise? Is there a significant advantage over "apt-get build-dep -y ./"? I note that updating it is not trivial as it presently FTBFS in unstable. popcon is 20 and not growing. Given the adoption of profiles (<!nocheck> in particular), I guess that haskell-debian is unable to cope with 10% of the archive already. I can look into it in principle, but definitely not this year. If this is a blocker to you, consider applying the other aspects from my ftcbfs patch. Helmut
