public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/cmusfm/
Date: Sat, 19 Jun 2021 08:24:54 +0000 (UTC)	[thread overview]
Message-ID: <1624091072.1f2f15ef2177725914831748d7355e19c016d15d.fordfrog@gentoo> (raw)

commit:     1f2f15ef2177725914831748d7355e19c016d15d
Author:     Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 19 08:24:32 2021 +0000
Commit:     Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Sat Jun 19 08:24:32 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f2f15ef

media-sound/cmusfm: bump to 0.4.0, dropped 0.3.3 due to api change

Closes: https://bugs.gentoo.org/792447
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>

 media-sound/cmusfm/Manifest                                     | 2 +-
 media-sound/cmusfm/{cmusfm-0.3.3.ebuild => cmusfm-0.4.0.ebuild} | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/media-sound/cmusfm/Manifest b/media-sound/cmusfm/Manifest
index ea606266f13..aa4b36bd0a3 100644
--- a/media-sound/cmusfm/Manifest
+++ b/media-sound/cmusfm/Manifest
@@ -1 +1 @@
-DIST cmusfm-0.3.3.tar.gz 37553 BLAKE2B f266d83edbed960d8c466cba80ce57d645c5c9cdfceac27c29d0ef424c8135f22377dc0490462d3107dfcfd32ac9d15fa6142269b453c8a80818da9bd10a28fd SHA512 6537905bdf09d04f09783237997536a1ee231ee4e589826d87f435c0dd7542dbd7d97167990bf949d2a9eb73c4a9a4da1bab17888de0aecedb2a63deaa873f39
+DIST cmusfm-0.4.0.tar.gz 41451 BLAKE2B 02fe95079b902c23b594d25c93e99da4ff9a62437a3edb0ff0812db6d490a6320da5e6b5387aa49a55490b02c17b7982d48b3d773687ccffa5d85adee6b54aeb SHA512 dba2ca51953186ca21bd5074367da21c74a371b1ae7578cc851badf3f225274bfe7f3e5f5d7a322c50be9d839af2568339d10fae2d402548e5246a11f6acf9ae

diff --git a/media-sound/cmusfm/cmusfm-0.3.3.ebuild b/media-sound/cmusfm/cmusfm-0.4.0.ebuild
similarity index 95%
rename from media-sound/cmusfm/cmusfm-0.3.3.ebuild
rename to media-sound/cmusfm/cmusfm-0.4.0.ebuild
index 83f80380a2a..b2cac96f9c3 100644
--- a/media-sound/cmusfm/cmusfm-0.3.3.ebuild
+++ b/media-sound/cmusfm/cmusfm-0.4.0.ebuild
@@ -17,7 +17,7 @@ IUSE="libnotify"
 DEPEND="
 	net-misc/curl
 	dev-libs/openssl:0=
-	libnotify? ( >=x11-libs/libnotify-0.7 )
+	libnotify? ( x11-libs/libnotify )
 "
 RDEPEND="
 	${DEPEND}


             reply	other threads:[~2021-06-19  8:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19  8:24 Miroslav Šulc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-10  6:19 [gentoo-commits] repo/gentoo:master commit in: media-sound/cmusfm/ Miroslav Šulc
2023-08-10  2:50 Sam James
2023-08-09 19:14 Sam James
2023-07-10  6:02 Miroslav Šulc
2023-06-03  3:23 Sam James
2021-09-24  6:45 Miroslav Šulc
2021-09-22  6:58 Agostino Sarubbo
2021-09-21  6:35 Agostino Sarubbo
2021-08-05 14:08 Sam James
2021-08-04 18:42 Agostino Sarubbo
2021-08-04  4:49 Miroslav Šulc
2020-11-14 15:06 David Seifert
2019-01-07 19:15 Lars Wendler
2018-05-05 20:51 Aaron Bauman
2017-06-20 12:37 Pacho Ramos
2016-08-22  2:46 Tim Harder

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=1624091072.1f2f15ef2177725914831748d7355e19c016d15d.fordfrog@gentoo \
    --to=fordfrog@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