Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Debian Testing (Trixie) can't install - libgconf-2-4 dependency not available in repos #26082

Open
dspadea opened this issue Dec 27, 2023 · 1 comment · May be fixed by #26149 or #26525
Open

Debian Testing (Trixie) can't install - libgconf-2-4 dependency not available in repos #26082

dspadea opened this issue Dec 27, 2023 · 1 comment · May be fixed by #26149 or #26525

Comments

@dspadea
Copy link

dspadea commented Dec 27, 2023 •
edited

Seems like Debian Testing (Trixie) can no longer install Keybase due to missing libgconf dependency. Are there work-arounds / fixes in the works? I did some googling for fixes, and also looked in the issues as best I could. I didn't see anything related.

$ sudo apt install keybase
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:
 keybase : Depends: libgconf-2-4 but it is not installable
E: Unable to correct problems, you have held broken packages.

$ cat /etc/apt/sources.list.d/keybase.list
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb [signed-by=/usr/share/keyrings/keybase-keyring.gpg] http://prerelease.keybase.io/deb stable main
@dspadea
Copy link
Author

dspadea commented Dec 27, 2023 •
edited

Just to avoid any red herrings, note that I did migrate my keyring to an external file from trusted.gpg due to warnings from Apt, but this problem has existed for a while, long before I did that. I'm not getting any signature issues.

@RyanZim RyanZim linked a pull request Jan 9, 2024 that will close this issue
Open
@vorlock vorlock linked a pull request Apr 9, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@dspadea