public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bash-3.1 stable
Date: Tue, 2 Apr 2013 14:29:33 +0200	[thread overview]
Message-ID: <20130402142933.2e76831c@portable> (raw)
In-Reply-To: <515ACE47.3030206@gentoo.org>

On Tue, 02 Apr 2013 14:25:43 +0200
hasufell <hasufell@gentoo.org> wrote:

> bash-3.1 seems to break ebuild sourcing and is blocked in most package
> managers. So I was wondering how can it still be stable then or even
> in the tree? I'd say mask it with a note that this breaks the shit
> out of gentoo, no matter what PM you use. Otherwise, just punt it?
> 

(this is pure speculation and I didn't check)

isn't it the pivot of some upgrade path  like 'update bash to 3.1,
portage to xx.xx, bash to latest, portage to latest' ?

Alexis.


  reply	other threads:[~2013-04-02 12:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 12:25 [gentoo-dev] bash-3.1 stable hasufell
2013-04-02 12:29 ` Alexis Ballier [this message]
2013-04-02 12:32   ` hasufell
2013-04-02 12:37     ` Alexis Ballier
2013-04-02 12:48       ` Rich Freeman
2013-04-02 13:07         ` Markos Chandras
2013-04-02 13:34           ` Alexis Ballier
2013-04-02 14:01             ` Markos Chandras
2013-04-02 14:11               ` Ciaran McCreesh
2013-04-02 14:21               ` Alexis Ballier
2013-04-02 14:26                 ` Markos Chandras
2013-04-02 14:35                   ` Raymond Jennings
2013-04-02 17:54                     ` [gentoo-dev] " Duncan
2013-04-14 21:51                       ` [gentoo-dev] OT: was " Gregory M. Turner
2013-04-15  9:49                         ` Jeroen Roovers
2013-04-15 16:42                           ` Peter Stuge
2013-04-02 14:39               ` [gentoo-dev] " hasufell
2013-04-02 14:43                 ` Ben Kohler
2013-04-02 13:28 ` Samuli Suominen
2013-04-02 13:33   ` Peter Stuge
2013-04-02 17:40 ` [gentoo-dev] " Mike Frysinger

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=20130402142933.2e76831c@portable \
    --to=aballier@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