Announcement

Collapse
No announcement yet.

Unable to upgrade 21.10 - Repository...

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Unable to upgrade 21.10 - Repository...

    E: The Repository'http://us.archive.ubuntu.com/ubuntu hirsute Realease' no longer has a Release file.
    W: Updating from such a repository can't be don't securely, and is therefore disabled by default.
    W: See apt-secure(8) manpage for repositry creation and user configuration details.
    E:The repository 'http://us.archive.ubuntu.com/ubuntu hirsute-updates Realease' no longer has a release file...

    Has 21.1 reached EOL? It wouldn't allow me to updrade to LTS this summer...
    Attached Files

    #2
    non-LTS releases of Ubuntu have a 9-month shelf life, with upgrades every 6. 21.10 reached EOL in July
    All is not list, however
    The repos have just been archived, so you can still upgrade to 22.04.
    https://help.ubuntu.com/community/EOLUpgrades

    Comment


      #3
      Status Update: I have updated the software sources as noted in the article link above. Howver, I have a question about the syntax of the text I entered and an error I encountered upon refresh of the cache. THis tells me something is wrong and I suspect it has to do with the CODENAME I entered... If you go to the top on couldnotrefreshcache.png on the box on the right there is a reference to hirsute and not hirsutehippo as I have noted. Is this my problem? I have included pngs of software sources so you are able to see my entries. I believe these need to be edited, but I am not sure.
      Attached Files

      Comment


        #4
        My system is 21.04

        Comment


          #5
          it should just be 'hirsute', just as it was before.

          The only change in the url is editing <country-code>.archive.ubuntu.com to old-releases.ubuntu.com. Everything else is identical.

          It is much clearer and easier editing /etc/apt/sources.list with Kate or Kwrite. It will be obvious if anything was missed.
          You ignore PPAs and other external repos, those will be disabled for the upgrade process anyway.

          Comment


            #6
            Now I'm having issues with aptitude. stefanso@stefanso-GL753VD:~$ sudo aptitude install update-manager-core update-manager
            [sudo] password for stefanso:
            sudo: aptitude: command not found
            stefanso@stefanso-GL753VD:~$ apt:update-manager-core,update-manager
            apt:update-manager-core,update-manager: command not found
            stefanso@stefanso-GL753VD:~$ sudo aptitude install update-manager-core update-manager
            sudo: aptitude: command not found
            stefanso@stefanso-GL753VD:~$ ^C
            stefanso@stefanso-GL753VD:~$ sudo apt:update-manager-core,update-manager
            sudo: apt:update-manager-core,update-manager: command not found
            stefanso@stefanso-GL753VD:~$ ^C
            stefanso@stefanso-GL753VD:~$ sudo apt update-manager-core,update-manager
            E: Invalid operation update-manager-core,update-manager
            stefanso@stefanso-GL753VD:~$ sudo aptitude install kubuntu-desktop
            sudo: aptitude: command not found
            stefanso@stefanso-GL753VD:~$


            Comment


              #7
              Installed aptitude via muon pkg mgr

              Comment


                #8
                Under 'Run the Upgrade' I got some errors. UPloading png's for DEETS...
                Do I continue the upgrade? I don't feel adventurous. I do have a copy of this drive as BU
                Attached Files

                Comment


                  #9
                  Ignore all the extra steps on that page, I probably should have advised that. Many apologies The EOL page is a long running one that has both current and outdated info for older releases, as well as server installs. I keep forgetting that.

                  But all we need to do is edit the sources, then update and start the upgrade process normally.

                  Your changes made in the Software Sources may not be saving until you close the GUI tool, they are not being reflected in your terminal output.

                  Open the file /etc/apt/sources.list in Kate or Kwrite.
                  Edit all instances of us.archive to old-releases, and save. You will be prompted for your password.
                  Then follow the instructions to upgrade from Hirsute to Jammy:
                  https://kubuntu.org/news/kubuntu-22-04-lts-released/
                  https://help.ubuntu.com/community/JammyUpgrades/Kubuntu

                  Hit alt-space to open krunner, and paste the command to manually start the upgrade tool:

                  pkexec do-release-upgrade -m desktop -f DistUpgradeViewKDE

                  Comment


                    #10
                    Well I did what you posted in the above. See the attached for screenshot. IDK?
                    Attached Files

                    Comment


                      #11
                      Please copy and paste text, it is easier for us to copy relevant text ourselves than trying to read an image (on a borrowed 13 inch laptop in my case at the moment, was on my phone earlier lol)

                      Edit the sources.list file with the offending url with the 404 error - security.Ubuntu.com to also be old-releases.ubuntu.com

                      You need a line that has:
                      deb http://old-releases.ubuntu.com/ubuntu/ hirsute-security main restricted universe multiverse to get that last pesky package

                      Comment


                        #12
                        I've edited as instructed. See pngs. I've also ran items as instructed in TERM and included that. Still stuck. I must be FUBAR'd The way I see it, (I'm pro'bly wrong) is that pesky N-Vidia-460-Generic file. I need to find an update for this file to do system upgrade: linux-modules-nvidia-460-generic
                        ​to 'linux-modules-nvidia-460-generic-5.11.0-49.55'.
                        Attached Files
                        Last edited by spiderman; Oct 16, 2022, 11:44 AM.

                        Comment


                          #13
                          TYVM for all the help! I had to rewrite the drive do to a personal FUBAR ... on the upgrade. I hit d to see the packages it was going to delete and couldn't get back to the screen for the upgrade. Lost all network connections. Used Clonezilla to restore a B/U image and the ran upgrade again. What a cluster. I WILL BE WATCHING THE UPGRADE NOTICES AND STICKING TO LTS > > > PERIOD

                          Comment

                          Working...
                          X