Just tested in Wily -- replicated failure condition, added -proposed
repo, updated apt and retested and it's all good. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1575
Here's a debdiff for fixing Wily.
** Patch added: "apt-wily.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1575877/+attachment/4665539/+files/apt-wily.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to a
Precise: tested failure condition, added -proposed repo, updated apt and
retested -- all good.
Trusty: tested failure condition, added -proposed repo, updated apt and
retested -- all good.
Xenial: tested failure condition, added -proposed repo, updated apt and
retested -- all good.
Not sure ho
I can toss together one for Wily tomorrow; I figured keeping unreleased
in the changelog was important for debdiffs that hadn't been accepted
yet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.lau
mpty files
* silently skip acquire of empty index files
-> clean up of the above
* ensure outdated files are dropped without lists-cleanup
-> ensures proper cleanup
[ Kelemen Gábor ]
* Hungarian program translation update (Closes: 820638)
-- Julian Andres Klode Mon
I've also created a debdiff for patching Precise for this bug.
** Patch added: "apt-precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1575877/+attachment/4664911/+files/apt-precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I've created a debdiff for patching Trusty for this bug.
** Patch added: "apt-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1575877/+attachment/4664905/+files/apt-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Question: Is there a process by which to get this fix into Trusty as
well? The code diff is the same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1575877
Title:
no_proxy ig
Sure thing. SRU to follow:
[Impact]
This bug breaks users who use a proxy to access externally-hosted https apt
repositories, but do not need to use a proxy to access internally hosted https
apt repositories. Specifically, if a user has a https_proxy (or http_proxy and
no https_proxy) setting
Updated the patch with the help of the debian-apt upstream.
** Patch added:
"0001-refactored-no_proxy-code-to-work-regardless-of-where.patch"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1575877/+attachment/4649568/+files/0001-refactored-no_proxy-code-to-work-regardless-of-where.patch
Public bug reported:
Description:
When using the https transport mechanism, $no_proxy is ignored if apt is
getting it's proxy information from $https_proxy. If the source of proxy
information is Acquire::https::Proxy set in apt.conf (or apt.conf.d), then
$no_proxy is honored.
Package Versions:
11 matches
Mail list logo
