Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000926]: lvm2 fails to install (DESTDIR issues)
Date: Mon, 12 Feb 2007 05:43:36 -0800	[thread overview]
Message-ID: <900aaaa00a1bed7110fac319780b223d@bugs.busybox.net> (raw)


The following issue has been ASSIGNED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=926 
====================================================================== 
Reported By:                redhatter
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   926
Category:                   Other
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             06-27-2006 03:59 PDT
Last Modified:              02-12-2007 05:43 PST
====================================================================== 
Summary:                    lvm2 fails to install (DESTDIR issues)
Description: 
When running the `make install` stage of the LVM2 build, the install
scripts attempt to write to /etc/lvm (instead of
/path/to/staging_dir/etc/lvm), yeilding a "permission denied" when run as
a non-root user.  The supplied patch fixes this issue.
====================================================================== 

---------------------------------------------------------------------- 
 redhatter - 06-27-06 04:01  
---------------------------------------------------------------------- 
Hrmm, this seems to have wound up in the uClibc bug list... (I *swear* I
clicked Busybox)... if it's out of place, I appologise. 

---------------------------------------------------------------------- 
 bernhardf - 12-21-06 03:57  
---------------------------------------------------------------------- 
Fixed in r17026. Thanks! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-27-06 03:59  redhatter      New Issue                                    
06-27-06 03:59  redhatter      Status                   new => assigned     
06-27-06 03:59  redhatter      Assigned To               => uClibc          
06-27-06 04:00  redhatter      File Added: buildroot-lvm2-fix.diff              
     
06-27-06 04:01  redhatter      Note Added: 0001458                          
12-21-06 03:57  bernhardf      Status                   assigned => closed  
12-21-06 03:57  bernhardf      Note Added: 0001902                          
12-21-06 03:57  bernhardf      Resolution               open => fixed       
02-12-07 05:43  vapier         Status                   closed => assigned  
02-12-07 05:43  vapier         Assigned To              uClibc => buildroot 
======================================================================

                 reply	other threads:[~2007-02-12 13:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=900aaaa00a1bed7110fac319780b223d@bugs.busybox.net \
    --to=bugs@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