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

What redhat version is running on your current-1.02 server?
								-Rob

> -----Original Message-----
> From: Vincent Cojot [mailto:[email protected]]
> Sent: Tuesday, April 02, 2002 4:06 AM
> To: [email protected]
> Subject: [Current-server] up2date package in two current-db : 
> different
> behaviour???
> 
> 
> 
> Hello everyone,
> 
> 	I'm going crazy here :)... I don't know why this is happening:
> 
> RedHat release up2date-2.7.46 some time ago and then followed with
> up2date-2.7.61 some time later.
> 
> I have two channels: redhat-6.2-sparc and redhat-7.2-i386..
> 
> On the same current server (rpm-4.0.4, python-2.2 and 
> current-1.02), I get
> this when rebuildind the databases...
> 
> RH7.2 (example with up2date-gnome but the same happens on "up2date"
> itself):
> 
> Apr %2m 10:53:37 Adding up2date-gnome-2.7.11-7.x.2.i386.rpm
> pkg0 = up2date-gnome, pkg4 = i386, filename = 
> up2date-gnome-2.7.11-7.x.2.i386.rpm
> Apr %2m 10:54:03 Removing up2date-gnome-2.7.11-7.x.2.i386.rpm
> Apr %2m 10:54:04 Adding up2date-gnome-2.7.46-7.x.2.i386.rpm
> pkg0 = up2date-gnome, pkg4 = i386, filename = 
> up2date-gnome-2.7.46-7.x.2.i386.rpm
> Apr %2m 10:54:23 Removing up2date-gnome-2.7.46-7.x.2.i386.rpm
> Apr %2m 10:54:24 Adding up2date-gnome-2.7.61-7.x.2.i386.rpm
> 
> So the latest package is: 2.7.61
> 
> But on RH6.2 sparc, I get this:
> 
> Apr %2m 10:55:03 Adding up2date-gnome-2.7.11-6.x.1.sparc.rpm
> pkg0 = up2date-gnome, pkg4 = sparc, filename = 
> up2date-gnome-2.7.11-6.x.1.sparc.rpm
> Apr %2m 10:55:03 Removing up2date-gnome-2.7.11-6.x.1.sparc.rpm
> Apr %2m 10:55:03 Adding up2date-gnome-2.7.61-6.x.1.sparc.rpm
> pkg0 = up2date-gnome, pkg4 = sparc, filename = 
> up2date-gnome-2.7.61-6.x.1.sparc.rpm
> Apr %2m 10:55:09 Removing up2date-gnome-2.7.61-6.x.1.sparc.rpm
> Apr %2m 10:55:10 Adding up2date-gnome-2.7.46-6.x.1.sparc.rpm
> 
> So it finds that the latest version is 2.7.46???
> 
> Here are the files I have:
> -rw-rw-r--   1 root     root       79591 Mar 23 04:20 
> 6.2/sparc/up2date-gnome-2.7.11-6.x.1.sparc.rpm
> -rw-rw-r--   1 root     root       80736 Mar 18 21:06 
> 6.2/sparc/up2date-gnome-2.7.46-6.x.1.sparc.rpm
> -rw-rw-r--   1 root     root       81089 Mar 26 22:09 
> 6.2/sparc/up2date-gnome-2.7.61-6.x.1.sparc.rpm
> 
> -rw-r--r--   1 root     root       79216 Nov 20 22:41 
> 7.2/i386/up2date-gnome-2.7.11-7.x.2.i386.rpm
> -rw-rw-r--   1 root     root       80564 Mar 18 20:50 
> 7.2/i386/up2date-gnome-2.7.46-7.x.2.i386.rpm
> -rw-rw-r--   1 root     root       80986 Mar 26 22:09 
> 7.2/i386/up2date-gnome-2.7.61-7.x.2.i386.rpm
> 
> Do anyone know what's going on and where I should start 
> investigating..?
> 
> Vincent
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
>