From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: poppler: update to 22.03.0
Date: Sat, 26 Mar 2022 20:30:45 +0100 [thread overview]
Message-ID: <20220326193045.7ADgw0UL5rYocy-THpHMfaF7XFU0uwIczpDICYcIjuc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36351@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 283 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/36351#issuecomment-1079755659
Comment:
I notified upstream of the ipe-tools patch.
(From what I can tell the failing x86_64-musl test has been an issue for a while before this PR)
next prev parent reply other threads:[~2022-03-26 19:30 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 1:37 [PR PATCH] " oreo639
2022-03-26 1:39 ` [PR PATCH] [Updated] " oreo639
2022-03-26 3:40 ` oreo639
2022-03-26 3:41 ` oreo639
2022-03-26 3:42 ` [PR PATCH] [Updated] " oreo639
2022-03-26 3:42 ` oreo639
2022-03-26 4:03 ` [PR PATCH] [Updated] " oreo639
2022-03-26 5:21 ` oreo639
2022-03-26 5:48 ` oreo639
2022-03-26 6:21 ` oreo639
2022-03-26 17:54 ` oreo639
2022-03-26 17:59 ` oreo639
2022-03-26 19:03 ` oreo639
2022-03-26 19:30 ` oreo639 [this message]
2022-03-26 19:30 ` oreo639
2022-04-17 8:12 ` oreo639
2022-04-17 8:14 ` oreo639
2022-04-17 8:35 ` [PR PATCH] [Updated] " oreo639
2022-04-17 8:52 ` [PR PATCH] [Updated] poppler: update to 22.04.0 oreo639
2022-04-17 9:29 ` oreo639
2022-04-17 9:31 ` oreo639
2022-04-17 9:35 ` oreo639
2022-04-17 10:22 ` oreo639
2022-04-17 10:45 ` oreo639
2022-04-17 10:46 ` oreo639
2022-04-17 10:47 ` oreo639
2022-04-17 10:55 ` oreo639
2022-04-17 23:07 ` [PR PATCH] [Updated] " oreo639
2022-04-18 23:47 ` oreo639
2022-05-01 2:03 ` oreo639
2022-05-01 2:05 ` oreo639
2022-05-12 4:19 ` oreo639
2022-05-16 21:43 ` oreo639
2022-06-11 23:10 ` oreo639
2022-06-17 0:05 ` [PR PATCH] [Updated] poppler: update to 22.06.0 oreo639
2022-06-17 0:51 ` oreo639
2022-06-17 1:40 ` classabbyamp
2022-06-17 4:53 ` oreo639
2022-06-18 23:59 ` oreo639
2022-06-19 0:02 ` oreo639
2022-06-19 0:02 ` oreo639
2022-06-19 0:04 ` oreo639
2022-06-19 0:05 ` [PR PATCH] [Updated] " oreo639
2022-06-19 0:06 ` oreo639
2022-06-19 0:06 ` oreo639
2022-06-19 0:10 ` oreo639
2022-06-19 0:11 ` oreo639
2022-06-19 0:37 ` oreo639
2022-07-05 10:47 ` paper42
2022-07-05 18:26 ` oreo639
2022-07-05 18:29 ` oreo639
2022-07-05 18:30 ` oreo639
2022-07-05 18:31 ` oreo639
2022-07-05 18:42 ` oreo639
2022-07-05 18:47 ` oreo639
2022-07-05 19:38 ` oreo639
2022-07-05 23:12 ` [PR PATCH] [Updated] " oreo639
2022-07-05 23:13 ` oreo639
2022-07-05 23:26 ` oreo639
2022-07-05 23:38 ` oreo639
2022-07-05 23:58 ` [PR PATCH] [Updated] poppler: update to 22.07.0 oreo639
2022-07-06 7:39 ` oreo639
2022-07-06 7:39 ` oreo639
2022-07-06 7:40 ` oreo639
2022-07-06 8:50 ` [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=20220326193045.7ADgw0UL5rYocy-THpHMfaF7XFU0uwIczpDICYcIjuc@z \
--to=oreo639@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).