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

[context] Preserve additionalMetadata content (RhBug:1808677) #903

Conversation

jrohel
Copy link
Contributor

@jrohel jrohel commented Mar 3, 2020

The dnf_repo_check_internal() can creates new libdnf::Repo. This patch
copies content of additionalMetadata from old repository object
to the new one.
The swidtags plugin adds new metadata type into additionalMetadata
(which is part of libdnf::Repo) in configuration hook. Without this
patch the added metadata types are not copied to the newly created
repository.

@dmach dmach changed the base branch from master to dnf-4-master March 5, 2020 12:19
@jrohel jrohel force-pushed the fix/context_preserve_additionalMetadata_set branch from 433c57f to 03a4464 Compare March 5, 2020 12:22
@jrohel jrohel changed the title [context] Prevent additionalMetadata content (RhBug:1808677) [context] Preserve additionalMetadata content (RhBug:1808677) Mar 5, 2020
@jrohel jrohel force-pushed the fix/context_preserve_additionalMetadata_set branch from 03a4464 to 63ea04a Compare March 6, 2020 11:57
The dnf_repo_check_internal() can creates new libdnf::Repo. This patch
copies content of additionalMetadata from old repository object
to the new one.
The swidtags plugin adds new metadata type into additionalMetadata
(which is part of libdnf::Repo) in configuration hook. Without this
patch the added metadata types are not copied to the newly created
repository.
@jrohel jrohel force-pushed the fix/context_preserve_additionalMetadata_set branch from 63ea04a to 633d888 Compare March 16, 2020 05:51
@j-mracek
Copy link
Member

@rh-atomic-bot r+

@rh-atomic-bot
Copy link

📌 Commit 633d888 has been approved by j-mracek

@rh-atomic-bot
Copy link

⌛ Testing commit 633d888 with merge 4c728fd...

rh-atomic-bot pushed a commit that referenced this pull request Mar 16, 2020
The dnf_repo_check_internal() can creates new libdnf::Repo. This patch
copies content of additionalMetadata from old repository object
to the new one.
The swidtags plugin adds new metadata type into additionalMetadata
(which is part of libdnf::Repo) in configuration hook. Without this
patch the added metadata types are not copied to the newly created
repository.

Closes: #903
Approved by: j-mracek
@j-mracek j-mracek self-assigned this Mar 16, 2020
@rh-atomic-bot
Copy link

💔 Test failed - status-papr

@j-mracek
Copy link
Member

@rh-atomic-bot retry

@rh-atomic-bot
Copy link

⌛ Testing commit 633d888 with merge 25d63e0...

rh-atomic-bot pushed a commit that referenced this pull request Mar 16, 2020
The dnf_repo_check_internal() can creates new libdnf::Repo. This patch
copies content of additionalMetadata from old repository object
to the new one.
The swidtags plugin adds new metadata type into additionalMetadata
(which is part of libdnf::Repo) in configuration hook. Without this
patch the added metadata types are not copied to the newly created
repository.

Closes: #903
Approved by: j-mracek
@rh-atomic-bot
Copy link

💔 Test failed - status-papr

@jrohel
Copy link
Contributor Author

jrohel commented Mar 17, 2020

It seems that this is not a problem with this PR:

Failing scenarios:
features/module/dnf-3-install-package.feature:31  I cannot install a specific package from not enabled module after reset

@j-mracek j-mracek merged commit e64bb08 into rpm-software-management:dnf-4-master Mar 17, 2020
@m-blaha
Copy link
Member

m-blaha commented Mar 17, 2020

I saw this test failing before. I suspect it is somehow connected with libnf pull requests that were moved from master branch to dnf-4-master. May be the patch is still being rebased to the master branch before testing (that is how I'm able to reproduce the test failure). Anyway, local testing of the patch properly rebased to dnf-4-master is passing the tests, so let's merge it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants