From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4369] New: Fix permissions on untared lsof archive
Date: Sat, 22 Oct 2011 03:47:26 +0000 (UTC) [thread overview]
Message-ID: <bug-4369-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4369
Summary: Fix permissions on untared lsof archive
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: d_mo1234 at yahoo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 3667
--> https://bugs.busybox.net/attachment.cgi?id=3667
patch file
When buildroot untars a package, it opens permissions on the untarred results,
(The comment is "some packages have messed up permissions inside".) However,
in the case of lsof, the tar.bz2 contains another .tar, which contains the
source code. It needs to have the same treatment as buildroot's normal untar
process, because lsof has read-only files in the inner tarball.
A patch file is attached.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-10-22 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 3:47 bugzilla at busybox.net [this message]
2011-10-22 22:49 ` [Buildroot] [Bug 4369] Fix permissions on untared lsof archive bugzilla at busybox.net
2011-10-22 23:10 ` bugzilla at busybox.net
2011-10-22 23:10 ` bugzilla at busybox.net
2011-11-24 22:13 ` 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-4369-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox