On Tue, Jan 29, 2008 at 09:37:52AM -0500, Michael DeHaan wrote: > > > > >which is true, because after last upgrade python was in version 2.3.4 but > >this is problem of ScientificLinux. > > > You could of course just do rpmbuild --rebuild on the cobbler src RPM. > > Cobbler does not require that particular Python ABI. Well... Rebuilding of package or any software is always a nasty thing (hell of dependencies & compilers & environment). I don't want to spend 95% of my life with searching for correct dependency version and correct dependency version for previous dependency, e.t.c.... That's the reason why people invented thing such as yum or apt. Next problem is upgrade of the system (=upgrade of dependencies => new build which does not have to work, because of new features which may need new stuff you don't know about, so you spend 6 nights just to check what you really need). Also I'd like to add, that it should be responsibility of maintainer to keep things running for given platform. Besides, if the highest version of application in specific distribution is so old that it cannot work with rest of the distro then it's time to think about another distribution. (As I said in previous mail, problem is already solved: Debian+tftp server+pxe... without problem) V. > > > > > _______________________________________________ > et-mgmt-tools mailing list > et-mgmt-tools@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/et-mgmt-tools > _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
