Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cross-vpkg-dummy: provide libthread_db.so.1 on glibc
Date: Mon, 13 Mar 2023 01:50:00 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42736@inbox.vuxu.org> (raw)

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

There is a new pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages jre11-test
https://github.com/void-linux/void-packages/pull/42736

cross-vpkg-dummy: provide libthread_db.so.1 on glibc
this should fix issues with openjdk11-jre in void-packages/CI verify repository state on cross:

```
openjdk11-jre-11.0.12+7_4: broken, unresolvable shlib `libthread_db.so.1'
Transaction aborted due to unresolved shlibs.
```

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**



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

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

From 75a3f441d1278fb6f7047614ad226b2db6bf6311 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Sun, 12 Mar 2023 18:25:40 -0400
Subject: [PATCH] cross-vpkg-dummy: provide libthread_db.so.1 on glibc

this should fix issues with openjdk11-jre in void-packages/CI verify
repository state on cross:

```
openjdk11-jre-11.0.12+7_4: broken, unresolvable shlib `libthread_db.so.1'
Transaction aborted due to unresolved shlibs.
```
---
 srcpkgs/cross-vpkg-dummy/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/cross-vpkg-dummy/template b/srcpkgs/cross-vpkg-dummy/template
index 75ac42f2c1ab..943bfae9ee38 100644
--- a/srcpkgs/cross-vpkg-dummy/template
+++ b/srcpkgs/cross-vpkg-dummy/template
@@ -1,7 +1,7 @@
 # Template file for 'cross-vpkg-dummy'
 pkgname=cross-vpkg-dummy
 version=0.39
-revision=3
+revision=4
 build_style=meta
 short_desc="Dummy meta-pkg for cross building packages with xbps-src"
 maintainer="Orphaned <orphan@voidlinux.org>"
@@ -75,5 +75,5 @@ else
 	shlib_provides+=" libanl.so.1 libnsl.so.1 libutil.so.1"
 	shlib_provides+=" ld-linux.so.2 ld-linux.so.3 ld-linux-x86-64.so.2"
 	shlib_provides+=" ld-linux-armhf.so.3 ld-linux-aarch64.so.1"
-	shlib_provides+=" ld64.so.2 ld.so.1"
+	shlib_provides+=" ld64.so.2 ld.so.1 libthread_db.so.1"
 fi

             reply	other threads:[~2023-03-13  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  0:50 classabbyamp [this message]
2023-03-13  1:01 ` [PR PATCH] [Updated] " classabbyamp
2023-03-13 17:40 ` classabbyamp
2023-03-13 18:04 ` [PR PATCH] [Updated] " classabbyamp
2023-03-15 20:13 ` [PR PATCH] [Merged]: " classabbyamp

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-42736@inbox.vuxu.org \
    --to=classabbyamp@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).