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!
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!
FS#50651 - Gitlab package version 8.11.4 upgrade breaks with existing installation
Attached to Project:
Arch Linux
Opened by Edvard Holst (Zygote) - Sunday, 04 September 2016, 13:28 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 18 September 2016, 13:36 GMT
Opened by Edvard Holst (Zygote) - Sunday, 04 September 2016, 13:28 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 18 September 2016, 13:36 GMT
|
DetailsDescription:
This is the third time a gitlab package upgrade renders my existing installation completely broken. When upgrading from 8.10.6-1 to 8.11.4-1 a new ruby-bundler 1.12.5-1 dependency is added which conflicts with the existing bundler install resulting in the issues as shown in the attached pacman.log file. Even if I force-install the package it renders the gitlab install in a broken state where gitlab returns 500 errors whenever you try to access it and log files complain about redis not responding. Additional info: * gitlab 8.11.4-1 (this issue was introduced a while ago in a previous version though but I cant recall which one exactly) Steps to reproduce: Attempt an upgrade from gitlab 8.10.6 to 8.11.x. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 18 September 2016, 13:36 GMT
Reason for closing: Not a bug
Additional comments about closing: Files put in the filesystem outside of pacman are not a packaging problem.
Sunday, 18 September 2016, 13:36 GMT
Reason for closing: Not a bug
Additional comments about closing: Files put in the filesystem outside of pacman are not a packaging problem.
Comment by Doug Newgard (Scimmia) -
Sunday, 04 September 2016, 14:38 GMT
And where did all of those files come from?
Comment by Edvard Holst (Zygote) -
Sunday, 04 September 2016, 16:49 GMT
Cant really say for sure from the top of my head. pacman -Qo just states that no package owns the files.
Comment by Edvard Holst (Zygote) -
Sunday, 04 September 2016, 16:50 GMT
However, as I followed the Arch Linux wiki when installing Gitlab I'll assume they came from this instruction: https://wiki.archlinux.org/index.php/gitlab#Initialize_Gitlab_database
pacman.log