A few months back I edited the PostgreSQL version 8.2.19 source code in Ubuntu OS to change the algorithm of the buffer manager in it. I don't remember what I exactly did but I did something wrong (clearly) so now whenever I try to install a new program, I get the following error (even after it installs successfully)
This was after I used the command sudo apt-get install maven to install maven. This happens every time I do a sudo apt-get install <whatever>, the program installs but this comes up:
Errors were encountered while processing:
postgres-xc
E: Sub-process /usr/bin/dpkg returned an error code (1)
I think I messed with some files that affect what happens when a sudo apt-get install is done and I'm trying to get this to go away. I have attached a screenshot as well. Can someone help me?
***I need 10 reputation to post an image so it won't let me post a screenshot so here is the end part of the Maven install*****
Setting up testng (6.8.7-2) ...
Setting up libosgi-compendium-java (4.3.0-1) ...
Setting up libgeronimo-osgi-support-java (1.0-2) ...
Setting up libwagon-java (1.0.0-2ubuntu2) ...
Setting up libgeronimo-jpa-2.0-spec-java (1.1-2) ...
Setting up libmaven2-core-java (2.2.1-14) ...
Setting up libmaven-scm-java (1.3-5) ...
Setting up libplexus-containers1.5-java (1.5.5-6) ...
Setting up libsisu-ioc-java (2.3.0-5) ...
Setting up libaether-java (1.13.1-2) ...
Setting up libwagon2-java (2.5-1) ...
Setting up maven (3.0.5-1) ...
update-alternatives: using /usr/share/maven/bin/mvn to provide /usr/bin/mvn (mvn) in auto mode
Errors were encountered while processing:
postgres-xc
E: Sub-process /usr/bin/dpkg returned an error code (1)
root#r-HP-Pavilion-g6-Notebook-PC:/home/r# exit
exit
r#r-HP-Pavilion-g6-Notebook-PC:~$
Sorry for the late post, I figured this out around a year ago. I used the purge method in Ubuntu to completely unintall postgres. It stopped the error.
Related
I wanted to change my terminal to enable e.g. mouse interaction. So I got the gnome-terminal code, but when I wanted to generate it (without changing anything), the following problem occured:
When I run ./autogen.sh --without-pcre2 I get the error message Requested 'vte-2.91 >= 0.45.0' but version of vte is 0.42.5.
So I've tried to install vte-2.91 higher than 0.45.0 but the highest I could find was 0.44.2 (and I could not install that either)
Does anyone know how to get a vte-2.91 version >= 0.45.0?
Ok, found a solution myself.
just runsudo apt-get build-dep gnome-terminal .
Also to get the Code one can simply use apt-get source gnome-teminal
or for the VTE-Code: apt-get source libvte-2.91-0 .
I wanted to install msttfonts on CentOS 7. Following this guide everything goes fine, until I got to run the command:
# rpmbuild -bb msttcorefonts-2.5-1.spec
The system then throws this message:
cabextract is needed by msttcorefonts-2.0-1.noarch
It is pretty obvious that I've to install cabextract, so I did. By Downloading source from here, extracting, and then ./config... make... make install... (you know guys: all the routine). And I confirm the installation was successful with
# cabextract --version
Which answers with
cabextract version 1.6
So, I go back with my command rpmbuild... But the system stills answer me
cabextract is needed by msttcorefonts-2.0-1.noarch
And now, the questions:
What I'm doing wrong? Do I need to reboot the server? Is there a kind of command to tell the server "hey! this cabextract thing is already installed"?
... and well, while I was writting this question, I could resolve it thanks to this post. So I just leave this question just for further reference.
Thanks in advance.
You need to install the cabextract package (by running yum install cabextract).
The message you are seeing is a dependency error: the msttcorefonts-2.5-1.spec file lists a dependency on cabextract, but because you have installed it from source there is no information about it in the local packages database.
Since last day I am getting issue(see link) with the Upwork. Many times I have reinstall the Upwork and restart the system but nothing goes happen.The network connection is also fine.I google but got nothing helpful. Anyone can suggested me how can I fix the issue. and make the Upwork run correctly.
As I remember the Upwork is running fine, I am getting the issue, since I run the command 'sudo restart lightdm' to display time on menu bar.
Please follow the below link and steps to fix up-work issue.
https://community.upwork.com/t5/Freelancers/Error-Message-THERE-WAS-A-PROBLEM-LOADING-UPWORK/td-p/83016/page/3
sudo dpkg -i libnss
wget http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3_3.19.2-1ubuntu1_i386.deb
sudo dpkg -i libnss3_3.19.2-1ubuntu1_i386.deb
Upwork fixed.
Note : These issues we are getting if we do not close the up-work properly while shutting down the operating system. Please remember this things.
After repeated attempts and trying to google this issue I'm stuck and am looking for help from my fellow stackers.
Following the wiki from tcadmin I have to run the following commands
wget http://www.tcadmin.com/installer/mono-2.11.4-i386.rpm
yum -y install mono-2.11.4-i386.rpm --nogpgcheck
/opt/mono-2.11.4/bin/mozroots --import --sync --quiet
/opt/mono-2.11.4/bin/mono --aot -O=all /opt/mono-2.11.4/lib/mono/2.0/mscorlib.dll
for i in /opt/mono-2.11.4/lib/mono/gac/*/*/*.dll; do /opt/mono-2.11.4/bin/mono --aot -O=all $i; done
when I get to the yum part it fails and outputs this error.
file / from install of mono-2.11.4-bi.x86_64 conflicts with file from package filesystem-3.2-18.el7.x86_64
Most sites and places suggest using an override or force command but this sounds stupid and will probably cause issues down the road for myself and the system.
I have flagged a ticket with the company that supplies the wiki about this issue but I'm yet to have a reply.
Another suggestion was to extract the rpm and move the files one by one but this is quite time consuming..
The ticket was responed to with the following;
It is safe to force install because all files are placed in /opt/mono-2.11.4 but there is a bug with mono on centos 7 that prevents tcadmin from working correctly.
For anyone else who happens upon this thread, I'm pleased to report that while I didn't encounter this error installing mono (that was a whole other process) I did encounter it while trying to install TCAdmin itself, but I was able to complete the installation of TCAdmin on CentOS 7 after using rpmrebuild to modify the spec.
Simply install rpmrbebuild, run rpmrebuild -pe {packagename}.rpm, scroll down to the %files section and remove the lines for any offending directories (in my case, the '/' and '/home' directories), save and quit, press y, and note the result location. In my case, it was /root/rpmbuild/RPMS/noarch/{packagename}.rpm.
Traverse to that directory and run yum -y install ./{packagename.rpm and it will install without a hitch.
The same should also apply to any other packages that return the conflicts with filesystem error. Just adjust the package names in the above examples accordingly.
*Thanks to the venerable Ahmad Samir for pointing me in the right direction with his post in this thread.
I had the same issue trying to install Fluentd agent on CentOS 7:
(venv)[user#machine01 tmp]$ sudo rpm -ivh td-agent-2.1.1-0.x86_64.rpm
warning: td-agent-2.1.1-0.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID a12e206f: NOKEY
Preparing... ################################# [100%]
file /opt from install of td-agent-2.1.1-0.x86_64 conflicts with file from package filesystem-3.2-18.el7.x86_64
I wouldn't say that downgrading your whole OS is the solution. Maybe an elegant workaround would be to rebuild the .rpm file in order to avoid those file systems which are making conflicts. You can do this by modifying the spec file with rpmrebuild command.
However, if you trust the software you are about to install or you want to try if works no matter what, then an easier (and faster) workaround is to force the rpm installation. That's what I did ...
(venv)[user#machine01 tmp]$ sudo rpm -ivh --force td-agent-2.1.1-0.x86_64.rpm
warning: td-agent-2.1.1-0.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID a12e206f: NOKEY
Preparing... ################################# [100%]
Updating / installing...
1:td-agent-2.1.1-0 ################################# [100%]
adding 'td-agent' group...
adding 'td-agent' user...
Installing default conffile...
prelink detected. Installing /etc/prelink.conf.d/td-agent-ruby.conf ...
Configure td-agent to start, when booting up the OS...
...and it worked for me
(venv)[user#machine01 tmp]$ sudo systemctl start td-agent.service
(venv)[user#machine01 tmp]$ sudo systemctl status td-agent.service
td-agent.service - LSB: td-agent's init script
Loaded: loaded (/etc/rc.d/init.d/td-agent)
Active: active (running) since vie 2014-12-12 09:34:09 CET; 4s ago
Process: 17178 ExecStart=/etc/rc.d/init.d/td-agent start (code=exited, status=0/SUCCESS)
...
Hope it helps
This is an inherent issue with centos 7.
Going back to centos 6 fixed it.
Ok, I have this whole new machine on which I just freshly installed Ubuntu 12.10. I'm trying to install node.js by following the instructions on this website. The first time I did that it worked like a charm, but then I had some troubles installing packages because nodejs --version and node --version gave two different results. I thought then that the best idea was to do a rm -rf /usr/var/node or something like that. That resulted in a total mess up of everything.
By trying to call sudo apt-get install nodejs again, I get the following error message:
[...]
Errors were encountered while processing:
/var/cache/apt/archives/nodejs_0.8.26-1chl1~quantal1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
I really tried everything, from apt-autoremove to clean to whatever, I cannot possibly figure out why this is not working anymore. Any ideas?
Thanks
Edit: it's funny how people gives -1 without even reading the question. If these smart alecks think this question is stupid or inappropriate, they could simply write so or help me out, since I'm struggling with this. Also, removed some of the output, since people cannot read until the end of it.
Try install the locales packages, and run dpkg-reconfigure locales to set the locales "en-US" for the system.