Re: Re: grab, not update
Jef Spaleta <[email protected]> 21 Aug 2002 14:41:15 -0400
| Newsgroups | gmane.linux.redhat.rpm.grab |
|---|---|
| Message-ID | <1029955305.13037.73.camel@spatula> |
I just thought of one way to hack in some logic into grab to try to account for this....teired server priorities. give grab the ability to override these kind of situation by telling grab that a certain server takes priority over another. Usually you would have the situation where a redhat7.3-update ftptree takes priority over versions from redhat7.3-main. If grab sees a package on the update tree grab can force the upgrade to that priority package even if its badly named. My example where the libvorbis packages...redhat7.3 came with an rc package...but version 1.0 was added to the update tree so grab didnt see the 1.0 as a valid update due to the naming scheme. But if I could tell grab to prioritize the update tree and update from it instead of keeping a package from a server with a lower priority, then grab would see the libvorbis package in the update tree....and see that I currently have a package of the same name in sync main...and then override the package numbering sorting rules and upgrade from the update tree becuase I've given the update tree a higher priority than the mainos tree. Being a little more conservative...and use the server priority ability to get grab to warn about these situations but not to actually try the upgrade when doing sysupdate. This way grab could see there are packages in the higher priority tree...and warn you with some output that it skipped them do to a percieved naming problem so they appear to be older packages. So for this situation updating across distro releases...you give the current release a low priority and the new release branch a higher priority... -jef On Wed, 2002-08-21 at 12:05, Greg Kurtzer wrote: > As far as the telnet issue... That is the packagers problem (I hate to do say > that, but their version nomenclature is wrong). 0.17.* is always bigger then > 0.17 . Someone did not follow the rules! I would suggest to first uninstall > telnet and telnet-server (I am sorry to even suggest that crude hack) and then > do the sysupdate, and reinstall telnet (if it is even needed).