Question

I can't apt update github repo doesn't have a "Release file"

Posted December 2, 2020 1.2k views
Ubuntu

I was trying to update with apt-get update and I got this result:

E: The repository 'http://ppa.launchpad.net/certbot/certbot/ubuntu focal Release' does not 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 'https://github.com/myacount/myrepo.git focal Release' does not 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 update my existing release? Thank you!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
3 answers

Hi @AlenosEMPEROR,

The important part of this error message is “focal release”.

You probably already know that each Ubuntu release has a codename. For Ubuntu 20.04, the codename is Focal Fossa. The “focal” in the error message indicates Focal Fossa which is Ubuntu 20.04.

The error is basically telling you that though you have added a third-party repository to your system’s sources list, this new repository is not available for your current Ubuntu version.

This most probably means you are using a new version of Ubuntu and the developer has not made the software available for this new version.

I take it, you’ve added the repository manually in your sources file, is that correct? If so, how exactly did you add it there, what Line did you add?

Regards,
KFSys

Thank you for your quick answer @KFSys ,
I am pretty new to digital ocean and ubnutu, so I watched a tutorial on deploying my web app (https://www.youtube.com/watch?v=oykl1Ih9pMg&t=522s).

Regarding the source files, I added them via the command line. git clone myrepourl

Again, thank you for your submission.
Regards,
AlenosEMPEROR

  • Wait, I’m not sure I fully understand. So you are trying to deploy your App on your Droplet. Having said that, you are not able to do a push request to your git repo, is that correct?

    • Yes, that is right. I was able to preform it first time.

      • Hello,

        The above error should be seen when you do apt-update. What if you do

        git push origin master
        

        What do you see as an error?

        • After I do apt update it is the same. And after the git push origin master I get:

           ! [rejected]        master -> master (fetch first)
          error: failed to push some refs to 'https://github.com/alenosEMPEROR-program/TeenChat.git'
          hint: Updates were rejected because the remote contains work that you do
          hint: not have locally. This is usually caused by another repository pushing
          hint: to the same ref. You may want to first integrate the remote changes
          hint: (e.g., 'git pull ...') before pushing again.
          hint: See the 'Note about fast-forwards' in 'git push --help' for details.
          

          This confuses me lol.
          By the way, I tried to pull and then do the push but it again logs this error.
          Thank you.

Hi @AlenosEMPEROR,

I’m starting this in a new answer thread for better visibility

If the GitHub repo has seen new commits pushed to it, while you were working locally, I would advise using:

git pull --rebase
git push

The full syntax is:

git pull --rebase origin main
git push origin main

With Git 2.6+ (Sept. 2015), after having done (once)

git config --global pull.rebase true
git config --global rebase.autoStash true

A simple git pull would be enough.

(Note: with Git 2.27 Q2 2020, a merge.autostash is also available for your regular pull, without rebase)

That way, you would replay (the –rebase part) your local commits on top of the newly updated origin/main (or origin/yourBranch: git pull origin yourBranch).

I would recommend a:

# add and commit first
git push -u origin main

That would establish a tracking relationship between your local main branch and its upstream branch.
After that, any future push for that branch can be done with a simple:

git push

Another solution would be to try and use a branch and then merge it from the git ui.

  • Thank you, it helped with the repo. I would have never think of this. For some reason problem is still there. Would setting up the whole droplet again help because I think I messed something up in the process?

    • Glad to be of help!

      Let’s see if I got it straight so now you can push and pull from the repo but when you do an apt upgrade, you still see the previous errors, is that correct?

      Regarding recreating your droplet, it’s always a possibility but it’s better to find out what the source of the problem is if it occurs again.