Comment 42 for bug 1825755

Hi Heather,

thanks for these verifications!

I just wanted to clarify some points.

Jammy verification:

> Failed to open Release file from http://archive.ubuntu.com/ubuntu/dists/eoan-updates/Release at
> /usr/bin/apt-mirror line 653.

I don't think this is expected to work today, since eoan is EOL and doesn't exist at that URL anymore. I would have changed the ubuntu release to mirror to something that is still available, like jammy itself.

So this conclusion:
> ** Running apt-mirror never successfully finishes and errors out **

Is not because of the bug that is being fixed, is just because that distro is not available anymore.

Later on, when verifying the proposed package:
> # show mirror.list
> vim /etc/apt/mirror.list

You edit the mirror list, but don't show what you edited it to.

Of interest to this bug, we can see that now it downloads cnf files, so that's good:
> Downloading 24 cnf files using 20 threads...

The last step of the test plan, however:
> apt-get update
> also returns no errors

Here I would like some clarification. The intention is to show that the mirror that was just created is working, and to do that we want to run "apt-get update" *against* *it*. I can't infer that from this verification: it could be that you just ran apt-get update with sources.list pointing at the ubuntu archive, and not the mirror you just created.

From the test plan, we can see that apt-get update is meant to run against the newly created mirror:

> * Attempt to run `apt update` against the mirror. The result will be similar to:
> ...
> Err:7 http://10.3.0.41/ubuntu eoan-updates/main amd64 c-n-f Metadata
> 404 Not Found [IP: 10.3.0.41 80]