Hi Bruce, On 11/1/24 10:13 PM, Bruce Ashfield wrote:
On Thu, Oct 31, 2024 at 4:44 PM Bruce Ashfield via lists.yoctoproject.org <http://lists.yoctoproject.org> <[email protected] <mailto:[email protected]>> wrote: On Thu, Oct 31, 2024 at 11:02 AM Bruce Ashfield via lists.yoctoproject.org <http://lists.yoctoproject.org> <[email protected] <mailto:[email protected]>> wrote: On Thu, Oct 31, 2024 at 9:26 AM Javier Tia <[email protected] <mailto:[email protected]>> wrote: Hi Bruce, On 10/30/24 9:37 PM, Bruce Ashfield wrote: > On Wed, Oct 30, 2024 at 8:38 PM Javier Tia via lists.yoctoproject.org <http://lists.yoctoproject.org> <http://lists.yoctoproject.org <http://lists.yoctoproject.org>> <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> wrote: > > upx recipe fails with: > > ERROR: upx-4.2.4+git-r0 do_fetch: Fetcher failure: Unable to find revision 5221596a608acbc8efed1e54f758bab1908ce7a8 in branch even from upstream > ERROR: upx-4.2.4+git-r0 do_fetch: gitsm: submodule download failed: FetchError Fetcher failure for URL: 'gitsm://github.com/upx/upx-vendor-valgrind.git;protocol=https;name=vendor/valgrind;subpath=vendor/valgrind;nobranch=1;lfs=True;bareclone=1;nobranch=1 <http://github.com/upx/upx-vendor-valgrind.git;protocol=https;name=vendor/valgrind;subpath=vendor/valgrind;nobranch=1;lfs=True;bareclone=1;nobranch=1> <http://github.com/upx/upx-vendor-valgrind.git;protocol=https;name=vendor/valgrind;subpath=vendor/valgrind;nobranch=1;lfs=True;bareclone=1;nobranch=1 <http://github.com/upx/upx-vendor-valgrind.git;protocol=https;name=vendor/valgrind;subpath=vendor/valgrind;nobranch=1;lfs=True;bareclone=1;nobranch=1>>'. Unable to fetch URL from any source. > > Likely, upstream rewrote the Git history. > > > I'll wait until I can reproduce this one myself: > > bitbake -c cleanall upx; bitbake upx > > I can also clone upx, reset it to the revision I'm currently using in meta-virt and do a git submodule init without issues. > > Just worked fine here. Were you doing anything different than a regular build when you hit it ? No, I am aware of it. For me, is easy to reproduce. Clone poky master, add meta-virtualization layer, add virtualization to DISTRO_FEATURES, change MACHINE to 'genericarm64' and `bitbake upx -c cleanall && bitbake upx` will do it. Exactly the same thing works fine for me. I'll continue to debug it here. I'll likely just update upx to tip, but until I see the failure in my builds, I can't be sure I've fixed anything! It looks like I was being fed a cached repository from a mirror. When I switched configurations (I switched builders), I can see it now. Although, I have no idea why my manual clones were working, since they don't use that infrastructure. I'm going to debug that a bit more. I'll get this fixed on Friday (assuming I satisfy my manual clone curiosity). I went a different way with this. I've had "issues" with this git repository in the past (failing fetcher tests, etc) I've already done one switch from gitsm to individual git fetches and then back to gitsm. I've gone back to individual fetches, since I tested the tip of the tree and it is still broken with gitsm fetching. This worked on all my builders, let me know if you still see issues.
No issues so far. Thank you! » Javier Tia 🖋
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8956): https://lists.yoctoproject.org/g/meta-virtualization/message/8956 Mute This Topic: https://lists.yoctoproject.org/mt/109307127/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
