From Haowen Liu to ~sircmpwn/sr.ht-discuss
On 6/20/22 13:25, Drew DeVault wrote:
> Not really, sorry. Can't prioritize it right now.
Alright. I'll work on other things.
From Haowen Liu to ~sircmpwn/sr.ht-discuss
On 6/20/22 13:21, Drew DeVault wrote: > Nah, I'd wait for now. Would be good to tackle it following the (oft > postponed) builds overhaul. Makes sense. Does anything related to the overhaul need help? I just got a lot of extra time and want to involve further in meaningful ways.
From Haowen Liu to ~sircmpwn/sr.ht-discuss
On 6/20/22 13:19, Drew DeVault wrote: > multi-arch is still not complete and even the debian image is not > recommended for use Should I work on it then? Is there a tracker for its current issues and todos?
From Haowen Liu to ~sircmpwn/sr.ht-dev
--- According to crontab debian/oldstable is updated monthly. 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 f4a5984..04c34bf 100644 --- a/builds.sr.ht/compatibility.md @@ -388,7 +388,7 @@ See also: [upstream releases](https://www.debian.org/releases/) <td><code>arch: amd64</code> (default)</td> <td style="text-align: center; color: green">✓</td> <td style="text-align: center; color: green">✓</td> [message trimmed]
From Haowen Liu to ~sircmpwn/sr.ht-discuss
Hi Drew and others, I see that Debian Sid has experimental arm64 support. What do you feel about expanding this support to other images (specifically Ubuntu, Fedora, and Rocky Linux that I maintain)? I also see that it's manually updated for now and I imagine this will be a more involved process maintaining more distros manually. Should I also setup automatic image refresh for those? Would adding appropriate tasks to crontab be sufficient? Haowen
From Haowen Liu to ~sircmpwn/sr.ht-dev
--- builds.sr.ht/compatibility.md | 1 - 1 file changed, 1 deletion(-) diff --git a/builds.sr.ht/compatibility.md b/builds.sr.ht/compatibility.md index f4a5984..5adaf9c 100644 --- a/builds.sr.ht/compatibility.md @@ -1014,7 +1014,6 @@ information. <th>Ubuntu Jammy (22.04)</th> <th colspan="3" style="font-weight: normal; text-align: center"> <code>image: ubuntu/lts</code> <strong>or</strong> <code>image: ubuntu/next</code> <strong>or</strong> <code>image: ubuntu/jammy</code> <strong>or</strong> [message trimmed]
From Haowen Liu to ~sircmpwn/sr.ht-dev
--- builds.sr.ht/compatibility.md | 28 +--------------------------- 1 file changed, 1 insertion(+), 27 deletions(-) diff --git a/builds.sr.ht/compatibility.md b/builds.sr.ht/compatibility.md index 9f51aae..f4a5984 100644 --- a/builds.sr.ht/compatibility.md @@ -451,7 +451,7 @@ Maintainer: Haowen Liu <lhw@lunacd.com> <table class="table table-sm table-hover"> <thead> <tr> <th>Fedora Rawhide</th> <th>Fedora 36</th>[message trimmed]
From Haowen Liu to ~sircmpwn/sr.ht-dev
--- contrib/crontab | 2 +- images/fedora/34/functions | 1 - images/fedora/34/genimg | 3 --- 3 files changed, 1 insertion(+), 5 deletions(-) delete mode 120000 images/fedora/34/functions delete mode 100755 images/fedora/34/genimg diff --git a/contrib/crontab b/contrib/crontab index 1f1a8a0..31e945b 100644 --- a/contrib/crontab +++ b/contrib/crontab @@ -24,6 +24,6 @@ 0 18 1 * * chronic /usr/local/bin/submit_image_build -n "Monthly scheduled build image refresh" -a amd64 ubuntu/oldlts [message trimmed]
From Haowen Liu to ~sircmpwn/sr.ht-dev
On 5/13/22 01:59, Drew DeVault wrote: > I'm not sure that this is a particularly good idea. Manually maintaining > the crontab seems easier than maintaining some YAML stuff to generate a > crontab. Gotcha.
From Haowen Liu to ~sircmpwn/sr.ht-dev
On 5/6/22 05:57, Drew DeVault wrote:
> Missing a corresponding sr.ht-docs patch and crontab update.
Just sent a sr.ht-docs patch. Since ubuntu/next is already in crontab,
no crontab update is necessary.
Also, this is probably not the right place, but just briefly:
I would have more time soon and I'm thinking about having each image
provide some sort of metadata (refresh interval, architecture, EOL date,
etc.) in e.g. YAML file. Then things like crontab can be auto-generated.
I'm not sure about image removal on EOL, but it might be possible to
automate as well.