On Mon, 2007-03-12 at 15:53 +, Grant Edwards wrote:
Yup, that was evidently the problem. Perhaps step #2 should be
documented in the Handbook and/or the Quickinstall
Perhaps the constant nagging from the timezone-data package when it's
emerged as well as the system when it's booted isn't
At Mon, 12 Mar 2007 15:53:40 + (UTC) Grant Edwards [EMAIL PROTECTED]
wrote:
On 2007-03-12, Albert Hopkins [EMAIL PROTECTED] wrote:
On Mon, 2007-03-12 at 15:07 +, Grant Edwards wrote
That was the old way of doing it. For a number of reasons a new
method is devised. The new method
On Mon, 2007-03-12 at 16:28 +, Grant Edwards wrote:
Perhaps the constant nagging from the timezone-data package
when it's emerged
When it's emerged as part of an update with 30 or 40 other
packages, it's pretty easy to miss things like that.
This has long been a complaint among users
On Mon, 2007-03-12 at 15:33 -0400, John covici wrote:
I wish you could have an option for portage to stop until these things
are acknowledged -- I had a 106 package update of which the timezone
data were a part and I use script and check these little notices,
however its easy to miss such
On 3/12/07, Albert Hopkins [EMAIL PROTECTED] wrote:
On Mon, 2007-03-12 at 15:33 -0400, John covici wrote:
I wish you could have an option for portage to stop until these things
are acknowledged -- I had a 106 package update of which the timezone
data were a part and I use script and check
On Mon, 12 Mar 2007 15:33:54 -0400, John covici wrote:
I wish you could have an option for portage to stop until these things
are acknowledged -- I had a 106 package update of which the timezone
data were a part and I use script and check these little notices,
however its easy to miss such
On Mon, 12 Mar 2007 14:19:03 -0700, Mark Knecht wrote:
I am interested however in learning about how to get these messages
logged and sent by email or at least into some file that easy to look
at. I think they already go into the portage /var log file but I find
that pretty tedious and easy
7 matches
Mail list logo