[Bug 773172] Re: corrupted filesystem tarfile - corrupted package archive

[evalckea]

Really the apt-get help mi to correct the problem, after this it has
installed without any problem.


2013/4/6 Majal Abe Mirasol <773172 at bugs.launchpad.net>

> If a package is broken, usually due to internet connection/download
> problems, I would usually delete the problematic package, eg:
>
> sudo rm /VAR/CACHE/APT/ARCHIVES/PYTHON-QT4_4.8.3-2_AMD64.DEB
>
> after that, running:
>
> sudo apt-get -f install
> or
> reinstalling the program by command line
>
> would solve the problem where apt-get would download a new copy of the
> package.
>
> What I would like to suggest is that, during problems like these
> (damaged packages, error returns), apt-get could be set to first check
> the integrity (checksum/signature) of the problematic package, comparing
> it to the online signature, and if it is found to be different, a new
> copy could be automatically downloaded from the repos and installed.
> Just a suggestion, but I totally don't know the security/other concerns
> surrounding that implementation.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (993522).
> https://bugs.launchpad.net/bugs/773172
>
> Title:
>   corrupted filesystem tarfile - corrupted package archive
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/773172/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/773172

Title:
  corrupted filesystem tarfile - corrupted package archive

Status in “update-manager” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: update-manager

  '/VAR/CACHE/APT/ARCHIVES/PYTHON-QT4_4.8.3-2_AMD64.DEB' package may not
  be in working state.  could not install'/VAR/CACHE/APT/ARCHIVES
  /PYTHON-QT4_4.8.3-2_AMD64.DEB'

  Note well:

  While comment #1 will resolve the immediate issue - it is possible
  that the package became corrupted on your system due to filesystem or
  memory corruption so one should run an fsck on your filesystem and a
  memory test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/773172/+subscriptions