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#49238 - [gitlab] /usr/share/doc/database.yml.* files empty

Attached to Project: Community Packages
Opened by Nick (nanny) - Friday, 06 May 2016, 17:56 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 07 May 2016, 15:43 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

gitlab 8.7.2-8

The installation of gitlab says:

>Copy a database example config from /usr/share/doc/gitlab/ to /etc/webapps/gitlab/database.yml and configure it

However, those database.yml files are empty.

Off topic: Overall, I've had a ton of trouble with this package since it was moved from aur to community. I came across this empty file error when I was reinstalling, because I was having a different problem (LoadError, could not load /usr/share/webapps/lib/gitlab/redis). Perhaps the move to community should be re-evaluated, because right now it feels to me like it's not being executed as smoothly as it could be.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Saturday, 07 May 2016, 15:43 GMT
Reason for closing:  Fixed
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 07 May 2016, 15:20 GMT
Thanks for the report, fixing ASAP.

To your addendum: You have to view this package by itself without having any connection to the old AUR packages. We do not offer migration paths for previously unsupported packages. In other words: The gitlab in [community] is not the one in AUR. I agree, the first few days weren't smooth but keep in mind that gitlab is a really, really complex package and I'm doing my best to maintain it properly. Just keep on reporting bugs and we'll get there.

I'm running this package in production myself so if you keep having problems, make a backup and restore into a clean installation. It should work fine then.

Loading...