On 10/29/2015 04:34 PM, Jérémy Lal wrote: > > > 2015-10-29 16:24 GMT+01:00 Thomas Goirand <z...@debian.org > <mailto:z...@debian.org>>: > > Hi, > > I'm worried that this bug is left undressed. It affects *a lot* of > packages, including: > - nodejs > - openstack-dashboard > > And also, upstream seems to not care about it, as per the github issue > set in the forwarded-to-url. > > Laszlo, will you work on this? > > > Hi, > how does it affect "nodejs" ? > > Jérémy
Well, not nodejs itself directly. Though a lot of javascript libraries are build-depending on node-smash, like for example libjs-angularjs. This breaks the dependency chain of many things, not only nodejs packages: - libjs-angular-gettext - libjs-angularjs-smart-table - libjs-lrdragndrop - libjs-magic-search - libjs-twitter-bootstrap-wizard - rickshaw: buggy deps smash, flagged for removal in 29.9 days Then lots of things are in AUTORM status because of this: - python-mpld3 - some owncloud stuff - things related to d3 - prometheus - ... and affecting OpenStack dashboard and friends: - horizon - murano-dashboard - python-xstatic-angular-cookies - python-xstatic-angular-gettext - python-xstatic-angular-lrdragndrop - python-xstatic-angular-mock - python-xstatic-angular - python-xstatic-d3 - python-xstatic-magic-search - python-xstatic-rickshaw - python-xstatic-smart-table - tuskar-ui I didn't have my facts completely strait, though the point is: node-smash removal from testing would impact lots of packages, so it'd be nice to have a way to solve the issue ASAP. And I'm worried that upstream wrote in the Github issue that nothing will be done. :( Thomas Goirand (zigo)
