Can't update from 17.10 to 18.04 because a repository doesn't have a Release file [duplicate]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite













This question already has an answer here:



  • How can I fix apt error “W: Target Packages … is configured multiple times”?

    3 answers



When I try to update from Ubuntu 17.10 to 18.04 I get the following error message:



E:The repository 'http://ppa.launchpad.net/jonathonf/backports/ubuntu artful Release' does not have a Release file.,
W:Updating from such a repository can't be done securely,
and is therefore disabled by default.,
W:See apt-secure(8) manpage for repository creation and user configuration details.,
W:Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
W:Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
W:Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
W:Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
W:Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
W:Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3


How do I continue upgrading?







share|improve this question














marked as duplicate by L. D. James, karel, N0rbert, Eliah Kagan, Eric Carvalho Apr 27 at 18:34


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.


















    up vote
    0
    down vote

    favorite













    This question already has an answer here:



    • How can I fix apt error “W: Target Packages … is configured multiple times”?

      3 answers



    When I try to update from Ubuntu 17.10 to 18.04 I get the following error message:



    E:The repository 'http://ppa.launchpad.net/jonathonf/backports/ubuntu artful Release' does not have a Release file.,
    W:Updating from such a repository can't be done securely,
    and is therefore disabled by default.,
    W:See apt-secure(8) manpage for repository creation and user configuration details.,
    W:Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
    W:Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
    W:Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
    W:Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
    W:Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
    W:Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3


    How do I continue upgrading?







    share|improve this question














    marked as duplicate by L. D. James, karel, N0rbert, Eliah Kagan, Eric Carvalho Apr 27 at 18:34


    This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite












      This question already has an answer here:



      • How can I fix apt error “W: Target Packages … is configured multiple times”?

        3 answers



      When I try to update from Ubuntu 17.10 to 18.04 I get the following error message:



      E:The repository 'http://ppa.launchpad.net/jonathonf/backports/ubuntu artful Release' does not have a Release file.,
      W:Updating from such a repository can't be done securely,
      and is therefore disabled by default.,
      W:See apt-secure(8) manpage for repository creation and user configuration details.,
      W:Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3


      How do I continue upgrading?







      share|improve this question















      This question already has an answer here:



      • How can I fix apt error “W: Target Packages … is configured multiple times”?

        3 answers



      When I try to update from Ubuntu 17.10 to 18.04 I get the following error message:



      E:The repository 'http://ppa.launchpad.net/jonathonf/backports/ubuntu artful Release' does not have a Release file.,
      W:Updating from such a repository can't be done securely,
      and is therefore disabled by default.,
      W:See apt-secure(8) manpage for repository creation and user configuration details.,
      W:Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3,
      W:Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:49 and /etc/apt/sources.list.d/vscode.list:3


      How do I continue upgrading?





      This question already has an answer here:



      • How can I fix apt error “W: Target Packages … is configured multiple times”?

        3 answers









      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 26 at 14:29









      Carl H

      3,08641632




      3,08641632










      asked Apr 26 at 14:26









      Jacob Shore

      33




      33




      marked as duplicate by L. D. James, karel, N0rbert, Eliah Kagan, Eric Carvalho Apr 27 at 18:34


      This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






      marked as duplicate by L. D. James, karel, N0rbert, Eliah Kagan, Eric Carvalho Apr 27 at 18:34


      This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          4
          down vote



          accepted










          The PPA found under http://ppa.launchpad.net/jonathonf/backports/ubuntu is no full Ubuntu repository but a PPA. In this case it does not contain any bionic packages (yet).



          You want to use an official repository or mirror which carries all of the packages you need for an upgrade.



          Take a look into your /etc/apt/sources.list. Are there the regular repositories linked?



          For Ubuntu 17.10 you should have something like



          deb http://de.archive.ubuntu.com/ubuntu/ artful main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
          ...


          and the corresponding deb-src entries.



          There might be more *.list files in /etc/apt/sources.list.d/ - there you might have to disable the PPA entry manually.



          Ho do you try to do the upgrade? The do-release-upgrade would take care of disabling the PPA entries automatically. As the time of writing this, the official release hasn't happen yet. Therefore a do-release-upgrade would not find the currtly beta status release right now. Either wait some time until they released 18.04 or use do-release-upgrade -d and go with the current status of 18.04.






          share|improve this answer
















          • 1




            Thanks! After reading your and checking my sources.list files like you say - and finding them in order- I noticed that in the "software and updates/other software" area of the updates-manger the ppa.launchpad... was checked. I unchecked it and that seemed to solve the problem.
            – Jacob Shore
            Apr 26 at 16:23


















          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          4
          down vote



          accepted










          The PPA found under http://ppa.launchpad.net/jonathonf/backports/ubuntu is no full Ubuntu repository but a PPA. In this case it does not contain any bionic packages (yet).



          You want to use an official repository or mirror which carries all of the packages you need for an upgrade.



          Take a look into your /etc/apt/sources.list. Are there the regular repositories linked?



          For Ubuntu 17.10 you should have something like



          deb http://de.archive.ubuntu.com/ubuntu/ artful main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
          ...


          and the corresponding deb-src entries.



          There might be more *.list files in /etc/apt/sources.list.d/ - there you might have to disable the PPA entry manually.



          Ho do you try to do the upgrade? The do-release-upgrade would take care of disabling the PPA entries automatically. As the time of writing this, the official release hasn't happen yet. Therefore a do-release-upgrade would not find the currtly beta status release right now. Either wait some time until they released 18.04 or use do-release-upgrade -d and go with the current status of 18.04.






          share|improve this answer
















          • 1




            Thanks! After reading your and checking my sources.list files like you say - and finding them in order- I noticed that in the "software and updates/other software" area of the updates-manger the ppa.launchpad... was checked. I unchecked it and that seemed to solve the problem.
            – Jacob Shore
            Apr 26 at 16:23















          up vote
          4
          down vote



          accepted










          The PPA found under http://ppa.launchpad.net/jonathonf/backports/ubuntu is no full Ubuntu repository but a PPA. In this case it does not contain any bionic packages (yet).



          You want to use an official repository or mirror which carries all of the packages you need for an upgrade.



          Take a look into your /etc/apt/sources.list. Are there the regular repositories linked?



          For Ubuntu 17.10 you should have something like



          deb http://de.archive.ubuntu.com/ubuntu/ artful main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
          ...


          and the corresponding deb-src entries.



          There might be more *.list files in /etc/apt/sources.list.d/ - there you might have to disable the PPA entry manually.



          Ho do you try to do the upgrade? The do-release-upgrade would take care of disabling the PPA entries automatically. As the time of writing this, the official release hasn't happen yet. Therefore a do-release-upgrade would not find the currtly beta status release right now. Either wait some time until they released 18.04 or use do-release-upgrade -d and go with the current status of 18.04.






          share|improve this answer
















          • 1




            Thanks! After reading your and checking my sources.list files like you say - and finding them in order- I noticed that in the "software and updates/other software" area of the updates-manger the ppa.launchpad... was checked. I unchecked it and that seemed to solve the problem.
            – Jacob Shore
            Apr 26 at 16:23













          up vote
          4
          down vote



          accepted







          up vote
          4
          down vote



          accepted






          The PPA found under http://ppa.launchpad.net/jonathonf/backports/ubuntu is no full Ubuntu repository but a PPA. In this case it does not contain any bionic packages (yet).



          You want to use an official repository or mirror which carries all of the packages you need for an upgrade.



          Take a look into your /etc/apt/sources.list. Are there the regular repositories linked?



          For Ubuntu 17.10 you should have something like



          deb http://de.archive.ubuntu.com/ubuntu/ artful main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
          ...


          and the corresponding deb-src entries.



          There might be more *.list files in /etc/apt/sources.list.d/ - there you might have to disable the PPA entry manually.



          Ho do you try to do the upgrade? The do-release-upgrade would take care of disabling the PPA entries automatically. As the time of writing this, the official release hasn't happen yet. Therefore a do-release-upgrade would not find the currtly beta status release right now. Either wait some time until they released 18.04 or use do-release-upgrade -d and go with the current status of 18.04.






          share|improve this answer












          The PPA found under http://ppa.launchpad.net/jonathonf/backports/ubuntu is no full Ubuntu repository but a PPA. In this case it does not contain any bionic packages (yet).



          You want to use an official repository or mirror which carries all of the packages you need for an upgrade.



          Take a look into your /etc/apt/sources.list. Are there the regular repositories linked?



          For Ubuntu 17.10 you should have something like



          deb http://de.archive.ubuntu.com/ubuntu/ artful main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates main restricted
          deb http://de.archive.ubuntu.com/ubuntu/ artful multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-updates multiverse
          deb http://de.archive.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
          ...


          and the corresponding deb-src entries.



          There might be more *.list files in /etc/apt/sources.list.d/ - there you might have to disable the PPA entry manually.



          Ho do you try to do the upgrade? The do-release-upgrade would take care of disabling the PPA entries automatically. As the time of writing this, the official release hasn't happen yet. Therefore a do-release-upgrade would not find the currtly beta status release right now. Either wait some time until they released 18.04 or use do-release-upgrade -d and go with the current status of 18.04.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 26 at 15:16









          pdr

          1434




          1434







          • 1




            Thanks! After reading your and checking my sources.list files like you say - and finding them in order- I noticed that in the "software and updates/other software" area of the updates-manger the ppa.launchpad... was checked. I unchecked it and that seemed to solve the problem.
            – Jacob Shore
            Apr 26 at 16:23













          • 1




            Thanks! After reading your and checking my sources.list files like you say - and finding them in order- I noticed that in the "software and updates/other software" area of the updates-manger the ppa.launchpad... was checked. I unchecked it and that seemed to solve the problem.
            – Jacob Shore
            Apr 26 at 16:23








          1




          1




          Thanks! After reading your and checking my sources.list files like you say - and finding them in order- I noticed that in the "software and updates/other software" area of the updates-manger the ppa.launchpad... was checked. I unchecked it and that seemed to solve the problem.
          – Jacob Shore
          Apr 26 at 16:23





          Thanks! After reading your and checking my sources.list files like you say - and finding them in order- I noticed that in the "software and updates/other software" area of the updates-manger the ppa.launchpad... was checked. I unchecked it and that seemed to solve the problem.
          – Jacob Shore
          Apr 26 at 16:23



          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491