Bonjour,
j’aimerais connaître la procédure afin de downgrader php en version 5.4 vers la version 5.3 car j’ai découvert et reporté ce bug : bugs.php.net/bug.php?id=61443 cependant c’est assez bloquant pour le moment…
Merci d’avance.
Bonjour,
j’aimerais connaître la procédure afin de downgrader php en version 5.4 vers la version 5.3 car j’ai découvert et reporté ce bug : bugs.php.net/bug.php?id=61443 cependant c’est assez bloquant pour le moment…
Merci d’avance.
Déjà, tu peux faire un “apt-cache policy php5” et voir ce qui est disponible.
S’il existe une version, il faut essayer de créer un fichier “preferences” dans “/etc/apt/”.
Et forcer la version qui fonctionne 5.3 pour le moment en attendant un patch.
Format du fichier :
[code]The format is simple:
Package: <package>
Pin: <pin definition>
Pin-Priority: <pin's priority>
Each entry must be separated from any other entries by a blank line. For example, to keep package sylpheed that I have modified to use “reply-to-list” at version 0.4.99, I add:
Package: sylpheed
Pin: version 0.4.99*
Note that I used an * (asterisk). This is a “wildcard”; it say that I want that this “pin” to be valid for all versions beginning with 0.4.99. This is because Debian versions its packages with a “Debian revision” and I don’t want to avoid the installation of these revisions. So, for instance, versions 0.4.99-1 and 0.4.99-10 will be installed as soon as they are made available. Note that if you modified the package you won’t want to do things this way.
The pin priority helps determine whether a package matching the “Packages:” and “Pin:” lines will be installed, with higher priorities making it more likely that a matching package will be installed. You can read apt_preferences(7) for a thorough discussion of priorities, but a few examples should give the basic idea. The following describes the effect of setting the priority field to different values in the sylpheed example above.
1001
Sylpheed version 0.4.99 will never be replaced by apt. If available, apt will install version 0.4.99 even if it would replace an installed package with a higher version. Only packages of priority greater than 1000 will ever downgrade an existing package.
1000
The effect is the same as priority 1001, except that apt will refuse to downgrade an installed version to 0.4.99
990
Version 0.4.99 will be replaced only by a higher version available from a release designated as preferred using the "APT::Default-Release" variable (see How to keep a mixed system, Section 3.8, above).
500
Any version higher than 0.4.99 of sylpheed which is available from any release will take preference over version 0.4.99, but 0.4.99 will still be preferred to a lower version.
100
Higher versions of sylpheed available from any release will take preference over version 0.4.99, as will any installed higher version of slypheed; so 0.4.99 will be installed only if no version is installed already. This is the priority of installed packages.
-1
Negative priorities are allowed as well, and prevent 0.4.99 from ever being installed.
[/code]
PS : Si je m’en souviens bien, j’avais désinstallé la nouvelle version et j’avais bloqué la version voulue à l’aide de ce fichier comme ça, je pouvais faire des “apt-get upgrade” sans risque.
Faut essayer voir ce que ça donne 
Merci pour les explications 