Upgrade Kubuntu Lucid 10.04.02 LTS to Maverick 10.10

Last Updated: 2025-01-02

Today i wanted to upgrade to the latest version of kubuntu (being 10.10 Maverick Meerkat) and ran into some trouble. Normally, a quite simple

sudo do-release-upgrade --dev

should do the magic, but it just throw me the following error:

An unresolvable problem occurred while calculating the upgrade: Can not mark 'kubuntu-desktop' for upgrade.

A quick look into the log-file didn't clarify things much, but helped finding the answer to the problem:

upgrade kubuntu 10.10 Can't mark 'kubuntu-desktop' for upgrade (E:Unable to correct problems, you have held broken packages.)

To sum it up, i have installed a newer version of KDE through backports than the one which comes bundled with maverick. To solve this issure, just follow these steps:

$ bzr get lp:~ubuntu-core-dev/update-manager/maverick
$ cd maverick/DistUpgrade
$ sudo ./dist-upgrade.py

Not yet rated

94 Comments

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1
1

-1 OR 2+431-431-1=0+0+0+1: on 2025-02-10

1

mGZaLUfS'": on 2025-02-10

1
1

@@7BKZi: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

1

mGZaLUfS: on 2025-02-10

-1 OR 2+682-682-1=0+0+0+1 --

mGZaLUfS: on 2025-02-10

-1 OR 2+46-46-1=0+0+0+1

mGZaLUfS: on 2025-02-10

-1' OR 2+471-471-1=0+0+0+1 --

mGZaLUfS: on 2025-02-10

-1' OR 2+507-507-1=0+0+0+1 or 'eNWm4exO'='

mGZaLUfS: on 2025-02-10

-1" OR 2+312-312-1=0+0+0+1 --

mGZaLUfS: on 2025-02-10

1*if(now()=sysdate(),sleep(15),0)

mGZaLUfS: on 2025-02-10

10'XOR(1*if(now()=sysdate(),sleep(15),0))XOR'Z

mGZaLUfS: on 2025-02-10

10"XOR(1*if(now()=sysdate(),sleep(15),0))XOR"Z

mGZaLUfS: on 2025-02-10

(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/

mGZaLUfS: on 2025-02-10

1-1; waitfor delay '0:0:15' --

mGZaLUfS: on 2025-02-10

1-1); waitfor delay '0:0:15' --

mGZaLUfS: on 2025-02-10

1-1 waitfor delay '0:0:15' --

mGZaLUfS: on 2025-02-10

1KpX9azCo'; waitfor delay '0:0:15' --

mGZaLUfS: on 2025-02-10

1-1 OR 298=(SELECT 298 FROM PG_SLEEP(15))--

mGZaLUfS: on 2025-02-10

1-1) OR 487=(SELECT 487 FROM PG_SLEEP(15))--

mGZaLUfS: on 2025-02-10

1-1)) OR 433=(SELECT 433 FROM PG_SLEEP(15))--

mGZaLUfS: on 2025-02-10

1LGZfqyuj' OR 576=(SELECT 576 FROM PG_SLEEP(15))--

mGZaLUfS: on 2025-02-10

1ya5k2gw7') OR 567=(SELECT 567 FROM PG_SLEEP(15))--

mGZaLUfS: on 2025-02-10

1XbqqNoRC')) OR 109=(SELECT 109 FROM PG_SLEEP(15))--

mGZaLUfS: on 2025-02-10

1*DBMS_PIPE.RECEIVE_MESSAGE(CHR(99)||CHR(99)||CHR(99),15)

mGZaLUfS: on 2025-02-10

1'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||'

mGZaLUfS: on 2025-02-10

1'"

mGZaLUfS: on 2025-02-10

1????%2527%2522'"

mGZaLUfS: on 2025-02-10

@@5v2qb

Add a comment:

*Required fields