Nazar Gerasymchuk Posted January 10, 2019 Posted January 10, 2019 Good day, What is the best and easiest way to deal with situation: The following packages have unmet dependencies: armbian-config : Depends: debconf-utils but it is not going to be installed Depends: html2text but it is not going to be installed Depends: html2text but it is not going to be installed mc : Depends: mc-data (= 3:4.8.18-1) but it is not going to be installed nfs-kernel-server : Depends: libtirpc1 (>= 0.2.4) but it is not going to be installed Depends: nfs-common (= 1:1.3.4-2.1) but it is not going to be installed Depends: keyutils but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). Ign:1 http://httpredir.debian.org/debian stretch InRelease Ign:2 http://security.debian.org stretch/updates InRelease Ign:3 http://apt.armbian.com stretch InRelease Ign:4 http://httpredir.debian.org/debian stretch-updates InRelease Err:5 http://security.debian.org stretch/updates Release 500 Internal Server Error Ign:6 http://httpredir.debian.org/debian stretch-backports InRelease Err:7 http://apt.armbian.com stretch Release 500 Internal Server Error Err:8 http://httpredir.debian.org/debian stretch Release 500 Internal Server Error Err:9 http://httpredir.debian.org/debian stretch-updates Release 500 Internal Server Error Err:10 http://httpredir.debian.org/debian stretch-backports Release 500 Internal Server Error Reading package lists... Done E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://apt.armbian.com stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. When trying to build Armbian?
Igor Posted January 10, 2019 Posted January 10, 2019 1 hour ago, Nazar Gerasymchuk said: Err:5 http://security.debian.org stretch/updates Release 500 Internal Server Error Unrelated to Armbian.
Nazar Gerasymchuk Posted January 10, 2019 Author Posted January 10, 2019 Just now, Igor said: Unrelated to Armbian. Is there any way to configure alternative sources and/or timeout options and/or any general recommendations?
Igor Posted January 10, 2019 Posted January 10, 2019 5 minutes ago, Nazar Gerasymchuk said: Is there any way to configure alternative sources and/or timeout options and/or any general recommendations? This looks like some network related problems which are outside our power to fix and it looks like rootfs creation was not done properly. Start with a clean build. If you have been changing things in the script, you have to understand what you are doing ... Edit: I don't know if we have this configurable. Check manual and then inside the script / deboostrap.
Nazar Gerasymchuk Posted January 10, 2019 Author Posted January 10, 2019 1 minute ago, Igor said: This looks like some network related problems which are outside our power to fix and it looks like rootfs creation was not done properly. Start with a clean build. If you have been changing things in the script, you have to understand what you are doing ... Ok, got it. Thanks for quick response!
Recommended Posts