Your message dated Mon, 13 Mar 2017 15:07:19 +0000
with message-id <e1cnrz9-000hpn...@fasolo.debian.org>
and subject line Bug#857565: Removed package(s) from unstable
has caused the Debian Bug report #669541,
regarding underscore.logger: FTBFS: SyntaxError: In
src/underscore.logger.coffee, octal escape sequences "\033[#{color}m" are not
allowed on line 53
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.)
--
669541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: underscore.logger
Version: 0.3.0~20111114-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120419 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> debian/rules build
> test -x debian/rules
> mkdir -p "."
>
> Scanning upstream source for new/changed copyright notices...
>
> licensecheck -c '.*' -r --copyright -i
> '^debian/(changelog|copyright(|_hints|_newhints))' -l '99999' * |
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> 3 combinations of copyright and licensing found.
> WARNING: The following (and possibly more) new or changed notices discovered:
>
> Format: http://www.debian.org/doc/packaging-manuals/…
> License: GPL-2+
> HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER …
>
> To fix the situation please do the following:
> 1) Fully compare debian/copyright_hints with debian/copyright_newhints
> 2) Update debian/copyright as needed
> 3) Replace debian/copyright_hints with debian/copyright_newhints
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> coffee -o build src/*.coffee
> SyntaxError: In src/underscore.logger.coffee, octal escape sequences
> "\033[#{color}m" are not allowed on line 53
> at SyntaxError (unknown source)
> at Lexer.error (/usr/lib/coffee-script/lib/coffee-script/lexer.js:686:13)
> at Lexer.stringToken
> (/usr/lib/coffee-script/lib/coffee-script/lexer.js:174:14)
> at Lexer.tokenize
> (/usr/lib/coffee-script/lib/coffee-script/lexer.js:35:137)
> at Object.compile
> (/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:43:32)
> at /usr/lib/coffee-script/lib/coffee-script/command.js:182:33
> at /usr/lib/coffee-script/lib/coffee-script/command.js:152:18
> at [object Object].<anonymous> (fs.js:115:5)
> at [object Object].emit (events.js:64:17)
> at afterRead (fs.js:1117:12)
> make: *** [build/node-underscore.logger] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/04/19/underscore.logger_0.3.0~20111114-1_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!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--- End Message ---
--- Begin Message ---
Version: 0.3.0~20111114-1+rm
Dear submitter,
as the package underscore.logger has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/857565
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
