From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of master (d0ba077) for armv6l on arm64-02.dub.ipfire.org
Date: Fri, 09 Jul 2021 14:00:11 +0000 [thread overview]
Message-ID: <4GLvtg6jvPz603P@arm64-02.dub.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
https://nightly.ipfire.org/master/2021-07-09%2013%3A54%3A39%20%2B0000-d0ba077e/armv6l
commit d0ba077ed3851346b1dd6d82867103df8446aea8
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Wed Jul 7 19:27:14 2021 +0200
Pakfire: call "sync" in function.sh after having extracted archives
After upgrading to Core Update 157, a few number of users reported their
systems to be unworkable after a reboot. Most of them (the systems, not
the users) were apparently missing the new Linux kernel in their Grub
configuration, causing a non-functional bootloader written to disk.
While we seem to be able to rule out issues related to poor storage
(SDDs, flash cards, etc.) or very high I/O load, it occurred to me we
are not calling "sync" after having extracted a Core Update's .tar.gz
file.
This patch therefore proposes to do so. It is a somewhat homeopathic
approach, though, but might ensure all parts of the system to have
properly processed the contents of an extracted archive. While we cannot
even reasonably guess it will solve the problem(s) mentioned initially,
doing so cannot hurt either.
See also:
https://community.ipfire.org/t/after-update-ipfire-to-157-no-boot/5641/45
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=d0ba077ed3851346b1dd6d82867103df8446aea8
ERROR: Cannot build for architure armv6l [ FAIL ]
Check /build/nightly/master/log/_build.preparation.log for errors if applicable[ FAIL ]
reply other threads:[~2021-07-09 14:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4GLvtg6jvPz603P@arm64-02.dub.ipfire.org \
--to=nightly-builds@ipfire.org \
--cc=nightly-builds@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