Language Selection

English French German Italian Portuguese Spanish

Red Hat

The Fedora distribution Allows user to install multiple version of RPM packages using Modularity Repository

Filed under
Red Hat

The Fedora distribution has introduced a new concept called Modularity Repository, which enables Fedora users to install different versions of a package from the distribution’s repositories.

This is not added recently in Fedora, it was shipped with Fedora 28 server edition as an optional repository with additional content.

A lot has changed since then, and now Modularity is a core part of the Fedora distribution.

Read more

Events in America: Fedora 30 Release Party Mexico City and LibOCon Latinoamérica

Filed under
LibO
Red Hat
  • Fedora 30 Release Party Mexico City

    On May 23, 2019, the Fedora Community in Mexico City ran an awesome Fedora 30 Release Party. This activity took place in the local Red Hat office. We really appreciate the space for our activities and particularly thanks to Alex Callejas (darkaxl017) for doing all the necessary paperwork.

    We had three main activities: An amazing talk from Rolando Cedillo (@rolman) about KVM in Fedora, a Q&A session and our networking time with piz

  • LibOCon Latinoamérica – Asunción 2019, July 19 – 20

    A quick video inviting you to the LibreOffice Latin America Conference 2019! (English subtitles are available.) It will be held at the Facultad Politécnica de Universidad Nactional de Asunción (FPUNA) in Asunción, Paraguay on July 19th (Friday) and 20th (Sat). For more information about the conference please visit the website.

Fedora: Elliott Sales de Andrade, Outreachy and Katacoda

Filed under
Red Hat
  • Fedora Update Week 20–22

    Oops, again a bit late, but the past two weekends were fairly busy. I decided to post this today so that it wouldn’t slip another full week. So this probably looks a bit larger than usual, but I hope I didn’t miss anything. Two weeks ago was rather busy with many updates. Not just new releases, but I also spent a little time going over old updates that I’ve missed and ignored due to missing dependencies. Some of these dependencies could be skipped, so I did in order to get the update in.

    Last week was a bit calmer with the updates. Instead, I spent the past week preparing several new Go packages that are dependencies for htmltest, an interesting tool for testing HTML files. I’m hoping these will get some reviews soon.

    Last week was also spent trying to figure out several upstream bugs. Pillow has been having issues on s390x. This turned out to be a bug in the types passed via varargs between Python and C code. Because of disagreement on argument size, this generally ends up being problematic on big-endian systems. I’m still waiting for the upstream PR to be accepted, but we’ve used the patch and been able to rebuild several other dependent packages with it now applied.

    With python-zarr, I’ve been running into failures with LMDB on 32-bit systems. This is generally annoying since it requires rebuilds whenever it got built on one of those systems. Basically, the LMDB store opens a very large file mapping and even though there’s enough RAM to do so, it fails. Thanks to some discussion on the devel mailing list I was pointed in the right direction to fix it. The tests rely on old store being garbage collected, and so a lot of old LMDB mappings are still around causing later ones to fail. I’ve opened a pull request upstream to explicitly close these stores, which reduces the overall memory requirement and fixes the tests.

  • Fedora Community Blog: Outreachy with Fedora Happiness Packets: Phase 1

    This blog post summaries what I’ve completed in Phase 1 in my Outreachy internship with Fedora Happiness Packets, things I learned and the challenges I faced

  • Katacoda scenario creation

Red Hat and SUSE: Openshift, RHEL and Cloudwashing

Filed under
Red Hat
SUSE
  • Using Kubernetes Operators to Manage Let’s Encrypt SSL/TLS Certificates for Red Hat OpenShift Dedicated
  • No Downtime Upgrade for Red Hat Data Grid on Openshift

    In a blog post I wrote on the Red Hat Developer’s Blog, I wrote about multiple layers of security available while deploying Red Hat Data Grid on Red Hat Openshift. Another challenging problem I see for customer is performing a no downtime upgrade for Red Hat Data Grid images (published on Red Hat Container Catalog). That’s what we’re going to tackle in this post.

    If you’re new to it, Red Hat Data Grid is an in-memory, distributed, NoSQL datastore solution. With it, your applications can access, process, and analyze data at in-memory speed designed to deliver a superior user experience compared to traditional data stores like relational databases. In-memory Data Grids have a variety of use cases in today’s environments, such as fast data access for low-latency apps, storing objects (NoSQL) in a datastore, achieving linear scalability with data distribution/partitioning, and data high-availability across geographies.

  • World domination with cgroups in RHEL 8: welcome cgroups v2!

    One of the great things about open source development is that features can be designed and implemented organically and grow and change as needed. However, a drawback is that this methodology can sometimes lead to a hot mess and uncomfortable technical debt.

    In the case of cgroups v1, as the maintainer Tejun Heo admits, "design followed implementation," "different decisions were taken for different controllers," and "sometimes too much flexibility causes a hindrance."

    In short, not all of the controllers behave in the same manner and it is also completely possible to get yourself into very strange situations if you don’t carefully engineer your group hierarchy. Therefore, cgroups v2 was developed to simplify and standardize some of this.

    Let’s take a look at how the two versions are different. I’m going to show two different diagrams - controllers are in yellow blocks and cgroup directories have a grey background.

  • Cloud Strategies in Frankfurt
  • Are We Ready to Ditch the Data Center? [Ed: Perpetuating the myth that when you outsource all business functions to the Pentagon through its partners the servers just vanish and cease to exist]

    Over the past few decades, organizations have come to rely on their own data centers to run business applications, network their users together and for data storage. Initially, these data centers were largely hardware-centric.In the early days, a mainframe and terminals were the order of the day, before we moved onto the RISC/UNIX era, followed more recently by the server sprawl period of commodity X86 servers.
    But now, the whole concept of an organization-owned data center is going through a radical change. It started with virtualization, which separated the direct relationship between application software and the underlying hardware infrastructure. This helped improve server utilization, efficiency, and provisioning speed. The next step towards an even greater level of abstraction is the move to a software-defined infrastructure (SDI), including compute, storage and networking.

Speed Up Gnome Shell On Fedora 30 Using This Copr Repository

Filed under
Red Hat

There's a Copr repository for Fedora 30 that presumably speeds up Gnome Shell and Mutter by adding some patches. The repository also has builds for Fedora 29, and while they are no longer maintained, they should still work.

Gnome already worked fine on my laptop running Fedora 30, so I can't say from personal experience how big of an impact it makes. You can give it a try, and if you don't notice any improvements, or if it makes things worse, you can easily remove it.

Read more

Also: Fedora Gooey Karma Week 2 report GSoC

Converting fedmsg consumers to fedora-messaging

Filed under
Red Hat

So in case you hadn’t heard, the Fedora infrastructure team is currently trying to nudge people in the direction of moving from fedmsg to fedora-messaging.

Fedmsg is the Fedora project-wide messaging bus we’ve had since 2012. It backs FMN / Fedora Notifications and Badges, and is used extensively within Fedora infrastructure for the general purpose of “have this one system do something whenever this other system does something else”. For instance, openQA job scheduling and result reporting are both powered by fedmsg.

Over time, though, there have turned out to be a few issues with fedmsg. It has a few awkward design quirks, but most significantly, it’s designed such that message delivery can never be guaranteed. In practice it’s very reliable and messages almost always are delivered, but for building critical systems like Rawhide package gating, the infrastructure team decided we really needed a system where message delivery can be formally guaranteed.

Read more

Fedora: Applications for Writing Markdown, Community Platform Engineering Team, Securing Linux with Ansible

Filed under
GNU
Linux
Red Hat
  • Fedora Magazine: Applications for writing Markdown

    Markdown is a lightweight markup language that is useful for adding formatting while still maintaining readability when viewing as plain text. Markdown (and Markdown derivatives) are used extensively as the priumary form of markup of documents on services like GitHub and pagure. By design, Markdown is easily created and edited in a text editor, however, there are a multitude of editors available that provide a formatted preview of Markdown markup, and / or provide a text editor that highlights the markdown syntax.

    This article covers 3 desktop applications for Fedora Workstation that help out when editing Markdown.

  • Fedora Community Blog: State of the Community Platform Engineering team

    About two years ago the Fedora Engineering team merged with the CentOS Engineering team to form what is now called the Community Platform Engineering (CPE) team. For the team members, the day to day work did not change much.

    The members working on Fedora are still fully dedicated to work on the Fedora project on those working on CentOS are still fully dedicated to CentOS. On both projects its members are involved in infrastructure, release engineering, and design. However, it brought the two infrastructures and teams closer to each other, allowing for more collaboration between them.

    There are 20 people on this consolidated team.

  • Christopher Smart: Securing Linux with Ansible

    The Ansible Hardening role from the OpenStack project is a great way to secure Linux boxes in a reliable, repeatable and customisable manner.

    It was created by former colleague of mine Major Hayden and while it was spun out of OpenStack, it can be applied generally to a number of the major Linux distros (including Fedora, RHEL, CentOS, Debian, SUSE).

    The role is based on the Secure Technical Implementation Guide (STIG) out of the Unites States for RHEL, which provides recommendations on how best to secure a host and the services it runs (category one for highly sensitive systems, two for medium and three for low). This is similar to the Information Security Manual (ISM) we have in Australia, although the STIG is more explicit.

Fedora: DNF, Fedora Program Management, PHP and Fedora Magazine

Filed under
Red Hat
  • PostgreSQL and upgrades

    As mentioned previously, I run a personal Fediverse instance with Pleroma, which uses Postgres. On Fedora, of course. So, a week ago, I went to do the usual "dnf distro-sync --releasever=30". And then, Postgres fails to start, because the database uses the previous format, 10, and the packages in F30 require format 11. Apparently, I was supposed to dump the database with pg_dumpall, upgrade, then restore. But now that I have binaries that refuse to read the old format, dumping is impossible. Wow.

    A little web searching found an upgrader that works across formats (dnf install postgresql-upgrade; postgresql-setup --upgrade). But that one also copies the database, like a dump-restore procedure would. What if the database is too large for this? Am I the only one who finds these practices unacceptable?

  • Fedora Community Blog: FPgM report: 2019-23

    Here’s your report of what has happened in Fedora Program Management this week. Elections voting is underway!

    I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.

  • PHPUnit 8.2

    RPM of PHPUnit version 8.2 are available in remi repository for Fedora ≥ 27 and for Enterprise Linux (CentOS, RHEL...).

  • Fedora Magazine: Contribute to Fedora Magazine

Council policy proposal: modify election eligibility

Filed under
Red Hat

Inspired by the request that we provide written guidance on time commitment expectations and some conversations from our meeting in December, I have submitted a pull request to implement a policy that anyone running for an elected Fedora Council seat not run for other elected boards at the same time:

The reasoning is that we have an unspoken (for now) expectation that being on the Council, particularly as an elected representative, will not be a trivial commitment. This is an easier check than trying to determine post-election which body a candidate would rather serve on (and thus having to deal with alternates, etc).

Read more

Today: IBM is laying off more than 1,000 employees

Syndicate content

More in Tux Machines

First Release Candidate of Linux 5.3

  • Linux 5.3-rc1
    It's been two weeks, and the merge window is over, and Linux 5.3-rc1
    is tagged and pushed out.
    
    This is a pretty big release, judging by the commit count. Not the
    biggest ever (that honor still goes to 4.9-rc1, which was
    exceptionally big), and we've had a couple of comparable ones (4.12,
    4.15 and 4.19 were also big merge windows), but it's definitely up
    there.
    
    The merge window also started out pretty painfully, with me hitting a
    couple of bugs in the first couple of days. That's never a good sign,
    since I don't tend to do anything particularly odd, and if I hit bugs
    it means code wasn't tested well enough. In one case it was due to me
    using a simplified configuration that hadn't been tested, and caused
    an odd issue to show up - it happens. But in the other case, it really
    was code that was too recent and too rough and hadn't baked enough.
    The first got fixed, the second just got reverted.
    
    Anyway, despite the rocky start, and the big size, things mostly
    smoothed out towards the end of the merge window. And there's a lot to
    like in 5.3. Too much to do the shortlog with individual commits, of
    course, so appended is the usual "mergelog" of people I merged from
    and a one-liner very high-level "what got merged". For more detail,
    you should go check the git tree.
    
    As always: the people credited below are just the people I pull from,
    there's about 1600 individual developers (for 12500+ non-merge
    commits) in this merge window.
    
    Go test,
    
                Linus
    
  • Linux 5.3-rc1 Debuts As "A Pretty Big Release"

    Just as expected, Linus Torvalds this afternoon issued the first release candidate of the forthcoming Linux 5.3 kernel. It's just not us that have been quite eager for Linux 5.3 and its changes. Torvalds acknowledged in the 5.3-rc1 announcement that this kernel is indeed a big one: "This is a pretty big release, judging by the commit count. Not the biggest ever (that honor still goes to 4.9-rc1, which was exceptionally big), and we've had a couple of comparable ones (4.12, 4.15 and 4.19 were also big merge windows), but it's definitely up there."

  • The New Features & Improvements Of The Linux 5.3 Kernel

    The Linux 5.3 kernel merge window is expected to close today so here is our usual recap of all the changes that made it into the mainline tree over the past two weeks. There is a lot of changes to be excited about from Radeon RX 5700 Navi support to various CPU improvements and ongoing performance work to supporting newer Apple MacBook laptops and Intel Speed Select Technology enablement.

today's howtos and programming bits

  • How to fix Ubuntu live USB not booting
  • How to Create a User Account Without useradd Command in Linux?
  • Container use cases explained in depth
  • Containerization and orchestration concepts explained
  • Set_env.py

    A good practice when writing complicated software is to put in lots of debugging code. This might be extra logging, or special modes that tweak the behavior to be more understandable, or switches to turn off some aspect of your test suite so you can focus on the part you care about at the moment. But how do you control that debugging code? Where are the on/off switches? You don’t want to clutter your real UI with controls. A convenient option is environment variables: you can access them simply in the code, your shell has ways to turn them on and off at a variety of scopes, and they are invisible to your users. Though if they are invisible to your users, they are also invisible to you! How do you remember what exotic options you’ve coded into your program, and how do you easily see what is set, and change what is set?

  • RPushbullet 0.3.2

    A new release 0.3.2 of the RPushbullet package is now on CRAN. RPushbullet is interfacing the neat Pushbullet service for inter-device messaging, communication, and more. It lets you easily send alerts like the one to the left to your browser, phone, tablet, … – or all at once. This is the first new release in almost 2 1/2 years, and it once again benefits greatly from contributed pull requests by Colin (twice !) and Chan-Yub – see below for details.

  • A Makefile for your Go project (2019)

    My most loathed feature of Go was the mandatory use of GOPATH: I do not want to put my own code next to its dependencies. I was not alone and people devised tools or crafted their own Makefile to avoid organizing their code around GOPATH.

  • Writing sustainable Python scripts

    Python is a great language to write a standalone script. Getting to the result can be a matter of a dozen to a few hundred lines of code and, moments later, you can forget about it and focus on your next task. Six months later, a co-worker asks you why the script fails and you don’t have a clue: no documentation, hard-coded parameters, nothing logged during the execution and no sensible tests to figure out what may go wrong. Turning a “quick-and-dirty” Python script into a sustainable version, which will be easy to use, understand and support by your co-workers and your future self, only takes some moderate effort. 

  • Notes to self when using genRSS.py

The Status of Fractional Scaling (HiDPI) Between Windows & Linux

There’s a special type of displays commonly called “HiDPI“, which means that the number of pixels in the screen is doubled (vertically and horizontally), making everything drawn on the screen look sharper and better. One of the most common examples of HiDPI are Apple’s Retina displays, which do come with their desktops and laptops. However, one issue with HiDPI is that the default screen resolutions are too small to be displayed on them, so we need what’s called as “scaling”; Which is simply also doubling the drawn pixels from the OS side so that they can match that of the display. Otherwise, displaying a 400×400 program window on a 3840×2160 display will give a very horrible user experience, so the OS will need to scale that window (and everything) by a factor of 2x, to make it 800×800, which would make it better. Fractional scaling is the process of doing the previous work, but by using fractional scaling numbers (E.g 1.25, 1.4, 1.75.. etc), so that they can be customized better according to the user’s setup and needs. Now where’s the issue, you may ask? Windows operating system has been supporting such kind of displays natively for a very long time, but Linux distributions do lack a lot of things in this field. There are many drawbacks, issues and other things to consider. This article will take you in a tour about that. Read more Also: Vulkan 1.1.116 Published With Subgroup Size Control Extension

Android Leftovers