The only official Debian packages are what you find on debian.org and
its mirrors, third party repositories are unofficial by definition and
...
From upstream's perspective, this is not true, unless you apply the
term Debian in the strict sense of "released by the Debian project" and
not in the sense of "packaged using Debian's packaging system".
Debian packages are not broken, they are working fine, to the extent
permitted by extremely broken and messy upstream sources. Due to
upstream bugs outside of our control at times some subfeature might not
work, but there's nothing we can do about it, there's always something
broken in the upstream code.
From a user's perspective, this is also untrue:
If azure-cli is currently installed from the Debian package repository,
it fails on multiple subfeatures. In this context, it's irrelevant if
this is "upstream's fault". By releasing the package in the Debian
package repositories, one or multiple DDs or DMs have taken (limited)
responsibility for the Debian version, and they should make sure the
Debian version gets fixed.
That is a bit rich, given upstream routinely ignores bug reports, pull
requests and so on, to the extent that I have given up even trying. The
"azure-sdk-for-python" upstream repository is an absolute disaster of a
dumpster fire, with no attempt whatsoever at even a semblance of
functional release engineering, which causes enough pain already to us.
That may be the case, but this is not visible to users.
They will experience a bug in the Debian version, report it upstream, be
rebuffed because they had the gall (!!) to use the Debian version
instead of the upstream version, and then get redirected to upstream's
package repository.
Most regular users would think at this point that the fault lies with
the Debian project and simply install the upstream version instead.
This is a terrible user experience and does absolutely nothing to get
broken subfeatures fixed in the Debian packages.
Absolutely not, the official Debian packages are following Debian
policy and best practices as they should, while upstream is a gigantic
mess and a security nightmare, so ask them instead.
This may be the case, but taking this stance doesn't get the mess fixed.
As is evident in https://github.com/Azure/azure-cli/issues/19640 ,
upstream doesn't care about what their mess causes downstream, and they
will simply continue "fixing" it in their own way.
Again: I'm trying to blame Debian Developers for broken packages, I'm
trying to request a solution that does not result in a shitty user
experience.
