I believe editing that single file only solves the issue for systems using the Debian Package Add-on. If you do the same edit to /etc/apt/sources.list and /etc/apt/sources.list.d/raspi.list you should get it to work for a Piaware SD card image.
1 Like
That fixed most of it. Towards the end, I got this:
E: Failed to fetch https://www.flightaware.com/mirror/raspberrypi/debian/pool/ma in/f/firmware-nonfree/firmware-brcm80211_20230210-5%7ebpo11%2b1%2brpt1_all.deb Error reading from server. Remote end closed connection [IP: 104.18.39.201 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Notes from a previous update had this followed by a normal update and that ran OK.
sudo apt-get update --allow-releaseinfo-change
Get:1 https://www.flightaware.com/mirror/raspbian/raspbian bullseye InRelease [15.0 kB]
Hit:2 https://www.flightaware.com/adsb/piaware/files/packages bullseye InRelease
Get:3 https://www.flightaware.com/mirror/raspberrypi/debian bullseye InRelease
Fetched 38.6 kB in 2s (23.0 kB/s)
Reading package lists… Done
The http/https problems should be fixed now, sorry for the trouble.
however!
If you’re still on stretch, things will still be broken, as upstream no longer supports stretch. The fix here is, unfortunately, to re-image with something more recent …
1 Like
Fresh install of the OS… still getting this (just now):
Reading package lists… Done
E: The repository ‘https://flightaware.com/adsb/piaware/files/packages bookworm Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Am I doing something wrong? In short, still getting the “redirection is forbidden” error above what I have quoted here.
(I can’t post the entire output due to me being a “new user”, sorry)
We haven’t released bookworm piaware packages yet, they are a few days away.
Ah!
Ok. Thanks for the update; wasn’t aware.
Of course it’s sod’s law that I need to reimage my pi today and can’t get piaware to compile on it. I’ll have to reimage with the last version and try to upgrade later as I don’t particularly want to have to reinstall again later.
Do you know if 64 bit packages will be available for bookworm, or still 32 bit only for now?
Planning to release both armhf and arm64 packages for both bookworm and bullseye, all going well.
That’s good to know - perhaps I will give the 64 bit Bookworm a go. Compiling didn’t work on the 32 bit version with 64 bit kernel but some people seem to have it running on full 64 bit systems.
This should be fixed on the dev branch already if you don’t mind building a dev version
If I try it I get the following error. This is an up to date pull of the dev branch of piaware_builder:
removing build/bdist.linux-aarch64/wheel
Successfully built cx_Freeze-6.15.7-cp311-cp311-linux_aarch64.whl
/home/pi/piaware_builder/package-bookworm/debian/venv/bin/python -m pip install --no-index --no-deps --require-virtualenv /home/pi/piaware_builder/package-bookworm/wheels/cx_Freeze-6.15.7-*.whl
ERROR: cx_Freeze-6.15.7-cp311-cp311-linux_aarch64.whl is not a supported wheel on this platform.
make[1]: *** [debian/rules:73: build_cxfreeze] Error 1
make[1]: Leaving directory '/home/pi/piaware_builder/package-bookworm'
make: *** [debian/rules:105: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
pi@adsbpi:~/piaware_builder/package-bookworm $ uname -a
Linux adsbpi 6.1.0-rpi4-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.54-1+rpt2 (2023-10-05) aarch64 GNU/Linux
This is a clean 32-bit light installation straight from the Raspberry Pi SD card imager.
Edit - Full output of sensible-build.sh: ./sensible-build.sh bookwormRetrieving dev from https://github.com/flightaware - Pastebin.com
Full output of dpkg-buildpackage: pi@adsbpi:~/piaware_builder/package-bookworm $ dpkg-buildpackage -b --no-signd - Pastebin.com
Aha, thanks. I fixed this for bullseye but it looks like I missed transplanting it to the bookworm rules.
edit: this is sufficiently complicated (bookworm is using build not setup.py directly) that it’ll be a thing for tomorrow.
1 Like
I can confirm that my original posted issue is now resolved.
Updates now run without issue.
Thanks for the corrective action!
I’ve just re-imaged to a full 64 bit installation and dev branch piaware builder worked as expected. piaware is feeding OK and mlat is working.
1 Like
During last two days, I have thrice successfully built & installed (on 3 different microSD cards) piaware ver 9.0~dev package on 64-bit RaspberryPiOS Bookworm and twice on 32-bit Armbian Bookworm using following bash script. I never got this error.
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu-debian-amd64/master/install-piaware.sh)"
Yeah it works OK on a full 64 bit installation. The problem is that by default the headless Pi OS image uses a 64-bit kernel and 32-bit user space, which causes issues with the config. A 32-bit system with 32-bit kernel should be ok.
The short explanation of why this happens is that there’s a bug in the Python packaging system where it uses uname -m (kernel machine architecture) to decide the name of the architecture it’s building for, not the architecture that userspace / Python itself are built for. There is then some magic translation that goes on based on the word size that Python is built for, but some of the versions of the packaging system that we’re working with don’t know to do this translation for ARM. It’s a bit of a pain to work around …
(the fun begins here: https://github.com/pypa/wheel/blob/dc1b9f9008d28f63258e9cb59014e9a48d2649ab/src/wheel/bdist_wheel.py#L68 – this is the fixed version, older versions were unaware of aarch64)
This should be fixed on the dev branch now. It built armhf packages OK on our CI machine which is effectively a 64-bit-kernel-32-bit-userspace environment.
No update, they’re still in progress.