Björn Persson wrote:
To me it looks like an attempt to recruit packagers to help
promoting
the change _upstream_.
There is no upstream for kdelibs3. It is a compatibility package, which is 2
major (first digit!) versions behind what upstream actually develops. We are
mostly only backporting security fixes and compilation fixes, so that legacy
applications keep running.
Look at what packagers are actually asked to do:
> Propose patches to convert to libidn2, and notify upstream about it.
Note well the words "propose", "notify" and "upstream". How
is that
equivalent to blindly enforcing the change without assessing the impact?
It is when we are talking about a package like kdelibs3.
Kevin Kofler