Skip to content
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

revert: remove inconsistent use of outcome enums, add another error v… #122

Closed
wants to merge 1 commit into from

Conversation

drahnr
Copy link
Contributor

@drahnr drahnr commented Apr 15, 2023

…ariant instead

@@ -222,7 +212,7 @@ impl RPMPackage {

verifier.verify(header_and_content_cursor, signature_header_and_content)?;

Ok(SignatureVerificationOutcome::Pass)
Ok(())
}

pub fn verify_digest(&self) -> Result<DigestVerificationOutcome, RPMError> {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Need to remove it from this signature too

@dralley
Copy link
Collaborator

dralley commented Apr 16, 2023

@drahnr I've merged this into #124 and fixed the compile error

@dralley dralley closed this Apr 16, 2023
@dralley dralley deleted the bernhard-revert-outcome-enums branch April 16, 2023 19:20
@drahnr
Copy link
Contributor Author

drahnr commented Apr 18, 2023

Ok, next time, could we keep it open until the PR you merged the changeset into actually made it into main/master? I generally prefer to not make squashing multiple orthogonal changesets into one if they're already separate a pattern, (I know I made a very similar mistake in #111 )

@dralley
Copy link
Collaborator

dralley commented Apr 18, 2023

I don't ever use squash-and-merge personally. The commit is still separate in my PR

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