Posts Tagged ‘Open Source’

New Mageia Board


After releasing its 8th version, the community members part of the french 1901 law association had a meeting tonight to reinvigorate the work done by the association in support of the distribution, and elected a new board to support that goal.

I’m proud to have gathered the trust of my fellow association members and been elected as a board member ! We also have a brand new chairman (neoclust, more than 2000 packages maintained !), a new secretary (auroud85, mister QA) and a new treasurer (maat, French users community).

With that new team in place and acting, I’m sure you’ll hear more and more about our distribution through various channels !

Mageia 8 is out


As announced on the project site, Mageia 8 is now out ! It’s great to see the community succeeding in another joint work to publish that one.

Now, I have to update my servers, my laptops, my workstations in order to benefit from it. Won’t happen tomorrow however, as each time I need to check for major release updates and potential migration aspects before doing so. Using it for all what I do from apache, freedb, squid, shorewall to gnucash, tellico, digikam, and of course the usual firefox, thunderbird/mutt, libreoffice, that’s quite some software to test. Not counting the one I need to use on top of it such as teams, hpemyroom, zoom, openconnect with a Yubikey for my work.

Will start to look at shorewall first and fix my ansible playbooks to deploy the conf once the machine has been updated. Some fun ahead 😉

Congrats to all of you who contributed to that release (myself included in fact !!)

project-builder 0.16.1 is now available


When you start updating something, you often finish working on a unrelated but necessary topic before being able to finaly solve your first problem 🙂

So I had received remarks on issues to install MondoRescue on latest Ubuntu vesions (18.04 and 20.04) because of the lack of afio and also star in the distribution. Indeed both have been droped in Debian since quite some times in fact 😦

So in that case you have various choices :

  1. give up (not my state of mind anyway !).
  2. point them to the sources of the tools so they help themselves.
  3. move to more supported tools (that’s something that is now planned).
  4. provide users with the appropriate packages.

The two last possibilities are the nicest to me and the users. So I first build a round of packages for afio for all latest Debian and Ubuntu distributions, at least to unblock users. I already had the build infra in place, and a spec file for rpm, so wasn’t too hard to do it. Next one on the list is s-tar. And that’s where the perturbation happened 😉

I realized I had a hole in project-builder as it was always supposing that upstream tar files were in tar.gz format. That’s not a problem when you develop the upstream project yourself, because you generate indeed these files, but when upstream is s-tar and provides tar.bz2 files, suddenly you have a bug to solve 😉 Interestingly enough I didn’t had any issue since 13 years I’m working with the tool.

It wasn’t that hard to fix as the places referencing a source tar.gz file were easy to find, but that had implication also in the 150+ VMs and CTNs I’m managing to build packages. All of them also needed to have a update in order to support that correctly. Now project-builder doesn’t make any assumption on the nature of the tar file (but still requires a tar file BTW). A lazy solution would have been to just unpack/repack s-tar and voilà ! But I want to be able to use the upstream delivery untouched (checksum included).

So due to that 0.16.1 (to show incompatibility with 0.15) is on its way to the ftp server, and built at the moment for the various distributions. Then i’ll have to update all my VMs and CTNs with that new version, and finally I’ll be able to generate s-tar packages.

Then I’ll be back to what I’m really working on, which is the 3.3.0 of MondoRescue !!

HPE now contributes to OpenBMC !


For those of you reading articles on this blog, this is not completely a new info. Indeed, during Fosdem, it was already possible to see a demo unit of a HPE ProLiant DL 360 running Linuxboot and an iLO 5 running an OpenBMC software stack.

But that was a proof of concept. Now, HPE has officially announced on the OpenBMC mailing list that we were contributing to the project and will bring our patches upstream, and help the community build a better software stack. I supppose that in particular our knowledge of the Redfish standard will be helpful to improve the project.

And more over, if your company is interested to test such a combination, feel free to contact Jean-Marie Verdun, Mike Garrett (both writers in the thread and promoters of this internally) or myself and we should be able to provide to you an access to such a system.

But that’s not all, we’re also…. hum, well you’ll know when it’s offically announced 🙂

Anyway, that’s the best news for our Open Source involvement since monthes and I’m glad that we’re making that possibility a reality for all the customers we have wanting a more open platform.

Stay tuned, more to come !

Code is not confined !


Well, people are, at least in my country (France). But code, isn’t and can still be delivered on server once new versions are available !

And I have been able these last days to work more intensively of my code, which was well needed. As I still want to publish MondoRescue 3.3.0 I have to put my build farm in order to do that correctly. MondoRescue’s code is frozen for now, but‘s wasn’t and was in need of fixes. So I solved all the one I wanted, and I’m now publishing version 0.15.3, and have updated all my VMs (170) and containers (40) with it, so ready to start next week on building MondoRescue, once‘s own build is done.

Here is a list of what’s new with this version:

Fix #177– newproj command works again
Fix #184– with lots of performance improvements for sbx2build phase, back to early days
Feature– Adds internal YAML availability as last resort
Fix #180– by adding the pb_check_v function
Fix #181– with working *2docker commands to build the full stack for a project
Fix #183– by pushing the repomd.xml.asc file for SUSE and fix also repo names
Fix #140– where one extra line was generated in the pbcl
Feature– Adds install2pkg command
Fix #171– by initializing correctly pb_env_init in pbgetparam
Feature– Adds support for fedora 31, centos 8

As I write, code is appearing on and you’ll be able to use it starting tomorrow use the instructions to install from packages for your distribution (urpmi, dnf, yum, zypper, apt are your freinds !)

Using zoom on Mageia 7


As lots of people confined in these difficult times, I’m working remotely. And here at home, as when I’m at work, I’m using a Linux machine to perform all my tasks. What else ?!!

Among the interactive tools I can use to interact wih my colleagues, there is Skype Enterprise (no luck on LInux, so using just a phone call, painful), HPE My Room (multi-platform with many features and usable on Mageia 7), Microsoft Teams (which is working nicely on Mageia 7 without issue, and you even have source code access under GPLv3 for an unofficial client), and the fully FLOSS Jitsi.

But some of my recent meeting requests were also using zoom. And while there is indeed a Linux client, due to libraries versions incompatibilities, it refuses to install on Linux, and even when forced to, doesn’t launch.

So I had to create a small Fedora:32 container, and with some suitable parameters, zoom is now working in it. To ease it, I have create a small script to launch the stuff:

# Licensed under the GPLv3 🙂
mkdir -p /tmp/docker-fedora
export LUID=`id -u`
cd /tmp/docker-fedora
if [ ! -f zoom_x86_64.rpm ]; then

cat > Dockerfile << EOF
FROM fedora:32
RUN dnf makecache
RUN dnf -y update || true
COPY zoom_x86_64.rpm /
RUN dnf install -y /zoom_x86_64.rpm
RUN dnf install -y pulseaudio pulseaudio-utils libglvnd-gles
RUN useradd $USER -u $LUID  -N -M -d $RD/$USER
RUN usermod -a -G audio $USER
RUN echo "$USER ALL=NOPASSWD:/usr/bin/dnf" >> /etc/sudoers
CMD zoom
docker inspect pb:zoombuild 2>&1 > /dev/null
if [ $? -eq 0 ]; then
    if [ "$BASH_ARGV" = "-f" ]; then
        docker rmi pb:zoombuild
if [ $build -eq 1 ]; then
    docker build --file=Dockerfile -t pb:zoombuild .
if [ $stat -eq 0 ]; then
    # Priviledge needed for zoom command in ctn
    docker run --device /dev/snd --device /dev/usb --rm -v $RD/$USER:$RD/$USER --cap-add=SYS_ADMIN -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v /run/user/$LUID/pulse/native:/run/pulse/native -e PULSE_SERVER=/run/pulse/native -e PATH=/usr/bin:$PATH -ti pb:zoombuild

Just run that script and you can join a zoom conf call, benefiting from sound at least (I have no webcam to test the video at the moment).

So now, dear mageians no excuse to stay confined without contacts with your colleagues 😉

Back from the Fosdem


As usual Fosdem was crowdy. On Saturday, I decided to not try to enter in the container Devroom (whose queue was insane), and went instead to the Legal Devroom. This year, they decided to change their organisation and to have debates between people defending contrary positions (should licenses reflect ethical aspects, are the 4 freedoms too old, …)

Legal Devroom at Fosdem 2020

Unfortunately, as they didn’t manage to have people really having different opinions on the topics, it sounded a bit artificial sometimes, and didn’t really allow to enter more deeply in the subject, as a more classical roundtable would have allowed. 4 debates were probably too much, and having 1 or 2 (with real oponents, but respecting each other) and 2 or 3 round tables would probably be a better balance. Anyway, was even fun sometimes (can you believe that from a large set of lawyers ;-)) I passed the day in that room, where you could seat without issue and have good content.

One of the debates was around Bill of Material (BoM) vs source code delivery. And I really thought they didn’t go into enough details. Because it’s very difficult to reproduce software. And while BoM is hard to automate, and mostly useful for corporations that want to reduce risks (what they think BTW), providing the source, isn’t sufficient either. First as the GPL rightly points out, it’s not enough. You also need to provide the receipes to build the software. A Makefile e.g. helps a lot building the code the correct way. But what about the docs, the design schemas, the versions of the tools needed to build (or tested successfully contrary to others , gcc v5 vs 8 vs 10 ?), the precise versions of the dependencies (where doing npm install e.g. defeats tracking IMO) as you can only ensure that your software is working on a very specific environment (and reproduceable builds are linked to that). So clearly neither providing the sources + build files is sufficient, neither the BoM as it rarely provides all the required details, and would be a nightmare to reproduce, which creates an interesting challenge that shouldn’t be minimized when the produced software runs in a train, plane, or medical equipment of course. Which can lead you to re-read the excellent trusting the trust !

What they should also do is invite more european lawyers, as they are underrepresented, and some topics – author’s right vs copyright, EU law vs US law are not well enough taken in account IMHO. Contacting the ones behind EOLE would be a good start.

La Grande Place de Bruxelles, lieu des agapes nocturnes 😉

The evening is of course what most fosdemers like, because it’s time to meet again with friends you don’t see that often and enjoy beer (for the ones who like that !) and for me rather carbonade, wafles and more over chocolate 😉 As often, it was great to have dinner with Anne and Erwan (Kernel Receipes managers among other stuffs) and some of their friends. It always makes insightful discussions.

On Sunday, I decided to walk around and explore booths (I was needing some stickers for a new laptop !) which is a nice pretext to meet more relatives or make new ones ! Of course, each time I try to discuss with my fellow grenoblers (Vates, Algoo), or the french mafia, which lead me this year to … an HPE booth 🙂

LinuxBoot on a HPE ProLiant server DL 360 Gen10+ Beta

As Jean-Marie Verdun is back at HPE, he is also helping us with initiatives around LinuxBoot on our ProLiant servers (as shown on the left), and OpenBMC as well (while the one brought was still running the iLO Firmware as shown here on the right). It’s the first time it was ever demonstrated outside of a Lab, so big kudos to the team, and I’m sure lots of customers waiting for this will be very eager to ask for a test unit 😉

As usual Fosdem was crowdy. On Sunday, one way to test that is to go to the Janson auditorium, where keynotes happen. And when Jon Maddog is on stage, you can’t find a seat in it !!

Keynote of Jon Maddog Hall

It’s the first time I come without being a speaker, and that’s a bit more comfortable, as you don’t have to prepare material and deliver it, but as I am missing sharing info with others, I’ll try again next year to propose content, and I should have new one available for the audience. Stay tuned.

Happy 20th birthday to Fosdem, the greatest FLOSS event !

Attending Fosdem 2020


Well, after trying to speak again at FOSDEM 2020, and despite not being retained as a speaker, I’ll anyway attend this year’s FOSDEM as this is one of the best FLOSS Events on the planet and because that’s where you can meet with so many luminaries. And the food is also very good in Brussels, so I can’t wait for the 2 dinners I’ll pass with friends over there 😉 (ok, lunches are generally sandwishes based !)

Can’t say for once, meet you there, as it’s pretty difficult to find someone with so many devrooms or booths (maybe you’ll find me at the tracim one, as there is no Mageia one) at the same time, but that’s also why we like it.

And as I’m going on my own, without company support, you may find me more in the python room (to continue to learn on it) or stuff like CI/CD, containers, … or more probably talking with people 😉

CfP pour la µFLOSSCon 2020



Je suis d’abord ravi de vous souhaiter une année 2020 pleine de libertés numériques.

Et pour fêter cela, l’association FLOSSITA a le plaisir de vous annoncer la µFLOSSCon 2020 !

Quaesaquo ? Eh bien, c’est une FLOSSCon miniature, donnée lors du festival Transfo 2020, le 16 mars 2020, de 18h00 à 20h00 dans les locaux de CGI.

L’appel à conférenciers est donc officiellement lancé ; vous avez jusqu’au 29 février (profitons-en, ce n’est pas tous les ans qu’on peut le faire) pour soumettre un sujet (15′ ou 30′ selon votre loquacité) pour
parler de votre sujet favori lié au libre. Le programme retenu sera publié le 1 Mars et vous pourrez alors vous inscrire pour y participer. Faites passer le message (pour parler ou assister)

Je profite de ce message pour rappeler que FLOSSITA a décidé d’organiser une FLOSSCon complète en 2020 pour laquelle nous cherchons toujours un lieu d’accueil.

Presentations from the Redfish Workshop in Lyon


You can find the presentations made for the Redfish Workshop I organized in Lyon after the last Open Source Summit on the Workshop page. You’ll find there an updated status of the standard (2019.3) made by Jeff Autor compared to the version delivered in San Diego. Also you’ll find the level of adoption of Redfish by the OpenBMC project. As well, there is an interesting use case shared by Julien Niedergang from SUSE that wasn’t presented in San Diego.

If you managed an event and want to integrate that workshop in it, don’t hesitate to contact me so we can replay it.

Also available, the last version of the Docker Hands-on Lab that I delivered yesterday.