Package: closure-linter
Version: 2.3.13-2
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi!

There seems to be a new upstream version available with ES6
support. The project was moved to GitHub but there is no release tag,
so I am unsure if the newer version is 2.3.17 or 2.3.16:

 https://github.com/google/closure-linter/blob/master/setup.py

On Pypi, it's still 2.3.13.

I am interested by an update to get ES6 support.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages closure-linter depends on:
ii  python                2.7.9-1
ii  python-gflags         1.5.1-2
ii  python-pkg-resources  17.0-1

closure-linter recommends no packages.

closure-linter suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVnjimAAoJEJWkL+g1NSX5ecoP/182C2pDp173aUoS8wrqp4Y5
X5V9cpAliIqEDGok3sgZpZjzDX39bEwV0BH1AyAsFSGsRUKdgguRqaqRaVnFxAqX
cFRf6Vo8cFJEfOTP4Oj40sgXhqkR5JZBdOXrQJbM38ReL81SOTruGtL8N3ghMYcM
AZ9VmmX0LxsQkmUbQeJfSXlfkEC3EkV4Oez45jhmUSZNCcUJNv41eZkTW6VisLMW
TT8aKMKKTbHdCJK4f1N40Q95vXSz/aSDo909YHO9klLw0C83UpKhBu8+LoNBMDJf
STAkbbKLuLkxVH0uBi2e5JjJTTheskcTt3NQosVpENv3awkxGk4Nvx6JEGy4ggsb
8ZPLAyqMkwDr4ZL4LDYdhF74MoBvM0ZYH4LIqGYVti0amkTL3lpefGHv1WTkt0rQ
tAFYFAnVIRscwhQBzE2hdfDwmgyX4Q9q/4SdjIE/iXpvUmKxLryGp1mvPXl1OaI1
v8SPu/9DAepNo9g2CXCfW3YrFeC0nzx7M3zR6Ou3vnWuHwOBI/KuceWNkfKQzffg
NEEzDtM23brq5HCDYtwPBQY9h8JeBbeXJsmF5VLiSoEUjswUKMMxKPSx7roVjrbp
WiH4ffDc0csB3uD1vc7Au1QpA4yoN+uyycmFDfMOGG1teHvuY/dpyzi+wXUhkadN
PDnFVurrKbflKkJncGHk
=TKtU
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to