Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] libicui18n.so.73 (Read 11710 times) previous topic - next topic
0 Members and 5 Guests are viewing this topic.

Re: libicui18n.so.73

Reply #15 –
For me the icu update was held up by a few packages (atm it's ncmcpp) so glad i avoided the drama :)

@Andy No one forces you to update constantly, yes even on a rolling distro, I am repeating myself from a previous thread but you need to "feel" the update and postpone it until more stuff gathers up. Of course drivers, kernel and stuff are an exception.

@suren The solution is patience :) No i am not sarcastic.

Re: libicui18n.so.73

Reply #16 –
Hi Hitman,

I don't update constantly, I have octopi-notifier running
Screenshot at 2023-06-29 13-04-35.png
 with set to 'check once a day'.
Artix has to find a way to cluster updates in a way together that prevent this update drama.

Re: libicui18n.so.73

Reply #17 –
Allow me a rant now, all team members work in their precious free time on artix.
It is rather annoying, some people take everything for granted,  while they would never ever consider to work on anything without payment.

Re: libicui18n.so.73

Reply #18 –
It seems to me that most of this "drama" comes from (new) users.

I never understood updating an Arch/Artix system automatically periodically. It causes problems. I've witnessed it cause problems for some 12 years now. I'd never update even once without checking what's happening. Whenever I've had problems myself, it has turned out to be careless negligence in updating, perhaps combined with bad luck in timing. Automatic periodic updating is the ultimate careless negligence, by choice, repeated forever.

But if checking what's happening in an update is too much for you, I totally get that; go and try another distro, then.

Maintaining a distro is not an easy task. These people do it for free. You might think you are giving "justified criticism", but it is not very constructive (I don't see concrete, technical suggestions, let alone offers to help), and at least to me it comes off as rudely complaining when things turn out to be not exactly the way you mistakenly expected.

Re: libicui18n.so.73

Reply #19 –
Quote from: lotuskip – on
... and at least to me it comes off as rudely complaining when things turn out to be not exactly the way you mistakenly expected.


Not only to you. I suspect the rudeness stems from the favorite game not starting or so.

A consequence might be, we gonna remove arch support entirely, it has no benefit at all keeping it.

Re: libicui18n.so.73

Reply #20 –
Quote from: artoo – on
A consequence might be, we gonna remove arch support entirely, it has no benefit at all keeping it.
I can't say I'd blame you.
Thanks for the work you all do.

We unfortunately live in a very 'entitled' society.

Re: libicui18n.so.73

Reply #21 –
Quote from: Andy – on
Hi Hitman,

I don't update constantly, I have octopi-notifier running with set to 'check once a day'.
Okay, understood, the little red icon will bug you once a day. What happened now is that you probably don't have all those packages that would've held up the update, and thought something is wrong because it went through early. No one's to blame here.
Quote from: Andy – on
Artix has to find a way to cluster updates in a way together that prevent this update drama.
Check above, that's why rolling distros are for more advanced use generally. Manjaro tries to stop the rolling with pretty bad consequences. Alpine holds updates sometimes but it's basically for embedded systems, mainly due to lack of glibc.
Artix has went through some massive repo changes recently so until things settle down expect some of this stuff.
Quote from: gripped – on
We unfortunately live in a very 'entitled' society.
The direct cause of modern social media of the past 10 years.

Re: libicui18n.so.73

Reply #22 –
We don't have magic powers that can predict when Arch decides to move major library updates. So if you use a mix of Arch + Artix repos, it is possible that Arch will move a package that depends on a major library before we move ours. That's all this is and it's just something you should know how to deal with as a user (deal with in this case usually just means "wait a couple of hours"). The best solution is to just add more of this stuff into Artix repos, but there are some packages out there that are monsters to build.

Re: libicui18n.so.73

Reply #23 –
Quote from: Dudemanguy – on
We don't have magic powers that can predict when Arch decides to move major library updates. So if you use a mix of Arch + Artix repos, it is possible that Arch will move a package that depends on a major library before we move ours. That's all this is and it's just something you should know how to deal with as a user (deal with in this case usually just means "wait a couple of hours"). The best solution is to just add more of this stuff into Artix repos, but there are some packages out there that are monsters to build.

I totally agree, and personally I am very appreciative for all the work the devs do to provide such a wonderful OS, and also all the support that is in these forums from both the devs and some very knowledgable users who are extremely patient in the face of some (few) very demanding users.

If people want a stable distro without any update problems, why on earth are they using a rolling distro?

Re: libicui18n.so.73

Reply #25 –
Quote from: Andy – on
Do I get banned for justified criticism ?

I would remove you from the forum immediately.
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: [SOLVED] libicui18n.so.73

Reply #26 –
I'm getting some libicuuc.so.72 errors after updating on gremlins earlier today, for example the window decoration in Mate looks odd and mate-appearance -properties won't start, I haven't determined exactly why yet. But on stable repos it seems OK so far, if it was helpful to add.
Edit: I fixed it simply by running -Syuu (allows downgrades if version in repo is lower) which did this on a system which was fully updated according to -Syu:
Code: [Select]
downgraded libxml2 (2.11.0-1 -> 2.10.4-6)
downgraded python2-psutil (5.9.4-1 -> 5.9.0-1)
installed python2-appdirs (1.4.4-6)
installed python2-pyparsing (2.4.7-6)
installed python2-six (1.16.0-5)
installed python2-packaging (20.9-7)
installed python2-ordered-set (3.1.1-4)
downgraded python2-setuptools (2:44.1.1-2 -> 2:44.1.1-1)
Probably it was libxml2, as that came up as missing the libicuuc.so.72 according to check-link-consistency. For some reason a newer version had appeared in April but then disappeared again.
 

Re: [SOLVED] libicui18n.so.73

Reply #27 –
Quote from: rayburn – on
If people want a stable distro without any update problems, why on earth are they using a rolling distro?
Maybe that's due to that that to find a good fixed distro with all needed packages and without systemd plague is pretty challenging if possible at all?

Re: [SOLVED] libicui18n.so.73

Reply #28 –
You're pretty much right, there is Devuan but it's a complete mess, no software, still loads sysvinit first, takes a lot of work to be properly up to speed.
I mean you can make it work, but it's further expert level IMO than pampering a rolling distro sometimes.

Re: [SOLVED] libicui18n.so.73

Reply #29 –
Quote from: melleus – on
Quote from: rayburn – on
If people want a stable distro without any update problems, why on earth are they using a rolling distro?
Maybe that's due to that that to find a good fixed distro with all needed packages and without systemd plague is pretty challenging if possible at all?
The best "rolling release" without systemd : Artix Linux.
I've been using it on different machines since 2019.

The best "fixed release" on which systemd is not enabled by default : MX Linux.
I install it for people who don't want/know how to "put their fingers in the engine".