Your message dated Sat, 19 Feb 2022 08:38:10 +0000
with message-id <e1nllfq-0002v3...@fasolo.debian.org>
and subject line Bug#1006057: fixed in node-tildify 2.0.0-4
has caused the Debian Bug report #1006057,
regarding node-tildify: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-tildify
Version: 2.0.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>    dh_update_autotools_config
>    dh_autoreconf
>    dh_auto_configure --buildsystem=nodejs
>    dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>    dh_auto_test --buildsystem=nodejs
>       mkdir -p node_modules
>       ln -s ../. node_modules/tildify
>       /bin/sh -ex debian/tests/pkg-js/test
> + tape test.js
> TAP version 13
> # tildify home
> ok 1 should be strictly equal
> # tildify path
> ok 2 should be strictly equal
> ok 3 should be truthy
> ok 4 should not be strictly equal
> # ensure only a fully matching path is replaced
> ok 5 should be strictly equal
> # ignore relative paths
> ok 6 should be strictly equal
> # only tildify when home is at the start of a path
> ok 7 should be strictly equal
> 
> 1..7
> # tests 7
> # pass  7
> 
> # ok
> 
> Removing node_modules/tildify
>    create-stamp debian/debhelper-build-stamp
>    dh_prep
>    dh_auto_install --buildsystem=nodejs --destdir=debian/node-tildify/
> dh_auto_install: warning: ### Missing ./build/config.gypi, skipping
> 
> Found "files" field in ./package.json, using it
>       mkdir -p /<<PKGBUILDDIR>>/debian/node-tildify//usr/share/nodejs/tildify/
>       install -m 644 ./index.js 
> /<<PKGBUILDDIR>>/debian/node-tildify//usr/share/nodejs/tildify//
>       install -m 644 ./index.d.ts 
> /<<PKGBUILDDIR>>/debian/node-tildify//usr/share/nodejs/tildify//
>       install -m 644 ./package.json 
> /<<PKGBUILDDIR>>/debian/node-tildify//usr/share/nodejs/tildify//
>       install -m 644 ./package.json 
> /<<PKGBUILDDIR>>/debian/node-tildify//usr/share/nodejs/tildify//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-tildify_2.0.0-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: node-tildify
Source-Version: 2.0.0-4
Done: Yadd <y...@debian.org>

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

Debian distribution maintenance software
pp.
Yadd <y...@debian.org> (supplier of updated node-tildify 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: Sat, 19 Feb 2022 09:05:53 +0100
Source: node-tildify
Architecture: source
Version: 2.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Yadd <y...@debian.org>
Closes: 1006057
Changes:
 node-tildify (2.0.0-4) unstable; urgency=medium
 .
   * Team upload
   * Fix d/control for Debian::Control (Closes: #1006057)
Checksums-Sha1: 
 8af57accf01c8972cd295fe7c0540d5f44d064c8 2045 node-tildify_2.0.0-4.dsc
 fcc6ff91e531b5c0ddf803c2768278bd708db7ad 3152 
node-tildify_2.0.0-4.debian.tar.xz
Checksums-Sha256: 
 1949494e7191fb5d30fcb7fd7db04142248056d0a46935a3a1c4376ac9669fb9 2045 
node-tildify_2.0.0-4.dsc
 b9029a51d4c5b3ba52cc92da0d3d51fe7e30fffe348c58cc4d91c4bf704fc294 3152 
node-tildify_2.0.0-4.debian.tar.xz
Files: 
 3f97dd417806b78688c82ed0b076a6a8 2045 javascript optional 
node-tildify_2.0.0-4.dsc
 ca26a263d94b5e46214805587ee99e87 3152 javascript optional 
node-tildify_2.0.0-4.debian.tar.xz

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

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmIQpTgACgkQ9tdMp8mZ
7ule5hAAhHgpGktR1cvJaj59kgWDr5+YtZdyv4LOlTidFZH7irbyNzLh+H/KSBGj
dCE2y/qQvtqjnsMhcgoWEpeQ8iwCptcGZfNBIUMs0ataKH35pNuWABsb2a9Po79a
P/uF+mgVppNhPNCMTqBxoiy2T43IEoFi1f46lHth1B4lr1ZK2VjZ+cqYk63dYOou
0wo6VrUfAMLN5W2PYgdIxoTpTo3KnPCc7JdeSVY0c1Hm5VV9jkU/s1zxbXs466qA
XEzZjql5A+eoFaZkMYe3/nOItw9viO0ApDmaY3O0/dUrWutVan585eKut7oLq/Q0
1n7mrAAx2hTARBMeKJXZD/dI1QE+G827cQZKPtkCg/mva+9FpUpw+2H7JZL+yw+L
Cxurs+FXDbjnrtgHuJv0g6GiwroLJyAvH6S+ieJK0hxoJHV00OdA9cKgLgwJCKb8
VOh9I9t2/QD4dimmnrscC/Cq4CsX5j7lxNZxKZeWBbY6U3WUdrb0U32gF+E5kp9s
qMYKlIM+Sh2s/3mDzWQ9/+RCJQiJZsC7IX7TBwzW91ucQnRAPClr82ZU3bn1cb4U
ZuonLkStDkwXL3VEAPZVWtmw1+k9Q8NWm1kg4U4lI8DGcOCe7Pj6Si14YATyJ9Ps
n5qY0ynx/KJZV+5IBJRDPxKe9Jh6U73DyhZU9lghDQckktmmi+0=
=pzU5
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to