Getting "Requires installation of untrusted packages" error after copying packages w/binaries between two of my PPAs
In addition to my personal PPAs, I have PPAs in two teams that I created. After moving packages from one of my personal PPAs to one of the team PPAs I'm getting this error from Update Manager. All of the keys for the PPAs are installed in my system, so I don't understand why I'm getting this error.
The keys in question are:
1024R/455756F9
1024R/325283A9
1024R/8D8E9F8C
I'm most concerned that the PPAs under the first key trust packages that were built/signed with the second and third keys.
Thanks in advance for the help.
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- N1ck 7h0m4d4k15
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Your PPA has not the same signature as team's PPA. Correct ?
So you have to add the keys manually in apt, in order to install the software.
sudo apt-key adv --recv-key --keyserver keyserver.
Where <keynumber> replace it with the number of the key is missing. e.g 455756F9
Repeat as many times is required to import all missing keys.
Regards,
NikTh
Revision history for this message
|
#2 |
No, all three keys are installed in my system.
I can install packages from a PPA that were built in that PPA without problem.
What I can't do is install those same packages after copying them to a different PPA.
Revision history for this message
|
#3 |
Can you give the output of:
sudo apt-get update; lsb_release -a
Thanks
Revision history for this message
|
#4 |
Sure, it it is:
Wanted to double-check so I could give you a specific problem:
If I try to update the libreoffice package that is in ppa:centrych/
That package was built in one of my personal scratch PPAs and copied to the updates PPA. I had deleted it after copying, so I forget which one it was originally.
However, after copying the package to ppa:jprad/
$ sudo apt-get update; lsb_release -a
Get:1 http://
Hit http://
Get:2 http://
Hit http://
Hit http://
Get:3 http://
Hit http://
Get:4 http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Get:5 http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:6 http://
Hit http://
Ign http://
Get:7 http://
Get:8 http://
Get:9 http://
Get:10 http://
Get:11 http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Get:12 http://
Get:13 http://
Get:14 http://
Get:15 http://
Get:16 http://
Get:17 http://
Get:18 http://
Get:19 http://
Get:20 http://
Get:21 http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Get:22 http://
Get:23 http://
Get:24 http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:25 http://
Get:26 http://
Hit http://
Ign http://
Get:27 http://
Hit http://
Hit http://
Hit http://
Get:28 http://
Get:29 http://
Get:30 http://
Hit http://
Get:31 http://
Ign http://
Get:32 http://
Get:33 http://
Get:34 http://
Get:35 http://
Get:36 http://
Ign http://
Hit http://
Hit http://
Hit http://
Ign http://
Get:37 http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Fetched 3,311 kB in 2s (1,352 kB/s)
Reading package lists... Done
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
Revision history for this message
|
#5 |
Then its fine, there are no mention of GPG keys in that output....
Revision history for this message
|
#6 |
It's not fine, but I think I identified where the problem is.
I found another answer thread on launchpad with a similar error. One of the posts mentioned something about this happening if the PPA is renamed.
So, I set up a test by creating a dummy package in each of my PPAs, which are listed below, grouped by key. Each package has a unique version number and all of the PPAs have the same pin priority value.
With all of the PPAs enabled, the kernel, security and scratch1 PPAs are not listed in Synaptic when I select the Origin button.
I'm pretty sure I renamed each of those PPAs at some time in the past.
Hope that helps.
1024R/455756F9
deb http://
deb http://
deb http://
deb http://
deb http://
1024R/325283A9
deb http://
1024R/8D8E9F8C
deb http://
deb http://
deb http://
deb http://
deb http://
Revision history for this message
|
#7 |
Sorry but I cannot understand what is the problem here. I've tested one of your PPAs (centrych/release) and there is no problem at all.
Maybe you meant something else ?
The key imported successfully and no untrusted packages message at all.
Regards
NikTh
Revision history for this message
|
#8 |
I can't understand what's going on either.
Here's a recap.
I moved the 3.6.6.2 build of LibreOffice from one of my scratch PPAs to the updates PPA.
After waiting for the move to complete, indicated by the checkmark in package details page for the PPA, I attempted an upgrade on my machine.
The update-manager saw the updated files, but I got the "Requires installation of untrusted packages" error when I tried it.
I tried it again late yesterday and it worked. I've made no changes to my two systems, i386 and amd64. Both failed, now they work.
However, I still have the same problem as I mentioned in post #6 above, when I enable all the PPAs, only a few are listed in Synaptic.
Revision history for this message
|
#9 |
Try to remove all the PPAs from your system.
sudo add-apt-repository --remove ppa:<the name/here>
Then do
sudo apt-get update
and then add them again one by one
sudo add-apt-repository ppa:<the name/here>
Regards
NikTh
Revision history for this message
|
#10 |
Okay, that seems to have done the trick.
I had originally added the PPAs using the following:
# beta PPA
cat >/etc/apt/
deb http://
deb-src http://
EOF
# beta key
apt-key adv --keyserver keyserver.
Is there something else that add-apt-repository is doing that I'm missing doing it this way?
Revision history for this message
|
#11 |
Probably yes.
add-apt-repository adds the PPA to sources.list or sources.list.d , then imports the key and signed it as trusted in apt.
Please mark the question as solved.
Regards
NikTh
Revision history for this message
|
#12 |
Thanks NikTh, that solved my question.