This bug was fixed in the package squid-deb-proxy -
0.8.14ubuntu0.18.04.1
---
squid-deb-proxy (0.8.14ubuntu0.18.04.1) bionic; urgency=medium
* apt-avahi-discover: write errors to stderr instead
of stdout so that stdout can be captured correctly.
Thanks to . Note that this
This bug was fixed in the package squid-deb-proxy -
0.8.15ubuntu0.20.04.1
---
squid-deb-proxy (0.8.15ubuntu0.20.04.1) focal; urgency=medium
* apt-avahi-discover: write errors to stderr instead
of stdout so that stdout can be captured correctly.
Thanks to . Note that this is
This bug was fixed in the package squid-deb-proxy -
0.8.15ubuntu0.21.04.1
---
squid-deb-proxy (0.8.15ubuntu0.21.04.1) hirsute; urgency=medium
* apt-avahi-discover: write errors to stderr instead
of stdout so that stdout can be captured correctly.
Thanks to . Note that this
Thanks a lot, Christian, for the verification and all the previous help
on this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
python exceptions bleeding into stdout
To manage
Hirsute
Check after cacher is down in the host
+;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
+;enp7s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
+;enp1s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
Focal
Check after cacher is down in the host
+;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
+;enp7s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
+;enp1s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
Bionic
Check after cacher is down in the host
+;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
=;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local;Keschdeichel.local;192.168.122.1;3142;
ubuntu@b-deb-proxy:~$ curl 192.168.122.1:3142
** Also affects: squid-deb-proxy (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: squid-deb-proxy (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: squid-deb-proxy (Ubuntu Trusty)
Importance: Undecided => Low
** Also affects: squid-deb-proxy (Ubuntu
** Changed in: squid-deb-proxy (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: squid-deb-proxy (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: squid-deb-proxy (Ubuntu Hirsute)
Importance: Undecided => Low
--
You received this bug notification because you are a
Following discussion, I'm adjusting the Bionic package version string
from 0.8.14ubuntu1 to 0.8.14ubuntu0.18.04.1 to avoid any potential
conflict with a future ESM update to this package in Xenial.
** Changed in: squid-deb-proxy (Ubuntu Hirsute)
Status: In Progress => Fix Committed
**
** Description changed:
[Impact]
As @cell explains, the problem here is that the errors are going to
stdout, not to stderr. This means apt's Acquire::http::ProxyAutoDetect
is not able to figure out what the proxy URL is.
[Test Plan]
The idea is to create a VM with several
** Description changed:
[Impact]
- As @cell explains, the problem here is that the errors are going to stdout,
- not to stderr. This means apt's Acquire::http::ProxyAutoDetect is not able
- to figure out what the proxy URL is.
+ As @cell explains, the problem here is that the
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/squid-deb-proxy/+git/squid-deb-proxy/+merge/410288
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/squid-deb-proxy/+git/squid-deb-proxy/+merge/410286
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/squid-deb-proxy/+git/squid-deb-proxy/+merge/410287
--
You received this bug
** Description changed:
+ [Impact]
+
+ As @cell explains, the problem here is that the errors are going to stdout,
+ not to stderr. This means apt's Acquire::http::ProxyAutoDetect is not able
+ to figure out what the proxy URL is.
+
+ [Test Plan]
+
+ Steps to reproduce (by @cpaelzer
** Changed in: squid-deb-proxy (Ubuntu Bionic)
Status: New => In Progress
** Changed in: squid-deb-proxy (Ubuntu Focal)
Status: New => In Progress
** Changed in: squid-deb-proxy (Ubuntu Hirsute)
Status: New => In Progress
--
You received this bug notification because you
This bug was fixed in the package squid-deb-proxy - 0.8.15+nmu1ubuntu1
---
squid-deb-proxy (0.8.15+nmu1ubuntu1) impish; urgency=medium
[ Michael Vogt ]
* apt-avahi-discover: use syslog for logging
in AptAvahiClient, thanks to Jason Pepas
(jasonpe...@gmail.com).
(LP:
After the test (all worked) and sponsored it to impish.
Let us hope it slips in before the freeze happens.
SRUs from there will again be prepared by Miriam.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Testing in Impish without extra network interfaces:
# works
$ sudo apt install avahi-utils squid-deb-proxy-client
$ avahi-browse -kprtf _apt_proxy._tcp
+;enp1s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
** Changed in: squid-deb-proxy (Ubuntu Impish)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
python exceptions bleeding into stdout
To manage
** Summary changed:
- "uncaptured python exception"
+ python exceptions bleeding into stdout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
python exceptions bleeding into stdout
To
21 matches
Mail list logo
