News for package w3c-markup-validator

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

Format: 3.0 (quilt)
Source: w3c-markup-validator
Binary: w3c-markup-validator
Architecture: all
Version: 1.3+dfsg-3
Maintainer: Debian QA Group <[email protected]>
Homepage: http://validator.w3.org/about.html
Standards-Version: 3.9.6
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/w3c-markup-validator.git
Vcs-Git: git://anonscm.debian.org/collab-maint/w3c-markup-validator.git
Build-Depends: debhelper (>= 9)
Build-Depends-Indep: sharutils, perl, lynx-cur, yui-compressor, w3c-sgml-lib (>= 1.3), libhtml-template-perl, libconfig-general-perl
Package-List:
 w3c-markup-validator deb web optional arch=all
Checksums-Sha1:
 49bea5dda15cea19d06dfb9679097548257b4824 2257513 w3c-markup-validator_1.3+dfsg.orig.tar.gz
 9fc27c63c84b09c6a4d7c3c29e030497e42e640f 24156 w3c-markup-validator_1.3+dfsg-3.debian.tar.xz
Checksums-Sha256:
 feed37fe46791a21cbbd249d18770cf0f38fac420460f19b9ff60da06b45cfa7 2257513 w3c-markup-validator_1.3+dfsg.orig.tar.gz
 974a44f84c9aa7b5dbb4d112e4c52829898f8c1ebb4038524ea72fbbdaf023b2 24156 w3c-markup-validator_1.3+dfsg-3.debian.tar.xz
Files:
 cb5d77e7f6678b1019bf3ff14b4d088c 2257513 w3c-markup-validator_1.3+dfsg.orig.tar.gz
 823abc89cd987cef38378d6dcdec5275 24156 w3c-markup-validator_1.3+dfsg-3.debian.tar.xz

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

iQEcBAEBCAAGBQJWFSduAAoJEEHOfwufG4syRa8IAJNyxLakxqwTyM+Hm2R374oR
HRb4j24KHJvvfAqrMxu+ZfvrEi+RKVbLL5nEDrg3CZmlRjq4JyeLAFMwy6Rvb7cI
Tl27/KNnzFPpUvuo8PCJblxHe34SixbZvnDQOJOmMZRT6mI824DR1MhQHEDb+AZr
VdzoSVZZTFilpBJS5PfNXGAs15jEYE90YM6GuUqevIQUQttT0XiQQjx4KoM/lZeL
KurU6w7sZeYIo0EzLbMHaPHHeuPWjpyBxT1Y65NtMs9so5RGhN3g1GYc7yKitcvF
UFC3LPjxOXfx00X/lerioPgd9aABdmvRBru1Ohaa64eeT4JXdVnJz+B3uL2Sbcw=
=UpgD
-----END PGP SIGNATURE-----

Changes:
w3c-markup-validator (1.3+dfsg-3) unstable; urgency=medium

  * QA upload.
  * Use debhelper compatibility level 9.
  * Put lynx-cur in build-depends, not lynx which is a dummy package.
  * The output of lynx depends on locale setting. Try to be reproducible
    by always using C.UTF-8.

 -- Santiago Vila <[email protected]>  Wed, 07 Oct 2015 15:55:46 +0200