Bug#1055043: Debian carnivore: port from Python 2 to 3
Package: qa.debian.org Severity: serious User: qa.debian@packages.debian.org Usertags: carnivore X-Debbugs-CC: m...@qa.debian.org, debian-pyt...@lists.debian.org The carnivore system which tracks the activity of Debian members is written in Python 2, which has been removed from Debian, so carnivore needs porting to Python 3 and volunteers are needed to work on that. https://salsa.debian.org/qa/qa/-/tree/master/carnivore/ https://salsa.debian.org/qa/qa/-/blob/master/data/cronjobs/carnivore https://salsa.debian.org/qa/qa/-/blob/data/cronjobs/ddpo.carnivore https://salsa.debian.org/qa/qa/-/blob/data/ddpo/extract_carnivore.pl -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1055017: marked as done (node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED)
Your message dated Mon, 30 Oct 2023 03:19:03 + with message-id and subject line Bug#1055017: fixed in node-html-webpack-plugin 5.5.3+repack1-1 has caused the Debian Bug report #1055017, regarding node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED 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.) -- 1055017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-html-webpack-plugin Version: 5.5.3+~cs14.4.8-1 Severity: serious On 2023-10-29 04:49, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package node-html-minifier-terser, version > 5.5.3+~cs14.4.8-1, for all, > however unstable already has version 7.2.0~5.5.3+~cs14.4.7-2. > Uploads to unstable must have a higher version than present in unstable. > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: node-html-webpack-plugin Source-Version: 5.5.3+repack1-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-html-webpack-plugin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-html-webpack-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 30 Oct 2023 06:49:00 +0400 Source: node-html-webpack-plugin Architecture: source Version: 5.5.3+repack1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1055017 Changes: node-html-webpack-plugin (5.5.3+repack1-1) unstable; urgency=medium . * Drop component html-minifier-terser and repack (Closes: #1055017) Checksums-Sha1: 821935c7dd6e5b1ca83819ee5d0c21060fbd12a3 2955 node-html-webpack-plugin_5.5.3+repack1-1.dsc 82b4f9b4f18fa8ee11dc18b8cb4e0db5fc9f7602 16996 node-html-webpack-plugin_5.5.3+repack1.orig-relateurl.tar.gz 4102129b24074b47bace88e0f65d9ef87eacc4f9 798116 node-html-webpack-plugin_5.5.3+repack1.orig.tar.gz 9ca16fd9420cb7b5932a9a8d2d158e884e995850 3784 node-html-webpack-plugin_5.5.3+repack1-1.debian.tar.xz Checksums-Sha256: e13041a4be8776538f9b28b9b75c0576df7f479a84b62a6535df1594e802a4b1 2955 node-html-webpack-plugin_5.5.3+repack1-1.dsc 1cf4e97bc5384bf01bd78a0181c692ecb660677e94ad4df7ee756e4235eeb22b 16996 node-html-webpack-plugin_5.5.3+repack1.orig-relateurl.tar.gz 8d3d3f35ddf245aaefc380c7bc1424bd7a2fffa641ed9995ef882443a467a322 798116 node-html-webpack-plugin_5.5.3+repack1.orig.tar.gz 6bd7f3d7a6d511090b1a868d92472c75eeb7a81a81ac84d2d405f3159f2460a6 3784 node-html-webpack-plugin_5.5.3+repack1-1.debian.tar.xz Files: 9150319b819ef2f8c8b2861990a70ab9 2955 javascript optional node-html-webpack-plugin_5.5.3+repack1-1.dsc 85703eb36d347c619745ea5fd953153b 16996 javascript optional node-html-webpack-plugin_5.5.3+repack1.orig-relateurl.tar.gz c6a77b27fd141fb19db2e44f21ea943e 798116 javascript optional node-html-webpack-plugin_5.5.3+repack1.orig.tar.gz 3a377cad06268aa621820758befe9d0b 3784 javascript optional node-html-webpack-plugin_5.5.3+repack1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmU/HakACgkQ9tdMp8mZ 7ukxUBAAm/IdAg32GSZlvBF/R9moFWTOjZQbEvouLNJwmNgTJmC8h/nmzPEqdSPW yObiC0UqNNjdRnlw/h4Fy0eoxdYzEe8D3aUgRqc597k+yIi57yP2qCC1guOThv0v BN4AdnhK5n04qF3ebEdeFzoUjwQZFhJYFpczx5u/O4yK/T9+6X5luTCnkW7HyTGt aegpKEp51ptEvqgr6/JWitvssQsTVHtkvCVSfW1P0Hgaz6IiLBgpRWO6aXnAFZuL Zv+fD52NTDSnuTrqP4MBi3FFz3uRwgdXOXs2Rk/0qSgygoYShvqyuSp7+w0Jlf1Q 8uMARQubfuHW2ptJDZyPn7teuweggDK4tTyx4J8Wni4n1alrV+yNR2l0K4wS8qxZ TW1Lq87FELt6RnXXf9G6rP/hzDTgayf5VVXmSyWnDU3/l9GmDEjIHrTjjIQM7fkx t9rEZf+JlAvx6X70TsyTUQjyWkq3h6Fk2ebeR6+NoxESxmwvoZ8yB6+6ZhH1iFpK bP9uD2i2+Z5+gIegJp4x9kbmFEW/Utcbs0BeCkVlvtTYvdxZ9jpjjLqUK32mwRN6 AvAkYjLloWp1k8cS+6ZBipKKHzyoR4t5FvEjSuLE0RDSjTQ0Kmgy8a5n9QnwhdHQ ILNTOJzLUaJekY81YezIpqcJf95Hq/aXDr1Gmz0MNIkVn9JrEao= =r9wh
Processed: Bug#1055017 marked as pending in node-html-webpack-plugin
Processing control commands: > tag -1 pending Bug #1055017 [src:node-html-webpack-plugin] node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED Added tag(s) pending. -- 1055017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055017: marked as pending in node-html-webpack-plugin
Control: tag -1 pending Hello, Bug #1055017 in node-html-webpack-plugin 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/js-team/node-html-webpack-plugin/-/commit/a4479104364aed52971c11db02545c809ac664b8 Drop component html-minifier-terser Closes: #1055017 (this message was generated automatically) -- Greetings https://bugs.debian.org/1055017
Bug#1054252: marked as done (g2o: binary-all FTBFS)
Your message dated Mon, 30 Oct 2023 01:36:24 + with message-id and subject line Bug#1054252: fixed in g2o 0~20230806-3 has caused the Debian Bug report #1054252, regarding g2o: binary-all FTBFS 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.) -- 1054252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: g2o Version: 0~20230806-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=g2o=all=0~20230806-2=1696411342=0 ... The following tests FAILED: 1 - unittest_general (Not Run) 2 - unittest_data (Not Run) 3 - unittest_stuff (Not Run) 4 - unittest_sclam2d (Not Run) 5 - unittest_slam2d (Not Run) 6 - unittest_slam2d_addons (Not Run) 7 - unittest_slam3d (Not Run) 8 - unittest_slam3d_addons (Not Run) 9 - unittest_sim3 (Not Run) 10 - unittest_sba (Not Run) 11 - unittest_solver (Not Run) Errors while running CTest make[1]: *** [Makefile:94: test] Error 8 --- End Message --- --- Begin Message --- Source: g2o Source-Version: 0~20230806-3 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of g2o, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated g2o 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: Sun, 29 Oct 2023 17:56:35 -0700 Source: g2o Binary: libg2o-dev libg2o-doc libg2o0 libg2o0-dbgsym Architecture: source amd64 all Version: 0~20230806-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Dima Kogan Description: libg2o-dev - C++ framework for optimizing graph-based nonlinear error function libg2o-doc - C++ framework for optimizing graph-based nonlinear error function libg2o0- C++ framework for optimizing graph-based nonlinear error function Closes: 1054252 Changes: g2o (0~20230806-3) unstable; urgency=medium . * Fixed arch=all build (Closes: #1054252) * Ifxed arch-i386 build Checksums-Sha1: 406be61aceec97b4996bfd2a568fec87361c7802 2278 g2o_0~20230806-3.dsc 5adf58f35b9e93dfd0ac7eb00fa608758bf5cf43 9116 g2o_0~20230806-3.debian.tar.xz b81c0262ca1a70d6238c7f91c0a5638e6ff3fa18 15416 g2o_0~20230806-3_amd64.buildinfo f15934ead9e1224e833c63828f00b3fd88f71a28 123784 libg2o-dev_0~20230806-3_amd64.deb bde70c79a7c9f1c3153f9f3ffd8c7a2b9c4a9b9c 209714784 libg2o-doc_0~20230806-3_all.deb 0a235b6d8114b9ae3c3811f6a4466f023ba7bd59 145145880 libg2o0-dbgsym_0~20230806-3_amd64.deb 41e519b7b924dbc019c2fe8ddf7b545f19949db6 826632 libg2o0_0~20230806-3_amd64.deb Checksums-Sha256: a30c12cc88272518f1522bc67b59530e1b15026701504e6091f55da110f4dea8 2278 g2o_0~20230806-3.dsc da5e9b0233079397d0d24606103051df6a91bb0d494c4f465838698cc8194c74 9116 g2o_0~20230806-3.debian.tar.xz 55a5ea57331fb1b188b15f1404d7efbb0040818c9ad8be77144715ca5b63d91a 15416 g2o_0~20230806-3_amd64.buildinfo 7da8a2acdd7ce3c46b43d6b14eb57296d4ae24771b5b6a844499704194f788e8 123784 libg2o-dev_0~20230806-3_amd64.deb 859de3c9362ee3c608d207114da37146bb3ffa7e8f1e572952c9ad220b50488f 209714784 libg2o-doc_0~20230806-3_all.deb 46580f5fd82ff03a3f0d81266db2e70f0d90a43cee2393d112e1647ce2ec66dd 145145880 libg2o0-dbgsym_0~20230806-3_amd64.deb e7e3c14ee5aef92879849128f34b184e42cc78fd1a02f347fda815ab481a6792 826632 libg2o0_0~20230806-3_amd64.deb Files: bc4043782d594c01646f1e1499a7e531 2278 science optional g2o_0~20230806-3.dsc 8d2c41db8f148b9355cb6f9e4fbb4321 9116 science optional g2o_0~20230806-3.debian.tar.xz 5c8653f80590834ec6bd93c781fb027a 15416 science optional g2o_0~20230806-3_amd64.buildinfo 7459148b0ca38abdd38aabbaa99cafce 123784 libdevel optional libg2o-dev_0~20230806-3_amd64.deb af1de70e631dad8407b80554ad2b01ab 209714784 doc optional libg2o-doc_0~20230806-3_all.deb 29f60aab7f5d133a30ce654b59342ee6 145145880 debug optional libg2o0-dbgsym_0~20230806-3_amd64.deb d445a9cb6bbe0fad2a8f669144586f78 826632 libs optional libg2o0_0~20230806-3_amd64.deb -BEGIN PGP
Bug#1050769: dh-cargo: should provide a build() method
Quack, Sorry for the lag, I really lacked time and energy recently but I'll try to upload a fix soon. On 2023-10-07 04:09, Jeremy Bícha wrote: No, greetd needs to build itself correctly regardless of whether there are helper functions available. You're right and I did not realize nocheck would be used for real in this package. I never saw this as a perfect solution but until debcargo implements what's needed that seemed fine. https://salsa.debian.org/debian/greetd/-/merge_requests/4 It looks fine but that's precisely what I wanted to avoid: I do not want to maintain the build steps and have to update the calls and flags when cargo or any other piece of tooling changes. Maybe that won't change often but that's still silly to implement that in each and every leaf package and as a consequence there's no unified policy. Unfortunately I do not have the bandwidth to propose debcargo changes. So I guess I'll apply the patch you kindly provided but I'm thinking about handing over the maintainership of wlgreet and greetd to people who really have time to do it properly, or… maybe comaint. Anyway, thanks for the report and patch everyone. \_o< -- Marc Dequènes
Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices
On Sun, Oct 29, 2023 at 09:02:01PM +0100, Philip Hands wrote:
> Philip Hands writes:
>
> > Anthony Iliopoulos writes:
> > ...
> >> Yeap it is due to nrext64, I've submitted a patch to grub (should have
> >> cc'ed linux-xfs..)
> >>
> >> https://lore.kernel.org/grub-devel/20231026095339.31802-1-ail...@suse.com/
> >
> > That certainly seems to fix this bug.
>
> ... but sadly that may not be the end of the story.
>
> I've persuaded D-I to use the patched grub version, and when testing it,
> it now gets past the previous failure to complete the install, but then
> fails to boot after the first reboot, as seen here:
>
> https://openqa.debian.net/tests/200160#step/_console_wait_login/7
>
> where it drops to the 'grub rescue>' prompt, complaining that:
>
> error: file `/boot/grub/i386-pc/normal.mod' not found.
>
> if one types `ls (hd0,msdos1)/boot/grub/i386-pc` at that rescue prompt,
> it lists the files up to msdospart.mod and then says:
>
> error: invalid XFS directory entry.
>
> (BTW the directory seemed fine before the reboot, because I listed it)
This issue exists independently of the large extent counter, and it is
related to grub commit ef7850c75 ("fs/xfs: Fix issues found while
fuzzing the XFS filesystem"). That's actually the issue described in
#1051543.
There's a proposed fix at [1], and it works as expected with that patch
applied.
Regards,
Anthony
[1] https://lore.kernel.org/grub-devel/20231018030347.36174-1-n...@vault24.org/
Processed (with 2 errors): Closing #1042688
Processing commands for cont...@bugs.debian.org: > close 1042688 Bug #1042688 [src:python-pykka] python-pykka: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting Marked Bug as done > This issue was resolved in Pykka 4.0.0, which has been in Debian testing Unknown command or malformed arguments to command. > for a while. Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 1042688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1049331: marked as done (python3-blockdiag: fails with Pil 10)
Your message dated Sun, 29 Oct 2023 21:34:08 +
with message-id
and subject line Bug#1049331: fixed in blockdiag 2.0.1+dfsg-2
has caused the Debian Bug report #1049331,
regarding python3-blockdiag: fails with Pil 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.)
--
1049331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-blockdiag
Version: 2.0.1+dfsg-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Hi,
i don't use it directly, but via python3-sphinxcontrib.seqdiag, but that must
not
matter. Instead of producing image, it produces warning:
WARNING: dot code 'seqdiag {...}': 'ImageDraw' object has no attribute
'textsize'
AFAIK, the 'textsize' attribute was removed from PIL. It is reported to to
upstream
already (not by me), see https://github.com/blockdiag/seqdiag/issues/63
By that, the package is not usable at all.
regards
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Versions of packages python3-blockdiag depends on:
ii python33.11.4-5+b1
ii python3-docutils 0.19+dfsg-6
ii python3-funcparserlib 1.0.0-0.2
ii python3-pil10.0.0-1
ii python3-pkg-resources 68.0.0-1
ii python3-reportlab 4.0.4-9
ii python3-webcolors 1.11.1-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: blockdiag
Source-Version: 2.0.1+dfsg-2
Done: Sergio de Almeida Cipriano Junior
We believe that the bug you reported is fixed in the latest version of
blockdiag, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1049...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sergio de Almeida Cipriano Junior (supplier of updated
blockdiag package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 18 Oct 2023 23:03:49 -0300
Source: blockdiag
Architecture: source
Version: 2.0.1+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team
Changed-By: Sergio de Almeida Cipriano Junior
Closes: 850871 1042205 1049331
Changes:
blockdiag (2.0.1+dfsg-2) unstable; urgency=high
.
* Refresh patches, add standard DEP-3 fields to all patches.
* Add d/p/0009-Add-support-for-Pillow-10.patch:
+ Pillow (PIL) 10.0.1 removed several functions for computing the size and
offset of rendered text. The patch, which was cherry-picked from upstream,
fixes these breaking changes in a backwards compatible way (Closes:
#1049331, #1042205).
* Remove d/blockdiag folder, it was being used for nothing.
* d/copyright: Change URIs to use HTTPS.
* d/control:
+ Remove redundant build dependency.
- The python3-docutils build dependency is listed more
than one time when one would be sufficient.
+ Set Rules-Requires-Root to no.
- This package does not require fakeroot or root privileges.
+ Add VCS fields pointing to salsa.debian.org (Closes: #850871).
+ Bump Standards-Version from 4.5.1 to 4.6.2, no changes needed.
+ Move blockdiag to the Python team and add myself as uploader.
Checksums-Sha1:
80d470abbfcc7b828338f8bc1c783e4028bc901c 2337 blockdiag_2.0.1+dfsg-2.dsc
cf2d61ab7ce0a3ffc111d2fb02726f16b4bc8d06 116192
blockdiag_2.0.1+dfsg.orig.tar.xz
c5c14cc3d0d21e0b30d2cec92353762f1912e686 13328
blockdiag_2.0.1+dfsg-2.debian.tar.xz
da6e5ea6571d9c933fb322f3692a7e5f48b58200 9288
blockdiag_2.0.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
c10307d65680a8748bef31cf415d63ca09f585b6370eb7d22cb029fd98ee3a55 2337
blockdiag_2.0.1+dfsg-2.dsc
e717376ad4d4340ab2e7b7553611703abdc673b0bfe98d343cca1317f25f6262 116192
blockdiag_2.0.1+dfsg.orig.tar.xz
1b4d5f803db7b834f4ca28b6a6ca230de858fb831a70c933ddfcb1df8a3eed4f 13328
blockdiag_2.0.1+dfsg-2.debian.tar.xz
5fce1b3e5663f7e2aaf6f7c320b7168e8dda4cf396927841a05e3fbb37d95e4e 9288
blockdiag_2.0.1+dfsg-2_amd64.buildinfo
Files:
473adf0bc6a70e227270c8476618eb97 2337 python optional
blockdiag_2.0.1+dfsg-2.dsc
4d135961f8c1659fff5e26c5326ec754 116192
Processed: tagging 1042627, tagging 1042661, tagging 1042660, tagging 1042643, tagging 1043075, tagging 1042705 ...
Processing commands for cont...@bugs.debian.org:
> tags 1042627 + sid trixie
Bug #1042627 [src:emscripten] emscripten: FTBFS with Sphinx 7.1, docutils 0.20:
make[1]: *** [debian/rules:210: execute_after_dh_auto_build-indep] Error 2
Added tag(s) trixie and sid.
> tags 1042661 + sid trixie
Bug #1042661 [src:python-djvulibre] python-djvulibre: FTBFS with Sphinx 7.1,
docutils 0.20: error: invalid command 'build_sphinx'
Added tag(s) sid and trixie.
> tags 1042660 + sid trixie
Bug #1042660 {Done: Nicholas Breen } [src:votca] votca:
FTBFS with Sphinx 7.1, docutils 0.20: make[5]: ***
[share/doc/CMakeFiles/doc.dir/build.make:81: share/doc/CMakeFiles/doc] Error 2
Added tag(s) trixie and sid.
> tags 1042643 + sid trixie
Bug #1042643 {Done: gregor herrmann }
[src:libtext-markup-perl] libtext-markup-perl: FTBFS with Sphinx 7.1, docutils
0.20: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit
code 1
Added tag(s) trixie and sid.
> tags 1043075 + sid trixie
Bug #1043075 [python3-openstackdocstheme] python3-openstackdocstheme:
Incompatible with Sphinx 7
Added tag(s) trixie and sid.
> tags 1042705 + sid trixie
Bug #1042705 [src:sqlite-utils] sqlite-utils: FTBFS with Sphinx 7.1, docutils
0.20: TypeError: not all arguments converted during string formatting
Added tag(s) trixie and sid.
> tags 1042705 + sid trixie
Bug #1042705 [src:sqlite-utils] sqlite-utils: FTBFS with Sphinx 7.1, docutils
0.20: TypeError: not all arguments converted during string formatting
Ignoring request to alter tags of bug #1042705 to the same tags previously set
> tags 1042704 + sid trixie
Bug #1042704 [src:qutip] qutip: FTBFS with Sphinx 7.1, docutils 0.20:
TypeError: not all arguments converted during string formatting
Added tag(s) trixie and sid.
> tags 1042700 + sid trixie
Bug #1042700 [src:python-padme] python-padme: FTBFS with Sphinx 7.1, docutils
0.20: error: invalid command 'build_sphinx'
Added tag(s) sid and trixie.
> tags 1042703 + sid trixie
Bug #1042703 [src:python-pgpy] python-pgpy: FTBFS with Sphinx 7.1, docutils
0.20: make[2]: *** [Makefile:53: html] Error 2
Added tag(s) sid and trixie.
> tags 1042698 + sid trixie
Bug #1042698 [src:python-vispy] python-vispy: FTBFS with Sphinx 7.1, docutils
0.20: AttributeError: 'container' object has no attribute 'html5tagname'
Added tag(s) sid and trixie.
> tags 1042695 + sid trixie
Bug #1042695 [src:vine] vine: FTBFS with Sphinx 7.1, docutils 0.20: make[1]:
*** [debian/rules:16: override_dh_auto_build] Error 2
Added tag(s) sid and trixie.
> tags 1042694 + sid trixie
Bug #1042694 [src:deap] deap: FTBFS with Sphinx 7.1, docutils 0.20: TypeError:
not all arguments converted during string formatting
Added tag(s) trixie and sid.
> tags 1042688 + sid trixie
Bug #1042688 [src:python-pykka] python-pykka: FTBFS with Sphinx 7.1, docutils
0.20: TypeError: not all arguments converted during string formatting
Added tag(s) trixie and sid.
> tags 1042687 + sid trixie
Bug #1042687 [src:ycm-cmake-modules] ycm-cmake-modules: FTBFS with Sphinx 7.1,
docutils 0.20: TypeError: not all arguments converted during string formatting
Added tag(s) trixie and sid.
> tags 1042685 + sid trixie
Bug #1042685 [src:flufl.password] flufl.password: FTBFS with Sphinx 7.1,
docutils 0.20: error: invalid command 'build_sphinx'
Added tag(s) trixie and sid.
> tags 1042683 + sid trixie
Bug #1042683 [src:sagemath] sagemath: FTBFS with Sphinx 7.1, docutils 0.20:
[reference] RuntimeError: This function shouldn't be called in "inventory"
builder
Added tag(s) trixie and sid.
> tags 1042681 + sid trixie
Bug #1042681 [src:logbook] logbook: FTBFS with Sphinx 7.1, docutils 0.20:
intersphinx inventory '/usr/share/doc/python2.7/html/objects.inv' not fetchable
due to : [Errno 2] No such file or directory:
'/usr/share/doc/python2.7/html/objects.inv'
Added tag(s) sid and trixie.
> tags 1042680 + sid trixie
Bug #1042680 [src:sphinxcontrib-trio] sphinxcontrib-trio: FTBFS with Sphinx
7.1, docutils 0.20: AttributeError: 'Sphinx' object has no attribute
'add_stylesheet'
Added tag(s) sid and trixie.
> tags 1042679 + sid trixie
Bug #1042679 [src:quark-sphinx-theme] quark-sphinx-theme: FTBFS with Sphinx
7.1, docutils 0.20: AssertionError: no elements
Added tag(s) sid and trixie.
> tags 1042677 + sid trixie
Bug #1042677 [src:flask-security] flask-security: FTBFS with Sphinx 7.1,
docutils 0.20: make[1]: *** [debian/rules:25: override_dh_sphinxdoc] Error 2
Added tag(s) sid and trixie.
> tags 1042675 + sid trixie
Bug #1042675 [src:sphinx-gallery] sphinx-gallery: FTBFS with Sphinx 7.1,
docutils 0.20: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.11 --system=custom "--test-args={interpreter} -m pytest
--ignore=sphinx_gallery/tests/test_full.py -k \"not
test_embed_code_links_get_data\" sphinx_gallery/tests" returned exit code 13
Added tag(s) sid and trixie.
> tags 1042676 + sid trixie
Bug #1042676 [src:python-public] python-public: FTBFS with Sphinx 7.1, docutils
0.20: error: invalid
Processed: graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed]
Processing commands for cont...@bugs.debian.org: > severity 1042029 normal Bug #1042029 [src:graph-tool] graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed] Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1042029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-igraph: FTBFS: dh_auto_test:
Processing commands for cont...@bugs.debian.org:
> severity 1054721 normal
Bug #1054721 {Done: Lucas Nussbaum } [src:python-igraph]
python-igraph: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p
3.11 returned exit code 13
Severity set to 'normal' from 'serious'
> forwarded 1054721 https://github.com/igraph/python-igraph/issues/728
Bug #1054721 {Done: Lucas Nussbaum } [src:python-igraph]
python-igraph: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p
3.11 returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/igraph/python-igraph/issues/728'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1054721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#958692: node-matrix-js-sdk: Remove dependency to node-request
Quoting Praveen Arimbrathodiyil (2023-10-29 18:13:55) > On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote: > > Upstream has deprecated node-request: > > https://github.com/request/request/issues/3142 > > > > It can be replaced by node-got > > > > > > Hi Jonas, Hubert, > > Are you planning to update matrix-js-sdk? We'd like to remove deprecated > node-request from the archive and this package is a blocker. I have no interest in matrix-js-sdk. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#958682: node-jsonld: Remove dependency to node-request
Quoting Praveen Arimbrathodiyil (2023-10-29 18:10:08) > On Fri, 31 Dec 2021 13:17:07 +0100 Yadd wrote: > > updating node-jsonld is enough to fix this issue: > > Hi Jonas, > > Are you planning to update node-jsonld? > > > Else we can simply remove this package from Debian since it seems > > useless (no reverse dependencies). > > This is blocking removal of deprecated node-request. Yes, I still want to work on node-jsonld - I will make time to look at this soon... - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1054965: marked as done (guile-2.2: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Sun, 29 Oct 2023 21:10:19 +0100 with message-id and subject line Re: Bug#1054965: guile-2.2: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 has caused the Debian Bug report #1054965, regarding guile-2.2: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: guile-2.2 Version: 2.2.7+1-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>' > Testing /<>/meta/guile ... > with GUILE_LOAD_PATH=/<>/test-suite > Running 00-initial-env.test > Running 00-repl-server.test > Running 00-socket.test > Running alist.test > Running and-let-star.test > Running array-map.test > Running arrays.test > Running asyncs.test > ERROR: asyncs.test: preemption via sigprof - arguments: ((vm-error vm-run > "Unrewindable partial continuation" (#))) > Running atomic.test > Running bit-operations.test > Running bitvectors.test > Running brainfuck.test > Running bytevectors.test > Running c-api.test > Running chars.test > Running coding.test > Running common-list.test > Running compiler.test > Running continuations.test > Running control.test > Running coverage.test > Running cross-compilation.test > Running curried-definitions.test > Running dwarf.test > Running ecmascript.test > Running elisp-compiler.test > Running elisp-reader.test > Running elisp.test > Running encoding-escapes.test > UNRESOLVED: encoding-escapes.test: input escapes: \xfaltima > UNRESOLVED: encoding-escapes.test: input escapes: \u7f85\u751f\u9580 > Running encoding-iso88591.test > Running encoding-iso88597.test > Running encoding-utf8.test > Running eval-string.test > Running eval.test > Running exceptions.test > Running fdes-finalizers.test > Running filesys.test > Running fluids.test > Running foreign.test > UNRESOLVED: foreign.test: pointer<->string: bijection [latin1] > Running format.test > Running fractions.test > Running ftw.test > Running future.test > Running gc.test > Running getopt-long.test > Running goops.test > Running guardians.test > UNRESOLVED: guardians.test: g2-garbage saved > UNRESOLVED: guardians.test: standard guardian functionality: guarding > independent objects: re-guarding non-immediates > UNRESOLVED: guardians.test: standard guardian functionality: guarding weakly > referenced objects: guarded element of weak vector gets eventually removed > from weak vector > Running hash.test > Running hooks.test > Running i18n.test > UNRESOLVED: i18n.test: text collation (French): string-locale UNRESOLVED: i18n.test: text collation (French): char-locale UNRESOLVED: i18n.test: text collation (French): string-locale-ci=? > UNRESOLVED: i18n.test: text collation (French): string-locale-ci=? (2 args, > wide strings) > UNRESOLVED: i18n.test: text collation (French): string-locale-ci=? (3 args, > wide strings) > UNRESOLVED: i18n.test: text collation (French): string-locale-ci<>? > UNRESOLVED: i18n.test: text collation (French): string-locale-ci<>? (wide > strings) > UNRESOLVED: i18n.test: text collation (French): string-locale-ci<>? (wide and > narrow strings) > UNRESOLVED: i18n.test: text collation (French): char-locale-ci<>? > UNRESOLVED: i18n.test: text collation (French): char-locale-ci<>? (wide) > UNRESOLVED: i18n.test: text collation (German): string-locale-ci=? > UNRESOLVED: i18n.test: text collation (Greek): string-locale-ci=? > UNRESOLVED: i18n.test: text collation (Czech): string-locale UNRESOLVED: i18n.test: character mapping: char-locale-upcase Turkish > UNRESOLVED: i18n.test: character mapping: char-locale-downcase Turkish > UNRESOLVED: i18n.test: string mapping: string-locale-upcase German > UNRESOLVED: i18n.test: string mapping: string-locale-upcase Greek > UNRESOLVED: i18n.test: string mapping: string-locale-upcase Greek (two sigmas) > UNRESOLVED: i18n.test: string mapping: string-locale-downcase Greek > UNRESOLVED: i18n.test: string mapping: string-locale-downcase Greek (two > sigmas) > UNRESOLVED: i18n.test: string mapping: string-locale-upcase Turkish > UNRESOLVED: i18n.test: string mapping: string-locale-downcase Turkish > UNRESOLVED: i18n.test: number parsing: locale-string->inexact (French) >
Bug#1054980: marked as done (django-dirtyfields: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Sun, 29 Oct 2023 21:09:21 +0100
with message-id
and subject line Re: Bug#1054980: django-dirtyfields: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit
code 13
has caused the Debian Bug report #1054980,
regarding django-dirtyfields: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
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.)
--
1054980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-dirtyfields
Version: 1.3.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:310: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.11_django-dirtyfields/build/dirtyfields
> copying src/dirtyfields/compare.py ->
> /<>/.pybuild/cpython3_3.11_django-dirtyfields/build/dirtyfields
> copying src/dirtyfields/__init__.py ->
> /<>/.pybuild/cpython3_3.11_django-dirtyfields/build/dirtyfields
> copying src/dirtyfields/compat.py ->
> /<>/.pybuild/cpython3_3.11_django-dirtyfields/build/dirtyfields
> copying src/dirtyfields/dirtyfields.py ->
> /<>/.pybuild/cpython3_3.11_django-dirtyfields/build/dirtyfields
> PYTHONPATH=. python3 -m sphinx -N -bhtml docs/ build/html # HTML generator
> Running Sphinx v5.3.0
> WARNING: Invalid configuration value found: 'language = None'. Update your
> configuration to a valid language code. Falling back to 'en' (English).
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> loading intersphinx inventory from http://docs.python.org/2.7/objects.inv...
> loading intersphinx inventory from http://sphinx.pocoo.org/objects.inv...
> loading intersphinx inventory from
> http://docs.djangoproject.com/en/dev/_objects/...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.python.org/2.7/objects.inv' not fetchable
> due to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://docs.python.org/2.7/objects.inv (Caused by ProxyError('Cannot connect
> to proxy.', NewConnectionError(' 0x7f87006c6f10>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.djangoproject.com/en/dev/_objects/' not
> fetchable due to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://docs.djangoproject.com/en/dev/_objects/ (Caused by ProxyError('Cannot
> connect to proxy.', NewConnectionError(' object at 0x7f86fe50f810>: Failed to establish a new connection: [Errno 111]
> Connection refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://sphinx.pocoo.org/objects.inv' not fetchable due
> to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://sphinx.pocoo.org/objects.inv (Caused by ProxyError('Cannot connect to
> proxy.', NewConnectionError(' 0x7f86fe518c50>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 3 source files that are out of date
> updating environment: [new config] 3 added, 0 changed, 0 removed
> reading sources... [ 33%] contributing
> reading sources... [ 66%] credits
> reading sources... [100%] index
>
> /<>/docs/index.rst:88: WARNING: Title underline too short.
>
> Checking many-to-many fields.
>
> /<>/docs/index.rst:88: WARNING: Title underline too short.
>
> Checking many-to-many fields.
>
> /<>/docs/index.rst:122: WARNING: Title underline too short.
>
> Checking a limited set of model fields.
> -
> /<>/docs/index.rst:122: WARNING: Title underline too short.
>
> Checking a limited set of model fields.
> -
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 33%] contributing
> writing output... [ 66%] credits
>
Bug#1055034: mysql-8.0: CVE-2023-22032 CVE-2023-22059 CVE-2023-22064 CVE-2023-22066 CVE-2023-22068 CVE-2023-22070 CVE-2023-22078 CVE-2023-22079 CVE-2023-22084 CVE-2023-22092 CVE-2023-22097 CVE-2023-22
Source: mysql-8.0 Version: 8.0.34-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for mysql-8.0. CVE-2023-22032[0]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.34 and prior and 8.1.0. Easily exploitable | vulnerability allows high privileged attacker with network access | via multiple protocols to compromise MySQL Server. Successful | attacks of this vulnerability can result in unauthorized ability to | cause a hang or frequently repeatable crash (complete DOS) of MySQL | Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS | Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22059[1]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.34 and prior and 8.1.0. Easily exploitable | vulnerability allows low privileged attacker with network access via | multiple protocols to compromise MySQL Server. Successful attacks | of this vulnerability can result in unauthorized ability to cause a | hang or frequently repeatable crash (complete DOS) of MySQL Server. | CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22064[2]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.34 and prior. Easily exploitable vulnerability | allows high privileged attacker with network access via multiple | protocols to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized ability to cause a hang or | frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 | Base Score 4.9 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22066[3]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: InnoDB). Supported versions that are affected are | 8.0.34 and prior and 8.1.0. Easily exploitable vulnerability allows | high privileged attacker with network access via multiple protocols | to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized ability to cause a hang or | frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 | Base Score 4.9 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22068[4]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: InnoDB). Supported versions that are affected are | 8.0.34 and prior and 8.1.0. Easily exploitable vulnerability allows | high privileged attacker with network access via multiple protocols | to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized ability to cause a hang or | frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 | Base Score 4.9 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22070[5]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.34 and prior and 8.1.0. Easily exploitable | vulnerability allows high privileged attacker with network access | via multiple protocols to compromise MySQL Server. Successful | attacks of this vulnerability can result in unauthorized ability to | cause a hang or frequently repeatable crash (complete DOS) of MySQL | Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS | Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22078[6]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.34 and prior and 8.1.0. Easily exploitable | vulnerability allows high privileged attacker with network access | via multiple protocols to compromise MySQL Server. Successful | attacks of this vulnerability can result in unauthorized ability to | cause a hang or frequently repeatable crash (complete DOS) of MySQL | Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS | Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22079[7]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.34 and prior. Easily exploitable vulnerability | allows low privileged attacker with network access via multiple | protocols to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized ability to cause a hang or | frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 | Base Score 6.5 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22084[8]: |
Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices
Philip Hands writes: > Anthony Iliopoulos writes: > ... >> Yeap it is due to nrext64, I've submitted a patch to grub (should have >> cc'ed linux-xfs..) >> >> https://lore.kernel.org/grub-devel/20231026095339.31802-1-ail...@suse.com/ > > That certainly seems to fix this bug. ... but sadly that may not be the end of the story. I've persuaded D-I to use the patched grub version, and when testing it, it now gets past the previous failure to complete the install, but then fails to boot after the first reboot, as seen here: https://openqa.debian.net/tests/200160#step/_console_wait_login/7 where it drops to the 'grub rescue>' prompt, complaining that: error: file `/boot/grub/i386-pc/normal.mod' not found. if one types `ls (hd0,msdos1)/boot/grub/i386-pc` at that rescue prompt, it lists the files up to msdospart.mod and then says: error: invalid XFS directory entry. (BTW the directory seemed fine before the reboot, because I listed it) This makes me wonder: Could it be that the code within the grub components that get installed onto the disk also needs to be patched to understand the newer directory structure, and without that it is unable to read the whole directory, and thus fails to boot it? Cheers, Phil. P.S. If you want to try this for yourself, the test image used (that pulls in the patched grub) is to be found here: https://salsa.debian.org/philh/grub2/-/jobs/4865564/artifacts/file/debian/output/debian-202306XX+ABI~6.5.0~3+salsaci+20231029+21-amd64-gtkmini.iso and adding `partman/default_filesystem=xfs` on the kernel command line before booting into D-I will get it to default to using XFS. -- Philip Hands -- https://hands.com/~phil signature.asc Description: PGP signature
Bug#1054507: marked as done (golang-github-weaveworks-promrus: FTBFS with "invalid memory address" if the machine is not very fast (?))
Your message dated Sun, 29 Oct 2023 19:49:51 +
with message-id
and subject line Bug#1054507: fixed in golang-github-weaveworks-promrus
1.2.0+git20210208.77c195c-3
has caused the Debian Bug report #1054507,
regarding golang-github-weaveworks-promrus: FTBFS with "invalid memory address"
if the machine is not very fast (?)
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.)
--
1054507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-weaveworks-promrus
Version: 1.2.0+git20210208.77c195c-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During an incremental rebuild of all packages in trixie, this package failed to
build:
=== RUN TestRegisteringHookMultipleTimesShouldBeSafe
promrus_test.go:103:
Error Trace:
/<>/_build/src/github.com/weaveworks/promrus/promrus_test.go:103
/<>/_build/src/github.com/weaveworks/promrus/promrus_test.go:29
Error: Expected nil, but got: {Op:"Get",
URL:"http://localhost:8080/metrics;, Err:(*net.OpError)(0xc25360)}
Test: TestRegisteringHookMultipleTimesShouldBeSafe
--- FAIL: TestRegisteringHookMultipleTimesShouldBeSafe (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference
[recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x8a91ea]
That's what I got in my autobuilders, but it's also the way it fails in
reproducible-builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-weaveworks-promrus.html
I've decided to report this as "serious" because of the "invalid memory address or
nil pointer dereference", which seems, well, quite serious.
To reproduce, I usually build the packages using machines with 1 CPU and 2 CPUs,
and in this case I've noticed that it fails a lot more on systems with 1 CPU,
so maybe this is enough to reproduce it:
taskset -c 0 dpkg-buildpackage -uc -us
In case that would not be enough, please contact me privately, as I would
be willing to offer a virtual machine where this happens 100% of the time.
Thanks.
--- End Message ---
--- Begin Message ---
Source: golang-github-weaveworks-promrus
Source-Version: 1.2.0+git20210208.77c195c-3
Done: Mathias Gibbens
We believe that the bug you reported is fixed in the latest version of
golang-github-weaveworks-promrus, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mathias Gibbens (supplier of updated
golang-github-weaveworks-promrus 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: Sun, 29 Oct 2023 19:15:49 +
Source: golang-github-weaveworks-promrus
Architecture: source
Version: 1.2.0+git20210208.77c195c-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team
Changed-By: Mathias Gibbens
Closes: 1054507
Changes:
golang-github-weaveworks-promrus (1.2.0+git20210208.77c195c-3) unstable;
urgency=medium
.
[ Daniel Swarbrick ]
* d/control: don't use transitional package names in dependencies
.
[ Mathias Gibbens ]
* Add a patch to fix a test failure on CPU-constrained systems (Closes:
#1054507)
Checksums-Sha1:
d5fd63f59e16ebf1c2272ca9b8d18c524e36cafd 2562
golang-github-weaveworks-promrus_1.2.0+git20210208.77c195c-3.dsc
b5f862244a538957854d85ec6539dfb37fa082ce 8654
golang-github-weaveworks-promrus_1.2.0+git20210208.77c195c.orig.tar.gz
2a3882fa0bf9da60cb3b944e3b275d58daffba19 2512
golang-github-weaveworks-promrus_1.2.0+git20210208.77c195c-3.debian.tar.xz
69d588553c033302963e6a424a252a10ab4e 8284
golang-github-weaveworks-promrus_1.2.0+git20210208.77c195c-3_amd64.buildinfo
Checksums-Sha256:
f418fe1df27d29827117529300c12fbc8826ee0b509d4af57fa747302a269b69 2562
golang-github-weaveworks-promrus_1.2.0+git20210208.77c195c-3.dsc
ae7048e1af7a4f6f247320db7b7d08f63a716253dfc18f4166d42bdfcc5b8ffc 8654
Bug#1042660: marked as done (votca: FTBFS with Sphinx 7.1, docutils 0.20: make[5]: *** [share/doc/CMakeFiles/doc.dir/build.make:81: share/doc/CMakeFiles/doc] Error 2)
Your message dated Sun, 29 Oct 2023 19:37:40 + with message-id and subject line Bug#1042660: fixed in votca 2022.1-2 has caused the Debian Bug report #1042660, regarding votca: FTBFS with Sphinx 7.1, docutils 0.20: make[5]: *** [share/doc/CMakeFiles/doc.dir/build.make:81: share/doc/CMakeFiles/doc] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: votca Version: 2022.1-1 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, votca fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[5]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 98%] Generating ../../sphinx/customLogo.png > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/cmake -E > copy_if_different /<>/share/doc/customLogo.png > /<>/obj-x86_64-linux-gnu/sphinx/customLogo.png > [ 98%] Generating ../../sphinx/Architecture.rst > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/cmake -E > copy_if_different /<>/share/doc/Architecture.rst > /<>/obj-x86_64-linux-gnu/sphinx/Architecture.rst > [ 98%] Generating ../../sphinx/CODE_OF_CONDUCT.rst > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/cmake -E > copy_if_different /<>/share/doc/CODE_OF_CONDUCT.rst > /<>/obj-x86_64-linux-gnu/sphinx/CODE_OF_CONDUCT.rst > [ 98%] Generating ../../sphinx/DEVELOPERS_GUIDE.rst > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/cmake -E > copy_if_different /<>/share/doc/DEVELOPERS_GUIDE.rst > /<>/obj-x86_64-linux-gnu/sphinx/DEVELOPERS_GUIDE.rst > [ 98%] Generating ../../sphinx/INSTALL.rst > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/cmake -E > copy_if_different /<>/share/doc/INSTALL.rst > /<>/obj-x86_64-linux-gnu/sphinx/INSTALL.rst > [ 98%] Generating ../../sphinx/VOTCA_LANGUAGE_GUIDE.rst > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/cmake -E > copy_if_different /<>/share/doc/VOTCA_LANGUAGE_GUIDE.rst > /<>/obj-x86_64-linux-gnu/sphinx/VOTCA_LANGUAGE_GUIDE.rst > [100%] Generating ../../sphinx/index.rst > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/cmake -E > copy_if_different /<>/share/doc/index.rst > /<>/obj-x86_64-linux-gnu/sphinx/index.rst > [100%] Generating ../../sphinx/websiteAndDocumentation.rst > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/cmake -E > copy_if_different /<>/share/doc/websiteAndDocumentation.rst > /<>/obj-x86_64-linux-gnu/sphinx/websiteAndDocumentation.rst > cd /<>/obj-x86_64-linux-gnu/share/doc && /usr/bin/sphinx-build > /<>/obj-x86_64-linux-gnu/sphinx > /<>/obj-x86_64-linux-gnu/sphinx.html > Running Sphinx v7.1.1 > making output directory... done > building [mo]: targets for 0 po files that are out of date > writing output... > building [html]: targets for 207 source files that are out of date > updating environment: [new config] 207 added, 0 changed, 0 removed > [2Kreading sources... [ 0%] Architecture > [2Kreading sources... [ 1%] CODE_OF_CONDUCT > [2Kreading sources... [ 1%] DEVELOPERS_GUIDE > [2Kreading sources... [ 2%] INSTALL > [2Kreading sources... [ 2%] VOTCA_LANGUAGE_GUIDE > [2Kreading sources... [ 3%] csg-tutorials/README > [2Kreading sources... [ 3%] csg/advanced_topics > [2Kreading sources... [ 4%] csg/bibliography > [2Kreading sources... [ 4%] csg/csg_boltzmann > [2Kreading sources... [ 5%] csg/csg_call > [2Kreading sources... [ 5%] csg/csg_defaults > [2Kreading sources... [ 6%] csg/csg_density > [2Kreading sources... [ 6%] csg/csg_dlptopol > [2Kreading sources... [ 7%] csg/csg_dump > [2Kreading sources... [ 7%] csg/csg_fluctuations > [2Kreading sources... [ 8%] csg/csg_fmatch > [2Kreading sources... [ 8%] csg/csg_gmxtopol > [2Kreading sources... [ 9%] csg/csg_imc_solve > [2Kreading sources... [ 9%] csg/csg_inverse > [2Kreading sources... [ 10%] csg/csg_map > [2Kreading sources... [ 10%] csg/csg_orientcorr > [2Kreading sources... [ 11%] csg/csg_part_dist > [2Kreading sources... [ 11%] csg/csg_partial_rdf > [2Kreading sources... [ 12%] csg/csg_property > [2Kreading sources... [ 12%] csg/csg_radii > [2Kreading sources... [ 13%] csg/csg_resample > [2Kreading sources... [ 13%] csg/csg_reupdate > [2Kreading sources... [ 14%] csg/csg_scripts > [2Kreading sources... [ 14%] csg/csg_sphericalorder > [2Kreading sources... [ 14%] csg/csg_stat > [2Kreading sources... [ 15%] csg/csg_table > [2Kreading sources... [ 15%] csg/csg_traj_force > [2Kreading sources... [
Bug#1052859: marked as done (geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2)
Your message dated Sun, 29 Oct 2023 18:50:29 +
with message-id
and subject line Bug#1052859: fixed in geonames 0.3.0-2
has caused the Debian Bug report #1052859,
regarding geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make
-j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geonames
Version: 0.3.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration from
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration from
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
> Start 1: test_geonames
>
> 1: Test command: /<>/obj-x86_64-linux-gnu/tests/test_geonames
> 1: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 1: Test timeout computed to be: 1000
> 1: TAP version 13
> 1: # random seed: R02S845fe55aee887825f93218b66afea354
> 1: 1..4
> 1: ok 1 /common-cities
> 1: # slow test /common-cities executed in 0.59 secs
> 1: **
> 1: ERROR:./tests/test-geonames.c:110:assert_first_names: assertion failed
> (geonames_city_get_country (city) == expected_country): ("United States of
> America" == "\303\211tats Unis")
> 1: not ok /translations -
> ERROR:./tests/test-geonames.c:110:assert_first_names: assertion failed
> (geonames_city_get_country (city) == expected_country): ("United States of
> America" == "\303\211tats Unis")
> 1: Bail out!
> 1/1 Test #1: test_geonames Subprocess
> aborted***Exception: 1.17 sec
> TAP version 13
> # random seed: R02S845fe55aee887825f93218b66afea354
> 1..4
> ok 1 /common-cities
> # slow test /common-cities executed in 0.59 secs
> **
> ERROR:./tests/test-geonames.c:110:assert_first_names: assertion failed
> (geonames_city_get_country (city) == expected_country): ("United States of
> America" == "\303\211tats Unis")
> not ok /translations - ERROR:./tests/test-geonames.c:110:assert_first_names:
> assertion failed (geonames_city_get_country (city) == expected_country):
> ("United States of America" == "\303\211tats Unis")
> Bail out!
>
>
> 0% tests passed, 1 tests failed out of 1
>
> Total Test time (real) = 1.17 sec
>
> The following tests FAILED:
> 1 - test_geonames (Subprocess aborted)
> Errors while running CTest
> make[2]: *** [Makefile:74: test] Error 8
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test
> ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/geonames_0.3.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: geonames
Source-Version: 0.3.0-2
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
geonames, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Processed: Bug#1052859 marked as pending in geonames
Processing control commands: > tag -1 pending Bug #1052859 [src:geonames] geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 1052859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052859: marked as pending in geonames
Control: tag -1 pending Hello, Bug #1052859 in geonames 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/ubports-team/geonames/-/commit/0c974e58f3860bb49a4c5a4a8e31c5a2a067e474 debian/rules: Run unit tests with LC_ALL=en_US.UTF-8. (Closes: #1052859). (this message was generated automatically) -- Greetings https://bugs.debian.org/1052859
Processed: bug 1055021 is forwarded to https://lore.kernel.org/linux-mips/20231026111715.1281728-1-jiaxun.y...@flygoat.com/
Processing commands for cont...@bugs.debian.org: > forwarded 1055021 > https://lore.kernel.org/linux-mips/20231026111715.1281728-1-jiaxun.y...@flygoat.com/ Bug #1055021 [src:linux] linux: mips64el loongson3 kernel crashes when running cmake Set Bug forwarded-to-address to 'https://lore.kernel.org/linux-mips/20231026111715.1281728-1-jiaxun.y...@flygoat.com/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042643: marked as done (libtext-markup-perl: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 1)
Your message dated Sun, 29 Oct 2023 17:35:07 + with message-id and subject line Bug#1042643: fixed in libtext-markup-perl 0.24-2 has caused the Debian Bug report #1042643, regarding libtext-markup-perl: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 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.) -- 1042643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtext-markup-perl Version: 0.24-1 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, libtext-markup-perl fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > /usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config > "ld=x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" > Checking prerequisites... > recommends: > * Test::Pod is not installed > * Test::Pod::Coverage is not installed > > ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions > of the modules indicated above before proceeding with this installation > > Run 'Build installdeps' to install missing prerequisites. > > Created MYMETA.yml and MYMETA.json > Creating new 'Build' script for 'Text-Markup' version '0.24' >dh_auto_build > /usr/bin/perl Build > Building Text-Markup >dh_auto_test > /usr/bin/perl Build test --verbose 1 > t/base.t . > 1..38 > ok 1 - use Text::Markup; > ok 2 - Text::Markup->can(...) > ok 3 - Should have core formats > ok 4 - Get format matchers > ok 5 - Should have core format matchers > ok 6 - '(?^:p(?:od|m|l))' isa 'Regexp' > ok 7 - '(?^:textile)' isa 'Regexp' > ok 8 - '(?^:x?html?)' isa 'Regexp' > ok 9 - '(?^:(?:m(?:edia)?)?wiki)' isa 'Regexp' > ok 10 - '(?^:m(?:d(?:own)?|kdn?|arkdown))' isa 'Regexp' > ok 11 - '(?^:tra?c)' isa 'Regexp' > ok 12 - '(?^:re?st)' isa 'Regexp' > ok 13 - '(?^:a(?:sc(?:iidoc)?|doc)?)' isa 'Regexp' > ok 14 - '(?^:bb(?:code)?)' isa 'Regexp' > ok 15 - '(?^:mm(?:d(?:own)?|kdn?|arkdown))' isa 'Regexp' > ok 16 - '(?^:creole)' isa 'Regexp' > ok 17 - Should be now have the "cool" parser > ok 18 - An object of class 'Text::Markup' isa 'Text::Markup' > ok 19 - Should have no default format > ok 20 - An object of class 'Text::Markup' isa 'Text::Markup' > ok 21 - Should have default format > ok 22 - Should be able to find specific parser > ok 23 - Should be able to find default format parser > ok 24 - Should be find the specified default parser > ok 25 - Should be able to guess the parser file the file name > ok 26 - Should guess "cool" format file "foo.cool" > ok 27 - Should not guess "cool" format file "foocool" > ok 28 - Should not guess "cool" format file "foo.cool.txt" > ok 29 - Should be now have the "cool" and "funky" parsers > ok 30 - Should still guess "cool" format file "foo.cool" > ok 31 - Should guess "funky" format file "foo.funky" > ok 32 - Should guess "funky" format file "foo.funky.txt" > ok 33 - Test the "cool" parser > ok 34 - Test the "funky" parser > ok 35 - Test the "cool" parser with options > ok 36 - Test pod option to suppress HTML header > ok 37 - Test pod options to suppress HTML header and footer > ok 38 - Test the "none" parser > ok > > # Failed test 'Parse rest file' > # at t/formats.t line 52. > # got: ' > # "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;> > # http://www.w3.org/1999/xhtml; xml:lang="en" lang="en"> > # > # > # I am a reST document > # > # > # > # > # I am a reST document > # And I am its > subtitle > # > # href="http://docutils.sourceforge.net/;>Rest allows inline > style and other stuff, > # but I guess this code is enough. > # > # unknown: arg1 arg2 class="literal-block"> > # We also support unknown directive, so that no content is lost if reST > # specialization is parsed. > # > # > # > # Of course we may also find new > roles. > # > # module: mymodule This is a module that > doesn't exist > # > # function: foo() In Sphinx documentation > you could find this stuff. >
Processed: Bug#1042643 marked as pending in libtext-markup-perl
Processing control commands: > tag -1 pending Bug #1042643 [src:libtext-markup-perl] libtext-markup-perl: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 1 Added tag(s) pending. -- 1042643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042643: marked as pending in libtext-markup-perl
Control: tag -1 pending Hello, Bug #1042643 in libtext-markup-perl 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/perl-team/modules/packages/libtext-markup-perl/-/commit/6635a51c65f8e1baad27a543d2ea4b58f9f6926a Cherry-pick upstream commit to fix test with docutils 0.20. Closes: #1042643 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042643
Bug#1055023: marked as done (FTBFS: libpoe-component-client-dns-perl requires DNS during tests.)
Your message dated Sun, 29 Oct 2023 17:19:28 + with message-id and subject line Bug#1055023: fixed in libpoe-component-client-dns-perl 1:1.054-4 has caused the Debian Bug report #1055023, regarding FTBFS: libpoe-component-client-dns-perl requires DNS during tests. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpoe-component-client-dns-perl Severity: serious Version: 1:1.054-3 While rebuilding debian trixie in a network-restricted environment, we ran into this build error (using sbuild): Can't call method "rdstring" on an undefined value at t/06_hosts.t line 143. # Looks like your test exited with 22 just after 1. The problem is likely that DNS does work to some degree (it can resolve some hosts, I'm not sure what the exact response is on other hosts). The test at https://sources.debian.org/src/libpoe-component-client-dns-perl/1%3A1.054-3/t/06_hosts.t/#L14 isn't a sufficient precaution to work around the Debian Policy *requirement* that required build targets *must* *not* *use* network resources that weren't created by the build processes themselves. The test itself is already using network resources it hasn't created itself. Please disable this test or ensure that it's not using external resolvers. Kind regards, Sven --- End Message --- --- Begin Message --- Source: libpoe-component-client-dns-perl Source-Version: 1:1.054-4 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libpoe-component-client-dns-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libpoe-component-client-dns-perl 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: Sun, 29 Oct 2023 17:57:28 +0100 Source: libpoe-component-client-dns-perl Architecture: source Version: 1:1.054-4 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1055023 Changes: libpoe-component-client-dns-perl (1:1.054-4) unstable; urgency=medium . * Disable querying of external nameservers during build tests. Set RES_NAMESERVERS and RES_OPTIONS in debian/rules, additionally patch t/05_api_4.t, which has nameservers hardcoded, to honour NO_NETWORK_TESTING. Thanks to Sven Mueller for the bug report. (Closes: #1055023) * debian/copyright: remove Upstream-Author field. Checksums-Sha1: f86fb258450d400fa0a98aad1a66a7f58c895319 2728 libpoe-component-client-dns-perl_1.054-4.dsc a70dc3e0a6a7ca873c364ba8bd54ec93100bee52 5884 libpoe-component-client-dns-perl_1.054-4.debian.tar.xz Checksums-Sha256: d0a8e1aa2aee6b768672d1e4f879f2127a02e51070cb5195e431e4489a0e7a82 2728 libpoe-component-client-dns-perl_1.054-4.dsc c7e9b43b9e58bfa4cc016aca0ef564a851f3c220f5325cd11dc27eb83c8b97ec 5884 libpoe-component-client-dns-perl_1.054-4.debian.tar.xz Files: f293f76433e52c12466a92051e6c22e0 2728 perl optional libpoe-component-client-dns-perl_1.054-4.dsc c00e94a7fda1c5cffbf5225cb3700342 5884 perl optional libpoe-component-client-dns-perl_1.054-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmU+kAhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZm5Q/+KoZXKEOScDF5rLIr7IXQEDDuNcch8M9vGgGQ/4IWTPfMquCwSk2ideFa IooB6m/yyW88BYpveeFWCJHH4XcEcSb0sue5O+QQ6IcejH4aQuSc/21cxjRR7BAP RT4qPa25iQg7LJPMjsAUHS/SFG5SdRjxs1gtfJBrEQZ0w3g9KCxuu66AQq6CsQxv IFSKymRL62KZSU7vBQBgL+IgKIUrAgzwJSPnCG6fPh44Fw27iAN4TZ6Aq8j25Ni/ kNmX7k5oy2qBbKpfabk+ywOYhCo9SaGhoo1duhZ229ljSdCIL98x/g3c+d5prqET dDymfrMAtewC5iZX9vqTAMNhvBZsBmvXxvXlk58UtSSO8dX/9zLmDSaDFIfLubB0 sJsPTCbPYnUc+jsHJ0RGVaP+e06efTOAVyoBPyF8gXvZCaYIbNqWb9xEqxtEG4UU ikfMltJtAdGmpNX2x3Lb+ZbPxRj/FSH5lEEypL3blf0yButHjT+94oFnB/WUA95e EiqrUoDkLiqc2qDBqiTJja5yGmxdDqYoNFxJPtn0pRA4tDoV68skoAJx/kHj+Yh3
Bug#958682: node-jsonld: Remove dependency to node-request
On Fri, 31 Dec 2021 13:17:07 +0100 Yadd wrote: Hi, updating node-jsonld is enough to fix this issue: Hi Jonas, Are you planning to update node-jsonld? Else we can simply remove this package from Debian since it seems useless (no reverse dependencies). This is blocking removal of deprecated node-request. OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#958692: node-matrix-js-sdk: Remove dependency to node-request
On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote: Upstream has deprecated node-request: https://github.com/request/request/issues/3142 It can be replaced by node-got Hi Jonas, Hubert, Are you planning to update matrix-js-sdk? We'd like to remove deprecated node-request from the archive and this package is a blocker. thanks Praveen OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1002901: node-request-capture-har is a wrapper around deprecated node-request
On Fri, 31 Dec 2021 13:02:44 +0100 Yadd wrote: Package: node-request-capture-har Version: 1.2.2-2 Severity: serious Tags: upstream security Justification: security X-Debbugs-Cc: Debian Security Team node-request-capture-har is usable only as a wrapper around deprecated node-request. Then it should be removed from Debian bookstorm. yarnpkg 4.x in experimental no longer depends on this package. So once we reupload that to unstable, we can file rm request for this package. We are pretty close to the unstable reupload https://lists.debian.org/debian-js/2023/10/msg00080.html OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Processed: Bug#1055023 marked as pending in libpoe-component-client-dns-perl
Processing control commands: > tag -1 pending Bug #1055023 [libpoe-component-client-dns-perl] FTBFS: libpoe-component-client-dns-perl requires DNS during tests. Added tag(s) pending. -- 1055023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055023: marked as pending in libpoe-component-client-dns-perl
Control: tag -1 pending Hello, Bug #1055023 in libpoe-component-client-dns-perl 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/perl-team/modules/packages/libpoe-component-client-dns-perl/-/commit/6333e4667475957119aae4e7bdc68b87e4c16f75 Disable querying of external nameservers during build tests. Set RES_NAMESERVERS and RES_OPTIONS in debian/rules, additionally patch t/05_api_4.t, which has nameservers hardcoded, to honour NO_NETWORK_TESTING. Thanks: Sven Mueller for the bug report. Closes: #1055023 (this message was generated automatically) -- Greetings https://bugs.debian.org/1055023
Bug#1020507: marked as done (libcleri breaks siridb-server autopkgtest, siridb-server rebuild "fixes" the issue)
Your message dated Sun, 29 Oct 2023 16:19:23 +
with message-id
and subject line Bug#1020507: fixed in libcleri 1.0.1-2
has caused the Debian Bug report #1020507,
regarding libcleri breaks siridb-server autopkgtest, siridb-server rebuild
"fixes" the issue
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.)
--
1020507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcleri
Control: found -1 libcleri/1.0.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks
Dear maintainer(s),
With a recent upload of libcleri the autopkgtest of siridb-server fails
in testing when that autopkgtest is run with the binary packages of
libcleri from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
libcleri from testing1.0.0-1
siridb-server from testing2.0.48-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. The test hangs
until the 2:47 hour timeout kills the test. I tried to run the
autopgktest with a rebuild of siridb-server, and that passes quickly.
So, this hints at an ABI breakage. The failures *looks* very much like
the libuv failure of some weeks ago.
Currently this regression is blocking the migration of libcleri to
testing [1]. Can you please investigate the situation?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=libcleri
https://ci.debian.net/data/autopkgtest/testing/amd64/s/siridb-server/26309651/log.gz
autopkgtest [19:27:49]: test http-api: [---
* fixing /etc/siridb/siridb.conf
* restarting siridb-server
* run queries
get-version
["2.0.48"]
new-database
"OK"
new-account
"OK"
change-password
"OK"
drop-account
"OK"
drop-database
"OK"
drop-database again
{"error_msg":"cannot find database 'sampledb'"}
get-accounts
["sa"]
new-database for queries
"OK"
get-databases
["sampledb"]
query data (nothing there)
autopkgtest [22:14:29]: ERROR: timed out on command "su -s /bin/bash
root -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true; . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.9z7k06kk/downtmp/build.AuZ/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.9z7k06kk/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.9z7k06kk/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=64; unset
LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY
LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export
AUTOPKGTEST_NORMAL_USER=debci; export ADT_NORMAL_USER=debci; chmod +x
/tmp/autopkgtest-lxc.9z7k06kk/downtmp/build.AuZ/src/debian/tests/http-api;
touch /tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-stdout
/tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-stderr;
/tmp/autopkgtest-lxc.9z7k06kk/downtmp/build.AuZ/src/debian/tests/http-api
2> >(tee -a /tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-stderr >&2) >
>(tee -a /tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-stdout);"
(kind: test)
autopkgtest [22:14:29]: test http-api: ---]
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libcleri
Source-Version: 1.0.1-2
Done: Paul Gevers
We believe that the bug you reported is fixed in the latest version of
libcleri, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Paul Gevers (supplier of updated libcleri package)
(This message was
Bug#1052915: libdnf: FTBFS: dh_install: error: missing files, aborting
Control: tags -1 pending On Tue, 26 Sep 2023 15:28:47 +0200 Lucas Nussbaum wrote: > Source: libdnf > Version: 0.69.0-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230925 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[3]: Entering directory '/<>/build' > > make[3]: Nothing to be done for 'preinstall'. > > make[3]: Leaving directory '/<>/build' > > Install the project... > > /usr/bin/cmake -P cmake_install.cmake > > -- Install configuration: "None" > > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/pkgconfig/libdnf.pc > > -- Installing: /<>/debian/tmp/usr/include/libdnf/config.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/log.hpp > > -- Installing: /<>/debian/tmp/usr/include/libdnf/nevra.hpp > > -- Installing: /<>/debian/tmp/usr/include/libdnf/nsvcap.hpp > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- advisory.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- advisorypkg.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- advisoryref.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- db.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- conf.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- context.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- enums.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- goal.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- keyring.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- lock.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- package.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- packagedelta.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- repo-loader.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- rpmts.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- sack.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- reldep.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- reldep-list.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- repo.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- state.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- transaction.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- types.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- utils.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf- version.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/libdnf.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- goal.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- nevra.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- package.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- packageset.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- query.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- repo.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- selector.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- subject.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- types.h > > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy- util.h Uploaded NMU to DELAYED/5 fixing this issue with the attached debdiff. -- Kind regards, Luca Boccassi diff -Nru libdnf-0.69.0/debian/changelog libdnf-0.69.0/debian/changelog --- libdnf-0.69.0/debian/changelog 2023-01-08 09:08:51.0 + +++ libdnf-0.69.0/debian/changelog 2023-10-29 15:57:28.0 + @@ -1,3 +1,10 @@ +libdnf (0.69.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Move python3 modules from /usr/lib/local/ (Closes: #1052915) + + -- Luca Boccassi Sun, 29 Oct 2023 15:57:28 + + libdnf (0.69.0-2) unstable; urgency=medium * Set myself to maintainer diff -Nru libdnf-0.69.0/debian/python3-hawkey.install libdnf-0.69.0/debian/python3-hawkey.install --- libdnf-0.69.0/debian/python3-hawkey.install 2022-11-12 22:06:07.0 + +++ libdnf-0.69.0/debian/python3-hawkey.install 2023-10-29 15:53:24.0 + @@ -1 +1 @@ -usr/local/lib/python3.*/dist-packages/hawkey +usr/lib/python3/dist-packages/hawkey diff -Nru libdnf-0.69.0/debian/python3-libdnf.install libdnf-0.69.0/debian/python3-libdnf.install --- libdnf-0.69.0/debian/python3-libdnf.install 2022-11-12 22:06:07.0 + +++ libdnf-0.69.0/debian/python3-libdnf.install 2023-10-29 15:53:37.0 + @@ -1 +1 @@ -usr/local/lib/python3.*/dist-packages/libdnf +usr/lib/python3/dist-packages/libdnf signature.asc Description: This is a digitally signed message part
Processed: Re: libdnf: FTBFS: dh_install: error: missing files, aborting
Processing control commands: > tags -1 pending Bug #1052915 [src:libdnf] libdnf: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 1052915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052911: librepo: FTBFS: dh_install: error: missing files, aborting
Control: tags -1 pending On Tue, 26 Sep 2023 15:28:51 +0200 Lucas Nussbaum wrote: > Source: librepo > Version: 1.14.5-3 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230925 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[3]: Entering directory '/<>/build' > > make[3]: Nothing to be done for 'preinstall'. > > make[3]: Leaving directory '/<>/build' > > Install the project... > > /usr/bin/cmake -P cmake_install.cmake > > -- Install configuration: "None" > > -- Installing: /<>/debian/tmp/usr/include/librepo/checksum.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/fastestmirror.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/gpg.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/handle.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/librepo.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/metadata_downloader.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/metalink.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/mirrorlist.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/package_downloader.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/rcodes.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/repoconf.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/repomd.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/repoutil_yum.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/result.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/types.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/url_substitution.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/util.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/version.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/xmlparser.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/yum.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/downloader.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/downloader_internal.h > > -- Installing: /<>/debian/tmp/usr/include/librepo/downloadtarget.h > > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/librepo.so.0 > > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/librepo.so > > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/pkgconfig/librepo.pc > > -- Installing: /<>/debian/tmp/usr/lib/python3/dist- packages/librepo/__init__.py > > -- Installing: /<>/debian/tmp/usr/lib/python3/dist- packages/librepo/_librepo.so > > make[2]: Leaving directory '/<>/build' > > # Use system-provides files. > > rm -fv 'build/doc/python/_static/jquery.js' \ > > 'build/doc/python/_static/underscore.js' \ > > 'build/doc/c/html/jquery.js' \ > > 'build/doc/python/_static/doctools.js' \ > > 'build/doc/python/_static/language_data.js' \ > > 'build/doc/python/_static/searchtools.js' > > removed 'build/doc/python/_static/jquery.js' > > removed 'build/doc/python/_static/underscore.js' > > removed 'build/doc/c/html/jquery.js' Uploaded NMU to DELAYED/5 fixing this issue with the attached debdiff. -- Kind regards, Luca Boccassi diff -Nru librepo-1.14.5/debian/changelog librepo-1.14.5/debian/changelog --- librepo-1.14.5/debian/changelog 2023-01-10 08:23:24.0 + +++ librepo-1.14.5/debian/changelog 2023-10-29 15:42:43.0 + @@ -1,3 +1,10 @@ +librepo (1.14.5-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Move python3 modules from /usr/lib/local/ (Closes: #1052911) + + -- Luca Boccassi Sun, 29 Oct 2023 15:42:43 + + librepo (1.14.5-3) unstable; urgency=medium * Update patch for test_yum_package_downloading.py thanks to diff -Nru librepo-1.14.5/debian/python3-librepo.install librepo-1.14.5/debian/python3-librepo.install --- librepo-1.14.5/debian/python3-librepo.install 2022-11-13 08:26:30.0 + +++ librepo-1.14.5/debian/python3-librepo.install 2023-10-29 15:42:22.0 + @@ -1 +1 @@ -usr/local/lib/python3.* +usr/lib/python3 signature.asc Description: This is a digitally signed message part
Processed: Re: librepo: FTBFS: dh_install: error: missing files, aborting
Processing control commands: > tags -1 pending Bug #1052911 [src:librepo] librepo: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 1052911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052913: libcomps: FTBFS: dh_install: error: missing files, aborting
Control: tags -1 pending On Tue, 26 Sep 2023 15:28:41 +0200 Lucas Nussbaum wrote: > Source: libcomps > Version: 0.1.19-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230925 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[3]: Entering directory '/<>/build' > > make[3]: Nothing to be done for 'preinstall'. > > make[3]: Leaving directory '/<>/build' > > Install the project... > > /usr/bin/cmake -P cmake_install.cmake > > -- Install configuration: "None" > > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/libcomps.so.0 > > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/libcomps.so > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_doc.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_docgroup.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_doccategory.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_docenv.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_docpackage.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_docgroupid.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_obj.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_mm.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_hslist.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_dict.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_objradix.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_objmradix.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_objdict.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_objlist.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_elem.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_radix.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_mradix.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_bradix.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_set.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_parse.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_log.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_default.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_utils.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_validate.h > > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_log_codes.h > > -- Up-to-date: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/libcomps.so.0 > > -- Up-to-date: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/libcomps.so > > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/pkgconfig/libcomps.pc > > -- Up-to-date: /<>/debian/tmp/usr/lib/x86_64-linux- gnu/pkgconfig/libcomps.pc > > -- Installing: /<>/debian/tmp/usr/lib/python3/dist- packages/libcomps/__init__.py > > -- Installing: /<>/debian/tmp/usr/lib/python3/dist- packages/libcomps/_libpycomps.so > > running install_egg_info > > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. > > !! Uploaded NMU to DELAYED/5 fixing this issue with the attached debdiff. -- Kind regards, Luca Boccassi diff -Nru libcomps-0.1.19/debian/changelog libcomps-0.1.19/debian/changelog --- libcomps-0.1.19/debian/changelog 2023-01-07 19:04:37.0 + +++ libcomps-0.1.19/debian/changelog 2023-10-29 15:32:45.0 + @@ -1,3 +1,10 @@ +libcomps (0.1.19-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Move python3 modules from /usr/lib/local/ (Closes: #1052913) + + -- Luca Boccassi Sun, 29 Oct 2023 15:32:45 + + libcomps (0.1.19-2) unstable; urgency=medium * Set myself to maintainer. diff -Nru libcomps-0.1.19/debian/python3-libcomps.install libcomps-0.1.19/debian/python3-libcomps.install --- libcomps-0.1.19/debian/python3-libcomps.install 2022-11-13 08:29:48.0 + +++ libcomps-0.1.19/debian/python3-libcomps.install 2023-10-29 15:31:40.0 + @@ -1 +1 @@ -usr/local/lib/python3.* +usr/lib/python3* signature.asc Description: This is a digitally signed message part
Processed: Re: libcomps: FTBFS: dh_install: error: missing files, aborting
Processing control commands: > tags -1 pending Bug #1052913 [src:libcomps] libcomps: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 1052913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037395: marked as done (mediascanner2: build-depends on transitional package libgdk-pixbuf2.0-dev)
Your message dated Sun, 29 Oct 2023 15:34:40 + with message-id and subject line Bug#1037395: fixed in mediascanner2 0.115-4 has caused the Debian Bug report #1037395, regarding mediascanner2: build-depends on transitional package libgdk-pixbuf2.0-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mediascanner2 Version: 0.115-3 Severity: important Tags: trixie sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: split-gdk-pixbuf This package Build-Depends on libgdk-pixbuf2.0-dev. In Debian 11, libgdk-pixbuf2.0-dev was split into two packages: - libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library - libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained Xlib integration layer, gdk-pixbuf-xlib-2.0 If this package only requires functionality from gdk-pixbuf-2.0.pc and , please update the build-dependency to libgdk-pixbuf-2.0-dev. If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and (unlikely), then you can also build-depend on libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove that requirement. libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative dependency, even for packages that are expected to be backported. We should remove the libgdk-pixbuf2.0-dev transitional package during the Debian 13 'trixie' cycle, so this bug is likely to become RC later. Thanks, smcv --- End Message --- --- Begin Message --- Source: mediascanner2 Source-Version: 0.115-4 Done: Marius Gripsgard We believe that the bug you reported is fixed in the latest version of mediascanner2, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marius Gripsgard (supplier of updated mediascanner2 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: Sun, 29 Oct 2023 16:14:15 +0100 Source: mediascanner2 Architecture: source Version: 0.115-4 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Marius Gripsgard Closes: 1037395 Changes: mediascanner2 (0.115-4) unstable; urgency=medium . * d/control: Use my debian email * d/control: replace B-D libgdk-pixbuf2.0-dev with libgdk-pixbuf-2.0-dev (closes: #1037395) Checksums-Sha1: 58205e405c179b8113b242630e5fd4ebffbeee4f 2247 mediascanner2_0.115-4.dsc 3b5cf4ccaf3a4c53ad1fbd2d045233125499a02d 383156 mediascanner2_0.115.orig.tar.gz 945f524b58441373a73c846b8816fe6d71e010fc 7124 mediascanner2_0.115-4.debian.tar.xz 6bb9a4b6ff281bd9c32b75a04ec02b9c92d8a9b7 17058 mediascanner2_0.115-4_source.buildinfo Checksums-Sha256: 38f8479844b40158af3d8ebdb9b5e7733680b6f1d2c8bf2b60b8d12752e824d8 2247 mediascanner2_0.115-4.dsc 5a4bd7dc493b66cf31a36fc2e8221d52bf05240dc621d4751dc12d9edd2df472 383156 mediascanner2_0.115.orig.tar.gz fdfa47eba3eb83d709a569aa8b723b93940a8a43f274fedf5aba656e9a319fdf 7124 mediascanner2_0.115-4.debian.tar.xz 2992fe47bd8bcd7fbe3956b28ad444d52f900e9d0cfdb8266c800defedd07570 17058 mediascanner2_0.115-4_source.buildinfo Files: 395c65e60464a21d89f6387da8e9594f 2247 libs optional mediascanner2_0.115-4.dsc 3df8baade7d2fd7388b7e72e9a239922 383156 libs optional mediascanner2_0.115.orig.tar.gz e837fc7c9fd4be3810494430b97c4556 7124 libs optional mediascanner2_0.115-4.debian.tar.xz 1648552e08dda16bcffd043cbe8b1ca8 17058 libs optional mediascanner2_0.115-4_source.buildinfo -BEGIN PGP SIGNATURE- iIsEARYIADMWIQT0KegCiCm6mh1JH2jwqyDIdgBMKgUCZT53IBUcbWFyaW9ncmlw QGRlYmlhbi5vcmcACgkQ8KsgyHYATCryDwEAxcpUIQS3X1WQFLSaGfhJ5m+a63lo MHxcE/wGRIbiGFYBAK+DicWiXrkBUdG9b9VBJLga7jXdYOXcr6bWGhqN05MK =ifnA -END PGP SIGNATURE End Message ---
Bug#1054788: marked as done (libseccomp: FTBFS: dh_install: error: missing files, aborting)
Your message dated Sun, 29 Oct 2023 15:19:05 + with message-id and subject line Bug#1054788: fixed in libseccomp 2.5.4-2 has caused the Debian Bug report #1054788, regarding libseccomp: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libseccomp Version: 2.5.4-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/src/python' > VERSION_RELEASE="2.5.4" CPPFLAGS="-I\../../include -I../../include > -I../../include -Wdate-time -D_FORTIFY_SOURCE=2" CFLAGS="-Wall -Umips -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection" > LDFLAGS="-Wl,-z -Wl,relro -Wl,-z,relro" python3.11 ./setup.py install > --install-lib=/<>/debian/tmp//usr/lib/python3.11/site-packages \ > > --record=/<>/debian/tmp//usr/lib/python3.11/site-packages/install_files.txt > make[3]: Nothing to be done for 'install-data-am'. > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > EasyInstallDeprecationWarning: easy_install command is deprecated. > !! > > > > Please avoid running ``setup.py`` and ``easy_install``. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://github.com/pypa/setuptools/issues/917 for details. > > > > !! > self.initialize_options() > TEST FAILED: /<>/debian/tmp//usr/lib/python3.11/site-packages/ > does NOT support .pth files > bad install directory or PYTHONPATH > > You are attempting to install a package to a directory that is not > on PYTHONPATH and which Python does not read ".pth" files from. The > installation directory you specified (via --install-dir, --prefix, or > the distutils default setting) was: > > /<>/debian/tmp//usr/lib/python3.11/site-packages/ > > and your PYTHONPATH environment variable currently contains: > > '' > > Here are some of your options for correcting the problem: > > * You can choose a different installation directory, i.e., one that is > on PYTHONPATH or supports .pth files > > * You can add the installation directory to the PYTHONPATH environment > variable. (It must then also be on PYTHONPATH whenever you run > Python and want to use the package(s) you are installing.) > > * You can set up the installation directory to support ".pth" files by > using one of the approaches described here: > > > https://setuptools.pypa.io/en/latest/deprecated/easy_install.html#custom-installation-locations > > > Please make the appropriate changes for your system and try again. > zip_safe flag not set; analyzing archive contents... > __pycache__.seccomp.cpython-311: module references __file__ > make[3]: Leaving directory '/<>/src/python' > make[2]: Leaving directory '/<>/src/python' > make[1]: Leaving directory '/<>' >dh_install > dh_install: warning: Cannot find (any matches for) > "usr/lib/python3.*/site-packages/seccomp.cpython-*.so" (tried in ., > debian/tmp) > > dh_install: warning: python3-seccomp missing files: > usr/lib/python3.*/site-packages/seccomp.cpython-*.so > dh_install: error: missing files, aborting > make: *** [debian/rules:14: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/10/27/libseccomp_2.5.4-1_unstable.log All bugs filed during this archive rebuild are listed at:
Bug#1054536: marked as done (cyrus-sasl2 FTBFS: sphinx failure: AttributeError("'str' object has no attribute 'attributes'"))
Your message dated Sun, 29 Oct 2023 16:14:57 +0100
with message-id
and subject line Re: Bug#1054536: cyrus-sasl2 FTBFS: sphinx failure:
AttributeError("'str' object has no attribute 'attributes'")
has caused the Debian Bug report #1054536,
regarding cyrus-sasl2 FTBFS: sphinx failure: AttributeError("'str' object has
no attribute 'attributes'")
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.)
--
1054536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-sasl2
Version: 2.1.28+dfsg1-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
cyrus-sasl2 fails to build from source in unstable. A non-parallel build
ends as follows:
| /usr/bin/sphinx-build -d docsrc/.doctrees -n -q -D today=2023-08-03 -b html
./docsrc ./doc/html
| WARNING: extlinks: Sphinx-6.0 will require a caption string to contain
exactly one '%s' and all other '%' need to be escaped as '%%'.
| WARNING: extlinks: Sphinx-6.0 will require a caption string to contain
exactly one '%s' and all other '%' need to be escaped as '%%'.
|
| Theme error:
| An error happened in rendering the page developer.
| Reason: AttributeError("'str' object has no attribute 'attributes'")
| make[2]: *** [Makefile:1165: doc/html/.sphinx-build.stamp] Error 2
| make[2]: Leaving directory '/<>/build-mit'
| dh_auto_build: error: cd build-mit && make -j1
sasldir=/usr/lib/x86_64-linux-gnu/sasl2 all doc-html returned exit code 2
| make[1]: *** [debian/rules:166: override_dh_auto_build] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:127: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I don't quit see the cause of this failure just yet, maybe someone else
does?
Helmut
--- End Message ---
--- Begin Message ---
Version: sphinx-rtd-theme/2.0.0~rc3+dfsg-2--- End Message ---
Bug#1054874: marked as done (openimageio: CVE-2023-42295)
Your message dated Sun, 29 Oct 2023 15:05:44 + with message-id and subject line Bug#1054873: fixed in openimageio 2.4.16.0+dfsg-1 has caused the Debian Bug report #1054873, regarding openimageio: CVE-2023-42295 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.) -- 1054873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openimageio Version: 2.4.14.0+dfsg-1 Tags: security upstream Justification: user security hole Forwarded: https://github.com/AcademySoftwareFoundation/OpenImageIO/issues/3947 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for openimageio. CVE-2023-42295[0]: | An issue in OpenImageIO oiio v.2.4.12.0 allows a remote attacker to | execute arbitrary code and cause a denial of service via the | read_rle_image function of file bifs/unquantize.c If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-42295 https://www.cve.org/CVERecord?id=CVE-2023-42295 [1] https://github.com/AcademySoftwareFoundation/OpenImageIO/issues/3947 [2] https://github.com/AcademySoftwareFoundation/OpenImageIO/commit/672ed4c445ebefd5581974c27e28ef717fb6c401 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: openimageio Source-Version: 2.4.16.0+dfsg-1 Done: Matteo F. Vescovi We believe that the bug you reported is fixed in the latest version of openimageio, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated openimageio 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: Sun, 29 Oct 2023 14:50:00 +0100 Source: openimageio Architecture: source Version: 2.4.16.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Matteo F. Vescovi Closes: 1054873 Changes: openimageio (2.4.16.0+dfsg-1) unstable; urgency=medium . * New upstream release (Closes: #1054873) * debian/watch: upstream URL updated Checksums-Sha1: c3613b839cf2d6e45494b6a1f81a214364d9fde6 2996 openimageio_2.4.16.0+dfsg-1.dsc 4c1aebb0a9f6a005d809acb20507920e3e5fd34d 40379252 openimageio_2.4.16.0+dfsg.orig.tar.xz 94b1ea966c6b41c25dd4845fcde3953e77494796 17912 openimageio_2.4.16.0+dfsg-1.debian.tar.xz ebe3ad02bddfef2cef51da0e1bcf098fb26634ba 7762 openimageio_2.4.16.0+dfsg-1_source.buildinfo Checksums-Sha256: 285f51811a42a781491d90189f59f6948c6dc6b811ab67e5f583eaa9dab6d708 2996 openimageio_2.4.16.0+dfsg-1.dsc b4ead8843afb10b8a166eacf3902c7abd71902e0b02f9b0ad004a7347e90dbed 40379252 openimageio_2.4.16.0+dfsg.orig.tar.xz c5f8f117a84e7da2bbba952699511ff6a1816d19a746f580c9466abb971d7982 17912 openimageio_2.4.16.0+dfsg-1.debian.tar.xz 973f8409de7d09b8e06b4391f707a0a743a94ceeb758e95957e279869934d2af 7762 openimageio_2.4.16.0+dfsg-1_source.buildinfo Files: b6fed27516b8bd5cbd7a641120c16f4c 2996 libs optional openimageio_2.4.16.0+dfsg-1.dsc b245de04c2e2f6e4634455613a9ab699 40379252 libs optional openimageio_2.4.16.0+dfsg.orig.tar.xz 49c11b451bf4b4f5b49d7ccd8c6e7a51 17912 libs optional openimageio_2.4.16.0+dfsg-1.debian.tar.xz be8d1eb663530ad5bf8b013f17c65d24 7762 libs optional openimageio_2.4.16.0+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Debian powered! iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAmU+bjFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N zVq7RQ//Ws8FMxFEXd/ge7Ox6L/Y4yh3NpVT+hrHW/5lzD4Vh5xplOh6RpEohyk+ KDIKw3QFNH4F2XmCXgPTSFVtAofYb6pXfqvpbdTsox8Ymw1/h3QRrxKziRHiWMl+ DBHxwpub3wQ+GK0YxVFY2thQMOEudXE/7lQG009YyD/y0+ee7nsr/bcQ1vPrFkb1 Mo8PLfIf46KFcMewuQ7gigiSC8wgcuHTV8Zmu7chBxms9/4JRSr5SOVPZjNEanRJ urFdFO9qkudSSPEXeaF9Kl55qSJgZiYFegWaY39IEAPPhzr9wvirj2QZWHHDCu3R
Bug#1054873: marked as done (openimageio: CVE-2023-42295)
Your message dated Sun, 29 Oct 2023 15:05:44 + with message-id and subject line Bug#1054873: fixed in openimageio 2.4.16.0+dfsg-1 has caused the Debian Bug report #1054873, regarding openimageio: CVE-2023-42295 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.) -- 1054873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openimageio X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for openimageio. CVE-2023-42295[0]: | An issue in OpenImageIO oiio v.2.4.12.0 allows a remote attacker to | execute arbitrary code and cause a denial of service via the | read_rle_image function of file bifs/unquantize.c https://github.com/AcademySoftwareFoundation/OpenImageIO/issues/3947 https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/3948 Fixed by: https://github.com/AcademySoftwareFoundation/OpenImageIO/commit/15750af31a5d130ea63ac133453eb5448cefa636 (v2.5.3.0-beta1) Fixed by: https://github.com/AcademySoftwareFoundation/OpenImageIO/commit/672ed4c445ebefd5581974c27e28ef717fb6c401 (v2.4.15.0) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-42295 https://www.cve.org/CVERecord?id=CVE-2023-42295 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: openimageio Source-Version: 2.4.16.0+dfsg-1 Done: Matteo F. Vescovi We believe that the bug you reported is fixed in the latest version of openimageio, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated openimageio 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: Sun, 29 Oct 2023 14:50:00 +0100 Source: openimageio Architecture: source Version: 2.4.16.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Matteo F. Vescovi Closes: 1054873 Changes: openimageio (2.4.16.0+dfsg-1) unstable; urgency=medium . * New upstream release (Closes: #1054873) * debian/watch: upstream URL updated Checksums-Sha1: c3613b839cf2d6e45494b6a1f81a214364d9fde6 2996 openimageio_2.4.16.0+dfsg-1.dsc 4c1aebb0a9f6a005d809acb20507920e3e5fd34d 40379252 openimageio_2.4.16.0+dfsg.orig.tar.xz 94b1ea966c6b41c25dd4845fcde3953e77494796 17912 openimageio_2.4.16.0+dfsg-1.debian.tar.xz ebe3ad02bddfef2cef51da0e1bcf098fb26634ba 7762 openimageio_2.4.16.0+dfsg-1_source.buildinfo Checksums-Sha256: 285f51811a42a781491d90189f59f6948c6dc6b811ab67e5f583eaa9dab6d708 2996 openimageio_2.4.16.0+dfsg-1.dsc b4ead8843afb10b8a166eacf3902c7abd71902e0b02f9b0ad004a7347e90dbed 40379252 openimageio_2.4.16.0+dfsg.orig.tar.xz c5f8f117a84e7da2bbba952699511ff6a1816d19a746f580c9466abb971d7982 17912 openimageio_2.4.16.0+dfsg-1.debian.tar.xz 973f8409de7d09b8e06b4391f707a0a743a94ceeb758e95957e279869934d2af 7762 openimageio_2.4.16.0+dfsg-1_source.buildinfo Files: b6fed27516b8bd5cbd7a641120c16f4c 2996 libs optional openimageio_2.4.16.0+dfsg-1.dsc b245de04c2e2f6e4634455613a9ab699 40379252 libs optional openimageio_2.4.16.0+dfsg.orig.tar.xz 49c11b451bf4b4f5b49d7ccd8c6e7a51 17912 libs optional openimageio_2.4.16.0+dfsg-1.debian.tar.xz be8d1eb663530ad5bf8b013f17c65d24 7762 libs optional openimageio_2.4.16.0+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Debian powered! iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAmU+bjFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N zVq7RQ//Ws8FMxFEXd/ge7Ox6L/Y4yh3NpVT+hrHW/5lzD4Vh5xplOh6RpEohyk+ KDIKw3QFNH4F2XmCXgPTSFVtAofYb6pXfqvpbdTsox8Ymw1/h3QRrxKziRHiWMl+ DBHxwpub3wQ+GK0YxVFY2thQMOEudXE/7lQG009YyD/y0+ee7nsr/bcQ1vPrFkb1 Mo8PLfIf46KFcMewuQ7gigiSC8wgcuHTV8Zmu7chBxms9/4JRSr5SOVPZjNEanRJ
Processed: tagging 1054728
Processing commands for cont...@bugs.debian.org: > tags 1054728 - upstream + confirmed Bug #1054728 [src:ledger] ledger: FTBFS: +RuntimeError: Cannot read journal file "/<>/test/regress/xact_code.da" Removed tag(s) upstream. Bug #1054728 [src:ledger] ledger: FTBFS: +RuntimeError: Cannot read journal file "/<>/test/regress/xact_code.da" Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1054728
Processing commands for cont...@bugs.debian.org: > tags 1054728 + upstream Bug #1054728 [src:ledger] ledger: FTBFS: +RuntimeError: Cannot read journal file "/<>/test/regress/xact_code.da" Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054777: Fwd: Bug#1054777: libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2
On Sun, Oct 29, 2023 at 02:00:32PM +, Chris Lamb wrote: Dear Alberto, I think this is likely a problem I already fixed back in February in commit 5dcc6d4. Ah, cherry-picking that commit fixed it for me. I've gone ahead and uploaded that to Debian in order to close this RC bug, but please do feel free to also release a libfiu v1.2 as well. That would have the added advantage of "clearing out" the other patch we had to apply re. Link-Time Optimisation. Great! I've just released libfiu 1.2 then :) Just in case, one of the possibly-impacting patches is updating to setuptools, that may need some adjustments in the build-depends: https://blitiri.com.ar/git/r/libfiu/c/88b961aad6b1fcbc0e1decbf34a0bc9510600988/ Hopefully with that you can clear the other patch! Thank you! Alberto
Processed: limit source to gpgme1.0, tagging 1054786, tagging 1039724
Processing commands for cont...@bugs.debian.org: > limit source gpgme1.0 Limiting to bugs with field 'source' containing at least one of 'gpgme1.0' Limit currently set to 'source':'gpgme1.0' > tags 1054786 + pending Bug #1054786 [src:gpgme1.0] gpgme1.0: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. > tags 1039724 + pending Bug #1039724 [src:gpgme1.0] gpgme: building underbookworm fails with no matches in python3-gpg.install Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1039724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039724 1054786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054981: libtk-objeditor-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
On Sunday, 29 October 2023 01:09:21 CET you wrote: > This seems to be broken by libtk-objscanner-perl 2.018-1 (building in > a testing chroot with 2.017-2 still works). > > Dominique, I think that's a case for you :) ack. I'll handle it upstream. No need to open a bug there. All the best
Bug#1054777: Fwd: Bug#1054777: libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2
Dear Alberto, > I think this is likely a problem I already fixed back in February in > commit 5dcc6d4. Ah, cherry-picking that commit fixed it for me. I've gone ahead and uploaded that to Debian in order to close this RC bug, but please do feel free to also release a libfiu v1.2 as well. That would have the added advantage of "clearing out" the other patch we had to apply re. Link-Time Optimisation. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#1055023: FTBFS: libpoe-component-client-dns-perl requires DNS during tests.
Package: libpoe-component-client-dns-perl Severity: serious Version: 1:1.054-3 While rebuilding debian trixie in a network-restricted environment, we ran into this build error (using sbuild): Can't call method "rdstring" on an undefined value at t/06_hosts.t line 143. # Looks like your test exited with 22 just after 1. The problem is likely that DNS does work to some degree (it can resolve some hosts, I'm not sure what the exact response is on other hosts). The test at https://sources.debian.org/src/libpoe-component-client-dns-perl/1%3A1.054-3/t/06_hosts.t/#L14 isn't a sufficient precaution to work around the Debian Policy *requirement* that required build targets *must* *not* *use* network resources that weren't created by the build processes themselves. The test itself is already using network resources it hasn't created itself. Please disable this test or ensure that it's not using external resolvers. Kind regards, Sven
Processed: Bumping severity of Sphinx 7 bugs to RC
Processing commands for cont...@bugs.debian.org:
> # Dear Maintainers, I am going to upload Sphinx 7.2.6 to unstable next
> weekend.
> # That will make these packages FTBFS in sid, which is a release-critical bug.
> # The new docutils will be uploaded after Sphinx migrates to testing.
> severity 1042585 serious
Bug #1042585 [src:python-i3ipc] python-i3ipc: FTBFS with Sphinx 7.1, docutils
0.20: TypeError: Python directive method get_signature_prefix() must return a
list of nodes. Return value was 'coroutine '.
Severity set to 'serious' from 'important'
> severity 1042586 serious
Bug #1042586 [src:python-flask-marshmallow] python-flask-marshmallow: FTBFS
with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:19:
override_dh_sphinxdoc] Error 2
Severity set to 'serious' from 'important'
> severity 1042587 serious
Bug #1042587 [src:sphinx-rst-builder] sphinx-rst-builder: FTBFS with Sphinx
7.1, docutils 0.20: Could not import extension sphinx_rst_builder (exception:
cannot import name 'versionlabels' from 'sphinx.locale'
(/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
Severity set to 'serious' from 'important'
> severity 1042588 serious
Bug #1042588 [src:fmtlib] fmtlib: FTBFS with Sphinx 7.1, docutils 0.20:
make[1]: *** [debian/rules:18: override_dh_auto_build-indep] Error 2
Severity set to 'serious' from 'important'
> severity 1042590 serious
Bug #1042590 [src:django-session-security] django-session-security: FTBFS with
Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'
Severity set to 'serious' from 'important'
> severity 1042591 serious
Bug #1042591 [src:pg8000] pg8000: FTBFS with Sphinx 7.1, docutils 0.20: error:
invalid command 'build_sphinx'
Severity set to 'serious' from 'important'
> severity 1042593 serious
Bug #1042593 [src:flufl.lock] flufl.lock: FTBFS with Sphinx 7.1, docutils 0.20:
error: invalid command 'build_sphinx'
Severity set to 'serious' from 'important'
> severity 1042594 serious
Bug #1042594 [src:python-tornado] python-tornado: FTBFS with Sphinx 7.1,
docutils 0.20: TypeError: Python directive method get_signature_prefix() must
return a list of nodes. Return value was 'coroutine '.
Severity set to 'serious' from 'important'
> severity 1042595 serious
Bug #1042595 [src:python-gevent] python-gevent: FTBFS with Sphinx 7.1, docutils
0.20: TypeError: not all arguments converted during string formatting
Severity set to 'serious' from 'important'
> severity 1042597 serious
Bug #1042597 [src:python-amqp] python-amqp: FTBFS with Sphinx 7.1, docutils
0.20: make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2
Severity set to 'serious' from 'important'
> severity 1042598 serious
Bug #1042598 [src:python-ironicclient] python-ironicclient: FTBFS with Sphinx
7.1, docutils 0.20:
ironicclient.tests.unit.v1.test_events.EventManagerTest.test_event ...
check_parser: error: the following arguments are required:
Severity set to 'serious' from 'important'
> severity 1042599 serious
Bug #1042599 [src:python-pkginfo] python-pkginfo: FTBFS with Sphinx 7.1,
docutils 0.20: error: invalid command 'build_sphinx'
Severity set to 'serious' from 'important'
> severity 1042600 serious
Bug #1042600 [src:imexam] imexam: FTBFS with Sphinx 7.1, docutils 0.20:
make[1]: *** [debian/rules:14: override_dh_installdocs-indep] Error 25
Severity set to 'serious' from 'important'
> severity 1042601 serious
Bug #1042601 [src:python-apt] python-apt: FTBFS with Sphinx 7.1, docutils 0.20:
error: invalid command 'build_sphinx'
Severity set to 'serious' from 'important'
> severity 1042602 serious
Bug #1042602 [src:sphinx-panels] sphinx-panels: FTBFS with Sphinx 7.1, docutils
0.20: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
3.11 returned exit code 13
Severity set to 'serious' from 'important'
> severity 1042605 serious
Bug #1042605 [src:terminaltables] terminaltables: FTBFS with Sphinx 7.1,
docutils 0.20: TypeError: not all arguments converted during string formatting
Severity set to 'serious' from 'important'
> severity 1042606 serious
Bug #1042606 [src:calcium] calcium: FTBFS with Sphinx 7.1, docutils 0.20: rm:
cannot remove 'doc/build/html/_static/underscore.js': No such file or directory
Severity set to 'serious' from 'important'
> severity 1042607 serious
Bug #1042607 [src:harp] harp: FTBFS with Sphinx 7.1, docutils 0.20: rm: cannot
remove 'debian/tmp/usr/share/harp/doc/html/_static/underscore*': No such file
or directory
Severity set to 'serious' from 'important'
> severity 1042609 serious
Bug #1042609 [src:sphinxcontrib-mermaid] sphinxcontrib-mermaid: FTBFS with
Sphinx 7.1, docutils 0.20: Could not import sphinx.util.SphinxParallelError
(exception: No module named 'sphinx.util.SphinxParallelError')
Severity set to 'serious' from 'important'
> severity 1042610 serious
Bug #1042610 [src:behave] behave: FTBFS with Sphinx 7.1, docutils 0.20:
TypeError: not all arguments converted during string formatting
Severity set to 'serious' from
Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory
El 29/10/23 a las 14:20, Mark Hindley escribió: Lucas, I am afraid I still cannot reproduce this. I attach my successful .buildinfo. What are the differences to yours? Hello. The problem is that failed builds do not produce .buildinfo files, so we can't compare buildinfo files in this case. However, I can create a machine for you to reproduce the problem. Please contact me privately for details. Thanks.
Bug#1054867: marked as done (python-pyftpdlib: FTBFS: make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100
with message-id
and subject line Closing bugs I cannot reproduce anymore.
has caused the Debian Bug report #1054867,
regarding python-pyftpdlib: FTBFS: make[1]: *** [debian/rules:21:
override_dh_auto_build] Error 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyftpdlib
Version: 1.5.7-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:310: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/handlers.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/authorizers.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/prefork.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/__main__.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/filesystems.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/_compat.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/ioloop.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/log.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> copying pyftpdlib/servers.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib
> creating
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/test_functional.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/test_authorizers.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/test_ioloop.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/test_misc.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/test_filesystems.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/runner.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/test_functional_ssl.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/test_servers.py ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/README ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> copying pyftpdlib/test/keycert.pem ->
> /<>/.pybuild/cpython3_3.11_pyftpdlib/build/pyftpdlib/test
> running build_scripts
> creating build
> creating build/scripts-3.11
> copying and adjusting scripts/ftpbench -> build/scripts-3.11
> changing mode of build/scripts-3.11/ftpbench from 644 to 755
> ( cd docs; \
> PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -M html . _build )
> Running Sphinx v5.3.0
> WARNING: Invalid configuration value found: 'language = None'. Update your
> configuration to a valid language code. Falling back to 'en' (English).
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 8 source files that are out of date
> updating environment: [new config] 8 added, 0 changed, 0 removed
> reading sources... [ 12%] adoptions
> reading sources... [ 25%] api
> reading sources... [ 37%] benchmarks
> reading sources... [ 50%] faqs
> reading sources... [ 62%] index
> reading sources... [ 75%] install
> reading sources... [ 87%] rfc-compliance
> reading sources... [100%] tutorial
>
> /<>/docs/tutorial.rst:358: WARNING: Inline literal start-string
> without end-string.
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 12%] adoptions
>
> Theme error:
> An error happened in rendering the page adoptions.
> Reason: AttributeError("'str' object has no attribute 'attributes'")
> make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
The full build log is available from:
Bug#1054834: marked as done (coreboot: FTBFS: make[1]: *** [debian/rules:29: override_dh_auto_build] Error 2)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054834, regarding coreboot: FTBFS: make[1]: *** [debian/rules:29: override_dh_auto_build] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coreboot Version: 4.15~dfsg-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/util/superiotool' > > Checking for pciutils and zlib... found. > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o superiotool.o superiotool.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o serverengines.o serverengines.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o ali.o ali.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o exar.o exar.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o fintek.o fintek.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o ite.o ite.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o nsc.o nsc.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o nuvoton.o nuvoton.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o smsc.o smsc.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef -Wstrict-aliasing > -Werror-implicit-function-declaration -ansi -pedantic > -D'SUPERIOTOOL_VERSION=""' -DPCI_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o winbond.o winbond.c > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 > -Wall -Wstrict-prototypes -Wundef
Bug#1054855: marked as done (powerline: FTBFS: make[1]: *** [debian/rules:17: override_dh_installdocs] Error 2)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054855, regarding powerline: FTBFS: make[1]: *** [debian/rules:17: override_dh_installdocs] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: powerline Version: 2.8.3-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PYTHONPATH=. sphinx-build -b html -N docs/source docs/build/html > Running Sphinx v5.3.0 > WARNING: while setting up extension powerline_autodoc: directive > 'autofunction' is already registered, it will be overridden > WARNING: while setting up extension powerline_autodoc: directive > 'autoattribute' is already registered, it will be overridden > making output directory... done > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 38 source files that are out of date > updating environment: [new config] 38 added, 0 changed, 0 removed > reading sources... [ 2%] commands > reading sources... [ 5%] commands/config > reading sources... [ 7%] commands/daemon > reading sources... [ 10%] commands/lint > reading sources... [ 13%] commands/main > reading sources... [ 15%] configuration > reading sources... [ 18%] configuration/listers > reading sources... [ 21%] configuration/local > reading sources... [ 23%] configuration/reference > reading sources... [ 26%] configuration/segments > reading sources... [ 28%] configuration/segments/common > reading sources... [ 31%] configuration/segments/i3wm > reading sources... [ 34%] configuration/segments/pdb > reading sources... [ 36%] configuration/segments/shell > reading sources... [ 39%] configuration/segments/tmux > reading sources... [ 42%] configuration/segments/vim > reading sources... [ 44%] configuration/selectors > reading sources... [ 47%] configuration/selectors/vim > reading sources... [ 50%] develop > reading sources... [ 52%] develop/extensions > reading sources... [ 55%] develop/listers > reading sources... [ 57%] develop/local-themes > reading sources... [ 60%] develop/segments > reading sources... [ 63%] develop/tips-and-tricks > reading sources... [ 65%] index > reading sources... [ 68%] installation > reading sources... [ 71%] installation/linux > reading sources... [ 73%] installation/osx > reading sources... [ 76%] license-and-credits > reading sources... [ 78%] overview > reading sources... [ 81%] tips-and-tricks > reading sources... [ 84%] troubleshooting > reading sources... [ 86%] troubleshooting/linux > reading sources... [ 89%] troubleshooting/osx > reading sources... [ 92%] usage > reading sources... [ 94%] usage/other > reading sources... [ 97%] usage/shell-prompts > reading sources... [100%] usage/wm-widgets > > WARNING: error while formatting arguments for > powerline.segments.common.sys.cpu_load_percent: decoding str is not supported > WARNING: error while formatting arguments for > powerline.segments.common.sys.system_load: decoding str is not supported > WARNING: error while formatting arguments for > powerline.segments.common.sys.uptime: decoding str is not supported > WARNING: error while formatting arguments for > powerline.segments.common.net.external_ip: decoding str is not supported > WARNING: error while formatting arguments for > powerline.segments.common.net.internal_ip: decoding str is not supported > WARNING: error while formatting arguments for > powerline.segments.common.net.network_load: decoding str is not supported > WARNING: error while formatting arguments for > powerline.segments.common.env.cwd: decoding str is not supported > /<>/powerline/segments/common/env.py:docstring of > powerline.segments.common.env.virtualenv:3: ERROR: Unexpected indentation. > /<>/powerline/segments/common/env.py:docstring of > powerline.segments.common.env.CwdSegment:1: WARNING: Block quote ends without > a blank line; unexpected unindent. > WARNING: error while formatting arguments for > powerline.segments.common.bat.battery: decoding str is not supported > WARNING: error while formatting arguments for > powerline.segments.common.wthr.weather: decoding str is not supported > WARNING: error while formatting arguments for >
Bug#1054837: marked as done (pyodc: FTBFS: make: *** [debian/rules:11: binary] Error 25)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100
with message-id
and subject line Closing bugs I cannot reproduce anymore.
has caused the Debian Bug report #1054837,
regarding pyodc: FTBFS: make: *** [debian/rules:11: binary] Error 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyodc
Version: 1.1.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules binary
> dh binary --buildsystem=pybuild
>dh_testroot -O--buildsystem=pybuild
>dh_prep -O--buildsystem=pybuild
> rm -f -- debian/python3-pyodc.substvars
> debian/python3-pyodc-docs.substvars
> rm -fr -- debian/.debhelper/generated/python3-pyodc/
> debian/python3-pyodc/ debian/tmp/
> debian/.debhelper/generated/python3-pyodc-docs/ debian/python3-pyodc-docs/
>dh_auto_install -O--buildsystem=pybuild
> install -m0755 -d /<>/debian/tmp
> pybuild --install -i python{version} -p 3.11 --dest-dir
> /<>/debian/tmp
> I: pybuild base:310: /usr/bin/python3 setup.py install --root
> /<>/debian/python3-pyodc
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66:
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
>
>
>
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
>
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html
> for details.
>
>
>
> !!
> self.initialize_options()
> running build
> running build_py
> running egg_info
> writing pyodc.egg-info/PKG-INFO
> writing dependency_links to pyodc.egg-info/dependency_links.txt
> writing requirements to pyodc.egg-info/requires.txt
> writing top-level names to pyodc.egg-info/top_level.txt
> reading manifest file 'pyodc.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'pyodc.egg-info/SOURCES.txt'
> running install_lib
> creating /<>/debian/python3-pyodc
> creating /<>/debian/python3-pyodc/usr
> creating /<>/debian/python3-pyodc/usr/lib
> creating /<>/debian/python3-pyodc/usr/lib/python3.11
> creating
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages
> creating
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/codc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/codc/constants.py
> -> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/codc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/codc/lib.py ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/codc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/codc/__init__.py
> -> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/codc
> copying
> /<>/.pybuild/cpython3_3.11_pyodc/build/codc/processed_odc.h ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/codc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/codc/reader.py ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/codc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/codc/frame.py ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/codc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/codc/encoder.py
> -> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/codc
> creating
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/pyodc
> copying
> /<>/.pybuild/cpython3_3.11_pyodc/build/pyodc/constants.py ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/pyodc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/pyodc/__init__.py
> ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/pyodc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/pyodc/reader.py
> ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/pyodc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/pyodc/stream.py
> ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/pyodc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/pyodc/codec.py ->
> /<>/debian/python3-pyodc/usr/lib/python3.11/dist-packages/pyodc
> copying /<>/.pybuild/cpython3_3.11_pyodc/build/pyodc/frame.py ->
>
Bug#1054833: marked as done (openshot-qt: FTBFS: make[1]: *** [debian/rules:11: execute_after_dh_auto_build] Error 2)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054833, regarding openshot-qt: FTBFS: make[1]: *** [debian/rules:11: execute_after_dh_auto_build] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openshot-qt Version: 3.1.1+dfsg1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -b html -d > build/doctrees doc build/html > Running Sphinx v5.3.0 > making output directory... done > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 20 source files that are out of date > updating environment: [new config] 20 added, 0 changed, 0 removed > reading sources... [ 5%] animation > reading sources... [ 10%] clips > reading sources... [ 15%] contributing > reading sources... [ 20%] developers > reading sources... [ 25%] effects > reading sources... [ 30%] export > reading sources... [ 35%] files > reading sources... [ 40%] getting_started > reading sources... [ 45%] glossary > reading sources... [ 50%] import_export > reading sources... [ 55%] index > reading sources... [ 60%] installation > reading sources... [ 65%] introduction > reading sources... [ 70%] learn_more > reading sources... [ 75%] main_window > reading sources... [ 80%] preferences > reading sources... [ 85%] profiles > reading sources... [ 90%] quick_tutorial > reading sources... [ 95%] titles > reading sources... [100%] transitions > > /<>/doc/animation.rst:57: ERROR: "table" widths do not match the > number of columns in table (2). > > .. table:: >:widths: 12 > >== >NameDescription >== >Bézier Interpolated values use a quadratic curve, and ease-in > and ease-out >Linear Interpolated values are calculated linear (each step > value is equal) >ConstantInterpolated values stay the same until the next key > frame, and jump to the new value >== > /<>/doc/animation.rst:95: ERROR: "table" widths do not match the > number of columns in table (3). > > .. table:: >:widths: 5 25 > >== ># Name Description >== >1 File Properties Select an image sequence in the **Project > Files** panel, right click and choose **File Properties** >2 Frame RateAdjust the frame rate of the animation. > Typically, hand-drawn animations use 12 frames per second. >== > /<>/doc/clips.rst:69: ERROR: "table" widths do not match the > number of columns in table (2). > > .. table:: >:widths: 30 > >== >Trim & Slice Method Description >== >**Resizing Edge** Mouse over the edge of a clip, and resize the > edge, by dragging it left/right. >**Slice** When the play-head (i.e. vertical red playback > line) is overlapping a clip, right click on the clip, >and choose :guilabel:`Slice`. >**Slice All** When the play-head is overlapping many clips, > right click on the play-head, and choose >:guilabel:`Slice All` (it will cut all > intersecting clips on all tracks). >**Split Clip Dialog** Right click on a file, and choose :guilabel:`Split > Clip`. A dialog will appear which allows >for creating lots of small cuts in a single video > file. >**Razor Tool** The :guilabel:`razor tool` from the **Edit > Toolbar** cuts a clip wherever you click on it. >So be careful, it is easy and dangerous! >== > /<>/doc/clips.rst:97: ERROR: "table" widths do not match the > number of columns in table (2). > > .. table:: >:widths: 20 > >== >NameDescription >== >FadeFade
Bug#1054817: marked as done (terminaltables: FTBFS: InputError: [Errno 2] No such file or directory: 'README.rst'.)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100
with message-id
and subject line Closing bugs I cannot reproduce anymore.
has caused the Debian Bug report #1054817,
regarding terminaltables: FTBFS: InputError: [Errno 2] No such file or
directory: 'README.rst'.
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.)
--
1054817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: terminaltables
Version: 3.1.10-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. /usr/share/sphinx/scripts/python3/sphinx-build -N -q -E -b html
> docs/
> debian/python-terminaltables-doc/usr/share/doc/python-terminaltables-doc/html/
> WARNING: extlinks: Sphinx-6.0 will require a caption string to contain
> exactly one '%s' and all other '%' need to be escaped as '%%'.
> /<>/docs/changelog.rst:3: CRITICAL: Problems with "include"
> directive path:
> InputError: [Errno 2] No such file or directory: 'README.rst'.
>
> Theme error:
> An error happened in rendering the page asciitable.
> Reason: AttributeError("'str' object has no attribute 'attributes'")
> make[1]: *** [debian/rules:15: override_dh_sphinxdoc] Error 2
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/terminaltables_3.1.10-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
This doesn't fail anymore. Closing.--- End Message ---
Bug#1054811: marked as done (python-oslo.rootwrap: FTBFS: tests failed)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054811, regarding python-oslo.rootwrap: FTBFS: tests 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.) -- 1054811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-oslo.rootwrap Version: 7.1.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_test --no-py2 'oslo_rootwrap\.tests\.(?!(.*test_functional.*))' > + PKGOS_TEST_PARALLEL=yes > + PKGOS_TEST_SERIAL=no > + PYTHONS=disabled > + PYTHON3S=disabled > + TEST_PARALLEL_OPT=--parallel > + TEST_SERIAL_OPT= > + echo WARNING: --no-py2 is deprecated, and always on. > WARNING: --no-py2 is deprecated, and always on. > + shift > + py3versions -vr > + PYTHON3S=3.11 > + [ yes = no ] > + [ no = yes ] > + [ 3.11 = disabled ] > + echo 3.11 > + cut -d. -f1 > + PYMAJOR=3 > + echo ===> Testing with python (python3) > ===> Testing with python (python3) > + pwd > + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ] > + [ -e .stestr.conf ] > + [ -x /usr/bin/python3-stestr ] > + STESTR=stestr > + rm -rf .stestr > + PYTHON=python3.11 stestr run --parallel --subunit > oslo_rootwrap\.tests\.(?!(.*test_functional.*)) > + subunit2pyunit > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_ChainingRegExpFilter_match > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_ChainingRegExpFilter_match > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_ChainingRegExpFilter_multiple > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_ChainingRegExpFilter_multiple > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_ChainingRegExpFilter_not_match > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_ChainingRegExpFilter_not_match > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_CommandFilter > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_CommandFilter ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_EnvFilter > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_EnvFilter ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_EnvFilter_without_leading_env > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_EnvFilter_without_leading_env > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_netns > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_netns ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_netns_add > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_netns_add > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_netns_delete > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_netns_delete > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_netns_list > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_netns_list > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_non_netns > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpFilter_non_netns > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpNetnsExecFilter_match > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpNetnsExecFilter_match > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpNetnsExecFilter_nomatch > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpNetnsExecFilter_nomatch > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpNetnsExecFilter_nomatch_nonroot > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_IpNetnsExecFilter_nomatch_nonroot > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_KillFilter > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_KillFilter ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_KillFilter_deleted_exe > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_KillFilter_deleted_exe > ... ok > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_KillFilter_no_raise > oslo_rootwrap.tests.test_rootwrap.RootwrapTestCase.test_KillFilter_no_raise > ... ok >
Bug#1054807: marked as done (python-psutil: FTBFS: make[1]: *** [Makefile:58: html] Error 2)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100
with message-id
and subject line Closing bugs I cannot reproduce anymore.
has caused the Debian Bug report #1054807,
regarding python-psutil: FTBFS: make[1]: *** [Makefile:58: html] Error 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-psutil
Version: 5.9.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>/docs'
> python3 -m sphinx -b html -d _build/doctrees . _build/html
> Running Sphinx v5.3.0
> loading translations [eng]... not available for built-in messages
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [100%] index
>
> Theme error:
> An error happened in rendering the page index.
> Reason: AttributeError("'str' object has no attribute 'attributes'")
> make[1]: *** [Makefile:58: html] Error 2
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/python-psutil_5.9.5-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
This doesn't fail anymore. Closing.--- End Message ---
Bug#1054769: marked as done (quilt: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054769, regarding quilt: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: quilt Version: 0.67+really0.67-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > [add-filename-check.test] > 6 commands (6 passed, 0 failed) > [altered-series.test] > 12 commands (12 passed, 0 failed) > [comments.test] > 11 commands (11 passed, 0 failed) > [applied.test] > 15 commands (15 passed, 0 failed) > [colon-in-patch-name.test] > 23 commands (23 passed, 0 failed) > [dir-a-b.test] > 11 commands (11 passed, 0 failed) > [create-delete.test] > 19 commands (19 passed, 0 failed) > [annotate.test] > 31 commands (31 passed, 0 failed) > [duplicate-patch-in-series.test] > 9 commands (9 passed, 0 failed) > [auto-refresh.test] > 14 commands (14 passed, 0 failed) > [dotglob.test] > 7 commands (7 passed, 0 failed) > [conflicts.test] > 39 commands (39 passed, 0 failed) > [delete.test] > 33 commands (33 passed, 0 failed) > [faildiff.test] > 15 commands (15 passed, 0 failed) > [failbackup.test] > 10 commands (10 passed, 0 failed) > [failpop.test] > 13 commands (13 passed, 0 failed) > [empty.test] > 10 commands (10 passed, 0 failed) > [edit.test] > 31 commands (31 passed, 0 failed) > [fold.test] > 11 commands (11 passed, 0 failed) > [hard-linked-patch.test] > 15 commands (15 passed, 0 failed) > [formats.test] > 13 commands (13 passed, 0 failed) > [empty-files.test] > 40 commands (40 passed, 0 failed) > [half-applies.test] > 18 commands (18 passed, 0 failed) > [help.test] > 31 commands (31 passed, 0 failed) > [example1.test] > 30 commands (30 passed, 0 failed) > [header.test] > 17 commands (17 passed, 0 failed) > [new-nosubdir.test] > 4 commands (4 passed, 0 failed) > [backup-files.test] > 136 commands (136 passed, 0 failed) > [missing-newline.test] > 9 commands (9 passed, 0 failed) > [missing.test] > 6 commands (6 passed, 0 failed) > [no-file-to-patch.test] > 5 commands (5 passed, 0 failed) > [merge.test] > 11 commands (11 passed, 0 failed) > [new.test] > 9 commands (9 passed, 0 failed) > [no-series.test] > 44 commands (44 passed, 0 failed) > [project-settings.test] > 10 commands (10 passed, 0 failed) > [null-bug.test] > 9 commands (9 passed, 0 failed) > [perms.test] > 21 commands (21 passed, 0 failed) > [import2.test] > 40 commands (40 passed, 0 failed) > [nolink.test] > 28 commands (28 passed, 0 failed) > [remember-locations.test] > 13 commands (13 passed, 0 failed) > [refresh-z.test] > 10 commands (10 passed, 0 failed) > [refresh.test] > 12 commands (12 passed, 0 failed) > [mail.test] > 23 commands (23 passed, 0 failed) > [remove-trailing-ws.test] > 44 commands (44 passed, 0 failed) > [push_timeskew.test] > [5] $ mkdir patches d -- ok > [7] $ quilt new patch1 -- ok > [10] $ cd d -- ok > [11] $ mkdir dir -- ok > [12] $ echo "This is file one." > dir/file1 -- ok > [13] $ quilt add dir/file1 -- ok > [16] $ echo "This is file two." > dir/file2 -- ok > [17] $ quilt add dir/file2 -- ok > [20] $ echo "More content to file one." >> dir/file1 -- ok > [21] $ echo "More content to file two." >> dir/file2 -- ok > [22] $ quilt refresh -- ok > [25] $ quilt pop -q -- ok > [29] $ test dir/file1 -nt dir/file2 && echo "timeskew!" -- ok > [30] $ test dir/file2 -nt dir/file1 && echo "timeskew!" -- ok > [32] $ quilt push -q -- ok > [36] $ test dir/file1 -nt dir/file2 && echo "timeskew!" -- ok > [37] $ test dir/file2 -nt dir/file1 && echo "timeskew!" -- failed > timeskew! != ~ > [42] $ quilt new patch2.diff -- ok > [45] $ echo "some content" > dir/file_removed -- ok > [46] $ quilt add dir/file_removed -- ok > [49] $ quilt add dir/file_created -- ok > [52] $ rm dir/file_removed -- ok > [53] $ echo "some content" > dir/file_created -- ok > [54] $ quilt refresh -- ok > [57] $ quilt diff --no-timestamps --no-index -p ab -- ok > [67] $ quilt pop -- ok > [74] $ test -e dir/file_created && echo "Created file should not exist when > patch is poped!" -- ok > [75] $ test ! -e dir/file_removed && echo "Deleted file
Bug#1054721: marked as done (python-igraph: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100
with message-id
and subject line Closing bugs I cannot reproduce anymore.
has caused the Debian Bug report #1054721,
regarding python-igraph: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.11 returned exit code 13
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.)
--
1054721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-igraph
Version: 0.11.2+ds-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/configuration.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/seq.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/sparse_matrix.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/utils.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/datatypes.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/version.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/statistics.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/__init__.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/structural.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/bipartite.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/summary.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/community.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/matching.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/basic.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/layout.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/automorphisms.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/cut.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/clustering.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/adjacency.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> copying src/igraph/formula.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph
> creating /<>/.pybuild/cpython3_3.11_igraph/build/igraph/operators
> copying src/igraph/operators/functions.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/operators
> copying src/igraph/operators/__init__.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/operators
> copying src/igraph/operators/methods.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/operators
> creating /<>/.pybuild/cpython3_3.11_igraph/build/igraph/app
> copying src/igraph/app/__init__.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/app
> copying src/igraph/app/shell.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/app
> creating /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/utils.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/random.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/__init__.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/bipartite.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/objects.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/files.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/libraries.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/adjacency.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> copying src/igraph/io/images.py ->
> /<>/.pybuild/cpython3_3.11_igraph/build/igraph/io
> creating /<>/.pybuild/cpython3_3.11_igraph/build/igraph/remote
> copying src/igraph/remote/__init__.py ->
>
Bug#1052924: marked as done (gyoto: FTBFS: mkdir: cannot create directory ‘././sbuild-nonexistent’: Permission denied)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100
with message-id
and subject line Closing bugs I cannot reproduce anymore.
has caused the Debian Bug report #1052924,
regarding gyoto: FTBFS: mkdir: cannot create directory
‘././sbuild-nonexistent’: Permission denied
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.)
--
1052924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gyoto
Version: 1.4.4-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/doc/user_guide'
> pdflatex '\nonstopmode \newcommand{\GyotoSrcDir}{../..}
> \input{./GyotoManual.tex}'
> This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> LaTeX2e <2023-06-01>
> L3 programming layer <2023-06-05>
>
> (./GyotoManual.tex (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2023/05/17 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/natbib/natbib.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/preprint/fullpage.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/rotating.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def)
> (/usr/share/texlive/texmf-dist/tex/generic/babel-french/frenchb.ldf
>
> Package babel-french Warning: Option `frenchb' for Babel is *deprecated*,
> (babel-french)it might be removed sooner or later. Please
> (babel-french)use `french' instead; reported on input line 35.
>
> (/usr/share/texlive/texmf-dist/tex/generic/babel-french/french.ldf))
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/locale/en/babel-english.tex)
> (/usr/share/texlive/texmf-dist/tex/latex/carlisle/scalefnt.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
> (/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/kvsetkeys/kvsetkeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/letltxmacro/letltxmacro.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/auxhook/auxhook.sty)
>
Bug#1052925: marked as done (python-kaptan: FTBFS: chmod: cannot access '/<>/kaptan.egg-info/*': No such file or directory)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052925, regarding python-kaptan: FTBFS: chmod: cannot access '/<>/kaptan.egg-info/*': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-kaptan Version: 0.5.12-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:291: python3.11 setup.py config > Warning: 'classifiers' should be a list, got type 'tuple' > running config >debian/rules execute_before_dh_auto_build > make[1]: Entering directory '/<>' > chmod -x /<>/kaptan.egg-info/* > chmod: cannot access '/<>/kaptan.egg-info/*': No such file or > directory > make[1]: *** [debian/rules:9: execute_before_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/09/25/python-kaptan_0.5.12-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- This doesn't fail anymore. Closing.--- End Message ---
Bug#1052864: marked as done (simgear: FTBFS: dh_auto_test: error: cd build && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052864, regarding simgear: FTBFS: dh_auto_test: error: cd build && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: simgear Version: 1:2020.3.18+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j1 > UpdateCTestConfiguration from :/<>/build/DartConfiguration.tcl > Parse Config file:/<>/build/DartConfiguration.tcl > UpdateCTestConfiguration from :/<>/build/DartConfiguration.tcl > Parse Config file:/<>/build/DartConfiguration.tcl > Test project /<>/build > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: test_bucket > > 1: Test command: /<>/build/simgear/bucket/test_bucket > 1: Working Directory: /<>/build/simgear/bucket > 1: Test timeout computed to be: 1500 > 1: [TEST] BNA Airport: -87:1, 36:0 > 1: [TEST] BNA lon: -86.625 > 1: [TEST] BNA lat: 36.0625 > 1: all tests passed OK > 1/35 Test #1: test_bucket .. Passed0.00 sec > test 2 > Start 2: bvhtest > > 2: Test command: /<>/build/simgear/bvh/bvhtest > 2: Working Directory: /<>/build/simgear/bvh > 2: Test timeout computed to be: 1500 > 2/35 Test #2: bvhtest .. Passed0.00 sec > test 3 > Start 3: embedded_resources > > 3: Test command: > /<>/build/simgear/embedded_resources/test_embedded_resources > 3: Working Directory: /<>/build/simgear/embedded_resources > 3: Test timeout computed to be: 1500 > 3: Creating the EmbeddedResourceManager instance and adding a few resources > to it > 3: Testing resource fetching methods of EmbeddedResourceManager with a > RawEmbeddedResource > 3: > 3: /path/to/resource1 -> RawEmbeddedResource: > 3: compressionType = "none" > 3: rawPtr = 0x561a4e345e00 > 3: rawSize = 40 > 3: > 3: Testing EmbeddedResourceManager::getStreambuf() > 3: Testing EmbeddedResourceManager::getIStream() > 3: Testing resource fetching methods of EmbeddedResourceManager with a > ZlibEmbeddedResource > 3: > 3: /path/to/resource2 -> ZlibEmbeddedResource: > 3: compressionType = "zlib" > 3: rawPtr = 0x561a4e3560c0 > 3: rawSize = 320 > 3: uncompressedSize = 568 > 3: > 3: Resource 2 compression ratio: 1.775 > 3: Testing the behavior of EmbeddedResourceManager when trying to fetch > inexistent resources > 3: Testing the behavior of EmbeddedResourceManager when trying to add an > already existing resource > 3: Testing the locale-dependency of resource fetching from > EmbeddedResourceManager > 3: Testing the getLocale() and selectLocale() methods of > EmbeddedResourceManager > 3: Testing the EmbeddedResourceProxy class > 3: Testing EmbeddedResourceProxy::getIStream() > 3: Testing EmbeddedResourceProxy::getIStream() > 3: Testing EmbeddedResourceProxy::getIStream() > 3: Testing EmbeddedResourceProxy::getIStream() > 3: Testing EmbeddedResourceProxy::getIStream() > 3: Testing EmbeddedResourceProxy::getIStream() > 3: Testing EmbeddedResourceProxy::getIStream() > 3: Testing EmbeddedResourceProxy::getIStream() > 3/35 Test #3: embedded_resources ... Passed0.01 sec > test 4 > Start 4: emesary > > 4: Test command: /<>/build/simgear/emesary/test_emesary > 4: Working Directory: /<>/build/simgear/emesary > 4: Test timeout computed to be: 1500 > 4: invocations 199960002 > 4: starting thread Notif 0 > 4: starting thread Notif 1 > 4: starting thread Notif 2 > 4: starting thread Notif 3 > 4: starting thread Notif 4 > 4: starting thread Notif 5 > 4: starting thread Notif 6 > 4: starting thread Notif 7 > 4: starting thread Notif 8 > 4: starting thread Notif 9 > 4: starting thread Notif 10 > 4: starting thread Notif 11 > 4: Notif 3 invocations > 4: finish thread Notif 3 > 4: Notif 5 invocations > 4: finish thread Notif 5 > 4: Notif 1 invocations > 4: finish thread Notif 1 > 4: Notif 2
Bug#1052888: marked as done (epics-base: FTBFS: make[2]: *** [configure/RULES_TOP:62: runtests] Error 1)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052888, regarding epics-base: FTBFS: make[2]: *** [configure/RULES_TOP:62: runtests] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: epics-base Version: 7.0.7+dfsg1-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[6]: Entering directory > '/<>/modules/pva2pva/iocBoot/iocwfdemo' > make[6]: Nothing to be done for 'runtests'. > make[6]: Leaving directory > '/<>/modules/pva2pva/iocBoot/iocwfdemo' > make[5]: Leaving directory '/<>/modules/pva2pva/iocBoot' > make[4]: Leaving directory '/<>/modules/pva2pva' > make[3]: Leaving directory '/<>/modules' > > Tests failed in: > /<>/modules/database/test/std/rec/O.linux-x86_64 > make[2]: *** [configure/RULES_TOP:62: runtests] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/09/25/epics-base_7.0.7+dfsg1-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- This doesn't fail anymore. Closing.--- End Message ---
Bug#1052899: marked as done (python-fido2: FTBFS: chmod: cannot access 'fido2.egg-info/*': No such file or directory)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100
with message-id
and subject line Closing bugs I cannot reproduce anymore.
has caused the Debian Bug report #1052899,
regarding python-fido2: FTBFS: chmod: cannot access 'fido2.egg-info/*': No such
file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fido2
Version: 0.9.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:291: python3.11 setup.py clean
> /<>/setup.py:33: DeprecationWarning: distutils Version classes
> are deprecated. Use packaging.version instead.
> if LooseVersion(__version__) < LooseVersion("20.2"):
> running clean
> removing '/<>/.pybuild/cpython3_3.11_fido2/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>debian/rules override_dh_clean
> make[1]: Entering directory '/<>'
> chmod a-x fido2.egg-info/*
> chmod: cannot access 'fido2.egg-info/*': No such file or directory
> make[1]: *** [debian/rules:9: override_dh_clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/python-fido2_0.9.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
This doesn't fail anymore. Closing.--- End Message ---
Bug#1052774: marked as done (php-arthurhoaro-web-thumbnailer: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052774, regarding php-arthurhoaro-web-thumbnailer: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-arthurhoaro-web-thumbnailer Version: 2.1.0+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > phpunit --no-coverage --include-path src --testsuite NoNetworkTests > Tue, 26 Sep 2023 06:53:47 + - Web server started on localhost:8081 with > PID 1290407 > PHPUnit 9.6.13 by Sebastian Bergmann and contributors. > > ...SSF..S...FFF 63 / 129 ( > 48%) > .S.SS.. 126 / 129 ( > 97%) > .SS 129 / 129 > (100%) > > Time: 00:00.221, Memory: 6.00 MB > > There were 4 failures: > > 1) WebThumbnailer\Finder\DefaultFinderTest::testDefaultFinderImageMimetype > Failed asserting that false matches expected > 'http://localhost:8081/default/image-mimetype.php'. > > /<>/tests/Finder/DefaultFinderTest.php:95 > > 2) WebThumbnailer\Finder\QueryRegexFinderTest::testQueryRegexFinderCurlValid > Failed asserting that false matches expected > 'https://domain.tld/pics/thumb.png?name=text'. > > /<>/tests/Finder/QueryRegexFinderTest.php:91 > > 3) > WebThumbnailer\Finder\QueryRegexFinderTest::testQueryRegexFinderCurlTwoThumbs > Failed asserting that false matches expected > 'https://domain.tld/pics/thumb.png?name=text'. > > /<>/tests/Finder/QueryRegexFinderTest.php:102 > > 4) > WebThumbnailer\Finder\QueryRegexFinderTest::testQueryRegexFinderCurlWithParameter > Failed asserting that false matches expected > 'https://domain.tld/pics/thumb.png?param=foobar-other'. > > /<>/tests/Finder/QueryRegexFinderTest.php:128 > > FAILURES! > Tests: 129, Assertions: 255, Failures: 4, Skipped: 24. > Tue, 26 Sep 2023 06:53:48 + - Killing process with ID 1290407 > make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/09/25/php-arthurhoaro-web-thumbnailer_2.1.0+dfsg-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- This doesn't fail anymore. Closing.--- End Message ---
Bug#1042231: marked as done (ipxe: FTBFS: arch/x86/image/bootsector.c:85: Error: operand size mismatch for `push')
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1042231, regarding ipxe: FTBFS: arch/x86/image/bootsector.c:85: Error: operand size mismatch for `push' 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.) -- 1042231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipxe Version: 1.0.0+git-20190125.36a4c85-5.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DARCH=x86_64 -DPLATFORM=efi -DSECUREBOOT=0 -fstrength-reduce > -fomit-frame-pointer -falign-jumps=1 -falign-loops=1 -falign-functions=1 -m64 > -mno-mmx -mno-sse -fshort-wchar -Ui386 -Ulinux -DNVALGRIND -fpie > -mno-red-zone -Iinclude -I. -Iarch/x86/include -Iarch/x86_64/include > -Iarch/x86_64/include/efi -Os -g -ffreestanding -fcommon -Wall -W > -Wformat-nonliteral -fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions > -fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-address > -Wno-stringop-truncation -ffunction-sections -include include/compiler.h > -DASM_TCHAR='@' -DASM_TCHAR_OPS='@' -DOBJECT=multiboot -c > arch/x86/image/multiboot.c -o bin-x86_64-efi/multiboot.o > arch/x86/image/bootsector.c: Assembler messages: > arch/x86/image/bootsector.c:85: Error: operand size mismatch for `push' > make[2]: *** [Makefile.housekeeping:938: bin-x86_64-efi/bootsector.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/26/ipxe_1.0.0+git-20190125.36a4c85-5.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- This doesn't fail anymore. Closing.--- End Message ---
Bug#1052729: marked as done (cogl: FTBFS if Mesa is currently a release candidate)
Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052729, regarding cogl: FTBFS if Mesa is currently a release candidate 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.) -- 1052729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cogl Version: 1.22.8-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I.. -I.. -I./deprecated -I./winsys -I./driver/gl -I./driver/gl/gl > -I./driver/gl/gles -DG_LOG_DOMAIN=\"Cogl\" -DCOGL_COMPILATION > -DCOGL_GL_LIBNAME=\"libGL.so.1\" -DCOGL_GLES1_LIBNAME=\"\" > -DCOGL_GLES2_LIBNAME=\"libGLESv2.so.2\" > -DCOGL_LOCALEDIR=\""/usr/share/locale"\" -DCOGL_DEFAULT_DRIVER=\"gl\" > -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/cairo -I/usr/include/libpng16 > -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -pthread > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/libdrm > -DCOGL_GL_DEBUG -DCOGL_OBJECT_DEBUG -DCOGL_ENABLE_DEBUG -Wall -Wcast-align > -Wformat -Wformat-security -Werror=uninitialized -Werror=empty-body > -Werror=init-self -Werror=undef -Werror=declaration-after-statement > -Werror=vla -Werror=pointer-arith -Werror=missing-declarations > -Werror=maybe-uninitialized -DG_DISABLE_DEPRECATED > -DG_DISABLE_SINGLE_INCLUDES -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o cogl-enum-types.lo > cogl-enum-types.c > winsys/cogl-winsys-egl-kms.c: In function ‘crtc_copy’: > winsys/cogl-winsys-egl-kms.c:636:3: warning: ‘g_memdup’ is deprecated: Use > 'g_memdup2' instead [-Wdeprecated-declarations] > 636 | new->connectors = g_memdup (from->connectors, from->count * > sizeof(uint32_t)); > | ^~~ > In file included from /usr/include/glib-2.0/glib/gstring.h:37, > from /usr/include/glib-2.0/glib/giochannel.h:36, > from /usr/include/glib-2.0/glib.h:56, > from winsys/cogl-winsys-egl-kms.c:49: > /usr/include/glib-2.0/glib/gstrfuncs.h:350:23: note: declared here > 350 | gpointer g_memdup (gconstpointer mem, > | ^~~~ > In file included from ../cogl/cogl-macros.h:36, > from ../cogl/cogl-texture.h:52, > from ../cogl/cogl-framebuffer.h:60, > from ../cogl/cogl-primitive.h:48, > from ../cogl/cogl-context.h:47, > from ./cogl-onscreen.h:41, > from winsys/cogl-winsys-private.h:35, > from winsys/cogl-winsys-egl-kms-private.h:36, > from winsys/cogl-winsys-egl-kms.c:55: > winsys/cogl-winsys-egl-kms.c: In function > ‘_cogl_winsys_onscreen_swap_buffers_with_damage’: > ../config.h:20:25: error: missing binary operator before token "~" >20 | #define COGL_GBM_MICRO 0~rc4 > | ^ > ../cogl/cogl-version.h:159:7: note: in definition of macro > ‘COGL_VERSION_ENCODE’ > 159 || (micro)) > | ^ > winsys/cogl-winsys-egl-kms.c:920:59: note: in expansion of macro > ‘COGL_GBM_MICRO’ > 920 | #if (COGL_VERSION_ENCODE (COGL_GBM_MAJOR, COGL_GBM_MINOR, > COGL_GBM_MICRO) >= \ > | > ^~ > winsys/cogl-winsys-egl-kms.c:924:12: warning: implicit declaration of > function ‘gbm_bo_get_pitch’; did you mean ‘gbm_bo_get_width’? > [-Wimplicit-function-declaration] > 924 | stride = gbm_bo_get_pitch (kms_onscreen->next_bo); > |^~~~ > |gbm_bo_get_width > make[5]: *** [Makefile:1786: winsys/cogl-winsys-egl-kms.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/09/25/cogl_1.22.8-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results A
Bug#1054921: Build error for quantlib-swig on mips64el
The Debian package fails to build now on mipsel, a log is at [1]. The gist seems to be a relocation error: g++ -shared -Wl,-O1 -Wl,-Bsymbolic-functions -O0 -g0 -mxgot --param ggc-min-expand=20 -DBOOST_NO_AUTO_PTR build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o -L/usr/lib/mips64el-linux-gnuabi64 -L/usr/lib -lQuantLib -o build/lib.linux-mips64-cpython-311/QuantLib/_QuantLib.cpython-311-mips64el-linux-gnuabi64.so -fopenmp build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function `virtual thunk to QuantLib::HimalayaOption::arguments::~arguments()': quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption9argumentsD1Ev[_ZN8QuantLib14HimalayaOption9argumentsD1Ev]+0x104): relocation truncated to fit: R_MIPS_GOT_PAGE against `.text._ZN8QuantLib14HimalayaOption9argumentsD1Ev' Luigi, and idea if that is a known swig-on-mips64el issue and if we can addres it with particular flag? As the Debian bug report at [2] states, "this used to work" and I didn't change anything for the 1.32 pair of quantlib and quantlib-swig. For quantlib-swig, and for a few years now, I set some exotic compiler flags: ifneq "$(findstring $(cpu), mipsel mips mips64el)" "" compilerflags = -O0 -g0 -mxgot --param ggc-min-expand=20 -DBOOST_NO_AUTO_PTR endif but that mostly came from trying to keep the build with time or ram limits. Any hints would be most welcome. Cheers, Dirk [1] https://buildd.debian.org/status/fetch.php?pkg=quantlib-swig=mips64el=1.32-1=1698321785=0 [2] https://bugs.debian.org/1054921, also in CC for this email -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory
Lucas, I am afraid I still cannot reproduce this. I attach my successful .buildinfo. What are the differences to yours? Thanks Mark Format: 1.0 Source: insserv Binary: insserv insserv-dbgsym Architecture: amd64 Version: 1.24.0-1 Checksums-Md5: 3c928ff0990c2942950fa368b3978086 79480 insserv-dbgsym_1.24.0-1_amd64.deb 9bffd1e3395d57a5979030bc472dc80c 50572 insserv_1.24.0-1_amd64.deb Checksums-Sha1: aa26018adc027c1af58704991d3339c1a43dccf2 79480 insserv-dbgsym_1.24.0-1_amd64.deb 1d1a7b8f6e5b5ea864a7661f34e767b9a93e4b77 50572 insserv_1.24.0-1_amd64.deb Checksums-Sha256: 39912ad2e18538a91ae397467a6cd96519dd948fee2ed90b39c40b4477352bc1 79480 insserv-dbgsym_1.24.0-1_amd64.deb e4e58a1a6a3cb6a68e205341606b1702ef10dd5bd6d43af03e123b536b4cc8f8 50572 insserv_1.24.0-1_amd64.deb Build-Origin: Debian Build-Architecture: amd64 Build-Date: Sun, 29 Oct 2023 13:16:40 + Build-Path: /build/insserv-1.24.0 Build-Tainted-By: merged-usr-via-aliased-dirs Installed-Build-Depends: autoconf (= 2.71-3), automake (= 1:1.16.5-1.3), autopoint (= 0.21-12), autotools-dev (= 20220109.1), base-files (= 13), base-passwd (= 3.6.1), bash (= 5.2.15-2+b2), bash-completion (= 1:2.11-8), binutils (= 2.40.50.20230625-1), binutils-common (= 2.40.50.20230625-1), binutils-x86-64-linux-gnu (= 2.40.50.20230625-1), bsdextrautils (= 2.38.1-5+b1), bsdutils (= 1:2.38.1-5+b1), build-essential (= 12.10), bzip2 (= 1.0.8-5+b1), coreutils (= 9.1-1), cpp (= 4:12.3.0-1), cpp-10 (= 10.4.0-9), cpp-11 (= 11.4.0-1), cpp-12 (= 12.3.0-5), cpp-6 (= 6.5.0-2), cpp-8 (= 8.4.0-4), cpp-9 (= 9.5.0-3), dash (= 0.5.12-6), debconf (= 1.5.82), debhelper (= 13.11.4), debianutils (= 5.7-0.4), dh-autoreconf (= 20), dh-strip-nondeterminism (= 1.13.1-1), diffutils (= 1:3.8-4), dpkg (= 1.21.22), dpkg-dev (= 1.21.22), dwz (= 0.15-1), file (= 1:5.44-3), findutils (= 4.9.0-4), g++ (= 4:12.3.0-1), g++-12 (= 12.3.0-5), gcc (= 4:12.3.0-1), gcc-10 (= 10.4.0-9), gcc-10-base (= 10.4.0-9), gcc-11 (= 11.4.0-1), gcc-11-base (= 11.4.0-1), gcc-12 (= 12.3.0-5), gcc-12-base (= 12.3.0-5), gcc-13-base (= 13.1.0-7), gcc-6 (= 6.5.0-2), gcc-6-base (= 6.5.0-2), gcc-7-base (= 7.4.0-14), gcc-8 (= 8.4.0-4), gcc-8-base (= 8.4.0-4), gcc-9 (= 9.5.0-3), gcc-9-base (= 9.5.0-3), gettext (= 0.21-12), gettext-base (= 0.21-12), grep (= 3.8-5), groff-base (= 1.22.4-10), gzip (= 1.12-1), hostname (= 3.23+nmu1), init-system-helpers (= 1.65.2), intltool-debian (= 0.35.0+20060710.6), libacl1 (= 2.3.1-3), libarchive-zip-perl (= 1.68-1), libasan3 (= 6.5.0-2), libasan5 (= 9.5.0-3), libasan6 (= 11.4.0-1), libasan8 (= 13.1.0-7), libatomic1 (= 13.1.0-7), libattr1 (= 1:2.5.1-4), libaudit-common (= 1:3.0.9-1), libaudit1 (= 1:3.0.9-1), libbinutils (= 2.40.50.20230625-1), libblkid1 (= 2.38.1-5+b1), libbz2-1.0 (= 1.0.8-5+b1), libc-bin (= 2.36-9), libc-dev-bin (= 2.36-9), libc6 (= 2.36-9), libc6-dev (= 2.36-9), libcap-ng0 (= 0.8.3-1+b3), libcap2 (= 1:2.66-4), libcc1-0 (= 13.1.0-7), libcilkrts5 (= 7.4.0-14), libcom-err2 (= 1.47.0-2), libcrypt-dev (= 1:4.4.35-1), libcrypt1 (= 1:4.4.35-1), libctf-nobfd0 (= 2.40.50.20230625-1), libctf0 (= 2.40.50.20230625-1), libdb5.3 (= 5.3.28+dfsg2-1), libdebconfclient0 (= 0.270), libdebhelper-perl (= 13.11.4), libdpkg-perl (= 1.21.22), libelf1 (= 0.188-2.1), libfile-find-rule-perl (= 0.34-3), libfile-stripnondeterminism-perl (= 1.13.1-1), libgcc-10-dev (= 10.4.0-9), libgcc-11-dev (= 11.4.0-1), libgcc-12-dev (= 12.3.0-5), libgcc-6-dev (= 6.5.0-2), libgcc-8-dev (= 8.4.0-4), libgcc-9-dev (= 9.5.0-3), libgcc-s1 (= 13.1.0-7), libgcrypt20 (= 1.10.2-2), libgdbm-compat4 (= 1.23-3), libgdbm6 (= 1.23-3), libgmp10 (= 2:6.2.1+dfsg1-1.1), libgomp1 (= 13.1.0-7), libgpg-error0 (= 1.46-1), libgprofng0 (= 2.40.50.20230625-1), libgssapi-krb5-2 (= 1.20.1-2), libicu72 (= 72.1-3), libisl19 (= 0.20-2), libisl22 (= 0.22.1-1), libisl23 (= 0.26-3), libitm1 (= 13.1.0-7), libjansson4 (= 2.14-2), libk5crypto3 (= 1.20.1-2), libkeyutils1 (= 1.6.3-2), libkrb5-3 (= 1.20.1-2), libkrb5support0 (= 1.20.1-2), liblsan0 (= 13.1.0-7), liblz4-1 (= 1.9.4-1), liblzma5 (= 5.4.1-0.2), libmagic-mgc (= 1:5.44-3), libmagic1 (= 1:5.44-3), libmd0 (= 1.1.0-1), libmount1 (= 2.38.1-5+b1), libmpc3 (= 1.3.1-1), libmpfr6 (= 4.2.0-1), libmpx2 (= 8.4.0-4), libnsl-dev (= 1.3.0-2), libnsl2 (= 1.3.0-2), libnumber-compare-perl (= 0.03-3), libpam-modules (= 1.5.2-6), libpam-modules-bin (= 1.5.2-6), libpam-runtime (= 1.5.2-6), libpam0g (= 1.5.2-6), libpcre2-8-0 (= 10.42-1), libperl5.36 (= 5.36.0-7), libpipeline1 (= 1.5.7-1), libquadmath0 (= 13.1.0-7), libseccomp2 (= 2.5.4-1+b3), libselinux1 (= 3.4-1+b6), libsmartcols1 (= 2.38.1-5+b1), libssl3 (= 3.0.9-1), libstdc++-12-dev (= 12.3.0-5), libstdc++6 (= 13.1.0-7), libsub-override-perl (= 0.09-4), libsystemd0 (= 253-4), libtext-glob-perl (= 0.11-3), libtinfo6 (= 6.4-4), libtirpc-common (= 1.3.3+ds-1), libtirpc-dev (= 1.3.3+ds-1), libtirpc3 (= 1.3.3+ds-1),
Bug#1055021: linux: mips64el loongson3 kernel crashes when running cmake
Source: linux Version: 5.10.197-1 Severity: grave Tags: upstream patch X-Debbugs-Cc: d...@debian.org, debian-m...@lists.debian.org The loongson3 flavour of the mips64el kernel crash when running cmake: | [ 4390.501529] do_cpu invoked from kernel context![#1]: | [ 4390.506483] CPU: 3 PID: 24061 Comm: iou-sqp-22284 Not tainted 5.10.0-26-loongson-3 #1 Debian 5.10.197-1 | [ 4390.515820] Hardware name: Loongson Lemote-3A4000-7A-1w-V1.00-A1901/Lemote-3A4000-7A-1w-V1.00-A1901, BIOS Loongson-PMON-V3.3-20201222 12/22/2020 | [ 4390.528699] $ 0 : 80bf9030 0001 98020f844000 | [ 4390.536669] $ 4 : 9801017bb2c0 80dbc0b8 0008 02008200 | [ 4390.544634] $ 8 : 0001 0001 02e27c19 | [ 4390.552600] $12 : 5400cce0 80199c00 01ea 01ea | [ 4390.560565] $16 : 980100253700 80ecc740 9800023cb8c0 | [ 4390.568530] $20 : 80ecdce0 9801017bb2c0 9801017bb8e0 | [ 4390.576495] $24 : 0028 98020f847e58 | [ 4390.584461] $28 : 98020f844000 98020f847d40 9800023cb8c0 80bf925c | [ 4390.592426] Hi : 00de | [ 4390.595974] Lo : d70a40ec | [ 4390.599532] epc : 802177c0 _save_fp+0x10/0xa0 | [ 4390.604727] ra : 80bf925c __schedule+0x804/0xe08 | [ 4390.610263] Status: 5400cce2 KX SX UX KERNEL EXL | [ 4390.614949] Cause : 102c (ExcCode 0b) | [ 4390.618930] PrId : 0014c004 (ICT Loongson-3) | [ 4390.623257] Modules linked in: asix usbnet mii sg ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables nfnetlink_log nfnetlink xt_hashlimit ipt_REJECT nf_reject_ipv4 xt_NFLOG xt_multiport xt_tcpudp xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter sch_fq tcp_bbr fuse drm drm_panel_orientation_quirks configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic ohci_pci dm_mod r8169 realtek mdio_devres ohci_hcd ehci_pci of_mdio xhci_pci xhci_hcd ehci_hcd fixed_phy libphy usbcore usb_common | [ 4390.671116] Process iou-sqp-22284 (pid: 24061, threadinfo=743a6e5b, task=63cca72a, tls=00fff0de98e0) | [ 4390.681930] Stack : 80ed 80ed 98020f6e8c40 | [ 4390.689897] 98020004 d37c8307c148dccb 9801017bb2c0 | [ 4390.697863] 0001 90 | [ 4390.721759] 980104957480 98020f6e8c00 80ed | [ 4390.729724] 98020f6e8c40 98020f6e8c08 | [ 4390.737689] 9801017bb2c0 802c61f8 98020f6e8c48 | [ 4390.745655] 98020f6e8c48 2d7071732d756f69 003438323232 d37c8307c148dccb | [ 4390.753621] 807106e0 98020f6e8c00 9801097e90c8 7400cce0 | [ 4390.761588] ... | [ 4390.764017] Call Trace: | [ 4390.766453] [] _save_fp+0x10/0xa0 | [ 4390.771306] [] __schedule+0x804/0xe08 | [ 4390.776497] [] schedule+0x58/0x150 | [ 4390.781432] [] io_sq_thread+0x550/0x578 | [ 4390.786798] [] ret_from_kernel_thread+0x14/0x1c | [ 4390.792856] | [ 4390.794330] Code: 000c6940 05a10011 f4830b10 f4850b30 f4870b50 f4890b70 f48b0b90 | [ 4390.804038] | [ 4411.502993] rcu: INFO: rcu_preempt self-detected stall on CPU | [ 4411.508728] rcu: 1-...!: (5250 ticks this GP) idle=2c6/1/0x4002 softirq=1149627/1149627 fqs=4 | [ 4411.518413] (t=5254 jiffies g=735145 q=4914963) | [ 4411.522999] rcu: rcu_preempt kthread starved for 5248 jiffies! g735145 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=2 | [ 4411.533458] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. | [ 4411.542535] rcu: RCU grace-period kthread stack dump: | [ 4411.547552] task:rcu_preempt state:R stack: 0 pid: 13 ppid: 2 flags:0x0010 | [ 4411.555860] Stack : 80ed 80bff978 80ed 8031bbd4 | [ 4411.563826] 0004 d37c8307c148dccb 98010025 00208040 | [ 4411.571791] 80ed 9801002c7c98 80ed 80f62ce0 | [ 4411.579756] 0006 0001 80bf98b8 | [ 4411.587721] 0001000f9aa0 80bfdb98 | [ 4411.595686] 8030bbc8 5400cce1 80ed | [ 4411.603651] 98000236cc78 0001000f9aa0 80319968 0842 | [ 4411.611617] 98010025 d37c8307c148dccb 80f62a80 | [ 4411.619582] 80ed 80ed 80ecdce0 8030b40c | [ 4411.627548] 80ef11f0 80ed 811f 80f6 | [ 4411.635515] ... | [ 4411.637947] Call Trace: | [ 4411.640384] [] __schedule+0x50c/0xe08 | [ 4411.645586] [] schedule+0x58/0x150 | [ 4411.650527] [] schedule_timeout+0x98/0x1e8 | [ 4411.656156]
Bug#1052859: geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2
Hi, On So 29 Okt 2023 11:17:21 CET, Mike Gabriel wrote: Investigating deeper... underlying cause that introduced this FTBFS in geonames is this patch [1] in glibc (added with glibc 2.37-8): [1] https://salsa.debian.org/glibc-team/glibc/-/blob/sid/debian/patches/any/git-c-utf-8-language.diff I just rebuilt 2.37-12 (glibc version currently in unstable) with that patch disabled in d/p/series and geonames builds fine again. Cc:ing Aurelien Jarno who cherry-picked that patch from upstream into the glibc Debian package. @Aurelien: Any idea, what my cause the observed FTBFS in geonames (#1052859). Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgp_J7R_wNJ2q.pgp Description: Digitale PGP-Signatur
Bug#1054777: marked as done (libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2)
Your message dated Sun, 29 Oct 2023 12:34:08 +
with message-id
and subject line Bug#1054777: fixed in libfiu 1.1-5
has caused the Debian Bug report #1054777,
regarding libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C
returned exit code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfiu
Version: 1.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/tests/utils'
> mkdir -p libs/
> ln -f ../../preload/posix/fiu_posix_preload.so libs/
> ln -f ../../preload/run/fiu_run_preload.so libs/
> LD_LIBRARY_PATH=../../libfiu/ ./test-basic_ctrl.py >
> output-test-basic_ctrl.py.txt 2>&1
> LD_LIBRARY_PATH=../../libfiu/ ./test-basic_run.sh >
> output-test-basic_run.sh.txt 2>&1
> ./generate-test -c tests/fprintf.conf -o tests/fprintf.c
> ./generate-test -c tests/fread.conf -o tests/fread.c
> ./generate-test -c tests/kill.conf -o tests/kill.c
> ./generate-test -c tests/malloc.conf -o tests/malloc.c
> ./generate-test -c tests/mmap.conf -o tests/mmap.c
> cc -I../../libfiu/ -L../../libfiu/ -L./ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE
> -fPIC -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -std=c99 -pedantic -Wall -std=c99
> -pedantic -Wall -L. binary.c -lfiu -lcoltest -o binary
> ./generate-test -c tests/open.conf -o tests/open.c
> ln -f ../preload/posix/fiu_posix_preload.so libs/
> ln -f ../preload/run/fiu_run_preload.so libs/
> ./generate-test -c tests/open64.conf -o tests/open64.c
> ./generate-test -c tests/pread.conf -o tests/pread.c
> ./generate-test -c tests/pread64.conf -o tests/pread64.c
> ./generate-test -c tests/strdup.conf -o tests/strdup.c
> cc -I../libfiu/ -L../libfiu/ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE -fPIC
> -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -std=c99 -pedantic -Wall \
> -rdynamic -fno-optimize-sibling-calls test-enable_stack.c -lfiu
> -lpthread -o test-enable_stack
> test-enable_stack.c: In function 'main':
> test-enable_stack.c:32:50: warning: ISO C forbids conversion of function
> pointer to object pointer type [-Wpedantic]
>32 | r = fiu_enable_stack("fp-1", 1, NULL, 0, (void *) , -1);
> | ^
> cc -I../libfiu/ -L../libfiu/ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE -fPIC
> -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -std=c99 -pedantic -Wall \
> -rdynamic -fno-optimize-sibling-calls test-enable_stack_by_name.c -lfiu
> -lpthread -o test-enable_stack_by_name
> cc -I../../libfiu/ -L../../libfiu/ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE -fPIC
> -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -std=c99 -pedantic -Wall -std=c99
> -pedantic -Wall tests/fopen.c -lfiu -o tests/fopen.bin
> LD_LIBRARY_PATH="./:../../libfiu/" ./binary
> make[4]: Leaving directory '/<>/tests/collisions'
> cc -I../libfiu/ -L../libfiu/ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE -fPIC
> -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -std=c99 -pedantic -Wall
> test-ferror.c -lfiu -lpthread -o test-ferror
> cc -I../../libfiu/ -L../../libfiu/ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE -fPIC
> -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -std=c99 -pedantic -Wall -std=c99
> -pedantic -Wall tests/fprintf.c -lfiu -o tests/fprintf.bin
> cc -I../../libfiu/ -L../../libfiu/ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE -fPIC
> -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -std=c99 -pedantic -Wall -std=c99
> -pedantic -Wall tests/fread.c -lfiu -o tests/fread.bin
> cc -I../../libfiu/ -L../../libfiu/ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE -fPIC
> -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
>
Bug#1054687: marked as done (nmap: FTBFS: ld: nse_main.o:(.data.rel.ro+0x38): undefined reference to `luaopen_lpeg(lua_State*)')
Your message dated Sun, 29 Oct 2023 12:19:35 + with message-id and subject line Bug#1054687: fixed in nmap 7.94+git20230807.3be01efb1+dfsg-2 has caused the Debian Bug report #1054687, regarding nmap: FTBFS: ld: nse_main.o:(.data.rel.ro+0x38): undefined reference to `luaopen_lpeg(lua_State*)' 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.) -- 1054687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nmap Version: 7.94+git20230807.3be01efb1+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -MM -I../libdnet-stripped/include -Wdate-time -D_FORTIFY_SOURCE=2 > -I../nbase -I../nsock/include ArgParser.cc common.cc common_modified.cc > nping.cc NpingOps.cc utils.cc utils_net.cc output.cc stats.cc NpingTargets.cc > NpingTarget.cc EchoHeader.cc EchoServer.cc EchoClient.cc ProbeMode.cc > NEPContext.cc Crypto.cc > makefile.dep > /usr/bin/ld: nse_main.o:(.data.rel.ro+0x38): undefined reference to > `luaopen_lpeg(lua_State*)' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2023/10/27/nmap_7.94+git20230807.3be01efb1+dfsg-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nmap Source-Version: 7.94+git20230807.3be01efb1+dfsg-2 Done: Sergio de Almeida Cipriano Junior We believe that the bug you reported is fixed in the latest version of nmap, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergio de Almeida Cipriano Junior (supplier of updated nmap 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: Fri, 27 Oct 2023 19:42:53 -0300 Source: nmap Architecture: source Version: 7.94+git20230807.3be01efb1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Sergio de Almeida Cipriano Junior Closes: 1054687 Changes: nmap (7.94+git20230807.3be01efb1+dfsg-2) unstable; urgency=medium . * Team upload. * Remove d/p/0003-Link-against-lua-lpeg.patch: - It is being removed because it is no longer needed, since the problem was resolved in 2016, and because it is making the package unreproduciple. The build failed due to "undefined reference to luaopen_lpeg(lua_State*)". More info at the bug this is related or at upstream discussion on github: https://github.com/nmap/nmap/issues/237 https://seclists.org/nmap-dev/2016/q1/268 (closes: #1054687) Checksums-Sha1: 4219fbb8df52bde1c60b6337fce1d5d6299741ea 2422 nmap_7.94+git20230807.3be01efb1+dfsg-2.dsc 69c0e92f1b5433e4bd976d75d7d035696bda1925 21924 nmap_7.94+git20230807.3be01efb1+dfsg-2.debian.tar.xz 67739bfc79c6490214767f95e0fad7fbff64 10772 nmap_7.94+git20230807.3be01efb1+dfsg-2_amd64.buildinfo Checksums-Sha256: 61e1839dafc4998e73263a2d8930b847603cde052c313842f3ab6b1e9272031d 2422 nmap_7.94+git20230807.3be01efb1+dfsg-2.dsc b2bd38fc942c3fde8ebba1d7b6f9e2005dd7faf5f778936ba7dcd3bb6c9e2095 21924 nmap_7.94+git20230807.3be01efb1+dfsg-2.debian.tar.xz e5c87b3c51e101cd65c52f5e1d41d5ee07602e99962a40ab105e509c6d718057 10772 nmap_7.94+git20230807.3be01efb1+dfsg-2_amd64.buildinfo Files:
Bug#1055017: node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED
Source: node-html-webpack-plugin Version: 5.5.3+~cs14.4.8-1 Severity: serious On 2023-10-29 04:49, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package node-html-minifier-terser, version > 5.5.3+~cs14.4.8-1, for all, > however unstable already has version 7.2.0~5.5.3+~cs14.4.7-2. > Uploads to unstable must have a higher version than present in unstable. > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Processed: rm
Processing commands for cont...@bugs.debian.org: > reassign 1053673 ftp.debian.org Bug #1053673 [src:libwnck] RM: libwnck -- RoQA; leaf library; depends on gtk2 Bug reassigned from package 'src:libwnck' to 'ftp.debian.org'. No longer marked as found in versions libwnck/2.30.7-6. Ignoring request to alter fixed versions of bug #1053673 to the same values previously set > severity 1053673 normal Bug #1053673 [ftp.debian.org] RM: libwnck -- RoQA; leaf library; depends on gtk2 Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1053673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 965979, found 965979 in 2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u2 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 965979
Bug #965979 {Done: Mike Gabriel } [src:freerdp2]
freerdp2: CVE-2020-15103
Unarchived Bug 965979
> found 965979 2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u2
Bug #965979 {Done: Mike Gabriel } [src:freerdp2]
freerdp2: CVE-2020-15103
Marked as found in versions
freerdp2/2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u2.
> fixed 965979 2.3.0+dfsg1-2+deb10u3
Bug #965979 {Done: Mike Gabriel } [src:freerdp2]
freerdp2: CVE-2020-15103
The source 'freerdp2' and version '2.3.0+dfsg1-2+deb10u3' do not appear to
match any binary packages
Marked as fixed in versions freerdp2/2.3.0+dfsg1-2+deb10u3.
> archive 965979
Bug #965979 {Done: Mike Gabriel } [src:freerdp2]
freerdp2: CVE-2020-15103
archived 965979 to archive/79 (from 965979)
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
965979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected
Processing control commands:
> found -1 1.9.6-2
Bug #1054323 {Done: Andreas Tille } [src:r-cran-tmb]
r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package
version inconsistency detected
Marked as found in versions r-cran-tmb/1.9.6-2; no longer marked as fixed in
versions r-cran-tmb/1.9.6-2 and reopened.
--
1054323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054323: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected
Control: found -1 1.9.6-2 > still depends on: > r-cran-matrix (>= 1.6-1.1) > > So the version is still not correct. Note that this is Depends, not Build-Depends. I found that in debian/control, r-cran-tmb has Depends: r-cran-matrix (>= 1.5-3-1~), but this is somehow replaced in the binary package, presumably by dh-r? Andreas, would it be possible for dh-r to always replace the version in r-cran-tmb's Depends with r-cran-matrix (>= [the version of r-cran-matrix it was built with]) ? Then you can avoid modifying Build-Depends and upstream's DESCRIPTION, and will allow r-cran-tmb to be binNMU'd when needed. It should also allow for easier backporting. Regards Graham
Bug#1054777: Fwd: Bug#1054777: libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2
On Sat, Oct 28, 2023 at 09:58:14AM +0100, Chris Lamb wrote: Hey Alberto, Hope all is well with you. Just wondering if you received the below re. a recently-filed bug report against libfiu. I can reproduce it locally if that helps. I got it, but I appreciate you forwarding it explicitly anyway just in case, and the confirmation of a reproduction! ./wrap-python 3 ./test-basic.py Can't find python3 bindings, run make python3 make[3]: *** [Makefile:96: py-run-test-basic] Error 1 Looking at this, I don find any issues with the Makefile dependency chain itself. I think this is likely a problem I already fixed back in February in commit 5dcc6d4. https://blitiri.com.ar/git/r/libfiu/c/5dcc6d449dc86d4ba9abc99ac52fd5798e573738/ There have been a few commits since v1.1, I think a v1.2 is probably overdue at this point in any case. Chris, do you want to confirm that patch fixes the issue in the Debian build environment? And if so I can just make a 1.2 including it. Do you think that would be the most practical course of action here? Thank you! Alberto
Bug#1033252: marked as done (maradns: CVE-2022-30256)
Your message dated Sun, 29 Oct 2023 10:49:24 + with message-id and subject line Bug#1033252: fixed in maradns 2.0.13-1.5 has caused the Debian Bug report #1033252, regarding maradns: CVE-2022-30256 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.) -- 1033252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: maradns X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for maradns. CVE-2022-30256[0]: | An issue was discovered in MaraDNS Deadwood through 3.5.0021 that | allows variant V1 of unintended domain name resolution. A revoked | domain name can still be resolvable for a long time, including expired | domains and taken-down malicious domains. The effects of an exploit | would be widespread and highly impactful, because the exploitation | conforms to de facto DNS specifications and operational practices, and | overcomes current mitigation patches for "Ghost" domain names. https://maradns.samiam.org/security.html#CVE-2022-30256 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-30256 https://www.cve.org/CVERecord?id=CVE-2022-30256 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: maradns Source-Version: 2.0.13-1.5 Done: Aron Xu We believe that the bug you reported is fixed in the latest version of maradns, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aron Xu (supplier of updated maradns 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: Sun, 29 Oct 2023 18:14:50 +0800 Source: maradns Architecture: source Version: 2.0.13-1.5 Distribution: unstable Urgency: high Maintainer: Dariusz Dwornikowski Changed-By: Aron Xu Closes: 1033252 1035936 Changes: maradns (2.0.13-1.5) unstable; urgency=high . * Non-maintainer upload by the Security Team, patches are from Bastien Roucariès of LTS team. * CVE-2023-31137: integer underflow in the DNS packet decompression (Closes: #1035936). * CVE-2022-30256: revoked and expired domains remain resolvable for a long time (Closes: #1033252). Checksums-Sha1: e4e8ca1f5c605119884e26e30e58d3857eead7d0 1761 maradns_2.0.13-1.5.dsc 565fab4c0ff2882e3acaa25490141c2ad337d88e 48204 maradns_2.0.13-1.5.debian.tar.xz fcf773db1faec1407aa9b0a35db50091ffbb0c3b 6370 maradns_2.0.13-1.5_source.buildinfo Checksums-Sha256: a4a27818fa6440856db9315e9af994bbb75b6082a877264d0a6b4c5d42ba7877 1761 maradns_2.0.13-1.5.dsc 117e72046c205e86f1b62ae0fce9cf43348209f96c7ff528e8c8b70e68a697e6 48204 maradns_2.0.13-1.5.debian.tar.xz 0a11cd7f69b3b5f8a2cca947b50b257ffb3155e2618e7f01cf5cf11cb1364a9a 6370 maradns_2.0.13-1.5_source.buildinfo Files: 941e56123943c63bb4ea300e49e8ced3 1761 net extra maradns_2.0.13-1.5.dsc 368a8b68fc2f5d87a76f2328d3695011 48204 net extra maradns_2.0.13-1.5.debian.tar.xz 3712f2335f5ba016ed9694fbce4f3b05 6370 net extra maradns_2.0.13-1.5_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhhz+aYQl/Bp4OTA7O1LKKgqv2VQFAmU+NZUACgkQO1LKKgqv 2VSZeQf9Gw6Okk85qmPdhy4j2fRYxzDHW8m6hvaH+Vqj4sAPuJprt/IqvUPaOqvh AgcJ2J5fT5rQUNdkVeVsAcWyj539GV1LbJbj3z96dr+dGhYzn1dV5PpXnh1yDAVP hQRtf9gBZkAIE9IT5od4i4eP5w61q/f6Z5ZpwIiOIzeOR9DSMPDGMFPM2Lc4bwjn 10aeCF5vmfm6IKdi6+PnUhxPgkG2pASqGDT0Q5iRb+87X0sGVO4Oi6n2Vg2PKIgo ZfNxqVRT7JxiDc3cNr2MUTau4wVOpHIBNNVbi8pjc79wzjN1Nkfo58ahvuFDVqQP uuW/P7Ls0rg/tyJ4grmL0Gm5PggkAg== =Exbc -END PGP SIGNATURE End Message ---
Bug#1054750: reuse: FTBFS: make: *** [debian/rules:4: binary] Error 1
Caused by dh-python #1055008
Bug#1052859: geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2
Hi Santiago,
On So 29 Okt 2023 10:35:13 CET, Santiago Vila wrote:
El 29/10/23 a las 7:59, Mike Gabriel escribió:
ERROR:./tests/test-geonames.c:110:assert_first_names: assertion
failed (geonames_city_get_country (city) == expected_country):
("United States of America" == "\303\211tats Unis")
not ok /translations -
ERROR:./tests/test-geonames.c:110:assert_first_names: assertion
failed (geonames_city_get_country (city) == expected_country):
("United States of America" == "\303\211tats Unis")
This is an interesting FTBFS. Do your test servers have a
non-C.UTF-8 locale configured on system level? It looks like we
should run unit tests with LANG=C.UTF-8 exported.
Hello. You are right that apparently this seems a locale problem,
but no, I can also
reproduce it using C.UTF-8.
The probably reason for this is that some locales recently moved from tzdata
to tzdata-legacy and your package is using some of those locales that moved
to tzdata-legacy.
Several solutions for that are explained in the link provided by Lucas,
and more precisely here:
https://wiki.debian.org/qa.debian.org/FTBFS#A2023-09-28_tzdata-legacy_split_from_tzdata
Hmmm... interesting... adding tzdata-legacy as B-D does not help, either.
Investigating deeper...
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgp4AGs5ohGdy.pgp
Description: Digitale PGP-Signatur
Bug#1052859: geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2
El 29/10/23 a las 7:59, Mike Gabriel escribió:
ERROR:./tests/test-geonames.c:110:assert_first_names: assertion failed (geonames_city_get_country
(city) == expected_country): ("United States of America" == "\303\211tats Unis")
not ok /translations - ERROR:./tests/test-geonames.c:110:assert_first_names: assertion failed
(geonames_city_get_country (city) == expected_country): ("United States of America" ==
"\303\211tats Unis")
This is an interesting FTBFS. Do your test servers have a non-C.UTF-8 locale
configured on system level? It looks like we should run unit tests with
LANG=C.UTF-8 exported.
Hello. You are right that apparently this seems a locale problem, but no, I can
also
reproduce it using C.UTF-8.
The probably reason for this is that some locales recently moved from tzdata
to tzdata-legacy and your package is using some of those locales that moved
to tzdata-legacy.
Several solutions for that are explained in the link provided by Lucas,
and more precisely here:
https://wiki.debian.org/qa.debian.org/FTBFS#A2023-09-28_tzdata-legacy_split_from_tzdata
Thanks.
Bug#1054946: marked as done (distro-info: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)
Your message dated Sun, 29 Oct 2023 09:04:12 + with message-id and subject line Bug#1054946: fixed in distro-info 1.7 has caused the Debian Bug report #1054946, regarding distro-info: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: distro-info Version: 1.6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./test-debian-distro-info > cd perl && ./test.pl > testAlias > testAll > py3versions: no X-Python3-Version in control file, using supported versions > testDevel > cd python && python3.11 setup.py test > 1..35 > ok 1 - unique: Matching lists > ok 2 - symmetric_difference: Matching lists > ok 3 - unique: 1 Unique Item > ok 4 - unique: 1 Unique Item in the haystack > ok 5 - symmetric_difference: 1 Unique Item > ok 6 - Debian all > ok 7 - Debian devel > ok 8 - Debian oldstable > ok 9 - Debian stable > ok 10 - Debian testing > ok 11 - Debian valid > ok 12 - Debian valid > ok 13 - Debian invalid > ok 14 - Debian supported > ok 15 - Debian LTS > ok 16 - Debian ELTS > ok 17 - Debian unsupported > ok 18 - Debian codename, invalid > ok 19 - Debian codename > ok 20 - Debian version, invalid > ok 21 - Debian version > testOldstable > ok 22 - Ubuntu all > ok 23 - Ubuntu version > ok 24 - Ubuntu LTS version > ok 25 - Ubuntu devel > ok 26 - Ubuntu LTS > ok 27 - Ubuntu stable > ok 28 - Ubuntu valid > ok 29 - Ubuntu invalid > ok 30 - Ubuntu is_lts > ok 31 - Ubuntu !is_lts > ok 32 - Ubuntu !is_lts > ok 33 - Ubuntu supported > ok 34 - Ubuntu ESM > ok 35 - Ubuntu unsupported > testStable > testSupported > testLTS > testELTS > testUnsupported > testTesting > testFullname > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > /usr/lib/python3/dist-packages/setuptools/command/test.py:193: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > ir_d = dist.fetch_build_eggs(dist.install_requires) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:194: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > tr_d = dist.fetch_build_eggs(dist.tests_require or []) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:195: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > er_d = dist.fetch_build_eggs( > WARNING: The wheel package is not available. > running egg_info > creating distro_info.egg-info > writing distro_info.egg-info/PKG-INFO > writing dependency_links to distro_info.egg-info/dependency_links.txt > writing top-level names to distro_info.egg-info/top_level.txt > writing manifest file 'distro_info.egg-info/SOURCES.txt' > testRelease > reading manifest file 'distro_info.egg-info/SOURCES.txt' > writing manifest file 'distro_info.egg-info/SOURCES.txt' > running build_ext > testSeries > testCombinedShortform > test_flake8 (distro_info_test.test_flake8.Flake8TestCase.test_flake8) > Test: Run flake8 on Python source code.
Processed: Bug#1054946 marked as pending in distro-info
Processing control commands: > tag -1 pending Bug #1054946 [src:distro-info] distro-info: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 Added tag(s) pending. -- 1054946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054946: marked as pending in distro-info
Control: tag -1 pending Hello, Bug #1054946 in distro-info 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/debian/distro-info/-/commit/64aecef3f187152cdf13c8d9d982c25de9502882 Update tests for distro-info-data 0.59, which adjusted Debian 7's EoL (Closes: #1054946) (this message was generated automatically) -- Greetings https://bugs.debian.org/1054946
Bug#1052926: marked as done (elisp-bug-hunter: FTBFS: make: *** [debian/rules:4: binary] Error 25)
Your message dated Sun, 29 Oct 2023 08:23:00 + with message-id and subject line Bug#1052926: fixed in elisp-bug-hunter 1.3.1+repack-7 has caused the Debian Bug report #1052926, regarding elisp-bug-hunter: FTBFS: make: *** [debian/rules:4: binary] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: elisp-bug-hunter Version: 1.3.1+repack-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with elpa >dh_update_autotools_config >dh_autoreconf >dh_elpa_test > emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list > \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list > 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f > package-initialize -L . -l bug-hunter-test.el --eval > \(ert-run-tests-batch-and-exit\) > Package cl is deprecated > Running 6 tests (2023-09-26 06:46:42+, selector ‘t’) > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: > The following error was signaled here: > (void-variable not-defined) > Caused by the following expression: > not-defined > > > Doing some initial tests... > Initial tests done. Hunting for the cause... > Testing: 1/5 > Testing: 2/5 > Testing: 3/5 > Testing: 4/5 > Testing: 5/5 > nil, line 12 pos 90: >
Bug#1053170: marked as done (Apache NOTICE file missing from binary package)
Your message dated Sun, 29 Oct 2023 08:24:13 + with message-id and subject line Bug#1053170: fixed in rust-bat 0.23.0-5 has caused the Debian Bug report #1053170, regarding Apache NOTICE file missing from binary package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1053170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bat Version: 0.23.0-4 Severity: serious bat's upstream source and the rust-bat_0.23.0.orig.tar.gz file both contain a NOTICE file which, per the packages's Apache 2.0 license, must be preserved in derivative works. However, this NOTICE file is not present in the binary .deb packages distributed by Debian. Note that bat itself embeds the text of the NOTICE file in its own binary, and the text is displayed when running `batcat --acknowledgements`. However, Paul Wise has stated on the debian-legal mailing list that the NOTICE should still be distributed as a file in the .deb packages: https://lists.debian.org/debian-legal/2023/09/msg00012.html --- End Message --- --- Begin Message --- Source: rust-bat Source-Version: 0.23.0-5 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of rust-bat, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated rust-bat 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: Sun, 29 Oct 2023 08:59:59 +0100 Source: rust-bat Architecture: source Version: 0.23.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Sylvestre Ledru Closes: 1053170 Changes: rust-bat (0.23.0-5) unstable; urgency=medium . * Package bat 0.23.0 from crates.io using debcargo 2.6.0 * Also install the notice file (#Closes: 1053170) Checksums-Sha1: 9ac5ed25d71e3fa83c0e9f6527500ed485ba7ba9 3817 rust-bat_0.23.0-5.dsc 537cbc28e4598987b02e7bf6970ad64920a0a97b 10768 rust-bat_0.23.0-5.debian.tar.xz b38b82067de41dd790fe5ee75b288fcdbf9fadef 13948 rust-bat_0.23.0-5_source.buildinfo Checksums-Sha256: 798f8d89bb297fe7ace8a4e200f50499210b0a0847c0aeb49bfebf17098e7968 3817 rust-bat_0.23.0-5.dsc 65c84eb96277201bc367c461787ba61fd0ce839a496693071ad0b480bea84ce8 10768 rust-bat_0.23.0-5.debian.tar.xz 0cffeb9837e73ab7a0fc89175f76441d8c8d0c76895189e6768af2cd8f2351c0 13948 rust-bat_0.23.0-5_source.buildinfo Files: a73d06c1836997791201abf4a3454f7d 3817 utils optional rust-bat_0.23.0-5.dsc c758e75286ebe2a39e24c99d92ec52d3 10768 utils optional rust-bat_0.23.0-5.debian.tar.xz c92c9a7b03ed5c325508e4c449552782 13948 utils optional rust-bat_0.23.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmU+EQUACgkQfmUo2nUv G+HmTg//TWBFUnxmnv8cBApYDS97lwDLdYM52/bsTTj+wqE32vuCFxGfPeqS5YuE nfehQYj7AzN6wtd8C97JFHCQ5ydtlDVht+FsSlr5uxygNGr/ip3C3i+qEz+4rAPq V7d4yDISdBeEeGn+bGUJw1vXR4fKwCVjniTlCwNZqp3qqWW2u31xpRP2wM6jX1rv UGSzgmjSkO6mGYEAYY35X/WcjNPjlPvLalns1ToRpDgLPfj0XiG1I3HD12C/Ln4g kyC95UHsN9ss02kCiAqEvQuwi7WOlndRjtYlDXy2GKWh2pTyTrHcyHQ4bmqvr8y/ qNJtd1cgwvzTnDi2WOeAgeOBbbVV5lorFUSOwfD5B6kdPbN1oUkxTYgi7E3uPAxI H4DC6BCGzgv1yYr/zQEURL0gMGRZNOxwx+DhdjNGj6b39U+JeyT03MajVidW+SdH HIpttO+03t0Y3VjOUe+fmE2OMs5JXo45yuAN2Qz4O7qOt145ESFGz6zwmIV4E+Wu NUkFMZ+gDW3wCs9foY5JbHUOsy/xdFbKIqplbhfG1hPY07OvAluXQzQ5iddgfExU kRdRuXrxVzh16c00g5a6OOkgDrwOjvvbs8bJEebTADbn8U0PHIzqFLKxU67qz6Rx VzkC8GLFLbtKf/jk8joLFhkTnmU1paVL6NXKk02uQN8ZAsUa0Uw= =UP9E -END PGP SIGNATURE End Message ---
Bug#1054667: [Pkg-javascript-devel] Bug#1054667: node-browserify-sign: CVE-2023-46234
Hi Yadd, On Sat, Oct 28, 2023 at 12:05:25PM +0400, Yadd wrote: > On 10/27/23 20:20, Moritz Mühlenhoff wrote: > > Source: node-browserify-sign > > X-Debbugs-CC: t...@security.debian.org > > Severity: grave > > Tags: security > > > > Hi, > > > > The following vulnerability was published for node-browserify-sign. > > > > CVE-2023-46234[0]: > > | browserify-sign is a package to duplicate the functionality of > > | node's crypto public key functions, much of this is based on Fedor > > | Indutny's work on indutny/tls.js. An upper bound check issue in > > | `dsaVerify` function allows an attacker to construct signatures that > > | can be successfully verified by any public key, thus leading to a > > | signature forgery attack. All places in this project that involve > > | DSA verification of user-input signatures will be affected by this > > | vulnerability. This issue has been patched in version 4.2.2. > > > > https://github.com/browserify/browserify-sign/security/advisories/GHSA-x9w5-v3q2-3rhw > > https://github.com/browserify/browserify-sign/commit/85994cd6348b50f2fd1b73c54e20881416f44a30 > > > > > > If you fix the vulnerability please also make sure to include the > > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > > > For further information see: > > > > [0] https://security-tracker.debian.org/tracker/CVE-2023-46234 > > https://www.cve.org/CVERecord?id=CVE-2023-46234 > > > > Please adjust the affected versions in the BTS as needed. > > Hi, > > please find attached the debdiff for Bookworm Thanks looks good and think we can release a DSA for it. FTR, please wait next time for an ack first. Regards, Salvatore
Bug#1040801: marked as done (mcomix: pillow 10.0.0 not recognized as higher than 6.0.0)
Your message dated Sun, 29 Oct 2023 07:19:04 + with message-id and subject line Bug#1040801: fixed in mcomix 3.0.0-1 has caused the Debian Bug report #1040801, regarding mcomix: pillow 10.0.0 not recognized as higher than 6.0.0 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.) -- 1040801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mcomix Version: 2.1.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, Since python3-pil:amd64 upgrade from 9.5.0-1 to 10.0.0-1, it's impossible to launch mcomix : $ mcomix 22:02:01 [MainThread] ERROR: You don't have the required version of the Python Imaging Library Fork (Pillow) installed. 22:02:01 [MainThread] ERROR: Installed Pillow version is: 10.0.0 22:02:01 [MainThread] ERROR: Required Pillow version is: 6.0.0 or higher Downgrading python3-pil to 9.5.0-1 solves the problem, but it removes other packages I use (qgis, matplotlib). Regards, Sébastien -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (980, 'unstable'), (970, 'testing'), (960, 'stable'), (500, 'testing-debug') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mcomix depends on: ii gir1.2-gtk-3.03.24.37-2 ii python3 3.11.4-5 ii python3-cairo 1.24.0-1 ii python3-gi3.42.2-3+b1 ii python3-gi-cairo 3.42.2-3+b1 ii python3-pil 10.0.0-1 Versions of packages mcomix recommends: ii python3-chardet 5.1.0+dfsg-2 Versions of packages mcomix suggests: pn lhasa ii mupdf-tools 1.22.2+ds1-1 ii p7zip16.02+dfsg-8 ii unrar1:6.2.8-1 ii unzip6.0-28 -- no debconf information --- End Message --- --- Begin Message --- Source: mcomix Source-Version: 3.0.0-1 Done: Emfox Zhou We believe that the bug you reported is fixed in the latest version of mcomix, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emfox Zhou (supplier of updated mcomix 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 Oct 2023 14:49:52 +0800 Source: mcomix Architecture: source Version: 3.0.0-1 Distribution: unstable Urgency: medium Maintainer: Emfox Zhou Changed-By: Emfox Zhou Closes: 1040801 Changes: mcomix (3.0.0-1) unstable; urgency=medium . * New upstream release. - Move to pyproject.toml packaging. - Fix pillow dependency. (Closes: #1040801) Checksums-Sha1: 3b3bd47de8f9b6a7282cd82805a70302c5f5c33f 1771 mcomix_3.0.0-1.dsc 137d1281ff6cc78f8af3acd7d26e56b9cdebb3ba 76 mcomix_3.0.0.orig.tar.gz 09b68c2975da04924e47cca82719ac01f012970a 3652 mcomix_3.0.0-1.debian.tar.xz 2213b603493ae438bc396678654fbbc74be2b16e 6305 mcomix_3.0.0-1_source.buildinfo Checksums-Sha256: 0ab721d3a34c592e0e82d2e7c601e6265b23ec13a9d562a3d1ed72b64d96807a 1771 mcomix_3.0.0-1.dsc 2270c43d75e2878f64e4c886d5b013125c42894b364594d5ec979154c4dea004 76 mcomix_3.0.0.orig.tar.gz b8bbc395f0ec63a5de0a024544a79cc899acdaf0b6e18a6c78434aa87a94fa3f 3652 mcomix_3.0.0-1.debian.tar.xz 695f057a82be2f6a4019ced384b63345ff3a38b51b2dd6c5232d871f62a5b2a6 6305 mcomix_3.0.0-1_source.buildinfo Files: ddb9621cd43787974d6968aea8d96c06 1771 x11 optional mcomix_3.0.0-1.dsc 02e48327276c4a2d9942224fd3776c04 76 x11 optional mcomix_3.0.0.orig.tar.gz 43ed9036c8b84abfbe18fdc5cc41805c 3652 x11 optional mcomix_3.0.0-1.debian.tar.xz 223363163926c5874c7b1d41e5d72069 6305 x11 optional mcomix_3.0.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEGSauJtItZVqOiaNpgImbv9t7vZQFAmU+At4ACgkQgImbv9t7 vZSzPRAAgp3Fseiyc0EK2UP+v8iYR7BgoDMIzI3RnS9ikNeVrN1g2ORNfJFwdpzj V8JDuIyGI6+wVvvrdzfuIsto9A5TOp65fsTtzaDh/KFQ5fyLJ8nCfQhcDuze5FVf
Bug#1052859: geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2
Hi Lucas,
On Di 26 Sep 2023 15:17:58 CEST, Lucas Nussbaum wrote:
Source: geonames
Version: 0.3.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process --verbose -j8
UpdateCTestConfiguration from
:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
UpdateCTestConfiguration from
:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
Test project /<>/obj-x86_64-linux-gnu
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
Start 1: test_geonames
1: Test command: /<>/obj-x86_64-linux-gnu/tests/test_geonames
1: Working Directory: /<>/obj-x86_64-linux-gnu/tests
1: Test timeout computed to be: 1000
1: TAP version 13
1: # random seed: R02S845fe55aee887825f93218b66afea354
1: 1..4
1: ok 1 /common-cities
1: # slow test /common-cities executed in 0.59 secs
1: **
1: ERROR:./tests/test-geonames.c:110:assert_first_names: assertion
failed (geonames_city_get_country (city) == expected_country):
("United States of America" == "\303\211tats Unis")
1: not ok /translations -
ERROR:./tests/test-geonames.c:110:assert_first_names: assertion
failed (geonames_city_get_country (city) == expected_country):
("United States of America" == "\303\211tats Unis")
1: Bail out!
1/1 Test #1: test_geonames Subprocess
aborted***Exception: 1.17 sec
TAP version 13
# random seed: R02S845fe55aee887825f93218b66afea354
1..4
ok 1 /common-cities
# slow test /common-cities executed in 0.59 secs
**
ERROR:./tests/test-geonames.c:110:assert_first_names: assertion
failed (geonames_city_get_country (city) == expected_country):
("United States of America" == "\303\211tats Unis")
not ok /translations -
ERROR:./tests/test-geonames.c:110:assert_first_names: assertion
failed (geonames_city_get_country (city) == expected_country):
("United States of America" == "\303\211tats Unis")
Bail out!
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 1.17 sec
The following tests FAILED:
1 - test_geonames (Subprocess aborted)
Errors while running CTest
make[2]: *** [Makefile:74: test] Error 8
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test
ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/geonames_0.3.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff
it with mine
so that we can identify if something relevant changed in the meantime.
This is an interesting FTBFS. Do your test servers have a non-C.UTF-8
locale configured on system level? It looks like we should run unit
tests with LANG=C.UTF-8 exported.
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgpW25ODfwy4A.pgp
Description: Digitale PGP-Signatur
Bug#1051739: marked as done (1.26.0-3 uninstallable due to nonexistent package)
Your message dated Sun, 29 Oct 2023 06:49:01 + with message-id and subject line Bug#1051739: fixed in caja-dropbox 1.26.0-4 has caused the Debian Bug report #1051739, regarding 1.26.0-3 uninstallable due to nonexistent package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1051739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: caja-dropbox Version: 1.26.0-3 Severity: normal -3 of this package cannot be installed because it depends on: > --- libayatana-appindicator1 | libappindicator1 (UNAVAILABLE) libayatana-appindicator3-1 is available on bookworm, but not testing or sid. Adding this was done apparently to fix an Ubuntu bug, but it completely broke the package installation for Debian. Actually, it broke the package on Ubuntu too—the only version of Ubuntu that has libayatana-appindicator1 is 22.10. It's not in 23.04 and won't be in 23.10 either. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-0-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages caja-dropbox (1.26.0-2) depends on: ii dbus-x11 1.14.10-1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1 ii gir1.2-glib-2.0 1.78.0-1 ii gir1.2-gtk-3.03.24.38-5 ii gir1.2-pango-1.0 1.51.0+ds-2 ii libc6 2.37-8 ii libcaja-extension11.26.1-1 ii libglib2.0-0 2.78.0-1 ii libgtk-3-03.24.38-5 ii policykit-1 123-1 ii procps2:4.0.3-1 ii python3 3.11.4-5+b1 ii python3-gi3.44.1-2 ii python3-gpg 1.18.0-3+b1 caja-dropbox recommends no packages. Versions of packages caja-dropbox suggests: ii caja 1.26.1-1 -- no debconf information --- End Message --- --- Begin Message --- Source: caja-dropbox Source-Version: 1.26.0-4 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of caja-dropbox, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated caja-dropbox 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: Sun, 29 Oct 2023 07:30:54 +0100 Source: caja-dropbox Architecture: source Version: 1.26.0-4 Distribution: unstable Urgency: medium Maintainer: Debian+Ubuntu MATE Packaging Team Changed-By: Mike Gabriel Closes: 1051739 Changes: caja-dropbox (1.26.0-4) unstable; urgency=medium . * debian/control: + Drop from D: libayatana-appindicator1 | libappindicator1. Not required anymore since proprietary Dropbox GUI has moved to PyQt5 and bundles all required libraries. (Closes: #1051739). Checksums-Sha1: 54fe4ea37cfaf84414fddeb528620306b901f83f 2379 caja-dropbox_1.26.0-4.dsc fe4e5acd6b636cfe9607792d683ef611aa7e6380 13916 caja-dropbox_1.26.0-4.debian.tar.xz 0382ddd2729adca113e1ae65c250bcc3e8d22f1c 16968 caja-dropbox_1.26.0-4_source.buildinfo Checksums-Sha256: 6a4b14dba0ec6a717cbe84f800d772e437c3cc3f3096e90a572a83dde67a053b 2379 caja-dropbox_1.26.0-4.dsc e735543ae1b9c535b9f6e36eb87942d68188c3288986ea81be7ab04d24937c16 13916 caja-dropbox_1.26.0-4.debian.tar.xz e366ecd79b21a1c3c10405e847f30d14aa7f710f571e3fd7b1048627bcc5c0f7 16968 caja-dropbox_1.26.0-4_source.buildinfo Files: cf9efbeab1650a9c627da7cca0ad2c6d 2379 non-free/x11 optional caja-dropbox_1.26.0-4.dsc 0950321c7408c1d1e668d9353e07aba1 13916 non-free/x11 optional caja-dropbox_1.26.0-4.debian.tar.xz d028240c4a6c77212c85407d9d20eec8 16968 non-free/x11 optional caja-dropbox_1.26.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmU9/EYVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxATIQAKkfRXiIuFnBIVMOuS9h4Gu5WfwF
Bug#1053673: RM: libwnck -- RoQA; leaf library; depends on gtk2
reassign -1 ftp.debian.org On So 08 Okt 2023 16:21:11 CEST, Bastian Germann wrote: Source: libwnck Severity: serious Version: 2.30.7-6 Please remove libwnck. It does not have any reverse dependencies anymore and depends on the obsolete gtk2. I am going to file a RM bug when this is autoremoved from testing. Reassigning to ftp.debian.org, so the removal request gets seen by ftp masters. Thanks! Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpP9bXuIoY7Q.pgp Description: Digitale PGP-Signatur
Bug#1037366: libplank-dev: depends on deprecated libgdk-pixbuf2.0-dev
Hi Bastian, On Sa 21 Okt 2023 12:11:16 CEST, Bastian Germann wrote: I am uploading a NMU in order to fix this. The debdiff is attached. .debdiff applied in packaging Git now. More ideal than sending the .debdiff to the original bug that gets closed by the .debdiff is sending the .debdiff as a new bug report. Closed bug reports disappear from the devs' radar whereas open/new bug reports do not so. light+love + thanks for qa'ing, Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpmjkPGivTTq.pgp Description: Digitale PGP-Signatur
Processed: Bug#1051739 marked as pending in caja-dropbox
Processing control commands: > tag -1 pending Bug #1051739 [caja-dropbox] 1.26.0-3 uninstallable due to nonexistent package Added tag(s) pending. -- 1051739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
