Package Details: nextcloud-upgrade-hook 1-2

Git Clone URL: (read-only, click to copy)
Package Base: nextcloud-upgrade-hook
Description: Trigger ‘occ upgrade’ and ‘occ maintenance:update:htaccess’ after Nextcloud updates
Upstream URL: None
Submitter: alerque
Maintainer: alerque
Last Packager: alerque
Votes: 1
Popularity: 0.000000
First Submitted: 2021-07-20 11:38 (UTC)
Last Updated: 2021-08-19 07:43 (UTC)

Required by (0)

Sources (2)

Latest Comments

ainola commented on 2021-08-14 00:14 (UTC)

I am going to reject the deletion request.

I personally do not agree to having a package merely add a hook: I'd say it violates the rules of submission:

Make sure the package you want to upload is useful. Will anyone else want to use this package? Is it extremely specialized? If more than a few people would find this package useful, it is appropriate for submission.

However, a cursory search of the AUR shows a lot of packages doing just that. A number of them have lots of votes, even. I can see this package being as useful as e.g. the systemd-boot upgrade hook.

Therefore, I believe this debate demands a discussion on defining whether a package only providing a hook is acceptable in the AUR. As there is precedent set, this belongs here.

alerque commented on 2021-08-07 10:00 (UTC)

@grawlinson Of course YMMV, that's why these hooks are not included by default in the repo packaging. There is a great argument for that, and certainly not everyone who runs Nextcloud will want this. But the same token though a lot of people running Nextcloud won't be running Ansible or any other orchestration tooling and hence may want a package that takes care of the hooks. Hence the popularity of several dozen similar packages apps that have such that have such needs. I'm not saying this is universally useful (otherwise it would belong in the repo packaging) but I am suggesting it can be useful for more than just me, hence why I put it here.

grawlinson commented on 2021-07-24 13:12 (UTC)

A lot of these optional hooks tend to be managed via Ansible or other management tools, so aminvakil isn't completely incorrect.

Personally, I have them in a custom repository (and a couple managed via Ansible playbooks), so YMMV.

aminvakil commented on 2021-07-23 16:29 (UTC) (edited on 2021-07-23 16:29 (UTC) by aminvakil)

@alerque Sorry if I wasn't clear, I didn't mean that if something is in wiki, it shouldn't be packaged, what I meant was there is already a hook to run occ upgrade in nextcloud package and BTW it has also been mentioned in wiki.

I'm not saying this package is useless at all, but other packages that you have mentioned are more broad and can be used by many more users, but I'm not sure if we want to have an upgrade hook for every package.

Either way you're more experienced and become a TU lately (Congrats!), therefore you definitely know this better than me, so I won't push this any further.

alerque commented on 2021-07-23 13:30 (UTC) (edited on 2021-07-23 13:35 (UTC) by alerque)

I think this is too customized to be included in AUR.

@aminvakil I don't think it's too customized at all. There is a good reason the upstream nextcloud package does not enable the hook by default as sometimes there are other upgrade concerns, but the steps here are almost completely universal and for people that do want to run them automatically and to be able to deploy systems 100% with the package manager a hook package in the AUR seems quite a reasonable thing to me.

By your logic would you drop nextcloud-systemd-timers too just because they are also something people can get off the Wiki? How about systemd-boot-pacman-hook? Or pacman-cleanup-hook/paccache-hook? Or docker-hook? Or any number of others that are service restarters? Many/most of these are eminently useful to the people that want to manage their systems that way.

aminvakil commented on 2021-07-21 08:34 (UTC) (edited on 2021-07-21 08:38 (UTC) by aminvakil)

/usr/share/doc/nextcloud/nextcloud.hook :

Exec = /usr/bin/runuser -u nextcloud -- /usr/bin/php /usr/share/webapps/nextcloud/occ upgrade

This is already included in nextcloud package and has been also mentioned in wiki:

I think this is too customized to be included in AUR.