| Summary: | www-apps/trac-0.11.2 not able to access sqlite database | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | kavol |
| Component: | [OLD] Server | Assignee: | Gentoo Web Application Packages Maintainers <web-apps> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
kavol
2008-11-21 09:20:05 UTC
one more note, I have found that the solution recommended at the trac site is to chown the file to apache:apache but in that case, the file still would be inaccessible by tracd, which runs as the user tracd I wonder if this has any reasonable solution(*) ... but anyway, IMHO having a setup which does not work in any way is worse than prefering setting one owner over the other, thus having only one not working but the second working (*) maybe adding tracd to the apache group, chowning to apache:apache to be consistent with the upstream preferred name/group and setting write permission for the group? As far as I can tell you run tracd *OR* apache. Not both at the same time. So this is indeed a configuration issue on your side that we cannot catch during install time. I know that setup of some tools is not an out-of-the box installation. While portage can do a lot it does not make too much sense to try to put every little detail into it. At some point also the packages itself need to provide decent configuration management tools. Closing as invalid. (In reply to comment #2) > As far as I can tell you run tracd *OR* apache. Not both at the same time. correct (if *OR* == XOR ;-)) > So this is indeed a configuration issue on your side that we cannot catch > during install time. not correct during install time, I can specify some use flags ... and if one of them is "apache2" (see the bug #247709), then you can safely assume that I want to use apache (mod python) mode if I have it set and that I want to use tracd mode otherwise > I know that setup of some tools is not an out-of-the box installation. While > portage can do a lot it does not make too much sense to try to put every little > detail into it. At some point also the packages itself need to provide decent > configuration management tools. ok, then pass it upstream, if you think that the solution should be provided by the package itself - I, as an user, cannot decide where exactly is the borderline (although I am inclined to think that the upstream has nothing to do with users and groups created by ebuilds ...) > Closing as invalid. if you do not feel like fixing that, then at least please handle this report correctly - reading http://bugs.gentoo.org/page.cgi?id=fields.html#resolution this is either WONTFIX or UPSTREAM ... you can hardly tell that there is no error at all if the application throws an exception (In reply to comment #3) > > So this is indeed a configuration issue on your side that we cannot catch > > during install time. > > not correct > > during install time, I can specify some use flags ... and if one of them is > "apache2" (see the bug #247709), then you can safely assume that I want to use > apache (mod python) mode if I have it set and that I want to use tracd mode > otherwise Probably right. But then, please, update your patch in bug 247709. > ok, then pass it upstream, if you think that the solution should be provided > by the package itself This is system administrator duties, so why bother upstream? > > Closing as invalid. > > if you do not feel like fixing that, then at least please handle this report > correctly - reading http://bugs.gentoo.org/page.cgi?id=fields.html#resolution > this is either WONTFIX or UPSTREAM ... Ok, let's look at that page: UPSTREAM: It is not suitable to deal with the bug at this level, and the bug should be taken to the upstream developers for resolution. WONTFIX: The problem described is a bug which will never be fixed. INVALID: The problem described is not a bug. This but is really INVALID since this is *not a bug*. Neither in application (they have easy_install tool so probably it does everything required), nor in our ebuild (yes, we can add apache2 feature as you described in bug 247709, but this feature is not yet in portage tree). > you can hardly tell that there is no > error at all if the application throws an exception This exception is result of misconfiguration. Currently portage does not provide possibility to install trac with apache2 out of box, so there is no surprise you have to configure your system manually for that. We'll consider adding apache2 USE flag and personally I'm all for adding that. But this is feature request and we already discussing it in another bug. So let's continue working on apache2 support for trac in bug 247709. |
