Can't upgrade - error “/etc/environment: source: not found” and “error processing package install-info”

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite












This is the error message I get when I do a sudo apt upgrade. The upgrade fails and includes this message:



Setting up install-info (6.1.0.dfsg.1-5) ...
/usr/sbin/update-info-dir: 2: /etc/environment: source: not found
dpkg: error processing package install-info (--configure):
subprocess installed post-installation script returned error exit 
status 127
Errors were encountered while processing:
 install-info
E: Sub-process /usr/bin/dpkg returned an error code (1)


I reinstalled install-info through synaptic and am still getting this error and would be grateful for help in setting me straight as to how to read this message and
how to react..




apt package-management upgrade dpkg




share|improve this question






















  • Can someone help me to read this error message? It seems to be saying /etc/environment is missing something? It's simply a line of path statements.
    – Tom Connolly
    May 11 at 19:06










  • I'd try sudo dpkg --configure -a and sudo apt-get install --reinstall install-info and then maybe sudo apt-get update && sudo dpkg --configure -a && sudo apt-get install -f && sudo apt-get upgrade. I hope this helps.
    – starkus
    May 11 at 20:42











  • also I'd try sudo dpkg-reconfigure install-info
    – starkus
    May 11 at 20:45










  • Looking at the error, it seems there is a command in the script /usr/sbin/update-info-dir that says source /etc/environment, but it is being run by a shell (dash I guess) that doesn't know the source command. Instead of source, that script should have . /etc/environment, which does the same thing. That's very very strange. Here's the version of that file I have on my system
    – Zanna
    May 16 at 7:48















up vote
2
down vote

favorite












This is the error message I get when I do a sudo apt upgrade. The upgrade fails and includes this message:



Setting up install-info (6.1.0.dfsg.1-5) ...
/usr/sbin/update-info-dir: 2: /etc/environment: source: not found
dpkg: error processing package install-info (--configure):
subprocess installed post-installation script returned error exit 
status 127
Errors were encountered while processing:
 install-info
E: Sub-process /usr/bin/dpkg returned an error code (1)


I reinstalled install-info through synaptic and am still getting this error and would be grateful for help in setting me straight as to how to read this message and
how to react..




apt package-management upgrade dpkg




share|improve this question






















  • Can someone help me to read this error message? It seems to be saying /etc/environment is missing something? It's simply a line of path statements.
    – Tom Connolly
    May 11 at 19:06










  • I'd try sudo dpkg --configure -a and sudo apt-get install --reinstall install-info and then maybe sudo apt-get update && sudo dpkg --configure -a && sudo apt-get install -f && sudo apt-get upgrade. I hope this helps.
    – starkus
    May 11 at 20:42











  • also I'd try sudo dpkg-reconfigure install-info
    – starkus
    May 11 at 20:45










  • Looking at the error, it seems there is a command in the script /usr/sbin/update-info-dir that says source /etc/environment, but it is being run by a shell (dash I guess) that doesn't know the source command. Instead of source, that script should have . /etc/environment, which does the same thing. That's very very strange. Here's the version of that file I have on my system
    – Zanna
    May 16 at 7:48













up vote
2
down vote

favorite









up vote
2
down vote

favorite











This is the error message I get when I do a sudo apt upgrade. The upgrade fails and includes this message:



Setting up install-info (6.1.0.dfsg.1-5) ...
/usr/sbin/update-info-dir: 2: /etc/environment: source: not found
dpkg: error processing package install-info (--configure):
subprocess installed post-installation script returned error exit 
status 127
Errors were encountered while processing:
 install-info
E: Sub-process /usr/bin/dpkg returned an error code (1)


I reinstalled install-info through synaptic and am still getting this error and would be grateful for help in setting me straight as to how to read this message and
how to react..




apt package-management upgrade dpkg




share|improve this question














This is the error message I get when I do a sudo apt upgrade. The upgrade fails and includes this message:



Setting up install-info (6.1.0.dfsg.1-5) ...
/usr/sbin/update-info-dir: 2: /etc/environment: source: not found
dpkg: error processing package install-info (--configure):
subprocess installed post-installation script returned error exit 
status 127
Errors were encountered while processing:
 install-info
E: Sub-process /usr/bin/dpkg returned an error code (1)


I reinstalled install-info through synaptic and am still getting this error and would be grateful for help in setting me straight as to how to read this message and
how to react..





apt package-management upgrade dpkg





share|improve this question













share|improve this question




share|improve this question








edited May 16 at 7:49









Zanna

47.9k13119227




47.9k13119227










asked May 11 at 15:29









Tom Connolly

133117




133117











  • Can someone help me to read this error message? It seems to be saying /etc/environment is missing something? It's simply a line of path statements.
    – Tom Connolly
    May 11 at 19:06










  • I'd try sudo dpkg --configure -a and sudo apt-get install --reinstall install-info and then maybe sudo apt-get update && sudo dpkg --configure -a && sudo apt-get install -f && sudo apt-get upgrade. I hope this helps.
    – starkus
    May 11 at 20:42











  • also I'd try sudo dpkg-reconfigure install-info
    – starkus
    May 11 at 20:45










  • Looking at the error, it seems there is a command in the script /usr/sbin/update-info-dir that says source /etc/environment, but it is being run by a shell (dash I guess) that doesn't know the source command. Instead of source, that script should have . /etc/environment, which does the same thing. That's very very strange. Here's the version of that file I have on my system
    – Zanna
    May 16 at 7:48

















  • Can someone help me to read this error message? It seems to be saying /etc/environment is missing something? It's simply a line of path statements.
    – Tom Connolly
    May 11 at 19:06










  • I'd try sudo dpkg --configure -a and sudo apt-get install --reinstall install-info and then maybe sudo apt-get update && sudo dpkg --configure -a && sudo apt-get install -f && sudo apt-get upgrade. I hope this helps.
    – starkus
    May 11 at 20:42











  • also I'd try sudo dpkg-reconfigure install-info
    – starkus
    May 11 at 20:45










  • Looking at the error, it seems there is a command in the script /usr/sbin/update-info-dir that says source /etc/environment, but it is being run by a shell (dash I guess) that doesn't know the source command. Instead of source, that script should have . /etc/environment, which does the same thing. That's very very strange. Here's the version of that file I have on my system
    – Zanna
    May 16 at 7:48
















Can someone help me to read this error message? It seems to be saying /etc/environment is missing something? It's simply a line of path statements.
– Tom Connolly
May 11 at 19:06




Can someone help me to read this error message? It seems to be saying /etc/environment is missing something? It's simply a line of path statements.
– Tom Connolly
May 11 at 19:06












I'd try sudo dpkg --configure -a and sudo apt-get install --reinstall install-info and then maybe sudo apt-get update && sudo dpkg --configure -a && sudo apt-get install -f && sudo apt-get upgrade. I hope this helps.
– starkus
May 11 at 20:42





I'd try sudo dpkg --configure -a and sudo apt-get install --reinstall install-info and then maybe sudo apt-get update && sudo dpkg --configure -a && sudo apt-get install -f && sudo apt-get upgrade. I hope this helps.
– starkus
May 11 at 20:42













also I'd try sudo dpkg-reconfigure install-info
– starkus
May 11 at 20:45




also I'd try sudo dpkg-reconfigure install-info
– starkus
May 11 at 20:45












Looking at the error, it seems there is a command in the script /usr/sbin/update-info-dir that says source /etc/environment, but it is being run by a shell (dash I guess) that doesn't know the source command. Instead of source, that script should have . /etc/environment, which does the same thing. That's very very strange. Here's the version of that file I have on my system
– Zanna
May 16 at 7:48





Looking at the error, it seems there is a command in the script /usr/sbin/update-info-dir that says source /etc/environment, but it is being run by a shell (dash I guess) that doesn't know the source command. Instead of source, that script should have . /etc/environment, which does the same thing. That's very very strange. Here's the version of that file I have on my system
– Zanna
May 16 at 7:48











2 Answers
2






active

oldest

votes

















up vote
1
down vote













I found this way down in a thread elsewhere, and it worked!




if all else fails. What I did was I first changed the directory to:



cd /var/lib/dpkg/info


then I removed everything with .postinst:



sudo rm *.postinst


then update repositories



sudo apt-get update


then everything went back to normal when I did:



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



Note: I did not do this last line, as my issue didn't have anything to do with openjdk. I simply ran the apt update






share|improve this answer






















  • postinst - This script typically completes any required configuration of the package foo once foo has been unpacked from its Debian archive (".deb") file. Often, 'postinst' scripts ask users for input, and/or warn them that if they accept default values, they should remember to go back and re-configure that package as needed. Many 'postinst' scripts then execute any commands necessary to start or restart a service once a new package has been installed or upgraded.
    – starkus
    May 12 at 17:36











  • I'm not sure if I would reinstall all installed packages if i did the above suggested...
    – starkus
    May 12 at 17:37










  • Another option is to edit the offending .postinst file and put exit 0 on the second line (after the first line containing #!/bin/sh.
    – WinEunuuchs2Unix
    May 12 at 18:21

















up vote
0
down vote













I started to get same thing and just used



for i in $(ls -F *.postinst); do mv ./$i ./$i.old; done in /var/lib/dpkg/info


then my standard ansible playbooks to bring servers current worked






share|improve this answer






















  • those files will have standard names, but in general, you shouldn't parse the output of ls and more importantly, you shouldn't post answers with commands with no explanation of what they do! Please edit this to add some commentary
    – Zanna
    May 16 at 7:42










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034961%2fcant-upgrade-error-etc-environment-source-not-found-and-error-processin%23new-answer', 'question_page');

);

Post as a guest

















2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













I found this way down in a thread elsewhere, and it worked!




if all else fails. What I did was I first changed the directory to:



cd /var/lib/dpkg/info


then I removed everything with .postinst:



sudo rm *.postinst


then update repositories



sudo apt-get update


then everything went back to normal when I did:



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



Note: I did not do this last line, as my issue didn't have anything to do with openjdk. I simply ran the apt update






share|improve this answer






















  • postinst - This script typically completes any required configuration of the package foo once foo has been unpacked from its Debian archive (".deb") file. Often, 'postinst' scripts ask users for input, and/or warn them that if they accept default values, they should remember to go back and re-configure that package as needed. Many 'postinst' scripts then execute any commands necessary to start or restart a service once a new package has been installed or upgraded.
    – starkus
    May 12 at 17:36











  • I'm not sure if I would reinstall all installed packages if i did the above suggested...
    – starkus
    May 12 at 17:37










  • Another option is to edit the offending .postinst file and put exit 0 on the second line (after the first line containing #!/bin/sh.
    – WinEunuuchs2Unix
    May 12 at 18:21














up vote
1
down vote













I found this way down in a thread elsewhere, and it worked!




if all else fails. What I did was I first changed the directory to:



cd /var/lib/dpkg/info


then I removed everything with .postinst:



sudo rm *.postinst


then update repositories



sudo apt-get update


then everything went back to normal when I did:



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



Note: I did not do this last line, as my issue didn't have anything to do with openjdk. I simply ran the apt update






share|improve this answer






















  • postinst - This script typically completes any required configuration of the package foo once foo has been unpacked from its Debian archive (".deb") file. Often, 'postinst' scripts ask users for input, and/or warn them that if they accept default values, they should remember to go back and re-configure that package as needed. Many 'postinst' scripts then execute any commands necessary to start or restart a service once a new package has been installed or upgraded.
    – starkus
    May 12 at 17:36











  • I'm not sure if I would reinstall all installed packages if i did the above suggested...
    – starkus
    May 12 at 17:37










  • Another option is to edit the offending .postinst file and put exit 0 on the second line (after the first line containing #!/bin/sh.
    – WinEunuuchs2Unix
    May 12 at 18:21












up vote
1
down vote










up vote
1
down vote









I found this way down in a thread elsewhere, and it worked!




if all else fails. What I did was I first changed the directory to:



cd /var/lib/dpkg/info


then I removed everything with .postinst:



sudo rm *.postinst


then update repositories



sudo apt-get update


then everything went back to normal when I did:



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



Note: I did not do this last line, as my issue didn't have anything to do with openjdk. I simply ran the apt update






share|improve this answer














I found this way down in a thread elsewhere, and it worked!




if all else fails. What I did was I first changed the directory to:



cd /var/lib/dpkg/info


then I removed everything with .postinst:



sudo rm *.postinst


then update repositories



sudo apt-get update


then everything went back to normal when I did:



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



Note: I did not do this last line, as my issue didn't have anything to do with openjdk. I simply ran the apt update







share|improve this answer














share|improve this answer



share|improve this answer








edited May 16 at 7:50









Zanna

47.9k13119227




47.9k13119227










answered May 12 at 17:25









Tom Connolly

133117




133117











  • postinst - This script typically completes any required configuration of the package foo once foo has been unpacked from its Debian archive (".deb") file. Often, 'postinst' scripts ask users for input, and/or warn them that if they accept default values, they should remember to go back and re-configure that package as needed. Many 'postinst' scripts then execute any commands necessary to start or restart a service once a new package has been installed or upgraded.
    – starkus
    May 12 at 17:36











  • I'm not sure if I would reinstall all installed packages if i did the above suggested...
    – starkus
    May 12 at 17:37










  • Another option is to edit the offending .postinst file and put exit 0 on the second line (after the first line containing #!/bin/sh.
    – WinEunuuchs2Unix
    May 12 at 18:21
















  • postinst - This script typically completes any required configuration of the package foo once foo has been unpacked from its Debian archive (".deb") file. Often, 'postinst' scripts ask users for input, and/or warn them that if they accept default values, they should remember to go back and re-configure that package as needed. Many 'postinst' scripts then execute any commands necessary to start or restart a service once a new package has been installed or upgraded.
    – starkus
    May 12 at 17:36











  • I'm not sure if I would reinstall all installed packages if i did the above suggested...
    – starkus
    May 12 at 17:37










  • Another option is to edit the offending .postinst file and put exit 0 on the second line (after the first line containing #!/bin/sh.
    – WinEunuuchs2Unix
    May 12 at 18:21















postinst - This script typically completes any required configuration of the package foo once foo has been unpacked from its Debian archive (".deb") file. Often, 'postinst' scripts ask users for input, and/or warn them that if they accept default values, they should remember to go back and re-configure that package as needed. Many 'postinst' scripts then execute any commands necessary to start or restart a service once a new package has been installed or upgraded.
– starkus
May 12 at 17:36





postinst - This script typically completes any required configuration of the package foo once foo has been unpacked from its Debian archive (".deb") file. Often, 'postinst' scripts ask users for input, and/or warn them that if they accept default values, they should remember to go back and re-configure that package as needed. Many 'postinst' scripts then execute any commands necessary to start or restart a service once a new package has been installed or upgraded.
– starkus
May 12 at 17:36













I'm not sure if I would reinstall all installed packages if i did the above suggested...
– starkus
May 12 at 17:37




I'm not sure if I would reinstall all installed packages if i did the above suggested...
– starkus
May 12 at 17:37












Another option is to edit the offending .postinst file and put exit 0 on the second line (after the first line containing #!/bin/sh.
– WinEunuuchs2Unix
May 12 at 18:21




Another option is to edit the offending .postinst file and put exit 0 on the second line (after the first line containing #!/bin/sh.
– WinEunuuchs2Unix
May 12 at 18:21












up vote
0
down vote













I started to get same thing and just used



for i in $(ls -F *.postinst); do mv ./$i ./$i.old; done in /var/lib/dpkg/info


then my standard ansible playbooks to bring servers current worked






share|improve this answer






















  • those files will have standard names, but in general, you shouldn't parse the output of ls and more importantly, you shouldn't post answers with commands with no explanation of what they do! Please edit this to add some commentary
    – Zanna
    May 16 at 7:42














up vote
0
down vote













I started to get same thing and just used



for i in $(ls -F *.postinst); do mv ./$i ./$i.old; done in /var/lib/dpkg/info


then my standard ansible playbooks to bring servers current worked






share|improve this answer






















  • those files will have standard names, but in general, you shouldn't parse the output of ls and more importantly, you shouldn't post answers with commands with no explanation of what they do! Please edit this to add some commentary
    – Zanna
    May 16 at 7:42












up vote
0
down vote










up vote
0
down vote









I started to get same thing and just used



for i in $(ls -F *.postinst); do mv ./$i ./$i.old; done in /var/lib/dpkg/info


then my standard ansible playbooks to bring servers current worked






share|improve this answer














I started to get same thing and just used



for i in $(ls -F *.postinst); do mv ./$i ./$i.old; done in /var/lib/dpkg/info


then my standard ansible playbooks to bring servers current worked







share|improve this answer














share|improve this answer



share|improve this answer








edited May 16 at 7:40









Zanna

47.9k13119227




47.9k13119227










answered May 16 at 2:02









GTIMANiac

1




1











  • those files will have standard names, but in general, you shouldn't parse the output of ls and more importantly, you shouldn't post answers with commands with no explanation of what they do! Please edit this to add some commentary
    – Zanna
    May 16 at 7:42
















  • those files will have standard names, but in general, you shouldn't parse the output of ls and more importantly, you shouldn't post answers with commands with no explanation of what they do! Please edit this to add some commentary
    – Zanna
    May 16 at 7:42















those files will have standard names, but in general, you shouldn't parse the output of ls and more importantly, you shouldn't post answers with commands with no explanation of what they do! Please edit this to add some commentary
– Zanna
May 16 at 7:42




those files will have standard names, but in general, you shouldn't parse the output of ls and more importantly, you shouldn't post answers with commands with no explanation of what they do! Please edit this to add some commentary
– Zanna
May 16 at 7:42












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034961%2fcant-upgrade-error-etc-environment-source-not-found-and-error-processin%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

Image
Clash Royale CLAN TAG #URR8PPP up vote 45 down vote favorite 7 I graduated last year with a BS in Computer Science. I do not come from a particularly wealthy family, (very low middle class), and was only able to afford my education via school loans/scholarships and working low-wage jobs, with no support from my family or anyone else. I realize some scholarship/loan programs extend into grad school. But I don't think those cover all costs. Now I'm lucky enough to have a decent-paying salary in industry, along with benefits and living on my own, and I'm thinking one day (sooner rather than later) I'd like to try my hand at research or continue my degree, but these things cost money, in addition to my regular living expenses. I read posts here often about academic people being in positions of choosing between these crazy research grad programs, some in Japan, or Ireland (while they currently live in the U.S./U.K.) then moving around between countries/universit...
Read more

Trouble downloading packages list due to a “Hash sum mismatch” error

Image
Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 331 down vote favorite 117 When I check for updates, I get a "Failed To Download Repository Information" error. This is what comes up under details: W: Failed to fetch gzip:/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_natty_main_source_Sources Hash Sum mismatch, E: Some index files failed to download. They have been ignored, or old ones used instead. apt share | improve this question edited Nov 12 '14 at 23:37 Braiam 49.5k 19 130 210 asked May 9 '11 at 20:55 Rob 5,300 10 26 40 add a comment  |  up vote 331 down vote favorite 117 When I check for updates, I get a "Failed To Download Repository Information" error. This is what comes up under details: W: Failed to fetch gzip:/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_nat...
Read more

How do I move numbers in filenames, in a batch renaming operation?

Image
Clash Royale CLAN TAG #URR8PPP up vote 10 down vote favorite 1 I have been trying to figure out how to rename files for the past few hours. I have 2000 files that are like this: file.1.pdb file.2.pdb file.3.pdb I would like to rename these files to something like: file.pdb.1 file.pdb.2 file.pdb.3 command-line batch-rename share | improve this question edited Mar 29 at 21:36 Eliah Kagan 79.6k 20 222 359 asked Mar 29 at 15:33 user812758 51 3 Didn't you mean bash ? – avazula Mar 29 at 15:38 4 @avazula No please read this article : en.wikipedia.org/wiki/Batch_renaming – Ali Razmdideh Mar 29 at 15:47 @PerlDuck yes ;) – Ali Razmdideh Mar 29 at 15:52 6 Possible duplicate of How to easily rename files using command line? – wjandrea Mar 29 at 16:09 2 Hey close voters...
Read more