From: "Andrew Ammerlaan" <andrewammerlaan@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: media-video/vidify/
Date: Wed, 1 Apr 2020 19:38:48 +0000 (UTC) [thread overview]
Message-ID: <1585769908.6575e940f59f1566a87489665b425f980a0d8b4f.andrewammerlaan@gentoo> (raw)
Message-ID: <20200401193848.pVX52vCqie460OfllguAxABMSeQksHQ7XiqrlLuul64@z> (raw)
commit: 6575e940f59f1566a87489665b425f980a0d8b4f
Author: Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
AuthorDate: Wed Apr 1 19:38:28 2020 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
CommitDate: Wed Apr 1 19:38:28 2020 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6575e940
media-video/vidify: version bump 2.2.0
Package-Manager: Portage-2.3.96, Repoman-2.3.22
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> riseup.net>
media-video/vidify/Manifest | 2 +-
.../{vidify-2.1.0.ebuild => vidify-2.2.0.ebuild} | 20 ++++++++++++++------
2 files changed, 15 insertions(+), 7 deletions(-)
diff --git a/media-video/vidify/Manifest b/media-video/vidify/Manifest
index f437ef6..552a9ac 100644
--- a/media-video/vidify/Manifest
+++ b/media-video/vidify/Manifest
@@ -1 +1 @@
-DIST vidify-2.1.0.tar.gz 2332514 BLAKE2B c3199cd20de6e306406482a15addaf1875630c61271ea04b4a0c283d14030102eced6428e2dc8945ab482af6c81f94c51742983e9a9b6581b3aac60bd1c942f6 SHA512 e1a7d60caacd30d68fc8b1ebf3ea30a0527218257fe762989dd8ca5213beb247c300a7ffafe68554c88a1f3bb2a054a555fe15a66a727c57911f1f545e8d0297
+DIST vidify-2.2.0.tar.gz 2903665 BLAKE2B 0740ad35728eb80537170f75180e03dd88bdbaba2ab84e7d4c0453bc8e104550a510f5a25f42d9a84a9e5659f7bd142d1eae537c58b629cc509a110d14e353b8 SHA512 456ad36487c7a66b004de2e8837e718a9b18a235a5bc95bc6322ee43e4fbdf610f4a38dfdbea139e05ae3dc9551eb9116ace7a4dddf01356bea9858599aaa6cd
diff --git a/media-video/vidify/vidify-2.1.0.ebuild b/media-video/vidify/vidify-2.2.0.ebuild
similarity index 77%
rename from media-video/vidify/vidify-2.1.0.ebuild
rename to media-video/vidify/vidify-2.2.0.ebuild
index 7cc16dd..66c27c9 100644
--- a/media-video/vidify/vidify-2.1.0.ebuild
+++ b/media-video/vidify/vidify-2.2.0.ebuild
@@ -7,7 +7,7 @@ PYTHON_COMPAT=( python3_7 )
DISTUTILS_USE_SETUPTOOLS=rdepend
-inherit eutils xdg distutils-r1
+inherit eutils xdg distutils-r1 virtualx
DESCRIPTION="Watch music videos in real time for the songs playing on your device"
HOMEPAGE="https://github.com/vidify/vidify"
@@ -25,27 +25,36 @@ RDEPEND="
dev-python/appdirs[${PYTHON_USEDEP}]
dev-python/lyricwikia[${PYTHON_USEDEP}]
dev-python/pydbus[${PYTHON_USEDEP}]
+ dev-python/qdarkstyle[${PYTHON_USEDEP}]
dev-python/QtPy[gui,webengine,${PYTHON_USEDEP}]
dev-python/tekore[${PYTHON_USEDEP}]
net-misc/youtube-dl[${PYTHON_USEDEP}]
+ dev-python/zeroconf[${PYTHON_USEDEP}]
mpv? ( dev-python/python-mpv[${PYTHON_USEDEP}] )
- vlc? ( dev-python/python-vlc[${PYTHON_USEDEP}] )"
+ vlc? ( dev-python/python-vlc[${PYTHON_USEDEP}] )
+"
distutils_enable_tests unittest
python_prepare_all() {
# skip online test
- rm tests/apis/test_spotify_web.py || die
+ rm tests/api/test_spotify_web.py || die
+ rm tests/player/test_external.py || die
- # this needs dbus running
- rm tests/apis/test_mpris.py || die
+ # this needs dbus and a player running
+ rm tests/api/test_mpris.py || die
# fails to parse config for some reason
+ # likely because of the removal of the above tests
rm tests/test_api_and_player_data.py || die
distutils-r1_python_prepare_all
}
+python_test() {
+ virtx "${EPYTHON}" -m unittest discover -v
+}
+
pkg_postinst() {
xdg_pkg_postinst
@@ -53,6 +62,5 @@ pkg_postinst() {
use vlc && elog "If video playback is not working please check 'vidify --debug' for missing-codec-errors and recompile media-video/vlc with the missing codecs"
use mpv && elog "If video playback is not working please check 'vidify --player mpv --debug' for missing-codec-errors and recompile media-video/mpv with the missing codecs"
- optfeature "'vidify --dark-mode'" dev-python/qdarkstyle
optfeature "'vidify --audiosync'" media-video/vidify-audiosync
}
next reply other threads:[~2020-04-01 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 10:12 Andrew Ammerlaan [this message]
2020-04-01 19:38 ` [gentoo-commits] repo/proj/guru:dev commit in: media-video/vidify/ Andrew Ammerlaan
-- strict thread matches above, loose matches on Subject: below --
2020-04-02 10:12 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-04-03 21:37 Haelwenn Monnier
2020-04-07 15:04 Andrew Ammerlaan
2020-04-13 17:50 Andrew Ammerlaan
2020-05-07 11:13 Andrew Ammerlaan
2020-06-30 19:27 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-06-30 19:43 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-08-14 18:20 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-08-14 18:35 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-09-08 13:27 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-09-08 13:27 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-09-24 12:50 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-09-24 13:01 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-02-19 10:14 Michał Górny
2021-05-21 17:08 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2021-05-21 17:21 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
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=1585769908.6575e940f59f1566a87489665b425f980a0d8b4f.andrewammerlaan@gentoo \
--to=andrewammerlaan@riseup.net \
--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