Thanks!

To git@git.sr.ht:~sircmpwn/sr.ht-docs
   dbbd129..ae651dd  master -> master

hg.sr.ht is being migrated to a new server soon. Writing up the plans
here for posterity.

1. Build & install the new server (alice5) per normal Alice provisioning
   procedure
2. Announce planned outage a week in advance
3. Spin up an hg.sr.ht stack and restore from the last backup. This is a
   good opportunity to test our backups in action.
4. Test everything!
5. Await planned outage date
6. Set hg.sr.ht¹ to read-only mode (via pgbouncer, probably, and disable
   the hg SSH login account)
7. rsync any changes which have occured between steps 3 and 6 to
   hg.sr.ht²

Thanks!

To git@git.sr.ht:~sircmpwn/git.sr.ht
   567aee1..3bb19d0  master -> master

Thanks!

To git@git.sr.ht:~sircmpwn/sr.ht-docs
   ae651dd..d7c9c78  master -> master

This looks good to me, but can you send it again for CI? I just made
some of the build manifests more tolerant of missing secrets.

git.sr.ht annotations are deprecated
---
 .builds/annotate.yml | 24 ------------------------
 1 file changed, 24 deletions(-)
 delete mode 100644 .builds/annotate.yml

diff --git a/.builds/annotate.yml b/.builds/annotate.yml
deleted file mode 100644
index f0bfd3a..0000000
--- a/.builds/annotate.yml
@@ -1,24 +0,0 @@
-image: archlinux
-packages:
[message trimmed]

You should already automatically be subscribed to tickets you submit. If
not, it's some other bug.

Not a great idea. It'd be difficult to do - where do we store the list
of built changes? builds.sr.ht isn't responsible for that, so it'd fall
on git.sr.ht, presumably. Does it put them in redis? Does this get
expensive?

Also, after you merge or rebase commits from your feature branch to
master, their hash changes. So now we're deep comparing commits, and we
have to store the full patch somewhere instead of just the sha to know
that we've already built it.

On Tue Jul 14, 2020 at 7:41 AM EDT, Thomas Merkel wrote:
> Thanks for your feedback. Sadly I do not have a fully function sr.ht
> environment running.

Sending a bunch of untested patches and burdening me with
troubleshooting your work is the same crap which happened with all of
the previous NetBSD attempts, too. This is a non-trivial task with lots
of opportunities to break, you need to test it end-to-end before sending
me a new patch.

> Is it possible to use only a small setup of builds.sr.ht locally to
> test it manually?

No, but it's not especially difficult to set it up locally anyway.

Thanks!

To git@git.sr.ht:~sircmpwn/man.sr.ht
   470b959..6fbc80e  master -> master