Source: node-follow-redirects
Version: 1.14.9+~1.14.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
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
> Link node_modules/@types/follow-redirects -> ../../types-follow-redirects
> dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> dh_auto_test --buildsystem=nodejs
> ln -s ../. node_modules/follow-redirects
> /bin/sh -ex debian/tests/pkg-js/test
> + mocha
>
>
> follow-redirects
> undefined http.get with string and callback - redirect (47ms)
> undefined http.get with URL object and callback - redirect
> undefined http.get with options object and callback - redirect
> undefined http.get with string and callback - no redirect
> undefined http.get with options object and callback - no redirect
> undefined http.get with host option and callback - redirect
> undefined http.get with response event
> undefined should return with the original status code if the response
> does not contain a location header
> undefined should emit connection errors on the returned stream
> undefined should emit socket events on the returned stream
> undefined should emit connect events on the returned stream
> undefined emits an error on redirects with an invalid location
> undefined emits an error whem url.resolve fails
> undefined emits an error when the request fails for another reason
> undefined should destroy responses
> undefined should honor query params in redirects
> undefined should allow aborting
> undefined should provide connection
> undefined should provide flushHeaders
> undefined should provide getHeader
> undefined should provide removeHeader
> undefined should provide setHeader
> undefined should provide setNoDelay
> undefined should provide setSocketKeepAlive
> undefined should provide setTimeout
> undefined should provide socket
> undefined should wait for an explicit call to end
> undefined errors on write after end
> undefined should support writing into request stream without redirects
> undefined should support writing into request stream with redirects
> undefined should support piping into request stream without redirects
> undefined should support piping into request stream with redirects
> undefined should support piping into request stream with explicit
> Content-Length without redirects
> undefined should support piping into request stream with explicit
> Content-Length with redirects
> undefined keeps the header when redirected from HTTP to HTTPS
> undefined drops the header when redirected from HTTPS to HTTP
> undefined keeps the header when redirected from HTTP to HTTPS
> undefined drops the header when redirected from HTTPS to HTTP
> setTimeout
> undefined clears timeouts after a successful response
> undefined clears timeouts after an error response
> undefined handles errors occuring before a socket is established
> undefined sets a timeout when the socket already exists
> undefined destroys the socket after configured inactivity period (102ms)
> undefined should timeout on the final request
> undefined should include redirect delays in the timeout
> undefined overrides existing timeouts
> should obey a `maxRedirects` property
> undefined which defaults to 21 (64ms)
> undefined which can be set globally
> undefined set as an option on an individual request
> the trackRedirects option
> when not set
> undefined should not track redirects
> when set to true
> 1) should track redirects
> should switch to safe methods when appropriate
> when redirecting with status code 300
> undefined should reuse GET
> undefined should reuse HEAD
> undefined should reuse POST
> undefined should reuse PUT
> undefined should reuse DELETE
> when redirecting with status code 301
> undefined should reuse GET
> undefined should reuse HEAD
> undefined should switch from POST to GET
> undefined should reuse PUT
> undefined should reuse DELETE
> when redirecting with status code 302
> undefined should reuse GET
> undefined should reuse HEAD
> undefined should switch from POST to GET
> undefined should reuse PUT
> undefined should reuse DELETE
> when redirecting with status code 303
> undefined should reuse GET
> undefined should reuse HEAD
> undefined should switch from POST to GET
> undefined should switch from PUT to GET
> undefined should switch from DELETE to GET
> when redirecting with status code 307
> undefined should reuse GET
> undefined should reuse HEAD
> undefined should reuse POST
> undefined should reuse PUT
> undefined should reuse DELETE
> should error on an unsupported protocol redirect
> undefined (http -> about)
> should obey a `maxBodyLength` property
> undefined which defaults to 10MB
> undefined set globally, on write
> undefined set per request, on write
> undefined set globally, on end
> undefined set per request, on end
> writing invalid data
> undefined throws an error
> when switching from POST to GET
> undefined should drop the entity and associated headers
> when redirecting to a different host while the host header is set
> undefined uses the new host header if redirect host is different
> undefined uses the location host if redirect host is the same
> undefined uses the existing host header if redirect host is relative
> when the client passes an header named Authorization
> undefined ignores it when null
> undefined keeps the header when redirected to the same host
> undefined keeps the header when redirected to the same host via header
> undefined keeps the header when redirected to the same host via header
> undefined keeps the header when redirected to a subdomain
> undefined drops the header when redirected to a different host (same
> hostname and different port)
> undefined drops the header when redirected to a different host
> undefined drops the header when redirected from a different host via
> header
> when the client passes an header named Cookie
> undefined ignores it when null
> undefined keeps the header when redirected to the same host
> undefined keeps the header when redirected to the same host via header
> undefined keeps the header when redirected to the same host via header
> undefined keeps the header when redirected to a subdomain
> undefined drops the header when redirected to a different host (same
> hostname and different port)
> undefined drops the header when redirected to a different host
> undefined drops the header when redirected from a different host via
> header
> when the followRedirects option is set to false
> undefined does not redirect
> should not hang on empty writes
> undefined when data is the empty string without encoding
> undefined when data is the empty string with encoding
> undefined when data is Buffer.from('')
> end accepts as arguments
> undefined (none)
> undefined the empty string
> undefined a non-empty string
> undefined a non-empty string and an encoding
> undefined a non-empty string, an encoding, and a callback
> undefined a non-empty string and a callback
> undefined a callback
> change request options before redirects
> undefined only call beforeRedirect on redirects, not the inital http
> call
> undefined ignore beforeRedirect if not a function
> undefined append new header with every redirect
> undefined abort request chain after throwing an error
> undefined access response header in beforeRedirect
>
>
> 118 passing (784ms)
> 1 failing
>
> 1) follow-redirects
> the trackRedirects option
> when set to true
> should track redirects:
>
> AssertionError [ERR_ASSERTION]: 'text/plain' == 'text/plain;
> charset=utf-8'
> + expected - actual
>
> -text/plain
> +text/plain; charset=utf-8
>
> at /<<PKGBUILDDIR>>/test/test.js:807:20
> at processTicksAndRejections (internal/process/task_queues.js:95:5)
>
>
>
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-follow-redirects_1.14.9+~1.14.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220412&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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.
