** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/squid-deb-proxy/+git/squid-deb-proxy/+merge/409645
--
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:
"un
** Also affects: squid-deb-proxy (Ubuntu Impish)
Importance: Low
Assignee: Miriam España Acebal (mirespace)
Status: Confirmed
--
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
@Miriam - please consider applying [1] to impish and later on the same for the
SRUs.
Let me know if the test steps that I created based on all the discussions would
not work for you.
This can then, down the road become a sync again once there is 0.8.16
released.
[1]: https://github.com/mvo5/squ
> Christian, thank you for stepping in. It seems you finally got the ball
> rolling
> here where I was unsuccessful in a good half dozen attempts in #ubuntu-devel
> and other venues. That's the good news I suppose.
Np, glad to help - although this time as you said it was more "stepping
in" as I w
** Description changed:
+ Steps to reproduce (for later SRU work)
+
+ #0
+ # On the test Host install apt-cacher-ng
+ # you need to do so before creating the guest to propagate
+ # and configure correctly when spawned
+ $ sudo apt install apt-cacher-ng
+
+ #1
+ # create a VM guest or container w
Christian, thank you for stepping in. It seems you finally got the ball
rolling here where I was unsuccessful in a good half dozen attempts in
#ubuntu-devel and other venues. That's the good news I suppose.
I maintain my assessment of the situation of Ubuntu as stated in #16.
I've been with Ubun
My apologizes that this totally was not on my radar. I applied the patch
(thank you!) and moved the code from bzr to git, added a gbp.conf and
pushed to GH for now (but maybe this really should go to salsa instead).
I hope I will be able to release a new .16 release with these changes
(and the most
Hi Rolf,
let me try to calm things down a bit via clarifications on the
technical and ubuntu-process side of this.
> I'm not sure I understand what you did and what your results were. It
> appears that you got the issue of an "uncaptured python exception" at
> least once "when you removed squid-d
** Description changed:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/li
@Miriam, actually, all that I've written has been mentioned before in
the bug ticket. Have you actually read the ticket? Why is it that
people who get paid by Canonical to work on Ubuntu can't even be
bothered to read the tickets where volunteers who don't get paid have
already done their work (y
Thank, Miriam, for having a look. I only became aware of your response
now by accident.
I'm not sure I understand what you did and what your results were. It
appears that you got the issue of an "uncaptured python exception" at
least once "when you removed squid-deb-proxy"? I really don't know
Hi Rolf,
I'm trying to reproduce the issue on impish, but I only get this:
root@ondevelopment:~# /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('fd42:ce31:bcba:21af:216:3eff:fe27:28d6', 8000, 0, 0): 9223372036854775807
(:[Errno 111] Co
Thanks, Lucas.
As far as I'm aware, this was never addressed upstream and thus still
affects ubuntu+1 (ping @mvo). So, before SRU this needs to be fixed in
ubuntu+1. The patch from #4 is what I've been using for the last few
years without a hitch. It would certainly be nice for it to land befor
@Rolf and others, thanks for all the testing done so far. Since the
importance is set to Low I do not believe we will have time to tackle
this anytime soon, but I'd be happy to sponsor a fixed package if anyone
wants to work on it. In order to land this fix we would need to follow
the SRU process:
** Also affects: python2.7 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: squid-deb-proxy (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: python2.7 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: squid-deb-pro
I've long been using the patch from this ticket successfully and have
now published a bionic package in my LTS ppa
https://launchpad.net/~r0lf/+archive/ubuntu/stable Other release
pockets to follow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
filing against python2.7 as well based on comment #4
** Also affects: python2.7 (Ubuntu)
Importance: Undecided
Status: New
--
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:
"un
Andreas, I cannot confirm this for focal and I believe you should have
asked for confirmation from others before closing.
Code inspection suggests nothing was done to fix this bug, but of course
it was possible that a change in asyncore.py fixed this. That does not
look to be the case. I tested
I believe this is fixed in eoan at least:
root@eoan-squid-deb-proxy-clienbt:~# rm -f errors.txt
root@eoan-squid-deb-proxy-clienbt:~#
/usr/share/squid-deb-proxy-client/apt-avahi-discover 2>errors.txt
http://10.0.100.99:8000/
root@eoan-squid-deb-proxy-clienbt:~# cat errors.txt
Failed to resolve se
** Changed in: squid-deb-proxy (Ubuntu)
Status: In Progress => Confirmed
--
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:
"uncaptured python exception"
To manage notifications ab
Going by what's written here and in bug 1422162 it looks like this
problem occurs whenever there is more than one host/IP discovered via
avahi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Ti
@mvo, it would be nice if you took the time to consider inclusion of the
patch from comment 4
** Changed in: squid-deb-proxy (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Thanks, Jason! I applied the patch locally and indeed it works
beautifully.
I hope it lands soon and gets backported to trusty.
--
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:
"uncapt
So, I went ahead and made a different version of the patch which sends
asyncore's logging output to syslog, instead of stderr. This keep's
apt-get's output clean.
I think this is the patch I'd prefer. However, I should probably also
bark up the tree of asyncore.py and ask why they are calling 'p
(oops, the previous patch had some garbage at the top. re-attaching the
patch here).
** Patch removed: "Minimal patch to work-around this bug."
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1505670/+attachment/4498637/+files/apt-avahi-discover.patch
** Patch added: "Minimal
The attachment "Minimal patch to work-around this bug." seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad use
I just ran into this bug, and I think I've figured it out.
/usr/share/squid-deb-proxy-client/apt-avahi-discover is outputting the
URL of my squid-deb-proxy server, but it is also spitting out some
errors:
root@debian:~# /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured pytho
27 matches
Mail list logo
