[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: network manager, KDE and libudev

David wrote:
On 3/16/2009 6:13 PM, John Summerfield wrote:

Perhaps there should be an "enable repo" command to avoid this:

--- fedora.repo 2008-12-10 15:42:35.000000000 +0900
+++ fedora.repo.rpmnew  2008-11-07 05:06:38.000000000 +0900
@@ -3,9 +3,7 @@





It could be run when installing the release file.

The appropriate definition is the rpmnew file. I don't recall disabling
it, but originally I installed an Eight beta and the old definition for
the install media is present too. Early on, that would have sufficed.

The .rpmnew feature is to protect your/your systems configuration files

I understand all that, I've been using RHL and its descendants since RHL 3.0.3 - what is that, a decade or so?

There still isn't a good way to inform the administrator that this has been done. Flashing messages on the screen means they get scrolled off with any updates of size. Asking stupid questions (as Debian does) makes the update processes excessively interactive. Noting these things in a log file means the administrator has to know to look, and where to look.

mail to root should work if the alias has been set. A question during install could ensure it is.

My choice of a mirror should never be overturned, but enablements often should. If livna doesn't track rawhide or betas, then turning its repos on and off automatically is sensible, having it in the wrong state is troublesome.

Another thought. The last, very last, update of a Rawhide turns it into
a Release all by itself. Does here anyway and then I have to turn in
back into a rawhide by hand.

Something of that sort happened. It might be during my last turn on rawhide I disabled the repo.



-- spambait
1aaaaaaa coco merseine nu  Z1aaaaaaa coco merseine nu
-- Advice

You cannot reply off-list:-)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]