From: "Alexandre Rostovtsev" <tetromino@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/gnote/
Date: Sun, 19 Jun 2016 20:46:53 +0000 (UTC) [thread overview]
Message-ID: <1466369131.5f8551642b77435b0b2580e90ade514d328c2120.tetromino@gentoo> (raw)
commit: 5f8551642b77435b0b2580e90ade514d328c2120
Author: Alexandre Rostovtsev <tetromino <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 19 20:45:31 2016 +0000
Commit: Alexandre Rostovtsev <tetromino <AT> gentoo <DOT> org>
CommitDate: Sun Jun 19 20:45:31 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5f855164
app-misc/gnote: fix aclocal error (bug #581308)
Thanks to Ed Catmur for reporting and the fix.
Package-Manager: portage-2.3.0_rc1
app-misc/gnote/gnote-3.18.1.ebuild | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/app-misc/gnote/gnote-3.18.1.ebuild b/app-misc/gnote/gnote-3.18.1.ebuild
index 7aa6fe3..e0afcb2 100644
--- a/app-misc/gnote/gnote-3.18.1.ebuild
+++ b/app-misc/gnote/gnote-3.18.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
@@ -49,6 +49,10 @@ src_prepare() {
# Do not alter CFLAGS
sed 's/-DDEBUG -g/-DDEBUG/' -i configure.ac configure || die
+ # Prevent m4_copy error when running aclocal, bug #581308
+ # m4_copy: won't overwrite defined macro: glib_DEFUN
+ rm m4/glib-gettext.m4 || die
+
eautoreconf
gnome2_src_prepare
next reply other threads:[~2016-06-19 20:46 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 20:46 Alexandre Rostovtsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-30 7:15 [gentoo-commits] repo/gentoo:master commit in: app-misc/gnote/ Pacho Ramos
2024-07-16 8:48 Pacho Ramos
2024-07-16 8:48 Pacho Ramos
2024-07-16 8:48 Pacho Ramos
2024-05-06 7:09 Mart Raudsepp
2024-04-28 19:11 Ionen Wolkens
2024-04-01 20:53 Mart Raudsepp
2024-04-01 20:53 Mart Raudsepp
2024-03-09 23:15 Mart Raudsepp
2023-10-08 11:51 Pacho Ramos
2023-10-08 11:51 Pacho Ramos
2023-09-17 22:27 Matt Turner
2023-09-10 23:48 Matt Turner
2023-07-21 22:55 Matt Turner
2023-05-06 11:34 Sam James
2023-05-02 18:23 Arthur Zamarin
2023-05-02 18:23 Arthur Zamarin
2023-03-19 23:38 Matt Turner
2023-02-06 2:40 Matt Turner
2022-10-29 23:25 Matt Turner
2022-10-29 22:33 Matt Turner
2022-10-06 2:03 Matt Turner
2022-09-01 2:25 Matt Turner
2022-04-03 18:45 Matt Turner
2021-12-21 3:39 Yixun Lan
2021-06-26 1:34 Sam James
2021-06-15 19:33 Matt Turner
2021-05-02 15:01 Matt Turner
2021-04-12 21:59 Matt Turner
2021-04-12 21:59 Matt Turner
2021-01-31 17:54 Mart Raudsepp
2020-07-15 9:05 Mart Raudsepp
2020-07-04 15:07 Mart Raudsepp
2020-06-02 22:21 Mart Raudsepp
2019-05-18 19:59 Mart Raudsepp
2018-11-19 15:58 Gilles Dartiguelongue
2018-01-27 9:38 Mart Raudsepp
2018-01-18 1:49 Mikle Kolyada
2017-08-27 17:57 Gilles Dartiguelongue
2017-08-09 22:58 Gilles Dartiguelongue
2017-04-02 13:03 Mart Raudsepp
2017-02-15 16:57 Mart Raudsepp
2017-01-04 22:37 Gilles Dartiguelongue
2016-10-19 22:02 Gilles Dartiguelongue
2016-10-08 9:51 Pacho Ramos
2016-06-24 20:44 Pacho Ramos
2016-06-24 20:44 Pacho Ramos
2015-09-07 16:24 Mikle Kolyada
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=1466369131.5f8551642b77435b0b2580e90ade514d328c2120.tetromino@gentoo \
--to=tetromino@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