Bug 1889215 - libimagequant-2.13.0 is available
Summary: libimagequant-2.13.0 is available
Alias: None
Product: Fedora
Classification: Fedora
Component: libimagequant
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Sandro Mani
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-19 05:22 UTC by Upstream Release Monitoring
Modified: 2020-10-20 11:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-10-20 11:01:53 UTC
Type: ---

Attachments (Terms of Use)

Description Upstream Release Monitoring 2020-10-19 05:22:49 UTC
Latest upstream release: 2.13.0
Current version/release in rawhide: 2.12.6-3.fc33
URL: https://pngquant.org/lib/

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

Comment 1 Upstream Release Monitoring 2020-10-19 05:22:56 UTC
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 2 Sergio Basto 2020-10-19 09:10:56 UTC
Sandro, I added you as admin of pngquant package

Comment 3 Sandro Mani 2020-10-20 11:01:53 UTC
Thanks (actually didn't even realize I wasn't admin of pngquant :S I just have a bunch of packages which one reason or another I ended up taking care of updating them, and pngquant is on that list, I beleive due to the libimagequant coupling - so sorry in case there was miscommunication here!)

Note You need to log in before you can comment on or make changes to this bug.