Fixes an off-by-one comparison in the previous endpoint that prevented
the second site in the order (list index #1) from ever redirecting to
the first (list index #0).

Signed-off-by: Taavi Väänänen <hi@taavi.wtf>
---
 handlers.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/handlers.go b/handlers.go
index 609525f..e219510 100644
--- a/handlers.go
+++ b/handlers.go
@@ -84,7 +84,7 @@ func (m model) previous(writer http.ResponseWriter, request *http.Request) {
[message trimmed]

---
 builds.sr.ht/compatibility.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/builds.sr.ht/compatibility.md b/builds.sr.ht/compatibility.md
index 93ec58a..0d60568 100644
--- a/builds.sr.ht/compatibility.md
@@ -251,7 +251,7 @@ packages are signed with.
 
 ## Debian
 
-Maintainer: Taavi Väänänen <hi@taavi.wtf>
+Maintainer: Taavi Väänänen <taavi@debian.org>
[message trimmed]

According to its manpage, you can pass --extra-suites= to specify a 
comma-separated list of additional suites. I've never tried it though, 
and I don't ever recall seeing the same issue on the Debian image.

Taavi

When building a new jammy image, debootstrap by default only includes 
the main jammy APT suite, and then the genimg script then adds extra 
suites (for example jammy-security and jammy-updates) to the 
sources.list file later to be used for any future apt commands.

However to build a mantic image on jammy, you need the distro-info-data 
package from jammy-updates[0]. debootstrap pulls down the 
distro-info-data package from the jammy suite as a part of the base 
image for some reason, and the manual `sudo apt update && sudo apt 
upgrade -y` you tried pulls the newer version from `jammy-updates` which 
explains why it fixes the build.

[0]: https://packages.ubuntu.com/source/jammy-updates/distro-info-data

Is the third-party repository actually necessary? Current Debian stable 
ships with Node 18 and NPM 9 which is well within Eleventy's required 
Node 14 or newer.

Taavi

I got a request to update the arm64 variant of the debian/sid image as 
the listed maintainer of the Debian builds.sr.ht images. Could a staff 
member with the required access please trigger a manual update for that 
image?

Second, is there any historical context why there is an arm64 image for 
sid? The image pre-dates me taking over the Debian image maintenance, 
and as far as I can tell from [0] it's the only non-native and only 
manually updated image out there.

[0]: https://man.sr.ht/builds.sr.ht/compatibility.md

Taavi

Changes the error message for trying to run a non-existent architecture
to mention that it's specifically the architecture that's missing and
not the specific image (which is checked at the very start of the file).

The error message for a non-existent image is clarified a bit too, to
make it more clear what's wrong in the manifest, instead of how the
runner is detecting that.
---
 images/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/images/control b/images/control
index 4091ebd..b468e37 100755
--- a/images/control
[message trimmed]

---
 builds.sr.ht/compatibility.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/builds.sr.ht/compatibility.md b/builds.sr.ht/compatibility.md
index f783120..69bfe20 100644
--- a/builds.sr.ht/compatibility.md
@@ -251,7 +251,7 @@ packages are signed with.
 
 ## Debian
 
-Maintainer: Drew DeVault <sir@cmpwn.com>
+Maintainer: Taavi Väänänen <hi@taavi.wtf>
[message trimmed]

On 7/1/23 19:44, Simon Ser wrote:
> Have you tested this mutation? (Could be done with the GraphQL playground
> for instance, or hut(1).)
> 
> I would've expected "PUBLIC" to require double-quotes, but maybe I'm
> wrong.

I did test it using the playground. It's a GraphQL enum, and apparently 
that means you can't use quotes around it, and you get an error saying 
"Enum cannot represent non-enum value" if you try.

This patch restores the status quo for the refresh jobs being visible
at https://builds.sr.ht/~sircmpwn/refresh from before builds.sr.ht
gained the concept of job visibility.
---
 contrib/submit_image_build | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/submit_image_build b/contrib/submit_image_build
index e3d7137..93b01c2 100755
--- a/contrib/submit_image_build
+++ b/contrib/submit_image_build
@@ -46,7 +46,7 @@ if from_image:
 url = f"{url}/query"
 query = """
[message trimmed]