[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1031647: git-annex: Bogus build dependency whitelist results in FTBFS on m68k



control: tag -1 + pending

Hello,

On Thu 23 Feb 2023 at 12:27PM -04, Joey Hess wrote:

> Sean Whitton wrote:
>> Joey, do you know why d/control restricts these build deps as it does?
>
> IIRC some of those deps are or were not available on some architectures
> like m68k. And the deps used to be gated behind the webapp build flag,
> so it would still build on those architectures without them installed.
>
> (I don't know how to get rmadison to display what packages are available
> on m68k? If those deps are avilable now, you could make git-annex use
> them.)
>
> Unfortunately, commit 78440ca37d75039d5eadd52eafbcd1751daba70a moved
> those build dependencies from behind that build flag. See commit for
> details; for some reason a new version of cabal changed its
> behavior in a way that seemed buggy, and that was the only workaround
> I could come up with at the time.
>
> One way you could get git-annex to build on arches where those build
> deps are not available would be to remove those build deps from the cabal
> file when building on those arches, and turning off the Assistant build
> flag.
>
> I think I have a better way though. The attached patch seems to work
> around that cabal problem in a way that will keep git-annex building
> when those deps are not installd. It should be in the next release of
> git-annex.

Thank you very much for the information and for the patch.

Given our freeze, I can add m68k to the list of architectures for those
build-deps, but I don't think we should apply Joey's patch for now.  But
let's let 10.20230126 migrate to testing first.  I've committed the
change to git; please remind me if I don't upload it a couple of days
from now.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


Reply to: