Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). Your package (rust-tss-esapi) Fails To Install in Fedora 34: can't install rust-tss-esapi+generate-bindings-devel: - nothing provides (crate(tss-esapi-sys/generate-bindings) >= 0.1.1 with crate(tss-esapi-sys/generate-bindings) < 0.2.0~) needed by rust-tss-esapi+generate-bindings-devel-5.0.1-1.fc34.noarch can't install rust-tss-esapi-devel: - nothing provides (crate(tss-esapi-sys/default) >= 0.1.1 with crate(tss-esapi-sys/default) < 0.2.0~) needed by rust-tss-esapi-devel-5.0.1-1.fc34.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
Hello, This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
So this is because eclipseo moved rust-tss-esapi-sys to 0.2.0 in F-34 without moving rust-tss-esapi to 6.x and fixing any of the other deps in the chain. I'm not sure why it was moved, Robert why?
(In reply to Peter Robinson from comment #2) > So this is because eclipseo moved rust-tss-esapi-sys to 0.2.0 in F-34 > without moving rust-tss-esapi to 6.x and fixing any of the other deps in the > chain. I'm not sure why it was moved, Robert why? We had to bump up bindgen for some reason, which impacted tss-esapi-sys. For some unknown reason, I didn't see/take care of rust-tss-esapi-sys dependency tree?
Doyou need I will see to update the stack as soon as I can
Hello, This is the second reminder (step 4 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
Hi! I'm sorry about the bad handling of the particular broken update that caused this issue. Is there anything I can do to help fix it? I think reverting rust-tss-esapi-sys in Fedora 34 to version 0.1.x and adapting it to build with bindgen 0.59 should fix this bug.
(In reply to Fabio Valentini from comment #6) > Hi! I'm sorry about the bad handling of the particular broken update that > caused this issue. > Is there anything I can do to help fix it? > I think reverting rust-tss-esapi-sys in Fedora 34 to version 0.1.x and > adapting it to build with bindgen 0.59 should fix this bug. )This would imply an epoch bump, not sure that is the best solution.
The epoch bump would be restricted to F34 branch, and it should be the simplest fix, shouldn't it?
(In reply to Fabio Valentini from comment #8) > The epoch bump would be restricted to F34 branch, and it should be the > simplest fix, shouldn't it? No, because it instantly breaks upgrade paths! Less of a problem with rust as all the deps are statically compiled but it's like an uber override version number.
Upgrade path is 1) no longer strictly enforced between Fedora versions, and 2) uber-unimportant for packages that are never installed outside ephemeral build environments (so are never upgraded in-place).
Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). All subpackages of a package against which this bug was filled are now installable or removed from Fedora 34. Thanks for taking care of it!