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

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...




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
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> 
-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.