New answers tagged upgrade
0
Take a look at the steps outlined in this AskUbuntu question and answer thread titled: Requires installation of untrusted packages?.
I would try the steps outlined in this answer specifically:
$ sudo apt-get clean
$ cd /var/lib/apt
$ sudo mv lists lists.old
$ sudo mkdir -p lists/partial
$ sudo apt-get clean
$ sudo apt-get update
These steps will rebuild ...
1
No, apt doesn't make that easy.
The best option is some type of snapshot. Either filesystem snapshots through lvm/zfs/btrfs or instance snapshots if you're using a VM of some kind.
The only other option is to take an inventory of installed packages (dpkg -l) before and after. If you wan to "roll back" you have to explicitly install the previous version.
1
My first guess would be that you're mixing YUM repositories. Notice that the RPM for clamav as a .rf. in its name which signifies that it's a rpmforge package. I'd confirm that clamd also is a rpmforge package and not coming from one of the other repos.
The error message is basically telling you this, saying that it can't find an appropriate package, ...
2
I did as schaiba said, so:
backup your sensitive stuff (for me only /home dir)
reinstall operating system
0
I wouldn't recommend upgrading from Mint 13 to Mint 15. Mint doesn't take a lot of care to make upgrade smooth, and skipping a version increases the risk of problems. Upgrade to Mint 14 first.
When you have upgrade trouble with apt-get, try aptitude. It often uses different conflict resolution algorithms, and depending on the version one or the other may be ...
0
Linux Mint expressly discourages upgrades in general. I highly recommend you read the very good and thorough post written by Mint's chief developer about why it is generally a good idea to do a fresh install instead of an upgrade. Mint comes with a very good tool specifically designed to make this painless.
In any case, you should never jump releases like ...
0
I recently upgraded this netbook from Fedora 16 to 17 and then to 18, but before 16 went end-of-life. It can't be done in one step, check the upgrade notes for Fedora 17 and follow them; once Fedora 17 is A-OK (remember to run the cleanup commands suggested!) then go for Fedora 18.
0
I would try upgrading to Fedora 17 - 15 might be old enough that mirrors have removed it, which seems to be the error you're getting. If that doesn't work, you're probably better off wiping and starting anew, since you'll probably spend more time getting the upgrade to work than you would simply restoring your data.
0
the latest centos-release RPM:
rpm -Uvh http://mirror.centos.org/centos/5/os/i386/CentOS/centos-release-5-9.el5.centos.1.i386.rpm
2
Instead of doing the yum remove or yum update you should be able to yum install kernel-<ver> where <ver> is a specific version number. Also you can have multiple kernels installed.
It's usually advised to keep a couple around for situations like this. When the system boots up you can select from one of the kernels to boot the system up.
1
I had a similar problem (on Ubuntu 13.04), I had to install the ubuntuone-control-panel-qt package manually. Search for it in the Software Centre or run:
sudo apt-get install ubuntuone-control-panel-qt
in a terminal.
Possibly the problem has to do with the transition from the GTK-based control panel to the QT-based (the ubuntuone-control-panel-gtk ...
2
It appears you host added vmhgfs, which is a VMWare filesystem. So, likely, they're exporting something to you, possibly a fairly large filesystem, and don't want it to be crawled by updatedb.
Wheezy's default apparently adds curlftpfs as well (you can tell by scanning across the line in the diff, and seeing that's the only part that differs).
So, the ...
0
All distributions keep a few kernels around for the (unlikely) case a kernel install gets botched or the last update breaks badly. Boot an older one.
Most distribution's install media double as rescue media. Boot with that, and fix the system.
It might be due to some sort of hardware error (has happened to me...). Use the install media's diagnostic tools ...
0
You should remove /var/lib/ubuntu-release-upgrader/release-upgrade-available (on 12.04 and 10.04 systems that was /var/lib/update-notifier/release-upgrade-available). The release upgrade should have removed (or emptied) that file for you.
The /etc/motd file is updated by the scripts in /etc/update-motd.d, this release upgrade part in particular by ...
Top 50 recent answers are included
