Wrong version checks...
Patrick Zwahlen <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <29437FD3CBD6D411B75300306E00253218A354@ONSNYS0004> |
Hi you all, I hope I'm not going to say completely stupid things, but I've something strange here. My problem is basically the same as Vincent Cojot's one, but on a regular RedHat 7.2 i386 system... I'm running current-1.0.2 (RPM package), on a RedHat 7.2 with all the latests updates (RPM, Python, popt...) I have a local mirror of the RedHat 7.2 and it's updates (i386, i686, noarch) I have a single channel (RedHat 7.2, i386) with four directories (original RPMs, i386 updates, i686 updates, noarch updates). When I ran 'cadmin -v create redhat72' this morning, I saw the following things for the version checks for the up2date packages (redhat still have the -11 -46 and -61 packages on their site): ===================================================================== Apr 04 08:52:16 Adding up2date-2.7.2-7.x.6.i386.rpm pkg0 = up2date, pkg4 = i386, filename = up2date-2.7.2-7.x.6.i386.rpm Apr 04 08:53:53 Removing up2date-2.7.2-7.x.6.i386.rpm Apr 04 08:53:54 Adding up2date-2.7.61-7.x.2.i386.rpm pkg0 = up2date, pkg4 = i386, filename = up2date-2.7.61-7.x.2.i386.rpm Apr 04 08:54:24 Removing up2date-2.7.61-7.x.2.i386.rpm Apr 04 08:54:25 Adding up2date-2.7.46-7.x.2.i386.rpm pkg0 = up2date, pkg4 = i386, filename = up2date-2.7.46-7.x.2.i386.rpm Apr 04 08:55:11 Removing up2date-2.7.46-7.x.2.i386.rpm Apr 04 08:55:12 Adding up2date-2.7.11-7.x.2.i386.rpm ===================================================================== 2.7.2 is erased by 2.7.61 (OK), which is then erased by 2.7.46 (WRONG), and finally erased by 2.7.11 (WRONG) I end up with 2.7.11 on my current server ! On the other hand, here is what I get for up2date-gnome: ===================================================================== Apr 04 08:51:56 Adding up2date-gnome-2.7.2-7.x.6.i386.rpm pkg0 = up2date-gnome, pkg4 = i386, filename = up2date-gnome-2.7.2-7.x.6.i386.rpm Apr 04 08:52:53 Removing up2date-gnome-2.7.2-7.x.6.i386.rpm Apr 04 08:52:54 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 04 08:53:43 Removing up2date-gnome-2.7.46-7.x.2.i386.rpm Apr 04 08:53:44 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 04 08:55:19 Removing up2date-gnome-2.7.11-7.x.2.i386.rpm Apr 04 08:55:20 Adding up2date-gnome-2.7.61-7.x.2.i386.rpm ===================================================================== And this is RIGHT ! Finally, I have exactly the same behaviour with the 'rhn_register' (WRONG) and 'rhn_register-gnome' (RIGHT) packages... I know that current is NOT doing the version checking, but let's admit that this one should be simple to figure out by the RPM library ;-) Any idea about what could be wrong ? Thx for your help and for this GREAT project which makes me save plenty of time every day... Best regards, - Patrick - PS1: I've done some random checks on other packages which have been updated, even several times (like php), and I don't see any problem on those ones... PS2: This is not really hurting me, as I'm anyway building my own rhn_register and up2date client packages for use with our current server... -- Patrick Zwahlen Mail: [email protected] ISP/ASP Engineer Phone: +41 (0)22-363-6823 onSpirix Fax: +41 (0)22-363-6801 Ch. de la Vuarpilliere 31 Mobile: +41 (0)79-257-9884 CH-1260 NYON Web: http://www.onspirix.ch