Bug 2035151
Summary: | Please branch and build pandoc for EPEL9 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Michel Lind <michel> |
Component: | pandoc | Assignee: | Jens Petersen <petersen> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | epel9 | CC: | code, davide, dofiy12982, fedora, gigeti2945, leonfauster, maxwell, michel, orion, pasik, petersen, redhat-bugzilla, tdawson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | pandoc-2.14.0.3-16.el9 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-09-06 10:56:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2037934 | ||
Bug Blocks: | 1914423, 2068295, 2100264 |
Description
Michel Lind
2021-12-23 05:05:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36. This will need ghc to build, of course. Adding that as a blocker. Yes, thanks! I hope to build ghc soon. (In reply to Michel Alexandre Salim from comment #0) > Could this be branched for EPEL 9? I'm happy to co-maintain (FAS: salimma), > and also, if you add the epel-packagers-sig group to the ACL as collaborator > on epel* branch, the EPEL Packagers SIG can help branch and build this for > future EPEL releases. I requested epel9 https://pagure.io/releng/fedora-scm-requests/issue/43158 Also added you, Michel, as collaborator. I am open to including epel-packagers-sig, though I do feel boostrapping pandoc etc for epel9 is kind of non-trivial: anyway they would have to be added to many packages for it to be meaningful really. Having said that I would not have objected to having Haskell packages included in the epel10 bootstrap say. (In reply to Jens Petersen from comment #4) > I am open to including epel-packagers-sig, > though I do feel boostrapping pandoc etc for epel9 is kind > of non-trivial: anyway they would have to be added > to many packages for it to be meaningful really. > Having said that I would not have objected to having > Haskell packages included in the epel10 bootstrap say. The purpose of this comment is just to write down the list of missing direct dependencies: $ fedpkg --release epel9 mockbuild --enablerepo=epel-testing […] No matching package to install: 'ghc-Glob-prof' No matching package to install: 'ghc-HTTP-prof' No matching package to install: 'ghc-HsYAML-prof' No matching package to install: 'ghc-JuicyPixels-prof' No matching package to install: 'ghc-SHA-prof' No matching package to install: 'ghc-aeson-pretty-prof' No matching package to install: 'ghc-aeson-prof' No matching package to install: 'ghc-attoparsec-prof' No matching package to install: 'ghc-base64-bytestring-prof' No matching package to install: 'ghc-blaze-html-prof' No matching package to install: 'ghc-blaze-markup-prof' No matching package to install: 'ghc-case-insensitive-prof' No matching package to install: 'ghc-connection-prof' No matching package to install: 'ghc-data-default-prof' No matching package to install: 'ghc-doclayout-prof' No matching package to install: 'ghc-doctemplates-prof' No matching package to install: 'ghc-file-embed-prof' No matching package to install: 'ghc-haddock-library-prof' No matching package to install: 'ghc-hslua-module-text-prof' No matching package to install: 'ghc-hslua-prof' No matching package to install: 'ghc-http-client-prof' No matching package to install: 'ghc-http-client-tls-prof' No matching package to install: 'ghc-http-types-prof' No matching package to install: 'ghc-network-prof' No matching package to install: 'ghc-network-uri-prof' No matching package to install: 'ghc-pandoc-types-prof' No matching package to install: 'ghc-random-prof' No matching package to install: 'ghc-safe-prof' No matching package to install: 'ghc-scientific-prof' No matching package to install: 'ghc-skylighting-core-prof' No matching package to install: 'ghc-skylighting-prof' No matching package to install: 'ghc-split-prof' No matching package to install: 'ghc-syb-prof' No matching package to install: 'ghc-tagsoup-prof' No matching package to install: 'ghc-temporary-prof' No matching package to install: 'ghc-texmath-prof' No matching package to install: 'ghc-text-conversions-prof' No matching package to install: 'ghc-th-lift-instances-prof' No matching package to install: 'ghc-unicode-transforms-prof' No matching package to install: 'ghc-uniplate-prof' No matching package to install: 'ghc-unordered-containers-prof' No matching package to install: 'ghc-vector-prof' No matching package to install: 'ghc-xml-conduit-prof' No matching package to install: 'ghc-xml-prof' No matching package to install: 'ghc-zip-archive-prof' No matching package to install: 'ghc-zlib-prof' What's the best way to help in this process? Here is another list: https://issues.redhat.com/projects/CS/issues/CS-611 Thanks, I have started requesting branches. I hope pandoc will be ready within a few weeks. I am also happy to so a temporary copr repo for this or other Haskell tools while people are waiting - it is fairly easy to spin up. (In reply to Orion Poplawski from comment #6) > What's the best way to help in this process? I wish I had an good answer - in practice I found coordinating all these deps across different people doesn't really help a whole lot because they really all need to be built together. A copr repo might be useful to test and provide earlier access. Anyway my current plan is to push a refresh to Rawhide and use that as the basis for epel9 packages. I hope the rawhide building will complete by the end of this week - after that the main bottleneck is requesting epel9 branches for the packages I don't "own". *** Bug 2089013 has been marked as a duplicate of this bug. *** Any news on this? stalled? As far as I know, Jens is still working on this. There are a lot of dependencies that need to be branched. Please be patient and understand that this is a volunteer driven project. Yes, thanks gotmax, I will be asking for 33 branches for packages that I don't maintain directly. (Actually I am also adding some features to fbrnch to help with this.) Thanks for everyone's patience. Also my offer to put up an epel9 copr repo for the pandoc executable in the meantime, if it helps out, still stands :-) Though hopefully it won't be too much longer now, thanks to everyone for their long patience. (Also just the record, the total number of library dependencies is 117 - the rest of the packages have already been branched by me though.) I am currently blocked on branches for the following 3 packages: - ghc-cmdargs - ghc-colour - ghc-network-uri I sent a mail to Ben, but in the worst case there might be a delay of a few weeks. > - ghc-cmdargs
> - ghc-colour
> - ghc-network-uri
It looks like you already have `commit` on all of those packages. I'm not sure if that happened since you wrote the last message. Note that you don't need `admin` to request an EPEL branch.
Yep, I got around to it this morning. Thanks a loit, Ben! Appreciate it (Including edit-distance, in f37 this would unlock 267 packages :-)) Thanks Jens for your work FEDORA-EPEL-2022-2f6165822e has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2f6165822e FEDORA-EPEL-2022-2f6165822e has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2f6165822e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-2f6165822e has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. |