New postgresql 12 package pre installation script subprocess returned error exit status 127

script returned error exit status 127 или dpkg returned an error code (1)

Возился я как-то с установкой php5-rrd и так довозился, что после этого у меня не устанавливалась ни одна софтина, и даже при попытке исправить зависимости, я получил ошибку:

Оказывается, такие ошибки возникают у многих, и решаются они тоже весьма интересно (обратите внимание на файл, который я выделил в ошибке).

Так вот, открываем этот файл /var/lib/dpkg/info/php5-rrd.postrm и удаляем там все, а затем вписываем в него следующее:

сохраняем и закрываем файл, собственно это и есть решение проблемы 🙂 после чего в консоле например запускаем исправление зависимостей:

Вот и все, всем удачки!

Обычно ошибка выглядит так:

Удалите кеш пакетов:

Удалите осиротевшие пакеты:

Обновите список пакетов:

Обычно этого достаточно.

Если вы запутались с зависимостями, поможет интеллектуальное обновление системы:

Если установка была прервана, то следует переустановить пакет

Если репозиторий недоступен, исправить:

Если невозможно удалить/переустановить пакет, исправить:

Добавление нового репозитория

Пример добавления репозитория:

echo ‘deb http://cz.archive.ubuntu.com/ubuntu xenial main universe’ >> /etc/apt/sources.list.d/ubuntu-xenial-main-universe.list
apt-update

Если появится ошибка невалидности ключей:

Значит, нужно добавить указанные в сообщении ключи в доверенные:

Источник

Thread: installation script returned error exit status 127

Thread Tools

Display

installation script returned error exit status 127

E: linux-image-2.6.32-25-generic-pae: subprocess installed post-installation script returned error exit status 127
E: linux-image-generic-pae: dependency problems — leaving unconfigured
E: linux-generic-pae: dependency problems — leaving unconfigured

Every time I try to use Synaptic or do an update I am getting this message.
Any suggestions to fix this problem.
Thanks

Re: installation script returned error exit status 127

E: linux-image-2.6.32-25-generic-pae: subprocess installed post-installation script returned error exit status 127
E: linux-image-generic-pae: dependency problems — leaving unconfigured
E: linux-generic-pae: dependency problems — leaving unconfigured

Every time I try to use Synaptic or do an update I am getting this message.
Any suggestions to fix this problem.
Thanks

the -f will tell aptitude to try and fix and the -s says to simulate. It won’t do anything except tell you what would happen without the -s switch.

Re: installation script returned error exit status 127

As you can see from below, I am still getting the error message.
I have replaced the etc/apt/sources.list as per the link.

$ sudo apt-get install -f
[sudo] password for phil:
Reading package lists. Done
Building dependency tree
Reading state information. Done
0 upgraded, 0 newly installed, 0 to remove and 39 not upgraded.
3 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up linux-image-2.6.32-25-generic-pae (2.6.32-25.45) .
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.32-25-generic-pae
Running postinst hook script /usr/sbin/update-grub.
/etc/default/grub: 32: title: not found
User postinst hook script [/usr/sbin/update-grub] exited with value 127
dpkg: error processing linux-image-2.6.32-25-generic-pae (—configure):
subprocess installed post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration of linux-image-generic-pae:
linux-image-generic-pae depends on linux-image-2.6.32-25-generic-pae; however:
Package linux-image-2.6.32-25-generic-pae is not configured yet.
dpkg: error processing linux-image-generic-pae (—configure):
dependency problems — leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-pae:
linux-generic-pae depends on linux-image-generic-pae (= 2.6.32.25.27); however:
Package linux-image-generic-pae is not configured yet.
dpkg: error processing linux-generic-pae (—configure):
dependency problems — leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
linux-image-2.6.32-25-generic-pae
linux-image-generic-pae
linux-generic-pae
E: Sub-process /usr/bin/dpkg returned an error code (1)

Re: installation script returned error exit status 127

You’ve got something wrong with grub! I’m only vaguely familiar with legacy grub; it never breaks. Do you know what version of grub you’ve got?

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

SOLVED: update manager and software manager not working

SOLVED: update manager and software manager not working

Post by kjvonly » Fri Sep 14, 2012 1:17 am

Last week I installed Linux Mint 13 Maya on my new HDD. My old windows 7 HDD died and since I was sick of Windows I decided to go to linux. Well, long story short yesterday and today software manager will not install software, and now update manager won’t even update. Here’s the error for update manager, as far as software manager is concerned you hit «install» and the install button disappears it appears to install, but low and behold, it doesn’t. what is going on? I’m hoping i didn’t make the wrong choice transitioning to linux

E: install-info: subprocess installed post-installation script returned error exit status 127

Setting up install-info (4.13a.dfsg.1-8ubuntu2) .
/var/lib/dpkg/info/install-info.postinst: 32: /var/lib/dpkg/info/install-info.postinst: update-info-dir: not found
dpkg: error processing install-info (—configure):
subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
install-info
W: Waited for dpkg —assert-multi-arch but it wasn’t there — dpkgGo (10: No child processes)
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up install-info (4.13a.dfsg.1-8ubuntu2) .
/var/lib/dpkg/info/install-info.postinst: 32: /var/lib/dpkg/info/install-info.postinst: update-info-dir: not found
dpkg: error processing install-info (—configure):
subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
install-info

Re: update manager and software manager not working

Post by caf4926 » Fri Sep 14, 2012 2:17 am

Re: update manager and software manager not working

Post by kjvonly » Fri Sep 14, 2012 8:07 pm

Sorry, I’m a total newbie. Last time i used linux was in high school. red hat back in the 90’s

When I type that in this is what I get:

$ sudo apt-get —fix-broken
[sudo] password for chris:
apt 0.8.16

exp12ubuntu10.2 for amd64 compiled on Jun 15 2012 15:08:48
Usage: apt-get [options] command
apt-get [options] install|remove pkg1 [pkg2 . ]
apt-get [options] source pkg1 [pkg2 . ]

apt-get is a simple command line interface for downloading and
installing packages. The most frequently used commands are update
and install.

Commands:
update — Retrieve new lists of packages
upgrade — Perform an upgrade
install — Install new packages (pkg is libc6 not libc6.deb)
remove — Remove packages
autoremove — Remove automatically all unused packages
purge — Remove packages and config files
source — Download source archives
build-dep — Configure build-dependencies for source packages
dist-upgrade — Distribution upgrade, see apt-get(8)
dselect-upgrade — Follow dselect selections
clean — Erase downloaded archive files
autoclean — Erase old downloaded archive files
check — Verify that there are no broken dependencies
changelog — Download and display the changelog for the given package
download — Download the binary package into the current directory

Options:
-h This help text.
-q Loggable output — no progress indicator
-qq No output except for errors
-d Download only — do NOT install or unpack archives
-s No-act. Perform ordering simulation
-y Assume Yes to all queries and do not prompt
-f Attempt to correct a system with broken dependencies in place
-m Attempt to continue if archives are unlocatable
-u Show a list of upgraded packages as well
-b Build the source package after fetching it
-V Show verbose version numbers
-c=? Read this configuration file
-o=? Set an arbitrary configuration option, eg -o dir::cache=/tmp
See the apt-get(8), sources.list(5) and apt.conf(5) manual
pages for more information and options.
This APT has Super Cow Powers.

So I guess I need to know what else I need to type in for options and switches

Источник

Thread: post-removal script returned error exit status 127

Thread Tools

Display

SOLVED metacity-common post-removal script returned error exit status 127

Eish, it’s a hot day and nothing seems to be going right. Trying to figure a way out of this one — error 127. Looks like it could be Metacity problem? There a couple of pythons that also have a problem.

Not sure if I should remove entry for each single one in the database or not? This is the second time I’ve seen this happen, on a different machine, and one would think there is an automatic solution or utility to do this in Synaptic. Advice please.

Last edited by afrodeity; March 14th, 2010 at 03:40 PM .

Re: post-removal script returned error exit status 127

This could be the problem item?

Re: post-removal script returned error exit status 127

Last edited by afrodeity; March 10th, 2010 at 04:05 PM .

Re: post-removal script returned error exit status 127

Seems like the system is missing update-python-modules

Re: post-removal script returned error exit status 127

Re: post-removal script returned error exit status 127

I think this is my problem: update-gconf-defaults, should have spotted this right at the top, but stupidly went and googled the error code.

If I enter update-gconf-defaults in terminal I get this message:

There are a number of posts on error 127 which suggest recreating the file.

In this case, all I need to do is make a symbolic link between /usr/bin/pyhon2.6 and /usr/bin/python since the problem is with interpretation which python setup to use, I have both 2.5 AND 2.6 installed.

To make a symbolic link between /usr/bin/pyhon2.6 and /usr/bin/python

Last edited by afrodeity; March 14th, 2010 at 03:46 PM .

Источник

5.6.4-1 post-installation script error

Hey guys, I’m running in to an error when updating to 5.6.4-1, and I could use some guidance.

The update itself seems to have applied correctly, as the webgui reports that I’m on 5.6.4-1, but the post-install script is failing on the processing system modifications step.

I poked around a bit in the script and it looks like that step involves checking the versions of things and flagging possible issues? But I don’t know enough about omv under the hood to be sure.

Any help or just a point in the right direction would be appreciated!

Sorry, no solutions but lending credence to the issue. I’m on same boat.

Not the same boat, but you’re on the same lake

right — not sure why you’re running apt-get install -f. Can you try again with omv-upgrade and see if the same error occurs again?

TXJD64 — try apt install openmediavault. If it fails, apt install openmediavault-sftp. If that succeeds, try the first apt command again. What happens?

TXJD64 — try apt install openmediavault. If it fails, apt install openmediavault-sftp. If that succeeds, try the first apt command again. What happens?

Thanks, I’ve already tried both. Removing openmediavault-sftp then leaves openmediavault to exit with a (1) just the same. Doing an install (reinstall) of openmediavault fails with the same error. It seems to be happening at the SALT command when it tries to configure *something* but I’m not able to ascertain what. I’m removed openmediavault-sftp to better isolate the problem. what log can I check to see what exactly is failing in the post installation configuration?

Re-running omv-upgrade gives:

Edited once, last by TXJD64 ( Apr 13th 2021 ).

Afraid that’s above my pay grade. You’re on the right track, but I wouldn’t know where to check for logs either. hope someone more knowledgeable can chime in soon.

right — not sure why you’re running apt-get install -f. Can you try again with omv-upgrade and see if the same error occurs again?

omv-upgrade looks like it’s just running apt-get update and then stopping without doing anything else, not even getting to the post-install script part.

Looking in /var/lib/dpkg/info/openmediavault.postinst as far as I can tell the «processing system modifications» step is checking what version you’re coming from, then running different commands depending on which version it was, but i can’t see how that would be erroring out, so i’m kinda at a loss.

So are you saying that omv-upgrade does not produce any error message at all?

It produces the exact same output as apt-get update and nothing more.

Those target source errors don’t seem relevant, but who knows

There seem to be a number of repositories that I’m not sure should even belong there. they concern me.

Ign:12 http://ftp.nl.debian.org/debian stretch InRelease

Ign:13 https://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.6 InRelease

Get:17 https://dl.ubnt.com/unifi/debian unifi-5.13 InRelease [3010 B]

E: Repository ‘https://dl.ubnt.com/unifi/debian unifi-5.13 InRelease’ changed its ‘Suite’ value from ‘testing’ to »

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Did you add these? Debian Stretch is version 9, and OMV 5 runs on Buster (version 10).

I can’t even begin to imagine what Ubuntu Xenial (that’s 16.04!) and Debian Unifi are doing in there.

I also have a unifi controller running on this machine, those were probably added by it. But I’m not sure how that is relevant to the post-install script erroring out.

Good point. But I’ve seen some strange things in the past. it honestly wouldn’t surprise me if this was part of the problem.

Sorry I can’t be of more help.

An update: after some further testing I got the script to complete successfully by commenting out these 2 sections in /var/lib/dpkg/info/openmediavault.postinst :

I then ran omv-salt deploy run —no-color —quiet apt cronapt separately, and after a reboot everything seems normal. I’m not 100% sure what omv_module_set_dirty nginx is or how to apply it, but things seem to be working ok so far.

Thanks. that’s worked for me as well, though I share your concern about that omv_module_set_dirty nginx line.

Thanks a lot for your investigation. About omv_module_set_dirty nginx line, you have more information on dirty modules from documentation.

openmediavault does not display the submodules that are affected by the configuration changes. If you still want to know which submodules are affected, simply run cat /var/lib/openmediavault/dirtymodules.json in the CLI.

You just need to add ‘nginx’ module in ‘/var/lib/openmediavault/dirtymodules.json’ file. That’s what does this line in the post script.

So I guess it’s not necessary to comment this section in /var/lib/dpkg/info/openmediavault.postinst.

You never need to add anything to the dirtymodules file. If you want nginx config updates, just run sudo omv-salt deploy run nginx

omv 6.0.46-2 Shaitan | 64 bit | 5.19 proxmox kernel | plugins :: omvextrasorg 6.1.1 | kvm 6.1.23 | mergerfs 6.3.3 | zfs 6.0.11
omv-extras.org plugins source code and issue tracker — github

Please try ctrl-shift-R and read this before posting a question.
Please don’t PM for support. Too many PMs!

right Apr 16th 2021

hi,
i have the same problem,

Paramétrage de openmediavault (5.6.5-1) .

Creating configuration database .

Migrating configuration database .

Setting up Salt environment .

Processing system modifications .

dpkg: erreur de traitement du paquet openmediavault (—configure) :

installed openmediavault package post-installation script subprocess returned error exit status 1

Des erreurs ont été rencontrées pendant l’exécution :

E: Sub-process /usr/bin/dpkg returned an error code (1)

when i run this command sudo omv-salt deploy run nginx

Comment: States ran successfully. Updating debian.

Duration: 2019.287 ms

Duration: 219.673 ms

Duration: 2.33 ms

Name: update-ca-certificates —fresh

Comment: Command «update-ca-certificates —fresh» run

Duration: 1418.091 ms

Clearing symlinks in /etc/ssl/certs.

Updating certificates in /etc/ssl/certs.

126 added, 0 removed; done.

Running hooks in /etc/ca-certificates/update.d.

Duration: 2.885 ms

Summary for debian

Succeeded: 4 (changed=4)

Total states run: 4

Total run time: 1.643 s

Comment: File /etc/nginx/sites-available/openmediavault-webgui is in the correct state

Duration: 230.325 ms

Comment: File /etc/nginx/openmediavault-webgui.d/security.conf updated

Duration: 68.54 ms

add_header X-XSS-Protection «1; mode=block»;

+add_header Permissions-Policy «microphone=(), camera=(), geolocation=(), payment=()» always;

Name: nginx_ensite openmediavault-webgui

Comment: Command «nginx_ensite openmediavault-webgui» run

Duration: 44.713 ms

Site configuration file ‘openmediavault-webgui’ is already enabled.

Comment: Run failed on minions: debian

Duration: 358.911 ms

Data failed to compile:

Rendering SLS ‘base:omv.deploy.monit.default’ failed: Jinja error: tls: Invalid value ‘0’, allowed values are ‘none, ssl, starttls, auto’.

Traceback (most recent call last):

File «/usr/lib/python3/dist-packages/salt/utils/templates.py», line 497, in render_jinja_tmpl

File «/usr/lib/python3/dist-packages/jinja2/asyncsupport.py», line 76, in render

return original_render(self, *args, **kwargs)

File «/usr/lib/python3/dist-packages/jinja2/environment.py», line 1008, in render

return self.environment.handle_exception(exc_info, True)

File «/usr/lib/python3/dist-packages/jinja2/environment.py», line 780, in handle_exception

reraise(exc_type, exc_value, tb)

File «/usr/lib/python3/dist-packages/jinja2/_compat.py», line 37, in reraise

File » «, line 37, in top-level template code

File «/usr/lib/python3/dist-packages/jinja2/sandbox.py», line 438, in call

return __context.call(__obj, *args, **kwargs)

File «/usr/lib/python3/dist-packages/salt/loader.py», line 1235, in __call__

return self.loader.run(run_func, *args, **kwargs)

File «/usr/lib/python3/dist-packages/salt/loader.py», line 2268, in run

return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)

File «/usr/lib/python3/dist-packages/salt/loader.py», line 2283, in _run_as

return _func_or_method(*args, **kwargs)

File «/var/cache/salt/minion/extmods/modules/omv_conf.py», line 39, in get

objs = db.get(id_, identifier)

File «/usr/lib/python3/dist-packages/openmediavault/config/database.py», line 85, in get

File «/usr/lib/python3/dist-packages/openmediavault/config/database.py», line 726, in execute

File «/usr/lib/python3/dist-packages/openmediavault/config/database.py», line 487, in _elements_to_object

File «/usr/lib/python3/dist-packages/openmediavault/config/object.py», line 236, in validate

File «/usr/lib/python3/dist-packages/openmediavault/config/datamodel.py», line 202, in validate

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 175, in validate

self._validate_type(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 229, in _validate_type

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 200, in _validate_type

self._validate_object(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 305, in _validate_object

self._check_properties(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 519, in _check_properties

self._validate_type(value[propk], propv, path)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 229, in _validate_type

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 209, in _validate_type

self._validate_string(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 284, in _validate_string

self._check_enum(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 475, in _check_enum

% (valuev, «, «.join(map(str, schema[‘enum’]))),

Источник

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх

That output is the output from the env command, not the content of any «normal» /etc/environment file.

These type of errors during package adds and updates usually can be cleared by running this command:

$ dpkg --configure -a

And, although the similar error I just received when doing upgrades in Ubuntu Mate 18 was not resolved by running the command, it has in fact worked for me until last night in every other case.

Related packages being upgraded during times when LTS versions are fading into the past, along with their software updates that match the deps, and you start getting this stuff happen again, much like when when Ubuntu 14.x.x was reaching EOL.

It is much better now, and dist-upgrade has been working better than ever, BUT here that problem seems to have popped its head up again.

Solved:

https://askubuntu.com/questions/1069702/dpkg-error-processing-package-install-info

My exact package issue was with locales but the rest is exactly the same and the solution needs adjustment to the package you are having issues with.

Sorry about the bad formatting. This is my first post here and with code remarks after 25 years on the internet I don’t really care if that is wrong just sending the right answer without going back to my main terminal to reply to this.

I have tried the solution provided by the link above. It worked instantly on this system I am writing from and remoted into.

The usual dpkg command fails, and will continue to endlessly. Been there, done that.

# dpkg --configure -a
Setting up locales (2.31-0ubuntu9) ...
/var/lib/dpkg/info/locales.postinst: 64: /var/lib/dpkg/info/locales.postinst: locale-gen: not found
dpkg: error processing package locales (--configure):
 installed locales package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
 locales
root@main:~# mv /var/lib/dpkg/info/locales.postinst /var/lib/dpkg/info/locales.postinst.bad
root@main:~# apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB]      
Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB]     
Hit:4 http://archive.canonical.com/ubuntu xenial InRelease                     
Get:5 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB]  
Fetched 317 kB in 1s (427 kB/s)                               
Reading package lists... Done
root@mine-hive-main:~# dpkg --configure -a
Setting up locales (2.31-0ubuntu9) ...

From there all is well, again, with dpkg and apt.

Как удалить / установить пакет, который не установлен полностью?

Setting up google-chrome-stable (33.0.1750.152-1) ...
/var/lib/dpkg/info/google-chrome-stable.postinst: 124: /var/lib/dpkg/info/google-chrome-stable.postinst: update-alternatives: not found
dpkg: error processing google-chrome-stable (--configure):
 subprocess installed post-installation script returned error exit status 127
Setting up bsnes (0.088-7) ...
/var/lib/dpkg/info/bsnes.postinst: 5: /var/lib/dpkg/info/bsnes.postinst: update-alternatives: not found
dpkg: error processing bsnes (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 google-chrome-stable
 bsnes
E: Sub-process /usr/bin/dpkg returned an error code (1)

sudo apt-get clean && sudo apt-get autoremove
sudo apt-get -f install
sudo dpkg --configure -a

Ответы:

subprocess installed post-installation script returned error exit status 127

sudo apt-get install --reinstall dpkg

sudo rm /var/lib/dpkg/info/[package_name].*
sudo dpkg --configure -a
sudo apt-get update

cd /var/lib/dpkg/info

sudo rm *.postinst

sudo apt-get update

sudo apt-get --force-yes install openjdk-7-jre-headless

sudo apt-get install -f --reinstall coreutils init-system-helpers

Возился я как-то с установкой php5-rrd и так довозился, что после этого у меня не устанавливалась ни одна софтина, и даже при попытке исправить зависимости, я получил ошибку:

# apt-get -f install

Reading package lists… Done

Building dependency tree       

Reading state information… Done

The following packages will be REMOVED:

  php5-rrd

0 upgraded, 0 newly installed, 1 to remove and 46 not upgraded.

1 not fully installed or removed.

After this operation, 42.0 kB disk space will be freed.

Do you want to continue [Y/n]? Y

(Reading database … 39480 files and directories currently installed.)

Removing php5-rrd …

/var/lib/dpkg/info/php5-rrd.postrm: 26: php5dismod: not found

dpkg: error processing php5-rrd (—remove):

 subprocess installed post-removal script returned error exit status 127

configured to not write apport reports

                                      Errors were encountered while processing:

 php5-rrd

E: Sub-process /usr/bin/dpkg returned an error code (1)

E: Неудовлетворённые зависимости. Попытайтесь выполнить 'apt-get -f install', не указывая имени пакета, (или найдите другое решение).

sudo apt-get clean

sudo apt-get autoremove

sudo apt-get update

sudo apt-get -f install

sudo apt-get dist-upgrade

sudo apt-get install --reinstall имя_пакета

Добавление нового репозитория

Пример добавления репозитория:

echo ‘deb http://cz.archive.ubuntu.com/ubuntu xenial main universe’ >> /etc/apt/sources.list.d/ubuntu-xenial-main-universe.list
apt-update

Если появится ошибка невалидности ключей:

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
Reading package lists... Done
W: GPG error: http://cz.archive.ubuntu.com/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
E: The repository 'http://cz.archive.ubuntu.com/ubuntu xenial InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Значит, нужно добавить указанные в сообщении ключи в доверенные:

apt-key adv —keyserver keyserver.ubuntu.com —recv-keys 40976EAF437D05B5 3B4FE6ACC0B21F32

теперь следующая команда не выдаст ошибки:

apt-update

Удачки.

30.10.2013 12:57

The package’s .preinst script is failing for some reason.

To find out why, examine the script in /var/lib/dpkg/info/PACKAGENAME.preinst

If you want to see exactly which line the script is failing on, edit the .preinst script and add set -x immediately after the #! line. This turns on execution tracing in the script.

NOTE: This assumes that the .preinst script is a shell script (either posix sh or bash). Almost all .preinst (and .postinst, .prerm, and .postrm) scripts are shell scripts but they don’t have to be, they could be any executable. e.g. on my main desktop machine with 9104 packages installed, 14 are perl scripts, 1 is a compiled executable (bash’s preinst — it can’t assume there is a functioning shell already installed), and all of the rest are shell scripts…9041 are POSIX shell scripts, 63 are bash scripts. If the .preinst is perl or python or something else, you’ll have to figure out how to enable debugging or execution trace mode or similar in that language.

Then run dpkg --configure --pending.

This will cause dpkg to try to configure the half-installed package. DO NOT reinstall it with dpkg -i, that will overwrite your edited .preinst script with the version in the .deb package.

This may give you enough information to fix the problem. It may be something simple like an unexpected or uncaught exit code from a program (most .preinst etc scripts have set -e, to make them terminate on the first error), or assuming that a directory already exists (and this may be due to an undeclared dependency in the package’s debian/control file — i.e it should depend on foo but doesn’t. just install foo anyway)

Once it’s fixed, run dpkg --configure --pending again, and the package should be properly installed.

If the .preinst script is buggy, there’s a reasonable chance that the .postinst (and/or .prerm and .postrm) scripts will be too. You may need to fix them as well.

Don’t forget to submit a bug report to whoever made the package so they can fix it.

I’m trying to install and upgrade R on Linux (Ubuntu 16.04). However, I get a mysterious error and am having trouble diagnosing it. The most similar error that I can find online is here.

The full error is at the bottom of the post. However, it appears the source of the problem is in the following lines.

/var/lib/dpkg/info/r-base-core.postinst: 1: /var/lib/dpkg/info/r-base-core.postinst: paperconf: not found
    dpkg: error processing package r-base-core (--configure):
     subprocess installed post-installation script returned error exit status 127

The entire output is as follows.

user@computer:~$ sudo apt-get install r-base-core
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  r-base-dev r-cran-boot r-cran-class r-cran-cluster r-cran-codetools
  r-cran-foreign r-cran-kernsmooth r-cran-lattice r-cran-mass r-cran-matrix
  r-cran-mgcv r-cran-nlme r-cran-nnet r-cran-rpart r-cran-spatial
  r-cran-survival r-recommended
Suggested packages:
  r-doc-info | r-doc-pdf r-mathlib r-base-html
The following NEW packages will be installed:
  r-base-core r-base-dev r-cran-boot r-cran-class r-cran-cluster
  r-cran-codetools r-cran-foreign r-cran-kernsmooth r-cran-lattice r-cran-mass
  r-cran-matrix r-cran-mgcv r-cran-nlme r-cran-nnet r-cran-rpart
  r-cran-spatial r-cran-survival r-recommended
0 upgraded, 18 newly installed, 0 to remove and 32 not upgraded.
Need to get 0 B/36.0 MB of archives.
After this operation, 55.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Selecting previously unselected package r-base-core.
(Reading database ... 429546 files and directories currently installed.)
Preparing to unpack .../r-base-core_3.2.3-4_amd64.deb ...
Unpacking r-base-core (3.2.3-4) ...
Selecting previously unselected package r-base-dev.
Preparing to unpack .../r-base-dev_3.2.3-4_all.deb ...
Unpacking r-base-dev (3.2.3-4) ...
Selecting previously unselected package r-cran-boot.
Preparing to unpack .../r-cran-boot_1.3-17-1_all.deb ...
Unpacking r-cran-boot (1.3-17-1) ...
Selecting previously unselected package r-cran-mass.
Preparing to unpack .../r-cran-mass_7.3-45-1_amd64.deb ...
Unpacking r-cran-mass (7.3-45-1) ...
Selecting previously unselected package r-cran-class.
Preparing to unpack .../r-cran-class_7.3-14-1_amd64.deb ...
Unpacking r-cran-class (7.3-14-1) ...
Selecting previously unselected package r-cran-cluster.
Preparing to unpack .../r-cran-cluster_2.0.3-1_amd64.deb ...
Unpacking r-cran-cluster (2.0.3-1) ...
Selecting previously unselected package r-cran-codetools.
Preparing to unpack .../r-cran-codetools_0.2-14-1_all.deb ...
Unpacking r-cran-codetools (0.2-14-1) ...
Selecting previously unselected package r-cran-foreign.
Preparing to unpack .../r-cran-foreign_0.8.66-1_amd64.deb ...
Unpacking r-cran-foreign (0.8.66-1) ...
Selecting previously unselected package r-cran-kernsmooth.
Preparing to unpack .../r-cran-kernsmooth_2.23-15-1_amd64.deb ...
Unpacking r-cran-kernsmooth (2.23-15-1) ...
Selecting previously unselected package r-cran-lattice.
Preparing to unpack .../r-cran-lattice_0.20-33-1_amd64.deb ...
Unpacking r-cran-lattice (0.20-33-1) ...
Selecting previously unselected package r-cran-matrix.
Preparing to unpack .../r-cran-matrix_1.2-3-1_amd64.deb ...
Unpacking r-cran-matrix (1.2-3-1) ...
Selecting previously unselected package r-cran-nlme.
Preparing to unpack .../r-cran-nlme_3.1.124-1_amd64.deb ...
Unpacking r-cran-nlme (3.1.124-1) ...
Selecting previously unselected package r-cran-mgcv.
Preparing to unpack .../r-cran-mgcv_1.8-11-1_amd64.deb ...
Unpacking r-cran-mgcv (1.8-11-1) ...
Selecting previously unselected package r-cran-nnet.
Preparing to unpack .../r-cran-nnet_7.3-12-1_amd64.deb ...
Unpacking r-cran-nnet (7.3-12-1) ...
Selecting previously unselected package r-cran-survival.
Preparing to unpack .../r-cran-survival_2.38-3-1_amd64.deb ...
Unpacking r-cran-survival (2.38-3-1) ...
Selecting previously unselected package r-cran-rpart.
Preparing to unpack .../r-cran-rpart_4.1-10-1_amd64.deb ...
Unpacking r-cran-rpart (4.1-10-1) ...
Selecting previously unselected package r-cran-spatial.
Preparing to unpack .../r-cran-spatial_7.3-11-1_amd64.deb ...
Unpacking r-cran-spatial (7.3-11-1) ...
Selecting previously unselected package r-recommended.
Preparing to unpack .../r-recommended_3.2.3-4_all.deb ...
Unpacking r-recommended (3.2.3-4) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Processing triggers for tex-common (6.04) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... done.
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Setting up r-base-core (3.2.3-4) ...
/var/lib/dpkg/info/r-base-core.postinst: 1: /var/lib/dpkg/info/r-base-core.postinst: paperconf: not found
dpkg: error processing package r-base-core (--configure):
 subprocess installed post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration of r-base-dev:
 r-base-dev depends on r-base-core (>= 3.2.3-4); however:
  Package r-base-core is not configured yet.

dpkg: error processing package r-base-dev (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-boot:
 r-cran-boot depends on r-base-core (>= 3.2.1-2); however:
  Package r-base-core is not configured yet.
 r-cran-boot depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing package r-cran-boot (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-mass:
 r-cran-mass depends on r-base-core (>= 3.2.2-1); however:
  Package r-base-core is not configured yet.
 r-cran-mass depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing pNo apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
ackage r-cran-mass (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-class:
 r-cran-class depends on r-base-core (>= 3.2.2-1); however:
  Package r-base-core is not configured yet.
 r-cran-class depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.
 r-cran-class depends on r-cran-mass; however:
  Package r-cran-mass is not configured yet.

dpkg: error processing package r-cran-class (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-cluster:
 r-cran-cluster depends on r-base-core (>= 3.2.1-4); however:
  Package r-base-core is not configured yet.
 r-cran-cluster depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing package r-cran-cluster (--configure):
 dependency problems - leaving unconfigured
dpkgNo apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
: dependency problems prevent configuration of r-cran-codetools:
 r-cran-codetools depends on r-base-core (>= 3.2.1-4); however:
  Package r-base-core is not configured yet.
 r-cran-codetools depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing package r-cran-codetools (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-foreign:
 r-cran-foreign depends on r-base-core (>= 3.2.2-1); however:
  Package r-base-core is not configured yet.
 r-cran-foreign depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing package r-cran-foreign (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-kernsmooth:
 r-cran-kernsmooth depends on r-base-core (>= 3.2.1-2); however:
  Package r-base-core is not configured yet.
 r-cran-kernsmooth depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.
 r-cran-kernsmooth depends on r-cran-mass; however:
  Package r-cran-mass is not configured yet.

dpkg: error processing package r-cran-kernsmooth (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-lattice:
 r-cran-lattice depends on r-base-core (>= 3.2.1-4); however:
  Package r-base-core is not configured yet.
 r-cran-lattice depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing package r-cran-lattice (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-matrix:
 r-cran-matrix depends on r-base-core (>= 3.2.2-1); however:
  Package r-base-core is not configured yet.
 r-cran-matrix depends on r-api-3; however:
  PNo apport report written because MaxReports is reached already
ackage r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.
 r-cran-matrix depends on r-cran-lattice (>= 0.12-11.1); however:
  Package r-cran-lattice is not configured yet.

dpkg: error processing package r-cran-matrix (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-nlme:
 r-cran-nlme depends on r-base-core (>= 3.2.3-4); however:
  Package r-base-core is not configured yet.
 r-cran-nlme depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.
 r-cran-nlme depends on r-cran-lattice (>= 0.12-11.1); however:
  Package r-cran-lattice is not configured yet.

dpkg: error processing package r-cran-nlme (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-mgcv:
 r-cran-mgcv depends on r-base-core (>= 3.2.3-4); however:
  Package r-base-core is not configured yet.
 r-cranNo apport report written because MaxReports is reached already
-mgcv depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.
 r-cran-mgcv depends on r-cran-nlme; however:
  Package r-cran-nlme is not configured yet.
 r-cran-mgcv depends on r-cran-matrix; however:
  Package r-cran-matrix is not configured yet.

dpkg: error processing package r-cran-mgcv (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-nnet:
 r-cran-nnet depends on r-base-core (>= 3.2.3-4); however:
  Package r-base-core is not configured yet.
 r-cran-nnet depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing package r-cran-nnet (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-survival:
 r-cran-survival depends on r-base-core (>= 3.2.1-3); however:
  Package r-base-core is not configured yet.
 r-cran-survival depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing package r-cran-survival (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-rpart:
 r-cran-rpart depends on r-base-core (>= 3.2.1-2); however:
  Package r-base-core is not configured yet.
 r-cran-rpart depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.
 r-cran-rpart depends on r-cran-survival; however:
  Package r-cran-survival is not configured yet.

No apport report written because MaxReports is reached already
dpkg: error processing package r-cran-rpart (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of r-cran-spatial:
 r-cran-spatial depends on r-base-core (>= 3.2.2-1); however:
  Package r-base-core is not configured yet.
 r-cran-spatial depends on r-api-3; however:
  Package r-api-3 is not installed.
  Package r-base-core which provides r-api-3 is not configured yet.

dpkg: error processing package r-cran-spatial (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of r-recommended:
 r-recommended depends on r-base-core (>= 3.2.3-4); however:
  Package r-base-core is not configured yet.
 r-recommended depends on r-cran-boot (>= 1.2.19); however:
  Package r-cran-boot is not configured yet.
 r-recommended depends on r-cran-cluster (>= 1.9.6-2); however:
  Package r-cran-cluster is not configured yet.
 r-recommended depends on r-cran-foreign (>= 0.7-2); however:
  Package r-cran-foreign is not configured yet.
 r-recommended depends on r-cran-kernsmooth (>= 2.2.14); however:
  Package r-cran-kernsmooth is not configured yet.
 r-recommended depends on r-cran-lattice (>= 0.10.11); however:
  Package r-cran-lattice is not configured yet.
 r-recommended depends on r-cran-mgcv (>= 1.1.5); however:
  Package r-cran-mgcv is not configured yet.
 r-recommended depends on r-cran-nlme (>= 3.1.52); however:
  Package r-cran-nlme is not configured yet.
 r-recommended depends on r-cran-rpart (>= 3.1.20); however:
  Package r-cran-rpart is No apport report written because MaxReports is reached already
not c
dpkg: error processing package r-recommended (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 r-base-core
 r-base-dev
 r-cran-boot
 r-cran-mass
 r-cran-class
 r-cran-cluster
 r-cran-codetools
 r-cran-foreign
 r-cran-kernsmooth
 r-cran-lattice
 r-cran-matrix
 r-cran-nlme
 r-cran-mgcv
 r-cran-nnet
 r-cran-survival
 r-cran-rpart
 r-cran-spatial
 r-recommended
E: Sub-process /usr/bin/dpkg returned an error code (1)