From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: jamulus: update to 3.8.2
Date: Sun, 27 Feb 2022 19:58:23 +0100 [thread overview]
Message-ID: <20220227185823.acaf0RDZDDIXkhkxHcqqsm6sqhroZndzLO0L-ZXE5lE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35867@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
There's a merged pull request on the void-packages repository
jamulus: update to 3.8.2
https://github.com/void-linux/void-packages/pull/35867
Description:
#### Testing the changes
- I tested the changes in this PR: **NO**
#### Local build testing
```
libxml2-2.9.10_5: broken, unresolvable shlib `libicudata.so.69'
libxml2-2.9.10_5: broken, unresolvable shlib `libicui18n.so.69'
libharfbuzz-2.9.1_1: broken, unresolvable shlib `libicuuc.so.69'
libxml2-2.9.10_5: broken, unresolvable shlib `libicuuc.so.69'
Transaction aborted due to unresolved shlibs.
```
Build currently failing due to unresolved shlibs. According to the [docs](https://docs.voidlinux.org/xbps/troubleshooting/common-issues.html):
> If you get an error message saying:
>
> `Transaction aborted due to unresolved shlibs`
>
> the repositories are in the staging state, which can happen due to large builds. The solution is to wait for the builds to finish. You can view the builds' progress in the [Buildbot's Waterfall Display](https://build.voidlinux.org/waterfall).
I'll skip CI and tag WIP until it's resolved. I figured I would make the PR just in case anyone was curious about the status of updating to 3.8.2.
prev parent reply other threads:[~2022-02-27 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 15:16 [PR PATCH] [WIP] " kawaiiamber
2022-02-26 15:26 ` [PR PATCH] [Updated] " kawaiiamber
2022-02-27 10:30 ` paper42
2022-02-27 15:23 ` kawaiiamber
2022-02-27 15:23 ` [PR PATCH] [Updated] " kawaiiamber
2022-02-27 15:27 ` kawaiiamber
2022-02-27 17:41 ` kawaiiamber
2022-02-27 18:57 ` paper42
2022-02-27 18:58 ` paper42 [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=20220227185823.acaf0RDZDDIXkhkxHcqqsm6sqhroZndzLO0L-ZXE5lE@z \
--to=paper42@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).