TC-2279 has_sbom: subject artifact management #79
TC-2279 has_sbom: subject artifact management #79mrizzi merged 2 commits intotrustification:mainfrom
Conversation
@helio-frota wouldn't the update of this project's toolchain cause issues when building trustification due to https://github.com/trustification/trustification/blob/3bddbdbd25f7444e3d25aa063dc625e6729d8d30/rust-toolchain.toml#L2? @dejanb WDYT? |
|
@mrizzi I'm not sure, something to test 👍 what I know is that something may happen with trustification at some point like happened with your PR 👍 I'll build using guac-rs from github to see what happens |
|
Apparently this PR #78 is not working anymore or I have issues with my cargo setup something insists to keep these versions: Causing build errors: apparently related to async-nats, that is declared as [workspace.dependencies]
anyhow = "1.0.39"
async-nats = "0.39"and the Cargo.lock shows some other async-nats dependencies: I'll uninstall rust and try again |
|
no problem with my setup, after uninstalling rust the error continues, |
|
we are having a cyclic dependency issue that got worst overtime, (since the PR worked (past year)) : ➜ guac-rs git:(updates) ✗ cargo tree --depth 3 | rg "async\-nats" -B 10
guac v0.7.2-0 (/home/heliofrota/Desktop/tc/guac-rs/lib)
├── anyhow v1.0.97
├── async-nats v0.39.0
--
│ │ ├── log v0.4.26 (*)
│ │ └── regex v1.11.1 (*)
│ ├── humantime v2.1.0
│ └── log v0.4.26 (*)
├── exporter v0.1.0 (https://github.com/trustification/trustification.git?tag=v0.1.0-nightly.9382a428#9382a428) < ------
│ ├── anyhow v1.0.97
│ ├── clap v4.5.31 (*)
│ ├── futures v0.3.31 (*)
│ ├── guac v0.1.0 (https://github.com/trustification/guac-rs.git?rev=5b8cad8342d42072a72ef4a149348d0d86a84176#5b8cad83)
│ │ ├── anyhow v1.0.97
│ │ ├── async-nats v0.29.0 < ------➜ guac-rs git:(updates) ✗ cargo tree --depth 3 | rg "nuid" -B 20
├── async-nats v0.39.0 < -----
│ ├── base64 v0.22.1
│ ├── bytes v1.10.0
│ │ └── serde v1.0.218
│ ├── futures v0.3.31
│ │ ├── futures-channel v0.3.31
│ │ ├── futures-core v0.3.31
│ │ ├── futures-executor v0.3.31
│ │ ├── futures-io v0.3.31
│ │ ├── futures-sink v0.3.31
│ │ ├── futures-task v0.3.31
│ │ └── futures-util v0.3.31
│ ├── memchr v2.7.4
│ ├── nkeys v0.4.4
│ │ ├── data-encoding v2.8.0
│ │ ├── ed25519 v2.2.3
│ │ ├── ed25519-dalek v2.1.1
│ │ ├── log v0.4.26
│ │ ├── rand v0.8.5
│ │ └── signatory v0.27.1
│ ├── nuid v0.5.0 < -------------same error downgrading async-nats... -async-nats = "0.38"
+async-nats = "0.29" |
|
and the ➜ guac-rs git:(main) cargo build
Updating crates.io index
Downloaded graphql_client v0.14.0
Downloaded prost v0.12.6
Downloaded graphql_query_derive v0.14.0
Downloaded tonic-build v0.11.0
Downloaded prost-derive v0.12.6
Downloaded prost-types v0.12.6
Downloaded prost-build v0.12.6
Downloaded graphql_client_codegen v0.14.0
Downloaded tonic v0.11.0
Downloaded rustls v0.22.4
Downloaded async-nats v0.35.1
Downloaded tokio-rustls v0.25.0
Downloaded 12 crates (1.1 MB) in 0.98s
error: package `zerofrom v0.1.6` cannot be built because it requires rustc 1.81 or newer, while the currently active rustc version is 1.77.2
Either upgrade to rustc 1.81 or newer, or use
cargo update zerofrom@0.1.6 --precise ver
where `ver` is the latest version of `zerofrom` supporting rustc 1.77.2 |
|
we need to update to rust 1.81.0 as MSRV 👍 #81 |
|
@helio-frota How do we know that circular dependency is the cause of the issue? For me locally it also builds without any issues If it is, maybe we should try to fix that. I'm also a bit wary of upgrading rust as it may affect the rest of the stack |
|
@dejanb now I see a different (when comparing with CI) error asking for rust 1.80.0.. but we already know CI will break if not using 1.81 we can reproduce with: edit: same error #79 (comment) |
|
@helio-frota Thanks I think we should remove dependency to I would move the whole code from We should coordinate rust version upgrade with trustification in a separate effort. |
Signed-off-by: mrizzi <mrizzi@redhat.com>
Signed-off-by: mrizzi <mrizzi@redhat.com>
https://issues.redhat.com/browse/TC-2279