Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1922376 - python-pagure-messages-0.0.5 is available
Summary: python-pagure-messages-0.0.5 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pagure-messages
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-29 16:38 UTC by Upstream Release Monitoring
Modified: 2021-01-30 02:13 UTC (History)
3 users (show)

Fixed In Version: python-pagure-messages-0.0.5-1.fc32 python-pagure-messages-0.0.5-1.fc33 python-pagure-messages-0.0.5-1.el8
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-30 01:42:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Upstream Release Monitoring 2021-01-29 16:38:35 UTC 
Latest upstream release: 0.0.5
Current version/release in rawhide: 0.0.4-1.fc34
URL: https://pagure.io/pagure-messages

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/146089/
Comment 1 Upstream Release Monitoring 2021-01-29 16:38:39 UTC 
One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.
Comment 2 Upstream Release Monitoring 2021-01-29 16:38:40 UTC 
Skipping the scratch build because an SRPM could not be built: ['git', 'commit', '-a', '-m', 'Update to 0.0.5 (#1922376)'] returned 1: b'On branch master\nYour branch is up to date with \'origin/master\'.\n\nUntracked files:\n  (use "git add <file>..." to include in what will be committed)\n\tSRPMS/\n\nnothing added to commit but untracked files present (use "git add" to track)\n'
Comment 3 Fedora Update System 2021-01-29 16:46:13 UTC 
FEDORA-2021-091f116b62 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-091f116b62
Comment 4 Fedora Update System 2021-01-29 16:46:16 UTC 
FEDORA-2021-45b64b42c8 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-45b64b42c8
Comment 5 Fedora Update System 2021-01-29 16:46:18 UTC 
FEDORA-EPEL-2021-130f5ed6ae has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-130f5ed6ae
Comment 6 Fedora Update System 2021-01-30 01:42:36 UTC 
FEDORA-2021-45b64b42c8 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 7 Fedora Update System 2021-01-30 01:54:50 UTC 
FEDORA-2021-091f116b62 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2021-01-30 02:13:43 UTC 
FEDORA-EPEL-2021-130f5ed6ae has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.