3 ms·
First, this is not in Debian stable (yet). Issues like this is one reason why Debian testing/unstable exist. Secondly, it is common and expected for distributio
by layer8 3y ago
First, this is not in Debian stable (yet). Issues like this is one reason why Debian testing/unstable exist. Secondly, it is common and expected for distributions to select the feature flags they deem appropriate. It is not a fork. The mistake here was not to provide a compatible upgrade option in addition to the new default.
- Spivak 3y agoWhen I found out that it was just in unstable my position flipped on it. The guy has no business being as crass as he is in the comments section of the GH issue but lack of tact from an opinionated software dev in internet discourse is nothing new. And the point behind the petty of switching to package/package-full, which is pretty standard in the Debian world, is perfectly reasonable so long as it happens on a major version bump. I don't disagree that it's annoying to the upstream devs but c'est la vie when you have a bunch of 3rd parties repackaging your code. They won't be the first to have a "uninstall your distro's package and install the upstream version before reporting a bug" in their issue template.