Summary: | www-apps/otrs: fails to install with correct permissions when using webapp-config | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Beutin <tb> |
Component: | Current packages | Assignee: | Gentoo Web Application Packages Maintainers <web-apps> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | alexanderyt, ferimy, jesse, kspy, lists, patrick, scen |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
otrs-2.3.3_bin_fix.patch
webapp-config error "could not set permissions" + "failed to write content" |
Description
Thomas Beutin
2008-05-06 10:56:07 UTC
I just got this as well. This bug still exists in version 2.3.3 Created attachment 194800 [details, diff]
otrs-2.3.3_bin_fix.patch
Here's a trivial (maybe not elegant) patch to fix this problem :-)
Created attachment 243857 [details]
webapp-config error "could not set permissions" + "failed to write content"
I altered /usr/share/webapps/otrs/2.2.6/hooks/reconfig-2 per the initial comment to the Bug and removed the two directories previously created. Reran the installer, this time no error re: Permissions. However, I did have the error (below modified by replacing real domain with "xxx.domain"): Failed to write content file /var/www/xxx.domain/htdocs/ot/.webapp-otrs-2.3.3! * Error was: 'ascii' codec can't encode characters in position 18434-18437: ordinal not in range(128) I just realized OTRS is now in version 2.4.7, so I'm backing out my install and going the route of creating a custom ebuild so I pull in 2.4.7. Therefore, my previous participation in the bug should be ignored. www-apps/otrs-3.0.10 still does not install correctly. No files get to /usr/share/webapps so webapp-config can't use them. I might try some of your old patches now. Wondering. I'm pretty sure a fix should be applied to otrs and not webapp-config. I'm going to change the title to reflect that. Here it's even not possible to emerge it: bin/otrs.SetPermissions.pl - set OTRS file permissions Copyright (C) 2001-2013 OTRS AG, http://otrs.com/ Setting permissions on /var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10 Error in chown 101 81 /var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10: Operation not permitted * ERROR: www-apps/otrs-3.2.10::gentoo failed (prepare phase): * Could not set permissions * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 2558: Called die * The specific snippet of code: * perl "${S}"/bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=apache --otrs-group=apache --web-group=apache "${S}" || die "Could not set permissions"; * * If you need support, post the output of `emerge --info '=www-apps/otrs-3.2.10::gentoo'`, * the complete build log and the output of `emerge -pqv '=www-apps/otrs-3.2.10::gentoo'`. * The complete build log is located at '/var/tmp/portage/www-apps/otrs-3.2.10/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/www-apps/otrs-3.2.10/temp/environment'. * Working directory: '/var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10/Kernel/Config' * S: '/var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10' Looks like 3.2.10 and all older versions in portage are affected :-( I think this line above chown 101 81 /var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10 should look like chown 101:81 /var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10 But I'm not able to fix this since I don't speak perl by now. Please someone fix this. It's unusable like this. By the way webapp-config support would be great! The same problem on version 3.2.12. * otrs-3.2.12.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking otrs-3.2.12.tar.bz2 to /var/tmp/portage/www-apps/otrs-3.2.12/work >>> Source unpacked in /var/tmp/portage/www-apps/otrs-3.2.12/work >>> Preparing source in /var/tmp/portage/www-apps/otrs-3.2.12/work/otrs-3.2.12 ... bin/otrs.SetPermissions.pl - set OTRS file permissions Copyright (C) 2001-2013 OTRS AG, http://otrs.com/ Setting permissions on /var/tmp/portage/www-apps/otrs-3.2.12/work/otrs-3.2.12 Error in chown 102 81 /var/tmp/portage/www-apps/otrs-3.2.12/work/otrs-3.2.12: Operation not permitted * ERROR: www-apps/otrs-3.2.12::gentoo failed (prepare phase): * Could not set permissions * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 2616: Called die * The specific snippet of code: * perl "${S}"/bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=apache --otrs-group=apache --web-group=apache "${S}" || die "Could not set permissions"; * * If you need support, post the output of `emerge --info '=www-apps/otrs-3.2.12::gentoo'`, * the complete build log and the output of `emerge -pqv '=www-apps/otrs-3.2.12::gentoo'`. * The complete build log is located at '/var/tmp/portage/www-apps/otrs-3.2.12/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/www-apps/otrs-3.2.12/temp/environment'. * Working directory: '/var/tmp/portage/www-apps/otrs-3.2.12/work/otrs-3.2.12/Kernel/Config' * S: '/var/tmp/portage/www-apps/otrs-3.2.12/work/otrs-3.2.12' >>> Failed to emerge www-apps/otrs-3.2.12, Log file: >>> '/var/tmp/portage/www-apps/otrs-3.2.12/temp/build.log' * Messages for package www-apps/otrs-3.2.12: * ERROR: www-apps/otrs-3.2.12::gentoo failed (prepare phase): * Could not set permissions * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 2616: Called die * The specific snippet of code: * perl "${S}"/bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=apache --otrs-group=apache --web-group=apache "${S}" || die "Could not set permissions"; * * If you need support, post the output of `emerge --info '=www-apps/otrs-3.2.12::gentoo'`, * the complete build log and the output of `emerge -pqv '=www-apps/otrs-3.2.12::gentoo'`. * The complete build log is located at '/var/tmp/portage/www-apps/otrs-3.2.12/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/www-apps/otrs-3.2.12/temp/environment'. * Working directory: '/var/tmp/portage/www-apps/otrs-3.2.12/work/otrs-3.2.12/Kernel/Config' * S: '/var/tmp/portage/www-apps/otrs-3.2.12/work/otrs-3.2.12' (In reply to tazinblack from comment #9) > Here it's even not possible to emerge it: > > > > > > > bin/otrs.SetPermissions.pl - set OTRS file permissions > Copyright (C) 2001-2013 OTRS AG, http://otrs.com/ > Setting permissions on /var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10 > Error in chown 101 81 > /var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10: Operation not > permitted > * ERROR: www-apps/otrs-3.2.10::gentoo failed (prepare phase): > * Could not set permissions > * > * Call stack: > * ebuild.sh, line 93: Called src_prepare > * environment, line 2558: Called die > * The specific snippet of code: > * perl "${S}"/bin/otrs.SetPermissions.pl --otrs-user=otrs > --web-user=apache --otrs-group=apache --web-group=apache "${S}" || die > "Could not set permissions"; > * > * If you need support, post the output of `emerge --info > '=www-apps/otrs-3.2.10::gentoo'`, > * the complete build log and the output of `emerge -pqv > '=www-apps/otrs-3.2.10::gentoo'`. > * The complete build log is located at > '/var/tmp/portage/www-apps/otrs-3.2.10/temp/build.log'. > * The ebuild environment file is located at > '/var/tmp/portage/www-apps/otrs-3.2.10/temp/environment'. > * Working directory: > '/var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10/Kernel/Config' > * S: '/var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10' > > > Looks like 3.2.10 and all older versions in portage are affected :-( > > > I think this line above > > chown 101 81 /var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10 > > should look like > > chown 101:81 /var/tmp/portage/www-apps/otrs-3.2.10/work/otrs-3.2.10 > > > But I'm not able to fix this since I don't speak perl by now. > Please someone fix this. It's unusable like this. > > By the way webapp-config support would be great! webapp-config developers do what they can to assist. The issue doesn't seem to be with webapp-config though, at least...what you're showing here. I'll try what I can to reproduce but as Anthony said, it looks like there is an issue with the ebuild. 4.0.13 looks to install |