From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyshark/
Date: Tue, 2 May 2017 19:31:33 +0000 (UTC) [thread overview]
Message-ID: <1493753490.f326ec72161256201ee39ef7a747cd15d00319e8.floppym@gentoo> (raw)
commit: f326ec72161256201ee39ef7a747cd15d00319e8
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Tue May 2 19:31:09 2017 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Tue May 2 19:31:30 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f326ec72
dev-python/pyshark: add link to upstream bug report
Package-Manager: Portage-2.3.5_p31, Repoman-2.3.2_p61
dev-python/pyshark/pyshark-0.3.7.2.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/dev-python/pyshark/pyshark-0.3.7.2.ebuild b/dev-python/pyshark/pyshark-0.3.7.2.ebuild
index 66b7f24e91b..4d11881ab65 100644
--- a/dev-python/pyshark/pyshark-0.3.7.2.ebuild
+++ b/dev-python/pyshark/pyshark-0.3.7.2.ebuild
@@ -37,7 +37,8 @@ DEPEND="
S="${WORKDIR}/${P}/src"
python_prepare_all() {
- # Test fails in ebuild env, works standalone.
+ # Test fails unless portage can execute /usr/bin/dumpcap
+ # https://github.com/KimiNewt/pyshark/issues/197
rm "${WORKDIR}/${P}/tests/capture/test_inmem_capture.py" || die
distutils-r1_python_prepare_all
}
next reply other threads:[~2017-05-02 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 19:31 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-28 18:26 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyshark/ Michał Górny
2019-05-17 2:56 Rick Farina
2018-06-24 17:24 Pacho Ramos
2017-05-02 19:15 Michał Górny
2017-05-02 16:13 Mike Gilbert
2017-05-02 15:13 Mike Gilbert
2016-01-11 8:16 Justin Lecher
2016-01-06 17:14 Justin Lecher
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=1493753490.f326ec72161256201ee39ef7a747cd15d00319e8.floppym@gentoo \
--to=floppym@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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