Distributions
Fedora rawhide packages gating, for real!
How we have implemented gating rawhide packages in Fedora
Rawhide, the, rolling, development version of Fedora has often been considered has too broken and too unstable. Sometime to the detriment of the development of stable releases as well.
In a near future, this should no longer be happening as now every change made to every package landing in Fedora rawhide can be gated based on test results.
This talk will walk you through the processes and changes that Fedora landed to make of this idea a reality.
Rawhide is the development version of Fedora. It is the version from which stable Fedora releases branch from and thus every change made to it will trickle down to the next stable release. This also means that there are time in the development of Fedora where changes landing in rawhide can (and do!) have a detrimental effect on the next stable release.
With the rawhide package gating initiative, Fedora has gained mechanisms to test and gate packages based on the results of these tests.
In this talk we will go through the mechanisms built to allow this gating, how it works, how to debug if there are issues with it.
We will also gladly receive feedback from Fedora contributors who have interacted with it.
Additional information
| Type | devroom |
|---|
More sessions
| 2/2/20 |
In the beginning there was compiling and static linking. My first programs when I was 10 years old worked like that. Then, we discovered dynamic linking. This was great because we could now patch one library and all of the programs would pick up the change on restart. But we created another problem - dependencies. Throughout the history of computing we have solved one problem and created another. Containers are no different. This talk will walk through why we invented Linux distros and why we ...
|
| 2/2/20 |
What are the new features in the upcoming R1/beta2? How did the packaging system work out? How to make your software easier to port to it, and how to contribute?
|
| 2/2/20 |
A talk about the Homebrew package manager and how we've been working with our users to introduce new features to subsets of users, encouraging users to donate to the project and communicating both these to as many users as possible without being annoying.
|
| 2/2/20 |
This talk demonstrates how to use GNU Guix to build a root filesystem for an embedded device (Pine A64 LTS). I will also try to answer the question: could GNU Guix be a viable alternative to the Yocto project and what would be the benefits of using GNU Guix?
|
| 2/2/20 |
There is a multitude of software or code ecosystems: Linux distribution packages, language-specific (e.g. Python or node.js) modules, third-party desktop themes, git repositories, and recently also Flatpak and Snap. Users thus obtain software and code mainly from the network. This talk explores what can go wrong in such code delivery mechanisms, and what actually went wrong when a new threat has materialized: networks in certain countries started to be unreliable "thanks" to the governments ...
|
| 2/2/20 |
The concept of home directories on Linux/UNIX has little changed in the last 39 years. It's time to have a closer look, and bring them up to today's standards, regarding encryption, storage, authentication, user records, and more. In this talk we'll talk about "systemd-homed", a new component for systemd, that reworks how we do home directories on Linux, adds strong encryption that makes sense, supports automatic enumeration and hot-plugged home directories and more.
|
| 2/2/20 |
Systemd provides a bunch of features which can be used to contain and secure services, making security and isolation primitives provided by the kernel accessible to system programs. This allows service authors to write much simpler code, and often to avoid any integration with the operating system for security purposes. Unfortunately, those features are still not widely used, possibly because developers want to maintain compatibility with a wide range of systems. I'll talk about the features ...
|
