[SOLVED]Old emerge output prepended to emerge world

Havin_it · Last edited by Havin_it on Mon Jul 08, 2013 1:00 am; edited 1 time in total

Hi,

This is an odd one. I had an emerge -uD --keep-going world running while my daily cron job kicked in (which is basically emerge --sync && emerge -uDp world && emerge -uDf world). I wouldn't normally allow this to happen, but I took my eye off the ball this time.

Since then, whenever I run emerge -u[anything] world, the output starts by spitting out the eerror lines from a failed build that happened around the time of the incident. It doesn't affect the ability to run the commands, but it is rather unsightly.

Could anyone advise where this output might be coming from, and how I can get rid of it? Thanks in advance!

dol-sen · Posted: Sun Jul 07, 2013 6:30 pm Post subject:

Well, we would have to see what it is that you are getting, along with any error messages.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

Havin_it · Posted: Mon Jul 08, 2013 12:49 am Post subject:

Gah, just as you ask, I now find it's stopped doing it :evil:

FWIW, as far as I remember it was a failure of tigervnc-1.2.0 (an out-of-tree version I had in place before it came in-tree) due to an EAPI mismatch. All the type of output you get on the end of a failed emerge, red stars and all.

Perhaps I'd done something odd to the shell I had open. Unless it recurs we may never know...