Github messages for voidlinux
 help / color / mirror / Atom feed
From: Gigahawk <Gigahawk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Manual.md: Document unresolvable shlib issue
Date: Wed, 19 Jan 2022 01:35:50 +0100	[thread overview]
Message-ID: <20220119003550.MVtUGk705mQMC23QFdcXRTGYt5ykU7EiLG1yJ0fnXb0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35107@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

There is an updated pull request by Gigahawk against master on the void-packages repository

https://github.com/Gigahawk/void-packages unresolvable_shlib
https://github.com/void-linux/void-packages/pull/35107

Manual.md: Document unresolvable shlib issue
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!-- 
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/35107.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-unresolvable_shlib-35107.patch --]
[-- Type: text/x-diff, Size: 2598 bytes --]

From 97ee8e9b9dd799e6fec3176349b050a72629486c Mon Sep 17 00:00:00 2001
From: Jasper Chan <jasperchan515@gmail.com>
Date: Tue, 18 Jan 2022 03:21:01 -0800
Subject: [PATCH 1/2] Manual.md: Document unresolvable shlib issue

---
 Manual.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/Manual.md b/Manual.md
index da72bd97128d..32dfbe6397b9 100644
--- a/Manual.md
+++ b/Manual.md
@@ -8,6 +8,8 @@ packages for XBPS, the `Void Linux` native packaging system.
 * [Introduction](#Introduction)
 	* [Quality Requirements](#quality_requirements)
 	* [Package build phases](#buildphase)
+	* [Common Build Problems](#commonbuildproblems)
+		* [Unresolvable shlib](#unresolvableshlib)
 	* [Package naming conventions](#namingconventions)
 		* [Libraries](#libs)
 		* [Language Modules](#language_modules)
@@ -192,6 +194,22 @@ via `make install` or any other compatible method.
 successfully, the phase will be skipped later (unless its work directory
 `${wrksrc}` is removed with `xbps-src clean`).
 
+<a id="commonbuildproblems"></a>
+### Common Build Problems
+
+<a id="unresolvableshlib"></a>
+#### Unresolvable shlib
+
+If you get an error like the following while building:
+```
+enchant2-2.2.15_4: broken, unresolvable shlib `libicudata.so.69'
+```
+
+It's likely that the Void Buildbot has recently rebuilt a library and has not rebuilt some packages that depend on it.
+You can check https://build.voidlinux.org/ for the current status of the builders.
+
+Once the dependent packages have finished building on Buildbot your build should succeed.
+
 <a id="namingconventions"></a>
 ### Package naming conventions
 

From 277081aa4986cb53658754299011ca90029647d2 Mon Sep 17 00:00:00 2001
From: Gigahawk <jasperchan515@gmail.com>
Date: Tue, 18 Jan 2022 16:35:47 -0800
Subject: [PATCH 2/2] Update Manual.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-authored-by: Érico Nogueira Rolim <34201958+ericonr@users.noreply.github.com>
---
 Manual.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Manual.md b/Manual.md
index 32dfbe6397b9..1e8bcb7497ee 100644
--- a/Manual.md
+++ b/Manual.md
@@ -8,7 +8,7 @@ packages for XBPS, the `Void Linux` native packaging system.
 * [Introduction](#Introduction)
 	* [Quality Requirements](#quality_requirements)
 	* [Package build phases](#buildphase)
-	* [Common Build Problems](#commonbuildproblems)
+	* [Common Build Problems](#common-build-problems)
 		* [Unresolvable shlib](#unresolvableshlib)
 	* [Package naming conventions](#namingconventions)
 		* [Libraries](#libs)

  parent reply	other threads:[~2022-01-19  0:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 11:21 [PR PATCH] " Gigahawk
2022-01-18 20:13 ` [PR REVIEW] " ericonr
2022-01-18 20:13 ` ericonr
2022-01-18 20:13 ` ericonr
2022-01-19  0:35 ` Gigahawk [this message]
2022-01-19  0:37 ` [PR PATCH] [Updated] " Gigahawk
2022-01-19  0:41 ` [PR REVIEW] " Gigahawk
2022-01-19  0:47 ` [PR PATCH] [Updated] " Gigahawk
2022-01-19  1:30 ` [PR REVIEW] Documentation: " ericonr
2022-01-19  5:01 ` Gigahawk
2022-06-22  2:14 ` github-actions
2022-07-07  2:14 ` [PR PATCH] [Closed]: " github-actions

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=20220119003550.MVtUGk705mQMC23QFdcXRTGYt5ykU7EiLG1yJ0fnXb0@z \
    --to=gigahawk@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    --subject='Re: [PR PATCH] [Updated] Manual.md: Document unresolvable shlib issue' \
    /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

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).