On Wed, Jul 11, 2001 at 02:56:27PM -0600, Eaon wrote:
> > This has been reported 10 times or so. We are waiting for a fix, or even
> > a confirmation. I wish that if MandrakeSoft is policing the list, that
> > they include in the changelog the name and e-mail of the person to first
> > report the bug. This way we cna check the CHRPM list and see that a bug
> > is indeed fixed.
> >
> Have you tried looking here:
> https://qa.mandrakesoft.com/cgi-bin/show_bug.cgi?id=2532 Or how about this
> one: https://qa.mandrakesoft.com/cgi-bin/show_bug.cgi?id=3638 I believe
> these are the bugs you are talking about, correct? Or something pretty
> close anyway. That they are in the bug tracking system seems to be
> confirmation that they are noticed. If I might stand up in defense of David
> (Odin, aka DindinX, the one that all the bugs are assigned to, and the one
> that bitched the other day about people repackaging rpmdrake without telling
> him, so obviously this is his baby and obviously he notices something and
> seems to care), despite not knowing him at all, he doesn't seem to reply to
> the list very often, and seems to be more partial to dealing with bugs that
> get into bugzilla (he probably doesn't want my help on this - too bad, huh?
> ;-) ). He's just a guy, with his own way of doing things, just like any
> one of us. I think that once a few people have discussed it on the list and
> decided that it is indeed a software bug and not some silly
> configuration/corrupt config file/whatever kind of issue, then the next
> logical step is to put it in bugzilla, and wait for the fix without
> complaining about it more to the list. That's what archives of the list and
> bugzilla are for - to see if your problem has addressed so that you don't
> have to ask again. If you're interested in whether or not a bug has been
> fixed, you could always add your name to the CC list in bugzilla and you'll
> get an email when the bug's status changes.
>
Yes, I don't answer to the list that often, but be sure I'm reading
all these mails.
Yes, I'm working on this problem, which does not come directly from
rpmdrake itself, but more likely from rpminst and/or urpmi. I need to
understand why this happens now, and why this was working before.
It may be related to rpm changes. I really do not know for now.
When I'll know more I tell the list.
DindinX
--
[EMAIL PROTECTED]
