I get the following message after updating roundcube which I think is a bug: * Running /usr/sbin/webapp-cleaner -p -C /roundcube * Package name must be in the form CATEGORY/PN
Please post your `emerge --info' output in a comment.
Is this a command you are running yourself? The problem is that the command should be executed as such: webapp-cleaner -p -C roundcube notice there is no forward slash in the PN. Or alternatively it can be executed like this: webapp-cleaner -p -C mail-client/roundcube where the category of the package is specified along with the package name. So if this is something you executed by yourself I hope this resolves the issue. If it's through a package then that's another story.
From the looks of your output it looks like it is through a package and not by yourself. May I have the roundcube version number, along with the python version you are using?
This happened while updating from roundcube-0.9.4 to 0.9.5. # emerge -pv python [ebuild R ] dev-lang/python-3.2.5-r3:3.2 USE="gdbm hardened ncurses readline ssl threads (wide-unicode) xml -build -doc -examples -ipv6 -sqlite -tk -wininst" 0 kB
When checking for your python version it's a poor choice to see based on the version portage is trying to install. See my example below: portable_enigmatic ~ # emerge -avq python [ebuild R ] dev-lang/python-3.2.5-r3 USE="gdbm ipv6 ncurses readline sqlite ssl threads (wide-unicode) xml -build -doc -examples -hardened -tk -wininst" Would you like to merge these packages? [Yes/No] n Quitting. Now see this: portable_enigmatic ~ # eselect python list Available Python interpreters: [1] python2.7 [2] python3.2 * It shows that the current python version being used is 3.2, which is would be true. But when I set the version I python that I want to run to 2.7 instead of 3.2 portable_enigmatic ~ # eselect python set 1 and I try and check the python version through portage it'll still display 3.2. portable_enigmatic ~ # emerge -avq python [ebuild R ] dev-lang/python-3.2.5-r3 USE="gdbm ipv6 ncurses readline sqlite ssl threads (wide-unicode) xml -build -doc -examples -hardened -tk -wininst" So when checking for the running verison of python it's best to check through eselect instead of portage. Now I believe the issue is probably because of python3.2 and we've been working on adding compatibility for python3.2 with webapp-config. So shortly a newer version should be out which should fix issues caused by people using webapp-config under the python3.2 interpreter.
Thank you for taking the time to explain. I have the following so you are correct: # eselect python list Available Python interpreters: [1] python2.7 [2] python3.2 *
(In reply to A. Person from comment #6) > Thank you for taking the time to explain. I have the following so you are > correct: > > # eselect python list > Available Python interpreters: > [1] python2.7 > [2] python3.2 * The issue might be because you are globally using python3.2. The only version compatible with python3.0+ is webapp-config-1.52 which was just pushed to the portage tree earlier today. I suggest emerging this version, testing it out, and trying to repeat the steps that caused this bug. If you try to do it and you don't get the same bug then it was likely due to that. If not then it might be something I overlooked. Nonetheless, please do let me know how it turns out.
Ouch. I gave you 'eselect python list' from the wrong system. Here is it from the correct system: # eselect python list Available Python interpreters: [1] python2.6 [2] python2.7 * [3] python3.1 [4] python3.2 I'm sorry about that. I emerged webapp-config-1.52 to test anyway but now emerge roundcube seems to hang here with webapp-config-1.52 and 1.51-r1 so I don't know what's going on: >>> Install roundcube-0.9.5 into /var/tmp/portage/mail-client/roundcube-0.9.5/image/ category mail-client Any idea why it would hang like this?
It wasn't hanging, just taking a very long time. But I still get the same error with either version of webapp-config.
Does this issue still persist? I believe it might have been a problem with the ebuild.
I just tested emerging roundcube and I get the same thing: * Running /usr/sbin/webapp-cleaner -p -C /roundcube * Package name must be in the form CATEGORY/PN
(In reply to A. Person from comment #11) > I just tested emerging roundcube and I get the same thing: > > * Running /usr/sbin/webapp-cleaner -p -C /roundcube > * Package name must be in the form CATEGORY/PN I can't seem to reproduce.
Hey, same problem since forever (check the last 2 lines of emerge output). It always appears when updating phpmyadmin. [emerge output] * vhosts USE flag not set - auto-installing using webapp-config * This is an upgrade * phpmyadmin-4.2.13.1 is already installed - upgrading * Running /usr/sbin/webapp-config -U -h localhost -u root -d /phpmyadmin phpmyadmin 4.3.12 * Upgrading /phpmyadmin-4.2.13.1 to /phpmyadmin-4.3.12 * Installed by root on 2015-01-21 20:57:03 * Config files owned by 0:988 --- /var/www/localhost/htdocs/phpmyadmin * Remove whatever is listed above by hand * Creating required directories * Linking in required files * This can take several minutes for larger apps * Files and directories installed * Install completed - success * Running /usr/sbin/webapp-cleaner -p -C /phpmyadmin * Package name must be in the form CATEGORY/PN [/emerge output]
This is fixed in the newest webapp.eclass which is currently on the tree. Marking as resolved.
