On Sunday, 24 June 2018 19:49:02 BST Rich Freeman wrote:
> On Sun, Jun 24, 2018 at 2:28 PM wrote:
> > Since the unstable packages of today are the stable packages of
> > tommorrow one needs to bite the bullet (and hopefully this sentence
> > is not complete nonsense...I am no native speaker...not
On 25 June 2018 at 04:19, wrote:
> I think, my attempt to play with words despite the fact that I am no
> native speaker ;) has spent some confusion (or I understand something
> wrong right now:
>
> In my make,conf this is set
>
> ACCEPT_KEYWORDS="~amd64"
>
> so I am on unstable.
The actual
On 06/24 07:01, Philip Webb wrote:
> 180624 Andreas K. Huettel wrote:
> > Am Sonntag, 24. Juni 2018, 09:01:53 CEST schrieb tu...@posteo.de:
> >> The bad news: mpfr-4 was installed after a successful compilation
> >> and gcc failed to compile.
> > This was a collective thinko of the toolchain team.
180624 Andreas K. Huettel wrote:
> Am Sonntag, 24. Juni 2018, 09:01:53 CEST schrieb tu...@posteo.de:
>> The bad news: mpfr-4 was installed after a successful compilation
>> and gcc failed to compile.
> This was a collective thinko of the toolchain team.
> The news item should never have been shown
Am Sonntag, 24. Juni 2018, 09:01:53 CEST schrieb tu...@posteo.de:
> Hi,
>
> I think I am in trouble here...especially after reading the news
> item...
>
> After the daily sunc routine, a new news items was announced which
> I read.
>
> It saus, that the update to mpfr-4 could possibly break
On Sun, Jun 24, 2018 at 2:28 PM wrote:
>
> Since the unstable packages of today are the stable packages of
> tommorrow one needs to bite the bullet (and hopefully this sentence
> is not complete nonsense...I am no native speaker...not at all!)
>
Presumably if you're running stable on a host you
On 06/24 11:12, Daniel Frey wrote:
> On 06/24/18 10:21, Dale wrote:
> > Plus it does say to include that info. If it wasn't provided, it would
> > likely be asked for at some point unless someone has ran into that
> > specific problem and can recognize it with nothing but the bare info.
> >
> >
On 06/24/18 10:21, Dale wrote:
> Plus it does say to include that info. If it wasn't provided, it would
> likely be asked for at some point unless someone has ran into that
> specific problem and can recognize it with nothing but the bare info.
>
> My email program downloaded the whole thing
zless wrote:
> În ziua de duminică, 24 iunie 2018, la 11:55:52 EEST, Zoltán Kócsi a scris:
>> Hi,
>>
>>> Here are the outputs, which I should include if I need support
>>> according to emerge ;)
>> Still, if you didn't attach 9MB worth of stuff, that'd be appreciated.
>>
>> As a rough guess, the
În ziua de duminică, 24 iunie 2018, la 11:55:52 EEST, Zoltán Kócsi a scris:
> Hi,
>
> > Here are the outputs, which I should include if I need support
> > according to emerge ;)
>
> Still, if you didn't attach 9MB worth of stuff, that'd be appreciated.
>
> As a rough guess, the Gentoo list
Hi,
> Here are the outputs, which I should include if I need support
> according to emerge ;)
Still, if you didn't attach 9MB worth of stuff, that'd be appreciated.
As a rough guess, the Gentoo list probably has at least 5 thousand
different subscribers, so your simple email generated some 45GB
11 matches
Mail list logo