I dragged out an unused Mint 19 laptop to dedicate to building OpenWrt images from Snapshot, and set to following Quick Image Building Guide.
All went well until I got to the Update and install feeds process - ./scripts/feeds update -a
When it got to Updating feed 'luci', it errors out with failed: Error in the pull function.
Same for feed 'routing', feed 'telephony' is OK, feed 'freifunk' seems OK, but then in Collecting package info: feeds/freifunk it all goes bad from there.
Checking the dump.txt logs as directed, they all seem to refer back to the original error with same content in each dump.txt file:
cat dump.txt
../../freifunk.mk:12: *** did not find luci.mk in any feed. Stop.
Can anyone please shed some light on what I might be missing?
Seems strange that Cloning into './feeds/packages'..., Cloning into './feeds/telephony'..., and Cloning into './feeds/freifunk'... were successful, but Cloning into './feeds/luci'... and Cloning into './feeds/routing'...
both returned: fatal: unable to access 'https://git.openwrt.org/project/luci.git/': gnutls_handshake() failed: Error in the pull function.
Your browser has no role in the download.
As you ssee from the error message, the "GnuTLS" library is used for the download byu the download tool.
No idea what is wrong, but likely something related to your environment (cache, antivirus, whatever), as there been no general error flood about downloads.
Yea. I felt more than a little dense when I thought about it.
FWIW, I have a suspicion it may have had something to do with my VPN and/or PBR. I can't be definitive of that, but with two contrasting fails and success only when VPN and VPN-PBR are taken out of the equation, well . . . I dunno.
rm -r openwrt
and started over - Updating feed 'luci' was sucessful this time, but conversely, Updating feed 'telephony' failed this time around. Hmmm - contrasting outcome.
Grasping at straws, I stopped PBR and took down the VPN and repeated the process. Voila! Success.
Likely your software caused the SSL handshake to fail due a "man-in-the-middle" attack suspicion, or something like that. Having any middlemen in HTTPS traffic is a no-go for secure libraries.