Bug#955055: marked as done (python-simpy: FTBFS with Sphinx 2.4: KeyError: 'python')

Your message dated Mon, 20 Jun 2022 05:49:03 + with message-id and subject line Bug#955055: fixed in python-simpy 2.3.1+dfsg-4 has caused the Debian Bug report #955055, regarding python-simpy: FTBFS with Sphinx 2.4: KeyError: 'python' to be marked as done. This means that you claim that the

Bug#955055: marked as pending in python-simpy

Control: tag -1 pending Hello, Bug #955055 in python-simpy 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:

Processed: Bug#955055 marked as pending in python-simpy

Processing control commands: > tag -1 pending Bug #955055 [src:python-simpy] python-simpy: FTBFS with Sphinx 2.4: KeyError: 'python' Added tag(s) pending. -- 955055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#997645: marked as done (python-slimmer: FTBFS: error in slimmer setup command: use_2to3 is invalid.)

Your message dated Mon, 20 Jun 2022 05:33:52 + with message-id and subject line Bug#997645: fixed in python-slimmer 0.1.30-9 has caused the Debian Bug report #997645, regarding python-slimmer: FTBFS: error in slimmer setup command: use_2to3 is invalid. to be marked as done. This means that

Bug#997645: marked as pending in python-slimmer

Control: tag -1 pending Hello, Bug #997645 in python-slimmer 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:

Processed: Bug#997645 marked as pending in python-slimmer

Processing control commands: > tag -1 pending Bug #997645 [src:python-slimmer] python-slimmer: FTBFS: error in slimmer setup command: use_2to3 is invalid. Added tag(s) pending. -- 997645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997645 Debian Bug Tracking System Contact

Bug#997633: marked as done (python-tempita: FTBFS: error in Tempita setup command: use_2to3 is invalid.)

Your message dated Mon, 20 Jun 2022 05:04:51 + with message-id and subject line Bug#997633: fixed in python-tempita 0.5.2-7 has caused the Debian Bug report #997633, regarding python-tempita: FTBFS: error in Tempita setup command: use_2to3 is invalid. to be marked as done. This means that

Processed: Bug#997633 marked as pending in python-tempita

Processing control commands: > tag -1 pending Bug #997633 [src:python-tempita] python-tempita: FTBFS: error in Tempita setup command: use_2to3 is invalid. Added tag(s) pending. -- 997633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997633 Debian Bug Tracking System Contact

Bug#997633: marked as pending in python-tempita

Control: tag -1 pending Hello, Bug #997633 in python-tempita 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:

Bug#1011889: marked as done (haskell-tldr: FTBFS: make: *** [/usr/share/cdbs/1/rules/debhelper.mk:252: binary-install/libghc-tldr-doc] Error 25)

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT) with message-id and subject line Fixed by haskell-devscripts 0.16.20 has caused the Debian Bug report #1011889, regarding haskell-tldr: FTBFS: make: *** [/usr/share/cdbs/1/rules/debhelper.mk:252: binary-install/libghc-tldr-doc] Error 25

Bug#1011883: marked as done (haskell-wcwidth: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-wcwidth-doc] Error 25)

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT) with message-id and subject line Fixed by haskell-devscripts 0.16.20 has caused the Debian Bug report #1011883, regarding haskell-wcwidth: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-wcwidth-doc] Error 25 to

Bug#1011866: marked as done (haskell-base-prelude: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-base-prelude-doc] Error 25)

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT) with message-id and subject line Fixed by haskell-devscripts 0.16.20 has caused the Debian Bug report #1011866, regarding haskell-base-prelude: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-base-prelude-doc]

Bug#1011831: marked as done (haskell-vector-builder: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-vector-builder-doc] Error 25)

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT) with message-id and subject line Fixed by haskell-devscripts 0.16.20 has caused the Debian Bug report #1011831, regarding haskell-vector-builder: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-vector-builder-doc]

Bug#1011782: marked as done (haskell-patience: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-patience-doc] Error 25)

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT) with message-id and subject line Fixed by haskell-devscripts 0.16.20 has caused the Debian Bug report #1011782, regarding haskell-patience: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-patience-doc] Error 25 to

Bug#1003353: marked as pending in lintian

Control: tag -1 pending Hello, Bug #1003353 in lintian 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:

Processed: Bug#1003353 marked as pending in lintian

Processing control commands: > tag -1 pending Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules? Ignoring request to alter tags of bug #1003353 to the same tags previously set -- 1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353 Debian Bug Tracking System

Bug#1013248: libseat-dev: Missing libseat-dev dependency on libsystemd-dev via pkg-config

Package: libseat-dev Version: 0.7.0-4 Severity: grave Justification: renders package unusable Dear Maintainer, Using pkg-config to find headers fails for libseat-dev with the following output: $ /usr/bin/pkg-config --cflags libseat Package libsystemd was not found in the pkg-config

Bug#1003353: lintian: Cannot use brackets in suppression rules?

Control: tag -1 + pending patch Hi Samuel, Samuel Thibault wrote: > Seeing that qa.debian.org is using version 2.114.123 of lintian, I > upgraded my lintian from its git tree, only to find that it seems I > cannot update my suppression rule according to the new output: > > W: libbrlapi-dev:

Processed: Re: Bug#1003353: lintian: Cannot use brackets in suppression rules?

Processing control commands: > tag -1 + pending patch Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules? Added tag(s) patch. -- 1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#984914: marked as done (rust-combine: depends on multiple unavailable packages)

Your message dated Sun, 19 Jun 2022 23:50:42 + with message-id and subject line Bug#984914: fixed in rust-combine 4.6.4-1 has caused the Debian Bug report #984914, regarding rust-combine: depends on multiple unavailable packages to be marked as done. This means that you claim that the

Bug#1003353: marked as pending in lintian

Control: tag -1 pending Hello, Bug #1003353 in lintian 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:

Processed: Bug#1003353 marked as pending in lintian

Processing control commands: > tag -1 pending Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules? Added tag(s) pending. -- 1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1011909: shellcheck: FTBFS: dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

The build is now failing with another error, but both FTBFS are not caused by shellcheck, and can't be fixed by it. There's something weird going on with haskell packages, I believe the error will eventually be solved in the next few weeks, let's see... Regards, -- Samuel Henrique

Bug#1012600: [Pkg-zfsonlinux-devel] Bug#1012600:

I think this is because it Depends: a kernel << 5.18 and not Conflicts/Breaks a kernel >= 5.18. Since you can install multiple kernel packages, your existing kernel package is satisfying the dependency. -- Richard OpenPGP_signature Description: OpenPGP digital signature

Bug#966780: marked as done (python-passfd: Unversioned Python removal in sid/bullseye)

Your message dated Sun, 19 Jun 2022 19:33:38 + with message-id and subject line Bug#1009280: Removed package(s) from unstable has caused the Debian Bug report #938001, regarding python-passfd: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#938001: marked as done (python-passfd: Python2 removal in sid/bullseye)

Your message dated Sun, 19 Jun 2022 19:33:38 + with message-id and subject line Bug#1009280: Removed package(s) from unstable has caused the Debian Bug report #938001, regarding python-passfd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#446343: marked as done (cutter: does not work at all)

Your message dated Sun, 19 Jun 2022 19:29:57 + with message-id and subject line Bug#1010705: Removed package(s) from unstable has caused the Debian Bug report #446343, regarding cutter: does not work at all to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1011844: marked as done (tools-analyzer-jvm-clojure: FTBFS: Cannot access snapshots (https://oss.sonatype.org/content/repositories/snapshots) in offline mode and the artifact nrepl:nrepl:jar:0.6.0

Your message dated Sun, 19 Jun 2022 15:22:30 -0400 with message-id <0adcfb28-0a17-2072-04ea-034120d66...@debian.org> and subject line close Clojure bugs created by the nrepl bug in lein has caused the Debian Bug report #1011844, regarding tools-analyzer-jvm-clojure: FTBFS: Cannot access snapshots

Bug#1011864: marked as done (tools-reader-clojure: FTBFS: Cannot access sonatype-oss-public (https://oss.sonatype.org/content/groups/public/) in offline mode and the artifact nrepl:nrepl:jar:0.6.0 has

Your message dated Sun, 19 Jun 2022 15:22:30 -0400 with message-id <0adcfb28-0a17-2072-04ea-034120d66...@debian.org> and subject line close Clojure bugs created by the nrepl bug in lein has caused the Debian Bug report #1011864, regarding tools-reader-clojure: FTBFS: Cannot access

Bug#1011837: marked as done (tools-analyzer-clojure: FTBFS: Cannot access snapshots (https://oss.sonatype.org/content/repositories/snapshots) in offline mode and the artifact nrepl:nrepl:jar:0.6.0 has

Your message dated Sun, 19 Jun 2022 15:22:30 -0400 with message-id <0adcfb28-0a17-2072-04ea-034120d66...@debian.org> and subject line close Clojure bugs created by the nrepl bug in lein has caused the Debian Bug report #1011837, regarding tools-analyzer-clojure: FTBFS: Cannot access snapshots

Bug#1011856: marked as done (test-check-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.2 has not been downloaded from i

Your message dated Sun, 19 Jun 2022 19:19:14 + with message-id and subject line Bug#1011856: fixed in test-check-clojure 0.9.0-5 has caused the Debian Bug report #1011856, regarding test-check-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact

Bug#1013238: src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary

Source: pyspread Version: 2.0.1-1 Severity: serious Control: close -1 2.1-2 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60

Processed: src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary

Processing control commands: > close -1 2.1-2 Bug #1013238 [src:pyspread] src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions pyspread/2.1-2. Bug #1013238 [src:pyspread] src:pyspread: fails to migrate to testing for too long:

Bug#1012613: marked as done (nftables: upgrade stops but does not start service)

Your message dated Sun, 19 Jun 2022 18:18:54 + with message-id and subject line Bug#1012613: fixed in nftables 1.0.4-2 has caused the Debian Bug report #1012613, regarding nftables: upgrade stops but does not start service to be marked as done. This means that you claim that the problem has

Processed: Re: Fwd: Re: [Pkg-javascript-devel] Bug#1013218: rails: ftbfs SyntaxError: Unexpected token 'export'

Processing control commands: > tags -1 help Bug #1013218 [ruby-sprockets] rails: ftbfs SyntaxError: Unexpected token 'export' Added tag(s) help. -- 1013218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#978259: marked as done (python-testing.mysqld: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13)

Your message dated Sun, 19 Jun 2022 18:03:54 + with message-id and subject line Bug#978259: fixed in python-testing.mysqld 1.4.0-6 has caused the Debian Bug report #978259, regarding python-testing.mysqld: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9

Bug#1013129: marked as done (exo: CVE-2022-32278)

Your message dated Sun, 19 Jun 2022 17:47:08 + with message-id and subject line Bug#1013129: fixed in exo 4.16.0-1+deb11u1 has caused the Debian Bug report #1013129, regarding exo: CVE-2022-32278 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1013129: marked as done (exo: CVE-2022-32278)

Your message dated Sun, 19 Jun 2022 17:47:26 + with message-id and subject line Bug#1013129: fixed in exo 0.12.4-1+deb10u1 has caused the Debian Bug report #1013129, regarding exo: CVE-2022-32278 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1012613: nftables: upgrade stops but does not start service

On 2022-06-19, at 13:48:59 +0200, Arturo Borrero Gonzalez wrote: > On Fri, 10 Jun 2022 12:21:37 +0200 Christian Göttsche wrote: > > Package: nftables > > Version: 1.0.4-1 > > Severity: serious > > > > Dear Maintainer, > > > > upgrades of nftables stop the service but do not start it (even if the >

Processed: Bug#978259 marked as pending in python-testing.mysqld

Processing control commands: > tag -1 pending Bug #978259 [src:python-testing.mysqld] python-testing.mysqld: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13 Added tag(s) pending. -- 978259:

Bug#978259: marked as pending in python-testing.mysqld

Control: tag -1 pending Hello, Bug #978259 in python-testing.mysqld 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:

Bug#1011142: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185)

Your message dated Sun, 19 Jun 2022 17:02:24 + with message-id and subject line Bug#1011142: fixed in nvidia-graphics-drivers-legacy-390xx 390.151-1~deb10u1 has caused the Debian Bug report #1011142, regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185 to be marked

Bug#1011142: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185)

Your message dated Sun, 19 Jun 2022 17:02:08 + with message-id and subject line Bug#1011142: fixed in nvidia-graphics-drivers-legacy-390xx 390.151-1~deb11u1 has caused the Debian Bug report #1011142, regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185 to be marked

Bug#1010230: marked as done (nvidia-graphics-drivers-legacy-390xx: spurious module build failure in autopkgtest on armhf)

Your message dated Sun, 19 Jun 2022 17:02:24 + with message-id and subject line Bug#1010230: fixed in nvidia-graphics-drivers-legacy-390xx 390.151-1~deb10u1 has caused the Debian Bug report #1010230, regarding nvidia-graphics-drivers-legacy-390xx: spurious module build failure in

Bug#1010230: marked as done (nvidia-graphics-drivers-legacy-390xx: spurious module build failure in autopkgtest on armhf)

Your message dated Sun, 19 Jun 2022 17:02:08 + with message-id and subject line Bug#1010230: fixed in nvidia-graphics-drivers-legacy-390xx 390.151-1~deb11u1 has caused the Debian Bug report #1010230, regarding nvidia-graphics-drivers-legacy-390xx: spurious module build failure in

Bug#1012703: marked as done (vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant))

Your message dated Sun, 19 Jun 2022 14:44:48 + with message-id and subject line Bug#1012703: fixed in vtk9 9.1.0+really9.1.0+dfsg2-4 has caused the Debian Bug report #1012703, regarding vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant) to be marked as

Processed: Re: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...

Processing control commands: > notfound 1003353 2.114.0 Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules? No longer marked as found in versions lintian/2.114.0. -- 1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353 Debian Bug Tracking System Contact

Bug#1003353: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...

Control: notfound 1003353 2.114.0 Hi Andreas, Andreas Beckmann wrote: > found 1003353 2.114.0 please explain what makes you think that this issue is present in lintian 2.114.0 as currently in Debian Unstable. The submitter clearly said he ran into it when he bumped his lintian copy to git

Bug#1013193: closing 1013193

close 1013193 1.16.0-4 thanks

Processed: closing 1013193

Processing commands for cont...@bugs.debian.org: > close 1013193 1.16.0-4 Bug #1013193 [ros-image-proc] ros-image-proc: missing Breaks+Replaces: libimage-proc-dev (<< 1.16.0-3) Marked as fixed in versions ros-image-pipeline/1.16.0-4. Bug #1013193 [ros-image-proc] ros-image-proc: missing

Bug#1008415: libnih: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2

Hi Marius, Marius Gripsgard wrote: > libnih has been removed as dependency for lomiri-donwload-manager > for a good while upstream [0] Ah, nice! > but has not had a release with this in it yet. So I make a new > released lomiri-download-manager 0.1.1 with libnih removed as dep, > and uploaded

Bug#1012613: nftables: upgrade stops but does not start service

On 2022-06-19, at 13:48:59 +0200, Arturo Borrero Gonzalez wrote: > On Fri, 10 Jun 2022 12:21:37 +0200 Christian Göttsche wrote: > > Package: nftables > > Version: 1.0.4-1 > > Severity: serious > > > > Dear Maintainer, > > > > upgrades of nftables stop the service but do not start it (even if the >

Bug#1013223: bird2: FTBFS on arm64: make[1]: *** [Makefile:180: obj/lib/bitmap_test.ok] Error 1

Source: bird2 Version: 2.0.9-3 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=bird2=arm64=2.0.9-3=1649868353=0 obj/lib/bitmap_test:

Bug#1012613: nftables: upgrade stops but does not start service

On Fri, 10 Jun 2022 12:21:37 +0200 =?UTF-8?Q?Christian_G=C3=B6ttsche?= wrote: Package: nftables Version: 1.0.4-1 Severity: serious Dear Maintainer, upgrades of nftables stop the service but do not start it (even if the service is actually enabled). This can lead to lockouts, e.g. when using

Processed: bug 1012663 is forwarded to https://gitlab.kitware.com/paraview/paraview/-/issues/21442

Processing commands for cont...@bugs.debian.org: > forwarded 1012663 https://gitlab.kitware.com/paraview/paraview/-/issues/21442 Bug #1012663 [src:paraview] paraview: FTBFS in unstable (error: expected identifier or ‘(’ before numeric constant) Set Bug forwarded-to-address to

Processed (with 1 error): Re: paraview: FTBFS in unstable (error: expected identifier or ‘(’ before numeric constant)

Processing control commands: > tags -1 upstream patch Bug #1012663 [src:paraview] paraview: FTBFS in unstable (error: expected identifier or ‘(’ before numeric constant) Added tag(s) patch and upstream. > forwarded -1 Unknown command or malformed arguments to command. -- 1012663:

Bug#1012663: paraview: FTBFS in unstable (error: expected identifier or ‘(’ before numeric constant)

Control: tags -1 upstream patch Control: forwarded -1 https://gitlab.kitware.com/paraview/paraview/-/issues/21442 The attached patch resolves the issue by renaming the conflicting variable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1

Processed: Re: vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant)

Processing control commands: > tags -1 upstream patch Bug #1012703 [src:vtk9] vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant) Added tag(s) upstream and patch. > forwarded -1 https://gitlab.kitware.com/vtk/vtk/-/issues/18576 Bug #1012703 [src:vtk9] vtk9:

Bug#1012703: vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant)

Control: tags -1 upstream patch Control: forwarded -1 https://gitlab.kitware.com/vtk/vtk/-/issues/18576 The attached patch resolves the issue by renaming the conflicting variable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

On Sat, 2022-06-18 at 16:21 +0200, Ben Hutchings wrote: > On Thu, 2022-06-16 at 01:28 +0200, Ben Hutchings wrote: > [...] > > > linux-image-4.19.0-17-amd64 4.19.194-1 > > lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko > > linux-image-4.19.0-17-amd64 4.19.194-2 > >

Processed: closing 1013189

Processing commands for cont...@bugs.debian.org: > close 1013189 Bug #1013189 [src:node-babel-polyfills] node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider' Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Processed (with 1 error): Re: Fwd: Re: [Pkg-javascript-devel] Bug#1013218: rails: ftbfs SyntaxError: Unexpected token 'export'

Processing control commands: > forwarded -1 Unknown command or malformed arguments to command. > reassign -1 ruby-sprockets Bug #1013218 [rails,ruby-coffee-script-source] rails: ftbfs SyntaxError: Unexpected token 'export' Bug reassigned from package 'rails,ruby-coffee-script-source' to

Processed: Fwd: Re: [Pkg-javascript-devel] Bug#1013218: rails: ftbfs SyntaxError: Unexpected token 'export'

Processing control commands: > reassign -1 rails,ruby-coffee-script-source Bug #1013218 [rails,node-babel7] rails: ftbfs SyntaxError: Unexpected token 'export' Bug reassigned from package 'rails,node-babel7' to 'rails,ruby-coffee-script-source'. No longer marked as found in versions

Bug#1012600:

I'm no expert, but since these packages are in 'contrib' I suspect they don't have the ability to block package upgrades in 'main'. On Sun, Jun 19, 2022 at 5:51 AM Chris Putnam wrote: > > Apologies if this question is well-answered, but why isn't this package > holding back the kernel to 5.17?

Bug#1011990: marked as done (pappl: autopkgtest regression: fails on output to stderr)

Your message dated Sun, 19 Jun 2022 10:04:29 + with message-id and subject line Bug#1011990: fixed in pappl 1.2.1-1 has caused the Debian Bug report #1011990, regarding pappl: autopkgtest regression: fails on output to stderr to be marked as done. This means that you claim that the problem

Bug#1012600:

Apologies if this question is well-answered, but why isn't this package holding back the kernel to 5.17? In my mind an "apt upgrade" should not have pulled 5.18, especially when the net result may well be an unbootable system. Surely there's some way to mark this package as broken in tandem with

Processed: Re: [Pkg-javascript-devel] Bug#1013189: Bug#1013189: node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider'

Processing control commands: > notfound -1 5.65.0+dfsg+~cs9.20.9-13 Bug #1013189 [src:node-babel-polyfills] node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider' The source 'node-babel-polyfills' and version '5.65.0+dfsg+~cs9.20.9-13' do not appear to

Bug#1011726: switcheroo-control: FTBFS: AssertionError: 0 != 1

severity 1011726 important thanks On Thu, 26 May 2022 08:13:24 +0200 Lucas Nussbaum wrote: > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Hello, I cannot reproduce this on my laptop, not sure what happened I'll reduce the severity to important

Processed: Re: switcheroo-control: FTBFS: AssertionError: 0 != 1

Processing commands for cont...@bugs.debian.org: > severity 1011726 important Bug #1011726 [src:switcheroo-control] switcheroo-control: FTBFS: AssertionError: 0 != 1 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: reassign 1013189 to src:node-babel-polyfills, found 1013189 in 0~20220520+ds1-1 ...

Processing commands for cont...@bugs.debian.org: > reassign 1013189 src:node-babel-polyfills Bug #1013189 {Done: Yadd } [src:node-webpack] node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider' Bug reassigned from package 'src:node-webpack' to

Bug#1013189: marked as done (node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider')

Your message dated Sun, 19 Jun 2022 08:53:03 +0200 with message-id <11be2313-1e9b-bdac-cfec-2a456b43d...@debian.org> and subject line Re: [Pkg-javascript-devel] Bug#1013189: node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider' has caused the Debian Bug

Bug#1013189: [Pkg-javascript-devel] Bug#1013189: node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider'

On 18/06/2022 20:21, Pirate Praveen wrote: Package: src:node-webpack Version: 5.65.0+dfsg+~cs9.20.9-13 severity: serious failed to build on buildd https://buildd.debian.org/status/fetch.php?pkg=node-webpack=all=5.65.0%2Bdfsg%2B%7Ecs9.20.9-13=1654591817=0 likely a missing build depends

Bug#1002361: marked as done (python-testing.postgresql: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" returned exit code 13)

Your message dated Sun, 19 Jun 2022 06:19:43 + with message-id and subject line Bug#1002361: fixed in python-testing.common.database 2.0.3-1 has caused the Debian Bug report #1002361, regarding python-testing.postgresql: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i

Processed: Bug#1002361 marked as pending in python-testing.common.database

Processing control commands: > tag -1 pending Bug #1002361 [src:python-testing.postgresql] python-testing.postgresql: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. -- 1002361:

Bug#1002361: marked as pending in python-testing.common.database

Control: tag -1 pending Hello, Bug #1002361 in python-testing.common.database 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: