Re: [gentoo-user] Heads-Up sys-lib/ss breaks Apps
On Fri, 2005-07-08 at 21:56 -0400, Allan Gottlieb wrote: At Fri, 08 Jul 2005 12:47:51 -0500 kashani [EMAIL PROTECTED] wrote: Ron Bickers wrote: On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: Which is a huge bummer since most of us don't go checking the ebuilds for these specific lines. How I wish It would just abort and BLAST the Einfo on the screen for me to see the next day and decide to do it manually. . It would be nice to at least have these messages logged somewhere. Are they? Can they be without patching portage? mkdir /var/log/portage echo PORT_LOGDIR=/var/log/portage /etc/make.conf Although I didn't check this particular case, it is normally true that emerge generates *two* logs in the directory for each build. The large one contains the normal stuff (e.g., compiler output); the small one contains the important tidbits such as those mentioned above. Yes.. I have this set-up as well, however the caveat here is that this will be _after_ the fact. Hence, to me, it's largely useless. Roy Wright has written a nice util which does do nice things, essentially just grepping the ebuild files for einfo lines and putting it onto the screen. nice. -- Ow Mun Heng Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM 98% Microsoft(tm) Free!! Neuromancer 09:41:41 up 2 days, 17:38, 2 users, load average: 0.29, 0.55, 0.57 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Heads-Up sys-lib/ss breaks Apps
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 working day since I can't get Evo to come up. Anyway, the ebuild _does_ mentioned breaking compatibility and stuffs. $grep einfo /usr/portage/sys-libs/com_err/*.ebuild einfo PLEASE PLEASE take note of this einfo Please make *sure* to run revdep-rebuild now einfo Certain things on your system may have linked against a einfo different version of com_err -- those things need to be einfo recompiled. Sorry for the inconvenience Which is a huge bummer since most of us don't go checking the ebuilds for these specific lines. How I wish It would just abort and BLAST the Einfo on the screen for me to see the next day and decide to do it manually. Oh well... It's fixed. Shouldn't revdep-rebuild solve issues like that? I always run revdep-rebuild after updates and I don't recall having any problem with this com_err update ( I know lots of others did though :-( ). Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Heads-Up sys-lib/ss breaks Apps
On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: Which is a huge bummer since most of us don't go checking the ebuilds for these specific lines. How I wish It would just abort and BLAST the Einfo on the screen for me to see the next day and decide to do it manually. I have this concern as well. Also, when emerging multiple packages, the helpful and sometimes necessary output at the end of each merge is easily missed as the next package begins. It would be nice to at least have these messages logged somewhere. Are they? Can they be without patching portage? -- Ron -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Heads-Up sys-lib/ss breaks Apps
On Friday 08 July 2005 16:52, Ron Bickers wrote: On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: Which is a huge bummer since most of us don't go checking the ebuilds for these specific lines. How I wish It would just abort and BLAST the Einfo on the screen for me to see the next day and decide to do it manually. I have this concern as well. Also, when emerging multiple packages, the helpful and sometimes necessary output at the end of each merge is easily missed as the next package begins. It would be nice to at least have these messages logged somewhere. Are they? Can they be without patching portage? emerge --update world /var/log/world_update.log 21 or if you want to see it on screen as well: emerge --update world | tee /var/log/world_update.log 21 Uwe -- 95% of all programmers rate themselves among the top 5% of all software developers. - Linus Torvalds http://www.uwix.iway.na (last updated: 20.06.2004) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Heads-Up sys-lib/ss breaks Apps
Ron Bickers wrote: On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: Which is a huge bummer since most of us don't go checking the ebuilds for these specific lines. How I wish It would just abort and BLAST the Einfo on the screen for me to see the next day and decide to do it manually. I have this concern as well. Also, when emerging multiple packages, the helpful and sometimes necessary output at the end of each merge is easily missed as the next package begins. It would be nice to at least have these messages logged somewhere. Are they? Can they be without patching portage? mkdir /var/log/portage echo PORT_LOGDIR=/var/log/portage /etc/make.conf kashani -- gentoo-user@gentoo.org mailing list
RE: [gentoo-user] Heads-Up sys-lib/ss breaks Apps
From: kashani [mailto:[EMAIL PROTECTED] Sent: Fri 7/8/2005 1:47 PM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Heads-Up sys-lib/ss breaks Apps Ron Bickers wrote: On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: Which is a huge bummer since most of us don't go checking the ebuilds for these specific lines. How I wish It would just abort and BLAST the Einfo on the screen for me to see the next day and decide to do it manually. I have this concern as well. Also, when emerging multiple packages, the helpful and sometimes necessary output at the end of each merge is easily missed as the next package begins. It would be nice to at least have these messages logged somewhere. Are they? Can they be without patching portage? mkdir /var/log/portage echo PORT_LOGDIR=/var/log/portage /etc/make.conf kashani -- gentoo-user@gentoo.org mailing list what permission does that have to be? 644? winmail.dat
Re: [gentoo-user] Heads-Up sys-lib/ss breaks Apps
At Fri, 08 Jul 2005 12:47:51 -0500 kashani [EMAIL PROTECTED] wrote: Ron Bickers wrote: On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: Which is a huge bummer since most of us don't go checking the ebuilds for these specific lines. How I wish It would just abort and BLAST the Einfo on the screen for me to see the next day and decide to do it manually. I have this concern as well. Also, when emerging multiple packages, the helpful and sometimes necessary output at the end of each merge is easily missed as the next package begins. It would be nice to at least have these messages logged somewhere. Are they? Can they be without patching portage? mkdir /var/log/portage echo PORT_LOGDIR=/var/log/portage /etc/make.conf Although I didn't check this particular case, it is normally true that emerge generates *two* logs in the directory for each build. The large one contains the normal stuff (e.g., compiler output); the small one contains the important tidbits such as those mentioned above. allan -- gentoo-user@gentoo.org mailing list
