Bug#1058254: marked as pending in python-keystonemiddleware
Control: tag -1 pending Hello, Bug #1058254 in python-keystonemiddleware 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/openstack-team/libs/python-keystonemiddleware/-/commit/a40753ecf611ace3557ded3315f4bf5ef6d82b74 Add do-not-use-utcnow.patch (Closes: #1058254). (this message was generated automatically) -- Greetings https://bugs.debian.org/1058254
Processed: Bug#1058254 marked as pending in python-keystonemiddleware
Processing control commands: > tag -1 pending Bug #1058254 [src:python-keystonemiddleware] python-keystonemiddleware: FTBFS: make[1]: pyversions: No such file or directory Added tag(s) pending. -- 1058254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058208: marked as done (pytorch-sparse: FTBFS: ImportError: Failed to load PyTorch C extensions:)
Your message dated Thu, 14 Dec 2023 07:35:10 +
with message-id
and subject line Bug#1058208: fixed in pytorch-sparse 0.6.18-2
has caused the Debian Bug report #1058208,
regarding pytorch-sparse: FTBFS: ImportError: Failed to load PyTorch C
extensions:
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.)
--
1058208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytorch-sparse
Version: 0.6.18-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 8, in
> import torch
> File "/usr/lib/python3/dist-packages/torch/__init__.py", line 443, in
>
> raise ImportError(textwrap.dedent('''
> ImportError: Failed to load PyTorch C extensions:
> It appears that PyTorch has loaded the `torch/_C` folder
> of the PyTorch repository rather than the C extensions which
> are expected in the `torch._C` namespace. This can occur when
> using the `install` workflow. e.g.
> $ python setup.py install && python -c "import torch"
>
> This error can generally be solved using the `develop` workflow
> $ python setup.py develop && python -c "import torch" # This should
> succeed
> or by running Python from a different directory.
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:10: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/pytorch-sparse_0.6.18-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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.
--- End Message ---
--- Begin Message ---
Source: pytorch-sparse
Source-Version: 0.6.18-2
Done: Andrius Merkys
We believe that the bug you reported is fixed in the latest version of
pytorch-sparse, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrius Merkys (supplier of updated pytorch-sparse 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, 14 Dec 2023 02:10:34 -0500
Source: pytorch-sparse
Architecture: source
Version: 0.6.18-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team
Changed-By: Andrius Merkys
Closes: 1058208
Changes:
pytorch-sparse (0.6.18-2) unstable; urgency=medium
.
* Build only on default Python (Closes: #1058208)
Checksums-Sha1:
5255d9b3afd9a464530489a861f206ba13689b11 2293 pytorch-sparse_0.6.18-2.dsc
a7105ce8947620d12854ac7acfadd86de187e20f 2412
pytorch-sparse_0.6.18-2.debian.tar.xz
61aa72c9935605f3c5c3ef080ba5b77e55c29a32 19275
pytorch-sparse_0.6.18-2_source.buildinfo
Checksums-Sha256:
b6d2e33959e5515dc4015f21473a3f9de62ecd57bd149e9ad4b18698af4c2dd5 2293
pytorch-sparse_0.6.18-2.dsc
0c869301a9e8fa3d8f91a46943e6e3526befddca0633b96a65fdfcd88c7a204e 2412
pytorch-sparse_0.6.18-2.debian.tar.xz
2c555b41098c91631c0a2c2d5ac0e4b9ef9ef1c512c74ad0498d82bea0ed099e 19275
pytorch-sparse_0.6.18-2_source.buildinfo
Files:
Processed (with 1 error): (No Subject)
Processing commands for cont...@bugs.debian.org: > tags 1056225 + fixed-upstream Bug #1056225 [src:aioquic] aioquic's autopkg tests fail with Python 3.12 Added tag(s) fixed-upstream. > merge 1056225 1058365 Bug #1056225 [src:aioquic] aioquic's autopkg tests fail with Python 3.12 Unable to merge bugs because: affects of #1058365 is 'src:python-lsp-server' not '' package of #1058365 is 'python-jedi' not 'src:aioquic' Failed to merge 1056225: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056225 1058365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058555: [Help] Missing proper Build-Depends from libreoffice (Wass: Bug#1058555: parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory)
Hi, Am 13.12.23 um 16:19 schrieb Andreas Tille: Control: tags -1 help Am Tue, Dec 12, 2023 at 09:52:48PM +0100 schrieb Lucas Nussbaum: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory This file is (re-)created via libreoffice --headless --convert-to pdf parallel_cheat_bw.fodt Formerly this worked with the only Build-Depends libreoffice-writer-nogui. Possibly since latest upgrade of libreoffice suite I had to add the following Build-Depends: libreoffice-java-common, ure-java, default-jre-headless I don't see why. Writer document conversion doesn't need Java. I admit the fact that default-jre-headless is no dependency of libreoffice-java-common smells like a bug in the dependencies but well, I have not enough insight here. No, data shouldn't depend on a JRE. Neither should libraries per Java policy anyway. Unfortunately this is not sufficient to recreate the pdf. I rather get /build/parallel-20231122+ds/src # libreoffice --headless --convert-to pdf parallel_cheat_bw.fodt Error: source file could not be loaded inside the pbuilder environment where I'm building the package. However, if I try on my local (testing!) system I get: .../parallel/src(master) $ libreoffice --headless --convert-to pdf parallel_cheat_bw.fodt convert .../parallel/src/parallel_cheat_bw.fodt as a Writer document -> .../parallel/src/parallel_cheat_bw.pdf using filter : writer_pdf_Export so the conversion is working. This pretty much sounds like some additional missing build depends which is installed in my more or less functional desktop installation of libreoffice. Rene, do you have some idea what Build-Depends might be missing in my pbuilder chroot to let the convert process work properly? Probably you have -core installed? See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052052 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058653 Regards, Rene Kind regards Andreas.
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org:
> tags 1058365 + fixed-upstream
Bug #1058365 [python-jedi] python-lsp-server: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1058536 marked as pending in ironic-inspector
Processing control commands: > tag -1 pending Bug #1058536 [src:ironic-inspector] ironic-inspector: FTBFS: AttributeError: 'called_once_with' is not a valid assertion. Use a spec for the mock if 'called_once_with' is meant to be an attribute.. Did you mean: 'assert_called_once_with'? Added tag(s) pending. -- 1058536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058536: marked as pending in ironic-inspector
Control: tag -1 pending Hello, Bug #1058536 in ironic-inspector 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/openstack-team/services/ironic-inspector/-/commit/83b30760e1934b14b274eb46cbf575c804d1fa62 * Blacklist TestManagerDelHost.test_del_host_with_coordinator (Closes: #1058536). (this message was generated automatically) -- Greetings https://bugs.debian.org/1058536
Bug#1058657: python3-apt: undefined symbol: PyAptWarning
Package: python3-apt Version: 2.7.2 Severity: serious Dear Maintainer, This morning I see : , | dak@christian ~ % dak dominate | Traceback (most recent call last): | File "/usr/bin/dak", line 43, in | import daklib.utils | File "/usr/lib/python3/dist-packages/daklib/utils.py", line 32, in | import apt_inst | ImportError: /usr/lib/python3/dist-packages/apt_inst.cpython-311-x86_64-linux-gnu.so: undefined symbol: PyAptWarning ` Christian -- System Information: Debian Release: trixie/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.7-1-custom (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-apt depends on: ii distro-info-data 0.60 ii libapt-pkg6.0 2.7.7 ii libc6 2.37-13 ii libgcc-s1 13.2.0-8 ii libstdc++6 13.2.0-8 ii python-apt-common 2.7.2 ii python33.11.6-1 Versions of packages python3-apt recommends: ii iso-codes4.15.0-1 ii lsb-release 12.0-2 Versions of packages python3-apt suggests: ii apt 2.7.7 pn python-apt-doc -- no debconf information
Processed: Re: ruby-android-key-attestation: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require "pry-byebug"
Processing commands for cont...@bugs.debian.org: > severity 1054749 normal Bug #1054749 [src:ruby-android-key-attestation] ruby-android-key-attestation: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require "pry-byebug" Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1054749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054749: ruby-android-key-attestation: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require "pry-byebug"
severity 1054749 normal thanks I could reproduce this locally, I am lowering the severity of this bug to normal.
Bug#1036697: asterisk: CVE-2023-27585
Dear Jonas, On Mon, Aug 07, 2023 at 03:51:51PM +0300, Faidon Liambotis wrote: > Dear maintainer, security team, > > (See #1032092 for a similar bug with an almost equivalent response) I've seen that you've uploaded a couple new upstream releases of Asterisk in the time since my last response. Given these are severity: grave bugs, and I believe are most likely resolved, would it be possible for you to have a look here? Thanks, Faidon
Bug#1058513: marked as done (node-signal-exit: FTBFS: SyntaxError: Cannot use import statement outside a module)
Your message dated Thu, 14 Dec 2023 09:42:55 +0400
with message-id <5e74ca61-1eb7-448d-aca5-3ca6f98eb...@debian.org>
and subject line Fixed elsewhere
has caused the Debian Bug report #1058513,
regarding node-signal-exit: FTBFS: SyntaxError: Cannot use import statement
outside a module
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.)
--
1058513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-signal-exit
Version: 4.1.0-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tsc -p tsconfig.json
> tsc -p tsconfig-esm.json
> sh ./scripts/fixup.sh
> #cp debian/index.cjs dist/cjs/
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> ln -s ../. node_modules/signal-exit
> /bin/sh -ex debian/tests/pkg-js/test
> + tap -T -R spec test/all-integration-test.ts test/signal-exit-test.ts
>
> /<>/test/all-integration-test.ts:1
> import assert from 'assert'
> ^^
>
> SyntaxError: Cannot use import statement outside a module
> at internalCompileFunction (node:internal/vm:73:18)
> at wrapSafe (node:internal/modules/cjs/loader:1274:20)
> at Module._compile (node:internal/modules/cjs/loader:1320:27)
> at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
> at Module.load (node:internal/modules/cjs/loader:1197:32)
> at Module._load (node:internal/modules/cjs/loader:1013:12)
> at ModuleWrap. (node:internal/modules/esm/translators:202:29)
> at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
> at async ModuleLoader.import (node:internal/modules/esm/loader:336:24)
> at async loadESM (node:internal/process/esm_loader:34:7)
>
> Node.js v18.19.0
> /<>/test/signal-exit-test.ts:1
> import { exec } from 'child_process'
> ^^
>
> SyntaxError: Cannot use import statement outside a module
> at internalCompileFunction (node:internal/vm:73:18)
> at wrapSafe (node:internal/modules/cjs/loader:1274:20)
> at Module._compile (node:internal/modules/cjs/loader:1320:27)
> at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
> at Module.load (node:internal/modules/cjs/loader:1197:32)
> at Module._load (node:internal/modules/cjs/loader:1013:12)
> at ModuleWrap. (node:internal/modules/esm/translators:202:29)
> at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
> at async ModuleLoader.import (node:internal/modules/esm/loader:336:24)
> at async loadESM (node:internal/process/esm_loader:34:7)
>
> Node.js v18.19.0
> test/all-integration-test.ts
>
> 1) test/all-integration-test.ts
> test/signal-exit-test.ts
>
> 2) test/signal-exit-test.ts
>
> 0 passing (2s)
> 2 failing
>
> 1) test/all-integration-test.ts test/all-integration-test.ts:
> test/all-integration-test.ts
>
>
> 2) test/signal-exit-test.ts test/signal-exit-test.ts:
> test/signal-exit-test.ts
>
>
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/node-signal-exit_4.1.0-6_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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.
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 46742--- End Message ---
Bug#1058535: marked as done (libhinawa: FTBFS: make: *** [debian/rules:8: binary] Error 25)
Your message dated Thu, 14 Dec 2023 05:35:04 + with message-id and subject line Bug#1058535: fixed in libhinawa 4.0.0-2 has caused the Debian Bug report #1058535, regarding libhinawa: FTBFS: make: *** [debian/rules:8: binary] Error 25 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.) -- 1058535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libhinawa Version: 4.0.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Ddoc=true > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr > --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu > -Dpython.bytecompile=-1 -Ddoc=true > The Meson build system > Version: 1.3.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: hinawa > Project version: 4.0.0 > C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-8) 13.2.0") > C linker for the host machine: cc ld.bfd 2.41.50.20231206 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Header "include/linux/firewire-cdev.h" has symbol "FW_CDEV_EVENT_REQUEST3" : > NO > Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 > Run-time dependency gobject-2.0 found: YES 2.78.3 > Build-time dependency glib-2.0 found: YES 2.78.3 > Program /usr/bin/glib-genmarshal found: YES (/usr/bin/glib-genmarshal) > Dependency glib-2.0 found: YES 2.78.3 (cached) > Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums) > Dependency glib-2.0 found: YES 2.78.3 (cached) > Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums) > Run-time dependency gobject-introspection-1.0 found: YES 1.78.1 > Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached) > Program /usr/bin/g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached) > Program /usr/bin/g-ir-compiler found: YES (/usr/bin/g-ir-compiler) > Program fw-node found: YES (/usr/bin/python3 /<>/tests/fw-node) > Program fw-req found: YES (/<>/tests/fw-req) > Program fw-resp found: YES (/<>/tests/fw-resp) > Program fw-fcp found: YES (/<>/tests/fw-fcp) > Program cycle-time found: YES (/usr/bin/python3 > /<>/tests/cycle-time) > Program hinawa-enum found: YES (/usr/bin/python3 > /<>/tests/hinawa-enum) > Program hinawa-functions found: YES (/usr/bin/python3 > /<>/tests/hinawa-functions) > Configuring hinawa.toml using configuration > Run-time dependency gi-docgen found: YES 2023.3 > Program gi-docgen found: YES (/usr/bin/gi-docgen) > Build targets in project: 8 > > hinawa 4.0.0 > > User defined options > buildtype : plain > libdir: lib/x86_64-linux-gnu > localstatedir : /var > prefix: /usr > sysconfdir: /etc > wrap_mode : nodownload > python.bytecompile: -1 > doc : true > > Found ninja-1.11.1 at /usr/bin/ninja > make[1]: Leaving directory '/<>' >dh_auto_build -O--buildsystem=meson > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v > [1/15] /usr/bin/glib-genmarshal --prefix hinawa_sigs_marshal --stdinc > --output src/hinawa_sigs_marshal.h --header ../src/hinawa_sigs_marshal.list > --pragma-once > INFO: Reading ../src/hinawa_sigs_marshal.list... > [2/15] /usr/bin/glib-genmarshal --prefix hinawa_sigs_marshal --stdinc > --output src/hinawa_sigs_marshal.c --body ../src/hinawa_sigs_marshal.list > --include-header hinawa_sigs_marshal.h > INFO: Reading ../src/hinawa_sigs_marshal.list... > [3/15] /usr/bin/meson --internal exe --unpickle > /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_2f524c9b023ec2ae23e6f08f59994151641f9f41.dat > [4/15] /usr/bin/meson --internal exe --unpickle > /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_c023153e6dc728bc4ca9c5bbd7bf1ecd9fe95298.dat > [5/15] cc -Isrc/libhinawa.so.4.0.0.p -Isrc -I../src -I../include > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ >
Bug#1058273: marked as done (gpredict: FTBFS: dh_install: error: missing files, aborting)
Your message dated Thu, 14 Dec 2023 05:34:25 + with message-id and subject line Bug#1058273: fixed in gpredict 2.3-115-g0f3beb6-3 has caused the Debian Bug report #1058273, regarding gpredict: FTBFS: dh_install: error: missing files, aborting 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.) -- 1058273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpredict Version: 2.3-115-g0f3beb6-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>' > make[4]: Nothing to be done for 'install-exec-am'. > /usr/bin/install -c -m 644 ./AUTHORS > /<>/debian/tmp/usr/share/gpredict > /usr/bin/install -c -m 644 ./NEWS > /<>/debian/tmp/usr/share/gpredict > /usr/bin/install -c -m 644 ./README > /<>/debian/tmp/usr/share/gpredict > /usr/bin/install -c -m 644 ./COPYING > /<>/debian/tmp/usr/share/gpredict > make[4]: Leaving directory '/<>' > make[3]: Leaving directory '/<>' > make[2]: Leaving directory '/<>' > make[1]: Leaving directory '/<>' >dh_install > dh_install: warning: Cannot find (any matches for) > "doc/um/gpredict-user-manual.pdf" (tried in ., debian/tmp) > > dh_install: warning: gpredict-doc missing files: > doc/um/gpredict-user-manual.pdf > dh_install: error: missing files, aborting > make: *** [debian/rules:17: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/gpredict_2.3-115-g0f3beb6-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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. --- End Message --- --- Begin Message --- Source: gpredict Source-Version: 2.3-115-g0f3beb6-3 Done: tony mancill We believe that the bug you reported is fixed in the latest version of gpredict, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated gpredict 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: Tue, 12 Dec 2023 14:02:31 -0800 Source: gpredict Architecture: source Version: 2.3-115-g0f3beb6-3 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: tony mancill Closes: 1058273 Changes: gpredict (2.3-115-g0f3beb6-3) unstable; urgency=medium . * Team upload. * Temporarily build-dep on libreoffice-writer instead of -nogui to resolve FTBFS. (See #1058653) (Closes: #1058273) * Bump Standards-Version to 4.6.2 * Set Rules-Requires-Root: no in debian/control Checksums-Sha1: 35e25b9ad78f0fdec6036549fed8171e7a02c014 2308 gpredict_2.3-115-g0f3beb6-3.dsc ccb5e8f0f1380fb1f88d4329b93a9a1d1e7ffd2d 6184 gpredict_2.3-115-g0f3beb6-3.debian.tar.xz b33701a29c442bb1fe8759d0987f97e87466963e 18662 gpredict_2.3-115-g0f3beb6-3_amd64.buildinfo Checksums-Sha256: 7b964362ee6df1774d191e6622f513a45d0c75cb84b2f10cd6cc31c552028a71 2308 gpredict_2.3-115-g0f3beb6-3.dsc 2d4aa149de17b2348a20b25f29f6763421f566d4664e3f8110d9c19f009ba1f7 6184 gpredict_2.3-115-g0f3beb6-3.debian.tar.xz 7533896eeb3f0c37476fff28785618d9cd4da4ce673991c0181a295f65271645 18662 gpredict_2.3-115-g0f3beb6-3_amd64.buildinfo Files: a71eedcaa4bc4ac29552c0fd6f1750ea 2308 hamradio optional gpredict_2.3-115-g0f3beb6-3.dsc bcf7ede8919378724eb4d9b86a7712f8 6184 hamradio optional
Bug#1058540: marked as done (ditaa: FTBFS: xargs: /usr/lib/jvm/default-java/bin/javac: No such file or directory)
Your message dated Thu, 14 Dec 2023 06:12:50 +0100 with message-id and subject line FTBF has caused the Debian Bug report #1058540, regarding ditaa: FTBFS: xargs: /usr/lib/jvm/default-java/bin/javac: No such file or 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.) -- 1058540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ditaa Version: 0.10+ds1-1.3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with javahelper >dh_update_autotools_config >dh_autoreconf >jh_linkjars >jh_build > xargs: /usr/lib/jvm/default-java/bin/javac: No such file or directory > jh_build: error: find ./src/org/ -name '*.java' -and -type f -print0 | xargs > -s 512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp > /usr/share/java/junit4.jar:/usr/lib/jvm/default-java/lib/tools.jar:/usr/share/java/commons-cli.jar:/usr/share/java/batik-bridge.jar:/usr/share/java/batik-dom.jar:/usr/share/java/batik-gvt.jar:/usr/share/java/batik-svg-dom.jar:/usr/share/java/batik-awt-util.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/batik-libs.jar:/usr/share/java/jericho-html.jar:debian/_jh_build.ditaa > -d debian/_jh_build.ditaa -encoding ISO8859-1 -source 7 -target 7 returned > exit code 127 > make: *** [debian/rules:11: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/ditaa_0.10+ds1-1.3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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. --- End Message --- --- Begin Message --- version: 0.10+ds1-1.4 there was a typo in d/changelog--- End Message ---
Bug#1058273: gpredict: FTBFS: dh_install: error: missing files, aborting
On Tue, Dec 12, 2023 at 05:47:46PM -0700, Bdale Garbee wrote: > tony mancill writes: > > > So this is very possibly a bug in libreoffice-writer-nogui. > > Sure seems like it. My guess would be that what files go in what > libreoffice binary packages got refactored somehow? Not sure what the > point of the nogui package is if it can't be used here any more. The soffice wrapper script is good enough to include an --strace option, from which it looks like libcuilo.so is the missing library: $ dpkg -S /usr/lib/libreoffice/program/libcuilo.so libreoffice-core: /usr/lib/libreoffice/program/libcuilo.so However, libreoffice-core is the proverbial kitchen sink - it pulls in almost everything you'd get from libreoffice-writer - so for the time-being, I'll use the latter to work around the FTBFS and have filed a bug against libreoffice-writer-nogui (#1058653).
Bug#1058346: marked as done (libitext-java: FTBFS: [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:88: error: cannot find symbol)
Your message dated Thu, 14 Dec 2023 03:49:45 +
with message-id
and subject line Bug#1057165: fixed in libitext-java 2.1.7-15
has caused the Debian Bug report #1057165,
regarding libitext-java: FTBFS: [javac]
/<>/core/com/lowagie/text/pdf/PdfPKCS7.java:88: error: cannot find
symbol
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.)
--
1057165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libitext-java
Version: 2.1.7-14
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- jar jar.rtf
> ant -propertyfile ./debian/ant.properties -Duser.name debian jar jar.rtf
> Buildfile: /<>/build.xml
>
> jar:
>
> compile:
> [mkdir] Created dir: /<>/build/bin
> [javac] /<>/ant/compile.xml:45: warning: 'includeantruntime'
> was not set, defaulting to build.sysclasspath=last; set to false for
> repeatable builds
> [javac] Using javac -source 1.5 is no longer supported, switching to 7
> [javac] Using javac -target 1.5 is no longer supported, switching to 7
> [javac] Compiling 359 source files to /<>/build/bin
> [javac] warning: [options] bootstrap class path not set in conjunction
> with -source 7
> [javac] warning: [options] source value 7 is obsolete and will be removed
> in a future release
> [javac] warning: [options] target value 7 is obsolete and will be removed
> in a future release
> [javac] warning: [options] To suppress warnings about obsolete options,
> use -Xlint:-options.
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:88:
> error: cannot find symbol
> [javac] import org.bouncycastle.asn1.DEREnumerated;
> [javac] ^
> [javac] symbol: class DEREnumerated
> [javac] location: package org.bouncycastle.asn1
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:89:
> error: cannot find symbol
> [javac] import org.bouncycastle.asn1.DERInteger;
> [javac] ^
> [javac] symbol: class DERInteger
> [javac] location: package org.bouncycastle.asn1
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:91:
> error: cannot find symbol
> [javac] import org.bouncycastle.asn1.DERObjectIdentifier;
> [javac] ^
> [javac] symbol: class DERObjectIdentifier
> [javac] location: package org.bouncycastle.asn1
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:93:
> error: DEROutputStream is not public in org.bouncycastle.asn1; cannot be
> accessed from outside package
> [javac] import org.bouncycastle.asn1.DEROutputStream;
> [javac] ^
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:1478:
> error: cannot find symbol
> [javac] public static final DERObjectIdentifier C = new
> DERObjectIdentifier("2.5.4.6");
> [javac] ^
> [javac] symbol: class DERObjectIdentifier
> [javac] location: class X509Name
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:1483:
> error: cannot find symbol
> [javac] public static final DERObjectIdentifier O = new
> DERObjectIdentifier("2.5.4.10");
> [javac] ^
> [javac] symbol: class DERObjectIdentifier
> [javac] location: class X509Name
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:1488:
> error: cannot find symbol
> [javac] public static final DERObjectIdentifier OU = new
> DERObjectIdentifier("2.5.4.11");
> [javac] ^
> [javac] symbol: class DERObjectIdentifier
> [javac] location: class X509Name
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:1493:
> error: cannot find symbol
> [javac] public static final DERObjectIdentifier T = new
> DERObjectIdentifier("2.5.4.12");
> [javac] ^
> [javac] symbol: class DERObjectIdentifier
> [javac] location: class X509Name
> [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:1498:
> error: cannot find symbol
> [javac] public static final DERObjectIdentifier CN = new
> DERObjectIdentifier("2.5.4.3");
> [javac] ^
> [javac] symbol: class DERObjectIdentifier
> [javac]
Bug#1057165: marked as done (libitext-java: FTBFS with bouncycastle 1.77)
Your message dated Thu, 14 Dec 2023 03:49:45 +
with message-id
and subject line Bug#1057165: fixed in libitext-java 2.1.7-15
has caused the Debian Bug report #1057165,
regarding libitext-java: FTBFS with bouncycastle 1.77
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.)
--
1057165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libitext-java
Version: 2.1.7-14
Severity: serious
Tags: ftbfs sid
User: a...@debian.org
Usertags: bouncycastle-1.77
X-Debbugs-Cc: a...@debian.org
Dear maintainer,
libitext-java fails to build from source with bouncycastle 1.77. The reason
is the removal of long deprecated methods. The (hopefully) relevant
error message from the build log.
compile:
[mkdir] Created dir: /<>/build/bin
[javac] /<>/ant/compile.xml:45: warning: 'includeantruntime'
was not set, defaulting to build.sysclasspath=last; set to false for repeatable
builds
[javac] Using javac -source 1.5 is no longer supported, switching to 7
[javac] Using javac -target 1.5 is no longer supported, switching to 7
[javac] Compiling 359 source files to /<>/build/bin
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 7
[javac] warning: [options] source value 7 is obsolete and will be removed
in a future release
[javac] warning: [options] target value 7 is obsolete and will be removed
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use
-Xlint:-options.
[javac]
/<>/core/com/lowagie/text/pdf/MappedRandomAccessFile.java:58:
warning: [removal] AccessController in java.security has been deprecated and
marked for removal
[javac] import java.security.AccessController;
[javac] ^
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:356:
error: cannot find symbol
[javac] if (tag.getObject() instanceof ASN1Sequence) {
[javac]^
[javac] symbol: method getObject()
[javac] location: variable tag of type ASN1TaggedObject
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:357:
error: cannot find symbol
[javac] seq = (ASN1Sequence)tag.getObject();
[javac]^
[javac] symbol: method getObject()
[javac] location: variable tag of type ASN1TaggedObject
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:403:
error: cannot find symbol
[javac] ASN1Sequence content =
(ASN1Sequence)((DERTaggedObject)signedData.getObjectAt(1)).getObject();
[javac]
^
[javac] symbol: method getObject()
[javac] location: class DERTaggedObject
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:435:
error: cannot find symbol
[javac] DEROctetString rsaDataContent =
(DEROctetString)((DERTaggedObject)rsaData.getObjectAt(1)).getObject();
[javac]
^
[javac] symbol: method getObject()
[javac] location: class DERTaggedObject
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:488:
error: cannot find symbol
[javac] ASN1Sequence seqin =
(ASN1Sequence)tg.getObject();
[javac] ^
[javac] symbol: method getObject()
[javac] location: variable tg of type ASN1TaggedObject
[javac] /<>/core/com/lowagie/text/pdf/FontDetails.java:264:
warning: [removal] Integer(int) in Integer has been deprecated and marked for
removal
[javac] Integer codeKey = new Integer(code);
[javac] ^
[javac]
/<>/core/com/lowagie/text/pdf/TrueTypeFontUnicode.java:144:
warning: [removal] Integer(int) in Integer has been deprecated and marked for
removal
[javac] inverseCmap.put(new
Integer(metrics[0]), code);
[javac] ^
[javac]
/<>/core/com/lowagie/text/pdf/TrueTypeFontUnicode.java:150:
warning: [removal] Integer(int) in Integer has been deprecated and marked for
removal
[javac] return inverseCmap == null ? null : (Integer)
inverseCmap.get(new Integer(code));
[javac]
^
[javac]
/<>/core/com/lowagie/text/pdf/MappedRandomAccessFile.java:203:
warning:
Bug#1058237: python-boto: FTBFS: ModuleNotFoundError: No module named 'imp'
On Tue, Dec 12, 2023 at 08:14:41PM +0100, Andreas Tille wrote: > maybe we need to remove python-boto and fix all its rdepends. > > According to upstream[1]: > > This repo, boto was deprecated in 2020 and the last supported Python 3 > version was 3.4. It's unlikely this package will ever work with Python 3.12. Yes, python-boto should be removed from the archive. Really it should have been removed prior to bookworm, if not even earlier. I'll take care of filing the appropriate bugs. noah
Bug#1056480: python-markdown2's autopkg tests fail with Python 3.12
The issue seems to have been fixed in upstream markdown2 v2.4.11 commit commit 0fde72b: Remove deprecated imp module Updating markdown2 to 2.4.11 may fix the issue.
Bug#1058171: marked as done (python-logutils: FTBFS: AttributeError: 'ConfigDictTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)
Your message dated Wed, 13 Dec 2023 23:04:44 + with message-id and subject line Bug#1058171: fixed in python-logutils 0.3.5-3 has caused the Debian Bug report #1058171, regarding python-logutils: FTBFS: AttributeError: 'ConfigDictTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? 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.) -- 1058171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-logutils Version: 0.3.5-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > set -x ; set -e && for pyvers in 3.12 3.11; do \ > python$pyvers setup.py test -v ; \ > done > + set -e > + python3.12 setup.py test -v > Some unicode string with some śćźół chars > .s..EE.. > == > ERROR: test_config4_ok (test_dictconfig.ConfigDictTest.test_config4_ok) > -- > Traceback (most recent call last): > File "/<>/tests/test_dictconfig.py", line 571, in > test_config4_ok > self.assertEquals(h.formatted[0], > ^ > AttributeError: 'ConfigDictTest' object has no attribute 'assertEquals'. Did > you mean: 'assertEqual'? > > == > ERROR: test_config4a_ok (test_dictconfig.ConfigDictTest.test_config4a_ok) > -- > Traceback (most recent call last): > File "/<>/tests/test_dictconfig.py", line 583, in > test_config4a_ok > self.assertEquals(h.formatted[0], > ^ > AttributeError: 'ConfigDictTest' object has no attribute 'assertEquals'. Did > you mean: 'assertEqual'? > > -- > Ran 32 tests in 0.009s > > FAILED (errors=2, skipped=1) > make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/python-logutils_0.3.5-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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. --- End Message --- --- Begin Message --- Source: python-logutils Source-Version: 0.3.5-3 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of python-logutils, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-logutils 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: Wed, 13 Dec 2023 23:35:10 +0100 Source: python-logutils Architecture: source Version: 0.3.5-3 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1058171 Changes: python-logutils (0.3.5-3) unstable; urgency=medium . * Add use-assertEqual-not-assertEquals.patch (Closes: #1058171). Checksums-Sha1: dab1f20f1bac7ca64b0408d8e70f26a76f809614 2161 python-logutils_0.3.5-3.dsc 4a1b2ba543f597541a56ef3f541b7f877f34964a 4392
Processed: Bug#1058171 marked as pending in python-logutils
Processing control commands: > tag -1 pending Bug #1058171 [src:python-logutils] python-logutils: FTBFS: AttributeError: 'ConfigDictTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? Added tag(s) pending. -- 1058171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058171: marked as pending in python-logutils
Control: tag -1 pending Hello, Bug #1058171 in python-logutils 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/openstack-team/python/python-logutils/-/commit/ec0cc3fd2454dee8bf02b6758cf7bcb3b0a5ab0a Add use-assertEqual-not-assertEquals.patch (Closes: #1058171). (this message was generated automatically) -- Greetings https://bugs.debian.org/1058171
Processed: reassign 1057926 to src:linux, reassign 1057694 to src:nodejs, tagging 1057850, tagging 1057356 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1057926 src:linux 6.1.64-1
Bug #1057926 {Done: Salvatore Bonaccorso }
[linux-image-6.1.0-14-rt-amd64] 403 Access Denied on some packages on official
Debian repo
Warning: Unknown package 'linux-image-6.1.0-14-rt-amd64'
Bug reassigned from package 'linux-image-6.1.0-14-rt-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.1.64+1.
Ignoring request to alter fixed versions of bug #1057926 to the same values
previously set
Bug #1057926 {Done: Salvatore Bonaccorso } [src:linux] 403
Access Denied on some packages on official Debian repo
Marked as found in versions linux/6.1.64-1.
> reassign 1057694 src:nodejs
Bug #1057694 [nodejs-18.19.0] nodejs:please enable loong64
Warning: Unknown package 'nodejs-18.19.0'
Bug reassigned from package 'nodejs-18.19.0' to 'src:nodejs'.
No longer marked as found in versions 18.19.0.
Ignoring request to alter fixed versions of bug #1057694 to the same values
previously set
> tags 1057850 + sid trixie
Bug #1057850 [src:libnss-db] libnss-db: Uses db5.3, no replacement in sight
Added tag(s) trixie and sid.
> tags 1057356 + sid trixie
Bug #1057356 [src:pyjunitxml] pyjunitxml: FTBFS with Python 3.12
Added tag(s) sid and trixie.
> tags 1057392 + sid trixie
Bug #1057392 [src:codelite] codelite: FTBFS:
editorsettingsdockingwidows.cpp:62:16: error: call ... ambigous
Added tag(s) trixie and sid.
> tags 1057542 + sid trixie
Bug #1057542 [src:ap-utils] ap-utils: FTBFS: input.c:340:43: error: invalid
application of ‘sizeof’ to incomplete type ‘ITEM’ {aka ‘struct tagITEM’}
Added tag(s) sid and trixie.
> tags 1057557 + sid trixie
Bug #1057557 [src:emacs-helm-ag] emacs-helm-ag: FTBFS: FAILED visited-buffers
Added tag(s) sid and trixie.
> tags 1058575 + sid trixie
Bug #1058575 [glogic] glogic: Fails to start due AttributeError
Added tag(s) sid and trixie.
> tags 1057613 + sid trixie
Bug #1057613 [src:shed] shed: FTBFS: error: invalid use of incomplete typedef
‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) sid and trixie.
> tags 1057792 + sid trixie
Bug #1057792 [src:darcs-monitor] Removal notice: obsolete
Added tag(s) trixie and sid.
> tags 1057722 + sid trixie
Bug #1057722 [src:haskell-tidal] Removal notice: obsolete
Added tag(s) sid and trixie.
> tags 1057720 + sid trixie
Bug #1057720 [src:haskell-ircbot] Removal notice: obsolete
Added tag(s) trixie and sid.
> tags 1057719 + sid trixie
Bug #1057719 [src:haskell-happstack-authenticate] Removal notice: obsolete
Added tag(s) sid and trixie.
> tags 1057718 + sid trixie
Bug #1057718 [src:haskell-userid] Removal notice: obsolete
Added tag(s) trixie and sid.
> tags 1057716 + sid trixie
Bug #1057716 [src:haskell-diagrams] Removal notice: obsolete
Added tag(s) sid and trixie.
> tags 1058526 - sid trixie
Bug #1058526 {Done: Alastair McKinstry } [src:openmpi]
openmpi: FTBFS: chmod: cannot access
'debian/libopenmpi*//usr/lib/x86_64-linux-gnu/fortran/*/openmpi/*.mod': No such
file or directory
Removed tag(s) sid and trixie.
> tags 1058379 - sid trixie
Bug #1058379 [src:cython] compyle: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Removed tag(s) trixie and sid.
> tags 1058543 - sid trixie
Bug #1058543 [src:ceph] ceph: FTBFS: make[1]: *** [debian/rules:125:
override_dh_auto_configure] Error 2
Removed tag(s) trixie and sid.
> tags 1058532 + experimental
Bug #1058532 [src:golang-google-api] golang-google-api: FTBFS: tests failed
Added tag(s) experimental.
> tags 1058432 + experimental
Bug #1058432 [src:glyphslib] glyphslib: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) experimental.
> tags 1058428 + experimental
Bug #1058428 [src:python-twilio] python-twilio: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Added tag(s) experimental.
> tags 1058245 - sid trixie
Bug #1058245 [src:libportal] libportal: FTBFS with test failure:
AssertionError: dbus-daemon PID still alive
Removed tag(s) trixie and sid.
> tags 1058405 - sid trixie
Bug #1058405 [src:mesa] mesa: FTBFS:
../src/gallium/drivers/d3d12/d3d12_video_enc_h264.cpp:127:16: error:
‘D3D12_VIDEO_ENCODER_RATE_CONTROL_FLAG_ENABLE_EXTENDED_QVBR1_SUPPORT’ was not
declared in this scope; did you mean
‘D3D12_VIDEO_ENCODER_RATE_CONTROL_FLAG_ENABLE_EXTENSION1_SUPPORT’?
Removed tag(s) trixie and sid.
> tags 1058350 + experimental
Bug #1058350 [src:python-kubernetes] python-kubernetes: FTBFS: make[1]: ***
[debian/rules:17: override_dh_auto_test] Error 1
Added tag(s) experimental.
> tags 1058303 - sid trixie
Bug #1058303 [src:sphinx] sphinx: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Removed tag(s) trixie and sid.
> tags 1058291 - sid trixie
Bug #1058291 [src:python-urllib3] python-urllib3: FTBFS: dh_auto_test: error:
pybuild --test -i
Bug#1058348: marked as done (libapache-poi-java: FTBFS: [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLSignatureFacet.java:235: error: cannot find symbol)
Your message dated Wed, 13 Dec 2023 22:20:53 + with message-id and subject line Bug#1057167: fixed in libapache-poi-java 4.0.1-5 has caused the Debian Bug report #1057167, regarding libapache-poi-java: FTBFS: [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLSignatureFacet.java:235: error: cannot find symbol 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.) -- 1057167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libapache-poi-java Version: 4.0.1-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build -- -Dversion.id=4.0.1 -DDSTAMP=20220516 jar maven-poms javadocs > ant -propertyfile ./debian/ant.properties -Duser.name debian > -Dversion.id=4.0.1 -DDSTAMP=20220516 jar maven-poms javadocs > Buildfile: /<>/build.xml >[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been > set to 1652736074 > > check-jars: > [mkdir] Created dir: /<>/ooxml-testlib > > fetch-jars: > > check-ooxml-jars: > > fetch-ooxml-jars: > > init: > [mkdir] Created dir: /<>/build > [mkdir] Created dir: /<>/build/classes > [mkdir] Created dir: /<>/build/test-classes > [mkdir] Created dir: /<>/build/test-results > [mkdir] Created dir: /<>/build/scratchpad-classes > [mkdir] Created dir: /<>/build/scratchpad-test-classes > [mkdir] Created dir: /<>/build/scratchpad-test-results > [mkdir] Created dir: /<>/build/geometry-java > [mkdir] Created dir: /<>/build/ooxml-classes > [mkdir] Created dir: /<>/build/ooxml-test-classes > [mkdir] Created dir: /<>/build/ooxml-test-results > [mkdir] Created dir: /<>/build/excelant-classes > [mkdir] Created dir: /<>/build/excelant-test-classes > [mkdir] Created dir: /<>/build/excelant-test-results > [mkdir] Created dir: /<>/build/examples-classes > [mkdir] Created dir: /<>/build/integration-test-classes > [mkdir] Created dir: /<>/build/integration-test-results > [mkdir] Created dir: /<>/build/dist > [mkdir] Created dir: /<>/build/site > [echo] Using Ant: Apache Ant(TM) version 1.10.14 compiled on September > 25 2023 from /usr/share/ant, Ant detected Java 17 (may be different than > actual Java sometimes...) > [echo] Using Java: 17.0.9/17.0.9+9-Debian-2/17.0.9+9-Debian-2/OpenJDK > 64-Bit Server VM from Debian on Linux: 6.1.0-13-cloud-amd64 > > compile-main: > [javac] Compiling 1211 source files to /<>/build/classes > [javac] Ignoring source, target and bootclasspath as release has been set > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [javac] Note: Some input files use unchecked or unsafe operations. > [javac] Note: Recompile with -Xlint:unchecked for details. > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/dev/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/common/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/filesystem/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/storage/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/crypt/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/eventfilesystem/package-info.class > [javac] Creating empty > /<>/build/classes/org/apache/poi/poifs/property/package-info.class > [javac] Compiling 538 source files to /<>/build/test-classes > [javac] Ignoring source, target and bootclasspath as release has been set > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [javac] Note: > /<>/src/testcases/org/apache/poi/sl/usermodel/BaseTestSlideShow.java > uses unchecked or unsafe operations. > [javac] Note: Recompile with -Xlint:unchecked for details. > [copy] Copying 4 files to /<>/build/classes > > check-ooxml-xsds: > > fetch-ooxml-xsds: > > generate-geometry: > > compile-scratchpad: > [javac] Compiling 488 source files to > /<>/build/scratchpad-classes > [javac]
Bug#1057167: marked as done (libapache-poi-java: FTBFS with bouncycastle 1.77)
Your message dated Wed, 13 Dec 2023 22:20:53 + with message-id and subject line Bug#1057167: fixed in libapache-poi-java 4.0.1-5 has caused the Debian Bug report #1057167, regarding libapache-poi-java: FTBFS with bouncycastle 1.77 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.) -- 1057167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libapache-poi-java Version: 4.0.1-4 Severity: serious Tags: ftbfs sid User: a...@debian.org Usertags: bouncycastle-1.77 X-Debbugs-Cc: a...@debian.org Dear maintainer, libapache-poi-java fails to build from source with bouncycastle 1.77. The reason is the removal of long deprecated methods. The (hopefully) relevant error message from the build log. ompile-ooxml: [javac] Compiling 589 source files to /<>/build/ooxml-classes [javac] Ignoring source, target and bootclasspath as release has been set [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLS ignatureFacet.java:235: error: cannot find symbol [javac] ASN1OctetString keyHashOctetString = (ASN1OctetString)derTaggedObject.getObject(); [javac] ^ [javac] symbol: method getObject() [javac] location: variable derTaggedObject of type DERTaggedObject [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLS ignatureFacet.java:239: error: cannot find symbol [javac] X500Name name = X500Name.getInstance(derTaggedObject.getObject()); [javac] ^ [javac] symbol: method getObject() [javac] location: variable derTaggedObject of type DERTaggedObject [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/SignaturePart.j ava uses unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors BUILD FAILED /<>/build.xml:1133: Compile failed; see the compiler error output for details. signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: libapache-poi-java Source-Version: 4.0.1-5 Done: tony mancill We believe that the bug you reported is fixed in the latest version of libapache-poi-java, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated libapache-poi-java 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: Wed, 13 Dec 2023 13:42:30 -0800 Source: libapache-poi-java Architecture: source Version: 4.0.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 1012079 1039741 1057167 Changes: libapache-poi-java (4.0.1-5) unstable; urgency=medium . [ Pierre Gruet ] * Team upload * Providing classpaths of build jars in debian/libapache-poi-java.classpath (Closes: #1012079) * Raising Standards version to 4.6.1 (Rules-Requires-Root: no) * Removing unneeded versioned dependencies in debian/control * Replacing obsolete X-Comment field with Comment in d/copyright * Trim trailing whitespace. * Raising debian/watch format from 3 to 4. * Adding missing dependencies to the binary package * Apply multi-arch hints. + libapache-poi-java-doc: Add Multi-Arch: foreign. . [ tony mancill ] * Add patch for BouncyCastle 1.77 (Closes: #1057167) * Use UTC for build timestamp (Closes: #1039741) Checksums-Sha1: a408551c2365eda25c764004b78e3268db421bf6 2574 libapache-poi-java_4.0.1-5.dsc 615fbbe431c882d5d068539cdae11695227e7688 16340 libapache-poi-java_4.0.1-5.debian.tar.xz f8d086aa8a09dd47a63cda866672b050c2dc1ba7 15303 libapache-poi-java_4.0.1-5_amd64.buildinfo Checksums-Sha256: 30ff505e1b29933ef6f5794ff01740b40b1d83f14baac01ffc281a54ee3705fd 2574
Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12
On Sun, Nov 26, 2023 at 09:01:12 +, Mate Kukri wrote: > The mechanism used to load the kernel has changed from GRUB 2.06 to > GRUB 2.12, it is possible that there are unfortunate bugs in either in > GRUB and/or your firmware that is stopping the new mechanism from > loading the kernel. Just as a point of comparison, I updated a Lenovo ThinkPad T470 from 2.12~rc1-11 to 2.12~rc1-12 today, and didn't see any trouble. The boot log shows "Kernel is locked down from EFI Secure Boot", and the initial system installation was done in January 2023 with 2.06-3~deb11u5 as the GRUB version (from "installer build 20210731+deb11u7+b1"). -- Michael signature.asc Description: PGP signature
Bug#1058086: marked as done (python-monasca-statsd: FTBFS: AttributeError: 'TestMonascaStatsd' object has no attribute 'assertRegexpMatches')
Your message dated Wed, 13 Dec 2023 22:07:05 +
with message-id
and subject line Bug#1058086: fixed in python-monasca-statsd 2.7.0-3
has caused the Debian Bug report #1058086,
regarding python-monasca-statsd: FTBFS: AttributeError: 'TestMonascaStatsd'
object has no attribute 'assertRegexpMatches'
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.)
--
1058086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-monasca-statsd
Version: 2.7.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + echo WARNING: --no-py2 is deprecated, and always on.
> WARNING: --no-py2 is deprecated, and always on.
> + shift
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ yes = no ]
> + [ no = yes ]
> + [ 3.12 = disabled ]
> + echo 3.12
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -x /usr/bin/python3-stestr ]
> + STESTR=stestr
> + rm -rf .stestr
> + PYTHON=python3.12 stestr run --parallel --subunit
> + subunit2pyunit
> /usr/lib/python3.12/unittest/case.py:580: RuntimeWarning: TestResult has no
> addDuration method
> warnings.warn("TestResult has no addDuration method",
> tests.test_monascastatsd.TestMonascaStatsd.test_batched
> tests.test_monascastatsd.TestMonascaStatsd.test_batched ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_batched_buffer_autoflush
> tests.test_monascastatsd.TestMonascaStatsd.test_batched_buffer_autoflush ...
> ok
> tests.test_monascastatsd.TestMonascaStatsd.test_client_default_host_port
> tests.test_monascastatsd.TestMonascaStatsd.test_client_default_host_port ...
> ok
> tests.test_monascastatsd.TestMonascaStatsd.test_client_set_host_port
> tests.test_monascastatsd.TestMonascaStatsd.test_client_set_host_port ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_context_manager
> tests.test_monascastatsd.TestMonascaStatsd.test_context_manager ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_counter
> tests.test_monascastatsd.TestMonascaStatsd.test_counter ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_counter_with_dimensions
> tests.test_monascastatsd.TestMonascaStatsd.test_counter_with_dimensions ...
> FAIL
> tests.test_monascastatsd.TestMonascaStatsd.test_gauge
> tests.test_monascastatsd.TestMonascaStatsd.test_gauge ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_gauge_with_dimensions
> tests.test_monascastatsd.TestMonascaStatsd.test_gauge_with_dimensions ... FAIL
> tests.test_monascastatsd.TestMonascaStatsd.test_sample_rate
> tests.test_monascastatsd.TestMonascaStatsd.test_sample_rate ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_samples_with_dimensions
> tests.test_monascastatsd.TestMonascaStatsd.test_samples_with_dimensions ... ok
> ERROR:monascastatsd.connection:Error submitting metric
> Traceback (most recent call last):
> File "/<>/monascastatsd/connection.py", line 143, in
> _send_to_server
> self.socket.send(packet.encode(self.encoding))
> File "/<>/tests/test_monascastatsd.py", line 79, in send
> raise socket.error("Socket error")
> OSError: Socket error
> tests.test_monascastatsd.TestMonascaStatsd.test_socket_error
> tests.test_monascastatsd.TestMonascaStatsd.test_socket_error ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_time
> tests.test_monascastatsd.TestMonascaStatsd.test_time ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_timed
> tests.test_monascastatsd.TestMonascaStatsd.test_timed ... ok
> tests.test_monascastatsd.TestMonascaStatsd.test_timing
> tests.test_monascastatsd.TestMonascaStatsd.test_timing ... ok
>
> ==
> FAIL: tests.test_monascastatsd.TestMonascaStatsd.test_counter_with_dimensions
> tests.test_monascastatsd.TestMonascaStatsd.test_counter_with_dimensions
> --
>
Processed: Bug#1058086 marked as pending in python-monasca-statsd
Processing control commands: > tag -1 pending Bug #1058086 [src:python-monasca-statsd] python-monasca-statsd: FTBFS: AttributeError: 'TestMonascaStatsd' object has no attribute 'assertRegexpMatches' Added tag(s) pending. -- 1058086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058086: marked as pending in python-monasca-statsd
Control: tag -1 pending Hello, Bug #1058086 in python-monasca-statsd 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/openstack-team/libs/python-monasca-statsd/-/commit/f741a8c783c6870049b7e0692f77f0640e791651 * Fix FTBFS by adding patch (Closes: #1058086): - do-not-use-assertRegexpMatches-but-assertRegex.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1058086
Processed (with 1 error): merging 1057167 1057516
Processing commands for cont...@bugs.debian.org: > merge 1057167 1057516 Bug #1057167 [src:libapache-poi-java] libapache-poi-java: FTBFS with bouncycastle 1.77 Bug #1058348 [src:libapache-poi-java] libapache-poi-java: FTBFS: [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLSignatureFacet.java:235: error: cannot find symbol Unable to merge bugs because: severity of #1057516 is 'important' not 'serious' owner of #1057516 is '' not 'tony mancill ' Failed to merge 1057167: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1057167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057167 1057516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057516 1058348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: aioquic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Processing control commands: > tags -1 + fixed-upstream Bug #1058169 [src:aioquic] aioquic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) fixed-upstream. -- 1058169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058169: aioquic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Control: tags -1 + fixed-upstream This has been fixed upstream in aioquic/0.9.22 - https://github.com/aiortc/aioquic/commit/b09747820e3539950123f85385c978d473ac5a61 Best regards, Dale Richards
Processed: Re: Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1
Processing control commands: > reassign -1 debputy Bug #1057934 [src:libjs-jquery-jstree] libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1 Bug reassigned from package 'src:libjs-jquery-jstree' to 'debputy'. No longer marked as found in versions libjs-jquery-jstree/3.3.16+dfsg1-1. Ignoring request to alter fixed versions of bug #1057934 to the same values previously set > affects -1 src:libjs-jquery-jstree Bug #1057934 [debputy] libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1 Added indication that 1057934 affects src:libjs-jquery-jstree -- 1057934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1
Control: reassign -1 debputy
Control: affects -1 src:libjs-jquery-jstree
Hi Niels,
I think this one is for you.
Paul
On 10-12-2023 20:18, Santiago Vila wrote:
Package: src:libjs-jquery-jstree
Version: 3.3.16+dfsg1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp debian/build.js build.js
nodejs /usr/share/nodejs/requirejs/r.js -o build.js
Tracing dependencies for: jstree
/<>/dist/jstree.js
/<>/src/jstree.js
/<>/src/jstree.changed.js
/<>/src/jstree.checkbox.js
/<>/src/jstree.conditionalselect.js
/<>/src/jstree.contextmenu.js
/<>/src/jstree.dnd.js
/<>/src/jstree.massload.js
/<>/src/jstree.search.js
/<>/src/jstree.sort.js
/<>/src/jstree.state.js
/<>/src/jstree.types.js
/<>/src/jstree.unique.js
/<>/src/jstree.wholerow.js
/<>/src/vakata-jstree.js
sed -i -e 's/{{VERSION}}/3.3.16+dfsg1/' dist/jstree.js
Checking syntax of dist/jstree.js ...
uglifyjs dist/jstree.js --output dist/jstree.min.js --compress
dh_auto_build
make[1]: Leaving directory '/<>'
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs --check dist/jstree.js
nodejs --check dist/jstree.min.js
make[1]: Leaving directory '/<>'
create-stamp debian/debhelper-build-stamp
dh_prep
dh_auto_install --destdir=debian/libjs-jquery-jstree/
dh_debputy
Internal error in debputy
- 8< BEGIN STACK TRACE 8< -
Traceback (most recent call last):
File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line
2082, in main
command.handler(cmd_context)
File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line
1133, in _dh_integration_generate_debs
intermediate_manifest = manifest.finalize_data_tar_contents(
File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line
1177, in finalize_data_tar_contents
intermediate_manifest = list(
^
File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 180,
in _generate_intermediate_manifest
tar_member = _path_to_tar_member(path, clamp_mtime_to)
^
File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 159,
in _path_to_tar_member
return TarMember.from_file(
File "/usr/share/dh-debputy/debputy/intermediate_manifest.py", line
147, in from_file
"debputy/scratch_dir/" in fs_path
AssertionError: README.md should not have been stealable
- 8< END STACK TRACE 8< -
Please file a bug against debputy with the full output.
README.md should not have been stealable
dh_debputy: error: debputy internal-command dh-integration-generate-debs
-p libjs-jquery-jstree .. returned exit code 1
make: *** [debian/rules:34: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
The above is just how the build ends and not necessarily the most
relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202312/
About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processed: Bug#1057167 marked as pending in libapache-poi-java
Processing control commands: > tag -1 pending Bug #1057167 [src:libapache-poi-java] libapache-poi-java: FTBFS with bouncycastle 1.77 Bug #1058348 [src:libapache-poi-java] libapache-poi-java: FTBFS: [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLSignatureFacet.java:235: error: cannot find symbol Added tag(s) pending. Added tag(s) pending. -- 1057167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057167 1058348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057167: marked as pending in libapache-poi-java
Control: tag -1 pending Hello, Bug #1057167 in libapache-poi-java 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/java-team/libapache-poi-java/-/commit/42f8d757b0bfa2a1261447912e0aba6f5f1ae6d7 Add patch for BouncyCastle 1.77 (Closes: #1057167) (this message was generated automatically) -- Greetings https://bugs.debian.org/1057167
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org:
> merge 1056224 1058209
Bug #1056224 [src:advocate] advocate's autopkg tests fail with Python 3.12
Bug #1056224 [src:advocate] advocate's autopkg tests fail with Python 3.12
Added tag(s) ftbfs.
Bug #1058209 [src:advocate] advocate: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p "3.12 3.11" returned exit code 13
Merged 1056224 1058209
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056224
1058209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058365: python-lsp-server: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
This is fixed upstream in jedi/0.19.1 - https://github.com/davidhalter/jedi/commit/c137eb69182f21771dbd1dce8ce9f6b3c4901777 Best regards, Dale Richards
Bug#1058640: src:lintian-brush: unsatisfied build dependency in testing: ognibuild (>= 0.0.18)
Source: lintian-brush Version: 0.152 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051166: FTBFS with doxygen 1.9.8
This is discussed upstream here: https://github.com/breathe-doc/breathe/issues/935 It appears to be a regression in doxygen caused by: https://github.com/doxygen/doxygen/commit/a18e4c76ed6415893800c7d77a2f798614fb638b Best regards, Dale Richards
Processed: merging 1057167 1058348, owner 1057167
Processing commands for cont...@bugs.debian.org: > merge 1057167 1058348 Bug #1057167 [src:libapache-poi-java] libapache-poi-java: FTBFS with bouncycastle 1.77 Bug #1058348 [src:libapache-poi-java] libapache-poi-java: FTBFS: [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLSignatureFacet.java:235: error: cannot find symbol Merged 1057167 1058348 > owner 1057167 ! Bug #1057167 [src:libapache-poi-java] libapache-poi-java: FTBFS with bouncycastle 1.77 Bug #1058348 [src:libapache-poi-java] libapache-poi-java: FTBFS: [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLSignatureFacet.java:235: error: cannot find symbol Owner recorded as tony mancill . Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1057167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057167 1058348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055021: linux: mips64el loongson3 kernel crashes when running cmake
Contol: tags -1 + fixed-upstream Control: found -1 6.1.66-1 Control: found -1 6.5.13-1 On Sun, Oct 29, 2023 at 02:16:57PM +0100, Aurelien Jarno wrote: > Source: linux > Version: 5.10.197-1 > Severity: grave > Tags: upstream patch > X-Debbugs-Cc: d...@debian.org, debian-m...@lists.debian.org > > The loongson3 flavour of the mips64el kernel crash when running cmake: > > | [ 4390.501529] do_cpu invoked from kernel context![#1]: > | [ 4390.506483] CPU: 3 PID: 24061 Comm: iou-sqp-22284 Not tainted > 5.10.0-26-loongson-3 #1 Debian 5.10.197-1 > | [ 4390.515820] Hardware name: Loongson > Lemote-3A4000-7A-1w-V1.00-A1901/Lemote-3A4000-7A-1w-V1.00-A1901, BIOS > Loongson-PMON-V3.3-20201222 12/22/2020 > | [ 4390.528699] $ 0 : 80bf9030 0001 > 98020f844000 > | [ 4390.536669] $ 4 : 9801017bb2c0 80dbc0b8 0008 > 02008200 > | [ 4390.544634] $ 8 : 0001 0001 > 02e27c19 > | [ 4390.552600] $12 : 5400cce0 80199c00 01ea > 01ea > | [ 4390.560565] $16 : 980100253700 80ecc740 > 9800023cb8c0 > | [ 4390.568530] $20 : 80ecdce0 9801017bb2c0 9801017bb8e0 > > | [ 4390.576495] $24 : 0028 98020f847e58 > | [ 4390.584461] $28 : 98020f844000 98020f847d40 9800023cb8c0 > 80bf925c > | [ 4390.592426] Hi : 00de > | [ 4390.595974] Lo : d70a40ec > | [ 4390.599532] epc : 802177c0 _save_fp+0x10/0xa0 > | [ 4390.604727] ra : 80bf925c __schedule+0x804/0xe08 > | [ 4390.610263] Status: 5400cce2 KX SX UX KERNEL EXL > | [ 4390.614949] Cause : 102c (ExcCode 0b) > | [ 4390.618930] PrId : 0014c004 (ICT Loongson-3) > | [ 4390.623257] Modules linked in: asix usbnet mii sg ip6t_REJECT > nf_reject_ipv6 ip6table_filter ip6_tables nfnetlink_log nfnetlink > xt_hashlimit ipt_REJECT nf_reject_ipv4 xt_NFLOG xt_multiport xt_tcpudp > xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c > iptable_filter sch_fq tcp_bbr fuse drm drm_panel_orientation_quirks configfs > ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic ohci_pci > dm_mod r8169 realtek mdio_devres ohci_hcd ehci_pci of_mdio xhci_pci xhci_hcd > ehci_hcd fixed_phy libphy usbcore usb_common > | [ 4390.671116] Process iou-sqp-22284 (pid: 24061, > threadinfo=743a6e5b, task=63cca72a, tls=00fff0de98e0) > | [ 4390.681930] Stack : 80ed 80ed > 98020f6e8c40 > | [ 4390.689897] 98020004 d37c8307c148dccb 9801017bb2c0 > > | [ 4390.697863] 0001 90 > | [ 4390.721759] 980104957480 98020f6e8c00 > 80ed > | [ 4390.729724] 98020f6e8c40 98020f6e8c08 > > | [ 4390.737689] 9801017bb2c0 802c61f8 > 98020f6e8c48 > | [ 4390.745655] 98020f6e8c48 2d7071732d756f69 003438323232 > d37c8307c148dccb > | [ 4390.753621] 807106e0 98020f6e8c00 9801097e90c8 > 7400cce0 > | [ 4390.761588] ... > | [ 4390.764017] Call Trace: > | [ 4390.766453] [] _save_fp+0x10/0xa0 > | [ 4390.771306] [] __schedule+0x804/0xe08 > | [ 4390.776497] [] schedule+0x58/0x150 > | [ 4390.781432] [] io_sq_thread+0x550/0x578 > | [ 4390.786798] [] ret_from_kernel_thread+0x14/0x1c > | [ 4390.792856] > | [ 4390.794330] Code: 000c6940 05a10011 f4830b10 > f4850b30 f4870b50 f4890b70 f48b0b90 > | [ 4390.804038] > | [ 4411.502993] rcu: INFO: rcu_preempt self-detected stall on CPU > | [ 4411.508728] rcu: 1-...!: (5250 ticks this GP) > idle=2c6/1/0x4002 softirq=1149627/1149627 fqs=4 > | [ 4411.518413] (t=5254 jiffies g=735145 q=4914963) > | [ 4411.522999] rcu: rcu_preempt kthread starved for 5248 jiffies! g735145 > f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=2 > | [ 4411.533458] rcu: Unless rcu_preempt kthread gets sufficient CPU time, > OOM is now expected behavior. > | [ 4411.542535] rcu: RCU grace-period kthread stack dump: > | [ 4411.547552] task:rcu_preempt state:R stack: 0 pid: 13 ppid: 2 > flags:0x0010 > | [ 4411.555860] Stack : 80ed 80bff978 80ed > 8031bbd4 > | [ 4411.563826] 0004 d37c8307c148dccb 98010025 > 00208040 > | [ 4411.571791] 80ed 9801002c7c98 80ed > 80f62ce0 > | [ 4411.579756] 0006 0001 > 80bf98b8 > | [ 4411.587721] 0001000f9aa0 > 80bfdb98 > | [ 4411.595686] 8030bbc8 5400cce1 80ed > > | [ 4411.603651] 98000236cc78 0001000f9aa0 80319968 > 0842 > | [ 4411.611617] 98010025 d37c8307c148dccb 80f62a80 > > | [ 4411.619582]
Processed: Re: Bug#1055021: linux: mips64el loongson3 kernel crashes when running cmake
Processing control commands: > found -1 6.1.66-1 Bug #1055021 [src:linux] linux: mips64el loongson3 kernel crashes when running cmake Marked as found in versions linux/6.1.66-1. > found -1 6.5.13-1 Bug #1055021 [src:linux] linux: mips64el loongson3 kernel crashes when running cmake Marked as found in versions linux/6.5.13-1. -- 1055021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:mes: fails to migrate to testing for too long: FTBFS on armhf
Processing control commands: > close -1 0.25-1 Bug #1058635 [src:mes] src:mes: fails to migrate to testing for too long: FTBFS on armhf Marked as fixed in versions mes/0.25-1. Bug #1058635 [src:mes] src:mes: fails to migrate to testing for too long: FTBFS on armhf Marked Bug as done -- 1058635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058635: src:mes: fails to migrate to testing for too long: FTBFS on armhf
Source: mes Version: 0.24.2-1 Severity: serious Control: close -1 0.25-1 Tags: sid trixie ftbfs 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 30 days as having a Release Critical bug in testing [1]. Your package src:mes has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armhf. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=mes OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: update found
Processing commands for cont...@bugs.debian.org: > found 1056427 2023.9.25-1 Bug #1056427 [src:monty] monty's autopkg tests fail with Python 3.12 Marked as found in versions monty/2023.9.25-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:coreutils: fails to migrate to testing for too long: triggers autopkgtest failure
Processing control commands: > close -1 9.4-2 Bug #1058630 [src:coreutils] src:coreutils: fails to migrate to testing for too long: triggers autopkgtest failure Marked as fixed in versions coreutils/9.4-2. Bug #1058630 [src:coreutils] src:coreutils: fails to migrate to testing for too long: triggers autopkgtest failure Marked Bug as done -- 1058630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058630: src:coreutils: fails to migrate to testing for too long: triggers autopkgtest failure
Source: coreutils Version: 9.1-1 Severity: serious Control: close -1 9.4-2 Tags: sid trixie 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 30 days as having a Release Critical bug in testing [1]. Your package src:coreutils has been trying to migrate for 33 days [2]. Hence, I am filing this bug. The version in unstable triggers failure of the autopkgtest of initramfs-tools. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=coreutils OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:starjava-votable: fails to migrate to testing for too long: triggers autopkgtest failure
Processing control commands: > close -1 2.0+2023.10.31-1 Bug #1058629 [src:starjava-votable] src:starjava-votable: fails to migrate to testing for too long: triggers autopkgtest failure Marked as fixed in versions starjava-votable/2.0+2023.10.31-1. Bug #1058629 [src:starjava-votable] src:starjava-votable: fails to migrate to testing for too long: triggers autopkgtest failure Marked Bug as done -- 1058629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058629: src:starjava-votable: fails to migrate to testing for too long: triggers autopkgtest failure
Source: starjava-votable Version: 2.0+2023.04.14-1 Severity: serious Control: close -1 2.0+2023.10.31-1 Tags: sid trixie 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 30 days as having a Release Critical bug in testing [1]. Your package src:starjava-votable has been trying to migrate for 33 days [2]. Hence, I am filing this bug. The version in unstable triggers autopkgtest failure in starjava-ttools. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=starjava-votable OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:r10k: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 4.0.0-1 Bug #1058628 [src:r10k] src:r10k: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r10k/4.0.0-1. Bug #1058628 [src:r10k] src:r10k: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1058628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058628: src:r10k: fails to migrate to testing for too long: autopkgtest regression
Source: r10k Version: 3.15.4-1 Severity: serious Control: close -1 4.0.0-1 Tags: sid trixie 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 30 days as having a Release Critical bug in testing [1]. Your package src:r10k has been trying to migrate for 34 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=r10k OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:zope.proxy: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 5.1-2 Bug #1058627 [src:zope.proxy] src:zope.proxy: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions zope.proxy/5.1-2. Bug #1058627 [src:zope.proxy] src:zope.proxy: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1058627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058627: src:zope.proxy: fails to migrate to testing for too long: autopkgtest regression
Source: zope.proxy Version: 4.5.0-1 Severity: serious Control: close -1 5.1-2 Tags: sid trixie 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 30 days as having a Release Critical bug in testing [1]. Your package src:zope.proxy has been trying to migrate for 36 days [2]. Hence, I am filing this bug. The version in unstable triggers autopkgtest failures in zope.security (albeit that seems fixed with the version of zope.security in unstable). However, it also fails its own autopkgtest. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=zope.proxy OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: netcdf: Finalize HDF5 library at exit
Processing control commands: > block 1057590 by -1 Bug #1057590 [src:octave-netcdf] octave-netcdf: FTBFS: fatal: caught signal Segmentation fault -- stopping myself... Bug #1057589 [src:octave-netcdf] octave-ncarray: FTBFS: fatal: caught signal Segmentation fault -- stopping myself... 1057590 was not blocked by any bugs. 1057590 was not blocking any bugs. Added blocking bug(s) of 1057590: 1058621 1057589 was not blocked by any bugs. 1057589 was not blocking any bugs. Added blocking bug(s) of 1057589: 1058621 -- 1057589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057589 1057590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057590 1058621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057802: marked as done (libgetdata ftbfs when building binary-indep packages only)
Your message dated Wed, 13 Dec 2023 16:37:57 + with message-id and subject line Bug#1057802: fixed in libgetdata 0.11.0-11 has caused the Debian Bug report #1057802, regarding libgetdata ftbfs when building binary-indep packages only 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.) -- 1057802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libgetdata Version: 0.11.0-8 Severity: serious Tags: sid trixie libgetdata ftbfs when building binary-indep packages only: [...] dh_missing -i dh_missing: warning: usr/local/lib/python3.11/dist-packages/pygetdata.cpython-311-x86_64-linux-gnu.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/local/lib/python3.12/dist-packages/pygetdata.cpython-312-x86_64-linux-gnu.so exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting --- End Message --- --- Begin Message --- Source: libgetdata Source-Version: 0.11.0-11 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of libgetdata, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated libgetdata 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: Wed, 13 Dec 2023 16:09:22 + Source: libgetdata Architecture: source Version: 0.11.0-11 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 1057802 1057872 Changes: libgetdata (0.11.0-11) unstable; urgency=medium . * Drop obsolete breaks/replaces from d/control * Add binary files to d/not-installed. Closes: #1057802, #1057872 Checksums-Sha1: f88539e3b0332d3c777a3eeb12f0c44e3cf0ba9f 2790 libgetdata_0.11.0-11.dsc c47e2f05f2b25a142dc03b0a51305dae38800ab2 7368 libgetdata_0.11.0-11.debian.tar.xz Checksums-Sha256: 017a155f4a4c76061ef2511852695307b355d14fffd5c07dc7de479a8aca6935 2790 libgetdata_0.11.0-11.dsc 7d6772196489ac74a8b587e71493d6e7aa1deb04a8769a07861637998642e51c 7368 libgetdata_0.11.0-11.debian.tar.xz Files: 7fd549249d96825c6531485b7e6dec21 2790 science optional libgetdata_0.11.0-11.dsc 83b4dec9214c9bc47e16631d5ecfeed6 7368 science optional libgetdata_0.11.0-11.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmV52hMACgkQy+a7Tl2a 06WVGw//Uiv3tuB6OPIp1Ycrr7zSmJf+WUGEBQyR5wzUE8ZoWgUs3co+TU4RPbnG QwBOEFcSl4zsFP7qjoVG9f/Ygn/1y+H5cLrzXvO2Hq18ljiqcIt1wY8AwoT5UZy+ aabHM7uNsjxxNzrhID5IYtOgVPbjRIQK9roaMhTVXS2roEOJVrx90yvaiMVbhc6m DcuPHJtPlJ8CENccRVGGLYGzpjTmXegq9T+3atigP+7woTbIbCazwwwMZkdyHZLp RLbfGJcKHlLN5PH9meg6OK3lP642qzCyT6zRoyKJYw0WW37sif0/CWECZaqh5Lb2 vo/nnFT1xNIuLomjXc1Dtj+OuJ3ehbkHTDPOnKyzkHzkrEaa2K5hOT6Rg1tEev/R qmpfCEExK/56ImlD296OcgwCsFOigigGE5f+R5S+/qd15TaEtnC5LsfLDU/3aSe+ 30QSFNXu8znQ47tazZTpTEzndUpfB6pwg5FWInHIfYWa3KXBwtHmfePiHUVVunKi KJb5piOdWpIkpqJ1SjhIzO2mpK3SY4ju0dLAHxurFUiWDU5tLY6btUL8mB2/QD62 p17hhxfN8z/nMFpiS2q1QqNzBEQ6da6A4UP+X4R3DtcEOClZaG1RC//OU4acoDkU tzC7BcijMbEhnP4ZxvVQ/oOa3+rZqpSZPr2dmBc1vdWEl+rK6zs= =mPJn -END PGP SIGNATURE End Message ---
Bug#1057872: marked as done (python3-pygetdata is empty)
Your message dated Wed, 13 Dec 2023 16:37:57 + with message-id and subject line Bug#1057872: fixed in libgetdata 0.11.0-11 has caused the Debian Bug report #1057872, regarding python3-pygetdata is empty 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.) -- 1057872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pygetdata Version: 0.11.0-9 Severity: serious $ dpkg -L python3-pygetdata /. /usr /usr/share /usr/share/doc /usr/share/doc/python3-pygetdata /usr/share/doc/python3-pygetdata/changelog.Debian.gz /usr/share/doc/python3-pygetdata/changelog.gz /usr/share/doc/python3-pygetdata/copyright $ --- End Message --- --- Begin Message --- Source: libgetdata Source-Version: 0.11.0-11 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of libgetdata, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated libgetdata 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: Wed, 13 Dec 2023 16:09:22 + Source: libgetdata Architecture: source Version: 0.11.0-11 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 1057802 1057872 Changes: libgetdata (0.11.0-11) unstable; urgency=medium . * Drop obsolete breaks/replaces from d/control * Add binary files to d/not-installed. Closes: #1057802, #1057872 Checksums-Sha1: f88539e3b0332d3c777a3eeb12f0c44e3cf0ba9f 2790 libgetdata_0.11.0-11.dsc c47e2f05f2b25a142dc03b0a51305dae38800ab2 7368 libgetdata_0.11.0-11.debian.tar.xz Checksums-Sha256: 017a155f4a4c76061ef2511852695307b355d14fffd5c07dc7de479a8aca6935 2790 libgetdata_0.11.0-11.dsc 7d6772196489ac74a8b587e71493d6e7aa1deb04a8769a07861637998642e51c 7368 libgetdata_0.11.0-11.debian.tar.xz Files: 7fd549249d96825c6531485b7e6dec21 2790 science optional libgetdata_0.11.0-11.dsc 83b4dec9214c9bc47e16631d5ecfeed6 7368 science optional libgetdata_0.11.0-11.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmV52hMACgkQy+a7Tl2a 06WVGw//Uiv3tuB6OPIp1Ycrr7zSmJf+WUGEBQyR5wzUE8ZoWgUs3co+TU4RPbnG QwBOEFcSl4zsFP7qjoVG9f/Ygn/1y+H5cLrzXvO2Hq18ljiqcIt1wY8AwoT5UZy+ aabHM7uNsjxxNzrhID5IYtOgVPbjRIQK9roaMhTVXS2roEOJVrx90yvaiMVbhc6m DcuPHJtPlJ8CENccRVGGLYGzpjTmXegq9T+3atigP+7woTbIbCazwwwMZkdyHZLp RLbfGJcKHlLN5PH9meg6OK3lP642qzCyT6zRoyKJYw0WW37sif0/CWECZaqh5Lb2 vo/nnFT1xNIuLomjXc1Dtj+OuJ3ehbkHTDPOnKyzkHzkrEaa2K5hOT6Rg1tEev/R qmpfCEExK/56ImlD296OcgwCsFOigigGE5f+R5S+/qd15TaEtnC5LsfLDU/3aSe+ 30QSFNXu8znQ47tazZTpTEzndUpfB6pwg5FWInHIfYWa3KXBwtHmfePiHUVVunKi KJb5piOdWpIkpqJ1SjhIzO2mpK3SY4ju0dLAHxurFUiWDU5tLY6btUL8mB2/QD62 p17hhxfN8z/nMFpiS2q1QqNzBEQ6da6A4UP+X4R3DtcEOClZaG1RC//OU4acoDkU tzC7BcijMbEhnP4ZxvVQ/oOa3+rZqpSZPr2dmBc1vdWEl+rK6zs= =mPJn -END PGP SIGNATURE End Message ---
Bug#1050086: marked as done (rust-ahash: Fails to build)
Your message dated Wed, 13 Dec 2023 11:00:02 -0500
with message-id
and subject line Re: Bug#1050086: rust-ahash: Fails to build
has caused the Debian Bug report #1050086,
regarding rust-ahash: Fails to build
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.)
--
1050086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-ahash
Version: 0.8.3-7
Severity: serious
Tags: ftbfs
rust-ahash fails to build. Here's a build log excerpt:
error[E0432]: unresolved import `criterion`
--> tests/map_tests.rs:6:5
|
6 | use criterion::*;
| ^ use of undeclared crate or module `criterion`
error[E0432]: unresolved import `fxhash`
--> tests/map_tests.rs:7:5
|
7 | use fxhash::FxHasher;
| ^^ use of undeclared crate or module `fxhash`
|
help: there is a crate or module with a similar name
|
7 | use ahash::FxHasher;
| ~
error: cannot find macro `criterion_main` in this scope
--> tests/map_tests.rs:233:1
|
233 | criterion_main!(benches);
| ^^
error: cannot find macro `criterion_group` in this scope
--> tests/map_tests.rs:234:1
|
234 | criterion_group!(benches, bench_ahash_words, bench_fx_words,);
| ^^^
error[E0412]: cannot find type `Criterion` in this scope
--> tests/map_tests.rs:223:30
|
223 | fn bench_ahash_words(c: Criterion) {
| ^ not found in this scope
error[E0425]: cannot find function `black_box` in this scope
Full build log
==
https://buildd.debian.org/status/package.php?p=rust-ahash
Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Version: 0.8.5-2
https://buildd.debian.org/status/package.php?p=rust-ahash--- End Message ---
Bug#1058596: [Pkg-javascript-devel] Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function
On 13/12/23 9:13 pm, Praveen Arimbrathodiyil wrote: On 13/12/23 8:54 pm, Praveen Arimbrathodiyil wrote: On 13/12/23 8:52 pm, Yadd wrote: since severity is grave, please prepare an update for stable also Yes, I'm backporting the updated patch. Proposed it to release team as #1058615 and uploaded to https://people.debian.org/~praveen/yarnpkg/ until we get the approval from release team (need this immediately for gitlab). OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1058218: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned ex
Processing commands for cont...@bugs.debian.org: > tags 1058218 upstream Bug #1058218 [src:libei] libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1 Added tag(s) upstream. > forwarded 1058218 https://gitlab.freedesktop.org/libinput/libei/-/issues/50 Bug #1058218 [src:libei] libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1 Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/libinput/libei/-/issues/50'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1058218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058118: marked as done (python-apt: FTBFS: AssertionError: pyflakes failed with: 1)
Your message dated Wed, 13 Dec 2023 15:50:42 + with message-id and subject line Bug#1058118: fixed in python-apt 2.7.2 has caused the Debian Bug report #1058118, regarding python-apt: FTBFS: AssertionError: pyflakes failed with: 1 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.) -- 1058118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-apt Version: 2.7.0 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test || [ "linux" = "hurd" ]; > I: pybuild base:310: env > PYTHONPATH=/<>/.pybuild/cpython3_3.12_apt/build python3.12 > tests/test_all.py > [tests] Running on 3.12.1 (main, Dec 8 2023, 16:20:54) [GCC 13.2.0] > Using pybuild supplied build dir > s > Reading package lists... 0% > > Reading package lists... 100% > > Reading package lists... Done > > > Building dependency tree... 0% > > Building dependency tree... 0% > > Building dependency tree... 50% > > Building dependency tree... 50% > > Building dependency tree... Done > > > Reading state information... 0% > > Reading state information... 0% > > Reading state information... Done > > . > Reading package lists... 0% > > Reading package lists... 100% > > Reading package lists... Done > > > Building dependency tree... 0% > > Building dependency tree... 0% > > Building dependency tree... 50% > > Building dependency tree... 50% > > Building dependency tree... Done > > > Reading state information... 0% > > Reading state information... 0% > > Reading state information... Done > > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > ..WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .WARNING: Failed to read mirror file > .s...s../<>/apt/auth.py:40:1: > 'typing.List' imported but unused > /<>/apt/auth.py:40:1: 'typing.Optional' imported but unused > /<>/apt/auth.py:40:1: 'typing.Tuple' imported but unused > /<>/apt/utils.py:21:1: 'datetime' imported but unused > /<>/apt/utils.py:24:1: 'typing.Optional' imported but unused > /<>/apt/utils.py:24:1: 'typing.Tuple' imported but unused > /<>/apt/utils.py:26:1: 'apt' imported but unused > /<>/apt/cdrom.py:25:1: 'typing.Optional' imported but unused > /<>/apt/package.py:30:1: 'threading' imported but unused > /<>/apt/package.py:36:1: 'typing.Iterable' imported but unused > /<>/apt/package.py:36:1: 'typing.Iterator' imported but unused > /<>/apt/package.py:36:1: 'typing.Optional' imported but unused > /<>/apt/package.py:36:1: 'typing.Set' imported but unused > /<>/apt/package.py:36:1: 'typing.Tuple' imported but unused > /<>/apt/package.py:36:1: 'typing.Union' imported but unused > /<>/apt/package.py:53:1: 'apt.progress.base.AcquireProgress' > imported but unused > /<>/apt/package.py:53:1: 'apt.progress.base.InstallProgress' > imported but unused > /<>/apt/debfile.py:29:1: 'typing.Dict' imported but unused > /<>/apt/debfile.py:29:1: 'typing.Iterable' imported but unused > /<>/apt/debfile.py:29:1: 'typing.List' imported but unused > /<>/apt/debfile.py:29:1: 'typing.Optional' imported but unused > /<>/apt/debfile.py:29:1: 'typing.Set' imported but unused > /<>/apt/debfile.py:29:1: 'typing.Tuple' imported but unused > /<>/apt/debfile.py:29:1: 'typing.Union' imported but unused > /<>/apt/cache.py:30:1: 'typing.Any' imported but unused > /<>/apt/cache.py:30:1: 'typing.Callable' imported but unused > /<>/apt/cache.py:30:1: 'typing.Dict' imported but unused >
Bug#1058596: [Pkg-javascript-devel] Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function
On 13/12/23 8:54 pm, Praveen Arimbrathodiyil wrote: On 13/12/23 8:52 pm, Yadd wrote: since severity is grave, please prepare an update for stable also Yes, I'm backporting the updated patch. Proposed it to release team as #1058615 OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1058218: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1
The build is failing on ppc64el for Ubuntu so it might be more of a timing issue than architecture specific. I've reported it upstream to https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2046357
Processed: Bug#1058118 marked as pending in python-apt
Processing control commands: > tag -1 pending Bug #1058118 [src:python-apt] python-apt: FTBFS: AssertionError: pyflakes failed with: 1 Ignoring request to alter tags of bug #1058118 to the same tags previously set -- 1058118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058118: marked as pending in python-apt
Control: tag -1 pending Hello, Bug #1058118 in python-apt 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/apt-team/python-apt/-/commit/f7e6175357228462b0389b45bf9ec68309403483 Convert from type comments to type annotations Automatically converted using com2ann and some manual from future imports Closes: #1058118 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058118
Bug#1042652: marked as done (pyfuse3: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Wed, 13 Dec 2023 15:34:48 + with message-id and subject line Bug#1042652: fixed in pyfuse3 3.3.0-0.1 has caused the Debian Bug report #1042652, regarding pyfuse3: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 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.) -- 1042652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyfuse3 Version: 3.2.1-2 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, pyfuse3 fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2 > -Wl,-z,relro -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-cpython-311/src/pyfuse3.o > -L/usr/lib/x86_64-linux-gnu -o > build/lib.linux-x86_64-cpython-311/pyfuse3.cpython-311-x86_64-linux-gnu.so > -lfuse3 -lpthread -lpthread -lrt > copying > build/lib.linux-x86_64-cpython-311/pyfuse3.cpython-311-x86_64-linux-gnu.so -> > src > python3 setup.py build_sphinx > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: invalid command 'build_sphinx' > make[1]: *** [debian/rules:23: build_sphinx] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/pyfuse3_3.2.1-2_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results 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 --- End Message --- --- Begin Message --- Source: pyfuse3 Source-Version: 3.3.0-0.1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of pyfuse3, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated pyfuse3 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: Wed, 13 Dec 2023 16:09:18 +0100 Source: pyfuse3 Built-For-Profiles: noudeb Architecture: source Version: 3.3.0-0.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Gianfranco Costamagna Closes: 1042652 Changes: pyfuse3 (3.3.0-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release. * Adapt sphinx build for new release of sphinx syntax (note: there is no -doc package, so currently the documentation is built but not installed) * Drop sphinxcontrib-asyncio dependency useless with the upstream cherry-pick *
Processed: Re: Fixed upstream
Processing control commands: > tags -1 pending Bug #1042652 [src:pyfuse3] pyfuse3: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' Added tag(s) pending. -- 1042652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058596: [Pkg-javascript-devel] Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function
On 13/12/23 8:52 pm, Yadd wrote: since severity is grave, please prepare an update for stable also Yes, I'm backporting the updated patch. OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1058596: [Pkg-javascript-devel] Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function
On 12/13/23 19:17, Praveen Arimbrathodiyil wrote: Control: fixed -1 1.22.19+~cs24.27.18-4 On Wed, 13 Dec 2023 20:39:39 +0530 Pirate Praveen wrote: We should backport the patches in unstable to bookworm as well. Updating the fixed info. Hi, since severity is grave, please prepare an update for stable also Cheers, Yadd
Bug#1058613: r-bioc-dss: Prevent migration to testing due to missing source
Source: r-bioc-dss Version: 2.48.0+dfsg-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: 1054...@bugs.debian.org As reported to upstream the source download for Bioconductor 3.18 of DSS is broken. To enable the Bioconductor 3.18 transition this package will be removed from testing and should not migrate again until the issue is clarified upstream. Kind regards Andreas. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1058118: marked as pending in python-apt
Control: tag -1 pending Hello, Bug #1058118 in python-apt 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/apt-team/python-apt/-/commit/f7e6175357228462b0389b45bf9ec68309403483 Convert from type comments to type annotations Automatically converted using com2ann and some manual from future imports Closes: #1058118 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058118
Processed: Bug#1058118 marked as pending in python-apt
Processing control commands: > tag -1 pending Bug #1058118 [src:python-apt] python-apt: FTBFS: AssertionError: pyflakes failed with: 1 Added tag(s) pending. -- 1058118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058247: marked as done (git-review: FTBFS: AssertionError: Exception not expected: 'GitReviewConsole' object has no attribute 'assertRaisesRegexp')
Your message dated Wed, 13 Dec 2023 15:19:12 + with message-id and subject line Bug#1058247: fixed in git-review 2.3.1-2 has caused the Debian Bug report #1058247, regarding git-review: FTBFS: AssertionError: Exception not expected: 'GitReviewConsole' object has no attribute 'assertRaisesRegexp' 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.) -- 1058247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-review Version: 2.3.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_test --no-py2 > 'git_review\.tests\.test_unit\.(?!(.*GitReviewUnitTest\.test_track.*|.*GitReviewUnitTest\.test_notify.*))' > + PKGOS_TEST_PARALLEL=yes > + PKGOS_TEST_SERIAL=no > + PYTHONS=disabled > + PYTHON3S=disabled > + TEST_PARALLEL_OPT=--parallel > + TEST_SERIAL_OPT= > + echo WARNING: --no-py2 is deprecated, and always on. > WARNING: --no-py2 is deprecated, and always on. > + shift > + py3versions -vr > + PYTHON3S=3.12 3.11 > + [ yes = no ] > + [ no = yes ] > + [ 3.12 = disabled ] > + echo 3.12 > + cut -d. -f1 > + PYMAJOR=3 > + echo ===> Testing with python (python3) > ===> Testing with python (python3) > + pwd > + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ] > + [ -e .stestr.conf ] > + [ -x /usr/bin/python3-stestr ] > + STESTR=stestr > + rm -rf .stestr > + PYTHON=python3.12 stestr run --parallel --subunit > git_review\.tests\.test_unit\.(?!(.*GitReviewUnitTest\.test_track.*|.*GitReviewUnitTest\.test_notify.*)) > + subunit2pyunit > git_review.tests.test_unit.ResolveTrackingUnitTest.test_track_git_error > git_review.tests.test_unit.ResolveTrackingUnitTest.test_track_git_error ... ok > git_review.tests.test_unit.ResolveTrackingUnitTest.test_track_local_branch > git_review.tests.test_unit.ResolveTrackingUnitTest.test_track_local_branch > ... ok > git_review.tests.test_unit.ResolveTrackingUnitTest.test_track_remote_branch > git_review.tests.test_unit.ResolveTrackingUnitTest.test_track_remote_branch > ... ok > git_review.tests.test_unit.ResolveTrackingUnitTest.test_track_untracked_branch > git_review.tests.test_unit.ResolveTrackingUnitTest.test_track_untracked_branch > ... ok > git_review.tests.test_unit.ConfigTestCase.test_git_local_mode > git_review.tests.test_unit.ConfigTestCase.test_git_local_mode ... ok > git_review.tests.test_unit.ConfigTestCase.test_gitreview_local_mode > git_review.tests.test_unit.ConfigTestCase.test_gitreview_local_mode ... ok > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_at_sign > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_at_sign ... ok > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_at_sign_escaped > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_at_sign_escaped ... ok > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_at_signs_excessive > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_at_signs_excessive ... > ok > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_no_user_no_port > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_no_user_no_port ... ok > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_opendev > git_review.tests.test_unit.RepoUrlParsingTest.test_ssh_opendev ... ok > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_polygerrit_url > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_polygerrit_url ... > ok > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url ... ok > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url_trailing_slash > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url_trailing_slash > ... ok > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url_with_hash > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url_with_hash ... > ok > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url_with_hash_and_update > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url_with_hash_and_update > ... ok > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url_with_update > git_review.tests.test_unit.DownloadFlagUnitTest.test_parse_url_with_update > ... ok >
Processed: [Help] Missing proper Build-Depends from libreoffice (Wass: Bug#1058555: parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory)
Processing control commands: > tags -1 help Bug #1058555 [src:parallel] parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory Added tag(s) help. -- 1058555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058555: [Help] Missing proper Build-Depends from libreoffice (Wass: Bug#1058555: parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory)
Control: tags -1 help Am Tue, Dec 12, 2023 at 09:52:48PM +0100 schrieb Lucas Nussbaum: > > /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or > > directory This file is (re-)created via libreoffice --headless --convert-to pdf parallel_cheat_bw.fodt Formerly this worked with the only Build-Depends libreoffice-writer-nogui. Possibly since latest upgrade of libreoffice suite I had to add the following Build-Depends: libreoffice-java-common, ure-java, default-jre-headless I admit the fact that default-jre-headless is no dependency of libreoffice-java-common smells like a bug in the dependencies but well, I have not enough insight here. Unfortunately this is not sufficient to recreate the pdf. I rather get /build/parallel-20231122+ds/src # libreoffice --headless --convert-to pdf parallel_cheat_bw.fodt Error: source file could not be loaded inside the pbuilder environment where I'm building the package. However, if I try on my local (testing!) system I get: .../parallel/src(master) $ libreoffice --headless --convert-to pdf parallel_cheat_bw.fodt convert .../parallel/src/parallel_cheat_bw.fodt as a Writer document -> .../parallel/src/parallel_cheat_bw.pdf using filter : writer_pdf_Export so the conversion is working. This pretty much sounds like some additional missing build depends which is installed in my more or less functional desktop installation of libreoffice. Rene, do you have some idea what Build-Depends might be missing in my pbuilder chroot to let the convert process work properly? Kind regards Andreas. -- http://fam-tille.de
Processed: Re: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function
Processing control commands: > fixed -1 1.22.19+~cs24.27.18-4 Bug #1058596 [yarnpkg] yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function Marked as fixed in versions node-yarnpkg/1.22.19+~cs24.27.18-4. -- 1058596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function
Control: fixed -1 1.22.19+~cs24.27.18-4 On Wed, 13 Dec 2023 20:39:39 +0530 Pirate Praveen wrote: We should backport the patches in unstable to bookworm as well. Updating the fixed info. OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1058353: libadios2-mpi-c-dev: ships headers already shipped in libadios2-common-c-dev
Source: adios2 Followup-For: Bug #1058353 Damn, something went badly wrong in debian/rules. Sorry about that. I'll fix it as soon as possible, in the meantime use the version in testing. Drew
Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function
Package: yarnpkg Version: 1.22.19+~cs24.27.18-2 severity: grave justification: breaks any options passed to yarnpkg yarnpkg install also fails with similar errors due to incompatible node-commander We should backport the patches in unstable to bookworm as well. # cat /usr/share/nodejs/yarn-error.log Arguments: /usr/bin/node /usr/bin/yarnpkg --help PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Yarn version: 1.22.19 Node version: 18.13.0 Platform: linux x64 Trace: TypeError: commander.on is not a function at Object.run (/usr/share/nodejs/yarn/lib/cli/commands/help.js:75:13) at run (/usr/share/nodejs/yarn/lib/cli/index.js:494:30) at /usr/share/nodejs/yarn/lib/cli/index.js:732:24 npm manifest: No manifest yarn manifest: No manifest Lockfile: No lockfile # yarnpkg --frozen-lockfile install TypeError: _commander(...).default.optionFor is not a function at /usr/share/nodejs/yarn/lib/cli/index.js:355:88 at Array.findIndex () at _callee$ (/usr/share/nodejs/yarn/lib/cli/index.js:352:38) at tryCatch (/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:44:17) at Generator. (/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:125:22) at Generator.next (/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:69:21) at asyncGeneratorStep (/usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:3:24) at _next (/usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:22:9) at /usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:27:7 at new Promise ()
Bug#1058557: marked as done (msolve: FTBFS: ! LaTeX Error: Unknown option 'hyperef' for package xcolor.)
Your message dated Wed, 13 Dec 2023 15:06:52 +
with message-id
and subject line Bug#1058557: fixed in msolve 0.6.1-2
has caused the Debian Bug report #1058557,
regarding msolve: FTBFS: ! LaTeX Error: Unknown option 'hyperef' for package
xcolor.
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.)
--
1058557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: msolve
Version: 0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd doc && pdflatex msolve-tutorial && \
> biber msolve-tutorial && \
> pdflatex msolve-tutorial && \
> pdflatex msolve-tutorial
> This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./msolve-tutorial.tex
> LaTeX2e <2023-11-01>
> L3 programming layer <2023-11-09>
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls
> Document Class: scrartcl 2023/07/07 v3.41 KOMA-Script document class (article)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlogo.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize11pt.clo)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifpdf.sty
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def)
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/locale/en/babel-english.tex)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amscls/amsthm.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xpatch/xpatch.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def))
> (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
>
> Package xcolor Warning: Package option `usenames' is obsolete and ignored on
> in
> put line 266.
>
>
> ! LaTeX Error: Unknown option 'hyperef' for package xcolor.
>
> For immediate help type H .
> ...
>
> l.266 \edef
>\Gin@driver{\Gin@driver}
> ?
> ! Emergency stop.
> ...
>
> l.266 \edef
>\Gin@driver{\Gin@driver}
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on msolve-tutorial.log.
> make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/msolve_0.6.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems
Bug#1058549: marked as done (plastex: FTBFS: make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 2)
Your message dated Wed, 13 Dec 2023 15:07:03 + with message-id and subject line Bug#1058549: fixed in plastex 3.0-3 has caused the Debian Bug report #1058549, regarding plastex: FTBFS: make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 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.) -- 1058549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plastex Version: 3.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > export PYTHONPATH=/<>/.pybuild/cpython3_3.12_plastex/build > /<>/.pybuild/cpython3_3.11_plastex/build; \ > export > TEXINPUTS=.:/<>/Doc/commontex:/<>/Doc/texinputs; \ > cd Doc; \ > /<>/.pybuild/cpython3_3.12_plastex/build > /<>/.pybuild/cpython3_3.11_plastex/build/../scripts/plastex > --mathjax-url=mathjax/MathJax.js?config=TeX-AMS_CHTML plastex.tex > /bin/sh: 1: export: /<>/.pybuild/cpython3_3.11_plastex/build: > bad variable name > make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/plastex_3.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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. --- End Message --- --- Begin Message --- Source: plastex Source-Version: 3.0-3 Done: Stuart Prescott We believe that the bug you reported is fixed in the latest version of plastex, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stuart Prescott (supplier of updated plastex 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: Thu, 14 Dec 2023 01:36:02 +1100 Source: plastex Architecture: source Version: 3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stuart Prescott Closes: 1058549 Changes: plastex (3.0-3) unstable; urgency=medium . * Handle multiple Python interpreters when building docs (Closes: #1058549). * Add new patch to not break PYTHONPATH during tests with non-default interpreter. Checksums-Sha1: 09fe5b14803d06489eeba55a53eb92754535d37e 2855 plastex_3.0-3.dsc c3f151cef10d41c4b31d4da760d8fc4007388d2b 89908 plastex_3.0-3.debian.tar.xz abc065d1ee3beb06d652fb9faa5344a9227b3261 12594 plastex_3.0-3_amd64.buildinfo Checksums-Sha256: 39388e85fc7fbf550f1537f88c23ea6f10a731252bc49aad9703dc2374599472 2855 plastex_3.0-3.dsc a63e85df899ec480159ba4545c2c8d38f5f556b80155776a48e32822f010c5e1 89908 plastex_3.0-3.debian.tar.xz fa0880a7e74359900260bfa037b954c5c274e36a04a0d207198ce9dd7aa1d5ca 12594 plastex_3.0-3_amd64.buildinfo Files: 04d2b895636f9cdbd24f4b6fcc25ca94 2855 python optional plastex_3.0-3.dsc 051cdecf1b703ab65c2dc5fe26d2d437 89908 python optional plastex_3.0-3.debian.tar.xz d04cfbf44e39a707212082c8fa6e28b2 12594 python optional plastex_3.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAmV5xAwACgkQu8F+uxOW 8veTThAAjS5XMdfiGnauCfA0iZRM2biuSpzsCK819H5J6193yPAyFz4Y/qHh2GW4 bLx38LDq2k1ulYpAweuvKAfVQ/3DIiVf9vB/kI56pIi8GxqItQj3ZNVK9U+ferWm l/amSVjk6lN/kpPcEVTqe6vEuT6o2ORSMtrWzdsINcCb+1VrJsSTkx9b6zdfSKoW bsIrQdgxIo7oa1S29pmo0NiCa0yQxsnnL1SHGCNr0bI0cmrL8CsgeMTll4gcg6hr
Bug#1055817: marked as done (ghc-doc: piuparts regression)
Your message dated Wed, 13 Dec 2023 15:05:33 +
with message-id
and subject line Bug#1055817: fixed in ghc 9.4.7-2
has caused the Debian Bug report #1055817,
regarding ghc-doc: piuparts regression
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.)
--
1055817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghc-doc
Version: 9.4.7-1
Severity: serious
https://piuparts.debian.org/sid/fail/ghc-doc_9.4.7-1.log
...
0m46.0s ERROR: FAIL: debsums reports modifications inside the chroot:
/usr/share/doc/ghc-doc/html/libraries/doc-index.html
/usr/share/doc/ghc-doc/html/libraries/index.html
...
#1055070 might also be related to this issue.
--- End Message ---
--- Begin Message ---
Source: ghc
Source-Version: 9.4.7-2
Done: Ilias Tsitsimpis
We believe that the bug you reported is fixed in the latest version of
ghc, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ilias Tsitsimpis (supplier of updated ghc 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: Wed, 13 Dec 2023 12:28:47 +0200
Source: ghc
Architecture: source
Version: 9.4.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
Changed-By: Ilias Tsitsimpis
Closes: 1054894 1055070 1055817 1056636 1056742
Changes:
ghc (9.4.7-2) unstable; urgency=medium
.
* Remove files generated by gen_contents_index at installation time (Closes:
#1055817)
* Canonicalize paths in gen_contents_index (Closes: #1055070)
* Backport upstream fix for CLRRI opcode on ppc64{el,} (Closes: #1054894)
* Pass number of parallel jobs from DEB_BUILD_OPTIONS to hadrian.
Code adapted from the debian/rules file for src:cmake.
Thanks to John Paul Adrian Glaubitz for the fix (Closes: #1056742).
* Restore --disable-ld-override for affected architectures (Closes: #1056636)
Checksums-Sha1:
dad8755419c712fe492a4735b51b811358ec85e6 2715 ghc_9.4.7-2.dsc
8d8e30ac33d112769d9feca02fcad4d1486007a3 65488 ghc_9.4.7-2.debian.tar.xz
c53743382d2bc83cae80f3d69b5b4cabc4285e58 12229 ghc_9.4.7-2_source.buildinfo
Checksums-Sha256:
21207a018868e1ca0312d33104984fb5b4be8c28735dfc35202e6a5159615632 2715
ghc_9.4.7-2.dsc
e4f98a9481fb8b860950d2c51e33e33d6ddf0aba6501c4fd80b7557595c18e9b 65488
ghc_9.4.7-2.debian.tar.xz
3b8ef5d7e777f08dcd058be6b93909f16e219c8690d61b0310080e6df2d1e4ce 12229
ghc_9.4.7-2_source.buildinfo
Files:
1c86ca0b58f49690d8bd0708d80615f4 2715 haskell optional ghc_9.4.7-2.dsc
895b1dd9b3a06d34b02cc36c2476c92d 65488 haskell optional
ghc_9.4.7-2.debian.tar.xz
4f73c68f24269d1e1fa0f2a7127b22b6 12229 haskell optional
ghc_9.4.7-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmV5w2sUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDwq5xAAvs7FeFAe0zXI0f/GzXVs6PIH1zay
N6DkgCEd0WP3ODHS+eN/NcbS8dTy2w1Ba9+41/D9pANlb1oB8ycDmcdGEjAbby+N
rwiG90u91cRq00wiV9prG+UXgoU+rpj/E09jNmSrQJg04fVXdv6Algw0LFyLHPXS
qY0iIgi6ckWfrN3wnarEx5Emi+8a8E0J9k62nEwfw7bN8I8a4Db7xxNrYGA+geub
sUsg1RqGeRr5H2oUDHXrXzd5KxLqhYMZcpjdEeMh99P5KLsjLgU4zk31vku5gu5f
HV62KrPOeCNREOtpNVVAt4cKtplH7+plL7IqLlQWha1tAOjbMaOfcenmXPCxWBMr
2uKY2t82VmqN+rH+84W8xCRogQ0f2fR/n7VVnOQnR7jhiM2LKhMEon7eb/V57OqO
uVg4S24Tp3ko4KExNN46+k1PXjw8sh85WsV4f3FcUNaO2uVR6I1pjiTG4CLVfEdI
cYDRsojti1/wspKKRjSFno5etcxKNnHZ1UeVEQiIF53p13rBEmYT+r5muMjZFmOq
o0CJVon9yCJ+bnBDE2iDfvFwWowebrYdgHNKduSHe3NLyJjK3HS3NQuW0yv3a2K2
mk/4cxfIL52cKCpcWeb3YVLIPIKNrmo02xT/qrmCOXJBs+D/yeNZDmhGhG22afjq
svrlvTNWEC0PooI=
=IhsG
-END PGP SIGNATURE End Message ---
Processed: Bug#1058247 marked as pending in git-review
Processing control commands: > tag -1 pending Bug #1058247 [src:git-review] git-review: FTBFS: AssertionError: Exception not expected: 'GitReviewConsole' object has no attribute 'assertRaisesRegexp' Added tag(s) pending. -- 1058247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058247: marked as pending in git-review
Control: tag -1 pending Hello, Bug #1058247 in git-review 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/openstack-team/third-party/git-review/-/commit/312652a657953e84563254f3ae3db1a67e488d9c Add fix-unit-test-for-python-3.12.patch (Closes: #1058247). (this message was generated automatically) -- Greetings https://bugs.debian.org/1058247
Bug#1058462: marked as done (texlive-bibtex-extra: file conflict with liblatex-tounicode-perl on ltx2unitxt(1) manpage)
Your message dated Wed, 13 Dec 2023 14:49:36 + with message-id and subject line Bug#1058462: fixed in texlive-extra 2023.20231207-2 has caused the Debian Bug report #1058462, regarding texlive-bibtex-extra: file conflict with liblatex-tounicode-perl on ltx2unitxt(1) manpage 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.) -- 1058462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: texlive-bibtex-extra Version: 2023.20231207-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + src:liblatex-tounicode-perl Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. >From the attached log (scroll to the bottom...): Preparing to unpack .../texlive-bibtex-extra_2023.20231207-1_all.deb ... Unpacking texlive-bibtex-extra (2023.20231207-1) ... dpkg: error processing archive /var/cache/apt/archives/texlive-bibtex-extra_2023.20231207-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/ltx2unitxt.1.gz', which is also in package liblatex-tounicode-perl 0.54-1 Errors were encountered while processing: /var/cache/apt/archives/texlive-bibtex-extra_2023.20231207-1_all.deb cheers, Andreas liblatex-tounicode-perl=0.54-1_texlive-bibtex-extra=2023.20231207-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: texlive-extra Source-Version: 2023.20231207-2 Done: Hilmar Preusse We believe that the bug you reported is fixed in the latest version of texlive-extra, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilmar Preusse (supplier of updated texlive-extra 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: Wed, 13 Dec 2023 12:04:49 + Source: texlive-extra Architecture: source Version: 2023.20231207-2 Distribution: unstable Urgency: high Maintainer: Debian TeX Task Force Changed-By: Hilmar Preusse Closes: 1058462 Changes: texlive-extra (2023.20231207-2) unstable; urgency=high . * Stop installing manual page, which is in liblatex-tounicode-perl. (Closes: #1058462). * Declare Dep on liblatex-tounicode-perl & libbibtex-parser-perl instead, the files in TL will be killed in next upload. Checksums-Sha1: 04c7526118efe802bd2ee4010fb0bc7da5d9e368 3995 texlive-extra_2023.20231207-2.dsc 66821f641c20576d610eb1a65fff0ff7493068e6 196580 texlive-extra_2023.20231207-2.debian.tar.xz 23ba5548115c2e63cdd172049d0dcd182068c7f3 6040 texlive-extra_2023.20231207-2_source.buildinfo Checksums-Sha256: 293001ee8f40a927455ec9afe5fee8fec1ba1629a698292a23f72d7dfbe6a51b 3995 texlive-extra_2023.20231207-2.dsc a830ed5d30a1d5145eaeec8bac8b7b5c9d5b55a9d83795e142beca57cad4bc08 196580 texlive-extra_2023.20231207-2.debian.tar.xz 8b2ccee44d6d5f289dce689ed7f68deef80cf924159b02a5372100931c5e7f60 6040 texlive-extra_2023.20231207-2_source.buildinfo Files: cd6fca27d80aaf47eb5730e463308fed 3995 tex optional texlive-extra_2023.20231207-2.dsc e433524005b3b645d5675ee6a8d1f571 196580 tex optional texlive-extra_2023.20231207-2.debian.tar.xz 757dc8a63fa4ad128848ff383742b8b9 6040 tex optional texlive-extra_2023.20231207-2_source.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmV5syhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5 NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg LIsHow//WZXTwycIMt62QkXDogxdLqI5BwNyPUMPuNGnTaIghZ1RbFyjN27DqMIj eRj6nJfUuvGdzFwwLJ/l3iiWfql9OV25isRwEiAfU3M7/XHo84osR7F4Lk2K9uT+ 8KynfvngMFxJjy8skH+IsEclyVklmccI2E3WTFswq4AiUdzPHlzx8r+CohwrJBSf YDvJSnS1/iZHQSC/Ioja0kcV+hWm2rADS97GvY8ENKBNZSynKmWlvccvMB+AmE1m /VVkX9zx0pk8yQxbj9keiKbNezN2ESi6e2gyb+PQgSe0ef6rl7PZ7rBDqr1Z5Fe3 qNWvP2YaUpdVlIqwg93C6yggepM0v7Jc0/4BgPcAdLvqdT1KjVEczQJHQL7gfXDf jwT7bYbQhiz2eJCyzqRiwWzhtjnFHS4465s/fl44FZvgZ+vFCLTrUk3HhOq88fEx xjYiTnuZR4/dnhmhux5I315bB/b9vHcsXqzBzSqQxs9owvmeHDfGjFZFCbq4M2fi
Bug#1058152: marked as done (qt5reactor: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)
Your message dated Wed, 13 Dec 2023 14:34:59 +
with message-id
and subject line Bug#1058152: fixed in qt5reactor 0.6.1-2
has caused the Debian Bug report #1058152,
regarding qt5reactor: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)
--
1058152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt5reactor
Version: 0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> /<>/versioneer.py:421: SyntaxWarning: invalid escape sequence
> '\s'
> LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
> File "/<>/setup.py", line 29, in
> version=versioneer.get_version(),
>
> File "/<>/versioneer.py", line 1480, in get_version
> return get_versions()["version"]
>^^
> File "/<>/versioneer.py", line 1412, in get_versions
> cfg = get_config_from_root(root)
> ^^
> File "/<>/versioneer.py", line 342, in get_config_from_root
> parser = configparser.SafeConfigParser()
> ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'.
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/qt5reactor_0.6.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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.
--- End Message ---
--- Begin Message ---
Source: qt5reactor
Source-Version: 0.6.1-2
Done: Stuart Prescott
We believe that the bug you reported is fixed in the latest version of
qt5reactor, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stuart Prescott (supplier of updated qt5reactor 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: Thu, 14 Dec 2023 00:42:48 +1100
Source: qt5reactor
Architecture: source
Version: 0.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team
Changed-By: Stuart Prescott
Closes: 1058152
Changes:
qt5reactor (0.6.1-2) unstable; urgency=medium
.
* Update Standards-Version to 4.6.2 (no changes required).
* Update Homepage.
* Add new patch to embedded versioneer.py to handle configparser change
(Closes: #1058152).
Checksums-Sha1:
1e9281e57d60374f10af1ced1f9c3087023cbfae 2025 qt5reactor_0.6.1-2.dsc
c5ee7826d3b3c243d906a5f4d533121f614a1f99 2892 qt5reactor_0.6.1-2.debian.tar.xz
c6467642cf96e1e20c0dd98833b1f4c626cad18e 7299
qt5reactor_0.6.1-2_amd64.buildinfo
Checksums-Sha256:
12b46c836dd85e37ad7df7b46eeceae2fabddf82ab6becd386d6847c19081331 2025
qt5reactor_0.6.1-2.dsc
225b4cb3a7c5d347c6ab24e4568b0c971eea46c36f94d2976f8dab51c6380db5 2892
qt5reactor_0.6.1-2.debian.tar.xz
Processed: Bug#1058152 marked as pending in qt5reactor
Processing control commands: > tag -1 pending Bug #1058152 [src:qt5reactor] qt5reactor: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? Added tag(s) pending. -- 1058152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058152: marked as pending in qt5reactor
Control: tag -1 pending Hello, Bug #1058152 in qt5reactor 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/qt-kde-team/extras/qt5reactor/-/commit/24edbfe4ed1a235cafd825454bac08283dbf1370 Add patch to change configparser usage Closes: #1058152 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058152
Bug#1058384: lazy-object-proxy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Control: forwarded -1 https://github.com/ionelmc/python-lazy-object-proxy/pull/78 Dear Maintainer, Root cause is that deprecations are treated as errors in pytest.ini [1] Kind regards [1] https://sources.debian.org/src/lazy-object-proxy/1.9.0-1/pytest.ini/#L35-L36
Processed: Re: lazy-object-proxy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Processing control commands:
> forwarded -1 https://github.com/ionelmc/python-lazy-object-proxy/pull/78
Bug #1058384 [src:lazy-object-proxy] lazy-object-proxy: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned
exit code 13
Set Bug forwarded-to-address to
'https://github.com/ionelmc/python-lazy-object-proxy/pull/78'.
--
1058384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058166: marked as done (python-tubes: FTBFS: AttributeError: 'RouterTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)
Your message dated Wed, 13 Dec 2023 13:49:40 + with message-id and subject line Bug#1058166: fixed in python-tubes 0.2.1-4 has caused the Debian Bug report #1058166, regarding python-tubes: FTBFS: AttributeError: 'RouterTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? 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.) -- 1058166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-tubes Version: 0.2.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:310: python3.12 setup.py config > running config > I: pybuild base:310: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:310: /usr/bin/python3.12 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/__init__.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/framing.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/fan.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/tube.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/undefer.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/_siphon.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/memory.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/itube.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/listening.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/protocol.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/routing.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/kit.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > copying tubes/_components.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes > creating /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/__init__.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_tube.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_routing.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_undefer.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_memory.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_kit.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_protocol.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/util.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_framing.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_fan.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_listening.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > copying tubes/test/test_chatter.py -> > /<>/.pybuild/cpython3_3.12_tubes/build/tubes/test > I: pybuild base:310: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/__init__.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/framing.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/fan.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/tube.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/undefer.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/_siphon.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/memory.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/itube.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/listening.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/protocol.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/routing.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/kit.py -> > /<>/.pybuild/cpython3_3.11_tubes/build/tubes > copying tubes/_components.py -> >
Bug#1056509: marked as done (python-tube's autopkg tests fail with Python 3.12)
Your message dated Wed, 13 Dec 2023 13:49:40 +
with message-id
and subject line Bug#1056509: fixed in python-tubes 0.2.1-4
has caused the Debian Bug report #1056509,
regarding python-tube's autopkg tests fail with Python 3.12
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.)
--
1056509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-tubes
Version: 0.2.1-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-tube's autopkg tests fail with Python 3.12:
[...]
296s ==
296s ERROR: test_linesToBytes
(test.test_framing.LineTests.test_linesToBytes)
296s Writing out lines delimits them, with the delimiter.
296s --
296s Traceback (most recent call last):
296s File
"/tmp/autopkgtest.fbHH6R/autopkgtest_tmp/build/test/test_framing.py",
line 94, in test_linesToBytes
296s self.assertEquals(b"".join(fd.received), b"hello\r\nworld\r\n")
296s ^
296s AttributeError: 'LineTests' object has no attribute 'assertEquals'.
Did you mean: 'assertEqual'?
296s
296s ==
296s ERROR: test_rawMode (test.test_framing.LineTests.test_rawMode)
296s You should be able to have some lines, and then some bytes, and then
296s --
296s Traceback (most recent call last):
296s File
"/tmp/autopkgtest.fbHH6R/autopkgtest_tmp/build/test/test_framing.py",
line 128, in test_rawMode
296s self.assertEquals(b"".join(Switchee.datums), b"abcde\r\nfgh")
296s ^
296s AttributeError: 'LineTests' object has no attribute 'assertEquals'.
Did you mean: 'assertEqual'?
296s
296s ==
296s ERROR: test_stringToLines
(test.test_framing.LineTests.test_stringToLines)
296s A line is something delimited by a LF or CRLF.
296s --
296s Traceback (most recent call last):
296s File
"/tmp/autopkgtest.fbHH6R/autopkgtest_tmp/build/test/test_framing.py",
line 81, in test_stringToLines
296s splitALine(b"\n")
296s File
"/tmp/autopkgtest.fbHH6R/autopkgtest_tmp/build/test/test_framing.py",
line 80, in splitALine
296s self.assertEquals(fd.received, [b"alpha", b"beta"])
296s ^
296s AttributeError: 'LineTests' object has no attribute 'assertEquals'.
Did you mean: 'assertEqual'?
296s
296s ==
296s ERROR: test_switchingWithMoreDataToDeliver
(test.test_framing.LineTests.test_switchingWithMoreDataToDeliver)
296s Switching drains should immediately stop delivering data.
296s --
296s Traceback (most recent call last):
296s File
"/tmp/autopkgtest.fbHH6R/autopkgtest_tmp/build/test/test_framing.py",
line 151, in test_switchingWithMoreDataToDeliver
296s self.assertEquals(fd1.received, [b"something"])
296s ^
296s AttributeError: 'LineTests' object has no attribute 'assertEquals'.
Did you mean: 'assertEqual'?
296s
296s ==
296s ERROR: test_bytesToNetstrings
(test.test_framing.NetstringTests.test_bytesToNetstrings)
296s L{bytesToNetstrings} works on subsequent inputs as well.
296s --
296s Traceback (most recent call last):
296s File
"/tmp/autopkgtest.fbHH6R/autopkgtest_tmp/build/test/test_framing.py",
line 45, in test_bytesToNetstrings
296s self.assertEquals(
296s ^
296s AttributeError: 'NetstringTests' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
296s
296s ==
296s ERROR: test_netstringToString
(test.test_framing.NetstringTests.test_netstringToString)
296s Length prefix is stripped off.
296s --
296s Traceback (most recent call last):
296s File
"/tmp/autopkgtest.fbHH6R/autopkgtest_tmp/build/test/test_framing.py",
line 62, in test_netstringToString
296s self.assertEquals(fd.received, [b"x", b"yz"])
296s ^
296s AttributeError:
Processed: tagging 1058031, bug 1058031 is forwarded to https://github.com/pygame/pygame/issues/4046
Processing commands for cont...@bugs.debian.org: > tags 1058031 + upstream Bug #1058031 [src:pygame] pygame: FTBFS with Python 3.12 Added tag(s) upstream. > forwarded 1058031 https://github.com/pygame/pygame/issues/4046 Bug #1058031 [src:pygame] pygame: FTBFS with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/pygame/pygame/issues/4046'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058201: marked as done (pytorch-scatter: FTBFS: ImportError: Failed to load PyTorch C extensions:)
Your message dated Wed, 13 Dec 2023 13:04:29 +
with message-id
and subject line Bug#1058201: fixed in pytorch-scatter 2.1.2-1
has caused the Debian Bug report #1058201,
regarding pytorch-scatter: FTBFS: ImportError: Failed to load PyTorch C
extensions:
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.)
--
1058201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytorch-scatter
Version: 2.1.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 8, in
> import torch
> File "/usr/lib/python3/dist-packages/torch/__init__.py", line 443, in
>
> raise ImportError(textwrap.dedent('''
> ImportError: Failed to load PyTorch C extensions:
> It appears that PyTorch has loaded the `torch/_C` folder
> of the PyTorch repository rather than the C extensions which
> are expected in the `torch._C` namespace. This can occur when
> using the `install` workflow. e.g.
> $ python setup.py install && python -c "import torch"
>
> This error can generally be solved using the `develop` workflow
> $ python setup.py develop && python -c "import torch" # This should
> succeed
> or by running Python from a different directory.
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:10: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/pytorch-scatter_2.1.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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.
--- End Message ---
--- Begin Message ---
Source: pytorch-scatter
Source-Version: 2.1.2-1
Done: Andrius Merkys
We believe that the bug you reported is fixed in the latest version of
pytorch-scatter, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrius Merkys (supplier of updated pytorch-scatter 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: Wed, 13 Dec 2023 07:25:18 -0500
Source: pytorch-scatter
Architecture: source
Version: 2.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team
Changed-By: Andrius Merkys
Closes: 1058201
Changes:
pytorch-scatter (2.1.2-1) unstable; urgency=medium
.
* New upstream version 2.1.2
* Build on default Python only as python3-torch is built only there
(Closes: #1058201)
Checksums-Sha1:
6cc119773da5e423e79cea63ec1b7d4f2396c516 2216 pytorch-scatter_2.1.2-1.dsc
c53a2f830e66d322bc4cbe4c25782a219bc0539a 104854
pytorch-scatter_2.1.2.orig.tar.gz
b015659d8b518f5132bc325daba848b93a8f8fa5 2520
pytorch-scatter_2.1.2-1.debian.tar.xz
8baf3bdf6dc26ff747bdbb7c25b06efb1b362cde 18598
pytorch-scatter_2.1.2-1_source.buildinfo
Checksums-Sha256:
6f4adfa46fe4ff17dd7133a7a8e4d7c86d51750eae6bc7d84f30dd9fe454f5a9 2216
pytorch-scatter_2.1.2-1.dsc
6f375dbc9cfe03f330aa29ea553e9c7432e9b040d039b041f08bf05df1a8bf37 104854
Bug#1058504: marked as done (lua-zlib: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2)
Your message dated Wed, 13 Dec 2023 12:48:56 + with message-id and subject line Bug#1058504: fixed in lua-zlib 1.2-4 has caused the Debian Bug report #1058504, regarding lua-zlib: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test 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.) -- 1058504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-zlib Version: 1.2-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > DEB_BUILD_MAINT_OPTIONS=hardening=-stackprotector dh build --buildsystem=lua > --with lua >dh_update_autotools_config -O--buildsystem=lua >dh_autoreconf -O--buildsystem=lua >dh_auto_configure -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple configure > > Making target configure for debian/lua5.1.dh-lua.conf > # .install > Filling in debian/lua-zlib.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/lib/x86_64-linux-gnu/lua/5.1/zlib.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-zlib.so.* > Filling in debian/lua-zlib-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-zlib.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-zlib.a > Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.1-zlib.pc > Adding new line: usr/include/lua5.1/lua-zlib.h > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.1 > Target configure made > > > Making target configure for debian/lua5.2.dh-lua.conf > # .install > Filling in debian/lua-zlib.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/lib/x86_64-linux-gnu/lua/5.2/zlib.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-zlib.so.* > Filling in debian/lua-zlib-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-zlib.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-zlib.a > Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.2-zlib.pc > Adding new line: usr/include/lua5.2/lua-zlib.h > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.2 > Target configure made > > > Making target configure for debian/lua5.3.dh-lua.conf > # .install > Filling in debian/lua-zlib.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/lib/x86_64-linux-gnu/lua/5.3/zlib.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-zlib.so.* > Filling in debian/lua-zlib-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-zlib.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-zlib.a > Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-zlib.pc > Adding new line: usr/include/lua5.3/lua-zlib.h > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.3 > Target configure made > > > Making target configure for debian/lua5.4.dh-lua.conf > # .install > Filling in debian/lua-zlib.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/lib/x86_64-linux-gnu/lua/5.4/zlib.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-zlib.so.* > Filling in debian/lua-zlib-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-zlib.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-zlib.a > Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.4-zlib.pc > Adding new line: usr/include/lua5.4/lua-zlib.h > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.4 > Target configure made > >dh_auto_build -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple build > > Making target build for debian/lua5.1.dh-lua.conf > libtoolize: putting auxiliary files in '.'. > libtoolize: copying file './config.guess' > libtoolize: copying file './config.sub' > libtoolize: copying file './install-sh' > libtoolize: copying file './ltmain.sh' > libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, > libtoolize: and rerunning libtoolize and aclocal. > libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
Bug#1055553: marked as done (python-lzo ftbfs with Python 3.12)
Your message dated Wed, 13 Dec 2023 13:29:34 +0100 with message-id <5e5a0b0b-13ed-4c70-8af1-b26237afa...@debian.org> and subject line Fixed has caused the Debian Bug report #103, regarding python-lzo ftbfs with Python 3.12 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.) -- 103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-lzo Version: 1.14-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] dh_auto_test -O--buildsystem=pybuild I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_lzo/build; python3.12 -m nose -v tests Traceback (most recent call last): File "", line 189, in _run_module_as_main File "", line 148, in _get_module_details File "", line 112, in _get_module_details File "/usr/lib/python3/dist-packages/nose/__init__.py", line 1, in from nose.core import collector, main, run, run_exit, runmodule File "/usr/lib/python3/dist-packages/nose/core.py", line 12, in from nose.loader import defaultTestLoader File "/usr/lib/python3/dist-packages/nose/loader.py", line 21, in from nose.importer import Importer, add_path, remove_path File "/usr/lib/python3/dist-packages/nose/importer.py", line 12, in from imp import find_module, load_module, acquire_lock, release_lock ModuleNotFoundError: No module named 'imp' and then later fails with: [...] dh_auto_test -O--buildsystem=pybuild I: pybuild base:310: cd /home/packages/12/python-lzo-1.14/.pybuild/cpython3_3.12_lzo/build; python3.12 -m nose -v tests Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/result.py", line 14, in from unittest.runner import _TextTestResult ImportError: cannot import name '_TextTestResult' from 'unittest.runner' (/usr/lib/python3.12/unittest/runner.py). Did you mean: 'TextTestResult'? During handling of the above exception, another exception occurred: Traceback (most recent call last): File "", line 189, in _run_module_as_main File "", line 148, in _get_module_details File "", line 112, in _get_module_details File "/usr/lib/python3/dist-packages/nose/__init__.py", line 1, in from nose.core import collector, main, run, run_exit, runmodule File "/usr/lib/python3/dist-packages/nose/core.py", line 15, in from nose.result import TextTestResult File "/usr/lib/python3/dist-packages/nose/result.py", line 16, in from unittest import _TextTestResult ImportError: cannot import name '_TextTestResult' from 'unittest' (/usr/lib/python3.12/unittest/__init__.py). Did you mean: 'TextTestResult'? E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd /home/packages/12/python-lzo-1.14/.pybuild/cpython3_3.12_lzo/build; python3.12 -m nose -v tests --- End Message --- --- Begin Message --- Fixed in nose.--- End Message ---
Bug#1058143: marked as done (python-pyutil: FTBFS: AttributeError: 'TestDecode' object has no attribute 'assert_'. Did you mean: 'assertIn'?)
Your message dated Wed, 13 Dec 2023 12:19:57 + with message-id and subject line Bug#1058143: fixed in python-pyutil 3.3.2-2 has caused the Debian Bug report #1058143, regarding python-pyutil: FTBFS: AttributeError: 'TestDecode' object has no attribute 'assert_'. Did you mean: 'assertIn'? 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.) -- 1058143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pyutil Version: 3.3.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:310: python3.12 setup.py config > running config > I: pybuild base:310: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:310: /usr/bin/python3.12 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/repeatable_random.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/verlib.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/fileutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/__init__.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/strutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/observer.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/lineutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/jsonutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/assertutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/twistedutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/version_class.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/find_exe.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/_version.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/benchutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/weakutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/logutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/increasing_timer.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/dictutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/humanreadable.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/odict.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/mathutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/platformutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/PickleSaver.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/randutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/testutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/nummedobj.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/iputil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/time_format.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/memutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/zlibutil.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > copying pyutil/cache.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil > creating /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil/test > copying pyutil/test/__init__.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil/test > creating /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil/scripts > copying pyutil/scripts/__init__.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil/scripts > copying pyutil/scripts/tailx.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil/scripts > copying pyutil/scripts/unsort.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil/scripts > copying pyutil/scripts/verinfo.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil/scripts > copying pyutil/scripts/randfile.py -> > /<>/.pybuild/cpython3_3.12_pyutil/build/pyutil/scripts > copying
Bug#1058519: marked as done (node-mdn-browser-compat-data: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1)
Your message dated Wed, 13 Dec 2023 12:19:46 +
with message-id
and subject line Bug#1058519: fixed in node-mdn-browser-compat-data
5.2.20+~3.33.0-2
has caused the Debian Bug report #1058519,
regarding node-mdn-browser-compat-data: FTBFS: make[1]: *** [debian/rules:11:
override_dh_auto_build] Error 1
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.)
--
1058519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-mdn-browser-compat-data
Version: 5.2.20+~3.33.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ts-node scripts/generate-types.ts
> TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for
> /<>/scripts/generate-types.ts
> at new NodeError (node:internal/errors:405:5)
> at Object.getFileProtocolModuleFormat [as file:]
> (node:internal/modules/esm/get_format:136:11)
> at defaultGetFormat (node:internal/modules/esm/get_format:182:36)
> at defaultLoad (node:internal/modules/esm/load:101:20)
> at nextLoad (node:internal/modules/esm/hooks:864:28)
> at load (/usr/share/nodejs/ts-node/dist/child/child-loader.js:19:122)
> at nextLoad (node:internal/modules/esm/hooks:864:28)
> at Hooks.load (node:internal/modules/esm/hooks:447:26)
> at MessagePort.handleMessage (node:internal/modules/esm/worker:196:24)
> at [nodejs.internal.kHybridDispatch] (node:internal/event_target:786:20) {
> code: 'ERR_UNKNOWN_FILE_EXTENSION'
> }
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/node-mdn-browser-compat-data_5.2.20+~3.33.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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.
--- End Message ---
--- Begin Message ---
Source: node-mdn-browser-compat-data
Source-Version: 5.2.20+~3.33.0-2
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-mdn-browser-compat-data, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-mdn-browser-compat-data
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: Wed, 13 Dec 2023 15:52:16 +0400
Source: node-mdn-browser-compat-data
Architecture: source
Version: 5.2.20+~3.33.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1058519
Changes:
node-mdn-browser-compat-data (5.2.20+~3.33.0-2) unstable; urgency=medium
.
* Update standards version to 4.6.2, no changes needed
* Workaround ts-node bug (Closes: #1058519)
Checksums-Sha1:
149aa6efa775ca2f17b8c59fb1fdd51e75343246 2800
node-mdn-browser-compat-data_5.2.20+~3.33.0-2.dsc
f514822a626bebc2762a5239e0cec30543a5eb28 73376
node-mdn-browser-compat-data_5.2.20+~3.33.0-2.debian.tar.xz
Checksums-Sha256:
ad86de41fe4b8e5b6f0d62ccf8e3b32ddf8b0b8d986ed1f1961674a743826fd4 2800
node-mdn-browser-compat-data_5.2.20+~3.33.0-2.dsc
a634ef344e0e9a421847adb2fa3963e7b4a5c39cda1979e190aa6e0a2cc90bfe 73376
node-mdn-browser-compat-data_5.2.20+~3.33.0-2.debian.tar.xz
Files:
7d61fc24d38d7fdaf569bae9dac1b882 2800 javascript optional
