Bug 2227084 - 389-ds-base FTBFS with rust-1.71.0
Summary: 389-ds-base FTBFS with rust-1.71.0
Keywords:
Status: VERIFIED
Alias: None
Deadline: 2023-08-14
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rust-toolset
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Josh Stone
QA Contact: Jesus Checa
URL:
Whiteboard:
Depends On: 2225471
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-27 18:20 UTC by Josh Stone
Modified: 2023-08-01 15:32 UTC (History)
5 users (show)

Fixed In Version: rust-toolset-rhel8-8090020230727010609.2227d48a
Doc Type: No Doc Update
Doc Text:
Clone Of: 2225471
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-163713 0 None None None 2023-07-27 18:22:09 UTC

Description Josh Stone 2023-07-27 18:20:42 UTC
Cloning to el8 for bugfix parity.

+++ This bug was initially created as a clone of Bug #2225471 +++

Description of problem:

389-ds-base-2.3.4-2.el9 and 2.3.4-3.el9 both FTBFS with rust-1.71.0.

error: using `.borrow()` on a double reference, which returns `&concread::cowcell::CowCellReadTxn<CacheStats>` instead of borrowing the inner t
ype
  --> librslapd/src/cache.rs:60:28
   |
60 |     let stats = stat_rguard.borrow();
   |                            ^^^^^^^^^
   |
note: the lint level is defined here
  --> librslapd/src/lib.rs:1:9
   |
1  | #![deny(warnings)]
   |         ^^^^^^^^
   = note: `#[deny(suspicious_double_ref_op)]` implied by `#[deny(warnings)]`
error: could not compile `librslapd` (lib) due to previous error

This is rust issue https://github.com/rust-lang/rust/issues/112489

--- Additional comment from Josh Stone on 2023-07-25 08:55:48 PDT ---

I do not recommend deny(warnings) in production builds, since we rebase frequently and there may always be new warnings -- whether or not they are false positives.

Still, I can see about backporting the upstream fix for this.


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