From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Fwd: [gentoo-commits] repo/gentoo:master commit in: dev-libs/elfutils/
Date: Sat, 06 Apr 2019 17:31:17 +0200 [thread overview]
Message-ID: <2092560.o4ugfyOGuR@pinacolada> (raw)
[-- Attachment #1: Type: text/plain, Size: 2323 bytes --]
Public service announcement: Calling for stabilization requires maintainer
acknowledgment.
While there may be parts of Gentoo where this requirement is seen a bit more
loosely, it is definitely true for TOOLCHAIN and BASE-SYSTEM.
Cheers,
Andreas
---------- Weitergeleitete Nachricht ----------
Betreff: [gentoo-commits] repo/gentoo:master commit in: dev-libs/elfutils/
Datum: Samstag, 6. April 2019, 17:25:11 CEST
Von: Andreas K. Hüttel <dilfridge@gentoo.org>
An: gentoo-commits@lists.gentoo.org
commit: 7ef6ada6d119ed6afccc9d6fb2006bc3e2814b40
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 6 15:23:54 2019 +0000
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sat Apr 6 15:24:59 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7ef6ada6
dev-libs/elfutils: Undo stabilization of 0.176
Stabilization was initiated without acknowledgment by toolchain
The result of the stabilization is a configuration in stable that is
unable to build the kernel, see bug 671760.
Bug: https://bugs.gentoo.org/676794
Bug: https://bugs.gentoo.org/671760
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
dev-libs/elfutils/elfutils-0.176.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/elfutils/elfutils-0.176.ebuild b/dev-libs/elfutils/
elfutils-0.176.ebuild
index 1c62b617a25..4c75e71b437 100644
--- a/dev-libs/elfutils/elfutils-0.176.ebuild
+++ b/dev-libs/elfutils/elfutils-0.176.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://sourceware.org/elfutils/ftp/${PV}/$
{P}.tar.bz2"
LICENSE="|| ( GPL-2+ LGPL-3+ ) utils? ( GPL-3+ )"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390
~sh sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390
~sh ~sparc ~x86 ~amd64-linux ~x86-linux"
IUSE="bzip2 lzma nls static-libs test +threads +utils"
RDEPEND=">=sys-libs/zlib-1.2.8-r1[${MULTILIB_USEDEP}]
-------------------------------------------------------------
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next reply other threads:[~2019-04-06 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 15:31 Andreas K. Huettel [this message]
2019-04-07 19:26 ` [gentoo-dev] Fwd: [gentoo-commits] repo/gentoo:master commit in: dev-libs/elfutils/ Matt Turner
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=2092560.o4ugfyOGuR@pinacolada \
--to=dilfridge@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