Nachdem diese Hürde genommen werden konnte, indem folgede Kommandos ausgeführt wurden:
[code]export ftp_proxy=http://localhost:3128
export http_proxy=http://localhost:3128
export https_proxy=http://localhost:3128
export proxy_enable=yes
ucr set repository/online/server=apt.univention.de
ucr set update23/ignoressh=yes
ucr set update23/ignoreterm=yes[/code]
Passiert nach univention-updater net:
# univention-updater net
Update to = 2.3-0
Space on /var/cache/apt/archives: OK
Space on /boot: OK
Space on /: OK
Checking for the package status
Starting preupdate of univention-ssl...done.
Starting update process, this may take a while.
Check /var/log/univention/updater.log for more information.
Failed to execute apt-get update
In /var/log/univention/updater.log findet sich:
Hit http://apt.univention.de sec4/i386/ Packages
Failed to fetch http://apt.univention.de/2.3/maintained/2.3-0/i386/Release.gpg Error reading from server. Remote end closed connection
Failed to fetch http://apt.univention.de/2.0/maintained/2.0-0/all/Release.gpg Error reading from server. Remote end closed connection
Failed to fetch http://apt.univention.de/2.0/maintained/2.0-2/i386/Release.gpg Error reading from server. Remote end closed connection
Failed to fetch http://apt.univention.de/2.1/maintained/2.1-2/all/Release.gpg Error reading from server. Remote end closed connection
Reading package lists...
E: Some index files failed to download, they have been ignored, or old ones used instead.
Failed to execute apt-get update
Das Update findet nicht statt. Via wget ist Release.gpg problemlos zu bekommen. Nur die univention-updater-Routinen scheitern. Wie kann ich dem Updater beibringen, dass er die anderweitig heruntergeladenen Release.gpg-Dateien verwenden soll oder gleich wget einsetzen möchte?