#archlinux32 | Logs for 2024-03-11
Back
[00:32:33] -!- zxrom has quit [Quit: Leaving]
[03:25:29] <bill-auger> when a package is marked 'to-be-deleted', how much time will be it be in that state before being deleted?
[03:25:53] <bill-auger> roughly, within a week or so? - it is not like to remain for longer than that?
[03:27:06] <bill-auger> specifically, 'ksysguard' - i see that all of it's dependents are crossed out, and it's replacement 'libksysguard' is in the repos now
[03:27:30] <bill-auger> maybe that is done by hand? - if so i think htat one can go now
[04:09:47] -!- bill-auger has quit [Ping timeout: 268 seconds]
[04:22:09] -!- bill-auger has joined #archlinux32
[04:25:24] -!- ssserpent has joined #archlinux32
[04:28:33] -!- ssserpent has quit [Client Quit]
[04:31:40] -!- ssserpent has joined #archlinux32
[10:33:46] -!- zxrom has joined #archlinux32
[12:07:51] <KitsuWhooa> I think they only get deleted if a new one finally gets built
[12:07:59] <KitsuWhooa> And is then moved to the repo
[12:08:10] <KitsuWhooa> Or someone manually deletes it
[12:40:10] <KitsuWhooa> speaking of that
[12:40:15] <KitsuWhooa> The following packages appear on the build- and deletion-list:
[12:40:15] <KitsuWhooa> tree-sitter-cli
[12:40:38] <KitsuWhooa> We have 0.22.1, but upstream's PKGBUILD is 0.21.0-1
[12:40:53] <KitsuWhooa> how
[12:43:51] <KitsuWhooa> oh
[12:43:56] <KitsuWhooa> tree-sitter-cli was replaced with tree-sitter
[12:48:24] <KitsuWhooa> oh I made it worse now
[12:48:26] <KitsuWhooa> excellent
[13:04:23] -!- ssserpent has quit [Ping timeout: 260 seconds]
[13:06:21] -!- ssserpent has joined #archlinux32
[13:33:16] -!- Darius10467 has joined #archlinux32