| Summary: | GPG Key and Repositories not Accessible | ||
|---|---|---|---|
| Product: | TDE | Reporter: | sqlpython |
| Component: | ubuntu | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugwatch, darrella, james, michele.calgaro, mutantturkey, ogldelphi, pearsoncomputing |
| Priority: | P5 | ||
| Version: | 3.5.13.x [Trinity] | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
sqlpython
2010-10-19 11:02:07 CDT
We at RevLinux are interested in joining the Project but the repository availability is of concern.. The past few days, I have been seeing the following from synaptic: Failed to fetch http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/ubuntu/dists/maverick/Release.gpg Failed to fetch http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/ubuntu/dists/maverick/main/i18n/Translation-en.bz2 Failed to fetch http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/ubuntu/dists/maverick/main/i18n/Translation-en_US.bz2 Failed to fetch http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps/ubuntu/dists/maverick/Release.gpg Failed to fetch http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps/ubuntu/dists/maverick/main/i18n/Translation-en.bz2 Failed to fetch http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps/ubuntu/dists/maverick/main/i18n/Translation-en_US.bz2 Please confirm that this issue is fixed and mark as resolved:fixed if so. Thanks! Me too and it happens quite often root@AX201-00316:~# sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 gpg: requesting key 2B8638D0 from hkp server keyserver.quickbuild.pearsoncomputing.net gpg: keyserver timed out gpg: keyserver receive failed: keyserver error root@AX201-00316:~# sudo apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys 2B8638D0 gpg: requesting key 2B8638D0 from hkp server keyserver.quickbuild.pearsoncomputing.net gpg: keyserver timed out gpg: keyserver receive failed: keyserver error Suspect on this occasion it might be due to a restrictive firewall. Changes have been made to increase reliability of the firewall which protects the keyserver; please let me know if you continue to experience problems. I'm tired with this bug! I have to make apt-get update about 5-10 times for GPG keys are checked. Чтение списков пакетов... Готово W: Ошибка GPG: http://ppa.quickbuild.pearsoncomputing.net squeeze Release: Следующие подписи неверные: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment W: Ошибка GPG: http://ppa.quickbuild.pearsoncomputing.net squeeze Release: Следующие подписи неверные: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment Please, make something with this. I have added a duplicate key on my server: wget http://www.netlinux.org.uk/uploads/trinity.asc -O - |sudo apt-key add - This may get out of sync with the original key, but you can try it. Is this report still valid? On my Debian - testing, I finally commented-out the /etc/apt/sources.list references to http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/debian. I'd get things like E: Encountered a section with no Package: header E: Problem with MergeList /var/lib/apt/lists/ppa.quickbuild.pearsoncomputing.net_trinity_trinity-v3.5.13_debian_dists_squeeze_main_i18n_Translation-en E: The package lists or status file could not be parsed or opened. So I'd say yes, still a problem. I cannot say anything about specific problems, but there are still download problems that come and go. Currently, I have switched to Arch Linux for something more current than Debian, but Arch is not as current with Trinity and does not use the ppa. James Repository availability has improved a lot over the years, thanks to the secondary mirrors and Slavek repo as well. |