I upgraded from 0.8.4 to 0.9.3 and everything seems ok except that the web browser can not find any css file (at least). It appears that webapp-config-1.11 did not install anything in my webserver trac root (/var/www/foo/htdocs-secure/trac/). Further investigations shows that /usr/share/webapps/trac/0.9.3/htdocs/ is empty (while 0.8.4/htdocs/ is full of files including css files). #emerge -pv trac [ebuild R ] www-apps/trac-0.9.3 -cgi +enscript -fastcgi -postgres +silvercity +sqlite +vhosts 0 kB #emerge --info Portage 2.0.53 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r2 i686) ================================================================= System uname: 2.6.14-gentoo-r2 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg ccache collision-protect distcc distlocks fixpackages sandbox sfperms strict test userpriv usersandbox" GENTOO_MIRRORS="http://mirror.ovh.net/gentoo-distfiles/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo/" LANG="en_US.ISO8859-15" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 apache2 apm arts avi bash-completion berkdb bitmap-fonts bzip2 crypt cups curl eds emboss encode enscript expat fam foomaticdb fortran gd gdbm gif gmp gstreamer gtk2 idn imlib jpeg libg++ libwww mad maildir mikmod mp3 mpeg ncurses nls nptl ogg oggvorbis opengl oss pam pcre pdflib pic png python quicktime readline recode ruby sasl sdl sqlite ssl tcpd test threads tiff truetype truetype-fonts type1-fonts udev vhosts vorbis xml2 xmms xv zlib video_cards_nvidia userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS
You did not follow the post-install instructions; the ebuild is correct and works. http://projects.edgewall.com/trac/wiki/TracInstall
(In reply to comment #1) > You did not follow the post-install instructions; the ebuild is correct and > works. Yes, i did follow the post-install/upgrade instructions and my trac installation *is* working, except for that CSS thing (plus images and javascript of course). If i had not followed thoses instuctions, i would have ended with pyhton handler errors (name change) and DB env files errors (sqlite upgrade) on every trac'd projects of mine. The fact is that i do not see how webapp-config --upgrade could install files in htdocs if /usr/share/webapps/trac/0.9.3/htdocs/ is empty in the first place. But i may be wrong in the way i think webapp-config works. Did i missed something ? Should i re-open the bug myself if i did not ?
As I said, your configuration is incorrect... Relevant snip of configuration with mod_python: DocumentRoot /var/www/example.com/htdocs/trac/test Alias /chrome/common/ /usr/share/trac/htdocs <Location /> SetEnv PYTHON_EGG_CACHE /tmp/eggs SetHandler mod_python PythonHandler trac.web.modpython_frontend PythonOption TracUriRoot / PythonOption TracEnv /var/www/example.com/htdocs/trac/test </Location> The location of files is correct, your config is not. If you have problems, then forums.gentoo.org or #gentoo-apache on Freenode is the right place for questions.
*** Bug 119481 has been marked as a duplicate of this bug. ***
*** Bug 121351 has been marked as a duplicate of this bug. ***
