Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 230703 - phpmyadmin ebuild should depend on webapp-config
Summary: phpmyadmin ebuild should depend on webapp-config
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-04 06:13 UTC by Mark D.
Modified: 2009-01-02 17:27 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark D. 2008-07-04 06:13:46 UTC
When I try to install phpmyadmin-2.11.7 without the webapp-config package installed, I get this nasty error message:

 * checking auxfile checksums ;-) ...                                                                                       [ ok ]
 * checking miscfile checksums ;-) ...                                                                                      [ ok ]
 * checking phpMyAdmin-2.11.7-all-languages-utf-8-only.tar.bz2 ;-) ...                                                      [ ok ]
Traceback (most recent call last):
  File "/usr/sbin/webapp-config", line 27, in <module>
    from WebappConfig.config import Config
ImportError: No module named WebappConfig.config
 * 
 * ERROR: dev-db/phpmyadmin-2.11.7 failed.
 * Call stack:
 *                  ebuild.sh, line   49:  Called pkg_setup
 *   phpmyadmin-2.11.7.ebuild, line   24:  Called webapp_pkg_setup
 *              webapp.eclass, line  378:  Called webapp_read_config
 *              webapp.eclass, line   60:  Called die
 * The specific snippet of code:
 *   		ENVVAR=$(${WEBAPP_CONFIG} --query ${PN} ${PVR}) || die "Could not read settings from webapp-config!"
 *  The die message:
 *   Could not read settings from webapp-config!


I would expect the phpmyadmin emerge to pull in webapp-config as a pre-requisite, so everything just works!

Reproducible: Always

Steps to Reproduce:
Comment 1 Mark D. 2008-07-04 06:19:55 UTC
Sorry, it's a problem with upgrading to python 2.5 without rebuilding my python modules.
Comment 2 hacker angelm 2009-01-02 03:42:36 UTC
please be more specific.
Packages rebuild?
You could command line measurements to use.

(In reply to comment #0)
> When I try to install phpmyadmin-2.11.7 without the webapp-config package
> installed, I get this nasty error message:
> 
>  * checking auxfile checksums ;-) ...                                          
>                                             [ ok ]
>  * checking miscfile checksums ;-) ...                                         
>                                             [ ok ]
>  * checking phpMyAdmin-2.11.7-all-languages-utf-8-only.tar.bz2 ;-) ...         
>                                             [ ok ]
> Traceback (most recent call last):
>   File "/usr/sbin/webapp-config", line 27, in <module>
>     from WebappConfig.config import Config
> ImportError: No module named WebappConfig.config
>  * 
>  * ERROR: dev-db/phpmyadmin-2.11.7 failed.
>  * Call stack:
>  *                  ebuild.sh, line   49:  Called pkg_setup
>  *   phpmyadmin-2.11.7.ebuild, line   24:  Called webapp_pkg_setup
>  *              webapp.eclass, line  378:  Called webapp_read_config
>  *              webapp.eclass, line   60:  Called die
>  * The specific snippet of code:
>  *              ENVVAR=$(${WEBAPP_CONFIG} --query ${PN} ${PVR}) || die "Could
> not read settings from webapp-config!"
>  *  The die message:
>  *   Could not read settings from webapp-config!
> 
> 
> I would expect the phpmyadmin emerge to pull in webapp-config as a
> pre-requisite, so everything just works!
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 

(In reply to comment #1)
> Sorry, it's a problem with upgrading to python 2.5 without rebuilding my python
> modules.
> 

(In reply to comment #1)
> Sorry, it's a problem with upgrading to python 2.5 without rebuilding my python
> modules.
> 

Comment 3 Mark D. 2009-01-02 06:00:56 UTC
Use the python-updater command line tool to fix python, after it's been updated.
Comment 4 hacker angelm 2009-01-02 17:27:36 UTC
(Mark Deepwell) Your solution for this bug is correct:
# python-updater