Update to Debian Trixie#1069
Merged
Merged
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Owner
Author
+ apt-get update
Get:1 http://deb.debian.org/debian trixie InRelease [138 kB]
Get:2 http://deb.debian.org/debian trixie-updates InRelease [47.1 kB]
Get:3 http://deb.debian.org/debian-security trixie-security InRelease [43.4 kB]
Get:4 http://deb.debian.org/debian trixie/main amd64 Packages [9668 kB]
Get:5 http://deb.debian.org/debian trixie-updates/main amd64 Packages [2432 B]
Get:6 http://deb.debian.org/debian-security trixie-security/main amd64 Packages [5304 B]
Get:7 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease [29.1 kB]
Err:7 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DB085A08CA13B8ACB917E0F6D938EC0D038651BD is not bound: primary key because: No binding signature at time 2025-07-24T20:19:54Z because: Policy rejected non-revocation signature (PositiveCertification) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z
Reading package lists...
W: OpenPGP signature verification failed: https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DB085A08CA13B8ACB917E0F6D938EC0D038651BD is not bound: primary key because: No binding signature at time 2025-07-24T20:19:54Z because: Policy rejected non-revocation signature (PositiveCertification) requiring collision resistance because: SHA1 is not considered secure since 2013-02-01T00:00:00Z
E: The repository 'https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease' is not signed.Lovely, good fun. |
Owner
Author
|
A few Go deps which are on older versions than will see Trixie, which will be fun to navigate. Also, Docker Desktop seems to be failing to start with this again, so that's going to be fun to try and track down. |
Owner
Author
In an adorable twist, it's apparently just Electron failing this time - the VM and even the API proxy are up and working just fine. |
Owner
Author
|
Docker Desktop was just a couple missing libraries - now fixed. 👍 |
2bf16d8 to
47adafb
Compare
Owner
Author
|
Added a temporary workaround for |
With the notable exception of Slack
Owner
Author
|
I could do more, like |
This was referenced Aug 13, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.