notice these things, I only notice via my QA page. (Possibly I should remove
myself from Uploaders, since I don't intend to maintain this in the future, as
far as I can avoid doing so.)
On Thu, 01 Dec 2016 21:01:32 +0100 Paul Gevers <elb...@debian.org> wrote:
> Package: src:jquery-ui-themes
> Version: 1.12.1+dfsg-1
> Severity: important
> Hi Ximin,
> The debci test of cactiÂ¹ started failing after the update of
> jquery-ui-themes. This is caused by the change of the css file names in the
> packages. The names used to be
> packages requiring updating, I suggest to rename back to the old name, unless
> this was really done on purpose. In that case I'd like to hear why.
> Â¹ https://ci.debian.net/packages/c/cacti/unstable/amd64/
This description is not entirely correct, in fact both versions contain
jquery-ui.css - note the dash instead of a dot.
The new version  does not contain any jquery.ui.* files, that is what the
upstream distribution zip chose for this version. I didn't do this.
The old version  contains both jquery-ui.css as well as jquery.ui.all.css.
The former seems to be an amalgated single-file version of the theme, the
latter @imports the separate files when loaded.
It looks like upstream has dropped support for this type of usage in the new
version, though that was what the old README.Debian recommended.
This is a very unfortunate situation but I don't think it would be appropriate
for Debian to "put back in" the old feature that upstream dropped.
I hope this kind of crappy situation would be an incentive for everyone to
avoid using JS in their own projects as far as possible, or at least only use
the good JS projects and avoid the crappy ones (and learn how to distinguish