Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
root@articaproxy:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
blablablabla....blablabla...
The following packages will be upgraded:
php-pear
1 upgraded, 0 newly installed, 0 to remove and 532 not upgraded.
125 not fully installed or removed.
Need to get 284 kB of archives.
After this operation, 127 kB disk space will be freed.
Do you want to continue [Y/n]? y
Get:1 http://packages.dotdeb.org/ jessie/all php-pear all 1:1.10.1+submodules+notgz-8.1 [284 kB]
Fetched 284 kB in 8s (34.9 kB/s)
Reading changelogs... Done
(Reading database ... 56583 files and directories currently installed.)
Preparing to replace php-pear 5.4.45-0+deb7u6 (using .../php-pear_1%3a1.10.1+submodules+notgz-8.1_all.deb) ...
dpkg-maintscript-helper: error: command symlink_to_dir is unknown
Hint: upgrading dpkg to a newer version might help.
Usage: dpkg-maintscript-helper <command> <parameter>... -- <maintainer-script-parameter>...
Commands:
supports <command>
Returns 0 (success) if the given command is supported, 1 otherwise.
rm_conffile <conffile> [<last-version> [<package>]]
Remove obsolete conffile. Must be called in preinst, postinst and
postrm.
mv_conffile <old-conf> <new-conf> [<last-version> [<package>]]
Rename a conffile. Must be called in preinst, postinst and postrm.
help
Display this usage information.
dpkg: error processing /var/cache/apt/archives/php-pear_1%3a1.10.1+submodules+notgz-8.1_all.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
dpkg-maintscript-helper: error: command symlink_to_dir is unknown
Hint: upgrading dpkg to a newer version might help.
Usage: dpkg-maintscript-helper <command> <parameter>... -- <maintainer-script-parameter>...
Commands:
supports <command>
Returns 0 (success) if the given command is supported, 1 otherwise.
rm_conffile <conffile> [<last-version> [<package>]]
Remove obsolete conffile. Must be called in preinst, postinst and
postrm.
mv_conffile <old-conf> <new-conf> [<last-version> [<package>]]
Rename a conffile. Must be called in preinst, postinst and postrm.
help
Display this usage information.
dpkg: error while cleaning up:
subprocess new post-removal script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/php-pear_1%3a1.10.1+submodules+notgz-8.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Anyone have any ideas?
Last edited by winda on 2017-03-14 12:03, edited 1 time in total.
Well, that looks pretty messy.- and dotdeb is not a debian repo, you should have removed it and made sure you were 'vanilla' and uo to date on wheezy prior to attempting a dist- upgrade.
deb http://httpredir.debian.org/debian jessie main contrib non-free
deb http://httpredir.debian.org/debian jessie-updates main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
Removing some packages that are from other repositories may be necessary as already suggested. One tricky thing would be finding out what repository each package is from. A short script or aptitude query could work. If you're interested, I have a short script to print out packages with their repositories here: https://gist.github.com/horgh/6a431dea4 ... fb92520eda
But possibly you could get away with not mass removing unofficial packages.
root@articaproxy:~# apt-get autoclean
Reading package lists... Done
Building dependency tree
Reading state information... Done
root@articaproxy:~# apt-get clean all
root@articaproxy:~# apt-get update
Hit http://debian.mirror.uber.com.au jessie Release.gpg
Hit http://debian.mirror.uber.com.au jessie-updates Release.gpg
Hit http://security.debian.org jessie/updates Release.gpg
Hit http://security.debian.org jessie/updates Release
Hit http://security.debian.org jessie/updates/main Sources
Hit http://debian.mirror.uber.com.au jessie Release
Hit http://debian.mirror.uber.com.au jessie-updates Release
Hit http://security.debian.org jessie/updates/contrib Sources
Hit http://debian.mirror.uber.com.au jessie/main Sources
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://debian.mirror.uber.com.au jessie/main amd64 Packages
Hit http://debian.mirror.uber.com.au jessie/main Translation-en
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://security.debian.org jessie/updates/contrib Translation-en
Hit http://security.debian.org jessie/updates/main Translation-en
Hit http://debian.mirror.uber.com.au jessie-updates/main Sources
Hit http://debian.mirror.uber.com.au jessie-updates/contrib Sources
Get:1 http://debian.mirror.uber.com.au jessie-updates/main amd64 Packages/DiffIndex [6,916 B]
Hit http://debian.mirror.uber.com.au jessie-updates/contrib amd64 Packages
Hit http://debian.mirror.uber.com.au jessie-updates/contrib Translation-en
Get:2 http://debian.mirror.uber.com.au jessie-updates/main Translation-en/DiffIndex [2,704 B]
Fetched 9,620 B in 4s (2,001 B/s)
Reading package lists... Done
root@articaproxy:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
E: Unmet dependencies. Try using -f.
root@articaproxy:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
Likely what will resolve this is removing whatever packages are causing issues. The trick will be finding which ones need removal. It's unfortunate apt-get is not showing any package names!
There is probably a way to show more about what is doesn't like, but I'm sure how...
The dotdeb repository has newer packages than Wheezy for LAMP-type stuff and will often interfere with dist-upgrades like this. The only way to make sure the upgrade goes smoothly is to remove any dotdeb packages and do the dist-upgrade. You can reinstall the packages after the upgrade either from the Jessie repo, or restore dotdeb if you want/need the shiny new shi..stuff.
stevepusser wrote:The dotdeb repository has newer packages than Wheezy for LAMP-type stuff and will often interfere with dist-upgrades like this. The only way to make sure the upgrade goes smoothly is to remove any dotdeb packages and do the dist-upgrade. You can reinstall the packages after the upgrade either from the Jessie repo, or restore dotdeb if you want/need the shiny new shi..stuff.
Thanks, Solved
I search the held package and remove the package