Chaotic-AUR
702 subscribers
5 photos
66 links
Newsletter and stability reports of aur.chaotic.cx

- Offtopics & Support group: @chaotic_aur_sac

- Down for everyone or just you? Check it here: status.chaotic.cx
Download Telegram
Hey people πŸ‘‹
You might have noticed that updates were no longer pushed since Saturday - this is due to a full repo rebuild we started with the goal of a general cleanup and having everything compiled with the new toolchain. Initially, the plan was to freeze the mirrors and be done with it yesterday but things are taking longer than expected. Our mirrors will resume syncing once a missing set of packages has been fixed 😊
It's also worth noting that some packages will return at a later date while some others won't return at all due to compilation issues or PKGBUILDs being gone from AUR πŸ‘€

Update: the mirrors are fully synced up again πŸ‘Œ
It is now possible to use an IPFS mirror thanks to the pacman.store project providing it! The address can be found in the updated mirrorlist (of course disabled by default) while usage instructions can be found on the projects git repo πŸš€
Hello everyone! πŸ‘‹πŸ»
I hope you are alright and feeling fine! During the last few hours, a major repository cleanup & a lot of package fixes took place. The cleanup had the goal of spending less time building these packages & wasting less energy.

Most of the removed packages concerned the garuda-builder routines - here a lot of the listed packages were in fact not used anymore by respective maintainers, making them redundant. Some other packages were either severely outdated or not building anymore for a longer period of time.

This might have the side effect of also having removed a few packages that other people were using (as the packages were never requested since they were available already). If you are wondering why a package is suddenly marked as "foreign" if it wasn't before, it is very likely that the cleanup was causing it.

Don't be afraid, we can easily add them back (given they build successfully) - just open up an issue at our packages repo and we will handle the rest! 😊

At this point, since we never really had a proper announcement, I would also like to thank @Technetium1 and @alex_j_p for helping out with package maintenance and @itsTyrion and @shrirangkahale for providing their mirrors. ☺️

Finally, 5.18 TKG kernel builds are getting started soon, the toolbox was still building 5.17 ones until now. That's it for now, have a nice time! 🐱
Sup everyone! πŸ‘‹πŸ»
We have some cool news regarding a (massive) bunch of new mirrors thanks to @edu4rdshl, @ayulauffer and @alissonlauffer! πŸŽ‰πŸ˜
The new locations are as follows:
- Arizona, USA
- Australia
- Brazil 2
- Canada 2
- Chile
- Finland
- Hong Kong
- New York, USA
- Saudi Arabia
- Taipei City
- United Arab Emirates
- Virginia, USA 2
As usual, our geo-mirror will route requests to the nearest location automatically, for those who prefer to do it manually there is the updated chaotic-mirrorlist.
Cheers! πŸ§‘πŸ»β€πŸ’»
Forwarded from TNE
Did some codering today and came up with a fancy lil project

Ever wondered where the chaotic mirrors are and which one is used? Well now you can know!
https://status.chaotic.cx/map
Also super great if you want to consider hosting a mirror wink wink
We're aware of connection issues in our main router, we're investing it, expect instability in all mirrors and .chaotic.cx domain.

UPDATE: Problem bypassed!
Chaotic-AUR pinned Β«We're aware of connection issues in our main router, we're investing it, expect instability in all mirrors and .chaotic.cx domain. UPDATE: Problem bypassed!Β»
It is time for another announcement! I hope everyone is feeling good ☺️
After having performed a full repository rebuild due to OpenSSL 3 hitting the Arch repositories, a few packages aren't yet back. We are tracking the progress in this GitHub issue! πŸ“‘
A merry Christmas to everyone! Have a nice time and take care of yourselvesπŸŽ„πŸŽπŸ€—
Hello everyone! πŸ€—
We have a new statuspage powered by Upptime! πŸŽ‰ Being completely driven by GitHub actions, it is also able to automatically create issues and tag the corresponding maintainer in case of outages. Its repo can be found here. πŸ‘€
Chaotic-CDN is back! A big thanks to @makzk for providing a mirror in Chile as well as @ayulauffer for providing Silky.Network mirrors! ❀️

Our mirror map has become pretty green again😊
Officially releasing https://github.com/chaotic-cx/nyx today

It works for any distro with nix package manager installed, though Linux-only (no Darwin) and the modules are NixOS-only. Includes daily bumped gamescope_git, mesa_git, sway_git, yuzu-early-access_git.

For non-nixers, you can run any of these things without installing system-wide, like: nix run github:chaotic-cx/nyx/nyxpkgs-unstable#gamescope_git -- -w 1920 -h 1080 -W 3440 -H 1440 -b vkcube

Updates on a separated tg channel: @chaotic_nyx
We are aware of the python 3.11 bump, we're rebuilding stuff already, there are a lot of packages please be patient.

If stuff fails, please rebuild them from AUR (specify "aur/" to your helper, like "paru -S aur/python-mydarilingpackage"), most python packages are light, or wait a little more before upgrading.
Hello chaotic community πŸ€—

Some of you might have noticed a new username among our maintainers lately - therefore I'd like to officially welcome @stackofprimes (xiota), who is going to help with general package maintenance πŸ₯³
They already initiated a massive cleanup of broken / obsolete packages as well as a lot of package fixes which also means having more space for other applications πŸŽ‰
The Arch Linux project announces that they are retiring the community repo since Chaotic-AUR got it covered. It's mirrors are currently in progress of being synced to reflect those changes πŸš€
/s
One of our signing keys expired today, causing packages to fail to install with the key being marked as "is unknown trust" - we are aware of this and try to get it fixed as soon as possible, while also ensuring a condition like this does not occur again! πŸ”§

Update: we are back to regular business.
Whats up everyone! A lot of time passed since our last announcement. As usual, we hope everyone is feeling fine ☺️

The reason for this announcement is the EOL of linux-tkg kernel builds in our repository. Since we used to provide these since the early beginning, we felt that an announcement explaining the reasoning behind this decision was necessary. The main reasons are:
- Introduced maintenance burden due to missing options in the kernel config. Since these were missing from time to time, user input was necessary to continue the build process. No other kernel showed this kind of behaviour and confirming the use of the default option for all kernel variants is a quite time consuming and annoying task. Opening issues every time this happens is also unsustainable long-term.
- Maintainers making use of it moved to linux-cachyos variants and therefore don't need linux-tkg anymore.
- Not having a dedicated builder for these packages anymore. During the last months, they were built on demand to not introduce too much load to the main builder. This means builds were sometimes happening too late (or stalled due to the previously mentioned kernel config issues because we can't babysit the process for multiple hours)

As an alternative, we can recommend the linux-cachyos kernel variants of @ptr1337. They have proven to be great kernels. In case of popular demand, we also might add additional variants of this kernel 😊
Hello, everyone πŸ€—

We have some interesting news to share - Chaotic-AUR's new website just went live πŸŽ‰
What started as a project to learn and improve Angular and Typescript skills quickly evolved into a useful tool for all Chaotic-AUR users and maintainers πŸ˜„ Not only is our memorial finally in place, but we can also show basic stats about packages and deployments. While we have a dedicated channel for news and deployments, these channels haven't been easily available to non-Telegram users. This changes today 😊 An important note about the deploy logs: these show the deployments of our currently in-development infra 4.0 as a preparation for its launch - the pilot phase is currently in progress. The features of the website will eventually be expanded in the future, as soon as we have more monitoring set up for our new build system 🧐

PS: If you find any issues with the website don't hesitate to report them to @dr460nf1r3 πŸ‘Ύ
Chaotic-AUR turns six years old on October 18! πŸ₯³

It has been three years since celebrating Chaotic-AUR's birthday with a memorial.
We would love to repeat this occasion this year, as it's the exactly double the years as the last time! ☺️

Let's see what happened in the meantime πŸ•΅

- Our user count is currently around 107k per month;
- The amount of offered packages is roughly 3400 (after a big cleanup happening)
- Active mirror count decreased to 12, but the CDN-mirror is powered by blazing-fast Cloudflare R2 these days
- The website got a complete rewrite and now offers a lot of useful functionality, such as viewing package lists and stats, build processes, and more information
- Though not directly Chaotic-AUR-related, the Chaotic-CX spaces gained a new project via Chaotic Nyx
- And there is something else really cool coming up at the day the birthday takes place (you might guess what it is - it's been hinted at in several places πŸ˜‹) ! Stay tuned! πŸ˜‡

This time, we will also be collecting screenshots of terminals and desktops showing fastfetch with the Chaotic-AUR logo. To take part in this special day, the following is needed:

- fastfetch (get it via Arch repos)
- The Chaotic-AUR logo
- Run fastfetch like that: fastfetch --logo ~/Downloads/logo.png --logo-width 45, replacing the location with the location the logo has been downloaded to, and width with something that makes the image fit the height of your fastfetch output
- Take a screenshot and either add a PR to the memorial repo, send it to memorial@chaotic.cx, @dr460nf1r3 or the group chat

Submissions will close on October 18, the day the birthday takes place.

A big thanks to everyone helping us with achieving the things we did during the last years. It certainly wouldn't be the same without you! ❀️
Three days are left for memorial submissions! ☺️
Today is a special day because it marks the 6th birthday of this project, as well as the day when the next big evolution of our build tools finally goes live.

While we already highlighted the most prominent changes between those three years in our previous post, it is a pleasure to be officially announcing our new build system, also called infra 4.0 ☺️ This is the end of a journey that took more than half a year to finally be filling close to all Chaotic-AUR build requirements. While this is primarily a solution written for Chaotic-AUR, it is still a generic solution everyone wanting to compile PKGBUILDs on smaller or larger scale can adopt.

Why would we need a new build system if the old one was working well? The question is easy: the pre-assumptions the previous infra had, like inhomogeneous builder landscapes lead to some drawbacks (while serving a really good job for many years nevertheless!). One of them is that we continually need to run routines to check packages for new updates, another one being unable to control the allocation of builds to individual builders.
This time, we were able to work with different pre-assumptions, which allowed us to optimize the entire process to a great extent. The fact that we've been running the entire load of Chaotic-AUR in our infra 4.0 test environment on our main builder besides the regular builds is a great example of how efficient it has become.

Since the entire process consists of GitLab CI pipelines and a central instance for managing build processes after they have been scheduled by the pipelines, it is also much easier for users to figure out when packages were updated, as well as being able to inspect logs for multiple revisions of builds. This also means that our well-known packages repository is now mainly operated on GitLab CI due to making use of their CI tools. To preserve issues and comment histories, the "old" repository will be kept as a read-only mirror of the main repository, and also kept open for issues and bug reports.

There are many other changes and new features, like:
- Builds getting scheduled on demand (read: whenever an AUR package changes and CI pipelines pull in the updated files, or someone pushes a change to a locally maintained package) rather than with every routine run
- Live logs can be opened either via the pipeline's external stages, as well as being presented on our status page of the website. If you always wanted to watch your Ungoogled Chromium build logs in real-time - now it is possible 😎
- Build queues are visible to the public, also on the status page
- Support of build for multiple repos at once
- Saving/Restoring build queue state on builder/manager shutdown
- Dependency trees
- Automated lib bumps (which are not enabled for most packages, as adding deps is a manual process. The plan is to enable this for more packages in the following months)
- No more split repos for packages and interference - the repo now consists of folders, one for each pkgbase. Inside it, you may find a .CI folder with interferes and further builds configurations
- Being able to maintain a PKGBUILD on Chaotic-AURs repo, and pushing it back to AUR automatically, whenever a new change gets pushed. This opens a door for AUR packages to be community-maintained via PRs (looking at you, proton-ge-custom!)
- The state present in the packages repo fully reflects the state of the repository. Packages not present will automatically be removed
- Being able to review non-trivial package updates (which is opt-in and turned off for Chaotic-AUR. Might explore the idea of a reviewed/trusted subset of packages in the future)

For everyone wanting to take a closer look inside, dedicated documentation is available here.

At this point, I want to especially thank two people, who played a major role in making this possible.
- TNE, whose ideas and visions ensured all of it became as efficient as it turned out.
- xiota , who did close to all of the heavy lifting regarding porting our current set of packages to v4 and provided feedback on build processes and existing issues