From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: ddgtk: fixes for vte, latest meson, py module name, additional deps
Date: Sun, 30 Jun 2019 15:35:04 +0200 [thread overview]
Message-ID: <20190630133504.9g-G9NqWhlkYE6xAqmtlfmljglNdu2W70p-KeBmsfsU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12710@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
There's a merged pull request on the void-packages repository
ddgtk: fixes for vte, latest meson, py module name, additional deps
https://github.com/void-linux/void-packages/pull/12710
Description: **Changes:**
1. Added additional dependencies against build warnings [template]
2. Updated for latest meson [patch]
3. Updated for latest python module (instead of deprecated `python3` module, used the new `python` module, according to: [https://mesonbuild.com/Release-notes-for-0-48-0.html#dependencyversion-now-applies-to-all-dependency-types](https://mesonbuild.com/Release-notes-for-0-48-0.html#dependencyversion-now-applies-to-all-dependency-types)) [patch]
4. Fixed breakage of write functionality due to recent changes in Vte python bindings (Explanation here: [https://github.com/Guake/guake/issues/1243#issuecomment-410208659](https://github.com/Guake/guake/issues/1243#issuecomment-410208659)) [patch]
#4 raised an error like this below which has been fixed:
```
Traceback (most recent call last):
File "/usr/local/share/ddgtk/ddgtk/main.py", line 154, in on_confirm_ok_clicked
self.dd()
File "/usr/local/share/ddgtk/ddgtk/main.py", line 125, in dd
self.terminal.feed_child(clear,-1)
TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given)
```
next prev parent reply other threads:[~2019-06-30 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 22:51 [PR PATCH] ddgtk: fixes for recent vte python bindings + other changes voidlinux-github
2019-06-26 23:14 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-26 23:14 ` voidlinux-github
2019-06-27 8:23 ` voidlinux-github
2019-06-27 14:25 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-27 14:25 ` voidlinux-github
2019-06-27 14:30 ` voidlinux-github
2019-06-27 14:32 ` voidlinux-github
2019-06-27 15:24 ` voidlinux-github
2019-06-27 15:26 ` voidlinux-github
2019-06-27 15:26 ` voidlinux-github
2019-06-27 16:55 ` ddgtk: added fixes for recent vte python bindings, added additional deps, updated for latest meson, adjusted to new python module name voidlinux-github
2019-06-27 16:56 ` voidlinux-github
2019-06-27 16:58 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-27 16:58 ` voidlinux-github
2019-06-28 16:17 ` voidlinux-github
2019-06-28 21:13 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-28 21:13 ` voidlinux-github
2019-06-28 21:22 ` ddgtk: fixes for vte, latest meson, py module name, additional deps voidlinux-github
2019-06-30 13:35 ` voidlinux-github [this message]
2019-06-30 13:39 ` voidlinux-github
2019-06-30 14:46 ` voidlinux-github
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=20190630133504.9g-G9NqWhlkYE6xAqmtlfmljglNdu2W70p-KeBmsfsU@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).