dak (the Debian Archive Kit, the software that manages the package repositories in Debian proper) now contains slop

source: committer pointed it specifically out in IRC

🤮

and I cannot tell if the suggestions around using slop machines for NEW processing are entirely in jest…

I just…

… fuck this, fuck all this.

@werdahias yeah.

Most of my personal Free Software contributions over the last year
have been AI-assisted to some degree.

Who’s going to tell him that that makes them not Free Software any more?

@werdahias urgs.

+---
| [A patch] that was merged for the 6.15 release. That patch was
| entirely written by an LLM, changelog included.
+---[ https://lwn.net/Articles/1026558/ ]

Why has that not been reverted? Why is the author not a persona nōn grata? Why is this not reverted in Debian?

I guess it’s #Slopian now.

I mean, yes, can’t tell all slop, but at least remove the known slop, ya know?

Linus Torvalds, I’m looking at you.

Bastian Blank, Ben Hutchings, Maximilian Attems, Romain Perier, Salvatore Bonaccorso, Yves-Alexis Perez, I’m looking at you for knowing about it and not reverting it. (Or, well, the Debian Linux Kernel Team.)

@SpaciousCoder78 @werdahias I already tried with a GR proposal, but… 😿

I completely agree with that statement of yours.

@SpaciousCoder78 @werdahias immediate consequence would be the removal of rsysslop :D

@werdahias @SpaciousCoder78 but tbh in my eyes that’s exactly the same thing we would do if an upstream contained nōn-free contributions…

… which these ARE!

@werdahias @SpaciousCoder78 no, rsysslop is already in trixie, upstream said it was already slopped shortly after bookworm