The OpenWrt Firmware Selector

Please return the normal error output, as it was. So that the packages are clearly indicated!!!
As it is now - NOT OK!!! How can I understand from this message what is wrong?
The list of packages is taken from a router that works without problems.
This is some kind of quest without an input and output!!!

Summary

Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/rq/worker.py", line 1633, in perform_job return_value = job.perform() ^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/rq/job.py", line 1331, in perform self._result = self._execute() ^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/rq/job.py", line 1365, in _execute result = self.func(*self.args, **self.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/asu/build.py", line 245, in build report_error(job, "Impossible package selection") File "/app/asu/util.py", line 308, in report_error raise RuntimeError(msg) RuntimeError: Impossible package selection

bridger disappeared again and the error is because of him.
But no amount of nerves will be enough to calculate it like that(((.

@Lexeyko how did the output look like before?

A list of packages that for some reason had an error and a brief description of the error. Now you can see it on the website ImmortalWrt. It is done there in the same way as it was done here until recently.

Summary

Package list missing or not up-to-date, generating it.

Building package index...
Downloading http://192.168.49.7/releases/24.10.1/targets/mediatek/filogic/packages/Packages.gz
Updated list of available packages in /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../builder/dl/immortalwrt_core
Downloading http://192.168.49.7/releases/24.10.1/targets/mediatek/filogic/packages/Packages.sig
Signature check passed.
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/base/Packages.gz
Updated list of available packages in /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../builder/dl/immortalwrt_base
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/base/Packages.sig
Signature check passed.
Downloading http://192.168.49.7/releases/24.10.1/targets/mediatek/filogic/kmods/6.6.86-1-f2c63d42896f12da2b55f2c2b626e7be/Packages.gz
Updated list of available packages in /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../builder/dl/immortalwrt_kmods
Downloading http://192.168.49.7/releases/24.10.1/targets/mediatek/filogic/kmods/6.6.86-1-f2c63d42896f12da2b55f2c2b626e7be/Packages.sig
Signature check passed.
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/luci/Packages.gz
Updated list of available packages in /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../builder/dl/immortalwrt_luci
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/luci/Packages.sig
Signature check passed.
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/packages/Packages.gz
Updated list of available packages in /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../builder/dl/immortalwrt_packages
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/packages/Packages.sig
Signature check passed.
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/routing/Packages.gz
Updated list of available packages in /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../builder/dl/immortalwrt_routing
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/routing/Packages.sig
Signature check passed.
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/telephony/Packages.gz
Updated list of available packages in /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../builder/dl/immortalwrt_telephony
Downloading http://192.168.49.7/releases/24.10.1/packages/aarch64_cortex-a53/telephony/Packages.sig
Signature check passed.
Downloading file:packages/Packages
Updated list of available packages in /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../builder/dl/imagebuilder
Downloading file:packages/Packages.sig
Signature check passed.
Collected errors:

  • check_data_file_clashes: Package libustream-mbedtls20201210 wants to install file /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/lib/libustream-ssl.so
    But that file is already provided by package * libustream-openssl20201210
  • opkg_install_cmd: Cannot install package libustream-mbedtls20201210.
  • check_data_file_clashes: Package libustream-mbedtls20201210 wants to install file /builder/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/lib/libustream-ssl.so
    But that file is already provided by package * libustream-openssl20201210
  • opkg_install_cmd: Cannot install package luci-ssl.
  • check_conflicts_for: The following packages conflict with wpad-wolfssl:
  • check_conflicts_for: wpad-openssl *
  • opkg_install_cmd: Cannot install package wpad-wolfssl.
    make[2]: *** [Makefile:234: package_install] Error 255
    make[1]: *** [Makefile:171: _call_manifest] Error 2
    make: *** [Makefile:349: manifest] Error 2

Im trying to have snapshot to test something since MediaTek MT7621 wakes up on LAN without reason (24.x series), and some people doesnt have this effect on actual snapshots, how i can have it?

snapshot (r29528-ffde9a9fe9)

Error: Impossible package selection
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:
  opkg (no such package):
    required by: world[opkg]
make[2]: *** [Makefile:226: package_install] Error 1
make[1]: *** [Makefile:167: _call_manifest] Error 2
make: *** [Makefile:344: manifest] Error 2
base-files busybox ca-bundle dnsmasq dropbear firewall4 fstools kmod-gpio-button-hotplug kmod-leds-gpio kmod-nft-offload libc libgcc libustream-mbedtls logd mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd procd-seccomp procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd wpad-basic-mbedtls kmod-mt7915-firmware kmod-usb3 kmod-usb-ledtrig-usbport luci banip ddns-scripts-noip luci-app-banip luci-app-opkg luci-base luci-i18n-banip-pl luci-i18n-base-pl luci-i18n-ddns-pl luci-i18n-firewall-pl luci-i18n-opkg-pl luci-mod-network luci-mod-status luci-proto-ipv6 luci-proto-ppp luci-theme-bootstrap mc msmtp netifd openvpn-easy-rsa openvpn-openssl htop nano-plus luci-app-statistics luci-i18n-statistics-pl luci-app-wifischedule luci-i18n-wifischedule-pl luci-app-commands luci-i18n-commands-pl ethtool-full iperf3-ssl kmod-crypto-hw-eip93 luci-app-attendedsysupgrade luci-i18n-attendedsysupgrade-pl owut luci-i18n-adblock-pl

There is no opkg in main snapshot, it has been replaced by apk. The future is now: opkg vs apk

2 Likes

hm, these messages come from the backend.
@aparcar any idea if the backend error output changed?

I provided the error output as it was and as it has become. It is impossible to understand anything from the new error output!!! Perhaps it is tailored for AI, but definitely not for human intelligence(((.

Could it be unrelated to your problem error, or not?

And - YES! The bridger is back in action and now with the same packages it assembles perfectly! What's wrong with this bridger - is not clear.
Bewitched package))).
It could be related to anything, but if it was written clearly, and not as a derivation of ancient Egyptian hieroglyphs on the tomb of a pharaoh, it would be great!. There would be no questions. Corrected the package list and reassembled.

The Firmware Selector is broken again, it gets stuck with no error.

3 Likes

Yeah, I reported it to @aparcar on irc several hours ago...

1 Like

It seems like it hasn't broken like this before, so it's something new.

The error message has changed but it still doesn't work!!!

Would be nice if @aparcar would tell us what's going on... Is there anybody else to reach regarding this issue?


It would be nice if we never saw these errors and everything always worked without them.
What will knowledge of why it doesn't work give?
It won't help us in any way, we can't influence it in any way).

Remember this is open source. Paul probably has a family, a job and other competing calls on their time. Preface any frustration with thanks for the work that he and his fellow volunteers do. I for one am extremely grateful. Even as I also would love to know what is going on under the covers.

3 Likes

Hi, I’m on vacation and have no access right now. I’ll ask the hypervisor maintainers to shutdown the server until my return.

Sorry for the inconvenience, I will see to add more maintainers to the server itself or simplify the setup so other communities (I.e. Freifunk) can offer an instance as redundant backup.

15 Likes

Is it related to attended sysupgrade not working?

I cannot use it for several days.

But there is no error message, just it keeps waiting looking for upgrades forever.

Yes, they all use the ASU server. So, auc/owut, The Firmware Selector and Luci Attended Sysupgrade don't work at the moment.

The only option is to build an image using the build system or the image builder, both locally on your computer.

Cheers!

1 Like