I googled around for it, but couldn't find anything at all. But then
again, I didn't try really really hard..
Walter
On Mon, Oct 12, 2009 at 13:11, Christoph Maser c...@financial.com wrote:
Am Montag, den 12.10.2009, 06:43 +0200 schrieb Walter Heck:
Steve,
thanks for your excellent
On Oct 12, 2009, at 2:46 AM, Tom G. Christensen wrote:
This is still just a workaround for an issue that RPMforge should
have dealt with instead of putting this burden on the user.
eh? how would you suggest that RPMforge address this particular
issue? i can see essentially three
On Oct 12, 2009, at 8:27 AM, Tom G. Christensen wrote:
2) package Sys::Syslog 0.16 without a man page, or with man page
in some nonstandard location (thus hiding the fact that we're
replacing a system package)
Ah yes, this is the real issue, the need to alert the user that a
system
On Mon, 12 Oct 2009, Tom G. Christensen wrote:
Steve Huff wrote:
On Oct 12, 2009, at 2:46 AM, Tom G. Christensen wrote:
Ah yes, this is the real issue, the need to alert the user that a system
package is being replaced.
I feel strongly that deliberately breaking packages is the wrong way
On Mon, 2009-10-12 at 17:05 +0200, Tom G. Christensen wrote:
I agree that the current situation is not a good one. I could once again
state that this is because of yum, since apt would not propose to update
it. But I also don't see a good fix for this.
Perhaps a yum plugin could
