Apricity OS 04.2016 Beta & RC1 Release

8 Replies

We’re very excited to announce Apricity’s first ever stable Release Candidate. Apricity OS 04.2016 Beta is being released alongside Apricity OS 04.2016 RC1. This month, a lot of effort has gone into improving the development workflow and making a distinction between stable, tested features and untested features. The apricity-core repository has split into three seperate repositories: the standard, unsigned apricity-core repo, a new signed apricity-core repo, and a signed apricity-core-dev repository for developers. All three repos are now being built twice a week. On the github side of things, almost all repositories have moved onto a new branching model. Repositories on this branching model have at least two branches: dev, and master. Feature branches are merged into dev when they are more-or-less finished. Master is considered the stable branch, and dev, as its name suggests, is for development. New features should be built on seperate feature-* branches, releases will be developed on release-* branches, and hotfixes for production code will be built on hotfix-* branches. Both versions of stable apricity-core now build packages from the master branches, and apricity-core-dev builds from dev branches. In terms of the OS itself, not much has changed. Many bugs with the installer have been fixed, more mouse/touchpad drivers are being included by default, and many apricity-* packages have received bugfixes. Autologin for the Gnome edition has been fixed. A particularly annoying bug where the Apricity Icons iconset threw warnings about missing size fields has (finally) been fixed. As an aside, Apricity recently passed 100,000 downloads! Thanks to everyone who helped us reach this milestone.

As always, we hope you will find this release easy and enjoyable to use.

Sincerely,

The Apricity OS Team

8 thoughts on “Apricity OS 04.2016 Beta & RC1 Release”

    • admin

      Right now, the only difference is that the betas are on the dev repo and rc1 is on the stable repo. However, as more features are developed in the future, they will start out in the betas and in the dev repo before trickling down into the stable releases and repo after one or two months of testing.

      Reply
  2. Tomas

    Hi, I already have the same problem with april releases (both beta and RC, both gnome and cinnamon) than with march: segmentation fault during instalation, just after partition stage. I also tried to prepare the partitions with gparted before installation but the same result.

    I would like to report this problem in the Installation thread of the forum but I’m not able to register, always problems with security check (sometimes the audio is diferent from the picture….).

    Reply
    • admin

      Hmm, what kind of hardware do you have? Also, it would be worth it to try running the installer from the command line with “sudo calamares -d”.

      Reply
      • Tomas

        It’s a old Acer Aspire 5630 laptop. The realease is still beta and I don’t want to break my main computer. Anyway, this laptop is able to run other distros like Linux Mint or Manjaro Linux without problems.

        This is what happens when I run the cinnamon april beta:
        1.- I must run “pacman-key –populate” in order to be able to install updates, other way I get the error “Invalid or corrupted database” (also with gnome)
        2.- Run “su” and “calamares -d” as suggested
        3.- Select Spanish (Spain) and Next
        4.- Select Madrid and Next
        5.- Select Spanish keyboard and default
        6. Select “replace partition” and select a existing 20GB ext4 partition and next. The same with manual partitioning.
        7.- Introduce user data and next
        8.- The sum shows that the installer is going to remove and create again the partition. Click next.
        9.- The installer closes suddenly
        10.- Error “zsh: segmentation fault (core dumped) calamares -d”. The last three lines in console are:

        15:02:35 [1]: ClearTempMountsJob finished. Here’s what was done: “”
        15:02:35 [0]: Starting job “Clear mounts for partitioning operations on /dev/sda”
        zsh: segmentation fault (core dumped) calamars -d

        It’s exactly the same with the default language options and/or Manual partitioning.

        Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

*