Your message dated Mon, 02 Dec 2019 03:20:09 +0000
with message-id <e1ibcft-0001zr...@fasolo.debian.org>
and subject line Bug#943521: fixed in node-proxyquire 2.1.3+~1.0.1+~1.0.2-5
has caused the Debian Bug report #943521,
regarding node-proxyquire: fails to clean after build: rm: cannot remove 
'./debian/node_modules': Is a directory
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 ow...@bugs.debian.org
immediately.)


-- 
943521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-proxyquire
Version: 2.1.3+~1.0.1+~1.0.2-3
Severity: serious

Hi,

node-proxyquire fails to clean after a successful build:

 debian/rules clean
dh clean
   dh_clean
rm: cannot remove './debian/node_modules': Is a directory
dh_clean: rm -f -- debian/node-proxyquire.substvars ./debian/node_modules 
debian/files returned exit code 1
make: *** [debian/rules:47: clean] Error 255


This sounds like you have a 'debian/node_modules' entry without
trailing slash in debian/clean.


Andreas

Attachment: node-proxyquire_2.1.3+~1.0.1+~1.0.2-3_twice.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: node-proxyquire
Source-Version: 2.1.3+~1.0.1+~1.0.2-5

We believe that the bug you reported is fixed in the latest version of
node-proxyquire, 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 943...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard <d...@jones.dk> (supplier of updated node-proxyquire 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 02 Dec 2019 04:07:01 +0100
Source: node-proxyquire
Architecture: source
Version: 2.1.3+~1.0.1+~1.0.2-5
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Jonas Smedegaard <d...@jones.dk>
Closes: 943521
Changes:
 node-proxyquire (2.1.3+~1.0.1+~1.0.2-5) experimental; urgency=medium
 .
   * fix cleanup after build;
     closes: bug#943521, thanks to Andreas Beckmann
Checksums-Sha1:
 6faf1b7077cee753baa001a47c16784af31b76d7 2969 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5.dsc
 e39f85b3229fae88df8487a2be311b3a4658266d 5100 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5.debian.tar.xz
 b7e7ef25660d66934cfa56c2a9153da5c16daa80 9414 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5_amd64.buildinfo
Checksums-Sha256:
 4d4dfa704e7979c85d8d9d1a1b066a2692403326cc873a83dd7e924d980b0cc7 2969 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5.dsc
 3a44a5ab65b8f2130f3a05981253e15cb2ad3d401d0ea43ceecc22a6a28ab3fb 5100 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5.debian.tar.xz
 756387196136f0533e94b3f69d6475910bbb87a620c5f725c1ae33f28d97f6fd 9414 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5_amd64.buildinfo
Files:
 2bd64c8f3f3cd9a2d2f7adc24fb9ccad 2969 javascript optional 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5.dsc
 b0cd4b69ed2628b3891eb292816bd29f 5100 javascript optional 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5.debian.tar.xz
 65c7c2b9aeec1499d3f2f1f7c1834711 9414 javascript optional 
node-proxyquire_2.1.3+~1.0.1+~1.0.2-5_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl3kgL8ACgkQLHwxRsGg
ASF1aQ//erhB7FIBlpBt2Fl1OL/EUCrkinlWr8sYq9Va/aS1twFUxo2hGcfjN90D
UAJ85pZCxiyFo1DO6OYeY+Kl67mmcy/5dWhdHHgbe3grjHXbxOKoo3hSrF/8HyVp
3keUcISBlUTMuB3TBLYpNlPmBjVsFAmc6ua2UdunpffQr3T89PF6fsGZAnOP66Of
kwI3JLtjTVACNKTWxhbDDsocaAh21Nqrzkfv1s/JfXJq9csl9inxO81j/Qj1cAr9
N+91J2il/sewSq7PA9F6Qtpc/oUFxwG9mElm5QQZCwwEx85MRPbUMvfZCP7FxvwB
vK9SZzAk6MeNPuLde15rrfQUK8mGGaAuM0ewMuAqebXEla/vMz79Rhcfv4X/glcH
9Ni5G6U1lHH/KnDdO+ClDTJNUKZph6lZoplMFAdOqH+uatqdiPN4b8MqqCaLlVhS
a7OL2C3KNmWvSNmB9R3Tr1fUORvwNQZAEbX8rQi0eHU34jhYaEDAczyNf+uG1WHR
OwdHhoqjxQUvf7vExUN+tpfwC+vuDT3Jc5C6N/NEovR0eSo0SlUVLM7eCOXbpZnu
pJQGnH5yAZ7yRBMlmrEh9Rc96mWgQOx661UGoJWeO19bPh36hSe7ReE1fYTTC/WA
Ed/w04IzCMnLhBUEN+DNvSVSnEFK7arEY7khQf3QdxPQBTQm+YM=
=7LnE
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to