From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core-upgrade-2.21-121
Date: Thu, 07 Jun 2018 22:09:02 +0100 [thread overview]
Message-ID: <2514e361dfbfe4a980db18d93b9fb91fa5fda8f1.camel@ipfire.org> (raw)
In-Reply-To: <9d20d912-648c-87fb-7fec-6332255371be@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
Hey,
On Thu, 2018-06-07 at 22:02 +0200, Matthias Fischer wrote:
> Hi,
>
> First ("just for the records"):
> I'm taking some days off. Until 24.06.2018 you can find me here (from
> time to time): https://www.utersum.de/?page_id=89 ;-)
Have a nice holiday.
> Second:
> I made a clean build from current 'next' today and noticed that
> 'ROOTFILES' starts with a blank line. I don't know if this could cause
> us any troubles!?
It shouldn't have been empty. But as far as I know the builds are fine.
> Third:
> It's BIG. 'core-upgrade-2.21-121.ipfire' has now ~103 MB. I'm hoping
> that this won't cause any troubles, too.
Yes, it is huuuuuge. And that *will* cause problems. I have no idea why
though. The kernel and firmware themselves shouldn't be that large and
there is barely anything else in it. Unless I have added something that
shouldn't be in there.
> Fourth:
> "./make.sh gettoolchain" gives me:
>
> ...
> Jun 7 19:57:57: Load toolchain image for i586
> Jun 7 19:57:57: error downloading ipfire-2.21-toolchain-20180606-i586 toolchain for i586 machine
> ...
I will upload that one shortly.
Best,
-Michael
>
> Best to all and take care...,
> Matthias
prev parent reply other threads:[~2018-06-07 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 20:02 Core-upgrade-2.21-121 Matthias Fischer
2018-06-07 21:09 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2514e361dfbfe4a980db18d93b9fb91fa5fda8f1.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox