Right, I would update every so often but just to build something, I don't need to download everything all the time.
I'm not sure what you mean by downloading to the computer. Do I just put the downloaded packages somewhere in the build tree and that prevents them from being downloaded again?
If you’re still using the image builder, you’d have to check to see if there’s a way to disable fetching of the current package lists. Otherwise, even if there is a local copy for an updated package, it will fetch the new one.
Since most builds are only 4-10 MB, none of this seems to be worth significant effort.
Well, this is day two of not being able to build now. Same thing is still happening. I've never seen this problem before in this way. Downloads would fail now and then but usually, re-trying a while later and things worked.
There must be something that is not working the same with the repo I would think.
Might want to consider compiling an image if that is an option.
I'm also working on that but it is overkill for some of the things I need. Image generator is perfect for making small changes or testing something. I have not fully understood the other environment yet, still working on that :).
The question remains however, why is this happening only to the ramips version that I am trying to build? I tried building at71xx and it completes no problem. Since openwrt is doing a daily snapshot, doesn't this mean that the repo will end up broken most every day for most of the day as it has been doing since I at least started posting about it.
You may consider it “overkill” but the repeated suggestions from experienced members of the community should be considered. You’d be done by now if you heeded that advice.
Jeff, please, give me some credit. I have been taking everything I am being offered and trying to learn. I have not once discarded anything that was suggested to me but I have limited technical skills and don't do this full time. I am trying as hard as I can with the time that I have and have been absorbing all I am offered which I appreciate.
Right now, I just want to build using image generator, it's the fastest way for me to get what I want but the repo keeps being down or broken. It's not me that needs to add more hours into this, it's the repo that needs to be more reliable I think.
Out of curiosity, someone mentioned to wait a while since packages can take a long time to build but this is again going on two days now. If the repo will never be ready in under a day, how will it ever be available for us since the snapshot is a daily one?
I think what you are currently seeing is some breakage, combined with the buildbots being busy as some new stable revisions are occurring; check the logs. Just to clarify, the snapshots are not generated by the clock, but by data(i.e. commits, so there can be >= 0 in any one day for any given target).
Ok, so it's possible that sometimes, builds will not complete for a day or two?
I just want to understand so I'm not trying to report problems that don't exist.
I also would love to just download everything one time for the different builds that I use so as not to use the repo bandwidth over and over again. No idea if it is but maybe this is something which could be added as an option when using 'make -option image'.
Third day now. The interesting part is this is only happening to the one build I am trying which is ramips-mt76x8. Just FYI since ARxxxx are building file.
Is there some way to help? I have friends that have lots of computing resources and maybe even bandwidth to share.
It's working!
Can anyone answer my question about possibly keeping the downloads, some way to prevent those from being required to be downloaded?
I know about using /files for example but I've not yet found any information on where I could put packages to prevent them from being downloaded when I don't need/want them to be.
I got lost reading this. Is this still an Unbound issue? Or was it a buildbot issue? There was just discovered a cross thread between OpenWrt core source and packages. It should be resolved now.
Not buildbot issue. OP wanted "local" downloaded, customized software in the image; and/or to just save all needed packages locally between resetting to default configs (thus erasing those packages).
Actually, that was not my original post. My original question was where did unbound go since all I could find was unbound.daemon. Two days later, unbound showed up again and this happened more than once as you can see in the thread.
The idea of local downloads was very much later in the thread where I asked if there was a way to save files since much of the time that I tried building using ramips, the repo was not responding and was missing packages.
OK...I just consider it all one thread, cool beans in any case. It wasn't a build [server] issue.
Hi,
did you ever find a solution for your problem?
I am facing the same problem with 19.07.0 final now. The same config worked on 18.06.5 for a very long time and also reverting the whole unbound config back to default doesnt stop the crash loop.
A raise of the verbosity level shows no other log messages.
Thanks and best regards
Robert
@imk82 its seems this may be a new issue piling on top of an old thread. please follow up here Missing Unbound package on OpenWrt 19.07 because it may be a make dependency between the two variants of Unbound and libunbound.
You are fully right. I will switch to the other thread.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.