From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/xnee/
Date: Wed, 29 Jan 2020 12:20:48 +0000 (UTC) [thread overview]
Message-ID: <1580300447.7d32f5c45d63ea43b2f7f13b9a346846be762063.jer@gentoo> (raw)
commit: 7d32f5c45d63ea43b2f7f13b9a346846be762063
Author: Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 29 12:16:47 2020 +0000
Commit: Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Wed Jan 29 12:20:47 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7d32f5c4
x11-misc/xnee: Prune libtool files
Subject: "BROKEN: repository became broken!"
Looks like someone just broke Gentoo!
Fix this by fixing Gentoo.
Package-Manager: Portage-2.3.86, Repoman-2.3.20
Toxicity-level: you could start by getting jer to fix his crap instead of ignoring ci mail
Signed-off-by: Jeroen Roovers <jer <AT> gentoo.org>
x11-misc/xnee/xnee-3.19-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-misc/xnee/xnee-3.19-r1.ebuild b/x11-misc/xnee/xnee-3.19-r1.ebuild
index 7b673eb0484..0d71add730d 100644
--- a/x11-misc/xnee/xnee-3.19-r1.ebuild
+++ b/x11-misc/xnee/xnee-3.19-r1.ebuild
@@ -69,5 +69,5 @@ src_install() {
default
dodoc AUTHORS BUGS ChangeLog FAQ NEWS README TODO
use gnome && make_desktop_entry gnee Gnee ${PN} "Utility;GTK"
- use static-libs || rm -f "${ED}"usr/lib*/lib*.la
+ find "${ED}" -name '*.la' -delete || die
}
next reply other threads:[~2020-01-29 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 12:20 Jeroen Roovers [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-18 2:18 [gentoo-commits] repo/gentoo:master commit in: x11-misc/xnee/ Sam James
2022-02-14 22:02 Jonas Stein
2021-04-01 21:17 Sam James
2020-07-02 7:21 Andreas Sturmlechner
2020-01-29 11:32 Jeroen Roovers
2017-02-11 19:47 David Seifert
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=1580300447.7d32f5c45d63ea43b2f7f13b9a346846be762063.jer@gentoo \
--to=jer@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