Github messages for voidlinux
 help / color / mirror / Atom feed
From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: volctl: update to 0.8.2.
Date: Wed, 17 Feb 2021 15:58:26 +0100	[thread overview]
Message-ID: <20210217145826.ZSBD5sl2qhpyL9EiGUcz8dF38iV-GcY91eGirhwZ-iA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28806@inbox.vuxu.org>

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

New comment by teldra on void-packages repository

https://github.com/void-linux/void-packages/pull/28806#issuecomment-780613503

Comment:
> This looks like it's looking for X server. Maybe use `xvfb-run dbus-run-session`?

Yes that did the Trick.

Now the funny parts: 
- No tests were executed. Should I instead add `do_check() { : }`? https://github.com/void-linux/void-packages/pull/28806/checks?check_run_id=1919520285#step:8:108
- Right now, I had to add `post_extract()`. Without it, this happens:
```
/builddir/volctl-0.8.2/volctl/meta.py:2: 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
```

  parent reply	other threads:[~2021-02-17 14:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 23:50 [PR PATCH] " teldra
2021-02-17 14:04 ` ericonr
2021-02-17 14:21 ` [PR PATCH] [Updated] " teldra
2021-02-17 14:37 ` teldra
2021-02-17 14:49 ` teldra
2021-02-17 14:54 ` teldra
2021-02-17 14:58 ` teldra [this message]
2021-02-18  4:54 ` [PR REVIEW] " ericonr
2021-02-18  4:54 ` ericonr
2021-02-18  4:54 ` ericonr
2021-02-19  9:17 ` [PR PATCH] [Updated] " teldra
2021-02-19  9:24 ` teldra
2021-02-19 10:33 ` teldra
2021-02-22 19:10 ` teldra
2021-02-22 19:16 ` [PR REVIEW] " teldra
2021-02-22 19:16 ` teldra
2021-02-22 19:21 ` [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=20210217145826.ZSBD5sl2qhpyL9EiGUcz8dF38iV-GcY91eGirhwZ-iA@z \
    --to=teldra@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).