From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13616] New: tar file from git repository generation issue
Date: Mon, 15 Mar 2021 10:36:01 +0000 [thread overview]
Message-ID: <bug-13616-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13616
Bug ID: 13616
Summary: tar file from git repository generation issue
Product: buildroot
Version: 2020.02.8
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jpcartal at free.fr
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 8791
--> https://bugs.busybox.net/attachment.cgi?id=8791&action=edit
Master branch patch
Hello,
The support/download/git script is generating tar files from git repositories
using the following command :
# Create GNU-format tarballs, since that's the format of the tarballs on
# sources.buildroot.org and used in the *.hash files
tar cf - --transform="s#^\./#${basename}/#" \
--numeric-owner --owner=0 --group=0 --mtime="${date}" --format=gnu \
-T "${output}.list.sorted" >"${output}.tar"
In one of our repository, the --transform option is generating unusable tar
files because of the bug described here :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775247
Links with the following pattern src/foo -> ./foo_bar/bar are replaced with
src/foo -> ${basename}/foo_bar/bar and thus the generated tarball is not
usable.
As explained in the debian bug report, adding the S flag to the transform
pattern (i.e. --transform="s#^\./#${basename}/#" =>
--transform="s#^\./#${basename}/#S") solves this issue.
Attaching the corresponding patches for master and 2020.02.x branches
Regards.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-15 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 10:36 bugzilla at busybox.net [this message]
2021-03-15 10:36 ` [Buildroot] [Bug 13616] tar file from git repository generation issue bugzilla at busybox.net
2021-03-15 10:41 ` bugzilla at busybox.net
2021-03-15 15:41 ` bugzilla at busybox.net
2021-03-15 21:07 ` bugzilla at busybox.net
2021-03-16 9:42 ` bugzilla at busybox.net
2021-03-24 12:37 ` bugzilla at busybox.net
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=bug-13616-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.