Re: Package version conflicts

Let me take this bit by bit.

On Tue, 2002-01-29 at 16:44, Nathan G. Grennan wrote:
> 
> Hello,
> 
> 	Since the release of the most recent patch we have a functioning
> up2date server, but something Must be done about cadmin/current and more
> than one version of the package in the tree. Having to go through by
> hand and remove duplicates every time a new update comes out will be a
> nightmare. There are duplicates of original vs errata, old errata vs.

It IS a development version...


> new errata, rawhide vs errata, gnomehide vs errata,  different arch vs
> everything else, arch vs arch. There is also the problem of when you
> want to keep things up to date by mirroring redhat so that all the rpms
> will be under directories in like redhat's ftp tree. I think this can be

Unfortunate that RH does things this way, but I agree that Current must
be able to use a simple RH mirror.


> over come by using symlinks generated by a script, but there is still
> the multiple copies problem. Has anyone come up with any elegant scripts
> to solve this problem? I think really this must be address without
> current so that it just doesn't care and figures out the newest/best for
> the client itself.

Here's where we  are: the db finally supports a low level "delete one
rpm" function (in channel.py). What still needs to be done (and both
John and I are hacking on it) is during database creation, if current
sees a newer/older package to do the right thing. The tricky part was
being able to do the right thing if what you found was a newer package
than what was already in the database (thats why a "delete" function was
needed).

> 
> Example:
> 
> 
> xchat-1.8.1-2.i386.rpm      - original 7.2
> xchat-1.8.6-1.i386.rpm      - current gnomehide
> xchat-1.8.7-1.72.0.i386.rpm - current errata

0.9.4 or 0.9.5 (depending on how fast John and I are) will "correctly
deal with this, as far as simple versions go - Current would see 1.8.1,
add that to the database, see 1.8.6, pull 1.8.1 out of the database, put
1.8.6 in, see 1.8.7, pull 1.8.6 out, put 1.8.7 in, done.

HOWEVER, this brings up the question of consistency - the errata package
is newer, but its built against the original libs in RH 7.2. The
gnomehide is an "older" package, but its built against all the other
libs in gnomehide. You can't just install gnomehide, and then the
errata, and expect things to work.

This kind of thing is where "channels" came from, and is unsupported in
Current as of yet (its not fully supported in RHN yet).

You would HAVE to figure out for your site whether you wanted 
straight RH 7.2 + errata   
OR 
gnomehide for RH 7.2 

Once you had decided this for your site, you would then know what to
feed to current, as far as what dirs to use to build your db.


> 
> 
> or
> 
> kernel-2.4.7-10.i386.rpm   - original 7.2
> kernel-2.4.9-13.i386.rpm   - old errata

Older versions of the same package will be handled as above.

> kernel-2.4.9-21.i386.rpm   - latest errata i386
> kernel-2.4.9-21.i586.rpm   - latest errata i586
> kernel-2.4.9-21.i686.rpm   - latest errata i686
> kernel-2.4.9-21.athlon.rpm - latest errata athlon

Current already handles multiple archs of EXACTLY the same version of a
package. What problems are you seeing here?


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