Skip to main content ↑ ↓
Topic: Maximum file size exceeded (Read 5953 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Maximum file size exceeded

Updating today with pacman -Syyu failed:
:: Retrieving packages...
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from ftp.cc.uoc.gr : Maximum file size exceeded
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from mirror.clarkson.edu : Maximum file size exceeded
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from ftp.sh.cvut.cz : The requested URL returned error: 404
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from www.uex.dk : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.



https://ftp.cc.uoc.gr/mirrors/linux/artixlinux/system/os/x86_64/

pacman-5.1.0-1-x86_64.pkg.tar.xz                   31-May-2018 17:23    745K
pacman-5.1.0-1-x86_64.pkg.tar.xz.sig               31-May-2018 17:23     566

The files are in the repo, so I downloaded them manually and placed in cachedir:

$ sudo cp pacman-5.1.0-1-x86_64.pkg.tar.xz* /var/cache/pacman/pkg/


:: Proceed with installation? [Y/n] y
(62/62) checking keys in keyring
[################################################################] 100%
downloading required keys...
:: Import PGP key 256E/1A60DC44245D06FEF90623D6EEEEE2EEEE2EEEEE, "Gaetan Bisson <[email protected]>", created: 1998-03-24? [Y/n] y
(62/62) checking package integrity
[################################################################] 100%
error: pacman: signature from "Cromnix (Buildbot) <[email protected]>" is invalid
:: File /var/cache/pacman/pkg/pacman-5.1.0-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

There is some sort of signature issue, so clearly the pacman package has been replaced with a counterfeit one by evil hackers from Mars. I'm not sure of what is the best method to proceed.

Re: Maximum file size exceeded

Reply #1 –
Same issue here but I'll wait until the repo issue is worked out.
OS: Artix x86_64
Host: Predator PH517-61 V1.07
CPU: AMD Ryzen 7 2700 (16) @ 3.2GHz [112.4°F]
GPU: AMD ATI Radeon RX Vega 56/64
Memory: 1129MiB / 64390MiB

Re: Maximum file size exceeded

Reply #2 –
Remove the packages effected from /var/cache/pacman/pkg  then sudo pacman -Syyu and see if it updates correctly

Re: Maximum file size exceeded

Reply #3 –
Well I rm'ed the offending pacman packages from the cache again, and tried to build the new pacman version from source using makepkg, but that failed with a pgp signature error too. Apparently I can still install  packages with pacman -S though, as I  installed svn to do this. I just tried sudo pacman -Syyu and that still gives the same errors as before.
Code: [Select]
$ svn export https://github.com/artix-linux/packages/trunk/pacman/repos/core-x86_64
A    core-x86_64
A    core-x86_64/PKGBUILD
A    core-x86_64/makepkg.conf
A    core-x86_64/pacman.conf
Exported revision 3290.

$ makepkg -sirc
==> Making package: pacman 5.1.0-1 (Sat  2 Jun 03:38:52 BST 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...

Packages (5) docbook-xml-4.5-6  docbook-xsl-1.79.2-4  libxslt-1.1.32+3+g32c88216-1  asciidoc-8.6.10-1  fakechroot-2.19-1

Total Download Size:    1.64 MiB
Total Installed Size:  19.60 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 libxslt-1.1.32+3+g32c88216-1-x86_64                                              361.9 KiB   137K/s 00:03 [################################################################] 100%
 docbook-xml-4.5-6-any                                                             84.7 KiB   187K/s 00:00 [################################################################] 100%
 docbook-xsl-1.79.2-4-any                                                         729.1 KiB   107K/s 00:07 [################################################################] 100%
 fakechroot-2.19-1-x86_64                                                          48.1 KiB   140K/s 00:00 [################################################################] 100%
 asciidoc-8.6.10-1-any                                                            458.8 KiB   123K/s 00:04 [################################################################] 100%
(5/5) checking keys in keyring                                                                             [################################################################] 100%
(5/5) checking package integrity                                                                           [################################################################] 100%
(5/5) loading package files                                                                                [################################################################] 100%
(5/5) checking for file conflicts                                                                          [################################################################] 100%
(5/5) checking available disk space                                                                        [################################################################] 100%
:: Processing package changes...
(1/5) installing libxslt                                                                                   [################################################################] 100%
(2/5) installing docbook-xml                                                                               [################################################################] 100%
(3/5) installing docbook-xsl                                                                               [################################################################] 100%
(4/5) installing asciidoc                                                                                  [################################################################] 100%
Optional dependencies for asciidoc
    lilypond: music-filter
    imagemagick: music-filter (used in conjunction with lilypond)
    source-highlight: source-highlight-filter
    dblatex: pdf generation
    fop: alternative pdf generation
    lynx: text generation
    w3m: text generation (alternative to lynx)
(5/5) installing fakechroot                                                                                [################################################################] 100%
==> Retrieving sources...
  -> Downloading pacman-5.1.0.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3256k  100 3256k    0     0   322k      0  0:00:10  0:00:10 --:--:--  332k
  -> Downloading pacman-5.1.0.tar.gz.sig...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   310  100   310    0     0    652      0 --:--:-- --:--:-- --:--:--   652
  -> Found pacman.conf
  -> Found makepkg.conf
==> Validating source files with sha256sums...
    pacman-5.1.0.tar.gz ... Passed
    pacman-5.1.0.tar.gz.sig ... Skipped
    pacman.conf ... Passed
    makepkg.conf ... Passed
==> Verifying source file signatures with gpg...
    pacman-5.1.0.tar.gz ... FAILED (unknown public key F99FFE0FEAE999BD)
==> ERROR: One or more PGP signatures could not be verified!
==> Removing installed dependencies...
checking dependencies...

Packages (5) asciidoc-8.6.10-1  docbook-xml-4.5-6  docbook-xsl-1.79.2-4  fakechroot-2.19-1  libxslt-1.1.32+3+g32c88216-1

Total Removed Size:  19.60 MiB

:: Do you want to remove these packages? [Y/n] y
:: Processing package changes...
(1/5) removing fakechroot                                                                                  [################################################################] 100%
(2/5) removing asciidoc                                                                                    [################################################################] 100%
(3/5) removing docbook-xsl                                                                                 [################################################################] 100%
(4/5) removing libxslt                                                                                     [################################################################] 100%
(5/5) removing docbook-xml                                                                                 [################################################################] 100%

Re: Maximum file size exceeded

Reply #4 –
Quote from: mandog – on
Remove the packages effected from /var/cache/pacman/pkg  then sudo pacman -Syyu and see if it updates correctly

Failed.  Same error.

Code: [Select]
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from jenkins.artixlinux.org:55555 : Maximum file size exceeded
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from mirror1.artixlinux.org : Maximum file size exceeded
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from artix.wheaton.edu : Maximum file size exceeded
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from mirror.strits.dk : Maximum file size exceeded
error: failed retrieving file 'pacman-5.1.0-1-x86_64.pkg.tar.xz' from mirrors.dotsrc.org : Maximum file size exceeded
warning: failed to retrieve some files
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.
OS: Artix x86_64
Host: Predator PH517-61 V1.07
CPU: AMD Ryzen 7 2700 (16) @ 3.2GHz [112.4°F]
GPU: AMD ATI Radeon RX Vega 56/64
Memory: 1129MiB / 64390MiB

Re: Maximum file size exceeded

Reply #5 –
I also experienced this issue. I had to manually download the tar.xz for pacman from one of the mirrors and then install it locally with pacman -U. After that, everything worked smoothly.

Re: Maximum file size exceeded

Reply #6 –
This command fixed the pgp build error:
$ GNUPGHOME=/etc/pacman.d/gnupg makepkg -sirc

Then I got a problem with the tests from make --check failing so the build failed again. This was because I was missing a few of the packages from the base-devel group:
$ sudo pacman -S base-devel
:: There are 26 members in group base-devel:
:: Repository system
   1) autoconf  2) automake  3) binutils  4) bison  5) fakeroot  6) file  7) findutils  8) flex  9) gawk  10) gcc  11) gettext  12) grep  13) groff  14) gzip
   15) libelogind   16) libtool  17) m4  18) make  19) pacman  20) patch  21) pkg-config  22) sed  23) sudo  24) texinfo  25) util-linux  26) which

But I couldn't install that because it included pacman.
So I installed just the ones I was missing, I think it was probably the lack of fakeroot that caused the tests to fail:
$ sudo pacman -S fakeroot bison flex texinfo
$ GNUPGHOME=/etc/pacman.d/gnupg makepkg -sirc
Success!
pacman -Syu worked.

An updated pacman with no danger of Martian involvement.

The only thing was the latest xorg-server -5 packages still don't fix the earlier no X problem so I downgraded them again and put them back as ignorepkg's.

Re: Maximum file size exceeded

Reply #7 –
Having built pacman, updating today I had this:
Code: [Select]
error: failed to prepare transaction (could not satisfy dependencies)
:: installing pacman (5.1.0-2) breaks dependency 'pacman=5.1.0-1' required by pacman-debug
$ sudo pacman -R pacman-debug
So removing the previously built pacman-debug package created by building from source as above fixed this.
pacman is back, man!  ;D  The new -2 version is installing without problems.

Re: Maximum file size exceeded

Reply #8 –
Quote from: ####### – on
So removing the previously built pacman-debug package created by building from source as above fixed this.
pacman is back, man!  ;D  The new -2 version is installing without problems.

So the moral of the story is not to build from source?

Re: Maximum file size exceeded

Reply #9 –
Use a build helper, or be prepared to resolve issues! And follow psy0nic's advice, it was scarcely worth building for it to be replaced the next day.  ;D  But I wanted to install some new stuff at the time with a fully up to date system so just went ahead regardless.