On Sat, September 14, 2013 00:30, Matthias Kilian wrote: > Hi, > > On Fri, Sep 13, 2013 at 06:17:40PM +0400, Kirill Bychkov wrote: >> On Fri, September 13, 2013 15:42, Stuart Henderson wrote: >> > On 2013/09/13 19:01, wen heping wrote: >> >> Please go ahead and feel free to take the maintainership of it. >> > >> > I don't use it, but if security fixes aren't handled reasonably quickly, >> there >> > isn't much point in having webapps in ports. >> > >> > (Wordpress also needs some update love if anyone interested is reading - >> > remote >> > code execution in some cases). >> >> I have patch for latest wordpress. It works with fresh install, but I have >> problems while updating from 3.5.2. May be my setup is some way incompatible >> with new version... > > Well, wordpress is a perfect example for something that shouldn't be > provided as an OpenBSD (or any other system distribution) package... > > When updating, you may have to push some buttons to make the updated > version work. > > It's unknown *which* buttons you'll have to push, because it depends > on what plugins and themes you're using, and in which ways you > customised your wordpress installations. (Or in which ways you > *patched* it to make it a little bit less insane than the upstream > version) > >> If anyone can run some update tests see attachment. > > Even if I tested my local toy installation of wordpress (from the > wordpress package) this wouldn't say anything about installations > with whatever configurations and whatever plugins and themes > installed. > > And did anyone notice that an update of wordpress from 3.5 to 3.6 > zaps some outdated but probably still used theme? Guess what'll > happen. People stupid enough using wordpress (because it's so easy > to pkg_add it) will complain that they now get "white pages" [tm].
So we can add a note about this fact in upgrade guide, no? Maintainers are supposed to use packages the're maintaining and they should test at least common update scenarios. BTW, thanks for a hint with white pages ;) > I really think we should stop supporting those "webapps" that just > don't fit into a system distribution but have their own ecosystem > (where users are advised to "ftp" to their "webspace" and similar) Well, for someone it will be a pain to set correct permissions for such updates. And they end up with "chmod -R 777 /var/www/wordpress". > Ciao, > Kili > >
