Simon Walker

@rafeanders We're only really building on Ubuntu Trusty (20.04, libc 2.31) and Ubuntu Jammy (22.04, libc 2.35) as those are the only runners GitHub Actions supports natively, and we don't...

Yeah, it does support a [few different options](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories), but they are quite limited. There's also the option to self-host runners, or to [run the build in Docker](https://docs.github.com/en/actions/using-jobs/running-jobs-in-a-container) (and thus build...

Just building on Trusty alone also runs the risk of introducing ABI incompatibilities with Pillow on newer Ubuntu versions.

I know we've almost finished work to add proper .deb packages for Debian-based distros (just testing and publishing to an apt repo I think), and I think @Gregory-AM was starting...

This now shows up, but without the correct autogen help messages - probably due to the frontend picking up the version from CommandLib, not Helpmebot.

@JustBerry this will be in your own GitHub settings, not something I can change on your behalf.

Hi, I'm afraid we're going to need a bunch more info to try reproducing this. * What version of Overviewer are you running? * What version of Python are you...

I've closed this for now as we don't have enough information to understand the problem.

Apparently this has also broken tests. A quick look at the broken tests makes me think that the expected values of the tests are depending on the shorter chunk size,...

I've ended up doing some digging into this since the fix to this issue has caused another issue reported in #90. I reverted the changes made to fix this issue...