RE: scarthgap: mbedtls: Fetcher failure: Conflicting revisions
"Marko, Peter" <[email protected]>
| Newsgroups | org.yoctoproject.lists.yocto |
|---|---|
| Message-ID | <AS1PR10MB569757B1132207A209188AF2FD34A@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM> |
Patch for this is already available https://lists.openembedded.org/g/openembedded-devel/message/118954 However it will take maybe a month to apply with current cadence. Meanwhile either don't update or add a bbappend to your layer to fix it. Peter > -----Original Message----- > From: [email protected] <[email protected]> On Behalf Of > Matthias Klein via lists.yoctoproject.org > Sent: Friday, August 15, 2025 10:00 > To: Yocto-mailing-list <[email protected]> > Subject: [yocto] scarthgap: mbedtls: Fetcher failure: Conflicting revisions > > Hello everyone, > > since yesterday evening, all of our Yocto builds have been failing with the > following message: > > Loading cache: 100% | > | ETA: --:--:-- > Loaded 0 entries from dependency cache. > WARNING: .../yocto/meta-openembedded/meta-networking/recipes- > connectivity/mbedtls/mbedtls_3.6.4.bb: Exception during build_dependencies for > fetcher_hashes_dummyfunc | > ETA: 0:00:10 > WARNING: .../yocto/meta-openembedded/meta-networking/recipes- > connectivity/mbedtls/mbedtls_3.6.4.bb: Error during finalise of .../yocto/meta- > openembedded/meta-networking/recipes-connectivity/mbedtls/mbedtls_3.6.4.bb > ERROR: ExpansionError during parsing .../yocto/meta-openembedded/meta- > networking/recipes-connectivity/mbedtls/mbedtls_3.6.4.bb > bb.data_smart.ExpansionError: Failure expanding variable > fetcher_hashes_dummyfunc[vardepvalue], expression was > ${@bb.fetch.get_hashvalue(d)} which triggered exception FetchError: Fetcher > failure: Conflicting revisions (c765c831e5c2a0971410692f92f7a81d6ec65ec2 from > SRCREV and v3.6.4 from the url) found, please specify one valid value > The variable dependency chain for the failure is: > fetcher_hashes_dummyfunc[vardepvalue] > > (I replaced the absolute paths in the output with three dots.) > > > Does anyone have any idea what the cause might be? > > Best regards, > Matthias