Source: node-superagent Version: 6.1.0-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210728 ftbfs-bullseye
Hi, During a rebuild of all packages in bullseye, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > babeljs --config-file ./.lib.babelrc src --out-dir lib > Browserslist: caniuse-lite is outdated. Please run: > npx browserslist@latest --update-db > > Why you should do it regularly: > https://github.com/browserslist/browserslist#browsers-data-updating > Error [BrowserslistError]: [BABEL] /<<PKGBUILDDIR>>/src/agent-base.js: > Unknown browser query `> 1%`. Maybe you are using old Browserslist or made > typo in query. (While processing: > "/usr/share/nodejs/@babel/preset-env/lib/index.js") > at unknownQuery (/usr/share/nodejs/browserslist/index.js:285:10) > at /usr/share/nodejs/browserslist/index.js:372:11 > at Array.reduce (<anonymous>) > at resolve (/usr/share/nodejs/browserslist/index.js:318:18) > at browserslist (/usr/share/nodejs/browserslist/index.js:444:21) > at getTargets > (/usr/share/nodejs/@babel/helper-compilation-targets/lib/index.js:204:48) > at /usr/share/nodejs/@babel/preset-env/lib/index.js:258:57 > at /usr/share/nodejs/@babel/helper-plugin-utils/lib/index.js:19:12 > at /usr/share/nodejs/@babel/core/lib/config/full.js:211:14 > at Generator.next (<anonymous>) { > browserslist: true > } > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/07/28/node-superagent_6.1.0-3_testing.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. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.