03-22-2019, 06:19 AM
In your first post, that just meant that the repo hadn't completely synced and that you just had to wait, that's why that error isn't present in post #2.
In post #2, it's a connection issue. That package is there on the repo, I can see it. Make sure you have a stable connection eg. avoid WiFi if you can. An ethernet cable is always preferred.
In post #2, it's a connection issue. That package is there on the repo, I can see it. Make sure you have a stable connection eg. avoid WiFi if you can. An ethernet cable is always preferred.