Welcome to Planet openSUSE

This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.

To have your blog added to this aggregator, please read the instructions.


Tuesday
11 June, 2019


face

Here is a straightforward port of some easy code.

randtable.c has a lookup table with seemingly-random numbers. This table is used by the following macros in bzlib_private.h:

extern Int32 BZ2_rNums[512];

#define BZ_RAND_DECLS                          \
   Int32 rNToGo;                               \
   Int32 rTPos                                 \

#define BZ_RAND_INIT_MASK                      \
   s->rNToGo = 0;                              \
   s->rTPos  = 0                               \

#define BZ_RAND_MASK ((s->rNToGo == 1) ? 1 : 0)

#define BZ_RAND_UPD_MASK                       \
   if (s->rNToGo == 0) {                       \
      s->rNToGo = BZ2_rNums[s->rTPos];         \
      s->rTPos++;                              \
      if (s->rTPos == 512) s->rTPos = 0;       \
   }                                           \
   s->rNToGo--;

Here, BZ_RAND_DECLS is used to declare two fields, rNToGo and rTPos, into two structs (1, 2). Both are similar to this:

typedef struct {
   ...
   Bool     blockRandomised;
   BZ_RAND_DECLS
   ...
} DState;

Then, the code that needs to initialize those fields calls BZ_RAND_INIT_MASK, which expands into code to set the two fields to zero.

At several points in the code, BZ_RAND_UPD_MASK gets called, which expands into code that updates the randomization state, or something like that, and uses BZ_RAND_MASK to get a useful value out of the randomization state.

I have no idea yet what the state is about, but let's port it directly.

Give things a name

It's interesting to see that no code except for those macros uses the fields rNToGo and rTPos, which are declared via BZ_RAND_DECLS. So, let's make up a type with a name for that. Since I have no better name for it, I shall call it just RandState. I added that type definition in the C code, and replaced the macro-which-creates-struct-fields with a RandState-typed field:

-#define BZ_RAND_DECLS                          \
-   Int32 rNToGo;                               \
-   Int32 rTPos                                 \
+typedef struct {
+   Int32 rNToGo;
+   Int32 rTPos;
+} RandState;

...

-      BZ_RAND_DECLS;
+      RandState rand;

Since the fields now live inside a sub-struct, I changed the other macros to use s->rand.rNToGo instead of s->rNToGo, and similarly for the other field.

Turn macros into functions

Now, three commits (1, 2, 3) to turn the macros BZ_RAND_INIT_MASK, BZ_RAND_MASK, and BZ_RAND_UPD_MASK into functions.

And now that the functions live in the same C source file as the lookup table they reference, the table can be made static const to avoid having it as read/write unshared data in the linked binary.

Premature optimization concern: doesn't de-inlining those macros cause performance problems? At first, we will get the added overhead from a function call. When the whole code is ported to Rust, the Rust compiler will probably be able to figure out that those tiny functions can be inlined (or we can #[inline] them by hand if we have proof, or if we have more hubris than faith in LLVM).

Port functions and table to Rust

The functions are so tiny, and the table so cut-and-pasteable, that it's easy to port them to Rust in a single shot:

#[no_mangle]
pub unsafe extern "C" fn BZ2_rand_init() -> RandState {
    RandState {
        rNToGo: 0,
        rTPos: 0,
    }
}

#[no_mangle]
pub unsafe extern "C" fn BZ2_rand_mask(r: &RandState) -> i32 {
    if r.rNToGo == 1 {
        1
    } else {
        0
    }
}

#[no_mangle]
pub unsafe extern "C" fn BZ2_rand_update_mask(r: &mut RandState) {
    if r.rNToGo == 0 {
        r.rNToGo = RAND_TABLE[r.rTPos as usize];
        r.rTPos 

face

Trois instantanés openSUSE Tumbleweed ont été publiés au cours des quatre premiers jours de juin, ce qui entraîne plusieurs mises à jour des paquets dans cette rolling-release.

L'instantané 20190604 apportait le paquet babl 0.1.64, améliorant la cohérence du code, la prise en charge de l'intégration continue (CI) de [gitlab](https://gitlab. com), ainsi que des améliorations d’autotools et meson build. Un accident dans la dénomination a entraîné le passage de la version 0.3.2 de bubblewrap à la version 0.3.3. Cependant, bubblewrap 0.3.3. a corrigé une vulnérabilité (CVE), fourni quelques corrections plus petites et ajouté l’API (Application Programming Interface) JSON qui permet de lire le code de sortie du processus interne. GNU Compiler Collection 8 a eu quelques mises à jour qui comprenaient quelques correctifs dont un rendant les constructions sans profilage reproductibles. La bibliothèque Generic Graphics Library gegl 0.4.16 a également ajouté le support de gitlab CI et utilise un allocateur personnalisé pour les données de mosaïque, qui aligne les données et les allocations de groupes dans des blocs ; ceci a été réalisé sur Linux en utilisant l'extension GNU malloc_trim pour permettre de forcer l'invocation de la fonction de récupération de place d'allocateurs, malloc, présente au sein de la glibc. La version 6.0.8 d’Oracle virtualbox corrigeait un crash lors de la mise hors tension d’une machine virtuelle sans contrôleur graphique et la version 1.20.5 de xorg-x11-server en corrigeait certains types d'entrées. L’instantané a actuellement une cote de 96, selon l'évaluateur d’instantané.

L'instantané 20190603 a mis à jour Mesa et Mesa-drivers en version 19.0.5 améliorant certaines parties du code et des pilotes. NetworkManager 1.16.2 a corrigé certaines autorisations erronées du fichier /var/lib/NetworkManager/secret_key. La mise à jour de la version mineure de Ceph a désactivé l'[Optimisation du temps de liaison](https://stackoverflow.com/questions/23736507/is-there-a-rreason-why-not-to -use-link-time-optimization-lto) dans le fichier spec lors de son utilisation. GNOME 3.32.2 comportait plusieurs mises à jour et correctifs de packages, notamment le correctif d'une régression qui entraînait la disparition de la catégorie "Fonts" (Polices). Tumbleweed a zappé la série 1.3.0 de Flatpak pour fournir directement à la version 1.4.0. Les principales modifications depuis la version 1.2.4 concernent l'utilisation améliorée des Entrées/Sorties pour les applications installées sur le système et le nouveau format des dépôts préconfigurées. Glib2 2.60.3 a mis à jour les traductions et fourni diverses corrections au support des petites clés/valeurs dans [GHashTable](https://developer.gnome.org/glib/stable /glib-Hash-Tables.html). Le langage de script php7 7.3.6 a ajouté une curl_version manquante et corrigé plusieurs autres bugs. L’instantané a actuellement une côte


Monday
10 June, 2019


Michael Meeks: 2019-06-10 Monday.

21:00 UTCmember

face
  • Mail chew, worked away at project planning and acceptance criteria. Couple of project calls and sync with Kendy.

face

Du vendredi 24 au dimanche 26 s’est tenue, à Nuremberg, la conférence annuelle du projet openSUSE. Comme chaque année, cette conférence est l’occasion de rassembler les membres de la communauté, de présenter les projets en cours et les grandes tendances techniques, de boire des bières et de faire le point sur l’avenir du projet.

Cliquez sur l'image pour l'afficher en taille normale

Nom : oSC19-logo-with-name-1-300x204.png </div>
        </div>
      </div>
      
      <hr class=
face

La comunidad de KDE está mejorando aspectos básicos de distintas partes del escritorio y aplicaciones para pulir errores y mejorar las aplicaciones. Este es un repaso semanal a algunas de esas tareas.

Como ya pudiste leer en otro artículo del blog, parte de la comunidad de KDE está inmersa en la ardua y extensa tarea de pulir y mejorar ciertos aspectos del escritorio Plasma y de las aplicaciones de KDE.

Desde hace ya varias semanas empecé la tarea de traducir y publicar en mi blog los anuncios en inglés para tratar de difundir y dar a conocer el trabajo que realiza la comunidad de KDE

Puedes leer todos los artículos que he traducido en este enlace:

Una semana más Nate Graham nos trae a su blog las novedades en cuanto a mejoras, correcciones de pequeños y grandes errores y nuevas opciones:

En este artículo traduzco, una vez más, el artículo de Nate Graham, para difundir lo que nos traerá KDE. Empezamos…

Ahora que Plasma 5.16 está en periodo de “congelación” y a punto de ser publicada, es hora de seguir trabajando y poner la vista en Plasma 5.17. Una de los grandes objetivos que se ha marcado Nate Graham, es dar un nuevo impulso y dar una evolución visual al tema de Plasma Breeze.

El primer componente ya ha llegado: ¡el generador de bordes de ventanas KWin ahora está fuera del tema Breeze de manera predeterminada!

No te preocupes, esto no significa que tengas que a puntar a un pixel para redimensionar las ventanas; hay áreas virtuales en las que poder redimensionar como el comportamiento que tenían los antiguos bordes, así que eso no ha cambiado

Tampoco eso ha afectado a otros temas, muchos de los cuales, tienen grades y elegantes bordes que destacan como parte del diseño de las ventanas. Pero Breeze es un tema minimalista, y este es uno de los primeros pasos dados para modernizar el aspecto de las aplicaciones de KDE.

¡Creemos que os va a encantar el resultado final!

Ahora sí, sin más preámbulos veamos cuales son esas novedades:

Nuevas características

Corrección de errores y mejoras de funcionamiento


face

openSUSE

Είναι από καιρό σαφές ότι η διανομή openSUSE υποφέρει από έλλειψη ενεργού συμμετοχής. Χωρίς την ισχυρή υποστήριξη της SUSE, που βλέπει την openSUSE ως το δοκιμαστικό έδαφος για την εταιρική διανομή SUSE Linux Enterprise, η δωρεάν openSUSE ενδέχεται να μην υπάρχει πια. Ως επί το πλείστον, η openSUSE αποτελείται από τον πυρήνα και τα πακέτα του SUSE Linux Enterprise.

Αλλά αυτή η εξάρτηση από την SUSE υπερβαίνει τα όρια, για ορισμένα μέλη της κοινότητας. Στο φετινό συνέδριο openSUSE, το openSUSE board, συζήτησε πώς να δημιουργήσει μια δομή ανεξάρτητη από την SUSE. Αυτό προηγήθηκε σε συνεδριάσεις του board (δείτε τις συζητήσεις εδώ, κυρίως 2,16,30 Μαρτίου). Επίσης αναπτύσσεται αναλυτικά σε άρθρο στο LWN.

Δείτε την συζήτηση στο συνέδριο:



Σίγουρα δεν πρόκειται να γίνει απολύτως ανεξάρτητη από την SUSE, επειδή αυτή τη στιγμή δεν είναι δυνατό. Αντίθετα, ανεξάρτητα από τα οικονομικά οφέλη της SUSE, ένα κομμάτι του board πρέπει να είναι σε θέση να δέχεται δωρεές και να χρησιμοποιούνται τα έσοδα κατάλληλα.

Τα μέλη της κοινότητας φοβούνται ότι η SUSE μπορεί να παραιτηθεί από τις προηγούμενες δεσμεύσεις της στο openSUSE, για παράδειγμα, αν η εταιρεία πωληθεί. Η προηγούμενη σχέση με την SUSE θεωρείται θετική και δεν πρέπει να τερματίζεται από την κοινότητα (δείτε την σχετική συζήτηση που έχει ξεκινήσει στις λίστες της κοινότητας). Επίσης έχει ξεκινήσει και συζήτηση στο Github σχετικά με το branding. Ο οργανισμός που θα ιδρυθεί, ενδεχομένως ως ίδρυμα βάσει του γερμανικού νόμου, θα πρέπει ωστόσο να εξασφαλίσει μια χαμηλότερη εξάρτηση από την SUSE και, κατά συνέπεια, να είναι πιο ανθεκτική στο μέλλον.

Η μορφή που θα υιοθετήσει τελικά ο οργανισμός εξακολουθεί να είναι ανοιχτή. Ωστόσο, υπάρχουν πολλοί υποστηρικτές για την ίδρυσή του και οι φωνές τους ακούγονται ελάχιστα. Ωστόσο, ο Richard Brown, πρόεδρος του board της openSUSE, λέει ότι δεν βιάζεται και μπορούν να πάρουν το χρόνο τους για να βρουν τη βέλτιστη λύση.

Ο χρόνος θα δείξει!!!

Sunday
09 June, 2019


face

FerenOS review title

I haven’t been able to do one of these in a while but it is always fun to try out other distributions and experience another example of how to answer that user experience question. As part of the BigDaddyLinux community. I have given Feren OS a spin to see how it goes for me, the biased, well entrenched openSUSE user.

Installation

The installation is done by what looks to my poorly trained eye to be the Calamares Installation Tool. This is, in my opinion, one of the most user approachable installation tools I have used. Clean, not clumsy and but yet not so basic that you can’t configure it to your liking.

Feren gives you one option when it starts. Live Media mode. You can play around with it or go right into the installation.

The installation is straight forward and works quite well. When the installation tool starts up you get an animated wheel while it “warms up” or whatever, presumably detecting bits about your system and starts you off to select your language.

Next you need to select your location and keyboard layout. This auto detected my location and keyboard layout.

For the partitions I used to erase the entire disk because for this purpose, erasing the disk works fine. Next, I entered my user information. There isn’t an option to add multiple users and I am unsure if you were to do an upgrade if you would be able to pull in previous user information or not.

The installation process provides an installation summary that includes everything you just selected, Location, Keyboard Layout and partition layout. After you select “Install” it will give you one final opportunity to bail out.

During the installation you aren’t given a slideshow of distribution propaganda, just one image to stare at. I would have liked to have had details fly by the screen during this process. Not that most people would care about that sort of information but I happen to like it. When the installation is complete, selecting “Done” will have the system reboot.

First Run

I really meant to nab the Plasma version of Feren OS but instead seem to have snagged the Cinnamon version and in keeping true to my form… I just went with it. Cinnamon is a fantastic desktop environment and since I haven’t played around with it during my last Linux Mint journey, this was a good refresher.

My overall impression of this spin of Feren OS is that it is a kind of re-imagining of the Cinnamon desktop, set aside the technical shortcomings of Cinnamon as it is based off of Gnome Shell and is encumbered with the single thread process limitation, it just looks fantastic. The Cinnamon developers have done a great job of mashing up the visual capabilities of Gnome into a more familiar desktop paradigm with which many are familiar. No one can argue that that Cinnamon (or Gnome for that matter) don’t have a


Michael Meeks: 2019-06-09 Sunday.

21:00 UTCmember

face
  • All Saints, band in the morning. Back for a fine lunch, and out for another, much less used stretch of walk along the nearby ancient, defensive Dyke.
  • Slept while H. did Organ practice, encouraging progres with the quartet. Slugged in front of a movie in the evening.

face

What is Bedrock Linux?

From their website:

Bedrock Linux is a meta Linux distribution which allows users to utilize features from other, typically mutually exclusive distributions. Essentially, users can mix-and-match components as desired. For example, one could have:

  • The bulk of the system from an old/stable distribution such as CentOS or Debian.
  • Access to cutting-edge packages from Arch Linux.
  • Access to Arch’s AUR.
  • The ability to automate compiling packages with Gentoo’s portage
  • Library compatibility with Ubuntu, such as for desktop-oriented proprietary software.
  • Library compatibility with CentOS, such as for workstation/server oriented proprietary software.

All at the same time, all working together like one, largely cohesive operating system.

So, what is this thing? Bedrock Linux is a package manager compatibility overlay. Ever wanted to use CentOS or Arch packages on your Debian system? Bedrock Linux will let you do that.

Strata

A stratos in Bedrock Linux is a package management overlay. For example, if you want to add a CentOS Strata, you run:

$ sudo brl fetch centos

The BRL app will then download yum and it’s required apps and libraries into the overlay. Once it’s done you can then yum install whatever you want.

Have multiple versions of the same package? Use:

$ strat [stratus name] [packagename]

For example with the Nano editor:

tux@debian:~$ strat arch nano -V
GNU nano, version 4.2
(C) 1999-2011, 2013-2019 Free Software Foundation, Inc.
(C) 2014-2019 the contributors to nano
Email: nano@nano-editor.org Web: https://nano-editor.org/
Compiled options: --enable-utf8
tux@debian:~$ strat debian nano -V
GNU nano, version 2.7.4
(C) 1999..2016 Free Software Foundation, Inc.
(C) 2014..2016 the contributors to nano
Email: nano@nano-editor.org Web: https://nano-editor.org/
Compiled options: --disable-libmagic --disable-wrapping-as-root --enable-utf8
tux@debian:~$ strat centos nano -V
GNU nano version 2.3.1 (compiled 04:47:52, Jun 10 2014)
(C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
2008, 2009 Free Software Foundation, Inc.
Email: nano@nano-editor.org Web: http://www.nano-editor.org/
Compiled options: --enable-color --enable-extra --enable-multibuffer --enable-nanorc --enable-utf8

There are problems

It’s not as easy as it sounds. In order to install Bedrock Linux, you must have a compatible base OS. Here is the list that’s currently on the website:

Distro Hijack-able Fetch-able Maintainer
Alpine Linux Yes Yes paradigm
Arch Linux Yes Yes paradigm
CentOS Known issues Yes paradigm
Clear Linux Mixed reports Experimental support N/A
CRUX Known issues No N/A
Debian Yes Yes paradigm
Devuan Needs investigation Yes paradigm
Elementary OS Yes, but limited testing No N/A
Exherbo Yes In development Wulf C. Krueger
Fedora Yes Yes paradigm
Gentoo Linux Yes Yes paradigm
GoboLinux Known issues No N/A
GuixSD Needs investigation No N/A
Manjaro Yes, but pamac/octopi broken No N/A
Mint Needs investigation No N/A
MX Linux Known issues No N/A
NixOS Known issues No N/A
OpenSUSE Yes Experimental support N/A
OpenWRT Needs investigation Experimental support N/A
Raspbian Yes

Saturday
08 June, 2019


Michael Meeks: 2019-06-08 Saturday.

21:00 UTCmember

face
  • Up late; did some maths with H, N. and E. variously. More work - attacked various problems with long re-build times.
  • Finally, after some weeks, got space to get around to repairing the toilet flush in the upstairs toilet. One good opportunity for Goverments would be to ban pointless, self- defeating and environmentally damaging cost-engineering. A non-servicable, polythene flush membranes is an abomination. Hours of work, waste and expense to replace a sub-penny worth of plastic. Siliconed everything in sight to get it watertight.
  • Why is it that when my daughters invite their friends over, one of them inevitably appears used to turning the bathroom tap off with the moral equivalent of a spanner - making it come loose & rotate. Mended that too.

Friday
07 June, 2019


Michael Meeks: 2019-06-07 Friday.

21:00 UTCmember

face
  • Mail chew, show & tell call with Ivan, patch review, Board call. Ferried babes around while J. took E. to her birthday 'football golf' party. Ran games for the babes in the garden: running noughts and crosses, stilt walking, and a movie. Back to work until late.

face

Le 6 juin 2019 par Douglas DeMaio (traduction par sogal)



Trois instantanés openSUSE Tumbleweed ont été publiés au cours des quatre premiers jours de juin, ce qui entraîne plusieurs mises à jour des paquets

face

openSUSE Tumbleweed es una distribución “Rolling Release” en desarrollo continuo. Aquí puedes estar al tanto de las últimas novedades.

Tumbleweed

openSUSE Tumbleweed es la versión “rolling release” o de actualización continua de la distribución de GNU/Linux openSUSE.

Hagamos un repaso a las novedades que han llegado hasta los repositorios estas semanas.

El anuncio original lo puedes leer en el blog de Dominique Leuenberger, publicado bajo licencia CC-by-sa, en este enlace:

Las ISO’s son instalables, pero si ya estás disfrutando de openSUSE Tumbleweed en tu equipo, simplemente deberás actualizarlo mediante este comando aunque desde hace poco un simple zypper dup hace ya todo el trabajo.

Durante las pasadas 2 semana, Tumbleweed ha visto un total de 9 nuevas “snapshots” publicadas y tal como esperas de esta distribución de GNU/Linux “rolling release”, han venido llenas de novedades.

Las “snapshots” que se publicaron han sido las 0524, 0525, 0527, 0529, 0601, 0603, 0604, 0605 y 0606 entre los cambios y novedades más notables se pueden destacar las siguientes:

  • Linux kernel 5.1.4, 5.1.5 y 5.1.7
  • Cambio a GCC 9 como compilador predeterminado de la distro
  • Mozilla Firefox 67.0 y Thunderbird 60.7.0
  • libopenraw 0.1.3 (atención: el archivo .pc ha sido renombrado de *-1.0.pc a *-0.1.pc)
  • Mesa 19.0.5
  • flatpak 1.4.0
  • strace 5.1
  • nodejs10.16.0

Pero muchos más cambios y actualizaciones están esperando en la recámara, así que pronto tendremos novedades como:

  • openssl 1.1.1c
  • Texlive 2019
  • KDE Plasma 5.16
  • Qt 5.13
  • LLVM 8
  • swig 4.0
  • cmake 3.14

Si quieres estar a la última con software actualizado y probado utiliza openSUSE Tumbleweed la opción rolling release de la distribución de GNU/Linux openSUSE.

Mantente actualizado y ya sabes: Have a lot of fun!!

Enlaces de interés

Geeko_ascii

——————————–


face

Dear Tumbleweed users and hackers

During the last two weeks, openSUSE Tumbleweed has seen a total of 9 snapshots being released. As you come to expect from Tumbleweed, those snapshots are filled with updates. And as usual, the snapshots are tested by openQA before they are shipped out (in the last two weeks, for example, three snapshots were tested and discarded before publishing). The snapshots that did get published were 0524, 0525, 0527, 0529, 0601, 0603, 0604, 0605 and 0606 (hot off the press), summing up to those major changes:

  • Linux kernel 5.1.4, 5.1.5 & 5.1.7
  • Switch to GCC 9 as distro default compiler (full rebuild)
  • Mozilla Firefox 67.0 & Thunderbird 60.7.0
  • libopenraw 0.1.3 (beware: .pc file was renamed from *-1.0.pc to *-0.1.pc)
  • Mesa 19.0.5
  • flatpak 1.4.0
  • strace 5.1
  • nodejs10.16.0

The distro keeps on rolling, and based on the staging projects I can predict those updates coming soon to Tumbleweed:

  • openssl 1.1.1c
  • Texlive 2019
  • KDE Plasma 5.16
  • Qt 5.13
  • LLVM 8
  • swig 4.0
  • cmake 3.14

face

There is a lot of activity in the bzip2 repository!

Perhaps the most exciting thing is that Dylan Baker made a merge request to add Meson as a build system for bzip2; this is merged now into the master branch.

The current status is this:

  • Both Meson and Autotools are supported.
  • We have CI runs for both build systems.

A plea for help: add CI runners for other platforms!

Do you use *BSD / Windows / Solaris / etc. and know how to make Gitlab's CI work for them?

The only runners we have now for bzip2 are for well-known Linux distros. I would really like to keep bzip2 working on non-Linux platforms. If you know how to make Gitlab CI runners for other systems, please send a merge request!

Why two build systems?

Mainly uncertainty on my part. I haven't used Meson extensively; people tell me that it works better than Autotools out of the box for Windows.

Bzip2 runs on all sorts of ancient systems, and I don't know whether Meson or Autotools will be a better fit for them. Time will tell. Hopefully in the future we can have only a single supported build system for bzip2.


face

Introduction

I’m LCP, or Stasiek if you can pronounce that. Just a 20 years old guy from Poland who spends way too much time in front of computers. That’s how all my potted plants end up dead.

My Journey

I’ve been using computers for as long as I can remember, playing Solitaire, The Settlers, and other simple DOS games, because that’s what my parents and grandma liked to play. I started with Win95, 98, and 2000, before learning about Linux.

My interest in design was sparked by the original iPhone icons, which I loved. In contrast with my hatred toward the Faenza icon theme, both have fairly similar style yet widely different results. That’s how I began exploring and learned from there.

Correspondingly, my Linux journey started back in 2007 when my dad showed me Ubuntu, and just like what I did with Windows 2000 before, my pastime became installing and reinstalling Linux alongside Windows in different configurations (I apparently was consumed by the concept of installation and configuration, which might explain my YaST obsession?).

Later in 2010, I had a tough time with a machine that wouldn’t take any distro with the exception of openSUSE (although it did end up with a few Linuxrc errors). Besides, I really liked its GNOME 2 config back then; it was really user friendly yet powerful. I gave KDE a shot but to this day I never really liked it.

Contributing, how it all started…

My first contribution was because of my consistent and annoying complaining to Richard Brown on Linux Gaming Discord about the sorrow state of artwork in Tumbleweed. I didn’t like anything there. I, it seemed too dark, too boring; stuff was barely visible due to contrast issues. He pointed me to contribute and make it better then, so I did. Around the same time me and some of other people from Linux Gaming Discord created the openSUSE Discord, and I reused some assets from the Discord to create the new branding.

Even though my main focus has been artwork, I also take part in some coding, translations, and obviously testing. I enjoy all of it in general. It is a great way to make computing easier and more pleasant for other less experienced users.

Actually, to me, my most valuable contribution has been encouraging people to use openSUSE and contribute to it, while doing my best to help them out when needed. Otherwise, I wouldn’t have been able to provide anything on my own because I rely on community to actively help me out with their judgment; just as I do help them out with mine.

Side projects

Outside of openSUSE I also work on Pixelfed, some Discord distros collaboration (artwork for Fedora and Gentoo discords on top of openSUSE one) and more recently been working on User Interface (UI) design for SuperTuxKart and some custom tiles for OpenSkyscraper in order to replace injecting the EXE file (but gamedev is hard


Thursday
06 June, 2019


Michael Meeks: 2019-06-06 Thursday.

21:00 UTCmember

face
  • Mail chew, build testing, code reading variously. Re-factored clipboard logic in master.
  • Read theregister while unit tests are running; Collabora has done a huge amount of work (and continues to do so) on behalf of our customers on Document Redaction:
    Paper based redaction

    There are lots of cool features from many individuals and organizations in LibreOffice 6.3 (far more than are listed there too) - but this is an interesting example of how the LibreOffice brand & marketing tends to bury sensible crediting for "the most notable" new feature, in the (otherwise beloved) el reg Then again, Dennis seems to have re-located to France as well.
  • Worked late, babes at music, scouts etc.

face

Vemos cómo escuchar en este caso la emisión en streaming en directo de la emisora Radio Nacional de España, en concreto Radio 3 o Radio clásica.

Actualizandome !!

aquí ando escuchando la radio 🙂

Soy habitual oyente de Radio 3 y de Radio clásica, ambas emisoras de Radio Nacional de España. Y ya había escrito tutoriales anteriores sobre cómo escuchar la radio, pero no quiero tener que tener abierta una pestaña de mi navegador para escucharlo en directo desde mi equipo con GNU/Linux.

Por tanto en este video tutorial veremos cómo recopilar la dirección en streaming de dicha emisión y poder escucharla con nuestro reproductor favorito. En mi caso utilizaré la línea de comandos de GNU/Linux y el reproductor VLC con una interfaz en modo texto o ncurses.

Desde Radio Nacional de España, no ponen fácil el poder hacerlo, ya que no facilitan las url de emisión en streaming y no he conseguido sacarlas con varios métodos, pero al final encontré la fórmula para hacerlo.

Tu puedes adaptar el video tutorial a las emisoras que prefieras y reproducirlos con el reproductor que más te guste. Empezamos…

Este video tutorial está en archive.org desde lo puedes descargar en formato libre .ogv

También está disponible en YouTube para quien prefiera esta plataforma. No es necesario que visitéis el canal, le deis me gusta, etc…

https://www.youtube.com/watch?v=EIvFfFjT2oU

Espero que os guste y le saquéis partido para escuchar vuestras emisoras de radio favorita desde la consola de GNU/Linux.


face

Three openSUSE Tumbleweed snapshots have been released in the first four days of June, which bring several minor package updates to the rolling release.

The 20190604 snapshot brought babl  0.1.64, which provided some code consistency, gitlab Continuous Integration (CI), autotools and meson build improvements. An accident in naming caused the 0.3.2 version of bubblewrap to become version 0.3.3. However, bubblewrap 0.3.3. did address a Common Vulnerabilities and Exposures (CVE), provided a few smaller fixes and added the JSON Application Programming Interface (API) that allows reading the inner process exit code. GNU Compiler Collection 8 had some updates that included a couple patches with one that makes builds without profiling reproducible. Generic Graphics Library gegl 0.4.16 also added gitlab CI and uses a custom allocator for tile data, which aligns data and groups allocations in blocks; this was achieved on Linux by using the GNU extension malloc_trim to permit forcing invocation of the glibc malloc/free allocators garbage collection function. Oracle’ virtualbox 6.0.8 had a minor maintenance release that fixed a crash when powering off a Virtual Machine without a graphics controller and xorg-x11-server 1.20.5 fixed some input. The snapshot is currently trending at a 96 rating, according to the snapshot reviewer.

Snapshot 20190603 updated Mesa and Mesa-drivers to version 19.0.5 and took care of some core code and drivers. NetworkManager 1.16.2 fixed some wrong permissions of the /var/lib/NetworkManager/secret_key file. Ceph’s minor version update disabled Link Time Optimisation in spec when being used. GNOME 3.32.2 had several package updates and fixes including the fix of a regression that caused the fonts category to go missing. Tumbleweed skipped over the 1.3.0 series of Flatpak directly to version 1.4.0. The major changes since 1.2.4 is the improved I/O use for system-installed applications, and the new format for pre-configured remotes. Glib2 2.60.3 updated translations and provided various fixes to small key/value support in GHashTable. Scripting language php7 7.3.6 added a missing curl_version and fixed several other bugs. The snapshot is currently trending at a 95 rating, according to the snapshot reviewer.

The snapshot that started out the month, 20190601, update the Linux Kernel to 5.1.5 that fixed a data loss bug. Flatpak-builder 1.0.7 fixed some details in how to create platform commits to fix font cache mtime issues. Among the other package updates in the snapshot were GNOME’s image viewer gthumb 3.8.0, ibus-libpinyin 1.11.1, libopenmpt 0.4.5, qalculate 3.2.0, rdesktop 1.8.6, which fixed the protocol code handling new licenses, and yast2-support 4.1.1. The snapshot is currently trending at a 90 rating, according to the snapshot reviewer.


face

I have just done a git push --force-with-lease to bzip2's master branch, which means that if you had a previous clone of this repository, you'll have to re-fetch it and rebase any changes you may have on top.

I apologize for the inconvenience!

But I have a good excuse: Julian Seward pointed me to a repository at sourceware where Mark Wielaard reconstructed a commit history for bzip2, based on the historical tarballs starting from bzip2-0.1. Bzip2 was never maintained under revision control, so the reconstructed repository should be used mostly for historical reference (go look for bzip2.exe in the initial commit!).

I have rebased all the post-1.0.6 commits on top of Mark's repository; this is what is in the master branch now.

There is a new rustify branch as well, based on master, which is where I will do the gradual port to Rust.

I foresee no other force-pushes to the master branch in the future. Apologies again if this disrupts your workflow.

Update: Someone did another reconstruction. If they weave the histories together, I'll do another force-push, the very last one, I promise. If you send merge requests, I'll rebase them myself if that happens.


face

Revamping Cloud and Monitor We’re getting closer to completing the Bootstrap migration and this time, we have revamped the Cloud and Monitor pages. This is part 7 of a series of posts about revamping the user interface of OBS. We started off with the Package pages in October 2018, moved on to the Project, User and Group pages in December 2018, continued with the Request pages in February 2019 and migrated the Configuration pages in...


Wednesday
05 June, 2019


Michael Meeks: 2019-06-05 Wednesday.

21:00 UTCmember

face
  • Practice with M, mail, patch reading, calls, booked hotel for the interesting OW2Con next week. Worked late.

face

Venez récupérer votre DVD openSUSE Leap 15.1 le 29 Juin! Attention, dans la limite du stock disponible 🙂 Pour rappel: https://nui.fr/rouen-journee-mensuelle-du-logiciel-libre-et-cybersecurite-samedi-29-juin-2019/

The post Les DVD openSUSE Leap 15.1 sont arrivés! appeared first on Network Users Institute - Intégration de Linux & Logiciels Libres à Rouen, Normandie..


face

Veamos en este artículo cómo hacer que vifm, el gestor de archivos para la consola con atajos de teclado de vim, tenga un mejor aspecto y muestre iconos.

gestor de archivo vifm

Pincha sobre la imagen para ampliar

En un artículo anterior, escribí y realicé un video tutorial sobre vifm, un gestor de archivos para la consola que se maneja con atajos de teclado iguales a los del editor de texto vim.

Si os habéis animado a probarlo, quizás habréis descubierto, que vuestro vifm es muy distinto del mío, ya que en el mío (en la captura que abre este artículo) se muestran iconos para las carpetas y archivos.

Veremos cómo hacer que vifm nos muestre unos iconos bien chulos para darle un toque extra a nuestro gestor de archivos.

Para ello, tal como explican en el foro de la aplicación, tenemos que editar y modificar el archivo de configuración vifmrc que estará en la ruta: ~/.config/vifm

En el archivo de configuración deberemos añadir iconos de fuentes como nerd-fonts, que se puedan visualizar en nuestra consola. Y deberemos utilizar la opción classify para mostrar qué tipos de archivos muestren los iconos que queremos:

" GETTING ICONS TO DISPLAY IN VIFM
" You need the next 14 lines!

" file types
set classify=' :dir:/, :exe:, :reg:, :link:'
" various file names
set classify+=' ::../::, ::*.sh::, ::*.[hc]pp::, ::*.[hc]::, ::/^copying|license$/::, ::.git/,,*.git/::, ::*.epub,,*.fb2,,*.djvu::, ::*.pdf::, ::*.htm,,*.html,,**.[sx]html,,*.xml::'
" archives
set classify+=' ::*.7z,,*.ace,,*.arj,,*.bz2,,*.cpio,,*.deb,,*.dz,,*.gz,,*.jar,,*.lzh,,*.lzma,,*.rar,,*.rpm,,*.rz,,*.tar,,*.taz,,*.tb2,,*.tbz,,*.tbz2,,*.tgz,,*.tlz,,*.trz,,*.txz,,*.tz,,*.tz2,,*.xz,,*.z,,*.zip,,*.zoo::'
" images
set classify+=' ::*.bmp,,*.gif,,*.jpeg,,*.jpg,,*.ico,,*.png,,*.ppm,,*.svg,,*.svgz,,*.tga,,*.tif,,*.tiff,,*.xbm,,*.xcf,,*.xpm,,*.xspf,,*.xwd::'
" audio
set classify+=' ::*.aac,,*.anx,,*.asf,,*.au,,*.axa,,*.flac,,*.m2a,,*.m4a,,*.mid,,*.midi,,*.mp3,,*.mpc,,*.oga,,*.ogg,,*.ogx,,*.ra,,*.ram,,*.rm,,*.spx,,*.wav,,*.wma,,*.ac3::'
" media
set classify+=' ::*.avi,,*.ts,,*.axv,,*.divx,,*.m2v,,*.m4p,,*.m4v,,.mka,,*.mkv,,*.mov,,*.mp4,,*.flv,,*.mp4v,,*.mpeg,,*.mpg,,*.nuv,,*.ogv,,*.pbm,,*.pgm,,*.qt,,*.vob,,*.wmv,,*.xvid::'
" office files
set classify+=' ::*.doc,,*.docx::, ::*.xls,,*.xls[mx]::, ::*.pptx,,*.ppt::'

En el ejemplo anterior, no se muestran los iconos, pero sí debería funcionar. El ejemplo anterior está sacado de este sitio, donde puedes echar un vistazo a otras configuraciones interesantes de vifm.

Guardamos el archivo, y salimos y volvemos a entrar en vifm.

Truco extra: dentro del propio vifm, si queremos editar directamente el archivo de configuración, simplemente tendremos que pulsar la combinación de teclas

, + c

Y nos abrirá Vim para editar el archivo, al guardar y cerrarlo, nos reiniciará directamente vifm, para que los cambios están activos inmediatamente.

Espero que os haya resultado interesante y si usáis vifm le deis un toque distintivo y elegante a ese gestor de archivos para la terminal.

Ellos también usan vifm :þ


face

Today I had a very pleasant conversation with Julian Seward, of bzip2 and Valgrind fame. Julian has kindly agreed to cede the maintainership of bzip2 to me.

Bzip2 has not had a release since 2010. In the meantime, Linux distros have accumulated a number of bug/security fixes for it. Seemingly every distributor of bzip2 patches its build system. The documentation generation step is a bit creaky. There is no source control repository, nor bug tracker. I hope to fix these things gradually.

This is the new repository for bzip2.

Ways in which you can immediately help by submitting merge requests:

  • Look at the issues; currently they are around auto-generating the version number.

  • Create a basic continuous integration pipeline that at least builds the code and runs the tests.

  • Test the autotools setup, courtesy of Stanislav Brabec, and improve it as you see fit.

The rustification will happen in a separate branch for now, at least until the Autotools setup settles down.

I hope to have a 1.0.7 release soon, but this really needs your help. Let's revive this awesome little project.


Tuesday
04 June, 2019


Michael Meeks: 2019-06-04 Tuesday.

21:00 UTCmember

face
  • Mail chew, ticket review & estimation, tech mgmt. call, built ESC proto-agenda. Sync. with Philippe. Dinner, 'cello and math's with M. put H. to bed. Read a lot of disappointing Chrome clipboard code, seems I'm far from alone in that regard. Still, a synchronous population of the complete clipboard from the get-go is also quite silly. The solution will have to be in the HTML.

face

Estou disponibilizando os pacotes da biblioteca realsense para os modelos da série D400, SR300 e T265. A biblioteca captura dados 3D, infravermelho e RGB. Mais informações sobre o projeto em : https://devmesh.intel.com/projects/intel-realsense-package-for-all-linux-distributions

No final deste post um vídeo demonstrativo da instalação e execução do exemplo no sistema OpenSuSE Leap 15.1.

A série de câmeras de profundidade Intel® RealSense™ D400 utiliza visão em estéreo para calcular a profundidade. Tanto a versão D415 como a D435 são alimentadas via USB e consistem em um par de sensores de profundidade, um sensor RGB e um projetor de infravermelho. Eles são ideais para makers e desenvolvedores adicionarem capacidade de percepção de profundidade ao desenvolvimento de protótipos.

Destaques

Ambas as câmeras de profundidade incluem:

  • Um poderoso processador de visão que utiliza processadores com tecnologia de 28 nanômetros (nm) e suporta até 5 faixas de Interface serial de câmera MIPI 2 para computação em tempo-real de imagens em profundidade e acelerar a saída.
  • Um algoritmo de profundidade estéreo novo e avançado para uma percepção de profundidade mais precisa e de alcance mais longo
  • Um conjunto de sensores de imagem que permitem capturar a disparidade entre imagens até uma resolução de 1280 x 720
  • Suporte para o novo SDK de código aberto de multiplataforma Intel® RealSense™ 2.0
  • Um processador dedicado de sinal de imagem colorida para ajustes de imagem e dados de cores de escala
  • Projetor infravermelho ativo para iluminar objetos para melhorar os dados de profundidade
 Intel RealSense D415 Intel RealSense D435
AmbienteInterno e externoInterno e externo
Tecnologia de profundidadeInfravermelho (IR) ativo estéreoIR ativo estéreo
Tecnologia de sensor de imagemObturador de rolamento: tamanho do pixel 1,4 mm x 1,4 mmObturador global: tamanho do pixel 3 mm x 3 mm
Principais produtos Intel® RealSense™ Processador de visão Intel® RealSense™ D4 Módulo Intel® RealSense™ D410 Processador de visão Intel® RealSense™ D4 Módulo Intel® RealSense™ D430
Profundidade do campo de visão (FOV)—(horizontal × vertical) para 16:9 HD63,4° x 40,4° (+/- 3°)85,2° x 58° (+/- 3°)
Resolução de saída do stream de profundidadeAté 1280 x 720Até 1280 x 720
Taxa de frames de saída do stream de profundidadeAté 90 fpsAté 90 fps
Distância de profundidade mínima (Min-Z)0,16 m0,11 m
Faixa máxima Aproximadamente 10 metros A precisão varia conforme a calibração, cena e condições de iluminação Aproximadamente 10 metros A precisão varia conforme a calibração, cena e condições de iluminação
Resolução do sensor RGB e taxa de quadros1920 x 1080 a 30 fps1920 x 1080 a 30 fps
FOV do sensor RGB (horizontal × vertical)69,4° x 42,5° (+/- 3°)69,4° x 42,5° (+/- 3

face

Bonjour à toutes et à tous,

L'assemblée générale de l'association Alionet aura lieu le mardi 18 juin à 20h. Elle se tiendra sous forme dématérialisée, via IRC, sur le canal #alionet-ag2019 (serveur Freenode).

Cette année, l'assemblée sera quelque peu différente puisqu'ouverte à tous les membres de la communauté Alionet et/ou openSUSE francophone, qu'ils soient adhérents de l'association ou non.
De la sorte nous espérons faire connaître les buts, actions et projets de l'association mais aussi recueillir les idées de tous et faire en sorte que certains d'entre vous prennent par à ces projets.

L'ordre du jour sera le suivant:


Monday
03 June, 2019


Michael Meeks: 2019-06-03 Monday.

21:00 UTCmember

face
  • Mail chew, sync with Kendy, team calls, status report. Customer call(s). Attempted to minute an All Saints PCC meeting in the evening, iteresting.

face

橋本修太です

5/24 – 26、ドイツのニュルンベルク(SUSEの本社がある街)で開催された openSUSE Conference 2019 に参加してきましたので、レポートしたいと思います。

会場 Z-Bau

ライブハウスのようですね。大きな大学が無いので、ニュルンベルクで開催する時は、こういった所なのだとか。中央奥の入り口から入るメインホールは、200〜300人くらいは入れそうでした。

向かって左側はオープンテラスになっていて、ランチが振る舞われたり、二日目の夜は15.1のリリースパーティーをしたりしました。

フレンズ

日本からは、武山さん、井川さん、私、の三名で参加させて頂きました。

しかし、現地にもう1人、日本人の方が・・・・

japanese member

そう、SUSEのカーネルメンテナーである、岩井さんにご挨拶させて頂きました。ずっとお会いしたかったので、めっちゃうれしかったです。岩井さんは、そんなはしゃぐ私に良く接してくださる、ナイスガイな方でした。

台湾からは、Joshsi、Kimlin, Iceの三名が参加されてました。去年のopenSUSE.Asia Summitで一緒だったらしいのですが、私は面識がなく・・・申し訳ない。しかし、そんな私にもとても仲良くしてくださいました。

今年のopenSUSE.Asia Summit開催国、インドネシアからはEdwinとSaputroが参加していて、Asia Summitに付いて皆と色々と議論していました。

インドからはAsia Summitのslackでお話しているAmey、それと、モーリシャスからパワフルなIshなど、各国の面白い方達と知り合うことが出来ました。

boardの方達も、良い方達ばかりで、私の挨拶に気軽に答えてくださいました。

私の英語力が拙く、あまりテクニカルな会話で盛り上がれなかったのが残念でしたが、世界中のopenSUSE熱を感じる事が出来ました。

セッション

色々と面白いセッションが続きました。そんな中からいくつかをピックアップしてみたいと思います。

YaST – Yet another SUSE Talk? by Thomas Di Giacomo

基調講演は、SUSEのCTO、Thomasの、SUSEとopenSUSEの協調関係に付いてでした。

Thinking About openSUSE HCL by Joshsi

台湾のJoshsiから、HCLの現在と提案についてのセッションでした。Joshsiはハードウェア屋らしく、自然と興味がこういう方向に向くのだとか。

”Kubernetes The Hard Way” on openSUSE Cloud environment by Masayuki Igawa

井川さんの発表は、”Hard Way”チュートリアルの紹介と、それを自分で構築したOpenStackでやってみた、という話でした。

Geeko Magazine: A Technical Magazine on openSUSE, edited on openSUSE by Fuminobu Takeyama

武山さんの発表は、Geeko Magazineについてでした。色々な国の方が興味津々に聞いていて、「翻訳用のデータは、いつ、どうやってアップするんだ?」とか、「なんでグローバルでやらないの?」といった、めっちゃポジティブな質問が飛び交いました。Geeko Magazine、世界に注目されてます。

openSUSE MicroOS in Production by Ish Sookun

モーリシャスのIshは、Kubicのプロダクションユースケースの紹介でした。タイトルはMicroOSになってますが、これは直前にRichardがKubicメインでは無く、MicroOSメインのリリースを行ったため。Ishは全面的にこの方針に賛成みたいですね。

Kubic with OpenSDS by hashimotosyuta

不肖、私も発表させて頂きました。統一的なストレージ管理プロジェクトであるOpenSDSと、Kubicからのストレージ利用の話をさせて頂きました。

しかし、ビデオがYouTubeにあがってるのですが、英語があんまりだねといった感じのコメントを頂いてしまいました。真剣に練習して、きちんと伝えたい事を伝えられるようになりたいです。

あと、ユースケースの話も聞きたい、という意見もあって、そういう話をした方がこういうカンファレンスでは良いのかも、と思いました。

Why you should choose openSUSE Kubic? by kimlin

台湾のkimlinによる、Kubicの紹介とインストール方法の案内でした。インストール方法の案内、私が前にOSCで発表したり、GeekoMagazineに書いたりした内容に似ていて、びっくりです。Kubicの入りやすさは、世界共通のようです。

openSUSE Leap 15.x Kernels: Status Quo by Takashi Iwai

岩井さんの発表は、15.1のカーネルについてでした。バックポートの8割方はドライバで、ドライバはユースケースが限られるのでユーザーによるテストもあまり進んでいない現実があるのだとか。カーネルメンテナの苦労の片鱗を窺い知れるお話でした。

印象的だったのは、openSUSEとSLESとで、カーネルのソースは一緒だよ、バイナリは違うけどね、という表現でした。

まだまだありましたが・・・・

以上、かいつまんで紹介させて頂きました。openSUSE Conferenec 2019のセッションは、YouTubeにあがってますので、是非みなさんも興味のあるものを聞いてみて下さい。

観光

ドイツについた日に、フランクフルトを少し観光し、帰る日に、ニュルンベルクを少し観光させて頂きました。あと、カンファレンスの終了後も、時間があればニュルンベルクの名所を回らせて頂きました。

Nuremberg

SUSE

SUSE本社にもお邪魔させて頂きました(外側からだけですが・・・)

ニュルンベルクはパンもソーセージも美味しく、街並みもきれいでとても印象に残る街でした。

来年はどこ開催かは決まってませんが、英語を練習して、また参加したいと思います。

その前に、秋のopenSUSE.Asia Summitですね。特にアジアの方達は、このイベントでお会いしましょう。

openSUSE、参加された皆さん、愉しいイベントをありがとう!

<- Current blog entries