| 1 |
On Tue, Apr 18, 2017 at 11:16 AM, Jörg Schaible < |
| 2 |
joerg.schaible@×××××××××××.com> wrote: |
| 3 |
|
| 4 |
> Hi Tomas, |
| 5 |
> |
| 6 |
> Tomas Mozes wrote: |
| 7 |
> |
| 8 |
> > On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible < |
| 9 |
> > joerg.schaible@×××××××××××.com> wrote: |
| 10 |
> > |
| 11 |
> >> Hi, |
| 12 |
> >> |
| 13 |
> >> according the logs, gcc 4.5.0-r3 is stable for amd64: |
| 14 |
> >> https://gitweb.gentoo.org/repo/gentoo.git/log/sys-devel/gcc?showmsg=1 |
| 15 |
> >> |
| 16 |
> >> However, after synching the tree, this version is still unstable for me. |
| 17 |
> >> Looking at the packages overview, it becomes even more weird, because |
| 18 |
> >> there seem to be two 4.5.0-r3 versions, one stable for amd64 and one |
| 19 |
> >> unstable: https://packages.gentoo.org/packages/sys-devel/gcc |
| 20 |
> >> |
| 21 |
> >> Can someone shed some light on this? |
| 22 |
> >> |
| 23 |
> >> Cheers, |
| 24 |
> >> Jörg |
| 25 |
> >> |
| 26 |
> >> |
| 27 |
> >> |
| 28 |
> > On which platform do you have it unstable? The packages problem is |
| 29 |
> > probably related to: |
| 30 |
> > https://bugs.gentoo.org/show_bug.cgi?id=612178 |
| 31 |
> |
| 32 |
> Amd64. |
| 33 |
> |
| 34 |
> Yes, it might be the same problem. The ebuild for gcc-4.5.0-r3 on my |
| 35 |
> machine |
| 36 |
> lists amd64 as unstable after synching the tree while the ebuild available |
| 37 |
> over packages.gentoo.org has a stable version in KEYWORDS. |
| 38 |
> |
| 39 |
> Even if some GIT mirrors might be out of sync, it does not explain why |
| 40 |
> https://packages.gentoo.org/packages/sys-devel/gcc lists the same version |
| 41 |
> more than once. |
| 42 |
> |
| 43 |
> Cheers, |
| 44 |
> Jörg |
| 45 |
> |
| 46 |
> |
| 47 |
> |
| 48 |
As mentioned by others, bugs on packages.gentoo.org will not affect your |
| 49 |
portage tree. I've just installed gcc 5.4.0-r3 on amd64, so try syncing |
| 50 |
your portage tree. Don't you have it in your package.mask? |
Archives