Open felixwiemuth opened 4 years ago
actionless
commented
4 years ago does that happens with slack-desktop package, or what exactly should i do to catch it?
without knowing more info (and without full logs with --pikaur-debug flag) i could only guess what PKGBUILD is corrupted and missing pkgver or pkgrel value
felixwiemuth
commented
4 years ago It happened with the slack-desktop package, yes. I don't think its PKGBUILD is corrupted as I could install successfully afterwards and others apparently use it as well (https://aur.archlinux.org/packages/slack-desktop/). I installed the package for the first time.
I tried to reproduce it, but couldn't (I uninstalled and tried to reinstall, but this time there were no other updates to install, so same situation as where it eventually worked above).
In the above case where it fails, the warning about "build deps" being removed actually lists all normal dependencies of the package (see PKGBUILD): libsecret, xdg-utils, libxtst, libxss, nss, alsa-lib, gtk3. None of these packages were upgraded recently, they were all installed already.
actionless
commented
4 years ago I tried to reproduce it, but couldn't (I uninstalled and tried to reinstall, but this time there were no other updates to install, so same situation as where it eventually worked above).
i couldn't neither without having a reproducible sequence
In the above case where it fails, the warning about "build deps" being removed actually lists all normal dependencies of the package (see PKGBUILD):
compare aur RPC reply and pkgbuild - the message about it
felixwiemuth
commented
4 years ago compare aur RPC reply and pkgbuild - the message about it
I'm not sure what you want to say with this, could you explain further?
I will try to observe this further, and when I have more information or can reproduce it, I'll let you know.
actionless
commented
4 years ago 
lectrode
commented
4 years ago I believe I reproduced this error. I'm not sure exactly what is needed to reproduce it yet, but I have a VM whose state I can revert to consistently produce it at will.
The VM is solely for testing purposes and does not have any important information on it. If it would help, I can probably compress and upload the VM. It'd probably be about 5-6GB.
Reproduced with:
$ pikaur -Vq
Pikaur v1.6.10.r9.g31e1605
Pacman v5.2.1 - libalpm v12.0.1Further testing reveals something interesting: repeatedly running the command will eventually succeed. I ran the same command a total of 8 times before it succeeded (no other changes were made).
lectrode
commented
4 years ago actionless
commented
4 years ago thanks a lot, @lectrode !
i'll try to figure it out, first i'll start from inspecting pkgbuild/srcinfo files of the affected aur packages from your log, and next will think more
actionless
commented
4 years ago @lectrode could you please apply this patch to installed pikaur and next upload the file ~/.local/share/pikaur/aur_repos/<PKG_NAME>/.SRCINFO from the failed attempt?
diff --git a/pikaur/aur.py b/pikaur/aur.py
index d29b771..01d5653 100644
--- a/pikaur/aur.py
+++ b/pikaur/aur.py
@@ -53,6 +53,7 @@ class AURPackageInfo(DataType):
@classmethod
def from_srcinfo(cls, srcinfo) -> 'AURPackageInfo':
+ print(srcinfo.package_name)
+ print(srcinfo.get_value('pkgbase'))
return cls(
name=srcinfo.package_name,
version=srcinfo.get_value('pkgver') + '-' + srcinfo.get_value('pkgrel'),It seems the version isn't always successfully retrieved from the AUR. I was able to reproduce it with just the following (but it doesn't happen every time).
actionless
commented
4 years ago print(srcinfo.package_name) print(srcinfo.get_value('pkgbase'))pikaur-git None
what i can see so far is what srcinfo is empty for some reason
i'll try to figure out if it might be some sort of race condition
lectrode
commented
4 years ago Ok. Btw, The .SRCINFO and PKGBUILD located in /var/cache/pikaur/aur_repos/pikaur-git/ do not appear incomplete. They are identical to what is on aur.archlinux.org for both crashes (I deleted /var/cache/pikaur between attempts).
The crash logs appear to be different. They're both transient issues, but they have different crash traces. Not sure if the 2nd crash is a separate issue or another symptom of the same issue.
actionless
commented
4 years ago @lectrode also i see in your test runs you're always using root/dynamic_users
is it the same reproducible when running pikaur from unprivileged user without systemd dynamic users?
lectrode
commented
4 years ago I can confirm that this only appears to happen when run as root, or when alwaysusedynamicusers = yes. There were no issues when running it without dynamic_users.
actionless
commented
1 year ago i wonder if it's still reproducible?
Pikaur crashes with
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'after doing the following:The installation succeeded successfully when first doing
pikaur -Syu --neededand thenpikaur -Syu --needed slack-desktop, both times deselecting the same packages as above, where the error occurred.The following warning already seems suspicious to me:
:: warning: Some build deps removed for slack-desktop package: libsecret, xdg-utils, libxtst, libxss, nss, alsa-lib, gtk3, suggesting that the dependencies are not listed in the file for manually selecting packages and not added afterwards.I am not sure whether I can reproduce it now, maybe this is already enough to find the error.