From: rivanfebrian123 <rivanfebrian123@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: pdfarranger-1.8.0
Date: Wed, 24 Nov 2021 07:33:30 +0100 [thread overview]
Message-ID: <20211124063330.d4nOrhZmUy7TxpSacAiAsHmeZz2B7D4eRlV9u_StX40@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34216@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
New comment by rivanfebrian123 on void-packages repository
https://github.com/void-linux/void-packages/pull/34216#issuecomment-977573772
Comment:
Why didn't some jobs pass the test? Is there any problem with CI/CD config or something?
```
=> pdfarranger-1.8.0_1: running do_check ...
running test
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
running egg_info
creating pdfarranger.egg-info
writing pdfarranger.egg-info/PKG-INFO
writing dependency_links to pdfarranger.egg-info/dependency_links.txt
writing entry points to pdfarranger.egg-info/entry_points.txt
writing requirements to pdfarranger.egg-info/requires.txt
writing top-level names to pdfarranger.egg-info/top_level.txt
writing manifest file 'pdfarranger.egg-info/SOURCES.txt'
reading manifest file 'pdfarranger.egg-info/SOURCES.txt'
adding license file 'COPYING'
writing manifest file 'pdfarranger.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
File "/builddir/pdfarranger-1.8.0/pdfarranger/pdfarranger.py", line 455, in do_activate
self.uiXML = self.__build_from_file(DOMAIN + '.ui')
File "/builddir/pdfarranger-1.8.0/pdfarranger/pdfarranger.py", line 308, in __build_from_file
b.add_from_file(f)
gi.repository.GLib.Error: g-file-error-quark: Failed to open file “/usr/local/share/pdfarranger/pdfarranger.ui”: No such file or directory (4)
[Errno 2] No such file or directory: '/builddir/pdfarranger-1.8.0/test'
Error: The operation was canceled.
```
next prev parent reply other threads:[~2021-11-24 6:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34216@inbox.vuxu.org>
2021-11-23 18:29 ` Duncaen
2021-11-24 6:33 ` rivanfebrian123 [this message]
2021-12-11 10:16 ` hervyqa
2022-01-02 2:21 ` [PR PATCH] [Updated] " hervyqa
2022-01-02 2:24 ` [PR PATCH] [Updated] New package: pdfarranger-1.8.2 hervyqa
2022-01-02 2:43 ` hervyqa
2022-01-02 10:52 ` hervyqa
2022-01-06 4:39 ` rivanfebrian123
2022-01-06 6:21 ` [PR PATCH] [Updated] " hervyqa
2022-01-06 6:22 ` hervyqa
2022-01-06 6:33 ` hervyqa
2022-01-06 6:48 ` hervyqa
2022-01-06 7:16 ` hervyqa
2022-06-16 2:14 ` github-actions
2022-07-01 2:14 ` [PR PATCH] [Closed]: " github-actions
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=20211124063330.d4nOrhZmUy7TxpSacAiAsHmeZz2B7D4eRlV9u_StX40@z \
--to=rivanfebrian123@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).