public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org, dlan@gentoo.org
Subject: Re: [gentoo-dev] [Fwd: [gentoo-automated-testing] BROKEN: repository became broken!]
Date: Mon, 1 Feb 2016 22:16:53 +0100	[thread overview]
Message-ID: <201602012216.54035.dilfridge@gentoo.org> (raw)
In-Reply-To: <20160201203041.GN7732@vapier.lan>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Am Montag, 1. Februar 2016, 21:30:41 schrieb Mike Frysinger:
> 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

I took the liberty of doing (2) and reverted the commit. Not sure why this 
needs so much discussion; after all a broken tree is always suboptimal.

Now there's lots of time to come up with a better solution.


- -- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1

iQJ8BAEBCgBmBQJWr8tFXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDMjhGQ0IwRjdCRUQxMzdBQUNCMDJEODlB
NDRDRjM3M0U3RUU5OUU0AAoJEKRM83Pn7pnk2RcP/jQFF5qb1Cftus7TRXQ71xsm
xJh6cpmivsVYv0c1I1edtAyMCObWJ+Fs75nlQIRTx/hB3oFdEmLtzmdj9riPQ62M
2y3yWiGSCyey07AieIQlaOREbuBe7lBiXM0VwFAzEc2YACvaL7L/oMF/TeKVs/mD
TI31OZYztuR7/1RBevF5q+occx+mboDouMJqHEn/3dr0zVY8mo480T0CNZxsXJhT
A+zNPXa9rKM6EPcqKR41QBWXXy8rGn4gt7+zPwLc7jVZaWmNBpRWwaX95kQYkyiT
P1qYOhpsC/QMA89pGwBwC4fRVEsarX1tYaxjr6rjzQb8jTrjAeqN+ieZhg7VWxBq
+icdhwHodTtB7XepWOdGeuO+ykc+a8syShUi++8GxhOM4R42u+8j12+wGRgOcyaW
Yf9OFm4riM6LN24Fw2LdGYkyVVIR2OeG5j+ABxXFcivTSc99fxc0MywlMhACzdqg
a56nyGPekCeiGIdIno6yfC98aItGLGVFwU1XhcTC2FXBsOKA9nrs9ZYMKHzraqU/
d0G9wCz9TiRgdbuzakuHYK1MrxOnWBLpXmfdaVGf0llIquQ8phLgZbvITkMc8Q+W
xMH7Dt9plBud0OlK/VNy/SC+F/nTX9VqbEnk0gZ5h+OMebJ1olaF1e7Lk6Rlgkp3
Xvxps+yqU6pDuSQoxEkU
=S77D
-----END PGP SIGNATURE-----


  reply	other threads:[~2016-02-01 21:17 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
2016-02-01 21:16   ` Andreas K. Huettel [this message]
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=201602012216.54035.dilfridge@gentoo.org \
    --to=dilfridge@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