From: kotoko <kotoko@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] xbps-remove -oO gives: Broken, unresolvable shlib `libpodofo.so.2'
Date: Tue, 26 Dec 2023 13:01:00 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47907@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
New issue by kotoko on void-packages repository
https://github.com/void-linux/void-packages/issues/47907
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.13_1 x86_64 GenuineIntel uptodate FFF
### Package(s) Affected
calibre-7.1.0_1 krename-5.0.2_3 scribus-1.5.8_13 libpodofo-0.10.3_1 libpodofo0.9.7-0.9.7_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Here is the official instruction saying that I should just wait.
https://docs.voidlinux.org/xbps/troubleshooting/common-issues.html#shlib-errors
### Expected behaviour
I can update system and remove outdated packages without errros.
### Actual behaviour
For the last 3 weeks I am getting this error. I think it is long enough that „just waiting” does not fix the issue.
Command `/usr/bin/xbps-remove --yes -Oo` produces error:
```
calibre-7.1.0_1: broken, unresolvable shlib `libpodofo.so.2'
krename-5.0.2_3: broken, unresolvable shlib `libpodofo.so.2'
scribus-1.5.8_13: broken, unresolvable shlib `libpodofo.so.2'
Transaction aborted due to unresolved shlibs.
```
### Steps to reproduce
I run these commands to update system:
```
/usr/bin/xbps-install --yes -Su xbps
/usr/bin/xbps-install --yes -Su
/usr/bin/xbps-install --yes -Su
/usr/bin/vkpurge rm all
/usr/bin/xbps-remove --yes -Oo
```
I am using mirrors.dotsrc.org mirror:
```
repository=https://mirrors.dotsrc.org/voidlinux/current
repository=https://mirrors.dotsrc.org/voidlinux/current/nonfree
```
next reply other threads:[~2023-12-26 12:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 12:01 kotoko [this message]
2023-12-26 17:56 ` Anachron
2023-12-26 19:06 ` kotoko
2023-12-26 19:09 ` kotoko
2023-12-26 22:10 ` Duncaen
2023-12-27 1:57 ` [ISSUE] [CLOSED] " sgn
2023-12-27 10:38 ` kotoko
2023-12-27 10:40 ` kotoko
2023-12-27 10:41 ` kotoko
2023-12-27 10:43 ` kotoko
2023-12-27 10:46 ` kotoko
2023-12-27 11:02 ` kotoko
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47907@inbox.vuxu.org \
--to=kotoko@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).