Any workaround if I cannot ping/reach raw.githubusercontent.com?

[Cobell73]

I was so excited to learn about JuNest.

I installed without issue using wget:
wget https://github.com/fsquillace/junest/archive/refs/heads/master.zip

But I have not been able to update packages with pacman. The problem appears to be my network is blocking access to raw.githubusercontent.com (the hostname is resolving, I just can't ping to it from where I want to run JuNest.)

Pacman updates core, extra, and community just fine. Is there a way to disable check of junest.db so can proceed? Or better yet, update junest.db via an offline or local file method (I should be able to retrieve external to this machine and move a necessary file over to this server without issue....if I could point to a local file instead)

I'm somewhat "linux competent" and can generally get around, but I'm new to Arch and pacman specifically.

[Cobell73]

ha, well the first thing I can do is comment out [junest] section of the .junest/etc/pacman.conf
This at least allows pacman to successfully update core, extra, and community.

[Cobell73]

So I'm proceeding merrily without the [junest] repo and have succeeded with my shorterm goal of JuNest (install VSCode on a work machine where I have no sudo).

But I don't fully understand the impact or how to work around this long term. I can retrieve junest.db via another method and transfer it the .junest/var/lib/pacman/sync, but I'm pretty sure that's not sufficient. What I really need are the packages defined by junest.db and I'm not sure how to figure out what those are or how to manually get/put them where they need to go (likely in .junest/var/lib/pacman/local)

Again, this is all because I can't reach the junest repo.

Any help?

[fsquillace]

The packages in junest repo do not get update that often and they are already included in the junest image, so there is not much to worry if you can access to the repo. If you can't get access to githubusercontent.com I'd guess there is not much we can do. As you mentioned, disabling the repo in .junest/etc/pacman.conf should make the trick.