Ned Slider wrote:
On 23/07/12 15:48, m.roth@5-cent.us wrote:
And for the guy from the elrepo team, you'll note it was *not* an elrepo problem, which is what I'd suspected, unless the repodata file's changed since Friday.
It was a problem caused by *you* editing the default elrepo config file and not understanding the implications and subsequent problems caused by *your* changes. So you are correct that it was not an elrepo problem, it was a "user" issue.
And you clearly don't like the idea that I might edit the elrepo.repo because I might only want to allow *one* package, even though everyone knows that some other elrepo packages result in conflicts with the base CentOS repositories.
No one ever said it was an elrepo problem, it was noted that the elrepo mailing list was a more appropriate place to deal with issues relating to the elrepo.repo config file as this has absolutely nothing to do with CentOS.
The point is that you would have been given the solution a lot quicker if you had just posted the whole config file when you were asked rather than waste everyone's time with your attitude.
You didn't care to pay attention to what I *DID* post. The rest of it was identical to, in fact, what I posted twice. I did not feel I needed to clutter up the mailing list the way some folks do, with many dozens or hundreds of lines of error messages or config files, when I certainly know enough to pull out the relevant information. <snip> And the guy who *did* read what I posted did help me.
mark "this thread declared dead"