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#52185 - [gitlab] PKGBUILD should not use gid and uid integer values but names

Attached to Project: Community Packages
Opened by Robert Obermeier (Obbi) - Saturday, 17 December 2016, 09:37 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 17 December 2016, 14:05 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
140: install -dm750 -o 105 -g 105 "${pkgdir}${_homedir}"
141: install -dm750 -o 105 -g 105 "${pkgdir}${_homedir}/satellites"
142: install -dm750 -o 105 -g 105 "${pkgdir}${_homedir}/shared/"{,artifacts,lfs-objects}
143: install -dm750 -o 105 -g 105 "${pkgdir}${_homedir}/builds"
144: install -dm750 -o 105 -g 105 "${pkgdir}${_homedir}/uploads"
145: install -dm750 -o 105 -g 105 "${pkgdir}${_homedir}/backups"
146: install -dm750 -o 105 -g 105 "${pkgdir}${_etcdir}"
160: chown root:105 "${pkgdir}${_etcdir}/gitlab_workhorse_secret"
189: chown 105:105 "${pkgdir}${_datadir}/db/schema.rb"

Those should use gitlab and gitlab:gitlab

132: depends+=('gitlab-shell>=4.0.0')

should be moved to depends at top.

I guess someone had a reason to do this, but I couldn't figure out why.

Additional info:
* gitlab 8.14.5-1 (basically every version since the package came to community)


Steps to reproduce:
create gitlab user and group manually, then
install gitlab

That is the setup if one had gitlab installed when it was an AUR package.
Pacman basically just upgraded gitlab from an AUR package on my side and I had to fix a lot then. But I refuse changing user and group ids, cause this package should not require those in the first place.

Btw. same should apply to gitlab-shell
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 17 December 2016, 14:05 GMT
Reason for closing:  Not a bug
Comment by Robert Obermeier (Obbi) - Saturday, 17 December 2016, 10:00 GMT
Ok I guess it's just the tar xf that pacman install is that breaks if it's not 105.

But I still doesn't explain why pacman only enforces ownership of files and ignores directories (140-146) on upgrade.

Loading...