Accepted node-has-gulplog 0.1.0-2 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 25 Nov 2021 17:31:35 +0100
Source: node-has-gulplog
Architecture: source
Version: 0.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
Changed-By: Yadd <yadd@debian.org>
Changes:
node-has-gulplog (0.1.0-2) unstable; urgency=medium
.
* Team upload
[ Debian Janitor ]
* Trim trailing whitespace.
* Use secure copyright file specification URI.
* Bump debhelper from old 9 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
* Remove constraints unnecessary since buster:
+ node-has-gulplog: Drop versioned constraint on node-sparkles in Depends
* Remove empty leading paragraph in Description.
* Bump debhelper from old 12 to 13.
.
[ Yadd ]
* Declare compliance with policy 4.6.0
* Add "Rules-Requires-Root: no"
* Change section to javascript
* Add debian/gbp.conf
* Modernize debian/watch
* Fix filenamemangle
* Fix GitHub tags regex
* Drop dependency to nodejs
* Use dh-sequence-nodejs auto install
Checksums-Sha1:
3f6c7e8753a73e42eedf6140b1f94ad49a6a6741 2084 node-has-gulplog_0.1.0-2.dsc
1c5a3a6d696633395fc888a2fec1faab1e5d7dd1 2520 node-has-gulplog_0.1.0-2.debian.tar.xz
Checksums-Sha256:
15e7c6421603687dded721c9e9fb4b88927ca769da44fb366abfc343670e8d92 2084 node-has-gulplog_0.1.0-2.dsc
d06a62b7b27a33828aa0a709a66a593ab69c9dba086dadd69fa4a6a170ee8eda 2520 node-has-gulplog_0.1.0-2.debian.tar.xz
Files:
63f63f057185f7cfc80651803b2f882a 2084 javascript optional node-has-gulplog_0.1.0-2.dsc
c919bb2fbad16564f8b8a0458fe9de6f 2520 javascript optional node-has-gulplog_0.1.0-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGfuqoACgkQ9tdMp8mZ
7umpuA//WT790RoreBMtoHN4+HR5rixCmKQpCuPPG/wpweALxGMFE8Mz8WcAYN72
SaLvUpFZ7R/Mn7Off4hcMkWtMcisDQK8vPAWoiPMHAhCwjsIh+7Iv9zXLRKpzvK/
jHFHUwYfN4jjmzncHmDA4PJTe3vIUjNkpqsJHQeAvTgtMus5GYivPvRcOVt9aZV7
MHiBI7eBpGAqIg2a4M4TmV/Lwa73k2rw+KLHd+SwvlLhikg+Y3ckVD9m1pTEu3fk
YVHcRFxfycrCQMyvqGgSxuLAxGg88BKrAA/0KQ2rwqsx5FoAgyMaIrLAI1KDIXHI
Cdj8ORXp9UKE+t+8KoSVOuijArG42x6oj76uxyMznWwGF6iJvZZNkjTh2O2SKbZr
yByJekpgOqj2QsLihAz9IcUXykBGVUUIc4OnxclGP02lwhWu0QF33P2AyineBxVj
/0HWK3AxllOGLLxSooLuNqovM0KtX+Pc3XJZufxHCC1yNFGMRRoYn0OqKHBhew/V
RkYiUE8NWahaORexWx3ljdXvHz611szdZwNumGxYELvHiLySz9cOgwg4zmbC+oE8
sFdIUN8ejDhw8Yg5/2ZI7S8NXLLDhczgO6322wluASRp8rnWamqe8qrTnlVlFdwj
lG9+9iiWIRMxivptnPXnFow0SmXX8TItUVsnfAiat9OTJrXlIzk=
=ZIyb
-----END PGP SIGNATURE-----
Reply to: