Same here. Using Jammy's 3.7.4-1build1 results in "503" errors even when
downloading from main archive. Seems to happen only when used with apt
in http_proxy mode (when using with localhost:3142/xxx prefix, eg, for
debootstrap, that works).
Reverted to debian/3.6.4-1 from salsa and all goes back
@fossfreedom: Thank you for the quick response. I assume you can still
reproduce the problem, right? It would be great to see logs, for
example /var/log/apt-cacher-ng/apt-cacher.err Would you be so kind to
provide those?
--
You received this bug notification because you are a member of Ubuntu
Mine was a fresh install of jammy with it installed from the repo.
On Sun, 27 Feb 2022, 11:10 Rolf Leggewie, <1960...@bugs.launchpad.net>
wrote:
> The problem disappeared after installing the version in impish. More
> importantly, it hasn't come back after reinstalling the version from
> jammy.
The problem disappeared after installing the version in impish. More
importantly, it hasn't come back after reinstalling the version from
jammy.
@fossfreedom, did you upgrade the system where acng is running from
focal as well? Can you provide logs of the problem?
--
You received this bug
** Tags added: regression-release
** Description changed:
- For Jammy - all PPAs seem to fail - the main archive is ok
+ For apt-cacher-ng from jammy - all PPAs seem to fail - the main archive
+ is ok
503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
Err:12
I can confirm that acng running the version in jammy triggers the
problem with PPA in the clients it serves (which may or may not be
running jammy). Going by the fact that the version from impish when
installed on jammy does not have this problem and runs fine otherwise,
it looks like a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960264
I don't know if anyone looks at apt-cacher-ng bug reports, but reassigning it
there for further analysis.
The log says that this is apt-cacher-ng failing to talk to launchpad.
I generally recommend avoiding apt-cacher-ng due to bugs in the
interaction with apt (which then go in endless circles
Julian - correct I was using apt-cacher-ng as per sbuild instructions
here https://wiki.ubuntu.com/SimpleSbuild
Sorry - I've no idea how to configure squid-deb-proxy with sbuild. So
I've deleted my sbuild chroots & disabled using the .mk-sbuildrc proxy.
Installing from a ppa no longer shows 503
It seems you use apt-cacher-ng, please try if the issue reproduces
without it, and if so, if it happens with a known good proxy like squid
(e.g. using deb-squid-proxy).
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Are there any log entries in your proxy that might help explain what's
happening?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960264
Title:
503 errors for Jammy PPAs
To manage
11 matches
Mail list logo
