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
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1960264
Title:
503 errors for Jammy
4 matches
Mail list logo
