| 1 |
On Tue, 02 Apr 2013 14:32:26 +0200 |
| 2 |
hasufell <hasufell@g.o> wrote: |
| 3 |
|
| 4 |
> On 04/02/2013 02:29 PM, Alexis Ballier wrote: |
| 5 |
> > On Tue, 02 Apr 2013 14:25:43 +0200 |
| 6 |
> > hasufell <hasufell@g.o> wrote: |
| 7 |
> > |
| 8 |
> >> bash-3.1 seems to break ebuild sourcing and is blocked in most |
| 9 |
> >> package managers. So I was wondering how can it still be stable |
| 10 |
> >> then or even in the tree? I'd say mask it with a note that this |
| 11 |
> >> breaks the shit out of gentoo, no matter what PM you use. |
| 12 |
> >> Otherwise, just punt it? |
| 13 |
> >> |
| 14 |
> > |
| 15 |
> > (this is pure speculation and I didn't check) |
| 16 |
> > |
| 17 |
> > isn't it the pivot of some upgrade path like 'update bash to 3.1, |
| 18 |
> > portage to xx.xx, bash to latest, portage to latest' ? |
| 19 |
> > |
| 20 |
> > Alexis. |
| 21 |
> > |
| 22 |
> |
| 23 |
> afair the upgrade path was for 1 year? |
| 24 |
> |
| 25 |
> 3.1 is blocked way longer |
| 26 |
> |
| 27 |
|
| 28 |
but what's the problem with keeping it and not breaking older |
| 29 |
upgrade paths? |
Archives