ok. thanks for your valuable help. I could solve this issue running. pbuilder clean
and the error is gone. Best regards, Elías Alejandro On Wed, Jul 6, 2016 at 12:08 PM, Christian Seiler <christ...@iwakd.de> wrote: > On 07/06/2016 06:55 PM, Gianfranco Costamagna wrote: > > Sometimes I'm behind a proxy, and I get a *lot* of hash sum mismatches > > when using pbuilder/sbuild. > > On actual package files or just the "Packages" / "Contents" > files while pbuilder is doing "apt-get update"? If it's the > latter, that problem should not exist anymore for stretch > and/or sid (search "by-hash" in that email): > > https://lists.debian.org/debian-devel-announce/2016/06/msg00002.html > > If it's for packages themselves, then something's wrong with > your proxy, because that should definitely not happen. > (Package file names are unique in the proper Debian archive, > so it should never be the the case that a package file is > replaced.) > > > Retry the build works, but I have to say, packages are put in aptcache > > only when the md5 is verified AFAIK, so the question is: > > how a broken md5 did end up in that directory in first place? > > I agree, hence I assume this happened by means of "out of disk > space" (look at the errror message) while copying back the > cached contents (at the end of a build). Don't know for sure, > though. > > Regards, > Christian >
