FS#53100 - [nextcloud] nextcloud: /usr/share/webapps/nextcloud/config exists in filesystem

Attached to Project: Community Packages
Opened by BoBeR182 (BoBeR182) - Monday, 27 February 2017, 21:31 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 13 March 2017, 11:07 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Updating with pacman -Syu causes conflict.
nextcloud: /usr/share/webapps/nextcloud/config exists in filesystem

Additional info:
* package version(s)
community/nextcloud 11.0.1-1 -> 11.0.2-1

Steps to reproduce:
pacman -Syu
This task depends upon

Closed by  Sergej Pupykin (sergej)
Monday, 13 March 2017, 11:07 GMT
Reason for closing:  Not a bug
Comment by bobpaul (bobpaul) - Tuesday, 28 February 2017, 18:52 GMT
pacman -Qo reports that the directory /usr/share/webapps/nextcloud/config/ is owned by nextcloud 11.0.1-1
pacman -Qo also shows that the file /usr/share/webapps/nextcloud/config/config.sample.php is owned by nextcloud 11.0.1-1, but not config.php (which IIRC was created during initial setup). The update via pacman -Syu only complains about the directory.

Removing /usr/share/webapps/nextcloud/config/config.php allowed the upgrade to continue, but then nextcloud obviously lost all configuration. This seems incorrect; I don't have to move/delete my config files when upgrading other packages. Would it not be better for nextcloud to own the sample config but not the runtime config, like in previous versions of the package? If the nextcloud package owns the runtime config.php (which is necessarily modified by usage), then I'll have to repeat this every time I update the nextcloud package.
Comment by Sergej Pupykin (sergej) - Tuesday, 28 February 2017, 19:04 GMT
I've just upgraded from 11.0.1 to 11.0.2, but on armv7h. So cannot reproduce.
Did your 11.0.1 was installed from aur?
Comment by Andreas (uboot) - Tuesday, 28 February 2017, 20:46 GMT
I have exactly the same problem when trying to upgrade from 11.0.1-1 on armv7h (Raspberry Pi 2) and Google brought me to this bug ticket.

And no: nextcloud wasn't installed from aur.
Comment by bobpaul (bobpaul) - Tuesday, 28 February 2017, 20:54 GMT
I'm sorry, you are correct. I thought the error was that community/nextcloud 11.0.2 now includes config.php, but that is not the case. I see that pacman -Qo still shows no package owns config.php, even after install 11.0.2

I can reproduce the error by installing aur/nextcloud (currently 11.0.1) and then running pacman -Su. If I install community/nextcloud version 11.0.1-1 from archlinux archive, I cannot produce the error.
Comment by bobpaul (bobpaul) - Tuesday, 28 February 2017, 20:57 GMT
Andreas, do you use pacaur, yaourt, or another aur helper? community/nextcloud and aur/nextcloud have the same name. I think in my case I installed aur/nextcloud without noticing.

Edit: Actually, it looks like community/nextcloud is a new package as of earlier this month. I installed nextcloud in the fall, so I obviously installed from AUR back then. Here's more details on the upgrade issue cause by upgrading from the AUR package to the community package: https://bugs.archlinux.org/task/52791#comment155476
Comment by Andreas (uboot) - Wednesday, 01 March 2017, 06:58 GMT
Ok, it seems that my nextcloud was from aur, so I'm sorry too. I mistook it with owncloud, which has been in community for some time...

I moved config-directory to ~/config and then upgraded without problems. config is now a symlink to /etc/webapps/nextcloud/config which is more reasonable than before.

Ticket can be closed.

Loading...