I'm trying to do a clean-up of the packages to remove the broken ones (e.g. pixman-0.32), clean up dependencies (several Xorg packages in the updates-testing repository seem to require pixman 0.32+, and I seem to recall that there was an issue with the way evolution-data-server dependencies were resolving that was making the update process somewhat trickier than it should have been.
Jacco, seen as we currently have no immediate fix or explanation for the pixman (segfault in glibc) issue within EL6, the options are: 1) Rebuild those Xorg packages against earlier, working pixman (will that work or do they have a dependency requirement on the later version?) 2) Bodge it with the EL7 build of pixman which I seem to recall Jacco saying works (will that actually work properly, WRT it being linked against the EL7 version of glibc and libgcc?) Also, Jacco, WRT evolution-data-server dependency fixing, do I rememeber correctly that the correct fix is to replace my latest build in the updates repository with your build of the same version from updates-testing? Or was it more involved than that? Once that is all straightened out and reasonably well tested, I am pondering moving all of the packages from updates and updates-testing over into the base repository and having any future updates to into the freshly cleaned out updates repository. The process can be periodically repeated to keep the updates repository relatively small (lower metadata volume) and keep the base repository changes infrequent (less metadata churn and syncing overhead). Since this will involve some repository changes, it would probably be good time to roll out an updated release package with the new .repo and public key, and re-sign all the packages with a new key. Any objections, suggestions or thoughts on this from anyone? Gordan _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
