As mentioned in the announcement last week, a repository de-duplication (removing old version s of all packages in the repository) is planned for this weekend - and now, the process is complete.
Ideally, as an user who regularly updates their copy of AOSC OS, they would/should not notice the changes taken place this weekend. But we do anticipate removals of some packages may lead to dependency issues, and that our bulk removal of files on the repository server may cause error on our mirror partners (due to
rsync's delete threshold, or
If unfortunately you run into issue with updating or installing packages, please first try and switch to our source server…
sudo apt-gen-list -e "40-source"
And contact us at the IRC channel
#aosc to report this incident - we will then try and get into contact with our mirror servers to solve the issue.
Icenowy Zheng has recently uploaded a new batch of AArch64/ARM64 SD card images for compatible Allwinner devices, with Linux Kernel Updated to
4.11-rc6. Along with the Kernel update, two new devices are now supported:
Please head over to the download page for more downloads and more information.
With today’s newest changes to AOSC OS packages, we have decided to split the
firmware-nonfree package to free and non-free portions, with the
firmware-nonfree packages (pre-installed with any system release) containing only non-free firmware files, and a new
firmware-free package containing “free” firmware files.
A normal system upgrade may not install the new
firmware-free package automatically. If you started encountering issues regarding missing firmware after you upgraded your system, please check if you have installed
Both packages will be pre-installed with future system releases.
Since 2014, our community repository has been growing in size due to our (essentially) permissive policy on keeping all old versions of all our packages.
As we stand today, the repository is roughly 500GiB in size. This is abnormal even when considering all of our architectural ports, as Debian, the largest binary-based *nix distribution requires just over 1TiB in size. This continuing growth in repository size has brought storage challenges to both our mirror hosts and our own repository server.
Therefore, it is decided that starting at midnight of next Friday (April 14th, UTC time) that we will be starting to remove all packages that are not the newest provided across all architectures. We expect this operation to be finished by the weekend of April 16th.
Users (like you) should not be concerned about this operation, nor would impact your experience with AOSC OS. Removal of old packages only removes the possibility for developers to backtrack onto older revisions of a packages for comparative and regression testing.
GNOME 3.24 was released on March 22nd, 2017 with a large amount of new features and fixes, and here below is a quick summary of changes brought in by the 3.24 release:
And here below are some things we are happy to notice with GNOME 3.24:
For a full list of changes brought in by GNOME 3.24, please read the GNOME Release Notes.
However, GNOME 3.24 is not without its issues. For now, we have experienced the following issues:
We are currently looking into these issues and we are committed to bring fixes to these issues to you as soon as possible.
March is approaching its end, and thus time for the second issue of AOSC development update. In general, this has been a relatively quiet period - for our developers are experiencing time constraints, things are recently picking up again so no worries.
There have been general updates and security fixes for AOSC OS, but not to neglect the recent GNOME update. GNOME 3.24 is already made available by the time of writing.
Our MIPS ports has gain extra care from Junde Yhi and Jiaxun Yang, our new developer. Jiaxun Yang has been able to fix the Silicon Motion display driver used by various YeeLoong laptop models - which should boost desktop performance significantly. Junde Yhi has been working on “mainline” or “standard” Kernels (mainline and long-term support flavours) for both the MIPS32el and MIPS64el ports, and they are both tested on Loongson devices running on 2E/2F/3A series processors. Junde Yhi has also said that we could be expecting GNOME 3.24 on MIPS64el in the coming month. Tarballs will be released for the two architectures in the coming month.
Our ARM ports however, are experiencing a reduction in release line-up. Icenowy Zheng, our ARMv7 and ARMv8 maintainer has decided to drop a large amount of device-specific images - and now only releasing those tested by herself and community members - those images with no real world testing conducted are dropped. If you have an ARM device that you would like to run AOSC OS on, please get in contact with us at the
#aosc channel on Freenode, or shoot an e-mail at Icenowy at
icenowy at aosc dot io.
Several website changes has been put in place since Issue #1:
In the coming months, as AOSCC closes in, we will start to work on a feature list for AOSC OS Core 5, and begin preparation for AOSCC 2017 - which will be held in Guangzhou, in July of this year.
There will be extra additions to our community infrastucture:
But before which, we really don’t have much else to tell you. So stay tuned for the third issue, and thanks for coming by.
Please update your
libytnef package to version
A recently released version of Yerase’s TNEF Stream Reader Library has addressed the following security vulnerabilities:
Please update your
firefox package to version
A recent update to Firefox has addressed the following security vulnerabilities:
CVE-2017-5398, CVE-2017-5399, CVE-2017-5400, CVE-2017-5401, CVE-2017-5402, CVE-2017-5403, CVE-2017-5404, CVE-2017-5405, CVE-2017-5406, CVE-2017-5407, CVE-2017-5408, CVE-2017-5409, CVE-2017-5410, CVE-2017-5411, CVE-2017-5412, CVE-2017-5413, CVE-2017-5414, CVE-2017-5415, CVE-2017-5416, CVE-2017-5417, CVE-2017-5418, CVE-2017-5419, CVE-2017-5420, CVE-2017-5421, CVE-2017-5422, CVE-2017-5425, CVE-2017-5426, CVE-2017-5427.
Some highlights include:
A full list of packages added this time could be found here.
To learn about how to request new packages for addition into our community repository, please check out our “pakreq” guide. Or simply shout out requests with
#pakreq hashtag on our #aosc IRC channel, or on our Telegram group (joining information available on IRC).