Skip to content

The audiodsp recipe honours its pin, now 0.6.4 - #22

Merged
bdbarnett merged 2 commits into
mainfrom
audiodsp-pin
Oct 9, 2026
Merged

bdbarnett merged 2 commits into
mainfrom
audiodsp-pin

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

The pydevices-audiodsp recipe named 0.6.0, but its get_pip_name() returned the bare package name, so p4a ran pip install pydevices-audiodsp and took whatever was newest on TestPyPI. A fresh build took 0.6.4.

get_pip_name() now returns pydevices-audiodsp==<version> when a version is set, the way the pydevices-lvgl recipe does, and the pin moves to 0.6.4, the latest final and what unpinned builds have been shipping. The other pins stay where they are.

Same fix as PyDevices/android-runner#37.

Tested: an APK built from this branch with ./build_android.sh -y (results in a comment below).

get_pip_name() returned the bare name, so p4a installed the newest audiodsp on the index whatever the pin said. It now returns pydevices-audiodsp==<version>, the way the lvgl recipe does. 0.6.4 is the latest final and what an unpinned build has been taking.
p4a matches the existing dist by recipe names alone and repackages the old packages. Remove the dist and the old dist-info, and check what the APK carries.
@bdbarnett

Copy link
Copy Markdown
Contributor Author

Built from this branch with ./build_android.sh -y and installed on a Galaxy S21 (Android 14). The APK's bundle carries pydevices_audiodsp-0.6.4 beside its own pins (pydevices 0.5.2, pydevices-desktop 0.5.2, pydevices-lvgl 9.5.48), and the app starts and draws its four colour bands with no traceback in logcat. Template check passed.

The second commit documents a trap found on the way: an incremental build ignores a changed recipe pin, because p4a reuses the dist when the recipe names match. The Runner hit it moving pydevices-lvgl (PyDevices/android-runner#39).

@bdbarnett
bdbarnett merged commit 0b5c75d into main Oct 9, 2026
1 check passed
@bdbarnett
bdbarnett deleted the audiodsp-pin branch October 9, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant