public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev]  Re: %n in writable segment detected ??
Date: Sat, 14 Mar 2009 23:05:41 -0600	[thread overview]
Message-ID: <20090314230541.4de94192@halo.dirtyepic.sk.ca> (raw)
In-Reply-To: pan.2009.03.14.16.53.52@cox.net

[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]

On Sat, 14 Mar 2009 16:53:52 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:

> What's the below "%n in writable segment detected" bit all about?
> Should I worry about it?  I saw it once before but have no clue
> whether it's portage/emerge itself outputting it (I would guess yes,
> QA warning??), or one of the build processes.
> 
> I'm guessing it's a warning from portage's newer parallel jobs
> processing that you guys may be interested in (a bug to trace down?
> file it??  any other info beyond the below that would be useful?  how
> to duplicate? etc.) but don't know and obviously haven't the foggiest
> how serious it is.  But it didn't cause anything to barf, so I
> figured it couldn't be too bad.  But it's still worrying not knowing
> what it is, when it's obviously important enough to break the
> parallel jobs enforced backgrounding.
> 
> ~amd64/2008.0/no-multilib, portage-2.2_rc25 (now, previously with a 
> different _rc)
> 
> Would you like to merge these packages? [Yes/No]
> >>> Verifying ebuild manifests
> >>> Starting parallel fetch
> >>> Emerging (1 of 5) sys-devel/gnuconfig-20090203
> >>> Emerging (2 of 5) sys-apps/sandbox-1.6
> >>> Installing sys-devel/gnuconfig-20090203
> >>> Installing sys-apps/sandbox-1.6
> >>> Emerging (3 of 5) sys-fs/udev-140
> >>> Emerging (4 of 5) sys-apps/coreutils-7.1
> >>> Jobs: 2 of 5 complete, 1 running                Load avg: 4.81,
> >>> 3.95, 
> 2.11*** %n in writable segment detected ***
> 
> Thanks!

http://bugs.gentoo.org/show_bug.cgi?id=257279

-- 
gcc-porting,
http://bugs.gentoo.org/show_bug.cgi?id=257279
by design, by neglect treecleaner,                              for a
fact or just for effect wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD
C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-03-15  5:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 16:53 [gentoo-portage-dev] %n in writable segment detected ?? Duncan
2009-03-14 17:11 ` [gentoo-portage-dev] " Duncan
2009-03-14 17:58 ` [gentoo-portage-dev] " Mike Frysinger
2009-03-15  5:05 ` Ryan Hill [this message]
2009-03-15  7:52   ` [gentoo-portage-dev] " Duncan

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=20090314230541.4de94192@halo.dirtyepic.sk.ca \
    --to=dirtyepic@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /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