Bug 2253997 - zlib-ng-compat for rust-flate2
Summary: zlib-ng-compat for rust-flate2
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-flate2
Version: 40
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Rust SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2165961
TreeView+ depends on / blocked
 
Reported: 2023-12-11 12:49 UTC by Lumír Balhar
Modified: 2024-05-26 16:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-26 16:23:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lumír Balhar 2023-12-11 12:49:55 UTC
Would it be possible to add zlib-ng-compat feature into rust-flate2 package?

Reproducible: Always

Steps to Reproduce:
1. Try to update rust-yrs to the latest version 0.17.2
Actual Results:  
Problem 1: nothing provides requested (crate(flate2/zlib-ng-compat) >= 1.0.22 with crate(flate2/zlib-ng-compat) < 2.0.0~)

Comment 1 Fabio Valentini 2023-12-11 13:36:23 UTC
Does this crate's test suite actually depend on zlib-ng or would it also work with the default backend?

Could you try replacing

[dev-dependency.flate2]
version = "..."
default-features = false
features = ["zlib-ng-compat"]

with something like this?

[dev-dependency.flate2]
version = "..."

If this also works, then I wouldn't need to package zlib-ng bindings and whatever else those pull in as additional dependencies :)

Comment 2 Lumír Balhar 2023-12-12 13:13:27 UTC
Thanks for the quick response. After the proposed change implemented via sed into the specfile, the build process no longer complains about the missing feature but there are two more missing dependencies so I cannot tell for sure that the build will work with that workaround.

Comment 3 Aoife Moloney 2024-02-15 23:07:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle.
Changing version to 40.

Comment 4 Fabio Valentini 2024-05-26 16:23:15 UTC
We have now enabled the zlib-ng backend, but zlib-ng-compat isn't universally available ... so it's not really feasible to do that. I'm also not sure why project would want to use zlib-ng via the zlib compat API instead of either ... the actual zlib backend *or* the actual zlib-ng backend. :shrug:


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