From: "Yi Qingliang" <niqingliang2003@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/1] fetch2/git: Use basename for gitsrcname when ud.proto is file
Date: Mon, 12 May 2025 17:41:45 -0700 [thread overview]
Message-ID: <13242.1747096905485013812@lists.openembedded.org> (raw)
In-Reply-To: <d743138a1b56d1f31f81d837a1136013737cde03.camel@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1355 bytes --]
upload my glic recipe as attachement.
my download directory is "/mnt/datum/downloads/".
premirror of glibc is: /mnt/datum/repositories/sourceware.org/git/glibc.git
the file system structure generated by bitbake in download is:
lrwxrwxrwx 1 ll ll 120 May 7 17:04 /mnt/datum/downloads/git2/sourceware.org.git.glibc.git -> /mnt/datum/downloads/gitshallow_mnt.datum.repositories.sourceware.org.git.glibc.git_0557361-1_release.2.17.master.tar.gz
-rw-r--r-- 1 ll ll 6 May 7 17:04 /mnt/datum/downloads/git2/sourceware.org.git.glibc.git.done
-rw-r--r-- 1 ll ll 0 May 7 17:09 /mnt/datum/downloads/git2/sourceware.org.git.glibc.git.lock
-rw-r--r-- 1 ll ll 24413461 May 7 17:04 /mnt/datum/downloads/gitshallow_mnt.datum.repositories.sourceware.org.git.glibc.git_0557361-1_release.2.17.master.tar.gz
-rw-r--r-- 1 ll ll 0 May 7 17:04 /mnt/datum/downloads/gitshallow_mnt.datum.repositories.sourceware.org.git.glibc.git_0557361-1_release.2.17.master.tar.gz.done
when unpacking, the bitbake expect a bare repo at /mnt/datum/downloads/git2/sourceware.org.git.glibc.git, but indeed, it is a symbollink to gitshallow file.
and then bitbake expect a git shallow file with name "gitshallow_sourceware.org.git.glibc.git_0557361-1_release.2.17.master.tar.gz", also no luck.
so bitbake report error finally.
[-- Attachment #1.2: Type: text/html, Size: 1575 bytes --]
[-- Attachment #2: glibc.tar.gz --]
[-- Type: application/gzip, Size: 78122 bytes --]
next prev parent reply other threads:[~2025-05-13 0:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 5:20 [PATCH 0/1] fetch2/git: Use basename for gitsrcname when ud.proto is file liezhi.yang
2024-06-22 5:20 ` [PATCH 1/1] " liezhi.yang
2024-07-14 11:17 ` [bitbake-devel] " Richard Purdie
2024-07-14 13:03 ` Robert Yang
2024-07-14 13:32 ` Richard Purdie
2024-07-14 13:54 ` Robert Yang
2024-08-06 11:06 ` Richard Purdie
2024-08-06 11:20 ` Ross Burton
2024-08-06 13:42 ` Robert Yang
2024-08-06 14:10 ` Richard Purdie
2024-08-07 2:23 ` Robert Yang
2024-08-07 14:58 ` Richard Purdie
[not found] ` <17E927848AD479BA.28314@lists.openembedded.org>
2024-08-06 13:50 ` Robert Yang
2024-07-14 11:08 ` [bitbake-devel] [PATCH 0/1] " Robert Yang
2025-05-12 9:26 ` Yi Qingliang
2025-05-12 11:20 ` [bitbake-devel] " Koch, Stefan
2025-05-13 0:41 ` Yi Qingliang [this message]
2025-05-13 0:48 ` Yi Qingliang
2025-05-13 1:02 ` Yi Qingliang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13242.1747096905485013812@lists.openembedded.org \
--to=niqingliang2003@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.