I've come into a problem, my build system refuses to build images.  I haven't been able to debug it, so I'm curious if anyone else in North America is having this trouble?  I have historically had odd name resolution bugs/etc that required some massaging of the scripts' use of URL's, but this seems impervious to my efforts. 

 

Reading package lists...
W: The repository 'http://apt.armbian.com stretch Release' does not have a Release file.
E: Failed to fetch http://apt.armbian.com/dists/stretch/stretch-desktop/binary-armhf/Packages  500  Connection failure: Network is unreachable [IP: ::1 3142]
E: Some index files failed to download. They have been ignored, or old ones used instead.
[ o.k. ] Upgrading base packages [ Armbian ]

 

Hi, I'm in Maine, (Spectrum ISP)  and could reach  http://apt.armbian.com/dists/stretch/stretch-desktop/binary-armhf/Packages  through  Chrome and also  built (I don't have on of these,  I was just doing this a a test...my current builds/patches are too messy)  BOARD=nanopct3 BRANCH=next RELEASE=stretch BUILD_DESKTOP=yes KERNEL_ONLY=no KERNEL_CONFIGURE=no  sucessfully with a Vagrant  on Virtualbox  build.      That sure is a weird looking IP number on the " Network is unreachable

message" ;-)    Could this be a glitch from your ISP,  or has it been happen consistently over hours or days?   You'd think more poeple would run into it if it were on the apt.armbian.com end of things..

1 hour ago, belfastraven said:

Could this be a glitch from your ISP

 

I am certain it is, however there are quite a few machines between mine and the server, so I'm not sure how far it goes.  I had to massage the key server url's at one point because they would fail for me unless I very specifically named them.  It's been consistent for a few weeks, I've built a few kernels for cleaning, but images are a no-go.  I'm pulling up my secondary machine to determine if it's my install for some reason, I can reach the server via browser and ping.

What if you try bypassing apt cacher?

I just tried a build on my laptop and it's fine (it was buried), so now to figure out what happened to my main machine...

OK, something was wrong with ubuntu, I apt update/upgraded today and it's fine.  my laptop likewise has updated today, so it may have not seen the issue

Upstream bugs I suppose. I saw some other, possible related, problem the other day: https://askubuntu.com/questions/1049411/release-file-is-not-valid-yet-and-other-errors-when-running-apt-get-update

 

After second apt update, the problem was gone ...