Tag Info

New answers tagged

1

I got this temporary solution from dropbox killall dropbox rm ~/.dropbox-dist/dropbox-lnx.x86*/libxml2.so.2 ~/.dropbox-dist/dropboxd &


0

It looks like you've got a missing comment from the top of the file. Put a # in front of the very first line that says CentOS-Base.repo, yum should then work fine. Have you/anyone modified this file?


0

Not really a transaction error from what I can see, it's a file conflict. IMO (maybe someone can correct me) you pretty much have to remove the npm package. Either physically or just from the RPM database. If you're comfortable with it, you can just do a rpm -e npm to uninstall the package and remove the conflicting files from the filesystem. This would ...


0

As of this writing, there is no minetest 0.4.10 update for Fedora 20. I see that it's included in the new Fedora 21 release. You could also use my COPR, which tracks minetest development (roughly whenever I get around to updating it). See http://copr.fedoraproject.org/coprs/mattdm/minetest — there are builds for F19 and F20 as well as F21.


0

Verify VLC Versions According to the Web Version of the Repository that you are trying to add, the only versions for Ubuntu that the daily builds will work for are: Trusty - 14.04 Utopic - 14.10 Vivid - 15.04 Click the Technical Details line in Green on the Link Above, as the versions will change as this Answer ages. To download the proper version, ...


1

Here are the commands you need to run, if you just want to get it done: sudo add-apt-repository ppa:git-core/ppa -y sudo apt-get update sudo apt-get install git git --version As of Dec 2014, I get git 2.2.0 that way, while the version in the Ubuntu Trusty repositories is 1.9.1.


0

I had the exact error today. I installed plymouth but it did not change the result. It was caused by a wrong nfs entry in /etc/fstab. After deleting that entry the error disappeared. I guess this horrible behaviour is due to the stupid systemd.


4

In Linux Mint 17 Qiana, Synaptic "officially" lacks the upgrade feature. This is for sake of stability - users are supposed to use mintupdate for already-installed packages. Synaptic can still be used to install additional, new packages.


2

Your module was built for an earlier kernel (the one that has just been updated). Make sure that you've rebooted so that you are using the latest kernel. Confirm that the running kernel and the installed version of kernel-headers is the same. You'll now need to recompile your module again for the current kernel: cd rtl8188eu make clean make all make ...


1

I guess you want an automatic update notifier (not just apt-get). Try with the update-notifier package.


1

You can update the package list and print the available updates by executing apt-get update apt-get --just-print upgrade You can update your system by executing the same command without --just-print: apt-get upgrade You'll need to be root or have sudo privileges to execute the above commands. As for getting notifications, take a look at ...


4

TL;DR I have a different take on this as a Gentoo user. While I agree with peterph's approach of "Let the System Decide," I disagree when it comes to an ABI Update. An ABI Update is sometimes a major shift in behavior. In the case of GCC 4.7, the ABI Change was the adoption of the new C++11 Standard, which peterph also pointed out. Here is why I write ...



Top 50 recent answers are included