From: hervyqa <hervyqa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: pdfarranger-1.7.1_1
Date: Tue, 10 Aug 2021 16:22:38 +0200 [thread overview]
Message-ID: <20210810142238.XvNg_SLaQp02L5tEMGmfPFFWPFj9A-N-yZXh0Z_9MtI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32301@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]
New comment by hervyqa on void-packages repository
https://github.com/void-linux/void-packages/pull/32301#issuecomment-896073369
Comment:
> > If @noarchwastaken is interested in this continuing the work on pdfarranger, I will to close this PR as a duplicate of #30338, but @hervyqa, please create a review on that PR, because some parts of this one are better and should be moved there.
> > If they are not interested in it anymore, we can continue here and pull in some of their changes.
> > @rivanfebrian123 thanks for noticing this
>
> I'll go with this PR since it has the above fixes.
>
> About the `xvfb-run` dependency, I can't find any checks included with `pdfarranger`, so what does `setup.py test` actually do here?
Needs a graphical session. https://github.com/void-linux/void-packages/pull/32301#issuecomment-891248272
```
running build_ext
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
/builddir/pdfarranger-1.7.1/pdfarranger/splitter.py:17: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
(setup.py:3814): Gtk-CRITICAL **: 18:11:15.810: gtk_clipboard_get_for_display: assertion 'display != NULL' failed
(setup.py:3814): Gtk-CRITICAL **: 18:11:15.810: gtk_clipboard_get_for_display: assertion 'display != NULL' failed
Unable to init server: Could not connect: Connection refused
(setup.py:3814): Gtk-WARNING **: 18:11:15.811: cannot open display:
=> ERROR: pdfarranger-1.7.1_1: do_check: 'python3 setup.py ${make_check_target} ${make_check_args}' exited with 1
=> ERROR: in do_check() at common/build-style/python3-module.sh:40
Error: Process completed with exit code 1.
```
next prev parent reply other threads:[~2021-08-10 14:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 17:26 [PR PATCH] " hervyqa
2021-08-02 17:34 ` [PR PATCH] [Updated] " hervyqa
2021-08-02 17:47 ` hervyqa
2021-08-02 18:07 ` hervyqa
2021-08-02 18:19 ` hervyqa
2021-08-02 18:42 ` paper42
2021-08-02 18:56 ` [PR REVIEW] " paper42
2021-08-02 18:56 ` paper42
2021-08-02 18:56 ` paper42
2021-08-02 18:56 ` paper42
2021-08-02 23:44 ` [PR PATCH] [Updated] " hervyqa
2021-08-02 23:51 ` hervyqa
2021-08-02 23:51 ` [PR REVIEW] " hervyqa
2021-08-02 23:54 ` hervyqa
2021-08-02 23:55 ` hervyqa
2021-08-03 0:12 ` [PR PATCH] [Updated] " hervyqa
2021-08-08 6:41 ` rivanfebrian123
2021-08-08 8:11 ` paper42
2021-08-09 5:02 ` hervyqa
2021-08-10 9:02 ` noarchwastaken
2021-08-10 14:22 ` hervyqa [this message]
2021-08-10 16:57 ` paper42
2021-08-15 11:14 ` hervyqa
2021-11-23 17:15 ` [PR PATCH] [Updated] " hervyqa
2021-11-23 18:07 ` [PR PATCH] [Closed]: " hervyqa
2021-11-23 18:07 ` hervyqa
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=20210810142238.XvNg_SLaQp02L5tEMGmfPFFWPFj9A-N-yZXh0Z_9MtI@z \
--to=hervyqa@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).