public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/flameeyes-tinderbox:master commit in: /
Date: Sun,  7 Aug 2011 12:23:30 +0000 (UTC)	[thread overview]
Message-ID: <c04393b04a46f8d658be1128fdd67d9888d8f5ba.flameeyes@gentoo> (raw)

commit:     c04393b04a46f8d658be1128fdd67d9888d8f5ba
Author:     Diego Elio Pettenò <flameeyes <AT> gmail <DOT> com>
AuthorDate: Sun Aug  7 12:22:27 2011 +0000
Commit:     Diego Elio Pettenò <flameeyes <AT> gentoo <DOT> org>
CommitDate: Sun Aug  7 12:22:27 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/flameeyes-tinderbox.git;a=commit;h=c04393b0

Save to file the list of unsatisfied USE dependencies.

When running non-interactively this output would be unreachable, so save it
to file to actually read it out separately.

---
 tinderbox-restart.sh |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/tinderbox-restart.sh b/tinderbox-restart.sh
index 5a1a8c8..2f96d7d 100755
--- a/tinderbox-restart.sh
+++ b/tinderbox-restart.sh
@@ -112,7 +112,7 @@ reset_emergelog
 # Generate a new complete list, this will also produce the list of new
 # dependencies to satisfy. Ignore new-style virtuals, leave them to be
 # merged out of dependencies.
-${tboxdir}/tinderbox.py | egrep -v '^virtual/' > /var/cache/tinderbox/list-complete
+${tboxdir}/tinderbox.py 2> /var/cache/tinderbox/use-conflicts | egrep -v '^virtual/' > /var/cache/tinderbox/list-complete
 
 # Launch the fetch operation in background, saving the log (of both
 # good results and failures).



             reply	other threads:[~2011-08-07 12:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07 12:23 Diego Elio Pettenò [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-05 13:42 [gentoo-commits] proj/flameeyes-tinderbox:master commit in: / Diego Elio Pettenò
2013-02-19 20:39 Diego Elio Pettenò
2013-01-26 14:49 Diego Elio Pettenò
2013-01-26  1:15 Diego Elio Pettenò
2013-01-26  0:23 Diego Elio Pettenò
2013-01-26  0:23 Diego Elio Pettenò
2013-01-26  0:23 Diego Elio Pettenò
2012-11-01 18:51 Diego Elio Pettenò
2012-11-01 16:54 Diego Elio Pettenò
2012-07-15 10:31 Diego Elio Pettenò
2012-07-15 10:28 Diego Elio Pettenò
2012-06-22 19:49 Diego Elio Pettenò
2012-06-22 19:49 Diego Elio Pettenò
2012-06-22 19:46 Diego Elio Pettenò
2012-06-21 10:48 Diego Elio Pettenò
2012-06-19 18:59 Diego Elio Pettenò
2012-06-16 14:57 Diego Elio Pettenò
2012-06-16 14:51 Diego Elio Pettenò
2012-06-16 14:48 Diego Elio Pettenò
2012-06-16 14:45 Diego Elio Pettenò
2012-06-16 14:39 Diego Elio Pettenò
2012-06-16 14:39 Diego Elio Pettenò
2012-06-15 15:09 Diego Elio Pettenò
2012-06-15 15:09 Diego Elio Pettenò
2012-06-15 15:09 Diego Elio Pettenò
2012-05-18 16:03 Diego Elio Pettenò
2012-05-18 15:56 Diego Elio Pettenò
2012-05-18 15:56 Diego Elio Pettenò
2012-05-18 15:56 Diego Elio Pettenò
2012-05-18  4:32 Diego Elio Pettenò
2012-05-18  4:07 Diego Elio Pettenò
2012-05-18  4:07 Diego Elio Pettenò
2011-05-28  9:09 Diego Elio Pettenò
2011-05-03 14:54 Diego Elio Pettenò
2011-05-03 14:54 Diego Elio Pettenò
2011-04-13 12:50 Diego Elio Pettenò
2011-03-22 17:09 Jeremy Olexa

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=c04393b04a46f8d658be1128fdd67d9888d8f5ba.flameeyes@gentoo \
    --to=flameeyes@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-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