public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/zbar/
Date: Sun, 17 May 2020 16:42:09 +0000 (UTC)	[thread overview]
Message-ID: <1589733711.7da97a920351fe66ee3fad7264817341342334e6.juippis@gentoo> (raw)

commit:     7da97a920351fe66ee3fad7264817341342334e6
Author:     Yury Martynov <email <AT> linxon <DOT> ru>
AuthorDate: Sun May 10 05:47:41 2020 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Sun May 17 16:41:51 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7da97a92

media-gfx/zbar: 0.23.1 configure fails with /bin/sh != bash

Closes: https://bugs.gentoo.org/721370
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Yury Martynov <email <AT> linxon.ru>
Closes: https://github.com/gentoo/gentoo/pull/15735
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 media-gfx/zbar/zbar-0.23.1.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/media-gfx/zbar/zbar-0.23.1.ebuild b/media-gfx/zbar/zbar-0.23.1.ebuild
index c284e6b7e98..79c9d2c02b8 100644
--- a/media-gfx/zbar/zbar-0.23.1.ebuild
+++ b/media-gfx/zbar/zbar-0.23.1.ebuild
@@ -193,6 +193,8 @@ multilib_src_configure() {
 		use test && myeconfargs+=( --without-zbarimg-tests )
 	fi
 
+	# use bash (bug 721370)
+	CONFIG_SHELL='/bin/bash' \
 	ECONF_SOURCE="${S}" \
 		econf "${myeconfargs[@]}"
 


             reply	other threads:[~2020-05-17 16:42 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 16:42 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-07 19:12 [gentoo-commits] repo/gentoo:master commit in: media-gfx/zbar/ Andreas Sturmlechner
2024-09-22  4:50 Sam James
2024-09-22  4:50 Sam James
2023-09-29 13:04 Arthur Zamarin
2023-04-12  1:50 Sam James
2023-04-11 19:05 Arthur Zamarin
2022-08-02 10:13 Joonas Niilola
2022-04-11  6:35 Jakov Smolić
2022-04-11  6:35 Jakov Smolić
2021-04-06 21:17 Sam James
2021-02-21 20:23 Sam James
2021-02-21 20:23 Sam James
2021-02-21 12:14 David Seifert
2020-12-13 10:34 Sam James
2020-02-24 18:07 Andreas Sturmlechner
2020-02-24 16:25 Agostino Sarubbo
2020-02-21  9:37 Agostino Sarubbo
2020-02-09 16:29 Michał Górny
2020-02-03 17:37 Andreas Sturmlechner
2019-02-12  9:39 Mikle Kolyada
2019-02-12  9:39 Mikle Kolyada
2019-02-12  9:39 Mikle Kolyada
2019-01-12 10:59 Pacho Ramos
2018-12-29 13:37 Andreas Sturmlechner
2018-12-29  9:16 Mikle Kolyada
2018-12-22 22:25 Thomas Deutschmann
2018-12-05 12:49 Louis Sautier
2018-12-05  9:53 Louis Sautier
2018-12-05  8:19 Louis Sautier
2018-11-25 17:36 Andreas Sturmlechner
2018-05-10 10:08 Andreas Sturmlechner
2018-05-10 10:08 Andreas Sturmlechner
2018-02-06 16:24 Thomas Deutschmann
2017-12-19 10:38 Jason Zaman
2017-12-18 10:37 Michael Weber
2017-12-18  9:52 Michael Weber
2017-12-18  9:19 Michael Weber
2017-09-07 20:31 Michał Górny
2017-09-07 20:31 Michał Górny
2017-09-07 20:31 Michał Górny
2017-09-07 20:31 Michał Górny
2017-09-07 20:31 Michał Górny
2017-09-07 20:31 Michał Górny
2016-09-07  6:36 Andrew Savchenko
2015-08-10 23:16 Michael Weber

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=1589733711.7da97a920351fe66ee3fad7264817341342334e6.juippis@gentoo \
    --to=juippis@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