| 23 Jul 2020 |
 wb9688 | Meh, I don't want to spend time debugging this when I don't see obvious differences, while just disabling shrinkResources works even though I don't really like that. | 14:16:20 |
 _hc | that works :) | 15:04:54 |
| _hc | reproducible builds can suck down amazing amounts of time | 15:05:06 |
| _hc | luckily, its gotten a lot better recently | 15:05:15 |
| _hc | people have developed all sorts of hacks 🪓 | 15:05:42 |
| _hc | Bubu: if you don't mind could you toot out about the API merge request, it would be great to have feedback from potential consumers. Something like:
@kitsunyan has put together a simple JSON API for f-droid.org data, what kinds of data do you want in an API? https://gitlab.com/fdroid/fdroid-website/-/merge_requests/568
| 15:07:31 |
| _hc | I hope you don't mind kitsunyan , it just seems that with a little extra effort, we can make the API widely applicable | 15:08:20 |
 kitsunyan |
Meh, I don't want to spend time debugging this when I don't see obvious differences, while just disabling shrinkResources works even though I don't really like that.
Don't worry about that. In fact, resource shrinker will work if there is something to shrink. This is not your case.
| 15:17:41 |
| kitsunyan | In your case about 80 files are shrinked, and they all are small XML files. You save no more than 20 kB. | 15:25:02 |
| kitsunyan | _hc: should I use force pushes to squash my commits in MR? | 15:26:46 |
| kitsunyan | Or just add more commits? | 15:26:51 |
| _hc | force pushing is OK. the commits should be organized on topic, ideally. For that MR, a single commit is probably fine | 15:27:47 |
 Bubu | In reply to @eighthave:matrix.org
Bubu: if you don't mind could you toot out about the API merge request, it would be great to have feedback from potential consumers. Something like:
@kitsunyan has put together a simple JSON API for f-droid.org data, what kinds of data do you want in an API? https://gitlab.com/fdroid/fdroid-website/-/merge_requests/568
I currently don't have any context on this. | 15:31:25 |
| kitsunyan |
force pushing is OK. the commits should be organized on topic, ideally. For that MR, a single commit is probably fine
Yes, I just thought thought that API and webserver configuration could be different topics. I'll squash them too.
| 15:32:12 |
| _hc | they could be separate topics | 15:37:13 |
| _hc | Bubu: kitsunyan is putting together an f-droid.org API so that shields.io works with current info | 15:38:33 |
|  marzzzello left the room. | 18:19:40 |
| marzzzello joined the room. | 18:19:51 |
| 24 Jul 2020 |
| wb9688 | Bubu: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/7144 should work. In the future we'll always build without shrinkResources. | 07:12:42 |
 cdesai | 1.10-alpha0 is already built, that was fast | 15:13:10 |
| cdesai | :D | 15:13:12 |
| _hc | yeah, when things are working, its pretty smooth | 15:18:50 |
| _hc | FYI I'm basically AFK for the next 5 days, I'll be staying up at 1730m in the mountains! | 15:19:31 |
| cdesai | awesome :D | 15:21:01 |
| wb9688 | "could not bring up vm 'builder_default'" for NewPipe :/ | 23:02:07 |
| wb9688 | So I guess we'll have to wait another build cycle | 23:02:23 |
| 25 Jul 2020 |
| kitsunyan |
"could not bring up vm 'builder_default'" for NewPipe :/
More looks like "could not bring up vm 'builder_default'" for everything. 0 packages were built successfully this time.
| 03:04:00 |
|  dupondje left the room. | 03:19:12 |
|  jochensp left the room. | 03:19:12 |
|  izzy left the room. | 03:19:12 |
