/rss20.xml">
fedora

Fedora People
Blog List
RSS 1.0 RSS 2.0 Atom 1.0 FOAF blogroll

Fedora Moves Towards Forgejo

Posted by Fedora Magazine on 2024-12-04 14:11:35 UTC

The decision to move to Forgejo as the new git forge has been made. There are numerous factors involved in this decision and this article will discuss them, present some background on the process, and invite one more chance for feedback before the formal Fedora Council vote.

Gist of the situation

We’ve known for a long time that the Fedora Project needs a new git forge solution. The software we currently use, Pagure, has served us well. Sadly, it never took off in the wider world. So we had to maintain the Pagure git forge ourselves and use it to build the Fedora Linux releases at the same time. A few years ago, we considered GitLab, and had a lot of discussion… which ultimately didn’t go anywhere. Out of that we got a clear message. It’s important that this crucial part of our infrastructure be free and open source software.

At the Fedora Council’s annual face-to-face meeting in February we discussed a large list of options. By the end of the day, we crossed off all but two: GitLab Community Edition and Forgejo. We also determined that no hosting providers can meet our unique needs; we’ll have to self-host. We then asked the Advanced Reconnaissance Crew (ARC, a subteam of Fedora Infrastructure) to investigate these in more detail. They were particularly asked to look at 1) any show-stopper missing features and 2) maintenance effort and cost.

ARC has presented their initial results (about which Akashdeep goes into detail below). The quick summary: either option could work, and both have some gaps we’ll need to fill. Several things tilt the scales one direction. GitLab CE is “open core”, with some features only in the non-open-source “premium” version (including some we really want). This is both an immediate practical concern and a long-term one. Open core software tends, over time, to get less open (no matter how good the initial intentions). In addition, the Infrastructure team is more comfortable with the Forgejo codebase and the language it is written in.

So, what’s next? The Council, currently, has a clear preference for Forgejo. This is a big decision and we don’t want it to feel rushed. Therefore, we’re opening this up one last time to everyone’s comments. After two weeks, we’ll take our formal vote — and then get on with the work!

– Matthew

How we got here

The earliest attempts to move over to an alternative git forge solution started as early as January 2020. At that time the development work on Pagure became increasingly inconsistent. This resulted in the maintenance costs soaring due to the unmaintained state of the development. Shortly after that, in March 2020, the decision was made to move over to GitLab after evaluating over 300 user stories and a SaaS offering was planned for the Fedora Project. While the development of new features for Pagure slowed down, an exemplary group of contributors stepped up to ensure that the current state of Pagure was maintained well. After a detailed AMA session with folks from GitLab in September 2020, a SaaS offering was announced for Fedora Project in October 2021, and a bunch of sub-projects and SIGs started moving their workflows over to the Fedora Project namespace of GitLab.

While the case looked mostly positive for the sub-projects and SIGs like Fedora Websites and Apps team, there were concerns regarding the scalability in terms of contributor counts and suitability in terms of the Dist Git purposes. This was specifically brought up in the Fedora Council issue ticket discussion and realized at a much later stage in function which led to the initiative request of Dist Git to GitLab from Fedora Infrastructure in February 2023. Fedora Infrastructure worked on an application that helps migrate repositories from Pagure to GitLab through November 2023. By December 2023, the evaluation of Git Forges had become a priority for Fedora Council and a concurrent investigation that explored migrating Dist Git functionality in a forge-agnostic way to another git forge was completed by March 2024.

The Investigation, a.k.a The Prequel!

After the Git Forge alternatives were shortlisted during the Fedora Council F2F Hackfest in February 2024, the Community Linux Engineering (CLE) team (previously called the Community Platform Engineering (CPE) team) were tasked with the investigation. The Advanced Reconnaissance Crew (ARC) sub-team was to report the positives and negatives of each git forge option, while working with various stakeholders across the Fedora Project community to capture the projects requirements for our dist-git. The initiative was led by Tomas Hckra and Akashdeep Dhar, and Akashdeep also represented the Fedora Councils needs to the team. They began collecting these requirements in the form of user stories in March 2024 to use as the baseline of the investigation. The initiative was then joined by David Kirwan and Ryan Lerch who were able to deploy an instance of both Forgejo and GitLab CE in the CommuniShift app, and the team began validating that each user story worked in each git forge instance. These findings were reported in the official documentation.

The availability of these instances really helped onboard more contributors into the user stories validation efforts. This meant that the focus was not only on the packagers and release engineering workflow but also covered those associated with subprojects/SIGs like Design, Documentation, Accessibility, Websites & Apps, Mindshare etc.

Throughout the investigation, conversations on Fedora Discussion and on the Fedora Project mailing list were happening, making sure Fedoras use cases were being addressed, and the ARC team had presentations during the Fedora Linux 40 Release Party as well as Tomas Hrcka’s talk during the Flock To Fedora 2024 to give this huge change maximum exposure.

Once the investigation completed, Fedora Council was slated to make the final decision on which forge the project would choose to migrate to.

And now the work really begins

Like any other initiative, or large project or piece of work, the plan is never perfect, and this particular effort was quite literally years in the making. The next step for all the parties involved is to have some retrospectives to reflect on how this all went. There are plenty of learnings to be had for sure, and we hope to have a better understanding of how to drive such major decisions in a much better way.

With the investigation on the git forge solutions now wrapped up, we plan to work with Community Linux Engineering (CLE) to direct the migration of Dist Git assets and the conversion of team workflows to the deployed Forgejo Server instance once the decision is formally (and finally!) announced in the coming weeks by Fedora Council.

Pagure Dist Git is connected with a variety of ecosystem services. These include, among others:

Please do not hesitate to reach out to the Fedora Infrastructure team to provide your support. 

Utmost attempts will be made to ensure that the git forge replacement has feature parity with the systems it is attempting to replace (i.e. Pagure Dist Git and Bugzilla). However, it is important to understand that this is a complex undertaking. Most workflows related to various subteams, subprojects and SIGs are likely to remain the same. In some cases we might have to re-imagine the workflows to fit the change (best case scenario). In other cases it may be necessary to deprecate workflows that are no longer reasonably supportable (worst case scenario).

Folks are requested to have an understanding of the user stories that were taken into consideration while comparing the git forge alternatives. Please collaborate with the Fedora Infrastructure team to integrate your specific workflows into the Dist Git Replacement platform.

We look forward to bringing this change to Fedora collaboratively with you in 2025!

The best way to make a decision is to decide

Posted by Ben Cotton on 2024-12-04 13:00:00 UTC

Making decisions in an open source community is hard. Most communities have some sort of consensus model where major decisions require broad support. There’s not just one Big Boss who can come in and unilaterally decide. But sometimes decisions become bogged down in an attempt to get unanimous support or achieve the One Best Decision™. If you’re the person who is supposed to make the decision, make the damn decision.

Consensus is important. People want to feel like their input matters, especially when they’re contributing on a volunteer basis. If participating in your project stops being fun, people will leave. It’s hard to make sustainable progress if you can’t get the majority to go along with you.

But we sometimes overcorrect toward consensus. In those cases, the decision drags on. If a decision is ever made, it no longer has momentum. It might be the most correct decision, but it loses impact because it sits in a state of limbo for months.

In most cases, a good decision made quickly is better than a great decision made slowly. You can iterate on decisions, and that works better with short cycles. The smaller the decision — or the easier it is to reverse — the less time you need to spend building consensus. This is not to say that you should go around making a bunch of decisions on your own. That’s chaos.

Instead, you should have a defined process for how decisions are made: who can gives input, who is empowered to make the decision, and what the time frame looks like. Set a deadline and then make the best decision you can. The process doesn’t have to be complicated — it’s better if the process is simple — it just needs to not catch the community by surprise. Chapter 4 of Program Management for Open Source Projects lays out a framework for building your decision process.

This post’s featured photo by krakenimages on Unsplash

The post The best way to make a decision is to decide appeared first on Duck Alignment Academy.

Upgrade of Copr servers

Posted by Fedora Infrastructure Status on 2024-12-04 09:00:00 UTC

We're updating Copr servers to F41

This outage impacts the copr-frontend and the copr-backend.

Basedpyright and neovim

Posted by Kushal Das on 2024-12-03 20:50:01 UTC

screenshot from the website

Basedpyright is a fork of pyright with various type checking improvements, improved vscode support and pylance features built into the language server. It has a list of benefits over Pyright.

In case you want to use that inside of neovim using Mason, you will have to remember to have the configuration inside of a settings key. The following is from my setup.

basedpyright = {
  settings = {
    basedpyright = {
      analysis = {
        diagnosticMode = 'openFilesOnly',
        typeCheckingMode = 'basic',
        capabilities = capabilities,
        useLibraryCodeForTypes = true,
        diagnosticSeverityOverrides = {
          autoSearchPaths = true,
          enableTypeIgnoreComments = false,
          reportGeneralTypeIssues = 'none',
          reportArgumentType = 'none',
          reportUnknownMemberType = 'none',
          reportAssignmentType = 'none',
        },
      },
    },
  },
},

Struggled for a few hours to fix this couple of days ago.

Posted by Mohammadreza Hendiani on 2024-12-03 18:44:11 UTC

fun fact: in dependent packages can be checked by running:
fedrq wr -F "name" -s "package name"

Posted by Mohammadreza Hendiani on 2024-12-02 22:58:38 UTC

If you are looking for of the aforementioned I suggest looking through the latest *.spec files that can be found here: 'pkgs.fedoraproject.org/repo/rp'

Posted by Mohammadreza Hendiani on 2024-12-02 22:53:23 UTC

packager, here's a fun fact: If you're software with custom patches in its git repo, Fedora RPM has built-in macros for
macros like '%autosetup' and '%autopatch' use these git macros under the hood.
github.com/rpm-software-manage

Bahnhof Bar

Posted by Kushal Das on 2024-12-02 08:10:22 UTC

photo of bahnhof bar

A few weeks ago Bahnhof organized an evening to celebrate technology/innovation/freedom, and opened Bahnhof Bar only for the evening. Back in 2005 their office was raided and servers were taken, and the latest TV series, The Pirate Bay on SVT Play already showed that as part of the series.

from the pirate bay on SVT

The evening went too fast, met a lot of new people and a few old friends too. I love Bahnhof's service as Internet provider, but also love how they fight for privacy and freedom.

You can read their blog post about the event too.

Fedora Linux Flatpak cool apps to try for December

Posted by Fedora Magazine on 2024-12-02 08:00:00 UTC

This article introduces projects available in Flathub with installation instructions.

Flathub is the place to get and distribute apps for all of Linux. It is powered by Flatpak, allowing Flathub apps to run on almost any Linux distribution.

Please read “Getting started with Flatpak“. In order to enable flathub as your flatpak provider, use the instructions on the flatpak site.

These apps are classified into four categories:

  • Productivity
  • Games
  • Creativity
  • Miscellaneous

Ghostwriter

In the Productivity section we have Ghostwriter. Ghostwriter is a distraction-free text editor for Markdown featuring a live HTML preview as you type, theme creation, focus mode, fullscreen mode, live word count, and document navigation. All of this appears in an aesthetic writing environment. It comes with the cmark-gfm Markdown processor built in, and can integrate with Pandoc, MultiMarkdown, Discount, and cmark processors, if they are installed. I personally use it when I’m offline before moving it to my markdown online application and the syntax works perfectly.

You can install “Ghostwriter” by clicking the install button on the web site or manually using this command:

flatpak install flathub org.kde.ghostwriter

Ghostwriter is also available as an rpm in the Fedora Linux repositories

Hedgewars

In the Games section we have Hedgewars. Hedgewars is a turn-based strategy, artillery, action and comedy game. It features the antics of pink hedgehogs with attitude as they battle from the depths of hell to the depths of space. As commander, it’s your job to assemble your crack team of hedgehog soldiers and bring the war to your enemy.

Game features:

  • Plugin your own custom maps, costumes, and other artwork
  • Hilarious and strategic turn based combat for up to 8 players
  • Single player mode with two campaigns and many scenarios and challenges
  • Both local and network multiplayer, with optional AI opponents
  • Battle on an infinite number of randomly generated maps, with over 22 environments
  • Attack with one of over 38 devastating weapons!
  • Including the piano strike and explosive robotic cake
  • Utilize over 16 utilities like the rope or portable portal device to pave your path to victory
  • Play the game your way, with many different game modifiers. You may tweak almost every aspect of the match
  • Customize your team, with numerous hats, costumes, graves, forts, flags and unique voice packs
  • Huge battles with up to 64 hedgehogs
  • Play both single player and multiplayer minigames

You can install “Hedgewars” by clicking the install button on the web site or manually using this command:

flatpak install flathub org.hedgewars.Hedgewars

Hedgewars is also available as an rpm in the Fedora Linux repositories

Podcasts

In the Miscellaneous section we have Podcasts. Play, update, and manage your podcasts from a lightweight interface that seamlessly integrates with GNOME. Podcasts can play various audio formats and it remembers where you stopped listening. You can subscribe to shows via RSS/Atom, iTunes, and Soundcloud links. Subscriptions from other apps can be imported via OPML files.

You can install “Podcasts” by clicking the install button on the web site or manually using this command:

flatpak install flathub org.gnome.Podcasts

FamiStudio

In the Creativity section we have FamiStudio. FamiStudio is a simple music editor for the Nintendo Entertainment System or Famicom. It is targeted at both chiptune artists and NES homebrewers. I’ve been playing around with 8-bit art, and the start was with music. FamiStudio is a complete suit so you don’t need to move between a MIDI editor and then and instrument/music sheet program; you have everything in here. I love the tutorial and how everything is very well explained. Some of its features are:

  • Sunsoft 5B Envelope Support
  • FDS Auto-Modulation and FDS Emulation Improvements
  • Phase Reset Support
  • Improved Ability to Disable Attacks
  • Folders in Project Explorer
  • Eraser Mode
  • Copy DPCM Sample Mapping between instruments

You can install “FamiStudio” by clicking the install button on the web site or manually using this command:

flatpak install flathub org.famistudio.FamiStudio

Access to serial console in EC2

Posted by Pavel Raiskup on 2024-12-01 00:00:00 UTC

Even in the cloud, it is sometimes convenient to monitor systemd logs via the serial console (or even log into the machine) when services like sshd fail or disks fail to mount. With EC2, you can use SSH for this purpose.

Get the instance ID

Either go to the console (web-ui) and get the instance ID there, or just ssh to the machine and query the Metadata Service:

$ ssh <user>@<host>
$ TOKEN=$(curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600")
$ curl -H "X-aws-ec2-metadata-token: $TOKEN" http://169.254.169.254/latest/meta-data/instance-id ; echo
i-015xxxxxxxxxxxxxx
$ exit

Access the serial console

On your machine, setup a few environment variables:

$ instance_id=i-015xxxxxxxxxxxxxx
$ pubkey=/home/praiskup/.ssh/id_rsa.pub
$ region=us-east-1

Tell EC2 what SSH key you want to use first, and then ssh to the console:

$ aws ec2-instance-connect send-serial-console-ssh-public-key \
    --instance-id "$instance_id" \
    --serial-port 0 \
    --ssh-public-key file://"$pubkey" \
    --region "$region"
-----------------------------------------------------
|           SendSerialConsoleSSHPublicKey           |
+----------------------------------------+----------+
|                RequestId               | Success  |
+----------------------------------------+----------+
|  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  |  True    |
+----------------------------------------+----------+

$ ssh "$instance_id".port0@serial-console.ec2-instance-connect."$region".aws
copr-fe-dev login:

Work with the console over SSH

Use the neat SSH control keys, start with ~?, quit the session with ~.:

copr-fe-dev login: ~?
Supported escape sequences:
 ~.   - terminate connection (and any multiplexed sessions)
 ~B   - send a BREAK to the remote system
 ~R   - request rekey
 ~V/v - decrease/increase verbosity (LogLevel)
 ~^Z  - suspend ssh
 ~#   - list forwarded connections
 ~&   - background ssh (when waiting for connections to terminate)
 ~?   - this message
 ~~   - send the escape character by typing it twice
(Note that escapes are only recognized immediately after newline.)

Watch the systemd logs over SSH:

[root@copr-fe-dev ~][STG]# reboot 
         Stopping session-160.scope - Session 160 of User root...
         Stopping session-49.scope - Session 49 of User root...
[  OK  ] Removed slice system-modprobe.slice - Slice /system/modprobe.
[  OK  ] Removed slice system-sshd\x2dkeygen.slice - Slice /system/sshd-keygen.
[  OK  ] Removed slice system-systemd\x2dzr…- Slice /system/systemd-zram-setup.
...

Make grub2 menu available

Currently there’s a problem with Grub in EC2, but in general you would be doing something like:

$ cp /boot/grub2/grub.cfg /var/tmp/     # backup
$ grub2-editenv - unset menu_auto_hide  # https://fedoraproject.org/wiki/Changes/HiddenGrubMenu
$ vim /etc/default/grub                 # change the $GRUB_TIMEOUT
$ grub2-mkconfig > /boot/grub2/grub.cfg # re-generate
$ vim -d /boot/grub2/grub.cfg /var/tmp/grub.cfg  # review!

You might notice a problem that I did, systemd disallows reboot over EC2 console, not reported for now. The EC2 console has no “send ctrl+alt+delete” button, nor an on-screen keyboard. You can’t send ctrl+alt+delte over the SSH-console. SysRq is disabled of course (by default). Could we have something like ctrl+R for rebooting? Not sure.

Infra and RelEng Update – Week 48 2024

Posted by Fedora Community Blog on 2024-11-29 10:00:00 UTC

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 25 – 29 November 2024

I&R infographic

Infrastructure & Release Engineering

The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues

Fedora Infra

CentOS Infra including CentOS CI

Release Engineering

List of new releases of apps maintained by I&R Team

Minor update of Bodhi from 8.2.0 to 8.3.0 on 2024-11-25: https://github.com/fedora-infra/bodhi/releases/tag/8.3.0

If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.

The post Infra and RelEng Update – Week 48 2024 appeared first on Fedora Community Blog.

Contribute at the Fedora Linux Test Week for Kernel 6.12

Posted by Fedora Magazine on 2024-11-29 08:00:00 UTC

The kernel team is working on final integration for Linux kernel 6.12. This version was just recently released, and will arrive soon in Fedora Linux. As a result, the Fedora Linux kernel and QA teams have organized a test week from Sunday, December 01, 2024 to Sunday, December 08, 2024. The wiki page in this article contains links to the test images you’ll need to participate. Please continue reading for details.

How does a test week work?

A test week is an event where anyone can help ensure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.

To contribute, you only need to be able to do the following things:

  • Download test materials, which include some large files
  • Read and follow directions step by step

The wiki page for the kernel test week has a lot of good information on what and how to test. After you’ve done some testing, you can log your results in the test week web application. If you’re available on or around the days of the event, please do some testing and report your results. We have a document which provides all the necessary steps.

Happy testing, and we hope to see you on one of the test days.

Amnesty seminar on activism

Posted by Kushal Das on 2024-11-29 07:35:33 UTC

picture of a sign on the road about the event

2 Weeks ago I was down with fever, but as I became better after a few days I managed to attend Amnesty International's Stockholm chapter's event on activism. I had to travel to a different part of Stockholm, which was fun.

The day started with welcome talk and then a new "Palestine Activist Group" presented their work (in both English and Swedish). Then the main opening talk (in Swedish) from a very senior Swedish journalist about history and important dates related to Palestine. I managed to understand 50-60% of the words. Still a lot of learn.

During the break I had longer chats about privacy, data and our lives. It was good to find folks who knows/uses Python/Fedora/Debian/Ubuntu and other Open Source tools in their daily lives, sometimes even without knowing.

After the morning break, I attended a workshop about being an activist. It was filled with discussions, and of course a lot of new words in Swedish for me. But, the delivery of the workshop was good, people talked about what they think about being an individual activist and things to consider etc.

Next day I had a workshop for a selected group, about boycotting large services and how to providing least amount data to preserve our privacy. The group consisted people from various parts of Swedish society, people working in other government agencies and large multinational companies.

We talked about metadata and phones provide both metadata and real data to the various services via apps. Explaining people to imagine that every time they get out of home, there are many humans walking with them to every destination, keeping notes of every place visit, and every chats they are having with another person or about groups, and then later selling that information to other businesses. It is one thing to talk about these, but it is complete opposite to show. So, I showed them live how much our phones/computers talk. I had my old Pixel4a configured with GrapheneOS, and one of the participant connected their regular Pixel phone to the same VPN. And people seemed to be offended by seeing the amount of data flowing, even when the phone is not use. The below is a screenshot I took today morning from the same demo setup.

screenshot of the DNS calls

We also talked about various chatting platforms, I already built another system to teach kids about how various social chatting platforms work. It was a perfect tool for this demo. We discussed about various other technologies in our daily lives and how they affect privacy.

Syslog-ng Prometheus exporter added to RPM syslog-ng container image

Posted by Peter Czanik on 2024-11-28 08:37:03 UTC

Last week I introduced you to my latest project: a syslog-ng container based on Alma Linux. This week I added a syslog-ng Prometheus exporter to the container, so you can also monitor syslog-ng, if you enable it.

syslog-ng logo

Innovation Happens Elsewhere: now in a portable form

Posted by Ben Cotton on 2024-11-27 13:00:00 UTC

A little over a year ago, a colleague suggested I read the book Innovation Happens Elsewhere: Open Source as Business Strategy by Ron Goldman & Richard P. Gabriel. It’s nearly two decades old, but it’s a good look at how open source and business were interacting in the “early” days. The authors made the book open-access on their website, but I wanted to put it on my e-reader for airplane reading. Thankfully, it’s under CC BY-NC-SA 2.0, so I could do something about that.

After working on conversion off-and-on, I’ve finally made it available in PDF and epub formats. The source is available in a GitHub repo if you find any errors. Note that I am explicitly not looking to update it. That’s too large of a project. (Plus, if you want an up-to-date book about the intersection of open source and business, you can read VM Brasseur’s Business Success With Open Source.) I will gladly accept fixes to formatting, broken links, and so on.

This post’s featured photo by Aaron Burden on Unsplash.

The post Innovation Happens Elsewhere: now in a portable form appeared first on Duck Alignment Academy.

Accessing UCL VPN using OpenConnect on Linux systems

Posted by Ankur Sinha on 2024-11-25 14:49:25 UTC

I needed to use the UCL VPN again, on my Fedora/Linux machine. Linux isn't really supported by the university infrastructure, but there are instructions that others have come up with and they had worked for me the last time I'd needed VPN access. Unfortunately, that was a few years ago, and things have changed a little since then. Notably, UCL has introduced two factor authentication (2FA).

I had to look around a little but I did manage to get it to work again using NetworkManager. I thought I'd write it up quickly so everyone that needs it, including future me, have a quick reference to look at.

This is on Fedora 41 with the following OpenConnect packages:

$ rpm -qa \*openconnect\*
openconnect-9.12-6.fc41.x86_64
NetworkManager-openconnect-1.2.10-6.fc41.x86_64
NetworkManager-openconnect-gnome-1.2.10-6.fc41.x86_64

In NetworkManager one needs to create a new VPN connection with the following settings:

Screenshot of settings in Network Manager for setting up a VPN connection to UCL VPN using Open Connect (settings are listed below)

Here are the settings in a list too:

  • VPN Protocol: Cisco AnyConnect or OpenConnect
  • Gateway: vpn.ucl.ac.uk
  • User Agent: AnyConnect
  • CA Certificate: <None>
  • Proxy: <leave blank>
  • Allow security scanner trojan (CSD): Yes (checked)
  • Trojan (CSD) wrapper script: /usr/libexec/openconnect/csd-post.sh
  • Reported OS: Windows 10 (I didn't try another)
  • Machine certificate: <None>
  • Machine private key: <will be greyed out>
  • User certification: <None>
  • User private key: <will be greyed out>
  • Use FSID for key passphrase: No (unchecked)
  • Prevent user from manually accepting invalid credentials: No (unchecked)
  • Token mode: TOTP - manually entered

This is similar to what had worked before. What changed:

  • It didn't work without setting the User Agent to "AnyConnect"
  • I set the token mode to "TOTP - manually entered"

This opens up a web login page where one can enter their credentials.

Infra and RelEng Update – Week 47 2024

Posted by Fedora Community Blog on 2024-11-22 11:00:00 UTC

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 18 – 22 November 2024

Infra&Releng infographic

Infrastructure & Release Engineering

The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues

Fedora Infra

CentOS Infra including CentOS CI

Release Engineering

If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.

The post Infra and RelEng Update – Week 47 2024 appeared first on Fedora Community Blog.

PHP version 8.4 is released!

Posted by Remi Collet on 2024-11-21 09:33:00 UTC

RC4 was GOLD, so version 8.4.1 GA was just released, at the planned date.

A great thanks to Eric Mann, Calvin Buckley and Saki Takamachi, our Release Managers, to all developers who have contributed to this new, long-awaited version of PHP, and to all testers of the RC versions who have allowed us to deliver a good-quality version.

RPMs are available in the php:remi-8.4 module for Fedora and Enterprise Linux ≥ 8 and as Software Collection in the remi-safe repository.

Read the PHP 8.4.1 Release Announcement and its Addendum for new features and detailed description.

For memory, this is the result of 6 months of work for me to provide these packages, starting in July for Software Collections of alpha versions, in September for module streams of RC versions, and also a lot of work on extensions to provide a mostly full PHP 8.4 stack.

emblem-notice-24.pngInstallation: read the Repository configuration and choose installation mode, or follow the Configuration Wizard instructions.

Replacement of default PHP by version 8.4 installation (simplest):

Fedora modular or Enterprise Linux:

dnf module reset php
dnf module install php:remi-8.4

Parallel installation of version 8.4 as Software Collection (recommended for tests):

yum install php84

emblem-important-2-24.pngTo be noticed :

  • EL-10 RPMs are built using RHEL-10.0-beta
  • EL-9 RPMs are built using RHEL-9.5
  • EL-8 RPMs are built using RHEL-8.10
  • This version will also be the default version in Fedora 42
  • Many extensions are already available, see the PECL extension RPM status page.

emblem-notice-24.pngInformation, read:

Base packages (php)

Software Collections (php84)

PHP version 8.1.30, 8.2.24 and 8.3.12

Posted by Remi Collet on 2024-09-27 06:33:00 UTC

RPMs of PHP version 8.3.12 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.2.24 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.1.30 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-important-2-24.pngPHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.

These versions are also available as Software Collections in the remi-safe repository.

security-medium-2-24.pngThese Versions fix 4 security bugs (CVE-2024-8925, CVE-2024-8926, CVE-2024-8927, CVE-2024-9026), so update is strongly recommended.

Version announcements:

emblem-notice-24.pngInstallation: use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.3 installation (simplest):

dnf module switch-to php:remi-8.3/common

Parallel installation of version 8.3 as Software Collection

yum install php83

Replacement of default PHP by version 8.2 installation (simplest):

dnf module switch-to php:remi-8.2/common

Parallel installation of version 8.2 as Software Collection

yum install php82

And soon in the official updates:

emblem-important-2-24.pngTo be noticed :

  • EL-9 RPMs are built using RHEL-9.4
  • EL-8 RPMs are built using RHEL-8.10
  • EL-7 repository is closed
  • intl extension now uses libicu74 (version 74.2)
  • mbstring extension (EL builds) now uses oniguruma5php (version 6.9.9, instead of the outdated system library)
  • oci8 extension now uses the RPM of Oracle Instant Client version 23.5 on x86_64, 19.24 on aarch64
  • a lot of extensions are also available, see the PHP extensions RPM status (from PECL and other sources) page

emblem-notice-24.pngInformation:

Base packages (php)

Software Collections (php81 / php82 / php83)

PHP version 8.2.26RC1 and 8.3.14RC1

Posted by Remi Collet on 2024-11-08 05:52:00 UTC

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.14RC1 are available

  • as base packages in the remi-modular-test for Fedora 39-41 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

RPMs of PHP version 8.2.26RC1 are available

  • as base packages in the remi-modular-test for Fedora 39-41 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-notice-24.pngPHP version 8.1 is now in security mode only, so no more RC will be released.

emblem-notice-24.pngInstallation: follow the wizard instructions.

emblem-notice-24.png 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:

dnf module switch-to php:remi-8.3
dnf --enablerepo=remi-modular-test update php\*

Update of system version 8.2:

dnf module switch-to php:remi-8.2
dnf --enablerepo=remi-modular-test update php\*

emblem-notice-24.png Notice:

  • version 8.4.0RC4 is in Fedora rawhide for QA
  • version 8.4.0RC4 is also available in the repository
  • EL-9 packages are built using RHEL-9.4
  • EL-8 packages are built using RHEL-8.10
  • oci8 extension uses the RPM of the Oracle Instant Client version 23.5 on x86_64 or 19.24 on aarch64
  • intl extension uses libicu 74.2
  • RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
  • versions 8.2.25 and 8.3.13 are planed for October 24th, in 2 weeks.

Software Collections (php82, php83)

Base packages (php)

PHP version 8.2.25 and 8.3.13

Posted by Remi Collet on 2024-10-24 13:57:00 UTC

RPMs of PHP version 8.3.13 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.2.25 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-notice-24.pngThere is no security fix this month, so no update for version 8.1.30.

emblem-important-2-24.pngPHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.

These versions are also available as Software Collections in the remi-safe repository.

Version announcements:

emblem-notice-24.pngInstallation: use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.3 installation (simplest):

dnf module switch-to php:remi-8.3/common

Parallel installation of version 8.3 as Software Collection

yum install php83

Replacement of default PHP by version 8.2 installation (simplest):

dnf module switch-to php:remi-8.2/common

Parallel installation of version 8.2 as Software Collection

yum install php82

And soon in the official updates:

emblem-important-2-24.pngTo be noticed :

  • EL-9 RPMs are built using RHEL-9.4
  • EL-8 RPMs are built using RHEL-8.10
  • EL-7 repository is closed
  • intl extension now uses libicu74 (version 74.2)
  • mbstring extension (EL builds) now uses oniguruma5php (version 6.9.9, instead of the outdated system library)
  • oci8 extension now uses the RPM of Oracle Instant Client version 23.5 on x86_64, 19.24 on aarch64
  • a lot of extensions are also available, see the PHP extensions RPM status (from PECL and other sources) page

emblem-notice-24.pngInformation:

Base packages (php)

Software Collections (php81 / php82 / php83)

PHP version 8.1.31, 8.2.26 and 8.3.14

Posted by Remi Collet on 2024-11-21 08:46:00 UTC

RPMs of PHP version 8.3.14 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.2.26 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.1.31 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-important-2-24.pngPHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.

These versions are also available as Software Collections in the remi-safe repository.

security-medium-2-24.pngThese Versions fix 6 security bugs (CVE-2024-11233, CVE-2024-11234, CVE-2024-11236, CVE-2024-8929, CVE-2024-8932), so update is strongly recommended.

Version announcements:

emblem-notice-24.pngInstallation: use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.3 installation (simplest):

dnf module switch-to php:remi-8.3/common

Parallel installation of version 8.3 as Software Collection

yum install php83

Replacement of default PHP by version 8.2 installation (simplest):

dnf module switch-to php:remi-8.2/common

Parallel installation of version 8.2 as Software Collection

yum install php82

And soon in the official updates:

emblem-important-2-24.pngTo be noticed :

  • EL-10 RPMs are built using RHEL-10.0-beta
  • EL-9 RPMs are built using RHEL-9.4
  • EL-8 RPMs are built using RHEL-8.10
  • EL-7 repository is closed
  • intl extension now uses libicu74 (version 74.2)
  • mbstring extension (EL builds) now uses oniguruma5php (version 6.9.9, instead of the outdated system library)
  • oci8 extension now uses the RPM of Oracle Instant Client version 23.6 on x86_64, 19.24 on aarch64
  • a lot of extensions are also available, see the PHP extensions RPM status (from PECL and other sources) page

emblem-notice-24.pngInformation:

Base packages (php)

Software Collections (php81 / php82 / php83)

Server updates and reboots

Posted by Fedora Infrastructure Status on 2024-11-20 21:00:00 UTC

We will be updating and rebooting servers to pick up the recent RHEL 9.5 release as well as to move a number of instances to Fedora 41

This outage impacts the most maintainer / contributor services for some short windows during the outage.

New badge: Let's have a watch party (Fedora 41) !

Posted by Fedora Badges on 2024-11-20 19:34:29 UTC
LetYou attended the F41 Online Release Watch Party!

© 2016 Red Hat, Inc. and others. Please send any comments or corrections to the websites team.

The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community maintained site. Red Hat is not responsible for content.

Your words are your own, duh. Nothing here represents Fedora™, Red Hat, Inc, or pretty much anything else. If you think it does then you are badly misled