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

Return valid repository signature flag (bsc#1009127) #65

Merged
merged 2 commits into from
Mar 29, 2017
Merged

Conversation

lslezak
Copy link
Member

@lslezak lslezak commented Feb 7, 2017

To allow checking the repository metadata status.

See bug 1009127 for more details.

@@ -115,6 +116,7 @@ PkgFunctions::SourceGetCurrent (const YCPBoolean& enabled)
* "service" : YCPString, (service to which the repo belongs, empty if there is no service assigned)
* "keeppackages" : YCPBoolean,
* "is_update_repo" : YCPBoolean, (true if this is an update repo - this requires loaded objects in pool otherwise the flag is not returned! The value is stored in repo metadata, not in .repo file!)
* "valid_repo_signature" : YCPBoolean or YCPVoid (boolean: whether the repo metadata are signed and valid, nil: unsigned metadata)
Copy link
Member

Choose a reason for hiding this comment

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

This is still unclear. How about: nil=unsigned, false=bad signature, true=good signature.

@lslezak
Copy link
Member Author

lslezak commented Mar 29, 2017

The change might not be used for fixing bug 1009127 in the end, but it still might be useful later anyway so let's merge it.

@lslezak lslezak changed the title [WIP] Return valid repository signature flag (bsc#1009127) Return valid repository signature flag (bsc#1009127) Mar 29, 2017
@lslezak lslezak merged commit afc8d51 into master Mar 29, 2017
@lslezak lslezak deleted the repo_signature branch March 29, 2017 16:24
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.

3 participants