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 0001594]: Portage bump, sandbox fix
Date: Fri, 16 Nov 2007 04:48:54 -0800	[thread overview]
Message-ID: <2138d78b98ca7df4f1c0b3cdc3e9fe1c@busybox.net> (raw)


The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=1594 
====================================================================== 
Reported By:                aron
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1594
Category:                   Other
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             11-16-2007 03:01 PST
Last Modified:              11-16-2007 04:48 PST
====================================================================== 
Summary:                    Portage bump, sandbox fix
Description: 
This patch bumps portage and makes buildroot use a standard gentoo mirror
for sandbox. 
====================================================================== 

---------------------------------------------------------------------- 
 aron - 11-16-07 03:23  
---------------------------------------------------------------------- 
For some reason, the .19 patch fails now. Taking the easy route going for
.9 instead. This make portage build fine. 
Hence don't bother with the first patch, only use the second one. 

---------------------------------------------------------------------- 
 vanokuten - 11-16-07 04:48  
---------------------------------------------------------------------- 
fixed in 20436 rev 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-16-07 03:01  aron           New Issue                                    
11-16-07 03:01  aron           Status                   new => assigned     
11-16-07 03:01  aron           Assigned To               => buildroot       
11-16-07 03:01  aron           File Added: portage_sandbox.patch                
   
11-16-07 03:01  aron           Issue Monitored: aron                        
11-16-07 03:21  aron           File Added: portage_sandbox_2.patch              
     
11-16-07 03:23  aron           Note Added: 0002936                          
11-16-07 04:48  vanokuten      Status                   assigned => closed  
11-16-07 04:48  vanokuten      Note Added: 0002937                          
======================================================================

             reply	other threads:[~2007-11-16 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 12:48 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-16 11:23 [Buildroot] [buildroot 0001594]: Portage bump, sandbox fix bugs at busybox.net
2007-11-16 11:01 bugs 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=2138d78b98ca7df4f1c0b3cdc3e9fe1c@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