Bug#1061366: python3.12: Python3.12 segfaults on python-xarray testsuite
Package: python3.12 Version: 3.12.1-2 Severity: serious Justification: 4 X-Debbugs-Cc: debian-pyt...@lists.debian.org Python3.12 segfaults on the unittest suite for python-xarray (2024.01.0, head of tree in debian/latest) Unfortunately I cannot get a core dump yet to be more specific; this is on arm64 at least. -- System Information: Debian Release: 12.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-17-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: bug 1060898 is forwarded to https://github.com/linux-apfs/linux-apfs-rw/pull/60
Processing commands for cont...@bugs.debian.org:
> forwarded 1060898 https://github.com/linux-apfs/linux-apfs-rw/pull/60
Bug #1060898 {Done: Gürkan Myczko } [apfs-dkms] apfs-dkms:
fails to build module: super.c:17:10: fatal error: version.h: No such file or
directory
Set Bug forwarded-to-address to
'https://github.com/linux-apfs/linux-apfs-rw/pull/60'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1061362: kitty: multi-key sequences do not abort when pressing an unknown key, waits indefinitely
Package: kitty Version: 0.32.0-1 Severity: serious Tags: upstream patch Forwarded: https://github.com/kovidgoyal/kitty/issues/7022 kitty 0.32.0 introduces a new regression where multi-key sequences do not abort when pressing an unknown key, but instead kitty waits indefinitely. https://github.com/kovidgoyal/kitty/issues/7022 Fixed in: https://github.com/kovidgoyal/kitty/commit/20e43a3 The purpose of this bug is to block 0.32.0 from migrating to testing. Kind regards, Maytham signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#1061341: cyrus-common: identified for time_t transition but no ABI in shlibs
Processing control commands: > tags -1 + moreinfo Bug #1061341 [cyrus-common] cyrus-common: identified for time_t transition but no ABI in shlibs Added tag(s) moreinfo. -- 1061341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061341: cyrus-common: identified for time_t transition but no ABI in shlibs
Control: tags -1 + moreinfo On 1/23/24 00:43, Steve Langasek wrote: Package: cyrus-common Version: 3.8.1-1 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Dear maintainers, Analysis of the archive for the 64-bit time_t transition[0][1] identifies cyrus-common as an affected package, on the basis that the headers could not be compiled and analyzed out of the box using abi-compliance-checker[2], so we have to assume it's affected. However, cyrus-commons's shlibs file declares a dependency on a library package name that contains no ABI information: Hi, according to https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/cyrus-dev/base/log.txt , this issue looks like a false-positive: test failed because of C error, not bad report Am I right here ? Best regards, Xavier
Bug#1061358: gnumeric: identified for time_t transition but no ABI in shlibs
Package: gnumeric Version: 1.12.56-2 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Hi Dmitry, Analysis of the archive for the 64-bit time_t transition[0][1] identifies gnumeric as an affected package, on the basis that the headers could not be compiled and analyzed out of the box using abi-compliance-checker[2], so we have to assume it's affected. However, gnumeric's shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libspreadsheet 1.12.56 gnumeric (>= 1.12.56) $ It is therefore not obvious that we should rename the package to 'gnumeric-t64' as part of this transition. Looking at the archive, there are packages built from separate source packages which depend on this library: both libgcu0v5 from gnome-chemistry-utils, and also gir1.2-gnumeric from gnumeric source whose only dependency on gnumeric is via the shlibs, rather than being a strict versioned dependency. Since there is no self-evident thing to do with the library package name here, we will not be handling this package as part of the mass NMUs. Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures will result in ABI skew and may result in broken behavior. Thanks, -- 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 [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html [2] https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/gnumeric/base/log.txt signature.asc Description: PGP signature
Bug#1052376: lxpanel: no longer obeys its geometry settings
On Thu, 21 Sep 2023 09:26:30 +0200 Francesco Poli wrote: > On Thu, 21 Sep 2023 08:49:04 +0200 Francesco Poli (wintermute) wrote: > > > Downgrading/reinstalling the following packages: > > > > libwnck-common (2.30.7-6) > > libwnck22 (2.30.7-6+b1) > > libkeybinder0 (0.3.1-2.1) > > libfm4 (1.3.2-1) > > libfm-gtk4 (1.3.2-1) > > lxpanel-data (0.10.1-2) ... > > lxpanel (0.10.1-2) > > > > is enough to restore the normal (sane) behavior. > > I also had to downgrade the following package: > > libfm-modules (1.3.2-1) > > and to purge the following packages: > > libfm-gtk3-4 > libkeybinder-3.0-0 > libwnck-3-0 > libwnck-3-common Hello, just a gentle ping about this bug report: any progress? I see that several other users are experiencing the same issues I reported. Is there any plan to fix them soon? Thanks for your time and dedication! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpP64E14hfkc.pgp Description: PGP signature
Bug#966115: marked as done (discodos: /usr/bin/disco is already shipped by mono-devel)
Your message dated Mon, 22 Jan 2024 22:19:25 + with message-id and subject line Bug#966115: fixed in discodos 1.1-1 has caused the Debian Bug report #966115, regarding discodos: /usr/bin/disco is already shipped by mono-devel 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.) -- 966115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: discodos Version: 1.0~rc2-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package discodos. Preparing to unpack .../43-discodos_1.0~rc2-1_all.deb ... Unpacking discodos (1.0~rc2-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-ke5XNX/43-discodos_1.0~rc2-1_all.deb (--unpack): trying to overwrite '/usr/bin/disco', which is also in package mono-devel 6.8.0.105+dfsg-3 Errors were encountered while processing: /tmp/apt-dpkg-install-ke5XNX/43-discodos_1.0~rc2-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/disco usr/share/man/man1/disco.1.gz Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html mono-devel=6.8.0.105+dfsg-3_discodos=1.0~rc2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: discodos Source-Version: 1.1-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of discodos, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated discodos 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: Mon, 22 Jan 2024 22:57:34 +0100 Source: discodos Architecture: source Version: 1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Alexandre Detiste Closes: 966115 Changes: discodos (1.1-1) unstable; urgency=medium . * Team Upload * New upstream version 1.1 * add gbp.conf * rename script 'disco' -> 'discodos' (Closes: #966115) (LP: #1978724, LP: #1928414) . [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Set upstream metadata fields: Bug-Database. * Update standards version to 4.6.2, no changes needed. Checksums-Sha1: d6f073bd78142b8a6fb9716966d29b163188d16b 1994 discodos_1.1-1.dsc bc34a66840d8ecea55fd6e85ac7a886e601e5988 10213387 discodos_1.1.orig.tar.gz 596ce0b198f460f08a58572ef1e43c22a744b1d5 2820 discodos_1.1-1.debian.tar.xz e1e24f45fced1c2af2d1648033bfca4f82d9f237 6924 discodos_1.1-1_source.buildinfo Checksums-Sha256: a93aadbe1852b117efda78aa559a407f2b9bee0304a7bc49f1b8e37cd7a7117f 1994 discodos_1.1-1.dsc b8ea40202c2e63cad87a60dc1f03117234006e54fbc9af27caf5d8bc406a265e 10213387 discodos_1.1.orig.tar.gz c0c9260f215268e112270d17a1f2786fd37571dc13256143ef1c090a50f2cd33 2820 discodos_1.1-1.debian.tar.xz e079a17210267ea34ba64342a1a49d27a3e089ee51da0027761e041d88816a5f 6924 discodos_1.1-1_source.buildinfo Files: 680ac35270e441258734a6d2d9cbacc8 1994 sound optional discodos_1.1-1.dsc 44fb689c48c359a0d5a3e4e9525ed9a2 10213387 sound optional
Bug#1057937: marked as done (pkcs11-provider: FTBFS: failing tests)
Your message dated Mon, 22 Jan 2024 22:04:19 +
with message-id
and subject line Bug#1057937: fixed in pkcs11-provider 0.3-1
has caused the Debian Bug report #1057937,
regarding pkcs11-provider: FTBFS: failing tests
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.)
--
1057937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pkcs11-provider
Version: 0.2+g20231107-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
aclocal: warning: couldn't open directory 'm4': No such file or directory
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:13: installing './ar-lib'
configure.ac:12: installing './compile'
configure.ac:14: installing './config.guess'
configure.ac:14: installing './config.sub'
configure.ac:8: installing './install-sh'
configure.ac:8: installing './missing'
src/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking for ar... ar
checking the archiver (ar) interface... ar
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format...
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
Processed: Bug#966115 marked as pending in discodos
Processing control commands: > tag -1 pending Bug #966115 [discodos] discodos: /usr/bin/disco is already shipped by mono-devel Added tag(s) pending. -- 966115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966115: marked as pending in discodos
Control: tag -1 pending Hello, Bug #966115 in discodos 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/python-team/packages/discodos/-/commit/3e92a5f203d2a3c5692a652e4abb198b1f1af437 rename script 'disco' -> 'discodo' (Closes: #966115) (this message was generated automatically) -- Greetings https://bugs.debian.org/966115
Bug#1061346: geany: identified for time_t transition but no ABI in shlibs
Package: geany Version: 2.0-1 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Dear maintainers, Analysis of the archive for the 64-bit time_t transition[0][1] identifies geany as an affected package, on the basis that the headers could not be compiled and analyzed out of the box using abi-compliance-checker[2], so we have to assume it's affected. However, geany's shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libgeany 0 geany (>= 2.0) $ It is therefore not obvious that we should rename the package to 'geany-t64' as part of this transition. Looking at the archive, there are packages built from the separate geany-plugins source package which depend on this library. Since there is no self-evident thing to do with the library package name here, we will not be handling this package as part of the mass NMUs. Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures will result in ABI skew and may result in broken behavior. Thanks, -- 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 [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html [2] https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/geany-common/base/log.txt signature.asc Description: PGP signature
Bug#1061345: lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have an undeclared file conflict
Package: libstdc++6-14-dbg,libx32stdc++6-14-dbg,lib32stdc++6-14-dbg Version: 14-20240121-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + lib32stdc++6-13-dbg libstdc++6-13-dbg libx32stdc++6-13-dbg lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib32/debug/libstdc++.a * /usr/lib32/debug/libstdc++.so * /usr/lib32/debug/libstdc++.so.6 * /usr/lib32/debug/libstdc++exp.a * /usr/lib32/debug/libstdc++fs.a are contained in the packages * lib32stdc++6-13-dbg/13.2.0-10 as present in trixie|unstable * lib32stdc++6-14-dbg/14-20240121-1 as present in experimental The files * /usr/lib/x86_64-linux-gnu/debug/libstdc++.a * /usr/lib/x86_64-linux-gnu/debug/libstdc++.so * /usr/lib/x86_64-linux-gnu/debug/libstdc++.so.6 * /usr/lib/x86_64-linux-gnu/debug/libstdc++exp.a * /usr/lib/x86_64-linux-gnu/debug/libstdc++fs.a are contained in the packages * libstdc++6-13-dbg/13.2.0-10 as present in trixie|unstable * libstdc++6-14-dbg/14-20240121-1 as present in experimental The files * /usr/libx32/debug/libstdc++.a * /usr/libx32/debug/libstdc++.so * /usr/libx32/debug/libstdc++.so.6 * /usr/libx32/debug/libstdc++exp.a * /usr/libx32/debug/libstdc++fs.a are contained in the packages * libx32stdc++6-13-dbg/13.2.0-10 as present in trixie|unstable * libx32stdc++6-14-dbg/14-20240121-1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
Processed: lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have an undeclared file conflict
Processing control commands: > affects -1 + lib32stdc++6-13-dbg libstdc++6-13-dbg libx32stdc++6-13-dbg Bug #1061345 [libstdc++6-14-dbg,libx32stdc++6-14-dbg,lib32stdc++6-14-dbg] lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have an undeclared file conflict Warning: Unknown package 'libstdc++6-14-dbg' Warning: Unknown package 'libx32stdc++6-14-dbg' Warning: Unknown package 'lib32stdc++6-14-dbg' Added indication that 1061345 affects lib32stdc++6-13-dbg, libstdc++6-13-dbg, and libx32stdc++6-13-dbg Warning: Unknown package 'libstdc++6-14-dbg' Warning: Unknown package 'libx32stdc++6-14-dbg' Warning: Unknown package 'lib32stdc++6-14-dbg' -- 1061345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058198: marked as pending in autopep8
Control: tag -1 pending Hello, Bug #1058198 in autopep8 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/python-team/packages/autopep8/-/commit/4872f13d07c9dff7ae5b3d1ab5a82c7e244a8a47 Patch: Python 3.12 support. (Closes: #1058198) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058198
Processed: Bug#1058198 marked as pending in autopep8
Processing control commands: > tag -1 pending Bug #1058198 [src:autopep8] autopep8: FTBFS: AssertionError: 'def tmp(g):\n g(4)))\n\nif not True:\npass\npass\n' != 'def tmp(g):\n g(4)))\n\n if not True:\npass\npass\n' Added tag(s) pending. -- 1058198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058179: marked as done (python-cliapp: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Mon, 22 Jan 2024 21:20:16 +
with message-id
and subject line Bug#1058179: fixed in python-cliapp 1.20180812.1-5
has caused the Debian Bug report #1058179,
regarding python-cliapp: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)
--
1058179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cliapp
Version: 1.20180812.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with=python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 22, in
> import cliapp
> File "/<>/cliapp/__init__.py", line 45, in
> from .pluginmgr import PluginManager
> File "/<>/cliapp/pluginmgr.py", line 29, in
> import imp
> ModuleNotFoundError: No module named 'imp'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-cliapp_1.20180812.1-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-cliapp
Source-Version: 1.20180812.1-5
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-cliapp, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated python-cliapp 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: Mon, 22 Jan 2024 17:04:45 -0400
Source: python-cliapp
Architecture: source
Version: 1.20180812.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Stefano Rivera
Closes: 1058179
Changes:
python-cliapp (1.20180812.1-5) unstable; urgency=medium
.
* QA upload.
* Patch: Port plugin loading to importlib for Python 3.12 support.
(Closes: #1058179)
Checksums-Sha1:
8a7b554c05b6a1eac2101dd3dcc6fde284c390b2 1345 python-cliapp_1.20180812.1-5.dsc
812f1e384ecc4f22c86fbae6c8ed04d1260d29d9 5216
python-cliapp_1.20180812.1-5.debian.tar.xz
6ff7ee1079b1a4d23f660e3d681c97f1100945a7 6434
python-cliapp_1.20180812.1-5_source.buildinfo
Checksums-Sha256:
58ba3a321f469b15612af774859b418453203f2b70d2d4798aacc2c8b0d72f0c 1345
python-cliapp_1.20180812.1-5.dsc
90c356b219340e58f9006190ce8e5d5f64b99d656110d6edcf9aaa5747cd9bed 5216
python-cliapp_1.20180812.1-5.debian.tar.xz
52dd5f6a315a79dcd6f88dbe96e8ba581f82da282c30a7bd466ca682e89546af 6434
python-cliapp_1.20180812.1-5_source.buildinfo
Files:
67b23c30fb385bd97895b8259f42a03d 1345 python optional
python-cliapp_1.20180812.1-5.dsc
572df96dcdbd935c443aced7c4a5e2b8 5216 python optional
python-cliapp_1.20180812.1-5.debian.tar.xz
Bug#1057484: marked as done (pelican: "ModuleNotFoundError: No module named 'watchfiles")
Your message dated Mon, 22 Jan 2024 21:06:22 + with message-id and subject line Bug#1057484: fixed in pelican 4.9.1+dfsg-3 has caused the Debian Bug report #1057484, regarding pelican: "ModuleNotFoundError: No module named 'watchfiles" 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.) -- 1057484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pelican Version: 4.9.1+dfsg-1 Severity: critical Dear maintainers, Running `pelican content` to generate HTML files, I get the following crash: Traceback (most recent call last): File "/usr/bin/pelican", line 5, in from pelican.__main__ import main File "/usr/lib/python3/dist-packages/pelican/__init__.py", line 24, in from pelican.generators import ( File "/usr/lib/python3/dist-packages/pelican/generators.py", line 20, in from pelican.cache import FileStampDataCacher File "/usr/lib/python3/dist-packages/pelican/cache.py", line 6, in from pelican.utils import mkdir_p File "/usr/lib/python3/dist-packages/pelican/utils.py", line 28, in import watchfiles ModuleNotFoundError: No module named 'watchfiles' It seems this library isn't currently packaged in Debian? Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ --- End Message --- --- Begin Message --- Source: pelican Source-Version: 4.9.1+dfsg-3 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of pelican, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated pelican 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: Mon, 22 Jan 2024 15:22:43 -0500 Source: pelican Architecture: source Version: 4.9.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Louis-Philippe Véronneau Closes: 1057484 Changes: pelican (4.9.1+dfsg-3) unstable; urgency=medium . * Team upload. * d/control: add needed B-D on python3-watchfiles. (Closes: #1057484) Checksums-Sha1: f984db587fe0971812afefba1130dbf6f8ab69a1 1758 pelican_4.9.1+dfsg-3.dsc 5766770b11770091e9b478f67ceccd6c5456e5a0 19164 pelican_4.9.1+dfsg-3.debian.tar.xz 4ccd61572f4a151754f5a60a777562ade8782439 8457 pelican_4.9.1+dfsg-3_amd64.buildinfo Checksums-Sha256: c60ac306e17d11e9fe6a790721c4baf01e14439795c1f511fb7e1db65c2fe44d 1758 pelican_4.9.1+dfsg-3.dsc aaba8f36102804fa3684a1ab9f134a32e8c8a6465901e264d41a30c74fa36915 19164 pelican_4.9.1+dfsg-3.debian.tar.xz ce1e1f3b6f71401fd5d0a58f8dcc2ec424b1c286971224052498579582e6ab78 8457 pelican_4.9.1+dfsg-3_amd64.buildinfo Files: 5decd36d0bf5c331b601af5b023d371a 1758 web optional pelican_4.9.1+dfsg-3.dsc 8bdb6b022e2b3a512e29020f338075b0 19164 web optional pelican_4.9.1+dfsg-3.debian.tar.xz 4c35a5984495c5fd128f065862e031b9 8457 web optional pelican_4.9.1+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTKp0AHB6gWsCAvw830JXpQshz6hQUCZa7SEgAKCRD0JXpQshz6 hVhnAP9ptrCm8Wg1pWDBdy5mZ/HWH8aOPPesgjo5Y1De66bDTwEAtOVR0Oe/SIgr /4NZbFaWJZzk1EZEqTgeUZrmzAKqaQs= =X9ee -END PGP SIGNATURE End Message ---
Bug#1061315: inn2 ftbfs with Python 3.12 as the default
On 22.01.24 21:31, Julien ÉLIE wrote: Hi Matthias, Package: src:inn2 Version: 2.7.2~20231223-1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: [...] checking for Python.h... yes checking for Py_Initialize... no configure: error: in `/<>/build': configure: error: unable to link with Python library See `config.log' for more details Could you put the end of the config.log file? (the part showing the failure to find Py_Initialize) sorry, just reporting the issue as found on the Ubuntu buildds: https://launchpad.net/ubuntu/+source/inn2/2.7.2~20231223-1build2
Bug#1061344: emboss-lib: identified for time_t transition but no ABI in shlibs
Package: emboss-lib Version: 6.6.0+dfsg-12 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Dear maintainers, Analysis of the archive for the 64-bit time_t transition[0][1] identifies emboss-lib as an affected package, on the basis that the headers could not be compiled and analyzed out of the box using abi-compliance-checker[2], so we have to assume it's affected. However, emboss-lib's shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libacd 6 emboss-lib (>= 6.6.0+dfsg) libajax 6 emboss-lib (>= 6.6.0+dfsg) libajaxdb 6 emboss-lib (>= 6.6.0+dfsg) libajaxg 6 emboss-lib (>= 6.6.0+dfsg) libensembl 6 emboss-lib (>= 6.6.0+dfsg) libepcre 7 emboss-lib (>= 6.6.0+dfsg) libeplplot 3 emboss-lib (>= 6.6.0+dfsg) libnucleus 6 emboss-lib (>= 6.6.0+dfsg) $ It is therefore not obvious that we should rename the package to 'emboss-lib-64' as part of this transition. Looking at the archive, there are packages built from separate source packages which depend on these libraries: embassy-domainatrix, embassy-domalign, embassy-domsearch. Since there is no self-evident thing to do with the library package name here, we will not be handling this package as part of the mass NMUs. Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures will result in ABI skew and may result in broken behavior. Thanks, -- 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 [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html [2] https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/emboss-lib/base/log.txt signature.asc Description: PGP signature
Processed: unattended-upgrades: diff for NMU version 2.9.1+nmu4
Processing control commands: > tags 1058172 + patch Bug #1058172 [src:unattended-upgrades] unattended-upgrades: FTBFS: AssertionError: 1 != 0 Added tag(s) patch. > tags 1058172 + pending Bug #1058172 [src:unattended-upgrades] unattended-upgrades: FTBFS: AssertionError: 1 != 0 Added tag(s) pending. -- 1058172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058172: unattended-upgrades: diff for NMU version 2.9.1+nmu4
Control: tags 1058172 + patch
Control: tags 1058172 + pending
Dear maintainer,
I've prepared an NMU for unattended-upgrades (versioned as 2.9.1+nmu4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
Stefano
diff -Nru unattended-upgrades-2.9.1+nmu3/debian/changelog unattended-upgrades-2.9.1+nmu4/debian/changelog
--- unattended-upgrades-2.9.1+nmu3/debian/changelog 2022-12-31 16:59:00.0 -0400
+++ unattended-upgrades-2.9.1+nmu4/debian/changelog 2024-01-22 16:11:59.0 -0400
@@ -1,3 +1,11 @@
+unattended-upgrades (2.9.1+nmu4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Don't run pyflakes, it dropped support for type comments.
+(Closes: #1058172)
+
+ -- Stefano Rivera Mon, 22 Jan 2024 16:11:59 -0400
+
unattended-upgrades (2.9.1+nmu3) unstable; urgency=medium
* test: don't confuse -dbg and -unsigned with current running kernel
diff -Nru unattended-upgrades-2.9.1+nmu3/test/test_pyflakes.py unattended-upgrades-2.9.1+nmu4/test/test_pyflakes.py
--- unattended-upgrades-2.9.1+nmu3/test/test_pyflakes.py 2022-12-31 16:59:00.0 -0400
+++ unattended-upgrades-2.9.1+nmu4/test/test_pyflakes.py 2024-01-22 16:11:59.0 -0400
@@ -7,6 +7,8 @@
""" ensure that the tree is pyflakes clean """
def test_pyflakes_clean(self):
+# https://github.com/PyCQA/pyflakes/issues/683
+self.skipTest("not clean, pyflakes no longer supports type comments")
top_src_dir = os.path.join(os.path.dirname(__file__), "..")
targets = [
top_src_dir,
Processed: notfixed 1058032 in 1.14.1-6
Processing commands for cont...@bugs.debian.org:
> notfixed 1058032 1.14.1-6
Bug #1058032 {Done: Stefano Rivera }
[src:python-grpc-tools] python-grpc-tools: FTBFS with Python 3.12
No longer marked as fixed in versions 1.14.1-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1058173 is forwarded to https://github.com/magic-wormhole/magic-wormhole-mailbox-server/pull/42
Processing commands for cont...@bugs.debian.org: > forwarded 1058173 > https://github.com/magic-wormhole/magic-wormhole-mailbox-server/pull/42 Bug #1058173 [src:magic-wormhole-mailbox-server] magic-wormhole-mailbox-server: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? Set Bug forwarded-to-address to 'https://github.com/magic-wormhole/magic-wormhole-mailbox-server/pull/42'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061341: cyrus-common: identified for time_t transition but no ABI in shlibs
Package: cyrus-common
Version: 3.8.1-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainers,
Analysis of the archive for the 64-bit time_t transition[0][1] identifies
cyrus-common as an affected package, on the basis that the headers could not
be compiled and analyzed out of the box using abi-compliance-checker[2], so
we have to assume it's affected.
However, cyrus-commons's shlibs file declares a dependency on a library
package name that contains no ABI information:
$ cat DEBIAN/shlibs
libcyrus 0 cyrus-common (>= 3.8.1)
libcyrus_imap 0 cyrus-common (>= 3.8.1)
libcyrus_min 0 cyrus-common (>= 3.8.1)
libcyrus_sieve 0 cyrus-common (>= 3.8.1)
$
It is therefore not obvious that we should rename the package to
'cyrus-common-t64' as part of this transition.
Looking at the archive, there are packages that depend on these libraries,
cyrus-admin and cyrus-clients. Despite being built from the same source
package, they do not have a strict versioned dependency on cyrus-common but
instead use the shlibs.
Since there is no self-evident thing to do with the library package name
here, we will not be handling this package as part of the mass NMUs.
Instead I am filing a serious bug because partial upgrades from bookworm to
trixie on 32-bit architectures (upgrading cyrus-common without also
upgrading cyrus-{admin,clients}) will result in ABI skew and may result in
broken behavior.
Thanks,
--
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
[0] https://wiki.debian.org/ReleaseGoals/64bit-time
[1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
[2]
https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/cyrus-dev/base/log.txt
signature.asc
Description: PGP signature
Processed: Bug#1057484 marked as pending in pelican
Processing control commands: > tag -1 pending Bug #1057484 [pelican] pelican: "ModuleNotFoundError: No module named 'watchfiles" Added tag(s) pending. -- 1057484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057484: marked as pending in pelican
Control: tag -1 pending Hello, Bug #1057484 in pelican 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/python-team/packages/pelican/-/commit/3fba8714e054efe2ba1d9982bc9225bb7c9d3f44 d/control: add needed B-D on python3-watchfiles. (Closes: #1057484) (this message was generated automatically) -- Greetings https://bugs.debian.org/1057484
Bug#1061315: inn2 ftbfs with Python 3.12 as the default
Hi Matthias, Package: src:inn2 Version: 2.7.2~20231223-1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: [...] checking for Python.h... yes checking for Py_Initialize... no configure: error: in `/<>/build': configure: error: unable to link with Python library See `config.log' for more details Could you put the end of the config.log file? (the part showing the failure to find Py_Initialize) Maybe a problem of Python not in the path? FWIW, I do not run trixie, but building INN with a downloaded version of Python 3.12 on bookworm works for me: checking for flags to link with Python... -L/home/news/work/py3.12.1/lib -lpython3.12 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic checking Python.h usability... yes checking Python.h presence... yes checking for Python.h... yes checking for Py_Initialize... yes configure:15028: checking for Py_Initialize configure:15028: gcc -o conftest -g -O2 -I/home/news/work/py3.12.1/include/python3.12 conftest.c -L/home/news/work/py3.12.1/lib -lpython3.12 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic >&5 -- Julien ÉLIE « L'éternité, c'est long, surtout vers la fin. » (Woody Allen)
Bug#1061339: numpy_1.26.3-1_s390x-buildd.changes REJECTED
Source: numpy Version: 1.26.3-1 Severity: serious On 2024-01-22 08:24, Debian FTP Masters wrote: > > > python3-numpy_1.26.3-1_s390x.deb: has 876 file(s) with a timestamp too far in > the past: > usr/lib/python3/dist-packages/numpy/LICENSE.txt (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/__init__.cython-30.pxd (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/__init__.pxd (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/__init__.py (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/__init__.pyi (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_core/__init__.py (Thu > Jan 1 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_core/_dtype.py > (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_core/_dtype_ctypes.py (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_core/_internal.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_core/_multiarray_umath.py (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_core/multiarray.py (Thu > Jan 1 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_core/umath.py > (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_distributor_init.py (Thu Jan 1 00:00:00 > 1970) usr/lib/python3/dist-packages/numpy/_globals.py (Thu Jan 1 00:00:00 > 1970) usr/lib/python3/dist-packages/numpy/_pyinstaller/__init__.py (Thu Jan > 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_pyinstaller/hook-numpy.py (Thu Jan 1 > 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_pyinstaller/pyinstaller-smoke.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_pyinstaller/test_pyinstaller.py (Thu Jan > 1 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_pytesttester.py (Thu > Jan 1 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_pytesttester.pyi > (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_typing/__init__.py (Thu Jan 1 00:00:00 > 1970) usr/lib/python3/dist-packages/numpy/_typing/_add_docstring.py (Thu Jan > 1 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_typing/_array_like.py > (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_typing/_callable.pyi (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_typing/_char_codes.py > (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_typing/_dtype_like.py (Thu Jan 1 > 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_typing/_extended_precision.py (Thu Jan > 1 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_typing/_nbit.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_typing/_nested_sequence.py (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_typing/_scalars.py (Thu > Jan 1 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_typing/_shape.py > (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_typing/_ufunc.pyi (Thu Jan 1 00:00:00 > 1970) usr/lib/python3/dist-packages/numpy/_typing/setup.py (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_utils/__init__.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/_utils/_convertions.py (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_utils/_inspect.py (Thu > Jan 1 00:00:00 1970) usr/lib/python3/dist-packages/numpy/_utils/_pep440.py > (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/__init__.py (Thu Jan 1 > 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_array_object.py (Thu Jan 1 > 00:00:00 1970) usr/lib/python3/dist-packages/numpy/array_api/_constants.py > (Thu Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_creation_functions.py (Thu Jan > 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_data_type_functions.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_dtypes.py (Thu Jan 1 00:00:00 > 1970) > usr/lib/python3/dist-packages/numpy/array_api/_elementwise_functions.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_indexing_functions.py (Thu Jan > 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_manipulation_functions.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_searching_functions.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_set_functions.py (Thu Jan 1 > 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_sorting_functions.py (Thu Jan > 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_statistical_functions.py (Thu > Jan 1 00:00:00 1970) > usr/lib/python3/dist-packages/numpy/array_api/_typing.py (Thu Jan 1 00:00:00 > 1970) usr/lib/python3/dist-packages/numpy/array_api/_utility_functions.py > (Thu Jan 1 00:00:00 1970) >
Bug#1061335: python3-breezy: ships files in `/build`
Package: python3-breezy Version: 3.3.5-1 Severity: serious Hi, python3-breezy ships files in `/build`: +--- | % dpkg-deb -c python3-breezy_3.3.5-1_amd64.deb | head | drwxr-xr-x root/root 0 2024-01-19 23:12 ./ | drwxr-xr-x root/root 0 2024-01-19 23:12 ./build/ | drwxr-xr-x root/root 0 2024-01-19 23:12 ./build/reproducible-path/ | drwxr-xr-x root/root 0 2024-01-19 23:12 ./build/reproducible-path/breezy-3.3.5/ | drwxr-xr-x root/root 0 2024-01-19 23:12 ./build/reproducible-path/breezy-3.3.5/debian/ +--- This is probably not intended. Ansgar
Bug#1058032: marked as done (python-grpc-tools: FTBFS with Python 3.12)
Your message dated Mon, 22 Jan 2024 15:59:37 -0400
with message-id
and subject line Re: Bug#1058032: python-grpc-tools: FTBFS with Python 3.12
has caused the Debian Bug report #1058032,
regarding python-grpc-tools: FTBFS with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-grpc-tools
Version: 1.14.1-6
Severity: serious
Tags: ftbfs sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Hi Maintainer
python-grpc-tools FTBFS [1] with Python 3.12 as a supported version.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://buildd.debian.org/status/package.php?p=python-grpc-tools
grpc_tools/_protoc_compiler.cpp: In function ‘long int
__Pyx_PyInt_As_long(PyObject*)’:
grpc_tools/_protoc_compiler.cpp:2529:55: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
2529 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~
grpc_tools/_protoc_compiler.cpp:2584:55: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
2584 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~
grpc_tools/_protoc_compiler.cpp: In function ‘int
__Pyx_PyInt_As_int(PyObject*)’:
grpc_tools/_protoc_compiler.cpp:2725:55: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
2725 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~
grpc_tools/_protoc_compiler.cpp:2780:55: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
2780 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~~~
grpc_tools/_protoc_compiler.cpp: In function ‘Py_ssize_t
__Pyx_PyIndex_AsSsize_t(PyObject*)’:
grpc_tools/_protoc_compiler.cpp:3231:47: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
3231 | const digit* digits = ((PyLongObject*)b)->ob_digit;
| ^~~~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:395: build: plugin distutils failed with: exit
code=1: /usr/bin/python3.12 setup.py build
--- End Message ---
--- Begin Message ---
Version: 1.14.1-6
It's building again, I guess cython 3 did the trick.
Stefano
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272--- End Message ---
Processed: bug 1058130 is forwarded to https://github.com/Knio/pynmea2/issues/163
Processing commands for cont...@bugs.debian.org: > forwarded 1058130 https://github.com/Knio/pynmea2/issues/163 Bug #1058130 [src:python-nmea2] python-nmea2: FTBFS: ModuleNotFoundError: No module named 'imp' Set Bug forwarded-to-address to 'https://github.com/Knio/pynmea2/issues/163'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1058111 with 1058179
Processing commands for cont...@bugs.debian.org: > block 1058111 with 1058179 Bug #1058111 [src:cmdtest] cmdtest: FTBFS: ModuleNotFoundError: No module named 'imp' 1058111 was not blocked by any bugs. 1058111 was not blocking any bugs. Added blocking bug(s) of 1058111: 1058179 > thanks Stopping processing here. Please contact me if you need assistance. -- 1058111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1058155 marked as pending in keystone
Processing control commands: > tag -1 pending Bug #1058155 [src:keystone] keystone: FTBFS: AttributeError: type object '_PurePosixPath' has no attribute '_from_parts'. Did you mean: '_load_parts'? Added tag(s) pending. -- 1058155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058155: marked as pending in keystone
Control: tag -1 pending Hello, Bug #1058155 in keystone reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/keystone/-/commit/0ae2d51b43b10a7f424ec228b10ea23fc8069e44 * Add Python 3.12 fixes (Closes: #1058155): - py3.12-use-raw-string-to-avoid-warning.patch. - do-not-set-chartset-in-flask-responce.patch. - py3.12-fix-datetime-usage.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1058155
Bug#1061330: calamares: identified for time_t transition but no ABI in shlibs
Package: calamares Version: 3.3.0-1 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Hi Jonathan, Analysis of the archive for the 64-bit time_t transition[0][1] identifies calamares as a package shipping a library whose ABI changes on 32-bit architectures with 64-bit time_t. However, calamares's shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libcalamares 3.3 calamares (>= 3.3.0) libcalamaresui 3.3 calamares (>= 3.3.0) $ It is therefore not obvious that we should rename the package to 'calamares-t64' as part of this transition. Looking at the archive, there are packages built from separate source packages, 'calamares-extensions' and 'calamares-settings-mobian', which depend on this library. Since there is no self-evident thing to do with the library package name here, we will not be handling this package as part of the mass NMUs. Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures (upgrading calamares without also upgrading worker) will result in ABI skew and may result in broken behavior. However, since calamares is an installer, maybe upgrades are a non-issue and all you need is to ensure rebuilds of the three packages in unstable. Thanks, -- 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 [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html signature.asc Description: PGP signature
Bug#1050683: marked as done (pep517: Should not be released with Trixie)
Your message dated Mon, 22 Jan 2024 19:27:25 + with message-id and subject line Bug#1043255: Removed package(s) from unstable has caused the Debian Bug report #1050683, regarding pep517: Should not be released with Trixie 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.) -- 1050683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pep517 Severity: serious Justification: Maintainer opinion This package has been replace by python-pyproject-hooks and should not be in Trixie. Scott K --- End Message --- --- Begin Message --- Version: 0.13.0-2+rm Dear submitter, as the package pep517 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1043255 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1061282: marked as done (libgtk-3-0: gtk crashes when I use a script to turn off the screen)
Your message dated Mon, 22 Jan 2024 19:19:22 + with message-id and subject line Bug#1061282: fixed in gtk+3.0 3.24.40-2 has caused the Debian Bug report #1061282, regarding libgtk-3-0: gtk crashes when I use a script to turn off the screen 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.) -- 1061282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgtk-3-0 Version: 3.24.40-1 Severity: normal Dear Maintainer, i'm a blind user and to save battery life on my laptop, i use a script to turn off the screen. since switching to this version of libgtk-3-0 when i use the script (provided below), my desktop (mate) crashes and i return to the login screen. downgrade to version 3.24.39-2 solves the problem and I can use the script without any problem. in the syslog, I have lots of gtk application crashes one after the other the script is available here on the debian accessibility wiki: https://wiki.debian.org/accessibility sexion screen off and sub seccion x11 log is attached -- System Information: Debian Release: bookworm APT prefers testing APT policy: (500, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_FORCED_RMMOD, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libgtk-3-0 depends on: ii adwaita-icon-theme 45.0-2 ii hicolor-icon-theme 0.17-2 ii libatk-bridge2.0-0 2.50.0-1+b1 ii libatk1.0-0 2.50.0-1+b1 ii libc62.37-13 ii libcairo-gobject21.18.0-1+b1 ii libcairo21.18.0-1+b1 ii libcloudproviders0 0.3.5-1 ii libcolord2 1.4.6-5 ii libcups2 2.4.7-1+b1 ii libepoxy01.5.10-1+b2 ii libfontconfig1 2.14.2-6+b1 ii libfribidi0 1.0.13-3+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 ii libglib2.0-0 2.78.3-1 ii libgtk-3-common 3.24.40-1 ii libharfbuzz0b8.0.1-1+b2 ii libpango-1.0-0 1.51.0+ds-4 ii libpangocairo-1.0-0 1.51.0+ds-4 ii libpangoft2-1.0-01.51.0+ds-4 ii libwayland-client0 1.22.0-2.1 ii libwayland-cursor0 1.22.0-2.1 ii libwayland-egl1 1.22.0-2.1 ii libx11-6 2:1.8.7-1 ii libxcomposite1 1:0.4.5-1 ii libxcursor1 1:1.2.1-1 ii libxdamage1 1:1.1.6-1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxi6 2:1.8-1+b1 ii libxinerama1 2:1.1.4-3 ii libxkbcommon01.6.0-1 ii libxrandr2 2:1.5.2-2+b1 ii shared-mime-info 2.4-1 Versions of packages libgtk-3-0 recommends: pn libgtk-3-bin ii librsvg2-common 2.54.7+dfsg-2 Versions of packages libgtk-3-0 suggests: ii gvfs 1.52.2-1 Versions of packages libgtk-3-0 is related to: pn appmenu-gtk3-module pn fcitx-frontend-gtk3 pn gcin-gtk3-immodule pn gtk-vector-screenshot pn gtk3-engines-xfce pn gtk3-im-libthai pn hime-gtk3-immodule pn ibus-gtk3 pn imhangul-gtk3 pn libcanberra-gtk3-module pn libcaribou-gtk3-module pn libgtk3-nocsd0 pn maliit-inputcontext-gtk3 pn packagekit-gtk3-module pn scim-gtk-immodule pn topmenu-gtk3 pn uim-gtk3 pn uim-gtk3-immodule -- no debconf information Jan 22 05:28:44 jerem-debian kernel: notification-ar[2719]: segfault at 55c83ce50ecd ip 7f674934b4fc sp 7ffc402ad3f0 error 4 in libglib-2.0.so.0.7800.3[7f67492ee000+99000] likely on CPU 3 (core 3, socket 0) Jan 22 05:28:44 jerem-debian kernel: Code: 89 fd 53 48 89 f3 48 83 ec 08 4c 8b 2d 7d 8a 0c 00 eb 10 0f 1f 00 48 89 ee e8 20 5e fe ff 48 85 db 74 29 41 8b 45 00 48 89 df <4a> 8b 1c 23 85 c0 74 e4 31 f6 48 89 ea e8 c2 2b fa ff 48 89 ee 48 Jan 22 05:28:44 jerem-debian kernel: mate-volume-con[2638]: segfault at 55def44d1049 ip 7fa8d5b484fc sp 7fffc2ff7a00 error 4 in libglib-2.0.so.0.7800.3[7fa8d5aeb000+99000] likely on CPU 2 (core 2, socket 0) Jan 22 05:28:44 jerem-debian kernel: Code: 89 fd 53 48 89 f3 48 83 ec 08 4c 8b 2d 7d 8a 0c 00 eb 10 0f 1f 00 48 89 ee e8 20 5e fe ff 48 85 db 74 29 41 8b 45 00 48 89 df <4a> 8b 1c 23 85 c0 74 e4 31 f6 48 89 ea e8 c2 2b fa ff 48 89 ee 48 Jan 22 05:28:44 jerem-debian
Bug#1061282: marked as pending in gtk+3.0
Control: tag -1 pending Hello, Bug #1061282 in gtk+3.0 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/gnome-team/gtk3/-/commit/d267fe9d04d7b7b0e1d4a9ad014ddebffa70e1e7 Cherry-pick 2 commits to fix crash when screen is turned off Closes: #1061282 (this message was generated automatically) -- Greetings https://bugs.debian.org/1061282
Processed: Bug#1061282 marked as pending in gtk+3.0
Processing control commands: > tag -1 pending Bug #1061282 [libgtk-3-0] libgtk-3-0: gtk crashes when I use a script to turn off the screen Added tag(s) pending. -- 1061282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: libgtk-3-0: gtk crashes when I use a script to turn off the screen
Processing commands for cont...@bugs.debian.org: > severity 1061282 serious Bug #1061282 [libgtk-3-0] libgtk-3-0: gtk crashes when I use a script to turn off the screen Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 1061282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056793: Quote variable in cmake file to allow empy values
The attached patch should fix the cmake errors Sebastiaan referred to.
--
Athos Ribeiro
Description: Quote variable in cmake file to allow empy values
Use quotes to allow empty submodules variable during the cmake build
configuration, fixing a FTBFS issue started in noble.
Author: Athos Ribeiro
Forwarded: no
Last-Update: 2024-01-20
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/cmake/modules/CTags.cmake
+++ b/cmake/modules/CTags.cmake
@@ -16,10 +16,10 @@
OUTPUT_VARIABLE submodules
OUTPUT_STRIP_TRAILING_WHITESPACE)
if(${result_code} EQUAL 0)
- string(REPLACE "${TAGS_SRC_DIR}/" "" submodules ${submodules})
+ string(REPLACE "${TAGS_SRC_DIR}/" "" submodules "${submodules}")
# cmake list uses ";" as the delimiter, so split the string manually
# before iterating in it.
- string(REPLACE "\n" ";" submodules ${submodules})
+ string(REPLACE "\n" ";" submodules "${submodules}")
list(APPEND excludes ${submodules})
endif()
endif()
Bug#1051284: marked as done (ABI breakage without SONAME bump)
Your message dated Mon, 22 Jan 2024 17:51:44 + with message-id and subject line Bug#1051284: fixed in tpm2-tss 4.0.1-5 has caused the Debian Bug report #1051284, regarding ABI breakage without SONAME bump 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.) -- 1051284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tpm2-pkcs11 Version: 1.9.0-0.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc version 13.1.0 (Debian 13.1.0-9) > ... rest of stderr output deleted ... > configure:3441: $? = 0 > configure:3430: gcc -V >&5 > gcc: error: unrecognized command-line option '-V' > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3430: gcc -qversion >&5 > gcc: error: unrecognized command-line option '-qversion'; did you mean > '--version'? > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3430: gcc -version >&5 > gcc: error: unrecognized command-line option '-version' > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3461: checking whether the C compiler works > configure:3483: gcc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3487: $? = 0 > configure:3537: result: yes > configure:3540: checking for C compiler default output file name > configure:3542: result: a.out > configure:3548: checking for suffix of executables > configure:3555: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3559: $? = 0 > configure:3582: result: > configure:3604: checking whether we are cross compiling > configure:3612: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3616: $? = 0 > configure:3623: ./conftest > configure:3627: $? = 0 > configure:3642: result: no > configure:3647: checking for suffix of object files > configure:3670: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3674: $? = 0 > configure:3696: result: o > configure:3700: checking whether the compiler supports GNU C > configure:3720: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3720: $? = 0 > configure:3730: result: yes > configure:3741: checking whether gcc accepts -g > configure:3762: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3762: $? = 0 > configure:3806: result: yes > configure:3826: checking for gcc option to enable C11 features > configure:3841: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3841: $? = 0 > configure:3859: result: none needed > configure:3980: checking whether gcc understands -c and -o together > configure:4003: gcc -c conftest.c -o conftest2.o > configure:4006: $? = 0 > configure:4003: gcc -c conftest.c -o conftest2.o > configure:4006: $? = 0 > configure:4018: result: yes > configure:4067: checking build system type > configure:4082: result: x86_64-pc-linux-gnu > configure:4102: checking host system type > configure:4116: result: x86_64-pc-linux-gnu > configure:4157: checking how to print strings > configure:4184: result: printf > configure:4205: checking for a sed that does not truncate output > configure:4275: result: /bin/sed > configure:4293: checking for grep that handles long lines and -e > configure:4357: result: /bin/grep > configure:4362: checking for egrep > configure:4430: result: /bin/grep -E > configure:4435: checking for fgrep > configure:4503: result: /bin/grep -F > configure:4539: checking for ld used by gcc > configure:4607: result: /usr/bin/ld > configure:4614: checking if the linker (/usr/bin/ld) is GNU ld > configure:4630: result: yes > configure:4642: checking for BSD- or MS-compatible name lister (nm) > configure:4697: result: /usr/bin/nm -B > configure:4837: checking the name lister
Bug#1027203: RFH: qiskit-terra
Hi, since qiskit-terra has two RC bugs (#1027203 and #1056878 in CC) and nobody who has expressed any help with this package I wonder whether we can keep this package in Debian. I had a look in later upstream versions but even in 0.13.0 there is a not yet packaged dependency retworkx[1] which seems to become not used in lates upstream any more but this becomes quite rust-dependant. So tags later than 0.19.2 need Rust crates.io-index[2] and I personally do not have any experience with packaging rust. Given that we have no real capacity to catch up with upstream sensibly I wonder whether it makes sense to keep this package inside Debian. I have not analysed the upstream status of qiskit-aer. If it will require similar new dependencies I wonder whether we should remove both packages. While it seems to be not very hard to fix the RC bugs in both packages it does not make much sense to fix very outdated software. What do you think? Kind regards Andreas. [1] https://pypi.org/project/retworkx/ [2] https://github.com/rust-lang/crates.io-index -- http://fam-tille.de
Bug#1050327: marked as done (gcc-arm-none-eabi update breaks other arm-none-eabi packages)
Your message dated Mon, 22 Jan 2024 17:23:58 + with message-id and subject line Bug#1050327: fixed in libstdc++-arm-none-eabi 25 has caused the Debian Bug report #1050327, regarding gcc-arm-none-eabi update breaks other arm-none-eabi packages 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.) -- 1050327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gcc-arm-none-eabi Version: 15:12.3.rel1-1 Severity: serious Tags: sid trixie a typical upload-and-run-away package upload ... see tracker.debian.org, doesn't pass autopkg tests, makes other packages uninstallable, breaks other packages autopkg tests. https://tracker.debian.org/pkg/gcc-arm-none-eabi --- End Message --- --- Begin Message --- Source: libstdc++-arm-none-eabi Source-Version: 25 Done: Keith Packard We believe that the bug you reported is fixed in the latest version of libstdc++-arm-none-eabi, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Keith Packard (supplier of updated libstdc++-arm-none-eabi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 18 Jan 2024 12:20:55 -0800 Source: libstdc++-arm-none-eabi Architecture: source Version: 25 Distribution: unstable Urgency: medium Maintainer: Agustin Henze Changed-By: Keith Packard Closes: 1050327 1052348 Changes: libstdc++-arm-none-eabi (25) unstable; urgency=medium . * Rebuild for new picolibc (1.8.6) . * Rebuild for new toolchain (15:13.2.rel1) (Closes: #1050327) (Closes: #1052348) Checksums-Sha1: 7da2557797156236576ec48638729de1d196d1cc 2296 libstdc++-arm-none-eabi_25.dsc bb626d4c4fe3fb494ca0a4118e203c8c50a94202 4856 libstdc++-arm-none-eabi_25.tar.xz 6f6804c6dff378720ebbd2d9e387753a2d856b10 8370 libstdc++-arm-none-eabi_25_amd64.buildinfo Checksums-Sha256: a6dc16610cd8ed73e81a7519b76e6524c250c74ad3b497af0ecf1cdde48f0cc5 2296 libstdc++-arm-none-eabi_25.dsc 01d461085ab01510bc33b1b589189272504a1cc731bdb642a27c88d8b403a679 4856 libstdc++-arm-none-eabi_25.tar.xz a30e383b8ee966fdf2707145109a06f0f76ab27ea7d642301fe53026eca3ed2f 8370 libstdc++-arm-none-eabi_25_amd64.buildinfo Files: 399d7d20780054391693793537e95228 2296 devel optional libstdc++-arm-none-eabi_25.dsc afec68d851e7dcf5158768bf8e87bffa 4856 devel optional libstdc++-arm-none-eabi_25.tar.xz 67203f9914107c59a9ae9859682d8b68 8370 devel optional libstdc++-arm-none-eabi_25_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAmWuny8ACgkQ2yIaaQAA ABEl/A/7BVIEEfb9lTe8Mwpk40yv+2zFtT5L2T4mLCvjCN+Z7EPTlK2MjlVN7He1 qMm4hhi4dByk6jWdbBz3zTZbMyjbFFHL+36jfpXGQiSJGUN7yg3Roy/OTvJPFlkL +n07gKIsCyFbESb0Lqh7AeXGroy1Xx+Hy7GzMUbEIbvelz11GwOV+0B9sFO1bt9q 78UMwXMaHJM336Ba1IBb/+h99hcQyvsV7CUXW56nF7s1rcV3VsyNDGvXA/AiDv6j aJ5F44T/V6xSmXtOqQspVwIe1anF4TtKp4KoCfQJ7LsTyhgIfcP2lIKxCrYLMlwH Hma+BxvEjeexMTdhSS8dWywL5Z47yuXT/i+1863llW3HVUH4jAss8Hb4OW3UsWxn a+9SdM+zOyoNX40OKKNNUI00a9KuXNb5GWD7mCqhr7Ub7Nh7NRDi1l3NC2HZfFqv 40MC4Y09lpMK0/eUA4BB0RqDPvYFdtSMneDXvvjNELVlZX6NYEe9ttvSEpfy29S5 +nK88LdxTRn9fxRW6cc8OQQIll+RVQzGLkoFt+WcwamiG0rltJ+mej9ntnKqeAT3 mcYtJSDtJpqfW6Dl8Vg9ijWjjIDyQ3b+Wf0zqvqlcZIkOGWzDkUb3r29gvFbvLlr 256tljVZApBYthKMMc5gy3jO1innoAvOuQLZH7GBVIbqH/CZStA= =tfzf -END PGP SIGNATURE End Message ---
Bug#1061313: marked as done (macaulay2 ftbfs with Python 3.12 as the default)
Your message dated Mon, 22 Jan 2024 16:07:18 +
with message-id
and subject line Bug#1061313: fixed in macaulay2 1.22+ds-6
has caused the Debian Bug report #1061313,
regarding macaulay2 ftbfs with Python 3.12 as the default
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.)
--
1061313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:macaulay2
Version: 1.22+ds-5
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
with python3-defaults from experimental:
[...]
gcc -std=gnu11 -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection
-fdebug-prefix-map=/<>=/usr/src/macaulay2-1.22+ds-5build1
-g3 -O2 -Wno-unused -pipe -Wall -Wno-shadow -Wcast-qual
-Wno-sign-conversion -Wno-sign-compare -Wno-parentheses
-Wno-sign-compare -Wuninitialized -Wframe-address -Wstrict-aliasing
-Wfatal-errors -Wimplicit-function-declaration -Wno-unused-label
-Wreturn-type -Wunused-function -Wfatal-errors -I. -I. -I./../e
-I./../system -I./../../include -I./../c -I/<>/M2/include
-I/<>/M2/include -I/<>/M2/usr-host/include
-I/<>/M2/include -I/<>/M2/include
-I/<>/M2/usr-host/include -I/<>/M2/include
-I/<>/M2/include -I/<>/M2/usr-host/include
-Wdate-time -D_FORTIFY_SOURCE=3 -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib -I/usr/include/cdd
-I/usr/include/eigen3 -I/usr/include/python3.12 -I/usr/include
-DBOOST_STACKTRACE_LINK -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib -I/usr/include/cdd
-I/usr/include/eigen3 -I/usr/include/python3.12 -I/usr/include
-DBOOST_STACKTRACE_LINK -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib -I/usr/include/cdd
-I/usr/include/eigen3 -I/usr/include/python3.12 -I/usr/include
-DBOOST_STACKTRACE_LINK -DNDEBUG -Wno-unknown-pragmas -c
-Wno-unused-value -Wno-unused-but-set-variable -Wno-maybe-uninitialized
util-tmp.c -o util.o
util.d: In function ‘util_getSequenceOfPairsOfSmallIntegers_1’:
util.d:52:12: warning: array subscript ‘struct M2_arrayint_struct[0]’ is
partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
52 | is x:Sequence do getSequenceOfPairsOfSmallIntegers(x)
|^~
In file included from ./../../include/M2/gc-include.h:44,
from util-exports.h:6,
from util-tmp.c:1:
util.d:52:29: note: object of size 4 allocated by ‘GC_malloc_atomic’
52 | is x:Sequence do getSequenceOfPairsOfSmallIntegers(x)
| ^~~~
util.d: In function ‘util_getSequenceOfSmallIntegers_1’:
util.d:102:19: warning: array subscript ‘struct M2_arrayint_struct[0]’
is partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
102 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
| ^~
util.d:102:36: note: object of size 4 allocated by ‘GC_malloc_atomic’
102 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
|^~~~
util.d: In function ‘util_getNullOrSequenceOfSmallIntegers’:
util.d:110:19: warning: array subscript ‘struct M2_arrayint_struct[0]’
is partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
110 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
| ^~
util.d:110:36: note: object of size 4 allocated by ‘GC_malloc_atomic’
110 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
|^~~~
util.d: In function ‘util_getSequenceOfStrings’:
util.d:120:12: warning: array subscript ‘struct
M2_ArrayString_struct[0]’ is partly outside array bounds of ‘unsigned
char[8]’ [-Warray-bounds=]
120 | new array(string) len length(s) do (
|^~
util.d:120:32: note: object of size 8 allocated by ‘GC_malloc’
120 | new array(string) len length(s) do (
|
Bug#1056882: marked as done (rdma-core: ftbfs with cython 3.0.x)
Your message dated Mon, 22 Jan 2024 15:41:14 + with message-id and subject line Bug#1056882: fixed in rdma-core 48.0-1.1 has caused the Debian Bug report #1056882, regarding rdma-core: ftbfs with cython 3.0.x 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.) -- 1056882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rdma-core Version: 48.0-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: rdma-core Source-Version: 48.0-1.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of rdma-core, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated rdma-core 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: Mon, 22 Jan 2024 16:08:10 +0100 Source: rdma-core Architecture: source Version: 48.0-1.1 Distribution: unstable Urgency: medium Maintainer: Benjamin Drung Changed-By: Matthias Klose Closes: 1056882 Changes: rdma-core (48.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Switch to cython3-legacy (Bas Couwenberg). Closes: #1056882. Checksums-Sha1: e15382c4aea5c32e7ff4da4fe7721b5028276290 3230 rdma-core_48.0-1.1.dsc 87176364a283dd1d4e60dc0fc7634880a5a737d1 23856 rdma-core_48.0-1.1.debian.tar.xz ed50cbfcdd11b8e542c141e55dfcca5c1bbb4af6 8282 rdma-core_48.0-1.1_source.buildinfo Checksums-Sha256: 3a246c219d9aa82385bd012119007b548594e58438006a53549ca059b2670316 3230 rdma-core_48.0-1.1.dsc 09108103781dbae51c0a8ecc1485022a6e7ffe45ea0fa354990b7d3280b7cc59 23856 rdma-core_48.0-1.1.debian.tar.xz f937e2dcf4b3a9b2649594c58811b0b3adf99e1850cf193124f5acf562b69a13 8282 rdma-core_48.0-1.1_source.buildinfo Files: 04a78c05c1f89c2fba463bb93db85bf3 3230 net optional rdma-core_48.0-1.1.dsc 5496f8e5db96254856c6544961077dda 23856 net optional rdma-core_48.0-1.1.debian.tar.xz 0df2823a74608c08f2c9e4facf807f52 8282 net optional rdma-core_48.0-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmWuhbMQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9RK4EADL6jHqt9yJzUKUshrOUD+12cWp/m+xlpT6 4sl3fg/pZkGNMY+Y4TNkp3dRmeqedG10CCbZP46mDLbHeFzKB0TmH1W+MSo8Y2Lj CJum8xGtgqrSrhaCOoDbURFKSqq3nl4PWjURxctcELVyepldBJkbvc3DELh/ZJr3 4xWvh/Z8i2Fdeh7R1L3yqo4pOjtnwt9lhT10Bnagk+hnilHfuufgsYA7LCGJNIvv Ql0oCQV2RBO4bQRvGh2PJCK+Y1Dz4Id29/+1T5pQrbyws3wRqCm+BNRVLASRvpiz 60i+mtbrmnXLNXT/li+GgdhZdyvf4Y+Y1XkApClE2nWlrRd8IPoDKPcG8Gq2RAT5 28t8TFfCv2psKOYWn5dhxVB9wo+uT497L+8TKUrJ+UVHXpADNJaInI179lqqxx3F Uwt3Tl+mdcpkLNlRQ+RC2RmWAQxm6ert3lmdaNnTAZPU0iBDUvWHgZz1DdaEFtTf Kc5o9FYTbo5eJEQDYa1Pta2yh4LMp1WGRUDjzy5441BUVvdGw6m8uUmLb/WBKIDF SBUifKB8uObZa7p9evrJWOYFRjlN1oFq91v/N/yeSphKVSvMr8Opx2ojr4hi0ANm UI4YyaKxY5GngtOoA5Ca2XaP6L0fvHCWGJe4uzMO+LZrlhVftn2Hqny6qOGLkeWI uC9HGYMOtQ== =7uck -END PGP SIGNATURE End Message ---
Bug#1060990: marked as done (wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2)
Your message dated Mon, 22 Jan 2024 15:37:03 + with message-id and subject line Bug#1060687: fixed in libwacom 2.9.0-2 has caused the Debian Bug report #1060687, regarding wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1060687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wacomtablet Version: 3.2.0-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > > > -- The C compiler identification is GNU 13.2.0 > -- The CXX compiler identification is GNU 13.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Installing in the same prefix as Qt, adopting their path scheme. > -- Could not set up the appstream test. appstreamcli is missing. > -- Looking for __GLIBC__ > -- Looking for __GLIBC__ - found > -- Performing Test _OFFT_IS_64BIT > -- Performing Test _OFFT_IS_64BIT - Success > -- Performing Test HAVE_DATE_TIME > -- Performing Test HAVE_DATE_TIME - Success > CMake Warning (dev) at /usr/share/ECM/modules/ECMFindModuleHelpers.cmake:113 > (message): > Your project should require at least CMake 3.16.0 to use FindKF5.cmake > Call Stack (most recent call first): > /usr/share/ECM/find-modules/FindKF5.cmake:30 > (ecm_find_package_version_check) > CMakeLists.txt:25 (find_package) > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Found KF5CoreAddons: > /usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake > (found version "5.107.0") > -- Found Gettext: /usr/bin/msgmerge (found version "0.21") > -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake > (found version "5.107.0") > -- Found KF5GlobalAccel: > /usr/lib/x86_64-linux-gnu/cmake/KF5GlobalAccel/KF5GlobalAccelConfig.cmake > (found version "5.107.0") > -- Found KF5Config: > /usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found > version "5.107.0") > -- Found KF5XmlGui: > /usr/lib/x86_64-linux-gnu/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found > version "5.107.0") > -- Found KF5WidgetsAddons: > /usr/lib/x86_64-linux-gnu/cmake/KF5WidgetsAddons/KF5WidgetsAddonsConfig.cmake > (found version "5.107.0") > -- Found X11: /usr/include > -- Looking for XOpenDisplay in > /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so > -- Looking for XOpenDisplay in > /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - > found > -- Looking for gethostbyname > -- Looking for gethostbyname - found > -- Looking for connect > -- Looking for connect - found > -- Looking for remove > -- Looking for remove - found > -- Looking for shmat > -- Looking for shmat - found > -- Found KF5WindowSystem: > /usr/lib/x86_64-linux-gnu/cmake/KF5WindowSystem/KF5WindowSystemConfig.cmake > (found version "5.107.0") > -- Found KF5Notifications: > /usr/lib/x86_64-linux-gnu/cmake/KF5Notifications/KF5NotificationsConfig.cmake > (found version "5.107.0") > -- Found KF5DBusAddons: >
Bug#1060687: marked as done (libwacom-dev: Needs Depends: libevdev-dev)
Your message dated Mon, 22 Jan 2024 15:37:03 + with message-id and subject line Bug#1060687: fixed in libwacom 2.9.0-2 has caused the Debian Bug report #1060687, regarding libwacom-dev: Needs Depends: libevdev-dev 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.) -- 1060687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libwacom Version: 2.9.0-1 Severity: serious libwacom.pc now has this line: Requires.private: gudev-1.0, glib-2.0, libevdev Therefore, please add libevdev-dev to libwacom-dev's Depends. I noticed this issue when building another package that uses libwacom but it was also detected by autopkgtests. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: libwacom Source-Version: 2.9.0-2 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of libwacom, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated libwacom 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: Mon, 22 Jan 2024 17:18:38 +0200 Source: libwacom Built-For-Profiles: noudeb Architecture: source Version: 2.9.0-2 Distribution: unstable Urgency: medium Maintainer: Timo Aaltonen Changed-By: Timo Aaltonen Closes: 1060687 Changes: libwacom (2.9.0-2) unstable; urgency=medium . * control: Add libevdev-dev to libwacom-dev depends. (Closes: #1060687) Checksums-Sha1: bcede0499e0976a743282c512acc92a676e7edd4 2219 libwacom_2.9.0-2.dsc 2ac6baf3dc90cab893d31ff222b1d4913b0f0a4d 6084 libwacom_2.9.0-2.debian.tar.xz cd824304e9b4ffe8caab158b06c0f06eacd8fa07 8098 libwacom_2.9.0-2_source.buildinfo Checksums-Sha256: 79878ca0fcc169b951b350e57cbe20b31219fc9098cc5f5784f5b4f0452ee385 2219 libwacom_2.9.0-2.dsc 1f58b6cd8d0f61ff83ed42cf105c94c7ba74e2eeb138999752aa4fd555c38da4 6084 libwacom_2.9.0-2.debian.tar.xz 728a204090d0db1c0e63ba3f401e7e3c6a97714d6685221d6b93297b0aeb94d7 8098 libwacom_2.9.0-2_source.buildinfo Files: 8e29831a0c144f8fd718f0ea6e06b8bd 2219 libs optional libwacom_2.9.0-2.dsc 0fcc4477125b26180400cce58fc83ca7 6084 libs optional libwacom_2.9.0-2.debian.tar.xz a90384cf6d6482437717593a789a49fb 8098 libs optional libwacom_2.9.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmWuh2YACgkQy3AxZaiJ hNyJog/+Mb8JBtmSdcXElA1ub497H/ccu5oLcygwnq87IFQteakSlzbWFK8ndQRR MY2H5NIKKBZv4+z1FbXXkMyMN2SfwwbSNmAPHdBKyWb7a0IH+Ivi8/qHJKfMD4fM za3Ka6BFlu5tYjIHL/nli7OV37e6cs6h3gPv5kAnOGmIJWtG4j6/iXIYU1BAvvUD RbcJW6cqxh5LNW3t5q/rfNnVPiMfOF8YIE63Qym9lU2lU/TInjWRYPoPJHYhWjmp Js+KpbTdSVQv8xMDkHGKNm56Ba0h722uh3OYdpwAZzSCeqlLA7sgyCPZhdyM1hcv QiWbSTpUcbIFXamcZE2qXcI3Re4WqGAdpykhqWWD6RgT5TZLoPSxxASDh/SqiXDe wikpyzoEOeA/0R/UsXUvwh6Bk/0pnO5+9X1dfv/h0eGoTUiscrsqUIIMBaa4n4cF YQ7y0IntVvxM1XMF3Pm985x86SQEDNbLJdeMwcVIs+faA6+dLkAHV6GoCEX2EuHb hNVeyQX4mdt4gh4MLDpxfekLZw9vyNsap4ZaRq/zEgGj1cjGmLIh4dZy5iDMXPYf NpaSCBIyGJjPBl0JwOiWv90SW6vMJfxdQ6zOIHWN+YjQ4MsPUEMYvxep5SxIgAZD jQ99Oy7rmXEItNuiOQNnnVAicEIKGijjl/EaWzCAP7z9rpF/AhA= =KAOa -END PGP SIGNATURE End Message ---
Bug#1056875: marked as done (python-thinc: ftbfs with cython 3.0.x)
Your message dated Mon, 22 Jan 2024 15:10:54 + with message-id and subject line Bug#1056875: fixed in python-thinc 8.2.2-1 has caused the Debian Bug report #1056875, regarding python-thinc: ftbfs with cython 3.0.x 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.) -- 1056875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-thinc Version: 8.1.7-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: python-thinc Source-Version: 8.2.2-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of python-thinc, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-thinc 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: Mon, 22 Jan 2024 14:11:01 +0100 Source: python-thinc Architecture: source Version: 8.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Closes: 1046341 1056875 1058004 Changes: python-thinc (8.2.2-1) unstable; urgency=medium . * New upstream version . [ Bas Couwenberg ] * Switch to cython3-legacy. Closes: #1056875 . [ Andreas Tille ] * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update) * Remove unused license definitions for BSD-3-Clause. * Fix clean target Closes: #1046341 * No runtime dependency from cython3 Closes: #1058004 Checksums-Sha1: 08c0241b018d58a297726f0cc91bb2d30a998d8f 2449 python-thinc_8.2.2-1.dsc e17e996bb0709676d583f6eb74420e2cb8f1bc23 1704605 python-thinc_8.2.2.orig.tar.gz b8b400742c0a7d41b53e8255c49fef598b140c9c 4024 python-thinc_8.2.2-1.debian.tar.xz c83fcdd68649897898dab484fc98267208ef108b 9018 python-thinc_8.2.2-1_amd64.buildinfo Checksums-Sha256: 761d61bafc72293b70b40a7d3638d422524ab62801cc463f48f5635c547d1323 2449 python-thinc_8.2.2-1.dsc dd0b98412007f604cdb978a3fe454dea62b61ca53977ff8bf4f672330268fa84 1704605 python-thinc_8.2.2.orig.tar.gz 0517c82a5472fa1dc00f2452c9b3afbe51e2a53bf49b7194ccc871218d2c84e2 4024 python-thinc_8.2.2-1.debian.tar.xz 74417df13eeca798d972d5f75933f669fa15c33187aeea879ba7ad720d8c0fa2 9018 python-thinc_8.2.2-1_amd64.buildinfo Files: ce4be822aa61ff7dccc14c825cd07551 2449 python optional python-thinc_8.2.2-1.dsc 61d59a550cf84bb4539d06542b17f604 1704605 python optional python-thinc_8.2.2.orig.tar.gz 8454e86011d7ddf25a306643d938c2ff 4024 python optional python-thinc_8.2.2-1.debian.tar.xz d7445f0b8b1b3f5307c11c1381d9e78f 9018 python optional python-thinc_8.2.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmWufuERHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEkww/9G+uqKoeajskKN+QBg/GiBRFCXO1EIy3m 9SrLW/dat8WAHSCXujslRFaUNSSd5twsEw/k8gDgBzluxgd1jr6QEsPCfJj6DJQE w1FjALSjPCaEueD9KOVvI01wOOxaEodtWhDVcNMZyBDsZKUTvR0Pcz7/vuUb5xoQ zOZsS/Pt/N51S3/mNwbh5hyMvWPqK3Ui0j0eVoVvfLa0nb1stdIF0u/jRZDJMe06 tdLgI8aEfutoI+G1aDL6a8jappd84uEY0LxfdXB647nLwQyeuYL4LYqRqMdJjq/5 KJ3iAF+qxeAUJ6m+dAkRNi+LGaoE4VmVHu1iK677J2ylmauw0r/JIMnp7e8bwSlC T3RocZFwg4B8p0EfGSqMhnL4Wb3ZEF0z/hPmyLIkyv9LIWNrQah6e+UIaPDD2gNx c11wCFR/CMTC1qkI5dzlH2DfEykaAodqYse9r7xSL39Rfg4tUFBy9xCmaNYERsDi VcXVsS3IPbAGjMRIAt42rmsuQon7S24QqI0hF0omspNb8HRSbRdzKwvn9d5StWsm
Bug#1059829: marked as done (node-html5-qrcode: Network access during build)
Your message dated Mon, 22 Jan 2024 15:04:52 + with message-id and subject line Bug#1059829: fixed in node-html5-qrcode 2.3.8+repack-4 has caused the Debian Bug report #1059829, regarding node-html5-qrcode: Network access during build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1059829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-html5-qrcode Version: 2.3.8+repack-3 Severity: serious Justification: not-dfsg X-Debbugs-Cc: y...@debian.org node-html5-qrcode is built using "npm install" which downloads libraries from Internet. This is totally out of DFSG. --- End Message --- --- Begin Message --- Source: node-html5-qrcode Source-Version: 2.3.8+repack-4 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-html5-qrcode, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-html5-qrcode 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: Tue, 02 Jan 2024 11:26:54 +0400 Source: node-html5-qrcode Architecture: source Version: 2.3.8+repack-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1059829 Changes: node-html5-qrcode (2.3.8+repack-4) unstable; urgency=medium . * Team upload * Don't build with npm (Closes: #1059829) * Fix install * Enable minimal test * Fix vcs * Provide libjs-html5-qrcode Checksums-Sha1: 7399bbfa0ed93ff16063f75db7b272347afebb7a 2252 node-html5-qrcode_2.3.8+repack-4.dsc d2e351af57deab34d8190128d7b77500d1beed71 18436 node-html5-qrcode_2.3.8+repack-4.debian.tar.xz 77398dcf0474f88ee5aa229a4e4901191e7c8ac6 20029 node-html5-qrcode_2.3.8+repack-4_amd64.buildinfo Checksums-Sha256: 9449a16793f25b5a3cce851f0b495e3860abad6ba6acb46db466cc447dd88578 2252 node-html5-qrcode_2.3.8+repack-4.dsc 297bc3cc7f5f19aaeeb41ad12e22ca114955e9e4d57167465f8e79c736023689 18436 node-html5-qrcode_2.3.8+repack-4.debian.tar.xz e58405cc16476f9a77605edc8bce304035b208952a79383fc65dc9b544e4f464 20029 node-html5-qrcode_2.3.8+repack-4_amd64.buildinfo Files: 26313f62d16f37ad2577670c292a2fe0 2252 javascript optional node-html5-qrcode_2.3.8+repack-4.dsc 38a7e58eba3cc3eb493efd330f84ea65 18436 javascript optional node-html5-qrcode_2.3.8+repack-4.debian.tar.xz 944e38513ec4c3193423bcb45c94896f 20029 javascript optional node-html5-qrcode_2.3.8+repack-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmWugDAACgkQHCgWkHE2 rjkfvhAAiX0f7msA/1mWP2pmtsMiLtMVbFFSde60BqBa8QIfQITMnPV/83tvXlOM uYxrXAA6iwpyFH5zE9aX3WnGsM4s9Fqs8+C618GkSAV64lnVVVmOznzn0SXXnmnV 3GPSydqKwNuEdS7Nwb21ZZDIu/JV4MINxGLk91xw6mHaYh2boSVh+BwiVMUkdBql 9H2K1G5zmQZbhyxZx4Gkyd2vEyeGPW5AQWZvhwhotOcxRYc6cBzzQ4WHEXcFkRJZ bf5egpQoDgCfKO6t/2v/GkOcWiR8cAdkuLxy25Fp5T1d2PrnceRmJsomYZoQOpGg 6k69hn7R13Z1eOlQG0J4HPpxIcZ1t9/ap/tLTy9NqdMlKJ7b0v6btn3dYMtN2qHp lXcnlEk+T8XsCMBRIC62BYF0K3IqYk4DWZlsww8ZNhOBMyXJCVAu1AT9QmRqSInn XwgG5XkoYdUFtpGKUO0dTYjJWO8erA7lB7qaq1BOP/nEHrpxC3h4LuideGMPUHKm M9SxKDGfjlZocMGwVPPmGUoZA6saqAf7B4z7+YawWzigpM4XzA6/fEHFbN2Hgp/k EnvefTg/sMiqmcF8pjdbHhMWeDrxICpjIXfQurClwhLtn/B8z9XCfS7Bg7QUKYYQ lEp6WxqvLI5aW8uHIQKJ1DbGNeRrEk/q4SDtHltG/6dtgHUGH1g= =Qo3v -END PGP SIGNATURE End Message ---
Bug#1061322: avfs: identified for time_t transition but no ABI in shlibs
Package: avfs Version: 1.1.5-1 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Hi Michael, Analysis of the archive for the 64-bit time_t transition[0][1] identifies avfs as a package shipping a library whose ABI changes on 32-bit architectures with 64-bit time_t. However, avfs's shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libavfs 0 avfs (>= 1.1.5) $ It is therefore not obvious that we should rename the package to 'avfs-t64' as part of this transition. Looking at the archive, there is a package built from a separate source package, 'worker', which depends on this library. Since there is no self-evident thing to do with the library package name here, we will not be handling this package as part of the mass NMUs. Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures (upgrading avfs without also upgrading worker) will result in ABI skew and may result in broken behavior. Thanks, -- 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 [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html signature.asc Description: PGP signature
Bug#1061313: macaulay2 ftbfs with Python 3.12 as the default
Control: tags -1 confirmed
On Mon 22 Jan 2024 09:22:49 AM -05, Matthias Klose wrote:
Package: src:macaulay2
Version: 1.22+ds-5
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
with python3-defaults from experimental:
[...]
gcc -std=gnu11 -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection
-fdebug-prefix-map=/<>=/usr/src/macaulay2-1.22+ds-5build1
-g3 -O2 -Wno-unused -pipe -Wall -Wno-shadow -Wcast-qual
-Wno-sign-conversion -Wno-sign-compare -Wno-parentheses
-Wno-sign-compare -Wuninitialized -Wframe-address -Wstrict-aliasing
-Wfatal-errors -Wimplicit-function-declaration -Wno-unused-label
-Wreturn-type -Wunused-function -Wfatal-errors -I. -I. -I./../e
-I./../system -I./../../include -I./../c -I/<>/M2/include
-I/<>/M2/include -I/<>/M2/usr-host/include
-I/<>/M2/include -I/<>/M2/include
-I/<>/M2/usr-host/include -I/<>/M2/include
-I/<>/M2/include -I/<>/M2/usr-host/include
-Wdate-time -D_FORTIFY_SOURCE=3 -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib -I/usr/include/cdd
-I/usr/include/eigen3 -I/usr/include/python3.12 -I/usr/include
-DBOOST_STACKTRACE_LINK -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib
-I/usr/include/cdd -I/usr/include/eigen3 -I/usr/include/python3.12
-I/usr/include -DBOOST_STACKTRACE_LINK -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib -I/usr/include/cdd
-I/usr/include/eigen3 -I/usr/include/python3.12 -I/usr/include
-DBOOST_STACKTRACE_LINK -DNDEBUG -Wno-unknown-pragmas -c
-Wno-unused-value -Wno-unused-but-set-variable
-Wno-maybe-uninitialized util-tmp.c -o util.o
util.d: In function ‘util_getSequenceOfPairsOfSmallIntegers_1’:
util.d:52:12: warning: array subscript ‘struct M2_arrayint_struct[0]’
is partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
52 | is x:Sequence do getSequenceOfPairsOfSmallIntegers(x)
|^~
In file included from ./../../include/M2/gc-include.h:44,
from util-exports.h:6,
from util-tmp.c:1:
util.d:52:29: note: object of size 4 allocated by ‘GC_malloc_atomic’
52 | is x:Sequence do getSequenceOfPairsOfSmallIntegers(x)
| ^~~~
util.d: In function ‘util_getSequenceOfSmallIntegers_1’:
util.d:102:19: warning: array subscript ‘struct M2_arrayint_struct[0]’
is partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
102 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
| ^~
util.d:102:36: note: object of size 4 allocated by ‘GC_malloc_atomic’
102 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
|^~~~
util.d: In function ‘util_getNullOrSequenceOfSmallIntegers’:
util.d:110:19: warning: array subscript ‘struct M2_arrayint_struct[0]’
is partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
110 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
| ^~
util.d:110:36: note: object of size 4 allocated by ‘GC_malloc_atomic’
110 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
|^~~~
util.d: In function ‘util_getSequenceOfStrings’:
util.d:120:12: warning: array subscript ‘struct
M2_ArrayString_struct[0]’ is partly outside array bounds of ‘unsigned
char[8]’ [-Warray-bounds=]
120 | new array(string) len length(s) do (
|^~
util.d:120:32: note: object of size 8 allocated by ‘GC_malloc’
120 | new array(string) len length(s) do (
|^
util.d: In function ‘util_getSequenceOfRingElements’:
util.d:151:12: warning: array subscript ‘struct
engine_RawRingElementArray_struct[0]’ is partly outside array bounds
of ‘unsigned char[8]’ [-Warray-bounds=]
151 | is a:RawRingElementCell do RawRingElementArray(a.p)
|^~
util.d:151:44: note: object of size 8 allocated by ‘GC_malloc’
151 | is a:RawRingElementCell do RawRingElementArray(a.p)
|^
util.d: In function ‘util_getSequenceOfMatrices’:
util.d:170:13: warning: array subscript ‘struct
engine_RawMatrixArray_struct[0]’ is partly outside array bounds of
‘unsigned char[8]’ [-Warray-bounds=]
170 | is
Processed: Re: Bug#1061313: macaulay2 ftbfs with Python 3.12 as the default
Processing control commands: > tags -1 confirmed Bug #1061313 [src:macaulay2] macaulay2 ftbfs with Python 3.12 as the default Added tag(s) confirmed. -- 1061313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: dblatex: FTBFS with Python 3.12
Processing control commands: > tags -1 + patch Bug #1061320 [src:dblatex] dblatex: FTBFS with Python 3.12 Added tag(s) patch. -- 1061320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061320: dblatex: FTBFS with Python 3.12
Control: tags -1 + patch
These two patches from Fedora[1] fix the FTBFS:
dblatex-0.3.12-replace-imp-by-importlib.patch
dblatex-0.3.12-adjust-submodule-imports.patch
I attach an additional patch that fixes several instances of
'SyntaxWarning: invalid escape sequence' that may be alarming to
users.
[1] https://src.fedoraproject.org/rpms/dblatex/tree/rawhide
Description: Fix several SyntaxWarnings
Use raw strings to avoid invalid escape sequence
Author: Graham Inggs
Last-Update: 2024-01-22
--- a/lib/dbtexmf/dblatex/grubber/texparser.py
+++ b/lib/dbtexmf/dblatex/grubber/texparser.py
@@ -31,7 +31,7 @@
# Make a "foo|bar\*stub" list
hooklist = [x.replace("*", "\\*") for x in self.hooks]
-pattern = "(?P%s)\*?"\
+pattern = r"(?P%s)\*?"\
" *(\\[(?P[^\\]]*)\\])?"\
" *({(?P[^{}]*)}|(?=[^A-Za-z]))"
--- a/lib/dbtexmf/dblatex/texcodec.py
+++ b/lib/dbtexmf/dblatex/texcodec.py
@@ -26,7 +26,7 @@
l.append(unient.unicode_map[ord(c)])
except KeyError:
print("Missing character
Processed: Forward bug number
Processing commands for cont...@bugs.debian.org: > forwarded 1061312 https://github.com/mypaint/mypaint/issues/1228 Bug #1061312 [src:mypaint] mypaint ftbfs with Python 3.12 as the default Set Bug forwarded-to-address to 'https://github.com/mypaint/mypaint/issues/1228'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061320: dblatex: FTBFS with Python 3.12
Source: dblatex Version: 0.3.12py3-2 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer dblatex FTBFS with Python 3.12. I've copied what I hope is the relevant part of the log below. Regards Graham Traceback (most recent call last): File "/<>/setup.py", line 498, in version=get_version(), ^ File "/<>/setup.py", line 475, in get_version from dbtexmf.dblatex import dblatex File "/<>/lib/dbtexmf/dblatex/dblatex.py", line 8, in from dbtexmf.core.dbtex import DbTex, DbTexCommand File "/<>/lib/dbtexmf/core/dbtex.py", line 18, in import imp ModuleNotFoundError: No module named 'imp'
Bug#1061319: cadabra2 ftbfs with Python 3.12 as default
Package: src:cadabra2 Version: 2.4.3.2-1.1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: there goes something wrong during the configuration, 3.11 is picked up instead of 3.12. Also d/rules reads: override_dh_auto_install: dh_auto_install sed -i s,python3.10,python3,g debian/cadabra2/usr/bin/cadabra2 please don't hardcode the python version. [...] --- Configuring Python --- -- Building for use with Python 3 (good!) CMake Deprecation Warning at libs/pybind11/CMakeLists.txt:8 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- pybind11 v2.11.0 dev1 CMake Warning (dev) at cmake/modules/FindPythonLibsNew.cmake:60 (find_package): Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules are removed. Run "cmake --help-policy CMP0148" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Call Stack (most recent call first): libs/pybind11/tools/pybind11Tools.cmake:50 (find_package) libs/pybind11/tools/pybind11Common.cmake:180 (include) libs/pybind11/CMakeLists.txt:208 (include) This warning is for project developers. Use -Wno-dev to suppress it. -- Found PythonInterp: /usr/bin/python3.11 (found version "3.11.7") -- Found PythonLibs: python3.11 -- Performing Test HAS_FLTO -- Performing Test HAS_FLTO - Success -- Found python python3.11 -- Python version is 3.11. -- Installing Python module in /usr/lib/python3.11/site-packages -- Python abi name cpython-311-x86_64-linux-gnu
Bug#1061304: marked as done (pam-python accesses the network during the build)
Your message dated Mon, 22 Jan 2024 14:36:10 + with message-id and subject line Bug#1061304: fixed in pam-python 1.1.0~git20220701.1d4e111-0.4 has caused the Debian Bug report #1061304, regarding pam-python accesses the network during the build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pam-python Version: 1.1.0~git20220701.1d4e111-0.3 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] making output directory... done loading intersphinx inventory from /usr/share/doc/python-doc/html/objects.inv... WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory '/usr/share/doc/python-doc/html/objects.inv' not fetchable due to : [Errno 2] No such file or directory: '/usr/share/doc/python-doc/html/objects.inv' building [mo]: targets for 0 po files that are out of date ... and then it downloads the files. just fix the path. --- End Message --- --- Begin Message --- Source: pam-python Source-Version: 1.1.0~git20220701.1d4e111-0.4 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of pam-python, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated pam-python 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: Mon, 22 Jan 2024 14:45:27 +0100 Source: pam-python Architecture: source Version: 1.1.0~git20220701.1d4e111-0.4 Distribution: unstable Urgency: medium Maintainer: Russell Stuart Changed-By: Matthias Klose Closes: 1061304 Changes: pam-python (1.1.0~git20220701.1d4e111-0.4) unstable; urgency=medium . * Non-maintainer upload. * Fix the path to the Python intersphinx repository. Closes: #1061304. Checksums-Sha1: f21b274f866ac9061171118cb42ff9df136491bd 2309 pam-python_1.1.0~git20220701.1d4e111-0.4.dsc d99f4b1226e86b76b2842fb09ef979ab3e1a6a71 18132 pam-python_1.1.0~git20220701.1d4e111-0.4.debian.tar.xz a3c5d772392b18061c058daac5869afcc5743c04 8149 pam-python_1.1.0~git20220701.1d4e111-0.4_source.buildinfo Checksums-Sha256: 6b7357c6672b07d7b5dfdb369456bf301397d5777e4d1e175dc71bc3b177aac4 2309 pam-python_1.1.0~git20220701.1d4e111-0.4.dsc fbe6cc0b0d4d51611bb64b7c8b163431304eef6d95ab3064d8a7933c97e4b338 18132 pam-python_1.1.0~git20220701.1d4e111-0.4.debian.tar.xz ad88154c099b2f74b53fd296a656b1ec1a4d8ab59292f0858bfe6383db42f51f 8149 pam-python_1.1.0~git20220701.1d4e111-0.4_source.buildinfo Files: 13be48989cfa1891fc6eb63bc7fe1747 2309 admin optional pam-python_1.1.0~git20220701.1d4e111-0.4.dsc c6bcdbccf29a704a6b604aaac3a0fe52 18132 admin optional pam-python_1.1.0~git20220701.1d4e111-0.4.debian.tar.xz 268aedcd8dfe356e9635eb914781aea6 8149 admin optional pam-python_1.1.0~git20220701.1d4e111-0.4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmWucloQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9dgdD/9DuZPkcjWYR3JOeflM5Im+ZoevH9lOPf80 yl8R4oM6HKxypiXBfMuAn9RnYI/g95mHVuLa8jn7u4ivEw1kb03mKpdz26RscRE8 w9YyjR4sK1UVJCmvAhV5T9z2Lru+3R7yEhkNY39kA+wcJF9wkxaAiUikR4KxyrSZ KHJyudKSoZM23mfLOAUbvautLaAwJD/63XBWsqMJ9A61twJBnlr55mzkoH0Y+NA8 rwx1XkET8ebcA9mBklviv44YfHPGmDkqfr+Q0OaDWDKJ1ODneI+ecAmyVUxTbDtE +0hr3CYJaLkixG1ixw3g+aRN7EzHjAq8fIgLYD4WUyfbNjuuuEYv0a2iGFjaLs1y sgo8gz3bMEWyaATNz2sJIFYRXRuftgfuXAslWiSSbSIPyXnGL3nRODtphGQd9xns Ilz/F9jClpWS0LUGqRtWumt+QYttIWB7uNljZ2CiQ9chTv2wPJi8XBZf8uUj5ntz TFMJk5hBkZec+51NWmC9+y0rvUb43vxb+f9+YXtx0zF3TaSpN6pjwi/Dyn70JR7K A74jFNs2nn5VLY2M6wEB1jOEToLK6a9IURkFSFhX0CnAlhPg+htuUAcCEr4xm4Vf OAdUWSn6P02bMaw8LsHWXM4mfb2fmgUCsyXcsSTg34SXSNzpxiJUqFi3JTC1dmds PqPchBQcfw== =y8jy -END PGP SIGNATURE End Message ---
Bug#1061318: device-tree-compiler ftbfs with Python 3.12 as default
Package: src:device-tree-compiler Version: 1.7.0-1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: [...] testCreate (__main__.PyLibfdtSwTests.testCreate) ... FAIL == FAIL: testReserveMap (__main__.PyLibfdtBasicTests.testReserveMap) Test that we can access the memory reserve map -- Traceback (most recent call last): File "/<>/tests/./pylibfdt_tests.py", line 421, in testReserveMap self.assertEqual([ 0xdeadbeef, 0x10], AssertionError: Lists differ: [16045690981097406464, 1048576] != [0, 16045690981097406464, 1048576] First differing element 0: 16045690981097406464 0 Second list contains 1 additional elements. First extra element 2: 1048576 - [16045690981097406464, 1048576] + [0, 16045690981097406464, 1048576] ? +++ == FAIL: testCreate (__main__.PyLibfdtSwTests.testCreate) -- Traceback (most recent call last): File "/<>/tests/./pylibfdt_tests.py", line 585, in testCreate self.assertEqual([TEST_ADDR_1, TEST_SIZE_1], fdt.get_mem_rsv(0)) AssertionError: Lists differ: [9223372036854775808, 1048576] != [0, 9223372036854775808, 1048576] First differing element 0: 9223372036854775808 0 Second list contains 1 additional elements. First extra element 2: 1048576 - [9223372036854775808, 1048576] + [0, 9223372036854775808, 1048576] ? +++ -- Ran 39 tests in 0.005s FAILED (failures=2) ** TEST SUMMARY * Total testcases: 2100 *PASS: 2098 *FAIL: 0 * Bad configuration: 0 * Strange test result: 0 ** make[1]: *** [tests/Makefile.tests:89: check] Error 1 make[1]: Leaving directory '/<>'
Bug#1061317: gemrb ftbfs with Python 3.12 as default
Package: src:gemrb
Version: 0.9.0+dfsg-1
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
with python3-defaults from experimental:
[...]
[ 83%] Building CXX object
gemrb/plugins/MVEPlayer/CMakeFiles/MVEPlayer.dir/mve_player.cpp.o
cd /<>/obj-x86_64-linux-gnu/gemrb/plugins/MVEPlayer &&
/usr/bin/c++ -DHAVE_CONFIG_H -DMVEPlayer_EXPORTS
-I/<>/obj-x86_64-linux-gnu
-I/<>/gemrb/includes -I/<>/gemrb/core -g -O2
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection
-fdebug-prefix-map=/<>=/usr/src/gemrb-0.9.0+dfsg-1build3
-Wdate-time -D_FORTIFY_SOURCE=3 -Wall -W -Wpointer-arith -pedantic
-Wno-format-y2k -Wno-long-long -fsigned-char -fvisibility=hidden
-Wimplicit-fallthrough=2 -std=gnu++11 -fPIC -MD -MT
gemrb/plugins/MVEPlayer/CMakeFiles/MVEPlayer.dir/mve_player.cpp.o -MF
CMakeFiles/MVEPlayer.dir/mve_player.cpp.o.d -o
CMakeFiles/MVEPlayer.dir/mve_player.cpp.o -c
/<>/gemrb/plugins/MVEPlayer/mve_player.cpp
In file included from /<>/gemrb/core/System/VFS.h:33,
from /<>/gemrb/core/Interface.h:46,
from
/<>/gemrb/plugins/GUIScript/PythonConversions.cpp:23:
/<>/gemrb/includes/Predicates.h:36:25: warning:
‘template struct std::unary_function’ is
deprecated [-Wdeprecated-declarations]
36 | struct Predicate : std::unary_function {
| ^~
In file included from /usr/include/c++/13/bits/refwrap.h:39,
from /usr/include/c++/13/bits/shared_ptr_base.h:57,
from /usr/include/c++/13/bits/shared_ptr.h:53,
from /usr/include/c++/13/condition_variable:45,
from /<>/gemrb/core/System/Logger.h:31,
from /<>/gemrb/core/System/Logging.h:31,
from /<>/gemrb/includes/Platform.h:56,
from /<>/gemrb/includes/ie_types.h:31,
from /<>/gemrb/core/System/String.h:23,
from /<>/gemrb/core/Resource.h:31,
from /<>/gemrb/core/ScriptEngine.h:25,
from
/<>/gemrb/plugins/GUIScript/GUIScript.h:43,
from
/<>/gemrb/plugins/GUIScript/PythonConversions.h:23,
from
/<>/gemrb/plugins/GUIScript/PythonConversions.cpp:19:
/usr/include/c++/13/bits/stl_function.h:117:12: note: declared here
117 | struct unary_function
|^~
/<>/gemrb/plugins/GUIScript/PythonConversions.cpp: In
function ‘GemRB::PyStringWrapper GemRB::PyString_AsString(PyObject*)’:
/<>/gemrb/plugins/GUIScript/PythonConversions.cpp:141:36:
error: ‘PyUnicode_AS_DATA’ was not declared in this scope; did you mean
‘PyUnicode_DATA’?
141 | wrap.str = PyUnicode_AS_DATA(obj);
|^
|PyUnicode_DATA
make[3]: ***
[gemrb/plugins/GUIScript/CMakeFiles/GUIScript.dir/build.make:107:
gemrb/plugins/GUIScript/CMakeFiles/GUIScript.dir/PythonConversions.cpp.o]
Error 1
Bug#1061315: inn2 ftbfs with Python 3.12 as the default
Package: src:inn2 Version: 2.7.2~20231223-1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: [...] checking for Python.h... yes checking for Py_Initialize... no configure: error: in `/<>/build': configure: error: unable to link with Python library See `config.log' for more details
Bug#1061316: gringo ftbfs with Python 3.12 as the default
Package: src:gringo Version: 5.4.1-3.1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: [...] -- Performing Test CLINGO_HAS_WORKING_LIBATOMIC -- Performing Test CLINGO_HAS_WORKING_LIBATOMIC - Success -- Found Python: /usr/bin/python3 (found version "3.12.1") found components: Interpreter Development Development.Module Development.Embed -- Found Lua: /usr/lib/x86_64-linux-gnu/liblua5.4.so;/usr/lib/x86_64-linux-gnu/libm.so (found version "5.4.6") -- Found BISON: /usr/bin/bison (found suitable version "3.8.2", minimum required is "2.5") -- Found RE2C: /usr/bin/re2c (found suitable version "0.301.0", minimum required is "0.13") CMake Deprecation Warning at clasp/CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- Potassco is not installed - using local copy CMake Deprecation Warning at clasp/libpotassco/CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) Traceback (most recent call last): File "/<>/cmake/python-site.py", line 1, in from distutils.sysconfig import get_python_lib, get_config_vars ModuleNotFoundError: No module named 'distutils' CMake Error at app/pyclingo/CMakeLists.txt:39 (set_target_properties): set_target_properties called with incorrect number of arguments.
Bug#1061313: macaulay2 ftbfs with Python 3.12 as the default
Package: src:macaulay2
Version: 1.22+ds-5
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
with python3-defaults from experimental:
[...]
gcc -std=gnu11 -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection
-fdebug-prefix-map=/<>=/usr/src/macaulay2-1.22+ds-5build1
-g3 -O2 -Wno-unused -pipe -Wall -Wno-shadow -Wcast-qual
-Wno-sign-conversion -Wno-sign-compare -Wno-parentheses
-Wno-sign-compare -Wuninitialized -Wframe-address -Wstrict-aliasing
-Wfatal-errors -Wimplicit-function-declaration -Wno-unused-label
-Wreturn-type -Wunused-function -Wfatal-errors -I. -I. -I./../e
-I./../system -I./../../include -I./../c -I/<>/M2/include
-I/<>/M2/include -I/<>/M2/usr-host/include
-I/<>/M2/include -I/<>/M2/include
-I/<>/M2/usr-host/include -I/<>/M2/include
-I/<>/M2/include -I/<>/M2/usr-host/include
-Wdate-time -D_FORTIFY_SOURCE=3 -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib -I/usr/include/cdd
-I/usr/include/eigen3 -I/usr/include/python3.12 -I/usr/include
-DBOOST_STACKTRACE_LINK -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib -I/usr/include/cdd
-I/usr/include/eigen3 -I/usr/include/python3.12 -I/usr/include
-DBOOST_STACKTRACE_LINK -isystem /usr/include/libxml2
-I/usr/include/x86_64-linux-gnu/singular -I/usr/include/singular
-DSING_NDEBUG -DOM_NDEBUG-I/usr/src/gtest -Wdate-time
-D_FORTIFY_SOURCE=3 -DNDEBUG -I/usr/include/cddlib -I/usr/include/cdd
-I/usr/include/eigen3 -I/usr/include/python3.12 -I/usr/include
-DBOOST_STACKTRACE_LINK -DNDEBUG -Wno-unknown-pragmas -c
-Wno-unused-value -Wno-unused-but-set-variable -Wno-maybe-uninitialized
util-tmp.c -o util.o
util.d: In function ‘util_getSequenceOfPairsOfSmallIntegers_1’:
util.d:52:12: warning: array subscript ‘struct M2_arrayint_struct[0]’ is
partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
52 | is x:Sequence do getSequenceOfPairsOfSmallIntegers(x)
|^~
In file included from ./../../include/M2/gc-include.h:44,
from util-exports.h:6,
from util-tmp.c:1:
util.d:52:29: note: object of size 4 allocated by ‘GC_malloc_atomic’
52 | is x:Sequence do getSequenceOfPairsOfSmallIntegers(x)
| ^~~~
util.d: In function ‘util_getSequenceOfSmallIntegers_1’:
util.d:102:19: warning: array subscript ‘struct M2_arrayint_struct[0]’
is partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
102 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
| ^~
util.d:102:36: note: object of size 4 allocated by ‘GC_malloc_atomic’
102 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
|^~~~
util.d: In function ‘util_getNullOrSequenceOfSmallIntegers’:
util.d:110:19: warning: array subscript ‘struct M2_arrayint_struct[0]’
is partly outside array bounds of ‘unsigned char[4]’ [-Warray-bounds=]
110 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
| ^~
util.d:110:36: note: object of size 4 allocated by ‘GC_malloc_atomic’
110 | anywhereAbort("internal error:
getSequenceOfSmallIntegers.");
|^~~~
util.d: In function ‘util_getSequenceOfStrings’:
util.d:120:12: warning: array subscript ‘struct
M2_ArrayString_struct[0]’ is partly outside array bounds of ‘unsigned
char[8]’ [-Warray-bounds=]
120 | new array(string) len length(s) do (
|^~
util.d:120:32: note: object of size 8 allocated by ‘GC_malloc’
120 | new array(string) len length(s) do (
|^
util.d: In function ‘util_getSequenceOfRingElements’:
util.d:151:12: warning: array subscript ‘struct
engine_RawRingElementArray_struct[0]’ is partly outside array bounds of
‘unsigned char[8]’ [-Warray-bounds=]
151 | is a:RawRingElementCell do RawRingElementArray(a.p)
|^~
util.d:151:44: note: object of size 8 allocated by ‘GC_malloc’
151 | is a:RawRingElementCell do RawRingElementArray(a.p)
|^
util.d: In function ‘util_getSequenceOfMatrices’:
util.d:170:13: warning: array subscript ‘struct
engine_RawMatrixArray_struct[0]’ is partly outside array bounds of
‘unsigned char[8]’ [-Warray-bounds=]
170 | is a:RawMatrixCell do RawMatrixArray(a.p)
| ^~
util.d:170:40:
Bug#1061312: mypaint ftbfs with Python 3.12 as the default
Package: src:mypaint
Version: 2.0.1-9
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
with python3-defaults from experimental:
[...]
fakeroot debian/rules clean
dh clean --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
pybuild --clean -i python{version} -p 3.12
I: pybuild base:305: python3.12 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 17, in
from distutils.command.build import build
ModuleNotFoundError: No module named 'distutils'
E: pybuild pybuild:391: clean: plugin distutils failed with: exit
code=1: python3.12 setup.py clean
Bug#1061310: python-cramjam FTBFS with pyo3 0.20
Source: python-cramjam Version: 2.7.0.1+ds1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=python-cramjam=ppc64el=2.7.0.1%2Bds1-2=1705802530=0 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-cramjam.html ... Running `maturin pep517 build-wheel -i /usr/bin/python3.11 --compatibility off` error: failed to select a version for the requirement `pyo3 = "^0.19"` candidate versions found which didn't match: 0.20.2 ...
Bug#1061311: neuron ftbfs with Python 3.12 as the default
Package: src:neuron Version: 8.2.2-5 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: [...] + /usr/bin/python3 setup.py build_ext --build-lib=/<>/obj-x86_64-linux-gnu/lib/python Traceback (most recent call last): File "/<>/obj-x86_64-linux-gnu/share/lib/python/neuron/rxd/geometry3d/setup.py", line 19, in from distutils.core import setup ModuleNotFoundError: No module named 'distutils' make[3]: *** [share/lib/python/neuron/rxd/geometry3d/CMakeFiles/rx3dextensions_0.dir/build.make:73: share/lib/python/neuron/rxd/geometry3d/CMakeFiles/rx3dextensions_0] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
Bug#1061308: atheme-services: identified for time_t transition but no ABI in shlibs
Package: atheme-services Version: 7.2.12-1 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Dear maintainers, Analysis of the archive for the 64-bit time_t transition[0][1] identifies atheme-services as an affected package, on the basis that the headers could not be compiled and analyzed out of the box using abi-compliance-checker[2], so we have to assume it's affected. However, atheme-services' shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libathemecore 1 atheme-services (>= 7.2.12) libmowgli-2 0 atheme-services (>= 7.2.12) $ It is therefore not obvious that we should rename the package to 'atheme-services-t64' as part of this transition. Looking at the archive, the only package that depends on these libraries is atheme-services-contrib, built from the same source package. Since there is no self-evident thing to do with the library package name here, and it's not certain that the library ABIs are affected by 64-bit time_t, and the only reverse dependency is from the same source package (so this is an internal transition), we will not be handling this package as part of the mass NMUs. However, I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures (upgrading atheme-services without also upgrading atheme-services-contrib) MAY result in ABI skew and broken behavior. So as maintainers, you should decide how you want to handle this. (Maybe sufficient to, after the dpkg changes land, upload with bumping the versioned dep on atheme-services and adding a versioned breaks on atheme-services-contrib.) Thanks, -- 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 [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html [2] https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/atheme-services/base/log.txt signature.asc Description: PGP signature
Bug#1058364: python-etcd: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Dear Maintainer,
Please find attached two patches that make your package buildable in my
sid chroot environment.
Please also refers to these commits [1][2] where patches come from.
Kind Regards
[1]
https://github.com/jplana/python-etcd/commit/68d8d5dd4ae7ece6c63f446e3c38448998cde3e4
[2]
https://github.com/jplana/python-etcd/commit/b8f3ad0d19626b21b08892ac910fc2e72e0001b6--- a/src/etcd/tests/unit/test_lock.py
+++ b/src/etcd/tests/unit/test_lock.py
@@ -90,8 +90,7 @@
"""
self.locker._sequence = '4'
retval = ('/_locks/test_lock/4', None)
-self.locker._get_locker = mock.MagicMock(
-spec=self.locker._get_locker, return_value=retval)
+self.locker._get_locker = mock.MagicMock(return_value=retval)
self.assertTrue(self.locker._acquired())
self.assertTrue(self.locker.is_taken)
retval = ('/_locks/test_lock/1', '/_locks/test_lock/4')
@@ -112,8 +111,7 @@
def side_effect():
return returns.pop()
-self.locker._get_locker = mock.MagicMock(
-spec=self.locker._get_locker, side_effect=side_effect)
+self.locker._get_locker = mock.MagicMock(side_effect=side_effect)
self.assertTrue(self.locker._acquired())
def test_acquired_no_timeout(self):
--- a/src/etcd/tests/unit/test_lock.py
+++ b/src/etcd/tests/unit/test_lock.py
@@ -31,9 +31,9 @@
"""
Verify the lock gets initialized correctly
"""
-self.assertEquals(self.locker.name, u'test_lock')
-self.assertEquals(self.locker.path, u'/_locks/test_lock')
-self.assertEquals(self.locker.is_taken, False)
+self.assertEqual(self.locker.name, u'test_lock')
+self.assertEqual(self.locker.path, u'/_locks/test_lock')
+self.assertEqual(self.locker.is_taken, False)
def test_acquire(self):
"""
@@ -52,8 +52,8 @@
}
}
self._mock_api(200, d)
-self.assertEquals(l.acquire(), True)
-self.assertEquals(l._sequence, '1')
+self.assertEqual(l.acquire(), True)
+self.assertEqual(l._sequence, '1')
def test_is_acquired(self):
"""
@@ -70,7 +70,7 @@
}
self._mock_api(200, d)
self.locker.is_taken = True
-self.assertEquals(self.locker.is_acquired, True)
+self.assertEqual(self.locker.is_acquired, True)
def test_is_not_acquired(self):
"""
@@ -78,11 +78,11 @@
"""
self.locker._sequence = '2'
self.locker.is_taken = False
-self.assertEquals(self.locker.is_acquired, False)
+self.assertEqual(self.locker.is_acquired, False)
self.locker.is_taken = True
self._mock_exception(etcd.EtcdKeyNotFound, self.locker.lock_key)
-self.assertEquals(self.locker.is_acquired, False)
-self.assertEquals(self.locker.is_taken, False)
+self.assertEqual(self.locker.is_acquired, False)
+self.assertEqual(self.locker.is_taken, False)
def test_acquired(self):
"""
@@ -147,11 +147,11 @@
with self.assertRaises(ValueError):
self.locker.lock_key
self.locker._sequence = '5'
-self.assertEquals(u'/_locks/test_lock/5',self.locker.lock_key)
+self.assertEqual(u'/_locks/test_lock/5',self.locker.lock_key)
def test_set_sequence(self):
self.locker._set_sequence('/_locks/test_lock/10')
-self.assertEquals('10', self.locker._sequence)
+self.assertEqual('10', self.locker._sequence)
def test_find_lock(self):
d = {
@@ -171,11 +171,11 @@
self.locker._sequence = None
self.recursive_read()
self.assertTrue(self.locker._find_lock())
-self.assertEquals(self.locker._sequence, '34')
+self.assertEqual(self.locker._sequence, '34')
def test_get_locker(self):
self.recursive_read()
-self.assertEquals((u'/_locks/test_lock/1', etcd.EtcdResult(node={'newKey': False, '_children': [], 'createdIndex': 33, 'modifiedIndex': 33, 'value': u'2qwwwq', 'expiration': None, 'key': u'/_locks/test_lock/1', 'ttl': None, 'action': None, 'dir': False})),
+self.assertEqual((u'/_locks/test_lock/1', etcd.EtcdResult(node={'newKey': False, '_children': [], 'createdIndex': 33, 'modifiedIndex': 33, 'value': u'2qwwwq', 'expiration': None, 'key': u'/_locks/test_lock/1', 'ttl': None, 'action': None, 'dir': False})),
self.locker._get_locker())
with self.assertRaises(etcd.EtcdLockExpired):
self.locker._sequence = '35'
--- a/src/etcd/tests/unit/test_old_request.py
+++ b/src/etcd/tests/unit/test_old_request.py
@@ -42,7 +42,7 @@
result = client.set('/testkey', 'test', ttl=19)
-self.assertEquals(
+self.assertEqual(
etcd.EtcdResult(
**{u'action': u'SET',
'node': {
@@ -67,7 +67,7 @@
Bug#1061307: rpds-py FTBFS with pyo3 0.20
Source: rpds-py Version: 0.12.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=rpds-py=0.12.0-2 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rpds-py.html ... Running `maturin pep517 build-wheel -i /usr/bin/python3.11 --compatibility off` error: failed to select a version for the requirement `pyo3 = "^0.19.0"` candidate versions found which didn't match: 0.20.2 ...
Bug#1061305: scribus ftbfs with Python 3.12
Package: src:scribus Version: 1.5.8+dfsg-4 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 there is a new upstream, didn't check if this is fixed. [...] /<>/scribus/plugins/scriptplugin/cmdgetsetprop.cpp: In function ‘PyObject* scribus_setproperty(PyObject*, PyObject*, PyObject*)’: /<>/scribus/plugins/scriptplugin/cmdgetsetprop.cpp:413:84: error: ‘PyUnicode_AS_UNICODE’ was not declared in this scope; did you mean ‘PyUnicode_AsUCS4’? 413 | const unsigned short * ucs2Data = (const unsigned short *) PyUnicode_AS_UNICODE(objValue); | ^~~~ | PyUnicode_AsUCS4 /<>/scribus/plugins/scriptplugin/cmdgetsetprop.cpp:433:84: error: ‘PyUnicode_AS_UNICODE’ was not declared in this scope; did you mean ‘PyUnicode_AsUCS4’? 433 | const unsigned short * utf16Data = (const unsigned short *)PyUnicode_AS_UNICODE(objValue); | ^~~~ | PyUnicode_AsUCS4 make[3]: *** [scribus/plugins/scriptplugin/CMakeFiles/scriptplugin.dir/build.make:173: scribus/plugins/scriptplugin/CMakeFiles/scriptplugin.dir/cmdgetsetprop.cpp.o] Error 1
Bug#1061304: pam-python accesses the network during the build
Package: src:pam-python Version: 1.1.0~git20220701.1d4e111-0.3 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] making output directory... done loading intersphinx inventory from /usr/share/doc/python-doc/html/objects.inv... WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory '/usr/share/doc/python-doc/html/objects.inv' not fetchable due to : [Errno 2] No such file or directory: '/usr/share/doc/python-doc/html/objects.inv' building [mo]: targets for 0 po files that are out of date ... and then it downloads the files. just fix the path.
Bug#1061003: lazpaint: FTBFS: make[2]: *** [Makefile:169: lazpaint] Error 2
Hi Gürkan, Thank you for promptly updating the package and addressing the compatibility issues. I appreciate your initiative in labeling the revised package as version 7.2.2.1. Typically, I adhere to a three-number versioning scheme for official releases. However, I understand the need for distinguishing this particular update, which primarily focuses on compatibility and minor fixes. Regarding the version naming, I envisioned it more as a minor revision, like 7.2.2-3, since the changes were essentially adjustments to ensure smooth compilation and operation on certain systems. Could you share your rationale for not adopting this versioning approach? It's crucial to maintain consistency in our versioning strategy to avoid confusion among users. If there's any uncertainty, I encourage open communication. Please feel free to reach out to discuss. In special cases like this, we might consider making an exception and creating a release for 7.2.2.1. Nonetheless, it's also essential to consider the user's perspective – we want to prevent them from needing to re-download the software if the previous version functions adequately on their setup. Perhaps, we could limit this version to the upstream repository, reflecting the minor nature of the changes. For clarity in the application's About section, the version number displayed can be easily adjusted. It's derived from the LazPaintVersion constant in the lazpainttype.pas file. To represent minor revisions like this, you could set it to something like "LazPaintVersion = 7020201;". This subtle modification allows us to manage minor updates efficiently, akin to using a dash version. I'm grateful for your diligence in updating the package, especially for amending the email addresses. Your efforts ensure that the project remains current and accessible. Regards, -- Johann ELSASS aka Juliette circu...@fastmail.com On Mon, Jan 22, 2024, at 12:46 PM, Gürkan Myczko wrote: > Hi Johan > >> Indeed, Lucas, the new version of Lazarus breaks existing code. There >> are some adjustments to do. >> >> Gürkan, I have made the following adjustments in my upstream >> repository. >> Location: https://github.com/bgrabitmap/lazpaint-upstream > > I have downloaded that version and called it 7.2.2.1, I hope that's > fine. > It builds, it works. Closed the bug with upload... > >> Here are the changes: >> - runtime fix for Qt (and in particular NixOS) >> - compilation fix for Lazarus 3.0 >> - removed the debian folder (it was lagging behind the Debian >> repository) > > That's great. You should have tagged the new version on github.com, > sorry for > the 7.2.2.1 version, the about still says 7.2.2 > >> I presume the Debian repository is the one used to build. >> Location: https://sources.debian.org/src/lazpaint/7.2.2-2/ >> >> I've noted that the copyright file has my old e-mail >> circu...@operamail.com. I suggest to update it to >> circu...@fastmail.com. There are three occurrences: >> Upstream-Contact: Johann ELSASS >> Copyright: 2011-2022 Johann ELSASS >> Copyright: 2011-2022 Johann ELSASS > > I have updated all your email addresses. > > Regards, > >> Regards, >> >> -- >> Johann ELSASS aka Juliette >> circu...@fastmail.com
Bug#1058225: marked as done (python-emmet-core: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'debian/control')
Your message dated Mon, 22 Jan 2024 13:22:45 +
with message-id
and subject line Bug#1058225: fixed in python-emmet-core 0.57.1-3
has caused the Debian Bug report #1058225,
regarding python-emmet-core: FTBFS: FileNotFoundError: [Errno 2] No such file
or directory: 'debian/control'
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.)
--
1058225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-emmet-core
Version: 0.57.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for py in 3.12 3.11; do \
> SKIP_TESTS=""; \
> list_initialised=0; \
> for t in test_from_url test_seriallization; do \
> if [ ${list_initialised} = 0 ]; then \
> SKIP_TESTS=$t; \
> list_initialised=1; \
> else \
> SKIP_TESTS="${SKIP_TESTS} or $t"; \
> fi; \
> done; \
> if [ "x${SKIP_TESTS}" != "x" ]; then \
> SKIP_TESTS="not ( ${SKIP_TESTS} )"; \
> fi; \
> echo "skipping tests: ${SKIP_TESTS}"; \
> pybuilddir=`pybuild --pyver $py --print build_dir | awk '{print $3}'`; \
> testdir=/<>/.pybuild/test_python$py; \
> mkdir $testdir; cp -a tests $testdir; \
> cd $testdir; \
> PMG_TEST_FILES_DIR=/<>/debian/test_files
> PYTHONPATH=$pybuilddir \
> python$py -m pytest -v -k "${SKIP_TESTS}" $testdir; \
> done
> skipping tests: not ( test_from_url or test_seriallization )
> ImportError while loading conftest
> '/<>/.pybuild/test_python3.12/tests/conftest.py'.
> tests/conftest.py:4: in
> from pymatgen.core import SETTINGS
> /usr/lib/python3/dist-packages/pymatgen/core/__init__.py:14: in
> from pymatgen.core.lattice import Lattice as Lattice
> /usr/lib/python3/dist-packages/pymatgen/core/lattice.py:19: in
> from pymatgen.util.coord import pbc_shortest_vectors
> /usr/lib/python3/dist-packages/pymatgen/util/coord.py:16: in
> from pymatgen.util import coord_cython
> E ImportError: cannot import name 'coord_cython' from 'pymatgen.util'
> (/usr/lib/python3/dist-packages/pymatgen/util/__init__.py)
> skipping tests: not ( test_from_url or test_seriallization )
> Traceback (most recent call last):
> File "/usr/share/dh-python/dhpython/debhelper.py", line 80, in __init__
> with open('debian/control', 'r', encoding='utf-8') as fp:
> ^
> FileNotFoundError: [Errno 2] No such file or directory: 'debian/control'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/usr/bin/pybuild", line 607, in
> main(cfg)
> File "/usr/bin/pybuild", line 103, in main
> dh = DebHelper(build_options())
> ^^
> File "/usr/share/dh-python/dhpython/debhelper.py", line 102, in __init__
> raise Exception('cannot find debian/control file')
> Exception: cannot find debian/control file
> ImportError while loading conftest
> '/<>/.pybuild/test_python3.11/tests/conftest.py'.
> tests/conftest.py:121: in
> class SiNonSCFUniform(SchemaTestData):
> tests/conftest.py:122: in SiNonSCFUniform
> from emmet.core.vasp.calculation import VaspObject
> E ModuleNotFoundError: No module named 'emmet'
> make[1]: *** [debian/rules:19: override_dh_auto_test] Error 4
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-emmet-core_0.57.1-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-emmet-core
Source-Version: 0.57.1-3
Done: Drew Parsons
We believe that the bug you reported is fixed in the latest version of
python-emmet-core, which is due to be installed in the Debian FTP archive.
A summary of the changes between
Bug#1061301: breezy fails autopkg tests (missing dependency) and accessing the net during the build
Package: src:breezy Version: 3.3.5-1 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] autopkgtest [04:11:10]: test testsuite3: [--- brz: ERROR: No module named 'packaging' You may need to install this Python library separately. autopkgtest [04:11:11]: test testsuite3: ---] also the tests don't pass during the build in Ubuntu noble, [...] Ran 33143 tests in 1297.905s FAILED (failures=7, errors=71, known_failure_count=49) 2133 tests skipped see https://launchpad.net/ubuntu/+source/breezy/3.3.5-1ubuntu1 for the complete build logs. Looking at the build logs, it looks like some plugins are missing, that the Debian build is getting from the net, which it is not allowed to for the build.
Bug#1049440: marked as done (calculix-cgx - build-depends on dropped transitional package.)
Your message dated Mon, 22 Jan 2024 12:04:08 + with message-id and subject line Bug#1049440: fixed in calculix-cgx 2.21+dfsg-1 has caused the Debian Bug report #1049440, regarding calculix-cgx - build-depends on dropped transitional package. 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.) -- 1049440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: calculix-cgx Version: 2.17+dfsg-2 Severity: serious Tags: trixie, sid calculix-cgx build-depends on libgl1-mesa-glx which is no longer built by the mesa source package. It is still present in unstable and on a couple of architectures in testing as a cruft package, but it is completely gone from most architectures in testing. Please update your build-dependencies as appropriate. --- End Message --- --- Begin Message --- Source: calculix-cgx Source-Version: 2.21+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of calculix-cgx, 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 1049...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated calculix-cgx 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: Mon, 22 Jan 2024 12:40:29 +0100 Source: calculix-cgx Architecture: source Version: 2.21+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Closes: 1049440 Changes: calculix-cgx (2.21+dfsg-1) unstable; urgency=medium . * Team upload. * Do not Build-Depend on transitional package libgl1-mesa-glx Closes: #1049440 * Standards-Version: 4.6.2 (routine-update) * Remove trailing whitespace in debian/copyright (routine-update) * Add salsa-ci file (routine-update) * watch file standard 4 (routine-update) Checksums-Sha1: 86f4a1309bbd99359931b7b11d5d7c5c030e0c12 2264 calculix-cgx_2.21+dfsg-1.dsc d6f7322f2102569ec33efd615e727e66ca89a258 3700508 calculix-cgx_2.21+dfsg.orig.tar.xz 098849f854390dca461559ec7c44dfefad829a7d 20452 calculix-cgx_2.21+dfsg-1.debian.tar.xz 34e16a5c00a3d6c6803be14e3c7d9fb4221c02cb 9222 calculix-cgx_2.21+dfsg-1_amd64.buildinfo Checksums-Sha256: acc934ac83a33cc7247c75c99a32795076d0f4ce885f1c34b40de59a8e2103da 2264 calculix-cgx_2.21+dfsg-1.dsc 0deedc755c921adcb7761ef2510031e29566b506a99a36dec251c7ea58f16a81 3700508 calculix-cgx_2.21+dfsg.orig.tar.xz 2cfe361bdba1bd9a2062eedefb90a615e970b67018f62fc92cb8bb936dfc71c4 20452 calculix-cgx_2.21+dfsg-1.debian.tar.xz d074b07c1d177488435f0cec7a2db4ae85a9c14d15c65c47f6ec422b7a42d8f9 9222 calculix-cgx_2.21+dfsg-1_amd64.buildinfo Files: 1c92b2ff355a9961cfb37f23da47c85e 2264 science optional calculix-cgx_2.21+dfsg-1.dsc 9a7388393f1018e8c1d0e99fd4e3c393 3700508 science optional calculix-cgx_2.21+dfsg.orig.tar.xz 51257024d60850c68f928cd39657a55b 20452 science optional calculix-cgx_2.21+dfsg-1.debian.tar.xz d7d2fc072dcb22258f15cfae756ec952 9222 science optional calculix-cgx_2.21+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmWuVeIRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGZQxAAjqhZENZStF8nn8FCa2JH4DZ24EQo0EFS +f1Jl80I673ws+qbHQ39SKkpT3ytt3npyqTe7k9hu8Dxi/DQCHvACW18e07039Ae e8krVH0SqlaN3bBR6nE5FCPHQPg8rHBldd1+RUqYArzAOdKoxA83f9bwQ/A8b4jR 8Go+Ra07PSg13cxfNEA5h0+WFMSGK+0IwsvA1NE5WSWoctwXQdv6eK/AwJmtThMM HXjziITobl2PgBOyN8f8X4k37hPB/dZLbAJbSnl4AKLamAMKJNb17n+Eik6zE6Pg KdoLh9nJkpQ6KnxxVmJIgZfY2trHbYrRvS7xt054UjC66hHhyb16CknVMDqo+4O/ buiBmDvBuwABRtSCjHW0G4bFeZlCWXHY0aFc5Vz/oC2NBCwR4C1Io/e6zgt9IOsh /IOlWazQkUauEi/TFXTAx1Rb/CcKfm8RTv6z+W+dJkoTpExXnnoDBSwnRmFWf6gk bXLHom1iSJs96gyZG+2RcKoeb70mapNK2+yn4CAetXKnjAuDIZeQXfkYVY5rGVVJ AzZLk62DTUvnPS4r8LxkgW5fIbNlk807Ux7KCs4gj7x9dkUn2alOffdnQ8lAjL1e vsWtoPC7sogyvtlxjwgeJEI1LUTJLSIo7Lq0+icbhBPdlIpd5ZAjGkvGK0SaRABI P5GpKwtG/xk= =dh+t -END PGP SIGNATURE End Message ---
Bug#1059484: marked as done (rasdaemon: autopkgtest failure: cannot access '/var/lib/rasdaemon/ras-mc_event.db')
Your message dated Mon, 22 Jan 2024 11:19:58 + with message-id and subject line Bug#1059484: fixed in rasdaemon 0.8.0-2 has caused the Debian Bug report #1059484, regarding rasdaemon: autopkgtest failure: cannot access '/var/lib/rasdaemon/ras-mc_event.db' 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.) -- 1059484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rasdaemon Version: 0.8.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package rasdaemon, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=rasdaemon https://ci.debian.net/data/autopkgtest/testing/amd64/r/rasdaemon/40156577/log.gz 34s ls: cannot access '/var/lib/rasdaemon/ras-mc_event.db': No such file or directory 34s autopkgtest [11:52:08]: test ras-mc-ctl OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: rasdaemon Source-Version: 0.8.0-2 Done: Russell Coker We believe that the bug you reported is fixed in the latest version of rasdaemon, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Russell Coker (supplier of updated rasdaemon 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: Tue, 16 Jan 2024 23:58:41 +1100 Source: rasdaemon Architecture: source Version: 0.8.0-2 Distribution: unstable Urgency: medium Maintainer: Taihsiang Ho (tai271828) Changed-By: Russell Coker Closes: 1054152 1059484 Changes: rasdaemon (0.8.0-2) unstable; urgency=medium . * Sponsored upload for Taihsiang Ho (tai271828) * When running autopkgtest, use isolation-machine so we can skip tests requiring to interact with things which fail in a container. This matters particularly with the migration from Sid to Testing for Debian Continuous Integration. * Add more tests that could run in any environment so autopkgtest will not return code 8 i.e. "No tests in this package". This will ensure Debian Continuous Integration moving forward when migrating rasdaemon from Sid to Testing. * Closes: #1059484 * Backporting f1ea76375281001cdf4a048c1a4a24d86c6fbe48 from the upstream to resolve Bug#1054152 (Closes: #1054152). Checksums-Sha1: 6297e0e90930c2e8fce42ec97c663135f23853eb 1978 rasdaemon_0.8.0-2.dsc 69af1c3de39c1df0a611eda26dc262d47dd29581 6296 rasdaemon_0.8.0-2.debian.tar.xz 47f06180ed88c1842a4f16ce880bab617dd449bd 7141 rasdaemon_0.8.0-2_amd64.buildinfo Checksums-Sha256: fabd0b597924a1cfd632bf9817fbcf3f0271332488ceb86b18618d5352e19a6c 1978 rasdaemon_0.8.0-2.dsc 3b0352021c36ee15ecd003bec4f9ac127afd207f17b707c5a77a76d4d835887d 6296 rasdaemon_0.8.0-2.debian.tar.xz e26b2a4d2869b07e4b00830741b350b88801ae912e15d1a629bf7e9521e75f8b 7141 rasdaemon_0.8.0-2_amd64.buildinfo Files: 41a9f5b2352e7c3c9b56edfd75a9941b 1978 admin optional rasdaemon_0.8.0-2.dsc 31d969c98a050cbfca2540dc8ffd88d6 6296 admin optional rasdaemon_0.8.0-2.debian.tar.xz 14d4e0ca5652789abc65d600ce04cd7c 7141 admin optional rasdaemon_0.8.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEn31hncwG9XwCqmbH0UHNMPxLj3kFAmWuTLgACgkQ0UHNMPxL j3m2WxAArE6OYCZxA6PkJHFQ5PaTKBB5+YGrUofI9lRmXfOSe/BhIw9dm6qcNjYO uRKAzo4Wk7q8C4ekONifMz4cT/dhQE2Q8jLHYvFkGyNXynrxvd9vDE7W053Zz0+O 2FdnU0Kpfn3SQBRTg4nnnih2TGR2uuaBZiv1xfTSf92t/leHbr/DfVxbIg6x6m9g 7pKsNy6NgcF61T89LjE58GUgkRyG9hZaGX15cE+HBQCRLVb6nDwm4GfmibGU+2E+ gSvz+FY+uhuHUQiYUAyq8USSUXw/HBYFugHoS6rUAIG4fQ6AsHqH87kc5vXH96V8 zksg6dq7R1YBG4HY9Q2BCNEItJGzNom7ZQ/Qfx7vyxQ7JyZo2kXQYO/IAGUat0oI ed+nOOJYoQbARsK/fp+18K3UZS8JNFUjWq9HDHKNFFtZcqqJxWLEX4hqLYvpaGGk
Bug#1061295: afterstep: binary-all FTBFS
Source: afterstep
Version: 2.2.12-16
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=afterstep=all=2.2.12-16=1705880091=0
...
debian/rules override_dh_install
make[1]: Entering directory '/<>'
* Install dynamic (common) *
cd DEB-build-tree/build-dynamic/src/ASDocGen && \
/usr/bin/make install.doc_html DESTDIR=/<>/debian/tmp
SHELL="/bin/sh -e" LDCONFIG=/bin/true CP="cp -a" INSTALL_PROGRAM="install -p -m
755" INSTALL_DATA="install -p -m 644" INSTALL_SCRIPT="install -p -m 755"
INSTALL_HEADER="install -p -m 644" INSTALL_LIB="install -p -m 644"
INSTALL="install -p"
AFTER_DOC_DIR=/<>/debian/tmp/usr/share/doc/afterstep-data
make[2]: Entering directory
'/<>/DEB-build-tree/build-dynamic/src/ASDocGen'
Generating man pages ...Done
All Done
Installing application HTML pages using command -
"install -p -m 644
/<>/debian/tmp/usr/share/doc/afterstep-data/html/"
ASDatabase.html ASDatabaseEntry.html AfterStep.html Align.html Animate.html
AnimateTypes.html Arrange.html AutoExec.html BalloonContents.html Base.html
Bevel.html ColorScheme.html Feel.html FeelWindowBox.html Functions.html
Glossary.html Gravity.html Look.html MyBackground.html MyFrame.html
MyStyle.html Pager.html PagerDecorations.html Placement.html Sound.html
SoundEvents.html SupportedHints.html TbarLayout.html Wharf.html
WharfFolders.html WharfSounds.html WinCommand.html WinList.html WinTabs.html
afterstep_faq.html asimagexml.html bg.html index.html monitorwharf.html
monitorwharf_asdoc.html monitorwharf_cycle.html monitorwharf_mnt.html
monitorwharf_ps.html monitorwharf_time.html monitorwharf_top.html
monitorwharf_xeyes.html pager_bg.html pager_focused.html pager_intro.html
pager_label.html pager_selected.html pager_unfocused.html preface.html
start_menu.html start_menu_highlight.html start_menu_main.html
start_menu_small.html start_menu_title.html visualselect.html wharf_asmix.html
wharf_filemgr.html wharf_gimp.html wharf_intro.html wharf_irc.html
wharf_mc.html wharf_moz.html wharf_spreadsheet.html wharf_term.html
wharf_wordprocessor.html wharf_xmms.html windecor.html windecor_buttons.html
windecor_frame.html windecor_title.html window_list.html winlist_focused.html
winlist_intro.html winlist_sticky.html winlist_unfocused.html
Done
Installing application images using command -
"install -p -m 644
/<>/debian/tmp/usr/share/doc/afterstep-data/html/images/"
Info.png Pager.jpg asdoc_screenshot.jpg aterm.jpg desktop.png monitorwharf.jpg
pager.jpg pager.png start_menu.jpg start_menu.png whandling.png wharf.jpg
wharf.png window_list.jpg winlist.jpg winlist.png
Done
Installing API HTML docs using command -
"install -p -m 644
/<>/debian/tmp/usr/share/doc/afterstep-data/html/images/"
Glossary.html afterimage.html ascmap.html ascompose.html asflip.html
asfont.html asgrad.html asimage.html asimagexml.html asmerge.html asscale.html
astext.html astile.html asview.html asvisual.html blender.html char2uni.html
common.html export.html imencdec.html import.html index.html transform.html
ximage.html
Done
make[2]: Leaving directory
'/<>/DEB-build-tree/build-dynamic/src/ASDocGen'
#
mkdir -p /<>/debian/tmp/usr/share/doc/libafterimage-dev
mv -T /<>/debian/tmp/usr/share/doc/afterstep-data/html/API \
/<>/debian/tmp/usr/share/doc/libafterimage-dev/html
#
# The .so files cannot be passed to dh_install -X...
for lib in libAfterConf libAfterStep libASGTK; do \
rm -f /<>/debian/tmp/usr/lib/x86_64-linux-gnu/${lib}.so; \
done
sh debian/scripts/move_spare_manpages "/<>/debian/tmp"
/<>/debian/tmp/usr/bin does not exists
make[1]: *** [debian/rules:222: override_dh_install] Error 1
Processed: closing 1056465
Processing commands for cont...@bugs.debian.org: > # Fixed by src:kombu-5.3.5-1. > close 1056465 Bug #1056465 [src:python-django-celery-beat] python-django-celery-beat's autopkg tests fail with Python 3.12 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1056465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052852: marked as done (python-django-crispy-forms: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1)
Your message dated Mon, 22 Jan 2024 10:05:09 +
with message-id
and subject line Bug#1052852: fixed in python-django-crispy-forms 2.1-2
has caused the Debian Bug report #1052852,
regarding python-django-crispy-forms: FTBFS: make[1]: *** [debian/rules:17:
override_dh_auto_test] Error 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-crispy-forms
Version: 1.14.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYTHONPATH=. DJANGO_SETTINGS_MODULE=crispy_forms.tests.test_settings py.test
> crispy_forms/tests --cov=crispy_forms
> = test session starts
> ==
> platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0
> django: settings: crispy_forms.tests.test_settings (from env)
> rootdir: /<>
> configfile: setup.cfg
> plugins: cov-4.1.0, django-4.5.2
> collected 624 items
>
> crispy_forms/tests/test_dynamic_api.py . [
> 5%]
> sss [
> 15%]
> crispy_forms/tests/test_form_helper.py . [
> 20%]
> [
> 32%]
> sss.s..s...ss..s...ss.sss.ss [
> 43%]
> ss.sss.sss.sss.ss.sss.s [
> 48%]
> crispy_forms/tests/test_layout.py ss [
> 54%]
> s..sss..FFsss.sss.ss..ss.... [
> 65%]
> ..sss.sss.sss. [
> 67%]
> crispy_forms/tests/test_layout_objects.py s. [
> 72%]
> ..s...sss.sss.sss.s...s...s...s...s...s...s...s...s...s...s...s...sss.s. [
> 84%]
> ..ss.sss..sss. [
> 87%]
> crispy_forms/tests/test_tags.py [
> 93%]
> s... [
> 94%]
> crispy_forms/tests/test_utils.py sss.
> [100%]
>
> === FAILURES
> ===
> _ test_keepcontext_context_manager[bootstrap3]
> _
>
> settings =
>
> @only_bootstrap
> def test_keepcontext_context_manager(settings):
> # Test case for issue #180
> # Apparently it only manifest when using render_to_response this
> exact way
> form = CheckboxesSampleForm()
> form.helper = FormHelper()
> # We use here InlineCheckboxes as it updates context in an unsafe way
> form.helper.layout = Layout("checkboxes",
> InlineCheckboxes("alphacheckboxes"), "numeric_multiple_checkboxes")
> context = {"form": form}
>
> response = render(request=None,
> template_name="crispy_render_template.html", context=context)
>
> if settings.CRISPY_TEMPLATE_PACK == "bootstrap":
> assert response.content.count(b"checkbox inline") == 3
> elif settings.CRISPY_TEMPLATE_PACK == "bootstrap3":
> > assert response.content.count(b"checkbox-inline") == 3
> E assert 0 == 3
> E+ where 0 = 0x2d267f0>(b'checkbox-inline')
> E+where
> = b'\n\n\n\n class="control-group"> id="id_numeric_multiple_checkboxes_2" value="3" >Option three\n
>\n\n'.count
> E+ where b'\n\n\n\n id="div_id_checkboxes" class="control-group"> class="control-label...checkboxes" id="id_numeric_multiple_checkboxes_2"
> value="3" >Option three\n \n\n' =
> .content
>
> crispy_forms/tests/test_layout.py:579: AssertionError
> _ test_keepcontext_context_manager[bootstrap4]
> _
>
> settings =
>
> @only_bootstrap
> def test_keepcontext_context_manager(settings):
> # Test case for issue #180
> # Apparently it only manifest when using render_to_response this
> exact way
> form = CheckboxesSampleForm()
> form.helper = FormHelper()
> # We use here InlineCheckboxes as it updates
Processed: Re: Bug#1061233: src:nitime: fails to migrate to testing for too long: autopkgtest regression on 32 bits systems
Processing control commands:
> tags -1 upstream
Bug #1061233 {Done: Paul Gevers } [src:nitime] src:nitime:
fails to migrate to testing for too long: autopkgtest regression on 32 bits
systems
Added tag(s) upstream.
> forwarded -1 https://github.com/nipy/nitime/issues/214
Bug #1061233 {Done: Paul Gevers } [src:nitime] src:nitime:
fails to migrate to testing for too long: autopkgtest regression on 32 bits
systems
Set Bug forwarded-to-address to 'https://github.com/nipy/nitime/issues/214'.
--
1061233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1061233: src:nitime: fails to migrate to testing for too long: autopkgtest regression on 32 bits systems
Control: tags -1 upstream Control: forwarded -1 https://github.com/nipy/nitime/issues/214
Bug#1061281: #1061281: gajim: Fails to start: AttributeError: module 'eventlet.green.select' has no attribute 'epoll'
Dear Shawn, could you check /var/log/dpkg.log which packages have been upgraded recently? My random guess would be python3-trio from 0.22 to 0.23. Maybe you can temporarily downgrade one or the other package to find the culprit? Cheers
Bug#1060777: marked as done (django-filter: build dependency missing in testing: python3-django-crispy-forms)
Your message dated Mon, 22 Jan 2024 09:34:16 + with message-id and subject line Bug#1060777: fixed in python-django-crispy-forms 2.1-1 has caused the Debian Bug report #1060777, regarding django-filter: build dependency missing in testing: python3-django-crispy-forms 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.) -- 1060777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-filter Version: 23.5-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all reverse build dependencies too, nor should a package be allowed to migrate unless all build dependencies are candidate for migration too. However, somehow we ended up in the current state and your source package is missing some Build-Depends for some while now. Not being able to build from source in a suite is an RC bug in that suite. Can you please solve the situation by either helping the maintainer of your Build-Depends to enable migration to testing, or by working around the lack of this build dependency? Paul [1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-django-crispy-forms Source-Version: 2.1-1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of python-django-crispy-forms, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated python-django-crispy-forms package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Jan 2024 09:59:47 +0100 Source: python-django-crispy-forms Architecture: source Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jérémy Lal Closes: 1060777 Changes: python-django-crispy-forms (2.1-1) unstable; urgency=medium . * Team upload * [1ad6c05] New upstream version 2.1 (Closes: #1060777) * [c69b0f6] Let pybuild run tests * [d0c244f] control: Testsuite for pybuild * [3861de1] Standards-Version 4.6.2 * [b81748f] Use github watch file * [e1daf84] Fix build deps * [bfd2e64] Test using bootstrap5 * [1ad5d49] Drop useless overrides * [49c0532] Do not install LICENSE Checksums-Sha1: 33ba07e65926a3fd0908c6e824d3d6e96be345a7 2551 python-django-crispy-forms_2.1-1.dsc c92abef74ff4ba78df2b8e16034906ad0ca9fc9c 274438 python-django-crispy-forms_2.1.orig.tar.gz a2bf806aa91a1f718da4532cfaa13b381b8274be 6984 python-django-crispy-forms_2.1-1.debian.tar.xz c6f913920b1d2c8c956bccbada79bb19a28cb491 7583 python-django-crispy-forms_2.1-1_source.buildinfo Checksums-Sha256: dcd44955d51f899f214db9990bc3f27d16bfbb8753971567bfaf7cdbccf0bc22 2551 python-django-crispy-forms_2.1-1.dsc 2b9e33cd56ba94d8b4dd21df16764ab7a985de5e17069cec722b2b566c7286e0 274438 python-django-crispy-forms_2.1.orig.tar.gz 19b4d603344a0bf16246f9162ad71272f9b292e93d3e3b2af283c0db48e7b755 6984 python-django-crispy-forms_2.1-1.debian.tar.xz 600e32fbc62bb257507091d94204ccd8a2a696d2acab3b50449fd4ff33a8dd4f 7583 python-django-crispy-forms_2.1-1_source.buildinfo Files: e83585c6c554b24e267707bfaa670384 2551 python optional python-django-crispy-forms_2.1-1.dsc c91452fdd5f94d3466a10d7cc534bac6 274438 python optional python-django-crispy-forms_2.1.orig.tar.gz 56d3b2dbf3d68b2e921674a15952b00b 6984 python optional python-django-crispy-forms_2.1-1.debian.tar.xz 483caee21d1c203b928c5bc278ce0586 7583 python optional python-django-crispy-forms_2.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmWuMmYSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0D4sP/10G2ER+lisMDfJB37B4Gl8AkNwgYfdG meCoU3vbRYdDxTRkkZ+FpFO9zdjtM2nSIVC7mvWVRu+UeJMejqGAfvrsmHl/8Ow6 F6d8wFcgtdVskINhniOmZPOtjREZey2avvfSFzvn2+/uJdZJhRp7VakF/pJj9hP4
Bug#1014862: marked as done (vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad")
Your message dated Mon, 22 Jan 2024 10:24:06 +0100 with message-id and subject line Fwd: Bug#1014862 vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad" has caused the Debian Bug report #1014862, regarding vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad" 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.) -- 1014862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdr-plugin-markad Version: 0.1.4+git20180120-3 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, vdr-plugin-markad recently started to FTBFS: [...] debian/rules override_dh_auto_install make[1]: Entering directory '/build/vdr-plugin-markad-0.1.4+git20180120' # Do nothing make[1]: Leaving directory '/build/vdr-plugin-markad-0.1.4+git20180120' dh_install dh_install: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_install: warning: Cannot find (any matches for) "command/markad" (tried in ., debian/tmp) dh_install: warning: vdr-markad missing files: command/markad dh_install: error: missing files, aborting make: *** [debian/rules:10: binary] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Andreas vdr-plugin-markad_0.1.4+git20180120-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 0.1.4+git20180120-3 the bug was already fixed at least with the previous uploaded version 0.1.4+git20180120-3. binOdtyrrKyee.bin Description: application/extension-eml OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Bug#1014862 vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad"
Processing commands for cont...@bugs.debian.org: > notfound 1014862 3.4.5-1 Bug #1014862 [src:vdr-plugin-markad] vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad" Ignoring request to alter found versions of bug #1014862 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1014862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
