On 7/3/2024 9:23 AM, Lucio Crusca wrote:
Il 03/07/24 13:48, Jeff Pang ha scritto:
maybe you can use rbenv to install the required ruby toolkit?
I'm afraid that's not the point. I assume that
# apt-get install gitlab
should just work out of the box, or there is a problem, either on my
part, or in the gitlab package itself.
As of now, that command outputs instead:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
gitlab : Depends: ruby-sidekiq (>= 7~) but 6.5.12+dfsg-1 is to be
installed
Depends: ruby-ruby-magic (>= 0.6~)
Depends: ruby-gitlab-labkit (>= 0.35~) but it is not going
to be installed
Recommends: certbot but it is not going to be installed
Recommends: gitaly (>= 16.8~) but it is not going to be
installed
E: Unable to correct problems, you have held broken packages.
I'd like to understand what the problem is and find the correct
solution to that problem.
I don't quite know how I did this but I installed Debian Unstable in
Virtualbox and I tried to install gitlab from contrib repo (unstable)
and got the same results as you. Then I tried to install the broken
dependency from the experimental repo. Then I copied all the broken
dependencies to a text file, told apt to install all the packages in
that file from unstable repo and it installed Gitlab.. I can confirm
that it is installed... it if works is another story and I'm trying to
figure out how exactly I did it. Will get back with more.
