From: crtxcr <crtxcr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] perl-rrdtool: Add missing "perl" dependency
Date: Thu, 22 Dec 2022 21:24:36 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41245@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
There is a new pull request by crtxcr against master on the void-packages repository
https://github.com/crtxcr/void-packages fix_rrdtool_depends
https://github.com/void-linux/void-packages/pull/41245
perl-rrdtool: Add missing "perl" dependency
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
The test for https://github.com/void-linux/void-packages/pull/41228 fails with:
> perl-rrdtool-1.7.2_13: broken, unresolvable shlib `libperl.so.5.36'
This can be reproduced by:
```
./xbps-src -m musl_temp binary-bootstrap x86_64-musl
./xbps-src -m musl_temp chroot
xbps-install perl-rrdtool
```
This is a due to missing "depends" on perl.
This PR simply adds perl to the dependecy
CC @Gottox
A patch file from https://github.com/void-linux/void-packages/pull/41245.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix_rrdtool_depends-41245.patch --]
[-- Type: text/x-diff, Size: 960 bytes --]
From 68d3804d182a4ded730a29d8f29bc86f8121d5ae Mon Sep 17 00:00:00 2001
From: Albert Schwarzkopf <dev-voidlinux@quitesimple.org>
Date: Thu, 22 Dec 2022 21:15:54 +0100
Subject: [PATCH] perl-rrdtool: Add missing "perl" dependency
---
srcpkgs/rrdtool/template | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/rrdtool/template b/srcpkgs/rrdtool/template
index c45176f72a85..3a717e8b9d03 100644
--- a/srcpkgs/rrdtool/template
+++ b/srcpkgs/rrdtool/template
@@ -1,7 +1,7 @@
# Template file for 'rrdtool'
pkgname=rrdtool
version=1.7.2
-revision=13
+revision=14
build_style=gnu-configure
# configure checks sys.version[:3] for Python versioning, so 3.10 becomes 3.1;
# until this is fixed upstream, manually define am_cv_python_version to circumvent
@@ -38,6 +38,7 @@ python3-rrdtool_package() {
}
perl-rrdtool_package() {
+ depends+=" perl"
short_desc+=" - perl bindings"
shlib_requires="libperl.so.5.36"
pkg_install() {
next reply other threads:[~2022-12-22 20:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 20:24 crtxcr [this message]
2022-12-22 20:52 ` paper42
2022-12-22 20:53 ` paper42
2022-12-22 21:36 ` [PR PATCH] [Updated] " crtxcr
2022-12-22 21:37 ` crtxcr
2022-12-22 21:40 ` perl-rddtool: rebuild to fix unresolvable shlib crtxcr
2022-12-22 23:40 ` [PR PATCH] [Updated] " crtxcr
2022-12-22 23:41 ` crtxcr
2022-12-22 23:48 ` crtxcr
2022-12-22 23:48 ` crtxcr
2022-12-23 0:35 ` rrdtool: rebuild to fix unresolvable shlib, fix tests paper42
2022-12-23 7:34 ` sgn
2022-12-23 7:52 ` [PR PATCH] [Updated] " crtxcr
2022-12-23 7:54 ` crtxcr
2022-12-23 8:01 ` crtxcr
2022-12-23 10:59 ` [PR PATCH] [Updated] " crtxcr
2022-12-23 11:00 ` crtxcr
2022-12-23 11:06 ` crtxcr
2022-12-23 11:16 ` [PR PATCH] [Merged]: " paper42
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-41245@inbox.vuxu.org \
--to=crtxcr@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).