update on F32 progress
by Jens-Ulrik Petersen
Hi Haskell SIG,
Sorry for the lack of communication: I think this time I forgot to send out
a heads-up about F32 plans, which also got a little delayed in the end but
are now completed in f32 at least (but not yet tagged into Rawhide)
https://bodhi.fedoraproject.org/updates/FEDORA-2020-b0652e4f4b
TL;DR *Please do not build anything now* (into Rawhide) until the f32
builds get tagged to f33 too. I will send a follow-up mail once I see that
releng has done that.
So I have updated, and today pushed 342 package builds into f32: the
packages have been refreshed to cabal-rpm-2.0.2 (which is not yet in
Fedora, but 2.0.3 (released today) with a couple of bugfixes will be very
soon), and a lot of the packages also got updated to Stackage LTS 14
versions (from 13). In fact I have refreshed all the packages locally to
2.0.2 in master but not pushed the rest yet to master - I will do that now
but no rebuilds are needed, since it is just smaller packaging changes
(though I wish I had pushed that part ahead of the mass rebuild).
I believe only 2 packages are currently leftover broken: ghc-derive which
is no longer maintained (I confirmed with the author and we can/should
probably retire it now), and also ghc-cabal-helper, which I already wanted
to retire in F31, but kept around - it now needs an additional dep
(optics-core) - I think it could be retired now too. I also fixed the
linking of libiw in wireless-tools (fixing the xmobar build) and restored
ghc-hgettext.
The biggest packaging change this time might be getting rid of the
temporary %{_devel} compat macro for ghc-*-prof. For F33 (in fact in the
next minor release of cabal-rpm probably) we can also drop the deprecated
install scriptlets (just needed for f30 now).
I have been thinking that next time we should start the process earlier and
I will send out a call for help so people can help refresh their packages
and also check for missing new dependencies. (We still have some "technical
debt" (aka subpackaging of missing libs, which we should get rid of too.)
LTS 15 (just released) will bring ghc-8.8. I am also thinking about not
using BR: ghc-*-static since they are just aliases and devel seems
sufficient, and the -static BRs caused some resolver problems (corner
cases).
You can see the complete list of updated packages in the Bodhi update which
went stable earlier (tomorrow was the deadline for completing F32 Changes):
https://bodhi.fedoraproject.org/updates/FEDORA-2020-b0652e4f4b
If you have any questions or comments please ask.
Thanks, Jens
ps Another topic now that F32 work is largely done, which deserves its own
thread, is ghc for EPEL8.
pps Also dhall is nearly packaged up now for Fedora. :)
3 years, 9 months
- 1
- 2
I would like to have dhall-haskell in Fedora, have questions
by Adam Saleh
Hi,
I don't think I am ready to go through the package process [1] with this
just yet, but I have questions to ask, so I am writing here :-)
I have been using https://dhall-lang.org/ for some of my
openshift/kubernetes configuration, like it much more than writing out
YAML, and I would like to have it available in Fedora.
I am mostly interested in the cli-utilities that compile dhall files to
various data formats (i.e. bash, yaml, json, text, e.t.c) and provide
development support (linting, language-server, e.t.c.), currently I am
using the statically compiled binaries from their github releases.
I know that there have been some attempts from dhall developer to use nix
to build RPMs, but after they started distributing statically compiled
binaries, they didn't pursue this further.
I can build binaries on my box using stack, but I am not yet sure how to
use fedora-provided utilities (i.e. is it just i.e. 'cabal-rpm builddep &&
cabal-rpm spec dhall && cabal-rpm local dhall' ?).
Here are my questions:
Did anybody try to package Dhall already?
Can I take a stab at it? :-)
Do I correctly assume I should first be able to build the binaries with
fedora-provided infrastructure (and not rely on i.e. nix)?
Should I assume i.e Fedora 31 is tracking Stackage LTS 13 and i.e Fedora 32
would be tracking Stackage LTS 14, when i.e. trying to resolve library
dependencies?
When running dealing with cabal-rpm, what should I do about packages
reported by `cabal-rpm missingdeps`?
Would some of you have time to help me troubleshoot, or answer more of my
questions? :)
Thanks for any response!
Adam
[1]
https://fedoraproject.org/wiki/Haskell_SIG?rd=SIGs/Haskell#New_Package_Pr...
and https://docs.fedoraproject.org/en-US/packaging-guidelines/Haskell/ ?
3 years, 9 months
- 4
- 12
- ← Newer
- 1
- Older →