"Guy T. Rice" <[EMAIL PROTECTED]> writes:
> Umm, okay, but how did you fix it? Do you need to remake the RPM (with a
> corrected spec file) or simply rename the RPM? Won't renaming the RPM
> cause other problems (like package X depends on package Y but we just
> renamed package Y to Z)? Of course, that might not come up, depending on
> which packages have the error...
No, I renamed the packages.
Actually, this happens when something silly between the chair and the
keyboard (an expression from Stefan AFAIR, I like that one!) renames the
package.
The packages should *never* be manually renamed.
For dependencies, no it's not a problem because when filename X gets
installed, it does not "provide X", it provides the official name of the
package.
> If this is the cause of the error, rather than attempting an install and
> seeing where the error occurs, it'd probably be easier to check the
> package name/RPM name correspondence before burning.
Of course!
We should include a "verify" script along with the "gen*" scripts.
--
Guillaume Cottenceau
