From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: perl: update to 5.34
Date: Tue, 20 Jul 2021 17:18:45 +0200 [thread overview]
Message-ID: <20210720151845.sWCQbcf8buc6N0cVW_K-sbKLkJsQltN2Q3QlP3yGfyE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31635@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/31635#issuecomment-883478732
Comment:
@leahneukirchen That's what confuses me: none of the `checkdepends` of `perl` are rebuilt in this pr, but if I first do `./xbps-pkg update-bulk` and then `./xbps-pkg -f perl` (I set `XBPS_CHECK_PKGS=full`), then `perl` passes the tests (see above), so I do not know why it fails on ci.
Btw, I fixed a couple of `checkdepends` for the failures above, and I'm left with test failures in
```
srcpkgs/biber/template
srcpkgs/gnumeric/template
srcpkgs/perl-Fuse/template
srcpkgs/perl-Gtk2/template
srcpkgs/perl-Image-Sane/template
srcpkgs/perl-Linux-Inotify2/template
srcpkgs/perl-OpenGL/template
srcpkgs/perl-Search-Xapian/template
srcpkgs/perl-Unix-Mknod/template
srcpkgs/perl-pcsc/template
srcpkgs/postgresql12/template
srcpkgs/postgresql13/template
srcpkgs/rrdtool/template
srcpkgs/subversion/template
```
as for biber, it can be removed from this pr, where it does not belong, but what about remaining others?
should I be happy with `make_check=no`?
next prev parent reply other threads:[~2021-07-20 15:18 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 17:29 [PR PATCH] [wip] " dkwo
2021-06-23 18:56 ` dkwo
2021-06-23 20:11 ` dkwo
2021-06-23 20:12 ` dkwo
2021-06-24 9:27 ` dkwo
2021-06-24 9:32 ` dkwo
2021-06-24 9:33 ` dkwo
2021-06-24 12:14 ` dkwo
2021-06-28 12:06 ` [PR PATCH] [Updated] " dkwo
2021-06-28 12:30 ` dkwo
2021-06-28 12:56 ` dkwo
2021-06-28 12:59 ` [PR PATCH] [Updated] " dkwo
2021-06-28 13:11 ` dkwo
2021-06-28 14:06 ` ericonr
2021-06-28 15:46 ` [PR PATCH] [Updated] " dkwo
2021-06-28 15:53 ` dkwo
2021-06-28 16:31 ` dkwo
2021-06-28 16:32 ` dkwo
2021-06-28 16:33 ` dkwo
2021-06-28 17:19 ` Chocimier
2021-06-29 7:12 ` [PR PATCH] [Updated] " dkwo
2021-06-29 7:13 ` dkwo
2021-06-29 7:19 ` dkwo
2021-06-29 7:22 ` dkwo
2021-06-29 7:24 ` dkwo
2021-06-29 7:27 ` dkwo
2021-07-07 15:57 ` [PR PATCH] [Updated] " dkwo
2021-07-07 15:59 ` dkwo
2021-07-07 16:04 ` [PR PATCH] [Updated] " dkwo
2021-07-07 16:31 ` sgn
2021-07-08 11:16 ` [PR PATCH] [Updated] " dkwo
2021-07-13 14:26 ` dkwo
2021-07-13 16:39 ` leahneukirchen
2021-07-14 7:42 ` [PR PATCH] [Updated] " dkwo
2021-07-14 9:13 ` dkwo
2021-07-14 10:40 ` dkwo
2021-07-14 10:46 ` leahneukirchen
2021-07-17 15:33 ` [PR PATCH] [Updated] " dkwo
2021-07-17 15:36 ` dkwo
2021-07-20 8:35 ` dkwo
2021-07-20 9:00 ` dkwo
2021-07-20 13:52 ` leahneukirchen
2021-07-20 15:18 ` dkwo [this message]
2021-07-20 15:23 ` leahneukirchen
2021-07-21 7:47 ` [PR PATCH] [Updated] " dkwo
2021-07-21 7:55 ` dkwo
2021-07-21 11:22 ` leahneukirchen
2021-07-21 11:24 ` leahneukirchen
2021-07-21 11:24 ` [PR PATCH] [Closed]: " leahneukirchen
2021-07-22 7:28 ` dkwo
2021-07-22 13:18 ` dkwo
2021-07-22 13:48 ` dkwo
2021-07-22 13:56 ` dkwo
2021-07-22 13:59 ` dkwo
2021-07-28 13:18 ` dkwo
2021-09-06 17:11 ` dkwo
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=20210720151845.sWCQbcf8buc6N0cVW_K-sbKLkJsQltN2Q3QlP3yGfyE@z \
--to=dkwo@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).