[11:54] <paride> @pilot in
[16:05] <paride> @pilot out
[16:06] <dbungert> @pilot in
[19:08] <tsimonq2> https://git.launchpad.net/ubuntu-dev-tools/commit/?id=2f396fe54956c85e0f0e62891f29dc7bab7d110b adds support for VCS detection on pull-lp-source, displaying the exact same message `apt source` does.
[19:08] -ubottu:#ubuntu-devel- Commit 2f396fe in ubuntu-dev-tools "When using pull-*-source to grab a package which already has a defined Vcs- field, display the exact same warning message `apt source` does."
[19:08] <tsimonq2> (cc juliank) I often wonder if adding support for e.g. Ubuntu-specific VCSes is worth the effort.
[19:09] <tsimonq2> Anyway, I've uploaded that to unstable, if anyone thinks there's justification for pulling it into Mantic, JFDI :)
[19:09] <juliank> Well hopefully it's not worth it for long
[19:10] <juliank> And we all use git-ubuntu staging branches :D
[19:11] <tsimonq2> I mean, it would still cover the case where Debian has their own VCS, right? On Debian that could be "Hey, clone from this Salsa repo," on Ubuntu it could be "hey you're using the wrong command." :P
[19:12] <tsimonq2> (Despite the really good impressions I have of git-ubuntu so far, it could take a bit to move to it "de facto." I mean, it's taken how long to move from Bazaar to Git?)
[19:13]  * tsimonq2 shrugs, some UX to think about I guess
[20:14] <dbungert> @pilot out
[21:19] <kanashiro> does anyone know if in the autopkgtest infrastructure there is any restriction to access the docker registry? I am getting this error multiple times:
[21:19] <kanashiro> ERROR: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
[21:20] <kanashiro> hum, actually, this address is returning 404
[21:34] <ahasenack> it's https://registry-1.docker.io/v2/ actually
[21:34] <ahasenack> and that returns json
[21:34] <ahasenack> try setting the proxy?
[21:34] <ahasenack> https_proxy=http://squid.internal:3128/
[22:10] <kanashiro> I'll try to set the proxy variable
[22:11] <kanashiro> locally this test works fine
[22:20] <bdmurray> If you are connected to the Canonical VPN you can use the squid.internal proxy server e.g. `--env='http_proxy=http://squid.internal:3128' --env='https_proxy=http://squid.internal:3128'`
[22:21] <kanashiro> bdmurray thanks for the hint
[22:22] <bdmurray> kanashiro: incidentally what package are you testing?
[22:22] <kanashiro> it is docker-buildx
[22:24] <bdmurray> kanashiro: the top of an autopkgtest log also has the no_proxy config https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/d/docker-buildx/20230824_190753_d7a7c@/log.gz
[22:25] <kanashiro> ok, I'll set all of them locally connected to the VPN to see if I can reproduce the issue