Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libtirpc: update to 1.3.1.
Date: Sat, 05 Dec 2020 21:45:35 +0100	[thread overview]
Message-ID: <20201205204535.Vn9NVhODCrm1F22FiMNCi6bks0U4HAr7Flv9hKyFBBM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26916@inbox.vuxu.org>

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/26916#issuecomment-739413775

Comment:
It seems to work ok with my version of ZFS, but I would prefer to have it sit for a while for testing. Will try Xorg as well.

Meanwhile, can you get tests to run?

```
=> libtirpc-1.3.1_1: running do_check ...
Making check in src
Making check in man
Making check in doc
Making check in src
make[1]: Entering directory '/builddir/libtirpc-1.3.1/src'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/builddir/libtirpc-1.3.1/src'
Making check in man
make[1]: Entering directory '/builddir/libtirpc-1.3.1/man'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/builddir/libtirpc-1.3.1/man'
Making check in doc
make[1]: Entering directory '/builddir/libtirpc-1.3.1/doc'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/builddir/libtirpc-1.3.1/doc'
make[1]: Entering directory '/builddir/libtirpc-1.3.1'
make[1]: Leaving directory '/builddir/libtirpc-1.3.1'
=> libtirpc-1.3.1_1: running pre-install hook: 00-lib32 ...
```

  reply	other threads:[~2020-12-05 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 12:18 [PR PATCH] " ndowens
2020-12-05 20:45 ` ericonr [this message]
2020-12-05 21:13 ` ndowens
2020-12-17 17:59 ` [PR PATCH] [Merged]: " ericonr

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=20201205204535.Vn9NVhODCrm1F22FiMNCi6bks0U4HAr7Flv9hKyFBBM@z \
    --to=ericonr@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).