Gentoo Archives: gentoo-dev

From: Mart Raudsepp <leio@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: stable gcc 5.4.0 ??
Date: Tue, 18 Apr 2017 09:44:33
Message-Id: 1492508657.18287.1.camel@gentoo.org
In Reply to: [gentoo-dev] Re: stable gcc 5.4.0 ?? by "Jörg Schaible"
1 Ühel kenal päeval, T, 18.04.2017 kell 11:16, kirjutas Jörg Schaible:
2 > Hi Tomas,
3 >
4 > Tomas Mozes wrote:
5 >
6 > > On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible <
7 > > joerg.schaible@×××××××××××.com> wrote:
8 > >
9 > > > Hi,
10 > > >
11 > > > according the logs, gcc 4.5.0-r3 is stable for amd64:
12 > > > https://gitweb.gentoo.org/repo/gentoo.git/log/sys-devel/gcc?showm
13 > > > sg=1
14 > > >
15 > > > However, after synching the tree, this version is still unstable
16 > > > for me.
17 > > > Looking at the packages overview, it becomes even more weird,
18 > > > because
19 > > > there seem to be two 4.5.0-r3 versions, one stable for amd64 and
20 > > > one
21 > > > unstable: https://packages.gentoo.org/packages/sys-devel/gcc
22 > > >
23 > > > Can someone shed some light on this?
24 > > >
25 > > > Cheers,
26 > > > Jörg
27 > > >
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 >
35 > Amd64.
36 >
37 > Yes, it might be the same problem. The ebuild for gcc-4.5.0-r3 on my
38 > machine 
39 > lists amd64 as unstable after synching the tree while the ebuild
40 > available 
41 > over packages.gentoo.org has a stable version in KEYWORDS.
42 >
43 > Even if some GIT mirrors might be out of sync, it does not explain
44 > why 
45 > https://packages.gentoo.org/packages/sys-devel/gcc lists the same
46 > version 
47 > more than once.
48
49 This is a packages.gentoo.org Ruby on Rails webapp bug, and has
50 absolutely nothing to do with some package being stable on an
51 architecture or not. Don't let that disturb you.
52
53
54 Mart

Replies

Subject Author
Re: [gentoo-dev] Re: stable gcc 5.4.0 ?? "M. J. Everitt" <m.j.everitt@×××.org>