Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#45227 - [owncloud] [owncloud-app-*] Follow upstream packaging recommendations?
Attached to Project:
Community Packages
Opened by Bastien Traverse (Neitsab) - Saturday, 06 June 2015, 10:33 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 02 October 2015, 11:08 GMT
Opened by Bastien Traverse (Neitsab) - Saturday, 06 June 2015, 10:33 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 02 October 2015, 11:08 GMT
|
DetailsDescription:
Conversation with upstream in a GitHub issue [1] revealed two things pertaining to Arch: - they frown upon creating packages for apps, and rather expect users to install them only from the OC app store [2]; - they warn against relying on GitHub tags to build packages, as they consider them WIP until a final announcement is made at https://owncloud.org/changelog/ [3]. Personally I'm quite happy with the way it currently is in Arch since it allowed us to benefit from a fix for a longstanding issue [4], but since I know Arch's philosophy values upstream views I felt I had to bring this up here. [1] https://github.com/owncloud/calendar/issues/714 [2] https://github.com/owncloud/calendar/issues/714#issuecomment-98466281 [3] https://github.com/owncloud/calendar/issues/714#issuecomment-109562686 [4] https://github.com/owncloud/calendar/issues/714#issuecomment-109562507 |
This task depends upon
Closed by Sergej Pupykin (sergej)
Friday, 02 October 2015, 11:08 GMT
Reason for closing: Fixed
Additional comments about closing: should be fixed
Friday, 02 October 2015, 11:08 GMT
Reason for closing: Fixed
Additional comments about closing: should be fixed
The git tags include all files - including some README files end up in the installation app folder:
/usr/share/webapps/owncloud/apps/issue_template.md
/usr/share/webapps/owncloud/apps/MAINTAINERS.md
/usr/share/webapps/owncloud/apps/build.xml
/usr/share/webapps/owncloud/apps/CONTRIBUTING.md
/usr/share/webapps/owncloud/apps/README
This leads to a php error:
Jul 05 16:17:28 owncloud ownCloud[12709]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/issue_template.md/appinfo/app.php) is not within the allowed path(s): (/srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/:/srv/owncloud/data) at /usr/share/webapps/owncloud/lib/private/app.php#776
sept. 26 18:17:14 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/CONTRIBUTING.md/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:14 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/README/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:14 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/issue_template.md/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:14 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/MAINTAINERS.md/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:14 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/build.xml/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:15 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/CONTRIBUTING.md/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:15 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/README/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:15 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/issue_template.md/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:15 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/MAINTAINERS.md/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
sept. 26 18:17:15 hostname ownCloud[811]: {PHP} is_file(): open_basedir restriction in effect. File(/usr/share/webapps/owncloud/apps/build.xml/appinfo/info.xml) is not within the allowed path(s): (/tmp/:/usr/share/webapps/:/etc/webapps/:/home/owncloud/:/dev/urandom) at /usr/share/webapps/owncloud/lib/private/app.php#788
Could we have the input of the maintainer on this issue?