Ubuntu

After update from 16.04 to 16.10 software sources are being ignored at update/upgrade

Asked by Ronald

I upgraded from16.04 to 16.10. when I now run update-manager all software sources are ignored.

~$ sudo apt-get update

Hit:1 http://security.ubuntu.com/ubuntu yakkety-security InRelease
Hit:2 http://archive.canonical.com/ubuntu yakkety InRelease
Ign:3 http://cr.archive.ubuntu.com/ubuntu yakkety InRelease
Ign:4 http://cr.archive.ubuntu.com/ubuntu yakkety-updates InRelease
Ign:5 http://cr.archive.ubuntu.com/ubuntu yakkety-backports InRelease
Err:6 http://cr.archive.ubuntu.com/ubuntu yakkety Release
  403 Forbidden
Err:7 http://cr.archive.ubuntu.com/ubuntu yakkety-updates Release
  403 Forbidden
Err:8 http://cr.archive.ubuntu.com/ubuntu yakkety-backports Release
  403 Forbidden
Reading package lists... Done
E: The repository 'http://cr.archive.ubuntu.com/ubuntu yakkety 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://cr.archive.ubuntu.com/ubuntu yakkety-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://cr.archive.ubuntu.com/ubuntu yakkety-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.

How can I fix this? Also

cr404@cr404-MS-7817:~$ uname -a
Linux cr404-MS-7817 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
cr404@cr404-MS-7817:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 16.10
Release: 16.10
Codename: yakkety
cr404@cr404-MS-7817:~$ cat -n /etc/apt/sources.list
     1 # deb cdrom:[Ubuntu 15.10 _Wily Werewolf_ - Release amd64 (20151021)]/ wily main restricted
     2
     3 # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
     4 # newer versions of the distribution.
     5 deb http://cr.archive.ubuntu.com/ubuntu/ yakkety main restricted multiverse
     6 deb-src http://cr.archive.ubuntu.com/ubuntu/ yakkety main multiverse restricted universe #Added by software-properties
     7
     8 ## Major bug fix updates produced after the final release of the
     9 ## distribution.
    10 deb http://cr.archive.ubuntu.com/ubuntu/ yakkety-updates main restricted multiverse
    11 deb-src http://cr.archive.ubuntu.com/ubuntu/ yakkety-updates main multiverse restricted universe #Added by software-properties
    12
    13 ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
    14 ## team. Also, please note that software in universe WILL NOT receive any
    15 ## review or updates from the Ubuntu security team.
    16 deb http://cr.archive.ubuntu.com/ubuntu/ yakkety universe
    17 deb http://cr.archive.ubuntu.com/ubuntu/ yakkety-updates universe
    18
    19 ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
    20 ## team, and may not be under a free licence. Please satisfy yourself as to
    21 ## your rights to use the software. Also, please note that software in
    22 ## multiverse WILL NOT receive any review or updates from the Ubuntu
    23 ## security team.
    24
    25 ## N.B. software from this repository may not have been tested as
    26 ## extensively as that contained in the main release, although it includes
    27 ## newer versions of some applications which may provide useful features.
    28 ## Also, please note that software in backports WILL NOT receive any review
    29 ## or updates from the Ubuntu security team.
    30 deb http://cr.archive.ubuntu.com/ubuntu/ yakkety-backports main universe restricted multiverse
    31 deb-src http://cr.archive.ubuntu.com/ubuntu/ yakkety-backports main universe restricted multiverse #Added by software-properties
    32
    33 deb http://security.ubuntu.com/ubuntu yakkety-security main restricted multiverse
    34 deb-src http://security.ubuntu.com/ubuntu yakkety-security main multiverse restricted universe #Added by software-properties
    35 deb http://security.ubuntu.com/ubuntu yakkety-security universe
    36
    37 ## Uncomment the following two lines to add software from Canonical's
    38 ## 'partner' repository.
    39 ## This software is not part of Ubuntu, but is offered by Canonical and the
    40 ## respective vendors as a service to Ubuntu users.
    41 deb http://archive.canonical.com/ubuntu yakkety partner
    42 deb-src http://archive.canonical.com/ubuntu yakkety partner
    43 # deb http://cran.rstudio.com/bin/linux/ubuntu trusty/ # disabled on upgrade to xenial
    44 # deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main # disabled on upgrade to xenial

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said : 		#1

This seems to be a problem with the repository server that you use, I suggest that you try switching to another server.

Remark: I get the same error messages when I try accessing http://cr.archive.ubuntu.com/ubuntu/ or http://ubuntu.ucr.ac.cr/ubuntu/ with a web browser.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#2

Try switching from the cr server to the main server. You can do this in software centre or you can simply remove "cr." from the lines it appears on.

Once editted, save the new file and run:

sudo apt-get update

Is it smoother?

Revision history for this message
Ronald (cr404) said : 		#3

This afternoon I tried to update again with the same server and I able to, I changed to the main server and it went smoothly. I would try again tomorrow again with the .cr to see if it was a problem with the server.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#4

It seems that this was a temporary problem with the ucr.ac.cr server. Accessing the repository with a web browser works again.

Can you help with this problem?

Provide an answer of your own, or ask Ronald for more information if necessary.

To post a message you must log in.