21.02.0-rc1 custom build - imagebuilder repositories.conf file is empty and the builder is missing the packages

after building the image builder i get this error:

/build/openwrt-imagebuilder-21.02.0-rc1-mvebu-cortexa9.Linux-x86_64 /build/source
Building images for mvebu - Linksys WRT1900ACS v1

Installing packages...
Unknown package 'libc'.
Collected errors:
 * pkg_hash_fetch_best_installation_candidate: Packages for libc found, but incompatible with the architectures configured
 * opkg_install_cmd: Cannot install package libc.
make[2]: *** [Makefile:165: package_install] Error 255
make[1]: *** [Makefile:122: _call_image] Error 2
make: *** [Makefile:240: image] Error 2

what is weird is that libc is built:

docker@10fa61294db7:/build/source$ find /build/source/bin/ -type f -iname '*libc*'
/build/source/bin/targets/mvebu/cortexa9/packages/libc_1.1.24-3_arm_cortex-a9_vfpv3-d16.ipk
docker@10fa61294db7:/build/source$

ok, i think the generated image builder is wrong, i get this:


## Place your custom repositories here, they must match the architecture and version.
# src/gz %n %U
# src custom file:///usr/src/openwrt/bin/%T/packages


option check_signature

with v19 i get this:

## Place your custom repositories here, they must match the architecture and version.
# src/gz %n http://cdn.corifeus.com/openwrt/19.07.7
# src custom file:///usr/src/openwrt/bin/mvebu/packages


## This is the local package repository, do not remove!
src imagebuilder file:packages

the problem is the image builder is only 80MB it is missing the packages folder (src imagebuilder file:packages)

how can i include the generated packages as it was before, now it is missing.

it's not created by default and exists purely for user custom packages...

you'll likely find this has something to do with some newer CONFIG_BUILDBOT(>ib-bundle) style logic... if you parse the mailing list... you can probably track down the specifics...

that... or your repositories.conf is messed up... for self compiled ib's... you'd need to ensure appropriate src/gz references to local repos...

could someone tell me how i can configure the build to include in the built image builder? before it was included in the files, now the repositories.conf is empty, please help, thanks

  • how is it able to guess where your src/gz http repos are going to be hosted?
  • are you asking developers to automate [ib]./packages/ population for non buildbot ib usage from [br]./bin/packages?

thanks for your help.
i could fix it like this:

docker@10fa61294db7:/build/openwrt-imagebuilder-21.02.0-rc1-mvebu-cortexa9.Linux-x86_64$ cat repositories.conf 
src/gz openwrt_core http://cdn.corifeus.com/openwrt/21.02.0-rc1/targets/mvebu/cortexa9/packages
src/gz openwrt_base http://cdn.corifeus.com/openwrt/21.02.0-rc1/packages/arm_cortex-a9_vfpv3-d16/base
src/gz openwrt_luci http://cdn.corifeus.com/openwrt/21.02.0-rc1/packages/arm_cortex-a9_vfpv3-d16/luci
src/gz openwrt_node http://cdn.corifeus.com/openwrt/21.02.0-rc1/packages/arm_cortex-a9_vfpv3-d16/node
src/gz openwrt_packages http://cdn.corifeus.com/openwrt/21.02.0-rc1/packages/arm_cortex-a9_vfpv3-d16/packages
src/gz openwrt_routing http://cdn.corifeus.com/openwrt/21.02.0-rc1/packages/arm_cortex-a9_vfpv3-d16/routing
src/gz openwrt_telephony http://cdn.corifeus.com/openwrt/21.02.0-rc1/packages/arm_cortex-a9_vfpv3-d16/telephony

this works but it not optimal, as it is so slow to download the packages, how can i configure to include the packages in the image builder? pleae help, thanks!

  • are you asking developers to automate [ib]./packages/ population for non buildbot ib usage from [br]./bin/packages?
    YES, i want to generate the image builder repositories.conf with buildbot usage without populate from the web, but inline

did 19x(era) non-buildbot buildroots do this? if so seems like a bug/regression

have you read mailing list as suggested?

(look for a two or three months ago where most bundled packages were removed from bundling onwards)

and does anyone how to setup the image builder of the repositories.conf without remote connection, all in the filesystem, is that possible?

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.