public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Importance of SLOTs on Java dependencies
Date: Wed, 15 Apr 2015 17:31:00 -0400	[thread overview]
Message-ID: <552ED894.2060102@gentoo.org> (raw)
In-Reply-To: <552ED84F.5060507@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 15/04/15 05:29 PM, Ian Stakenvicius wrote:
> On 15/04/15 05:27 PM, James Le Cuirot wrote:
>> On Sat, 11 Apr 2015 12:29:11 +0200 "Andreas K. Huettel" 
>> <dilfridge@gentoo.org> wrote:
>>> Sounds good to me (as long as repoman agrees :).
> 
>> Turns out it doesn't agree.
> 
>> RepoMan scours the neighborhood... KEYWORDS.stable [fatal]
>> 1 dev-embedded/arduino/arduino-1.0.5-r1.ebuild added with stable 
>> keywords: amd64 x86
> 
>> What are my options? Force it? :/
> 
> 
> If you're revbumping to introduce a necessary dependency change
> for VDB cleanup, and otherwise the package will be unchanged and
> will still work as it did before, you can force a direct-to-stable
> commit.
> 
> 

Note that you should probably drop the previous ebuild at the same
time, if you haven't already.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAlUu2JQACgkQ2ugaI38ACPAdkQD/ak+swM4hy6qMfaoZSatV+SyJ
UtqtZrYgbHuGCHOL2PMA/jYyutVeesbWS79MwKzGR3qgQi43LLIxgA7JV62Xzlad
=4eJB
-----END PGP SIGNATURE-----


  reply	other threads:[~2015-04-15 21:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 21:27 [gentoo-dev] Importance of SLOTs on Java dependencies James Le Cuirot
2015-04-15 21:29 ` Ian Stakenvicius
2015-04-15 21:31   ` Ian Stakenvicius [this message]
2015-04-16  5:27 ` Michał Górny
2015-04-16 23:09   ` James Le Cuirot
  -- strict thread matches above, loose matches on Subject: below --
2015-04-05 16:16 James Le Cuirot
2015-04-05 16:23 ` Andreas K. Huettel
2015-04-07 18:41 ` Pacho Ramos
2015-04-08 15:10   ` Patrice Clement
2015-04-08 15:25     ` James Le Cuirot

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=552ED894.2060102@gentoo.org \
    --to=axs@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