RE: up2date package in two current-db : differen t behaviour???

On 2 Apr 2002, Hunter Matthews wrote:

> Neither John nor I have been able to reproduce these version errors with
> the "good" versions of rpm. I must admit we have limited our testing to
> Red Hat Linux servers, but I don't see how that would affect how rpm
> decides who is newer...

Hunter and John,

	Thanks for trying to reproduce this.. The thing that tickled me
was why this was happening for the "sparc" channel and not for the "i386"
channel... I'll see if I can reproduce this on our other RH7.2 current
server (we also have a redhat-6.2-sparc channel there..). Thanks.

Vincent

>
>
>
> On Tue, 2002-04-02 at 08:32, Vincent Cojot wrote:
> > On Tue, 2 Apr 2002, Rob Hagopian wrote:
> >
> > > Well, that's a little more complicated :-)
> > >
> > > What versions of the supporting packages (rpm-python in particular) are you
> > > using?
> >
> > Well, I'm using poptmodule.so and rpmmodule.so built from rpm-4.0.4:
> >
> > root@unknown:[/usr/local/src/rpm-4.0.4/python ]uname -a
> > SunOS unknown 5.8 Generic_108528-12 sun4u sparc SUNW,Ultra-2
> >
> > root@unknown:[/usr/local/src/rpm-4.0.4/python ]ls -al *.so
> > -rwxr-xr-x   1 root     root       36548 Mar 16 14:15 poptmodule.so
> > -rwxr-xr-x   1 root     root       86320 Mar 16 14:14 rpmmodule.so
> >
> > I'll try to run current with more debug information to know where it
> > fails.. I'm just unsure about where to start...
> >
> > Vincent