| 12 Feb 2025 |
Atemu | Unless you have a full mirror, waiting for google to like you again and then not doing it quite as hard is your best bet | 22:32:46 |
Atemu | An exponential backoff retry mechanism would be great but I wouldn't put too much effort into the updaters, given that a replacement is in the works | 22:34:05 |
Atemu | * | 22:34:20 |
waltmck | Have you been blacklisted by google's servers before? how long did you have to wait? | 22:35:10 |
Atemu | Yes and only a few hours I think | 22:35:32 |
waltmck | I tried after 8 hours again with 1 thread and it still didn't work | 22:35:46 |
Atemu | You should be good to try right about now | 22:35:46 |
Atemu | Hm | 22:35:55 |
waltmck | sure, I'll try again now. It's been about 4-5 hours since my last try | 22:36:01 |
Atemu | Well as I said, your guess is as good as mine | 22:36:15 |
Atemu | There's a reason I use the local mirror... | 22:36:34 |
Atemu | What are you attempting to do btw.? | 22:36:52 |
waltmck | I just want to try to add lynx as a supported platform so I can test this on my phone | 22:37:17 |
Atemu | You don't need any repo updates then, especially not from Google | 22:37:47 |
Atemu | Skip the repo update and only do your device | 22:38:04 |
waltmck | how you told me to do it was to add my device to supported_devices and run the update script | 22:38:24 |
waltmck | there's a better way? | 22:38:28 |
Atemu | Someone added a handy CLI flag for that very recently | 22:38:31 |
Atemu | Only the device dir updater | 22:38:48 |
Atemu | You could update repo too but you don't have to | 22:39:12 |
waltmck | so I just run update_device_dirs.py instead of update.sh? | 22:39:31 |
Atemu | Yes but the -s flag is easier | 22:39:51 |