public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-tv/mythtv/
Date: Sun, 10 Mar 2024 01:59:17 +0000 (UTC)	[thread overview]
Message-ID: <1710035488.4a787cf93a7d25b8453eaaf71ae84b68486437e3.sam@gentoo> (raw)

commit:     4a787cf93a7d25b8453eaaf71ae84b68486437e3
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 10 01:51:28 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 10 01:51:28 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4a787cf9

media-tv/mythtv: fix DoubleEmptyLine

Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-tv/mythtv/mythtv-33.1-r1.ebuild | 1 -
 1 file changed, 1 deletion(-)

diff --git a/media-tv/mythtv/mythtv-33.1-r1.ebuild b/media-tv/mythtv/mythtv-33.1-r1.ebuild
index d0d9cd8758c6..f2564d87e018 100644
--- a/media-tv/mythtv/mythtv-33.1-r1.ebuild
+++ b/media-tv/mythtv/mythtv-33.1-r1.ebuild
@@ -168,7 +168,6 @@ src_prepare() {
 	# https://bugs.gentoo.org/888291
 	eapply -p2 "${FILESDIR}"/${PN}-33.1-python3.12.patch
 
-
 	# Perl bits need to go into vendor_perl and not site_perl
 	sed -e "s:pure_install:pure_install INSTALLDIRS=vendor:" \
 		-i "${S}"/bindings/perl/Makefile || die "Cannot convert site_perl to vendor_perl!"


             reply	other threads:[~2024-03-10  1:59 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10  1:59 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-06  9:24 [gentoo-commits] repo/gentoo:master commit in: media-tv/mythtv/ Miroslav Šulc
2024-09-03  8:07 Miroslav Šulc
2024-07-30 19:01 Pacho Ramos
2024-02-02 19:41 Sam James
2023-05-27 15:29 Sam James
2023-05-01  9:53 Sam James
2023-04-17  1:25 Matt Turner
2022-07-15  7:58 David Seifert
2022-04-27 14:00 Joonas Niilola
2022-04-27 13:19 Joonas Niilola
2022-04-15  5:28 Sam James
2022-04-15  5:27 Sam James
2022-04-12  1:13 Sam James
2022-04-12  1:13 Sam James
2022-04-10 23:01 Sam James
2021-10-31  0:19 Sam James
2021-08-10 16:22 Joonas Niilola
2021-08-10 16:22 Joonas Niilola
2021-08-10 16:22 Joonas Niilola
2021-06-10 19:05 Sam James
2021-04-20 13:30 Joonas Niilola
2021-03-02  5:42 Joonas Niilola
2021-03-01 17:41 Joonas Niilola
2020-09-04 16:34 Andreas Sturmlechner
2020-09-04 16:34 Andreas Sturmlechner
2020-08-01 22:24 Aaron Bauman
2020-07-24 12:03 Joonas Niilola
2020-07-04  9:20 Michał Górny
2020-06-14 10:29 Joonas Niilola
2020-06-11  8:03 Joonas Niilola
2020-04-03 16:55 Andreas Sturmlechner
2020-03-03 14:54 Joonas Niilola
2020-02-21  6:08 Joonas Niilola
2020-02-19  7:34 Joonas Niilola
2019-10-12 21:22 Andreas Sturmlechner
2019-10-09  3:07 Joonas Niilola
2019-10-09  3:07 Joonas Niilola
2019-10-09  3:07 Joonas Niilola
2019-01-27 19:46 Pacho Ramos
2019-01-05 13:24 Pacho Ramos
2018-10-20 16:36 Pacho Ramos
2018-06-26 21:07 Lars Wendler
2017-12-31 20:33 Pacho Ramos
2017-12-27 14:18 Pacho Ramos
2017-12-27 14:18 Pacho Ramos
2017-12-18 22:36 Craig Andrews
2017-08-11 15:43 Andreas Sturmlechner
2017-07-24  8:51 Pacho Ramos
2017-07-22  0:23 Andreas Sturmlechner
2017-07-22  0:23 Andreas Sturmlechner
2017-07-22  0:23 Andreas Sturmlechner
2017-03-12 23:19 Michael Palimaka
2017-01-08 13:12 Aaron Bauman
2016-12-05 14:24 Pacho Ramos
2016-10-02 12:37 Pacho Ramos
2016-10-02 12:37 Pacho Ramos
2016-04-19 11:25 Richard Freeman
2016-04-17 21:42 Richard Freeman
2016-04-17  0:13 Richard Freeman
2016-03-20  3:41 Doug Goldstein
2016-03-20  0:58 Doug Goldstein
2016-01-29 12:19 Richard Freeman
2015-11-15  4:37 Doug Goldstein
2015-10-27 20:25 Manuel Rüger
2015-10-27 14:21 Doug Goldstein
2015-09-17 14:07 Doug Goldstein
2015-09-13 15:11 Doug Goldstein
2015-09-09  3:27 Doug Goldstein
2015-08-10 13:17 Doug Goldstein

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=1710035488.4a787cf93a7d25b8453eaaf71ae84b68486437e3.sam@gentoo \
    --to=sam@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