Read hard, get it all caught up :-D

Things are (actually) going on around the community (surprise!), you may find latest news and happenings in and around the community, and of course, latest information for you to better enjoy AOSC OS.

Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program. – Linus Torvalds


  • AOSC OS Stable Branch: All Clear!AUGUST 5, 2019

    We were made aware earlier today that our Stable repository is currently in an inconsistent state. As of August 5th at 6:25 UTC time, we have resolved all known dependency issues and you may proceed with updating or installing packages on your AOSC OS installation.

    Thank you for your patience and understanding.

  • AOSC OS Stable Branch: Dependency IssuesAUGUST 5, 2019

    We were made aware earlier today that our Stable repository is currently in an inconsistent state. You may run into dependency issues when trying to update or install packages on your AOSC OS installation. This issue was introduced from our recent change in the update testing procedures for the Stable branch - and we are currently working on resolving these issues.

    For the meanwhile, please refrain from updating your system; when installing new packages, should you run into any dependency issue: we are aware of these issues.

    We apologise for the inconvenience.

  • AOSC Community Repository: Service RecoveredJULY 31, 2019

    As of 19:06, July 30 (UTC), the community repository has recovered from the unexpected downtime.

  • AOSC Community Repository: Unexpected DowntimeJULY 30, 2019

    Apologies for the delayed notification, but our repository has been down for more than 12 hours due to an unexpected issue. We are currently working with the hosting agency, and will keep you posted with further updates.

    We apologise for any inconvenience - please refer to our mirrors for system updates and package installation.

  • Weekly Community Report: Issue 28, 2019JULY 7, 2019

    Well, it’s been yet another… two months (?!) since the last community report.

    Let’s not make this a trend - but the writer of this series of news posts was drowned in packaging tasks to finish off the last wave of updates. Plus we are now just four days away from AOSCC 2019, so at any rate, we should have posted something anyways - right?

    Winter Wave: 7 Months Late

    The last update cycle has been nothing short of disastrous, with way too many features planned and crammed into the 3-month timeframe (which should have ended before 2019). Well at least it didn’t turn into another Windows “Longhorn”, phew!


    But as a user, while you may be angry at the delay - and rightfully so - we have worked (literally) beyond our capacity to bring you a ship load of system-wide upgrades…

    • All architectures have ~50% of their packages updated or refreshed. With this huge pass of builds, we have eliminated a huge amount of quality (and thus usability) issues with our packages - owing to our new Quality Assurance project led by Gumblex. We hope that you won’t miss the golden age of application launch errors.
    • Major component updates - most notably, OpenSSL 1.1, Python 3.7, and GCC C++ ABI upgrade. This is actually the main reason for the delay, across our five active architectures (plus one data/architectural-independent “architecture”), over 10,000 packages were built.
    • Core 6 “Fsck” is here! One year late. All toolchains and basic runtime components like the GNU C libraries are now up to date.
    • Device support improvements, such as (but not limited to)…
      • Added support for Intel Wi-Fi 6 AX200 wireless cards.
      • Improved support for post-Sony Vaio laptops, specifically, their keyboard backlight controls.
      • Added support for PineTab and its peripherals.
    • Package updates as usual, you know the drill. But admittedly we are a little behind on desktop environments for reasons stated above.

    You should be able to obtain the (large set of) updates now. However, we are aware of an issue that might prevent a smooth update. We have documented the cause and workaround in this Errata entry.

    Again, we are sorry about the delay and will work on cycle management improvements in the coming AOSCC sessions.

    AOSCC 2019

    On July 12 - 14th, AOSCC 2019 will take place in the University of Science and Technology of China - in Hefei, China. This three-day community gathering will provide loads of fun and giggles… and of course, ample opportunities for face-to-face discussions on community projects, talks from the friends of our community, and lucky draws.

    Since we didn’t get to meet last year due to venue troubles, we have greatly expanded our souvenir collection to try and make up for it. In keeping with our community traditions, we have made not one, but two pages of stickers for you meme aficionadoes!


    Additionally, we have made badges from the community, AOSC OS, and AOSC OS/Retro’s logos. These badges and the sticker sets are all free to take at the AOSCC venue - and available at the cost of postage after the conference.

    Information about attendance and schedules are availabe from the “AOSCC 2019” Wiki page. We look forward to seeing you there!

    — Mingcong Bai

  • Community Repository: All Systems Green!JULY 7, 2019

    Just a quick notice that we have fixed the issue earlier today and a full package scan has been completed. This issue was fixed with this commit. We will post a news update about the new wave of updates shortly.

    — Mingcong Bai

  • Unexpected Downtime on Repository ServerJULY 7, 2019

    If you are attempting to update your AOSC OS, or have already experienced trouble downloading packages (wrong sizes and checksums, etc.) - we are aware of this issue, and are working double time to resolve this issue. We have just finished up our (long overdue) Winter update wave, and moving ~10,000 packages triggered some obscure bugs in our package scanning toolkit, p-vector.

    • TL;DR: we are sorry, and are trying our best to get our repository back in normal order.
    • To our mirror maintainers, we have terminated our rsync service 15 minutes before this news, and this should explain why the syncing jobs are failing.

    — Mingcong Bai

  • Weekly Community Report: Issue 18, 2019APRIL 29, 2019

    AOSCC 2019 - It’s Happening!

    We are happy to announce that, after much searching, we have ourselves a host university for the AOSCC 2019 events!

    The AOSCC 2019 will take place in University of Science and Technology of China - in Hefei, China, on July 12 - 14th. The events details and venues are kindly negotiated and made available by LUG@USTC.

    Freezing Period

    On April 23rd, we have officially entered a month of freezing period for AOSC OS’s Testing branch. For the meanwhile, we are working to sync all package updates on the Testing branch, across all currently active ports.

    If you are using the Stable branch, you will continue to receive security and exceptional updates.

    AGX Xavier!

    To continue the tradition of mis-using NVIDIA’s development boards, we have obtained an NVIDIA Jetson AGX Xavier Developer Kit several days back. “JellyXavier,” as it is named as a BuildBot, is now available for all dev-pubkeys-registered AOSC developers at Relay port 24444.

    This build host will be dedicated to the building of AArch64 (arm64) packages. Formerly, both AArch64 (arm64) and ARMv7 (armel) packages are built on a shared BuildBot - an NVIDIA Jetson TX1 Developer Kit, with a measly 4GiB of RAM. In the recent cycles, we have been constantly plagued by this insufficient amount of RAM - and this in turn has resulted in the two ARM ports lagging behind the other architectures.

    The AGX Xavier, however, comes with 8 very fast NVIDIA “Carmel” cores, and 16GiB of RAM. Registering as the second fastest out of all Relay BuildBots. This hardware addition will undoubtedly help us catch up (and eventually enrich) both ARM ports.

    As for the Jetson TX1, it will now be dedicated to build ARMv7 packages (which of course, is much more available for this task).

    xavier-in-position Xavier in the Madison, WI. “Engine Room”.

    AOSC - How Moe Is… She?

    Over the past weekend, community member Shimizu Saki (清水 紗季) initiated the aosc-moe project - to create a “Moe,” anime-inspired character to represent our community.

    Confused? This is quite similar to the concept of an OS-tan - have a good read!

    At the time of writing, more details about the character’s name and other features are being finalised - and hopefully we will see her here on the Portal soon.

    Progess Report on the i586 Port

    At the time of writing, we have a bootable copy of AOSC OS i586 port! The port now contains packages needed for a “Base” variant tarball, and is now working towards a full-fledged desktop experience.

    The port is currently tested to run on a Sony PCG-C1VN sub-notebook. The sub-notebook is powered by a 600MHz Transmeta Crusoe processor, with 192MiB of RAM and 7GiB of HDD space made available for AOSC OS. The sub-notebook dual boots Windows Me - for my personal entertainment needs and a rudimentary test for GRUB functionalities.

    I am currently working to create a refined Kernel config for the port. At present, the port will boot and login with a memory footprint of approximately 20MiB. Not bad, if I may say so myself - but there are space for improvement, as we move more features out of the Kernel image, and built as modules. Having based our Kernel config on the AMD64 port’s, we have much to cut down.

    And finally, a video recording of the computer running a WindowMaker session.

    The AOSC OS/Retro Project

    With the i586 port going along, we have also started work on creating a set of visual designs for our OS/Retro family of ports. This family of ports will contain support deprecated and outdated architectures, such as i586 and the big endian PowerPC 32/64-bit devices. To better adapt to these older devices, system features and dependencies will be cut down, resulting in smaller install sizes and more reasonable performance (compared to the current PowerPC ports, which shares the same build configuration as all other “mainline” ports).

    The logo design was initially made by community member Neruthes, and further modifications made by me.

    poster Poster, “20th Century, Millennium, Present.”

    logo Logo, full colour, tilted.

    logo16 Logo, 16-colour.

    — Mingcong Bai, with regards.

  • Weekly Community Report: Issue 17, 2019APRIL 22, 2019

    End of Cycle (Imminent)!

    After some four months drowning in updates and rebuilds, the current cycle is now looking to start its one-month freezing period on Tuesday! In the coming month, we will work to smooth out the rough edges (.so dependencies, etc.) and make sure that Stable users will receive a smooth updating experience.

    Core 6

    After nearly a year in delay, Core 6 “Fsck” will ship as a part of this coming cycle update. Coming in this major Core update…

    • GCC 8.3.1, with many performance and new features from the upstream.
    • GNU C Library 2.29, and many other component updates.
    • Added i586 (yes, Pentium-class devices), and Loongson 2F, 3A/B support.
    • The ppc64 port will be specifically optimised for the PowerPC G5 processor - as our PowerPC 32/64-bit Big Endian ports are now built for the PowerPC-based Macintosh computers.

    The i586 Port

    The i586, now that we have mentioned it… Will serve as an experimental port, where we try and refactor parts of the AOSC OS dependency tree to make the system lighter to install and run. This will undoubtedly help us as a distribution which ports to newest, as well as vintage and long abadoned devices (from your newest Intel Coffee Lake laptops, to the “Clamshell” iBook G3’s).

    The reference device for this port will be the 2001 Sony Vaio PCG-C1VP running Windows 2000 (its owner - me - is considering swapping out he motherboard with one from the PCG-C1VN for Windows 9x support). This machine comes with the following (rough) list of hardware:

    • Transmeta Crusoe TM5600 @ 600MHz (Hi there Mr. Torvalds!)
    • 192MB RAM (16MB eaten by the processors CMS - Code Morphing Software)
    • 15GB HDD @ 4200RPM, dual booting Windows and AOSC OS
    • 1024x480 LCD


    We’ll see how it goes over the summer - maybe we’ll see it as a demonstration machine at AOSCC 2019!

    Taming ACBS

    Our venerable infrastructure contributor and resident Python guru @gumblex is currently undertaking a massive refactor for our ACBS (Autobuild CI Build System), which our packagers use to build packages daily.

    With this factor, we are hoping to see more reliable sequential/batch build support and dependency resolving.


    Utilising a tool from @gumblex, we have now covered most packages in our ABBS Tree and Core Tree with SHA256 checksums.

    Further more, we have now made it imperative to include checksum when packages from a source package/tarball.

    Security Update Workflow and AOSA Announcement

    Effective next week, we will start posting AOSA (AOSC OS Security Advisory) whenever the updates are ready for all branches. Formerly, AOSAs for the Testing branch will be delayed until it merges with Stable at the end of each cycle. Additionally, security issues that affects both Stable and Testing branches will be announced under a shared AOSA ID, as long as they describe an identical issue.

    Furthermore, our contributor @KexyBiscuit has offered to work on announcing future advisories in the future - after I have become too busy to write up security reports.

    — Mingcong Bai

  • Weekly Community Report: Issue 15, 2019APRIL 8, 2019

    So, let’s kick off the weekly updates (*note: issue “15” for this is “week 15” of 2019)! I’m still trying for a good format at the moment (and also tight on time), but hopefully we will see better quality in future posts.


    We are currently trying to wrap up the current cycle (which has been dragging on for almost six months at this point) - there are still hundreds more packages to rebuild for the upcoming Core 6 (GCC C++ ABI, and Perl 5.28). After these rebuilds are sorted for AMD64, we will go into a month-long freezing period - hopefully starting on April 26th. During this freeze period, the rest of our ports will be synchronised.

    In this cycle, we have updated or rebuilt virtually all packages in the repository - mostly because of other major updates, namely Python 3.7 and OpenSSL 1.1.

    Now, having trapped ourselves (and you) in this extremely long cycle, we are looking to shorten the next one - focusing on updating all major desktop environments and their components - GNOME 3.32, Plasma 5.16, KDE Applications 19.04, MATE Desktop 1.22, etc.

    We are also working on transitioning our RISC-V port (riscv64gc) port into “regular” maintenance - it will have working Testing and Stable branches, and ready to follow future cycle schedules by the end of this cycle.

    Looking back into history (literally), we have been putting (low-priority) effort into creating a new i586 port for 32-bit only, Pentium (1993) and newer devices (Pentium II, Pentium III, Transmeta Crusoe, …). We are also planning to create specialised configurations for ports targetting older devices (i586, mips64el, powerpc, and ppc64), while sharing the same Core and ABBS tree - more detail to come in future weeks.

    Community Infrastructure

    A new Telegram bot has been created by The Salted Fish, which manages a game of Last Man Standing… Where people who unfortunately can’t go to sleep early can entertain themselves with competetive “staying-up.”

    Of course, we don’t endorse such unhealthy behaviour… But if you’d like to have some fun while not asleep in early morning - here’s one option.

    Okay, that should do it for this week. Come back next Monday at 6:00AM for more community and project updates!

    — Mingcong Bai