When installing otrs via webapp-config after emerging the application the following error occurs: my.host.name # webapp-config -I -h my.host.name -d otrs otrs 1.3.1 sed: can't read /var/www/my.host.name//Kernel/Config.pm: No such file or directory sed: can't read /var/www/my.host.name//scripts/*: No such file or directory /usr/share/webapps/otrs/1.3.1/hooks/reconfig-1.3.1: line 7: /var/www/my.host.name//bin/SetPermissions.sh: No such file or directory *********************************************************** Your installation is almost complete. 1. You now need to edit /var/www/my.host.name//Kernel/Config.pm and setsome Kernel::Config options (FQDN, SystemID, TicketHook, Home, ...). *********************************************************** 2. Configure and restart your webserver. Read /usr/share/doc//README.webserver.gz. Sample config files are in /var/www/my.host.name//scripts *********************************************************** 3. Setup your database. Read /usr/share/doc//README.database.gz *********************************************************** 4. Read /usr/share/doc//INSTALL.gz , pp. 9-12, to finish the installation. If you are upgrading, read /usr/share/doc//UPGRADING.gz When attempting to remove this application the following occures: my.host.name # webapp-config -C -h my.host.name -d otrsotrs 1.3.1 --- !found /var/www/my.host.name/cgi-bin/otrs/customer.pl --- !found /var/www/my.host.name/cgi-bin/otrs/faq.pl --- !found /var/www/my.host.name/cgi-bin/otrs/index.pl --- !found /var/www/my.host.name/cgi-bin/otrs/installer.pl --- !found /var/www/my.host.name/cgi-bin/otrs/pic.pl --- cfgpro file /var/www/my.host.name/otrs-1.3.1/Kernel/Config.pm --- !empty dir /var/www/my.host.name/otrs-1.3.1/Kernel --- !empty dir /var/www/my.host.name/otrs-1.3.1 --- !empty dir /var/www/my.host.name/icons --- !empty dir /var/www/my.host.name/error --- !found /var/www/my.host.name/cgi-bin/otrs/cpanel --- !found /var/www/my.host.name/cgi-bin/otrs --- !found /var/www/my.host.name/cgi-bin * Remove whatever is listed above by hand Ironically it seems to remove cgi-bin completely regardless of if its empty or not. Reproducible: Always Steps to Reproduce: 1. USE="vhosts" emerge otrs-1.3.1 2. webapp-config -I -h my.host.name -d otrs otrs 1.3.1 3. To reproduce the uninstall/clean webapp-config -C -h my.host.name -d otrs otrs 1.3.1 Actual Results: The application failed to install properly Expected Results: Applcation should have been installed to the <hostname> directory via webapp-config.
Looking at the reconfig script for this it's using ${P} which isn't being expanded in the output below. I think this should be ${VHOST_APPDIR} but I'm not sure.
Firstly, portage and webapp-config versions? Thanks for reporting. I'm talking to Stu (who wrote webapp.eclass) to see what's the best way to resolve this. Incidentally, the removal of cgi-bin is also because ${PN} is blank when -C is called, which is a bit weird.
Here are my webapp and portage versions net-www/webapp-config-1.10-r11 sys-apps/portage-2.0.50-r11 Let me know if you need anything else, I figured the CGI-BIN removal was a -C call but since it wasn't empty I figured that could be labeled an unintended bug...
Created attachment 45508 [details] OTRS 1.3.2 ebuild updated and working with webapp-config This is a updated ebuild for otrs version 1.3.2 with this and the associated other files I'm attaching you should be able to both install otrs and uninstall it without the problems which originally plagued this ebuild. I do have this working with mod_perl as thats my preferred host system. The original ebuild forced fcgi and while I'm not sure I did it right I'm hoping this will use either fcgi or mod_perl or just plain perl. Perhaps a better ebuild hacker can check this for me. DEPEND and RDEPEND have been double checked and I've been free with comments so that anyone using this in its current form can see the method to my madness. In cases where either of these two sections were pulling in or requireing more then they needed I documented what I removed or added and why. The optional use of GD wasn't enabled in the ebuild so a new IUSE flag for gd has been put in and if enabled is used for stats generation. Bugs so far: - RELEASE is looked at whenever you go to otrs/index.pl so it needs to be copied to the vhost directory or the application needs to be modified to look for it in the /usr/share/doc directory - Apache2 w/ Mod_perl seems to work but requires some significant editing until I have template files or a automated way to get the necessary files to work with webapp-config or just the ebuild itself. The files that need to be edited or create are: - 76_otrs.conf which goes in /etc/apache/conf/modules.d and contains the information usually placed in the apache conf file. This works well for a single installation which I'm currently testing but won't function well for multiple installations so need to find a work around for that. - apache2-perl-startup.pl needs to be edited to reflect the actual location of otrs when it is installed. As with the file above changing the default script to point to the actual location works but this does not work with webapp-config. I am not sure if or how mod_perl works thus I am not sure if we were to call this file multiple times once per vhost installation if that would bork things or not. - Permissions for using this software via the webserver may not be completely correct. Specifically using the installer.pl requires you give at least group read write permission to the Config.pm file and change the group to be the web server. I am a little concerned that the file defaults to be 644 since it does contain passwords. perhaps a better change would be to 660 and chgrp the *.pm files so only the otrs user and the webserver can see their contents. Finally I am uploading the following files: 76_otrs.conf postinstall-en-1.3.2.txt
Created attachment 45509 [details] Webapp-config postinstall file for 1.3.2 of Otrs
Created attachment 45510 [details] 76_otrs.conf placed in /etc/apache2/conf/modules.d/ so that apache upon startup pulls this in. Not sure this is the right way to do it but it works right now....
Created attachment 52638 [details] Updated Apache2 OTRS config file, uses IfDefined Derived from: http://bugs.gentoo.org/attachment.cgi?id=45510&action=view
I'm just about to check out different trouble ticket systems. I noticed otrs-1.3.2 has been out for a while. If I get down to actually installing the tool, I'll report on how the suggested ebuilds work with that newer version.
sorry, forget about this silly comment of mine... lunch has drawn any blood from my brain further down. I believed the ebuild above were for 1.3.1... 8-|
Ok, I there we go: I have used the ebuild as suggested in this bug. In the end, I got it running, even though not exactly with the setup I'm used to. In the end, I have started with the ebuild for otrs-1.3.1 found in portage. I figured there were only some modifications to get the beast going. I don't experience the issue in bug #66792. RELEASE is moved to where otrs looks for it. Permissions are handled by the reconfig script (as in 1.3.1). I'll attach another version of the ebuild, the postinstall-text and the reconfig script.
Created attachment 56058 [details] Variant of www-apps/otrs-1.3.2.ebuild
Created attachment 56059 [details] Variant of postinstall-en-1.3.2.txt
Created attachment 56060 [details] Variant of reconfig-1.3.2
Created attachment 56061 [details] Variant of 76_otrs.conf Note: Copy 76_otrs.conf into /etc/apache2/conf/modules.d if your setup roughly matches mine: apache2 with fastcgi but no mod_perl. The ebuild doesn't handle this file but it's mentioned in the postinstall-en text file
Sorry for kinda hijacking the bug. Those ebuilds don't really solve the bug, yet webapp-config -C -d /otrs works with them and with webapp-config-1.10-r11.
I am looking at otrs in a production environment, however I notice 1.3.2 is the latest yet 1.3.1 is what is in portage. And also it's ~arch masked. This bug has been open for quite a while, any chance this might get wrapped up?
Hello, I tried something but I always get: Can't locate Kernel/Config.pm in @INC (@INC contains: /var/www/localhost/cgi-bin/otrs/../../Kernel/cpan-lib /var/www/localhost/cgi-bin/otrs/../.. /etc/perl /usr/lib/perl5/site_perl/5.8.5/i686-linux /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.5/i686-linux /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.5/i686-linux /usr/lib/perl5/5.8.5 /usr/local/lib/site_perl .) at /var/www/localhost/cgi-bin/otrs/installer.pl line 42. [Wed May 18 19:40:20 2005] [error] [client 127.0.0.1] BEGIN failed--compilation aborted at /var/www/localhost/cgi-bin/otrs/installer.pl line 42. regards Roland
Folks, 1.3.2 and 2.0.1 are now in Portage. Please test, and report any problems. Closing for now, please reopen if necessary.
