Bug#1027245: marked as done (symfit: autopkgtest fail with numpy/1.24.1)
Your message dated Sat, 28 Jan 2023 07:59:20 + with message-id and subject line Bug#1027245: fixed in symfit 0.5.5-2 has caused the Debian Bug report #1027245, regarding symfit: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: symfit Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- Source: symfit Source-Version: 0.5.5-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of symfit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated symfit 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: Sat, 28 Jan 2023 12:43:48 +0530 Source: symfit Architecture: source Version: 0.5.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Nilesh Patra Closes: 1027245 Changes: symfit (0.5.5-2) unstable; urgency=medium . * Team Upload. * Remove dep on matplotlib-doc and replace local sphinx inventory with URL (Closes: #1027245) * Bump Standards-Version to 4.6.2 (no changes needed) Checksums-Sha1: 807e6a540235746783175c653d6cba6d201bc5c8 1819 symfit_0.5.5-2.dsc ce17b20c12e131145de1999d9bf09081fb0516f8 3760 symfit_0.5.5-2.debian.tar.xz 5db97657fc81684670f7ddb193387815b084e747 12768 symfit_0.5.5-2_amd64.buildinfo Checksums-Sha256: f784606c46b3d026912613faf3ddd93503091bede6793ef379317b080ac69e25 1819 symfit_0.5.5-2.dsc c4d52ec459ac03e77a931bc21e56514d77747bd077e91fa063963b9012f77b2b 3760 symfit_0.5.5-2.debian.tar.xz b7ce355577da9aa498cc8c76e6dade46eef8fb07de59243ac294e10ff014ee84 12768 symfit_0.5.5-2_amd64.buildinfo Files: 6e0d64f5ae5bd0de03a40fe1383508e4 1819 python optional symfit_0.5.5-2.dsc dcfccc4a85692c941cef8bad203d2960 3760 python optional symfit_0.5.5-2.debian.tar.xz 698c6ce4fef21102ad5273a3d2cf09ff 12768 python optional symfit_0.5.5-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY9TPWgAKCRAqJ5BL1yQ+ 2sEFAP9dQxJEvqDal8L3v/UdvyDtkK6dPqG0iqJlfUHNUH8uIQD/RKvnoduDFxHC LGJEna7i1T3c4MDbZylj9o1qEde+egk= =ks2r -END PGP SIGNATURE End Message ---
Bug#1008220: Help needed to finalise the oneTBB migration of flexbar
Am Fri, Jan 27, 2023 at 11:12:10PM +0100 schrieb Étienne Mollier: > favor of funtion tbb::parallel_pipeline). I'm a bit dry for the > moment and will have the weekend busy, so if someone wants to > take over from here, please go ahead. I'll see what I can do, thanks in any case Andreas. -- http://fam-tille.de
Processed: closing 1027638
Processing commands for cont...@bugs.debian.org: > close 1027638 Bug #1027638 [src:pdm] pdm: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1027638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027382: Please, minimize your build chroots
On 2023-01-28 00:20, Santiago Vila wrote: Release Policy exists as a canonical list of what should be RC and > what not, and it's intended to avoid stupid discussions like this one. Extending build-essential is easier than asking many people to do pointless work to satisfy a set of non-existing users. It is not like we had several reports of people complaining they can't build a package because they are in an environment without tzdata. It is not OK to create problems to force many volunteers to do extra work.
Bug#1027305: Bug-Investigation
It seems the module does not yet support Python newer than 3.7 (3.9 in the latest version on Github), see https://github.com/ilius/pyglossary/tree/master/pyglossary/plugin_lib Copying the folder pyglossary/plugin_lib/py37 to py310 and py311 fixes this build-error for me.
Bug#1027354: marked as done (ruby-fogbugz: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such file -- mocha
Your message dated Sat, 28 Jan 2023 14:48:53 +0530 with message-id <20230128091853.cuzx362wehupa...@nileshpatra.info> and subject line Re: ruby-fogbugz: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such file -- mocha/mini_test (LoadError) has caused the Debian Bug report #1027354, regarding ruby-fogbugz: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such file -- mocha/mini_test (LoadError) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-fogbugz Version: 0.2.1-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221230 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is likely due to the upgrade of mocha. See https://lists.debian.org/debian-ruby/2022/12/msg00064.html Relevant part (hopefully): > :85:in > `require': cannot load such file -- mocha/mini_test (LoadError) > from > :85:in > `require' > from /<>/test/test_helper.rb:10:in `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/adapters/xml/crack_test.rb:1:in ` (required)>' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in > `block in ' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `select' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `' > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/adapters/xml/crack_test.rb" "test/interface_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2022/12/30/ruby-fogbugz_0.2.1-3.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221230;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221230&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- On Fri, 30 Dec 2022 17:21:46 +0100 Lucas Nussbaum wrote: > Source: ruby-fogbugz > Version: 0.2.1-3.1 > Severity: serious > Justification: FTBFS This builds as of Jan 26. Closing. -- Best, Nilesh signature.asc Description: PGP signature --- End Message ---
Processed: limit source to tar, tagging 1026204
Processing commands for cont...@bugs.debian.org: > limit source tar Limiting to bugs with field 'source' containing at least one of 'tar' Limit currently set to 'source':'tar' > tags 1026204 + pending Bug #1026204 [tar] tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028848: python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
reassign 1028848 python-zeroconf 0.47.1-1 fixed 0.47.1-2 close 1028848 stop This was a problem with zeroconf instead, which has been fixed. Re-assigned and closed. -- Best, Nilesh signature.asc Description: PGP signature
Processed (with 1 error): Re: python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Processing commands for cont...@bugs.debian.org:
> reassign 1028848 python-zeroconf 0.47.1-1
Bug #1028848 [src:python-miio] python-miio: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Bug reassigned from package 'src:python-miio' to 'python-zeroconf'.
No longer marked as found in versions python-miio/0.5.0.1-2.
Ignoring request to alter fixed versions of bug #1028848 to the same values
previously set
Bug #1028848 [python-zeroconf] python-miio: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
There is no source info for the package 'python-zeroconf' at version '0.47.1-1'
with architecture ''
Unable to make a source version for version '0.47.1-1'
Marked as found in versions 0.47.1-1.
> fixed 0.47.1-2
Unknown command or malformed arguments to command.
> close 1028848
Bug #1028848 [python-zeroconf] python-miio: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1028848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed vers
Processing commands for cont...@bugs.debian.org:
> fixed 1028848 0.47.1-2
Bug #1028848 {Done: Nilesh Patra } [python-zeroconf]
python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.10 3.11" returned exit code 13
There is no source info for the package 'python-zeroconf' at version '0.47.1-2'
with architecture ''
Unable to make a source version for version '0.47.1-2'
Marked as fixed in versions 0.47.1-2.
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1028848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: grep: inconsistent behaviour with anchored regex containing back-references
Processing control commands:
> submitter -1 Thorsten Glaser
Bug #1029235 {Done: Santiago Ruano Rincón } [grep] grep:
sometimes mistakenly matches lines when last of multiple patterns includes
backref
Changed Bug submitter to 'Thorsten Glaser ' from 'g1
'.
--
1029235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029235: grep: inconsistent behaviour with anchored regex containing back-references
Control: submitter -1 Thorsten Glaser
On Fri, 02 Dec 2022 02:12:20 +0100 Thorsten Glaser wrote:
> Package: grep
> Version: 3.6-1
> Followup-For: Bug #930247
> X-Debbugs-Cc: t...@mirbsd.de
> Control: found 930247 3.8-3
> Control: severity 930247 serious
> Control: retitle 930247 grep: does not handle backreferences correctly,
> violating POSIX
>
> I’m running into this, in stable and unstable both:
>
> (sid-amd64)tglase@tglase:/tmp $ cat x
> Total failed: 0
> Total failed: 1 (1 ignored)
> Total failed: 2 (1 ignored)
> Total failed: 1 (2 ignored)
> Total failed: 1
> Total failed: 111
> (sid-amd64)tglase@tglase:/tmp $ grep -e '^Total failed: 0$' -e '^Total
> failed: \([0-9]*\) (\1 ignored)$' x
> Total failed: 0
> Total failed: 1 (1 ignored)
> Total failed: 2 (1 ignored)
> Total failed: 1 (2 ignored)
>
> By contrast, BSD handles it correctly:
>
> tg@tglase-bsd:/tmp $ grep -e '^Total failed: 0$' -e '^Total failed:
> \([0-9]*\) (\1 ignored)$' x
> Total failed: 0
> Total failed: 1 (1 ignored)
>
> POSIX:
>
> 3. The back-reference expression '\n' shall match the same (possibly
>empty) string of characters as was matched by a subexpression
>enclosed between "\(" and "\)" preceding the '\n'. The character
>
> via
> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03
> from https://pubs.opengroup.org/onlinepubs/9699919799/utilities/grep.html
>
> Please fix this clear standards violation; it makes grep
> virtually unusable.
>
>
>
> -- System Information:
> Debian Release: 11.5
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
> 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.10.0-19-amd64 (SMP w/2 CPU threads)
> Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8),
> LANGUAGE not set
> Shell: /bin/sh linked to /bin/lksh
> Init: sysvinit (via /sbin/init)
>
> Versions of packages grep depends on:
> ii dpkg 1.20.12
> ii install-info 6.7.0.dfsg.2-6
> ii libc6 2.31-13+deb11u5
> ii libpcre3 2:8.39-13
>
Bug#1029044: marked as done (gcc-12-cross-mipsen: source and binary version go out of sync)
Your message dated Sat, 28 Jan 2023 10:50:19 + with message-id and subject line Bug#1029044: fixed in gcc-12-cross-mipsen 3+c2 has caused the Debian Bug report #1029044, regarding gcc-12-cross-mipsen: source and binary version go out of sync 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.) -- 1029044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-12-cross-mipsen Version: 1+c2 Severity: serious Dear maintainer, The current version in unstable is stuck, because the mips64el build is kept in Uploaded state. Asking around on #d-buildd, I got the following discussion: [20:09:34] mips64el 3days in uploaded state feels like an issue, right? https://buildd.debian.org/status/package.php?p=gcc-12-cross-mipsen [20:18:32] probably means dak rejected it [20:18:45] Your upload included the binary package cpp-12-mips-linux-gnu, version 12.2.0-13cross1, for mips64el, [20:18:48] however unstable already has version 12.2.0-14cross2. [20:19:09] coccia:/srv/ftp-master.debian.org/queue/reject/gcc-12-cross-mipsen_3+c1_mips64el-buildd.changes.reason [20:29:57] the higher version is [20:29:57] Source: gcc-12-cross-mipsen (2+c1) [20:30:23] so the generated version numbers are broken [20:32:07] not for the first time afair [[21:04:30] adsb: thanks for looking; but the source is 3+c1, no? or did the older one generate a newer binary? You may want to check your logic. Paul --- End Message --- --- Begin Message --- Source: gcc-12-cross-mipsen Source-Version: 3+c2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-12-cross-mipsen, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-12-cross-mipsen 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: Sat, 28 Jan 2023 11:25:26 +0100 Source: gcc-12-cross-mipsen Architecture: source Version: 3+c2 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 1029044 Changes: gcc-12-cross-mipsen (3+c2) unstable; urgency=medium . * Build using gcc 12.2.0-14. Closes: #1029044. * Bump standards version. Checksums-Sha1: 992088ef3fc4b1fa8b64465e9af303eaaae3377e 60977 gcc-12-cross-mipsen_3+c2.dsc 00a52c759bd61749d7f3580969624281936df9e7 44056 gcc-12-cross-mipsen_3+c2.tar.xz eeb85a999da8291ae3c5b243f55d64ef426d11b4 7384 gcc-12-cross-mipsen_3+c2_source.buildinfo Checksums-Sha256: a43414ff59b3a19cbe708187f1a5c977674f2eec806329cf2f0fadabb711ad04 60977 gcc-12-cross-mipsen_3+c2.dsc c2e52d51305af238690b430f2d1e51b26977d614add237522c8ecd3fdc1dd1db 44056 gcc-12-cross-mipsen_3+c2.tar.xz 1bdbc303343761be5c4be51f34b65f830a081c41ec1708a5766148dd607efc96 7384 gcc-12-cross-mipsen_3+c2_source.buildinfo Files: f7e30b67520e541638cf8085ba8f0ef7 60977 devel optional gcc-12-cross-mipsen_3+c2.dsc ac2a75b88b43321095d7371e985397cb 44056 devel optional gcc-12-cross-mipsen_3+c2.tar.xz fcb9acb7bb3983f069672d9db771c4d1 7384 devel optional gcc-12-cross-mipsen_3+c2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmPU+TEQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9ax+EADKBJ2a0rvLjLwtEyiPa+vjJ8L5iBdlgnVk MloNgEaN0fxkGSREUEXSDhQ/qVQPunzJ5NIYho46/A0opom8otyUEXZ8FfyB8MFc 3qu9yXDcz/5JvoJ9qztVsDv5aJmJ0ZN3u01FyIzcAnUVzmOugRcnEPIaIEkQlAgF PtvhLRgizTqvQxwe10PozM1xafY7MotakX4QTS830YnXI3pDueZ2COdaSpVqopwz n5BwYa8UBDwtF+1kMeA9lDq1A0FQXKobA6HhxOktXvnTahC+C+uHFu/r+WxBPS5z tov83CaokTfSnjC4ekKV57GZN6hyN5JcoRi+6s7LN5YscslI7xV4j0hzoNOjBtF9 kB9rpU32bcLtsxzXPXwkT5r2iTnY/LDgaSKXNDgW1QImgn9MvX1fBi2hfiCAvzVo MgzuRYypnwsMKKEVkDZ+/nd5GCdXqRJSe1uM0Z4Y9LxAD0jVPbOiMFTb4hcdvvmP NvgI84iwUNdzPMv1x6vArve2xc+FT5ylHdmf9ivBjvr/GIpSZKK7zo/KuoO/AP4L h8TjVURcWpridtuSpEmjpHNrSiPJxMLrv3W36/2BzW+z1HwscsfX362RDzIVlyeX XEW/3ddFAtWGhsPi4IasZvP5BWvDdGZkPj8oSLH+ZmkY1ht9oGA8DQb05vhtypD9 3XvmURpt6A== =dMdt -END PGP SIGNATURE End Message ---
Processed: severity of 1029806 is serious, tagging 1029806
Processing commands for cont...@bugs.debian.org: > severity 1029806 serious Bug #1029806 [steam-installer] steam-installer: Launching Steam (Failed). You are not authorised to execute this file Severity set to 'serious' from 'important' > tags 1029806 + pending Bug #1029806 [steam-installer] steam-installer: Launching Steam (Failed). You are not authorised to execute this file Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1026496 1024564
Processing commands for cont...@bugs.debian.org:
> forcemerge 1026496 1024564
Bug #1026496 [src:django-assets] django-assets: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.11 3.10" returned exit code
13
Bug #1024287 [src:django-assets] django-assets: FTBFS against python 3.11
Bug #1024564 [src:django-assets] django-assets FTBFS: re.error: global flags
not at the start of the expression at position 6
Set Bug forwarded-to-address to
'https://github.com/miracle2k/django-assets/pull/104'.
Severity set to 'serious' from 'important'
Marked as found in versions django-assets/2.0-2.
Added tag(s) sid and bookworm.
Bug #1024287 [src:django-assets] django-assets: FTBFS against python 3.11
Merged 1024287 1024564 1026496
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1024287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024287
1024564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024564
1026496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1024287: django-assets: diff for NMU version 2.0-2.1
Control: tags 1024287 + patch Control: tags 1024287 + pending Dear maintainer, I've prepared an NMU for django-assets (versioned as 2.0-2.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru django-assets-2.0/debian/changelog django-assets-2.0/debian/changelog --- django-assets-2.0/debian/changelog 2021-09-04 21:49:06.0 +0300 +++ django-assets-2.0/debian/changelog 2023-01-28 13:12:06.0 +0200 @@ -1,3 +1,10 @@ +django-assets (2.0-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Add proposed fix for Python 3.11 compatibility. (Closes: #1024287) + + -- Adrian Bunk Sat, 28 Jan 2023 13:12:06 +0200 + django-assets (2.0-2) unstable; urgency=low [ Debian Janitor ] diff -Nru django-assets-2.0/debian/patches/0001-Global-regex-flags-must-be-at-the-start-of-regex-in-.patch django-assets-2.0/debian/patches/0001-Global-regex-flags-must-be-at-the-start-of-regex-in-.patch --- django-assets-2.0/debian/patches/0001-Global-regex-flags-must-be-at-the-start-of-regex-in-.patch 1970-01-01 02:00:00.0 +0200 +++ django-assets-2.0/debian/patches/0001-Global-regex-flags-must-be-at-the-start-of-regex-in-.patch 2023-01-28 13:11:44.0 +0200 @@ -0,0 +1,25 @@ +From e57c5c3c02d84069600916fed74f165819393487 Mon Sep 17 00:00:00 2001 +From: Jonatan Heyman +Date: Thu, 10 Nov 2022 23:26:07 +0100 +Subject: Global regex flags must be at the start of regex in Python 3.11 + +--- + django_assets/glob.py | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/django_assets/glob.py b/django_assets/glob.py +index 66a9531..73d961c 100644 +--- a/django_assets/glob.py b/django_assets/glob.py +@@ -121,7 +121,7 @@ def translate(pat): + res = '%s([%s])' % (res, stuff) + else: + res = res + re.escape(c) +-return res + '\Z(?ms)' ++return '(?ms)' + res + '\Z' + + + """Filename globbing utility.""" +-- +2.30.2 + diff -Nru django-assets-2.0/debian/patches/series django-assets-2.0/debian/patches/series --- django-assets-2.0/debian/patches/series 2021-09-04 21:49:06.0 +0300 +++ django-assets-2.0/debian/patches/series 2023-01-28 13:12:01.0 +0200 @@ -1,3 +1,4 @@ 01-webassets_version.patch 02-intersphinx.patch 0003-Patch-pytest-plugin-to-check-whether-we-are-running-.patch +0001-Global-regex-flags-must-be-at-the-start-of-regex-in-.patch
Processed: django-assets: diff for NMU version 2.0-2.1
Processing control commands:
> tags 1024287 + patch
Bug #1024287 [src:django-assets] django-assets: FTBFS against python 3.11
Bug #1024564 [src:django-assets] django-assets FTBFS: re.error: global flags
not at the start of the expression at position 6
Bug #1026496 [src:django-assets] django-assets: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.11 3.10" returned exit code
13
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> tags 1024287 + pending
Bug #1024287 [src:django-assets] django-assets: FTBFS against python 3.11
Bug #1024564 [src:django-assets] django-assets FTBFS: re.error: global flags
not at the start of the expression at position 6
Bug #1026496 [src:django-assets] django-assets: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.11 3.10" returned exit code
13
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
--
1024287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024287
1024564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024564
1026496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027382: Please, minimize your build chroots
El 28/1/23 a las 10:11, Vincent Bernat escribió: On 2023-01-28 00:20, Santiago Vila wrote: Release Policy exists as a canonical list of what should be RC and > what not, and it's intended to avoid stupid discussions like this one. Extending build-essential is easier than asking many people to do pointless work to satisfy a set of non-existing users. It is not like we had several reports of people complaining they can't build a package because they are in an environment without tzdata. It is not OK to create problems to force many volunteers to do extra work. Of course, declaring something as not a bug is easier than fixing the bug. But there are several points to consider: * The "extra work" is adding a single line to debian/control. * This is not the right time for a policy change. * I already filed all the bugs I found after building the whole of bookworm from source. I do not expect there are a lot of unreported bugs right now of that type. * Most of the bugs I reported about this are already fixed. * Those bugs are a drop in the ocean of all FTBFS bugs which happened during this release cycle. * Those bugs are RC by definition and have been for a long time. Therefore, this discussion is absolutely pointless. So please stop harassing me about this issue. Thanks.
Processed: reopen until fixed in unstable
Processing commands for cont...@bugs.debian.org:
> reopen 997274
Bug #997274 {Done: Andreas Henriksson } [src:strace] strace:
FTBFS: ../../tests/perf_event_open.c:187:25: error: array subscript ‘struct
perf_event_attr[0]’ is partly outside array bounds of ‘unsigned char[120]’
[-Werror=array-bounds]
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions strace/6.1-0.1~exp1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64
Hi, Le Wed, Jan 18, 2023 at 01:24:37AM +0100, Helge Deller a écrit : > On Sat, 14 Jan 2023 20:38:38 +0100 Andreas Henriksson > wrote: > > Here's a slightly different patch to implement basically the same thing > > Yes, I like this patch better too. Unfortunately, even if both patches allow me to build tar on i386, they also both lead to an FTBFS on amd64. Regards taffit tar_1.34+dfsg-1.2_amd64-2023-01-28T10:47:33Z.build.xz Description: application/xz signature.asc Description: PGP signature
Bug#997274: NMU strace 6.1 for unstable?
Hello Steve McIntyre, As you might have noticed I've taken the liberty to NMU strace into *experimental*. I've done so based on my past experience that strace can have many architecture specific problems, to give me a picture of what the situation is for the latest upstream 6.1 release. (And since it's experimental we have the posisibily to just RM it and act like it never happened.) It seems like mips* has test failures (as usual?!). I've filed https://github.com/strace/strace/issues/235 with my limited conclusions about the issues. Given that strace has not been updated for the entire release cycle and that it's currently RC-buggy, I think it would be useful to try to update it before the 12 Feb freeze. The time window is however very small. Additionally ppc64el seems to have a huge build backlog, so if we want to make it during the limited time window before the freeze we can't wait for the results. (I could possibly build on a ppc64el porterbox to see if I can spot any problems there.) I would like to know what you think about a potential NMU of strace 6.1 to unstable at this point. Probably with mips* tests set to not fail the build (`|| true`). Possibly the same for ppc64el just to make sure it doesn't give any surprises once it finally builds (and the upload is old enough to migrate to testing). If I'm going to do the NMU I'll need to proceed very soon so your input on this would be very appreciated if you could give it ASAP! What do you think? Regards, Andreas Henriksson
Bug#1027877: marked as done (jool: please switch to B-D: dh-sequence-dkms (or dh-dkms))
Your message dated Sat, 28 Jan 2023 12:26:47 + with message-id and subject line Bug#1027877: fixed in jool 4.1.9-1 has caused the Debian Bug report #1027877, regarding jool: please switch to B-D: dh-sequence-dkms (or dh-dkms) 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.) -- 1027877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jool Version: 4.1.8-1 Severity: important Hi, please switch the Build-Depends of your package from `dkms` to `dh-dkms` or (preferrably) `dh-sequence-dkms`. With the latter you can also drop the `--with dkms` argument to `dh`. Please consider adding Testsuite: autopkgtest-pkg-dkms to the source stanza in debian/control s.t. the module gets build-tested against any new kernel version in the archive and breakage is noticed quickly. If you have questions or need help for disabling the module build on unsupported architectures/configurations (that may be exposed when enabling the autopkgtest), don't hesitate to contact me. Thanks Andreas --- End Message --- --- Begin Message --- Source: jool Source-Version: 4.1.9-1 Done: Alberto Leiva Popper We believe that the bug you reported is fixed in the latest version of jool, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Leiva Popper (supplier of updated jool 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: Fri, 27 Jan 2023 10:24:52 -0600 Source: jool Architecture: source Version: 4.1.9-1 Distribution: unstable Urgency: medium Maintainer: Jool Team Changed-By: Alberto Leiva Popper Closes: 1027877 1029268 Changes: jool (4.1.9-1) unstable; urgency=medium . * New upstream release * Switch to dh-sequence-dkms. Closes: #1027877 * Declare Testsuite: autopkgtest-pkg-dkms * Modernize the iptables shared object exports. Closes: #1029268 Checksums-Sha1: 7b6c4738aa4075085b4b4a59674929845ffe18e8 2260 jool_4.1.9-1.dsc d56955d97eb68f5f46863b73a95c67a7fab914b0 623233 jool_4.1.9.orig.tar.gz 924bb2744a4722f8f85ceafe057c13d54c3a2c40 833 jool_4.1.9.orig.tar.gz.asc 99677c4c6159a48ebb779122a45cda8e757c92c4 8948 jool_4.1.9-1.debian.tar.xz 381be2d9af97b7fcdde1f7e53bebb20ce46cb846 7778 jool_4.1.9-1_amd64.buildinfo Checksums-Sha256: 77961b6f33378dcf11ffbdbcf763d69dad45540f17829c56aae6c74172cd0615 2260 jool_4.1.9-1.dsc c569dc5b66b0767a43709df75d1007feb18fb3128c76dfae578cf610c7585dea 623233 jool_4.1.9.orig.tar.gz 25e3c3a8693d8bf1e075b137cab817c90eb09ee07c6c61a99195a5f3d51cb4e9 833 jool_4.1.9.orig.tar.gz.asc 8582400ed9a058ecf81d930973638ba7eb500f36d02688e0cfd3d1ca63a108ee 8948 jool_4.1.9-1.debian.tar.xz 1c91be54522be197e62535e42d4c75d9da8e56a9b2a3766590123dec6c460c1d 7778 jool_4.1.9-1_amd64.buildinfo Files: a07760545e2fa739c4375f6eff70af79 2260 kernel optional jool_4.1.9-1.dsc 54eb74846a5332200df31137d0a22c85 623233 kernel optional jool_4.1.9.orig.tar.gz 1ff98499b429fc51e855eab06bd3fe76 833 kernel optional jool_4.1.9.orig.tar.gz.asc 0e5e0ac71a4f2b31a69a51286290f939 8948 kernel optional jool_4.1.9-1.debian.tar.xz 63bc488acbfa73bfb4167d30b0ac9234 7778 kernel optional jool_4.1.9-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAmPVDS8QHGJlcm5hdEBs dWZmeS5jeAAKCRCVpC/oNTUl+XHAEACIaGCxZPMi0h6zWPJ/clFtmsaeOkYvk1uy D2VN3RERbhd+fKEKycNATXV+q4C9DFmhsAPCPkCJ3AGBKijpj/OTyQiuwf0yWwFP ArVV9kjY/Yhcei2a0URIU/SenFmNc069ViraZGrwyAz9tTW0yo3cfoJXYQwvocdk N86a/+qHkqaFkEhyKUdGgLlPRWA9mjBrG33gbOGeW03dVf4/P5XsoppIaA3Kz+IJ XL4ml1u8W+1Y4VTK+f7m4nwZa0UfFoH+yd0nnoCuCM5Ijz3LMLkZrr9kiPwqTnMT 2vb43JhZ+p7T9zzMbjUOiIDIfwz6v3yN5bY5HhPfjNlP3dK6j3mpioHPdyXpvio1 e20h5EUCgzuQDW8oakZaa2+uiZGPHtWXWLaB/dEKptuAgNZX/gmhNjyRiMC7cRaI qX69YWvaysY/asK7NON/YJ9cOI9plelYJK0CrhyheusZf4Wtz2Hck7JoTYPAhw0i wgFT2V2zzox6TS5yswWB8u4/vjVNcO6dOvWkSz3CHW0sfojKEbQtO5VHLHH+/sgP 0L7BCqCuZSJ7zR+vV64JOHJwKtGT/J3GuUjujxYvio0iTOF+Ao68/xoFfn6LGEZA 6cTqimz2lsPqyedwgIQEg+Pi8SUh2A3jYDJNTvLZU+n6wP8SyZDOxTOQ1nJ6VMCt gzvPEpRvzw== =ALBC -END PGP SIGNATURE End Message ---
Bug#1029268: marked as done (jool: FTBFS: multiple definition of `_init')
Your message dated Sat, 28 Jan 2023 12:26:47 + with message-id and subject line Bug#1029268: fixed in jool 4.1.9-1 has caused the Debian Bug report #1029268, regarding jool: FTBFS: multiple definition of `_init' 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.) -- 1029268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jool Version: 4.1.8-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, jool recently started to FTBFS in sid: ... Making all in iptables make[3]: Entering directory '/build/jool-4.1.8/src/usr/iptables' make libxt_JOOL_SIIT.so; make[4]: Entering directory '/build/jool-4.1.8/src/usr/iptables' make[4]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. cc -Wall -pedantic -std=gnu11 -O2 -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/build/jool-4.1.8=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -D_INIT=libxt_JOOL_SIIT_init -fPIC -c -o libxt_JOOL_SIIT.o libxt_JOOL_SIIT.c; cc -shared -fPIC -Wl,-z,relro -Wl,-z,now -o libxt_JOOL_SIIT.so libxt_JOOL_SIIT.o; /usr/bin/ld: libxt_JOOL_SIIT.o: in function `_init': ./src/usr/iptables/./src/usr/iptables/common.c:132: multiple definition of `_init'; /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o:(.init+0x0): first defined here collect2: error: ld returned 1 exit status make[4]: *** [Makefile:37: libxt_JOOL_SIIT.so] Error 1 rm libxt_JOOL_SIIT.o make[4]: Leaving directory '/build/jool-4.1.8/src/usr/iptables' make[3]: *** [Makefile:28: all] Error 2 make[3]: Leaving directory '/build/jool-4.1.8/src/usr/iptables' make[2]: *** [Makefile:360: all-recursive] Error 1 make[2]: Leaving directory '/build/jool-4.1.8/src/usr' make[1]: *** [Makefile:429: all-recursive] Error 1 make[1]: Leaving directory '/build/jool-4.1.8' dh_auto_build: error: make -j16 returned exit code 2 make: *** [debian/rules:17: binary] Error 25 Andreas jool.sid.build.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: jool Source-Version: 4.1.9-1 Done: Alberto Leiva Popper We believe that the bug you reported is fixed in the latest version of jool, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Leiva Popper (supplier of updated jool 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: Fri, 27 Jan 2023 10:24:52 -0600 Source: jool Architecture: source Version: 4.1.9-1 Distribution: unstable Urgency: medium Maintainer: Jool Team Changed-By: Alberto Leiva Popper Closes: 1027877 1029268 Changes: jool (4.1.9-1) unstable; urgency=medium . * New upstream release * Switch to dh-sequence-dkms. Closes: #1027877 * Declare Testsuite: autopkgtest-pkg-dkms * Modernize the iptables shared object exports. Closes: #1029268 Checksums-Sha1: 7b6c4738aa4075085b4b4a59674929845ffe18e8 2260 jool_4.1.9-1.dsc d56955d97eb68f5f46863b73a95c67a7fab914b0 623233 jool_4.1.9.orig.tar.gz 924bb2744a4722f8f85ceafe057c13d54c3a2c40 833 jool_4.1.9.orig.tar.gz.asc 99677c4c6159a48ebb779122a45cda8e757c92c4 8948 jool_4.1.9-1.debian.tar.xz 381be2d9af97b7fcdde1f7e53bebb20ce46cb846 7778 jool_4.1.9-1_amd64.buildinfo Checksums-Sha256: 77961b6f33378dcf11ffbdbcf763d69dad45540f17829c56aae6c74172cd0615 2260 jool_4.1.9-1.dsc c569dc5b66b0767a43709df75d1007feb18fb3128c76dfae578cf610c7585dea 623233 jool_4.1.9.orig.tar.gz 25e3c3a8693d8bf1e075b137cab817c90eb09ee07c6c61a99195a5f3d51cb4e9 833 jool_4.1.9.orig.tar.gz.asc 8582400ed9a058ecf81d930973638ba7eb500f36d02688e0cfd3d1ca63a108ee 8948 jool_4.1.9-1.debian.tar.xz 1c91be54522be197e62535e42d4c75d9da8e56a9b2a3766590123dec6c460c1d 7778 jool_4.1.9-1_amd64.buildinfo Files: a07760545e2fa739c4375f6eff70af79 2260 kernel optional jool_4.1.9-1.dsc 54eb74846a5332200df31137d0a22c85 623233 kernel optional jool_4.1.9.orig.tar.gz 1ff98499b429fc51e855eab06bd3fe76 833 kernel optional jool_4.1.9.orig.tar.gz.asc 0e5e0ac71a4f2b31a69a51286290f939 8948 kernel
Bug#1029799: marked as done (msmtp fails to purge when adduser is not installed)
Your message dated Sat, 28 Jan 2023 12:33:02 + with message-id and subject line Bug#1029799: fixed in msmtp 1.8.22-3 has caused the Debian Bug report #1029799, regarding msmtp fails to purge when adduser is not installed 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.) -- 1029799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: msmtp Version: 1.8.22-1 Severity: serious https://piuparts.debian.org/sid/fail/msmtp-mta_1.8.22-2.log ... Purging configuration files for msmtp (1.8.22-2) ... /var/lib/dpkg/info/msmtp.postrm: 14: deluser: not found dpkg: error processing package msmtp (--purge): installed msmtp package post-removal script subprocess returned error exit status 127 dpkg: warning: ignoring request to remove sensible-utils which isn't installed Purging configuration files for ucf (3.0043) ... Errors were encountered while processing: msmtp https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#summary-of-ways-maintainer-scripts-are-called The postrm script is called after the package’s files have been removed or replaced. The package whose postrm is being called may have previously been deconfigured and only be “Unpacked”, at which point subsequent package changes do not consider its dependencies. Therefore, all postrm actions must only rely on essential packages and must gracefully skip any actions that require the package’s dependencies if those dependencies are unavailable. --- End Message --- --- Begin Message --- Source: msmtp Source-Version: 1.8.22-3 Done: Emmanuel Bouthenot We believe that the bug you reported is fixed in the latest version of msmtp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bouthenot (supplier of updated msmtp 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: Sat, 28 Jan 2023 10:39:45 + Source: msmtp Architecture: source Version: 1.8.22-3 Distribution: unstable Urgency: medium Maintainer: Emmanuel Bouthenot Changed-By: Emmanuel Bouthenot Closes: 1029799 Changes: msmtp (1.8.22-3) unstable; urgency=medium . * Fix uninstall failure when deluser is not present (Closes: #1029799) Checksums-Sha1: d56dca59832ffefdc31369265119b6ffa0747185 2197 msmtp_1.8.22-3.dsc 7d3b3776e849268f3fdf228fa4bbde21d8dce51c 22052 msmtp_1.8.22-3.debian.tar.xz 1a027dd475415b8f5455c87a690cdacfd3b04bfb 9370 msmtp_1.8.22-3_source.buildinfo Checksums-Sha256: a0cb35343474474e214db145fa7a50b776858523b6855194461a0bf41a2cb490 2197 msmtp_1.8.22-3.dsc f5925c9de3478f653776bc08fa46f4dceef6faf6b174edc4eb16d1c61bf14a98 22052 msmtp_1.8.22-3.debian.tar.xz dfca059424a9d0fcbcd1372c8252b80a4c6d3fcc704ace8997ad99e7dd1f2130 9370 msmtp_1.8.22-3_source.buildinfo Files: 4d37bc784cfbb4ecc636f80376d49ac5 2197 mail optional msmtp_1.8.22-3.dsc a288a4d3f9e4b869336e5d81b8d4322b 22052 mail optional msmtp_1.8.22-3.debian.tar.xz 3fb83f7e2ca8355c89ec6003954cca25 9370 mail optional msmtp_1.8.22-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQ1Tfow3vJnf8QuHSwd3I5KdQsMFAmPU/B8ACgkQSwd3I5Kd QsMzPQ//XEZ86lTp0dMb4Vc/HUeGhvL98P0SwQarMImLeX/N5YThtyfiF3PC1qdX wWa8j80Ub3q3BLU6oPydAfV+bubaZdUywnNlneYnJ7bECbB1QhOYo+rptVdK0W4a Mih/PRLZ0RKgKaQIEznrw37IRexM8pZHHYGzCgq4hSwOEuAFs9O9B7GuDR1CWTJt MJzvi3bRAkrsyersqREUHBxqXm9pBX453vMKcuJLqIbPVDrixXIrDbL/uIF03ATH Ya2lD0DJUQ8Rp2NV+euAyELglsDc+iyzcmyNBn/jyzS/+l563raPqLu1MbcAG+dJ X78vxpDqfwMJpoSmi3EO2gn9cQ50DVx0B/UIApcAn+nx8XPhBB+VBsOp4K8THyQT LKRQAuxIHJ7PtyxXBxRY3DHFxDpNuzRWzsjpG6rV/zryXi/LFHfJgvjCA8eGyTOt qa8QtojWHipd7nvTAk633D9a7FOySsUdqlD016KOa0VT7Be/175DwcyPx6xL+G+L VHgfLb+KMpW7crYguRh30dQjvTJr2dguTPXovmbwVOMruQmbry4HoP2/R2Pkk3pM IvgBhwCZ9eggUtV8Z+eZD/Jl11q0Kdonz25WfbeOjkrjYo6Ynd7rUYXWtZ6pO9dx eUjAHU4BR8DtmaW22YmT857CeD8rA2QAOr8iFCX+BPDRJIwXrdA= =GrtV -END PGP SIGNATURE End Message ---
Bug#1029829: amanda: CVE-2022-37704 CVE-2022-37705
Source: amanda Version: 1:3.5.1-9 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for amanda. CVE-2022-37704[0], CVE-2022-37705[1]. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-37704 https://www.cve.org/CVERecord?id=CVE-2022-37704 [1] https://security-tracker.debian.org/tracker/CVE-2022-37705 https://www.cve.org/CVERecord?id=CVE-2022-37705 [2] https://github.com/zmanda/amanda/issues/192 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1027382: Please, minimize your build chroots
On Sat, Jan 28, 2023 at 12:20:16AM +0100, Santiago Vila wrote: > El 27/1/23 a las 22:37, Adrian Bunk escribió: > > On Fri, Dec 16, 2022 at 02:15:13AM +0100, Santiago Vila wrote: ... > > I am right now looking at #1027382, and the first question is how I can > > make apt remove e2fsprogs so that I can reproduce the problem - it feels > > like a real waste of my QA work to "fix" something that is incredibly > > hard to break. > > You don't have to fix #1027382. The maintainer has. >... Reality in Debian is that at any time a 3 digit number of maintainers is (sort-term or long-term or permanently) away/busy/MIA. A large part of QA work in Debian is fixing bugs in packages maintained by other people, for me that's > 95% of my uploads. I am not saying that trying to force maintainers to spend time on such issues by making them release critical is better, but you are also creating extra work and frustration for the people who are doing QA work in Debian. > > It has been practice for many years that FTBFS that do not happen on the > > buildds are usually not release critical bugs, and I would appreciate if > > this is followed by everyone. > > Well, that's also wrong, because having the build-dependencies correct has > been > in the list of RC bugs for many years as well. See below. > > I would appreciate if we all followed Policy 4.2, which says packages MUST > build > when the build-dependencies are installed. Policy tends to be a decade behind reality because it *follows* existing practices. If existing practice is that build environments have all "Priority: required" packages installed, then policy should be updated to follow reality. > In general, disputing the severity because it does not happen in the buildds > misses completely the point of what should be the goal, namely, a distribution > which may be rebuilt by everybody following documented procedures, not > a distribution which may only be rebuilt in our buildds. People who follow the (incomplete) documentation in our wiki for creating their own buildd setup will get a reasonable setup where builds have all "Priority: required" packages installed. > The end user MUST be able to rebuild the packages. Otherwise our > free software licenses are meaningless in practice. In general this is true, but you tend to use this argument when trying force pretty unimportant things on the whole project. #932795 was your failed attempt to make the Technical Committee decide that all build failures on single-core machines are release critical bugs in the year 2019. > > It is not helpful if people try to force the few people who are doing > > QA work to spend their scarce QA time on fixing bugs that only happen > > when building on single-core machines or in non-UTF-8 locales or without > > packages that are in practice installed everywhere, by making such > > issues that are not a problem on our buildds release critical bugs. > > That's the wrong approach. If the end user wants to make a modification, > they can't use our buildd network. In #932795 there was wide consensus that documentation could be improved to clarify what a supported/reasonable build environment is. E.g. the maximum amount of diskspace a package might currently use when building on amd64 is the undocumented tribal knowledge how much storage is available on our amd64 buildds. > > It also opens a gigantic can of worms, since there is the even bigger > > opposite problem that many packages FTBFS or are built differently > > when built in an environment that differs from our buildd setup. > > Adding Build-Conflicts for all such cases is not feasible in practice. > > This is a straw-man. I'm not opening any can of worms. Your argument is based on treating Policy 4.2 as a holy scripture that must be followed and never questioned. Policy 4.2 also says Source packages should specify which binary packages they require to be installed or not to be installed in order to build correctly. We are not following the "not to be installed" part, which is the can of worms you would be opening. In the section you are referring to, Policy 4.2 also says In particular, this means that version clauses should be used rigorously in build-time relationships so that one cannot produce bad or inconsistently configured packages when the relationships are properly satisfied. Personally I would strongly agree with that, but current practice with Janitor commits removing older version clauses goes in the opposite direction. > > If people want to support building without tzdata [...]> but none of these > > are critical for our releases since > > none of these impact how packages are built for bookworm on our buildds. > > There is a list of RC issues. It's called Release Policy, and it says this: > > Packages must list any packages they require to build beyond those > that are "build-essential" in the appropriate Build-Depends: fields. > Ref: 4.2 > > Source: ht
Bug#1027382: Please, minimize your build chroots
On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote: >... > * Those bugs are RC by definition and have been for a long time. >... Please provide a pointer where a release team member has said so explicitly in recent years. In my experience they are usually saying that FTBFS that do not happen on the buildds of release architectures are usually not RC. > Thanks. cu Adrian
Bug#1029832: ruby-rack: CVE-2022-44570 CVE-2022-44571 CVE-2022-44572
Source: ruby-rack Version: 2.2.4-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for ruby-rack. CVE-2022-44570[0]: | rack: Fix ReDoS in Rack::Utils.get_byte_ranges CVE-2022-44571[1]: | rack: Fix ReDoS vulnerability in multipart parser CVE-2022-44572[2]: | rack: Forbid control characters in attributes If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-44570 https://www.cve.org/CVERecord?id=CVE-2022-44570 [1] https://security-tracker.debian.org/tracker/CVE-2022-44571 https://www.cve.org/CVERecord?id=CVE-2022-44571 [2] https://security-tracker.debian.org/tracker/CVE-2022-44572 https://www.cve.org/CVERecord?id=CVE-2022-44572 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1027382: Please, minimize your build chroots
El 28/1/23 a las 13:59, Adrian Bunk escribió: Policy 4.2 also says Source packages should specify which binary packages they require to be installed or not to be installed in order to build correctly. We are not following the "not to be installed" part, which is the can of worms you would be opening. No, I'm not proposing any kind of mass proliferation of build-conflicts, and have never proposed anything of the sort. The strawman arguments should stop. Now. Thanks.
Bug#1029806: marked as done (steam-installer: Launching Steam (Failed). You are not authorised to execute this file)
Your message dated Sat, 28 Jan 2023 13:09:29 + with message-id and subject line Bug#1029806: fixed in steam-installer 1:1.0.0.75+ds-5 has caused the Debian Bug report #1029806, regarding steam-installer: Launching Steam (Failed). You are not authorised to execute this file 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.) -- 1029806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: steam-installer Version: 1:1.0.0.75+ds-4 Severity: important Tags: d-i a11y X-Debbugs-Cc: marcos.ca...@gmail.com Dear Maintainer, * What led up to the situation? upgrading to steam-installer, under KDE Plasma, clicking on the Steam iceon results in error "Launching Steam (Failed). You are not authorised to execute this file" * What exactly did you do (or not do) that was effective (or ineffective)? -clicking on Steam in the Plasma menu gives the error. Steam does not launch -running "steam" from console works fine -once running from console you can pin the icon to the plasma taskbar. If you quit Steam anc click on the pinned icon you get the same error as above * What outcome did you expect instead? Steam to run as always clicking the icon -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:es:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages steam-installer depends on: ii debconf [debconf-2.0] 1.5.82 ii steam-libs 1:1.0.0.75+ds-4 ii steam-libs-i3861:1.0.0.75+ds-4 ii zenity 3.43.0-1 steam-installer recommends no packages. steam-installer suggests no packages. Versions of packages steam-libs depends on: ii ca-certificates 20211016 ii curl 7.87.0-2 ii file 1:5.44-2 ii libc62.36-8 ii libcrypt11:4.4.33-2 ii libgcc-s1 [libgcc1] 12.2.0-14 ii libgl1 1.6.0-1 ii libgl1-mesa-dri 22.3.3-1 ii libgpg-error01.46-1 ii libstdc++6 12.2.0-14 ii libudev1 252.4-1 ii libva-x11-2 2.17.0-1 ii libva2 2.17.0-1 ii libxcb-dri3-01.15-1 ii libxcb1 1.15-1 ii libxi6 2:1.8-1+b1 ii libxinerama1 2:1.1.4-3 ii xz-utils 5.4.1-0.0 Versions of packages steam-libs recommends: ii fontconfig 2.14.1-3 ii fonts-liberation 1:1.07.4-11 ii i965-va-driver [va-driver] 2.4.1+dfsg1-1 ii intel-media-va-driver [va-driver]23.1.0+dfsg1-1 ii konsole [x-terminal-emulator]4:22.12.1-1 ii libasound2-plugins 1.2.7.1-1 ii libegl1 1.6.0-1 ii libexpat12.5.0-1 ii libfontconfig1 2.14.1-3 ii libgbm1 22.3.3-1 ii libsdl2-2.0-02.26.2+dfsg-1 ii libva-drm2 2.17.0-1 ii libva-glx2 2.17.0-1 ii libx11-6 2:1.8.3-3 ii libx11-xcb1 2:1.8.3-3 ii libxau6 1:1.0.9-1 ii libxcb-dri2-01.15-1 ii libxcb-glx0 1.15-1 ii libxcb-present0 1.15-1 ii libxcb-sync1 1.15-1 ii libxdamage1 1:1.1.6-1 ii libxdmcp61:1.1.2-3 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxss1 1:1.2.3-1 ii libxxf86vm1 1:1.1.4-1+b2 ii mesa-va-drivers [va-driver] 22.3.3-1 ii mesa-vulka
Processed: Bug#1028826 marked as pending in python-xlib
Processing control commands: > tag -1 pending Bug #1028826 [src:python-xlib] herbstluftwm: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Ignoring request to alter tags of bug #1028826 to the same tags previously set -- 1028826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028826: marked as pending in python-xlib
Control: tag -1 pending Hello, Bug #1028826 in python-xlib 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/python-xlib/-/commit/c095664ea447bbc893aca9aa770728d6ec3e57ba d/patches: Add inherit-XError-in-error-classes-in-randr.patch patch to inherit all error classes in randr from XError (Closes: #1028826). (this message was generated automatically) -- Greetings https://bugs.debian.org/1028826
Bug#1027382: Please, minimize your build chroots
On 2023-01-28 13:59, Adrian Bunk wrote: I am not saying that trying to force maintainers to spend time on such issues by making them release critical is better, but you are also creating extra work and frustration for the people who are doing QA work in Debian. It also pushes some maintainers to give up on packages. I gave up on maintaining any Go package after the whole "everything should compile with only one CPU because policy says so" fiasco. The most rare resource we have is volunteer time. Creating artificial problems is not helping.
Processed: limit source to linux, tagging 1029046
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1029046 + pending Bug #1029046 [src:linux] S3 suspend broken on AMD Ryzen Pro 7 5850U Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004963: marked as done (CVE-2020-21598 CVE-2020-21600 CVE-2020-21602)
Your message dated Sat, 28 Jan 2023 15:29:54 +0100 with message-id and subject line Re: libde265: CVE-2020-21594 CVE-2020-21595 CVE-2020-21596 CVE-2020-21597 CVE-2020-21599 CVE-2020-21601 CVE-2020-21603 CVE-2020-21604 CVE-2020-21605 CVE-2020-21606 has caused the Debian Bug report #1004963, regarding CVE-2020-21598 CVE-2020-21600 CVE-2020-21602 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.) -- 1004963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libde265 Version: 1.0.8-1 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team CVE-2020-21602: https://github.com/strukturag/libde265/issues/242 CVE-2020-21600: https://github.com/strukturag/libde265/issues/243 CVE-2020-21598: https://github.com/strukturag/libde265/issues/237 --- End Message --- --- Begin Message --- This is fixed already in unstable, so I guess these bugs can be closed.--- End Message ---
Bug#957229: marked as done (freedroidrpg: ftbfs with GCC-10)
Your message dated Sat, 28 Jan 2023 15:44:29 +0100 with message-id and subject line Re: freedroidrpg: ftbfs with GCC-10 has caused the Debian Bug report #957229, regarding freedroidrpg: ftbfs with GCC-10 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.) -- 957229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freedroidrpg Version: 0.16.1-5 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/freedroidrpg_0.16.1-5_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: lvledit/lvledit_input.o:./src/./struct.h:1025: multiple definition of `tux_rendering'; action.o:./src/struct.h:1025: first defined here /usr/bin/ld: lvledit/lvledit_map.o:./src/./struct.h:1025: multiple definition of `tux_rendering'; action.o:./src/struct.h:1025: first defined here /usr/bin/ld: lvledit/lvledit_menu.o:./src/./struct.h:1025: multiple definition of `tux_rendering'; action.o:./src/struct.h:1025: first defined here /usr/bin/ld: lvledit/lvledit_object_lists.o:./src/./struct.h:1025: multiple definition of `tux_rendering'; action.o:./src/struct.h:1025: first defined here /usr/bin/ld: lvledit/lvledit_tools.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_move'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tools.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_place'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tools.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_select'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tools.o:./src/./struct.h:1025: multiple definition of `tux_rendering'; action.o:./src/struct.h:1025: first defined here /usr/bin/ld: lvledit/lvledit_tool_move.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_select'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tool_move.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_move'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tool_move.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_place'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tool_move.o:./src/./struct.h:1025: multiple definition of `tux_rendering'; action.o:./src/struct.h:1025: first defined here /usr/bin/ld: lvledit/lvledit_tool_place.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_select'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tool_place.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_move'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tool_place.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_place'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tool_place.o:./src/./struct.h:1025: multiple definition of `tux_rendering'; action.o:./src/struct.h:1025: first defined here /usr/bin/ld: lvledit/lvledit_tool_select.o:./src/./lvledit/lvledit_tools.h:39: multiple definition of `tool_select'; keyboard.o:./src/lvledit/lvledit_tools.h:39: first defined here /usr/bin/ld: lvledit/lvledit_tool_select.o:./src/
Bug#1027360: marked as done (calcurse: FTBFS in bullseye (missing build-depends on tzdata))
Your message dated Sat, 28 Jan 2023 16:07:44 +0100
with message-id
and subject line not a bug in bullseye
has caused the Debian Bug report #1027360,
regarding calcurse: FTBFS in bullseye (missing build-depends on tzdata)
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.)
--
1027360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:calcurse
Version: 4.6.0-2
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
dh_auto_configure -a
./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
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --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 thread-safe mkdir -p... /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 whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking whether make supports the include directive... yes (GNU style)
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 we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) none
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for sys/types.h... (cached) yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for unistd.h... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking paths.h usability... yes
checking paths.h presence... yes
checking for pa
Bug#1027364: marked as done (golang-github-go-co-op-gocron: FTBFS in bullseye (missing build-depends on tzdata))
Your message dated Sat, 28 Jan 2023 16:07:44 +0100 with message-id and subject line not a bug in bullseye has caused the Debian Bug report #1027364, regarding golang-github-go-co-op-gocron: FTBFS in bullseye (missing build-depends on tzdata) 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.) -- 1027364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-go-co-op-gocron Version: 0.5.0-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/go-co-op/gocron internal/unsafeheader internal/cpu runtime/internal/atomic runtime/internal/sys internal/bytealg runtime/internal/math internal/race sync/atomic math/bits runtime math unicode/utf8 unicode internal/testlog internal/reflectlite sync errors sort io strconv hash internal/oserror syscall crypto reflect internal/syscall/unix time encoding/binary internal/fmtsort internal/poll crypto/sha256 internal/syscall/execenv os bytes strings fmt regexp/syntax regexp github.com/go-co-op/gocron dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/go-co-op/gocron === RUN TestParseTime === RUN TestParseTime/normal === RUN TestParseTime/normal_-_no_leading_hour_zeros === RUN TestParseTime/normal_with_second === RUN TestParseTime/normal_with_second_-_no_leading_hour_zeros === RUN TestParseTime/not_a_number === RUN TestParseTime/out_of_range_hour === RUN TestParseTime/out_of_range_minute === RUN TestParseTime/wrong_format === RUN TestParseTime/wrong_minute === RUN TestParseTime/wrong_hour --- PASS: TestParseTime (0.00s) --- PASS: TestParseTime/normal (0.00s) --- PASS: TestParseTime/normal_-_no_leading_hour_zeros (0.00s) --- PASS: TestParseTime/normal_with_second (0.00s) --- PASS: TestParseTime/normal_with_second_-_no_leading_hour_zeros (0.00s) --- PASS: TestParseTime/not_a_number (0.00s) --- PASS: TestParseTime/out_of_range_hour (0.00s) --- PASS: TestParseTime/out_of_range_minute (0.00s) --- PASS: TestParseTime/wrong_format (0.00s) --- PASS: TestParseTime/wrong_minute (0.00s) --- PASS: TestParseTime/wrong_hour (0.00s) === RUN TestTags --- PASS: TestTags (0.00s) === RUN TestGetScheduledTime --- PASS: TestGetScheduledTime (0.00s) === RUN TestGetWeekday === RUN TestGetWeekday/success === RUN TestGetWeekday/fail_-_not_set_for_weekday --- PASS: TestGetWeekday (0.00s) --- PASS: TestGetWeekday/success (0.00s) --- PASS: TestGetWeekday/fail_-_not_set_for_weekday (0.00s) === RUN TestJob_shouldRunAgain === RUN TestJob_shouldRunAgain/should_run_again_(infinite) === RUN TestJob_shouldRunAgain/should_run_again_(finite) === RUN TestJob_shouldRunAgain/shouldn't_run_again_#1 === RUN TestJob_shouldRunAgain/shouldn't_run_again_#2 --- PASS: TestJob_shouldRunAgain (0.00s) --- PASS: TestJob_shouldRunAgain/should_run_again_(infinite) (0.00s) --- PASS: TestJob_shouldRunAgain/should_run_again_(finite) (0.00s) --- PASS: TestJob_shouldRunAgain/shouldn't_run_again_#1 (0.00s) --- PASS: TestJob_shouldRunAgain/shouldn't_run_again_#2 (0.00s) === RUN TestJob_LimitRunsTo --- PASS: TestJob_LimitRunsTo (0.00s) === RUN TestJob_CommonExports --- PASS: TestJob_CommonExports (0.00s) === RUN TestImmediateExecution --- PASS: TestImmediateExecution (0.00s) === RUN TestExecutionSeconds --- PASS: TestExecutionSeconds (6.00s) === RUN TestScheduled --- PASS: TestScheduled (0.00s) === RUN TestScheduledWithTag --- PASS: TestScheduledWithTag (0.00s) === RUN TestAtFuture === RUN TestAtFuture/calls_to_.At()_should_parse_time_correctly === RUN TestAtFuture/error_due_to_bad_time_format --- PASS: TestAtFuture (0.00s) --- PASS: TestAtFuture/calls_to_.At()_should_parse_time_correctly (0.00s) --- PASS: TestAtFuture/error_due_to_bad_time_format (0.00s) === RUN TestWeekdayBeforeToday --- PASS: TestWeekdayBeforeToday (0.00s) ===
Bug#1027370: marked as done (golang-github-powerman-check: FTBFS in bullseye (missing build-depends on tzdata))
Your message dated Sat, 28 Jan 2023 16:07:44 +0100 with message-id and subject line not a bug in bullseye has caused the Debian Bug report #1027370, regarding golang-github-powerman-check: FTBFS in bullseye (missing build-depends on tzdata) 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.) -- 1027370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-powerman-check Version: 1.2.1-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/powerman/check internal/unsafeheader internal/cpu runtime/internal/atomic internal/bytealg runtime/internal/sys runtime/internal/math internal/race runtime sync/atomic unicode unicode/utf8 encoding math/bits math internal/testlog unicode/utf16 golang.org/x/sys/internal/unsafeheader internal/reflectlite sync errors sort io strconv bytes internal/oserror syscall reflect internal/syscall/unix time encoding/binary internal/fmtsort internal/poll encoding/base64 internal/syscall/execenv strings os regexp/syntax fmt regexp encoding/json flag encoding/hex github.com/davecgh/go-spew/spew path github.com/pkg/errors bufio github.com/smartystreets/goconvey/convey/gotest github.com/smartystreets/goconvey/convey/reporting github.com/pmezard/go-difflib/difflib path/filepath golang.org/x/sys/unix io/ioutil runtime/debug context runtime/trace testing github.com/powerman/check dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/powerman/check panic: time: missing Location in call to Time.In goroutine 1 [running]: time.Time.In(0xc0ac7376985035d0, 0xa8c01, 0x715b20, 0x0, 0x6f93a0, 0xcd1f18, 0x1) /usr/lib/go-1.15/src/time/time.go:1099 +0xb2 github.com/powerman/check_test.init() /<>/_build/src/github.com/powerman/check/check_test.go:150 +0x236 FAILgithub.com/powerman/check 0.007s FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 github.com/powerman/check returned exit code 1 make: *** [debian/rules:4: binary-indep] Error 25 dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). About the archive rebuild: The build was made using virtual machines from Hetzner, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages (plus debhelper). If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Hi! This MBF has been done _contrary_ to multiple discussions on debian-devel and elsewhere. While the wording of the Policy might be a bit unclear (even though everyone but Santiago seems to agree with the other interpretation), beyond any doubt this is not a material for a _stable_ update. A build failure in a supported environment is worth fixing, failing to build when explicitly declared "totally broken" by the Policy (§2.5) s not. I'm thus closing. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine. ⢿⡄⠘⠷⠚⠋⠀ ⠈⠳⣄--- End Message ---
Bug#1027381: marked as done (siridb-server: FTBFS in bullseye (missing build-depends on tzdata))
Your message dated Sat, 28 Jan 2023 16:07:44 +0100 with message-id and subject line not a bug in bullseye has caused the Debian Bug report #1027381, regarding siridb-server: FTBFS in bullseye (missing build-depends on tzdata) 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.) -- 1027381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:siridb-server Version: 2.0.43-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-arch dh binary-arch dh_update_autotools_config -a dh_autoreconf -a debian/rules override_dh_auto_build-arch make[1]: Entering directory '/<>' dh_auto_build --sourcedirectory=Release cd Release && make -j2 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>/Release' Building file: ../src/xpath/xpath.c Building file: ../src/base64/base64.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xpath/xpath.d" -MT"src/xpath/xpath.o" -o "src/xpath/xpath.o" "../src/xpath/xpath.c" Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/base64/base64.d" -MT"src/base64/base64.o" -o "src/base64/base64.o" "../src/base64/base64.c" Finished building: ../src/base64/base64.c Building file: ../src/xmath/xmath.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xmath/xmath.d" -MT"src/xmath/xmath.o" -o "src/xmath/xmath.o" "../src/xmath/xmath.c" Finished building: ../src/xpath/xpath.c Building file: ../src/timeit/timeit.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/timeit/timeit.d" -MT"src/timeit/timeit.o" -o "src/timeit/timeit.o" "../src/timeit/timeit.c" Finished building: ../src/xmath/xmath.c Finished building: ../src/timeit/timeit.c Building file: ../src/xstr/xstr.c Building file: ../src/vec/vec.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xstr/xstr.d" -MT"src/xstr/xstr.o" -o "src/xstr/xstr.o" "../src/xstr/xstr.c" Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/vec/vec.d" -MT"src/vec/vec.o" -o "src/vec/vec.o" "../src/vec/vec.c" Finished building: ../src/vec/vec.c Building file: ../src/siri/service/account.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/account.d" -MT"src/siri/service/account.o" -o "src/siri/service/account.o" "../src/siri/service/account.c" Finished building: ../src/xstr/xstr.c Building file: ../src/siri/service/client.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/client.d" -MT"src/siri/service/client.o" -o "src/siri/service/client.o" "../src/siri/service/client.c" Finished building: ../src/siri/service/account.c Building file: ../src/siri/service/request.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/request.d" -MT"src/siri/service/request.o" -o "src/siri/service/request.o" "../src/siri/service/request.c" Finished build
Bug#1029430: it's not tzdata
Control: tag -1 -patch Hi! The alleged patch doesn't fix the FTBFS. Besides the non-bug (per numerous discussions on debian-devel and elsewhere) of non-depending on a required package "tzdata", the package fails from an actual build failure even in a non-sabotaged build chroot. I'm thus untagging "patch". Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine. ⢿⡄⠘⠷⠚⠋⠀ ⠈⠳⣄
Processed: it's not tzdata
Processing control commands: > tag -1 -patch Bug #1029430 [src:reposurgeon] reposurgeon: FTBFS in bookworm (undeclared build-dependency on tzdata) Removed tag(s) patch. -- 1029430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027905: not reproducible in a valid sbuild chroot
Control: tags -1 +unreproducible Control: severity -1 wishlist Hi! You've done a MBF despite _negative_ consensus in several discussions (debian-devel, debootstrap, policy, ...); folks seem to be in agreement that either the Policy doesn't require building in an environment that is explicitly "totally broken" (§2.5), or at least that the issue is not RC. Thus: is there a way to reproduce this failure without intentionally removing tzdata? If not, I believe this bug should be closed -- and, if the change has already been applied in git, that it should be reverted. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine. ⢿⡄⠘⠷⠚⠋⠀ ⠈⠳⣄
Processed: not reproducible in a valid sbuild chroot
Processing control commands: > tags -1 +unreproducible Bug #1027905 [src:golang-github-arran4-golang-ical] golang-github-arran4-golang-ical: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) unreproducible. > severity -1 wishlist Bug #1027905 [src:golang-github-arran4-golang-ical] golang-github-arran4-golang-ical: FTBFS in bookworm (undeclared build-dependency on tzdata) Severity set to 'wishlist' from 'serious' -- 1027905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: not reproducible in a valid sbuild chroot
Processing control commands: > tags -1 +unreproducible Bug #1027907 [src:golang-github-go-git-go-git] golang-github-go-git-go-git: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) unreproducible. > severity -1 wishlist Bug #1027907 [src:golang-github-go-git-go-git] golang-github-go-git-go-git: FTBFS in bookworm (undeclared build-dependency on tzdata) Severity set to 'wishlist' from 'serious' -- 1027907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: not reproducible in a valid sbuild chroot
Processing control commands: > tags -1 +unreproducible Bug #1029418 [src:gnote] gnote: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) unreproducible. > severity -1 wishlist Bug #1029418 [src:gnote] gnote: FTBFS in bookworm (undeclared build-dependency on tzdata) Severity set to 'wishlist' from 'serious' -- 1029418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: not reproducible in a valid sbuild chroot
Processing control commands: > tags -1 +unreproducible Bug #1029423 [src:jc] jc: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) unreproducible. > severity -1 wishlist Bug #1029423 [src:jc] jc: FTBFS in bookworm (undeclared build-dependency on tzdata) Severity set to 'wishlist' from 'serious' -- 1029423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: not reproducible in a valid sbuild chroot
Processing control commands: > tags -1 +unreproducible Bug #1029419 [src:golang-github-mattn-go-sqlite3] golang-github-mattn-go-sqlite3: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) unreproducible. > severity -1 wishlist Bug #1029419 [src:golang-github-mattn-go-sqlite3] golang-github-mattn-go-sqlite3: FTBFS in bookworm (undeclared build-dependency on tzdata) Severity set to 'wishlist' from 'serious' -- 1029419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: not reproducible in a valid sbuild chroot
Processing control commands: > tags -1 +unreproducible Bug #1029424 [src:kopeninghours] kopeninghours: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) unreproducible. > severity -1 wishlist Bug #1029424 [src:kopeninghours] kopeninghours: FTBFS in bookworm (undeclared build-dependency on tzdata) Severity set to 'wishlist' from 'serious' -- 1029424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: not reproducible in a valid sbuild chroot
Processing control commands: > tags -1 +unreproducible Bug #1029462 [src:golang-github-nats-io-jwt] golang-github-nats-io-jwt: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) unreproducible. > severity -1 wishlist Bug #1029462 [src:golang-github-nats-io-jwt] golang-github-nats-io-jwt: FTBFS in bookworm (undeclared build-dependency on tzdata) Severity set to 'wishlist' from 'serious' -- 1029462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027364: golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata)
retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata) reopen 1027364 found 0.5.0-2 thanks Adam, please don't close bugs just because they say "bullseye" in the title. In most cases, I really meant "bullseye and later". I've now fixed the title to avoid confusion. Thanks.
Processed (with 1 error): golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata)
Processing commands for cont...@bugs.debian.org:
> retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends
> on tzdata)
Bug #1027364 {Done: Adam Borowski }
[src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron: FTBFS in
bullseye (missing build-depends on tzdata)
Changed Bug title to 'golang-github-go-co-op-gocron: FTBFS (missing
build-depends on tzdata)' from 'golang-github-go-co-op-gocron: FTBFS in
bullseye (missing build-depends on tzdata)'.
> reopen 1027364
Bug #1027364 {Done: Adam Borowski }
[src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron: FTBFS
(missing build-depends on tzdata)
Bug reopened
Ignoring request to alter fixed versions of bug #1027364 to the same values
previously set
> found 0.5.0-2
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found
Processing commands for cont...@bugs.debian.org: > found 1027364 0.5.0-2 Bug #1027364 [src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata) Ignoring request to alter found versions of bug #1027364 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1027364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027364: golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata)
Control: close 1027364 On Sat, Jan 28, 2023 at 04:31:25PM +0100, Santiago Vila wrote: > retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends > on tzdata) > reopen 1027364 > found 0.5.0-2 > thanks > > Adam, please don't close bugs just because they say "bullseye" in the title. > In most cases, I really meant "bullseye and later". I've just re-tested: Distribution: bullseye Host Architecture: amd64 Source-Version: 0.5.0-2 Status: successful So the package does build ok. Do you have an example of a build environment that is not explicitly declared "totally broken" by the Policy (§2.5)? Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine. ⢿⡄⠘⠷⠚⠋⠀ ⠈⠳⣄
Processed: Re: golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata)
Processing control commands: > close 1027364 Bug #1027364 [src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata) Marked Bug as done -- 1027364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to python-pytest-xprocess, tagging 1026549
Processing commands for cont...@bugs.debian.org: > limit source python-pytest-xprocess Limiting to bugs with field 'source' containing at least one of 'python-pytest-xprocess' Limit currently set to 'source':'python-pytest-xprocess' > tags 1026549 + pending Bug #1026549 [src:python-pytest-xprocess] python-pytest-xprocess: FTBFS: tests failed Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1024831 is important
Processing commands for cont...@bugs.debian.org: > severity 1024831 important Bug #1024831 [src:linux] xorg: xserver fails to resume after suspend-to-disk Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1024831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029403: shorewall: fails to start with "Couldn't load match `iface':No such file or directory"
On 2023-01-27 13:35, Romain Francoise wrote: Do you mind if I merge them? Sure, please merge.
Processed: closing 1024239
Processing commands for cont...@bugs.debian.org: > close 1024239 1.0.6-2 Bug #1024239 [src:libequihash] libequihash: baseline violation on i386 and FTBFS on !x86 Marked as fixed in versions libequihash/1.0.6-2. Bug #1024239 [src:libequihash] libequihash: baseline violation on i386 and FTBFS on !x86 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1024239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1019681 marked as pending in samizdat
Processing control commands: > tag -1 pending Bug #1019681 [src:samizdat] samizdat: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. Added tag(s) pending. -- 1019681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019681: marked as pending in samizdat
Control: tag -1 pending Hello, Bug #1019681 in samizdat reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/samizdat/-/commit/fbf5ddcf6f78951a53353880e02463b13e08b519 Fix FTBFS * d/control (Build-Depends, Depend): Depend on ruby-whitewash with Psych fix. * debian/patches/0003-Fix-compatibility-with-Psych-4.patch. Add patch. - Use YAML.unsafe_load() because YAML.load() changed to YAML.safe_load() in Psych 4, leading to a FTBFS with errors like: Psych::DisallowedClass: Tried to load unspecified class XXX (closes: #1019681). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/1019681
Processed: closing 1024238
Processing commands for cont...@bugs.debian.org: > close 1024238 1.0.6-2 Bug #1024238 [src:libequihash] libequihash: binary-any FTBFS Bug #1028268 [src:libequihash] libequihash: binary-any FTBFS Marked as fixed in versions libequihash/1.0.6-2. Marked as fixed in versions libequihash/1.0.6-2. Bug #1024238 [src:libequihash] libequihash: binary-any FTBFS Bug #1028268 [src:libequihash] libequihash: binary-any FTBFS Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1024238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024238 1028268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029775: pyhst2: FTBFS with setuptools 66: Invalid version: '2020ca'
Control: tags -1 confirmed +patch
Hello there,
while at St-Cergue's BSP, I took a look at this issue, so here are my
findings.
* I can confirm it fails to build from source in a main+contrib+non-free
cowbuilder.
* This FTBFS is the consequence of a new requirement from setuptools; see this
issue to get it better: https://github.com/pypa/setuptools/issues/2497 .
setuptools now imposes PEP-440-style versioning, that is, the version has to
match this format:
[N!]N(.N)*[{a|b|rc}N][.postN][.devN]
But pyHST2 uses the version number in some paths (such as /usr/lib/python3/
dist-packages/PyHST2_2020c(...) ), so it can't simply be patched to use
"2020.3" (c ~= 3 ?). I can't login to upstream's issues tracker at
https://gitlab.esrf.fr/mirone/pyhst2 but it's clearly something that needs to
be fixed by a new upstream release.
The attached patch is basically a `sed 's/2020c/2021/g' -i` (also check
aumento_versione="a" which can work, but should also be amended) on concerned
files. It allows to finish building, but the paths have become
/usr/lib/python3/dist-packages/PyHST2_2021(...), which is clearly not
upstream's intent.
I'll check if it's possible to only patch the version and not all files.
See you in a bit.
Cheers,
OdyX
Le vendredi, 27 janvier 2023, 15.37:13 h CET Andreas Beckmann a écrit :
> Source: pyhst2
> Version: 2020c-6
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
>
> Hi,
>
> pyhst2 FTBFS with setuptools 66 that was uploaded today:
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The
> version specified ('2020ca') is an invalid version, this may not work as
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP
> 440 for more details. warnings.warn(
> running clean
> removing '/build/pyhst2-2020c/.pybuild/cpython3_3.10_pyhst2/build' (and
> everything under it) 'build/bdist.linux-x86_64' does not exist -- can't
> clean it
> 'build/scripts-3.10' does not exist -- can't clean it
--
OdyXIndex: pyhst2/PyHST/__init__.py
===
--- pyhst2.orig/PyHST/__init__.py
+++ pyhst2/PyHST/__init__.py
@@ -30,4 +30,4 @@
# is a problem for you.
#*/
-version = "2020c"
+version = "2021"
Index: pyhst2/TEST_PYHST/nonregression.py
===
--- pyhst2.orig/TEST_PYHST/nonregression.py
+++ pyhst2/TEST_PYHST/nonregression.py
@@ -67,7 +67,7 @@ casi=[ "CRAYON", "HEIKKI", "HELICOID
"PATCHES_VECTORIAL", "SINO_THRESHOLD" ]
casi=["ID11_SNOW", "BIG", "LENA", "LENA_MULTIRINGS", "MOUSSE", "MULTIPAGANIN","NANOPOINTS", "PATCHES_VECTORIAL", "SINO_THRESHOLD"]
-LAUNCHING_INSTRUCTION = "PyHST2_2020c input.par"
+LAUNCHING_INSTRUCTION = "PyHST2_2021 input.par"
outputprefix="/home/esrf/mirone/nobackup/TEST_PYHST/RESULTS/p9/monogpu"
# outputprefix="/tmp/TEST_PYHST/RESULTS/p9-04/"
###
Index: pyhst2/scripts_link/pyhst2
===
--- pyhst2.orig/scripts_link/pyhst2
+++ pyhst2/scripts_link/pyhst2
@@ -1 +1 @@
-PyHST2_2020c $*
+PyHST2_2021 $*
Index: pyhst2/scripts_link/pyhst2_info
===
--- pyhst2.orig/scripts_link/pyhst2_info
+++ pyhst2/scripts_link/pyhst2_info
@@ -1,6 +1,6 @@
#!python
msg = """
-The pyhst2 script launches PyHST2_2020c
+The pyhst2 script launches PyHST2_2021
*** PyHST2_2020a
Index: pyhst2/setup.py
===
--- pyhst2.orig/setup.py
+++ pyhst2/setup.py
@@ -86,7 +86,7 @@ DO_LINK = 0
global version
global aumento_versione
-aumento_versione="a"
+aumento_versione=".1"
global version
@@ -95,7 +95,7 @@ if DO_LINK==0:
os.path.abspath(__file__)), "PyHST", "__init__.py"))
if l.strip().startswith("version")][0]
else:
-version = "2020c"
+version = "2021"
def do_link():
@@ -104,7 +104,7 @@ def do_link():
# aumento_versione=""
-version = "2020c"
+version = "2021"
packages = []
Index: pyhst2/stdeb_link.cfg
===
--- pyhst2.orig/stdeb_link.cfg
+++ pyhst2/stdeb_link.cfg
@@ -1,3 +1,3 @@
[DEFAULT]
-Depends: python-pyhst2-2020c | python-pyhst2-2020c-base
-Depends3: python3-pyhst2-2020c | python3-pyhst2-2020c-base
+Depends: python-pyhst2-2021 | python-pyhst2-2021-base
+Depends3: python3-pyhst2-2021 | python3-pyhst2-2021-base
signature.asc
Description: This is a digitally signed message part.
Processed: Re: Bug#1029775: pyhst2: FTBFS with setuptools 66: Invalid version: '2020ca'
Processing control commands: > tags -1 confirmed +patch Bug #1029775 [src:pyhst2] pyhst2: FTBFS with setuptools 66: Invalid version: '2020ca' Added tag(s) confirmed. Bug #1029775 [src:pyhst2] pyhst2: FTBFS with setuptools 66: Invalid version: '2020ca' Added tag(s) patch. -- 1029775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tags 1027851 + pending
Processing commands for cont...@bugs.debian.org: > tags 1027851 + pending Bug #1027851 [src:pytorch] pytorch FTBFS with Python 3.11 as default version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1028833 is forwarded to https://github.com/pimutils/khal/issues/1205
Processing commands for cont...@bugs.debian.org:
> forwarded 1028833 https://github.com/pimutils/khal/issues/1205
Bug #1028833 [src:khal] khal: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/pimutils/khal/issues/1205'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1029403 to xtables-addons, forcibly merging 973990 1029403
Processing commands for cont...@bugs.debian.org: > reassign 1029403 xtables-addons Bug #1029403 [shorewall] shorewall: fails to start with "Couldn't load match `iface':No such file or directory" Bug reassigned from package 'shorewall' to 'xtables-addons'. No longer marked as found in versions shorewall/5.2.3.4-1. Ignoring request to alter fixed versions of bug #1029403 to the same values previously set > forcemerge 973990 1029403 Bug #973990 [xtables-addons] shorewall: Fails to start with "Couldn't load match `iface':No such file or directory" Bug #1029403 [xtables-addons] shorewall: fails to start with "Couldn't load match `iface':No such file or directory" Severity set to 'critical' from 'grave' There is no source info for the package 'xtables-addons' at version '3.23-1' with architecture '' Unable to make a source version for version '3.23-1' Marked as found in versions 3.23-1. Merged 973990 1029403 > thanks Stopping processing here. Please contact me if you need assistance. -- 1029403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029403 973990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008409: marked as done (ctioga2: FTBFS: :85:in `require': /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/Dobjects/Dvector
Your message dated Sat, 28 Jan 2023 16:53:21 + with message-id and subject line Bug#1008409: fixed in ruby-tioga 1.19.1-4 has caused the Debian Bug report #1008409, regarding ctioga2: FTBFS: :85:in `require': /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/Dobjects/Dvector.so: undefined symbol: rb_safe_level - /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/Dobjects/Dvector.so (LoadError) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ctioga2 Version: 0.14.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > dh_ruby --build >dh_ruby --build > cd man; RUBYLIB=:../lib ruby ../bin/ctioga2 --write-man "0.14.1" > ctioga2.1.template > ctioga2.1 > :85:in > `require': > /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/Dobjects/Dvector.so: > undefined symbol: rb_safe_level - > /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/Dobjects/Dvector.so > (LoadError) > from > :85:in > `require' > from /<>/lib/ctioga2/plotmaker.rb:103:in `' > from > :85:in > `require' > from > :85:in > `require' > from ../bin/ctioga2:49:in `' > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/03/26/ctioga2_0.14.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-tioga Source-Version: 1.19.1-4 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-tioga, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-tioga 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: Sat, 28 Jan 2023 16:44:40 +0100 Source: ruby-tioga Architecture: source Version: 1.19.1-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Daniel Leidert Closes: 1008409 Changes: ruby-tioga (1.19.1-4) unstable; urgency=medium . * Team upload. * d/patches/drop-obsolete-rb_safe_level-function.patch: Add patch. - Drop the obsolete rb_safe_level() function (closes: #1008409). * d/patches/series: Add new patch. Checksums-Sha1: 5f2f88b1026c2c8f947c8433b257a323446fccad 1943 ruby-tioga_1.19.1-4.dsc e4c7ec8674ef6e2aa3e34be697976b54dfa805e3 8500 ruby-tioga_1.19.1-4.debian.tar.xz 4e332dce6e1a75aa70acaa09398407997d1f1992 10149 ruby-tioga_1.19.1-4_amd64.buildinfo Checksums-Sha256: 76490c4d74dc8a6e6077a7221732e32c3cd8a2912ef64d1e15584c4bffafa8e3 1943 ruby-tioga_1.19.1-4.dsc c959404ca59f23a95571f58c083a30824a7670389fb4afed2ce249ce5219d426 8500 ruby-tioga_1.19.1-4.debian.tar.xz 7519cfa7205579955e2e9775cac756064f1d8c0164518e6b842d5594e81e926c 10149 ruby-tioga_1.19.1-4_amd64.buildinfo Files: de08b55e18b8a0a04b0d6c3c0c213833 1943 ruby optional ruby-tioga_1.19.1-4.dsc a5dacdadffd6e489c92feb40cda71121 8500 ruby optional ruby-tioga_1.19.1-4.debian.tar.xz 08992544887b1c6e84a6aacc86b5cff1 10149 ruby optional ruby-tioga_1.19.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPVQ5YACgkQS80FZ8KW 0F0yzhAA0kZSOt2ONjuWyyo56cpqwBJvth0Z8Gp78qrJLHBe4kDl7565Fnxl/Cfr EeE6RYjEDu1FaZ4OHhG44l5dia120cthnuiU9AWz0nMUCBEa2kInNccsSqsfV71H I/eQDy/erhiWKAQaLylEZHaR64wOYSBPr6vAF9wleflRDtgN0x2Sr0dWlJHhf/UE
Bug#1029840: bazel-bootstrap: autopkgtest failure: Unrecognized VM option 'UseParallelOldGC'
Source: bazel-bootstrap Version: 4.2.3+ds-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/b/bazel-bootstrap/30777521/log.gz ... autopkgtest [09:12:31]: test java-1-hello: [--- Loading: Loading: 0 packages loaded Analyzing: target //examples/java-native/src/test/java/com/example/myproject:hello (1 packages loaded, 0 targets configured) INFO: Analyzed target //examples/java-native/src/test/java/com/example/myproject:hello (5 packages loaded, 90 targets configured). INFO: Found 1 test target... [0 / 4] [Prepa] BazelWorkspaceStatusAction stable-status.txt [9 / 12] [Prepa] Compiling Java headers examples/java-native/src/main/java/com/example/myproject/libhello-lib-hjar.jar (1 source file) ERROR: /tmp/autopkgtest-lxc.u4r5_89h/downtmp/build.JW0/src/examples/java-native/src/main/java/com/example/myproject/BUILD:11:13: Compiling Java headers examples/java-native/src/main/java/com/example/myproject/libhello-lib-hjar.jar (1 source file) failed: (Exit 1): java failed: error executing command (cd /home/debci/.cache/bazel/_bazel_debci/ac30c69205f9922c4c1ba25e527d4570/sandbox/linux-sandbox/17/execroot/io_bazel && \ exec env - \ LC_CTYPE=en_US.UTF-8 \ PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games \ external/local_jdk/bin/java -Xverify:none -XX:+UseParallelOldGC -XX:-CompactStrings '--patch-module=java.compiler=external/remote_java_tools_linux/java_tools/java_compiler.jar' '--patch-module=jdk.compiler=external/remote_java_tools_linux/java_tools/jdk_compiler.jar' '--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED' '--add-opens=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' '--add-opens=java.base/java.nio=ALL-UNNAMED' '--add-opens=java.base/java.lang=ALL-UNNAMED' -jar external/remote_java_tools_linux/java_tools/turbine_direct_binary_deploy.jar --output bazel-out/k8-fastbuild/bin/examples/java-native/src/main/java/com/example/myproject/libhello-lib-hjar.jar --output_deps bazel-out/k8-fastbuild/bin/examples/java-native/src/main/java/com/example/myproject/libhello-lib-hjar.jdeps --bootclasspath bazel-out/k8-fastbuild/bin/external/bazel_tools/tools/jdk/platformclasspath.jar --sources examples/java-native/src/main/java/com/example/myproject/Greeter.java --javacopts -source 8 -target 8 '-XDskipDuplicateBridges=true' '-XDcompilePolicy=simple' -g -parameters -XX:+UseParallelGC -XX:+IgnoreUnrecognizedVMOptions -- --target_label //examples/java-native/src/main/java/com/example/myproject:hello-lib --reduce_classpath_mode NONE) Execution platform: //:default_host_platform Use --sandbox_debug to see verbose messages from the sandbox OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release. Unrecognized VM option 'UseParallelOldGC' Did you mean '(+/-)UseParallelGC'? Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. Target //examples/java-native/src/test/java/com/example/myproject:hello failed to build ERROR: /tmp/autopkgtest-lxc.u4r5_89h/downtmp/build.JW0/src/examples/java-native/src/test/java/com/example/myproject/BUILD:3:10 Building examples/java-native/src/test/java/com/example/myproject/hello.jar (1 source file) failed: (Exit 1): java failed: error executing command (cd /home/debci/.cache/bazel/_bazel_debci/ac30c69205f9922c4c1ba25e527d4570/sandbox/linux-sandbox/17/execroot/io_bazel && \ exec env - \ LC_CTYPE=en_US.UTF-8 \ PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games \ external/local_jdk/bin/java -Xverify:none -XX:+UseParallelOldGC -XX:-CompactStrings '--patch-module=java.compiler=external/remote_java_tools_linux/java_tools/java_compiler.jar' '--patch-module=jdk.compiler=external/remote_java_tools_linux/java_tools/jdk_compiler.jar' '--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED' '--add-opens=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' '--add-opens=java.base/java.nio=ALL-UNNAMED' '--add-opens=java.base/java.lang=ALL-UNNAMED' -jar external/remote_java_tools_linux/java_tools/turbine_direct_binary_deploy.jar -
Bug#1029775: pyhst2: FTBFS with setuptools 66: Invalid version: '2020ca'
Control: tags -1 +pending
So. I have a much shorter (and better) patch, that I'll upload to DELAYED/5 in
few minutes.
See the attached patch, which consists of setting the setup.py version to a
PEP-440-compliant Debian-specific version (which I have confirmed to sort
bigger than "2020ca"). This fixes the FTBFS.
I've also pushed this as an MR on your VCS repository there:
https://salsa.debian.org/science-team/pyhst2/-/merge_requests/1
Best,
OdyX
Le samedi, 28 janvier 2023, 17.21:35 h CET Didier 'OdyX' Raboud a écrit :
> Hello there,
>
> while at St-Cergue's BSP, I took a look at this issue, so here are my
> findings.
>
> * I can confirm it fails to build from source in a main+contrib+non-free
> cowbuilder.
>
> * This FTBFS is the consequence of a new requirement from setuptools; see
> this issue to get it better: https://github.com/pypa/setuptools/issues/2497
> . setuptools now imposes PEP-440-style versioning, that is, the version has
> to match this format:
>
> [N!]N(.N)*[{a|b|rc}N][.postN][.devN]
>
> But pyHST2 uses the version number in some paths (such as /usr/lib/
python3/
> dist-packages/PyHST2_2020c(...) ), so it can't simply be patched to use
> "2020.3" (c ~= 3 ?). I can't login to upstream's issues tracker at
> https://gitlab.esrf.fr/mirone/pyhst2 but it's clearly something that needs
> to be fixed by a new upstream release.
>
> The attached patch is basically a `sed 's/2020c/2021/g' -i` (also check
> aumento_versione="a" which can work, but should also be amended) on
> concerned files. It allows to finish building, but the paths have become
> /usr/lib/python3/dist-packages/PyHST2_2021(...), which is clearly not
> upstream's intent.
>
> I'll check if it's possible to only patch the version and not all files.
>
> See you in a bit.
>
> Cheers,
>
> OdyX
>
> Le vendredi, 27 janvier 2023, 15.37:13 h CET Andreas Beckmann a écrit :
> > Source: pyhst2
> > Version: 2020c-6
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source
> >
> > Hi,
> >
> > pyhst2 FTBFS with setuptools 66 that was uploaded today:
> > /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The
> > version specified ('2020ca') is an invalid version, this may not work as
> > expected with newer versions of setuptools, pip, and PyPI. Please see PEP
> > 440 for more details. warnings.warn(
> > running clean
> > removing '/build/pyhst2-2020c/.pybuild/cpython3_3.10_pyhst2/build' (and
> > everything under it) 'build/bdist.linux-x86_64' does not exist -- can't
> > clean it
> > 'build/scripts-3.10' does not exist -- can't clean it
Set a Debian-specific PEP-440-compliant version: 2020.3.20230128
This is needed since setuptools 66.0
Bug-Debian: https://bugs.debian.org/1029775
Author: Didier Raboud
Origin: vendor
--- a/setup.py
+++ b/setup.py
@@ -88,6 +88,9 @@ global version
global aumento_versione
aumento_versione="a"
+# Debian-specific version to match PEP-440 with setuptools v66.0.0
+pep440_version = "2020.3.20230128" # 3 for c, today's date
+
global version
if DO_LINK==0:
@@ -121,7 +124,8 @@ def do_link():
distrib = setup(name="pyhst2_links",
license="GPL",
-version=version+aumento_versione,
+# Debian-specific version to fit PEP-440
+version=pep440_version,
description=description,
author="Alessandro Mirone",
author_email="mir...@esrf.fr",
@@ -156,7 +160,8 @@ def do_link_unstable():
distrib = setup(name="pyhst2unstable_links",
license="GPL",
-version=version+aumento_versione,
+# Debian-specific version to fit PEP-440
+version=pep440_version,
description=description,
author="Alessandro Mirone",
author_email="mir...@esrf.fr",
@@ -697,7 +702,8 @@ def do_pyhst():
distrib = setup(name="PyHST2_"+version+post_fix,
license="GPL",
-version=version+aumento_versione, ## aumenta qua versione
+# Debian-specific version to fit PEP-440
+version=pep440_version,
description=description,
author="Alessandro Mirone",
author_email="mir...@esrf.fr",
signature.asc
Description: This is a digitally signed message part.
Processed: Re: Bug#1029775: pyhst2: FTBFS with setuptools 66: Invalid version: '2020ca'
Processing control commands: > tags -1 +pending Bug #1029775 [src:pyhst2] pyhst2: FTBFS with setuptools 66: Invalid version: '2020ca' Added tag(s) pending. -- 1029775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: RC Bug #1026740: forwarded upstream
Processing commands for cont...@bugs.debian.org:
> forwarded 1026740 https://github.com/pyviz-dev/pyct/issues/94
Bug #1026740 [src:pyct] pyct: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/pyviz-dev/pyct/issues/94'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1019681: marked as done (samizdat: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)
Your message dated Sat, 28 Jan 2023 17:28:12 +
with message-id
and subject line Bug#1019681: fixed in samizdat 0.7.1-2
has caused the Debian Bug report #1019681,
regarding samizdat: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
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.)
--
1019681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: samizdat
Version: 0.7.1-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild samizdat with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-test-files.yaml
> │
> └──┘
>
> RUBYLIB=/<>/debian/samizdat/usr/lib/ruby/vendor_ruby:.
> GEM_PATH=/<>/debian/samizdat/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
> ruby3.1 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> /usr/lib/ruby/vendor_ruby/whitewash.rb:125: warning: Object#untaint is
> deprecated and will be removed in Ruby 3.2
> /<>/debian/samizdat/usr/lib/ruby/vendor_ruby/samizdat/engine/globals.rb:21:
> warning: Object#untaint is deprecated and will be removed in Ruby 3.2
> Loaded suite -e
> Started
> E
> ===
> Error: test_box_with_title(TC_ApplicationHelper): Psych::DisallowedClass:
> Tried to load unspecified class: Regexp
> /usr/lib/ruby/3.1.0/psych/class_loader.rb:99:in `find'
> /usr/lib/ruby/3.1.0/psych/class_loader.rb:28:in `load'
> (eval):2:in `regexp'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:97:in `deserialize'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:128:in
> `visit_Psych_Nodes_Scalar'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `block in register_empty'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `each'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `register_empty'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:146:in
> `visit_Psych_Nodes_Sequence'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:345:in `block in revive_hash'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each_slice'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `revive_hash'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:167:in
> `visit_Psych_Nodes_Mapping'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:345:in `block in revive_hash'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each_slice'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `revive_hash'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:167:in
> `visit_Psych_Nodes_Mapping'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:345:in `block in revive_hash'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `each_slice'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:343:in `revive_hash'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:167:in
> `visit_Psych_Nodes_Mapping'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:3
Bug#1026549: bug 1026549 is forwarded to https://github.com/pytest-dev/pytest-xprocess/issues/117, tagging 1026549
Hi, Le Sat, Dec 31, 2022 at 11:42:12PM +0100, Timo R=F6hling a =E9crit : > forwarded 1026549 https://github.com/pytest-dev/pytest-xprocess/issues/117 Thanks Timo, I prepared an upload (new upstream release) of this package in order to fix this RC-bug as part of the BSP currently happening in St-Cergue, Switzerland. A merge request has been submitted. https://salsa.debian.org/python-team/packages/python-pytest-xprocess/-/merge_requests/1 Unless advised otherwise, I intend to upload the updated package tomorrow. Regards taffit signature.asc Description: PGP signature
Processed: block 1025884 with 1028113
Processing commands for cont...@bugs.debian.org:
> block 1025884 with 1028113
Bug #1025884 {Done: Paul Gevers } [src:ddnet] src:ddnet:
fails to migrate to testing for too long: FTBFS on s390x
1025884 was not blocked by any bugs.
1025884 was not blocking any bugs.
Added blocking bug(s) of 1025884: 1028113
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1025884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029845: harfbuzz: non-distributable font included in source
Source: harfbuzz Severity: serious Version: 6.0.0-1 Justification: Policy 2.1 Harfbuzz includes a nondistributable font in its test suite. I thought it was just in sid/bookworm, but it's apparently also in bullseye as well. In bullseye: test/shaping/data/in-house/fonts/641ca9d7808b01cafa9a666c13811c9b56eb9c52.ttf In sid: test/shape/data/in-house/fonts/641ca9d7808b01cafa9a666c13811c9b56eb9c52.ttf dilinger@hm90:~/sid-build/harfbuzz2$ exiftool -Copyright-en-US test/shape/data/in-house/fonts/641ca9d7808b01cafa9a666c13811c9b56eb9c52.ttf Copyright (en-US) : The digitally signed machine readable Typeface(Font) licensed to you is copyrighted ©, (2010), King Fahd Glorious Quran Printing Complex...ISBN: 978-603-8010-15-0, Accession No. 1430/7278..All rights reserved. This Font is the property of King Fahd Glorious Quran Printing Complex, and may not be reproduced, modified without the express written approval of King Fahd Glorious Quran Printing Complex. Upstream has removed the font, and Debian should as well: https://github.com/harfbuzz/harfbuzz/issues/4059
Bug#1027364: golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata)
El 28/1/23 a las 16:50, Adam Borowski escribió: Control: close 1027364 On Sat, Jan 28, 2023 at 04:31:25PM +0100, Santiago Vila wrote: retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata) reopen 1027364 found 0.5.0-2 thanks Adam, please don't close bugs just because they say "bullseye" in the title. In most cases, I really meant "bullseye and later". I've just re-tested: Distribution: bullseye Host Architecture: amd64 Source-Version: 0.5.0-2 Status: successful So the package does build ok. Do you have an example of a build environment that is not explicitly declared "totally broken" by the Policy (§2.5)? Policy 4.2 says packages MUST build from source in a build environment having only essential and build-essential packages. How do you suggest that I can check whether or not a package meets such requirement (remember, a MUST requirement) if not by building in a chroot with only essential and build essential packages? Please, tell me, how can it be that at the same time: a) Policy mandates that packages are buildable in a build environment with only essential and build essential packages, and b) I'm not allowed to build packages in a build environment with only essential and build essential packages to check that packages follow policy? Are you missing the fact that tzdata is not build-essential? I think you are missing the build-essential definition: It is not necessary to explicitly specify build-time relationships on a minimal set of packages that are always needed to compile, link and put in a Debian package a standard “Hello World!” program written in C or C++. The required packages are called build-essential, [...] Do you need tzdata to build a hello world package? No, you don't. Nobody does. Is tzdata essential? No, it's not essential either. Therefore, tzdata is not build essential. And because it's not build essential, one has to put it in build-depends if you use it during build. It's that simple. Thanks.
Processed: tagging 1026204
Processing commands for cont...@bugs.debian.org: > tags 1026204 - patch pending Bug #1026204 [tar] tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64 Removed tag(s) patch and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026549: bug 1026549 is forwarded to https://github.com/pytest-dev/pytest-xprocess/issues/117, tagging 1026549
Hi David, * David Prévot [2023-01-28 17:44]: I prepared an upload (new upstream release) of this package in order to fix this RC-bug as part of the BSP currently happening in St-Cergue, Switzerland. A merge request has been submitted. https://salsa.debian.org/python-team/packages/python-pytest-xprocess/-/merge_requests/1 Unless advised otherwise, I intend to upload the updated package tomorrow. I have no objections. Happy bug squashing! Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Processed: limit source to nekohtml, tagging 1021739
Processing commands for cont...@bugs.debian.org: > limit source nekohtml Limiting to bugs with field 'source' containing at least one of 'nekohtml' Limit currently set to 'source':'nekohtml' > tags 1021739 + pending Bug #1021739 [src:nekohtml] nekohtml: CVE-2022-24839 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64
Hello taffit, On Sat, Jan 28, 2023 at 12:10:53PM +0100, David Prévot wrote: > Hi, > > Le Wed, Jan 18, 2023 at 01:24:37AM +0100, Helge Deller a écrit : > > On Sat, 14 Jan 2023 20:38:38 +0100 Andreas Henriksson > > wrote: > > > Here's a slightly different patch to implement basically the same thing > > > > Yes, I like this patch better too. > > Unfortunately, even if both patches allow me to build tar on i386, they > also both lead to an FTBFS on amd64. Thanks for the feedback. I ran short on time when looking at this and tried to cheap out on just setting `-D_TIME_BITS=64` directly which causes problems. I generally have no clue when it comes to gnulib but I've now made an attempt at backporting the `year2038` gnulib module that upstream has enabled. I've pushed this here: https://salsa.debian.org/debian/tar/-/commits/wip/bug1026204 This time I've build-tested both on a sid amd64 chroot and a sid i386 chroot (on top of amd64). Maybe there's a better/cleaner way of doing this backport. I also have no idea if this impacts the output format of tar in any incompatible way, but hopefully it doesn't since upstream seems to now have it enabled by default in git atleast. Hopefully someone finds this useful... I'm not confident enough to actually upload this myself. Reviews welcome. Also note that the debian gnulib package seems to have the year2038 stuff in largefile.m4 already, so maybe it would be better to try to use that instead of the bundled m4 files in tar?!... (That should hopefully also sort out anyones worry about shipping generated (diff) files without source.) Regards, Andreas Henriksson
Bug#1027382: Please, minimize your build chroots
On 2023-01-28 15:03:04 +0200, Adrian Bunk wrote: > On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote: > >... > > * Those bugs are RC by definition and have been for a long time. > >... > > Please provide a pointer where a release team member has said so > explicitly in recent years. > > In my experience they are usually saying that FTBFS that do not happen > on the buildds of release architectures are usually not RC. Indeed. We require that packages are buildable on the buildds. If they don't and they built before, they are RC buggy. For all other FTBFS bugs, please use severity important at most. Cheers -- Sebastian Ramacher
Bug#1025614: marked as done (ecflow: (autopkgtest) needs update for python3.11: initialization of ecflow raised unreported exception)
Your message dated Sat, 28 Jan 2023 15:58:04 -0400 with message-id <20230128195804.hhnzhpgven3dx...@haydn.kardiogramm.net> and subject line Re: Bug#1024911: ecflow: (autopkgtest) needs update for python3.11: initialization of ecflow raised unreported exception has caused the Debian Bug report #1025614, regarding ecflow: (autopkgtest) needs update for python3.11: initialization of ecflow raised unreported exception 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.) -- 1025614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ecflow Version: 5.9.1-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of ecflow fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 ecflow from testing5.9.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/e/ecflow/28723767/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/ecflow/__init__.py", line 1, in from .ecflow import * SystemError: initialization of ecflow raised unreported exception autopkgtest [12:13:30]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 5.9.2-1 This is now passing again. The bug was in boost. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 signature.asc Description: PGP signature --- End Message ---
Processed: severity of 1027359 is important
Processing commands for cont...@bugs.debian.org:
> severity 1027359 important
Bug #1027359 {Done: Carsten Schoenert }
[src:arduino-builder] arduino-builder: FTBFS in bullseye (missing build-depends
on tzdata)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 1027363 is important, severity of 1027365 is important, severity of 1027366 is important ...
Processing commands for cont...@bugs.debian.org:
> severity 1027363 important
Bug #1027363 {Done: Stephen Gelman }
[src:golang-github-araddon-dateparse] golang-github-araddon-dateparse: FTBFS in
bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027365 important
Bug #1027365 {Done: Daniel Swarbrick }
[src:golang-github-go-playground-locales] golang-github-go-playground-locales:
FTBFS in bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027366 important
Bug #1027366 {Done: Daniel Swarbrick }
[src:golang-github-go-playground-validator-v10]
golang-github-go-playground-validator-v10: FTBFS in bullseye (missing
build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027367 important
Bug #1027367 {Done: Shengjing Zhu }
[src:golang-github-jinzhu-gorm] golang-github-jinzhu-gorm: FTBFS in bullseye
(missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027368 important
Bug #1027368 {Done: Thorsten Alteholz }
[src:golang-github-mitch01-go-hbci] golang-github-mitch01-go-hbci:
FTBFS in bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027369 important
Bug #1027369 {Done: Shengjing Zhu }
[src:golang-github-mohae-deepcopy] golang-github-mohae-deepcopy: FTBFS in
bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027371 important
Bug #1027371 {Done: Nobuhiro Iwamatsu }
[src:golang-github-tealeg-xlsx] golang-github-tealeg-xlsx: FTBFS in bullseye
(missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027372 important
Bug #1027372 {Done: Arun Kumar Pariyar }
[src:golang-github-teambition-rrule-go] golang-github-teambition-rrule-go:
FTBFS in bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027373 important
Bug #1027373 {Done: Nicholas D Steeves }
[src:golang-github-viant-toolbox] golang-github-viant-toolbox: FTBFS in
bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027374 important
Bug #1027374 [src:golang-github-xenolf-lego] golang-github-xenolf-lego: FTBFS
in bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027375 important
Bug #1027375 [src:golang-gopkg-libgit2-git2go.v31]
golang-gopkg-libgit2-git2go.v31: FTBFS in bullseye (missing build-depends on
tzdata)
Severity set to 'important' from 'serious'
> severity 1027376 important
Bug #1027376 {Done: Dr. Tobias Quathamer } [src:hugo] hugo:
FTBFS in bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027377 important
Bug #1027377 {Done: Stephen Kitt } [src:miller] miller: FTBFS
in bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> severity 1027379 important
Bug #1027379 {Done: Bernhard Schmidt } [src:nfdump] nfdump:
FTBFS in bullseye (missing build-depends on tzdata)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027363
1027365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027365
1027366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027366
1027367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027367
1027368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027368
1027369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027369
1027371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027371
1027372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027372
1027373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027373
1027374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027374
1027375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027375
1027376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027376
1027377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027377
1027379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 1029417 is important, severity of 1029420 is important, severity of 1029427 is important ...
Processing commands for cont...@bugs.debian.org:
> severity 1029417 important
Bug #1029417 {Done: Boian Bonev } [src:gammu] gammu: FTBFS
in bookworm (undeclared build-dependency on tzdata)
Severity set to 'important' from 'serious'
> severity 1029420 important
Bug #1029420 {Done: Andrew Caudwell } [src:gource] gource:
FTBFS in bookworm (undeclared build-dependency on tzdata)
Severity set to 'important' from 'serious'
> severity 1029427 important
Bug #1029427 {Done: James McCoy } [src:neovim] neovim:
FTBFS in bookworm (undeclared build-dependency on tzdata)
Severity set to 'important' from 'serious'
> severity 1029430 important
Bug #1029430 [src:reposurgeon] reposurgeon: FTBFS in bookworm (undeclared
build-dependency on tzdata)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1029417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029417
1029420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029420
1029427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029427
1029430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029853: bluedevil: Wait for the resolution of the libkscreen transition before migrating to testing
Package: bluedevil Severity: serious Prevent bluedevil transition to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029854: kwayland-integration: Wait for the resolution of the libkscreen transition before migrating to testing
Package: kwayland-integration Severity: serious Prevent kwayland-integration migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029855: plasma-disks: Wait for the resolution of the libkscreen transition before migrating to testing
Package: plasma-disks Severity: serious Prevent plasma-disks migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029856: plasma-nm: Wait for the resolution of the libkscreen transition before migrating to testing
Package: plasma-nm Severity: serious Prevent plasma-nm migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029857: breeze-plymouth: Wait for the resolution of the libkscreen transition before migrating to testing
Package: breeze-plymouth Severity: serious Prevent breeze-plymouth migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029858: polkit-kde-agent-1: Wait for the resolution of the libkscreen transition before migrating to testing
Package: polkit-kde-agent-1 Severity: serious Prevent polkit-kde-agent-1 migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029859: plasma-vault: Wait for the resolution of the libkscreen transition before migrating to testing
Package: plasma-vault Severity: serious Prevent plasma-vault migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029860: kwin: Wait for the resolution of the libkscreen transition before migrating to testing
Package: kwin Severity: serious Prevent kwin migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029861: breeze-grub: Wait for the resolution of the libkscreen transition before migrating to testing
Package: breeze-grub Severity: serious Prevent breeze-grub migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029862: kdecoration: Wait for the resolution of the libkscreen transition before migrating to testing
Package: kdecoration Severity: serious Prevent kdecoration migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029863: plasma-workspace-wallpapers: Wait for the resolution of the libkscreen transition before migrating to testing
Package: plasma-workspace-wallpapers Severity: serious Prevent plasma-workspace-wallpapers migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029864: plasma-nano: Wait for the resolution of the libkscreen transition before migrating to testing
Package: plasma-nano Severity: serious Prevent plasma-nano migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029865: plasma-pa: Wait for the resolution of the libkscreen transition before migrating to testing
Package: plasma-pa Severity: serious Prevent plasma-pa migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
Bug#1029866: plasma-thunderbolt: Wait for the resolution of the libkscreen transition before migrating to testing
Package: plasma-thunderbolt Severity: serious Prevent plasma-thunderbolt migration to testing until the libkscreen transition for 5.26.90/5.27 is resolved.
