[SOLVED] Today's -current icu4c upgrade broke ktown's sddm

dugan · 12-06-2017, 09:13 PM

Just a heads up that if you're running ktown on -current, you should hold off upgrading to the new icu4c 60 package until ktown's also been updated.

ktown was built against icu4c 56, and I can confirm that (at least) sddm expects libicui18n.so.56 (which is now replaced by libicui18n.so.60) to be present, and won't launch without it.

RadicalDreamer · 12-06-2017, 09:31 PM

Thank you for sharing

I've been wondering which packages to avoid upgrading in Current until a new build of Plasma 5 is available.

gmgf · 12-07-2017, 02:58 AM

I do not know what Eric is going to do, but it will take, maybe a little patience, because,

framework-5.41 ready will be ready Sat December 9th, 2017

https://community.kde.org/Schedules/Frameworks

and applications-17.12 will be ready Thursday, December 14 2017

https://community.kde.org/Schedules/...lease_Schedule

Alien Bob · 12-07-2017, 03:55 AM

I will of course not wait that long with a fix. A couple of packages need to be rebuilt and I am working on that. Qt5 being the most time-consuming of them.

gmgf · 12-07-2017, 04:05 AM

A good men, this Eric

Darth Vader · 12-07-2017, 04:50 AM

Talking about luck...

So, the Plasma5 starts crashing in the day I decided to give it a try. Interesting, right?

Darth Vader · 12-07-2017, 04:53 AM

Quote:

Originally Posted by gmgf

A good men, this Eric

If you found a way for us to clone Eric, that would be a brilliant Plan To Take Over The World.

Imagine squadrons of Erics building many, many, many packages. Ubuntu would have to run for its money...

Unless then, sadly for us, Eric is just one man.

gmgf · 12-07-2017, 04:55 AM

Quote:

Originally Posted by Darth Vader

Talking about luck...

So, the Plasma5 starts crashing in the day I decided to give it a try. Interesting, right?

You're not invited here, and, you know why

just a joke

Darth Vader · 12-07-2017, 04:57 AM

Quote:

Originally Posted by gmgf

just a joke

And so I take your words.

gmgf · 12-07-2017, 05:04 AM

Eric, are you a cyborg ?

RadicalDreamer · 12-07-2017, 05:24 AM

We probably need to keep a backup of packages from a previous update so we can revert back to them if something in a new update to Current breaks something in Plasma 5. What would be an easy and elegant way to do that?

Toutatis · 12-07-2017, 05:28 AM

@RadicalDreamer

I have 3 computers with slackware64-current. I update them one after the other. If anything goes wrong with the first I can still come back using the others.

Alien Bob · 12-07-2017, 05:36 AM

Quote:

Originally Posted by Darth Vader

Talking about luck...

So, the Plasma5 starts crashing in the day I decided to give it a try. Interesting, right?

Yeah that's bad luck. Just wait a day (or two if you need 32bit packages) because qt5 and qt5-webkit need time to compile...

paolo27957 · 12-07-2017, 05:54 AM

On my 32bit PC the new package icu4c 60.1 crashing alien's libreoffice 5.4.3.
Going back to the previous version icu4c 56.1 is worse. Also crash Httpd and NetworkManager.
I solved by removing the alien's libreoffice and installing the SBo one.

Quote:

Originally Posted by RadicalDreamer

We probably need to keep a backup of packages from a previous update so we can revert back to them if something in a new update to Current breaks something in Plasma 5. What would be an easy and elegant way to do that?

I agree on the need.

gmgf · 12-07-2017, 06:00 AM

Eric, I just recompiled qt5-webkit with your SlackBuild, don't compil here with your SlackBuild, if it's installed