public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Patrick Lauer" <patrick@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/gnome-sound-recorder/
Date: Sat, 16 Sep 2017 18:13:32 +0000 (UTC)	[thread overview]
Message-ID: <1505585518.e8739ab2c82c5ca5f77f74179905ded1bf4d45a2.patrick@gentoo> (raw)

commit:     e8739ab2c82c5ca5f77f74179905ded1bf4d45a2
Author:     Patrick Lauer <patrick <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 16 18:11:58 2017 +0000
Commit:     Patrick Lauer <patrick <AT> gentoo <DOT> org>
CommitDate: Sat Sep 16 18:11:58 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e8739ab2

media-sound/gnome-sound-recorder: Whitespace

Package-Manager: Portage-2.3.8, Repoman-2.3.3

 .../gnome-sound-recorder/gnome-sound-recorder-3.24.0.1.ebuild  | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/media-sound/gnome-sound-recorder/gnome-sound-recorder-3.24.0.1.ebuild b/media-sound/gnome-sound-recorder/gnome-sound-recorder-3.24.0.1.ebuild
index 461f3c7fefe..363941236b1 100644
--- a/media-sound/gnome-sound-recorder/gnome-sound-recorder-3.24.0.1.ebuild
+++ b/media-sound/gnome-sound-recorder/gnome-sound-recorder-3.24.0.1.ebuild
@@ -36,9 +36,9 @@ DEPEND="${COMMON_DEPEND}
 src_prepare() {
 	gnome2_src_prepare
 
-    # FIXME: upstream should provide a way to set GST_INSPECT, bug #358755 & co.
-    # gst-inspect causes sandbox violations when a plugin needs write access to
-    # /dev/dri/card* in its init phase.
-    sed -e "s|\(gst10_inspect=\).*|\1$(type -P true)|" \
-        -i configure || die
+	# FIXME: upstream should provide a way to set GST_INSPECT, bug #358755 & co.
+	# gst-inspect causes sandbox violations when a plugin needs write access to
+	# /dev/dri/card* in its init phase.
+	sed -e "s|\(gst10_inspect=\).*|\1$(type -P true)|" \
+		-i configure || die
 }


             reply	other threads:[~2017-09-16 18:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-16 18:13 Patrick Lauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-11 21:27 [gentoo-commits] repo/gentoo:master commit in: media-sound/gnome-sound-recorder/ Mart Raudsepp
2023-07-19  3:24 Matt Turner
2022-10-29 17:44 Matt Turner
2022-05-28  1:27 Sam James
2022-05-28  1:20 Sam James
2022-03-26  0:23 Matt Turner
2022-01-25  0:51 Sam James
2021-06-26  1:34 Sam James
2021-05-29  9:02 Sam James
2021-05-29  6:09 Sam James
2021-04-16 20:58 Matt Turner
2021-04-13 16:12 Matt Turner
2021-04-01 16:44 Thomas Deutschmann
2021-03-12  8:01 Mikle Kolyada
2021-01-31 12:28 Mart Raudsepp
2020-04-25 20:17 Mart Raudsepp
2020-04-12 11:26 Mart Raudsepp
2019-05-18 23:05 Mart Raudsepp
2019-03-31  6:10 Mart Raudsepp
2019-01-12 10:59 Pacho Ramos
2018-09-30  0:19 Mart Raudsepp
2018-02-03 23:00 Mart Raudsepp
2018-01-27  0:41 Thomas Deutschmann
2018-01-18  2:40 Mikle Kolyada
2017-08-12 23:15 Gilles Dartiguelongue
2016-10-23 23:01 Gilles Dartiguelongue
2016-10-23 23:01 Gilles Dartiguelongue
2016-07-02 17:12 Pacho Ramos
2016-07-02 17:12 Pacho Ramos
2016-03-06 20:36 Mikle Kolyada
2015-12-29 12:08 Pacho Ramos
2015-11-09 10:22 Pacho Ramos
2015-09-07 21:55 Mikle Kolyada
2015-09-06 20:55 Pacho Ramos

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=1505585518.e8739ab2c82c5ca5f77f74179905ded1bf4d45a2.patrick@gentoo \
    --to=patrick@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