Community Packages

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!
Tasklist

FS#38528 - [owncloud] Upgrading to 6.0.0.a-3 requires manual intervention

Attached to Project: Community Packages
Opened by Sardelli Tommaso (cippaciong) - Wednesday, 15 January 2014, 14:56 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 21 January 2014, 12:35 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Upgrading to owncloud 6.0.0a-3 from a previous install is impossible without manual intervention and results in this error:

error: failed to commit transaction (conflicting files)
owncloud: /usr/share/webapps/owncloud/config exists in filesystem
Errors occurred, no packages were upgraded.

The error is caused by this recent change:
+ # move config to /etc
+ mv ${pkgdir}/usr/share/webapps/owncloud/config ${pkgdir}/etc/webapps/${pkgname}/config
+ chown -R http:http ${pkgdir}/etc/webapps/${pkgname}/config
+ ln -s /etc/webapps/${pkgname}/config ${pkgdir}/usr/share/webapps/owncloud/config

Additional info:
* package version(s)
owncloud (6.0.0.a-1 -> 6.0.0.a-3)

* config and/or log files etc.


Steps to reproduce:
Just upgrade owncloud from a previous install with config file located at /usr/share/webapps/owncloud/config
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 21 January 2014, 12:35 GMT
Reason for closing:  Not a bug
Comment by Sergej Pupykin (sergej) - Wednesday, 15 January 2014, 17:50 GMT
As I know pacman cannot move directory with modified by user config files, so it is feature.

Rename/move config dir manually, upgrade and merge.
Comment by Sardelli Tommaso (cippaciong) - Wednesday, 15 January 2014, 18:58 GMT
That's what i did but i think users should be warned. Someone may not know how to handle the problem.
Comment by rainer (raneon) - Wednesday, 15 January 2014, 23:16 GMT
Actually I didn't expect issues during the "hotfix" upgrade, but merge and considering file permissions of the new config example did the trick. Thanks
Comment by Sergej Pupykin (sergej) - Thursday, 16 January 2014, 07:40 GMT
I think merge was not complete. Probably you need to adjust apache config.

apache.example.conf now contains /etc/webapps in open_basedif for php.

https://projects.archlinux.org/svntogit/community.git/tree/trunk/apache.example.conf?h=packages/owncloud
Comment by Michael Holder (ls48hol) - Friday, 17 January 2014, 12:58 GMT
If you use simple configuration (linking owncloud to Document Root) you need to adopt /etc/php/php.ini:
add /etc/webapps/owncloud to open_basedir config line.
Comment by Sardelli Tommaso (cippaciong) - Friday, 17 January 2014, 17:45 GMT
I missed the point if anything will be done about the upgrading problem.
Comment by Sergej Pupykin (sergej) - Tuesday, 21 January 2014, 12:35 GMT
Users cannot be informed about manual intervention from package because pacman checks for file conflict before upgrading. Wiki page is the single way I think. Hopefully Arch users are quick-witted :)

Loading...