#archlinux32 | Logs for 2023-05-28

[09:56:42] -!- Vorpal has joined #archlinux32
[10:09:41] <Vorpal> if I understand things correctly, due to the git migration you ended up having to rebuild (almost?) all packages? I don't quite understand why that would be though. (Seems like a good opportunity to make sure no packages have bit rotted, but not needed as such.) Is it just some sort of limitation in the automated system?
[11:17:29] -!- titus_livius has joined #archlinux32
[11:19:44] -!- buildmaster has joined #archlinux32
[18:11:19] <girls> Yes, we "have to" rebuild all of them. The problem is, that the tracking mechanism changed. Before it was a git hash in a giant mono-repo (well, actually two: one for core & extra, one for community). Now it is a git hash in a separate git repository for each package. The buildmaster (and we) cannot know, which packages changed, and which did not. We could possibly semi-manually, heuristically sort this out based on the $pkgver and
[18:11:19] <girls> $pkgrel (which we will certainly do, if some packages are blocking us), but the cleanest way forward was to declare all packages as need-to-be-rebuilt.
[19:06:04] -!- mvchtz has quit [Ping timeout: 265 seconds]
[19:09:16] -!- mvchtz has joined #archlinux32
[21:13:35] -!- Vorpal has quit [Ping timeout: 240 seconds]