Community Packages

Please read this before reporting a bug:

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#63679 - [gitlab] gitlab-backup fails when gitlab-pages isn't installed

Attached to Project: Community Packages
Opened by simonzack (simonzack) - Saturday, 07 September 2019, 04:43 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 28 December 2019, 09:13 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Anatol Pomozov (anatolik)
Caleb Maclennan (alerque)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No


gitlab-backup fails when gitlab-pages isn't installed.

I would rather not install gitlab-pages, as it's quite a big package, at 478MiB, since it requires `go` being installed.

It is possible to skip backup up of pages by doing `ExecStart=/usr/bin/bundle-2.5 exec rake gitlab:backup:create SKIP=pages`.

Maybe this command could be used instead if it detects that gitlab-pages isn't installed?
This task depends upon

Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 22 September 2019, 02:19 GMT
I was unaware that you can even have the option to not install gitlab-pages. How do I go about testing that?
Comment by simonzack (simonzack) - Friday, 28 February 2020, 12:03 GMT
You can just install `gitlab` without `gitlab-pages`. Then you can setup GitLab (a repo maybe), and run `gitlab-backup.service`.

The dependencies for `gitlab` doesn't include `gitlab-pages`. `gitlab-pages` is in the AUR for some reason.
Comment by Jakub Klinkovsk√Ĺ (lahwaacz) - Sunday, 03 May 2020, 08:16 GMT
This is quite ironic, because as far as I know, gitlab-pages cannot be set up on the same domain as the main gitlab...
Comment by Caleb Maclennan (alerque) - Saturday, 08 May 2021, 08:20 GMT
Jakub, it cannot (without twisting its arm) be setup to run on the same domain, but that is mostly an SSL certificate handling and cookie scope issue. There is no problem running Gitlab Pages on the same server and IP as the main GitLab instance.
Comment by Caleb Maclennan (alerque) - Saturday, 08 May 2021, 08:22 GMT
Also Anatol, I can totally see not wanting to install services you don't use (and I support that) but I will just mention that you don't have to install go to install gitlab-pages. It is only a makedepends not a depends. You can compile a package on another machine and it will run fine without Go because it is a static compiled binary with no dependencies, or you can build it on the same machine, then uninstall the makedepends after you build. You could also install it from my user repo[1] which has precompiled packages, the package is 4.6M over the wire and 13.9M installed. (But I agree you shouldn't need to install services you don't want.)

Comment by simonzack (simonzack) - Saturday, 08 May 2021, 08:54 GMT
In my current setup I just disabled `gitlab-backup.timer`, since I have no need for this, nor `gitlab-pages`.

To do this, I copied `/usr/lib/systemd/system/` to `/etc/systemd/system/` and removed `gitlab-backup.timer` from it's file contents.
Comment by Caleb Maclennan (alerque) - Saturday, 08 May 2021, 09:40 GMT
I just did some testing on a new machine before installing pages and was able to run the backups as long as the directory for GitLab Pages that is configured in /etc/webaps/gitlab/gitlab.yml exists. The Pages package and service doesn't need to exist, just the directory that they would use if they did.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.