Your message dated Wed, 01 Nov 2017 11:00:19 +0000 with message-id <E1e9qkt-000HRH-6E@fasolo.debian.org> and subject line Bug#877156: fixed in node-registry-auth-token 3.3.1-1 has caused the Debian Bug report #877156, regarding ITP: node-registry-auth-token -- Get the auth token set for an npm registry (if any) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 877156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877156 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: ITP: node-registry-auth-token -- Get the auth token set for an npm registry (if any)
- From: Pirate Praveen <praveen@debian.org>
- Date: Fri, 29 Sep 2017 14:32:00 +0530
- Message-id: <c6b11dc0-d8ef-36c9-1240-1d46256379dc@debian.org>
Package: wnpp Severity: wishlist Owner: Pirate Praveen <praveen@debian.org> X-Debbugs-CC: debian-devel@lists.debian.org * Package name : node-registry-auth-token Version : 3.3.1 Upstream Author : Espen Hovlandsdal <espen@hovlandsdal.com> * URL : https://github.com/rexxars/registry-auth-token#readme * License : Expat Programming Lang: JavaScript Description : Get the auth token set for an npm registry (if any) Get the auth token set for an npm registry from `.npmrc`. Also allows fetching the configured registry URL for a given npm scope. . Node.js is an event-based server-side JavaScript engine. Dependency of npm.Attachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
- To: 877156-close@bugs.debian.org
- Subject: Bug#877156: fixed in node-registry-auth-token 3.3.1-1
- From: Pirate Praveen <praveen@debian.org>
- Date: Wed, 01 Nov 2017 11:00:19 +0000
- Message-id: <E1e9qkt-000HRH-6E@fasolo.debian.org>
Source: node-registry-auth-token Source-Version: 3.3.1-1 We believe that the bug you reported is fixed in the latest version of node-registry-auth-token, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 877156@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen <praveen@debian.org> (supplier of updated node-registry-auth-token package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 29 Sep 2017 14:34:27 +0530 Source: node-registry-auth-token Binary: node-registry-auth-token Architecture: source all Version: 3.3.1-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org> Changed-By: Pirate Praveen <praveen@debian.org> Description: node-registry-auth-token - Get the auth token set for an npm registry (if any) Closes: 877156 Changes: node-registry-auth-token (3.3.1-1) unstable; urgency=low . * Initial release (Closes: #877156) Checksums-Sha1: 2a0d852db1b2892c04ac88b7afa47c35f529598b 2177 node-registry-auth-token_3.3.1-1.dsc e160cfaac571c2bffc1783085c3c00e749e4d2ac 6363 node-registry-auth-token_3.3.1.orig.tar.gz cf16ba6233895b44c18ea2d029d6f2ce8e4bdfcc 2072 node-registry-auth-token_3.3.1-1.debian.tar.xz 271d06d8037794feadc7fa90e3b399e8e054c318 5642 node-registry-auth-token_3.3.1-1_all.deb a9c4d7da677dc076e49e5cbc113d3cc8dfa20730 5513 node-registry-auth-token_3.3.1-1_amd64.buildinfo Checksums-Sha256: 3da408fce1acab812f9a94d1b30af2d3bcaa5cfe4389f91d80f777f34b0354ce 2177 node-registry-auth-token_3.3.1-1.dsc dd14b6917afe1752873021776287b8b40d678d873762487577d84792986d2dfd 6363 node-registry-auth-token_3.3.1.orig.tar.gz c581a186c5676d0ef0953fb96842f3e2fca0162d915bb70f9531fdd72a097125 2072 node-registry-auth-token_3.3.1-1.debian.tar.xz ee74b4f10f48c5f8c167f1dcdd353716a7b9f5551703341dbdaeb77310098649 5642 node-registry-auth-token_3.3.1-1_all.deb 8be27413ed10c01a22c0bee13feec597bb8f06a799e5a5495ec85739202e89ea 5513 node-registry-auth-token_3.3.1-1_amd64.buildinfo Files: 83405b8086704f69ad549004d1fb551f 2177 javascript optional node-registry-auth-token_3.3.1-1.dsc 263e1e96237ade80ad8d0a77cb882b51 6363 javascript optional node-registry-auth-token_3.3.1.orig.tar.gz e6abc5565eca98f0b31cac47e521e4e7 2072 javascript optional node-registry-auth-token_3.3.1-1.debian.tar.xz d50e66f7f57dc2e24383006ee5669ac1 5642 javascript optional node-registry-auth-token_3.3.1-1_all.deb 374b69d1702ed244ad6bd760cedf516b 5513 javascript optional node-registry-auth-token_3.3.1-1_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlnODocACgkQzh+cZ0US wioruxAAkVikfk+xPah0Kln/BVDmYdjpqZ7D+HPNgHjQgAyWeRqdFkAkFxoRoGbh 4R1HWiQh2T1QKIfKzElV3iiLvVDxvGPR2qSY6C4HeSnonHR8SmoF94mSGXWlkPxQ +VhEe1UFaozq1kaPl0321QjOyKwM22uKMQRU41EvAe43ELGxVThF8u1Yn9/F7wfH hKz9zHDdQsJL0OS/Umx6VaZ61S4opDsdoQHMfY1nE4V1X/dgPWo9+d0oO4GkrSvC eNWtWKFHb9X27njzel/q5j1TW5E39NjHql2xi+gvDXft0EQ6nvSFuQU2h6CegwOc 8hla1EGT27xmVwR1fYWzwcJA9nOLZzft6dt85zjJOcQ4Vt41oq0PDyjsgErIwgmG lJuFeFNzqldVPC/FkNrYT9XZYxe/oVtMqXx0MN6Lhw+9bAiWykOOVXY6Iqe/Le4C HgEekA6WjPUkM+WLaKOPAiSJ9UIDHa/36lPo4KzrBn6dMIu9k4kqsQp2Rb7zPiYu /tu6DsrMeYua4yAjnbTxgYDjL79l1mNfJ7ABbMizoq5a88+FDJUESTsUYiiQZkq/ 0+i8fb6mgTXrv3xSKjy7jaE6c+KjCn+SgnAKJpfrRjXvhYMYtyOu+XexIEN4SJxL G11jV5zcCVFzlF3CWWv7AOZFd5zklKUHbzyv1dyhW4DXOoEmUVI= =Mbic -----END PGP SIGNATURE-----
--- End Message ---