Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alter copr spec file for Fedora 41 and Rawhide #6200

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

loops
Copy link
Contributor

@loops loops commented Sep 27, 2024

SlouchyButton mentioned in #6015 that a Fedora Openssl packaging change was likely causing a problem for the copr build.

The deprecated engine header has been broken out into its own package. Add a dependency on it for Fedora 41 and Rawhide.

SlouchyButton mentioned in wez#6015 that a Fedora Openssl
packaging change was likely causing a problem for the
copr build.

The deprecated engine header has been broken out into
its own package.  Add a dependency on it for Fedora 41
and Rawhide.
@SlouchyButton
Copy link

Just a note here, this might stop working in future Fedora versions as the use is deprecated. Ideally, the OpenSSL engine should not be used, but since wezterm is not using it directly afaik, there is a chance that newer versions of the dependency that does use it will fix it before it becomes a problem.

Otherwise, this looks good, slight problem is that when I tried to mockbuild the new spec file it seems that time dependency fails to build, possibly due to newer rust.

error[E0282]: type annotations needed for `Box<_>`
  --> /builddir/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.31/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
   = note: this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` by calling `cargo update`

This shouldn't really block this PR as it is unrelated, but will also need further investigation to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants