You might want to try to bisect poky? If there’s any fix, it needs to be
justified with something else than ‘unbreaks passwords in recipes’.
Alex
On Wed 22. May 2024 at 8.15, Lukas Weiß via Lists.Yoctoproject.Org
wrote:
> You are definitely right, we should switch to another auth mechanism.
We don't use wget2, at least it's not installed on the host. Also, we don't use
Fedora, but Debian 12.5 and Ubuntu 22.04.4 hosts.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63163): https://lists.yoctoproject.org/g/yocto/message/63163
Mute This
You are definitely right, we should switch to another auth mechanism. It's not
that easy, as build shall work in CI on our Build-Server - haven't found a good
"best practice" here yet.
But why did it work 2 weeks ago (even on Yocto-5.0) and still does for other
git-commands than ls-remote?
Looks like you are using wget2 fetcher instead of old good wget?!
Which distro on the host are you using? Fedora? Or something else?
Please, start reading from here!
https://lists.yoctoproject.org/g/yocto/message/63118
Zee
___
On Tue, May 21, 2024 at 3:38 PM Lukas Weiß via
Supplying passwords this way is a terrible idea, and isn't supported
(there's a comment in git fetcher source stating that explicitly). You
should transition everything to ssh (at which point the issue will go
away anyway), or place the https secrets into a more secure location
(man gitcredentials
Hello there,
i just updated our Yocto Project to latest 5.0 release. First tests went well,
but now after a subsequent repo-update (tag=yocto-5.0) i have problems with
call of most bitbake calls because of an error in some recipes with code in our
own repository: Clean build runs without
