Bug 1820795 - libzen-0.4.38 is available
Summary: libzen-0.4.38 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libzen
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vasiliy Glazov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-03 22:10 UTC by Upstream Release Monitoring
Modified: 2020-04-25 02:18 UTC (History)
2 users (show)

Fixed In Version: libzen-0.4.38-1.fc31 libzen-0.4.38-1.fc30 libzen-0.4.38-1.el8 libzen-0.4.38-1.el7 libzen-0.4.38-1.fc32
Clone Of:
Environment:
Last Closed: 2020-04-15 20:33:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2020-04-03 22:10:53 UTC
Latest upstream release: 0.4.38
Current version/release in rawhide: 0.4.37-6.fc32
URL: https://github.com/MediaArea/ZenLib

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

Comment 1 Upstream Release Monitoring 2020-04-03 22:10:56 UTC
One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Comment 2 Fedora Update System 2020-04-07 13:01:18 UTC
FEDORA-2020-3e12090ecc has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3e12090ecc

Comment 3 Fedora Update System 2020-04-07 13:01:19 UTC
FEDORA-2020-ebba614107 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ebba614107

Comment 4 Fedora Update System 2020-04-07 13:01:20 UTC
FEDORA-EPEL-2020-c4a578b4cc has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c4a578b4cc

Comment 5 Fedora Update System 2020-04-07 13:01:21 UTC
FEDORA-EPEL-2020-bc4f0d8770 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-bc4f0d8770

Comment 6 Fedora Update System 2020-04-07 13:01:22 UTC
FEDORA-2020-cff0e501f8 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-cff0e501f8

Comment 7 Fedora Update System 2020-04-08 02:15:31 UTC
FEDORA-2020-cff0e501f8 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-cff0e501f8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-cff0e501f8

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

Comment 8 Fedora Update System 2020-04-08 02:29:34 UTC
FEDORA-2020-ebba614107 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ebba614107`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ebba614107

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

Comment 9 Fedora Update System 2020-04-08 02:38:40 UTC
FEDORA-EPEL-2020-bc4f0d8770 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-bc4f0d8770

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

Comment 10 Fedora Update System 2020-04-08 02:47:04 UTC
FEDORA-2020-3e12090ecc has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3e12090ecc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3e12090ecc

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

Comment 11 Fedora Update System 2020-04-08 02:49:32 UTC
FEDORA-EPEL-2020-c4a578b4cc has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c4a578b4cc

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

Comment 12 Fedora Update System 2020-04-15 20:33:31 UTC
FEDORA-2020-cff0e501f8 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2020-04-15 21:01:30 UTC
FEDORA-2020-3e12090ecc has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2020-04-22 18:41:59 UTC
FEDORA-EPEL-2020-bc4f0d8770 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2020-04-22 19:13:15 UTC
FEDORA-EPEL-2020-c4a578b4cc has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2020-04-25 02:18:45 UTC
FEDORA-2020-ebba614107 has been pushed to the Fedora 32 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.