steven@mydesktop:~$ sudo apt-get update
Ign:1 https://dl.bintray.com/resin-io/debian stable InRelease
Get:2 https://dl.bintray.com/resin-io/debian stable Release [1,878 B]
Hit:2 https://dl.bintray.com/resin-io/debian stable Release ...
Ign:97 http://us.archive.ubuntu.com/ubuntu zesty-backports/restricted amd64 Packages
Reading package lists... Done
W: The repository 'http://us.archive.ubuntu.com/ubuntu zesty Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu zesty-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu zesty-backports Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.ubuntu.com/ubuntu zesty-security 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.
steven@mydesktop:~$
That was an attempt to fix broken packages. Or was I supposed to 'sudo dpkg --configure -a' which is coming from a faded memory and is probably incorrect anyway? ...Does that command format the USB3 stick? and install K18.04? If so, as the kids would say, "Sweet".
Ign:1 https://dl.bintray.com/resin-io/debian stable InRelease
Get:2 https://dl.bintray.com/resin-io/debian stable Release [1,878 B]
Hit:2 https://dl.bintray.com/resin-io/debian stable Release ...
Ign:97 http://us.archive.ubuntu.com/ubuntu zesty-backports/restricted amd64 Packages
Reading package lists... Done
W: The repository 'http://us.archive.ubuntu.com/ubuntu zesty Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu zesty-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu zesty-backports Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.ubuntu.com/ubuntu zesty-security 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.
steven@mydesktop:~$
That was an attempt to fix broken packages. Or was I supposed to 'sudo dpkg --configure -a' which is coming from a faded memory and is probably incorrect anyway? ...Does that command format the USB3 stick? and install K18.04? If so, as the kids would say, "Sweet".
Originally posted by Shabakthanai
View Post
Comment