W: Bizarre Error - File size is not what the server reported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Debian) |
Fix Released
|
Unknown
|
|||
apt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Oneiric |
Won't Fix
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have a private, GPG-signed repository that I use to distribute pre-packaged software to our servers and workstations. Use of this private repository has been without a hitch for years until now: Attempting to distribute a very large (2.3GB) package file, apt-fails with the following error message:
----------
# apt-get install <package>
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
<package>
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 2,224 MB of archives.
After this operation, 4,416 MB of additional disk space will be used.
Get:1 http://<url>/ stable/main <package> amd64 4 [2,224 MB]
Fetched 1 B in 38s (0 B/s)
Failed to fetch http://[<url-deleted>
W: Bizarre Error - File size is not what the server reported 2224455066 184467440716390
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
----------
The correct file size of the package file is: 2224455066
The entry for this package in the repository's Packages file:
----------
Package: <package>
Version: 4
Architecture: amd64
Maintainer: Michael Peek <email address hidden>
Installed-Size: 4312636
Filename: ./pool/
Size: 2224455066
MD5sum: e0daf5d8a658821
SHA1: a47121319aa4262
SHA256: e38a7f4d5ccce10
Section: non-free/admin
Priority: extra
Homepage: <url>
Description: <description>
<long description>
----------
Note that the size listed in the Packages entry is correct, and corresponds to the first number reported by the "Bizarre Error" warning returned by apt-get. But the second number, 184467440716390
The package has been re-built and the repository package files re-generated several times, to no avail. This bug may be related to this one: http://
NOTE: This bug has been reported before, and reportedly fixed, as bugs #122294 (2007) and #176675 (2009). Since this bug is clearly still happening and is referenced by an upstream Debian bug report I thought I would merely reference the other bugs here and open a new report.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: apt 0.8.13.2ubuntu4.1
ProcVersionSign
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Mon Jul 25 09:15:24 2011
InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
LANGUAGE=en_US:
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in apt (Debian): | |
status: | Unknown → Fix Released |
Changed in apt (Ubuntu): | |
status: | New → Confirmed |
The latest incarnation of this in debian is http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 632271
(your referred bugreport is just a report to change the message, which was done).
This bug is hopefully finally fixed in the version currently sitting in debian experimental. It would be splendid if you could try this version in a vm/chroot or alike and report back as it is untested so far (there are not many users around which have packages >2 GB or even >4 GB handy… and i am not one of those)