Dpkg deb error subprocess tar returned error exit status 2

Содержание

Linux Mint Forums
[SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13
[SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13
Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
Debian User Forums
Dpkg error can’t solve
Dpkg error can’t solve
[Tutorial] How to fix «subprocess dpkg-deb —control returned error exit status 2» after «re-jailbreaking» iOS 8 (possibly other versions too)
Dpkg deb error subprocess tar returned error exit status 2

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13

Post by LittleScriptMan » Mon Jun 20, 2022 5:36 am

Tried this morning to update apturl package version 0.5.2+linuxmint12 as suggested in Update Manager but got these errors in return

/var/cache/apt/archives/apturl_0.5.2+linuxmint12_all.deb uses an unknown compression process for control.tar.zst

and :
dpkg-deb —control subprocess returned error exit status 2
(which seems to be an unpack error probably caused by the unability to perform decompression of the archive).

Thanks for any help or suggestion.

PS : quick insight of the system (inxi -GS + Repos) — Kernel upgrade was necessary to allow wifi connection which didn’t work with 5.10 serie

Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)

Post by abu » Mon Jun 20, 2022 6:15 am

Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)

Post by karlchen » Mon Jun 20, 2022 6:52 am

Hello, LittleScriptMan. Hello, Abu.

Foreword:
At this point in time I can only crosscheck with LM 19.3, apturl 0.5.2+linuxmint8. LM 19.3 is not LMDE, so my findings may or may not be relevant.

Inner archive format of apturl.deb package
The inner archives in apturl 0.5.2+linuxmint8 is still .xz. No problem reading and extracting .xz archives here.
But on LMDE 4 and LMDE 5 the latest apturl 0.5.2+linuxmint12 has got inner archives of the format .zst.

In order to read .zst archives you seem to need a package simply named zstd.
By default this package is not pre-installed on LM 19.3.

I am not sure whether it will really resolve your problem.
Check whether zstd is available on your LMDE systems. Command: which zstd
In case this comes back empty, you might install zstd from the software repos.
Command: sudo apt-get install zstd
This might be sufficient to enable the Update Manager to read and install the apturl package 0.5.2+linuxmint12.
It is imaginable, however, that Update Manager will not use the commandline tool zstd, but instead some supporting library, which provides .zst archive reading capabilities.
In this case, you will have to wait for advice given by other LMDE users.

Update/Solution:
As explained in Clem’s post further down , the problem has been resolved by publishing a corrected apturl 0.5.2+linuxmint13.
So refresh your list of available software updates. It should display apturl 0.5.2+linuxmint13. The inner archives are in .xz format again. The installation should succeed.

Источник

Debian User Forums

Dpkg error can’t solve

#1 Post by theblueplll » 2019-07-04 15:29

Machine is an older machine I was trying to setup for a project running Debian Buster 32bit
AMD Semperon 3000+ 1.5gb ram no desktop(don’t need one for what I want to do)

Seems to run great untill I try to install a package.
I don’t have anything from any repo besides Debians official repos on purpose.

I keep getting this when I try to install things.

Partitions are setup like this

Doesn’t seem to matter what it is although some packages will install without error.

Have tried the instructions at this link and a few similar things to no avail

I also can NOT remove the package once this happens when I try to I get unment dependency warnings.
And if I try to install the dependencies it starts with the dpkg errors all over again.

This started when I had Buster installed on it originally so I switched to Stretch thinking the older hardware would work better but had the same problem.
So i reinstalled Buster again and some stuff was whacky so I looked into it and found out either my iso was corrupted or my flash drive was acting funny.
So I tried with a new usb stick and a fresh download that I verified and check for integrity and it seemed to install a lot faster and smoother.

2 days go by and the problem comes back.
Could this be a hardware problem somehow? Maybe a bad hdd?
Both drives are kind of old.

Any other information that could be needed please just ask and I will do my best to share it.

Источник

[Tutorial] How to fix «subprocess dpkg-deb —control returned error exit status 2» after «re-jailbreaking» iOS 8 (possibly other versions too)

In trying to compile a linux package for iOS 8, I accidentally removed bash and sh. Yes, you read that right. don’t judge me.

Anyway, for a long time, I thought I was completely screwed, and would have to upgrade and lose my jailbreak (and beloved iOS 8 podcasts app) because I had no access to a shell to replace the missing shells, and no file explorer apps worked because they also depend on a shell to launch.

Long story short, after many attempts, I finally found a specific configuration of hardware+windows+itunes+taig that allowed me to «rejailbreak» without restoring, the utility being that /bin would be repopulated with the needed shells. To my amazement, it worked, and for the first time in months, substrate launched and I had a working shell.

However, when I opened Cydia to update my packages, I ran into this problem upon trying to install anything:

subprocess dpkg-deb —control returned error exit status 2

Sub-process /usr/libexec/cydia/cydo returned an error code (1)

I did some looking around on reddit, JailbreakQA, and IRC, and discovered that this was a common issue on «rejailbroken» iOS 8 devices (perhaps others, I don’t really know), and that the only way to fix it is to restore and rejailbreak (which is not feasible because it would force me onto iOS 11).

HOWEVER, I decided to try running dpkg (which is what Cydia attempts to run when making modifications to packages) in a shell, to see if I would get a more verbose error. I did indeed.

«tar», which is run by dpkg, reported this problem:

tar: unrecognized option `—warning=no-timestamp’

It turns out, this is the only problem. It doesn’t require a restore at all. So, here is how to fix this yourself, and enable packages to be installed and otherwise modified in Cydia once again:

Get a copy of tar 1.29 built for iOS. You can fetch this from the /usr/bin/ directory of a fully functional jailbroken device on iOS 8+. If you don’t have access to such a device, I’ve uploaded the binary I used to dropbox at this location.

Once you have tar, copy it to /usr/bin, and /bin. If you used the copy I fetched, you might need to run chmod +x before it will work.

Reboot your device. For whatever reason, respringing wasn’t enough for me.

Profit! tar, dpkg, and cydia should now behave as expected.

Источник

I’ve just installed Ubuntu v10.10 on my laptop that previously had v10.04 installed on it.Now whenever I try to install ANY software, I get a message sayinh that the package operation failed.

For example, Update Manager stops with the following:

installArchives() failed: Preconfiguring packages .
Preconfiguring packages .
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/linux-image-2.6.35-22-generic_2.6.35-22.34_i386.deb (—unpack):
subprocess dpkg-deb —control returned error exit status 2
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/tzdata_2010m-0ubuntu0.10.10_all.deb (—unpack):
subprocess dpkg-deb —control returned error exit status 2
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-2.6.35-22-generic_2.6.35-22.34_i386.deb
/var/cache/apt/archives/tzdata_2010m-0ubuntu0.10.10_all.deb

Unfortunately, I’m not that familiar with these types of messages and I’m having great difficulty trying to track down the cause of the problem.

If there’s anyone out there who can offer some assistance, I’d very much appreciate it.

I was having a similar issue. From terminal enter:

sudo apt-get clean
That will clear all of the downloaded packages. Then go to «Update Manager» and try again. There is probably a bad package causing the errors.

Thanks for the prompt reply.

I’ve tried ‘sudo apt-get clean’ as you suggested. This made now difference.

Having read through the original error, I thought I’d try not installing the 2 packages that seemed to be causing the issue, ie, linux-image-2.6.35-22-generic_2.6.35-22.34_i386.deb and tzdata_2010m-0ubuntu0.10.10_all.deb by removing the ‘ticks’ from the Update Manager list. However, when I did this and tried again it got this error:

installArchives() failed: (Reading database . (Reading database . 5% (Reading database . 10% (Reading database . 15% (Reading database . 20% (Reading database . 25% (Reading database . 30% (Reading database . 35% (Reading database . 40% (Reading database . 45% (Reading database . 50% (Reading database . 55% (Reading database . 60% (Reading database . 65% (Reading database . 70% (Reading database . 75% (Reading database . 80% (Reading database . 85% (Reading database . 90% (Reading database . 95% (Reading database . 100% (Reading database . 118295 files and directories currently installed.)
Preparing to replace libvte-common 1:0.26.0-0ubuntu1 (using . /libvte-common_1%3a0.26.0-0ubuntu2_all.deb) .
Unpacking replacement libvte-common .
dpkg: error processing /var/cache/apt/archives/libvte-common_1%3a0.26.0-0ubuntu2_all.deb (—unpack):
corrupted filesystem tarfile — corrupted package archive
No apport report written because MaxReports is reached already
Preparing to replace libvte9 1:0.26.0-0ubuntu1 (using . /libvte9_1%3a0.26.0-0ubuntu2_i386.deb) .
Unpacking replacement libvte9 .
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
dpkg-deb: subprocess returned error exit status 2
dpkg: error processing /var/cache/apt/archives/libvte9_1%3a0.26.0-0ubuntu2_i386.deb (—unpack):
short read on buffer copy for backend dpkg-deb during `./usr/lib/libvte.so.9.2600.0′
No apport report written because MaxReports is reached already
Preparing to replace python-vte 1:0.26.0-0ubuntu1 (using . /python-vte_1%3a0.26.0-0ubuntu2_i386.deb) .
Unpacking replacement python-vte .
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
dpkg-deb: subprocess returned error exit status 2
dpkg: error processing /var/cache/apt/archives/python-vte_1%3a0.26.0-0ubuntu2_i386.deb (—unpack):
short read on buffer copy for backend dpkg-deb during `./usr/lib/pyshared/python2.6/gtk-2.0/vtemodule.so’
No apport report written because MaxReports is reached already
Preparing to replace update-manager 1:0.142.19 (using . /update-manager_1%3a0.142.20_all.deb) .
Unpacking replacement update-manager .
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
dpkg-deb: subprocess returned error exit status 2
dpkg: error processing /var/cache/apt/archives/update-manager_1%3a0.142.20_all.deb (—unpack):
short read on buffer copy for backend dpkg-deb during `./usr/lib/update-manager/check-new-release-gtk’
No apport report written because MaxReports is reached already
Preparing to replace update-manager-core 1:0.142.19 (using . /update-manager-core_1%3a0.142.20_i386.deb) .
Unpacking replacement update-manager-core .
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid literal/lengths set’
dpkg-deb: subprocess returned error exit status 2
dpkg: error processing /var/cache/apt/archives/update-manager-core_1%3a0.142.20_i386.deb (—unpack):
subprocess dpkg-deb —fsys-tarfile returned error exit status 2
No apport report written because MaxReports is reached already
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/linux-headers-2.6.35-22_2.6.35-22.34_all.deb (—unpack):
subprocess dpkg-deb —control returned error exit status 2
No apport report written because MaxReports is reached already
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/linux-headers-2.6.35-22-generic_2.6.35-22.34_i386.deb (—unpack):
subprocess dpkg-deb —control returned error exit status 2
No apport report written because MaxReports is reached already
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/linux-libc-dev_2.6.35-1022.34_i386.deb (—unpack):
subprocess dpkg-deb —control returned error exit status 2
No apport report written because MaxReports is reached already
Processing triggers for python-support .
Processing triggers for python-central .
Errors were encountered while processing:
/var/cache/apt/archives/libvte-common_1%3a0.26.0-0ubuntu2_all.deb
/var/cache/apt/archives/libvte9_1%3a0.26.0-0ubuntu2_i386.deb
/var/cache/apt/archives/python-vte_1%3a0.26.0-0ubuntu2_i386.deb
/var/cache/apt/archives/update-manager_1%3a0.142.20_all.deb
/var/cache/apt/archives/update-manager-core_1%3a0.142.20_i386.deb
/var/cache/apt/archives/linux-headers-2.6.35-22_2.6.35-22.34_all.deb
/var/cache/apt/archives/linux-headers-2.6.35-22-generic_2.6.35-22.34_i386.deb
/var/cache/apt/archives/linux-libc-dev_2.6.35-1022.34_i386.deb

Go to the folder that was indicated in:

/var/cache/apt/archives/libvte-common_1%3a0.26.0-0ubuntu2_all.deb
/var/cache/apt/archives/libvte9_1%3a0.26.0-0ubuntu2_i386.deb
/var/cache/apt/archives/python-vte_1%3a0.26.0-0ubuntu2_i386.deb
/var/cache/apt/archives/update-manager_1%3a0.142.20_all.deb
/var/cache/apt/archives/update-manager-core_1%3a0.142.20_i386.deb
/var/cache/apt/archives/linux-headers-2.6.35-22_2.6.35-22.34_all.deb
/var/cache/apt/archives/linux-headers-2.6.35-22-generic_2.6.35-22.34_i386.deb
/var/cache/apt/archives/linux-libc-dev_2.6.35-1022.34_i386.deb

Delete those packages manually. You will likely have to open Nautilus via terminal to have root access.

Try that at least. That is what I did with my issue. Many of the things I see in your errors were similar to mine. May want to restart the computer after clearing out the cache.

Once again, thanks for the reply. I have done as you suggested, restarted the laptop, but it has made no difference. Error message once again:

installArchives() failed: Preconfiguring packages .
Preconfiguring packages .
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/linux-image-2.6.35-22-generic_2.6.35-22.34_i386.deb (—unpack):
subprocess dpkg-deb —control returned error exit status 2
No apport report written because MaxReports is reached already
dpkg-deb (subprocess): data: internal gzip read error: ‘ : invalid distance too far back’
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/tzdata_2010m-0ubuntu0.10.10_all.deb (—unpack):
subprocess dpkg-deb —control returned error exit status 2
No apport report written because MaxReports is reached already
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-2.6.35-22-generic_2.6.35-22.34_i386.deb
/var/cache/apt/archives/tzdata_2010m-0ubuntu0.10.10_all.deb

Do you have any more ideas or suggestions?
Thanks

I had the very same problem with 10.10 and it was caused by my system clock being incorrectly set!

I played around with the date and time settings to correct it and the updates/other software magically installed themselves. (Actually I’m running Ubuntu inside VB and my Windows clock was all out of whack too so I had to fix that one first).

Источник

Tried to install jenkins.deb and I got the shown below. Any ideas?

~$ sudo dpkg -i jenkins_1.609.1_all.deb 


(Reading database ... 118056 files and directories currently installed.)
Unpacking jenkins (from jenkins_1.609.1_all.deb) ...
dpkg-deb: file `jenkins_1.609.1_all.deb' contains ununderstood data member data.tar.xz     , giving up
dpkg: error processing jenkins_1.609.1_all.deb (--install):
 subprocess dpkg-deb --fsys-tarfile returned error exit status 2
Errors were encountered while processing:
 jenkins_1.609.1_all.deb

kyodake

14.7k3 gold badges36 silver badges44 bronze badges

asked Jul 26, 2015 at 14:13

The package install rule of the Makefile is creating the Debian package using xz compression.

Now, this kind of compression is supported by versions of dpkg equal or higher than 1.15.6.

So, in order to solve your problem, you should update dpkg to a newer version.

Or install gdebi, and install with that application.

I download the package and install it gdebi. In Xubuntu 15.04 package daemon is required

answered Jul 26, 2015 at 15:14

kyodakekyodake

14.7k3 gold badges36 silver badges44 bronze badges

Источник

You may not need to worry about downloading the tar package.

Chances are, to get to this point because you were in the middle of an upgrade, and your package management system will have already downloaded the latest tar package for you, so it will be waiting for you in:

/var/cache/apt/archives/tar_(version-release_platform).deb

e.g.:

# ls -t /var/cache/apt/archives/tar_*|head -1

/var/cache/apt/archives/tar_1.26-4_amd64.deb

This is how I fixed my system:

Find the latest version on your system:

root@host:~# ls -t /var/cache/apt/archives/tar_*|head -1
/var/cache/apt/archives/tar_1.26-4_amd64.deb

Create a temporary working area and unpack the .deb archive:

root@host:~# mkdir fix_tar
root@host:~# cd fix_tar
root@host:~/fix_tar# ar x /var/cache/apt/archives/tar_1.26-4_amd64.deb

Unpack the data.tar.gz file to find the new tar binary:

root@host:~/fix_tar# ls -l
total 972
-rw-r--r-- 1 root root   2536 2012-02-03 12:20 control.tar.gz
-rw-r--r-- 1 root root 978996 2012-02-03 12:20 data.tar.gz
-rw-r--r-- 1 root root      4 2012-02-03 12:20 debian-binary
root@host:~/fix_tar# tar xzf data.tar.gz
root@host:~/fix_tar# find * -name tar
bin/tar
usr/share/doc/tar
usr/lib/mime/packages/tar

Check the existing version on your system:

root@host:~/fix_tar# /bin/tar --version
tar (GNU tar) 1.20
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.

Backup the old version in case something goes horribly wrong and you need it back:

root@host:~/fix_tar# mv /bin/tar /bin/tar_1.20

Put the new copy in place:

root@host:~/fix_tar# mv ./bin/tar /bin/tar

Check the new version:

root@host:~/fix_tar# /bin/tar --version
tar (GNU tar) 1.26
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.

You’re done!

I was then able to carry on with another:

root@host:~# aptitude update
root@host:~# aptitude safe-upgrade

Источник

After running do-release-upgrade --proposed on my Ubuntu Server 8.04, I got the message:

The upgrade is completed but there were errors during the upgrade process.

Searching up the upgrade output, I found this:

Setting up tar (1.22-2) ...

tar: ./md5sums: Cannot utime: Bad file descriptor
tar: ./control: Cannot utime: Bad file descriptor
tar: .: Cannot utime: Bad file descriptor
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/diff_1%3a2.8.1-18_all.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/diff_1%3a2.8.1-18_all.deb
Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an error code (1)

Could not install the upgrades

The upgrade is now aborted. Your system could be in an unusable
state. A recovery will run now (dpkg --configure -a).

Apparenly, this is a known bug. More details are here and here.

I will post the workaround I found as an answer.

asked Jun 27, 2010 at 6:41

As a workaround, you can create a wrapper for tar that will add the --touch option:

create a file named tar under /usr/local/sbin with the following content:

#!/bin/sh
exec /bin/tar --touch -"$@"

Do:

chmod +x /usr/local/sbin/tar

Now run aptitude dist-upgrade to continue the upgrade process.
Delete this file after installation has completed.

answered Jun 27, 2010 at 6:47

itsadokitsadok

1,8595 gold badges21 silver badges33 bronze badges

Sometimes the /usr/local/sbin/tar trick doesn’t work.
But I found this option helped for me. Run

export TAR_OPTIONS='--touch'

Then continue with your

apt-get upgrade

answered Sep 17, 2010 at 15:36

I got this same error, and I couldn’t install anything with aptitude either because of tar being broken. I had to leave /usr/local/sbin/tar so that aptitude would continue to work correctly.

answered Jul 17, 2010 at 15:21

Источник

Theos is failing to build a package, yet it will ‘make’ it just fine. It returns the following with messages enabled:

dpkg-deb: building package `com.ethanarbuckle.alienblue++' in `./com.ethanarbuckle.alienblue++_0.0.1-19_iphoneos-arm.deb'.
dpkg-deb: ignoring 2 warnings about the control file(s)
dpkg-deb (subprocess): failed to exec tar -cf: No such file or directory
dpkg-deb: subprocess tar -cf returned error exit status 2
make: *** [internal-package] Error 2

I have not found a solution online, everyone says its an issue with tar, but tar is working fine. Does anyone know how to fix this?

It hasnt worked since I upgraded to osx 10.9, which Im sure is the cause of all of this

asked Jul 30, 2013 at 4:46

That’s because OSX 10.9 doesn’t ship with gnutar anymore. You can run «tar —version» in Terminal to see if the it is bsdtar or gnutar.
One working solution for me is to reinstall MacPorts: Follow the official guide to uninstall MacPorts, and install again using the installer. Hope it helps!

answered Oct 29, 2013 at 6:40

snakeninnysnakeninny

2134 silver badges8 bronze badges

There is nothing wrong with your code. This is because dpkg won’t build a package that has a identifier that isn’t alphanumeric(ABC…123…) so it is rejecting the «++» in your package id. I suggest make a new tweak in the NIC and copy your «Tweak.xm» to the new tweak folder and give it an id something like com.ethanarbuckle.alienblueplusplus instead of com.ethanarbuckle.alienblue++. I had the same error and it took me about a month to figure it out. This change worked for me. Don’t forget when you make a new tweak in the NIC to re add any framewoks you had imported. Your package name can still have the «++» in it, just not in the package id.

Don’t use tar just run «make» or «make package»

answered Nov 7, 2013 at 1:35

DMPDMP

9631 gold badge7 silver badges13 bronze badges

Источник

Forum
The Ubuntu Forum Community
Ubuntu Specialised Support
Ubuntu Servers, Cloud and Juju
Server Platforms
[ubuntu] Error on apt-get upgrade

Error on apt-get upgrade

Hi,
apt-get upgrade on Ubuntu server 10.04 stopped working today.
update logs in english ;

Code:

administrateur@digihost:~$ sudo su - -c 'LANG=C apt-get upgrade'
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
  apache2 apache2-mpm-prefork apache2-utils apache2.2-bin apache2.2-common firefox-locale-en
  firefox-locale-fr libpng12-0 libvorbis0a libvorbisenc2 libvorbisfile3 python-lazr.restfulclient
  update-manager-core update-manager-kde
14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/4705kB of archives.
After this operation, 4096B of additional disk space will be used.
Do you want to continue [Y/n]? 
tar: ./md5sums: Cannot open: Invalid argument
tar: ./postinst: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/apache2_2.2.14-5ubuntu8.8_amd64.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
tar: ./md5sums: Cannot open: Invalid argument
tar: ./postinst: Cannot open: Invalid argument
tar: ./preinst: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: ./prerm: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/apache2-mpm-prefork_2.2.14-5ubuntu8.8_amd64.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
tar: ./conffiles: Cannot open: Invalid argument
tar: ./postrm: Cannot open: Invalid argument
tar: ./md5sums: Cannot open: Invalid argument
tar: ./postinst: Cannot open: Invalid argument
tar: ./preinst: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/apache2.2-common_2.2.14-5ubuntu8.8_amd64.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
tar: ./md5sums: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/apache2.2-bin_2.2.14-5ubuntu8.8_amd64.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
No apport report written because MaxReports is reached already
                                                              tar: ./md5sums: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/apache2-utils_2.2.14-5ubuntu8.8_amd64.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
No apport report written because MaxReports is reached already
                                                              tar: ./md5sums: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/firefox-locale-en_10.0.2+build1-0ubuntu0.10.04.1_all.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
No apport report written because MaxReports is reached already
                                                              tar: ./md5sums: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/firefox-locale-fr_10.0.2+build1-0ubuntu0.10.04.1_all.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
No apport report written because MaxReports is reached already
                                                              tar: ./shlibs: Cannot open: Invalid argument
tar: ./postinst: Cannot open: Invalid argument
tar: ./postrm: Cannot open: Invalid argument
tar: ./md5sums: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/libpng12-0_1.2.42-1ubuntu2.3_amd64.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
No apport report written because MaxReports is reached already
                                                              tar: ./postrm: Cannot open: Invalid argument
tar: ./md5sums: Cannot open: Invalid argument
tar: ./shlibs: Cannot open: Invalid argument
tar: ./postinst: Cannot open: Invalid argument
tar: ./symbols: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/libvorbis0a_1.2.3-3ubuntu1.1_amd64.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
No apport report written because MaxReports is reached already
                                                              tar: ./postrm: Cannot open: Invalid argument
tar: ./md5sums: Cannot open: Invalid argument
tar: ./shlibs: Cannot open: Invalid argument
tar: ./postinst: Cannot open: Invalid argument
tar: ./symbols: Cannot open: Invalid argument
tar: ./control: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors

Sorry my logs are in french.

Code:

administrateur@digihost:~$ sudo apt-get upgrade 
Lecture des listes de paquets... Fait
Construction de l'arbre des d�pendances       
Lecture des informations d'�tat... Fait
Les paquets suivants seront mis � jour*:
  apache2 apache2-mpm-prefork apache2-utils apache2.2-bin apache2.2-common libpng12-0 update-manager-core update-manager-kde
8 mis � jour, 0 nouvellement install�s, 0 � enlever et 0 non mis � jour.
Il est n�cessaire de prendre 0o/3'644ko dans les archives.
Apr�s cette op�ration, 4'096o d'espace disque suppl�mentaires seront utilis�s.
Souhaitez-vous continuer [O/n]*? 
tar: ./md5sums : la fonction open a �chou�: Argument invalide
tar: ./postinst : la fonction open a �chou�: Argument invalide
tar: ./control : la fonction open a �chou�: Argument invalide
tar: Arr�t avec code d'�chec � cause des erreurs pr�c�dentes
dpkg-deb: le sous-processus tar a retourn� une erreur de sortie d'�tat 2
dpkg*: erreur de traitement de /var/cache/apt/archives/apache2_2.2.14-5ubuntu8.8_amd64.deb (--unpack)*:
 le sous-processus dpkg-deb --control a retourn� une erreur de sortie d'�tat 2
tar: ./md5sums : la fonction open a �chou�: Argument invalide
tar: ./postinst : la fonction open a �chou�: Argument invalide
tar: ./preinst : la fonction open a �chou�: Argument invalide
tar: ./control : la fonction open a �chou�: Argument invalide
tar: ./prerm : la fonction open a �chou�: Argument invalide
tar: Arr�t avec code d'�chec � cause des erreurs pr�c�dentes
dpkg-deb: le sous-processus tar a retourn� une erreur de sortie d'�tat 2
dpkg*: erreur de traitement de /var/cache/apt/archives/apache2-mpm-prefork_2.2.14-5ubuntu8.8_amd64.deb (--unpack)*:
 le sous-processus dpkg-deb --control a retourn� une erreur de sortie d'�tat 2
tar: ./conffiles : la fonction open a �chou�: Argument invalide
tar: ./postrm : la fonction open a �chou�: Argument invalide
tar: ./md5sums : la fonction open a �chou�: Argument invalide
tar: ./postinst : la fonction open a �chou�: Argument invalide
tar: ./preinst : la fonction open a �chou�: Argument invalide
tar: ./control : la fonction open a �chou�: Argument invalide
tar: Arr�t avec code d'�chec � cause des erreurs pr�c�dentes
dpkg-deb: le sous-processus tar a retourn� une erreur de sortie d'�tat 2
dpkg*: erreur de traitement de /var/cache/apt/archives/apache2.2-common_2.2.14-5ubuntu8.8_amd64.deb (--unpack)*:
 le sous-processus dpkg-deb --control a retourn� une erreur de sortie d'�tat 2
tar: ./md5sums : la fonction open a �chou�: Argument invalide
tar: ./control : la fonction open a �chou�: Argument invalide
tar: Arr�t avec code d'�chec � cause des erreurs pr�c�dentes
dpkg-deb: le sous-processus tar a retourn� une erreur de sortie d'�tat 2
dpkg*: erreur de traitement de /var/cache/apt/archives/apache2.2-bin_2.2.14-5ubuntu8.8_amd64.deb (--unpack)*:
 le sous-processus dpkg-deb --control a retourn� une erreur de sortie d'�tat 2
Aucun rapport �*apport*� �crit car MaxReports a d�j� �t� atteint
                                                                tar: ./md5sums : la fonction open a �chou�: Argument invalide
tar: ./control : la fonction open a �chou�: Argument invalide
tar: Arr�t avec code d'�chec � cause des erreurs pr�c�dentes
dpkg-deb: le sous-processus tar a retourn� une erreur de sortie d'�tat 2
dpkg*: erreur de traitement de /var/cache/apt/archives/apache2-utils_2.2.14-5ubuntu8.8_amd64.deb (--unpack)*:
 le sous-processus dpkg-deb --control a retourn� une erreur de sortie d'�tat 2
Aucun rapport �*apport*� �crit car MaxReports a d�j� �t� atteint
                                                                tar: ./shlibs : la fonction open a �chou�: Argument invalide
tar: ./postinst : la fonction open a �chou�: Argument invalide
tar: ./postrm : la fonction open a �chou�: Argument invalide
tar: ./md5sums : la fonction open a �chou�: Argument invalide
tar: ./control : la fonction open a �chou�: Argument invalide
tar: Arr�t avec code d'�chec � cause des erreurs pr�c�dentes
dpkg-deb: le sous-processus tar a retourn� une erreur de sortie d'�tat 2
dpkg*: erreur de traitement de /var/cache/apt/archives/libpng12-0_1.2.42-1ubuntu2.3_amd64.deb (--unpack)*:
 le sous-processus dpkg-deb --control a retourn� une erreur de sortie d'�tat 2
Aucun rapport �*apport*� �crit car MaxReports a d�j� �t� atteint
                                                                tar: ./postinst : la fonction open a �chou�: Argument invalide
tar: ./preinst : la fonction open a �chou�: Argument invalide
tar: ./prerm : la fonction open a �chou�: Argument invalide
tar: ./conffiles : la fonction open a �chou�: Argument invalide
tar: ./md5sums : la fonction open a �chou�: Argument invalide
tar: ./control : la fonction open a �chou�: Argument invalide
tar: Arr�t avec code d'�chec � cause des erreurs pr�c�dentes
dpkg-deb: le sous-processus tar a retourn� une erreur de sortie d'�tat 2
dpkg*: erreur de traitement de /var/cache/apt/archives/update-manager-core_1%3a0.134.11.2_amd64.deb (--unpack)*:
 le sous-processus dpkg-deb --control a retourn� une erreur de sortie d'�tat 2
Aucun rapport �*apport*� �crit car MaxReports a d�j� �t� atteint
                                                                tar: ./postinst : la fonction open a �chou�: Argument invalide
tar: ./preinst : la fonction open a �chou�: Argument invalide
tar: ./prerm : la fonction open a �chou�: Argument invalide
tar: ./md5sums : la fonction open a �chou�: Argument invalide
tar: ./control : la fonction open a �chou�: Argument invalide
tar: Arr�t avec code d'�chec � cause des erreurs pr�c�dentes
dpkg-deb: le sous-processus tar a retourn� une erreur de sortie d'�tat 2
dpkg*: erreur de traitement de /var/cache/apt/archives/update-manager-kde_1%3a0.134.11.2_all.deb (--unpack)*:
 le sous-processus dpkg-deb --control a retourn� une erreur de sortie d'�tat 2
Aucun rapport �*apport*� �crit car MaxReports a d�j� �t� atteint
                                                                dpkg: impossible d'ouvrir �*/var/lib/dpkg/status*� pour �crire les informations de status: Argument invalide
E: Sub-process /usr/bin/dpkg returned an error code (2)

Any idea?
Thanks

Last edited by Hyli; February 23rd, 2012 at 10:09 AM.

Reason: Logs in English

Re: Error on apt-get upgrade

Hi I googled the error message: /usr/bin/dpkg returned an error code (2)

and it appears to be the same issue as this:

http://askubuntu.com/questions/98157…eration-failed

Hope this helps.

Please bear in mind I am no expert on anything Linux.
I won’t be offended if you wait for a response from somebody more experienced : D
Re: Error on apt-get upgrade

Sorry but it doesnt looks like it the same issue.
Re: Error on apt-get upgrade

Sorry, my French is very poor, but it looks as though the md5sum of at least one apache package that apt has downloaded may be corrupt.

I suggest you run

to clear the cache of downloaded packages, or if bandwidth is important, just delete the .deb files of the apache packages that seem to be the faulty ones from /var/cache/apt/archives, then try updating and upgrading again. Even if I am wrong it will not be a major problem for the system as the newly downloaded corrupt packages will simply report the same errors, leaving you exactly where you are now.
Re: Error on apt-get upgrade

No i already tried to clean.
It looks like tar or another installed program needed in the upgrade process is corrupted
Re: Error on apt-get upgrade

I replaced tar and dpkg-deb executables with ones from another server but error is still here. Any idea?

Last edited by Hyli; February 20th, 2012 at 10:25 AM.

Re: Error on apt-get upgrade

In the cron daily there is another error (for the same reason i think)

Code:

/etc/cron.daily/apt:
Traceback (most recent call last):
 File "/usr/bin/unattended-upgrade", line 519, in <module>
   main()
 File "/usr/bin/unattended-upgrade", line 446, in main
   fd = os.open(logfile_dpkg, os.O_RDWR|os.O_CREAT, 0644)
OSError: [Errno 22] Invalid argument: '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2012-02-21_06:31:53.510019.log'
/etc/cron.daily/aptitude:
cp: cannot create regular file `aptitude.pkgstates': Invalid argument
touch: setting times of `aptitude.pkgstates': No such file or directory
savelog: could not touch aptitude.pkgstates
run-parts: /etc/cron.daily/aptitude exited with return code 4
/etc/cron.daily/dpkg:
cp: cannot create regular file `dpkg.status': Invalid argument
touch: setting times of `dpkg.status': No such file or directory
savelog: could not touch dpkg.status
run-parts: /etc/cron.daily/dpkg exited with return code 4
/etc/cron.daily/logrotate:
error: error creating output file /var/log/syslog.1.gz: Invalid argument
run-parts: /etc/cron.daily/logrotate exited with return code 1
/etc/cron.daily/man-db:
fopen: Invalid argument
run-parts: /etc/cron.daily/man-db exited with return code 2
/etc/cron.daily/standard:
cp: cannot create regular file `dpkg.status': Invalid argument
touch: setting times of `dpkg.status': No such file or directory
savelog: could not touch dpkg.status

Re: Error on apt-get upgrade

I added logs in english on the 1st post

Bookmarks

Posting Permissions

Источник

Some backstory:

In trying to compile a linux package for iOS 8, I accidentally removed bash and sh. Yes, you read that right… don’t judge me.

However, when I opened Cydia to update my packages, I ran into this problem upon trying to install anything:

subprocess dpkg-deb —control returned error exit status 2

Sub-process /usr/libexec/cydia/cydo returned an error code (1)

HOWEVER, I decided to try running dpkg (which is what Cydia attempts to run when making modifications to packages) in a shell, to see if I would get a more verbose error. I did indeed.

«tar», which is run by dpkg, reported this problem:

tar: unrecognized option `—warning=no-timestamp’

It turns out, this is the only problem. It doesn’t require a restore at all. So, here is how to fix this yourself, and enable packages to be installed and otherwise modified in Cydia once again:

Get a copy of tar 1.29 built for iOS. You can fetch this from the /usr/bin/ directory of a fully functional jailbroken device on iOS 8+. If you don’t have access to such a device, I’ve uploaded the binary I used to dropbox at this location.
Once you have tar, copy it to /usr/bin, and /bin. If you used the copy I fetched, you might need to run chmod +x before it will work.
Reboot your device. For whatever reason, respringing wasn’t enough for me.
Profit! tar, dpkg, and cydia should now behave as expected.

Источник

Linux Mint Forums

[SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13

[SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13

Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)

Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)

Debian User Forums

Dpkg error can’t solve

Dpkg error can’t solve

[Tutorial] How to fix «subprocess dpkg-deb —control returned error exit status 2» after «re-jailbreaking» iOS 8 (possibly other versions too)