Bug#1029179: marked as done (relion-cuda: rebuild for libtiff6 transition)
Your message dated Thu, 19 Jan 2023 07:54:35 + with message-id and subject line Bug#1029179: fixed in relion-cuda 3.1.3-2 has caused the Debian Bug report #1029179, regarding relion-cuda: rebuild for libtiff6 transition 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.) -- 1029179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: relion-cuda Version: 3.1.3-1 Severity: serious Tag: sid bookworm relion-cuda requires a rebuild for the libtiff5 -> libtiff6 transition. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: relion-cuda Source-Version: 3.1.3-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of relion-cuda, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated relion-cuda 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, 19 Jan 2023 07:57:26 +0100 Source: relion-cuda Binary: relion-cuda relion-cuda-dbgsym relion-gui-cuda relion-gui-cuda-dbgsym Architecture: source amd64 Version: 3.1.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: relion-cuda - parallel toolkit for 3D reconstructions in cryo-electron microsco relion-gui-cuda - toolkit for 3D reconstructions in cryo-electron microscopy (gui a Closes: 1029179 Changes: relion-cuda (3.1.3-2) unstable; urgency=medium . * Team upload. * Fix watch file * Rebuild for the libtiff5 -> libtiff6 transition Closes: #1029179 Checksums-Sha1: 7ae6f84b0f6be10a50f8e2c23a17c495d422d168 2197 relion-cuda_3.1.3-2.dsc 78cf05e224cd35054fb8b47e47b1041691cbb553 12188 relion-cuda_3.1.3-2.debian.tar.xz 15b9bc8b4fff0c6a5511e2ecb573c7045a1b818d 741255312 relion-cuda-dbgsym_3.1.3-2_amd64.deb 52b2b55df6c9b4242c898b674a9a380885ef28b7 14030 relion-cuda_3.1.3-2_amd64.buildinfo 2c596c13d834514134b0afde2378d9155f66d8c0 81247420 relion-cuda_3.1.3-2_amd64.deb b80f1998b83215ffd2d3a2e77db797d6a7a01776 53131100 relion-gui-cuda-dbgsym_3.1.3-2_amd64.deb 2eaf500acd9da2c7a9f0fe99e1e316e5a107520c 5798516 relion-gui-cuda_3.1.3-2_amd64.deb Checksums-Sha256: 7daf8bbfd21d57e1eb672c7f3d411f8b1a8675bdd2a68a19feed96a454dc5d95 2197 relion-cuda_3.1.3-2.dsc e8013765e8d68887fc7418cd16cdb4b8d1d7ba29b8bafcbbdaf635295a42798e 12188 relion-cuda_3.1.3-2.debian.tar.xz 768c37595ceca369aae04d9ca02bb36659032518a0d838853f44fa744b7f 741255312 relion-cuda-dbgsym_3.1.3-2_amd64.deb d6ec7164cfe91813accdb554c96a099aff605815ab9f5afd865890092681bbf5 14030 relion-cuda_3.1.3-2_amd64.buildinfo 7a2c2ed7e335dd02a9195a08312199b5a510ea8bc598152af7d310e6b0377cd1 81247420 relion-cuda_3.1.3-2_amd64.deb cdb07afd5715c0c1ee92a664a4673f7c78746b530408dce801f18364bf716082 53131100 relion-gui-cuda-dbgsym_3.1.3-2_amd64.deb d9c014985f7167ceca647f4410f87f7fd1efc52411d5e05b1c9601bd0924885c 5798516 relion-gui-cuda_3.1.3-2_amd64.deb Files: 087a308f2820f1c261f570e7c5ddf04c 2197 contrib/science optional relion-cuda_3.1.3-2.dsc b60cd9d3861dcd5954672dda8cf48b73 12188 contrib/science optional relion-cuda_3.1.3-2.debian.tar.xz 5e6b600b89b089b44bcd53e1ce724242 741255312 contrib/debug optional relion-cuda-dbgsym_3.1.3-2_amd64.deb 6c4dbe43b9b5e08798a4bd3fb3ec88f0 14030 contrib/science optional relion-cuda_3.1.3-2_amd64.buildinfo bd70c9e7e47d29e168fa098bf3905941 81247420 contrib/science optional relion-cuda_3.1.3-2_amd64.deb 0237e5a62cd06b77baa74ffded729655 53131100 contrib/debug optional relion-gui-cuda-dbgsym_3.1.3-2_amd64.deb 40759dcf2018f2baf3bec4eb6027818b 5798516 contrib/science optional relion-gui-cuda_3.1.3-2_amd64.deb -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPI76wRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFjIA//ZU0BksCv7uACCXC8dkONhUNcQAgw5jKD dugArtUx8a7qMrz8LUUJgxkfi2rx4Vb5GCxxKYXnJPhNw7M6knNZChDZ4QFYOBVI mSOFYamiQzAMcdSpTZx8iR6UaES2WmJC1Iw5hJLlfiaxfJ0TvYsFzEGXuBI+MxHS eM+YKgejI47CX03wxHMH7gya8kQDI+6LNyVvcM/+IPWCN+8tgZFsND+zj7Z+11RW gzN5xUDMCj2m
Bug#1017919: Unable to reproduce
Hello I tested on version 108.0.2 and it works fine othing crashed Thank you Mina
Bug#1028587: datefudge: 64-bit time_t functions are not implemented/exposed
On Wed, Jan 18, 2023 at 12:50:15PM +0200, Graham Inggs wrote: > Control: severity -1 serious > Control: tags -1 + ftbfs > > Hi Maintainer and i386, arm, mips porters > > > As far as I can tell, the reason is that coreutils now uses a 64-bit > > time_t and functions with a "64" suffix. Datefudge however does not > > expose nor implement such functions. > > As can be seen on reproducible builds [1], datefudge now FTBFS on at > least i386 and armhf, and I was able to confirm the failure on the > mipsel porterbox. > > As datefudge is a build-dependency of gnutls28 and oath-toolkit, both > key packages, how should this be resolved? I'd start by asking how many implementations of this functionality we ship, and whether all of them have the same problem. faketime has more users and an upstream, but the same problem. Adding the missing functionality to one implementation (faketime?) and ensuring there are RC bugs against all other implementations (are there other ones apart from datefudge?) would be my suggestion. Users of unfixed implementations could then migrated to fixed ones. > Regards > Graham >... cu Adrian
Bug#1029178: vtk-dicom: autopkgtest failure
On Wed, Jan 18, 2023 at 11:29:35PM +0100, Sebastian Ramacher wrote: > Source: vtk-dicom > Version: 0.8.14-3 > Severity: serious > > https://ci.debian.net/data/autopkgtest/testing/amd64/v/vtk-dicom/30492694/log.gz > > autopkgtest [23:14:01]: test autodep8-python3: set -e ; for py in > $(py3versions -d 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with > $py:" ; $py -c "import vtkdicom; print(vtkdicom)" ; done > autopkgtest [23:14:01]: test autodep8-python3: [--- > Testing with python3.10: > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python3/dist-packages/vtkdicom/__init__.py", line 1, in > > from .vtkDICOM import * > ModuleNotFoundError: No module named 'vtkdicom.vtkDICOM' I don't see how this is the fault of the package, or something the package could easily address.[1] The package builds a Python C extension against the default Python3 version only. The autopkgtest tests this extension against the default Python3 version. With python3/unstable the autopkgtest is passing: https://ci.debian.net/packages/v/vtk-dicom/ Testing against a different python3 default fails for obvious reasons. > Cheers cu Adrian [1] Building a Python C extension against multiple Python3 versions is easy for packages that build nothing else, but usually hard (and rarely done) for packages that build Python bindings for a C/C++ library as part of their normal build process.
Bug#1029182: marked as done (pgcli: Dependency needs updating python3-psycopg3 -> python3-psycopg)
Your message dated Thu, 19 Jan 2023 06:34:03 + with message-id and subject line Bug#1029182: fixed in pgcli 3.5.0-4 has caused the Debian Bug report #1029182, regarding pgcli: Dependency needs updating python3-psycopg3 -> python3-psycopg 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.) -- 1029182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgcli Version: 3.5.0-3 Severity: serious python3-psycopg3 does not exist anymore, see #1016031. --- End Message --- --- Begin Message --- Source: pgcli Source-Version: 3.5.0-4 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of pgcli, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated pgcli 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, 19 Jan 2023 07:17:12 +0100 Source: pgcli Architecture: source Version: 3.5.0-4 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1029182 Changes: pgcli (3.5.0-4) sid; urgency=medium . * Uploading to sid. * Updating to standards version 4.6.2. * Updating psycopg3 depends (Closes: #1029182). Checksums-Sha1: 9e0e3808e63c133ed30c35f3d5d1c0c17a084753 1984 pgcli_3.5.0-4.dsc 6356328096aa8a6c01a607d240caf840399b1917 4328 pgcli_3.5.0-4.debian.tar.xz 761a66508b90efd353374e1e78d255eb0d452edb 6657 pgcli_3.5.0-4_amd64.buildinfo Checksums-Sha256: d87bbf0d8b3b6da668abb850b87c9aa9f01e55e73e32c6c50b37863ce017dc34 1984 pgcli_3.5.0-4.dsc d34f6b41593a4c16a6677bf70f0b161c21c000b48fddbbaa6cde7480a03ab9f0 4328 pgcli_3.5.0-4.debian.tar.xz b7ab9d6dba71d332397d3415efbb51fd4852e00bc26d72e6e2860d7c831e0eba 6657 pgcli_3.5.0-4_amd64.buildinfo Files: 98063b6f63bb38db8f8f96c8751fd804 1984 database optional pgcli_3.5.0-4.dsc 71f8ae29e827757e0d97359b3cd9e6d8 4328 database optional pgcli_3.5.0-4.debian.tar.xz f3afae71361c2497f0f15a4a28a547c2 6657 database optional pgcli_3.5.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmPI4I0ACgkQVc8b+Yar uccSnA/8CA6y9GIw/Oz2BeMvhB5ViASmdGrN+QOU44O46G4tJcpZ8ghlBDowkxCS SK5s6TpvmSts6iV2D66CLL0abFiRFQSEwQ3CfthuvAFDQP6U3vS4LafjnvtKNMrU y2ofbnq0Yq/ancayv+DhhtvoO0ZAcA7k6SquTE0xvnycoGNM/i96sOsfIJTlUz2I U39LAOXQreHnqukEjW2AehmHNH99Z/r4EXALOpK4hqXQkZ0vt4BipOYIoXgtXGkc f9RhdTClRZShohnmr/dBQQj3r3CSWEiRgg/sHArk+YrudJxdo2C8DPZkl/UR+yeD xzmNIb208pt0TpEURMjVGxmpQV/t3VOjkCBOuqMD2VF70gBXGRJVvBNmr6006QMP I7jhQ8yzcETIRDa5zai5Ooxh/vcp+2J0pdqzsvhwwQSyRi1G724/fUZ0lqtDbfbd IsKLMR02xB6aDFH/+95WBcYmCZCR2J5DkJaSPGaiO+aJHa0ihSFMN4Am76LyByz2 Qj5OwQgRmkyNbKhKS8V07iUPgxsHC7DDZeToqTarn/TFumFWYomZh4ZxGEkZurMn zFl+ZTU77mEYIAU5Y9oqT8JhSlMMzg6AX/1k2kw7ROkJk7EUCCr/lmNDfrU9nI6Q ULW06QPSOkWTIkVKX8B06/wkPC9DJzZ2xZ6bDJPxgHnmzfney98= =lvEg -END PGP SIGNATURE End Message ---
Bug#1015092: marked as done (fonts-ocr-a: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Thu, 19 Jan 2023 07:20:45 +0100 with message-id <8b533e73c4f64844ef756cad43266...@phys.ethz.ch> and subject line fonts-ocr-a: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #1015092, regarding fonts-ocr-a: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 1015092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fonts-ocr-a Version: 1.0-10 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Making OCRABold > Internal Error (overlap): Mismatched intersection. > (577.44,660.73)->(596.484,629.212) ends at (-99,-99) while > (596.484,629.212)->(597.837,624.513) starts at (596.484,629.212) > Internal Error (overlap): Winding number did not return to 0 when y=629.212 > Internal Error (overlap): Winding number did not return to 0 when y=629.212 > Internal Error (overlap): Winding number did not return to 0 when y=629.212 > Internal Error (overlap): Winding number did not return to 0 when y=629.212 > Internal Error (overlap): Winding number did not return to 0 when y=629.212 > Internal Error (overlap): Winding number did not return to 0 when y=629.212 > Internal Error (overlap): Winding number did not return to 0 when y=629.212 > Internal Error (overlap): Winding number did not return to 0 when y=629.212 > Internal Error (overlap): Neither needed nor unneeded > (596.484,629.212)->(596.484,629.212) > Internal Error (overlap): Humph. This monotonic leads nowhere > (426.041,758.838)->(436.173,759.665). > Internal Error (overlap): couldn't find a needed exit from an intersection > Internal Error (overlap): couldn't find a needed exit from an intersection > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2022/07/16/fonts-ocr-a_1.0-10_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- this has been a problem in fontforge and fixed with the recent sid upload--- End Message ---
Processed: python-pgspecial: Dependency and build dependency must be updated to python3-psycopg3 -> python3-psycopg
Processing control commands: > affects -1 python3-pgspecial Bug #1029183 [src:python-pgspecial] python-pgspecial: Dependency and build dependency must be updated to python3-psycopg3 -> python3-psycopg Added indication that 1029183 affects python3-pgspecial -- 1029183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029183: python-pgspecial: Dependency and build dependency must be updated to python3-psycopg3 -> python3-psycopg
Source: python-pgspecial Version: 2.0.1-1 Severity: serious Tags: ftbfs Control: affects -1 python3-pgspecial python3-psycopg3 does not exist anymore, see #1016031.
Bug#1029182: pgcli: Dependency needs updating python3-psycopg3 -> python3-psycopg
Package: pgcli Version: 3.5.0-3 Severity: serious python3-psycopg3 does not exist anymore, see #1016031.
Processed: found 1029151 in 8.0.31-1
Processing commands for cont...@bugs.debian.org: > found 1029151 8.0.31-1 Bug #1029151 [src:mysql-8.0] mysql-8.0: CVE-2023-21863 CVE-2023-21867 CVE-2023-21868 CVE-2023-21869 CVE-2023-21870 CVE-2023-21871 CVE-2023-21873 CVE-2023-21875 CVE-2023-21876 CVE-2023-21877 CVE-2023-21878 CVE-2023-21879 CVE-2023-21880 CVE-2023-21881 CVE-2023-21882 CVE-2023-21883 CVE-2023-21887 Marked as found in versions mysql-8.0/8.0.31-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026499: rows: diff for NMU version 0.4.1-5.1
On Wed, Jan 18, 2023 at 10:44:23PM -0300, Antonio Terceiro wrote: > On Wed, Jan 18, 2023 at 06:27:59PM +0200, Adrian Bunk wrote: > > Control: tags 1026499 + patch > > Control: tags 1026499 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for rows (versioned as 0.4.1-5.1) and uploaded > > it to DELAYED/14. Please feel free to tell me if I should cancel it. > > I'm about to upload a new upstream snapshot that will close this bug, so > I think you can cancel it. Thanks for looking into the package, though. Thanks, I've canceled mine. cu Adrian
Processed: affects 1028904, affects 1028904
Processing commands for cont...@bugs.debian.org: > affects 1028904 src:pikepdf Bug #1028904 [src:pillow] pillow: Lost tiff support after binNMU with tiff 4.5.0 Added indication that 1028904 affects src:pikepdf > affects 1028904 - satpy Bug #1028904 [src:pillow] pillow: Lost tiff support after binNMU with tiff 4.5.0 Removed indication that 1028904 affects satpy > thanks Stopping processing here. Please contact me if you need assistance. -- 1028904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024155: marked as done (libngs-c++-dev: missing Breaks+Replaces: libncbi-vdb-dev (<< 3), libngs-sdk-dev (<< 3))
Your message dated Thu, 19 Jan 2023 03:07:05 +
with message-id
and subject line Bug#1024155: fixed in sra-sdk 3.0.3+dfsg-1
has caused the Debian Bug report #1024155,
regarding libngs-c++-dev: missing Breaks+Replaces: libncbi-vdb-dev (<< 3),
libngs-sdk-dev (<< 3)
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.)
--
1024155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libngs-c++-dev
Version: 3.0.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libngs-c++-dev_3.0.0+dfsg-1_amd64.deb ...
Unpacking libngs-c++-dev:amd64 (3.0.0+dfsg-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libngs-c++-dev_3.0.0+dfsg-1_amd64.deb (--unpack):
trying to overwrite '/usr/include/ngs/Alignment.hpp', which is also in
package libngs-sdk-dev:amd64 2.11.2-4
Errors were encountered while processing:
/var/cache/apt/archives/libngs-c++-dev_3.0.0+dfsg-1_amd64.deb
Preparing to unpack .../libngs-c++-dev_3.0.0+dfsg-1_amd64.deb ...
Unpacking libngs-c++-dev:amd64 (3.0.0+dfsg-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libngs-c++-dev_3.0.0+dfsg-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libncbi-ngs-c++.a', which is
also in package libncbi-vdb-dev:amd64 2.11.2+dfsg-6
Errors were encountered while processing:
/var/cache/apt/archives/libngs-c++-dev_3.0.0+dfsg-1_amd64.deb
cheers,
Andreas
libncbi-vdb-dev=2.11.2+dfsg-6_libngs-c++-dev=3.0.0+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sra-sdk
Source-Version: 3.0.3+dfsg-1
Done: Aaron M. Ucko
We believe that the bug you reported is fixed in the latest version of
sra-sdk, 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 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aaron M. Ucko (supplier of updated sra-sdk 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, 18 Jan 2023 21:42:39 -0500
Source: sra-sdk
Architecture: source
Version: 3.0.3+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Aaron M. Ucko
Closes: 1024155 1025278
Changes:
sra-sdk (3.0.3+dfsg-1) experimental; urgency=medium
.
[ Andreas Tille ]
* Breaks+Replaces: libncbi-vdb-dev (<< 3), libngs-sdk-dev (<< 3)
Closes: #1024155
.
[ Aaron M. Ucko ]
* New upstream version.
* .gitignore:
- Unhardcode architecture name in build tree (obj-*).
- Ignore build results under ngs/ngs-python (dist, ngs.egg-info).
* debian/{control,salsa-ci.yml}: Build against libncbi-vdb-dev 3.0.1+.
* debian/copyright: Account for layout changes as of 3.0.1 and drop
references to content removed upstream, both in Files-Excluded and in
special cases.
* debian/patches: Update for 3.0.1+; in particular, account for layout
changes and better support for using system libraries.
* debian/rules:
- Correctly accommodate multiple supported Python versions. (I'd
insufficiently adapted ncbi-ngs's relevant logic.)
- Account for layout changes and CMAKE_INSTALL_LIBDIR support (with
the latter yielding multiarch paths).
- Clean up newly generated files under ngs/ngs-python.
* debian/{rules,sra-toolkit.install}: Move sratools and *-orig to a new
/usr/lib/sra-toolkit directory; repoint symlinks accordingly.
(Closes: #1025278.)
* Standards-Version: 4.6.2 (routine-upd
Bug#1026499: marked as done (rows: FTBFS: AssertionError: Lists differ: [] != ['iso', '8859'])
Your message dated Thu, 19 Jan 2023 02:38:10 + with message-id and subject line Bug#1026499: fixed in rows 0.4.2~0-1 has caused the Debian Bug report #1026499, regarding rows: FTBFS: AssertionError: Lists differ: [] != ['iso', '8859'] 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.) -- 1026499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rows Version: 0.4.1-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.10 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.10_rows/build/rows > copying rows/__init__.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows > copying rows/cli.py -> /<>/.pybuild/cpython3_3.10_rows/build/rows > copying rows/localization.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows > copying rows/table.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows > copying rows/operations.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows > copying rows/fields.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows > copying rows/utils.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows > creating /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/plugin_html.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/__init__.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/ods.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/plugin_json.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/xls.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/xpath.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/dicts.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/postgresql.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/txt.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/sqlite.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/plugin_pdf.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/plugin_parquet.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/plugin_csv.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/utils.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins > copying rows/plugins/xlsx.py -> > /<>/.pybuild/cpython3_3.10_rows/build/rows/plugins >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:240: cd /<>/.pybuild/cpython3_3.10_rows/build; > python3.10 -m nose -v --ignore-files=_parquet.py > --ignore-files=tests_table.py --ignore-files=tests_plugin_pdf.py > --ignore-files=tests_plugin_postgresql.py > test_detect_types (tests.tests_fields.FieldUtilsTestCase) ... ok > test_detect_types_binary (tests.tests_fields.FieldUtilsTestCase) ... ok > test_detect_types_different_number_of_fields > (tests.tests_fields.FieldUtilsTestCase) ... ok > test_detect_types_no_sample (tests.tests_fields.FieldUtilsTestCase) ... ok > test_precedence (tests.tests_fields.FieldUtilsTestCase) ... ok > test_as_string (tests.tests_fields.FieldsFunctionsTestCase) ... ok > test_get_items (tests.tests_fields.FieldsFunctionsTestCase) ... ok > test_is_null (tests.tests_fields.FieldsFunctionsTestCase) ... ok > test_BinaryField (tests.tests_fields.FieldsTestCase) ... ok > test_BoolField (tests.tests_fields.FieldsTestCase) ... ok > test_DateField (tests.tests_fields.FieldsTestCase) ... ok > test_DatetimeField (tests.tests_fields.FieldsTestCase) ... ok > test_DecimalField (tests.tests_fields.FieldsTestCase) ... ok > test_EmailField (tests.tests_fields.FieldsTestCase) ... ok > test_Field (tests.tests_fields.FieldsTestCase) ... ok > test_FloatField (tests.tests_fields.FieldsTestCase) ... ok > test_IntegerField (tests.tests_fields.FieldsTestCase) ... ok > test_JSONField (tests.tests_fields.FieldsTestCase) ... ok >
Bug#1026499: rows: diff for NMU version 0.4.1-5.1
On Wed, Jan 18, 2023 at 06:27:59PM +0200, Adrian Bunk wrote: > Control: tags 1026499 + patch > Control: tags 1026499 + pending > > Dear maintainer, > > I've prepared an NMU for rows (versioned as 0.4.1-5.1) and uploaded > it to DELAYED/14. Please feel free to tell me if I should cancel it. I'm about to upload a new upstream snapshot that will close this bug, so I think you can cancel it. Thanks for looking into the package, though. signature.asc Description: PGP signature
Bug#1027143: openimageio: CVE-2022-43592 CVE-2022-43593 CVE-2022-43594 CVE-2022-43595 CVE-2022-43596 CVE-2022-43597 CVE-2022-43598 CVE-2022-43599 CVE-2022-43600 CVE-2022-43601 CVE-2022-43602 CVE-2022-
The direct reverse dependencies all build fine with 2.4.7.1+dfsg-1, so we can ask for the transition.
Bug#1027338: marked as done (ruby-has-scope: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such file -- moc
Your message dated Wed, 18 Jan 2023 23:23:33 + with message-id and subject line Bug#1027338: fixed in ruby-has-scope 0.8.0-1 has caused the Debian Bug report #1027338, regarding ruby-has-scope: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such file -- mocha/mini_test (LoadError) 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.) -- 1027338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-has-scope Version: 0.7.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221230 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is likely due to the upgrade of mocha. See https://lists.debian.org/debian-ruby/2022/12/msg00064.html Relevant part (hopefully): > :85:in > `require': cannot load such file -- mocha/mini_test (LoadError) > from > :85:in > `require' > from /<>/test/test_helper.rb:5:in `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/has_scope_test.rb:1:in `' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in > `block in ' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `select' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `' > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/has_scope_test.rb" "test/test_helper.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2022/12/30/ruby-has-scope_0.7.2-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221230;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221230&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: ruby-has-scope Source-Version: 0.8.0-1 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-has-scope, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-has-scope 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, 18 Jan 2023 23:51:05 +0100 Source: ruby-has-scope Architecture: source Version: 0.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 1027338 Changes: ruby-has-scope (0.8.0-1) unstable; urgency=medium . * Team upload . [ Debian Janitor ] * Update watch file format version to 4. * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on ruby-actionpack and ruby-activesupport. + ruby-has-scope: Drop versioned constraint on ruby-actionpack and ruby-activesupport in Depends. . [ Cédric Boutillier ] * New upstream version 0.8.0 * update .gitattributes * use gem install layout * Refresh control file (Standards-Version to 4.6.2) * Drop tests-rails-6.patch, not needed any more * Add patch to work with mocha >= 1.10 (Closes: #1027338) Checksums-Sha1: 5f5
Bug#1029179: relion-cuda: rebuild for libtiff6 transition
Source: relion-cuda Version: 3.1.3-1 Severity: serious Tag: sid bookworm relion-cuda requires a rebuild for the libtiff5 -> libtiff6 transition. Cheers -- Sebastian Ramacher
Bug#1029127: context: manual has non-free files
Am 18.01.2023 um 20:29 teilte Bastian Germann mit: Am 18.01.23 um 20:20 schrieb Hilmar Preuße: Am 18.01.2023 um 11:52 teilte Bastian Germann mit: Am 18.01.23 um 11:21 schrieb Hilmar Preuße: Hi, Do you have a list of these files or do you know how to generate one? grep -r licence=cc-by-nc-sa This gives a lot of TeX input files should I remove them? Yes. But please make the repack reproducible. The easiest way is to convert the debian/copyright file to the machine-readable format and use Files-Excluded. As we don't get tar balls from upstream, the most easy way would be to edit the make-orig-tar and exclude the files there. I'll try to look into that further ASAP. Hilmar -- sigfault
Bug#1029178: vtk-dicom: autopkgtest failure
Source: vtk-dicom Version: 0.8.14-3 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/v/vtk-dicom/30492694/log.gz autopkgtest [23:14:01]: test autodep8-python3: set -e ; for py in $(py3versions -d 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import vtkdicom; print(vtkdicom)" ; done autopkgtest [23:14:01]: test autodep8-python3: [--- Testing with python3.10: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/vtkdicom/__init__.py", line 1, in from .vtkDICOM import * ModuleNotFoundError: No module named 'vtkdicom.vtkDICOM' Cheers -- Sebastian Ramacher
Bug#1027058: marked as done (ruby-github-api: FTBFS with ruby-hashie 5.0.0-1: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dep
Your message dated Wed, 18 Jan 2023 22:22:37 + with message-id and subject line Bug#1027058: fixed in ruby-github-api 0.19.0-2 has caused the Debian Bug report #1027058, regarding ruby-github-api: FTBFS with ruby-hashie 5.0.0-1: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'hashie' (>= 3.5.2, ~> 3.5) among 104 total gem(s) (Gem::MissingSpecError) 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.) -- 1027058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-github-api Version: 0.19.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-hashie-5.0.0 Hi, After updating ruby-hashie to 5.0.0-1, ruby-github-api fails to build. Relevant part of the build log (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block > in activate_dependencies': Could not find 'hashie' (>= 3.5.2, ~> 3.5) among > 104 total gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-github-api/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > at: > /<>/debian/ruby-github-api/usr/share/rubygems-integration/all/specifications/github_api-0.19.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'hashie' (>= 3.5.2, ~> 3.5) - did find: [hashie-5.0.0] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-github-api/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > abbrev (default: 0.1.0) > addressable (2.8.0) > atomic (1.1.16) > base64 (default: 0.1.1) > benchmark (default: 0.2.0) > bigdecimal (default: 3.1.1) > bundler (default: 2.3.7) > cgi (default: 0.3.1) > csv (default: 3.2.2) > date (default: 3.2.2) > debug (1.4.0) > delegate (default: 0.2.0) > descendants_tracker (0.0.4) > did_you_mean (default: 1.6.1) > digest (default: 3.1.0) > drb (default: 2.1.0) > english (default: 0.7.1) > erb (default: 2.2.3) > error_highlight (default: 0.3.0) > etc (default: 1.3.0) > faraday (1.1.0) > fcntl (default: 1.0.1) > fiddle (default: 1.1.0) > fileutils (default: 1.6.0) > find (default: 0.1.1) > forwardable (default: 1.3.2) > getoptlong (default: 0.1.1) > hashie (5.0.0) > io-console (default: 0.5.11) > io-nonblock (default: 0.1.0) > io-wait (default: 0.2.1) > ipaddr (default: 1.2.4) > irb (default: 1.4.1) > json (default: 2.6.1) > jwt (2.5.0) > logger (default: 1.5.0) > matrix (0.4.2) > minitest (5.15.0) > multi_json (1.14.1) > multi_xml (0.6.0) > multipart-post (2.0.0) > mutex_m (default: 0.1.1) > net-ftp (0
Bug#1028766: marked as done (zutty: FTBFS: ValueError: invalid mode: 'rUb')
Your message dated Wed, 18 Jan 2023 21:59:29 + with message-id and subject line Bug#1028766: fixed in zutty 0.13.4.20230114+dfsg1-1 has caused the Debian Bug report #1028766, regarding zutty: FTBFS: ValueError: invalid mode: 'rUb' 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.) -- 1028766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zutty Version: 0.13.2.20221029.103432+dfsg1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 ./waf configure --debug --prefix=/usr > Waf: The wscript in '/<>' is unreadable > Traceback (most recent call last): > File "/<>/waflib/Scripting.py", line 101, in waf_entry_point > > set_main_module(os.path.normpath(os.path.join(Context.run_dir,Context.WSCRIPT_FILE))) > File "/<>/waflib/Scripting.py", line 141, in set_main_module > Context.g_module=Context.load_module(file_path) > ^^ > File "/<>/waflib/Context.py", line 354, in load_module > code=Utils.readf(path,m='rU',encoding=encoding) > ^^ > File "/<>/waflib/Utils.py", line 141, in readf > with open(fname,m)as f: > ^ > ValueError: invalid mode: 'rUb' > make[1]: *** [debian/rules:33: override_dh_auto_configure] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/01/13/zutty_0.13.2.20221029.103432+dfsg1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: zutty Source-Version: 0.13.4.20230114+dfsg1-1 Done: Ricardo Mones We believe that the bug you reported is fixed in the latest version of zutty, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ricardo Mones (supplier of updated zutty 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, 18 Jan 2023 22:06:01 +0100 Source: zutty Architecture: source Version: 0.13.4.20230114+dfsg1-1 Distribution: unstable Urgency: high Maintainer: Ricardo Mones Changed-By: Ricardo Mones Closes: 1028766 Changes: zutty (0.13.4.20230114+dfsg1-1) unstable; urgency=high . * New upstream version - Includes WAF upgrade to 2.0.25 (Closes: #1028766) * Drop time from repackaged version * Update Standards-Version to 4.6.2, no other changes * Raised urgency because of RC bug Checksums-Sha1: 48f565165397222d218a0698bb8be7dc15f2518e 1968 zutty_0.13.4.20230114+dfsg1-1.dsc b18febda550e8a7b071092d03ebf247d1a135cf4 302460 zutty_0.13.4.20230114+dfsg1.orig.tar.xz cfe9ee0bc68ce8cf3ca7bfab9769a090c490df8e 6096 zutty_0.13.4.20230114+dfsg1-1.debian.tar.xz 9354caa2070e2047b1f96a44d000c32c968b8b55 9696 zutty_0.13.4.20230114+dfsg1-1_amd64.buildinfo Checksums-Sha256: d8aad669b5f97045aab6d91da4f5261a345af1ce348392308ea4775ff05dbd41 1968 zutty_0.13.4.20230114+dfsg1-1.dsc ba6b60d584f80204a7c74984071f3a5d9bb42e00c070e0f960153eb04b9d2f69 302460 zutty_0.13.4.20230114+dfsg1.orig.tar.xz dc3e91b32ba734fa0aa13ce10bb24275587b83a1aa64400f939151c369cfd15b 6096 zutty_0.13.
Processed: Re: Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Processing control commands: > severity -1 grave Bug #1028638 [libproxy1v5] libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call Severity set to 'grave' from 'normal' -- 1028638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026803: marked as done (nanopb: Missing dependency on python3-pkg-resources)
Your message dated Wed, 18 Jan 2023 21:56:01 + with message-id and subject line Bug#1026803: fixed in nanopb 0.4.7-2 has caused the Debian Bug report #1026803, regarding nanopb: Missing dependency on python3-pkg-resources 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.) -- 1026803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: chiaki Version: 2.1.0-1.1 Severity: serious Tags: ftbfs patch Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: i...@hack3r.moe Dear maintainer(s), chiaki failed to build due to Python module `pkg_resources` not found: ``` [ 4%] Generating takion.pb.c, takion.pb.h cd /<>/obj-riscv64-linux-gnu/lib/protobuf && /usr/bin/python3 /usr/bin/nanopb_generator.py /<>/obj-riscv64-linux-gnu/lib/protobuf/takion.pb Traceback (most recent call last): File "/usr/bin/nanopb_generator.py", line 53, in import proto File "/usr/lib/python3/dist-packages/proto/__init__.py", line 10, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' make[3]: *** [lib/protobuf/CMakeFiles/chiaki-pb.dir/build.make:77: lib/protobuf/takion.pb.c] Error 1 make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:199: lib/protobuf/CMakeFiles/chiaki-pb.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs ``` Full buildd log: https://buildd.debian.org/status/fetch.php?pkg=chiaki&arch=riscv64&ver=2.1.0-1.1%2Bb3&stamp=167159&raw=0 I've included a patch that adds python3-setuptools to d/control, fixing FTBFS. If more help is needed, please let me know. Cheers, Eric --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Bartosz Fenski -Build-Depends: debhelper-compat (= 13), cmake, pkg-config, libopus-dev, qtmultimedia5-dev, libqt5svg5-dev, libsdl2-dev, libavcodec-dev, libswscale-dev, libjerasure-dev, libnanopb-dev, libssl-dev, protobuf-compiler, python3-protobuf, libevdev-dev, libudev-dev, libqt5opengl5-dev, python3-dev, libgl1-mesa-dev, imagemagick, librsvg2-bin, libpthread-stubs0-dev, libpthreadpool-dev, nanopb +Build-Depends: debhelper-compat (= 13), cmake, pkg-config, libopus-dev, qtmultimedia5-dev, libqt5svg5-dev, libsdl2-dev, libavcodec-dev, libswscale-dev, libjerasure-dev, libnanopb-dev, libssl-dev, protobuf-compiler, python3-protobuf, libevdev-dev, libudev-dev, libqt5opengl5-dev, python3-dev, libgl1-mesa-dev, imagemagick, librsvg2-bin, libpthread-stubs0-dev, libpthreadpool-dev, nanopb, python3-setuptools Standards-Version: 4.5.1 Homepage: https://git.sr.ht/~thestr4ng3r/chiaki Rules-Requires-Root: no --- End Message --- --- Begin Message --- Source: nanopb Source-Version: 0.4.7-2 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of nanopb, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated nanopb 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, 18 Jan 2023 21:00:33 +0100 Source: nanopb Architecture: source Version: 0.4.7-2 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1026803 Changes: nanopb (0.4.7-2) unstable; urgency=medium . * Add python3-pkg-resources as dependency (closes: #1026803). Checksums-Sha1: d352022e00109e8e6548c7e7027b8caac7cf2fd4 1839 nanopb_0.4.7-2.dsc 148757a7a29eaaf0b12ca6bae758801ce3c33e74 4908 nanopb_0.4.7-2.debian.tar.xz Checksums-Sha256: 49027ea6f5e16fdc740868833346b6f073485ac44bcdcfa92069f43563eedbe7 1839 nanopb_0.4.7-2.dsc c90421efbcc82316f4004849fa0ec36b028a024730f0eb3b66b71642b129c41e 4908 nanopb_0.4.7-2.debian.tar.xz Files: f4f8e12672c42fc24cd9d7a98b6c949b 1839 devel optional nanopb_0.4.7-2.dsc f564ec6f55bacc242a4c6279d77942cd 4908 devel optional nanopb_0.4.7-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmPIWHUACgkQ3OMQ54ZM yL+9OB
Bug#1027058: marked as pending in ruby-github-api
Control: tag -1 pending Hello, Bug #1027058 in ruby-github-api 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/ruby-team/ruby-github-api/-/commit/c61b5d3cf23b2e0482257760f16f5721a007ac38 Fix version of ruby-hashie in gemspecs (Closes: #1027058) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027058
Processed: Bug#1027058 marked as pending in ruby-github-api
Processing control commands: > tag -1 pending Bug #1027058 [src:ruby-github-api] ruby-github-api: FTBFS with ruby-hashie 5.0.0-1: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'hashie' (>= 3.5.2, ~> 3.5) among 104 total gem(s) (Gem::MissingSpecError) Added tag(s) pending. -- 1027058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1027025 with 1026825
Processing commands for cont...@bugs.debian.org:
> block 1027025 with 1026825
Bug #1027025 {Done: Michael Banck } [src:psi4] psi4: FTBFS
with Python 3.11 as default version
1027025 was not blocked by any bugs.
1027025 was not blocking any bugs.
Added blocking bug(s) of 1027025: 1026825
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1027192
Processing commands for cont...@bugs.debian.org: > tags 1027192 + ftbfs Bug #1027192 [src:binoculars] binoculars: autopkgtest fail with numpy/1.24.1 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1020195
Processing commands for cont...@bugs.debian.org: > tags 1020195 + bookworm Bug #1020195 [src:elisp-bug-hunter] elisp-bug-hunter: FTBFS: make: *** [debian/rules:4: binary] Error 25 Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1020195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029174: dhcpcd-base: Brakes networking completely
Package: dhcpcd-base
Version: 9.4.1-13
Severity: grave
Justification: renders package unusable
When this version is installed, all networking is broken, e.g.
root@twentytwo:~# LC_ALL=C ping lwn.net
ping: lwn.net: Temporary failure in name resolution
I cannot access *any* outside resource. No IP, no ssh, no ping, ..
Additionally, comands involving network state take several minutes,
i.e. running into timeouts. E.g.
systemctl restart networking
Or shutdown takes several minutes (for each interface) before
completion.
If I strace such a command, I see:
access("/run/network/ifstate.enp3s0", R_OK) = 0
openat(AT_FDCWD, "/run/network/ifstate.enp3s0",
O_RDWR|O_CREAT|O_APPEND|O_CLOEXEC, 0666) = 3
fcntl(3, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = -1
EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
write(2, "ifdown: ", 8ifdown: ) = 8
write(2, "waiting for lock on /run/network"..., 47waiting for lock on
/run/network/ifstate.enp3s0) = 47
write(2, "\n", 1
) = 1
fcntl(3, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}
And there it hangs. (I did not search if this is the only place for
hangs, but it was the first).
Downgrading to 9.4.1-11 fixes the problem, i.e. the machine behaves
normally after reboot.
This is reproducible, i.e. upgrading to -13 and rebooting and the
broken network is back; downgrading and rebooting and the network is
fine again.
Please tell me which data you need to further boil this down and I can
provide it.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dhcpcd-base depends on:
ii adduser 3.130
ii libc6 2.36-8
ii libudev1 252.4-1
dhcpcd-base recommends no packages.
dhcpcd-base suggests no packages.
-- no debconf information
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
Bug#1027900: marked as done (parole 4.16.0-2 does not start)
Your message dated Wed, 18 Jan 2023 20:56:34 + with message-id and subject line Bug#1027900: fixed in parole 4.16.0-3 has caused the Debian Bug report #1027900, regarding parole 4.16.0-2 does not start 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.) -- 1027900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parole Version: 4.16.0-2 Severity: normal X-Debbugs-Cc: serfyod...@yandex.ru Dear Maintainer, parole 4.16.0-2 when running in the terminal emulator outputs : free(): invalid pointer Emergency stop parole 4.16.0-1 is up and running. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages parole depends on: ii gstreamer1.0-alsa [gstreamer1.0-audiosink] 1.20.4-1 ii gstreamer1.0-libav 1.20.3-1+b1 ii gstreamer1.0-plugins-bad [gstreamer1.0-audiosink] 1.20.4-1+b1 ii gstreamer1.0-plugins-base 1.20.4-1 ii gstreamer1.0-plugins-good [gstreamer1.0-audiosink] 1.20.3-1+b1 ii gstreamer1.0-x 1.20.4-1 ii libc6 2.36-7 ii libcairo2 1.16.0-7 ii libdbus-1-3 1.14.4-1 ii libdbus-glib-1-20.112-3 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 ii libglib2.0-02.74.4-1 ii libgstreamer-plugins-base1.0-0 1.20.4-1 ii libgstreamer1.0-0 1.20.4-1 ii libgtk-3-0 3.24.36-1 ii libnotify4 0.8.1-1 ii libtagc01.13-1 ii libx11-62:1.8.3-3 ii libxfce4ui-2-0 4.18.0-1 ii libxfce4util7 4.18.0-1 ii libxfconf-0-3 4.18.0-1 parole recommends no packages. Versions of packages parole suggests: ii gstreamer1.0-plugins-bad 1.20.4-1+b1 ii gstreamer1.0-plugins-ugly 1.20.3-1 -- no debconf information --- End Message --- --- Begin Message --- Source: parole Source-Version: 4.16.0-3 Done: Yves-Alexis Perez We believe that the bug you reported is fixed in the latest version of parole, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yves-Alexis Perez (supplier of updated parole 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, 18 Jan 2023 20:30:33 +0100 Source: parole Architecture: source Version: 4.16.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Xfce Maintainers Changed-By: Yves-Alexis Perez Closes: 1027900 Changes: parole (4.16.0-3) unstable; urgency=medium . * d/p/0002-build-Bump-GLib-minimum-required-to-2.38 added (Closes: #1027900) * d/control: update standards version Checksums-Sha1: 64152ac1aa251170a613f2d0918bb41b734f8a24 1896 parole_4.16.0-3.dsc fac9cbf2516de04c765cc7e364e1ca874dcddb57 6992 parole_4.16.0-3.debian.tar.xz 83537cee7dfc04d0315233f52081b7b182625436 18046 parole_4.16.0-3_amd64.buildinfo Checksums-Sha256: 7a823dd531e44885971b9df9bbc6d9e7ab18face25f5f62116deb04e263c2f8a 1896 parole_4.16.0-3.dsc 620911b2dad9b4d969ddf3aa401322d45712aff59575d7eb3429a81f65d4b2c4 6992 parole_4.16.0-3.debian.tar.xz e0ab5fe63e94730d79eb7a3980ff45ade7308d5fc710189dc0d7c53ee94d3314 18046 parole_4.16.0-3_amd64.buildinfo Files: fd6d39256894d5cfe20976b6b21206f1 1896 xfce optional parole_4.16.0-3.dsc 730af9c4cdf15179abbad89cc7134623 6992 xfce optional parole_4.
Bug#913916: grub-efi-amd64: UEFI boot option removed after update to grub2 2.02~beta3-5+deb9u1
Hi,
I observe the very same issue on a Dell Latitude 3590, but it only started to
affect the laptop running Bullseye all of a sudden after one of many
reinstallations.
19 other laptops (same model, same date of purchase, same hardware) with
exactly the same installation (preseed + configuration management via Puppet)
are (as of yet) unaffected.
I believe the described issue matches this one observed on various Dell laptops:
https://github.com/rhboot/efibootmgr/issues/86
To be more explicit, using:
efibootmgr -c -e 3 -v -L debian -l "\EFI\debian\shimx64.efi"
creates a working boot entry, using an EDD 3.0 path similar to the one created if an
entry is created via the UEFI firmware "by hand".
Using:
efibootmgr -c -v -L debian -l "\EFI\debian\shimx64.efi"
creates a boot entry invisible in the UEFI firmware.
This matches the observation of Gábor Gombás ("Debian" in the "efibootmgr -v" output for
an EDD 3.0 entry vs. "debian", an EDD 1.0 entry).
As of the fix for #891434 , grub-install does not leverage efibootmgr anymore,
but implements part of its functionality to reduce writes (and always seems to
use EDD 1.0).
From my observation and the one in the linked GitHub issue, I deduce the
following:
- There's actually a firmware bug on these Dell laptops (and maybe more
devices), causing the UEFI firmware to start ignoring EDD 1.0 entries after
some event (a number of write cycles? some corruption?).
- EDD 3.0 entries still work.
- Since grub-install always uses EDD 1.0 entries, it overwrites the entry with
an EDD 1.0 entry during each reinstall, causing such devices not to be bootable
anymore.
Workarounds appear to be:
- Create an EDD 3.0 entry (either via firmware, or via efibootmgr), name it
differently and inject it first in the boot order.
- Use --force-extra-removable to install to the fallback loader path (if this
is the only bootloader on the system).
Notably, the workaround described by ArchLinux at:
https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#Boot_entries_created_with_efibootmgr_fail_to_show_up_in_UEFI
does not work on Debian, since efibootmgr is not called by grub-install.
While the GitHub issue describes a user who could make EDD 1.0 entries work
again on an affected system by purging all entries, in my tests neither that
nor an UEFI update nor loading of firmware defaults nor a full RTC reset could
make the firmware accept EDD 1.0 entries again on the affected device.
A potential solution could be to probe whether the firmware accepts EDD 3.0
entries and preferrably create those over EDD 1.0, or allow to configure this.
Cheers and hope this helps,
Oliver
Processed: This bug is also in the version in testing
Processing commands for cont...@bugs.debian.org: > found 1029167 78.15.0-5 Bug #1029167 [src:mozjs78] mozjs78: Fails to build on armhf and armel Marked as found in versions mozjs78/78.15.0-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028622: marked as done (sphinx-prompt: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1)
Your message dated Wed, 18 Jan 2023 19:44:19 +
with message-id
and subject line Bug#1028622: fixed in sphinx-prompt 1.5.0-3
has caused the Debian Bug report #1028622,
regarding sphinx-prompt: autopkgtest is failng after updating pygments to
2.14.0+dfsg-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.)
--
1028622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx-prompt
Version: 1.5.0-2
Severity: serious
Dear Maintainer,
after the upload of pygments 2.14.0+dfsg-1 your package is failung while
running the autopkgtest.
Some of the failing parts are:
autopkgtest [03:25:03]: test unittests: [---
= test session starts ==
platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.k5oqcgm7/downtmp/build.h5g/src
collected 12 items
../build.h5g/src/tests/test_sphinx_prompt.py .FF...F.[100%]
=== FAILURES ===
_ test[arguments1-options1-content1-\nspan.prompt1:before {\n content: "$ ";\n}\none line\n] _
arguments = ['bash'], options = {'language': 'bash'}, content = ['one line']
expected = '\nspan.prompt1:before {\n
content: "$ ";\n}\none
line\n'
@pytest.mark.parametrize("arguments, options, content, expected", testdata)
def test(arguments, options, content, expected):
sphinx_prompt._cache.next_index = 1
sphinx_prompt._cache.prompts.clear()
stream = StringIO()
reporter = docutils.utils.Reporter("test data", 2, 4, stream, 1)
statemachine = docutils.statemachine.StateMachine([], None)
setattr(statemachine, "reporter", reporter)
directive = sphinx_prompt.PromptDirective(
"prompt", arguments, options, content, 0, 0, "", None, statemachine
)
result = directive.run()
> assert result[0].astext() == expected
E assert ''
E Skipping 159 identical leading characters in diff, use -v to show
E - ompt1">one line
E + ompt1">one line
E
../build.h5g/src/tests/test_sphinx_prompt.py:165: AssertionError
_ test[arguments2-options2-content2-\nspan.prompt1:before {\n content: "$ ";\n}\none line\n] _
arguments = [], options = {'language': 'bash'}, content = ['one line']
expected = '\nspan.prompt1:before {\n
content: "$ ";\n}\none
line\n'
@pytest.mark.parametrize("arguments, options, content, expected", testdata)
def test(arguments, options, content, expected):
sphinx_prompt._cache.next_index = 1
sphinx_prompt._cache.prompts.clear()
stream = StringIO()
reporter = docutils.utils.Reporter("test data", 2, 4, stream, 1)
statemachine = docutils.statemachine.StateMachine([], None)
setattr(statemachine, "reporter", reporter)
directive = sphinx_prompt.PromptDirective(
"prompt", arguments, options, content, 0, 0, "", None, statemachine
)
result = directive.run()
> assert result[0].astext() == expected
E assert ''
E Skipping 159 identical leading characters in diff, use -v to show
E - ompt1">one line
E + ompt1">one line
E
...
It might be enough to pick
https://github.com/sbrunner/sphinx-prompt/commit/f996f7ab96ec63b08e27f96559b759143ccff214
from the upstream git tree to fix the issues.
Regards
Carsten
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: sphinx-prompt
Source-Version: 1.5.0-3
Done: Carsten Schoenert
We believe that the bug you reported is fixed in the latest version of
sphinx-prompt, 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 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Carsten Schoenert (supplier of updated sphinx-prompt
package)
(This message was generated automatically
Processed: This bug is also in bullseye
Processing commands for cont...@bugs.debian.org:
> unarchive 1008318
Bug #1008318 {Done: Laszlo Boszormenyi (GCS) } [nanopb]
nanopb: missing dependency python3-protobuf
Unarchived Bug 1008318
> found 1008318 0.4.4-2
Bug #1008318 {Done: Laszlo Boszormenyi (GCS) } [nanopb]
nanopb: missing dependency python3-protobuf
Marked as found in versions nanopb/0.4.4-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1008318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029167: mozjs78: Fails to build on armhf and armel
On Wed, 18 Jan 2023 at 19:08:22 +, Joshua Peisach wrote: > CJS ported to mozjs78 in October 2020, and Cinnamon is still finishing their > 5.6x releases/making cleanups. > > Considering upstream uses Ubuntu Jammy, mozjs102 isn’t an option unless they > are willing to build it for their main development target. I think Cjs should > rebase for mozjs91, > Especially if mozjs78 is EOL. Firefox 91 (and therefore mozjs91) is already EOL, and has been since September 2022, so porting to mozjs91 doesn't seem like a great solution this year. Even if Cinnamon upstream has a version of Linux Mint that is based on Ubuntu jammy (22.04) as its primary development target, the version of Cinnamon in Ubuntu jammy is constant (5.2.x) and is unlikely to change (not making major changes is part of the point of a LTS distribution); so if Linux Mint wants to provide newer versions of Cinnamon for a jammy-based OS, they already need their own apt repository that provides those packages. Since that repository needs to exist anyway, it would be straightforward for it to also be used to ship updated versions of dependencies where necessary, such as a suitable version of mozjs102 for cjs' benefit. (Of course, that can only happen if someone in Cinnamon/Mint takes responsibility for uploading that version of mozjs102.) smcv
Bug#1025848: marked as done (src:kiwi: unsatisfied build dependency in testing: python3-testinfra)
Your message dated Wed, 18 Jan 2023 21:39:30 +0200 with message-id and subject line python3-testinfra is back in testing has caused the Debian Bug report #1025848, regarding src:kiwi: unsatisfied build dependency in testing: python3-testinfra 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.) -- 1025848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kiwi Version: 9.24.49-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: edos-uninstallable Control: block -1 by 1013872 1021317 1021920 1022530 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 Description: OpenPGP digital signature --- End Message --- --- Begin Message --- python3-testinfra is back in testing. cu Adrian--- End Message ---
Processed: bug 1026747 is forwarded to https://github.com/h2non/pook/pull/85
Processing commands for cont...@bugs.debian.org:
> forwarded 1026747 https://github.com/h2non/pook/pull/85
Bug #1026747 [src:python-pook] python-pook: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/h2non/pook/pull/85'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029167: mozjs78: Fails to build on armhf and armel
On Wed, Jan 18, 2023 at 2:08 PM Joshua Peisach wrote: > CJS ported to mozjs78 in October 2020, and Cinnamon is still finishing their > 5.6x releases/making cleanups. > > Considering upstream uses Ubuntu Jammy, mozjs102 isn’t an option unless they > are willing to build it for their main development target. I think Cjs should > rebase for mozjs91, > Especially if mozjs78 is EOL. Cinnamon upstream is more than welcome to add a backported mozjs* to the list of custom packages they provide. The absence of the latest mozjs on Debian Stable or Ubuntu LTS does not need to be a blocker at all. But I have news: Ubuntu 22.04 LTS now has mozjs102 in jammy-proposed. The intent is to release this as a security update there soon. See https://launchpad.net/bugs/1993214 for more details. If that works well, we may continue to backport new major mozjs releases in the future for Ubuntu LTS. Perhaps for Debian 12 too. Thank you, Jeremy Bicha
Bug#1026803: chiaki: FTBFS (ModuleNotFoundError: No module named 'pkg_resources')
Control: reassign -1 nanopb 0.4.7-1 Control: retitle -1 nanopb: Missing dependency on python3-pkg-resources Control: affects -1 src:chiaki On Wed, Dec 21, 2022 at 11:47:49AM +, Eric Long wrote: >... > cd /<>/obj-riscv64-linux-gnu/lib/protobuf && /usr/bin/python3 > /usr/bin/nanopb_generator.py > /<>/obj-riscv64-linux-gnu/lib/protobuf/takion.pb > Traceback (most recent call last): > File "/usr/bin/nanopb_generator.py", line 53, in > import proto > File "/usr/lib/python3/dist-packages/proto/__init__.py", line 10, in > > import pkg_resources > ModuleNotFoundError: No module named 'pkg_resources' >... This is a bug in nanopb that should be fixed there. cu Adrian
Processed: Re: Bug#1026803: chiaki: FTBFS (ModuleNotFoundError: No module named 'pkg_resources')
Processing control commands: > reassign -1 nanopb 0.4.7-1 Bug #1026803 [src:chiaki] chiaki: FTBFS (ModuleNotFoundError: No module named 'pkg_resources') Bug reassigned from package 'src:chiaki' to 'nanopb'. No longer marked as found in versions chiaki/2.1.0-1.1. Ignoring request to alter fixed versions of bug #1026803 to the same values previously set Bug #1026803 [nanopb] chiaki: FTBFS (ModuleNotFoundError: No module named 'pkg_resources') Marked as found in versions nanopb/0.4.7-1. > retitle -1 nanopb: Missing dependency on python3-pkg-resources Bug #1026803 [nanopb] chiaki: FTBFS (ModuleNotFoundError: No module named 'pkg_resources') Changed Bug title to 'nanopb: Missing dependency on python3-pkg-resources' from 'chiaki: FTBFS (ModuleNotFoundError: No module named 'pkg_resources')'. > affects -1 src:chiaki Bug #1026803 [nanopb] nanopb: Missing dependency on python3-pkg-resources Added indication that 1026803 affects src:chiaki -- 1026803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1029154 in 2.30.0-3, tagging 1029155, tagging 1029157, tagging 1029158
Processing commands for cont...@bugs.debian.org: > found 1029154 2.30.0-3 Bug #1029154 [src:swift] swift: CVE-2022-47950 Marked as found in versions swift/2.30.0-3. > tags 1029155 + upstream Bug #1029155 [src:qemu] qemu: CVE-2023-0330 Added tag(s) upstream. > tags 1029157 + upstream Bug #1029157 [src:rust-tokio] rust-tokio: CVE-2023-22466 Added tag(s) upstream. > tags 1029158 + upstream Bug #1029158 [src:rust-bzip2] rust-bzip2: CVE-2023-22895 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029154 1029155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029155 1029157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029157 1029158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029127: context: manual has non-free files
Am 18.01.23 um 20:20 schrieb Hilmar Preuße: Am 18.01.2023 um 11:52 teilte Bastian Germann mit: Am 18.01.23 um 11:21 schrieb Hilmar Preuße: Hi, Do you have a list of these files or do you know how to generate one? grep -r licence=cc-by-nc-sa This gives a lot of TeX input files should I remove them? Yes. But please make the repack reproducible. The easiest way is to convert the debian/copyright file to the machine-readable format and use Files-Excluded.
Bug#1029127: context: manual has non-free files
Am 18.01.2023 um 11:52 teilte Bastian Germann mit: Am 18.01.23 um 11:21 schrieb Hilmar Preuße: Hi, Do you have a list of these files or do you know how to generate one? grep -r licence=cc-by-nc-sa This gives a lot of TeX input files should I remove them? Hilmar -- sigfault
Processed: bug 1026599 is forwarded to https://github.com/kpeeters/cadabra2/commit/217bc21f9fff3de8eeb9ed651b2143a4f9c8a4b6
Processing commands for cont...@bugs.debian.org:
> forwarded 1026599
> https://github.com/kpeeters/cadabra2/commit/217bc21f9fff3de8eeb9ed651b2143a4f9c8a4b6
Bug #1026599 [src:cadabra2] cadabra2: FTBFS: type_caster_base.h:482:26: error:
invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
Set Bug forwarded-to-address to
'https://github.com/kpeeters/cadabra2/commit/217bc21f9fff3de8eeb9ed651b2143a4f9c8a4b6'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 1026650 to golang-github-census-instrumentation-opencensus-proto: Missing build (and runtime?) dependencies on golang-google-protobuf-dev
Processing commands for cont...@bugs.debian.org: > retitle 1026650 golang-github-census-instrumentation-opencensus-proto: > Missing build (and runtime?) dependencies on golang-google-protobuf-dev Bug #1026650 [src:golang-github-census-instrumentation-opencensus-proto] golang-github-census-instrumentation-opencensus-proto: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 25 Changed Bug title to 'golang-github-census-instrumentation-opencensus-proto: Missing build (and runtime?) dependencies on golang-google-protobuf-dev' from 'golang-github-census-instrumentation-opencensus-proto: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 25'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029167: mozjs78: Fails to build on armhf and armel
CJS ported to mozjs78 in October 2020, and Cinnamon is still finishing their 5.6x releases/making cleanups. Considering upstream uses Ubuntu Jammy, mozjs102 isn’t an option unless they are willing to build it for their main development target. I think Cjs should rebase for mozjs91, Especially if mozjs78 is EOL. > On Jan 18, 2023, at 1:59 PM, Jeremy Bicha wrote: > > Source: mozjs78 > Version: 78.15.0-6 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: debian-...@lists.debian.org, c...@packages.debian.org > User: debian-...@lists.debian.org > Usertags: armel armhf > > mozjs78 fails to build on armhf & armel. > > I have little interest in working on this bug myself. I only stumbled > across this bug because I applied a build fix needed by Debian's > switch to Python 3.11. mozjs78 has been End of Life since October 2021 > and is only still in Debian because Cinnamon hasn't switched to > mozjs102 yet. > > By the way, 0ad has an embedded copy of mozjs78 and still builds on > armhf so maybe it includes a fix or a workaround for this build > failure. > > I'm pasting the end of the build log below, but the actual build error > may have been earlier in the log. > > /usr/bin/arm-linux-gnueabihf-g++ -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 > -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -Wall > -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith > -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings > -Wno-invalid-offsetof -Wc++2a-compat -Wduplicated-cond > -Wimplicit-fallthrough -Wunused-function -Wunused-variable > -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations > -Wno-error=array-bounds -Wno-error=coverage-mismatch > -Wno-error=free-nonheap-object -Wno-multistatement-macros > -Wno-error=class-memaccess -Wno-error=deprecated-copy -Wformat > -Wformat-overflow=2 -Wno-noexcept-type -fno-sized-deallocation > -fno-aligned-new -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -fno-rtti > -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno > -pthread -pipe -g -freorder-blocks -O3 -fomit-frame-pointer > -funwind-tables -fPIC -shared -Wl,-z,defs -Wl,--gc-sections > -Wl,-h,libmozjs-78.so -o libmozjs-78.so > /<>/debian/build/js/src/build/libmozjs-78_so.list > -lpthread -Wl,-z,relro -Wl,-z,noexecstack -Wl,-z,text -Wl,-z,relro > -Wl,-z,nocopyreloc -Wl,-Bsymbolic-functions -Wl,--build-id=sha1 > -fstack-protector-strong > -Wl,-rpath-link,/<>/debian/build/dist/bin > -Wl,-rpath-link,/usr/lib > /<>/debian/build/armv7-unknown-linux-gnueabihf/release/libjsrust.a > -Wl,--version-script,symverscript -Wl,-soname,libmozjs-78.so.0 -lm > -lz -lm -ldl > /usr/bin/ld: > /<>/debian/build/js/src/build/../../../config/external/icu/common/rbbi.o: > in function `std::type_info::operator!=(std::type_info const&) const': > /usr/include/c++/12/typeinfo:115: undefined reference to > `std::type_info::operator==(std::type_info const&) const' > /usr/bin/ld: > /<>/debian/build/js/src/build/../../../config/external/icu/common/schriter.o: > in function `std::type_info::operator!=(std::type_info const&) const': > /usr/include/c++/12/typeinfo:115: undefined reference to > `std::type_info::operator==(std::type_info const&) const' > /usr/bin/ld: > /<>/debian/build/js/src/build/../../../config/external/icu/common/stringtriebuilder.o: > in function > `icu_67::StringTrieBuilder::Node::operator==(icu_67::StringTrieBuilder::Node > const&) const': > ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388: > undefined reference to `std::type_info::operator==(std::type_info > const&) const' > /usr/bin/ld: > ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388: > undefined reference to `std::type_info::operator==(std::type_info > const&) const' > /usr/bin/ld: > ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388: > undefined reference to `std::type_info::operator==(std::type_info > const&) const' > /usr/bin/ld: > /<>/debian/build/js/src/build/../../../config/external/icu/common/stringtriebuilder.o:./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388: > more undefined references to > `std::type_info::operator==(std::type_info const&) const' follow > collect2: error: ld returned 1 exit status > make[4]: *** [/<>/config/rules.mk:608: libmozjs-78.so] Error 1 > make[4]: Leaving directory '/<>/debian/build/js/src/build' > make[3]: *** [/<>/config/recurse.mk:74: > js/src/build/target] Error 2 > make[3]: Leaving directory '/<>/debian/build' > make[2]: *** [/<>/config/recurse.mk:34: compile] Error 2 > make[2]: Leaving directory '/<>/debian/build' > make[1]: *** [/<>/config/rules.mk:392: default] Error 2 > make[1]: Leaving directory '/<>/debian/build' > dh_auto_build: error: cd debian/build && make -j8 returned exit
Bug#1029167: mozjs78: Fails to build on armhf and armel
Source: mozjs78 Version: 78.15.0-6 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org, c...@packages.debian.org User: debian-...@lists.debian.org Usertags: armel armhf mozjs78 fails to build on armhf & armel. I have little interest in working on this bug myself. I only stumbled across this bug because I applied a build fix needed by Debian's switch to Python 3.11. mozjs78 has been End of Life since October 2021 and is only still in Debian because Cinnamon hasn't switched to mozjs102 yet. By the way, 0ad has an embedded copy of mozjs78 and still builds on armhf so maybe it includes a fix or a workaround for this build failure. I'm pasting the end of the build log below, but the actual build error may have been earlier in the log. /usr/bin/arm-linux-gnueabihf-g++ -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings -Wno-invalid-offsetof -Wc++2a-compat -Wduplicated-cond -Wimplicit-fallthrough -Wunused-function -Wunused-variable -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=coverage-mismatch -Wno-error=free-nonheap-object -Wno-multistatement-macros -Wno-error=class-memaccess -Wno-error=deprecated-copy -Wformat -Wformat-overflow=2 -Wno-noexcept-type -fno-sized-deallocation -fno-aligned-new -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -g -freorder-blocks -O3 -fomit-frame-pointer -funwind-tables -fPIC -shared -Wl,-z,defs -Wl,--gc-sections -Wl,-h,libmozjs-78.so -o libmozjs-78.so /<>/debian/build/js/src/build/libmozjs-78_so.list -lpthread -Wl,-z,relro -Wl,-z,noexecstack -Wl,-z,text -Wl,-z,relro -Wl,-z,nocopyreloc -Wl,-Bsymbolic-functions -Wl,--build-id=sha1 -fstack-protector-strong -Wl,-rpath-link,/<>/debian/build/dist/bin -Wl,-rpath-link,/usr/lib /<>/debian/build/armv7-unknown-linux-gnueabihf/release/libjsrust.a -Wl,--version-script,symverscript -Wl,-soname,libmozjs-78.so.0 -lm -lz -lm -ldl /usr/bin/ld: /<>/debian/build/js/src/build/../../../config/external/icu/common/rbbi.o: in function `std::type_info::operator!=(std::type_info const&) const': /usr/include/c++/12/typeinfo:115: undefined reference to `std::type_info::operator==(std::type_info const&) const' /usr/bin/ld: /<>/debian/build/js/src/build/../../../config/external/icu/common/schriter.o: in function `std::type_info::operator!=(std::type_info const&) const': /usr/include/c++/12/typeinfo:115: undefined reference to `std::type_info::operator==(std::type_info const&) const' /usr/bin/ld: /<>/debian/build/js/src/build/../../../config/external/icu/common/stringtriebuilder.o: in function `icu_67::StringTrieBuilder::Node::operator==(icu_67::StringTrieBuilder::Node const&) const': ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388: undefined reference to `std::type_info::operator==(std::type_info const&) const' /usr/bin/ld: ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388: undefined reference to `std::type_info::operator==(std::type_info const&) const' /usr/bin/ld: ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388: undefined reference to `std::type_info::operator==(std::type_info const&) const' /usr/bin/ld: /<>/debian/build/js/src/build/../../../config/external/icu/common/stringtriebuilder.o:./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388: more undefined references to `std::type_info::operator==(std::type_info const&) const' follow collect2: error: ld returned 1 exit status make[4]: *** [/<>/config/rules.mk:608: libmozjs-78.so] Error 1 make[4]: Leaving directory '/<>/debian/build/js/src/build' make[3]: *** [/<>/config/recurse.mk:74: js/src/build/target] Error 2 make[3]: Leaving directory '/<>/debian/build' make[2]: *** [/<>/config/recurse.mk:34: compile] Error 2 make[2]: Leaving directory '/<>/debian/build' make[1]: *** [/<>/config/rules.mk:392: default] Error 2 make[1]: Leaving directory '/<>/debian/build' dh_auto_build: error: cd debian/build && make -j8 returned exit code 2 Thank you, Jeremy Bicha
Processed: block 1026648 with 1027900
Processing commands for cont...@bugs.debian.org:
> block 1026648 with 1027900
Bug #1026648 {Done: Yves-Alexis Perez } [src:parole] parole:
FTBFS: make[1]: *** [debian/rules:22: override_dh_missing] Error 25
1026648 was not blocked by any bugs.
1026648 was not blocking any bugs.
Added blocking bug(s) of 1026648: 1027900
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1026639 is forwarded to https://github.com/mozilla/rhino/issues/462
Processing commands for cont...@bugs.debian.org: > forwarded 1026639 https://github.com/mozilla/rhino/issues/462 Bug #1026639 [librhino-java] librhino-java: IllegalAccessException With OpenJDK 17 Changed Bug forwarded-to-address to 'https://github.com/mozilla/rhino/issues/462' from 'https://github.com/ckeditor/ckbuilder/issues/34'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1026639 is forwarded to https://github.com/ckeditor/ckbuilder/issues/34
Processing commands for cont...@bugs.debian.org: > forwarded 1026639 https://github.com/ckeditor/ckbuilder/issues/34 Bug #1026639 [librhino-java] librhino-java: IllegalAccessException With OpenJDK 17 Set Bug forwarded-to-address to 'https://github.com/ckeditor/ckbuilder/issues/34'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1026639: ckeditor: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_build] Error 1
Processing control commands: > reassign -1 librhino-java 1.7.7.2-3 Bug #1026639 [src:ckeditor] ckeditor: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_build] Error 1 Bug reassigned from package 'src:ckeditor' to 'librhino-java'. No longer marked as found in versions ckeditor/4.19.1+dfsg-1. Ignoring request to alter fixed versions of bug #1026639 to the same values previously set Bug #1026639 [librhino-java] ckeditor: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_build] Error 1 Marked as found in versions rhino/1.7.7.2-3. > retitle -1 librhino-java: IllegalAccessException With OpenJDK 17 Bug #1026639 [librhino-java] ckeditor: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_build] Error 1 Changed Bug title to 'librhino-java: IllegalAccessException With OpenJDK 17' from 'ckeditor: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_build] Error 1'. > affects -1 ckbuilder src:ckeditor Bug #1026639 [librhino-java] librhino-java: IllegalAccessException With OpenJDK 17 Added indication that 1026639 affects ckbuilder and src:ckeditor -- 1026639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026639: ckeditor: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_build] Error 1
Control: reassign -1 librhino-java 1.7.7.2-3 Control: retitle -1 librhino-java: IllegalAccessException With OpenJDK 17 Control: affects -1 ckbuilder src:ckeditor On Tue, Dec 20, 2022 at 06:33:52PM +0100, Lucas Nussbaum wrote: > Source: ckeditor > Version: 4.19.1+dfsg-1 > Severity: serious > Justification: FTBFS >... > > Exception in thread "main" org.mozilla.javascript.WrappedException: Wrapped > > java.lang.IllegalAccessException: class org.mozilla.javascript.MemberBox > > cannot access class sun.java2d.SunGraphics2D (in module java.desktop) > > because module java.desktop does not export sun.java2d to unnamed module > > @614635c2 > > (/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/image.js#282) > > at > > org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1914) > > at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:134) > > at > > org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225) > > at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52) > > at > > ckbuilder.lib.image._c_anonymous_7(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/image.js:282) > > at > > ckbuilder.lib.image.call(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/image.js) > > at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52) > > at > > ckbuilder.lib.image._c_anonymous_4(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/image.js:144) > > at > > ckbuilder.lib.image.call(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/image.js) > > at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52) > > at > > ckbuilder.lib.builder._c_createPluginsSpriteImage_16(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/builder.js:499) > > at > > ckbuilder.lib.builder.call(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/builder.js) > > at > > org.mozilla.javascript.optimizer.OptRuntime.callName0(OptRuntime.java:74) > > at > > ckbuilder.lib.builder._c_anonymous_21(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/builder.js:726) > > at > > ckbuilder.lib.builder.call(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/builder.js) > > at > > org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85) > > at > > ckbuilder.lib.controller._c_anonymous_5(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/controller.js:80) > > at > > ckbuilder.lib.controller.call(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/controller.js) > > at > > org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2697) > > at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:287) > > at > > org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:101) > > at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52) > > at > > ckbuilder.lib.controller._c_anonymous_14(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/controller.js:243) > > at > > ckbuilder.lib.controller.call(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/lib/controller.js) > > at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32) > > at > > ckbuilder.ckbuilder._c_script_0(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/ckbuilder.js:119) > > at > > ckbuilder.ckbuilder.call(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/ckbuilder.js) > > at > > org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:399) > > at > > org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3452) > > at > > ckbuilder.ckbuilder.call(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/ckbuilder.js) > > at > > ckbuilder.ckbuilder.exec(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/ckbuilder.js) > > at > > org.mozilla.javascript.optimizer.OptRuntime$1.run(OptRuntime.java:234) > > at org.mozilla.javascript.Context.call(Context.java:526) > > at org.mozilla.javascript.ContextFactory.call(ContextFactory.java:509) > > at org.mozilla.javascript.optimizer.OptRuntime.main(OptRuntime.java:222) > > at > > ckbuilder.ckbuilder.main(/build/ckbuilder-Vz2B26/ckbuilder-2.4.3+dfsg/src/ckbuilder.js) >... This is a bug in Rhino, fixed in 1.7.14. cu Adrian
Bug#1028443: marked as done (bpython: autopkgtest regressions with python 3.11)
Your message dated Wed, 18 Jan 2023 18:34:27 +
with message-id
and subject line Bug#1028443: fixed in bpython 0.24-1
has caused the Debian Bug report #1028443,
regarding bpython: autopkgtest regressions with python 3.11
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.)
--
1028443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bpython
Version: 0.23-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar
Hi Sebastian,
The bpython package is now failing its autopkgtests in unstable because
/usr/bin/python3 has moved to python 3.11:
[...]
=== FAILURES ===
TestInspection.test_getfuncprops_print
self =
@unittest.skipIf(pypy, "pypy builtin signatures aren't complete")
def test_getfuncprops_print(self):
props = inspection.getfuncprops("print", print)
self.assertEqual(props.func, "print")
self.assertIn("end", props.argspec.kwonly)
self.assertIn("file", props.argspec.kwonly)
self.assertIn("flush", props.argspec.kwonly)
self.assertIn("sep", props.argspec.kwonly)
> self.assertEqual(props.argspec.kwonly_defaults["file"], "sys.stdout")
E AssertionError: None != 'sys.stdout'
[...]
(https://ci.debian.net/data/autopkgtest/testing/amd64/b/bpython/30225354/log.gz)
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: bpython
Source-Version: 0.24-1
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
bpython, 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 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated bpython 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, 18 Jan 2023 19:07:55 +0100
Source: bpython
Architecture: source
Version: 0.24-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Ramacher
Changed-By: Sebastian Ramacher
Closes: 1028443
Changes:
bpython (0.24-1) unstable; urgency=medium
.
* New upstream version 0.24
- Add support for Python 3.11 (Closes: #1028443)
* debian/control: Bump Standards-Version
Checksums-Sha1:
cc1363fdaf6554b9cdc645f0088a01740cfd4e06 2089 bpython_0.24-1.dsc
03324d2a904d651ac3d52a62622104c3de7ec1e5 222879 bpython_0.24.orig.tar.gz
0a0e667a33ffa2824cf26bdfa8528e9086212af1 8692 bpython_0.24-1.debian.tar.xz
Checksums-Sha256:
1eb3558d0fe4d6ec5a37f44393f2e4552f1ae74ee45887e6061297cdb2deac9e 2089
bpython_0.24-1.dsc
98736ffd7a8c48fd2bfb53d898a475f4241bde0b672125706af04d9d08fd3dbd 222879
bpython_0.24.orig.tar.gz
ea36d17896833d8e838c055e1167f964c3a5a95c1c559850de41db935b11abca 8692
bpython_0.24-1.debian.tar.xz
Files:
223b7b1c16d52a71cc957f0277d77c27 2089 python optional bpython_0.24-1.dsc
bb7a556715be0b974436eb0d920769c0 222879 python optional
bpython_0.24.orig.tar.gz
0ae7b509bfc09f115a4b03aab30cbd7e 8692 python optional
bpython_0.24-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmPINfMACgkQafL8UW6n
GZMnexAAguqvyZNOuzujwZ5fXMy8C1jdvWZ/rLVtdD3wbUZm1T6MEJU+Tg1YK6Wo
kWrHqnhzZs96+/U8HqVSIjtPvil+W75L/MF/d10xxd84iojJqPz/iiT6hXRjz66D
iWLwsBqSTro5hS+rOpxuuLyOvh9l8WUl8GDFrFSSMYXccuTrg3B2yGwHFwQtqQ+o
+8kebkpfprq5UrU54xZPRH2Bi0gXL6ov9micunLTpNqOHAQjT+/6gc5KZGz6q5GA
4o65kksbqeaE2uVv3VdrwafVMlEq8hhw4ZVtdxJiQ7RkZUStRActqKpgKvyVl+Aa
sn3dChsQkteE/iqyCpxi/sku0OIWVR79i0WXwJ6CpRs8luDe2JgvDTLQptr2E2It
FJHzfn9CPVjSnc+uVXmb23gt3bckR59qXoBcxndQZqUxn4SApQ6wZeeNmY3Z0Pc2
6kNuuelGHUcVPJarIgkoP9x3AVT9951ypLdH0kn3fukQLXQP9lTu3SoSANyXeZ75
uEBp/QtEtusbET9+Uuah7ndqYp8bX/fkOe6A8wmvs40ySYJpYDI2+l1QlDA454MD
P+alGuCke
Bug#1027143: openimageio: CVE-2022-43592 CVE-2022-43593 CVE-2022-43594 CVE-2022-43595 CVE-2022-43596 CVE-2022-43597 CVE-2022-43598 CVE-2022-43599 CVE-2022-43600 CVE-2022-43601 CVE-2022-43602 CVE-2022-
I have uploaded the latest 2.3 release to unstable and the latest 2.4 release to experimental (NEW). I have not yet updated d/copyright, so that is a TODO for any unstable 2.4 version. Transitions are not allowed anymore but if the reverse deps build fine with the experimental package I suggest to ask the release team for an exception. Else, someone has to grind through all the CVEs and check if they are applicable for 2.3.21. I do not think any volunteer steps up for that.
Processed: forcibly merging 993659 993660
Processing commands for cont...@bugs.debian.org: > forcemerge 993659 993660 Bug #993659 [src:firefox-esr] firefox-esr: FTBFS and embeded copy of code Bug #993660 [src:firefox-esr] firefox-esr: FTBFS and embeded copy of code Removed indication that 993660 affects src:firefox Merged 993659 993660 > thanks Stopping processing here. Please contact me if you need assistance. -- 993659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993659 993660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1026566 1022015
Processing commands for cont...@bugs.debian.org: > forcemerge 1026566 1022015 Bug #1026566 [src:elasticsearch-curator] elasticsearch-curator: FTBFS: TypeError: load() missing 1 required positional argument: 'Loader' Bug #1022015 [src:elasticsearch-curator] elasticsearch-curator: Uses deprecated yaml.load Severity set to 'serious' from 'normal' Added tag(s) ftbfs, bookworm, and sid. Merged 1022015 1026566 > thanks Stopping processing here. Please contact me if you need assistance. -- 1022015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022015 1026566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028691: dask.distributed: FTBFS: unsatisfiable build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc
On Wed, 2023-01-18 at 10:49 +0100, Sebastiaan Couwenberg wrote: > On 1/18/23 08:38, Sebastiaan Couwenberg wrote: > > python-numpy-doc has been dropped from the build dependencies in > > git, > > but the package FTBFS due to test failures. Those might be fixed in > > a > > new upstream release, but that may introduce regressions in its > > rdeps. > To workaround the two failing tests a patch has been added to mark > them > as xfail. > > The package now builds successfully, but needs more work before I'd > be > comfortable uploading it. Anyone else is free to upload it instead. > > Kind Regards, > > Bas > I've been working on updating dask.distributed to 2022.12.1 to match the dask version of dask and almost have an version where the tests pass (or are disabled). I'll probably have it uploaded in 10 - 30 hours. Diane
Bug#1028995: marked as done (mdtraj: (autopkgtest) needs update for Python 3.11)
Your message dated Wed, 18 Jan 2023 16:34:36 + with message-id and subject line Bug#1028995: fixed in mdtraj 1.9.7-5 has caused the Debian Bug report #1028995, regarding mdtraj: (autopkgtest) needs update for Python 3.11 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.) -- 1028995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mdtraj Version: 1.9.7-4 Severity: serious User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Hi Maintainer The autopkgtests of mdtraj fail with Python 3.11 as the default version (and Python 3.10 still supported) [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/m/mdtraj/testing/amd64/ Fatal Python error: Segmentation fault Current thread 0x7f9669eda040 (most recent call first): File "/usr/lib/python3/dist-packages/mdtraj/core/trajectory.py", line 2062 in image_molecules File "/tmp/autopkgtest-lxc.czx2fspl/downtmp/build.1n0/src/tests/test_trajectory.py", line 732 in test_image_molecules File "/usr/lib/python3/dist-packages/_pytest/python.py", line 195 in pytest_pyfunc_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in __call__ File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1789 in runtest File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 167 in pytest_runtest_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in __call__ File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 260 in File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 339 in from_call File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 259 in call_runtest_hook File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 220 in call_and_report File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 131 in runtestprotocol File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 112 in pytest_runtest_protocol File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 349 in pytest_runtestloop File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 324 in _main File "/usr/lib/python3/dist-packages/_pytest/main.py", line 270 in wrap_session File "/usr/lib/python3/dist-packages/_pytest/main.py", line 317 in pytest_cmdline_main File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in __call__ File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 167 in main File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 190 in console_main File "/usr/bin/pytest-3", line 33 in --- End Message --- --- Begin Message --- Source: mdtraj Source-Version: 1.9.7-5 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of mdtraj, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated mdtraj 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: SHA
Processed: tagging 1029151, tagging 1029153, tagging 1029154
Processing commands for cont...@bugs.debian.org: > tags 1029151 + upstream Bug #1029151 [src:mysql-8.0] mysql-8.0: CVE-2023-21863 CVE-2023-21867 CVE-2023-21868 CVE-2023-21869 CVE-2023-21870 CVE-2023-21871 CVE-2023-21873 CVE-2023-21875 CVE-2023-21876 CVE-2023-21877 CVE-2023-21878 CVE-2023-21879 CVE-2023-21880 CVE-2023-21881 CVE-2023-21882 CVE-2023-21883 CVE-2023-21887 Added tag(s) upstream. > tags 1029153 + upstream Bug #1029153 [src:virtualbox] virtualbox: CVE-2023-21884 CVE-2023-21885 CVE-2023-21886 CVE-2023-21889 CVE-2023-21898 CVE-2023-21899 Added tag(s) upstream. > tags 1029154 + upstream Bug #1029154 [src:swift] swift: CVE-2022-47950 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029151 1029153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029153 1029154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029154: swift: CVE-2022-47950
Source: swift X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for swift. CVE-2022-47950: OSSA-2023-001: Arbitrary file access through custom S3 XML entities Sébastien Meriot (OVH) reported a vulnerability in Swift's S3 XML parser. By supplying specially crafted XML files an authenticated user may coerce the S3 API into returning arbitrary file contents from the host server resulting in unauthorized read access to potentially sensitive data; this impacts both s3api deployments (Rocky or later), and swift3 deployments (Queens and earlier, no longer actively developed). Only deployments with S3 compatibility enabled are affected. https://www.openwall.com/lists/oss-security/2023/01/17/1 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-47950 https://www.cve.org/CVERecord?id=CVE-2022-47950 Please adjust the affected versions in the BTS as needed.
Processed: rows: diff for NMU version 0.4.1-5.1
Processing control commands: > tags 1026499 + patch Bug #1026499 [src:rows] rows: FTBFS: AssertionError: Lists differ: [] != ['iso', '8859'] Added tag(s) patch. > tags 1026499 + pending Bug #1026499 [src:rows] rows: FTBFS: AssertionError: Lists differ: [] != ['iso', '8859'] Added tag(s) pending. -- 1026499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029153: virtualbox: CVE-2023-21884 CVE-2023-21885 CVE-2023-21886 CVE-2023-21889 CVE-2023-21898 CVE-2023-21899
Source: virtualbox X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for virtualbox. Fixed in 7.0.6 CVE-2023-21884[0]: | Vulnerability in the Oracle VM VirtualBox product of Oracle | Virtualization (component: Core). Supported versions that are affected | are Prior to 6.1.42 and prior to 7.0.6. Easily exploitable | vulnerability allows high privileged attacker with logon to the | infrastructure where Oracle VM VirtualBox executes to compromise | Oracle VM VirtualBox. Successful attacks of this vulnerability can | result in unauthorized ability to cause a hang or frequently | repeatable crash (complete DOS) of Oracle VM VirtualBox. CVSS 3.1 Base | Score 4.4 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-21885[1]: | Vulnerability in the Oracle VM VirtualBox product of Oracle | Virtualization (component: Core). Supported versions that are affected | are Prior to 6.1.42 and prior to 7.0.6. Easily exploitable | vulnerability allows low privileged attacker with logon to the | infrastructure where Oracle VM VirtualBox executes to compromise | Oracle VM VirtualBox. While the vulnerability is in Oracle VM | VirtualBox, attacks may significantly impact additional products | (scope change). Successful attacks of this vulnerability can result in | unauthorized read access to a subset of Oracle VM VirtualBox | accessible data. Note: Applies to Windows only. CVSS 3.1 Base Score | 3.8 (Confidentiality impacts). CVSS Vector: | (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N). CVE-2023-21886[2]: | Vulnerability in the Oracle VM VirtualBox product of Oracle | Virtualization (component: Core). Supported versions that are affected | are Prior to 6.1.42 and prior to 7.0.6. Difficult to exploit | vulnerability allows unauthenticated attacker with network access via | multiple protocols to compromise Oracle VM VirtualBox. Successful | attacks of this vulnerability can result in takeover of Oracle VM | VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and | Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). CVE-2023-21889[3]: | Vulnerability in the Oracle VM VirtualBox product of Oracle | Virtualization (component: Core). Supported versions that are affected | are Prior to 6.1.42 and prior to 7.0.6. Easily exploitable | vulnerability allows low privileged attacker with logon to the | infrastructure where Oracle VM VirtualBox executes to compromise | Oracle VM VirtualBox. While the vulnerability is in Oracle VM | VirtualBox, attacks may significantly impact additional products | (scope change). Successful attacks of this vulnerability can result in | unauthorized read access to a subset of Oracle VM VirtualBox | accessible data. CVSS 3.1 Base Score 3.8 (Confidentiality impacts). | CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N). CVE-2023-21898[4]: | Vulnerability in the Oracle VM VirtualBox product of Oracle | Virtualization (component: Core). Supported versions that are affected | are Prior to 6.1.42 and prior to 7.0.6. Easily exploitable | vulnerability allows low privileged attacker with logon to the | infrastructure where Oracle VM VirtualBox executes to compromise | Oracle VM VirtualBox. Successful attacks of this vulnerability can | result in unauthorized ability to cause a hang or frequently | repeatable crash (complete DOS) of Oracle VM VirtualBox. Note: Applies | to VirtualBox VMs running Windows 7 and later. CVSS 3.1 Base Score 5.5 | (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). CVE-2023-21899[5]: | Vulnerability in the Oracle VM VirtualBox product of Oracle | Virtualization (component: Core). Supported versions that are affected | are Prior to 6.1.42 and prior to 7.0.6. Easily exploitable | vulnerability allows low privileged attacker with logon to the | infrastructure where Oracle VM VirtualBox executes to compromise | Oracle VM VirtualBox. Successful attacks of this vulnerability can | result in unauthorized ability to cause a hang or frequently | repeatable crash (complete DOS) of Oracle VM VirtualBox. Note: Applies | to VirtualBox VMs running Windows 7 and later. CVSS 3.1 Base Score 5.5 | (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-21884 https://www.cve.org/CVERecord?id=CVE-2023-21884 [1] https://security-tracker.debian.org/tracker/CVE-2023-21885 https://www.cve.org/CVERecord?id=CVE-2023-21885 [2] https://security-tracker.debian.org/tracker/CVE-2023-21886 https://www.cve.org/CVERecord?id=CVE-2023-21886 [3] https://security-tracker.debian.org/tracker/CVE-2023-21889 https://www.cve.org/CVERecord?id=CVE-2023-2
Processed: closing 1026556
Processing commands for cont...@bugs.debian.org: > close 1026556 Bug #1026556 [src:sorl-thumbnail] sorl-thumbnail: FTBFS: ImportError: cannot import name '_pgmagick' from partially initialized module 'pgmagick' (most likely due to a circular import) (/usr/lib/python3/dist-packages/pgmagick/__init__.py) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1026556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026499: rows: diff for NMU version 0.4.1-5.1
Control: tags 1026499 + patch
Control: tags 1026499 + pending
Dear maintainer,
I've prepared an NMU for rows (versioned as 0.4.1-5.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru rows-0.4.1/debian/changelog rows-0.4.1/debian/changelog
--- rows-0.4.1/debian/changelog 2022-01-09 16:14:00.0 +0200
+++ rows-0.4.1/debian/changelog 2023-01-18 18:19:46.0 +0200
@@ -1,3 +1,10 @@
+rows (0.4.1-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Build and test depend on python3-magic. (Closes: #1026499)
+
+ -- Adrian Bunk Wed, 18 Jan 2023 18:19:46 +0200
+
rows (0.4.1-5) unstable; urgency=medium
* debian/control: Remove XB-Python-Version field.
diff -Nru rows-0.4.1/debian/control rows-0.4.1/debian/control
--- rows-0.4.1/debian/control 2022-01-09 15:36:28.0 +0200
+++ rows-0.4.1/debian/control 2023-01-18 18:18:48.0 +0200
@@ -13,6 +13,7 @@
python3-coverage,
python3-ipdb,
python3-lxml,
+ python3-magic,
python3-mock,
python3-nose,
python3-nose-yanc,
diff -Nru rows-0.4.1/debian/tests/control rows-0.4.1/debian/tests/control
--- rows-0.4.1/debian/tests/control 2021-10-11 19:12:59.0 +0300
+++ rows-0.4.1/debian/tests/control 2023-01-18 18:19:41.0 +0200
@@ -1,6 +1,7 @@
Test-Command: excludes=$(cat debian/tests/excludes) && cp -r tests/ ${AUTOPKGTEST_TMP} && cd ${AUTOPKGTEST_TMP} && python3 -m nose --verbose $excludes
Depends: locales-all,
python3-lxml,
+ python3-magic,
python3-mock,
python3-nose,
python3-openpyxl,
Bug#1029151: mysql-8.0: CVE-2023-21863 CVE-2023-21867 CVE-2023-21868 CVE-2023-21869 CVE-2023-21870 CVE-2023-21871 CVE-2023-21873 CVE-2023-21875 CVE-2023-21876 CVE-2023-21877 CVE-2023-21878 CVE-2023-21
Source: mysql-8.0 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for mysql-8.0. All fixed in 8.0.32. CVE-2023-21863[0]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.31 | and prior. Easily exploitable vulnerability allows high privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-21867[1]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.31 | and prior. Easily exploitable vulnerability allows high privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-21868[2]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.31 | and prior. Easily exploitable vulnerability allows low privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). CVE-2023-21869[3]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | InnoDB). Supported versions that are affected are 8.0.31 and prior. | Easily exploitable vulnerability allows high privileged attacker with | network access via multiple protocols to compromise MySQL Server. | Successful attacks of this vulnerability can result in unauthorized | ability to cause a hang or frequently repeatable crash (complete DOS) | of MySQL Server as well as unauthorized update, insert or delete | access to some of MySQL Server accessible data. CVSS 3.1 Base Score | 5.5 (Integrity and Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H). CVE-2023-21870[4]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.31 | and prior. Easily exploitable vulnerability allows high privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-21871[5]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | InnoDB). Supported versions that are affected are 8.0.31 and prior. | Easily exploitable vulnerability allows high privileged attacker with | network access via multiple protocols to compromise MySQL Server. | Successful attacks of this vulnerability can result in unauthorized | ability to cause a hang or frequently repeatable crash (complete DOS) | of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS | Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-21873[6]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Optimizer). Supported versions that are affected are 8.0.31 | and prior. Easily exploitable vulnerability allows high privileged | attacker with network access via multiple protocols to compromise | MySQL Server. Successful attacks of this vulnerability can result in | unauthorized ability to cause a hang or frequently repeatable crash | (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability | impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-21875[7]: | Vulnerability in the MySQL Server product of Oracle MySQL (component: | Server: Security: Encryption). Supported versions that are affected | are 8.0.31 and prior. Difficult to exploit vulnerability allows high | privileged attacker with network access via multiple protocols to | compromise MySQL Server. Successful attacks of this vulnerability can | result in unauthorized creation, deletion or modification access to | critical data or all MySQL Server accessible data and unauthorized | ability to cause a hang or frequently repeatable crash (complete DOS) | of MySQL Server. CVSS 3.1 Base Score 5.9 (In
Bug#1028773: marked as done (python-quantities: FTBFS: AttributeError: module 'numpy' has no attribute 'typeDict')
Your message dated Wed, 18 Jan 2023 16:11:56 + with message-id and subject line Bug#1028773: fixed in python-quantities 0.13.0-2 has caused the Debian Bug report #1028773, regarding python-quantities: FTBFS: AttributeError: module 'numpy' has no attribute 'typeDict' 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.) -- 1028773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-quantities Version: 0.13.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.10 setup.py config > /<>/setup.py:1: DeprecationWarning: The distutils package is > deprecated and slated for removal in Python 3.12. Use setuptools or check PEP > 632 for potential alternatives > from distutils.cmd import Command > running config > I: pybuild base:240: python3.11 setup.py config > /<>/setup.py:1: DeprecationWarning: The distutils package is > deprecated and slated for removal in Python 3.12. Use setuptools or check PEP > 632 for potential alternatives > from distutils.cmd import Command > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3.10 setup.py build > /<>/setup.py:1: DeprecationWarning: The distutils package is > deprecated and slated for removal in Python 3.12. Use setuptools or check PEP > 632 for potential alternatives > from distutils.cmd import Command > running build > running data > running build_py > creating /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/registry.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/dimensionality.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/markup.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/quantity.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/umath.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/decorators.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/uncertainquantity.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/unitquantity.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > copying quantities/_version.py -> > /<>/.pybuild/cpython3_3.10/build/quantities > creating /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/frequency.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/radiation.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/velocity.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/heat.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/pressure.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/dimensionless.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/compound.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/electromagnetism.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/time.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/substance.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/viscosity.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/temperature.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/energy.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/information.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/power.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/angle.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantities/units/volume.py -> > /<>/.pybuild/cpython3_3.10/build/quantities/units > copying quantit
Bug#1026536: marked as done (nitpic: FTBFS: elf-sframe.c:526: undefined reference to `sframe_encoder_write')
Your message dated Wed, 18 Jan 2023 15:39:42 + with message-id and subject line Bug#1026536: fixed in nitpic 0.1-18 has caused the Debian Bug report #1026536, regarding nitpic: FTBFS: elf-sframe.c:526: undefined reference to `sframe_encoder_write' 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.) -- 1026536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nitpic Version: 0.1-17 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libbfd.a(elf-sframe.o): > in function `_bfd_elf_write_section_sframe': > /build/binutils-IJ3Mfh/binutils-2.39.50.20221208/builddir-single/bfd/../../bfd/elf-sframe.c:526: > undefined reference to `sframe_encoder_write' > /usr/bin/ld: > /build/binutils-IJ3Mfh/binutils-2.39.50.20221208/builddir-single/bfd/../../bfd/elf-sframe.c:541: > undefined reference to `sframe_encoder_free' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/12/20/nitpic_0.1-17_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: nitpic Source-Version: 0.1-18 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of nitpic, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated nitpic 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, 18 Jan 2023 17:09:17 +0200 Source: nitpic Architecture: source Version: 0.1-18 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 1026536 Changes: nitpic (0.1-18) unstable; urgency=low . * QA upload. * Adapt to binutils 2.40. (Closes: #1026536) Checksums-Sha1: de2a0eaaf1bea4bc819ab6104dcb0ebde1085200 1718 nitpic_0.1-18.dsc b1b7ddbb61113b0b436bc47c96b650549366da9a 11488 nitpic_0.1-18.debian.tar.xz Checksums-Sha256: a3c19bfe0c8e8654b9a817d6da9a468443e20521e5bacce20043e0fe3c875482 1718 nitpic_0.1-18.dsc d33b726e6adf51dfb3b2eb64a3f8d206934adc5f250d216ba0823fd8612d1e6c 11488 nitpic_0.1-18.debian.tar.xz Files: 9176cd03c35f3ce57e1f3a071e9f3291 1718 electronics optional nitpic_0.1-18.dsc 27fc8061ba48042c54219a728f055f67 11488 electronics optional nitpic_0.1-18.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPIDBgACgkQiNJCh6LY mLH9JRAAkxB6qaJNGu0jVsxpijDQYpHaP5N3NBRG/e+5jT9mxfanODp1YVfdvw3w Tw6Ljd9T1AXrwgY1kI7bwZYU9SQ/+ypZwDLTq3/jhOpfldAgRcLh3ebq1cIoWyfK rKEMkr22bv5vkQHT+/mNC0yr9xfZrDOcUMaNOJhBUtsFgT8eqVrBdU7PmfbqsYly PWeWjuY+9ZiBWTodMfPd/qUJ1/sAkIwwt5c8U73w+14T45knOKsJCsdx7gPPc/oG QeHFNnh93TZo5rcrY5UAxXEkf7i80u+iUbAtyeMB+2+eo0BbpOr1xBAID90//Q7H rBxCBbFZz7O97eoH/q1uqQeQ8UpraFBFkq6bpnl8zci/V8GMRJH+brK01LhH/zXD uwc2jpM3roVZUQa95K5XirHSm5hXZ0bAYauWiuwKl7OIxD0LDj8vIlA1X+KxlMvc SbDXMF8yw9zm+CP02zQAkQ5LmiWAJftiLb6s3dan1+AHIjVneHaUvWQz1hNF6it1 AFPogG7wXwBqFv1s2meCyLI1lhPH+i1jzI1H3d5EnoHHgZvgwOuWEDSMQJZO4b+g gvroNUS/7JemirTJfDOJoLzAHCC8XBYrrAwkKmLEO55iD3mD/24C50r5bzi5ZANY nmqQIp
Bug#1029112: Surprise build issue with ibus-libzhuyin
On 2023-01-18 02:07, Osamu Aoki wrote: Debian official packages are required to build without downloading external files during their build. (Builddd is in isolated network environment only with access to the Debian package repository. Yeah, that's what I thought — thanks for confirming. Which made my confusion even worse... But the explanation proved to be that debian/watch made uscan download another upstream tarball than the one we need to use. Boyuan spotted that issue and fixed it. Thanks Boyuan! -- Gunnar
Processed: bug 1026563 is forwarded to https://github.com/mardiros/aioxmlrpc/pull/15
Processing commands for cont...@bugs.debian.org: > forwarded 1026563 https://github.com/mardiros/aioxmlrpc/pull/15 Bug #1026563 [src:aioxmlrpc] aioxmlrpc: FTBFS: AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? Set Bug forwarded-to-address to 'https://github.com/mardiros/aioxmlrpc/pull/15'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026470: closing 1026470
close 1026470 thanks
Processed: closing 1026470
Processing commands for cont...@bugs.debian.org:
> close 1026470
Bug #1026470 [src:onionbalance] onionbalance: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit
code 13
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1028587: Acknowledgement (datefudge: 64-bit time_t functions are not implemented/exposed)
On 18.01.23 15:51, adrien wrote: As far as I can see, libfaketime doesn't have an equivalent to datefudge's -s (static time) but I'm not sure if it's really needed in practice and if it is, I'm confident we can add it to libfaketime. [ Author of datefudge here ] I assume that datefudge is used to support reproducible builds; in that case it most likely *is* necessary to use the '-s' option, as build times are not going to be constant. I do recommend switching to a supported library. I'm sorry to say that my time budget already is negative for the foreseeable future, thus resuming support for datefudge is out of the question unfortunately. -- -- regards -- -- Matthias Urlichs BEGIN:VCARD VERSION:4.0 N:Urlichs;Matthias;;; NICKNAME:Smurf EMAIL;PREF=1:matth...@urlichs.de TEL;TYPE=work;VALUE=TEXT:+49 911 59818 0 URL;TYPE=home:https://matthias.urlichs.de END:VCARD OpenPGP_signature Description: OpenPGP digital signature
Bug#1026541: android-platform-system-extras: diff for NMU version 10.0.0+r36+ds-2.1
Control: tags 1026541 + patch Control: tags 1026541 + pending Dear maintainer, I've prepared an NMU for android-platform-system-extras (versioned as 10.0.0+r36+ds-2.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru android-platform-system-extras-10.0.0+r36+ds/debian/changelog android-platform-system-extras-10.0.0+r36+ds/debian/changelog --- android-platform-system-extras-10.0.0+r36+ds/debian/changelog 2020-12-23 11:48:01.0 +0200 +++ android-platform-system-extras-10.0.0+r36+ds/debian/changelog 2023-01-18 17:40:05.0 +0200 @@ -1,3 +1,10 @@ +android-platform-system-extras (10.0.0+r36+ds-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Adapt to new libsquashfuse-dev. (Closes: #1026541) + + -- Adrian Bunk Wed, 18 Jan 2023 17:40:05 +0200 + android-platform-system-extras (10.0.0+r36+ds-2) unstable; urgency=medium * Team upload. diff -Nru android-platform-system-extras-10.0.0+r36+ds/debian/control android-platform-system-extras-10.0.0+r36+ds/debian/control --- android-platform-system-extras-10.0.0+r36+ds/debian/control 2020-12-23 11:48:01.0 +0200 +++ android-platform-system-extras-10.0.0+r36+ds/debian/control 2023-01-18 17:39:59.0 +0200 @@ -13,6 +13,7 @@ android-platform-system-core-headers (>= 1:10.0.0+r36-1~), dh-exec, libsquashfuse-dev, + pkg-config, Standards-Version: 4.2.1 Rules-Requires-Root: no Homepage: https://android.googlesource.com/platform/system/extras diff -Nru android-platform-system-extras-10.0.0+r36+ds/debian/rules android-platform-system-extras-10.0.0+r36+ds/debian/rules --- android-platform-system-extras-10.0.0+r36+ds/debian/rules 2020-12-23 11:48:01.0 +0200 +++ android-platform-system-extras-10.0.0+r36+ds/debian/rules 2023-01-18 17:39:59.0 +0200 @@ -6,7 +6,7 @@ # Security Hardening export DEB_BUILD_MAINT_OPTIONS = hardening=+all export DEB_LDFLAGS_MAINT_APPEND = -fPIC -export DEB_CPPFLAGS_MAINT_APPEND = -I/usr/include/android -DNDEBUG +export DEB_CPPFLAGS_MAINT_APPEND = -I/usr/include/android -DNDEBUG `pkg-config --cflags squashfuse` export OUT_DIR = debian/out lib%.so: debian/lib%.mk
Processed: android-platform-system-extras: diff for NMU version 10.0.0+r36+ds-2.1
Processing control commands: > tags 1026541 + patch Bug #1026541 [src:android-platform-system-extras] android-platform-system-extras: FTBFS: squashfs_utils/squashfs_utils.c:27:10: fatal error: squashfs_fs.h: No such file or directory Added tag(s) patch. > tags 1026541 + pending Bug #1026541 [src:android-platform-system-extras] android-platform-system-extras: FTBFS: squashfs_utils/squashfs_utils.c:27:10: fatal error: squashfs_fs.h: No such file or directory Added tag(s) pending. -- 1026541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029000: marked as done (yoyo: (autopkgtest) needs update for Python 3.11)
Your message dated Wed, 18 Jan 2023 15:16:34 +
with message-id
and subject line Bug#1029000: fixed in yoyo 8.2.0+dfsg1-1
has caused the Debian Bug report #1029000,
regarding yoyo: (autopkgtest) needs update for Python 3.11
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.)
--
1029000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yoyo
Version: 7.3.2+dfsg1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Hi Maintainer
The autopkgtests of yoyo fail with Python 3.11 as the default version
(and Python 3.10 still supported) [1]. I've copied what I hope is the
relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/y/yoyo/testing/amd64/
Creating new PostgreSQL cluster 15/regress ...
Warning: connection to the database failed, disabling startup checks:
psql: error: connection to server on socket "/tmp/.s.PGSQL.5433"
failed: FATAL: role "debci" does not exist
+ export
PYTHONPATH=/tmp/autopkgtest-lxc.z8fl1tkb/downtmp/build.X7w/src/debian/tests
+ PYTHONPATH=/tmp/autopkgtest-lxc.z8fl1tkb/downtmp/build.X7w/src/debian/tests
+ psql -Upostgres -c 'create database yoyo_test;'
CREATE DATABASE
+ pytest-3 yoyo/tests
= test session starts ==
platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.z8fl1tkb/downtmp/build.X7w/src
collected 152 items
yoyo/tests/test_backends.py ..ss..s.s.. [ 15%]
yoyo/tests/test_cli_script.py ..s.s. [ 42%]
.[ 43%]
yoyo/tests/test_config.py ...[ 53%]
yoyo/tests/test_connections.py [ 58%]
yoyo/tests/test_internalmigrations.py [ 63%]
yoyo/tests/test_migrations.py .. [ 91%]
..FF [ 96%]
yoyo/tests/test_utils.py . [100%]
=== FAILURES ===
__ TestPostApplyHooks.test_it_runs_multiple_post_apply_hooks ___
self =
backend_sqlite3 =
def test_it_runs_multiple_post_apply_hooks(self, backend_sqlite3):
with migrations_dir(
**{
"a": "step('create table postapply (i int)')",
"post-apply": "step('insert into postapply values (1)')",
"post-apply2": "step('insert into postapply values (2)')",
}
) as tmpdir:
> backend_sqlite3.apply_migrations(
backend_sqlite3.to_apply(read_migrations(tmpdir))
)
yoyo/tests/test_migrations.py:611:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
yoyo/backends.py:449: in apply_migrations
self.apply_migrations_only(migrations, force=force)
yoyo/backends.py:461: in apply_migrations_only
self.apply_one(m, force=force)
yoyo/backends.py:507: in apply_one
migration.process_steps(migration_backend, "apply", force=force)
yoyo/migrations.py:272: in process_steps
raise exc_info[1].with_traceback(exc_info[2])
yoyo/migrations.py:257: in process_steps
getattr(step, direction)(backend, force)
yoyo/migrations.py:315: in apply
getattr(self.step, direction)(backend, force)
yoyo/migrations.py:411: in apply
self._execute(cursor, self._apply)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , cursor =
stmt = 'create table postapply (i int)'
out = <_io.TextIOWrapper name="<_io.FileIO name=6 mode='rb+'
closefd=True>" mode='r+' encoding='utf-8'>
def _execute(self, cursor, stmt, out=None):
"""
Execute the given statement. If rows are returned, output these in a
tabulated format.
"""
if out is None:
out = sys.stdout
if isinstance(stmt, str):
logger.debug(" - executing %r", stmt.encode("ascii", "replace"))
else:
logger.debug(" - executing %r", stmt)
> cursor.execute(stmt)
E sqlite3.OperationalError: table postapply already exists
yoyo/migrations.py:381: OperationalError
___ TestPostApplyHooks.test_apply_migrations_only_does_not_run_hooks _
Bug#1027189: marked as done (astroplan: autopkgtest fail with numpy/1.24.1)
Your message dated Wed, 18 Jan 2023 14:51:36 + with message-id and subject line Bug#1027189: fixed in astroplan 0.7-4 has caused the Debian Bug report #1027189, regarding astroplan: autopkgtest fail with numpy/1.24.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.) -- 1027189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: astroplan Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- Source: astroplan Source-Version: 0.7-4 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of astroplan, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated astroplan 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, 18 Jan 2023 14:38:43 +0100 Source: astroplan Architecture: source Version: 0.7-4 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 1027189 Changes: astroplan (0.7-4) unstable; urgency=medium . * Team upload . [ Bas Couwenberg ] * Team upload. * Add gbp.conf to use pristine-tar & --source-only-changes by default. * Add upstream patch to fix test failure with Numpy 1.24 (Closes: #1027189) . [ Debian Janitor ] * Set upstream metadata fields: Bug-Submit. * Remove obsolete field Name from debian/upstream/metadata * Replace use of deprecated $ADTTMP with $AUTOPKGTEST_TMP. . [ Ole Streicher ] * Push Standards-Version to 4.6.2. No changes Checksums-Sha1: 3cb0f6d939f951bd77c67aeba49f62d42d400cd7 2212 astroplan_0.7-4.dsc 986c571638a00de2145c5bb879d77713800ffee9 8668 astroplan_0.7-4.debian.tar.xz Checksums-Sha256: b7db57a9fa3f90380727350eed49729a2d82ebc36a8a66c1b372fa410741a9dd 2212 astroplan_0.7-4.dsc 9a5fdea95371a5448595dbd5b70167bf48934208ffe7c1c8f8ad635e3a004270 8668 astroplan_0.7-4.debian.tar.xz Files: cbdb0702a1b7ebe24963c935d2b53f97 2212 python optional astroplan_0.7-4.dsc 53ba3e85dacead056dd20fbcc65aaf09 8668 python optional astroplan_0.7-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmPH+KcACgkQcRWv0HcQ 3PcnKg/9HJs9WwwYDUCBHe8ttYQ8kqn3rCypySkDgsQ0EydikbPoc7yX5JbaSM+D vF72Dc2zpqpQisfVgIlQZDNCRqDHPKDn89YBkt9ZKWGNwgxqLXjddmAz9155zma4 nme9vrk5gIFZUOq6PLb0Akn98PZ3dc2OU5wWN2H1z4Qawp+r5E/5sRWS2RrkwiEF u9ZmBXKLDhbjTBPs6xbs1BxhbAeuHLZCEkL4id1zAZ8MosMWKiUDqi0DzttL7Iv+ VUFB6y+ggKSRgs1Hmn0pVFNsZPHRv2nGo+JKmPWcnxY6zdfkIP4SHEe7eXpMehkV O3HPZTwEemyNHPHFTRV3YWesi93gUZvACP0sHNeuackmRkOvyOFIfJKhzLjREJlI X1iPMID/Hp0z2TBsobwrikFHmX1TmRTxWY/gzgcya5LYQWqzpUwtAXyeYVxtdk6I vR3Zr/pmAeDPPn7ntbQubX8McV/p6afivEYUPPp2bBknkzSDW6Vkq1oaBnw2n345 VhGRtYxf9JakYi+RMT2WrLEH39lXMsK19SFOhAgSMmCJbo8mkGX73zgkGYlYzsun mY3vpKUjnOZGEz/Q9CJxCgGtlbIWfiZZfw/4j
Bug#1028587: Acknowledgement (datefudge: 64-bit time_t functions are not implemented/exposed)
Hi, Considering datefudge has seen little development for the past decade, maybe we should try to move to libfaketime[1] instead which is being actively maintained. I don't really feel like doing the work for 64-bit time_t on 32 bit and making sure the ABI is actually fine; that sounds like a good way to self-inflict annoying bugs. Porting whatever needs faked time to libfaketime shouldn't be too much work and should be more future-proof. As far as I can see, libfaketime doesn't have an equivalent to datefudge's -s (static time) but I'm not sure if it's really needed in practice and if it is, I'm confident we can add it to libfaketime. [1] https://github.com/wolfcw/libfaketime Best, -- Adrien
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 1024287 src:django-assets
Bug #1024287 [django-assets] django-assets: FTBFS against python 3.11
Bug reassigned from package 'django-assets' to 'src:django-assets'.
Ignoring request to alter found versions of bug #1024287 to the same values
previously set
Ignoring request to alter fixed versions of bug #1024287 to the same values
previously set
> forcemerge 1026496 1024287
Bug #1026496 [src:django-assets] django-assets: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.11 3.10" returned exit code
13
Bug #1024287 [src:django-assets] django-assets: FTBFS against python 3.11
Set Bug forwarded-to-address to
'https://github.com/miracle2k/django-assets/pull/104'.
Severity set to 'serious' from 'normal'
Marked as found in versions django-assets/2.0-2.
Added tag(s) sid, ftbfs, and bookworm.
Merged 1024287 1026496
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1024287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024287
1026496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1026496 is forwarded to https://github.com/miracle2k/django-assets/pull/104
Processing commands for cont...@bugs.debian.org:
> forwarded 1026496 https://github.com/miracle2k/django-assets/pull/104
Bug #1026496 [src:django-assets] django-assets: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.11 3.10" returned exit code
13
Set Bug forwarded-to-address to
'https://github.com/miracle2k/django-assets/pull/104'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026494: eclipse-wtp: FTBFS: [javac] /<>/org.eclipse.wst.common.core/target/sources/org/eclipse/wst/common/core/util/RegistryReader.java:62: error: cannot find symbol
On Tue, Dec 20, 2022 at 05:17:33PM +0100, Lucas Nussbaum wrote:
> Source: eclipse-wtp
> Version: 3.18-5
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm
>...
> > [javac] Compiling 35 source files to
> > /<>/org.eclipse.wst.common.core/target/classes
> > [javac]
> > /<>/org.eclipse.wst.common.core/target/sources/org/eclipse/wst/common/core/util/RegistryReader.java:62:
> > error: cannot find symbol
> > [javac] public RegistryReader(IPluginRegistry registry, String
> > pluginID, String extensionPoint) {
> > [javac] ^
> > [javac] symbol: class IPluginRegistry
> > [javac] location: class RegistryReader
>...
The commit fixing this[1] is included in 3.22.
There are similar errors elsewhere after fixing this that might also be
fixed in more recent upstream versions (untested).
cu
Adrian
[1]
https://git.eclipse.org/c/webtools-common/webtools.common.git/commit/plugins/org.eclipse.wst.common.core/src-search/org/eclipse/wst/common/core/util/RegistryReader.java?id=bf236815e417929559715e2636057510b51bd46e
Processed: wcc: diff for NMU version 0.0.2+dfsg-4.2
Processing control commands: > tags 1026493 + patch Bug #1026493 [src:wcc] wcc: FTBFS: elf-sframe.c:526: undefined reference to `sframe_encoder_write' Added tag(s) patch. > tags 1026493 + pending Bug #1026493 [src:wcc] wcc: FTBFS: elf-sframe.c:526: undefined reference to `sframe_encoder_write' Added tag(s) pending. -- 1026493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026493: wcc: diff for NMU version 0.0.2+dfsg-4.2
Control: tags 1026493 + patch Control: tags 1026493 + pending Dear maintainer, I've prepared an NMU for wcc (versioned as 0.0.2+dfsg-4.2) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru wcc-0.0.2+dfsg/debian/changelog wcc-0.0.2+dfsg/debian/changelog --- wcc-0.0.2+dfsg/debian/changelog 2020-03-21 19:02:12.0 +0200 +++ wcc-0.0.2+dfsg/debian/changelog 2023-01-18 16:09:29.0 +0200 @@ -1,3 +1,10 @@ +wcc (0.0.2+dfsg-4.2) unstable; urgency=low + + * Non-maintainer upload. + * Adapt to binutils 2.40. (Closes: #1026493) + + -- Adrian Bunk Wed, 18 Jan 2023 16:09:29 +0200 + wcc (0.0.2+dfsg-4.1) unstable; urgency=medium * NMU: Fix build (Closes: #950910) diff -Nru wcc-0.0.2+dfsg/debian/patches/binutils_shared.patch wcc-0.0.2+dfsg/debian/patches/binutils_shared.patch --- wcc-0.0.2+dfsg/debian/patches/binutils_shared.patch 2020-03-21 19:02:12.0 +0200 +++ wcc-0.0.2+dfsg/debian/patches/binutils_shared.patch 2023-01-18 16:09:29.0 +0200 @@ -12,7 +12,7 @@ -all:: - $(CC) $(CFLAGS) wcc.c -o wcc -lbfd -lelf -lcapstone +all: -+ $(CC) $(CFLAGS) wcc.c -o wcc -l:libbfd.a -lz -ldl -liberty -lelf -lcapstone ++ $(CC) $(CFLAGS) wcc.c -o wcc -l:libbfd.a -l:libsframe.a -lz -ldl -liberty -lzstd -lelf -lcapstone # $(CC) $(CFLAGS) -m32 -Wl,-rpath /home/jonathan/solution-exp/unlinking/awareness/self/wcc/src/wcc/lib32/ wcc.c -o wcc32 -lelf ./lib32/libbfd-2.24-system.so ./lib32/libcapstone.so.3 cp wcc ../../bin/
Bug#1028705: marked as done (xraylarch: FTBFS: build-dependency not installable: python-numpy-doc)
Your message dated Wed, 18 Jan 2023 13:08:58 + with message-id and subject line Bug#1028705: fixed in xraylarch 0.9.58+ds1-5 has caused the Debian Bug report #1028705, regarding xraylarch: FTBFS: build-dependency not installable: python-numpy-doc 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.) -- 1028705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xraylarch Version: 0.9.58+ds1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, python3-setuptools, > python3-all, feff85exafs, python3-setuptools-scm, python3-scipy, > python3-numpy, python3-matplotlib, python3-sqlalchemy, python3-h5py, > python3-pil, python3-peakutils, python3-requests, python3-psycopg2, > python3-skimage, python3-sklearn, python3-asteval, python3-lmfit, > python3-uncertainties, python3-pyepics, python3-xraydb, python3-pymatgen, > python3-wxgtk4.0, python3-wxutils, python3-wxmplot, python3-yaml, > python3-psutil, python3-nose, python3-termcolor, python3-silx, python3-fabio, > python3-pyfai, python3-pycifrw, python3-pybtex, python3-sphinxcontrib.bibtex, > python3-sphinx, python3-doc, python-numpy-doc, python-scipy-doc, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, > python3-setuptools, python3-all, feff85exafs, python3-setuptools-scm, > python3-scipy, python3-numpy, python3-matplotlib, python3-sqlalchemy, > python3-h5py, python3-pil, python3-peakutils, python3-requests, > python3-psycopg2, python3-skimage, python3-sklearn, python3-asteval, > python3-lmfit, python3-uncertainties, python3-pyepics, python3-xraydb, > python3-pymatgen, python3-wxgtk4.0, python3-wxutils, python3-wxmplot, > python3-yaml, python3-psutil, python3-nose, python3-termcolor, python3-silx, > python3-fabio, python3-pyfai, python3-pycifrw, python3-pybtex, > python3-sphinxcontrib.bibtex, python3-sphinx, python3-doc, python-numpy-doc, > python-scipy-doc, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [602 B] > Get:5 copy:/<>/apt_archive ./ Packages [679 B] > Fetched 2244 B in 0s (183 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: python-numpy-doc but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/13/xraylarch_0.9.58+ds1-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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
Bug#1029136: configuration files not properly migrated on switch to unversioned packages
Package: mariadb-server Version: 1:10.11.1-1 Severity: serious The latest update switch to unversioned packages. One issue I immediately noticed is that /etc/init.d/mariadb was installed 644, i.e. is not executable. Even, after purging the now obsolete -10.6 packages, I got this: Löschen der Konfigurationsdateien von mariadb-server-10.6 (1:10.6.11-2) ... Löschen der Konfigurationsdateien von mariadb-client-10.6 (1:10.6.11-2) ... [master 28eeae9] committing changes in /etc made by "aptitude" Author: Michael Biebl 12 files changed, 80 deletions(-) delete mode 100644 logcheck/ignore.d.paranoid/mariadb-server-10_6 delete mode 100644 logcheck/ignore.d.server/mariadb-server-10_6 delete mode 100644 logcheck/ignore.d.workstation/mariadb-server-10_6 delete mode 12 rc0.d/K01mariadb delete mode 12 rc1.d/K01mariadb delete mode 12 rc2.d/S01mariadb delete mode 12 rc3.d/S01mariadb delete mode 12 rc4.d/S01mariadb delete mode 12 rc5.d/S01mariadb delete mode 12 rc6.d/K01mariadb delete mode 12 systemd/system/multi-user.target.wants/mariadb.service This is not good. May advice would be to keep (emtpy) transitional packages mariadb-server-10.6/mariadb-client-10.6 and mariadb-server-10.5/mariadb-client-10.5 which itself depend on the unversioned mariadb package. This will not only make the upgrade smoother, it will also ensure that if you purge the empty transitional packages, you do not accidentally remove any import configuration state. Post bookworm you can then safely drop those empty transitional packages. Regards, Michael -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mariadb-server depends on: ii adduser3.130 ii debconf [debconf-2.0] 1.5.82 ii galera-4 26.4.11-1+b2 ii gawk 1:5.1.0-1 ii iproute2 6.1.0-1 ii libc6 2.36-8 ii libdbi-perl1.643-4 ii libpam0g 1.5.2-6 ii libssl33.0.7-1 ii libstdc++6 12.2.0-14 ii lsb-base 11.5 ii lsof 4.95.0-1 ii mariadb-client 1:10.11.1-1 ii mariadb-common 1:10.11.1-1 ii mariadb-server-core1:10.11.1-1 ii passwd 1:4.13+dfsg1-1 ii perl 5.36.0-7 ii procps 2:4.0.2-3 ii psmisc 23.6-1 ii rsync 3.2.7-1 ii socat 1.7.4.4-2 ii sysvinit-utils [lsb-base] 3.06-2 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages mariadb-server recommends: ii libhtml-template-perl 2.97-2 ii pv 1.6.20-1 Versions of packages mariadb-server suggests: ii bsd-mailx [mailx] 8.1.2-0.20220412cvs-1 pn mariadb-test ii netcat-openbsd 1.219-1 -- Configuration Files: /etc/logcheck/ignore.d.paranoid/mariadb-server [Errno 13] Keine Berechtigung: '/etc/logcheck/ignore.d.paranoid/mariadb-server' /etc/logcheck/ignore.d.server/mariadb-server [Errno 13] Keine Berechtigung: '/etc/logcheck/ignore.d.server/mariadb-server' -- debconf information excluded
Bug#1029135: xtrx-dkms: xtrx module fails to build for kernel version 6.1
Package: xtrx-dkms Version: 0.0.1+git20190320.5ae3a3e-3.1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: gme...@mikroskosmos.gr Dear Maintainer, While installing linux-image-6.1.0-1-amd64 dpkg tries to build xtrx-dkms for this kernel and fails with the following log file: = DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.1 for kernel 6.1.0-1-amd64 (x86_64) Wed Jan 18 02:21:45 PM EET 2023 make: Entering directory '/usr/src/linux-headers-6.1.0-1-amd64' CC [M] /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.o /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.c:518:27: error: initialization of ‘void (*)(struct uart_port *, struct ktermios *, const struct ktermios *)’ from incompatible pointer type ‘void (*)(struct uart_port *, struct ktermios *, struct ktermios *)’ [-Werror=incompatible-pointer-types] 518 | .set_termios= xtrx_uart_set_termios, | ^ /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.c:518:27: note: (near initialization for ‘xtrx_uart_ops.set_termios’) cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.1.0-1-common/scripts/Makefile.build:255: /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build/xtrx.o] Error 1 make: *** [/usr/src/linux-headers-6.1.0-1-common/Makefile:2017: /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.1/build] Error 2 make: Leaving directory '/usr/src/linux-headers-6.1.0-1-amd64 = Thus the whole process of installing kernel 6.1 fails with an error. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (800, 'testing'), (730, 'stable-security'), (710, 'stable'), (500, 'stable-updates'), (450, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xtrx-dkms depends on: ii dkms 3.0.10-1 xtrx-dkms recommends no packages. xtrx-dkms suggests no packages. -- no debconf information
Bug#1029122: marked as done (scm: ftbfs on mipsel)
Your message dated Wed, 18 Jan 2023 12:10:06 + with message-id and subject line Bug#1029122: fixed in scm 5f3-4 has caused the Debian Bug report #1029122, regarding scm: ftbfs on mipsel 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.) -- 1029122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scm Version: 5f2-3 Severity: serious Dear Maintainer, The upload[0] cause a regression with build failure on mipsel: ``` ... make checklit make[3]: Entering directory '/<>' ./scmlit -fr4rstest.scm -e'(test-sc4)(test-delay)(gc)' \ -e '(or (null? errs) (quit 1))' < /dev/null remove #define SHORT_INT in scmfig.h and recompile scm make[3]: *** [Makefile:553: checklit] Error 1 ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=scm&arch=mipsel&ver=5f3-3&stamp=1673937776&raw=0 I have fixed the issue on my local machine and upload it after testing it. Thanks. [0]: https://tracker.debian.org/news/1409807/accepted-scm-5f3-3-source-into-unstable/ -- Regards, -- Bo YU signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: scm Source-Version: 5f3-4 Done: Bo YU We believe that the bug you reported is fixed in the latest version of scm, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bo YU (supplier of updated scm 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, 18 Jan 2023 12:34:18 +0800 Source: scm Architecture: source Version: 5f3-4 Distribution: unstable Urgency: medium Maintainer: Debian Scheme Dream Team Changed-By: Bo YU Closes: 1029122 Changes: scm (5f3-4) unstable; urgency=medium . * Team upload. * Fix ftbfs on mipsel. Closes: #1029122 * Use libncurses-dev instead of libncurses5-dev Checksums-Sha1: 08be078686809380bc04259b59fdd529d863cb45 2050 scm_5f3-4.dsc cd0813b461a2eca6520a2a653777a77160e6ad5f 14704 scm_5f3-4.debian.tar.xz f8e2fa2dff6f4a1548d623a8e52ab463c6bd6027 6302 scm_5f3-4_source.buildinfo Checksums-Sha256: f712d4affbf52028f15e3a3245d1de8823cdd52ddcbcd595bc004a26b42aaa44 2050 scm_5f3-4.dsc 40153b11508d4baf791a91b9664832d66f98dac8faa153525e90d4b0bfdc0d3c 14704 scm_5f3-4.debian.tar.xz 2056f67e04118d230a027f79e5f7eb8d3970ae296a3f7a2e368aa16619fa6994 6302 scm_5f3-4_source.buildinfo Files: 09e0fc599eac0a16f73e65a4f994c14b 2050 interpreters optional scm_5f3-4.dsc 03441fc70bba6762beb2f7dcf8e56739 14704 interpreters optional scm_5f3-4.debian.tar.xz b908eb29021331ec96510f0de18bda20 6302 interpreters optional scm_5f3-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmPH3UMACgkQweDZLphv fH6M1xAA92gR8ayTM2CjHjbcO7U8bsIaXsDwf/vBJEZWgx3tTgbBgwM6TxWLzbSf bn0xKzPpdjsRmPQ9yWha3icaOZF5CZ69u2xaehKIQ2GKFc3TWArmCLCY1FScTWVE wheK+bHB9dsVTsUcSnPRu6WuwDxU++YyEe/n/nJUxj5Rb7DYJj59ioZLqjCsXeeG hA5mh2XQgE+2CjYJ1GFlMfYAJg8sOXWWZ5/wTGFEsa4n4fmFi/FfbQvH69Q9NfQa 3RmDe2YwCDVcNbk9za3AhzaBD2vw2ttJtBAJoPisvFarYuIcvMtCUtlBwUU16I36 TXoExgX2NWECH9HrmY4uPChsjLHSpiMH6rUMMmS1uuWw39l/AXJQxoMk8g0U1XNS +4rdiWfq9oJnCvoYXEod8HVvdudqrgDg8G+HN945q5LbTSTJ159BOAolBFMZ+lmo Gq5dfIbGNblZeaplgzka0qNz69Q17u4FauI0buPk4GzG59BZmOyuEBA3AOhiLtnZ VIsRpoNPMO0/vVxNcFaycXdHDFDZQLVrYp8rA+g+xIpR5QhKaFmIzjJ3uCgC4Fm2 4KmZ5tA3HBKBQAGeeWX6S8dotdBl8gJCFvWDpIme7XzMgHqOKlWNsCTiIZdLOkZ6 cYDX6qfZ0798A+qLMC8T+L+rT4l18IfvAllqNU1ydNltU5VpXQI= =8+oF -END PGP SIGNATURE End Message ---
Bug#1029127: context: manual has non-free files
Am 18.01.23 um 11:21 schrieb Hilmar Preuße: Do you have a list of these files or do you know how to generate one? grep -r licence=cc-by-nc-sa
Processed: datefudge: 64-bit time_t functions are not implemented/exposed
Processing control commands: > severity -1 serious Bug #1028587 [datefudge] datefudge: 64-bit time_t functions are not implemented/exposed Severity set to 'serious' from 'important' > tags -1 + ftbfs Bug #1028587 [datefudge] datefudge: 64-bit time_t functions are not implemented/exposed Added tag(s) ftbfs. -- 1028587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029127: context: manual has non-free files
Am 18.01.2023 um 10:49 teilte Bastian Germann mit: Hi Bastian, Many of context's manual files contain licence=cc-by-nc-sa which is a non-free license (non-commercial). Please repack to get rid of them. Do you have a list of these files or do you know how to generate one? Thanks, Hilmar -- sigfault
Bug#1026761: marked as done (wreport: FTBFS: dh_install: error: missing files, aborting)
Your message dated Wed, 18 Jan 2023 11:07:21 +0100 with message-id <20230118100721.pb6nvwrb3takg...@enricozini.org> and subject line Fixed with #1026312 has caused the Debian Bug report #1026761, regarding wreport: 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.) -- 1026761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wreport Version: 3.35-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm 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_install > cd obj-x86_64-linux-gnu && DESTDIR=/<>/debian/tmp > LC_ALL=C.UTF-8 ninja install > [1/2] Generating tables/tables_ok with a custom command > [1/2] Installing files. > Installing subdir /<>/doc/examples to > /<>/debian/tmp/usr/share/doc/wreport/examples > Installing /<>/doc/examples/Makefile to > /<>/debian/tmp/usr/share/doc/wreport/examples > Installing /<>/doc/examples/dump.cc to > /<>/debian/tmp/usr/share/doc/wreport/examples > Installing wreport/libwreport.so.3.0.3 to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu > Installing wreport/libwreport.a to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu > Installing src/wrep to /<>/debian/tmp/usr/bin > Installing python/_wreport.cpython-310-x86_64-linux-gnu.so to > /<>/debian/tmp/usr/local/lib/python3.10/dist-packages > Installing doc/libwreport.doxytags to > /<>/debian/tmp/usr/share/doc/wreport > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/structwreport_1_1Tables.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/namespacewreport_1_1sys.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/main_8dox.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/classwreport_1_1tests_1_1FixtureTestCase.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/structwreport_1_1benchmark_1_1Task.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/decoder_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/sys_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/term_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/trace_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/dir_6064b93e6b0242a02ddc580243820560.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/namespacewreport_1_1bulletin.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/style.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/namespacewreport.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/namespacewreport_1_1term.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/structwreport_1_1tests_1_1TestCodec.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/tables_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/classwreport_1_1CrexBulletin.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/structwreport_1_1tests_1_1TestCase.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/dir_fead6d6e0910a8cba3fe878e43ac84a2.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/codetables_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/bitmaps_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/bufr_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing /<>/obj-x86_64-linux-gnu/doc/xml/notes_8h.xml to > /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/classwreport_1_1error__unimplemented.xml > to /<>/debian/tmp/usr/share/doc/wreport/xml > Installing > /<>/obj-x86_64-linux-gnu/doc/xml/structwreport_1_1bufr_1_1Verbose
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 1029122 5f3-3 Bug #1029122 [src:scm] scm: ftbfs on mipsel Marked as found in versions scm/5f3-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029046: Wayland session doesn't get back to life post-suspend
Control: tag -1 help Hi, On Wednesday, 18 January 2023 09:22:03 CET Didier 'OdyX' Raboud wrote: > Control: retitle -1 Thinkpad: amd_pmc module required for on 6.1 for correct > suspend > Le mardi, 17 janvier 2023, 22.53:54 h CET Didier 'OdyX' Raboud a écrit : > > Le mardi, 17 janvier 2023, 15.32:37 h CET Diederik de Haas a écrit : > > > On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote: > > > > This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't > > > > light up", so feel free to close the bug; I'll test if I get the same > > > > symptoms on an unpatched kernel anyway :-) > > > > > > If that issue doesn't occur with the unpatched kernel, could you add > > > your finding to that upstream/forwarded issue? > > ... > > > > All three 6.1 kernels (whether patched or not) don't bring the laptop to > > the suspended state (power led 'breathing', fans off), but it's kept in > > an "on" state (power led on, fans on), from which I found that I *can* > > wake the laptop up by short-pressing the power button; the screens gets > > back to life and show my lockscreen. But from there, I can't move the > > mouse nor do anything else. Alt-SysRq-r + ctrl-alt-f2 give me a tty, but > > any comeback to tty1 only blank (not even a blank screen, just a freeze). > > > > This seems to point to a quite severe regression in amdgpu or other amd- > > related code; I can't suspend-and-resume the laptop anymore on any 6.1 > > kernel, on battery, without anything attached to it. > > > > I'll forward the above findings to the bug you pointed to, hoping it could > > help upstream too! > > OK. I've gone and done this: > https://gitlab.freedesktop.org/drm/amd/-/issues/2171#note_1727281 Awesome, thanks. > It turns out to get suspend to work, the `amd_pmc` module needs to be > enabled (_AND_ the BIOS needs to have the "Sleep State" toggled to Windows > (from Linux). > > I _think_ Debian should make sure amd_pmc is loaded on (all?) modern AMD > laptops. I have no idea (yet) what the mechanism to make this happen is > though. Due to https://bugs.debian.org/992832 the AMD_PMC module got enabled and I and IIUC you too, verified that it is present in the kernel. I agree it should be auto-loaded, but I don't know why that didn't happen. Tagging this bug with 'help' to request the help from ppl who know more about this then I do. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1029046: Wayland session doesn't get back to life post-suspend
Processing control commands: > tag -1 help Bug #1029046 [src:linux] Thinkpad: amd_pmc module required for on 6.1 for correct suspend Added tag(s) help. -- 1029046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1028688 to python-zeroconf, reassign 1028813 to python-zeroconf ..., affects 1028606
Processing commands for cont...@bugs.debian.org:
> reassign 1028688 python-zeroconf
Bug #1028688 [src:pychromecast] pychromecast: FTBFS: ModuleNotFoundError: No
module named 'async_timeout'
Bug reassigned from package 'src:pychromecast' to 'python-zeroconf'.
No longer marked as found in versions pychromecast/9.4.0-2.
Ignoring request to alter fixed versions of bug #1028688 to the same values
previously set
> reassign 1028813 python-zeroconf
Bug #1028813 [src:nyx] nyx: FTBFS: AttributeError: module 'inspect' has no
attribute 'getargspec'
Bug reassigned from package 'src:nyx' to 'python-zeroconf'.
No longer marked as found in versions nyx/2.1.0-2.1.
Ignoring request to alter fixed versions of bug #1028813 to the same values
previously set
> forcemerge 1028606 1028688 1028813
Bug #1028606 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-zeroconf: Explicitly depend on python3-async-timeout.
Bug #1028688 [python-zeroconf] pychromecast: FTBFS: ModuleNotFoundError: No
module named 'async_timeout'
Severity set to 'normal' from 'serious'
Marked Bug as done
Marked as fixed in versions python-zeroconf/0.47.1-2.
Added tag(s) patch, bookworm, and sid.
Bug #1028606 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-zeroconf: Explicitly depend on python3-async-timeout.
Added tag(s) sid, ftbfs, and bookworm.
Bug #1028813 [python-zeroconf] nyx: FTBFS: AttributeError: module 'inspect' has
no attribute 'getargspec'
Severity set to 'normal' from 'serious'
Marked Bug as done
Marked as fixed in versions python-zeroconf/0.47.1-2.
Added tag(s) patch.
Merged 1028606 1028688 1028813
> affects 1028606 src:pychromecast src:nyx
Bug #1028606 {Done: YOKOTA Hiroshi } [python-zeroconf]
python-zeroconf: Explicitly depend on python3-async-timeout.
Bug #1028688 {Done: YOKOTA Hiroshi } [python-zeroconf]
pychromecast: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
Bug #1028813 {Done: YOKOTA Hiroshi } [python-zeroconf]
nyx: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Added indication that 1028606 affects src:pychromecast and src:nyx
Added indication that 1028688 affects src:pychromecast and src:nyx
Added indication that 1028813 affects src:pychromecast and src:nyx
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028606
1028688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028688
1028813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029073: marked as done (veusz: autopkgtest failure with Numpy 1.24)
Your message dated Wed, 18 Jan 2023 09:52:22 +
with message-id
and subject line Bug#1029073: fixed in veusz 3.5.3-2
has caused the Debian Bug report #1029073,
regarding veusz: autopkgtest failure with Numpy 1.24
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.)
--
1029073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: veusz
Version: 3.5.3-1
Severity: serious
Tags: upstream patch
Justification: autopkgtest failure
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24
Dear Maintainer,
The autopkgtest of your package fail with Numpy 1.24:
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hcokq11r/downtmp/build.caK/src/tests/runselftest.py",
line 320, in
runTests(
File
"/tmp/autopkgtest-lxc.hcokq11r/downtmp/build.caK/src/tests/runselftest.py",
line 247, in runTests
renderVszTest(infile, outfile, test_saves=test_saves,
File
"/tmp/autopkgtest-lxc.hcokq11r/downtmp/build.caK/src/tests/runselftest.py",
line 185, in renderVszTest
ifc.Export(outfile)
File "/usr/lib/python3/dist-packages/veusz/document/commandinterface.py",
line 810, in Export
e.add(filename, pages)
File "/usr/lib/python3/dist-packages/veusz/document/export.py", line 453, in
add
self.doc.paintTo(phelper, page)
File "/usr/lib/python3/dist-packages/veusz/document/doc.py", line 369, in
paintTo
self.basewidget.draw(painthelper, page)
File "/usr/lib/python3/dist-packages/veusz/widgets/root.py", line 144, in
draw
page.draw( posn, painthelper )
File "/usr/lib/python3/dist-packages/veusz/widgets/page.py", line 336, in
draw
axisdependhelper.findAxisRanges()
File "/usr/lib/python3/dist-packages/veusz/widgets/page.py", line 271, in
findAxisRanges
self.processDepends()
File "/usr/lib/python3/dist-packages/veusz/widgets/page.py", line 258, in
processDepends
self.processWidgetDeps(dep)
File "/usr/lib/python3/dist-packages/veusz/widgets/page.py", line 229, in
processWidgetDeps
self._updateRangeFromPlotter(widget, widgetd, widgetd_dep)
File "/usr/lib/python3/dist-packages/veusz/widgets/page.py", line 217, in
_updateRangeFromPlotter
plotter.getRange(axis, plotterdep, self.ranges[axis])
File "/usr/lib/python3/dist-packages/veusz/widgets/point.py", line 547, in
getRange
if data:
File "/usr/lib/python3/dist-packages/veusz/datasets/base.py", line 153, in
__len__
return len(self.data)
File "/usr/lib/python3/dist-packages/veusz/datasets/plugin.py", line 110, in
lambda self: self.getPluginData('data'),
File "/usr/lib/python3/dist-packages/veusz/datasets/plugin.py", line 33, in
getPluginData
self.pluginmanager.update()
File "/usr/lib/python3/dist-packages/veusz/plugins/datasetplugin.py", line
464, in update
self.plugin.updateDatasets(self.fields, self.helper)
File "/usr/lib/python3/dist-packages/veusz/plugins/datasetplugin.py", line
1033, in updateDatasets
anyfinite = N.zeros(maxlength, dtype=N.bool)
File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 284, in
__getattr__
raise AttributeError("module {!r} has no attribute "
AttributeError: module 'numpy' has no attribute 'bool'. Did you mean: 'bool_'?
https://ci.debian.net/data/autopkgtest/testing/amd64/v/veusz/30472445/log.gz
A patch for this has been committed in git:
https://salsa.debian.org/science-team/veusz/-/commit/9ad531101e6fc08852759ce537a85126d7fe4905
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
Source: veusz
Source-Version: 3.5.3-2
Done: Dmitry Shachnev
We believe that the bug you reported is fixed in the latest version of
veusz, 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 1029...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated veusz 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, 18 Jan 2023 13:33:57 +0400
Source: veusz
Architecture: source
Version: 3.5.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Dmitry Shachne
Bug#1028691: dask.distributed: FTBFS: unsatisfiable build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc
On 1/18/23 08:38, Sebastiaan Couwenberg wrote: python-numpy-doc has been dropped from the build dependencies in git, but the package FTBFS due to test failures. Those might be fixed in a new upstream release, but that may introduce regressions in its rdeps. To workaround the two failing tests a patch has been added to mark them as xfail. The package now builds successfully, but needs more work before I'd be comfortable uploading it. Anyone else is free to upload it instead. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1029127: context: manual has non-free files
Source: context Severity: serious Version: 2021.03.05.20220211-1 Many of context's manual files contain licence=cc-by-nc-sa which is a non-free license (non-commercial). Please repack to get rid of them.
Bug#1029073: veusz: autopkgtest failure with Numpy 1.24
Hi Bas and Jeremy! On Tue, Jan 17, 2023 at 01:40:47PM +0100, Bas Couwenberg wrote: > The autopkgtest of your package fail with Numpy 1.24: > > [...] > AttributeError: module 'numpy' has no attribute 'bool'. Did you mean: > 'bool_'? > > https://ci.debian.net/data/autopkgtest/testing/amd64/v/veusz/30472445/log.gz > > A patch for this has been committed in git: > > > https://salsa.debian.org/science-team/veusz/-/commit/9ad531101e6fc08852759ce537a85126d7fe4905 I went ahead and uploaded this, because the autopkgtest regression was blocking Qt 5.15.8 migration to testing. Thanks for the patch! -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1026503: libembperl-perl: FTBFS: Expected 6 more error(s) in logfile, tagging 1026503
Hi, Axel Beckert wrote: > > cat: test/tmp/httpd.pid: No such file or directory > > Just a short note: That last line is a red herring. It's just a follow > up error when the test suite tries to run the already no more running > httpd: > > test.pl:system "kill `cat $tmppath/httpd.pid` 2> /dev/null" if ($EPHTTPD > ne '' && !$opt_nokill) ; I looked a bit deeper into it, but didn't yet understand the issue fully yet. Not forgotten, but I will only continue on it in the next days, once I'm happy with Lintian's state again. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
