Release upgrade an unsupported version of ubuntu

Last Updated: 2025-01-02

If you want to do a release upgrade with an unsupported version of ubuntu, it seems to be quite straight forward, but nonetheless, you run into a couple of difficulties, because the sources are moved from archive.ubuntu.com to old-releases.ubuntu.com which results in not finding these if you want to do a release-upgrade.

What did the trick for me was to manually set the IP-Adress of the server old-releases.ubuntu.com in the /etc/hosts file for archive.ubuntu.com and security.ubuntu.com.

All other suggestions like changing the url in the /etc/apt/sources.list and modifying the /etc/update-manager/meta-release file didn't work, because i.e. of wrong checksums and in the end it always tried to contact archive.ubuntu.com for an updated version of the packages.

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+354-354-1=0+0+0+1: on 2025-02-10

1
1

mGZaLUfS'": on 2025-02-10

1
1

@@krdWL: 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+712-712-1=0+0+0+1 --

mGZaLUfS: on 2025-02-10

-1 OR 2+227-227-1=0+0+0+1

mGZaLUfS: on 2025-02-10

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

mGZaLUfS: on 2025-02-10

-1' OR 2+738-738-1=0+0+0+1 or 'rRC8ycWD'='

mGZaLUfS: on 2025-02-10

-1" OR 2+911-911-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

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

mGZaLUfS: on 2025-02-10

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

mGZaLUfS: on 2025-02-10

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

mGZaLUfS: on 2025-02-10

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

mGZaLUfS: on 2025-02-10

1eU3R5CoA' OR 510=(SELECT 510 FROM PG_SLEEP(15))--

mGZaLUfS: on 2025-02-10

1VaEllcOI') OR 603=(SELECT 603 FROM PG_SLEEP(15))--

mGZaLUfS: on 2025-02-10

146hCRa7y')) OR 282=(SELECT 282 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

@@67tby

Add a comment:

*Required fields