Thanks for the extension (checking for ewarn & eerror). I'm
still getting a handle on gentoo ;-)
I borrowed a portage.cron script from off of this list and run
it under cron.daily. One of my changes to the script is to run
einfo (I also pull down the files so they are ready for compile
after I r
Here's a perl script to display the einfo lines of packages to
be merged. Just run it with the same options you will use for
emerge. Example:
einfo -uDN world >einfo.txt
emerge -uDN world
less einfo.txt
You will probably want to save the output to refer to after
emerging.
Enjoy,
Roy
#!/
On Fri, 2005-07-08 at 15:38 +0800, W.Kenworthy wrote:
> This is one reason you should not do auto-updates via cron. It adds to
> the fun in tracking down such problems.
It wasn't cron. I did the emerge prior to heading off to bed.
Perhaps a good thing would be when the emerge -uDpv world output
This is one reason you should not do auto-updates via cron. It adds to
the fun in tracking down such problems.
I also wish that emerges would stop whenever a message like this is
printed to the screen, but people have been cursing/moaning and getting
caught with dead systems by this bug for lit
Ow Mun Heng wrote:
>
> It didn't catch everything. Right now I'm recompiling xscreensaver.
>
revdep-rebuild didn't catch everything? Do we know why? I wouldn't want that
to happen to me ;-).
> The thing which I'm talking about is, if there are _specific_ caveats
> such as with this new app,
[Changed Subject. , should be com_err and not ss]
On Thu, 2005-07-07 at 23:04 -0700, Zac Medico wrote:
> Ow Mun Heng wrote:
> > If you guys did a emerge -uDav world anytime these past few days. I'm
> > sure you'll be hit by the libcom_err.so.3 error.
> >
> > This was really bad. Ruined half my w
6 matches
Mail list logo
