package python2.5-dev None [modified: /var/lib/dpkg/info/python2.5-dev.list] failed to install/upgrade: misslyckades i buffer_write(handtag) (10, ret=-1): bakändan dpkg-deb under "./usr/lib/python2.5/config/libpython2.5.a"

[Tor-björn Claesson]

Binary package hint: python2.5

While trying to install pydev

ProblemType: Package
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 8.10
ErrorMessage: misslyckades i buffer_write(handtag) (10, ret=-1): bakändan dpkg-deb under "./usr/lib/python2.5/config/libpython2.5.a"
Package: python2.5-dev None [modified: /var/lib/dpkg/info/python2.5-dev.list]
SourcePackage: python2.5
Title: package python2.5-dev None [modified: /var/lib/dpkg/info/python2.5-dev.list] failed to install/upgrade: misslyckades i buffer_write(handtag) (10, ret=-1): bakändan dpkg-deb under "./usr/lib/python2.5/config/libpython2.5.a"
Uname: Linux 2.6.27-9-generic i686

[Matthias Klose (doko)]

Tor-björn Claesson schrieb:
> Public bug reported:
>
> Binary package hint: python2.5
>
> While trying to install pydev
>
> ProblemType: Package
> Architecture: i386
> Dependencies:
>
> DistroRelease: Ubuntu 8.10
> ErrorMessage: misslyckades i buffer_write(handtag) (10, ret=-1): bakändan dpkg-deb under "./usr/lib/python2.5/config/libpython2.5.a"
> Package: python2.5-dev None [modified: /var/lib/dpkg/info/python2.5-dev.list]

please re-run with LANG=C or english language set.

[Tor-björn Claesson (tclaesson)]

Fixed the problem locally, unable to reproduce

[Matthias Klose (doko)]

not a python2.5 issue

[Dominik Stadler (dominik-stadler)]

Looking at the attached dpkg-log, the following line shows the following reason for this problem:

dpkg: fel vid hantering av /var/cache/apt/archives/python2.5-dev_2.5.2-11.1ubuntu1_i386.deb (--unpack):
 misslyckades i buffer_write(handtag) (10, ret=-1): bakändan dpkg-deb under "./usr/lib/python2.5/config/libpython2.5.a": Enheten är full

"no space left on device" means that simply the disk ran out of space here, I don't think this is a problem of the package itself but rather shortage of general disk space is the cause of this problem.

Therefore I am closing this as duplicate of bug 312491 where improving the error message display is discussed, for now please try to make more space available on your harddrive and then try again.