Ah, I see

Well, I hate to say it, since I assume you're not in our Discord, but this project is no longer being actively developed.

I have taken Amethyst into packages that I intend to care for as part of Krypton Linux, my next project that aims to be a daily usable Arch OpenRC fork. You can read more at https://mattcompton.dev/blog

The new repo is https://gitlab.goober.cloud/krypton/amethyst

Which doesn't yet have registration enabled. If you'd like to develop on Amethyst, please let me know.

...

On October 25, 2025 11:50:41 AM EDT, "Mohammad Hisham Sayed (@avahi_daemon)" gitlab@mg.gitlab.com wrote:

Mohammad Hisham Sayed commented: #9 (comment 2845158076)

Hello @SomethingGeneric. No, actually some systems remain unupdated for a long time. Especially when ISO's are old enough to cause issues with keyrings. It has also happened that the day ISO's were released of prominent distributions the next day there came a keyring update which made updating via pacman -Syu really hard especially for beginners. I intend to keep this approach as close to manjaro's. In manjaro, first keyrings are checked for update then the whole system is updated.

-- Reply to this email directly or view it on GitLab: #9 (comment 2845158076) You're receiving this email because you have been mentioned on gitlab.com.

thanks for the bits

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.

---

Detected Package Files

• .gitlab-ci.yml (gitlabci)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding MR is merged
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Merge Request description the next time it runs.

---

What to Expect

It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

---

This MR has been generated by Renovate Bot.

it's a pkgbuild, hush

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.

---

Detected Package Files

• .gitlab-ci.yml (gitlabci)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding MR is merged
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Merge Request description the next time it runs.

---

What to Expect

It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

---

This MR has been generated by Renovate Bot.

it's a pkgbuild, begone

it's a pkgbuild, go away

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.

---

Detected Package Files

• .gitlab-ci.yml (gitlabci)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding MR is merged
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Merge Request description the next time it runs.

---

What to Expect

It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

---

This MR has been generated by Renovate Bot.

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.

---

Detected Package Files

• .gitlab-ci.yml (gitlabci)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding MR is merged
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Merge Request description the next time it runs.

---

What to Expect

It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

---

This MR has been generated by Renovate Bot.

it's a pkgbuild, go away

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.

---

Detected Package Files

• .gitlab-ci.yml (gitlabci)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding MR is merged
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Merge Request description the next time it runs.

---

What to Expect

It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

---

This MR has been generated by Renovate Bot.

no need

Fixes #7

Hi @avahi_daemon, this was likely a result of a partial upgrade to your system. Presumably it's resolved by now?

Closing since we responded and explained the happenings on your GitHub repo