From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: core 140?
Date: Mon, 03 Feb 2020 15:17:49 +0100 [thread overview]
Message-ID: <221dc3a3f35a4bcc89e54df27f26def9@ipfire.org> (raw)
In-Reply-To: <ebcdbec9-1314-aedd-0667-f42b03883d85@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
Am 2020-02-03 06:27, schrieb Paul Simmons:
> So, are we skipping 140? The nightly builds are at 141...
Yes. Some installations run out of diskspace on root so they cannot
install the full update
without cleanup before. So I have inserted a core upgrade that only
contains the filesystem
cleanup script.
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=69c529972aec2641f9f689915c0a29f84d457002
ISO's for core140 will not released.
next prev parent reply other threads:[~2020-02-03 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 5:27 Paul Simmons
2020-02-03 14:17 ` Arne Fitzenreiter [this message]
2020-02-03 14:49 ` Paul Simmons
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=221dc3a3f35a4bcc89e54df27f26def9@ipfire.org \
--to=arne_f@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