Your message dated Sun, 11 Oct 2015 21:19:17 +0200 with message-id <20151011191917.GA26099@crossbow> and subject line Re: Bug#800415: Missing transport (e.g. apt-transport-https) aborts apt update, including in-progress updates via other transports has caused the Debian Bug report #800415, regarding Missing transport (e.g. apt-transport-https) aborts apt update, including in-progress updates via other transports 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.) -- 800415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800415 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: Missing transport (e.g. apt-transport-https) aborts apt update, including in-progress updates via other transports
- From: Josh Triplett <josh@joshtriplett.org>
- Date: Mon, 28 Sep 2015 20:21:07 -0700
- Message-id: <20150929032107.29858.24918.reportbug@x>
Package: apt Version: 1.0.10.2 Severity: normal If apt detects a missing transport (such as apt-transport-https), it will abort the entire apt update, including any in-progress updates over other transports. When combined with #555674 (still present in unstable), the failed apt update causes apt to mark other packages as untrusted, including apt-transport-https. Thus, to securely install apt-transport-https, I had to temporarily comment out the https repository, update, install apt-transport-https, and uncomment the https repository. Even without that bug, though, aborting the rest of the update seems excessive. - Josh Triplett -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (/etc/apt/sources.list present, but not submitted) -- -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt depends on: ii debian-archive-keyring 2014.3 ii gnupg 1.4.19-5 ii libapt-pkg4.16 1.0.10.2 ii libc6 2.19-22 ii libgcc1 1:5.2.1-17 ii libstdc++6 5.2.1-17 apt recommends no packages. Versions of packages apt suggests: pn apt-doc <none> ii aptitude 0.7.2-1 ii dpkg-dev 1.18.3 ii python-apt 1.0.0 -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Josh Triplett <josh@joshtriplett.org>, 800415-done@bugs.debian.org
- Subject: Re: Bug#800415: Missing transport (e.g. apt-transport-https) aborts apt update, including in-progress updates via other transports
- From: David Kalnischkies <david@kalnischkies.de>
- Date: Sun, 11 Oct 2015 21:19:17 +0200
- Message-id: <20151011191917.GA26099@crossbow>
- In-reply-to: <20150929032107.29858.24918.reportbug@x>
- References: <20150929032107.29858.24918.reportbug@x>
Version: 1.1~exp13 On Mon, Sep 28, 2015 at 08:21:07PM -0700, Josh Triplett wrote: > If apt detects a missing transport (such as apt-transport-https), it > will abort the entire apt update, including any in-progress updates over > other transports. This and many more instances are fixed in the newest /experimental version, specifically with commit 90b56f54 aka "avoid using global PendingError to avoid failing too often too soon". Best regards David KalnischkiesAttachment: signature.asc
Description: PGP signature
--- End Message ---