On jeu., 2013-07-04 at 12:51 +0200, Paul Dreik wrote: > 2013-07-03 22:58, Yves-Alexis Perez skrev: > > On mer., 2013-07-03 at 10:25 +0200, Paul Dreik wrote: > >> Notice: add_option was called with an argument that > >> is <strong>deprecated</strong> > >> since version 2.3 with no alternative available. in > >> /usr/share/wordpress/wp-includes/functions.php on line 2927 > >> (repeated three times) > > > > My guess would be a plugin/theme not compatible with recent (post 2.3) > > wordpress. Do you have something like that installed?
> So, it seems like upgrading to a new version requires logging in to the > admin section to get it working properly. Yes. The DSA text might not be clear enough about that, but it's the exact same procedure you would have to follow if you updated to a new Debian version, or if you updated using Wordpress tarballs. > I assume this is also thye > case for the debian packaged version. I think it is really unfriendly of > wordpress to not give any output at all in this situation, not even when > enabling debugging. I kind of agree here. > Maybe most people update through the web interface > rather than the distributions package updates and never get such problems. > > According to the documentation at > http://codex.wordpress.org/Updating_WordPress#Step_2:_Update_your_installation > updating the database through the web interface is the right thing to > do. I do not think it would hurt to mention it among the other news > displayed when updating the package. Yes, I think we'll try to add something like that in the next DSA text and in the NEWS.Debian file. It's might be kind of obvious for people updating wordpress at every upstream release, but that's the kind of thing people forget, especially if we skip updates in Debian. > People run debian stable for a > reason, and security updates that bump the version should in my opinion > be careful about breaking existing installations. I hope I contributed > instead of only complaining by troubleshooting and reporting my findings. The procedure to update to a complete new upstream version in a stable Debian release is anything but trouble free. We try to avoid that kind of thing, but here we don't have much choice, identifying each and every vulnerability fixed in a new release is too time consuming (when even possible) and backporting the fixes is just not possible considering the resources we have. That means end-users have to take care when upgrading. We try to warn them in the DSA text but there's always room for improvement. Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
