Hai all,

I have upgraded Linux mint 13 Mate (maya) to 14 (Naida) using terminal with commands everything run fine but is not updated. Give me the remedy for this solution.

Thanks in Advance.,

Velmurugan.M,
System Administrator.

Dani AI

Generated

Quick diagnostic and recovery checklist (concise, practical)

First confirm whether the system actually completed an in-place upgrade or is still reporting the old release. Check the distro files and kernel to see the real state:

lsb_release -a
cat /etc/linuxmint/info
uname -r

If those still show Mint 13 (maya) while package activity appears recent, the upgrade likely stalled partway or APT sources were not switched.

Common causes and targeted fixes

  • Partially configured or broken packages will block a full upgrade. Check APT/dpkg logs at /var/log/apt/ and /var/log/dpkg.log, look for failures, and run package-repair steps (configure, fix dependencies, then re-check held packages). Useful commands for diagnosis/repair are shown below; they avoid repeating GUI steps already suggested earlier in the thread:
sudo dpkg --configure -a
sudo apt-get -f install
apt-mark showhold
  • Third-party PPAs and proprietary drivers frequently interfere. List sources and temporarily disable or move custom .list files from /etc/apt/sources.list.d/ before attempting fixes.

Prepare for a clean reinstall if needed

  • When many third-party packages are present or repairs become messy, a clean install is often faster and safer (this echoes ). Back up user data and a package list first so the system can be restored to the same state:
dpkg --get-selections > installed-packages.txt
rsync -aAX /home /etc ~/mint-backup/
ls /etc/apt/sources.list.d/

Context and how this ties to earlier replies

  • This expands on ’s point about ensuring upgrade paths are correct and complements ’s pointer to guides: the immediate next step is to verify what the system files actually say and to read the apt/dpkg logs. The sequence above will reveal whether the problem is held packages, broken dependencies, or unchanged APT sources — and those results determine whether repair or a fresh install is the cleanest solution.

Recommended Answers

All 3 Replies

I'm not a Mint user, but I have used several other Debian and Ubuntu based distros over the last few years. Assuming Mint 13 is based on Ubuntu 12.04 LTS and Mint 14 is based on Ubu 12.10 and assuming Mint isn't too vastly different to Ubuntu under the hood; If anything, it's probably just the release upgrade setting in the software sources options that needs to be set correctly in order to upgrade from 13 to 14.

I can't remember which file you need to edit to set this option from the command line, but if you open the upgrade manager or one of the GUI based package management tools (Software centre, Synaptic etc.. Again, not sure what Mint uses by default) and then go to 'Settings->Configure software sources' to bring up the software sources dialog; then go to the 'Upgrades' tab and set the 'Show new distribution upgrades:' option to 'Normal releases'.

There are two other settings for this option:
'Never' - which means you'll only pick up dist-upgrades for the currently installed version (kernel upgrades etc) and won't get notified when a new version becomes available.
'Long term releases only' - which will only show upgrades when a new LTS version is available.

But setting this option to 'Normal releases' should allow you to pick up any new distribution upgrades.

Once that setting has been made you can either upgrade via the GUI, or you can open a terminal and use:
sudo apt-get update && sudo apt-get dist-upgrade
And that should start the upgrade to Mint 14!

Like I said, I'm not a Mint user, so I don't know that my instructions are 100% correct. But as Mint is Ubuntu based, I imagine the steps required would be very similar to Ubuntu, if not exactly the same!

Like the above post says, you should @ least be running their latest linux headers and kernel on the previous version if thats all you did.

When you say updated from 13 to 14... Did you do a scripted install over itself? How did you upgrade?
Is there any reason you cant just wipe the partition version 13 is on and install version 14 there?
Theres no data there right? just the o/s?
Complications always bite me when installing overitself.

Personally i keep a goal of constant preparedness to nuke my o/s partition @ any moment and revive without issue. Via running a (well kept & updated & backed up) script after installing the new vesrion, restoring my customizations & i am right back where i was.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.