Doesn't start after updating Python, no idea what to do:
Traceback (most recent call last):
File "/usr/bin/zapzap", line 5, in <module>
from zapzap.__main__ import main
ModuleNotFoundError: No module named 'zapzap'
Git Clone URL: | https://aur.archlinux.org/zapzap.git (read-only, click to copy) |
---|---|
Package Base: | zapzap |
Description: | WhatsApp desktop application written in Pyqt6 + PyQt6-WebEngine |
Upstream URL: | https://github.com/rafatosta/zapzap |
Licenses: | GPL3 |
Submitter: | bordam |
Maintainer: | alllexx88 (AutoUpdateBot) |
Last Packager: | AutoUpdateBot |
Votes: | 36 |
Popularity: | 2.12 |
First Submitted: | 2022-09-25 10:47 (UTC) |
Last Updated: | 2025-03-08 07:56 (UTC) |
Doesn't start after updating Python, no idea what to do:
Traceback (most recent call last):
File "/usr/bin/zapzap", line 5, in <module>
from zapzap.__main__ import main
ModuleNotFoundError: No module named 'zapzap'
This PKGBUILD uses a pacman
feature to compute checksums in CVS packages, which requires pacman>=6.1.0
. If you're coming from Manjaro or an other Arch-based distro with pacman<6.1.0
, you need to pass --skipchecksums
to makepkg
, if building manually, or, if installing with yay
, add --mflags --skipchecksums
, e.g.:
yay -S --mflags --skipchecksums zapzap
@vvch Thank you for the feedback. I didn't know Manjaro still had pacman
6.0.2. I'll add instructions for people coming from Manjaro or other Arch-based distros with pacman<6.1.0
.
@alllexx88 Thank you for your investigation. I use Manjaro which still has pacman 6.0.2
https://software.manjaro.org/package/pacman
Just upgrade your system, and it should work fine.
As I said before, I have already managed to workaround my problem, but seems like there will be many people who also encounter it since pacman 6.1.0 is a bleeding edge released on March 2024.
@MajorMayer You can ommit the validitation check running makepkg --skipchecksums -si , but keep in mind that doing this implies a security risk, so isn't a recommended practice unless you fully trust the package.
@vvch @MajorMayer I was able to reproduce the error on an old livecd image that had pacman
6.0.1. After upgrading pacman
to the current 6.1.0 (and some libraries to make it work), the error was gone. Loos like the older pacman
never calculated checksums for CVS sources, while the actual one does (when a fixed tag or commit are specified), going recursively into the dir content. Just upgrade your system, and it should work fine.
P.S. The b2sum
from this PKGBUILD was generated automatically by the auto update bot by calling updpkgsums
command.
@alllexx88 I got the same problem as @MajorMayer .
rm -rf ~/.cache/yay/zapzap
did not help. Something is wrong with the b2sum. When I changed it to
b2sums=('SKIP')
it worked.
@MajorMayer Can you try a clean build? I'm unable to reproduce the error, but maybe there's something wrong with the previously cloned upstream git repo. If using yay
:
rm -rf ~/.cache/yay/zapzap
If building manually, remove pkg
src
zapzap
, or just clone the AUR repo afresh.
Installing doesn't work for me:
Building zapzap...
==> Making package: zapzap 5.2.1-1 (Fri Apr 5 13:28:56 2024)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating zapzap git repo...
==> Validating source files with b2sums...
zapzap ... NOT FOUND
==> ERROR: One or more files did not pass the validity check!
Error: Failed to build zapzap
@hsantanna, that seems more like an issue with your qt6-base beta.
Maybe you can try to update that one to the newer available version.
Pinned Comments
alllexx88 commented on 2024-12-24 08:51 (UTC)
Since python has recently been upgraded to 3.13, you need to rebuild the package if you installed it last before the upgrade, e.g., with
yay
(thanks @marco.righi) you can:alllexx88 commented on 2024-04-06 19:31 (UTC)
This PKGBUILD uses a
pacman
feature to compute checksums in CVS packages, which requirespacman>=6.1.0
. If you're coming from Manjaro or an other Arch-based distro withpacman<6.1.0
, you need to pass--skipchecksums
tomakepkg
, if building manually, or, if installing withyay
, add--mflags --skipchecksums
, e.g.: