26 Apr 2024
Fedora People
Remi Collet: PHP version 8.2.19RC1 and 8.3.7RC1
Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for a parallel installation, the perfect solution for such tests, and also as base packages.
RPMs of PHP version 8.3.7RC1 are available
- as base packages
- in the remi-modular-test for Fedora 38-40 and Enterprise Linux ≥ 8
- in the remi-php83-test repository for Enterprise Linux 7
- as SCL in remi-test repository
RPMs of PHP version 8.2.19RC1 are available
- as base packages
- in the remi-modular-test for Fedora 38-40 and Enterprise Linux ≥ 8
- in the remi-php82-test repository for Enterprise Linux 7
- as SCL in remi-test repository
The Fedora 39, 40, EL-8 and EL-9 packages (modules and SCL) are available for x86_64 and aarch64.
PHP version 8.1 is now in security mode only, so no more RC will be released.
Installation: follow the wizard instructions.
Announcements:
Parallel installation of version 8.3 as Software Collection:
yum --enablerepo=remi-test install php83
Parallel installation of version 8.2 as Software Collection:
yum --enablerepo=remi-test install php82
Update of system version 8.3 (EL-7) :
yum --enablerepo=remi-php83,remi-php83-test update php\*
or, the modular way (Fedora and EL ≥ 8):
dnf module switch-to php:remi-8.3 dnf --enablerepo=remi-modular-test update php\*
Update of system version 8.2 (EL-7) :
yum --enablerepo=remi-php82,remi-php82-test update php\*
or, the modular way (Fedora and EL ≥ 8):
dnf module switch-to php:remi-8.2 dnf --enablerepo=remi-modular-test update php\*
Notice:
- version 8.3.7RC1 is also in Fedora rawhide for QA
- EL-9 packages are built using RHEL-9.3
- EL-8 packages are built using RHEL-8.9
- EL-7 packages are built using RHEL-7.9
- oci8 extension uses the RPM of the Oracle Instant Client version 21.13 on x86_64 or 19.19 on aarch64
- intl extension uses libicu 73.2
- RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
- versions 8.2.18 and 8.3.5 are planed for April 11th, in 2 weeks.
Software Collections (php82, php83)
Base packages (php)
26 Apr 2024 4:38am GMT
24 Apr 2024
Fedora People
Peter Czanik: Using syslog-ng on multiple platforms
Your favorite Linux distribution is X. You test everything there. However, your colleagues use distro Y, and another team distro Z. Nightmares start here: the same commands install a different set of syslog-ng features, configuration defaults and use different object names in the default configuration. I ran into these problems while working with Gábor Samu on his HPC logging blog.
From this blog you can learn about some of the main differences in packaging and configuration of syslog-ng in various Linux distributions and FreeBSD, and how to recognize these when configuring syslog-ng on a different platform.
https://www.syslog-ng.com/community/b/blog/posts/using-syslog-ng-on-multiple-platforms
<figure>
<figcaption>
syslog-ng logo
</figcaption> </figure>
24 Apr 2024 12:07pm GMT
Fedora Magazine: How to rebase to Fedora Linux 40 on Silverblue
Fedora Silverblue is an operating system for your desktop built on Fedora Linux. It's excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. If you want to update or rebase to Fedora Linux 40 on your Fedora Silverblue system, this article tells you how. It not only shows you what to do, but also how to revert things if something unforeseen happens.
Update your existing system
Prior to actually doing the rebase to Fedora Linux 40, you should apply any pending updates. Enter the following in the terminal:
$ rpm-ostree update
or install updates through GNOME Software and reboot.
Note
rpm-ostree is the underlying atomic technology that all the Fedora Atomic Desktops use. The techniques described here for Silverblue will apply to all of them with proper modifications for the appropriate desktop.
Rebasing using GNOME Software
GNOME Software shows you that there is new version of Fedora Linux available on the Updates screen.
<figure class="wp-block-image size-full is-style-default">
</figure>
First thing to do is download the new image, so select the Download button. This will take some time. When it is done you will see that the update is ready to install.
<figure class="wp-block-image size-full">
</figure>
Select the Restart & Upgrade button. This step will take only a few moments and the computer will restart when the update is completed. After the restart you will end up in a new and shiny release of Fedora Linux 40. Easy, isn't it?
Rebasing using terminal
If you prefer to do everything in a terminal, then this part of the guide is for you.
Rebasing to Fedora Linux 40 using the terminal is easy. First, check if the 40 branch is available:
$ ostree remote refs fedora
You should see the following in the output:
fedora:fedora/40/x86_64/silverblue
If you want to pin the current deployment (meaning that this deployment will stay as an option in GRUB until you remove it), you can do this by running this command:
# 0 is entry position in rpm-ostree status $ sudo ostree admin pin 0
To remove the pinned deployment use the following command:
# 2 is entry position in rpm-ostree status $ sudo ostree admin pin --unpin 2
Next, rebase your system to the Fedora Linux 40 branch.
$ rpm-ostree rebase fedora:fedora/40/x86_64/silverblue
Finally, the last thing to do is restart your computer and boot to Fedora Linux 40.
How to roll back
If anything bad happens (for instance, if you can't boot to Fedora Linux 40 at all) it's easy to go back. At boot time, pick the entry in the GRUB menu for the version prior to Fedora Linux 40 and your system will start in that previous version rather than Fedora Linux 40. If you don't see the GRUB menu, try to press ESC during boot. To make the change to the previous version permanent, use the following command:
$ rpm-ostree rollback
That's it. Now you know how to rebase Fedora Silverblue to Fedora Linux 40 and roll back. So why not do it today?
FAQ
Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.
Question: Can I skip versions during rebase of Fedora? For example from Fedora 38 Silverblue to Fedora 40 Silverblue?
Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (38->39 for example) to avoid unnecessary errors.
Question: I have rpm-fusion layered and I get errors during rebase. How should I do the rebase?
Answer: If you have rpm-fusion layered on your Silverblue installation, you should do the following before rebase:
$ rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release
After doing this you can follow the guide in this blog post.
Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),…?
Yes, you can follow the Rebasing using the terminal part of this guide for every Fedora Atomic Desktop. Just use the corresponding branch. For example, for Kinoite use fedora:fedora/40/x86_64/kinoite
24 Apr 2024 8:00am GMT