4.1 auf 4.2 upgrade

Hallo,

ich würde es so machen:

mit apt-mirror kann man sich eine Kopie vom Repository erstellen.

Anschließend kann man die apt-Quellen auf die Lokalen Verzeichnisse verweisen lassen.

Danach sollte es keine Probleme mit einem Upgrade mehr geben.

Rein theoretisch sollte es so funktionieren.
 
Das ist in apt-get ohnehin eingebaut:

Code: 
$ man apt-get

...
       -d, --download-only
           Download only; package files are only retrieved, not unpacked or installed.
...

Code: 
# apt-get update
....
# apt-get -d dist-upgrade
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libmysqlclient18 mysql-common
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 756 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://security.debian.org/ jessie/updates/main mysql-common all 5.5.50-0+deb8u1 [81.8 kB]
Get:2 http://security.debian.org/ jessie/updates/main libmysqlclient18 amd64 5.5.50-0+deb8u1 [675 kB]
Fetched 756 kB in 0s (2,751 kB/s)        
Download complete and in download only mode

Jetzt sind alle Updates lokal gecached, die VMs/Container können abgedreht werden und die Updates ohne Internet (und ohne nochmaliges "apt-get update") installiert werden:

Code: 
# apt-get dist-upgrade 
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libmysqlclient18 mysql-common
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/756 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n]
 
  • Like
Reactions: iMer
You must log in or register to reply here.
Top Bottom