Sometimes, when Maat gets several new packages added to the repo, if the dependencies are alphabetically sorted before the package, then the package data will change and the dependencies won't install during runtime. This can be fixed with a one-time install of the dependency manually, but that's less than ideal if we can avoid it.
Symptomatic output can look like this:
|> pacman -S dotnet-runtime-bin
resolving dependencies...
looking for conflicting packages...
Packages (2) dotnet-host-3.1.0.sdk100-2 dotnet-runtime-bin-3.1.1.sdk101-2
Total Download Size: 5.20 MiB
Total Installed Size: 66.94 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
dotnet-runtime-bin-3.1.1.sdk101-2-x86_64 5.2 MiB 11.3 MiB/s 00:00 [--------------------------------------------------------------] 100%
(2/2) checking keys in keyring [--------------------------------------------------------------] 100%
(2/2) checking package integrity [--------------------------------------------------------------] 100%
error: dotnet-runtime-bin: signature from "DarkFeather <ircs://aninix.net:6697/DarkFeather>" is invalid
:: File /var/cache/pacman/pkg/dotnet-runtime-bin-3.1.1.sdk101-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
Sometimes, when Maat gets several new packages added to the repo, if the dependencies are alphabetically sorted before the package, then the package data will change and the dependencies won't install during runtime. This can be fixed with a one-time install of the dependency manually, but that's less than ideal if we can avoid it.
Symptomatic output can look like this:
```
|> pacman -S dotnet-runtime-bin
resolving dependencies...
looking for conflicting packages...
Packages (2) dotnet-host-3.1.0.sdk100-2 dotnet-runtime-bin-3.1.1.sdk101-2
Total Download Size: 5.20 MiB
Total Installed Size: 66.94 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
dotnet-runtime-bin-3.1.1.sdk101-2-x86_64 5.2 MiB 11.3 MiB/s 00:00 [--------------------------------------------------------------] 100%
(2/2) checking keys in keyring [--------------------------------------------------------------] 100%
(2/2) checking package integrity [--------------------------------------------------------------] 100%
error: dotnet-runtime-bin: signature from "DarkFeather <ircs://aninix.net:6697/DarkFeather>" is invalid
:: File /var/cache/pacman/pkg/dotnet-runtime-bin-3.1.1.sdk101-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Sometimes, when Maat gets several new packages added to the repo, if the dependencies are alphabetically sorted before the package, then the package data will change and the dependencies won't install during runtime. This can be fixed with a one-time install of the dependency manually, but that's less than ideal if we can avoid it.
Symptomatic output can look like this:
This is a duplicate of #1