Packages still linking to python 3.10 #183
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#183
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Lets track all packages still linked to 3.10 here to keep it cleaner instead of multiple issues for each package.
You can check if any packages are still build against 3.10 with:
Please note this issue is only for repo packages. (no AUR packages)
#182
kitty
#180
capstone
cython
dtc
i2c-tools
libftdi
libibus
libnewt
libvirt-python
ninja
obs-studio
gedit
python-apsw
python-brotlicffi
btrfs-progs
packagekit
python-coverage
aircrack-ng
gpsd
hivex
nlopt
nemo-audio-tab
nemo-emblems
nemo-pastebin
opensnitch
hugin
hexchat
OBS is not shown by that command, however it tries to load
libpython3.10.so.1.0
on startup (so it still needs to be rebuilt)My
pacman -Qo /usr/lib/python3.10
show these packagesFor me its:
For those wondering how to filter AUR/foreign packages, use:
pacman -Qm
For me, I get:
After simply reinstalling all packages manually that are listed using the command
pacman -Qo /usr/lib/python3.10
with before beingI still have two packages that need to be recompiled
Why weren't these packages bumped to a
.2
version suffix for the 3.11 recompile task to begin with?hexchat
is also still linked to python 3.10:The rebuilds should have been bumped, but there is a bug preventing that from happening I have not found yet. In my local tests it works perfectly fine. Need to find the time to deep-dive this section of code once more.
@anonfunc the cython package needs a .2 bump. Had 0.29.34-3.1 installed which is still linking to python 3.10. But if reinstalled I get the same version number but it's fixed.
Hey @anonfunc,
you can just ask pacman's database on that matter:
That's currently:
Same goes for
gpsd
andi2c-tools
, so this could be a widespread issue. So it would be best to check all version numbers on those which you had to recompile.Thanks for the tip with
-F
, I was able to filter out all remaining packages. As for the.2
bump, as I said herethere is still a bug to be found here. Manually bumping is not something I accounted for, so there is no mechanism to do that currently. Normally removing already build packages should trigger an
.(previous build-no+1)
build.See
943b37bee2/proto_package.go (L186)
:EDIT: I think I have found the problem. Seems like an older version of ALHP saved malformed versions, so the compare fails because this 'lastest build version' does not match the current version. For example:
Newer builds do not have this problem:
EDIT2: I fixed this with a housekeeping job in
ac909f4e36
.I'll close this as it seems we got every package. Please reopen if you get any 3.10 linking issues with packages from the ALHP repos.