Discussion:
Installing gitlab on sid
(too old to reply)
Lucio Crusca
2024-07-03 10:30:01 UTC
Permalink
I'm trying to install gitlab from sid, but it requires ruby-sidekiq>=7~,
which is not available in sid (there's only 6.5.12 available).

Am I doing anything wrong or should I file a bug report?
Jeff Pang
2024-07-03 11:50:01 UTC
Permalink
maybe you can use rbenv to install the required ruby toolkit?
Post by Lucio Crusca
I'm trying to install gitlab from sid, but it requires ruby-sidekiq>=7~,
which is not available in sid (there's only 6.5.12 available).
--
Jeff Pang
***@SimpleMail.co.in
Lucio Crusca
2024-07-03 14:30:01 UTC
Permalink
Post by Jeff Pang
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.
Dan Ritter
2024-07-03 14:50:01 UTC
Permalink
Post by Lucio Crusca
Post by Jeff Pang
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.
You're running sid; being broken is expected. Talk to the maintainer.

-dsr-
Henning Follmann
2024-07-03 15:00:01 UTC
Permalink
Post by Lucio Crusca
Post by Jeff Pang
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.
You are using unstable!
Post by Lucio Crusca
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.
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.
The error message is very transparent about this: "...if you are using the
unstable ..."
Post by Lucio Crusca
I'd like to understand what the problem is and find the correct solution to
that problem.
Well maybe you just have to wait until the package might be available. But
you never know. It might take a while...

-H
--
Henning Follmann | ***@itcfollmann.com
Lucio Crusca
2024-07-03 15:20:01 UTC
Permalink
Post by Henning Follmann
The error message is very transparent about this: "...if you are using the
unstable ..."
You are absolutely right. But I never stopped by to read that message
and it's the first time in years of sid (mixed with testing and stable)
that this thing bites me... I've always skipped the bla bla bla and
headed to the informations below, in order to manually solve
dependencies (impossible in this case).

My fault. Sorry.

Loading...