Ian Jackson <[email protected]> writes: > The DNS resolver library used by ssh *does* retry. See resolv.conf(5) > `attempts:'. But it defaults to 2 which seems far too little!
Oh, thank you. This may be a better solution to my problem than changes to dgit. I think I mostly filed this bug because I was surprised there was a possibility to fail past a point of no return in allocating the version number, although in retrospect it makes sense there would be such a point. In retrospect, I probably should just run a caching DNS server on my laptop so that I have more control over things like this. > This is not so easy; not all of the commands are idempotent (because of > the underlying protocols). Also dgit does some things itself with (eg) > a built-in http client. I will consider your suggestion but if I do > this it will probably be a long-term thing. Good point, that makes sense. Prompting is also kind of a pain. Maybe just the ssh commands, since they may be the most prone to failure? Although that's just an assumption; maybe the internal HTTP client could have just as easily had the same failure. > It might also be possible to try to do the generation of signed > artefacts in a single batch, and provide a way to retry the delivery of > the objects to remote places. That would also make it more convenient > to work around a dput failure. That sounds like an even better fix if it's possible. -- Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
