drulebian

They divorced in 2008, about 15 years after Debian was named. That's a pretty long relationship by today's standards, IMO.

Ian Murdock is his name if I recall. Deb and Ian

Maybe we can still achieve unity

In recent years, Debian maintainers have been acting with increasing disrespect toward upstream software maintainers and abusing their reputation of being a "stable distro" to shift blame for their bad decisions onto others.

The most significant example would be the orphaning of bcachefs-tools, during which Debian maintainers demonstrated outrageous incompetence in the way they package Rust libraries and a lack of willingness to make simple changes to their package manager (a way to have certain packages installed in multiple versions at once if the names of files inside those packages allow that to happen without conflicts) to accommodate for software whose library dependencies are at odds with those of other Debian packages. This incited an influx of harassment and bigotry towards the bcachefs-tools maintainers and the Rust community at large.

Another example that comes to mind is the KeePassXC fiasco, in which the build configuration for KeePassXC in its Debian package was modified to remove certain features, without any sort of prior communication or discussion with the KeePassXC team itself. One of the features removed by Debianers was the KeePassXC browser extension integration that helps users avoid exposing passwords to the clipboard when using the password manager, protecting them against clipboard grabbers. Because the KeePassXC team was not notified in advance, the settings menu of the password manager had no provisions for telling the user that specific features were disabled at compile time (the assumption being that only advanced users manually compiling KeePassXC would modify those settings), leading to their bug tracker being swarmed by frustrated and confused users of the Debian unstable branch who suddenly had the browser extension integration removed from their version of KeePassXC without a trace. This miscommunication put pressure on the KeePassXC team and misrepresented their software in the eyes of users, as Debian maintainers did not bother coordinating their changes with anyone. To add insult to injury, the Debianers then proceeded to scold the KeePassXC team on their issue tracker for supposedly having bad defaults, further escalating the purposeful breakage event into what came to most resemble bullying of upstream maintainers by Debian packagers.