enclave-agent build error. about enclave-cc HOT 8 CLOSED

Yea, the problems here is very funny. It seems that the definition of base64 dependency of sequoia-openpgp causes this.

• base64 crate abondoned decode_config_slice and some other apis (or change the directory) from ver 0.13.0 to ver 0.20.0 one day ago.
• sequoia-openpgp asks for a base64 version >= 0.12 here but use base64's <=0.13.0 apis.
• When image-rs is being built, a base64 0.20.0 and sequoia-openpgp 1.11.0 who leverages base64's 0.13.0 api is involved

The core problem is that base64 crate was published (1 day ago) with API changed but without modification of major version number.

• A temporary way is to fix base64 version in image-rs
• A better but future way is wait sequoia-openpgp to use a fixed version of base64

@jiere @hairongchen

from enclave-cc.

Related issue for sequoia-pgp https://gitlab.com/sequoia-pgp/sequoia/-/issues/961

from enclave-cc.

this crate is used in image-rs
@Xynnn007 @arronwy

from enclave-cc.

base info:
hrc@cre-M50CYP2SBSTD:/tmp/image-rs$ cargo tree |grep sequoia-openpgp
├── sequoia-openpgp v1.11.0

hrc@cre-M50CYP2SBSTD:/tmp/image-rs$ cargo tree |grep base6
│ ├── base64 v0.13.1
│ │ │ │ └── base64ct v1.5.3
│ │ │ │ │ ├── base64ct v1.5.3
├── base64 v0.13.1
│ │ ├── base64 v0.13.1
│ │ ├── base64 v0.13.1
│ ├── base64 v0.13.1
│ ├── base64-serde v0.6.1
│ │ ├── base64 v0.13.1
│ │ ├── base64 v0.13.1
│ ├── base64 v0.13.1
│ ├── base64 v0.20.0
│ │ │ ├── base64 v0.13.1
│ ├── base64 v0.13.1
│ │ ├── base64 v0.13.1
│ │ │ ├── base64 v0.13.1
│ │ └── base64 v0.13.1
│ │ ├── base64 v0.13.1
│ │ │ ├── base64 v0.13.1
│ ├── base64 v0.13.1
│ ├── base64 v0.13.1

from enclave-cc.

CI logs show in here and here

from enclave-cc.

• A better but future way is wait sequoia-openpgp to use a fixed version of base64

Thanks so much for your quick finding, @Xynnn007.
sequoia-openpgp seems to be a Gitlab project, who has account could help raise an issue there?
Anyway, for us, I think the first way makes sense.

from enclave-cc.

sequoia-openpgp seems to be a Gitlab project, who has account could help raise an issue there?

Yea, I'd like to open an issue there. Before this, I found it a little problematic to fix this in image-rs. I will open an PR in enclave-cc to fix this first.

from enclave-cc.

FYI, https://gitlab.com/sequoia-pgp/sequoia/-/issues/961 now is fixed. We can update Cargo.lock when it is needed.

from enclave-cc.