Actually, the nightly build didn't build either.
I don't know why. I will check tomorrow. If someone finds it earlier or has time to search, please go ahead.
Best, -Michael
On Mon, 2018-04-30 at 20:42 +0100, Michael Tremer wrote:
No, this should build after a pull.
On Mon, 2018-04-30 at 15:17 +0200, Matthias Fischer wrote:
Hi,
On 30.04.2018 14:13, Michael Tremer wrote:
Happens. Not a problem at all. That's what next is for. It is a development branch. ...
Does this changes require a clean build?
After pulling commit 36d9e459c0e259d6348438ea3594b6b2213d34b8 and rebuilding I ran into the same error(s) as before:
***SNIP*** ... # Compress Image pigz -f9 < /install/images/image.img > /install/images/ipfire-2.19.1gb-ext4- scon.i586-full-core121.img.gz rm -rf /install/images/image.img /install/harddisk mv: cannot stat '/home/matz/ipfire-2.x/build/install/images/*.tgz': No such file or directory mv: cannot stat '/home/matz/ipfire-2.x/build/install/images/*.bz2': No such file or directory Apr 30 12:38:09: Building core-updates + cd /usr/src/lfs
- MAKETUNING=-j9
- make -f core-updates LFS_BASEDIR=/usr/src install
rm -rf /install/packages/package mkdir -p /install/packages/package eval $(cat /usr/src/config/rootfiles/core/121/meta) #Generate ROOTFILES from filelists BUILD_ARCH=i586 BUILDTARGET=i586-pc-linux-gnu KVER=3.14.79 \ /usr/src/src/scripts/archive.files \ /usr/src/config/rootfiles/core/121/filelists \ /usr/src/config/rootfiles/core/121/files \ /usr/src/config/rootfiles/core/121/files.i586 \
/tmp/ROOTFILES.tmp
#remove excluded files from ROOTFILES grep -f /usr/src/config/rootfiles/core/121/exclude -v /tmp/ROOTFILES.tmp > /tmp/ROOTFILES make: *** [core-updates:60: core/121] Error 1 ***SNAP***
Nevertheless, I pushed 'dhcp: Update to 4.4.1'.
'_build.ipfire.log' from'next' is looking good and the new version is running without problems for a few days.
Best, Matthias