WARNING: The following packages cannot be authenticated!

Asked by dodamn on 2009-11-20

Today, I made my own PPA. https://launchpad.net/~dodamn/+archive/test
And I uploaded my own source package to the PPA. Finally binary package was built successfully. The package name is 'rt3070-dkms'.

I wanted to install my own package from my own PPA.
So first I registered signing key using following command.

$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F6FE71D0

(F6FE71D0 is my signing key for my PPA)

And then I added the following two lines to /etc/apt/sources.list.

deb http://ppa.launchpad.net/dodamn/test/ubuntu jaunty main
deb-src http://ppa.launchpad.net/dodamn/test/ubuntu jaunty main

And I run update command.

$ sudo apt-get update

The result of this command had no errors.

And I run install command.

$ sudo apt-get install rt3070-dkms

But the result of this command has warning 'The following packages cannot be authenticated!'.
Why does this warning occur??

The following are full message when I run 'sudo apt-get install rt3070-dkms' command.

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  rt3070-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 693kB of archives.
After this operation, 3645kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  rt3070-dkms
Install these packages without verification [y/N]?

My Ubuntu is 9.04 (Jaunty).

Please help me.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
2009-11-20
Last reply:
2013-06-04
Muharem Hrnjadovic (al-maisan) said : #1

Hello there!

maybe the signing key for the PPA was only generated after you uploaded and built your package and the deb was not signed for that reason.

Could you please do me a favour by re-uploading the package and have it built again? Then try to install the resulting deb and let us know whether the problem persists.

Thank you!

-- Muharem

Vikram Dhillon (dhillon-v10) said : #2

Its probably some issue with signing your ppa. How about this [1]

[1] https://help.launchpad.net/Packaging/PPA/InstallingSoftware

Regards,
Vikram

On Thu, Nov 26, 2009 at 8:30 AM, Muharem Hrnjadovic
<email address hidden> wrote:
> Question #90976 on Launchpad itself changed:
> https://answers.edge.launchpad.net/launchpad/+question/90976
>
>    Status: Open => Needs information
>
> Muharem Hrnjadovic requested for more information:
> Hello there!
>
> maybe the signing key for the PPA was only generated after you uploaded
> and built your package and the deb was not signed for that reason.
>
> Could you please do me a favour by re-uploading the package and have it
> built again? Then try to install the resulting deb and let us know
> whether the problem persists.
>
> Thank you!
>
> -- Muharem
>
> You received this question notification because you are an answer
> contact for Launchpad itself.
>

Timur Batyrshin (erthad) said : #3

The key you use for signing source packages is not the same key as used for building the apt-repository.
You should add to apt keyring the latter one and you can find it on the launchpad page for your PPA.

Can you help with this problem?

Provide an answer of your own, or ask dodamn for more information if necessary.

To post a message you must log in.