Bug#998156: contains non-DFSG-free files

Package: mlton Version: 20100608-5.1 Severity: serious Tags: upstream X-Debbugs-Cc: r...@debian.org Since at least oldoldoldstable, the mlton sources have included non-free files. In particular, the tarball lib/ckit-lib/ckit.tgz contains the files ckit/src/parser/util/error.sml and

Bug#998154: contains non-DSFG-free files

Package: smlnj Version: 110.76-2 Severity: serious Tags: upstream Since at least oldoldoldstable, the SML/NJ sources have included non-free files. In 110.76-2, these non-free files include at least ckit.tgz, which contains the files ckit/src/parser/util/error.sml and

Bug#997820: marked as done (python3-trezor: Depends: python3-click (< 8) but 8.0.2-1 is to be installed)

Your message dated Sun, 31 Oct 2021 02:35:53 + with message-id and subject line Bug#997820: fixed in python-trezor 0.12.4-1 has caused the Debian Bug report #997820, regarding python3-trezor: Depends: python3-click (< 8) but 8.0.2-1 is to be installed to be marked as done. This means that

Bug#997820: marked as pending in python-trezor

Control: tag -1 pending Hello, Bug #997820 in python-trezor 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#997820 marked as pending in python-trezor

Processing control commands: > tag -1 pending Bug #997820 [python3-trezor] python3-trezor: Depends: python3-click (< 8) but 8.0.2-1 is to be installed Added tag(s) pending. -- 997820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997820 Debian Bug Tracking System Contact

Bug#997461: marked as done (target-factory: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Sun, 31 Oct 2021 00:19:09 + with message-id and subject line Bug#997461: fixed in target-factory 1.4-2 has caused the Debian Bug report #997461, regarding target-factory: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff

Bug#984279: marked as done (openzwave: ftbfs with GCC-11)

Your message dated Sat, 30 Oct 2021 21:49:42 + with message-id and subject line Bug#984279: fixed in openzwave 1.6.1914+ds-1 has caused the Debian Bug report #984279, regarding openzwave: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#995123: marked as done (cyrus-sasl2 FTBFS: sphinx: AttributeError: 'CyrusManualPageBuilder' object has no attribute 'settings')

Your message dated Sat, 30 Oct 2021 21:33:31 + with message-id and subject line Bug#995123: fixed in cyrus-sasl2 2.1.27+dfsg-2.2 has caused the Debian Bug report #995123, regarding cyrus-sasl2 FTBFS: sphinx: AttributeError: 'CyrusManualPageBuilder' object has no attribute 'settings' to be

Bug#997471: marked as done (loguru: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

Your message dated Sat, 30 Oct 2021 21:06:42 + with message-id and subject line Bug#997471: fixed in loguru 0.5.3-4 has caused the Debian Bug report #997471, regarding loguru: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to be

Processed: bug 995356 is forwarded to https://github.com/wolever/parameterized/issues/122

Processing commands for cont...@bugs.debian.org: > forwarded 995356 https://github.com/wolever/parameterized/issues/122 Bug #995356 [src:python-parameterized] python-parameterized: autopkgtest regression: AssertionError in tearDownModule Set Bug forwarded-to-address to

Bug#998143: gatb-core breaks discosnp autopkgtest: Segmentation fault

Source: gatb-core, discosnp Control: found -1 gatb-core/1.4.2+dfsg-7 Control: found -1 discosnp/4.4.4-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of

Processed: gatb-core breaks discosnp autopkgtest: Segmentation fault

Processing control commands: > found -1 gatb-core/1.4.2+dfsg-7 Bug #998143 [src:gatb-core, src:discosnp] gatb-core breaks discosnp autopkgtest: Segmentation fault Marked as found in versions gatb-core/1.4.2+dfsg-7. > found -1 discosnp/4.4.4-2 Bug #998143 [src:gatb-core, src:discosnp] gatb-core

Bug#998142: opencv breaks node-opencv autopkgtest: c++ Exception processing resize

Source: opencv, node-opencv Control: found -1 opencv/4.5.4+dfsg-1 Control: found -1 node-opencv/7.0.0+git20200310.6c13234-3 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a

Processed: opencv breaks node-opencv autopkgtest: c++ Exception processing resize

Processing control commands: > found -1 opencv/4.5.4+dfsg-1 Bug #998142 [src:opencv, src:node-opencv] opencv breaks node-opencv autopkgtest: c++ Exception processing resize Marked as found in versions opencv/4.5.4+dfsg-1. > found -1 node-opencv/7.0.0+git20200310.6c13234-3 Bug #998142

Processed: opencv breaks auto-multiple-choice autopkgtest

Processing control commands: > found -1 opencv/4.5.4+dfsg-1 Bug #998141 [src:opencv, src:auto-multiple-choice] opencv breaks auto-multiple-choice autopkgtest Marked as found in versions opencv/4.5.4+dfsg-1. > found -1 auto-multiple-choice/1.5.1-2 Bug #998141 [src:opencv,

Bug#998141: opencv breaks auto-multiple-choice autopkgtest

Source: opencv, auto-multiple-choice Control: found -1 opencv/4.5.4+dfsg-1 Control: found -1 auto-multiple-choice/1.5.1-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent

Processed: opencv breaks caffe autopkgtest: (-4:Insufficient memory) Failed to allocate 160708409713560 bytes in function 'OutOfMemoryError'

Processing control commands: > found -1 opencv/4.5.4+dfsg-1 Bug #998140 [src:opencv, src:caffe] opencv breaks caffe autopkgtest: (-4:Insufficient memory) Failed to allocate 160708409713560 bytes in function 'OutOfMemoryError' Marked as found in versions opencv/4.5.4+dfsg-1. > found -1

Processed: src:browser-request: fails to migrate to testing for too long: uploader built arch:all binaries

Processing control commands: > close -1 0.3.3-4 Bug #998139 [src:browser-request] src:browser-request: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions browser-request/0.3.3-4. Bug #998139 [src:browser-request] src:browser-request: fails to

Bug#998139: src:browser-request: fails to migrate to testing for too long: uploader built arch:all binaries

Source: browser-request Version: 0.3.3-2 Severity: serious Control: close -1 0.3.3-4 X-Debbugs-CC: jel...@debian.org 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

Processed: src:rust-utf-8: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 0.7.6-1 Bug #998138 [src:rust-utf-8] src:rust-utf-8: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions rust-utf-8/0.7.6-1. Bug #998138 [src:rust-utf-8] src:rust-utf-8: fails to migrate to testing for too long:

Bug#998138: src:rust-utf-8: fails to migrate to testing for too long: autopkgtest regression

Source: rust-utf-8 Version: 0.7.5-1 Severity: serious Control: close -1 0.7.6-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 995419 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Processed: src:python-parameterized: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 0.8.1-1 Bug #998137 [src:python-parameterized] src:python-parameterized: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions python-parameterized/0.8.1-1. Bug #998137 [src:python-parameterized]

Bug#998137: src:python-parameterized: fails to migrate to testing for too long: autopkgtest regression

Source: python-parameterized Version: 0.7.0-2 Severity: serious Control: close -1 0.8.1-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 995356 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Bug#997758: marked as done (nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220))

Your message dated Sat, 30 Oct 2021 20:34:51 + with message-id and subject line Bug#997758: fixed in nose 1.3.7-8 has caused the Debian Bug report #997758, regarding nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220) to be marked as done.

Processed: src:node-toidentifier: fails to migrate to testing for too long: uploader built arch:all binaries

Processing control commands: > close -1 1.0.0-4 Bug #998136 [src:node-toidentifier] src:node-toidentifier: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions node-toidentifier/1.0.0-4. Bug #998136 [src:node-toidentifier] src:node-toidentifier:

Bug#997521: freedict: FTBFS: Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No such file or directory

On 29/10/21 at 16:17 +0200, Sebastian Humenda wrote: > Hi > > Due to the way the FreeDict stylesheets are written, a lot of memory is used. > Could you provide the amount of RAM that is used for the failed build? If it > is below 16G, could it be increased, somehow? Hi Sebastian, I use AWS EC2

Bug#998136: src:node-toidentifier: fails to migrate to testing for too long: uploader built arch:all binaries

Source: node-toidentifier Version: 1.0.0-2 Severity: serious Control: close -1 1.0.0-4 X-Debbugs-CC: jel...@debian.org 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

Processed: src:node-xdg-basedir: fails to migrate to testing for too long: uploader built arch:all binaries

Processing control commands: > close -1 3.0.0-2 Bug #998135 [src:node-xdg-basedir] src:node-xdg-basedir: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions node-xdg-basedir/3.0.0-2. Bug #998135 [src:node-xdg-basedir] src:node-xdg-basedir: fails

Bug#998135: src:node-xdg-basedir: fails to migrate to testing for too long: uploader built arch:all binaries

Source: node-xdg-basedir Version: 3.0.0-1 Severity: serious Control: close -1 3.0.0-2 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm 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

Bug#997122: marked as done (assembly-stats: FTBFS: fastq_unittest.cpp:53:78: error: taking address of rvalue [-fpermissive])

Your message dated Sat, 30 Oct 2021 20:33:47 + with message-id and subject line Bug#997122: fixed in assembly-stats 1.0.1+ds-5 has caused the Debian Bug report #997122, regarding assembly-stats: FTBFS: fastq_unittest.cpp:53:78: error: taking address of rvalue [-fpermissive] to be marked as

Bug#997940: view3dscene: FTBFS with fpc 3.2.2

Hi Abou, Our messages crossed. On 30-10-2021 22:09, Abou Al Montacir wrote: > On Sat, 2021-10-30 at 15:21 +0200, Paul Gevers wrote: >>  In that way, the Debian >> infrastructure knows that a rebuild (or potentially manual action) is >> needed. We don't want it to be too tight. > I don't know

Bug#997940: [Pkg-pascal-devel] Bug#997940: view3dscene: FTBFS with fpc 3.2.2

Hi, On 30-10-2021 15:21, Paul Gevers wrote: > Hi Abou, > > On 30-10-2021 12:46, Abou Al Montacir wrote: >>> "Just" rebuilding is not the solution to paper over such an issue, we'd >>> need to prevent it from going unnoticed next time. It should show up on >>>

Bug#997940: view3dscene: FTBFS with fpc 3.2.2

Hi Paul, On Sat, 2021-10-30 at 15:21 +0200, Paul Gevers wrote: > So all libraries need a Depends on a binary from src:fpc with an upper > limit (generated during the build). In some sense, this is done as any FPC library should depend on RTL package fp- units-rtl-${UPSTREAM_VERSION} with >=

Processed: Bug#997122 marked as pending in assembly-stats

Processing control commands: > tag -1 pending Bug #997122 [src:assembly-stats] assembly-stats: FTBFS: fastq_unittest.cpp:53:78: error: taking address of rvalue [-fpermissive] Added tag(s) pending. -- 997122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997122 Debian Bug Tracking System

Bug#997122: marked as pending in assembly-stats

Control: tag -1 pending Hello, Bug #997122 in assembly-stats 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: reassign 998126 to src:pipewire, severity of 998126 is serious

Processing commands for cont...@bugs.debian.org: > reassign 998126 src:pipewire 0.3.39-3 Bug #998126 [pipewire-pulse-dbgsym] pipewire-pulse-dbgsym: dbgsym files overlap between packages Warning: Unknown package 'pipewire-pulse-dbgsym' Bug reassigned from package 'pipewire-pulse-dbgsym' to

Bug#996569: getmail6 naming issues

I'd like to strongly object to the removal of this package from Debian. As per the Debian social contract: "4. Our priorities are our users and free software. We will be guided by the needs of our users and the free software community. *We will place their interests first in our priorities*".

Bug#998131: src:node-yamlish: fails to migrate to testing for too long: uploader built arch:all binaries

Source: node-yamlish Version: 0.0.7-1 Severity: serious Control: close -1 0.0.7-3 X-Debbugs-CC: jel...@debian.org 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

Processed: src:node-yamlish: fails to migrate to testing for too long: uploader built arch:all binaries

Processing control commands: > close -1 0.0.7-3 Bug #998131 [src:node-yamlish] src:node-yamlish: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions node-yamlish/0.0.7-3. Bug #998131 [src:node-yamlish] src:node-yamlish: fails to migrate to

Processed: severity of 996170 is important

Processing commands for cont...@bugs.debian.org: > severity 996170 important Bug #996170 [src:linux] linux: FTBFS if bpftool detects clang-bpf-co-re Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 996170:

Bug#997258: marked as done (tiddit: FTBFS: Translocation.cpp:13:74: error: taking address of rvalue [-fpermissive])

Your message dated Sat, 30 Oct 2021 19:35:12 + with message-id and subject line Bug#997258: fixed in tiddit 2.12.1+dfsg-2 has caused the Debian Bug report #997258, regarding tiddit: FTBFS: Translocation.cpp:13:74: error: taking address of rvalue [-fpermissive] to be marked as done. This

Processed: Bug#997258 marked as pending in tiddit

Processing control commands: > tag -1 pending Bug #997258 [src:tiddit] tiddit: FTBFS: Translocation.cpp:13:74: error: taking address of rvalue [-fpermissive] Added tag(s) pending. -- 997258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997258 Debian Bug Tracking System Contact

Bug#997258: marked as pending in tiddit

Control: tag -1 pending Hello, Bug #997258 in tiddit 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#997758: marked as pending in nose

Control: tag -1 pending Hello, Bug #997758 in nose 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#997758 marked as pending in nose

Processing control commands: > tag -1 pending Bug #997758 [src:nose] nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220) Added tag(s) pending. -- 997758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997758 Debian Bug Tracking System Contact

Bug#998114: Missing egg info directory prevents asciidoc cli tools from running

Hi Leon, Am Sat, Oct 30, 2021 at 06:45:28PM +0200 schrieb Leon Marz: > Thank you very much for finding the problem. I was quite confused since > everything was installed in the right place. As you already mentioned, > lintian doesn't like the egg-info directory and neither do I, so I wrote >

Bug#995421: rust-bumpalo: autopkgtest armhf regression: oom_instead_of_bump_pointer_overflow

It passes when run with only packages from testing. no it doesn't, it's skipped due to unsatisfiable dependencies. However manual testing shows that the underlying failure does affect the version in testing, so this is not *really* a regression it just looks like one to debci. I copied some

Bug#998125: libasound2-plugins: Config file for a52 plugin (60-a52-encoder.conf) produces no/garbled sound via optical digital out (S/PDIF)

Package: libasound2-plugins Version: 1.2.2-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Fresh Debian 11 install. I want to output 5.1 sound via toslink. Used KDE settings to switch from analog output to digital out 5.1. This produced

Bug#998108: firefox freezes shortly after start

Hi, same issue here: - AMD64 install - Debian testing + firefox from unstable After 93.0-1+b1 install, firefox freeze on some web sites, specially when new tab open a new link. According to "strace" command, this is look faulted tab open nvidia library, so maybe

Bug#998124: meson: gnome module missing install_dir fix for c_template

Package: meson Version: 0.60.0-1 Severity: serious Justification: Makes gedit FTBFS Hello, In addition to the issue raised in #997936, we have this happening when building the gedit package: dh_auto_configure -- -Dgtk_doc=true cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..

Bug#984200: marked as done (libpdb-redo: ftbfs with GCC-11)

Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#984093: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #984093, regarding libpdb-redo: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#993324: marked as done (libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp)

Your message dated Sat, 30 Oct 2021 18:00:11 + with message-id and subject line Bug#993324: fixed in gsl 2.7+dfsg-3 has caused the Debian Bug report #993324, regarding libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp to be marked as done. This means that you claim that the

Bug#984369: marked as done (tortoize: ftbfs with GCC-11)

Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#984093: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #984093, regarding tortoize: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#984093: marked as done (libcifpp: ftbfs with GCC-11)

Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#984093: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #984093, regarding libcifpp: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#984042: marked as done (dssp: ftbfs with GCC-11)

Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#984093: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #984093, regarding dssp: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#974793: marked as done (oclgrind: Please upgrade to llvm-toolchain-11)

Your message dated Sat, 30 Oct 2021 18:00:15 + with message-id and subject line Bug#974793: fixed in oclgrind 21.10-1 has caused the Debian Bug report #974793, regarding oclgrind: Please upgrade to llvm-toolchain-11 to be marked as done. This means that you claim that the problem has been

Bug#974813: marked as done (oclgrind: Please upgrade to llvm-toolchain-11)

Your message dated Sat, 30 Oct 2021 18:00:15 + with message-id and subject line Bug#974793: fixed in oclgrind 21.10-1 has caused the Debian Bug report #974793, regarding oclgrind: Please upgrade to llvm-toolchain-11 to be marked as done. This means that you claim that the problem has been

Bug#984157: closed by Debian FTP Masters (reply to bott...@debian.org (A. Maitland Bottoms)) (Bug#984157: fixed in uhd 3.15.0.0-5)

Control: retitle -1 libuhd-dev does not support C++20 Control: severity -1 normal On Fri, Oct 29, 2021 at 10:32:07PM +0300, Adrian Bunk wrote: > On Fri, Oct 22, 2021 at 06:06:06AM +, Debian Bug Tracking System wrote: > >... > > /usr/include/uhd/property_tree.ipp:26:50: error: expected ‘)’

Processed: Re: Bug#984157: closed by Debian FTP Masters (reply to bott...@debian.org (A. Maitland Bottoms)) (Bug#984157: fixed in uhd 3.15.0.0-5)

Processing control commands: > retitle -1 libuhd-dev does not support C++20 Bug #984157 [src:uhd] gnss-sdr: ftbfs with GCC-11 Changed Bug title to 'libuhd-dev does not support C++20' from 'gnss-sdr: ftbfs with GCC-11'. > severity -1 normal Bug #984157 [src:uhd] libuhd-dev does not support C++20

Bug#913159: marked as done (task-kannada-desktop: uninstallable on mips and mipsel)

Your message dated Sat, 30 Oct 2021 18:14:21 +0200 with message-id <20211030181421.dca8b82f05e51092b9950...@mailbox.org> and subject line Re: Bug#913159: task-kannada-desktop: uninstallable on mips and mipsel has caused the Debian Bug report #913159, regarding task-kannada-desktop: uninstallable

Processed: Re: Bug#997359: Inkscape crashes when running as batch without X11

Processing control commands: > forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/2899 Bug #997359 [inkscape] Inkscape crashes when running as batch without X11 Set Bug forwarded-to-address to 'https://gitlab.com/inkscape/inkscape/-/issues/2899'. -- 997359:

Bug#997359: Inkscape crashes when running as batch without X11

Control: forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/2899 On Sun, Oct 24, 2021 at 06:57:14PM +0200, Ole Streicher wrote: > On 24.10.21 18:29, Mattia Rizzolo wrote: > > Since you managed to reproduce it and all, could you perhaps consider > > forwarding it yourself on

Bug#998108: firefox freezes shortly after start

Hi, I am affected by the same problem. After downgrading to firefox=93.0-1 from snapshot.debian.org the problem is gone. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- OpenPGP_signature Description: OpenPGP digital

Processed: forwarded 997486

Processing commands for cont...@bugs.debian.org: > forwarded 997486 https://github.com/pytroll/pycoast/issues/57 Bug #997486 [src:pycoast] pycoast: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 Set Bug forwarded-to-address to

Bug#997119: marked as done (symfony: FTBFS: tests failed variable (T_VARIABLE))

Your message dated Sat, 30 Oct 2021 14:50:32 + with message-id and subject line Bug#997119: fixed in php-psr-link 1.1.0+really1.0.0-1 has caused the Debian Bug report #997119, regarding symfony: FTBFS: tests failed variable (T_VARIABLE) to be marked as done. This means that you claim that

Processed: limit source to php-psr-link, tagging 997119

Processing commands for cont...@bugs.debian.org: > limit source php-psr-link Limiting to bugs with field 'source' containing at least one of 'php-psr-link' Limit currently set to 'source':'php-psr-link' > tags 997119 + pending Bug #997119 [php-psr-link] symfony: FTBFS: tests failed variable

Processed: reassign 997119 to php-psr-link, affects 997119

Processing commands for cont...@bugs.debian.org: > reassign 997119 php-psr-link 1.1.0-1 Bug #997119 [src:symfony] symfony: FTBFS: tests failed variable (T_VARIABLE) Bug reassigned from package 'src:symfony' to 'php-psr-link'. No longer marked as found in versions symfony/4.4.19+dfsg-2. Ignoring

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 997933 https://github.com/OfflineIMAP/offlineimap/issues/706 Bug #997933 [offlineimap3] offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com Set Bug forwarded-to-address to

Bug#998114: Missing egg info directory prevents asciidoc cli tools from running

Source: asciidoc Version: 10.0.1-1 Severity: grave Justification: Causes builds of packages using asciidoc to build documentation to fail Tags: patch X-Debbugs-Cc: su...@debian.org /usr/bin/asciidoc and /usr/bin/a2x rely on python distribution info to locate the entry point. These files are

Bug#997188: marked as done (irqbalance: FTBFS: ui/ui.c:28:24: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Sat, 30 Oct 2021 13:35:34 + with message-id and subject line Bug#997188: fixed in irqbalance 1.8.0-1 has caused the Debian Bug report #997188, regarding irqbalance: FTBFS: ui/ui.c:28:24: error: format not a string literal and no format arguments [-Werror=format-security]

Bug#998108: Acknowledgement (firefox freezes shortly after start)

Sometimes it seems that firefox doesn't freeze "immediatly" but some sites continue to work (and e.g. the address bar still allows input). But new sites (especially with JS stuff) don't load correctly or just freeze. Eventually whole firefox freezes and one cannot event select the address bar

Bug#998113: src:osmnx: fails to migrate to testing for too long: autopkgtest regression

Source: osmnx Version: 1.0.1+ds-1 Severity: serious Control: close -1 1.1.1+ds-4 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 995021 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Processed: src:osmnx: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 1.1.1+ds-4 Bug #998113 [src:osmnx] src:osmnx: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions osmnx/1.1.1+ds-4. Bug #998113 [src:osmnx] src:osmnx: fails to migrate to testing for too long: autopkgtest

Processed: src:rust-bumpalo: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 3.7.0-2 Bug #998111 [src:rust-bumpalo] src:rust-bumpalo: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions rust-bumpalo/3.7.0-2. Bug #998111 [src:rust-bumpalo] src:rust-bumpalo: fails to migrate to testing for

Bug#998112: src:reqwest: fails to migrate to testing for too long: upload built arch:all binaries

Source: reqwest Version: 0.6.0-2 Severity: serious Control: close -1 0.6.0-3 Tags: sid bookworm pending X-Debbugs-CC: jel...@debian.org 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

Processed: src:reqwest: fails to migrate to testing for too long: upload built arch:all binaries

Processing control commands: > close -1 0.6.0-3 Bug #998112 [src:reqwest] src:reqwest: fails to migrate to testing for too long: upload built arch:all binaries Marked as fixed in versions reqwest/0.6.0-3. Bug #998112 [src:reqwest] src:reqwest: fails to migrate to testing for too long: upload

Bug#998111: src:rust-bumpalo: fails to migrate to testing for too long: autopkgtest regression

Source: rust-bumpalo Version: 3.4.0-1 Severity: serious Control: close -1 3.7.0-2 Tags: sid bookworm 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 days

Bug#997940: [Pkg-pascal-devel] Bug#997940: view3dscene: FTBFS with fpc 3.2.2

Hi Abou, On 30-10-2021 12:46, Abou Al Montacir wrote: >> "Just" rebuilding is not the solution to paper over such an issue, we'd >> need to prevent it from going unnoticed next time. It should show up on >> https://release.debian.org/transitions/ >>  with

Processed: reopening 997119

Processing commands for cont...@bugs.debian.org: > reopen 997119 Bug #997119 {Done: David Prévot } [src:symfony] symfony: FTBFS: tests failed variable (T_VARIABLE) 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to

Bug#998108: firefox freezes shortly after start

Package: firefox Version: 93.0-1+b1 Severity: grave Justification: renders package unusable Hey. Since about yesterday (possibly since the rebuilt package came in) firefox freezes shortly after being started. There is no high CPU activity then, it just takes no input anymore (no keyboard, no

Bug#998107: src:simile-timeline: fails to migrate to testing for too long: uploader built arch:all binaries

Source: simile-timeline Version: 2.3.0+dfsg1-4 Severity: serious Control: close -1 2.3.0+dfsg1-6 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are

Processed: src:simile-timeline: fails to migrate to testing for too long: uploader built arch:all binaries

Processing control commands: > close -1 2.3.0+dfsg1-6 Bug #998107 [src:simile-timeline] src:simile-timeline: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions simile-timeline/2.3.0+dfsg1-6. Bug #998107 [src:simile-timeline]

Processed: mpi4py: test_io.TestIOSelf failures on i386

Processing control commands: > forwarded -1 https://github.com/mpi4py/mpi4py/issues/105 Bug #998106 [src:mpi4py] mpi4py: test_io.TestIOSelf failures on i386 Set Bug forwarded-to-address to 'https://github.com/mpi4py/mpi4py/issues/105'. -- 998106:

Bug#998106: mpi4py: test_io.TestIOSelf failures on i386

Source: mpi4py Version: 3.1.1-8 Severity: serious Justification: debci Control: forwarded -1 https://github.com/mpi4py/mpi4py/issues/105 mpi4py tests are failing on i386 debci. e.g. https://ci.debian.net/data/autopkgtest/unstable/i386/m/mpi4py/16315322/log.gz The failing tests are file IO tests

Bug#997233: marked as done (loudgain: FTBFS: ld: cannot find -lz)

Your message dated Sat, 30 Oct 2021 12:03:50 + with message-id and subject line Bug#997233: fixed in loudgain 0.6.8+ds-2 has caused the Debian Bug report #997233, regarding loudgain: FTBFS: ld: cannot find -lz to be marked as done. This means that you claim that the problem has been dealt

Bug#995317: marked as done (apertium broken on s390x due to missing endianness definition)

Your message dated Sat, 30 Oct 2021 12:03:35 + with message-id and subject line Bug#995317: fixed in apertium 3.7.2-1 has caused the Debian Bug report #995317, regarding apertium broken on s390x due to missing endianness definition to be marked as done. This means that you claim that the

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 997233 + pending Bug #997233 [src:loudgain] loudgain: FTBFS: ld: cannot find -lz Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 997233:

Bug#997940: view3dscene: FTBFS with fpc 3.2.2

Hi Paul, > So, where should this tight dependency be recorded? Should we teach some > binary from castle-game-engine to be strict about some src:fpc counterpart? Normally, any new version of FPC should trigger a rebuild of the entire libraries (not programs) packaged for FPC. The reason is that

Bug#990224: [Pkg-pascal-devel] Bug#990224: lazarus-src-2.0: leaves diversion after upgrade from sid to experimental

The issue here is that LPK files are needed by binary libs (pascal units / ppu) and source packages. The right solution would be probably to move them into a separate packages that is used by both source and binaries. However, that ppu files are distributed not as a unique packages but split into

Processed: bug 984083 is forwarded to https://sourceforge.net/p/lasi/bugs/9/

Processing commands for cont...@bugs.debian.org: > forwarded 984083 https://sourceforge.net/p/lasi/bugs/9/ Bug #984083 [src:lasi] lasi: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://sourceforge.net/p/lasi/bugs/9/'. > thanks Stopping processing here. Please contact me if you need

Bug#997170: nmon: FTBFS: lmon16m.c:5478:45: error: format not a string literal and no format arguments [-Werror=format-security]

Hi, On Sat, Oct 23, 2021 at 09:07:29PM +0200, Lucas Nussbaum wrote: > Source: nmon > Version: 16m+debian-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part

Bug#997502: marked as done (pyresample: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

Your message dated Sat, 30 Oct 2021 09:48:40 + with message-id and subject line Bug#997502: fixed in pyresample 1.22.0-1 has caused the Debian Bug report #997502, regarding pyresample: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to

Processed: tagging 998026

Processing commands for cont...@bugs.debian.org: > tags 998026 + sid bookworm Bug #998026 {Done: Peter Pentchev } [libmodulemd] libmodulemd: autopkgtest fails with meson 0.60 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 998026:

Bug#998100: ruby-libxml: FTBFS on armhf and ppc64el

Source: ruby-libxml Version: 3.2.1-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | TestNS#test_duplicate_ns = /<>/test/test_namespace.rb:41: [BUG] Segmentation fault at 0x0018 |

Bug#998099: ruby-hitimes: FTBFS on s390x

Source: ruby-hitimes Version: 1.2.1-4 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | Failures: | | 1) Hitimes::Interval can time a block of code | Failure/Error: d.should

Bug#987379: llvm-toolchain-11 autopkgtest segfaults on armhf

Control: reassign -1 binutils 2.37-7 Control: affects -1 src:lvm-toolchain-12 On 2021-10-28 15:50:35 +0200, Julien Cristau wrote: > On Tue, Oct 26, 2021 at 04:14:35PM +0200, Paul Gevers wrote: > > Hi Diederik, all, > > > > On 26-10-2021 08:34, Diederik de Haas wrote: > > > Therefor it may be

Bug#997186: marked as done (nast: FTBFS: ncurses/n_nast.c:686:46: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Sat, 30 Oct 2021 09:03:29 + with message-id and subject line Bug#997186: fixed in nast 0.2.0-9 has caused the Debian Bug report #997186, regarding nast: FTBFS: ncurses/n_nast.c:686:46: error: format not a string literal and no format arguments [-Werror=format-security] to

Bug#998097: ruby-eventmachine FTBFS on IPV6-only buildds and accesses the internet during the build

Source: ruby-eventmachine Severity: serious Tags: ftbfs FTBFS on IPV6-only buildds: https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine=amd64=1.3~pre20201020-b50c135-3=1633500476=0

Processed: tagging 998091

Processing commands for cont...@bugs.debian.org: > tags 998091 + sid experimental bookworm Bug #998091 [src:libclc] libclc: Keep out of bookworm Added tag(s) experimental, bookworm, and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 998091:

Bug#998091: libclc: Keep out of bookworm

Source: libclc Version: 0.2.0+git20190827-8 Severity: serious Hello, libclc should be kept out of bookworm as packages built from llvm now offer the same files The package should more than probably be removed from the archive, but I let you open a RM bug (or reassign this one) Kind regards,

  1   2   >