"No Release file" from do-release-upgrade with an aptly repo

[Aaron Rainbolt]

On Tue, Aug 16, 2022 at 7:19 PM Aaron Rainbolt <arraybolt3 at gmail.com> wrote:
>
> On Tue, Aug 16, 2022 at 6:26 PM Sam Varshavchik <mrsam at courier-mta.com> wrote:
> > <snip>
> > Well, yes, looks like that's the way forward for me: set up apache and have
> > it serve the same filesystem repo that I already have. Just to make update-
> > manager happy. That should get me past that roadblock, hopefully it'll be
> > the last one.
> > </snip>
>
> Instead of going full-on Apache, you can just open a terminal in the
> folder containing the repo and run "python3 -m http.server --bind
> 127.0.0.1 8080". Boom, instant HTTP server on port 8080. I use a trick
> like this for using sbuild with a "local PPA".

Bah, realized I wanted to send one more detail after hitting Send. If
you want it to serve on port 80 you'll have to use sudo, I believe. I
have to do this because when I use sbuild with apt-cacher it for some
reason only wants to connect to port 80. So you might need to use
"sudo python3 -m http.server --bind 127.0.0.1 80".