Dnia 18 kwietnia 2017 23:31:31 CEST, James Le Cuirot
napisał(a):
>On Tue, 18 Apr 2017 08:08:44 +0200
>Michał Górny wrote:
>
>> On pon, 2017-04-17 at 22:53 +0100, James Le Cuirot wrote:
>> > diff --git a/eclass/cdrom.eclass b/eclass/cdrom.eclass
>> > index 41488d2446c2..de72f15563db 100644
>> > -
On Tue, 18 Apr 2017 08:08:44 +0200
Michał Górny wrote:
> On pon, 2017-04-17 at 22:53 +0100, James Le Cuirot wrote:
> > diff --git a/eclass/cdrom.eclass b/eclass/cdrom.eclass
> > index 41488d2446c2..de72f15563db 100644
> > --- a/eclass/cdrom.eclass
> > +++ b/eclass/cdrom.eclass
> > @@ -79,12 +79,1
On Tue, 18 Apr 2017 07:51:58 +0200
Ulrich Mueller wrote:
> > On Mon, 17 Apr 2017, James Le Cuirot wrote:
>
> > If you've been wondering why I've been quiet of late (you have,
> > right?!) then this is partly why. I'm not sure why I spent so long
> > on an eclass that hardly anyone uses but
On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible <
joerg.schai...@bpm-inspire.com> wrote:
> Hi,
>
> according the logs, gcc 4.5.0-r3 is stable for amd64:
> https://gitweb.gentoo.org/repo/gentoo.git/log/sys-devel/gcc?showmsg=1
>
> However, after synching the tree, this version is still unstable for
On Tue, Apr 18, 2017 at 3:12 PM, Jörg Schaible <
joerg.schai...@bpm-inspire.com> wrote:
> Tomas Mozes wrote:
>
> [snip]
>
> > As mentioned by others, bugs on packages.gentoo.org will not affect your
> > portage tree. I've just installed gcc 5.4.0-r3 on amd64, so try syncing
> > your portage tree.
James Le Cuirot wrote:
> On Tue, 18 Apr 2017 15:12:13 +0200
> Jörg Schaible wrote:
>
>> As said, I synced the tree twice this morning (4 hours ago) and the
>> KEYWORDS in the ebuild do not declare amd64 as stable although it was
>> committed to GIT already yesterday. And this is no wonder, becau
On Mon, Apr 17, 2017 at 7:07 AM, Michał Górny wrote:
> ---
> eclass/chromium.eclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/eclass/chromium.eclass b/eclass/chromium.eclass
> index 5f8c53cabf35..fcc02dd6e028 100644
> --- a/eclass/chromium.eclass
> +++ b/eclass/chro
On 2017-04-18 14:27, James Le Cuirot wrote:
> On Tue, 18 Apr 2017 15:12:13 +0200
> Jörg Schaible wrote:
>
> > As said, I synced the tree twice this morning (4 hours ago) and the
> > KEYWORDS in the ebuild do not declare amd64 as stable although it was
> > committed to GIT already yesterday. And t
On Tue, 18 Apr 2017 15:12:13 +0200
Jörg Schaible wrote:
> As said, I synced the tree twice this morning (4 hours ago) and the
> KEYWORDS in the ebuild do not declare amd64 as stable although it was
> committed to GIT already yesterday. And this is no wonder, because
> the stable branch of the GIT
Tomas Mozes wrote:
[snip]
> As mentioned by others, bugs on packages.gentoo.org will not affect your
> portage tree. I've just installed gcc 5.4.0-r3 on amd64, so try syncing
> your portage tree. Don't you have it in your package.mask?
As said, I synced the tree twice this morning (4 hours ago)
On Tue, Apr 18, 2017 at 11:16 AM, Jörg Schaible <
joerg.schai...@bpm-inspire.com> wrote:
> Hi Tomas,
>
> Tomas Mozes wrote:
>
> > On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible <
> > joerg.schai...@bpm-inspire.com> wrote:
> >
> >> Hi,
> >>
> >> according the logs, gcc 4.5.0-r3 is stable for amd64
On 18/04/17 10:44, Mart Raudsepp wrote:
> Ühel kenal päeval, T, 18.04.2017 kell 11:16, kirjutas Jörg Schaible:
>> Hi Tomas,
>>
>> Tomas Mozes wrote:
>>
>>> On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible <
>>> joerg.schai...@bpm-inspire.com> wrote:
>>>
Hi,
according the logs, gcc 4.5
Ühel kenal päeval, T, 18.04.2017 kell 11:16, kirjutas Jörg Schaible:
> Hi Tomas,
>
> Tomas Mozes wrote:
>
> > On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible <
> > joerg.schai...@bpm-inspire.com> wrote:
> >
> > > Hi,
> > >
> > > according the logs, gcc 4.5.0-r3 is stable for amd64:
> > > https:
Hi Tomas,
Tomas Mozes wrote:
> On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible <
> joerg.schai...@bpm-inspire.com> wrote:
>
>> Hi,
>>
>> according the logs, gcc 4.5.0-r3 is stable for amd64:
>> https://gitweb.gentoo.org/repo/gentoo.git/log/sys-devel/gcc?showmsg=1
>>
>> However, after synching th
On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible <
joerg.schai...@bpm-inspire.com> wrote:
> Hi,
>
> according the logs, gcc 4.5.0-r3 is stable for amd64:
> https://gitweb.gentoo.org/repo/gentoo.git/log/sys-devel/gcc?showmsg=1
>
> However, after synching the tree, this version is still unstable for
Hi,
according the logs, gcc 4.5.0-r3 is stable for amd64:
https://gitweb.gentoo.org/repo/gentoo.git/log/sys-devel/gcc?showmsg=1
However, after synching the tree, this version is still unstable for me.
Looking at the packages overview, it becomes even more weird, because there
seem to be two 4.5
Ühel kenal päeval, N, 13.04.2017 kell 16:01, kirjutas Mike Gilbert:
> On Thu, Apr 13, 2017 at 3:29 PM, Paweł Hajdan, Jr.
> wrote:
> > The latest dev channel release of chromium (59.0.3053.3) will
> > require
> > > =sys-apps/sandbox-2.11 to build.
> >
> > I'm sending this announcement because this
17 matches
Mail list logo
