From: Bleznudd <Bleznudd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: setzer-0.3.2
Date: Sun, 27 Sep 2020 14:29:23 +0200 [thread overview]
Message-ID: <20200927122923.XQhbG_YQdtKpWl4zFX-WAPt6gzj5WIh5gSjxsb2SFQo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25088@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
New review comment by Bleznudd on void-packages repository
https://github.com/void-linux/void-packages/pull/25088#discussion_r495568096
Comment:
It seems that `virtual?tex` is giving problem on arm (`aarch64`, `armv7l`, `armv6l-musl` and `aarch64-musl`), travis log says:
```
=> texlive-20200406_4: installing host dependencies: pkg-config-0.29.2_2 perl-5.30.3_1 lua52-BitOp-1.0.2_3 texinfo-6.7_1 texlive-20200406_4 cross-i686-linux-musl-0.33_3 ...
=> texlive-20200406_4: installing target dependencies: cairo-devel-1.16.0_2 freetype-devel-2.10.2_1 gd-devel-2.3.0_2 graphite-devel-1.3.14_1 gmp-devel-6.2.0_1 harfbuzz-devel-2.7.2_2 icu-devel-67.1_1 libpaper-devel-1.1.28_1 libpng-devel-1.6.37_1 mpfr-devel-4.0.2_1 poppler-devel-20.09.0_1 pixman-devel-0.38.4_1 libteckit-devel-2.5.10_1 zlib-devel-1.2.11_3 zziplib-devel-0.13.71_1 libXaw-devel-1.0.13_2 ...
=> texlive-20200406_4: running do-fetch hook: 00-distfiles ...
=> texlive-20200406_4: fetching distfile 'texlive-20200406-source.tar.xz'...
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
The build has been terminated
```
Any clue?
next prev parent reply other threads:[~2020-09-27 12:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 15:13 [PR PATCH] New package: setzer Bleznudd
2020-09-25 15:53 ` [PR REVIEW] " PaperMountainStudio
2020-09-25 15:53 ` PaperMountainStudio
2020-09-25 15:53 ` PaperMountainStudio
2020-09-25 15:54 ` PaperMountainStudio
2020-09-25 15:58 ` [PR REVIEW] " PaperMountainStudio
2020-09-25 16:02 ` PaperMountainStudio
2020-09-25 16:09 ` PaperMountainStudio
2020-09-25 16:49 ` [PR PATCH] [Updated] " Bleznudd
2020-09-25 16:51 ` Bleznudd
2020-09-25 16:52 ` [PR REVIEW] " Bleznudd
2020-09-25 16:52 ` Bleznudd
2020-09-25 16:52 ` Bleznudd
2020-09-25 16:55 ` Bleznudd
2020-09-25 16:58 ` Bleznudd
2020-09-25 17:03 ` [PR REVIEW] New package: setzer-0.3.2 Bleznudd
2020-09-25 19:37 ` PaperMountainStudio
2020-09-25 19:46 ` PaperMountainStudio
2020-09-26 17:10 ` [PR PATCH] [Updated] " Bleznudd
2020-09-26 17:41 ` Bleznudd
2020-09-26 20:14 ` [PR REVIEW] " Bleznudd
2020-09-26 20:35 ` ericonr
2020-09-26 20:44 ` Bleznudd
2020-09-26 20:44 ` [PR REVIEW] " ericonr
2020-09-26 20:52 ` ericonr
2020-09-26 21:01 ` [PR PATCH] [Updated] " Bleznudd
2020-09-26 22:34 ` ericonr
2020-09-27 3:07 ` ahesford
2020-09-27 3:25 ` ericonr
2020-09-27 6:01 ` [PR REVIEW] " ericonr
2020-09-27 6:03 ` ericonr
2020-09-27 11:58 ` [PR PATCH] [Updated] " Bleznudd
2020-09-27 12:00 ` [PR REVIEW] " Bleznudd
2020-09-27 12:29 ` Bleznudd [this message]
2020-09-27 14:29 ` ericonr
2020-09-27 14:32 ` ericonr
2020-09-27 16:59 ` [PR PATCH] [Updated] " Bleznudd
2020-09-27 17:00 ` [PR REVIEW] " Bleznudd
2020-09-29 0:24 ` [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=20200927122923.XQhbG_YQdtKpWl4zFX-WAPt6gzj5WIh5gSjxsb2SFQo@z \
--to=bleznudd@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).