You are not logged in.

#1 2018-11-19 23:03:09

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Broken upgrades... libidn, icu, any ETA?

I see a note on the rss feed that icu is breaking upgrades. And it appears the problem with libidn breaking certain packages is also still unresolved.
It's been over 10 days, and I'm wondering what the prognosis is?
Is it still true that upgrades are unsafe? Any estimate of when it will be possible again?

Thanks

Last edited by rogerthat (2018-11-21 14:47:59)

Offline

#2 2018-11-20 07:02:16

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 347

Re: Broken upgrades... libidn, icu, any ETA?

The title is somewhat misleading - icu is not broken, but rather too new for the mentioned packages. Honestly, I fear, we won't be building those packages there anytime soon / anytime at all - they simply come with too many/persistent problems.
Regarding libidn: We're currently experiencing trouble with our mysql database (tyzoid seems to have some server trouble - packages.archlinux32.org is down - and there is some internal transition in progress which makes accessing certain information in the database quite unreliable). It looks like rhythmbox was last built on 2018-08-31 (before libidn I assume), so I rescheduled it ... let's see if we get that building now.

Sry for the trouble, but we're outnumbered here.

regards,
deep42thought

Offline

#3 2018-11-21 14:51:26

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: Broken upgrades... libidn, icu, any ETA?

OK. Thanks. I've adjusted my post to be more accurate.

I understand it's a challenge, and I'm afraid I don't know enough about how builds work to be helpful. But just wondering how to monitor the situation as an end user and know when and what is safe to upgrade? The upgrade warning on the RSS news feed is about two weeks old now.

For the moment, can I safely run updrades with "ignore" on for libidn and icu?

Offline

#4 2018-11-21 23:01:31

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: Broken upgrades... libidn, icu, any ETA?

The icu post has been continually updated though, and as time of writing only four out of 15 or so are listed as not fixed (if your rss reader hasn't flagged up the updated to the post - maybe you need a better rss reader?), one or two of which were already not being upgraded as a matter of course.  I'm less familiar with the libidn breaks, all I can really say is thus far as a user of the testing repos I've not had anything I use regularly break.

If icu is still a problem for you, you may need to look for alternative soltuions as I have, but libidn thus far hasn't touched me; is that more of a qt thing?

Edit: Swapped the intention of my first sentence.  Almost 25% remain to be fixed, if they ever cane be, rather than only 25% being fixed.

Offline

#5 2018-11-22 03:24:35

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: Broken upgrades... libidn, icu, any ETA?

Well, "pacman -Syu --ignore libidn,icu" broke a ton of things. Luckily downgrade worked to roll it back.

Offline

#6 2018-11-22 08:23:20

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 347

Re: Broken upgrades... libidn, icu, any ETA?

rogerthat: As you figured out yourself, updating with "--ignore libidn,icu" is a bad idea - most packages use the new icu and libidn.
I recommend to update your system normally. In case, you need some of the broken packages (e.g. firefox), install abaumann's icu62 package - but keep in mind that you are then running a quite old build of a browser which does have security implications (but you are running that old browser version right now anyway).

Offline

#7 2018-11-22 21:44:23

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: Broken upgrades... libidn, icu, any ETA?

Ah ok. Thanks, but I don't understand how that works. If these packages have certain version(s) of icu as a dependency how come pacman doesn't resolve that and not upgrade them also when I block the icu upgrade?

Offline

#8 2018-11-22 22:09:38

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: Broken upgrades... libidn, icu, any ETA?

Because pacman doesn't support partial upgrades I guess.  If you want that, you will probably need to identify what depends on the packages you want to ignore and also ignore those, which could be automated, but is not something the pacman authors want to go out of their way to support.

Offline

#9 2018-11-22 22:36:08

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 347

Re: Broken upgrades... libidn, icu, any ETA?

pacman would support partial upgrades if archlinux did, but they don't.
one would need to enter all linked libraries (including their version!) as pacman dependencies.
Actually, that is something we do programatically (check "link" dependencies in our package database, but even our system is not perfect - otherwise those problems would not happen at all

Offline

#10 2019-01-18 14:52:54

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: Broken upgrades... libidn, icu, any ETA?

Checking back in after a long time away... Wondering the state of this, if it's safe to run an update? Or will there still be these broken dependencies?

Thanks!

Offline

#11 2019-01-18 14:56:34

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 347

Re: Broken upgrades... libidn, icu, any ETA?

these issues should be resolved.

Offline

#12 2019-01-18 18:56:14

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: Broken upgrades... libidn, icu, any ETA?

Yes, although if you run lightdm to login, I'd advise holding off updating that for now.

Offline

Board footer

Powered by FluxBB