-
Notifications
You must be signed in to change notification settings - Fork 701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport batch 2 #6400
Closed
Closed
Backport batch 2 #6400
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
phadej
commented
Dec 3, 2019
- Use lukko for file-locking #6345
- Use hackage-security-0.6 #6388
- Travis ghc 8.8 #6389
Issue haskell#5119 is tracking spurious generation of these warnings. There are a lot of them! We can't release with so many false positives, so just squelch the warning outright. This is a hack and this commit should be reverted if we get a proper fix that can be backported to the 2.4 branch. (cherry picked from commit e8ba731)
3.0 port of the 2.4 haskell#5119 hack
(cherry picked from commit 4d2ca52)
While those buildinfo fields were added to the parser some time ago via 57d7f28 and 4a28765 that work was never completed by implementing the necessary build/sdist logic in Cabal. This commit remedies this oversight by implementing and wiring up the missing build logic. NOTE: This is a backport of (at time of writing) unfinished haskell#6033 to the 3.0 branch Specifically preprocessor-generated asm/cmm-sources need more work. Co-authored-by: Sylvain Henry <sylvain@haskus.fr>
* Fix `v2-repl` changing directory incorrectly. * Add changelog entry * Add haddocks * Add check for GHC geq 7.6 (`-ghci-script` wasn't there yet) (cherry picked from commit fef6d8d)
Make `debug-info` >= 1 imply library/executable-stripping: False (cherry picked from commit ed3ae13)
This reverts commit c5395b8.
) Treating globs like filenames was always illegitimate, but this code was broken further by the addition of recursive globs. I had a look around for other dubious code along these lines, and it looks like this site is the only problematic one. Fixes haskell#6125. (cherry picked from commit 7fec503)
This reverts commit 9b1e15c.
Parse list fields in cabal config file (cherry picked from commit 0d32892)
Previously we would issue a warning of the following form when we encountered a field that isn't supported by the cabal-version declared in the cabal file: Warning: ghc-heap.cabal:30:3: The field "cmm-sources" is available only since the Cabal specification version 3.0. The message, however, doesn't tell the user the consequence of this warning. Consequently a user could easily be confused when the build subsequently fail. Avoid this possibility by clearly stating that the field value will be ignored.
Backports ignore msg spdx
…o-ghc Pass `ld-options` through to GHC (cherry picked from commit 853414b)
cabal run works with Literate Haskell file (cherry picked from commit dc13803)
Issue 5977 (cherry picked from commit 0d2d9ca)
Add changelog for haskell#5977 amd haskell#6134 fixes [ci skip] (cherry picked from commit 773ad13)
…-default Default to non-interactive init. (cherry picked from commit 690d6c5)
Fix v2-install ProgramDb confusion (cherry picked from commit a7a9766)
[ci skip]
- Add needProgram Ad use it to make readPkgConfigDb not fail if there aren't pkg-config executable. - Skip few tests on windows - Use removePathForcibly in integration-tests2 if available remove local tarball test on Windows
Backport 6270
- They use 7.10.3 and 8.0.2 - timeout quite often. - Let's have them, but let them fail without red mark
Travis backports 3.0
Also in CI setup, install hackage-repo-tool using `cabal new-install`. And remove slightly confusing cabal.project.travis file.
Use cabal-install-3.0, as otherwise we won't be able to build custom setup for GHC-8.8
I have no idea why GitHub created this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.