Bug#991651: marked as done (FTBFS: Replace Autoprefixer browsers option to)
Your message dated Fri, 30 Jul 2021 05:35:09 + with message-id and subject line Bug#991651: fixed in twitter-bootstrap4 4.5.2+dfsg1-7 has caused the Debian Bug report #991651, regarding FTBFS: Replace Autoprefixer browsers option to 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.) -- 991651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: twitter-bootstrap4 Version: 4.5.2+dfsg1-6 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 '/<>' > mkdir -p dist/css dist/js dist/tmp > sassc --sourcemap=auto scss/bootstrap.scss dist/tmp/bootstrap.css > sassc --sourcemap=auto scss/bootstrap-grid.scss dist/tmp/bootstrap-grid.css > sassc --sourcemap=auto scss/bootstrap-reboot.scss > dist/tmp/bootstrap-reboot.css > node debian/postcss.js > > Replace Autoprefixer browsers option to Browserslist config. > Use browserslist key in package.json or .browserslistrc file. > > Using browsers option can cause errors. Browserslist config can > be used for Babel, Autoprefixer, postcss-normalize and other tools. > > If you really need to use option, rename it to overrideBrowserslist. > > Learn more at: > https://github.com/browserslist/browserslist#readme > https://twitter.com/browserslist > > > 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 > (node:16484) UnhandledPromiseRejectionWarning: BrowserslistError: Unknown > browser query `> 1%`. Maybe you are using old Browserslist or made typo in > query. > at unknownQuery (/usr/share/nodejs/browserslist/index.js:285:10) > at /usr/share/nodejs/browserslist/index.js:372:11 > at Array.reduce () > at resolve (/usr/share/nodejs/browserslist/index.js:318:18) > at browserslist (/usr/share/nodejs/browserslist/index.js:444:21) > at Browsers.parse (/usr/share/nodejs/autoprefixer/lib/browsers.js:54:12) > at new Browsers (/usr/share/nodejs/autoprefixer/lib/browsers.js:42:26) > at loadPrefixes > (/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:103:20) > at Object.prepare > (/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:117:22) > at /usr/share/nodejs/postcss/lib/lazy-result.js:133:39 > (node:16484) UnhandledPromiseRejectionWarning: Unhandled promise rejection. > This error originated either by throwing inside of an async function without > a catch block, or by rejecting a promise which was not handled with .catch(). > To terminate the node process on unhandled promise rejection, use the CLI > flag `--unhandled-rejections=strict` (see > https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection > id: 1) > (node:16484) [DEP0018] DeprecationWarning: Unhandled promise rejections are > deprecated. In the future, promise rejections that are not handled will > terminate the Node.js process with a non-zero exit code. > > Replace Autoprefixer browsers option to Browserslist config. > Use browserslist key in package.json or .browserslistrc file. > > Using browsers option can cause errors. Browserslist config can > be used for Babel, Autoprefixer, postcss-normalize and other tools. > > If you really need to use option, rename it to overrideBrowserslist. > > Learn more at: > https://github.com/browserslist/browserslist#readme > https://twitter.com/browserslist > > > (node:16484) UnhandledPromiseRejectionWarning: BrowserslistError: Unknown > browser query `> 1%`. Maybe you are using old Browserslist or made typo in > query. > at unknownQuery (/usr/share/nodejs/browserslist/index.js:285:10) > at /usr/share/nodejs/browserslist/index.js:372:11 > at Array.reduce () > at resolve (/usr/share/nodejs/browserslist/index.js:318:18) > at browserslist (/usr/share/nodejs/browserslist/index.js:444:21) > at Browsers.parse (/usr/share/nodejs/autoprefixer/lib/browsers.js:54:12) > at new Browsers (/usr/share/nodejs/autoprefixer/lib/browsers.js:42:26) > at loadPrefixes > (/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:103:20) > at Object.prepare > (/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:117:22) > at /usr/share/nodejs/postcss/lib/lazy-result.js:133:39 > (node:16484) UnhandledPromiseRejectionWarning: Unhandled promise
Processed: Bug#991651 marked as pending in twitter-bootstrap4
Processing control commands: > tag -1 pending Bug #991651 [src:twitter-bootstrap4] FTBFS: Replace Autoprefixer browsers option to Ignoring request to alter tags of bug #991651 to the same tags previously set -- 991651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991651: marked as pending in twitter-bootstrap4
Control: tag -1 pending Hello, Bug #991651 in twitter-bootstrap4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/twitter-bootstrap4/-/commit/12442ac1673142543d2e946ee6cec3e74ff88f1b Don't check for caniuse-lite updates during build Closes: #991651 (this message was generated automatically) -- Greetings https://bugs.debian.org/991651
Bug#991651: marked as pending in twitter-bootstrap4
Control: tag -1 pending Hello, Bug #991651 in twitter-bootstrap4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/twitter-bootstrap4/-/commit/e2d9364529633b513d6407d22348defd77e53e8c Don't check for caniuse-lite updates during build Closes: #991651 (this message was generated automatically) -- Greetings https://bugs.debian.org/991651
Processed: Bug#991651 marked as pending in twitter-bootstrap4
Processing control commands: > tag -1 pending Bug #991651 [src:twitter-bootstrap4] FTBFS: Replace Autoprefixer browsers option to Ignoring request to alter tags of bug #991651 to the same tags previously set -- 991651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991651: marked as pending in twitter-bootstrap4
Control: tag -1 pending Hello, Bug #991651 in twitter-bootstrap4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/twitter-bootstrap4/-/commit/12442ac1673142543d2e946ee6cec3e74ff88f1b Don't check for caniuse-lite updates during build Closes: #991651 (this message was generated automatically) -- Greetings https://bugs.debian.org/991651
Processed: Bug#991651 marked as pending in twitter-bootstrap4
Processing control commands: > tag -1 pending Bug #991651 [src:twitter-bootstrap4] FTBFS: Replace Autoprefixer browsers option to Added tag(s) pending. -- 991651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991280: marked as done (firmware-microbit-micropython-dl: fails to install: checksum of downloaded file does not match)
Your message dated Fri, 30 Jul 2021 03:48:50 + with message-id and subject line Bug#991280: fixed in python-uflash 1.2.4+dfsg-8 has caused the Debian Bug report #991280, regarding firmware-microbit-micropython-dl: fails to install: checksum of downloaded file does not match 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.) -- 991280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-microbit-micropython-dl Version: 1.2.4+dfsg-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up firmware-microbit-micropython-dl (1.2.4+dfsg-7) ... Either your micro:bit MicroPython runtime is missing, or it is out-of-date. Downloading micro:bit MicroPython runtime from https://raw.githubusercontent.com/ntoll/uflash/master/firmware.hex... --2021-07-15 14:11:04-- https://raw.githubusercontent.com/ntoll/uflash/master/firmware.hex Connecting to 10.99.1.1:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 1832972 (1.7M) [text/plain] Saving to: '/tmp/tmp.6rBUe36m2h' /tmp/tmp.6rBUe36m2h 0%[] 0 --.-KB/s /tmp/tmp.6rBUe36m2h 100%[===>] 1.75M --.-KB/sin 0.07s 2021-07-15 14:11:04 (26.6 MB/s) - '/tmp/tmp.6rBUe36m2h' saved [1832972/1832972] /tmp/tmp.6rBUe36m2h: FAILED md5sum: WARNING: 1 computed checksum did NOT match Warning: Failed to download micro:bit MicroPython runtime. Please run "dpkg-reconfigure firmware-microbit-micropython-dl" again when networking is up, or download the file manually: URL: https://raw.githubusercontent.com/ntoll/uflash/master/firmware.hex File: /usr/share/firmware-microbit-micropython/firmware.hex dpkg: error processing package firmware-microbit-micropython-dl (--configure): installed firmware-microbit-micropython-dl package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.31-13) ... Processing triggers for ca-certificates (20210119) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Errors were encountered while processing: firmware-microbit-micropython-dl (at the time of reporting this bug, the downloaded file has size 1832972 and md5sum d6f85e0f84b62e67fc18907c1a8920b9) cheers, Andreas firmware-microbit-micropython-dl_1.2.4+dfsg-7.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-uflash Source-Version: 1.2.4+dfsg-8 Done: Nick Morrott We believe that the bug you reported is fixed in the latest version of python-uflash, 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 991...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nick Morrott (supplier of updated python-uflash 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: Fri, 30 Jul 2021 04:26:04 +0100 Source: python-uflash Architecture: source Version: 1.2.4+dfsg-8 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Nick Morrott Closes: 991280 Changes: python-uflash (1.2.4+dfsg-8) unstable; urgency=medium . * d/firmware-microbit-micropython-dl.postinst: - Update firmware URL (Closes: #991280) Checksums-Sha1: fdaa54b0bb48f01d86fde16069497962dad64f84 2414 python-uflash_1.2.4+dfsg-8.dsc 1fff10a950b59266719e6ed430668d2112b162bc 9140 python-uflash_1.2.4+dfsg-8.debian.tar.xz 0c921e786e0de6349f7de1064b8f710e6f37e127 9029 python-uflash_1.2.4+dfsg-8_amd64.buildinfo Checksums-Sha256: 5f66d1875f00c8307f53e6425c04aade6ec265a0dd6507a82a08935c17f88482 2414 python-uflash_1.2.4+dfsg-8.dsc fae41f49568e84edf53c0b33995c143653900c13eee49f474f1cb181f97bb8ff 9140 python-uflash_1.2.4+dfsg-8.debian.tar.xz
Processed: Re: Bug#991613: DHCPv6 problem in our image: needs "-D LL" when spawning dhclient
Processing control commands: > severity -1 important Bug #991613 [cloud.debian.org] DHCPv6 problem in our image: needs "-D LL" when spawning dhclient Severity set to 'important' from 'serious' -- 991613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991613: DHCPv6 problem in our image: needs "-D LL" when spawning dhclient
Control: severity -1 important Please see https://www.debian.org/Bugs/Developer#severities On Wed, Jul 28, 2021 at 05:22:43PM +0200, Thomas Goirand wrote: > After spawning a VM, it takes a long time to get networking (output from > the console): > > cloud-init[281]: Cloud-init v. 20.2 running 'init-local' at Wed, 28 Jul 2021 > 07:49:23 +. Up 2.98 seconds. > Started [0;1;39mInitial cloud-init job (pre-networking). > Reached target [0;1;39mNetwork (Pre). > Starting [0;1;39mRaise network interfaces... > A start job is running for Raise network interfaces (6s / 5min 1s) > A start job is running for Raise network interfaces (7s / 5min 1s) > A start job is running for Raise network interfaces (7s / 5min 1s) > [...] > A start job is running for Raise ne���ork interfaces (5min 1s / 5min 1s) > Failed to start Raise network interfaces. > > A systemctl status networking.service shows: > >Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor > preset: enabled) >Active: failed (Result: timeout) since Wed 2021-07-28 07:54:23 UTC; 52min > ago > > This is specific to the Debian image. We've compared with Ubuntu 21.04. It seems specific to the OpenStack image. Which OpenStack images are you testing? The FAI-generated images or the others? > Ubuntu: > - Initial boot: > 2021-07-28T11:58:50.836457+00:00 pub1-network-3 dnsmasq-dhcp[3765807]: > DHCPSOLICIT(tap67fa8c3f-8d) 00:02:00:00:ab:11:11:16:f0:97:0e:c5:c9:b6 > 2021-07-28T11:58:50.836724+00:00 pub1-network-3 dnsmasq-dhcp[3765807]: > DHCPREPLY(tap67fa8c3f-8d) ::3ba > 00:02:00:00:ab:11:11:16:f0:97:0e:c5:c9:b6 host---3ba > > - Server side: > /var/lib/neutron/dhcp/dcf25c41-9057-4bc2-8475-a2e3c5d8c662/host:fa:16:3e:63:54:8c,tag:dhcpv6,host---3ba.dc3-a.pub1.infomaniak.cloud.,[::3ba] > /var/lib/neutron/dhcp/dcf25c41-9057-4bc2-8475-a2e3c5d8c662/leases:1627559930 > 3042863103 ::3ba /host---3ba > 00:02:00:00:ab:11:11:16:f0:97:0e:c5:c9:b6 > > Then we do "openstack server rebuild" and get the same result. What exactly are the semantics of "openstack server rebuild"? Is the rebuilt host expected to be identical to the original? > Debian: > - Intial boot: > 2021-07-28T11:59:15.838131+00:00 pub1-network-3 dnsmasq-dhcp[3765807]: > DHCPSOLICIT(tap67fa8c3f-8d) 00:01:00:01:28:94:03:11:fa:16:3e:f1:a9:da > 2021-07-28T11:59:15.838369+00:00 pub1-network-3 dnsmasq-dhcp[3765807]: > DHCPADVERTISE(tap67fa8c3f-8d) ::143 > 00:01:00:01:28:94:03:11:fa:16:3e:f1:a9:da host---143 > 2021-07-28T11:59:16.795826+00:00 pub1-network-3 dnsmasq-dhcp[3765807]: > DHCPREQUEST(tap67fa8c3f-8d) 00:01:00:01:28:94:03:11:fa:16:3e:f1:a9:da > 2021-07-28T11:59:16.796177+00:00 pub1-network-3 dnsmasq-dhcp[3765807]: > DHCPREPLY(tap67fa8c3f-8d) ::143 > 00:01:00:01:28:94:03:11:fa:16:3e:f1:a9:da host---143 These logs are coming from dnsmasq, not dhclient, which isn't installed on the FAI-generated images, so I guess you're talking about the images generated from openstack-debian-images? Do our FAI generated images exhibit similar symptoms in the same environment? > So here, we probably need to get ifupdown to use the -D LL option > explicitely, but I'm not sure how to do this... Does ifupdown even has > an option for forcing that? It doesn't seem to be the case. :/ > > Any help or comment would be welcome. A host (VM or physical) would only normally generate a DUID once, on initial launch. It shouldn't really matter which mechanism it uses to choose one except for the purposes of disambiguation in the event of interface reuse across installations. I think we need more details on exactly what software is involved and exactly what issue is wrong. The FAI-generated images use dhclient for DHCPv6 autoconfiguration on Amazon EC2 today, and have for a long time now, without exhibiting any of the symptoms you're describing. noah
Processed: bug 991656 is forwarded to https://github.com/visionmedia/superagent/pull/1633
Processing commands for cont...@bugs.debian.org:
> forwarded 991656 https://github.com/visionmedia/superagent/pull/1633
Bug #991656 {Done: Yadd } [src:node-superagent] Unknown
browser query `> 1%`. Maybe you are using
Set Bug forwarded-to-address to
'https://github.com/visionmedia/superagent/pull/1633'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
991656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#989296 marked as pending in gdcm
Processing control commands: > tag -1 pending Bug #989296 [libgdcm-dev] missing dependencies and wrong path in the .cmake file Added tag(s) pending. -- 989296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989296: marked as pending in gdcm
Control: tag -1 pending Hello, Bug #989296 in gdcm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/gdcm/-/commit/92bee7344b774b45b66185ed17b040f12fe31c43 d/rules: adjust GDCMTargets*.cmake Some files are reaffected on the fly by multiarchitecture support, pybuild, and possibly other scripts, after .cmake files are generated. This causes various inconsistencies with the names of libraries, between what is recorded in GDCMTargets*.cmake, and what is effectively present in the file system. This addresses the second point of #989296, the first point being the missing dependencies to libgdcm-dev. Closes: #989296 (this message was generated automatically) -- Greetings https://bugs.debian.org/989296
Bug#991649: libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Control: tag -1 confirmed Control: tag -1 patch Hi Lucas, Lucas Nussbaum, on 2021-07-29: > > # Failed test at t/examples.t line 42. > > # got: '' > > # expected: 'lang=en-US' > > # Looks like you failed 1 test of 2. > > > > # Failed test 'expiration' > > # at t/examples.t line 45. > > # Looks like you failed 1 test of 6. I confirm I can reproduce the issue on my end. Looking around line 42 in the corresponding source code, I see an overdue expiration date suspiciously close to nowadays: 41:$jar->add( $req, "lang=en-US; Expires=Wed, 09 Jun 2021 10:18:14 GMT" ); ^ 42:is( $jar->cookie_header($req), "lang=en-US" ); If postpone expiration by say ten years, the test passes for me. I see if I can upload something today… Thanks for your extensive testings! Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Processed: Re: Bug#991652: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2
Processing control commands: > tags -1 upstream Bug #991652 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2 Added tag(s) upstream. > forwarded -1 Pjotr Prins Bug #991652 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2 Set Bug forwarded-to-address to 'Pjotr Prins '. -- 991652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991501: linux-image-5.10.0-8-amd64: amdgpu does not let Graphics Card enter low power state, HIGH idle powerconsumption
Hi, On Mon, Jul 26, 2021 at 04:03:59PM -0400, John Franklin wrote: > Package: src:linux > Version: 5.10.46-2 > Followup-For: Bug #991501 > > I'm affected by this bug in 5.10.46-2. The 5.10.46-1 version of this package > (linux-image-5.10.0-7-amd64) does not seem to have this bug. I guess you mean 5.10.40-1 in the above? 5.10.46-3 contains a fix for this issue. It was uploaded to unstable and should enter testing tomorrow. Regards, Salvatore
Bug#991656: marked as done (Unknown browser query `> 1%`. Maybe you are using)
Your message dated Thu, 29 Jul 2021 20:33:41 +
with message-id
and subject line Bug#991656: fixed in node-superagent 6.1.0-4
has caused the Debian Bug report #991656,
regarding Unknown browser query `> 1%`. Maybe you are using
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.)
--
991656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 '/<>'
> 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] /<>/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 ()
> 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 () {
> 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.
--- End Message ---
--- Begin Message ---
Source: node-superagent
Source-Version: 6.1.0-4
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-superagent, 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 991...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-superagent 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: Thu, 29 Jul 2021 22:01:16 +0200
Source: node-superagent
Architecture: source
Version: 6.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 991656
Changes:
node-superagent (6.1.0-4) unstable; urgency=medium
.
[ Yadd ]
* Fix GitHub tags regex
* Uploaders: replace Leo Iannacone by myself, thanks for your work!
.
[ Pirate Praveen ]
* Drop browsers option in .lib.babelrc file (Closes: #991656)
Checksums-Sha1:
3b2c7f717fd09295edd557edec744b6d78390e0f 2690 node-superagent_6.1.0-4.dsc
d1e9c99f4ded50beae1c1a7cc31d1d02064f9d20 137900
node-superagent_6.1.0-4.debian.tar.xz
Checksums-Sha256:
980f5599c8579f9bc7feb90096149e73e9cd79678a9678324e14b55c3365d46f 2690
node-superagent_6.1.0-4.dsc
50e7578c74bbc30e32532480a8c7b5bf0e3e0a521e638b8c2bb7cc562b27a57e 137900
node-superagent_6.1.0-4.debian.tar.xz
Files:
a44d336dcd6a288dffa27dad4d88394a 2690 javascript optional
node-superagent_6.1.0-4.dsc
Processed: tagging 991386
Processing commands for cont...@bugs.debian.org: > # can be fixed later via a DSA > tags 991386 + bullseye-ignore Bug #991386 [src:ublock-origin] ublock-origin: CVE-2021-36773: Denial of Service Added tag(s) bullseye-ignore. > tags 991593 + bullseye-ignore Bug #991593 [src:otrs2] otrs2: CVE-2021-36092 CVE-2021-36091 CVE-2021-21443 CVE-2021-21440 Added tag(s) bullseye-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 991386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991386 991593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991656: marked as pending in node-superagent
Control: tag -1 pending Hello, Bug #991656 in node-superagent reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-superagent/-/commit/7dc940b6e2725131641ed80af714dc464f38d8d2 Closes: #991656 (this message was generated automatically) -- Greetings https://bugs.debian.org/991656
Processed: Bug#991656 marked as pending in node-superagent
Processing control commands: > tag -1 pending Bug #991656 [src:node-superagent] Unknown browser query `> 1%`. Maybe you are using Added tag(s) pending. -- 991656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bullseye-ignore
Processing commands for cont...@bugs.debian.org: > # We're getting very close to the bullseye release. Although we'd > # (still) love to have these bugs fixed, let's focus on what absolutely > # needs fixing. > # I'm considering adding a release-notes section about some/most of > # these bugs > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was elb...@debian.org). > tag 924151 bullseye-ignore Bug #924151 [grub2-common] grub2-common: wrong grub.cfg for efi boot and fully encrypted disk Bug #926689 [grub2-common] cryptsetup-initramfs: config lines in grub.cfg for cryptodisk/luks and other modules missing Added tag(s) bullseye-ignore. Added tag(s) bullseye-ignore. > tag 558422 bullseye-ignore Bug #558422 [grub-pc] grub-pc: upgrade hangs Added tag(s) bullseye-ignore. > tag 897975 bullseye-ignore Bug #897975 [gdm3] gdm3: restarts in a loop: IceLockAuthFile fail: Already exists (race condition?) Added tag(s) bullseye-ignore. > tag 948318 bullseye-ignore Bug #948318 [openssh-server] openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2 Added tag(s) bullseye-ignore. > usertag 948318 bullseye-release-notes Usertags were: bullseye-can-defer. Usertags are now: bullseye-release-notes bullseye-can-defer. > tag 859926 bullseye-ignore Bug #859926 [speech-dispatcher] breaks with pulse-audio as output when spawned by speechd-up from init system Added tag(s) bullseye-ignore. > usertag 859926 bullseye-release-notes Usertags were: bullseye-can-defer stretch-can-defer. Usertags are now: bullseye-release-notes bullseye-can-defer stretch-can-defer. > tag 948739 bullseye-ignore Bug #948739 [gparted] gparted should not mask .mount units Added tag(s) bullseye-ignore. > usertag 948739 bullseye-release-notes Usertags were: bullseye-can-defer. Usertags are now: bullseye-can-defer bullseye-release-notes. > tag 975931 bullseye-ignore Bug #975931 [libllvm11] libllvm11: libgpuarray autopkgtest using pocl on armhf triggers segfault Added tag(s) bullseye-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 558422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558422 859926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859926 897975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897975 924151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924151 926689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926689 948318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948318 948739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948739 975931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: node-superagent: FTBFS: Browserslist: caniuse-lite isoutdated. Please run: npx browserslist@latest --update-db
Processing control commands: > tags -1 patch Bug #991656 [src:node-superagent] Unknown browser query `> 1%`. Maybe you are using Added tag(s) patch. -- 991656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: twitter-bootstrap4: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db
Processing control commands: > retitle -1 FTBFS: Replace Autoprefixer browsers option to Bug #991651 [src:twitter-bootstrap4] twitter-bootstrap4: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db Changed Bug title to 'FTBFS: Replace Autoprefixer browsers option to' from 'twitter-bootstrap4: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db'. -- 991651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991651: twitter-bootstrap4: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db
Control: retitle -1 FTBFS: Replace Autoprefixer browsers option to Browserslist config On Thu, 29 Jul 2021 17:19:34 +0200 Lucas Nussbaum wrote: > Source: twitter-bootstrap4 > Version: 4.5.2+dfsg1-6 > 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 '/<>' > > mkdir -p dist/css dist/js dist/tmp > > sassc --sourcemap=auto scss/bootstrap.scss dist/tmp/bootstrap.css > > sassc --sourcemap=auto scss/bootstrap-grid.scss dist/tmp/bootstrap-grid.css > > sassc --sourcemap=auto scss/bootstrap-reboot.scss dist/tmp/bootstrap-reboot.css > > node debian/postcss.js > > > > Replace Autoprefixer browsers option to Browserslist config. > > Use browserslist key in package.json or .browserslistrc file. > > > > Using browsers option can cause errors. Browserslist config can > > be used for Babel, Autoprefixer, postcss-normalize and other tools. > > > > If you really need to use option, rename it to overrideBrowserslist. > > > > Learn more at: > > https://github.com/browserslist/browserslist#readme > > https://twitter.com/browserslist Dropping this line should fix the bug I think, https://salsa.debian.org/js-team/twitter-bootstrap4/-/blob/master/debian/postcss.js#L28 It already ships a .browserslistrc file https://salsa.debian.org/js-team/twitter-bootstrap4/-/blob/master/.browserslistrc
Bug#991656: node-superagent: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db
Control: retitle -1 Unknown browser query `> 1%`. Maybe you are using
old Browserslist or made typo in query.
On Thu, 29 Jul 2021 17:14:42 +0200 Lucas Nussbaum
wrote:
> 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 '/<>'
> > 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]
/<>/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")
The actual error that caused failure is,
Unknown browser query `> 1%`. Maybe you are using old Browserslist or
made typo in query.
This patch fixes the build failure, .browserslistrc already has these
values and babel-preset-env recommends using this option as per
https://babeljs.io/docs/en/babel-preset-env#browserslist-integration
--- a/.lib.babelrc
+++ b/.lib.babelrc
@@ -2,8 +2,7 @@
"presets": [
["@babel/env", {
"targets": {
- "node": "6.4.0",
- "browsers": [ "> 1%", "last 2 versions", "ie 9" ]
+ "node": "6.4.0"
}
}]
],
But later down in the same doc it says,
By default @babel/preset-env will use browserslist config sources
unless either the targets or ignoreBrowserslistConfig options are set.
and we have targets option set here. One option would be to drop
targets entirely as we need to support only the nodejs version shipped
with debian.
Processed: Re: node-superagent: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db
Processing control commands: > retitle -1 Unknown browser query `> 1%`. Maybe you are using Bug #991656 [src:node-superagent] node-superagent: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db Changed Bug title to 'Unknown browser query `> 1%`. Maybe you are using' from 'node-superagent: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db'. -- 991656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991501: linux-image-5.10.0-8-amd64: amdgpu does not let Graphics Card enter low power state, HIGH idle powerconsumption
Package: src:linux Version: 5.10.46-2 Followup-For: Bug #991501 I'm affected by this bug in 5.10.46-2. The 5.10.46-1 version of this package (linux-image-5.10.0-7-amd64) does not seem to have this bug. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20XK0019US product_version: ThinkPad T14 Gen 2a chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: R1MET35W (1.05 ) board_vendor: LENOVO board_name: 20XK0019US board_version: Not Defined ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630] Subsystem: Lenovo Renoir Root Complex [17aa:5094] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.7 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51) Subsystem: Lenovo FCH SMBus Controller [17aa:5094] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nvme Kernel modules: nvme 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0e) Subsystem: Lenovo RTL8111/8168/8411
Bug#991654: marked as done (astropy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Thu, 29 Jul 2021 18:03:29 +
with message-id
and subject line Bug#991654: fixed in astropy 4.2-6
has caused the Debian Bug report #991654,
regarding astropy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
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.)
--
991654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astropy
Version: 4.2-5
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 '/<>'
> dh_auto_test
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.9.2, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
> Matplotlib: 3.3.4
> Freetype: 2.10.4
>
> Running tests with Astropy version 4.2.
> Running tests in .pybuild/cpython3_3.9/build.
>
> Date: 2021-07-29T06:19:49
>
> Platform: Linux-4.19.0-6-cloud-amd64-x86_64-with-glibc2.31
>
> Executable: /usr/bin/python3.9
>
> Full Python Version:
> 3.9.2 (default, Feb 28 2021, 17:03:44)
> [GCC 10.2.1 20210110]
>
> encodings: sys: utf-8, locale: UTF-8, filesystem: utf-8
> byteorder: little
> float info: dig: 15, mant_dig: 15
>
> Package versions:
> Numpy: 1.19.5
> Scipy: 1.6.0
> Matplotlib: 3.3.4
> h5py: 2.10.0
> Pandas: not available
> PyERFA: 1.7.2
>
> Using Astropy options: remote_data: none.
>
> rootdir: /<>, configfile: setup.cfg
> plugins: openfiles-0.5.0, doctestplus-0.9.0, filter-subpackage-0.1.1,
> mpl-0.11, astropy-header-0.1.2, cov-2.10.1, hypothesis-5.43.3, arraydiff-0.3,
> remotedata-0.3.2
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File
> "/<>/.pybuild/cpython3_3.9/build/astropy/time/core.py", line
> 2665, in update_leap_seconds
> INTERNALERROR> table = iers.LeapSeconds.auto_open(files)
> INTERNALERROR> File
> "/<>/.pybuild/cpython3_3.9/build/astropy/utils/iers/iers.py",
> line 1018, in auto_open
> INTERNALERROR> warn('leap-second file is expired.', IERSStaleWarning)
> INTERNALERROR> astropy.utils.iers.iers.IERSStaleWarning: leap-second file is
> expired.
> INTERNALERROR>
> INTERNALERROR> During handling of the above exception, another exception
> occurred:
> INTERNALERROR>
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line
> 240, in wrap_session
> INTERNALERROR> session.exitstatus = doit(config, session) or 0
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line
> 295, in _main
> INTERNALERROR> config.hook.pytest_collection(session=session)
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line
> 286, in __call__
> INTERNALERROR> return self._hookexec(self, self.get_hookimpls(), kwargs)
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/manager.py",
> line 92, in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/manager.py",
> line 83, in
> INTERNALERROR> self._inner_hookexec = lambda hook, methods, kwargs:
> hook.multicall(
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/callers.py",
> line 208, in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/callers.py",
> line 80, in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/callers.py",
> line 182, in _multicall
> INTERNALERROR> next(gen) # first yield
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/warnings.py",
> line 169, in pytest_collection
> INTERNALERROR> with catch_warnings_for_item(
> INTERNALERROR> File "/usr/lib/python3.9/contextlib.py", line 117, in
> __enter__
> INTERNALERROR> return next(self.gen)
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/warnings.py",
> line 113, in catch_warnings_for_item
> INTERNALERROR> warnings.filterwarnings(*_parse_filter(arg, escape=False))
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/warnings.py",
> line 39, in _parse_filter
> INTERNALERROR> category = warnings._getcategory(
> INTERNALERROR> File
Bug#991649: marked as done (libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Thu, 29 Jul 2021 18:03:35 + with message-id and subject line Bug#991649: fixed in libhttp-cookiejar-perl 0.010-2 has caused the Debian Bug report #991649, regarding libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 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.) -- 991649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libhttp-cookiejar-perl Version: 0.010-1 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 '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > # > # Versions for all modules listed in MYMETA.json (including optional ones): > # > # === Configure Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker 6.17 7.44 > # > # === Build Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # > # === Test Requires === > # > # ModuleWant Have > # --- -- > # ExtUtils::MakeMakerany 7.44 > # File::Spec any 3.78 > # Test::Deep any1.130 > # Test::More0.96 1.302175 > # Test::Requires any 0.11 > # Time::Local 1.1901 1.28 > # URIany 5.08 > # libany 0.65 > # > # === Test Recommends === > # > # Module Want Have > # -- > # CPAN::Meta 2.120900 2.150010 > # > # === Runtime Requires === > # > # ModuleWant Have > # --- -- - > # Carp any 1.50 > # HTTP::Date any 6.05 > # Time::Local 1.1901 1.28 > # parent any 0.238 > # strict any 1.11 > # warnings any 1.47 > # > # === Runtime Recommends === > # > # ModuleWantHave > # - --- > # Mozilla::PublicSuffix any missing > # > t/00-report-prereqs.t .. > 1..1 > ok 1 - Reported prereqs > ok > t/add.t > ok 1 - no cookies > ok 2 - simple key=value > ok 3 - invalid cookie not stored > ok 4 - localhost treated as host only > ok 5 - single domain level treated as host only > ok 6 - different domain not stored > ok 7 - subdomain not stored > ok 8 - superdomain stored > ok 9 - path prefix /foo/ stored > ok 10 - path prefix /foo stored > ok 11 - last cookie wins > ok 12 - expired supercedes prior > ok 13 - separated by path > ok 14 - max-age supercedes expires > 1..14 > ok > > # Failed test at t/examples.t line 42. > # got: '' > # expected: 'lang=en-US' > # Looks like you failed 1 test of 2. > > # Failed test 'expiration' > # at t/examples.t line 45. > # Looks like you failed 1 test of 6. > t/examples.t ... > ok 1 - An object of class 'HTTP::CookieJar' isa 'HTTP::CookieJar' > # Subtest: just key & value > ok 1 > 1..1 > ok 2 - just key & value > # Subtest: secure > ok 1 > ok 2 > 1..2 > ok 3 - secure > # Subtest: not a subdomain > ok 1 > 1..1 > ok 4 - not a subdomain > # Subtest: wrong path > ok 1 > 1..1 > ok 5 - wrong path > # Subtest: expiration > not ok 1 > ok 2 > 1..2 > not ok 6 - expiration > 1..6 > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/6 subtests > t/parse.t .. > ok 1 - '' > ok 2 - SID= > ok 3 - =31d4d96e407aad42 > ok 4 - ; Max-Age: 1360343635 > ok 5 - SID=31d4d96e407aad42 > ok 6 - SID=ID=31d4d96e407aad42 > ok 7 - SID=31d4d96e407aad42 ; ; ; > ok 8 - SID=31d4d96e407aad42; Path=/; Secure; HttpOnly > ok 9 - SID=31d4d96e407aad42; Domain=.example.com > ok 10 - SID=31d4d96e407aad42; Path=/; Domain=example.com > ok 11 - SID=31d4d96e407aad42; Path=/; Domain= > ok 12 - lang=en-US; Expires = Wed, 09 Jun 2021 10:18:14 GMT > ok 13 - lang=en-US; Expires = Wed, 09 Jun 2021 10:18:14 GMT; Max-Age=3600 > 1..13 > ok > t/publicsuffix.t ... skipped: Test requires module > 'Mozilla::PublicSuffix' but it's not found > t/save.t ... > # Subtest: empty cookie jar > ok 1 - dumped zero
Bug#987321: marked as done (openntpd: if-up.d script uses SysV command instead of systemd and blocks boot)
Your message dated Thu, 29 Jul 2021 18:03:41 +
with message-id
and subject line Bug#987321: fixed in openntpd 1:6.2p3-4.2
has caused the Debian Bug report #987321,
regarding openntpd: if-up.d script uses SysV command instead of systemd and
blocks boot
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.)
--
987321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openntpd
Version: 1:6.2p3-4.1
Severity: important
Dear Maintainer,
openntpd installs a smart if-up.d script to reload the configuration
when an interface is started. It blocks the boot process until a timeout
occurs at the "Raise network interfaces" step.
I noticed an "invoke-rc.d force-reload" in the script. this force-reload
is supported by SysV scripts, but not by SystemD scripts, according to
the doc. I changed the "force-reload" to a simple 'reload', and the boot
process is not blocked anymore.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages openntpd depends on:
ii adduser 3.118
ii libc6 2.31-11
ii lsb-base 11.1.0
ii netbase 6.3
openntpd recommends no packages.
Versions of packages openntpd suggests:
ii apparmor 2.13.6-10
-- Configuration Files:
/etc/apparmor.d/usr.sbin.ntpd changed:
/usr/sbin/ntpd flags=(attach_disconnected) {
#include
#include
# conf
/etc/openntpd/ntpd.conf r,
# capabilities
capability kill,
capability sys_chroot,
capability setgid,
capability setuid,
capability sys_time,
capability sys_nice,
/usr/sbin/ntpd mrix,
/var/lib/openntpd/db/ntpd.drift rw,
/var/lib/openntpd/run/ntpd.sock rw,
/run/openntpd.pid rw,
}
/etc/default/openntpd changed:
DAEMON_OPTS="-f /etc/openntpd/ntpd.conf -p /var/run/openntpd.pid"
/etc/network/if-up.d/openntpd changed:
CONFIG="/etc/openntpd/ntpd.conf"
if [ "${METHOD}"X = "loopback"X ] || [ "${METHOD}"X = "none"X ]
then
exit 0
fi
invoke-rc.d openntpd reload || true
/etc/openntpd/ntpd.conf changed:
listen on 127.0.0.1
servers 0.debian.pool.ntp.org
servers 1.debian.pool.ntp.org
servers 2.debian.pool.ntp.org
servers 3.debian.pool.ntp.org
-- no debconf information
--
François - 21 rue d'Eaubonne - 95580 Margency
Free : +33 6 03 01 55 12
http://www.cerbelle.net
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: openntpd
Source-Version: 1:6.2p3-4.2
Done: Baptiste Beauplat
We believe that the bug you reported is fixed in the latest version of
openntpd, 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 987...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Baptiste Beauplat (supplier of updated openntpd 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: SHA256
Format: 1.8
Date: Sun, 25 Jul 2021 14:37:54 +0200
Source: openntpd
Architecture: source
Version: 1:6.2p3-4.2
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli
Changed-By: Baptiste Beauplat
Closes: 987321
Changes:
openntpd (1:6.2p3-4.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Ensure that openntpd is running before restarting it from the if-up.d
hook. (Closes: #987321)
Checksums-Sha1:
3ea4a25a464bebdc9b0b649ac0e5815ebaf41460 1340 openntpd_6.2p3-4.2.dsc
f4783d1afadaaf36cb4a02bd9bc66186c6020bf7 15824 openntpd_6.2p3-4.2.debian.tar.xz
b9355c081ac65877e726a988253605ab0386d946 5612
openntpd_6.2p3-4.2_amd64.buildinfo
Checksums-Sha256:
4fc79739c79be2443a0176263b6396a87b12f82b10ff810fab8583a4a18fc1f2 1340
openntpd_6.2p3-4.2.dsc
22611a48d5ab0bd715dc3dc94457e959b0245bea2ac1dab2c699c7ea4c36e06f 15824
openntpd_6.2p3-4.2.debian.tar.xz
317f30b4398d1faaf81cfd0452b3aa041143beb681be34888c9f90a6cd7c3988 5612
Processed: apparently the issue has already been fixed upstream
Processing commands for cont...@bugs.debian.org: > # This turned out to be already spotted upstream, not surpising though. > forwarded 991649 https://github.com/dagolden/HTTP-CookieJar/issues/11 Bug #991649 [src:libhttp-cookiejar-perl] libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/dagolden/HTTP-CookieJar/issues/11'. > tag 991649 upstream Bug #991649 [src:libhttp-cookiejar-perl] libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) upstream. > thank you Stopping processing here. Please contact me if you need assistance. -- 991649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#987321: openntpd: if-up.d script uses SysV command instead of systemd and blocks boot
Processing control commands: > tags -1 + pending Bug #987321 [openntpd] openntpd: if-up.d script uses SysV command instead of systemd and blocks boot Added tag(s) pending. -- 987321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987321: openntpd: if-up.d script uses SysV command instead of systemd and blocks boot
Control: tags -1 + pending Ended-up uploading to DELAY/0. After a quick exchange on IRC #debian-release, asking for pre-approval for a targeted RC fix is a waste of time for the release team. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Processed: Bug#991654 marked as pending in astropy
Processing control commands:
> tag -1 pending
Bug #991654 [src:astropy] astropy: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.
--
991654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#991654: marked as pending in astropy
Control: tag -1 pending Hello, Bug #991654 in astropy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-astro-team/astropy/-/commit/f855be52ed6196e3efd680de488d3572f43a569f Ignore IERSStaleWarning in pytest This may happen when the tzdata file is too old, f.e. within a long freeze. Closes: #991654 (this message was generated automatically) -- Greetings https://bugs.debian.org/991654
Processed: Bug#991649 marked as pending in libhttp-cookiejar-perl
Processing control commands: > tag -1 pending Bug #991649 [src:libhttp-cookiejar-perl] libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 991649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991649: marked as pending in libhttp-cookiejar-perl
Control: tag -1 pending Hello, Bug #991649 in libhttp-cookiejar-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libhttp-cookiejar-perl/-/commit/ca4b0210b7758f991fc65da36cc5b33cbfcd841d add postpone-test-expiry.patch from David Golden Closes: #991649 (this message was generated automatically) -- Greetings https://bugs.debian.org/991649
Processed: Re: Bug#991649: libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Processing control commands: > tag -1 confirmed Bug #991649 [src:libhttp-cookiejar-perl] libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) confirmed. > tag -1 patch Bug #991649 [src:libhttp-cookiejar-perl] libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) patch. -- 991649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991651: [Pkg-javascript-devel] Bug#991651: twitter-bootstrap4: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db
Le 29/07/2021 à 17:19, Lucas Nussbaum a écrit : > Source: twitter-bootstrap4 > Version: 4.5.2+dfsg1-6 > 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 '/<>' >> mkdir -p dist/css dist/js dist/tmp >> sassc --sourcemap=auto scss/bootstrap.scss dist/tmp/bootstrap.css >> sassc --sourcemap=auto scss/bootstrap-grid.scss dist/tmp/bootstrap-grid.css >> sassc --sourcemap=auto scss/bootstrap-reboot.scss >> dist/tmp/bootstrap-reboot.css >> node debian/postcss.js Looks to be a postcss bug. @praveen: could you confirm?
Bug#989103: closed by Felipe Sateler (DMO is not supported)
On Thu, Jul 29, 2021 at 12:57:03PM +, Debian Bug Tracking System wrote: > Date: Thu, 29 Jul 2021 08:51:50 -0400 > From: Felipe Sateler > To: 989103-d...@bugs.debian.org, 991337-d...@bugs.debian.org > Subject: DMO is not supported > > deb-multimedia.org is not supported here. Please ask the maintainers of > that repository for support. Closing the bug. The bug is in bullseye package. I'm not sure where deb-multimedia came from? (It's not enabled in my sources.list) Best Regards Michał Mirosław
Processed: tagging 990488
Processing commands for cont...@bugs.debian.org: > tags 990488 + pending Bug #990488 [statsvn] statsvn: Package in stable does not work Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 990488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989878: marked as done (openstack-dashboard: fails to remove: rm: cannot remove '/usr/lib/python3/dist-packages/openstack_dashboard/local/enabled': Is a directory)
Your message dated Thu, 29 Jul 2021 15:49:27 + with message-id and subject line Bug#989878: fixed in horizon 3:19.2.0-4 has caused the Debian Bug report #989878, regarding openstack-dashboard: fails to remove: rm: cannot remove '/usr/lib/python3/dist-packages/openstack_dashboard/local/enabled': 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.) -- 989878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openstack-dashboard Version: 3:19.2.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing openstack-dashboard (3:19.2.0-3) ... rm: cannot remove '/usr/lib/python3/dist-packages/openstack_dashboard/local/enabled': Is a directory dpkg: error processing package openstack-dashboard (--remove): installed openstack-dashboard package pre-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: openstack-dashboard Processing was halted because there were too many errors. This was observed after an upgrade from sid to experimental. cheers, Andreas openstack-dashboard_3:19.2.0-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: horizon Source-Version: 3:19.2.0-4 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of horizon, 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 989...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated horizon 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: SHA256 Format: 1.8 Date: Mon, 28 Jun 2021 10:39:33 +0200 Source: horizon Architecture: source Version: 3:19.2.0-4 Distribution: experimental Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 989878 Changes: horizon (3:19.2.0-4) experimental; urgency=medium . * Fix handling of openstack_dashboard/local/enabled in prerm of openstack-dashboard (Closes: #989878). * Build the doc in the override_dh_auto_build: target. * Add patches: - Dont_load_user_role_assignment_or_groups_tabs_for_non-admins.patch - do-not-create-volume-by-default-when-launching-instance.patch Checksums-Sha1: 6a52ccee717cec1f37716e8353e5737d71ae6b6d 4309 horizon_19.2.0-4.dsc 0f4d32f385385ab5b739b1cfeba89d0656b72877 30580 horizon_19.2.0-4.debian.tar.xz 06544dcbd49c891d9e050540febae8e08bf2b27e 16955 horizon_19.2.0-4_amd64.buildinfo Checksums-Sha256: 2805d153b6b93c3c3fe6350a4790f50db30f6915d6fcd277419030039009c874 4309 horizon_19.2.0-4.dsc 363dd187535841fe3f5fe6287f74059f270728c7c44ddd6a6a3b7c37f5fe06df 30580 horizon_19.2.0-4.debian.tar.xz 915315ba999cbdc0028b6e9c89368604468b0d256a4ab54c46829085768a96dd 16955 horizon_19.2.0-4_amd64.buildinfo Files: ba961c0ca3d0282c391508e71e983bfc 4309 net optional horizon_19.2.0-4.dsc e38c14d947133a4045bb5a11d0035a94 30580 net optional horizon_19.2.0-4.debian.tar.xz f9a354ec80ec3bf855cdbfdec6766f2f 16955 net optional horizon_19.2.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmECy2kACgkQ1BatFaxr Q/4u8g//bMZeMQOnqRCAajwVd7+aVCoMa5Hu0v93K3SxdO2rSGWjh820qoQgMeqS 6AStbya+4+kJHtL6nuMbrCif9KMvy9pbsfItNO4wKG9MWPtIQkPDU4bcUsdcxWjB pr99I9MRpEbF/RDq08aAPYutt3DUAjTyOe1Pc6w7zHxyU3RphUXgY1/86XKugjdE xNi186zizQ1OhJsRxWiBvxxENgmh25rK4OYtGCPXAp1Arx9au/iJB3LD7sXcEMVC JYA27SOP8o0HYHhXbO/A2C6P++RgJVcq2eO4wl+R8RDXHWVQ2mOEgfU4oQz2sdth OuD98AViPSt0eBXrJ+wGjzuq7lqTJU9x9mMyQXyiY3+zcWp8KzH0Hozp0uuLaJ9V Nx+bTigL/O5ZJOvynQvmy/Vq5JIbBsqwBG98IG/pWonLbAZeA2FhU1UQYiOAkvaa 2mnPaVZyFt89PS054Dix0GDWQKtPWMKS3vGVs8HlDGPrnC9ogGQOTrSY7fpeMFFy UXFAAFNhYbXpbVJ91/Qw6Z8yEfS8LXCMoGE3o5yODp8vXTUCPlfiBqaYPRTZQDq2 QxGkEnus4eYOdH0sjHQ9qLXhQogSFZaDV0HvAT+q4ToGpc+Y/sEHTVRWjjo74m49 Yl5EAY0pT2dT5g/RqDL39dV5Qe0wT5JVle5DMIMfCuPg1pLiaKk= =xZTj -END PGP SIGNATURE End Message ---
Bug#991656: node-superagent: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db
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 '/<>'
> 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] /<>/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 ()
> 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 () {
> 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.
Bug#991655: weresync: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1
Source: weresync Version: 1.0.9-1 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): > fakeroot debian/rules clean > dh clean --with python3,sphinxdoc --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:232: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9/build' (and everything under > it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: warning: cannot import key in > weresync-1.0.9/debian/upstream/signing-key.asc since GnuPG is not installed > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building weresync using existing > ./weresync_1.0.9.orig.tar.gz > dpkg-source: info: building weresync using existing > ./weresync_1.0.9.orig.tar.gz.asc > gpgv: Signature made Thu Jun 28 14:09:30 2018 UTC > gpgv:using RSA key 7F72CC8DA5F377C9 > gpgv: Can't check signature: No public key > dpkg-source: warning: failed to verify signature on > ./weresync_1.0.9.orig.tar.gz.asc > dpkg-source: error: cannot represent change to > src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo: binary file > contents changed > dpkg-source: error: add > src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1 > > Build finished at 2021-07-29T06:17:40Z The full build log is available from: http://qa-logs.debian.net/2021/07/28/weresync_1.0.9-1_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.
Bug#991654: astropy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Source: astropy
Version: 4.2-5
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 '/<>'
> dh_auto_test
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.9.2, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
> Matplotlib: 3.3.4
> Freetype: 2.10.4
>
> Running tests with Astropy version 4.2.
> Running tests in .pybuild/cpython3_3.9/build.
>
> Date: 2021-07-29T06:19:49
>
> Platform: Linux-4.19.0-6-cloud-amd64-x86_64-with-glibc2.31
>
> Executable: /usr/bin/python3.9
>
> Full Python Version:
> 3.9.2 (default, Feb 28 2021, 17:03:44)
> [GCC 10.2.1 20210110]
>
> encodings: sys: utf-8, locale: UTF-8, filesystem: utf-8
> byteorder: little
> float info: dig: 15, mant_dig: 15
>
> Package versions:
> Numpy: 1.19.5
> Scipy: 1.6.0
> Matplotlib: 3.3.4
> h5py: 2.10.0
> Pandas: not available
> PyERFA: 1.7.2
>
> Using Astropy options: remote_data: none.
>
> rootdir: /<>, configfile: setup.cfg
> plugins: openfiles-0.5.0, doctestplus-0.9.0, filter-subpackage-0.1.1,
> mpl-0.11, astropy-header-0.1.2, cov-2.10.1, hypothesis-5.43.3, arraydiff-0.3,
> remotedata-0.3.2
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File
> "/<>/.pybuild/cpython3_3.9/build/astropy/time/core.py", line
> 2665, in update_leap_seconds
> INTERNALERROR> table = iers.LeapSeconds.auto_open(files)
> INTERNALERROR> File
> "/<>/.pybuild/cpython3_3.9/build/astropy/utils/iers/iers.py",
> line 1018, in auto_open
> INTERNALERROR> warn('leap-second file is expired.', IERSStaleWarning)
> INTERNALERROR> astropy.utils.iers.iers.IERSStaleWarning: leap-second file is
> expired.
> INTERNALERROR>
> INTERNALERROR> During handling of the above exception, another exception
> occurred:
> INTERNALERROR>
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line
> 240, in wrap_session
> INTERNALERROR> session.exitstatus = doit(config, session) or 0
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line
> 295, in _main
> INTERNALERROR> config.hook.pytest_collection(session=session)
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line
> 286, in __call__
> INTERNALERROR> return self._hookexec(self, self.get_hookimpls(), kwargs)
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/manager.py",
> line 92, in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/manager.py",
> line 83, in
> INTERNALERROR> self._inner_hookexec = lambda hook, methods, kwargs:
> hook.multicall(
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/callers.py",
> line 208, in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/callers.py",
> line 80, in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/callers.py",
> line 182, in _multicall
> INTERNALERROR> next(gen) # first yield
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/warnings.py",
> line 169, in pytest_collection
> INTERNALERROR> with catch_warnings_for_item(
> INTERNALERROR> File "/usr/lib/python3.9/contextlib.py", line 117, in
> __enter__
> INTERNALERROR> return next(self.gen)
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/warnings.py",
> line 113, in catch_warnings_for_item
> INTERNALERROR> warnings.filterwarnings(*_parse_filter(arg, escape=False))
> INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/warnings.py",
> line 39, in _parse_filter
> INTERNALERROR> category = warnings._getcategory(
> INTERNALERROR> File "/usr/lib/python3.9/warnings.py", line 260, in
> _getcategory
> INTERNALERROR> m = __import__(module, None, None, [klass])
> INTERNALERROR> File
> "/<>/.pybuild/cpython3_3.9/build/astropy/wcs/__init__.py", line
> 26, in
> INTERNALERROR> from .wcs import *
> INTERNALERROR> File
> "/<>/.pybuild/cpython3_3.9/build/astropy/wcs/wcs.py", line 55,
> in
> INTERNALERROR> from .wcsapi.fitswcs import FITSWCSAPIMixin, SlicedFITSWCS
> INTERNALERROR> File
> "/<>/.pybuild/cpython3_3.9/build/astropy/wcs/wcsapi/fitswcs.py",
> line 11, in
> INTERNALERROR> from astropy.coordinates import SpectralCoord, Galactic,
> ICRS
> INTERNALERROR> File
> "/<>/.pybuild/cpython3_3.9/build/astropy/coordinates/__init__.py",
> line 16, in
> INTERNALERROR> from .builtin_frames import *
> INTERNALERROR> File
>
Bug#991653: isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: isoquery Version: 3.2.4-1 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. This sounds like #963371. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p /<>/debian/tmpdir/locale > localedef -i de_DE -f UTF-8 /<>/debian/tmpdir/locale/de_DE.UTF-8 > LOCPATH=/<>/debian/tmpdir/locale LANG=de LC_ALL=de_DE.UTF-8 > dh_auto_test > make -j4 check VERBOSE=1 > make[2]: Verzeichnis „/<>“ wird betreten > Making check in po > make[3]: Verzeichnis „/<>/po“ wird betreten > make[3]: Für das Ziel „check“ ist nichts zu tun. > make[3]: Verzeichnis „/<>/po“ wird verlassen > Making check in src > make[3]: Verzeichnis „/<>/src“ wird betreten > make[3]: Für das Ziel „check“ ist nichts zu tun. > make[3]: Verzeichnis „/<>/src“ wird verlassen > Making check in tests > make[3]: Verzeichnis „/<>/tests“ wird betreten > make check-am > make[4]: Verzeichnis „/<>/tests“ wird betreten > make options integration\ > > make[5]: Verzeichnis „/<>/tests“ wird betreten > gcc -DPACKAGE_NAME=\"isoquery\" -DPACKAGE_TARNAME=\"isoquery\" > -DPACKAGE_VERSION=\"3.2.4\" -DPACKAGE_STRING=\"isoquery\ 3.2.4\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"isoquery\" > -DVERSION=\"3.2.4\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 > -DGETTEXT_PACKAGE=\"isoquery\" -I. -I../src -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/json-glib-1.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o options.o > options.c > gcc -DPACKAGE_NAME=\"isoquery\" -DPACKAGE_TARNAME=\"isoquery\" > -DPACKAGE_VERSION=\"3.2.4\" -DPACKAGE_STRING=\"isoquery\ 3.2.4\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"isoquery\" > -DVERSION=\"3.2.4\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 > -DGETTEXT_PACKAGE=\"isoquery\" -I. -DTESTDIR=\".\" -I../src > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/json-glib-1.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > integration-integration.o `test -f 'integration.c' || echo './'`integration.c > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o integration > integration-integration.o -lglib-2.0 -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 > -lglib-2.0 ../src/options.o > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o options > options.o -lglib-2.0 -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 > ../src/options.o > make[5]: Verzeichnis „/<>/tests“ wird verlassen > make check-TESTS > make[5]: Verzeichnis „/<>/tests“ wird betreten > make[6]: Verzeichnis „/<>/tests“ wird betreten > PASS: options 1 /options/standard_default > PASS: options 2 /options/standard_provided > PASS: options 3 /options/standard_deprecated_639 > PASS: options 4 /options/standard_deprecated_3166 > PASS: options 5 /options/standard_invalid > PASS: options 6 /options/pathname_default > PASS: options 7 /options/pathname_provided > PASS: options 8 /options/pathname_provided_with_dir_separator > PASS: options 9 /options/pathname_from_standard > PASS: options 10 /options/name_default > PASS: options 11 /options/name_name > PASS: options 12 /options/name_official_name > PASS: options 13 /options/name_common_name > PASS: options 14 /options/null_separator > PASS: options 15 /options/invalid_option > PASS: integration 1 /integration/iso_639-2/all_localized > PASS: integration 2 /integration/iso_639-2/all_null_separator > PASS: integration 3 /integration/iso_639-2/all > PASS: integration 4 /integration/iso_639-2/multiple_codes > PASS: integration 5 /integration/iso_639-3/all_localized > PASS: integration 6 /integration/iso_639-3/all_null_separator > PASS: integration 7 /integration/iso_639-3/all > PASS: integration 8 /integration/iso_639-3/multiple_codes > PASS: integration 9 /integration/iso_639-5/all_localized > PASS: integration 10 /integration/iso_639-5/all_null_separator > PASS: integration 11 /integration/iso_639-5/all > PASS: integration 12 /integration/iso_639-5/multiple_codes > PASS: integration 13 /integration/iso_3166-1/all_localized > PASS: integration 14 /integration/iso_3166-1/all_null_separator > PASS: integration 15 /integration/iso_3166-1/all > PASS: integration 16 /integration/iso_3166-1/invalid_codes_localized > PASS: integration 17
Bug#991650: python-django-imagekit: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
Source: python-django-imagekit Version: 4.0.2-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 '/<>' > dh_auto_build > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/registry.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/generatorlibrary.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/lib.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/pkgmeta.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/conf.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/hashers.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/compat.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/admin.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/exceptions.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/signals.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/utils.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > copying imagekit/files.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms > copying imagekit/forms/fields.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms > copying imagekit/forms/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models > copying imagekit/models/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors > copying imagekit/processors/resize.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors > copying imagekit/processors/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors > copying imagekit/processors/crop.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors > copying imagekit/processors/base.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors > copying imagekit/processors/utils.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs > copying imagekit/specs/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs > copying imagekit/specs/sourcegroups.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags > copying imagekit/templatetags/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags > copying imagekit/templatetags/imagekit.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles > copying imagekit/cachefiles/backends.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles > copying imagekit/cachefiles/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles > copying imagekit/cachefiles/strategies.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles > copying imagekit/cachefiles/namers.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/management > copying imagekit/management/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/management > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models/fields > copying imagekit/models/fields/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models/fields > copying imagekit/models/fields/utils.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models/fields > copying imagekit/models/fields/files.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models/fields > creating > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/management/commands > copying imagekit/management/commands/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/management/commands > copying imagekit/management/commands/generateimages.py -> > /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/management/commands >
Bug#991651: twitter-bootstrap4: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db
Source: twitter-bootstrap4 Version: 4.5.2+dfsg1-6 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 '/<>' > mkdir -p dist/css dist/js dist/tmp > sassc --sourcemap=auto scss/bootstrap.scss dist/tmp/bootstrap.css > sassc --sourcemap=auto scss/bootstrap-grid.scss dist/tmp/bootstrap-grid.css > sassc --sourcemap=auto scss/bootstrap-reboot.scss > dist/tmp/bootstrap-reboot.css > node debian/postcss.js > > Replace Autoprefixer browsers option to Browserslist config. > Use browserslist key in package.json or .browserslistrc file. > > Using browsers option can cause errors. Browserslist config can > be used for Babel, Autoprefixer, postcss-normalize and other tools. > > If you really need to use option, rename it to overrideBrowserslist. > > Learn more at: > https://github.com/browserslist/browserslist#readme > https://twitter.com/browserslist > > > 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 > (node:16484) UnhandledPromiseRejectionWarning: BrowserslistError: Unknown > browser query `> 1%`. Maybe you are using old Browserslist or made typo in > query. > at unknownQuery (/usr/share/nodejs/browserslist/index.js:285:10) > at /usr/share/nodejs/browserslist/index.js:372:11 > at Array.reduce () > at resolve (/usr/share/nodejs/browserslist/index.js:318:18) > at browserslist (/usr/share/nodejs/browserslist/index.js:444:21) > at Browsers.parse (/usr/share/nodejs/autoprefixer/lib/browsers.js:54:12) > at new Browsers (/usr/share/nodejs/autoprefixer/lib/browsers.js:42:26) > at loadPrefixes > (/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:103:20) > at Object.prepare > (/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:117:22) > at /usr/share/nodejs/postcss/lib/lazy-result.js:133:39 > (node:16484) UnhandledPromiseRejectionWarning: Unhandled promise rejection. > This error originated either by throwing inside of an async function without > a catch block, or by rejecting a promise which was not handled with .catch(). > To terminate the node process on unhandled promise rejection, use the CLI > flag `--unhandled-rejections=strict` (see > https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection > id: 1) > (node:16484) [DEP0018] DeprecationWarning: Unhandled promise rejections are > deprecated. In the future, promise rejections that are not handled will > terminate the Node.js process with a non-zero exit code. > > Replace Autoprefixer browsers option to Browserslist config. > Use browserslist key in package.json or .browserslistrc file. > > Using browsers option can cause errors. Browserslist config can > be used for Babel, Autoprefixer, postcss-normalize and other tools. > > If you really need to use option, rename it to overrideBrowserslist. > > Learn more at: > https://github.com/browserslist/browserslist#readme > https://twitter.com/browserslist > > > (node:16484) UnhandledPromiseRejectionWarning: BrowserslistError: Unknown > browser query `> 1%`. Maybe you are using old Browserslist or made typo in > query. > at unknownQuery (/usr/share/nodejs/browserslist/index.js:285:10) > at /usr/share/nodejs/browserslist/index.js:372:11 > at Array.reduce () > at resolve (/usr/share/nodejs/browserslist/index.js:318:18) > at browserslist (/usr/share/nodejs/browserslist/index.js:444:21) > at Browsers.parse (/usr/share/nodejs/autoprefixer/lib/browsers.js:54:12) > at new Browsers (/usr/share/nodejs/autoprefixer/lib/browsers.js:42:26) > at loadPrefixes > (/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:103:20) > at Object.prepare > (/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:117:22) > at /usr/share/nodejs/postcss/lib/lazy-result.js:133:39 > (node:16484) UnhandledPromiseRejectionWarning: Unhandled promise rejection. > This error originated either by throwing inside of an async function without > a catch block, or by rejecting a promise which was not handled with .catch(). > To terminate the node process on unhandled promise rejection, use the CLI > flag `--unhandled-rejections=strict` (see > https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection > id: 2) > > Replace Autoprefixer browsers option to Browserslist config. > Use browserslist key in package.json or .browserslistrc file. > > Using browsers option can cause errors. Browserslist config can > be used for Babel, Autoprefixer, postcss-normalize and other tools. > > If you really need to use option, rename it to overrideBrowserslist. > > Learn more at: > https://github.com/browserslist/browserslist#readme >
Bug#991649: libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Source: libhttp-cookiejar-perl Version: 0.010-1 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 '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > # > # Versions for all modules listed in MYMETA.json (including optional ones): > # > # === Configure Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker 6.17 7.44 > # > # === Build Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # > # === Test Requires === > # > # ModuleWant Have > # --- -- > # ExtUtils::MakeMakerany 7.44 > # File::Spec any 3.78 > # Test::Deep any1.130 > # Test::More0.96 1.302175 > # Test::Requires any 0.11 > # Time::Local 1.1901 1.28 > # URIany 5.08 > # libany 0.65 > # > # === Test Recommends === > # > # Module Want Have > # -- > # CPAN::Meta 2.120900 2.150010 > # > # === Runtime Requires === > # > # ModuleWant Have > # --- -- - > # Carp any 1.50 > # HTTP::Date any 6.05 > # Time::Local 1.1901 1.28 > # parent any 0.238 > # strict any 1.11 > # warnings any 1.47 > # > # === Runtime Recommends === > # > # ModuleWantHave > # - --- > # Mozilla::PublicSuffix any missing > # > t/00-report-prereqs.t .. > 1..1 > ok 1 - Reported prereqs > ok > t/add.t > ok 1 - no cookies > ok 2 - simple key=value > ok 3 - invalid cookie not stored > ok 4 - localhost treated as host only > ok 5 - single domain level treated as host only > ok 6 - different domain not stored > ok 7 - subdomain not stored > ok 8 - superdomain stored > ok 9 - path prefix /foo/ stored > ok 10 - path prefix /foo stored > ok 11 - last cookie wins > ok 12 - expired supercedes prior > ok 13 - separated by path > ok 14 - max-age supercedes expires > 1..14 > ok > > # Failed test at t/examples.t line 42. > # got: '' > # expected: 'lang=en-US' > # Looks like you failed 1 test of 2. > > # Failed test 'expiration' > # at t/examples.t line 45. > # Looks like you failed 1 test of 6. > t/examples.t ... > ok 1 - An object of class 'HTTP::CookieJar' isa 'HTTP::CookieJar' > # Subtest: just key & value > ok 1 > 1..1 > ok 2 - just key & value > # Subtest: secure > ok 1 > ok 2 > 1..2 > ok 3 - secure > # Subtest: not a subdomain > ok 1 > 1..1 > ok 4 - not a subdomain > # Subtest: wrong path > ok 1 > 1..1 > ok 5 - wrong path > # Subtest: expiration > not ok 1 > ok 2 > 1..2 > not ok 6 - expiration > 1..6 > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/6 subtests > t/parse.t .. > ok 1 - '' > ok 2 - SID= > ok 3 - =31d4d96e407aad42 > ok 4 - ; Max-Age: 1360343635 > ok 5 - SID=31d4d96e407aad42 > ok 6 - SID=ID=31d4d96e407aad42 > ok 7 - SID=31d4d96e407aad42 ; ; ; > ok 8 - SID=31d4d96e407aad42; Path=/; Secure; HttpOnly > ok 9 - SID=31d4d96e407aad42; Domain=.example.com > ok 10 - SID=31d4d96e407aad42; Path=/; Domain=example.com > ok 11 - SID=31d4d96e407aad42; Path=/; Domain= > ok 12 - lang=en-US; Expires = Wed, 09 Jun 2021 10:18:14 GMT > ok 13 - lang=en-US; Expires = Wed, 09 Jun 2021 10:18:14 GMT; Max-Age=3600 > 1..13 > ok > t/publicsuffix.t ... skipped: Test requires module > 'Mozilla::PublicSuffix' but it's not found > t/save.t ... > # Subtest: empty cookie jar > ok 1 - dumped zero cookies > ok 2 - load new cookie jar > ok 3 - second jar is empty > 1..3 > ok 1 - empty cookie jar > # Subtest: roundtrip > ok 1 - dumped correct number of cookies > ok 2 - load new cookie jar > ok 3 - second jar has correct count > ok 4 - old and new jars are the same > 1..4 > ok 2 - roundtrip > # Subtest: persistent > ok 1 - dumped correct number of cookies > ok 2 - load new cookie jar > ok 3 - second jar has correct count > 1..3 > ok 3 - persistent > # Subtest: liberal load > ok 1 - load_cookies with raw cookies > ok 2 - jar has correct count > 1..2 > ok 4 - liberal load > 1..4 > ok > t/sort.t ... > ok 1 - path length > ok 2 - creation time > 1..2 > ok > t/zzz-lwp.t > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok 13 > ok 14 > ok 15 > ok 16
Bug#991648: python-a38: FTBFS: AssertionError: "routines:CMS_verify:content verify error" does not match "b'Verification failure\n140224232826176:error:2E099064:CMS routines:cms_signerinfo_verify_cert
Source: python-a38 Version: 0.1.3-1 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 '/<>' > nose2-3 > sEF.. > == > ERROR: test_verify (test_p7m.TestAnagrafica) > -- > Traceback (most recent call last): > File "/<>/tests/test_p7m.py", line 63, in test_verify > p7m.verify_signature(capath) > File "/<>/a38/crypto.py", line 102, in verify_signature > raise InvalidSignatureError(res.stderr) > a38.crypto.InvalidSignatureError: b'Verification > failure\n140292464510272:error:2E099064:CMS > routines:cms_signerinfo_verify_cert:certificate verify > error:../crypto/cms/cms_smime.c:252:Verify error:certificate has expired\n' > > == > FAIL: test_verify_corrupted_payload (test_p7m.TestAnagrafica) > -- > a38.crypto.InvalidSignatureError: b'Verification > failure\n140224232826176:error:2E099064:CMS > routines:cms_signerinfo_verify_cert:certificate verify > error:../crypto/cms/cms_smime.c:252:Verify error:certificate has expired\n' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/<>/tests/test_p7m.py", line 81, in > test_verify_corrupted_payload > p7m.verify_signature(capath) > AssertionError: "routines:CMS_verify:content verify error" does not match > "b'Verification failure\n140224232826176:error:2E099064:CMS > routines:cms_signerinfo_verify_cert:certificate verify > error:../crypto/cms/cms_smime.c:252:Verify error:certificate has expired\n'" > > -- > Ran 145 tests in 0.155s > > FAILED (failures=1, errors=1, skipped=1) > make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/07/28/python-a38_0.1.3-1_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.
Bug#991647: libisocodes: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: libisocodes Version: 1.2.3-1 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. See also #963371 and the bug I just filed against isoquery. Relevant part (hopefully): > make[3]: Entering directory '/<>/po' > make[3]: Nothing to be done for 'check'. > make[3]: Leaving directory '/<>/po' > make[3]: Verzeichnis „/<>“ wird betreten > make check-local > make[4]: Verzeichnis „/<>“ wird betreten > /usr/bin/valac --pkg libxml-2.0 --pkg gee-0.8 --vapidir=./vapi --pkg config > -X -I. -X -DGETTEXT_PACKAGE=\"libisocodes\" -X > -DLOCALEDIR=\"/usr/share/locale\" -X -DTESTDIR=\"./tests/data\" > --output=codetest tests/codetest.vala tests/test_iso_3166.vala > tests/test_iso_3166_2.vala tests/test_iso_639.vala tests/test_iso_639_3.vala > tests/test_iso_639_5.vala tests/test_iso_4217.vala tests/test_iso_15924.vala > src/isocodes.vala src/iso_3166.vala src/iso_3166_item.vala > src/iso_3166_2.vala src/iso_3166_2_item.vala src/iso_639.vala > src/iso_639_item.vala src/iso_639_3.vala src/iso_639_3_item.vala > src/iso_639_5.vala src/iso_639_5_item.vala src/iso_4217.vala > src/iso_4217_item.vala src/iso_15924.vala src/iso_15924_item.vala > src/exceptions.vala > config.vapi:19.2-19.6: warning: argument `prefix' never used > [CCode (prefix = "", lower_case_cprefix = "", cheader_filename = "config.h")] > ^ > /<>/src/isocodes.vala.c: In function > ‘libisocodes_iso_codes_set_standard’: > /<>/src/isocodes.vala.c:1313:12: warning: assignment discards > ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] > 1313 | old_value = libisocodes_iso_codes_get_standard (self); > |^ > Compilation succeeded - 1 warning(s) > gtester --verbose codetest > > ** (gtester:16679): WARNING **: 06:18:09.479: Deprecated: Since GLib 2.62, > gtester and gtester-report are deprecated. Port to TAP. > TEST: codetest... (pid=16680) > /iso_3166/3.x/create class: OK > /iso_3166/3.x/create class with changed filepath:OK > /iso_3166/3.x/change filepath with null value or empty string: OK > /iso_3166/3.x/change locale: OK > /iso_3166/3.x/throw exception for non-existant file: OK > /iso_3166/3.x/throw exception for directory: OK > /iso_3166/3.x/throw exception for parsing failure: OK > /iso_3166/3.x/throw exception for wrong ISO data:OK > /iso_3166/3.x/find all codes:OK > /iso_3166/3.x/find all codes in locale 'fr': OK > /iso_3166/3.x/call find_code() without argument: OK > /iso_3166/3.x/search empty code: OK > /iso_3166/3.x/find code 'de':OK > /iso_3166/3.x/find code 'FR':OK > /iso_3166/3.x/find code 'Tw':OK > /iso_3166/3.x/find code 'ukr': OK > /iso_3166/3.x/find code '798': OK > /iso_3166/3.x/search non existant code: OK > /iso_3166/3.x/find code 'ES' in locale 'de': OK > /iso_3166/3.x/find code 'TW' in locale 'fr': OK > /iso_3166/3.x/find code 'RUS' in non existant locale:OK > /iso_3166_2/3.x/create class:OK > /iso_3166_2/3.x/create class with changed filepath: OK > /iso_3166_2/3.x/find all codes: OK > /iso_3166_2/3.x/find all codes in locale 'fr': OK > /iso_3166_2/3.x/call find_code() without argument: OK > /iso_3166_2/3.x/search empty code: OK > /iso_3166_2/3.x/find code 'de-hh': OK > /iso_3166_2/3.x/find code 'FR-78': OK > /iso_3166_2/3.x/find code 'ES-C':OK > /iso_3166_2/3.x/search non existant code:OK > /iso_3166_2/3.x/find code 'DE-HH' in locale 'fr':OK > /iso_3166_2/3.x/find code 'NO-15' in non existant locale:OK > /iso_639/3.x/create class: OK > /iso_639/3.x/create class with changed filepath: OK > /iso_639/3.x/find all codes: OK > /iso_639/3.x/find all codes in locale 'fr': OK > /iso_639/3.x/call find_code() without argument: OK > /iso_639/3.x/search empty code: OK >
Bug#990463: libgstreamer1.0-dev: please add Conflicts: libgstreamer0.10-dev
Followup-For: Bug #990463 Control: tag -1 pending Hi, I've just NMUed the fix to DELAYED/2. Unblock request: https://bugs.debian.org/991644 Andreas
Processed: Re: libgstreamer1.0-dev: please add Conflicts: libgstreamer0.10-dev
Processing control commands: > tag -1 pending Bug #990463 [libgstreamer1.0-dev] libgstreamer1.0-dev: please add Conflicts: libgstreamer0.10-dev Added tag(s) pending. -- 990463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991635: FTBFS on amd64
close 991635 6.1.26-2 thanks Hi Gianfranco thanks for the fix, it compiled now. Regards, Daniel
Processed: Re: FTBFS on amd64
Processing commands for cont...@bugs.debian.org: > close 991635 6.1.26-2 Bug #991635 [virtualbox] FTBFS on amd64 There is no source info for the package 'virtualbox' at version '6.1.26-2' with architecture '' Unable to make a source version for version '6.1.26-2' Marked as fixed in versions 6.1.26-2. Bug #991635 [virtualbox] FTBFS on amd64 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 991635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#989103 closed by Felipe Sateler (DMO is not supported)
Processing control commands:
> found -1 14.2-2
Bug #989103 {Done: Felipe Sateler } [pulseaudio]
pulseaudio crashes on startup
Did not alter found versions and reopened.
> fixed -1 14.99-1
Bug #989103 [pulseaudio] pulseaudio crashes on startup
There is no source info for the package 'pulseaudio' at version '14.99-1' with
architecture ''
Unable to make a source version for version '14.99-1'
Marked as fixed in versions 14.99-1.
--
989103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#989103: closed by Felipe Sateler (DMO is not supported)
Control: found -1 14.2-2 Control: fixed -1 14.99-1 Hi Michał! On Thu, Jul 29, 2021 at 9:27 AM Michał Mirosław wrote: > On Thu, Jul 29, 2021 at 12:57:03PM +, Debian Bug Tracking System wrote: > > Date: Thu, 29 Jul 2021 08:51:50 -0400 > > From: Felipe Sateler > > To: 989103-d...@bugs.debian.org, 991337-d...@bugs.debian.org > > Subject: DMO is not supported > > > > deb-multimedia.org is not supported here. Please ask the maintainers of > > that repository for support. Closing the bug. > > The bug is in bullseye package. I'm not sure where deb-multimedia came > from? > (It's not enabled in my sources.list) > Sorry, I got confused by the last message from Keith Edmunds[1]. On a more detailed look, this is fixed in experimental but not on bullseye. Help with an update for bullseye would be appreciated. [1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989103#53 -- Saludos, Felipe Sateler
Bug#991337: marked as done (pulseaudio: Pulseaudio craches on start with SegFault error)
Your message dated Thu, 29 Jul 2021 08:51:50 -0400 with message-id and subject line DMO is not supported has caused the Debian Bug report #991337, regarding pulseaudio: Pulseaudio craches on start with SegFault error 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.) -- 991337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: pulseaudio: Pulseaudio craches on start with SegFault error Package: pulseaudio Version: 14.2-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Probably, some daily dist-upgrade. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to reinstall alsa and pulseaudio, tried to downgrade to the version in stable branch, to upgrade to newer version in experimental branch. * What was the outcome of this action? Nothing has helped me. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: File '/etc/default/pulseaudio' does not exist -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (500, 'testing-security'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pulseaudio depends on: ii adduser 3.118 ii init-system-helpers 1.60 ii libasound2 1.2.4-1.1 ii libasound2-plugins 1:1.2.2-dmo2 ii libc62.31-12 ii libcap2 1:2.44-1 ii libdbus-1-3 1.12.20-2 ii libgcc-s110.2.1-6 ii libice6 2:1.0.10-1 ii libltdl7 2.4.6-15 ii liborc-0.4-0 1:0.4.32-1 ii libpulse014.2-2 ii libsm6 2:1.2.3-1 ii libsndfile1 1.0.31-1 ii libsoxr0 0.1.3-4 ii libspeexdsp1 1.2~rc1.2-1.1 ii libstdc++6 10.2.1-6 ii libsystemd0 247.3-5 ii libtdb1 1.4.3-1+b1 ii libudev1 247.3-5 ii libwebrtc-audio-processing1 0.3-1+b1 ii libx11-6 2:1.7.1-1 ii libx11-xcb1 2:1.7.1-1 ii libxcb1 1.14-3 ii libxtst6 2:1.2.3-1 ii lsb-base 11.1.0 ii pulseaudio-utils 14.2-2 Versions of packages pulseaudio recommends: ii dbus-user-session1.12.20-2 ii libpam-systemd [logind] 247.3-5 ii rtkit0.13-4 Versions of packages pulseaudio suggests: pn paprefs ii pavucontrol 4.0-2 pn pavumeter ii udev 247.3-5 -- no debconf information $ aplay -l List of PLAYBACK Hardware Devices card 0: nvidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: nvidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: nvidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: nvidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: nvidia [HDA NVidia], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: nvidia [HDA NVidia], device 11: HDMI 5 [HDMI 5] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: nvidia [HDA NVidia], device 12: HDMI 6 [HDMI 6] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: USB [E-MU 0202 | USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pulseaudio -v I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted I: [pulseaudio] core-util.c: Successfully gained nice level -11. I: [pulseaudio] main.c: This is PulseAudio 14.2 I: [pulseaudio] main.c: Page size is 4096
Bug#989103: marked as done (pulseaudio crashes on startup)
Your message dated Thu, 29 Jul 2021 08:51:50 -0400 with message-id and subject line DMO is not supported has caused the Debian Bug report #989103, regarding pulseaudio crashes on startup 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.) -- 989103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pulseaudio Version: 14.2-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: mirq-debo...@rere.qmqm.pl After upgrade to bullseye, pulseaudio crashes on startup in pa_alsa_sink_new() -> find_mixer() due to mapping==NULL. The code at upstream's HEAD seems to assume that (element != NULL) implies (mapping != NULL). Program received signal SIGSEGV, Segmentation fault. 0x7286d85c in find_mixer (ignore_dB=false, element=0x5566dfe0 "Wave", mapping=0x0, u=0x556709b0) at modules/alsa/alsa-sink.c:2110 2110modules/alsa/alsa-sink.c: No such file or directory. (gdb) bt #0 0x7286d85c in find_mixer (ignore_dB=false, element=0x5566dfe0 "Wave", mapping=0x0, u=0x556709b0) at modules/alsa/alsa-sink.c:2110 #1 find_mixer (u=0x556709b0, mapping=0x0, element=0x5566dfe0 "Wave", ignore_dB=) at modules/alsa/alsa-sink.c:2098 #2 0x72871d14 in pa_alsa_sink_new (m=m@entry=0x5566b070, ma=ma@entry=0x55582990, driver=driver@entry=0x72895618 "modules/alsa/module-alsa-sink.c", card=card@entry=0x0, mapping=, mapping@entry=0x0) at modules/alsa/alsa-sink.c:2586 #3 0x72894347 in module_alsa_sink_LTX_pa__init (m=0x5566b070) at modules/alsa/module-alsa-sink.c:102 #4 0x77e30279 in pa_module_load (module=module@entry=0x7fffce40, c=c@entry=0x555761d0, name=name@entry=0x5566a820 "module-alsa-sink", argument=0x55669570 "device=hw:1,0 control=Wave") at pulsecore/module.c:191 #5 0x77e1c36c in pa_cli_command_load (c=0x555761d0, t=0x5566db00, buf=0x5556f0c0, fail=0x5556e5a5) at pulsecore/cli-command.c:437 #6 0x77e2429b in pa_cli_command_execute_line_stateful (c=c@entry=0x555761d0, s=s@entry=0x7fffcfa0 "load-module module-alsa-sink device=hw:1,0 control=Wave", buf=buf@entry=0x5556f0c0, fail=fail@entry=0x5556e5a5, ifstate=ifstate@entry=0x7fffcf9c) at pulsecore/cli-command.c:2141 #7 0x77e24a01 in pa_cli_command_execute_file_stream (c=c@entry=0x555761d0, f=f@entry=0x5556e980, buf=buf@entry=0x5556f0c0, fail=fail@entry=0x5556e5a5) at pulsecore/cli-command.c:2181 #8 0xb570 in main (argc=, argv=) at daemon/main.c:1105 -- Package-specific info: File '/etc/default/pulseaudio' does not exist -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (900, 'testing'), (800, 'stable-debug'), (800, 'proposed-updates'), (800, 'stable'), (700, 'unstable'), (600, 'experimental'), (540, 'oldstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'proposed-updates-debug'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.12.6+ (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pulseaudio depends on: ii adduser 3.118 ii init-system-helpers 1.60 ii libasound2 1.2.4-1.1 ii libasound2-plugins 1.2.2-2 ii libc62.31-12 ii libcap2 1:2.44-1 ii libdbus-1-3 1.12.20-2 ii libgcc-s110.2.1-6 ii libice6 2:1.0.10-1 ii libltdl7 2.4.6-15 ii liborc-0.4-0 1:0.4.32-1 ii libpulse014.2-2 ii libsm6 2:1.2.3-1 ii libsndfile1 1.0.31-1 ii libsoxr0 0.1.3-4 ii libspeexdsp1 1.2~rc1.2-1.1 ii libstdc++6 10.2.1-6 ii libsystemd0 247.3-5 ii libtdb1 1.4.3-1+b1 ii libudev1 247.3-5 ii libwebrtc-audio-processing1 0.3-1+b1 ii libx11-6 2:1.7.1-1 ii libx11-xcb1 2:1.7.1-1 ii libxcb1 1.14-3 ii libxtst6 2:1.2.3-1 ii lsb-base 11.1.0 ii pulseaudio-utils 14.2-2 Versions of packages pulseaudio recommends: ii
Bug#991635: FTBFS on amd64
Package: virtualbox Version: 6.1.26-dfsg-1 Severity: serious Hi, virtualbox 6.1.26-dfsg-1 fails to build from source on amd64 (but builds fine on i386): [...] kBuild: Linking vboxjxpcom.jar => /<>/out/obj/VBoxJXpcom-inst-jar/vboxjxpcom.jar "/usr/lib/jvm/default-java/bin/jar" cf /<>/out/obj/VBoxJXpcom-inst-jar/vboxjxpcom.jar -C /<>/out/obj/vboxjxpcom-gen/jdest . kmk: *** Exiting with status 2 kBuild: Compiling VBoxOGL2D - /<>/src/VBox/Frontends/VirtualBox/src/VBoxGLSupportInfo.cpp => /<>/out/obj/VBoxOGL2D/src/VBoxGLSupportInfo.o kmk_builtin_rm -f -- /<>/out/obj/VBoxOGL2D/src/VBoxGLSupportInfo.o.dep /<>/out/obj/VBoxOGL2D/src/VBoxGLSupportInfo.o g++ -c -O2 -fPIC -g -pipe -Wall -Wextra -Wno-missing-field-initializers -Wno-trigraphs -fdiagnostics-show-option -Wlogical-op -Wno-variadic-macros -frtti -fno-exceptions -Wno-long-long -fshort-wchar -fno-strict-aliasing -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fvisibility-inlines-hidden -Wno-multistatement-macros -Wno-ignored-qualifiers -std=c++11 -Wno-deprecated-declarations -fPIC -Wno-deprecated-copy -g -pipe -Wall -Wextra -Wno-missing-field-initializers -Wno-trigraphs -fdiagnostics-show-option -Wlogical-op -Wno-variadic-macros -frtti -fno-exceptions -Wno-long-long -fshort-wchar -fno-strict-aliasing -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fvisibility-inlines-hidden -Wno-multistatement-macros -Wno-ignored-qualifiers -std=c++11 -Wno-deprecated-declarations -fPIC -m64 -I/<>/src/VBox/Frontends/VirtualBox/include -I/<>/out/bin/sdk/bindings/xpcom/include -I/<>/out/bin/sdk/bindings/xpcom/include/xpcom -I/<>/out/bin/sdk/bindings/xpcom/include/string -I/<>/out/bin/sdk/bindings/xpcom/include/xpcom -I/<>/out/bin/sdk/bindings/xpcom/include/nsprpub -I/<>/out/bin/sdk/bindings/xpcom/include/ipcd -I/usr/include/x86_64-linux-gnu/qt5/QtGui/QtOpenGL -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/<>/out/obj/VBoxOGL2D/qtmoc -I/<>/out/obj/VBoxOGL2D/qtuic -I/<>/include -I/<>/out -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/share/doc/virtualbox\" -DPIC -DIN_RING3 -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_SHARED -DHAVE_CONFIG_H -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DVBOX_WITH_XPCOM -DVBOX_WITH_XPCOM_NAMESPACE_CLEANUP -DPIC -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_SHARED -DHAVE_CONFIG_H -DVBOX_WITH_VIDEOHWACCEL -DVBOX_GUI_USE_QGL -DQT_OPENGL_LIB -D_REENTRANT -Wp,-MD,/<>/out/obj/VBoxOGL2D/src/VBoxGLSupportInfo.o.dep -Wp,-MT,/<>/out/obj/VBoxOGL2D/src/VBoxGLSupportInfo.o -Wp,-MP -o /<>/out/obj/VBoxOGL2D/src/VBoxGLSupportInfo.o /<>/src/VBox/Frontends/VirtualBox/src/VBoxGLSupportInfo.cpp /<>/src/VBox/Frontends/VirtualBox/src/VBoxGLSupportInfo.cpp:22:10: fatal error: QGLWidget: No such file or directory 22 | #include | ^~~ compilation terminated. kmk: *** [/usr/share/kBuild/footer-pass2-compiling-targets.kmk:277: /<>/out/obj/VBoxOGL2D/src/VBoxGLSupportInfo.o] Error 1 make[1]: *** [debian/rules:62: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:37: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 https://buildd.debian.org/status/fetch.php?pkg=virtualbox=amd64=6.1.26-dfsg-1=1627555826=0 Regards, Daniel
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 991334 normal Bug #991334 [monit] monit: Race condition on reboot timestamp checks Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 991334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991451: redis breaks python-fakeredis autopkgtest: AssertionError
Jochen Sprickerhof wrote: > I have no idea about Redis/Fakeredis, adding Ondřej as he did all the > uploads, lately. Hey Ondřej, any input here? Otherwise, not sure what to suggest... Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#991630: snort-common: maintainer scripts must always call dpkg-maintscript-helper
Package: snort-common
Version: 2.9.15.1-5
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
debsums reports modification of the following files,
from the attached log (scroll to the bottom...):
/etc/cron.daily/snort-common
This happens in the following scenario:
* install snort-common/buster
* remove (nut not purge) snort-common
* upgrade system from bsuter to bullseye
* install snort-common/bullseye
dpkg-maintscript-helper gets "$@" as arguments s.t. it can decide what
to do depending on the action.
The preinst/postinst scripts only call dpkg-maintscript-helper for a limited
set of actions, especially missing "preinst install $oldversion", which
causes the wrong action being taken by the postinst in the above scenario
(it preserves the unmodified old file and moves it to the new location).
cheers,
Andreas
diff -Nru snort-2.9.15.1/debian/changelog snort-2.9.15.1/debian/changelog
--- snort-2.9.15.1/debian/changelog 2021-04-10 22:55:04.0 +0200
+++ snort-2.9.15.1/debian/changelog 2021-07-29 11:33:46.0 +0200
@@ -1,3 +1,10 @@
+snort (2.9.15.1-6) UNRELEASED; urgency=medium
+
+ * snort-common.{pre,post}inst: Call dpkg-maintscript-helper for all actions.
+(Closes: #-1)
+
+ -- Andreas Beckmann Thu, 29 Jul 2021 11:33:46 +0200
+
snort (2.9.15.1-5) unstable; urgency=medium
* debian/snort-common.{preinst,postinst,postrm}:
diff -Nru snort-2.9.15.1/debian/snort-common.postrm
snort-2.9.15.1/debian/snort-common.postrm
--- snort-2.9.15.1/debian/snort-common.postrm 2021-04-10 22:55:04.0
+0200
+++ snort-2.9.15.1/debian/snort-common.postrm 2021-07-29 11:33:46.0
+0200
@@ -6,17 +6,6 @@
set -e
test $DEBIAN_SCRIPT_DEBUG && set -v -x
-# summary of how this script can be called:
-#* `remove'
-#* `purge'
-#* `upgrade'
-#* `failed-upgrade'
-#* `abort-install'
-#* `abort-install'
-#* `abort-upgrade'
-#* `disappear' overwrit>r>
-# for details, see /usr/doc/packaging-manual/
-
case "$1" in
purge)
@@ -33,7 +22,8 @@
rm -f /etc/snort/database.conf
fi
;;
- abort-install|abort-upgrade)
+esac
+
# if installation was aborted then revert the rename of the cron job
using dpkg-maintscript-helper
if dpkg-maintscript-helper supports mv_conffile; then
dpkg-maintscript-helper mv_conffile \
@@ -43,17 +33,8 @@
if dpkg-maintscript-helper supports rm_conffile; then
dpkg-maintscript-helper rm_conffile /etc/snort/database.conf 2.9.3~
snort-common -- "$@"
fi
- ;;
- remove|upgrade|failed-upgrade|abort-install|abort-upgrade)
-# nothing
- ;;
-esac
-
-
-
# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.
#DEBHELPER#
-
diff -Nru snort-2.9.15.1/debian/snort-common.preinst
snort-2.9.15.1/debian/snort-common.preinst
--- snort-2.9.15.1/debian/snort-common.preinst 2021-04-10 22:55:04.0
+0200
+++ snort-2.9.15.1/debian/snort-common.preinst 2021-07-29 11:33:45.0
+0200
@@ -3,20 +3,9 @@
set -e
test $DEBIAN_SCRIPT_DEBUG && set -v -x
-# summary of how this script can be called:
-#* `install'
-#* `install'
-#* `upgrade'
-#* `abort-upgrade'
-
GENCONF="/etc/snort/snort.conf" # generic configuration file
DBCONF="/etc/snort/database.conf" # deprecated
-case "$1" in
-install)
-# Do nothing
-;;
-upgrade)
# versions previous to 2.9.3 created the /etc/snort/database.conf
# file for configuration
#if dpkg --compare-versions "$2" le "2.9.3" && [ -e "$DBCONF" ] && !
[ -s "$DBCONF" ]
@@ -32,7 +21,9 @@
if dpkg-maintscript-helper supports rm_conffile; then
dpkg-maintscript-helper rm_conffile $DBCONF 2.9.3~
snort-common -- "$@"
else
+ if [ "$1" = "upgrade" ]; then
rm -f $DBCONF
+ fi
fi
fi
@@ -44,26 +35,15 @@
# Manually move the file, this will generate a dpkg prompt to
# approve the changes
if [ -e /etc/cron.daily/5snort ]; then
+ if [ "$1" = "upgrade" ]; then
mv /etc/cron.daily/5snort /etc/cron.daily/snort-common
+ fi
fi
fi
-;;
-configure)
-# Do nothing
-;;
-abort-upgrade)
-;;
-*)
-echo "preinst called with unknown argument \`$1'" >&2
-exit 0
-;;
-esac
-
# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.
#DEBHELPER#
exit 0
-
snort-common_2.9.15.1-5.log.gz
Description: application/gzip
Bug#991334:
Severity: normal This is not a serious bug and is currently slated to remove monit from testing. Please check for severities here https://www.debian.org/Bugs/Developer#severities It's been rejected upstream I'll let the maintainers here comment on if it should be accepted or rejected here.
Processed: reassign 991588 to tpm2-abrmd
Processing commands for cont...@bugs.debian.org: > reassign 991588 tpm2-abrmd Bug #991588 [ifupdown] systemd: Buster to Bullseye: boot stalls at network loading on normal boot Bug reassigned from package 'ifupdown' to 'tpm2-abrmd'. Ignoring request to alter found versions of bug #991588 to the same values previously set Ignoring request to alter fixed versions of bug #991588 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 991588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
