~haowenl

~haowenl/berlyd-portfolio-devel

Last active 3 years ago

~haowenl/berlyd-portfolio-announce

Last active 3 years ago
View more

Recent activity

Re: [PATCH builds.sr.ht] ubuntu/noble starts development a month ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

On 1/23/2024 6:19 AM, Conrad Hoffmann wrote:>
> Can you please re-submit the patch and include a link to a successful 
> build log?
> 
> Cheers,
> Conrad

[1] and [2]. I'll send another pair tomorrow or the day after to remove 
23.04.

Haowen

[1] https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/48877
[2] https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/48876

[PATCH sr.ht-docs] ubuntu/noble starts development a month ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

---
 builds.sr.ht/compatibility.md | 53 +++++++++++++++++++++++++++--------
 1 file changed, 41 insertions(+), 12 deletions(-)

diff --git a/builds.sr.ht/compatibility.md b/builds.sr.ht/compatibility.md
index afcfb78..aca1e65 100644
--- a/builds.sr.ht/compatibility.md
@@ -1102,7 +1102,7 @@ information.
      <td><code>arch: amd64</code> (default)</td>
      <td style="text-align: center; color: green">✓</td>
      <td style="text-align: center; color: green">✓</td>
      <td>daily</td>
      <td>weekly</td>
[message trimmed]

[PATCH builds.sr.ht] ubuntu/noble starts development a month ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

---

Successful build log: https://builds.sr.ht/~haowenl/job/1137305

Also moving aliases in crontab to actual releases to make it clear what
is being refreshed. Like rn, ubuntu/23.04 and ubuntu/23.10 are not being
refreshed at all and it's hard to tell if crontab uses aliases.

ubuntu/23.04 isn't being added here because it will reach EOL tomorrow.
Will send another patch to remove it.

 contrib/crontab               | 9 +++++----
 images/ubuntu/24.04           | 1 +
 images/ubuntu/next            | 2 +-
[message trimmed]

Re: [PATCH builds.sr.ht] ubuntu/noble starts development a month ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

Hi Conrad,

Could you please check this patch once again? With this [1] commit, this 
patch should be good to go.

Haowen

[1] 
https://git.sr.ht/~sircmpwn/builds.sr.ht/commit/1b21add920b56007b8597db667e858a403a88b1d

Re: [PATCH builds.sr.ht] ubuntu/noble starts development 2 months ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

On 12/4/2023 9:50 PM, Taavi Väänänen wrote:
> 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

Thank you! I checked how genimg is doing things and it seems it 
currently overrides the source list after bootstrapping. I chose the 
route of less disruptive change and simply added an extra upgrade in the 
genimg process.

See [1].

[PATCH builds.sr.ht] ubuntu: upgrade packages during genimg 2 months ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

From: Haowen Liu <liu.haowen.andy@gmail.com>

---
This patch makes sure packages in all suites are properly up to date in
the generated image, rather than only those in the ubuntu main suite.

 images/ubuntu/genimg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/images/ubuntu/genimg b/images/ubuntu/genimg
index 6bf312e..14cba1b 100755
--- a/images/ubuntu/genimg
+++ b/images/ubuntu/genimg
@@ -110,6 +110,7 @@ deb http://archive.ubuntu.com/ubuntu/ $release-backports main restricted univers
[message trimmed]

Re: [PATCH builds.sr.ht] ubuntu/noble starts development 2 months ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

On 12/4/2023 9:44 PM, Taavi Väänänen wrote:
> 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

Re: [PATCH builds.sr.ht] ubuntu/noble starts development 2 months ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

On 12/4/2023 10:06 AM, Conrad Hoffmann wrote:
> I am not quite sure what to make of this?
> 
> [1] https://builds.sr.ht/~sircmpwn/refresh/ubuntu/lts
> 
> Cheers,
> Conrad

Yup, not sure either. One of the following three is happening:

1. genimg is building an outdated image to begin with
2. The updated version image is not properly deployed
3. The properly deployed version did not get used by builds.sr.ht

Re: [PATCH builds.sr.ht] ubuntu/noble starts development 2 months ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

On 11/30/2023 8:33 AM, Conrad Hoffmann wrote:
> I tried to apply this, but the image does not build (on /lts, at least?):
> 
> https://builds.sr.ht/~bitfehler/job/1104224

That is correct. But that is unfortunately not caused by the genimg 
script. The current ubuntu/next is also failing [1].

This is caused by the ubuntu/lts image being VERY VERY out of date. 
Inserting `sudo apt update && sudo apt upgrade -y` fixed the issue. This 
is a repro [2] on the current ubuntu/next 4 months ago. It's fair to say 
that ubuntu/lts hasn't been updated, for some unknown reason, for at 
least 4 months now.

Re: [PATCH builds.sr.ht] ubuntu/noble starts development 3 months ago

From Haowen Liu to ~sircmpwn/sr.ht-dev

On 11/16/2023 6:33 AM, Conrad Hoffmann wrote:
> 
> Any specific reason you are replacing the symbolic names with explicit 
> versions here? Seems like that will just require more changes in the 
> future?

Here are my thoughts:
1. Yes. That requires more changes in the future. But that might be a 
good thing, because we would need to update it EVERY time we update it. 
That way it's much less likely for people to forget than something that 
needs changing every approximately 3 times we change ubuntu. Also, we 
know immediately if we forget to update, rather than having one image 
silently being out of date.
2. I see [1] and want to follow what people are doing.