From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Update fails after boost 1.80
Date: Thu, 01 Sep 2022 19:09:46 +0200 [thread overview]
Message-ID: <20220901170946.ufM7wmVSrdkF1xGLrn0I91wZgATc8SNrASTb1Tfm4U4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39029@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
Closed issue by 7r3nzy on void-packages repository
https://github.com/void-linux/void-packages/issues/39029
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.19_1 x86_64 AuthenticAMD uptodate rrrmdFFFFFFFFFF
### Package(s) Affected
libcmis-0.5.2_4 liborcus-0.17.2_1 libreoffice-common-7.3.3.2_3 inkscape-1.1.1_4 libixion-0.17.0_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
`xbps-install -Suv` to work without any errors
### Actual behaviour
`xbps-install -Suv`
```
libcmis-0.5.2_4: broken, unresolvable shlib `libboost_date_time.so.1.72.0'
liborcus-0.17.2_1: broken, unresolvable shlib `libboost_date_time.so.1.72.0'
libreoffice-common-7.3.3.2_3: broken, unresolvable shlib `libboost_date_time.so.1.72.0'
inkscape-1.1.1_4: broken, unresolvable shlib `libboost_filesystem.so.1.72.0'
libixion-0.17.0_1: broken, unresolvable shlib `libboost_filesystem.so.1.72.0'
```
### Steps to reproduce
`xbps-install -Suv`
must have the following packages already installed:
```
libcmis-0.5.2_4
liborcus-0.17.2_1
libreoffice-common-7.3.3.2_3
inkscape-1.1.1_4
libixion-0.17.0_1
prev parent reply other threads:[~2022-09-01 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 15:14 [ISSUE] " 7r3nzy
2022-09-01 16:22 ` oreo639
2022-09-01 17:07 ` 7r3nzy
2022-09-01 17:09 ` Duncaen [this message]
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=20220901170946.ufM7wmVSrdkF1xGLrn0I91wZgATc8SNrASTb1Tfm4U4@z \
--to=duncaen@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).