FS#36254 - [dokuwiki] Upgrading dokuwiki fails do to a filesystem conflict.

Attached to Project: Community Packages
Opened by Michael (M1Sports20) - Tuesday, 23 July 2013, 13:40 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 06 August 2013, 13:06 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 2
Private No

Details

I have dokuwiki 20130510-2 installed. When upgrading to version dokuwiki 20130510-3 I am getting a file system conflict. The conflict, which are existing files, are owned by the dokuwiki package itself.

Log:
(38/38) loading package files
(38/38) checking for file conflicts
error: failed to commit transaction (conflicting files)
dokuwiki: /usr/share/webapps/dokuwiki/lib/plugins exists in filesystem

[root@XXX lib]# pacman -Qo /usr/share/webapps/dokuwiki/lib/plugins
/usr/share/webapps/dokuwiki/lib/plugins is owned by dokuwiki 20130510-2
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 06 August 2013, 13:06 GMT
Reason for closing:  Not a bug
Comment by Ethan Zonca (normaldotcom) - Wednesday, 24 July 2013, 14:30 GMT
I'm getting the same issue, but the tpl error is also giving me trouble:

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

scmsrv # pacman -Qo /usr/share/webapps/dokuwiki/lib/plugins
/usr/share/webapps/dokuwiki/lib/plugins is owned by dokuwiki 20130510-2
scmsrv # pacman -Qo /usr/share/webapps/dokuwiki/lib/tpl
/usr/share/webapps/dokuwiki/lib/tpl is owned by dokuwiki 20130510-2
Comment by Sergej Pupykin (sergej) - Thursday, 25 July 2013, 09:09 GMT
It is because of manually installed plugins/templates. Now plugins and tpl dirs are in /var/..., so you need temporary remove manually installed stuff.
Comment by Michael (M1Sports20) - Thursday, 25 July 2013, 17:24 GMT
I don't mind doing and this is what I did to get around the problem for now.
It just seems wrong that you have to do this manual intervention every time you upgrade the package. Is there not a better way of doing this, there may not be, just wondering.
Comment by Sergej Pupykin (sergej) - Friday, 26 July 2013, 10:46 GMT
I don't think that this is 'every time intervention'. It should happen only one time because of moving files from /usr to /var

Loading...