Looks like this was dropped again in R3571:dad3cd0991cd13bab13f535fd17ffcef7fd3f0e8 ? Did it break something?

Did you already take a look at the pkgconfig file of libluv?

Cheers for the investigation @DonHugo =)

Control Panel Color settings/information displays what I would expect to see. Not sure what to test there.

GNOME Logs 3.34.0 (which apparently isn't installed by default in the desktop.gnome component?) works fine.

• samba: fix missing '|' in build step declaration

• samba: Fix indendation in package.yml

Don't know how relevant this is, but just a quick note that I've also seen the "unresponsive GNOME Shell overlay" (can't click or exit) after enabling the Desktop Icons extension NG (DING) from rastersoft.

Just tested Totem (works), Disks (works) and Gaupol (works).

Successful upgrade report (the present system was originally a Budgie install, but was converted to GNOME via 'eopkg it -c desktop.gnome' before the 3.34 upgrade):

"something something something Dark Side. Something something something Complete"
(source)

Resolved by R3030:db3dec47b2d5830897182eedcb5cb36ae310ff05

In D6863#108961, @DataDrake wrote:

In D6863#108951, @ermo wrote:

@joebonrichie
gcc-9.2 is apparently just around the corner -- it might make more sense to go with that, assuming that it's mostly a bugfix release plus the SuSE-sourced zen2 optimisations from gcc-10?

If all goes well, I'd like to release 9.2 on Monday, August 12th. (source)

Not that I have a strong preference for which version we use, but the Zen2 optimizations are useless to us since we don't build binaries specifically for AMD.

gcc-9.2 is apparently just around the corner -- it might make more sense to go with that, assuming that it's mostly a bugfix release plus the SuSE-sourced zen2 optimisations from gcc-10?

I just noticed this: https://flathub.org/apps/details/org.blender.Blender

Also note that Josh is currently swamped with IRL stuff, so don't expect him to land the OpenSSL and systemd stuff right away.

In T6817#155282, @JoshStrobl wrote:

If it needs the latest version of python 3, then you're not going to get it ASAP. Upgrading to the latest release of Python (2 and 3) will require us to update OpenSSL. Updating OpenSSL involves also keeping the existing version around, both in the same upgrade (so shipping both at the same time, in the same package, to ensure no libs are removed and ABIs pulled out from underneath python's feet). This has to be done to ensure the package manager continues to function, so we can perform the necessary package transactions to get the dependencies to build (and even rebuild) Python 2/3 in the first place. And all of that will be done at the same time I'm updating systemd.
So, don't expect it in the immediate future.

Did the patch help? I can test this on MATE -unstable once you feel it's ready for testing.

All that out of the way, where/how may I submit the aforementioned PR?

Is this still an issue?

Cannot reproduce with kodi-18.3 and the newest version of kodi-platform (R1573:b0a10efe259ed4c9fd1d593016bdce0c34c4512c).

Latest supported version of pvr-iptvsimple is now built as part of our "batteries included" version of Kodi.

Any comments re. the test of the recently landed pvr-iptvsimple-3.5.8?

Kodi-18.3 was landed in unstable last night (R1571:115a53714a61).

Good news! Kodi-18.3 now correctly builds and includes the pvr-iptvsimple-3.5.8 plugin when I do a complete build of kodi. \o/

So, just so I'm sure we're on the same page:

I don’t think we should update to 4.0 or later because they seem to be for the next Kodi update possibly named Matrix? I think it would be wiser to stick with the 3.x.x series that explicitly states that it’s for Leia. Will be updating my revision to 3.5.8!