Replies: 1 comment 8 replies
-
|
Thanks for raising attention to this! |
Beta Was this translation helpful? Give feedback.
-
|
There's no way of re-publishing a package, but I will try to push a new v5 version soon, which should solve the problem. I'll let you know. |
Beta Was this translation helpful? Give feedback.
-
|
I just tried to switch to while my .sources file looks like this: But running Maybe this is helpful: nodesource/distributions#1865 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
I spent many hours trying to find a solution. Took the wrong path of thinking I can update my signing key on Launchpad with support of a strong hashing algorithm. Then I learned launchpad uses its own key (59EBDE772980C381CA13FA59FAF1020699503176) that I have no control over. And, Launchpad doesn't support a binding signature. I may be wrong in these discoveries to some extent because I have limited knowledge of how Launchpad works. I will revisit this issue before 2026-02-01T00:00:00Z when SHA1 support expires. |
Beta Was this translation helpful? Give feedback.
-
|
Frustrating. Thank you for all effort put on this @gornostal |
Beta Was this translation helpful? Give feedback.
-
|
Looks like you're right and the Launchpad team has to fix this. Thanks for your efforts! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
On Debian 13 I'm getting the following warning when running
sudo apt update --audit:The signing key needs to be updated by the packager.
Also, the Debian installation instructions aren't correct anymore after
.sources(deb822 format) is the new default now, instead of.list.Beta Was this translation helpful? Give feedback.
All reactions