Created attachment 375494 [details] emerge --info when installing phpmyadmin i got the following error: * phpMyAdmin-4.1.8-all-languages.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] [31;01m* [39;49;00m[31;01mFatal error: [39;49;00mThe config file /etc/vhosts/webapp-config appears to be for an older version of webapp-config. [31;01m* [39;49;00m[31;01mFatal error: [39;49;00mMaybe you need to etc-update? [31;01m* [39;49;00m[31;01mFatal error: [39;49;00m/etc/vhosts/webapp-config needs updating! [31;01m* [39;49;00m[31;01mFatal error(s) - aborting[39;49;00m * ERROR: dev-db/phpmyadmin-4.1.8::gentoo failed (setup phase): full error log can be found here: http://bpaste.net/show/nP5dtuGFX6ijbp5DVM7X/. and my /etc/vhosts/webapp-config content here: http://bpaste.net/show/wWCQoZTnLXKwYdgKfmIJ/.
1) Please attach the entire build log to this bug report. 2) Please attach /etc/vhosts/webapp-config to this bug report.
Created attachment 375602 [details] emerge phpmyadmin
Created attachment 375606 [details] /etc/vhosts/webapp-config
(In reply to qinghao from comment #3) > Created attachment 375606 [details] > /etc/vhosts/webapp-config That appears to be the default. File permissions?
I'm not sure what's going on here. What verison of webapp-config are you using? I was not able to reproduce using webapp-config-1.52-r1 or 1.53. Also, as jer suggested, what are the permissions on /etc/vhosts/webapp-config?
Created attachment 375690 [details] webapp-config --version run webapp-config individually always reports that error, no matter what options or arguments is given. * Fatal error: The config file /etc/vhosts/webapp-config appears to be for an older version of webapp-config. * Fatal error: Maybe you need to etc-update? * Fatal error: /etc/vhosts/webapp-config needs updating! * Fatal error(s) - aborting
(In reply to qinghao from comment #6) > Created attachment 375690 [details] > webapp-config --version > > run webapp-config individually always reports that error, no matter what > options or arguments is given. > > * Fatal error: The config file /etc/vhosts/webapp-config appears to be for > an older version of webapp-config. > * Fatal error: Maybe you need to etc-update? > * Fatal error: /etc/vhosts/webapp-config needs updating! > * Fatal error(s) - aborting What version are you using?
Created attachment 375692 [details] eix webapp-config
Created attachment 375694 [details] /etc/apache2/vhosts.d/00_default_vhost.conf
Created attachment 375696 [details] eix tomcat
>Also, as jer suggested, what are the permissions on /etc/vhosts/webapp-config? -rw-r--r-- 1 root root 8121 Apr 22 00:06 /etc/vhosts/webapp-config >I'm not sure what's going on here. What verison of webapp-config are you using? I was not able to reproduce using webapp-config-1.52-r1 or 1.53. i am using 1.52-r1 as attachment eix_webapp-config.log === does vhosts in apache matter? === i don't know what is webapp-config. but "vhosts" reminds me that i have configured several vhosts on my machine in Apache as listed attachment 00_default_vhost.conf. that's all the content of that file which have been overwritten be mis-typed edit command in vim accidentally.
(In reply to qinghao from comment #11) > >Also, as jer suggested, what are the permissions on /etc/vhosts/webapp-config? > -rw-r--r-- 1 root root 8121 Apr 22 00:06 /etc/vhosts/webapp-config > > >I'm not sure what's going on here. What verison of webapp-config are you using? I was not able to reproduce using webapp-config-1.52-r1 or 1.53. > i am using 1.52-r1 as attachment eix_webapp-config.log > > > === does vhosts in apache matter? === > i don't know what is webapp-config. but "vhosts" reminds me that i have > configured several vhosts on my machine in Apache as listed attachment > 00_default_vhost.conf. that's all the content of that file which have been > overwritten be mis-typed edit command in vim accidentally. vhost in apache does not matter directly. You're getting "No option 'wa_conf_version' in section: 'USER'" and yet in your config file you have WA_CONF_VERSION="7". The caps shouldn't matter. Try the following: 1) Edit /etc/vhosts/webapp-config and switch to upper to lower case so you have wa_conf_version="7" 2) If you still get "No option 'wa_conf_version' in section: 'USER'" then edit the following file: /usr/lib64/python3.3/site-packages/WebappConfig/config.py replacing 3.3 with whatever version of python you are using. Just above the lines that read: if (self.config.get('USER', 'wa_conf_version') != self.config.get('USER', 'my_conf_version')): add the following line print("DEBUG %s" % self.config.get('USER', 'wa_conf_version')) Then run something like `webapp-config --li` (or any webapp-config command which causes the config file to be read) and you should see a line that looks like DEBUG 7 Please report what you get.
Created attachment 375710 [details] webapp-config --li have changed WA_CONF_VERSION to wa_conf_version it seems the script did not get that value correctly.
There's no need to add an attachment when you just want to show a few lines of output. For reference: [31;01m* [39;49;00m[31;01mFatal error: [39;49;00mThe config file /etc/vhosts/webapp-config appears to be for an older version of webapp-config. [31;01m* [39;49;00m[31;01mFatal error: [39;49;00mMaybe you need to etc-update? [31;01m* [39;49;00m[31;01mFatal error: [39;49;00m/etc/vhosts/webapp-config needs updating! [31;01m* [39;49;00m[31;01mFatal error(s) - aborting[39;49;00m [33;01m* [39;49;00m [33;01m* [39;49;00mThere is a problem with your configuration file or an environment variable. [33;01m* [39;49;00mwebapp-config tried to read the variable "wa_conf_version" [33;01m* [39;49;00mand received the following error: [33;01m* [39;49;00m [33;01m* [39;49;00mNo option 'wa_conf_version' in section: 'USER' [33;01m* [39;49;00mPlease note that webapp-config is not written in bash anymore [33;01m* [39;49;00mand that you cannot use the bash scripting features. DEBUG [33;01m* [39;49;00m [33;01m* [39;49;00mThere is a problem with your configuration file or an environment variable. [33;01m* [39;49;00mwebapp-config tried to read the variable "wa_conf_version" [33;01m* [39;49;00mand received the following error: [33;01m* [39;49;00m [33;01m* [39;49;00mNo option 'wa_conf_version' in section: 'USER' [33;01m* [39;49;00mPlease note that webapp-config is not written in bash anymore [33;01m* [39;49;00mand that you cannot use the bash scripting features. Have you tried running etc-update / dispatch-conf? Does it try to update the config file? If you have portage-utils and haven't cleaned /var/log/emerge.log, it could be interesting to check the output of "qlop -l webapp-config". Another option is to backup the /etc/vhosts/webapp-config file, remove it and reinstall webapp-config. Does this error go away? If so, a diff between the existing file and the one installed by webapp-config would also be interesting.
>Have you tried running etc-update / dispatch-conf? Does it try to update the config file? i tried both just now. have run etc-update before merge config files sudo etc-update Scanning Configuration files... Exiting: Nothing left to do; exiting. :) and run dispatch-conf the first time. it asked about the config about /etc/crontab. >If you have portage-utils and haven't cleaned /var/log/emerge.log, it could be >interesting to check the output of "qlop -l webapp-config". qlop -l webapp-config given this prompt Wed Apr 16 00:43:52 2014 >>> [32;01mapp-admin/webapp-config-1.52-r1[00;00m Thu Apr 17 22:50:44 2014 >>> [32;01mapp-admin/webapp-config-1.52-r1[00;00m Tue Apr 22 00:08:04 2014 >>> [32;01mapp-admin/webapp-config-1.52-r1[00;00m >Another option is to backup the /etc/vhosts/webapp-config file, remove it and reinstall webapp-config. Does this error go away? have tried this. but errors are still there. sudo rm /etc/vhosts/webapp-config sudo emerge webapp-config sudo emerge phpmyadmin <-- this failed same errors. >If so, a diff between the existing file and the one installed by webapp-config would also be interesting. nothing different.
(In reply to qinghao from comment #15) > >Have you tried running etc-update / dispatch-conf? Does it try to update the config file? That's not what's going on. We can tell from comment #3 that his config file is fine. The problem is occurring around line 815 of WebappConfig/config.py, see my comment #12. The if succeeds: self.config.get('USER', 'wa_conf_version') != self.config.get('USER', 'my_conf_version') meaning that wa_conf_version is not equal to my_conf_version which is set to '7' on line line 232 as part of __init__ for class Config. In fact wa_conf_version is not set at all: No option 'wa_conf_version' in section: 'USER' And yet, in his config file, he has: wa_conf_version="7" Since I can't reproduce this and he can't get rid of it by re-emerging, it sounds to me like there some cruft laying around that is getting imported. (In reply to qinghao from comment #15) Can you try step 2 of comment #12. Also, can I see what you get for `eselect python list`. Finally, for good measure, try `python-updater`
Created attachment 375792 [details] sudo python-updater when set as 2.7 >Can you try step 2 of comment #12. Also, can I see what you get for `eselect >python list`. Finally, for good measure, try `python-updater` sudo eselect python list Available Python interpreters: [1] python2.7 [2] python3.2 * [3] python3.3 running `sudo python-updater` under 3.2 report error about no module portage. ImportError: No module named portage and some subsequence errors. the switch to 2.7 sudo eselect python set python2.7 python-updater works with errors as python-updater_2.7.log
I seem to have similar problem. It goes away when setting default python to 3.3 and goes back when setting python 2.7
Is this issue sill occurring? I can't seem to reproduce.
(In reply to Lukasz Ligowski from comment #18) > I seem to have similar problem. It goes away when setting default python to > 3.3 and goes back when setting python 2.7 Seeing as this is the issue I'm fairly certain this has to do with dev-python/configparser being installed on the users' systems. This being the case is very likely so I'm going to mark this bug as a duplicate of bug #528752 which goes into more detail regarding the issue at hand. *** This bug has been marked as a duplicate of bug 528752 ***
