if you are using systemd (the default parabola system) and have the 'libidn2' package installed, upgrading it could break your system until the next version of systemd is in the repos
if this has already happened to you, here is a temporary work-around:
sudo ln -s /usr/lib/libidn2.so /usr/lib/libidn2.so.0
refer to this bug report for follow-ups: https://labs.parabola.nu/issues/2139
Parabola now supports the Asus Chromebook C201 with the Linux-libre kernel. In the past, the furthest thing we achieved was to boot Parabola with the non-free CrOS kernel. However, that changed when a Parabola user reported at issue #1965 to successfully boot our beloved distro in this Librebooted ARM laptop. Users that wish to do this, just have to install the linux-libre-chromebook package, which has the signature to boot Linux-libre with Depthcharge in the C201.
The newest version of PAM has an unspecified dependency on the 'audit' package. Upgrading that package today causes su and sudo to fail and makes logins impossible.
To avoid any trouble, you should explicitly install the 'audit' package before attempting to upgrade the system. If you upgrade without first installing the 'audit' package, then you will need to chroot into the system and install it.
The rather long outage (2018-08-27 through 2018-09-18; 22 days) of the
proton.parabola.nu server has been resolved, with all services being
winston.parabola.nu. Please notify us if you encounter
any lingering issues.
We'd like to specifically thank Jonathan "n1md4" Gower for graciously hosting
us at Positive Internet all these years--since before most of us were even
Parabola users, let alone contributors.
However, that sponsorship has come to an end. We are alright for now; the
server that 1984 Hosting is sponsoring us with is capable of covering our
immediate needs. We are looking for a ...
Due to a known bug in upstream Linux 4.18, users with older multi-core x86 CPUs (Core 2 Duo and earlier?) may not correctly boot up with
linux-libre 4.18 when using the default clocksource.
If you are affected, and the CPU is new enough to support HPET, you may work around this by adding
clocksource=hpet to the kernel command line. GRUB users can accomplish this by inserting
GRUB_CMDLINE_LINUX_DEFAULT+=" clocksource=hpet" in to
/etc/default/grub and re-running
If your CPU is too old to support HPET, you may work around this by using the
linux-libre-lts (4.14 ...