http://www.deb-multimedia.org testing or stretch Release' does not have a Release file

[GiaThnYgeia]

NEW thread, no a hijacked one, as I give up searching for what I may
have done WRONG

GPG error: http://www.deb-multimedia.org testing InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 5C808C2B65558117
The repository 'http://www.deb-multimedia.org testing InRelease' is not
signed.

After switching between testing and stretch .org and .org/dists I have
given up. Something with gpg and keyrings is messed up and can't find
out what it is. The rest of the debian repositories work and everything
is current and updated.


http://www.deb-multimedia.org testing does not have a Release file

http://www.deb-multimedia.org/dists testing Release' does not have a
Release file

The repository 'http://www.deb-multimedia.org/dists testing Release'
does not have a Release file.

I just browsed into the directory and it DOES have a Release file right
there. So I switched testing to stretch which appears to be the same

Updating from such a repository can't be done securely, and is therefore
disabled by default.See apt-secure(8) manpage for repository creation
and user configuration details.

The repository 'http://www.deb-multimedia.org/dists stretch Release'
does not have a Release file.

In the instructions it says once you open the directory download the
multimedia keyring

DUHHH....... !! But can't reach that repository because it is not signed
as legit!

--
"The most violent element in society is ignorance" rEG

[Eduardo M KALINOWSKI]

On 04-03-2017 12:59, GiaThnYgeia wrote:
> GPG error: http://www.deb-multimedia.org testing InRelease: The
> following signatures couldn't be verified because the public key is not
> available: NO_PUBKEY 5C808C2B65558117
> The repository 'http://www.deb-multimedia.org testing InRelease' is not
> signed.

> [...]

> DUHHH....... !! But can't reach that repository because it is not signed
> as legit!

aptitude allows installation from untrusted sources, it'll just ask for
confirmation before. I suppose apt-get is similar.

Install deb-multimedia-keyring and run update again, the repository will
be trusted.

It's also possible to add the signing key manually with apt-key, but I
couldn't easily find the key ID in http://deb-multimedia.org .


--
If you want to travel around the world and be invited to speak at a lot
of different places, just write a Unix operating system.
-- Linus Torvalds

Eduardo M KALINOWSKI
edu...@kalinowski.com.br

[Frank]

Op 04-03-17 om 16:59 schreef GiaThnYgeia:

> http://www.deb-multimedia.org/dists testing Release' does not have a
> Release file
>
> The repository 'http://www.deb-multimedia.org/dists testing Release'
> does not have a Release file.

What does your deb-multimedia entry in sources.list look like exactly?
These two lines suggest apt is looking for the Release file of a
component called 'Release' in the suite 'testing'

> In the instructions it says once you open the directory download the
> multimedia keyring

Alternatively - if you really can't get hold of the keys - put [
trusted=yes ] between 'deb' and the url, e.g.:

deb [ trusted=yes ] http://www.deb-multimedia.org testing main non-free

Regards,
Frank

[GiaThnYgeia]

Eduardo M KALINOWSKI:

> On 04-03-2017 12:59, GiaThnYgeia wrote:
>> GPG error: http://www.deb-multimedia.org testing InRelease: The
>> following signatures couldn't be verified because the public key is not
>> available: NO_PUBKEY 5C808C2B65558117
>> The repository 'http://www.deb-multimedia.org testing InRelease' is not
>> signed.
>> [...]
>> DUHHH....... !! But can't reach that repository because it is not signed
>> as legit!
> aptitude allows installation from untrusted sources, it'll just ask for
> confirmation before. I suppose apt-get is similar.
>
> Install deb-multimedia-keyring and run update again, the repository will
> be trusted.
>
> It's also possible to add the signing key manually with apt-key, but I
> couldn't easily find the key ID in http://deb-multimedia.org .

Both apt-get and aptitude resulted in the same error
E: Unable to locate package deb-multimedia-keyring

www.deb-multimedia.org/pool/main/d/deb-multimedia-keyring/deb-multimedia-keyring_2016.8.1_all.deb

Even downloaded it locally and tried to install and it won't work

[GiaThnYgeia]

SOLVED=YES LEARNING A NEW TRICK=YES YES YES

Frank:

> Op 04-03-17 om 16:59 schreef GiaThnYgeia:
>> http://www.deb-multimedia.org/dists testing Release' does not have a
>> Release file
>>
>> The repository 'http://www.deb-multimedia.org/dists testing Release'
>> does not have a Release file.
>
> What does your deb-multimedia entry in sources.list look like exactly?
> These two lines suggest apt is looking for the Release file of a
> component called 'Release' in the suite 'testing'

I tried that dists on my own in case that was the problem, but it made
no difference /dists or nothing after org, stretch or testing, same result.

>> In the instructions it says once you open the directory download the
>> multimedia keyring
>
> Alternatively - if you really can't get hold of the keys - put [
> trusted=yes ] between 'deb' and the url, e.g.:

This is getting too secure for me, I couldn't even import the downloaded
key file verified and through an encrypted channel...

But your trick worked, imported the multimdedia-key rerun without the
[trusted=yes] tag and all is OK

Thank you, you made a waste of a day receive high value. I now have the
other half of the weekend to investigate why all my multimedia packages
have multimedia-upgrades/revisions within testing.

> deb [ trusted=yes ] http://www.deb-multimedia.org testing main non-free

OK, it worked, but what was the issue would I ever know? Too many keys
in the keyring? I don't think so. Just for kicks I added some other
distributions repository (testing based) and it didn't have such a
problem. Maybe some public key-certificate somewhere where multimedia
is not registered yet as trustworthy?

> Regards,
> Frank

Thank you again, you really made my day, I was going mad with this
thinking it is a much deeper problem.

[Frank]

Op 04-03-17 om 21:04 schreef GiaThnYgeia:

> SOLVED=YES LEARNING A NEW TRICK=YES YES YES

:)

> Thank you, you made a waste of a day receive high value. I now have the
> other half of the weekend to investigate why all my multimedia packages
> have multimedia-upgrades/revisions within testing.

It's probably too late now to tell you I actually wouldn't advise using
deb-multimedia...

>> deb [ trusted=yes ] http://www.deb-multimedia.org testing main non-free
>
> OK, it worked, but what was the issue would I ever know? Too many keys
> in the keyring? I don't think so. Just for kicks I added some other
> distributions repository (testing based) and it didn't have such a
> problem. Maybe some public key-certificate somewhere where multimedia
> is not registered yet as trustworthy?

Unlikely. And the deb line I showed (but without the trusted=yes bit) is
nothing special. No idea why it didn't work for you before.

> Thank you again, you really made my day,

You're welcome.

Regards,
Frank

[GiaThnYgeia]

Luckily I have not used any package from them, no wonder it was so hard
for me to include their rep.

I guess I fell for it being included in the debian main mirrors before
and thought it was an internal project that became autonomous.

There is also an AV-linux distro for AV people, I don't know if they
just made a debian based distro with multimedia stuff.

Too many layers of interdependence between all these packages, enough to
destroy one's mind before the system breaks. If someone is working on a
bug on sound or graphics hardware it seems as if for that industry it is
like messing around with the foundations of a high-rise building.