Hello Eric, Tuesday, December 4, 2012, 11:02:26 AM, you wrote:
ES> On 12/04/2012 08:21 AM, Diana Calder wrote: >> --> Running transaction check >> --> Processing Dependency: php = 4.3.9-3.36 for package: php-ldap >> --> Finished Dependency Resolution >> Error: Missing Dependency: php = 4.3.9-3.36 is needed by package php-ldap >> qtp-dependencies - installation of base dependencies failed, exiting >> qtp-newmodel - dependent packages processing failed, exiting >> >> --- Hit ENTER to return to menu --- >> >> When I do a "yum list php" I get: >> >> Loading "priorities" plugin >> Setting up repositories >> Reading repository metadata in from local files >> 274 packages excluded due to repository priority protections >> Installed Packages >> php.i386 4.3.11-2.8 installed >> Available Packages >> php.i386 4.3.9-3.36 update >> >> So, in other words, I would need to downgrade php, right? Urgh. That >> won't be fun. ES> I've no idea what php-ldap is doing in the dependency list. QTP doesn't ES> use it at all that I'm aware of. It's not on my system. I'd try removing ES> qtp-ldap from the qtp-dependencies script, then re-try qtp-newmodel. Let ES> us know how this works. Removing qtp-ldap from the qtp-dependencies script let qtp-newmodel run successfully. (Finally!) So far, everything looks okay. >> Maybe I'll just have to leave this Qmail server as-is and cross my >> fingers that being on different versions won't cause any issues when I >> migrate over to the new Qmail server... ES> Perhaps, but I'd try getting QTP upgraded if possible. It'll make your ES> migration simpler (fewer variables). There are a couple recent vpopmail ES> database changes that I'd be cautious of. Vpopmail in general would be ES> my biggest concern migrating from previous QTP versions. Yeah, I really didn't want to migrate between different versions if I could avoid it. I wasn't sure whether there wasy anything in there that would matter but I figured that Murphy's Law would rule if there was the slightest chance of a problem. >> Speaking of which - where does the CentOS6 & Qmailtoaster situation >> stand? Is official support for Qmailtoaster on CentOS6 close or still >> some months off? I'd rather use CentOS6 instead of CentOS5 but the new >> hardware is here and I need to get it set up, so if CentOS6 support is >> still more than a week or two away, I'll have to go with 5. >> ES> I'm swamped until January at least, so don't expect the official COS6 ES> release before 13Q1. Busy time of year for everyone, I think, so I'm not exactly surprised that it's going to be a bit before the official release. ES> That being said, I would go ahead with COS6 in your situation. There are ES> several folks here that are running QMT on production COS6 hosts. Dan ES> even has a script that takes care of things that need to be changed. ES> There's not much difference really. I was hoping to be able to use COS6 as I hopefully won't need to rebuild the Qmail server for a very, very long time since this time it's going in a VM on Citrix Xenserver rather than on a physical box. It will be the first of our servers to make that switch. I've sent Dan an offlist email regarding his script since both mirror4.qmailtoaster.com and mirror9 (the two locations he'd said that the script could be downloaded from) seem to no longer exist. So, unless someone has a copy of it that they can make available, I'll have to wait to hear back from him before I can get too far with the new Qmail server. ES> Please keep us posted on your progress. Well, the qmailtoaster on the old server is now up to date and I'm getting started on the CentOS6 minimal install on the new server. With a little luck and a quick response regarding Dan's script, I hope to get the new server at least as far as the testing phase by the end of the week. If I'm really lucky, I might even manage to get the migration done (there's less than 100 accounts on the Qmail install, so it shouldn't take too long to back up and migrate). Thanks for the assistance, Diana -- Best regards, Diana mailto:[email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
