Just a quick update that we have confirmed that our repository server is now up and running, all regular services have returned to stable status.
Again, we apologise for any inconvenience experienced.
At this point (well beyond 12 hours), we are sorry to announce we are yet to be able to have our repository server up for service. Our host over at Taiwan is still having issue from within OSSPlanet’s datacenter…
Here are two updates we received from our partner Matthew Lien…
At 5:23 UTC, August 19th.
All public networks working now. Two PSU[s] on SAN (Storage Area Network) Switch failed at once. The chance is lower than winning the lottery, but it really happened. Trying to fix it.
At 14:53 UTC, August 19th.
Our DC staffs are trying to recover VM [Virtual Machine] infra. Sorry for the unexpected inconvenience...
Therefore, please keep watching out for updates in the coming day. We do as well apologise for any inconvenience with this unfortunate repository downtime.
Due to damaged high voltage power lines and equipment at our host for community repository, we are expecting an one-day downtime for this server.
At the meantime, we would recommend that you:
We apologise for any inconvenience.
Here below is a copy of the original announcement from our server host OSSPlanet:
MAINTENANCE DOWNTIME: 2017/8/19 9am-4pm CST (1am-8am UTC) In short: Tomorrow. We are going to have a maintenance downtime for damaged High Voltage power lines and equipment (ATS) to prevent further unexpected issues in case of power outage. Please shutdown your VMs before 7am CST (8/18 23:00 UTC) to prevent any data lose. We're sorry for the inconveniences. If you need any assistance, please feel free to contact us.
With a somewhat successful completion of the monthly update cycle in the July Wave, we have just finished discussion on goals/objectives in the August Wave of updates. The focus or the theme, if you like, of this month will be refinement and clean up.
First of all, a majority of work to be done this week will be dictacted by ACID - a CI-like mechanism which builds every single packages on offer in the ABBS Tree. Packages to be fixed are mounting up to couple hundreds at present, and that will be what we are doing this month - fix them while the number climbs even higher. In addition to that, new commits introduced to our Autobuild3 toolkit - if you haven’t heard of it yet, it’s our only official packaging tool for AOSC OS - increased the level of strictness while running build scripts, loads of old scripts should end up failing. It’s better to rebuild these old and low-quality packages preemptively than ending up as bugs discovered by users, and this is exactly why we are doing this in August.
While handling this potentially significant task load, in August…
longtermlabel, should be re-investigated and (if time allows) fixed, or else closed (if justified).
How about package updates then? Those not specifically requested by community members will be handled according to time allowance in August - while of course, those requested will be dealt with with priority. As always, security and urgent bugfixes will be provided at instance of availability as usual, no worries there.
Hopefully, in September we developers and users will be working with a cleaner copy of AOSC OS.
— Mingcong Bai
Today marks the conclusion to our first AOSC OS monthly update cycle - yes, we are a day late, however, this was largely due to some difficulties trying to get Mozilla software (Firefox, Thunderbird, etc.) working on ARMv7 (
armel) and AArch64 (
arm64) - not much success this month despite a five-day effort, however, we’ve heard good news about version 55 of Mozilla software. Anyways, here’s a re-cap.
This NVIDIA Jetson TX1 development kit has handled most of the packaging work, computing resources on non-PC platform is still quite scarce in AOSC.
With a longer period for packaging and testing, we are more confident about our updates. Another thing which time could “buy” is better attention to usability of packages - and that would include higher availability of packages for a particular port, higher reliability, and more importantly, better coverage with usability investigation for existing packages.
The first part could be seen with updates made to our two ARM ports, which includes for the first time, a full KDE/Plasma suite. Though we are still having a blocker which prevented Plasma from running on ARMv7 devices, and a minor issue which will crash KInfoCenter when checking PCI information on a device (which is, well, most ARM devices) which does not have such bus on board. We will be looking into pushing a quick patch revision for ARMv7 later this week for the former issue, while the latter will have to wait for upstream’s response (it is quite dangerous for a software upstream to disregard their own portable software running on non-x86 platforms, eh?). Apart from that, we are looking at a ~+300 package delta for this port, and more will come later as we get around to it.
Krita running on an AArch64-capable board, Orange Pi PRIME - AOSC OS image is available in the download page.
For usability investigation then, we would have to talk about two sets development utilities, the Ciel (Lion Yang asked me to leave “the” in so…) and ACID (just a random name). The Ciel is a (development) environment deployment and manipulation kit which manages one or more systemd-nspawn containers running on a hierarchical OverlayFS architecture, which allows for quick rollback of development/packaging environment(s) - soon to be a requirement for AOSC OS packaging, starting as an experiment in August.
Working upon the Ciel will be ACID, which is a simple script running on our servers to thoroughly build all packages in our ABBS tree, acting somewhat like a CI (considering the amount of packages - 4000+ of them - to be built continuously over the course of a month) to discover any packaging error - missing dependencies, misspelled words, incorrect scripting, and more. This system will surely improve the general packaging quality for AOSC OS, benefiting developers and users alike.
Lion Yang’s laptop looking at a netdata page of our buildbot (compiling host).
With the introduction of monthly cycles, we have now introduced two new types of community requests available to community members: updreq (Update Request) and optreq (Optimisation Request). The former is quite easy to understand, a package is too old, then request it.
The latter though could be more variable in its content, for example, Profile Guided Optimisation is available for a package, say
git, then a community member could open a optreq specifying building the
git package with PGO enabled (which involves changes to the build script, or configurations). For another example, which will be a future feature to be introduced to AOSC OS, the Overlay system - in this case, a community member may request that the package Python to be built with AVX2 support flags enabled, further enhancing its performance on newer processors, to be found in its
While updreq could be a quick and simple request, optimisation could quite easily be more difficult to open, and for our developers to investigate request and decide on if such request is actually beneficial - and to be fair, this could require more technical awareness on the part of our community members, one may quite simply think that “GNOME is too damn slow on my computer” is a valid request for us to invest into, but let’s just say up front, “tell it to the upstream, we did not write the program, can’t really help here, sorry”.
We’ve mentioned that PowerPC (32/64-bit big endian) ports will be halted until September due to lack of device availability for building and testing.
Similarly, but with time, our MIPS maintainer Junde Yhi decided that it will be quite difficult for our MIPS ports to catch up with the cycles until some major architecture-specific issues (compilers, and more) could be properly resolved. He’s also estimating a September return to the cycled updates. Meanwhile, catching up will be his task.
You might have noticed a lack of AOSA news posts on this page in August, we are currently working on a new community website which contains AOSC OS related Errata and Knowledge Base articles. Future AOSA will be posted there with a set format and more technical details (vulnerability descriptions, and PoCs if available).
We will keep you updated on this issue.
My apologies for rambling on and on about July - there are actually quite a bit happening in our July development cycle, the changelog is over 700 lines long, it’s quite hard to generalise them all - will keep practicing, I promise (LOL). But do expect the same amount of work done to AOSC OS - as our part of our continuous development effort to improve and optimise AOSC OS as your daily productivity platform.
Anyways, please enjoy this month’s update. For more information on what’s changed in this month’s wave of updates, please take a read at our complete changelog.
Information on August wave of updates will be announced tomorrow, or the day after - we are currently in the process of determining what’s to be done this month. Stay tuned.
— Mingcong Bai (with kind regards)
Brutally simplified rolling Linux distribution.
Install AOSC OS on your Windows machine.
Localization improvements made by the community.
A catalog of packages available for AOSC OS.
Our community repository server, where AOSC OS installation medias, tarballs, packages, project documentation, etc. are stored.
Take a look at current mirror synchronization and availability information.
Community mailing lists for discussions, advisories, and announcements.
Get in touch with the community.
Learn about newest news and happenings in and around AOSC.
Our WebMail service for AOSC developers and contributors.
Our public clipboard service (or pastebin) that you can use for all your clippy needs.