From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: virtuoso: update to 7.2.10
Date: Sun, 25 Jun 2023 22:16:30 +0200 [thread overview]
Message-ID: <20230625201630.hDgNQe26CA4NqJb1Gsql0Ye-WHlxCPl010VjP-ckn94@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42666@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
There's a merged pull request on the void-packages repository
virtuoso: update to 7.2.10
https://github.com/void-linux/void-packages/pull/42666
Description:
#### Testing the changes
- I tested the changes in this PR: most of the test suite passes (excepting tgraphql), I don't use this package directly
This package has some weirdness in the test suite. It fails when run from `./xbps-src -K pkg virtuoso` but succeeds if I do `./xbps-src chroot` afterwards and:
```
make clean
./autogen.sh
./configure
make
make check
```
I tried replacing pre_configure, do_configure, do_build and do_check to do the same thing but it still fails. Maybe I'm missing some dependencies or something.
`tgraphql` is the only test failing:
[tgraphql.output.log](https://github.com/void-linux/void-packages/files/10926435/tgraphql.output.log)
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for my native architecture, (x86_64-musl)
prev parent reply other threads:[~2023-06-25 20:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 0:24 [PR PATCH] virtuoso: update to 7.2.9 klarasm
2023-03-09 15:12 ` [PR PATCH] [Updated] " klarasm
2023-03-09 15:13 ` klarasm
2023-03-09 16:14 ` klarasm
2023-03-09 20:34 ` [PR PATCH] [Updated] " klarasm
2023-03-09 21:04 ` klarasm
2023-06-08 2:05 ` github-actions
2023-06-08 19:33 ` klarasm
2023-06-09 13:51 ` klarasm
2023-06-09 14:24 ` [PR PATCH] [Updated] " klarasm
2023-06-25 19:03 ` [PR REVIEW] virtuoso: update to 7.2.10 Duncaen
2023-06-25 19:31 ` [PR PATCH] [Updated] " klarasm
2023-06-25 19:43 ` [PR REVIEW] " klarasm
2023-06-25 20:16 ` Duncaen [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=20230625201630.hDgNQe26CA4NqJb1Gsql0Ye-WHlxCPl010VjP-ckn94@z \
--to=duncaen@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).