Hi,
I changed the RPB qcom-lt builds to use docker-buster-amd64 because we have been experimenting image corruption with ext2simg tool in new RPB zeus builds [1], there is a related bug report [1] and that's the reason why our Debian builds uses img2simg.
I tried to use img2simg in Debian stretch but is an old version (5.x) and fails to create images when are small size (ramdisk).
So it's a good opportunity to change the docker builder to Debian buster with a newer img2simg (8.x) tool in qcom-lt builds, I made the change in a way that doesn't affect current builds that uses Debian stretch [3] and give time to other users to switch (if needed).
Regards, Anibal
[1] https://validation.linaro.org/scheduler/job/1965964 [2] https://discuss.96boards.org/t/ext2simg-is-corrupting-custom-rootfs/8792 [3] https://git.linaro.org/ci/job/configs.git/commit/?id=2798029ae4a2772c9b51efc...
hey Anibal,
ok, thanks for sharing..
To be honest, I think we should figure out how to add sparse image support in oe-core directly. I tried in the past, but it didn't get merge, most likely i didn't follow up enough..
cheers nico
On Thu, Feb 6, 2020 at 9:43 PM Anibal Limon anibal.limon@linaro.org wrote:
Hi,
I changed the RPB qcom-lt builds to use docker-buster-amd64 because we have been experimenting image corruption with ext2simg tool in new RPB zeus builds [1], there is a related bug report [1] and that's the reason why our Debian builds uses img2simg.
I tried to use img2simg in Debian stretch but is an old version (5.x) and fails to create images when are small size (ramdisk).
So it's a good opportunity to change the docker builder to Debian buster with a newer img2simg (8.x) tool in qcom-lt builds, I made the change in a way that doesn't affect current builds that uses Debian stretch [3] and give time to other users to switch (if needed).
Regards, Anibal
[1] https://validation.linaro.org/scheduler/job/1965964 [2] https://discuss.96boards.org/t/ext2simg-is-corrupting-custom-rootfs/8792 [3] https://git.linaro.org/ci/job/configs.git/commit/?id=2798029ae4a2772c9b51efc...
An update,
I switched back RPB sumo build to Debian stretch because it fails (bison-native) building with Debian buster,
https://ci.linaro.org/job/lt-qcom-openembedded-rpb-sumo/152/DISTRO=rpb,MACHI...
On Thu, 6 Feb 2020 at 15:30, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
hey Anibal,
ok, thanks for sharing..
To be honest, I think we should figure out how to add sparse image support in oe-core directly. I tried in the past, but it didn't get merge, most likely i didn't follow up enough..
cheers nico
On Thu, Feb 6, 2020 at 9:43 PM Anibal Limon anibal.limon@linaro.org wrote:
Hi,
I changed the RPB qcom-lt builds to use docker-buster-amd64 because we
have been experimenting image corruption with ext2simg tool in new RPB zeus builds [1], there is a related bug report [1] and that's the reason why our Debian builds uses img2simg.
I tried to use img2simg in Debian stretch but is an old version (5.x)
and fails to create images when are small size (ramdisk).
So it's a good opportunity to change the docker builder to Debian buster
with a newer img2simg (8.x) tool in qcom-lt builds, I made the change in a way that doesn't affect current builds that uses Debian stretch [3] and give time to other users to switch (if needed).
Regards, Anibal
https://discuss.96boards.org/t/ext2simg-is-corrupting-custom-rootfs/8792
[3]
https://git.linaro.org/ci/job/configs.git/commit/?id=2798029ae4a2772c9b51efc...
-
Anibal Limon -
Nicolas Dechesne