Vitalij Dovhanyc
Vitalij Dovhanyc
There is an arm window version but it has such a small user base that I would not worry about it for now.
> One downside of publishing to stores is that it makes it difficult or impossible to rollback faulty release. It's not possible to roll back a release, we need to...
We are building many packages on our server and never experienced any issue with connection timing out or container not having internet access. Have you tried on a different system?
I just tried to build deb packages on four different systems, and none of them had an issue.
I have been using for something like this a setup with committing `.git-hooks` folder to git. Create a make file that creates a symlink for pre-commit, and in that pre-commit...
That is indeed strange. I do not observe such behavior on my end. Can you try to run the build using debian11 as the base image with `make all-bitcoin BASE_IMAGE=debian:11`?
Can you please try the build from this branch `vd/fix-build`, I added ca-certificates as it looks like base Debian image is missing the root certificate for the one dl.google.com uses.
well i don't know, can you try different host? do you run any proxy on your host machine? this could also be some issue with docker networking, do you have...
This happens, whenever the window is visible but not active, happens to me too. No idea to what could be the culprit.
I think files should be deleted in the rollback bucket.