Tag Info

New answers tagged

0

I had a similar problem, but instead of different arrays, mdadm.conf got empty after a Debian upgrade (Lenny to Squeeze). W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. The same solution worked. I used the output of mkconf as my mdadm.conf: /usr/share/mdadm/mkconf > /etc/mdadm/mdadm.conf The reboot test passed.


2

PHP 5.3 is not 100% backwards compatible with PHP 5.5. An important change is that the old fashioned mysql connector (http://php.net/manual/en/book.mysql.php) is deprecated. More info on deprecated functions for PHP 5.4 => PHP 5.5: http://php.net/manual/en/migration55.deprecated.php PHP 5.3 => PHP 5.4: http://php.net/manual/en/migration54.deprecated.php I ...


0

PHP 5.4 and 5.5 could display more warnings on different things. Depending on the PHP applications, those warnings / errors can be visible to the end user also. Therefore I recommend you to upgrade the PHP in your test environment, and test if things work as they should, before you upgrade it in your production environment.


-2

I've managed to fix it by running 'package-cleanup --cleandupes' several times and then running yum update. All working okay now. Cheers


2

I have solved such problems in the past with package-cleanup tool (install "yum-utils") with --cleandupes and then repeat yum check and yum-complete-transaction.


0

correct el%24releasever variable name to $releasever in your repo file. for more information about yum variables check yum.conf. Variables There are a number of variables you can use to ease maintenance of yum's configuration files. They are available in the values of several options including name, baseurl and commands. $releasever This will ...


0

Pinning is the canonical way to pin packages to a certain version on Debian based Linuxes. Configuration management tools like Puppet or Chef can be used to roll out a pinning config to many hosts.



Top 50 recent answers are included