#93 epel7-ghc side tag to bootstrap ghc for ppc64le and aarch64
Closed: Fixed 4 years ago Opened 4 years ago by petersen.

[edit title updated]

I would like finally to address https://bugzilla.redhat.com/show_bug.cgi?id=1200404 and get epel7 ghc updated to support ppc64le, since it is blocking builds and updates of epel7 Haskell packages without excluding ppc64le, which I don't want to do. The current build ghc-7.6.3-18.3.el7 is only for x86_64 and ppc64.

Is it possible please to tag ghc-7.6.3-26.3.fc21 into epel7-build (or epel7-overrides) to allow building ghc-7.6.3 also for ppc64le? This would open EPEL7 again to Haskell package building.


No it's not, we could potentially looking at doing something in a epel7 sidetag so while it's done the main epel7 isn't polluted.

Okay that would also be fine.

what is the status here?

Was waiting on aarch64 so it can all be done at once.

Is there an ETA for aarch64?

We now have a epel7-ghc tag with ghc-7.6.3-26.3.fc21 for all EPEL architectures, let me know if you need any other packages

Thanks

Could you tag one more build into epel7-ghc for me?: hscolour-1.20.3-10.fc21
Then I think I should be good.

Thanks
http://koji.fedoraproject.org/koji/buildinfo?buildID=771784

Maybe I should rebase Epel7 to ghc-8.0 next year since it should support aarch64 and ppc64[le] much better (ghc-7.6 is really old now).

ghc-7.6.3-26.4.el7 is built :)

What is the plan for rebuilding the Haskell and other packages for arm64 and ppc64le?
Is that something that releng can take care of?

What is the plan for rebuilding the Haskell and other packages for arm64 and ppc64le?
Is that something that releng can take care of?

My understanding was that you would do the entire stack. The mass rebuild scripts don't deal with ordering or dependency requirements at all which is fine when all of the packages are already built like in a mass rebuild but not in a boostrap situation because there is a requirement of ordering, and possibly circular deps. Hence in these situations it's generally the maintainers that do it and it then gets submitted as an update via the standard process once the builds are all complete.

Okay I am working on it now after FUDCon APAC.

I finished most of the building just a handful of packages left: waiting for https://admin.fedoraproject.org/pkgdb/package/requests/9075

(Incidently I used this script to merge package commits from f21, and fhorder to order the builds.)

Actually ghc-hakyll will be a new package for epel7 so it can wait.

I would like to tag the epel7-ghc builds to epel7-candidate.
Can I go ahead and do that or does releng prefer to do that?

Actually ghc-hakyll will be a new package for epel7 so it can wait.
I would like to tag the epel7-ghc builds to epel7-candidate.
Can I go ahead and do that or does releng prefer to do that?

I'm happy for you to do that, it needs to go via bodhi anyway for EPEL as it's not like rawhide where it just gets mass tagged in.

Okay thanks! Will do :)

Okay the packages have been pushed to Bodhi and I tested them on x86_64: look good.
It would be good to test the other arch's though, just in case.

I sent an email out to ppc/arm/epel lists asking for feedback. epel7-ghc target is now removed. Thank you very much for the effort in getting this done!

@pbrobinson changed the status to Closed

4 years ago

Login to comment on this ticket.

Metadata