All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9826] post-build scritp - symlinks created in post-build script are overwritten after exit of the script
Date: Thu, 20 Apr 2017 21:37:55 +0000	[thread overview]
Message-ID: <bug-9826-163-kxG6znXoUt@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9826-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9826

Timo V?lim?ki <timo.valimaki@sensoan.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #2 from Timo V?lim?ki <timo.valimaki@sensoan.com> ---
Thanks.

I have totally missed the fakeroot script - perhaps I have just skipped it as
didn't understood when to use it.

I moved /etc/group, /etc/passwd and /etc/shadow handling from post-build script
to fakeroot script.  Result: works as it should be.

I mark bug resolved as invalid.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2017-04-20 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20  9:35 [Buildroot] [Bug 9826] New: post-build scritp - symlinks created in post-build script are overwritten after exit of the script bugzilla at busybox.net
2017-04-20 20:15 ` [Buildroot] [Bug 9826] " bugzilla at busybox.net
2017-04-20 21:37 ` bugzilla at busybox.net [this message]

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-9826-163-kxG6znXoUt@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.