From mboxrd@z Thu Jan 1 00:00:00 1970 From: IPFire Nightly Builder 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 Message-ID: <4GLvtg6jvPz603P@arm64-02.dub.ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2099984723911059776==" List-Id: --===============2099984723911059776== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable https://nightly.ipfire.org/master/2021-07-09%2013%3A54%3A39%20%2B0000-d0ba077= e/armv6l commit d0ba077ed3851346b1dd6d82867103df8446aea8 Author: Peter M=C3=BCller Date: Wed Jul 7 19:27:14 2021 +0200 Pakfire: call "sync" in function.sh after having extracted archives =20 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. =20 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. =20 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. =20 See also: https://community.ipfire.org/t/after-update-ipfire-to-157-no-boot/5641/45 =20 Signed-off-by: Peter M=C3=BCller Signed-off-by: Michael Tremer https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dshortlog;h=3Dd0ba077ed3851346b= 1dd6d82867103df8446aea8 ERROR: Cannot build for architure armv6l [ FAI= L ] Check /build/nightly/master/log/_build.preparation.log for errors if appl= icable[ FAIL ] --===============2099984723911059776==--