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

[noissue]: Update python-gnupg requirement from ~=0.4.7 to ~=0.5.1 #130

Open
wants to merge 79 commits into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Aug 4, 2023

Updates the requirements on python-gnupg to permit the latest version.

Release notes

Sourced from python-gnupg's releases.

Enhancement and bug-fix release

This is an enhancement and bug-fix release, and all users are encouraged to upgrade.

Brief summary:

  • Added TRUST_EXPIRED to trust_keys. Thanks to Leif Liddy for the patch.

  • Fix #206: Remove deprecated --always-trust in favour of --trust-model always

  • Fix #208: Add status_detail attribute to result objects which is populated when the status is 'invalid recipient' (encryption/decryption) or 'invalid signer' (signing). This attribute will be set when the result object's status attribute is set to invalid recipient and will contain more information about the failure in the form of reason:ident where reason is a text description of the reason, and ident identifies the recipient key.

  • Add scan_keys_mem() function to scan keys in a string. Thanks to Sky Moore for the patch.

  • Fix #214: Handle multiple signatures when one of them is invalid or unverified.

  • A problems attribute was added which holds problems reported by gpg during verification. This is a list of dictionaries, one for each reported problem. Each dictionary will have status and keyid keys indicating the problem and the corresponding key; other information in the dictionaries will be error specific.

  • Fix #217: Use machine-readable interface to query the gpg version. Thanks to Justus Winter for the patch.

  • Added the ability to export keys to a file. Thanks to Leif Liddy for the patch.

This release has been signed with my code signing key:

Vinay Sajip (CODE SIGNING KEY) Fingerprint: CA74 9061 914E AC13 8E66 EADB 9147 B477 339A 9B86

Commits
  • 1aabc9b Changes for 0.5.1.
  • ca8e378 Update documentation.
  • 8b29334 Add documentation for custom stream handling using the on_data attribute.
  • 2a7eb0c Updated Python versions in GitHub Actions matrix.
  • e7c39d2 Fix #217: Use machine-readable interface to query the version. (#224)
  • d35dfbd Pin Sphinx version.
  • 8f0a84f Add Read The Docs configuration.
  • bc98882 Update documentation to explain how to get signed data out during verification.
  • 6081e55 Collect problems reported during verification.
  • f7023c6 Tidy up handling of KEY_CONSIDERED.
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dkliban and others added 30 commits July 1, 2021 10:22
The change pins towncrier to 19.9.0 and also adds an optional parameter to the release
workflow. The optional 'before_script' parameter allows custom bash code to be run
before script.sh is run. This is useful for resolving docs issues after a release.

[noissue]
This patch clearly defines the exported_resources as a list of URI strings. The implementation for
the ExportedResourceSerializer is shared with CreatedResource serializer. They now both inherit from
a new RelatedResourceField.

backports: #9008
https://pulp.plan.io/issues/9008

fixes #9025

(cherry picked from commit f52ba80)
backports: #9003
https://pulp.plan.io/issues/9003

fixes #9015

(cherry picked from commit e4b1724)
backports: #9024
https://pulp.plan.io/issues/9024

fixes #9068

(cherry picked from commit 0c9541d)
backports: #9039
https://pulp.plan.io/issues/9039

fixes #9059

(cherry picked from commit 2cc9804)
backports #8954

fixes #9058

(cherry picked from commit 3bc707a)
This unskips the `Range` header and adds support for it to the content
app.

backports #8865

fixes #9057

(cherry picked from commit df2c8f1)
backports: #9074

fixes #9077

(cherry picked from commit ca0ef8f)
If Redis goes down then its persisted data can get out of sync with
Pulp, because cache invalidation events cannot occur. We should mitigate
the impact by letting cache entries expire after a shorter period of
time.

backports: #8996
https://pulp.plan.io/issues/8996

fixes #9063

(cherry picked from commit 017b0b1)
[noissue]
When hitting ctrl-c twice, workers should also kill their supervised
tasks. And shut them down.

backports #8986
https://pulp.plan.io/issues/8986

fixes #9086

(cherry picked from commit 80d7d6d)
Before this change, it was not possible to determine why did the synchronization fail when a user provided a seemingly valid URL. This commit also adds more relevant information to the error message.

Having set `ALLOWED_EXPORT_PATHS` to `["/tmp", "/home/vagrant/test"]`, the following error messages are shown:

```
$ pulp file remote create --name test --url file://error/vagrant/test/centos-7/PULP_MANIFEST
Error: {"url":["The path 'error/vagrant/test/centos-7/PULP_MANIFEST' needs to be an absolute pathname."]}

$ pulp file remote create --name test --url file:///error/vagrant/test/centos-7/PULP_MANIFEST
Error: {"url":["The path '/error/vagrant/test/centos-7/PULP_MANIFEST' does not start with any of the allowed import paths"]}
```

backports #9080

fixes #9083

(cherry picked from commit d8cba5a)
Redis is only used when cache is enabled or RQ tasking is used. In other
cases, the connection is not needed. We've changed the Foreman installer
to only install Redis if needed, just to stop wasting resources[1].
However, this leads to warnings.

This PR changes the status view to only include Redis if it's used.

[1]: theforeman/puppet-pulpcore@7a5543b

backports #9070
https://pulp.plan.io/issues/9070

fixes #9085

(cherry picked from commit 8ab8afb)
backports #8779

fixes #9116

(cherry picked from commit 0cfaa8e)
As of this commit, content app is no longer storing temporary files in the /var/run/ directory. The temporary files were created during on-demand downloading and were not removed until, e.g., restarting pulp services.

backports #9000

fixes #9110

(cherry picked from commit f8bd7f8)
Before this commit, the condition that checks whether pulp's temporary files are stored within /var/lib/pulp was never met because it looked for files starting with /var/lib/pulp/media (MEDIA_ROOT). MEDIA_ROOT is however no longer pointing to /var/lib/pulp.

backports #8295

fixes #9103

(cherry picked from commit fbe2d7f)
pulpbot and others added 28 commits August 24, 2021 17:46
Instead perform a simple xor on the first and second half of the task
uuid.

backports #9249

fixes #9288

(cherry picked from commit 1d77e5c)
aiohttp automatically enflates gzipped responses. Pulp clients always receive
uncompressed responses when requesting on_demand content.

backports: #9213

fixes #9325

(cherry picked from commit 7e0a79e)
For some strange reason some Openshift environments do not like the
runtime import the worker entrypoint used. Moving it to the top where it
belongs anyway resolves the problem.

backports #9338

fixes #9339

(cherry picked from commit 022d2e3)
backports #9266.
closes: #9401

(cherry picked from commit 4023fce)
backports #9395.
closes: #9400

(cherrypicked from commit 489156e)
backports #9427.
closes: #9440

[nocoverage]

(cherry picked from commit 6e18f2e)
[noissue]
backports #9441.
[nocoverage]
Required PR: pulp#1637

fixes #9445

(cherry picked from commit cd9b578)
All workers that are considered offline will be removed from the database
periodically.

backports #8931

fixes #9462

(cherry picked from commit 5bbf959)
backports: #9427

fixes #9453

(cherry picked from commit 6fb9109)
Forcing deadlocks requires a lot of time and pulpcore-workers running.
There is therefore no specific CI test for this, but there is a reproducer
script that will force deadlocks to happen (and show that they're fixed) here:

https://github.com/ggainey/pulp_startup/blob/main/8750_deadlocks/file_repro.sh

backports #8750
fixes #9379

(cherry picked from commit 6af3519)
[noissue]
closes #9491
backports #9301

(cherry picked from commit 8a1db3b)
[noissue]
SimpleTestCase does not allow database access.

[noissue]
Updates the requirements on [python-gnupg](https://github.com/vsajip/python-gnupg) to permit the latest version.
- [Release notes](https://github.com/vsajip/python-gnupg/releases)
- [Changelog](https://github.com/vsajip/python-gnupg/blob/master/release)
- [Commits](vsajip/python-gnupg@0.4.7...0.5.1)

---
updated-dependencies:
- dependency-name: python-gnupg
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants