I tried to update to 24.10.5 first but when I try to give the command "owut download -V 25.12 --force" I get the error "Impossible package selection: missing (libubox20260213)".
Hello,
I am also facing the same problem with my Linksys E8450 (UBI) running OpenWrt 24.10.5. When using the firmware selector, I got the following error:
Generate local signing keys...
WARNING: can't open config file: /builder/shared-workdir/build/staging_dir/host/etc/ssl/openssl.cnf
WARNING: can't open config file: /builder/shared-workdir/build/staging_dir/host/etc/ssl/openssl.cnf
read EC key
writing EC key
WARNING: opening /builder/packages/packages.adb: No such file or directory
Package list missing or not up-to-date, generating it.
Building package index...
ERROR: unable to select packages:
libubox20260213 (no such package):
required by: mtd-27[libubox20260213]
make[2]: *** [Makefile:254: package_install] Error 2
make[1]: *** [Makefile:193: _call_manifest] Error 2
make: *** [Makefile:369: manifest] Error 2
Traceback (most recent call last):
File "/app/.venv/lib/python3.14/site-packages/rq/worker.py", line 1439, in perform_job
return_value = job.perform()
File "/app/.venv/lib/python3.14/site-packages/rq/job.py", line 1318, in perform
self._result = self._execute()
~~~~~~~~~~~~~^^
File "/app/.venv/lib/python3.14/site-packages/rq/job.py", line 1376, in _execute
result = self.func(*self.args, **self.kwargs)
File "/app/asu/build.py", line 463, in build
result = _build(build_request, job)
File "/app/asu/build.py", line 282, in _build
report_error(job, check_package_errors(job.meta["stderr"]))
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/asu/util.py", line 332, in report_error
raise RuntimeError(msg)
RuntimeError: Impossible package selection: missing (libubox20260213)
I am not in the hurry to upgrade though. Thanks for your hard work!
It seems an update on libubox caused this.
As part of commit 8aac058 on openwrt-25.12 branch.
I got the following on image builded for x86 and qualcommax:
Building package index...
Installing packages...
ERROR: unable to select packages:
libubox20260213 (no such package):
required by: mtd-27[libubox20260213]
I'm not sure if we need to wait for downloads to update, or wait for the next point release ( @robimarko mentioned one is expected soon).
This is a known build issue with 25.12.0 that will take either a revert or a new 25.12.1 release to resolve. There is no timeline for a solution, so you'll have to wait...
Fix in place, 25.12.0 should be building for most devices now (although I still see a couple lagging behind, lantiq, mvebu and some ath79).
Hello,
I'm trying to upgrade my Pi4B from 25.12.0-rc5 - r32673-482ba7230a to 25.12.0 using attended system upgrade. After starting to build the firmware the it stops with: - Server response: Error: Impossible package selection: missing (libblobmsg-json20260213, libubox20260213).
I then thought I'd download a new file using the firmware selector and include the additional files I need in it. After many attempts I could not get it to work. So, I resorted to removing some of the additional packages to try and find if there was one particular one causing the issue. Eventually I removed them all and requested a build and it still failed.
As a final check I selected a different router / firmware to build but the screen displayed the following error message..
Customize installed packages and/or first boot script
Error: Impossible package selection: missing (libubox20260213)
STDERR
Generate local signing keys...
WARNING: can't open config file: /builder/shared-workdir/build/staging_dir/host/etc/ssl/openssl.cnf
WARNING: can't open config file: /builder/shared-workdir/build/staging_dir/host/etc/ssl/openssl.cnf
read EC key
writing EC key
WARNING: opening /builder/packages/packages.adb: No such file or directory
Package list missing or not up-to-date, generating it.
Building package index...
ERROR: unable to select packages:
libubox20260213 (no such package):
required by: mtd-27[libubox20260213]
make[2]: *** [Makefile:254: package_install] Error 2
make[1]: *** [Makefile:193: _call_manifest] Error 2
make: *** [Makefile:369: manifest] Error 2
Traceback (most recent call last):
File "/app/.venv/lib/python3.14/site-packages/rq/worker.py", line 1439, in perform_job
return_value = job.perform()
File "/app/.venv/lib/python3.14/site-packages/rq/job.py", line 1318, in perform
self._result = self._execute()
~~~~~~~~~~~~~^^
File "/app/.venv/lib/python3.14/site-packages/rq/job.py", line 1376, in _execute
result = self.func(*self.args, **self.kwargs)
File "/app/asu/build.py", line 463, in build
result = _build(build_request, job)
File "/app/asu/build.py", line 282, in _build
report_error(job, check_package_errors(job.meta["stderr"]))
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/asu/util.py", line 332, in report_error
raise RuntimeError(msg)
RuntimeError: Impossible package selection: missing (libubox20260213)
STDOUT
Installed Packages
Script to run on first boot (uci-defaults)
REQUEST BUILD
What is happening/ what am I doing wrong?
This has never been a problem in the past when I previously built Pi4B images.
Any help would be greatly appreciated!
Like already said in the thread a few times, it is currently impossible (with attended sysupgrade, owut, etc. glue-binaries-together tools) due to a few package upgrades. A new point release 25.12.1 is needed for those tools to work again with 25.12.x.
But you can build a coherent firmware from source code with the full toolchain.
Would instructing the build bots to re-compile all packages (or the one with broken dependencies) work as well?
They would need to do it for a point release anyway.
Since ASU / owut are now officially included by default for some devices (from 25.12 release notes), I think we might need to revisit the current approach to avoid breaking their workflow in the future.
Personally, I can build from source, so ASU (and image builder) is just a convenience feature.
Please don't get me wrong, I'm not demanding anything.
I know this is a community project and there is no guarantied support, but the official inclusion of ASU / owut also has some challenges.
