Bug#770425: Possibility of update to 4.x
On Sat, 2014-11-29 at 14:53 +1100, Craig Small wrote: Hi Nick, The security update will only be 3.6.1 with the 4.7.4-4.7.5 patches. It's difficult balancing act really but the whole purpose of the security updates is just to update for security. It's not ideal for certain situations. The proposed update went to the security team a few minutes ago and should mean an update for wordpress in wheezy will be out today. Thanks for that. Doesn't actually concern me which solution was picked, as long as one was chosen and implemented reasonably quickly (I'll stick with the 4.x packages I now have anyway). Cheers, Nick -- Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195 # These statements are mine, not those of the University of Otago
Bug#770425: Possibility of update to 4.x
Hi Nick, The security update will only be 3.6.1 with the 4.7.4-4.7.5 patches. It's difficult balancing act really but the whole purpose of the security updates is just to update for security. It's not ideal for certain situations. The proposed update went to the security team a few minutes ago and should mean an update for wordpress in wheezy will be out today. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770425: Possibility of update to 4.x
On Wed, Nov 26, 2014 at 11:45:29PM +, Nick Phillips wrote: Issues: * New package splits out the themes into separate packages. * New package no longer links /usr/share/wordpress/wp-config.php to /etc/wordpress/wp-config.php - customisations there will be ignored until admin intervenes. Both of these issues could fairly easily be reverted to old behaviour, I think. It's tricky because on the one hand I can back-port the patches (hopefully) to the version in stable. Alternatively I can push 4.0.1 down to stable and try to fix up the difference such as dependencies. Stable security fixes should have the minimal set of changes, but at what point does it become better to abandon that ideal? - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770425: Possibility of update to 4.x
FYI... * 4.0.1+dfsg-1 appears to build fine with a wheezy-only pbuilder. * Review at http://premium.wpmudev.org/blog/wordpress-4-0-hugely-underwhelming/ claims that The fact is, users who upgrade to 4.0 when it’s released on August 27 won’t even realize there are any changes. It's worked smoothly on 2 out of 3 of my machines. The other relied on customisations in /etc/wordpress/wp-config.php (which warns you not to make changes, despite being a config file). Issues: * New package splits out the themes into separate packages. * New package no longer links /usr/share/wordpress/wp-config.php to /etc/wordpress/wp-config.php - customisations there will be ignored until admin intervenes. Both of these issues could fairly easily be reverted to old behaviour, I think. Cheers, Nick -- Nick Phillips / n...@debian.org / 03 479 4195 # These statements are mine, not those of the University of Otago
Bug#770425: Possibility of update to 4.x
On mer., 2014-11-26 at 23:45 +, Nick Phillips wrote: FYI... * 4.0.1+dfsg-1 appears to build fine with a wheezy-only pbuilder. * Review at http://premium.wpmudev.org/blog/wordpress-4-0-hugely-underwhelming/ claims that The fact is, users who upgrade to 4.0 when it’s released on August 27 won’t even realize there are any changes. It's worked smoothly on 2 out of 3 of my machines. The other relied on customisations in /etc/wordpress/wp-config.php (which warns you not to make changes, despite being a config file). Issues: * New package splits out the themes into separate packages. * New package no longer links /usr/share/wordpress/wp-config.php to /etc/wordpress/wp-config.php - customisations there will be ignored until admin intervenes. Both of these issues could fairly easily be reverted to old behaviour, I think. Thanks for the investigation. From the various updates I did in the past, I remember having to deal with the removal of embedded stuff, which was different in stable, but maybe that's not the case anymore. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
