From: lane-brain <lane-brain@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP]: GNOME 43
Date: Tue, 10 Jan 2023 18:57:38 +0100 [thread overview]
Message-ID: <20230110175738.FFl9Ip2hAARBfsNSklZo41IZ9cDZViOJFhWTdIDYODg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39513@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]
New comment by lane-brain on void-packages repository
https://github.com/void-linux/void-packages/pull/39513#issuecomment-1377642623
Comment:
I think this update has plunged my system into some shlib hell, just wanted to note it for anyone else having the same issue
```
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/nonfree/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/nonfree/x86_64-repodata' ...
gnome-calendar-42.2_2: broken, unresolvable shlib `libecal-2.0.so.1'
gnome-shell-42.4_1: broken, unresolvable shlib `libecal-2.0.so.1'
gnome-calendar-42.2_2: broken, unresolvable shlib `libedataserver-1.2.so.26'
gnome-shell-42.4_1: broken, unresolvable shlib `libedataserver-1.2.so.26'
gnome-control-center-42.3_1: broken, unresolvable shlib `libgnome-bg-4.so.1'
xdg-desktop-portal-gnome-43.1_1: broken, unresolvable shlib `libgnome-bg-4.so.1'
gnome-session-42.0_2: broken, unresolvable shlib `libgnome-desktop-3.so.19'
gnome-settings-daemon-42.2_2: broken, unresolvable shlib `libgnome-desktop-3.so.19'
gnome-shell-42.4_1: broken, unresolvable shlib `libgnome-desktop-3.so.19'
mutter-42.4_1: broken, unresolvable shlib `libgnome-desktop-3.so.19'
gnome-clocks-42.0_2: broken, unresolvable shlib `libgnome-desktop-4.so.1'
gnome-control-center-42.3_1: broken, unresolvable shlib `libgnome-desktop-4.so.1'
gnome-initial-setup-42.2_2: broken, unresolvable shlib `libgnome-desktop-4.so.1'
xdg-desktop-portal-gnome-43.1_1: broken, unresolvable shlib `libgnome-desktop-4.so.1'
gnome-control-center-42.3_1: broken, unresolvable shlib `libgnome-rr-4.so.1'
```
next prev parent reply other threads:[~2023-01-10 17:57 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 21:39 [PR PATCH] " paper42
2022-09-28 22:10 ` [PR PATCH] [Updated] " paper42
2022-09-28 22:47 ` paper42
2022-09-28 22:57 ` [PR REVIEW] " oreo639
2022-09-28 22:57 ` oreo639
2022-09-28 23:15 ` paper42
2022-09-28 23:29 ` oreo639
2022-09-29 1:41 ` oreo639
2022-09-29 15:48 ` [PR PATCH] [Updated] " paper42
2022-09-29 15:48 ` [PR REVIEW] " paper42
2022-09-29 15:48 ` paper42
2022-09-30 20:17 ` [PR PATCH] [Updated] " paper42
2022-10-12 10:04 ` paper42
2022-10-26 19:06 ` paper42
2022-11-03 21:38 ` [PR REVIEW] " oreo639
2022-11-03 21:38 ` oreo639
2022-11-22 19:17 ` oreo639
2022-11-22 19:19 ` oreo639
2022-11-22 21:11 ` [PR PATCH] [Updated] " paper42
2022-11-22 21:54 ` paper42
2022-11-23 1:38 ` [PR REVIEW] " oreo639
2022-11-23 1:39 ` oreo639
2022-11-23 1:59 ` oreo639
2022-11-23 2:00 ` oreo639
2022-11-23 2:01 ` oreo639
2022-11-23 6:04 ` oreo639
2022-11-23 6:04 ` oreo639
2022-11-23 17:39 ` oreo639
2022-11-23 20:08 ` [PR PATCH] [Updated] " paper42
2022-12-02 7:27 ` oreo639
2022-12-02 7:27 ` oreo639
2022-12-09 17:32 ` [PR PATCH] [Updated] " paper42
2022-12-11 20:53 ` paper42
2022-12-11 21:00 ` paper42
2022-12-11 21:53 ` paper42
2022-12-13 20:00 ` paper42
2022-12-15 16:39 ` paper42
2022-12-15 17:09 ` paper42
2022-12-15 19:48 ` paper42
2022-12-15 20:13 ` paper42
2022-12-15 20:54 ` paper42
2023-01-01 20:26 ` paper42
2023-01-01 21:32 ` paper42
2023-01-01 22:29 ` paper42
2023-01-01 23:17 ` [PR REVIEW] " oreo639
2023-01-02 8:03 ` [PR PATCH] [Updated] " paper42
2023-01-02 8:07 ` paper42
2023-01-02 10:51 ` [PR REVIEW] " paper42
2023-01-02 10:52 ` paper42
2023-01-02 10:52 ` [PR PATCH] [Closed]: " paper42
2023-01-02 14:03 ` motorto
2023-01-03 21:46 ` thegarlynch
2023-01-04 14:51 ` paper42
2023-01-09 4:46 ` thegarlynch
2023-01-09 4:46 ` thegarlynch
2023-01-09 4:47 ` thegarlynch
2023-01-10 17:57 ` lane-brain [this message]
2023-01-10 18:00 ` JamiKettunen
2023-01-10 18:09 ` lane-brain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230110175738.FFl9Ip2hAARBfsNSklZo41IZ9cDZViOJFhWTdIDYODg@z \
--to=lane-brain@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).