apport report blocking of dpkg I/O errors is incomplete

The Lucid version of dpkg has the following:

        if (bytesread < 0 || byteswritten < 0)
                ohshite(_("failed in buffer_copy (%s)"), desc);
        if (limit > 0)
                ohshit(_("short read in buffer_copy (%s)"), desc);

While apt looks for:

   if(strstr(errormsg, "short read in buffer_copy (")) {
      std::clog << _("No apport report written because the error message indicates a dpkg I/O error") << std::endl;
      return;
   }

So depending on the volume of apport-package bug reports regarding Lucid with 'failed in buffer_copy' this may be worth SRUing.

The Maverick version of dpkg uses the following:

        if (bytesread < 0)
                ohshite(_("failed to read on buffer copy for %s"), desc);
        if (byteswritten < 0)
                ohshite(_("failed in write on buffer copy for %s"), desc);
        if (limit > 0)
                ohshit(_("short read on buffer copy for %s"), desc);

Which is the same as Natty.

mvo - I found the reason for some of the additional apport package bug reports and I've attached a branch for Natty that should fix it. I haven't had a chance to test it yet though.

Uploaded to both natty-propposed and maverick-proposed now

Accepted apt into natty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted apt into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I've been running apt version 0.8.13.2ubuntu3 from a local build since I reported this bug and haven't had any issues upgrading packages.

Sorry, I misread it as "apport", but apt is a binary package. Setting back to v-needed for confirming with the actual package in the archive, and also for maverick.

I've testing the Maverick proposed package and did not encounter any regression with it (did a lot of installs, removals, etc). Also i've been using the one for Natty for a few days already and everything works fine as well, setting this as verification done.

I also installed an Ubuntu desktop from a Maverick ISO, then installed the version of apt in maverick-proposed and installed all the packages in -updates and -proposed without any issues.

This bug was fixed in the package apt - 0.8.13.2ubuntu3

---------------
apt (0.8.13.2ubuntu3) natty-proposed; urgency=low

  * apt-pkg/deb/dpkgpm.cc:
    - stop reporting of apport-package bug reports regarding
      dpkg I/O errors (LP: #767776)
 -- Brian Murray <email address hidden> Wed, 20 Apr 2011 15:05:12 -0700

This bug was fixed in the package apt - 0.8.3ubuntu7.1

---------------
apt (0.8.3ubuntu7.1) maverick-proposed; urgency=low

  [ Brian Murray ]
  * apt-pkg/deb/dpkgpm.cc:
    - stop reporting of apport-package bug reports regarding
      dpkg I/O errors (LP: #767776)

  [ Michael Vogt ]
  * apt-pkg/deb/dpkgpm.cc:
    - backport improved dpkg I/O error detection
 -- Michael Vogt <email address hidden> Thu, 21 Apr 2011 15:41:29 +0200

This fix is included in Oneiric's version of apt.

Can someone explain the decision to mark this Won'tFix in Lucid? This bug seems to block the installation of linux-image-2.6.32-33-generic on one of our lucid machines, and being that it is an LTS release I find it surprising that this will not be fixed or even backported.

@Ryan - this bug report is about modifying apt to prevent specific types of package installation failures from being reported to Launchpad by apport. If you happen to be having a problem installing linux-image on a Lucid machine and have found this bug report I'd guess its because you are seeing 'short read in buffer_copy' error message when trying to install the package. This is likely due to a hardware or memory failure on your system which is corrupting the package. You should try investigating the system to see if it is failing. Thanks and good luck.