-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 1 Oct 2003 12:12:47 +0300, Axel Thimm wrote:
> With the Epoch: (which went from 0 to 1 on the redhat-release
package),
> everything works out fine and is rpm-increasing.
You have to do it for each package in a multiple concurrent release
supporting repo that exists for multiple releases of RH. Read up this
thread for details and examples.
How many packages would that be? Consider the package naming scheme
of fedora.us which uses the following target release tags:
rh80 < rh90 < rh90.93 < 0.94
No problems during upgrades. The other example (kernel) doesn't hold
true for Fedora Core, because 0.94 contains a kernel version which is
higher than Red Hat Linux 9, 8.0 and older releases:
2.4.20-20.9 < 2.4.22-1.2061.nptl
2.4.20-20.8 < 2.4.22-1.2061.nptl
2.4.20-20.7 < 2.4.22-1.2061.nptl
Even if there were a kernel upgrade for RHL<=9, I'm sure it would see
a lower package release version than what is in Fedora Core, e.g.
2.4.22-2 in Fedora Core and 2.4.22-1.9 in Shrike Updates.
- --
Michael, who doesn't reply to top posts and complete quotes anymore.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/esDo0iMVcrivHFQRAma9AJ94XrV9hWWlf9BbuhKRyhTiuHJ2OwCgiCxP
NkbVR5pA5sg/X6Pf9yexk9w=
=sniF
-----END PGP SIGNATURE-----