Moinmoin 1.3.2 is out, this is a huge upgrade to the currently available version, 1.2.3, no ebuilds are available at the moment Reproducible: Always Steps to Reproduce: 1. emerge sync && emerge -p moinmoin Actual Results: Shows me version 1.2.3 is the highest version available Expected Results: I can't get any version better than 1.2.3, even if I add "www-apps/moinmoin ~x86" to /etc/portage/package.keywords
Actually the newest MoinMoin available is 1.3.1. The www-apps/moinmoin-1.2.3 package survives a version bump to 1.3.1, but www-apps/moinmoin-1.2.3-r1 does not (it uses webapp-config stuff)
what's the holdup? all that has to be done is: # cp /usr/portage/www-apps/moinmoin/moinmoin-1.2.3.ebuild /usr/portage/www-apps/moinmoin/moinmoin-1.3.1.ebuild # ebuild /usr/portage/www-apps/moinmoin/moinmoin-1.3.1.ebuild digest
> what's the holdup? This would work as a duct-tape solution, but in reality MoinMoin should start supporting webapp-config. And it wouldn't probably work for people who already have 1.2.3-r1 installed.
I tried bumping 1.2.3-r1 to 1.3.2 and it seemed to work okay. Anyone else verify, and if so, I'll commit.
Does your ebuild overwrite htdocs/moinmoin/moin_config.py, or does it create an appropriate ._cfg*moin_config.py file?
It overwrites - I found a few other issues that aren't addressed in the ebuild as well, so I'll plan to attach a proposed one as soon as I get them worked out.
At 2005-02-01 20:40 PST John Altstadt wrote: > Does your ebuild overwrite htdocs/moinmoin/moin_config.py You're encouraged to create your own wiki instance as per http://moinmaster.wikiwikiweb.de/HelpOnInstalling/WikiInstanceCreation With MoinMoin 1.3 it is much easier to update a separate instance because of the underlay directory.
1.3.3 is in portage now, but it's hard-masked for testing. Please note that upgrading from 1.2.x to 1.3.x is non-trivial.
emerged moinmoin with or without use of vhosts. 'webapp-config -I -d /mywiki -v -p moinmoin 1.3.3' outputs: /usr/sbin/webapp-config: line 2916: fn_version_verify: command not found Is this a moinmoin or a webapp-config problem?
> 'webapp-config -I -d /mywiki -v -p moinmoin 1.3.3' outputs: > /usr/sbin/webapp-config: line 2916: fn_version_verify: command not found > Is this a moinmoin or a webapp-config problem? This looks like a webapp-config problem, I don't think it expects the version parameter to be used when installing a webapp. If you want verbose you should use --verbose or -V (capital V).
It seems like the underlay directory needs to be server owned. After installing moinmoin it gives this message: "data_underlay_dir" does not exists at "./underlay/", or has incorrect ownership and permissions. Which is fixed by changing the permissions on underlay to be owned by the webserver.
Experienced the same as Scott Hadfield. Everything else works perfectly...
CAUTION: Although moinmoin-1.3.3 seems to be SLOTed differently, it messes up (overwrites) the files in "site-packages". Be ready to experience problems when trying to run both 1.2.x and 1.3.x
Version 1.3.4 has been out for a couple of weeks. I locally bumped the ebuild for 1.3.3 to 1.3.4. It compiled well and in the end I got it running nicely. A couple of remarks/suggestions: 1) Permissions of ./underlay I experienced the same issue as Scott in comment #11. His solution works for me. 2) I guess there is a bug in postinstall-en.txt. I believe it should be as follows: --- postinstall-en.txt 2005-03-24 13:22:24.000000000 +0100 +++ postinstall-en.txt.new 2005-03-28 21:29:02.000000000 +0200 @@ -4,7 +4,7 @@ 1. ExecCGI needs to be enabled in your Moinmoin directory. You con do this by simply # echo "Options ExecCGI" > ${MY_INSTALLDIR}/.htaccess -# echo "AddHandler cgi-script .cgi" > ${MY_INSTALLDIR}/.htaccess +# echo "AddHandler cgi-script .cgi" >> ${MY_INSTALLDIR}/.htaccess 2. Add the following lines to your Apache configs: Alias /wiki "${MY_INSTALLDIR}" 3) I wasn't quite sure on how to install several wiki pages on the same host. As Marti notes (comment #7) , the moin way of doing that kinda makes webapp-config obsolete (for the given ebuild ;-). However, webapp-config seems to be the gentooish-way - and the ebuild prepares for this as far as I understand it. I settled using webapp-config and it works fine. I'm not sure if this is more resource intensive than the moin way. Maybe somebody could comment on how this is meant to be in Gentoo. Maybe even in the postinstall text. 4) If the webapp-config way is the way to choose, the ebuild might replace the dummy path in line 16 of moin.cgi like s/'\/path\/to\/wikiconfig'/./ I don't know if this can be done by webapp-config. Would make more sense than having this change already in /usr/share/webapps...
webapp-config seems to be hard-linking the wiki_config.py file which leads to ALL your wikis having the SAME configuration. ...or maybe I just didn't get how to use webapp-config... :-( ...never liked it anyway...
I might have missed that because my /usr/share/webapps and my /var/www used to be on different partitions. In that case it copies the files as opposed to (hard) linking them. (I have since moved /usr/share/webapps to /var/www/webapps and symlinked it to /usr/share/webapps - as suggested by `man webapp-config`. Didn't reinstall the wikis though). Is Radeks issue a bug in the ebuild - and can thus be corrected? Naturally the configs should be copies and not hardlinks.
MoinMoin 1.3 won't provide RSS support without PyXML installed as described in their CHANGES file: http://moinmoin.wikiwikiweb.de/MoinMoinRelease1.3/CHANGES I'm not sure what the best solution is for this, but perhaps it should have the option of an RSS USE flag that will install PyXML if set.
moinmoin-1.3.5 is out (bugfix release) I have successfully bumped the current ebuild 1.3.3. Compiled fine and works nicely so far. Of course all the issues detailed in this thread still apply...
1.3.5 is in the tree 1. wikiconfig.py is no longer overwritten 2. underlay directory is owned by webserver 3. moinmoin is now MANUAL_SLOTted, SLOT=0, and blocks previous versions. This should solve the upgrading issue 4. Urs' comments in #14 have been addressed 5. the hardlinking issue is resolved as the file is marked as webapp_configfile and therefore always copied, not hardlinked 6. added rss USE flag Please test and reopen if necessary.