Unmet dependencies debian buster

After running apt-get install certbot python-certbot-apache as root I get the following output. However, I could not solve the problem.

Reading package lists... Done
Building dependency tree
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:
 certbot : Depends: python3-certbot (= 0.31.0-1) but it is not going to be installed
 python-certbot-apache : Depends: python3-certbot-apache but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

It also does not work with the -f option.

1 Like

Hmmm… that’s not great. :thinking:

Are you using raspbian?

You could try using snap, but I’m not sure if that will mesh with your system:

Unfortunately, no, not really. I’m running Gentoo and actually don’t have much experience with apt. Although I do use it on my Raspberry Pi’s though, this isn’t something I have had earlier.

2 Likes

Saw the python piece and thought you had dealt with similar in other topics.

It’s not really a Python issue unfortunately :wink:

In any case, I’m interested in what the following would do:

apt-get install python3-certbot

Or more interested in: what error do you get. Unfortunately, I’m not seeing any “verbose” option for apt-get… IMO it’s a stupid design choice not to offer the user any information or clue what’s wrong. It just states “it’s not going to be installed”… BUT WHY?!? We need an actual helpful error message darn it!

2 Likes

Even credit card companies give some reasons. :grin:

1 Like

I have tried apt-get install python3-certbot and get the following output:

Reading package lists... Done
Building dependency tree
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:
 python3-certbot : Depends: python3-acme (>= 0.29.0~) but it is not going to be installed
                   Depends: python3-cryptography (>= 1.2.3) but it is not going to be installed
                   Depends: python3-josepy but it is not going to be installed
                   Depends: python3-mock but it is not going to be installed
                   Depends: python3-parsedatetime (>= 1.3) but it is not going to be installed
                   Depends: python3-zope.component but it is not going to be installed
                   Depends: python3-zope.interface but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Additionally the following output with debug: apt-get install certbot python-certbot-apache -f -oDebug::pkgProblemResolver=true

Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 6
Starting 2 pkgProblemResolver with broken count: 6
Investigating (0) python3-cryptography:amd64 < none -> 2.6.1-3+deb10u2 @un uN Ib >
Broken python3-cryptography:amd64 Depends on python3-cffi-backend-api-min:amd64 < none @un H > (<= 9729)
  Considering python3-cffi-backend:amd64 0 as a solution to python3-cryptography:amd64 7
  Holding Back python3-cryptography:amd64 rather than change python3-cffi-backend-api-min:amd64
Investigating (0) python3-openssl:amd64 < none -> 19.0.0-1 @un uN Ib >
Broken python3-openssl:amd64 Depends on python3-cryptography:amd64 < none | 2.6.1-3+deb10u2 @un uH > (>= 2.3)
  Considering python3-cryptography:amd64 7 as a solution to python3-openssl:amd64 3
  Holding Back python3-openssl:amd64 rather than change python3-cryptography:amd64
Investigating (0) python3-josepy:amd64 < none -> 1.1.0-2 @un uN Ib >
Broken python3-josepy:amd64 Depends on python3-cryptography:amd64 < none | 2.6.1-3+deb10u2 @un uH > (>= 0.8)
  Considering python3-cryptography:amd64 7 as a solution to python3-josepy:amd64 3
  Holding Back python3-josepy:amd64 rather than change python3-cryptography:amd64
Investigating (0) python3-zope.component:amd64 < none -> 4.3.0-1 @un uN Ib >
Broken python3-zope.component:amd64 Depends on python3-zope.hookable:amd64 < none | 4.0.4-4+b4 @un uH >
  Considering python3-zope.hookable:amd64 1 as a solution to python3-zope.component:amd64 2
  Holding Back python3-zope.component:amd64 rather than change python3-zope.hookable:amd64
Investigating (0) python3-certbot:amd64 < none -> 0.31.0-1 @un uN Ib >
Broken python3-certbot:amd64 Depends on python3-cryptography:amd64 < none | 2.6.1-3+deb10u2 @un uH > (>= 1.2.3)
  Considering python3-cryptography:amd64 7 as a solution to python3-certbot:amd64 2
  Holding Back python3-certbot:amd64 rather than change python3-cryptography:amd64
Investigating (0) python3-acme:amd64 < none -> 0.31.0-2 @un uN Ib >
Broken python3-acme:amd64 Depends on python3-openssl:amd64 < none | 19.0.0-1 @un uH > (>= 0.15)
  Considering python3-openssl:amd64 3 as a solution to python3-acme:amd64 2
  Holding Back python3-acme:amd64 rather than change python3-openssl:amd64
Investigating (0) python3-certbot-apache:amd64 < none -> 0.31.0-1 @un uN Ib >
Broken python3-certbot-apache:amd64 Depends on python3-acme:amd64 < none | 0.31.0-2 @un uH > (>= 0.25.0~)
  Considering python3-acme:amd64 2 as a solution to python3-certbot-apache:amd64 0
  Holding Back python3-certbot-apache:amd64 rather than change python3-acme:amd64
Investigating (0) python3-future:amd64 < none -> 0.16.0-1 @un uN Ib >
Broken python3-future:amd64 Depends on python3-lib2to3:amd64 < none | 3.7.3-1 @un uH >
  Considering python3-lib2to3:amd64 1 as a solution to python3-future:amd64 0
  Holding Back python3-future:amd64 rather than change python3-lib2to3:amd64
Investigating (0) python3-setuptools:amd64 < none -> 40.8.0-1 @un uN Ib >
Broken python3-setuptools:amd64 Depends on python3-distutils:amd64 < none | 3.7.3-1 @un uH >
  Considering python3-distutils:amd64 1 as a solution to python3-setuptools:amd64 0
  Holding Back python3-setuptools:amd64 rather than change python3-distutils:amd64
Investigating (1) certbot:amd64 < none -> 0.31.0-1 @un puN Ib >
Broken certbot:amd64 Depends on python3-certbot:amd64 < none | 0.31.0-1 @un uH > (= 0.31.0-1)
  Considering python3-certbot:amd64 2 as a solution to certbot:amd64 10002
    Reinst Failed early because of python3:amd64
    Reinst Failed because of python3-cffi-backend:amd64
    Reinst Failed because of python3-cryptography:amd64
    Reinst Failed because of python3-openssl:amd64
    Reinst Failed because of python3-acme:amd64
Investigating (1) python-certbot-apache:amd64 < none -> 0.31.0-1 @un puN Ib >
Broken python-certbot-apache:amd64 Depends on python3-certbot-apache:amd64 < none | 0.31.0-1 @un uH >
  Considering python3-certbot-apache:amd64 0 as a solution to python-certbot-apache:amd64 9999
    Reinst Failed because of python3-acme:amd64
Investigating (1) python3-pbr:amd64 < none -> 4.2.0-5 @un uN Ib >
Broken python3-pbr:amd64 Depends on python3-setuptools:amd64 < none | 40.8.0-1 @un uH >
  Considering python3-setuptools:amd64 0 as a solution to python3-pbr:amd64 2
  Holding Back python3-pbr:amd64 rather than change python3-setuptools:amd64
Investigating (1) python3-parsedatetime:amd64 < none -> 2.4-2 @un uN Ib >
Broken python3-parsedatetime:amd64 Depends on python3-future:amd64 < none | 0.16.0-1 @un uH >
  Considering python3-future:amd64 0 as a solution to python3-parsedatetime:amd64 1
  Holding Back python3-parsedatetime:amd64 rather than change python3-future:amd64
Investigating (2) certbot:amd64 < none -> 0.31.0-1 @un puN Ib >
Broken certbot:amd64 Depends on python3-certbot:amd64 < none | 0.31.0-1 @un uH > (= 0.31.0-1)
  Considering python3-certbot:amd64 2 as a solution to certbot:amd64 10002
Investigating (2) python-certbot-apache:amd64 < none -> 0.31.0-1 @un puN Ib >
Broken python-certbot-apache:amd64 Depends on python3-certbot-apache:amd64 < none | 0.31.0-1 @un uH >
  Considering python3-certbot-apache:amd64 0 as a solution to python-certbot-apache:amd64 9999
Investigating (2) python3-mock:amd64 < none -> 2.0.0-4 @un uN Ib >
Broken python3-mock:amd64 Depends on python3-pbr:amd64 < none | 4.2.0-5 @un uH > (>= 1.3)
  Considering python3-pbr:amd64 2 as a solution to python3-mock:amd64 4
  Holding Back python3-mock:amd64 rather than change python3-pbr:amd64
Investigating (3) certbot:amd64 < none -> 0.31.0-1 @un puN Ib >
Broken certbot:amd64 Depends on python3-certbot:amd64 < none | 0.31.0-1 @un uH > (= 0.31.0-1)
  Considering python3-certbot:amd64 2 as a solution to certbot:amd64 10002
Investigating (3) python-certbot-apache:amd64 < none -> 0.31.0-1 @un puN Ib >
Broken python-certbot-apache:amd64 Depends on python3-certbot-apache:amd64 < none | 0.31.0-1 @un uH >
  Considering python3-certbot-apache:amd64 0 as a solution to python-certbot-apache:amd64 9999
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:
 certbot : Depends: python3-certbot (= 0.31.0-1) but it is not going to be installed
 python-certbot-apache : Depends: python3-certbot-apache but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

is this the right one where you need it?
As a system I do not use raspberry pi, but debian buster on an industrial server.

2 Likes

To me, without having very much experience with this like I said, stands out: what’s wrong with python3? Is python3 even installed? Could you check?

2 Likes

I have uninstalled python3 and reinstalled it with the certbot. This solved the problem.
Thanks a lot :smiley:

2 Likes

Seriously? Glad it worked out, but I have no idea why :grimacing:

2 Likes

Yes, the browser has verified it and python3 works again.
I also have no idea why it works now. But now it works.

And you know: don’t touch the running System :wink:

2 Likes

@Osiris

I can feel the rage from here. :flushed: So beneficial yet anticlimactic and unsettling. Eh doctor? :wink:

Told you it was a python issue you’d help fix… :face_with_hand_over_mouth:

1 Like

Still thinking this was an aptitude issue.

I guess that is true :stuck_out_tongue:

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.