From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: dlan@gentoo.org
Subject: Re: [gentoo-dev] [Fwd: [gentoo-automated-testing] BROKEN: repository became broken!]
Date: Mon, 1 Feb 2016 15:30:41 -0500 [thread overview]
Message-ID: <20160201203041.GN7732@vapier.lan> (raw)
In-Reply-To: <20160201185501.GB28175@ultrachro.me>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On 01 Feb 2016 19:55, Patrice Clement wrote:
> > New issues:
> > https://qa-reports.gentoo.org/output/gentoo-ci/780f65b/output.html#dev-libs/efl
>
> This commit is breaking the tree:
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97a6aec
>
> I did try to work around the issue you've introduced when but the enlightenment
> eclasses are a bit of mystery to me and I eventually gave up.
>
> Could you revert this commit and fix this issue?
the issue is that efl-1.15.2 is marked stable for alpha/ia64/sparc, and
it depends on app-i18n/ibus, but commit 97a6aec deleted the only ibus
ebuild that was marked stable for those arches.
it can be fixed in a few ways (i'm listing in order of preference):
(1) mark a newer ibus stable
(2) revert that commit to re-add the old stable ebuilds
(3) add USE=ibus to package.use.stable.mask for these arches
(4) degrade all packages for these arches to unstable
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-01 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 18:55 [gentoo-dev] [Fwd: [gentoo-automated-testing] BROKEN: repository became broken!] Patrice Clement
2016-02-01 20:30 ` Mike Frysinger [this message]
2016-02-01 21:16 ` Andreas K. Huettel
2016-02-02 1:33 ` Mike Frysinger
2016-02-03 21:35 ` Andreas K. Huettel
2016-02-09 19:30 ` Mike Frysinger
2016-03-03 20:51 ` Raymond Jennings
2016-02-02 1:50 ` Yixun Lan
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=20160201203041.GN7732@vapier.lan \
--to=vapier@gentoo.org \
--cc=dlan@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