• Corrupt or invalid files in update


    I had this pop up in my last update attempt. Any suggestions? I’ve never had issue with Antergos specific updates before. Any help would me much appreciated.

    error: antergos-keyring: signature from "Antergos Build Server (Automated Package Build System) <[email protected]>" is unknown trust
    :: File /var/cache/pacman/pkg/antergos-keyring-20170524-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] y
    error: tilix: signature from "Antergos Build Server (Automated Package Build System) <[email protected]>" is unknown trust
    :: File /var/cache/pacman/pkg/tilix-1.5.8-1-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)
    Errors occurred, no packages were upgraded.
    
  • Changing SigLevel to ‘Optional TrustAll’ in my pacman.conf helped when I had the same error when trying to upgrade GitKraken.

  • Looks like some other folks had similar issues in other threads and sudo pacman-key --refresh-keys worked for them.

  • Please see: https://forum.antergos.com/topic/6984/error-with-antergos-keyring for possible reasons and solutions.

    And PLEASE don’t use TrustALL if you do not really wan’t to open your system.

    @bytefu suggests in https://forum.antergos.com/topic/6996/antergos-keyring-package-corrupted/9

    Try to disable signature checks for “antergos” repo in /etc/pacman.conf (SignatureLevel = Never), reinstall antergos-keyring and re-enable signature checks. Worked for me.

  • Thanks for the info @thomas-kerpe.

  • @bazini2880 said in Corrupt or invalid files in update:

    sudo pacman-key --refresh-keys

    but only if you install the new keyring before …

    wget http://mirrors.antergos.com/antergos/x86_64/antergos-keyring-20170524-1-any.pkg.tar.xz
    pacman -U antergos-keyring-20170524-1-any.pkg.tar.xz
    sudo pacman -Scc
    sudo pacman-key --refresh-keys
    sudo pacman -Syu
    

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    https://forum.antergos.com/topic/1883/how-to-include-system-logs-when-asking-for-help

  • @joekamprad or:

    @thomas.kerpe said in Error with antergos-keyring:

    Manually importing the “broken key”
    gpg --recv-key 24B445614FAC071891EDCE49CDBD406AA1AA7A1D

    gpg -a --export 24B445614FAC071891EDCE49CDBD406AA1AA7A1D | sudo pacman-key -a -

    After that I could run my updates again, I additionally reinstalled antergos-keyring, just to be sure.
    yaourt -S antergos-keyring.

  • @thomas.kerpe this problem done a so big KAOS ;) … i think they are around 23 Treats with the same issue…

    But for safety it is he better way to follow your instruction… because with downloading the package over wget + URL i can give you a corrupted package and if you install it with pacman -U it will not be verified…

    But also if you do not check what your command:

    gpg --recv-key “longstrangenumbers” gives back … you can force someone to import my special key and then i may can login over ssh on this machine ?
    I am joking only… but we need to think about safety also …

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    https://forum.antergos.com/topic/1883/how-to-include-system-logs-when-asking-for-help

  • @joekamprad

    I get invalid or corrupted package (PGP signature) on step 2.

    Coder / Tech enthusiast / Linux convert / Motocross fan / Master Procrastinator

  • @joekamprad
    Thanks, brother. Worked perfect.
    You guys are awesome.

    Karl Schneider

corrupt4 invalid7 Posts 10Views 1103
Log in to reply