Skip to content

Conversation

hamishmack
Copy link
Collaborator

Not sure what caused #884, but this check should prevent the
erroneous output from making it into the binary cache if it happens
again.

Not sure what caused #884, but this check should prevent the
erroneous output from making it into the binary cache if it happens
again.
@@ -24,6 +24,12 @@ export expires="4000-01-01T00:00:00Z"
ln -sf ${index} $out/01-index.tar.gz
export index_md5=$(nix-hash --flat --type md5 ${index})
export index_sha256=$(nix-hash --flat --type sha256 ${index})
${ pkgs.lib.optionalString (index ? outputHash) ''
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does it mean if the attribute is missing?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The index can come from extra-hackages and I don't think we want to require an outputHash for those. For instance the test for extra-hackages does not include one

index = ./01-index.tar.gz;

I have added a comment to the code.

@hamishmack hamishmack merged commit a1b6975 into master Oct 21, 2020
@iohk-bors iohk-bors bot deleted the hkm/hackage-check branch October 21, 2020 08:51
booniepepper pushed a commit to booniepepper/haskell.nix that referenced this pull request Feb 4, 2022
…#885)

Not sure what caused input-output-hk#884, but this check should prevent the
erroneous output from making it into the binary cache if it happens
again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants