jens-lody-debian-keyring

[oneiric]

Greetings,

Using apt-get install jens-lody-debian-keyring doesn't work. How does one install the keyring? (I'm running Debian 10.)

Thanks.

[stahta01]

Did you add his repository? And, then update the packages?

Tim S.

[oneiric]

Tim,

Yes. I've completed installing Buster (belatedly) and I'm in the midst of reinstalling everything. I've updated sources.list and run apt-get update/upgrade.

This is the result when I try to add the keyring:
root@debian:/home/oneiric# apt-get update
. . .
W: GPG error: https://apt.jenslody.de/stable stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C5C6563A3CCA431B
E: The repository 'https://apt.jenslody.de/stable stable Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure( manpage for repository creation and user configuration details.

root@debian:/home/oneiric# apt-get install jens-lody-debian-keyring
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package jens-lody-debian-keyring
root@debian:/home/oneiric#

[oneiric]

cont'd

This is the sources.list entry for the repository:

# Code::Blocks packages (SVN build) using apt
deb [arch=amd64,i386] https://apt.jenslody.de/stable stable main
deb-src https://apt.jenslody.de/stable stable main

[stahta01]

Going to need to wait for a Debian expert to tell you how to get around the issue.

Edit: You might read and try https://askubuntu.com/questions/732985/force-update-from-unsigned-repository

Tim S.

[oBFusCATed]

At the bottom of the https://apt.jenslody.de/ you find this text

Nevertheless, if you want to contact me directly, you can send me an E-Mail or a Personal Message via the Code::Blocks - forum (nickname jens).

This is the only option you have.

[oneiric]

Thanks for the advice. This may wind up being filed under "read the manpage, stupid" (for apt-get).

And I may wind up contacting Jens, too.

Thanks again.

[oBFusCATed]

Most probably the repo is out of date.

I think Jens has migrated to redhat based distros and I don't know if he is actively maintaining his debian repos.
If all ends badly it is not hard to build packages yourself.
The steps are: read a manual how to build debian packages, run the command, install missing deps, repeat the command

[oneiric]

"If all ends badly it is not hard to build packages yourself."

With my new installation, that's what I intend to do with all tarball source I choose to install: convert them into .deb packages and avoid the headache of trying to remove every last scrap of tarball installations when I want to update to a new release. In fact, that's what I intended to do with code::blocks, but there was a DEB version available (supposedly).

[oneiric]

cont'd

Actually, to be clear, I have 16.01 installed from the Debian repository, but I was hoping to install the latest-and-greatest (with periodic updates!).