1 |
On 18/04/17 10:44, Mart Raudsepp wrote: |
2 |
> Ühel kenal päeval, T, 18.04.2017 kell 11:16, kirjutas Jörg Schaible: |
3 |
>> Hi Tomas, |
4 |
>> |
5 |
>> Tomas Mozes wrote: |
6 |
>> |
7 |
>>> On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible < |
8 |
>>> joerg.schaible@×××××××××××.com> wrote: |
9 |
>>> |
10 |
>>>> Hi, |
11 |
>>>> |
12 |
>>>> according the logs, gcc 4.5.0-r3 is stable for amd64: |
13 |
>>>> https://gitweb.gentoo.org/repo/gentoo.git/log/sys-devel/gcc?showm |
14 |
>>>> sg=1 |
15 |
>>>> |
16 |
>>>> However, after synching the tree, this version is still unstable |
17 |
>>>> for me. |
18 |
>>>> Looking at the packages overview, it becomes even more weird, |
19 |
>>>> because |
20 |
>>>> there seem to be two 4.5.0-r3 versions, one stable for amd64 and |
21 |
>>>> one |
22 |
>>>> unstable: https://packages.gentoo.org/packages/sys-devel/gcc |
23 |
>>>> |
24 |
>>>> Can someone shed some light on this? |
25 |
>>>> |
26 |
>>>> Cheers, |
27 |
>>>> Jörg |
28 |
>>>> |
29 |
>>>> |
30 |
>>>> |
31 |
>>> On which platform do you have it unstable? The packages problem is |
32 |
>>> probably related to: |
33 |
>>> https://bugs.gentoo.org/show_bug.cgi?id=612178 |
34 |
>> Amd64. |
35 |
>> |
36 |
>> Yes, it might be the same problem. The ebuild for gcc-4.5.0-r3 on my |
37 |
>> machine |
38 |
>> lists amd64 as unstable after synching the tree while the ebuild |
39 |
>> available |
40 |
>> over packages.gentoo.org has a stable version in KEYWORDS. |
41 |
>> |
42 |
>> Even if some GIT mirrors might be out of sync, it does not explain |
43 |
>> why |
44 |
>> https://packages.gentoo.org/packages/sys-devel/gcc lists the same |
45 |
>> version |
46 |
>> more than once. |
47 |
> This is a packages.gentoo.org Ruby on Rails webapp bug, and has |
48 |
> absolutely nothing to do with some package being stable on an |
49 |
> architecture or not. Don't let that disturb you. |
50 |
> |
51 |
> |
52 |
> Mart |
53 |
> |
54 |
+1 |
55 |
|
56 |
CONFIRMED but fix unknown at present. Gcc is /not/ the only package that |
57 |
is affected by the Ruby-on-Rails bug. |
58 |
|
59 |
RESOLVED:DUPLICATE :] |