Bug 1931187 - libgphoto2-2.5.27 is available
Summary: libgphoto2-2.5.27 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libgphoto2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Josef Ridky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-21 11:42 UTC by Upstream Release Monitoring
Modified: 2021-03-19 20:10 UTC (History)
7 users (show)

Fixed In Version: libgphoto2-2.5.27-1.fc32 libgphoto2-2.5.27-1.fc33 libgphoto2-2.5.27-1.fc34
Clone Of:
Environment:
Last Closed: 2021-03-18 04:12:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2021-02-21 11:42:34 UTC
Latest upstream release: 2.5.27
Current version/release in rawhide: 2.5.26-1.fc34
URL: http://www.gphoto.org/

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/12558/

Comment 1 Fedora Update System 2021-03-10 10:47:20 UTC
FEDORA-2021-e617863fe9 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e617863fe9

Comment 2 Fedora Update System 2021-03-10 10:47:22 UTC
FEDORA-2021-e823f5d508 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e823f5d508

Comment 3 Fedora Update System 2021-03-10 18:52:03 UTC
FEDORA-2021-e823f5d508 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e823f5d508`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e823f5d508

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2021-03-10 22:09:59 UTC
FEDORA-2021-e617863fe9 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e617863fe9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e617863fe9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-03-10 22:40:01 UTC
FEDORA-2021-8201d03bb6 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8201d03bb6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8201d03bb6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-03-18 04:12:11 UTC
FEDORA-2021-8201d03bb6 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-03-18 04:45:24 UTC
FEDORA-2021-e617863fe9 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-03-19 20:10:24 UTC
FEDORA-2021-e823f5d508 has been pushed to the Fedora 34 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.