Due to recent flooding of messages from various @qq.com (bots?) to our “discussions” list, we have currently taken emergency - and temporary - measure against all posts from @qq.com e-mail addresses.
If you own such e-mail account and wish to post on our mailing lists, we do apologise for your inconvenience. Please, for now, switch to another e-mail account - or create one elsewhere - for posting on our lists.
We will keep you updated if we are ready with a more scientific and appropriate solution.
We are happy to report that the August-September Wave of updates are now made available for AMD64 users of AOSC OS - along with AOSC OS Core 5 component updates, eMMC is here!
First of all, let’s take a glance at the August-September Wave.
The majority of our work in these two months has been focused upon fixing broken packages (build-time) by ACID, an idea brought up by Lion Yang to spawn “clean”, BuildKit containers and perform a coverage testing with our ABBS tree - putting Ciel to use.
As a result, hundreds of packages - old and new - were marked as broken. ~99% of them has been fixed now. Apart from the effects of fixing these tatty packages (that they should work better than before with less bugs), is the inspiration for us to further enhance the quality assurance modules and error handling of Autobuild3 - our automatic packaging toolkit.
As noted from Mingcong Bai’s last update, we have failed to sync up package updates for our non-AMD64 AOSC OS ports: PowerPC 32/64-bit Big Endian, ARMv7, AArch64, and MIPS 32/64-bit. However…
testingrepositories (except MIPS 32/64-bit)
bugfixupdates are made available (thus no security concerns as of yet).
We will continue to work on catching up with these ports.
Now, onto the exciting stuff, Core 5 “eMMC” is now made available to AOSC OS users as…
As how major (+1.0) Core updates go for AOSC OS, Core 5 includes more extensive updates over the Core 4 series - of course, from the GNU C Library at the bottom, to your GNU Compiler Collection (GCC) - are all updated to the newest versions.
Though no new architectural port is brought to the table for this year, we have worked on improving, and fixing up system application and development experiences.
For example, our compiler/linker hardening spec files were included within Autobuild3 - while some packages, like Python and Qt, records build-time compiler/linker flags, which references to the spec file included within Autobuild3’s installation directory - making developments using tools provided by these packages practically impossible without installing Autobuild3, which is absurd. In Core 5, we have moved these files to the
gcc package, working around this potential issue.
AArch64 should also be able to run applications more reliably with latest fixes in GCC and Binutils - a lot of applications that used to exit with a Segmentation Fault should work properly now. Though by our observation this should be a gradual process.
As one of the major changes to be brought by Core 5, we are introducing the Overlays system to AMD64 users in the coming month or two.
The Overlays system provides binary packages optimised for newer processors - and in AMD64’s case, processors with AVX2 instruction set support - to squeeze out extra performance potentially obtainable by enabling new instructional optimisation flags. For example, instruction-aware packages like GNU C Library, FFmpeg, Mesa, etc. should see observable performance gain than packages built with our standard compilation configurations - for example, all AMD64 packages are built with instruction set support up to SSE3.
Changes were required for Autobuild3 and
apt-gen-list to make it work smoothly for our developers and users, respectively. Autobuild3 now includes “sub-architectural” support, for example, setting
amd64/haswell+ will enable configurations to build packages for the Haswell+ (AVX2) Overlay, while generating packages for the
amd64 architecture in general.
Then, the new implementation of
apt-gen-list detects processor capability when generating APT repository configurations so that, say, users with their computer running Intel’s 5th generation Core processors, when running
apt-gen-list -e "40-source", should result in an APT configuration using the source repository with the
haswell+ Overlay repository automatically enabled - so that they could take advantage of their processors newer instruction sets, thus higher application performance.
October will be a good time to make up package updates left behind in the past two months due to our focus on ACID. Major desktop updates like GNOME 3.26, KDE Applications 16.08 will roll out by the end of October - along with many more applications and component updates to improve your experience with AOSC OS. What’s more…
On a personal note, I do apologise for the lack of update for the past month - as my friend Junde Yhi and I went on a 2-week trip to parts of Russia - and now it’s the beginning of the school season so time management was a great struggle.
Anyways, lets go on with the update. I’m happy to report that Core 5.0 is now in the final testing phase (Release Candidate 4), and should hit the stable repository by the end of the month - yes, with the Joint-August-and-September Wave of updates (and for the same reason mentioned above, we were unable to release the August wave, need more packagers!).
We have now finished preparing a semi-final set (well, final if we didn’t find anything stupid) of Core 5 wallpapers with a completely new style, here’s a small banner to be used in the Core 5 announcement to give you some ideas…
If you want, the full set is already available at the aosc-os-artworks repository, and will be made available to users of the Testing repositories in ~6 hours.
Apart from the wallpaper change, we have made quite some changes to the Core, including…
But I’m not going to share them all just yet, as in the Release Candidate phase, things can still change… a little bit. We will post another update on the actual date-of-release.
Another thing worth looking forward to in September or October is the inclusion of the first wave of “Overlay” packages for AMD64 (x86_64). We are currently making some final touches to the Autobuild3 build toolkit and apt-gen-list - which when done, Overlay repositories should be enabled based on your processor’s capabilities.
More on that later (it’s still crazy busy here so I do apologise for repeated delays).
As for non-AMD64 (ARMv7, AArch64, PowerPC 32-bit, PowerPC 64-bit, MIPS 32-bit, MIPS 64-bit) ports of AOSC OS, we are currently working to synchronise all updates with the ABBS Tree - we can’t guarantee a date of completion just yet, but here are the two things we are sure about…
bugfixupdates (and that includes all security fixes).
bugfixupdates will be synchronised immediately, while “normal updates” from the
stagingbranch will settle in the forseable future.
New AOSC OS tarballs and images will roll out in October (probably by the end of the month) with the Core 5 updates - but again, for non-AMD64 ports, this will not necessarily include all the feature updates from the main tree - we do apologise for that.
— Mingcong Bai
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.
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.