[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#526181: marked as done (apt-key: ERROR no URL when ARCHIVE_KEYRING_URI is not set to real URL)

Your message dated Sat, 2 Jan 2010 20:12:12 +0100
with message-id <c64043e61001021112n28b040d8q4193986289e8f1a5@mail.gmail.com>
and subject line Re: apt-key: ERROR no URL when ARCHIVE_KEYRING_URI is not set to real  URL
has caused the Debian Bug report #526181,
regarding apt-key: ERROR no URL when ARCHIVE_KEYRING_URI is not set to real URL
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
526181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526181
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.7.20.2+lenny1
Severity: normal
Tags: patch

Hello,

as I was worried because my keys werent valid to apt when i updated i
played 
around with apt-key and found out that when ARCHIVE_KEYRING_URI is not
set to an 
actual URL the script sends an error and exits.
the error I get is : 
ERROR: no location for the archive-keyring given
wget: missing URL
Usage: wget [OPTION]... [URL]...

Try `wget --help' for more options.

So  I checked its code and found out that ARCHIVE_KEYRING_URI
was set to ARCHIVE_KEYRING_URI="".

I copied the script to my home directory and checked if it can be banned
by 
changing the code at this part. The patch is actually pretty trivial but
I 
already tested it from my home partition and it works fine though(But
maybe no 
output is also bad news).
output of diff -u 


--- /usr/bin/apt-key	2009-04-20 22:25:02.000000000 +0200
+++ ./apt-key.sh	2009-04-29 18:25:55.000000000 +0200
@@ -11,9 +11,9 @@
 

 MASTER_KEYRING=""
-ARCHIVE_KEYRING_URI=""
+#ARCHIVE_KEYRING_URI=""
 #MASTER_KEYRING=/usr/share/keyrings/debian-master-keyring.gpg
-#ARCHIVE_KEYRING_URI=http://ftp.debian.org/debian/debian-archive-keyring.gpg
+ARCHIVE_KEYRING_URI=http://ftp.debian.org/debian/debian-archive-keyring.gpg
 
 ARCHIVE_KEYRING=/usr/share/keyrings/debian-archive-keyring.gpg
 REMOVED_KEYS=/usr/share/keyrings/debian-archive-removed-keys.gpg


So if its ok for a patch for the personal use thats ok but maybe
somebody involved
can tell better on this one .

Sincerely,

Andreas Marschke.
-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Acquire "";
APT::Acquire::Translation "environment";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^linux-image.*";
APT::NeverAutoRemove:: "^linux-restricted-modules.*";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Unattended-Upgrade "0";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success::::
"touch /var/lib/apt/periodic/update-success-stamp 2>/dev/null || true";
APT::Archives "";
APT::Archives::MaxAge "30";
APT::Archives::MinAge "2";
APT::Archives::MaxSize "500";
Dir "/";
Dir::State "var/lib/apt/";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::userstatus "status.user";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache "var/cache/apt/";
Dir::Cache::archives "archives/";
Dir::Cache::srcpkgcache "srcpkgcache.bin";
Dir::Cache::pkgcache "pkgcache.bin";
Dir::Etc "etc/apt/";
Dir::Etc::sourcelist "sources.list";
Dir::Etc::sourceparts "sources.list.d";
Dir::Etc::vendorlist "vendors.list";
Dir::Etc::vendorparts "vendors.list.d";
Dir::Etc::main "apt.conf";
Dir::Etc::parts "apt.conf.d";
Dir::Etc::preferences "preferences";
Dir::Bin "";
Dir::Bin::methods "/usr/lib/apt/methods";
Dir::Bin::dpkg "/usr/bin/dpkg";
Dir::Log "var/log/apt";
Dir::Log::Terminal "term.log";
Unattended-Upgrade "";
Unattended-Upgrade::Allowed-Origins "";
Unattended-Upgrade::Allowed-Origins:: "Debian stable";
DPkg "";
DPkg::Pre-Install-Pkgs "";
DPkg::Pre-Install-Pkgs:: "/usr/sbin/dpkg-preconfigure --apt || true";
DPkg::Post-Invoke "";
DPkg::Post-Invoke:: "if [ -d /var/lib/update-notifier ]; then
touch /var/lib/update-notifier/dpkg-run-stamp; fi";

-- (no /etc/apt/preferences present) --


-- /etc/apt/sources.list --

# 
deb cdrom:[Debian GNU/Linux 5.0.0 _Lenny_ - Official amd64 DVD Binary-1
20090214-19:45]/ lenny contrib main

deb cdrom:[Debian GNU/Linux 5.0.0 _Lenny_ - Official amd64 DVD Binary-2
20090214-19:45]/ lenny contrib main

deb http://security.debian.org/ lenny/updates main contrib non-free
deb-src http://ftp.de.debian.org/debian/ lenny/updates main contrib
non-free

deb http://volatile.debian.org/debian-volatile lenny/volatile main
contrib
deb http://ftp.de.debian.org/debian/ lenny main contrib non-free
deb-src http://ftp.de.debian.org/debian/ lenny main contrib non-free
deb http://ftp.de.debian.org/debian/ lenny-proposed-updates main contrib
non-free
deb-src http://ftp.de.debian.org/debian/ lenny-proposed-updates main
contrib non-free
deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
contrib
deb cdrom:[Debian GNU/Linux 5.0.0 _Lenny_ - Official amd64 DVD Binary-3
20090214-19:45]/ lenny contrib main
deb http://people.debian.org/~rmh/linux-libre lenny main
# vorgeschlagene Änderungen für eine 5.0 Zwischenveröffentlichung
  deb http://ftp.us.debian.org/debian proposed-updates main contrib
non-free

-- System Information:
Debian Release: 5.0.1
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt depends on:
ii  debian-archive-keyring       2009.01.31  GnuPG archive keys of the
Debian a
ii  libc6                        2.7-18      GNU C Library: Shared
libraries
ii  libgcc1                      1:4.3.2-1.1 GCC support library
ii  libstdc++6                   4.3.2-1.1   The GNU Standard C++
Library v3

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc               <none>             (no description available)
ii  aptitude              0.4.11.11-1~lenny1 terminal-based package
manager
ii  bzip2                 1.0.5-1            high-quality block-sorting
file co
ii  dpkg-dev              1.14.25            Debian package development
tools
ii  lzma                  4.43-14            Compression method of 7z
format in
ii  python-apt            0.7.7.1+nmu1       Python interface to
libapt-pkg
ii  synaptic              0.62.1+nmu1        Graphical package manager

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi Andreas Marschke,

First of all: Thanks for your report.
(Unfortunately) i intend to close this bugreport now for the
following reason(s), but feel free to reopen it if you disagree.

The apt-key net-update command you refer to is unused
in debian as there is neither an url to get the current keyring
nor a master-key to check the validity of the downloaded key.
(ubuntu has this facility in place i think, maybe also other
 debian-spinoffs)

Your purposed patch therefore silently doesn't work:
It tries to download the keyring from the given location,
but as it can't download it successfully it returns from the
method without a further note...

But debian doesn't need this feature anyway: Pretty the same
is achieved with the "update" command which imports the
locally installed keyring provided by the debian-archive-keyring
package (which is a dependency of apt and therefore available).


Best regards / Mit freundlichen Grüßen,

David "DonKult" Kalnischkies

--- End Message ---
Reply to: